Hi.
On Sun, Aug 13, 2023 at 04:53:13PM -0500, Steve Langasek wrote:
> On Fri, Aug 04, 2023 at 10:55:44AM +0300, Reco wrote:
> > On Fri, Aug 04, 2023 at 08:55:21AM +0200, Rainer Dorsch wrote:
> > > dmesg reports for end0:
> > > [7.771809] fec 2188000.et
ry adding "net.ifnames=0" to kernel's commandline.
Reco
Hi.
On Mon, Apr 17, 2023 at 02:48:44AM -0700, Rick Thomas wrote:
> Sadly, when I do:
> i2cdetect -l
> I get nothing back. Leading me to conclude that there are no busses
> available.
"modprobe i2c-dev" should fix that.
Reco
ect to clarify things.
Reco
ly
> recent u-boot platforms in Debian, and u-boot has been blocked from
> migration to testing partly because of this.
>
> As the bookworm freeze approaches, this is getting to be... worrysome!
That Ordoid N2 board that I had was damaged about year ago.
I have not procured a replacement to it since then.
So I cannot test u-boot on Odroid N2 in the foreseeable future.
Reco
On Fri, Sep 10, 2021 at 12:04:56PM -0400, Gene Heskett wrote:
> So why do we not have a .deb builder for kernels.?
wiki.debian.org is your friend, consider learning how to search it.
In this particular case, you probably want [1].
Reco
[1] https://wiki.debian.
Hi.
On Fri, Sep 10, 2021 at 08:07:56AM -0400, Gene Heskett wrote:
> On Friday 10 September 2021 06:59:17 Reco wrote:
>
> > On Fri, Sep 10, 2021 at 09:50:24AM +0200, LinAdmin wrote:
> > > I have some doubts that debian.net has the same ownership
> > > than of
Hi.
On Fri, Sep 10, 2021 at 09:50:24AM +0200, LinAdmin wrote:
> I have some doubts that debian.net has the same ownership
> than official debian.org?
RPi images from raspi.debian.net are GPG-signed by Gunnar Wolf's key
(who is Debian Developer), that's good enough for me.
Reco
Hi.
On Thu, Sep 09, 2021 at 08:11:43PM +1000, Keith Bainbridge wrote:
> On 7/9/21 22:46, Reco wrote:
> > > Some will recall the discussion around raspberry adding a MS repo to
> > > sources.list last year.
> > I've "installed" fresh RaspiOS recentl
w thread.
Frankly, this subthread belongs to debian-user, there's nothing
ARM-specific here.
In the case of further questions regarding sshfs or network filesystems
in general I suggest you to start a new thread at debian-user.
Reco
On Tue, Sep 07, 2021 at 03:02:20PM +0100, Pete Batard wrote:
> On 2021.09.07 13:31, Reco wrote:
> > Yet there's a difference. Intel ME or AMD PSP do not require firmware to
> > be written on a boot media, thus making the boot media redistributable
> > and (other blobs exclu
user pi.
IMO that's expected from fuse.
> Some will recall the discussion around raspberry adding a MS repo to
> sources.list last year.
I've "installed" fresh RaspiOS recently and they're still doing it.
Reco
[1] https://www.khadas.com/product-page/edge-v
[2] https://www.hard
On Tue, Sep 07, 2021 at 11:00:29AM +0100, Pete Batard wrote:
> Hi Reco,
>
> On 2021.09.07 10:42, Reco wrote:
> > Hi.
> >
> > On Tue, Sep 07, 2021 at 10:29:40AM +0100, Pete Batard wrote:
> > > Hi Gunnar,
> > >
> > > On 2021.09.06 18:59,
nd the same has been true for Buster on the Pi 3 for some
> time too [2].
A small nitpick. While it's indeed possible to boot rebuilt UEFI on
Raspberry Pi3 (which is free software, since it's patched TianoCore),
and boot unmodified Debian ARM64 via said UEFI - the booting of UEFI
itself still requires Broadcom blobs, which are non-free software.
Reco
https://raspi.debian.net
> I switched to Ubuntu LTS which made me (and many others) happy.
Whatever floats your boat.
Reco
04.
And if soldering is not your cup of tea - look for so-called Breakout
Board Kit, like that one - [1].
[1] https://www.amazon.com/DS1307-Real-Clock-Breakout-Board/dp/B00NAY199E
Reco
amp on reboot) solves
it to some extent, but nothing else does.
Reco
othing.
End result - you can measure whatever happens during the boot just fine,
but you start 1st Jan 1970 0:00 each boot.
You see, the problem is not the timekeeping, it's the setting
more-or-less the same time on different systems.
Reco
Hi.
On Sun, Feb 21, 2021 at 06:10:08PM +0200, Andrei POPESCU wrote:
> On Du, 21 feb 21, 09:20:07, Jeffrey Walton wrote:
> > On Sun, Feb 21, 2021 at 8:58 AM Reco wrote:
> > > On Sun, Feb 21, 2021 at 08:42:45AM -0500, Alan Corey wrote:
> > > > I guess a q
" (i.e. before NTP time
sync kicks in), and that's valuable to me by itself.
Reco
Hi.
On Sun, Feb 21, 2021 at 02:26:26AM -0800, Rick Thomas wrote:
> On Sat, Feb 20, 2021, at 11:14 PM, Reco wrote:
> > Hi.
> >
> > On Sat, Feb 20, 2021 at 10:53:18PM -0800, Rick Thomas wrote:
> > > root@pi:~# ls -l /dev/rtc*
> > > ls:
berry PI has RTC, so this is
expected.
Reco
u-boot
didn't even launch - see bl31.bin.log.
Reco
G12B:BL:6e7c85:7898ac;FEAT:E0F83180:2000;POC:F;RCY:0;EMMC:800;NAND:81;SD?:0;SD:0;READ:0;0.
bl2_stage_init 0x01
bl2_stage_init 0x81
hw id: 0x - pwm id 0x01
bl2_stage_init 0xc1
bl2_stage_init 0x02
no sdio debug board detected
L0:
L1:070
On Wed, Jan 06, 2021 at 10:19:48AM -0800, Vagrant Cascadian wrote:
> On 2021-01-06, Reco wrote:
> > On Tue, Oct 27, 2020 at 10:20:28PM +0300, Reco wrote:
> >> On Tue, Oct 27, 2020 at 10:21:01AM -0700, Vagrant Cascadian wrote:
> >> > Please file bugs and/or merge req
Hi.
On Tue, Oct 27, 2020 at 10:20:28PM +0300, Reco wrote:
> On Tue, Oct 27, 2020 at 10:21:01AM -0700, Vagrant Cascadian wrote:
> > Please file bugs and/or merge requests on u-boot and
> > arm-trusted-firmware if you want to get those parts enabled for Odroid
> > N2
n.org, so it
could take some time to reach bugs.d.o.
Reco
On Tue, Oct 27, 2020 at 08:59:38AM -0700, Vagrant Cascadian wrote:
> On 2020-10-27, Reco wrote:
> > On Tue, Oct 27, 2020 at 08:02:18AM -0700, Vagrant Cascadian wrote:
> >> It looks like u-boot 2020.10 has an odroid-n2 target and
> >> arm-trusted-firmware 2.3 has an amlog
> to test them semi-regularly.
I happen to have an Odroid N2. What exactly such testing would require?
Reco
here's nothing ARM-specific in this problem.
Second,
> ii pi-bluetooth 0.1.15
> all Raspberry Pi 3 bluetooth
Proper Debian does not provide this package, and a certain popular
GNU/Linux distribution for Raspberry Pi is an off-topic here.
Reco
Hi.
On Thu, May 28, 2020 at 12:48:47AM -0500, Gunnar Wolf wrote:
> Reco dijo [Sun, Apr 26, 2020 at 01:29:13PM +0300]:
> > > There is a very minor issue with the 0/1 image (which I intend to fix
> > > now).
> >
> > There are two, actually:
> >
&g
.. enable SSH access?
Not for the root user. These images have Debian default set in
sshd_config, and for this specific case it's "PermitRootLogin
prohibit-password". You'll probably need to change that. Or get
yourself USB TTL adapter and hook up to the UART.
Reco
pre-up iptables-restore < /etc/iptables/rules.v4
pre-up ip6tables-restore < /etc/iptables/rules.v6
2) An attempt to launch agetty on ttyS1 (which should be uart console
according to /proc/cmdline) fails with:
agetty[655]: /dev/ttyS1: not a tty
Reco
pected.
Reco
ses,
Glxgears is an old and somewhat obsolete benchmark.
Try using glmark instead.
Reco
only possible culprit being the installation of u-boot itself
(by d-i) itself, in the case that Debian-provided u-boot is unable to
function on that particular board. Which is not the case for HC2, but I
lack HC1 to check it.
Reco
to date and seem to work pretty reliably.
I've yet to see an announcement from Armbian at oss-security maillist.
E-mails from Debian Developers land at oss-security within a day of
publishing DSA.
Reco
[1] https://wiki.debian.org/InstallingDebianOn/OdroidHC1
ious
> release?)
QNAP TS-419. HDD LEDs were red for me since I installed Debian there
(squeeze IIRC).
I worked around it by setting qpios 46, 47, 48 and 49 to "out" like
this:
echo 46 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio46/direction
echo 1 > /sys/class/gpio/gpio46/value
echo 46 > /sys/class/gpio/unexport
Reco
On Tue, Jul 30, 2019 at 06:02:05AM -0400, Gene Heskett wrote:
> > > That simple question is:
> > >
> > > What log file do you want to see?
> >
> > Assuming Debian defaults - /var/log/kern.log,
>
> is empty. kern.log.1 is over 200k, and the list won't accept that.
This very e-mail that I'm
On Mon, Jul 29, 2019 at 07:56:25AM -0400, Gene Heskett wrote:
> On Monday 29 July 2019 05:08:49 Reco wrote:
>
> > On Sun, Jul 28, 2019 at 08:15:20PM -0400, Gene Heskett wrote:
> > > On Sunday 28 July 2019 00:27:36 Reco wrote:
> > > > On Sun, Jul 28, 2019 at 12:
Hi.
On Sun, Jul 28, 2019 at 08:15:20PM -0400, Gene Heskett wrote:
> On Sunday 28 July 2019 00:27:36 Reco wrote:
>
> > On Sun, Jul 28, 2019 at 12:13:21AM -0400, Gene Heskett wrote:
> > > > > That, and a whole restaraunt sized menu of dpkg stuff for
On Sun, Jul 28, 2019 at 11:04:41AM +0200, Luca Olivetti wrote:
> El 27/7/19 a les 23:20, Reco ha escrit:
>
> >
> > > yet it always gets the name wlxe894f615307a.
> >
> > What you're doing colud work.
> > The problem is - you have NIC that's attached via U
On Sun, Jul 28, 2019 at 06:50:53AM -0400, Gene Heskett wrote:
> On Sunday 28 July 2019 00:27:36 Reco wrote:
>
> > On Sun, Jul 28, 2019 at 12:13:21AM -0400, Gene Heskett wrote:
> > > > > That, and a whole restaraunt sized menu of dpkg stuff for
> > > > >
o ( about
> 1.7 fps for glxgearrs full screen ) that otherwise works well.
It's not a Debian, it's Raspbian.
> > > The user can't even look at dmseg! How dumb is that?
> >
> > A security feature. If you want that:
> >
> No Reco, its not security, its harassment
t dmseg! How dumb is that?
A security feature. If you want that:
/sbin/sysctl -w kernel.dmesg_restrict=0
Reco
dictably™.
In your place I'd consider myself lucky - at least you have a network
interface that's always called eth0, the way the kernel wants it.
> Extra points if it involves getting rid of systemd altogether ;-)
It won't help you here. To solve this particular problem once and for
all, you need a replacement for udev, which Debian does not provide.
Reco
o disconnect ALL that stuff. ;-)
An exaggeration. My installation was successful with the following
devices attached to the board:
USB keyboard
HDMI-to-VGA adapter
Raspberry Pi Camera
Ethernet cable
I was too lazy to dig out that USB TTL cable for the true console, but I
suppose that it won't interfere either.
Reco
On Sat, Jul 27, 2019 at 12:02:18PM -0400, Gene Heskett wrote:
> On Friday 26 July 2019 17:35:01 Reco wrote:
>
> > Hi.
> >
> > On Thu, Jul 25, 2019 at 12:49:32PM -0400, Gene Heskett wrote:
> > > I am furious (fat lot of good that does me) with the lack of to
you downloaded to the root of the
> FAT partition.
'Extract' does not mean you copy the iso file into the partition.
You mount iso, and copy files from there to the partition's filesystem.
Reco
apt-get source {the-exact-same-package-name}
sudo apt-get source raspberrypi-firmware
As others said, this maillist is unsuitable place for Raspian-specific
question.
Reco
ing all future similar problems (involving
configuration of a resolver, IP routing and package management) to
debian-user.
Thank you in advance, Reco
4) Wayland requires kernel version 5.1 IIRC.
If you need ODroid board you probably better getting yourself ODroid
HC2. That one actually works with Debian stretch and a kernel from the
backports.
Reco
[1] https://forum.odroid.com/viewtopic.php?t=33865
Hi.
On Sat, Oct 20, 2018 at 01:44:36PM +0200, LinAdmin wrote:
> On 19.10.2018 23:35, Reco wrote:
> > Hi.
> >
> > On Fri, Oct 19, 2018 at 11:25:47PM +0200, LinAdmin wrote:
> >> On 19.10.2018 20:12, Uwe Kleine-König wrote:
> >>> Hello,
> >
gged into it, the load average is below
> > 0.1 and according to htop the CPUs run at < 1%.
> >
> > Best regards
> > Uwe
> >
> Using top or htop show that cpu load.
What about 'perf top' result?
I happen to have Armada385/Caiman with stock Debian kernel, and I see no
such CPU load.
Reco
53 matches
Mail list logo
