Boot method: win32-loader 0.10.6
Image version: the one for testing as selected by win32-loader dated Apr/01 or
Apr/02
Date: 2023-Apr-02

Machine: Acer Aspire 4810TZG (laptop)
Partitions:
Sys. de fichiers Type    blocs de 1K  Utilisé Disponible Uti% Monté sur
udev            devtmpfs    1910140        0    1910140  0% /dev
tmpfs            tmpfs        390632    1432    389200  1% /run
/dev/sda6        ext4        50080296 20482704  27021208  44% /
tmpfs            tmpfs        1953144        0    1953144  0% /dev/shm
tmpfs            tmpfs          5120      12      5108  1% /run/lock
tmpfs            tmpfs        390628      76    390552  1% /run/user/1000


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:          [O]
Detect network card:    [O]
Configure network:      [E]
Detect media:          [O]
Load installer modules: [O]
Clock/timezone setup:  [O]
User/password setup:    [O]
Detect hard drives:    [O]
Partition hard drives:  [O]
Install base system:    [O]
Install tasks:          [O]
Install boot loader:    [O]
Overall install:        [O]

Comments/Problems:

I loaded the installer with win32-loader 0.10.6 from a PC running win7
I selected the testing image.

In the installer, it is not possible to use the wifi network to install. The
installer doesn't find the firmware for the wifi device. Installing with wired
network works.

Moreover, after installation, the firmware is not installed for both the wifi
card & the video chip. I had to install them manually. Required fw packages
were:
- firmware-amd-graphics
- firmware-iwlwifi

I expected these packages to be installed by the installer.

See attached logs & lspci output.


Please make sure that any installation logs that you think would
be useful are attached to this report. (You can find them in the
installer system in /var/log/ and later on the installed system
under /var/log/installer.) Please compress large files using gzip.

dmesg output (with firmware packages installed) attached

Hi,

I had a similar experience with a desktop system containing a Radeon
RX470 graphics card.  The text-based installation went all right and
then even the Gnome desktop opened after reboot, but it ran in a
low-resolution mode until I manually installed firmware-amd-graphics
(the non-free-firmware archive component was already enabled).

Is this the intended behaviour?

Ferenc Wágner <wferi@niif.hu> (2023-05-22):

Which installer did you use?


Cheers,

Cyril Brulebois <kibi@debian.org> writes:

Its lsb-release says:

DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230401"
X_INSTALLATION_MEDIUM=netboot

so it must have been bookworm RC 1.  The date was 22nd of April.  I
started the kernel+initrd.gz from GRUB.

I must have sent 1/2 a dozen requests to unscript to this email address.

debian-boot-request@lists.debian.org <mailto:debian-boot-request@lists.debian.org>

This address was in the email headers.

Why am I not being removed?

Ferenc Wágner <wferi@niif.hu> (2023-05-22):

In other words you were also using netboot.

https://wiki.debian.org/DebianInstaller/NetbootFirmware should have
details about how to deal with firmware when netbooting. It's been there
since ~ forever, and has been updated for Bookworm.


Cheers,

Cyril Brulebois <kibi@debian.org> writes:

Thanks for the pointer.  Are you implying that if some firmware isn't
loaded during installation, it isn't expected to be present on the
installed system either?  If so, then it worked for me as intended.
(Actually, my Ethernet driver also tries to load some Realtek firmware,
but apparenetly works just fine without it, so I only installed it later
to reduce warnings from update-initramfs.  The graphics firmware was a
must for desktop usage, though.)

Ferenc Wágner <wferi@niif.hu> (2023-05-23):

I'm implying that installation images produced by debian-cd (and available
on cdimage.d.o) should have firmware packages available and ready to deploy,
and should do that automatically; while netboot images (produced by the
debian-installer build system) don't, and won't be able to deploy firmware
packages unless tweaked beforehand via the procedure documented on that
page.

And yes, I'm seeing similar “wanting while not actually needing” things with
some wireless Realtek hardware locally.


Cheers,

Cyril Brulebois <kibi@debian.org> writes:

Yes, that'f perfectly fine.  My question was whether the relavant
firmware packages should be present on the installed system even if the
installer itself did not use/load them.  The netboot installer installs
everything from the network after all, so it could install firmware
packages just as it installs desktop packages for example.  Apparently
it does not, which is fine again, but I wasn't certain of the intent.