[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#989593: installation report Raspberry Pi 4 UEFI



On Tue, Jun 08, 2021 at 11:17:51AM +0200, Cyril Brulebois wrote:
> Marc Haber <mh+debian-packages@zugschlus.de> (2021-06-08):
> > I followed the instructions given on
> > https://www.raspberrypi.org/forums/viewtopic.php?t=282839
> > to install Debian on a Raspberry Pi using the UEFI firmware
> > available for the raspi.
> > 
> > This involves unpacking the official Debian 11 image into an ESP
> > partition on an USB medium and using the Rasberry Pi UEFI firmware
> > to boot the installer via UEFI => grub => Linux. Once the
> > installe has started, this feels 100 % like a standard Debian
> > installation.
> 
> Fun!

Yes!

> > I experienced the following issues:
> > 
> > "Detecting Hardware" complains about missing firmware. I guess
> > that's Wifi related, since the Wifi Interface doesn't work in the
> > installed system and the 1000Base-TX interface works fine without.
> 
> AFAICR (I'll get back to that soon enough) you should get a message
> indicating which files were expected, so that you don't have to guess.

The Raspi 4 has both Wifi and Ethernet interfaces named brcmsomething,
so it's still kind of guessing, but I have verified in the mean time
that it's actually really the Wifi firmware.

> > Requesting German keyboard layout does not work in the beginning of
> > installation, domain name and user name configuration still happens
> > with the default US keyboard layout. Later, when configuring the
> > network mirror, the keyboard layout has been changed to the requested
> > german layout. I guess this happens during base system installation.
> 
> Was that with the text or graphical installer?

Text installer ("expert"). I have used the graphical installer just a
handful of times in two decades.

Since my default domain types differently with US and DE keyboard, I
guess this might be an actual regression, I would have noticed this in
earlier versions of the installer.

> > For very strange reasons, the installed system ends up without
> > /sbin/start-stop-daemon despite the dpkg package being in state "ii".
> > This is reproducible. In the installer, I see a temporary diversion of
> > /sbin/start-stop-daemon, but in the installed system, dpkg-divert
> > --list doesn't show that.
> > 
> > /var/lib/dpkg/diversions-old has those three lines:
> > /sbin/start-stop-daemon
> > /sbin/start-stop-daemon.REAL
> > :
> > 
> > There is no /sbin/start-stop-daemon.REAL though.
> 
> A quick grep across our source packages show 3 possibilities:
>  - debootstrap
>  - debian-installer-utils
>  - apt-setup (code apparently copied from d-i-utils until some clean-up
>    happens, which never did)
> 
> > And, the installed system does neither have /var/log/installer nor
> > /var/log/debian-installer. This is also reproducible :-(   Where would
> > I find the files that get copied to /target/var/log/installer in the
> > still running installer?
> 
> Simply /var/log/syslog for the main log. Other files are mentioned
> there:
>   https://salsa.debian.org/installer-team/installation-report/-/blob/master/debian/installation-report.postinst

Is there anything you need from me to go on?

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421


Reply to: