Some updates: recompiled the kernels without the VIA driver (actually,
compiled as a module but not loaded).
With 2.4.27, I don't have the CRC errors anymore, though I can't get
DMA to work (is because I load the generic PCI driver afterwards?).
With 2.6.18, I get this:
VFS: Cannot open root dev
On 8/4/07, Wayne Topa <[EMAIL PROTECTED]> wrote:
>
> I also have the ABIT KT7 and it has gone from kernels 2.4.27 ->
> 2.6.18-4 with no CRC errors showing up at all. It's only been running
> for 5-6 years. CPU Fan has been changed twice but other then that,
> its fine.
I have mine since december
Francois Duranleau([EMAIL PROTECTED]) is reported to have said:
> On 8/4/07, Francois Duranleau <[EMAIL PROTECTED]> wrote:
> > On 8/3/07, Brad Sawatzky <[EMAIL PROTECTED]> wrote:
> > > Hi Francois,
> > >
> > > I agree with Doug: CRC errors shouldn't be ignored. At _best_ they are a
> > > sign tha
Francois Duranleau wrote:
>> I tried to change the IDE cables (I had a few spares from my father's
>> computer).
>> I happened to notice that I had a 40 pins cable. I replaced it with a 80 pins
>> cable. I have two, I tried both: nothing changed. I still have CRC errors.
>> BTW,
>> there is only
On 8/4/07, Francois Duranleau <[EMAIL PROTECTED]> wrote:
> On 8/3/07, Brad Sawatzky <[EMAIL PROTECTED]> wrote:
> > Hi Francois,
> >
> > I agree with Doug: CRC errors shouldn't be ignored. At _best_ they are a
> > sign that something in your system is marginal. At worst you end up
> > reading and
On Sat, Aug 04, 2007 at 12:35:54AM -0400, Francois Duranleau wrote:
> I tried to change the IDE cables (I had a few spares from my father's
> computer).
> I happened to notice that I had a 40 pins cable. I replaced it with a 80 pins
> cable. I have two, I tried both: nothing changed. I still hav
On 8/3/07, Brad Sawatzky <[EMAIL PROTECTED]> wrote:
> Hi Francois,
>
> I agree with Doug: CRC errors shouldn't be ignored. At _best_ they are a
> sign that something in your system is marginal. At worst you end up
> reading and/or writing bogus data. The fact that the errors persisted
> after y
Francois Duranleau wrote:
On 8/3/07, Brad Sawatzky <[EMAIL PROTECTED]> wrote:
Perhaps I misunderstood, but I thought he got the errors with the old
kernel (and had for a long time) but they did not trigger a filesystem
check. My hunch was that the 2.6.x IDE driver (or ext3 driver) is handling
t
Hi Francois,
On Fri, 03 Aug 2007, Francois Duranleau wrote:
> On 2.4.27, I get the CRC errors (not at boot time, later, and all the
> time thereafter), and I've been having them for many years. I mentionned
> just in case there might be a link with my problem. Otherwise, I am not
> trying to solv
On Fri, Aug 03, 2007 at 03:26:11PM -0400, Francois Duranleau wrote:
> On 2.4.27, I get the CRC errors (not at boot time, later, and all the
> time thereafter), and I've been having them for many years. I
> mentionned just in case there might be a link with my problem.
> Otherwise, I am not trying
On 8/3/07, Brad Sawatzky <[EMAIL PROTECTED]> wrote:
>
> Perhaps I misunderstood, but I thought he got the errors with the old
> kernel (and had for a long time) but they did not trigger a filesystem
> check. My hunch was that the 2.6.x IDE driver (or ext3 driver) is handling
> the error condition
Hi Douglas,
On Fri, 03 Aug 2007, Douglas Allan Tutty wrote:
> On Fri, Aug 03, 2007 at 02:28:58PM -0400, Brad Sawatzky wrote:
> > On Fri, 03 Aug 2007, Francois Duranleau wrote:
> > [ . . . ]
> > > Now, when I boot my computer using the new kernel, I get an error
> > > message during filesystem che
On Fri, Aug 03, 2007 at 02:28:58PM -0400, Brad Sawatzky wrote:
> On Fri, 03 Aug 2007, Francois Duranleau wrote:
>
> [ . . . ]
> > Now, when I boot my computer using the new kernel, I get an error
> > message during filesystem check saying it contains errors (sorry, I
> > don't have a more precise
On Fri, 03 Aug 2007, Francois Duranleau wrote:
[ . . . ]
> Now, when I boot my computer using the new kernel, I get an error
> message during filesystem check saying it contains errors (sorry, I
> don't have a more precise error message, and I have no logs) and
> it then mounts the filesystem read
Hi!
I have a somewhat strange problem at home. Lately, I decided to
finally update my kernel from 2.4.27 to 2.6.18 (actually now it
would be 2.6.21, but when I tried it was 2.6.18). I installed the
source package, compiled the kernel as I used to with the previous
one (didn't change much the confi
15 matches
Mail list logo
