mkinitrd_command_generator and ehci_hcd
In Slackware64-14.1, the huge kernel has both echi_hcd and ehci_pci configured as modules. After booting with the huge kernel, lsmod suggests ehci_hcd is used by ehci_pci, and lspci -k shows the USB controller using ehci_pci, not ehci_hcd.
Code:
# grep -i ehci /boot/config-huge-3.10.17 Code:
mkinitrd -c -k 3.10.17 -f ext4 -r /dev/sda1 -m usbhid:hid_generic:uhci-hcd:mbcache:jbd2:ext4 -u -o /boot/initrd.gz After booting with this initrd, without the ehci_hcd, and the generic kernel, the kernel issues a warning in dmesg: Code:
<4>[ 5.640786] Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after It seems kernel 3.10.17 handles ehci differently from previous Slackware kernels and hopefully a next version of the mkinitrd_command_generator.sh will address this. This is not intended as criticism, I am indebted to alienBOB for his on-going contribution to Slackware. :hattip: Two similar threads I could locate, here, and here. |
I don't remember if I used the script mkinitrd_command_generator.sh at that time but I had a similar issue, closed in including the module ehci-pci in the initrd.
|
I used the mkinitrd_command_generator script on my Slackware64, and don't get that warning in dmesg.
Code:
root@slackdesk:~# dmesg | grep ehci_hcd |
@didier Thanks, I didn't come across your thread when I looked.
@brianL If a usb disk, or stick, is plugged-in while running mkinitrd_command_generator.sh, the usb storage modules are included and with them usb_hcd, resulting in no dmesg warning. Perhaps other similar cases also exist. |
All times are GMT -5. The time now is 05:39 PM. |