Bug#250677: more info needed
On Fri, Jun 11, 2004 at 04:52:57PM -0400, Joey Hess wrote:
> Finn-Arne Johansen wrote:
> > On Fri, Jun 11, 2004 at 03:03:10PM -0400, Joey Hess wrote:
> > > Apparently one of the ide chipset modules makes your CD not work. The
> > > thing to do, then, would be to boot the installer in expert mode, and
> > > tell it not to load some of the ide chipset modules. Repeat until you've
> > > narrowed it down to one problimatic module.
> > Well, loading ide-detect first solves the problem. but then it fails
> > with all the other ide-modules. I tried with another machine, that
> > works withuopt problem. I loaded ide-detect first, and then only the
> > driver that fitted the chipset was loaded. Is it possible to change so
> > that ide-detect is loaded first, and then load the ide-chipset drivers
> > afterwards ? but then it should fail silently when loading the
> > ide-modules fails.
> The ide chipset modules have to be loaded before ide-detect to take
> effect, I belive. And they're needed on some machines to access the
> drive without it hanging. Loading it first works around your problem,
> but it not a solution. Like I said, you need to do a binary search and
> work out which ide chipset module is at fault; which I guess will take a
> fair bit of rebooting.
I found the bastard :)
It's the triflex driver. loading everything else except the triflex
solves the problem.
My next question is, would it be possible to do a lspci , and by
default only load the drivers that are found (like it does on scsi),
and then if things still fails, load the others. leaving out triflex
from beeing autoloaded will sure hurt some people.
--
Finn-Arne Johansen
faj@bzz.no
http://bzz.no/
Reply to: