GNU bug report logs - #47723
Boot failure with u-boot on cubietruck

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Julien Lepiller <julien <at> lepiller.eu>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#47723: closed (Boot failure with u-boot on cubietruck)
Date: Sat, 17 Apr 2021 18:24:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Sat, 17 Apr 2021 20:22:58 +0200
with message-id <20210417202258.433cca7f <at> tachikoma.lepiller.eu>
and subject line Re: bug#47723: Boot failure with u-boot on cubietruck
has caused the debbugs.gnu.org bug report #47723,
regarding Boot failure with u-boot on cubietruck
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
47723: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=47723
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Julien Lepiller <julien <at> lepiller.eu>
To: bug-guix <at> gnu.org
Subject: Boot failure with u-boot on cubietruck
Date: Mon, 12 Apr 2021 13:18:30 +0200

Hi Guix!

This week-end, I had to reboot my server and it couldn't boot anymore.
It's a Cubietruck, an armhf machine that's in my parents' basement.
They helped me debug the issue (though that was not easy, since they
only have windows machines and not a lot of knowledge about Linux).

At boot, the machine loads the kernel and initramfs, and gets stuck at
"Starting kernel...". We tried booting various generations, including
the very firts generation (as I never had to run guix gc on the
machine, I kept all the generations around, that's 129 of them!). None
of them worked, and they all get stuck at the same message.

I suspect something might have changed in u-boot recently (maybe the
upgrade to 2021.01, since I didn't have to reboot this year yet). The
board might not be initialized as expected and all kernels from 4.19 to
the latest 5.11 fail to boot.

In the end, I reinstalled a foreign distribution (that uses u-boot
2017.01) and can SSH to the machine, but I haven't reinstalled Guix
yet. Guix was installed on an external disk, so I haven't lost anything
other that the bootloader it installed. I can chroot to the Guix system:

  mount -v --bind /dev /mnt/dev
  mount -v --bind /dev/pts /mnt/dev/pts
  mount -vt proc proc /mnt/proc
  mount -vt sysfs sysfs /mnt/sys
  chroot /mnt /run/current-system/profile/bin/bash
  . /etc/profile

What should be my next step?

I tried running guix from inside the chroot:
  /root/.config/current/bin/guix-daemon --build-users-group=guixbuild &

But when I try to use it:

  guix system build /etc/config.scm
  guix system: error: while setting up the build environment: cannot
  pivot old root directory onto
  '/gnu/store/brkm5bb59w9i4kmyznk0k4ndsz6dzq95-system.drv.chroot/real-root':
  Invalid argument

My hope was to run "guix system reconfigure" from the chroot, so I
would not loose my previous generations, and would not have to build
too much, since there are almost no substitutes for armhf.

[Message part 3 (message/rfc822, inline)]

From: Julien Lepiller <julien <at> lepiller.eu>
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 47723-done <at> debbugs.gnu.org
Subject: Re: bug#47723: Boot failure with u-boot on cubietruck
Date: Sat, 17 Apr 2021 20:22:58 +0200

Le Tue, 13 Apr 2021 21:14:49 +0200,
Danny Milosavljevic <dannym <at> scratchpost.org> a écrit :

> Hi Julien,
> 
> On Mon, 12 Apr 2021 13:18:30 +0200
> Julien Lepiller <julien <at> lepiller.eu> wrote:
> 
> > I suspect something might have changed in u-boot recently (maybe the
> > upgrade to 2021.01, since I didn't have to reboot this year yet).   
> [...]
> > board might not be initialized as expected and all kernels from
> > 4.19 to the latest 5.11 fail to boot.  
> 
> Yeah, that happens sometimes with u-boot.  It sucks--but I suspect
> there's just not a lot of people updating their u-boot installation
> all the time (or at all ever).
> 
> I'm not sure whether it's better to just provide the old u-boot or to
> figure out what exactly broke (the latter is probably gonna take
> quite some time).

Thanks for the help, I finally managed to boot it with the newer
2021.04 u-boot. Maybe 2021.01 did something wrong that was fixed later?

> 
> > In the end, I reinstalled a foreign distribution (that uses u-boot
> > 2017.01) and can SSH to the machine, but I haven't reinstalled Guix
> > yet. Guix was installed on an external disk, so I haven't lost
> > anything other that the bootloader it installed. I can chroot to
> > the Guix system:
> > 
> >   mount -v --bind /dev /mnt/dev
> >   mount -v --bind /dev/pts /mnt/dev/pts
> >   mount -vt proc proc /mnt/proc
> >   mount -vt sysfs sysfs /mnt/sys
> >   chroot /mnt /run/current-system/profile/bin/bash
> >   . /etc/profile
> > 
> > What should be my next step?
> > 
> > I tried running guix from inside the chroot:
> >   /root/.config/current/bin/guix-daemon
> > --build-users-group=guixbuild &  
> 
> Try
> 
> unshare -m /root/.config/current/bin/guix-daemon
> --build-users-group=guixbuild &
> 
> It should work then.

Ah, I found another workaround, not sure how it works but, from the
foreign system I could "mount --make-rprivate /" and it would work.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.