PCI chipset -- module vs. compiled-in

[Tim Writer]

Ivan Avery Frey <ivan.frey-H217xnMUJC0sA/PxXw9srA at public.gmane.org> writes:

> Tim Writer wrote:
> > lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org (Lennart Sorensen) writes:
> >
> 
> >> On Sun, Feb 05, 2006 at 10:26:51PM -0500, William Park wrote:
> >>> Normally, my PCI chipset is compiled in.  But, for experiment, I
> >>> tried compiling in only the "generic" options, and moved all specific
> >>> PCI chipsets (ie. via82cxxx, hpt366) as modules.
> >> You do NOT want generic compiled in.  That is the last one you would
> >> want compiled in.  It is a generic ide driver that runs most pci ide
> >> controllers, but being generic does not do dma or anything else.  Since
> >> it would now get first shot at controlling all your ide ports, the
> >> native drivers you try and load later as modules of course can't load
> >> because generic already took control of the ports.  Make them all
> >> generic, and load the correct ones for your chipset in the initrd.
> >> generic can be loaded last as a last resort for accessing the ide ports.
> > And load the chipset module before any IDE modules. A default Ubuntu (5.04
> 
> > Hoary Hedgehog) install gets this wrong, for example. It properly identifies
> > the chipset but loads it after ide_cd. As a result, you can't set DMA on the
> > CD.
> >
> 
> Does Ubuntu 5.10 do the same thing?

I don't know but it's easy enough to discover and fix if you're aware of the
problem.

-- 
tim writer <tim-s/rLXaiAEBtBDgjK7y7TUQ at public.gmane.org>                                  starnix inc.
647.722.5301                                      toronto, ontario, canada
http://www.starnix.com              professional linux services & products
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml