Classmate PC fails to connect a wired LAN.

[xiayi]

1. Press "Fn" key and hit "F7" key to disable wireless.
2. Select on the start bar: System->Administration->Network and click unlock and enter user password.Double click wired connection and make sure roaming mode is checked and plug in a network cable connected to an AP.
3. Select on the start bar: System->Administration->Network and click unlock and enter user password.Double click wired connection and check "Enable roaming mode" off.Select DHCP in the Connection settings configuration and click "OK".
4. Select on the start bar: System->Administration->Network and click unlock and enter user password.Double click wired connection and check "Enable roaming mode" off.Select "static IP address" and input an valid IP in the same network segment of the AP and C class mask and click OK.

I cannot get wired link work in the above way(step 2,3,4).

[Oliver Grawert (ogra)]

network manager maintainer subscribed to the bug

[Alexander Sack (asac)]

Could you please try to rephrase your test case? In particular its unclear how you can |check "Enable roaming mode" off| in step 2 and then |check "Enable roaming mode" off| in step 3 again.

What is the primary use-case you are trying to deal with here? setting up a static IP configuration?

Does the behaviour change if you dont do step 1?

Please also attach the complete /var/log/syslog /var/log/daemon.log and /var/log/messages taken _after_ reproducing this bug.

Thanks!

[xiayi (yi-xia)]

Hi,
 Pls click the "System" item on the top tool bar and move mouse to "Administration" in popped menu and select "Network" and then you can see the network configuration panel as attached "screenshot.png". Above steps are described as "System->Administration->network" in launchpad.

 The primary use-case is that when wireless is not available, user could connect in wired way. But now I can accomplish this neither in roaming mode nor by DHCP nor by static IP.

 The log files are attached and I'll also upload them on launchpad.

Best Regards
Yi Xia

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Alexander Sack
Sent: 2008年7月11日 18:50
To: Xia, Yi
Subject: [Bug 247478] Re: Classmate PC fails to connect a wired LAN.

Could you please try to rephrase your test case? In particular its
unclear how you can |check "Enable roaming mode" off| in step 2 and then
|check "Enable roaming mode" off| in step 3 again.

What is the primary use-case you are trying to deal with here? setting
up a static IP configuration?

Does the behaviour change if you dont do step 1?

Please also attach the complete /var/log/syslog /var/log/daemon.log and
/var/log/messages taken _after_ reproducing this bug.

Thanks!

** Changed in: cmpc
       Status: New => Incomplete

--
Classmate PC fails to connect a wired LAN.
https://bugs.launchpad.net/bugs/247478
You received this bug notification because you are a direct subscriber
of the bug.

Status in Application and image devlopment around the Classmate PC: Incomplete

Bug description:
1. Keep roaming mode enabled and plug in a network cable connected to an AP.
2. Select on the start bar: System->Administration->Network and click.Click unlock and enter user password.Double click wired connection and check "Enable roaming mode" off.Select DHCP in the Connection settings configuration and click "OK".
3. Select on the start bar: System->Administration->Network and click.Click unlock and enter user password.Double click wired connection and check "Enable roaming mode" off.Select "static IP address" and input an valid IP in the same network segment of the AP and C class mask and click OK.

I cannot get wired link work in the above way.

[Oliver Grawert (ogra)]

for dhcp you should not do anything but plug in a network cable, if you want to forcefully make the network card getting a new dhcp ip address, right click the NM applet, uncheck "enable networking", check it again and it will scan for an IP.

the manual configuration part should only be used if you actually do manual configuration of a static IP ...

roaming isnt involved in wired networking at all ...

even though teh bove mentiond actions are a bit confusing, i can confirm that dhcp doesnt get picked up as it should if i follow the documented standard way.

[Oliver Grawert (ogra)]

confirming, even though reproduction was done as the documentation suggests instead of the way the initial reporter tried.

[Oliver Grawert (ogra)]

digging deeper it might be related to ubuntu bug #240648, i will try out the fixes applied there tomorrow and report back.

[xiayi (yi-xia)]

 I did assume the wired network should be available on plugging in a network cable but it failed.
 I meant to find a workaround to get the wired link work so I did the manual configuration. If a workaround is found, we may lower the severity.

Best Regards
Yi Xia

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Oliver Grawert
Sent: 2008年7月18日 1:23
To: Xia, Yi
Subject: [Bug 247478] Re: Classmate PC fails to connect a wired LAN.

for dhcp you should not do anything but plug in a network cable, if you
want to forcefully make the network card getting a new dhcp ip address,
right click the NM applet, uncheck "enable networking", check it again
and it will scan for an IP.

the manual configuration part should only be used if you actually do
manual configuration of a static IP ...

roaming isnt involved in wired networking at all ...

even though teh bove mentiond actions are a bit confusing, i can confirm
that dhcp doesnt get picked up as it should if i follow the documented
standard way.

--
Classmate PC fails to connect a wired LAN.
https://bugs.launchpad.net/bugs/247478
You received this bug notification because you are a direct subscriber
of the bug.

Status in Application and image devlopment around the Classmate PC: Confirmed
Status in “gnome-system-tools” source package in Ubuntu: New
Status in “network-manager” source package in Ubuntu: New

