In message <[EMAIL PROTECTED]>
Rod Stewart <[EMAIL PROTECTED]> wrote:
> On Thu, 15 Feb 2001, Peter Naulls wrote:
>
> > I've built a 2.4.1 kernel which is ok - until eth0 is brought up. I'm
> > then presented with the same message over and over with increasing
> > numbers:
> >
> > eth0: (N) System Error Occurred
>
> You've not said which device eth0 is, but from the error message I would
> say the tulip. The short answer is: There is a problem with the tulip
> driver in 2.4 with certain revisions of the chip. Ralph said he has used
> the old_tulip.c from 2.2 without any problems on 2.4. You might be able
Yeah, it is. I had originally though it was both interfaces, but on
second thoughts it's not. I'll try the other driver.
> to boot with:
> boot cmd=init=/bin/sh
> and might get away with things as long as you do not use eth0.
I can boot ok having first disabled the interface setup from 2.2.13.
Now that do I do have kernel running, I can see this message:
IRQ: spurious interrupt 108
Appearing as the last thing in dmesg after swap is activated. Perhaps
this is related?
Peter
--
------------------------------------------------------------------------
Peter Naulls - [EMAIL PROTECTED]
Homepage - http://free.prohosting.com/~chocky/
Java for RISC OS and ARM - http://www.java.riscos.org.uk/
Debian Linux on RiscPCs - http://www.erble.freeserve.co.uk/
------------------------------------------------------------------------
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
