I have a brand new Western Digital sata drive, VIA KT600 based ECS
motherboard on which I am trying to install various distros (with installers
based on 2.4.26, 2.6.7, 2.6.8, 2.6.11 etc) all of them fail to detect the HD
(and bomb out) because sata-via is ignoring it . I have only one
I have a brand new Western Digital sata drive, VIA KT600 based ECS
motherboard on which I am trying to install various distros (with installers
based on 2.4.26, 2.6.7, 2.6.8, 2.6.11 etc) all of them fail to detect the HD
(and bomb out) because sata-via is ignoring it . I have only one
I have a KT600 based motherboard & I am planning to set up my new system using
that. It has onboard via 8237 sata {raid, cough cough} controller. I am
planning to use a single sata disk (I am not interested in raid). The
various distro installers are having tough time noticing a brand new
I have a KT600 based motherboard I am planning to set up my new system using
that. It has onboard via 8237 sata {raid, cough cough} controller. I am
planning to use a single sata disk (I am not interested in raid). The
various distro installers are having tough time noticing a brand new
I have been getting this error off and on with vendor kernel 2.6.8, I have
posted about it on lkml 3/4 times before. Actually I had offered to provide a
summary of similar reports from the web with no takers, I can still provide
that to somebody if it is useful.
I had run memtest overnight
I have been getting this error off and on with vendor kernel 2.6.8, I have
posted about it on lkml 3/4 times before. Actually I had offered to provide a
summary of similar reports from the web with no takers, I can still provide
that to somebody if it is useful.
I had run memtest overnight
This might or might not be useful to anybody but I googled with the above
error and tried to track down how many of these errors had actually been
resolved. [It is possible that people don't come back to summarize once the
problem is resolved]. I only tracked once that did not get reported on
This might or might not be useful to anybody but I googled with the above
error and tried to track down how many of these errors had actually been
resolved. [It is possible that people don't come back to summarize once the
problem is resolved]. I only tracked once that did not get reported on
>Thanks for giving that a thorough run, memory seems exonerated... yet I
>don't trust this machine at all: have you tried manufacturer diagnostics?
Ouch, that hurts. This is a machine I built myself over three years ago. Ran
very stably with 2.4.*. may be it is the age of the machine. The
Thanks for giving that a thorough run, memory seems exonerated... yet I
don't trust this machine at all: have you tried manufacturer diagnostics?
Ouch, that hurts. This is a machine I built myself over three years ago. Ran
very stably with 2.4.*. may be it is the age of the machine. The
I am not sure this is a fixed problem in 2.6.11-rc2 based on my read of the
changelog, hence this email. Here is the summary:
1. I started with vanilla 2.6.10 where I replaced ieee1394 drivers from trunk
rev 1251 patched in. My kernel is tainted due to ndiswrapper that loads
windows drivers
I am not sure this is a fixed problem in 2.6.11-rc2 based on my read of the
changelog, hence this email. Here is the summary:
1. I started with vanilla 2.6.10 where I replaced ieee1394 drivers from trunk
rev 1251 patched in. My kernel is tainted due to ndiswrapper that loads
windows drivers
12 matches
Mail list logo
