Finn-Arne Johansen wrote: > 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.
I don't know if lspci has enough info to tell what ide chipset drivers are needed, or not. The failure modes if they're loaded are generally things like disk read/write errors or hangs though, and the inability to load more of them after the ide-probe module is loaded makes it harder too. Especially because you seem to have a triflex controller.. Of course maybe the triflex driver is not needed to avoid problems like thse I described, and only turns on DMA or something else, and does a bad job of it. If so we could just skip it. One other problem is that AFAIK the standard debian initrd (in sarge, maybe you're doing skolelinux/woody stuff though) loads all of these drivers unconditionally, just like d-i does, so even if it's fixed in d-i the installed system may be unable to boot. -- see shy jo
signature.asc
Description: Digital signature
