On Sun, 2024-09-01 at 00:40 +0300, Henrik Ahlgren wrote: > On Sat, 2024-08-31 at 23:22 +0200, Ben Hutchings wrote: > > None of the driver changes are relevant to this system. You are not > > using Hyper-V and Linux 6.1 does not include the USB drivers that > > initramfs-tools tries to add. > > I suspect this commit might be relevant: > > https://salsa.debian.org/kernel-team/initramfs-tools/-/commit/5d28dad0e24020d43daf51a5c1e70eb2fe5b4ee2 > > Both onboard_usb_hub and onboard_usb_dev are listed. From kernel git > history it seems to me that it is the same module, but it was renamed from > _hub to _dev (31e7f6c015d). Bookworm 6.1 kernel does include > onboard_usb_hub I believe, but I don't quite understand what it is exactly.
Well, the driver source is there, but we didn't enable it until later and then only on arm64. > When I have time, I might try to disable this part from hook-functions to > see if it helps. I would not be surprised if this is was hardware-relevant, > of course. > > > I suspect that probing of your USB keyboard is slightly unreliable and > > that it just happened to fail on the first boot after you upgraded. > > Please try again with the new initramfs-tools packages. Also, if the > > keyboard is not detected at first, try unplugging and re-plugging it. > > I did try rebooting many times with same results each time. Also tried > unpluggint and re-plugging and even switching to a different keyboard. I > have never seen this issue with 0.142. Well this is very weird. Another possibility is a USB hub getting into a broken state which isn't cleared by rebooting. But this doesn't seem very likely. Ben. -- Ben Hutchings For every complex problem there is a solution that is simple, neat, and wrong.
signature.asc
Description: This is a digitally signed message part
