[svlug] the continuing saga of the supercheap eMachines box;-)

[Rick Moen]

Quoting Tim Utschig (tim at tetro.net):

> I remember one instance of a laptop hanging on boot while loading the
> [ou]hci_hcd and ehci_hcd modules in a certain order which happened to be
> the default on Fedora Core 4.  Reversing the order would allow the
> machine to boot successfully.
> 
> I'm not aware of any way to change the order in which modules are loaded
> by 'discover' (which does the "Detecting hardware..."), but you could
> try putting:
> 
>   skip uhci_hcd
>   skip ohci_hcd
>   skip ehci_hcd
> 
> in /etc/discover.conf-2.6, and adding the two modules which are right
> for your hardware to /etc/modules in a certain order, e.g:
> 
>   ehci_hcd
>   ohci_hcd
> 
> or: 
> 
>   ohci_hcd
>   ehci_hcd
> 
> (I don't recall which order worked).

Ja.  Hardware-autorecognition software such as discover/libdiscover,
kudzu, etc. is a mixed blessing at best.  One alternate approach,
therefore, would be to just statically add the correct driver lines for
your hardware -- in the desired order -- into /etc/module and disable
the discover script.  You would implicitly, of course, be assuming
responsibility for managing which driver modules do and do not load,
thereafter.

-- 
Cheers,
Rick Moen                                                    Habetis bona deum. 
rick at linuxmafia.com