That log isn't udev _saying_ it's going to load the module, it's the kernel informing udev that the module has been loaded into the system.
I'm not trying to be awkward or shirk a bug here, if you really have a bug, I will take the time to diagnose it for you. However I'm saying that all of the evidence you have supplied indicates the system is working perfectly and you haven't provided a single piece of evidence that it isn't. The next course of action is logical: - remove any changes you have made from the system (e.g. to /etc/modules) to try and force the loading of these modules - boot the system - attach /var/log/udev from that boot - attach "lsmod" from after booting - attach output of "uname -a" - attach your /lib/modules/`uname -r`/modules.alias file If you could also run the following commands and attach output from those: modprobe --first-time -v -n pci:v000010ECd00008139sv000010ECsd00008139bc02sc00i00 modprobe --first-time -v -n pci:v00008086d000024D5sv00008086sd0000E002bc04sc01i00 modprobe --first-time -v -n pci:v00008086d000024DDsv00008086sd00004C43bc0Csc03i20 -- Some modules are not automatically loaded after dist-upgrade from 5.10 to 6.06 beta https://launchpad.net/bugs/41144 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
