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

Bug#985956: Installation Report - Bullseye 2021-03-15

Package: installation-reports
Boot method: SSD built with Rufus using this installation guide:
Image version: Debian 11 ARM64 net install ISO 
               Debian-testing-arm64-netinst.iso 2021-03-15 04:03
Date: 2021-03-25 1109
Machine: Raspberry Pi 
Processor: Broadcom BCM2711 - Quad-core Cortex-A72 (ARM v8) 64-bit SoC
Memory: 4GB
Filesystem    Type     1K-blocks   Used Available Use% Mounted on
udev          devtmpfs   1438812      0   1438812   0% /dev
tmpfs         tmpfs       297504    536    296968   1% /run
/dev/sda4     ext4       1883580   3724   1765836   1% /
/dev/sda5     ext4       3764408 961688   2591008  28% /usr
tmpfs         tmpfs      1487504      0   1487504   0% /dev/shm
tmpfs         tmpfs         5120      0      5120   0% /run/lock
/dev/sda8     ext4      99027088 241836  93708724   1% /var
/dev/sda7     ext4       1883580     44   1769516   1% /home
/dev/sda6     ext4       1883580     72   1769488   1% /usr/local
/dev/sda2     ext4       3764408 118432   3434264   4% /boot
/dev/sda1     vfat        391408 342172     49236  88% /boot/efi
tmpfs         tmpfs       297500      0    297500   0% /run/user/1000
Output of lspci -knn (or lspci -nn): Command produces no output  here is the output from lsusb-tv:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/4p, 5000M
   ID 1d6b:0003 Linux Foundation 3.0 root hub
   |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
       ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
   ID 1d6b:0002 Linux Foundation 2.0 root hub
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
       ID 2109:3431 VIA Labs, Inc. Hub
   |__ Port 3: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
       ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
   |__ Port 3: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
       ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot:           [o]
Detect network card:    [e]
Configure network:      [e]
Detect media:           [o]
Load installer modules: [o]
Detect hard drives:     [o]
Partition hard drives:  [o]
Install base system:    [o]
Clock/timezone setup:   [o]
User/password setup:    [o]
Install tasks:          [o]
Install boot loader:    [o]
Overall install:        [o]
Comments/Problems: Other than the not detecting the builtin ethernet adapter, the installation went okay.  The result of the install was a functioning system which when booted would detect and initialize the ethernet adapter.
When the Install process failed to find a dhcp server, I used Alt-F2 to activate a console and searched through the syslog for the error.  I found that the module mdio-bcm-unimac.ko failed to load.  When the newly built system was booted, I copied mdio-bcm-unimac.ko from /lib/modules/5.10.0-5-arm64/kernel/drivers/net/mdio to a usb stick. 
I rebuilt the SSD using Rufus and started the installation process from the beginning.  When the network setup failed to find the dhcp server, I opened the Alt-F2 console, mounted the usb stick, copied the mdio-bcm-unimac.ko module to
/lib/modules/5.10.0-5-arm64/kernel/drivers/net/mdio, and then issued the command insmod to install the module in the kernel.
I used  Alt-F1 to return to the installation process and selected go-back to restart the network configuration process.  The network adapter was initialized, the dhcp server found, and the installation was completed successfully.
This problem has been present in the Bullseye Weekly Builds: 2021-03-01, 2021-03-08, and 2021-03-15.
The problem summary is: mdio-bcm-unimac.ko module is not installed in the kernel.
The problem solution is: install the mdio-bcm-unimac.ko module in the kernel.

Reply to: