On 31/05/2024 at 10:26, Roland Clobus wrote:
* Moment 1: the first d-i screen is shown. The USB device is seen by the
kernel, but the module is not yet loaded
ls -d /sys/bus/usb/drivers/r8712u/1-3*
No such file or directory
As expected, the module is not loaded so /sys/bus/usb/drivers/r8712u
does not exist.
ls -d /sys/bus/usb/drivers/usb/1-3*
/sys/bus/usb/drivers/usb/1-3
ls -d /sys/bus/usb/devices/1-3/1-3*
/sys/bus/usb/devices/1-3/1-3:1:0
The device is present.
* Moment 2: the d-i screen 'No Ethernet card was detected' is shown
(The firmware has been placed where it can be found, module r8712u has
been removed and added)
ls -d /sys/bus/usb/drivers/r8712u/1-3*
No such file or directory
The module is loaded so /sys/bus/usb/drivers/r8712u should exist but is
not associated with the device.
ls -d /sys/bus/usb/drivers/usb/1-3*
No such file or directory
ls -d /sys/bus/usb/devices/1-3/1-3*
No such file or directory
It looks like the device is not present any more. But there was no
disconnect message in the kernel log. All I can see it the reset
message, but AFAICS a reset should not remove the device. Maybe it was
disabled or powered down.
I do not know enough about the kernel and USB subsystem to have any clue
about what is wrong. Maybe running "udevadm trigger" during specific
moments and recording its output may provide useful information:
- when the adapter is connected
- when the module is loaded without the firmware
- when the adapter is disconnected
- when the module is reloaded with the firmware
You do not have to run check-missing-firmware for this, you can run
modprobe commands in a shell.
* Moment 3: I disconnect and reconnect the USB device in virt-manager
and select 'Detect network hardware' from the d-i menu. d-i shows a list
of SSIDs
ls -d /sys/bus/usb/drivers/r8712u/1-3*
/sys/bus/usb/drivers/r8712u/1-3:1.0
As expected, the device is associated with the driver.