Bug description:
1. Press "Fn" key and hit "F7" key to disable wireless.
2. Select on the start bar: System->Administration->Network and click unlock and enter user password.Double click wired connection and make sure roaming mode is checked and plug in a network cable connected to an AP.
3. Select on the start bar: System->Administration->Network and click unlock and enter user password.Double click wired connection and check "Enable roaming mode" off.Select DHCP in the Connection settings configuration and click "OK".
4. Select on the start bar: System->Administration->Network and click unlock and enter user password.Double click wired connection and check "Enable roaming mode" off.Select "static IP address" and input an valid IP in the same network segment of the AP and C class mask and click OK.

I cannot get wired link work in the above way(step 2,3,4).

[Oliver Grawert (ogra)]

After several days of testing and building various different images and kernels i can clearly say that this bug is obviously not showing up with the 8.10 kernel nor with the lpia flavour of 8.04 on the atom equipped classmate (which has identical hardware in all other aspects apart from the CPU). It is definately an issue with either the driver or the networking stack in the current 8.04 kernel.

I backported the r8169 changes from the 2.6.26 kernel used in 8.10 with no results (while using the complete kernel makes it work) and did as well an image and kernel build with the proposed patch from the linux-netdev list as shown on (http://marc.info/?l=linux-netdev&m=121498012600793&w=2) without any results.
I suspect the issue lies either in the af_packet code or even somewhere in the PCI stack itself, sice the changes to the driver in 2.6.26 are minor.
I'm subscribing Tim Gardner who is the kernel team networking specialist in the hope that he can shed some more light on this issue.

Attached are the ethtool and dmesg output for a removal/insertion of the module with plugged in cable.
If the cable is plugged in at boot ethtool actually reports a Link but doesnt reply to any DHCPOFFER messages from the DHCP server (it sends DHCPREQUEST messages that can be seen in the server logs though).
Setting up static IP data and routing does not make any difference either.

Sadly the NIC LEDs that show the physical link status at the plug were removed in the 1.5 hardware version, so there is no way to actually say if there is a physical link in place on the interface.

[Oliver Grawert (ogra)]

ogra@classmate:~$ sudo modprobe -r r8169
ogra@classmate:~$ sudo modprobe r8169
ogra@classmate:~$ sudo ethtool eth0
Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Advertised auto-negotiation: Yes
        Speed: Unknown! (0)
        Duplex: Half
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000033 (51)
        Link detected: no

dmesg during removal/addition of the module:
[ 5545.844003] ACPI: PCI interrupt for device 0000:01:00.0 disabled
[ 5549.014105] r8169 Gigabit Ethernet driver 2.2LK loaded
[ 5549.014886] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
[ 5549.014936] PCI: Setting latency timer of device 0000:01:00.0 to 64
[ 5549.018957] eth0: RTL8101e at 0xe04fa000, 00:03:0d:89:1f:1d, XID 34200000 IRQ 222
[ 5549.098476] r8169: eth0: link down
[ 5549.098915] ADDRCONF(NETDEV_UP): eth0: link is not ready

[Richard Weideman (richard-weideman)]

Oliver has discussed with Tim in the kernel team.
The issue is understood, and a solution has been identified.
An image with this bug resolved is anticipated on or before Friday 1 August.

[Oliver Grawert (ogra)]

please note that there is shipment of hardware involved, before tim can start to work on the issue.

[Stefan Bader (smb)]

The newer driver tries to enable MSI (according to the high interrupt number printed). Would it work with "pci=nomsi" as a boot parameter?

[Oliver Grawert (ogra)]

unfortunately i have to hop on a plane now, to get back to germany, i will test asap if i'm near a wired network again if that change helps (within 24-36h i should have an answer)

[Oliver Grawert (ogra)]

i tried the r8101-1.008.05-1 driver tim sent me without much success ...
it loads fine and reports the proper link state when loaded ...
it does not recognize any link changes with ethtool or in dmesg.

if i plug/unplug the cable and disable/enable networking in network manager the initial link state if NM comes up again is reported correctly by ethtool, but state changes (unplugging or re-plugging) are not detected ...

if i try to get a dhcp address with link up state DHCPDISCOVER messages are broadcasted and i see the following in my dhcpd logs repeatedly untl NM gives up and falls back to avahi:

Jul 30 12:50:43 ceron dhcpd: DHCPDISCOVER from 00:03:0d:89:1f:1d (classmate) via eth0
Jul 30 12:50:43 ceron dhcpd: DHCPOFFER on 192.168.2.85 to 00:03:0d:89:1f:1d (classmate) via eth0

[Oliver Grawert (ogra)]

ok, next time i'll try stefans suggestion first before compiling 3rd party drivers ... pci=nomsi makes it work properly (with both drivers btw) !!!

stefan: are there any known issues i could run into with the rest of the hardware if that parameter goes into my menu.lst as default in the image build ? (i will test everything over indeed, but if there is anything already known it would be good to know in advance)

[Stefan Bader (smb)]

Since there seem to be various MSI related problems it would be interesting to gather the following information:

- lspci -t
- sudo lspci -vvnn

[Tim Gardner (timg-tpi)]

@Oliver - setting nomsi will only have a performance impact. However, on a machine like the CMPC with few devices active you'll likely not be able to detect much difference.

[Oliver Grawert (ogra)]

fix is in hardy-classmate-20080730.img, please test

[Oliver Grawert (ogra)]

setting invalid for g-s-t as it was a driver issue

[Oliver Grawert (ogra)]

setting invalid for network-manager, driver issue