ECS k7s5a motherboard doesnt work
First of all, I'm not subscribed to the list, could any comments please be cc'd to [email protected]
Secondly, I thank you all very much for taking the time to help.
Here's the problem. I just bought a 1.4 GHz AMD athlon and an ECS k7s5a motherboard. I tried to install linux using this motherboard several dozen times, using several different distros (mandrake, redhat, and debian). Not once did it install completely. The problems ranged from the partition table being scrambled when it attempted to make the partitions, to failure to access harddisk, to failure to access the cdrom. Cdrom failures were actually the most common reason for the failed install. I tried the different distros, as well as an old version of mandrake which i know the install cd works (i used it on another computer).
Before the harddisk scrambling occurred the once or twice, I thought maybe my cdrom was no longer functioning (even though the same cdrom drive worked fine with linux with a different motherboard). So I tried using a cdr drive, a dvd drive, and a regular 48x cdrom drive, and all of the distros had issues.
For this reason, i'm leaning towards believing that the ECS k7s5a's built-in ultradma controller is incompatable with linux.
Has anyone else experienced this, is this a known issue, and is any work being done to fix it? or does anyone have any suggestions?
Thank you all very much for your time,
Justin
Quoted 2 lines
Has anyone else experienced this, is this a known issue, and is any work being done to fix it? or does anyone have any suggestions?
The sort of things you describe sound like straight forward broken hardware not even incompatibilities - bad ram , bad board, bad CPU could all do this
here's some more info for everyone trying to help:
redhat says (at some point) that it insmod'd sis900, not the sis5513 that mark had suggested, and the sis735 that everything says is actually in the motherboard. (i have to assume the sis900 was ide, because it didnt tell me anything more useful than "insmod sis900" and that it worked)
however, the messages i'm seeing are something like this:
hda atapi: reset complete
irq timeout: complete status = 0xC0 { busy } (sometimes thats 0xD0)
then there's a few lines every now and then saying "drive not ready for command" and "I/O error"
any suggestions?
justin
sis900 is the integrated ethernet controller...
joelja
Quoted 24 lines · Justin Mierta
here's some more info for everyone trying to help:
redhat says (at some point) that it insmod'd sis900, not the sis5513 that mark had suggested, and the sis735 that everything says is actually in the motherboard. (i have to assume the sis900 was ide, because it didnt tell me anything more useful than "insmod sis900" and that it worked)however, the messages i'm seeing are something like this:
hda atapi: reset complete
irq timeout: complete status =0xC0{ busy } (sometimes thats0xD0)then there's a few lines every now and then saying "drive not ready for command" and "I/O error"
any suggestions?
justin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Signature · 8 lines
-------------------------------------------------------------------------- Joel Jaeggli [email protected] Academic User Services [email protected] PGP Key Fingerprint: 1DE9 8FCA 51FB 4195 B42A 9C32 A30D 121E -------------------------------------------------------------------------- It is clear that the arm of criticism cannot replace the criticism of arms. Karl Marx -- Introduction to the critique of Hegel's Philosophy of the right, 1843.