Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64

2007-01-05 Thread Sid Boyce
Len Brown wrote: ..same problem with 2.6.20-rc3. Last worked with 2.6.19-rc6-git12, so it was 2.6.19 where it failed. Attaching both case1 normal, case2 acpi=noirq. With acpi=noirq ethernet doesn't get configured, route -n says it's an Unsupported operation, ifconfig only shows for l

Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64

2007-01-04 Thread Jarek Poplawski
On Wed, Jan 03, 2007 at 04:53:58PM +, Sid Boyce wrote: ... > It seems >=2.6.19 and the SuSEfirewall are incompatible. Actually, many programs could be incomapatible with newer kernel versions, so sometimes upgrades or at least recompilations are needed. ... > There is still the problem whe

Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64

2007-01-03 Thread Sid Boyce
Jarek Poplawski wrote: On Tue, Jan 02, 2007 at 03:32:01PM +, Sid Boyce wrote: Jarek Poplawski wrote: ... If you could send full ifconfig, route -n (or ip route if you use additional tables) and tcpdump (all packets) >from both boxes while pinging each other and a few words how it is conn

Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64

2007-01-03 Thread Jarek Poplawski
On Tue, Jan 02, 2007 at 03:32:01PM +, Sid Boyce wrote: > Jarek Poplawski wrote: ... > >If you could send full ifconfig, route -n (or ip route > >if you use additional tables) and tcpdump (all packets) > >from both boxes while pinging each other and a few words > >how it is connected (other card

Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64

2007-01-02 Thread Len Brown
> ..same problem with 2.6.20-rc3. Last worked with > 2.6.19-rc6-git12, so it was 2.6.19 where it failed. > Attaching both case1 normal, case2 acpi=noirq. With acpi=noirq ethernet > doesn't get configured, route -n says it's an Unsupported operation, > ifconfig only shows for localhost, ifconf

Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64

2007-01-02 Thread Sid Boyce
Apologies for the long spiel, if memory serves me correct, gzip'd attachments are verboten. openSUSE 10.2 Network does not get configured with "acpi=noirq" or "acpi=off". There may be something in dmesg that allows further analysis of the problem. 00:0a:e4:4e:a1:42 is the laptop MAC address. 00

Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64

2007-01-02 Thread Len Brown
On Tuesday 02 January 2007 10:41, Sid Boyce wrote: > Same problem with 2.6.19-rc3. Do you mean 2.6.20-rc3 still does not work? What was the last kernel that worked properly with no cmdline parameters? > Apologies for the long spiel, if memory serves me correct, gzip'd > attachments are verboten.

Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64

2007-01-02 Thread Sid Boyce
Same problem with 2.6.19-rc3. Apologies for the long spiel, if memory serves me correct, gzip'd attachments are verboten. openSUSE 10.2 Network does not get configured with "acpi=noirq" or "acpi=off". There may be something in dmesg that allows further analysis of the problem. 00:0a:e4:4e:a1:4

Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64

2007-01-02 Thread Sid Boyce
Jarek Poplawski wrote: On Sat, Dec 30, 2006 at 02:21:15AM +, Sid Boyce wrote: Jarek Poplawski wrote: On 28-12-2006 04:23, Sid Boyce wrote: I first saw the problem on the 64x2 box after upgrading to 2.6.19. The network appeared OK with ifconfig and route -n, but I had no network access. Pin

Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64

2007-01-02 Thread Sid Boyce
Jarek Poplawski wrote: On Sat, Dec 30, 2006 at 02:21:15AM +, Sid Boyce wrote: Jarek Poplawski wrote: On 28-12-2006 04:23, Sid Boyce wrote: I first saw the problem on the 64x2 box after upgrading to 2.6.19. The network appeared OK with ifconfig and route -n, but I had no network access. Pin

Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64

2007-01-02 Thread Sid Boyce
Jarek Poplawski wrote: On Sat, Dec 30, 2006 at 02:21:15AM +, Sid Boyce wrote: Jarek Poplawski wrote: On 28-12-2006 04:23, Sid Boyce wrote: I first saw the problem on the 64x2 box after upgrading to 2.6.19. The network appeared OK with ifconfig and route -n, but I had no network access. Pin

Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64

2007-01-02 Thread Jarek Poplawski
On Sat, Dec 30, 2006 at 02:21:15AM +, Sid Boyce wrote: > Jarek Poplawski wrote: > >On 28-12-2006 04:23, Sid Boyce wrote: > >> > >>I first saw the problem on the 64x2 box after upgrading to 2.6.19. The > >>network appeared OK with ifconfig and route -n, but I had no network > >>access. Pinging a

Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64

2006-12-28 Thread Jarek Poplawski
On 28-12-2006 04:23, Sid Boyce wrote: > > > I first saw the problem on the 64x2 box after upgrading to 2.6.19. The > network appeared OK with ifconfig and route -n, but I had no network > access. Pinging any other box, the box was responding, but no response ... > barrabas:/usr/src/linux-2.6.20-r

2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64

2006-12-28 Thread Sid Boyce
I first saw the problem on the 64x2 box after upgrading to 2.6.19. The network appeared OK with ifconfig and route -n, but I had no network access. Pinging any other box, the box was responding, but no response was received by the 64x2. I checked cables and the switch which were OK, so I figured