Juan Quintela kirjoitti viestiss��n (l�hetysaika Torstai 28. Elokuuta 2003 12:40): > >>>>> "john" == John Allen <[EMAIL PROTECTED]> writes: > > Hi > > john> This probably explains what the problem is then; I'm getting UDMA100 > with the john> 2.4.22-0.8, and this is probably the source of the problem. > > Please, check that you have a real 80 pins cable. It appears that for > some reason, the cable is misdetected. >
It's not misdectected... It's not detected at all... The driver uses a simple logic for theese chipsets..., if it finds a harddisk that supports >= udma66 it will automatically assume that the system owner is smart enough to have used a real 80 pin cable... Theese asumptions in the driver are added because of the lack of public documentation over the ide chipsets / registers..., and in some cases poorly implemented m/b design... > john> I've also put the 2.4.22 kernel on my other machine (NF7-S V1.2, > which is john> normally very stable), and X crashed after 3 hours, with > console video john> knackered. > > not here, could you try a serial console to see the hang? > > Later, Juan. There has been some recent discussion on the fact that some of the chipset revisions has had more problem than other, and considering the fact that nVidia themseleves have problems with their WindowsXP/2000 IDE-drivers stability (or the fact that there is no IDE SW driver at all in latest nForce chipset drivers), it may still take some time before the problem is fixed.... And there is not many people that actually have access to the nVidia NDA documentations (I know of only 2) ... Thomas
