Red Hat Bugzilla – Bug 323861
Wrong device driver recognizing
Last modified: 2014-03-16 23:08:54 EDT
Description of problem: Kudzu make wrong information about device driver. The filed of kudzu_device.driver from compatible driver, but not from real loaded driver. Probably kudzu dont collect blacklisted modules information. How reproducible: Easy almost every time depend on order modules in modules.dep file. Steps to Reproduce: 1. install TWDrv (proprietary touch screen driver 3m.com) 2. put 'blacklist usbtouchscreen' in /etc/modules.d/blacklist 3. depmod -a 4. run print kudzu.probe(kudzu.CLASS_UNSPEC, kudzu.BUS_UNSPEC, kudzu.PROBE_SAFE) Actual results: kudzu_device.driver = usbtouchscnreen Expected results: kudzu_device.driver = TWDrv Additional info: You can run easy test. Remove usbtouchscreen from /lib/modules-x.x.x and run depmod -a. After it you got right kudzu_device.driver value.
kudzu is only used in anaconda, where there is no blacklist.
True, this is main target. But kudzu used for check local hardware changes evey reboot kudzu service S05kudzu. Additional, probaby right for anaconda, initial modproble.d/blacklist is not empty, you can check your /etc/modules.d/blacklist, this file full of blacklisted modules.
Yes, but none of those are relevant for the installer. As for the 'check hardware' that only runs in F7 for sound, network, and video cards, and will run for even less in the future.