Re: Linux IDE bug in 2.4.21 and 2.4.22 ?
From: Phil Dibowitz
Date: Tue Sep 09 2003 - 09:33:59 EST
Bartlomiej Zolnierkiewicz wrote:
On Tuesday 09 of September 2003 00:51, Phil Dibowitz wrote:
Hey folks,
I think I may have found a bug in the Linux IDE subsystem
introduced in 2.4.21 and still present in 2.4.22.
Nope, user error :-).
I thought there was a reasonable chance of that! =)
Nope, your CMD649 was handled by generic PCI IDE driver.
Ah, OK. Makes sense.
As of 2.4.21, this configuration no longer works -- which is not
necessarily a bug. I'm almost there, stay with me. =)
Assumption that current .config will work with future kernel versions is *false*.
Agreed. I said that wasn't a bug. =)
Just add these two lines to your .config:
CONFIG_BLK_DEV_VIA82CXXX=y
CONFIG_BLK_DEV_CMD64X=y
Doh!! Didn't see the VIA driver down there at the bottom. Double doh! My
appologies, I should have been able to figure that out.
That works quite well, thank you! Still have a question though...
Your VIA IDE controller was handled by generic IDE chipset driver which
did probe devices *after* PCI controllers are probed, so CMD649 took
ide0 and ide1 first.
But, what about the case when I built in the generic driver, but made
the CMD649 driver a module, and loaded it after boot. That shouldn't
have *changed* what ide0 and ide1 are, right? I had ide0 and ide1
assigned, did a modprobe, and CMD649 changed what ide0 adn ide1 where,
and then forgot about the previous ones.. like all of a sudden it told
the generic driver "no, no, you were wrong, there's no VIA chipset here,
go back to sleep."
I may well be misunderstanding something precedence in the kernel here,
but I figured while I'm bugging you, I might as well get the full picture.
Thanks for your time!
--
Phil Dibowitz phil@xxxxxxxx
Freeware and Technical Pages Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
- Benjamin Franklin, 1759
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/