Re: 2.6.18-4-686 broke 8139too

2007-05-13 Thread Adrian Levi
On 5/14/07, Florian Kulzer <[EMAIL PROTECTED]> wrote: With 2.6.8 you have: > ACPI disabled because your bios is from 95 and too old > You can enable it with acpi=force > IRQ9: eth0 With 2.6.18, on the other hand: > ACPI: Core revision 20060707 > ACPI: setting ELCR to 0800 (from 0200) > ACP

Re: 2.6.18-4-686 broke 8139too

2007-05-13 Thread Florian Kulzer
On Sun, May 13, 2007 at 16:17:55 +1000, Adrian Levi wrote: > After an upgrade from Sarge networking no linger works. I can see no > reason for it. > > I have attached lspci -vvv, dmesg, and ifconfig eth0 and > /proc/interrupts for both kernels 2.6.8-2-686 works perfectly. > > Error message is: > Ma

Re: 2.6.18-4-686 broke 8139too

2007-05-13 Thread Nigel Henry
On Sunday 13 May 2007 08:17, Adrian Levi wrote: > After an upgrade from Sarge networking no linger works. I can see no > reason for it. > > I have attached lspci -vvv, dmesg, and ifconfig eth0 and > /proc/interrupts for both kernels 2.6.8-2-686 works perfectly. > > Error message is: > May 13 13:12:

Re: 2.6.18-4-686 broke 8139too

2007-05-13 Thread Ralph Katz
On 05/13/2007 02:17 AM, Adrian Levi wrote: > After an upgrade from Sarge networking no linger works. I can see no > reason for it. > > I have attached lspci -vvv, dmesg, and ifconfig eth0 and > /proc/interrupts for both kernels 2.6.8-2-686 works perfectly. > > Error message is: > May 13 13:12:39