Problem with network connect

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
Post Reply
sci_fi
Black ninja
Black ninja
Posts: 52
Joined: 28 Dec 2010, 18:25

Problem with network connect

Post#1 by sci_fi » 28 Feb 2011, 18:51

Hi,

I am having problems with my network card (wired, not wireless). Porteus detects the card and appears to select the correct driver. The connection is made but resets after a few seconds. This repeats indefinitely.
The card is Intel 82567LM (rev 3) with the Intel Pro/1000 driver.
The Below is psinfo.txt for this notebook. Not sure what other information to provide.

This card works fine on another distro (Tiny Core linux 3.5) so perhaps the problem is with the kernel support for the card.

Suggestions appreciated.

Thanks and best regards,

sci_fi

Output from psinfo
----------------------
script by jayflood
.
.

====== USER INFO =====
User is: root
.
===== MACHINE INFO =====
Platform: i686
Kernel: 2.6.37-porteus
Processor: Intel(R) Core(TM)2 Duo CPU U9300 @ 1.20GHz
MemTotal: 1939124 kB
MemFree: 1355396 kB
Bootparam: root=/dev/ram0 ramdisk_size=6666 rw root=/dev/ram0 rw max_loop=255 autoexec=xconf;lxde;telinit~4
.
===== SOUND INFO =====
Sound card: 0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xf6a20000 irq 45
Sound driver: Advanced Linux Sound Architecture Driver Version 1.0.23.
.
===== PARTITION INFO =====
Porteus is on: /mnt/sda7
.
Partitions:
sda
sda1
sda2
sda3
sda5
sda6
sda7
sda8
sda9
sda10
sda11
.
Mounted:
/dev/sda1 fuseblk 35G 12G 23G 35% /mnt/sda1
/dev/sda2 vfat 204M 20M 185M 10% /mnt/sda2
/dev/sda5 vfat 20G 440M 20G 3% /mnt/sda5
/dev/sda7 ext3 9.5G 631M 8.4G 7% /mnt/sda7
/dev/sda8 ext3 9.5G 431M 8.6G 5% /mnt/sda8
/dev/sda9 ext3 9.8G 2.0G 7.4G 21% /mnt/sda9
/dev/sda10 ext3 60G 331M 57G 1% /mnt/sda10
/dev/sda11 ext3 1.9G 187M 1.6G 11% /mnt/sda11
.
===== OPTICAl DRIVE =====

.
===== USB INFO =====
Removables:
Removable status: sd0:0:0:0:[sda]Protect
.
lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 044e:3001 Alps Electric Co., Ltd UGTZ4 Bluetooth
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
.
===== SCREEN INFO =====
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
.
===== MODULES LOADED =====

.
===== NETWORK INFO =====
eth0 Link encap:Ethernet HWaddr 00:1B:D3:8B:BE:52
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21b:d3ff:fe8b:be52/64 Scope:Link
UP BROADCAST MULTICAST MTU:1492 Metric:1
RX packets:44 errors:0 dropped:0 overruns:0 frame:0
TX packets:90 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14300 (13.9 Kb) TX bytes:11180 (10.9 Kb)
Interrupt:20 Memory:f6a00000-f6a20000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:196 errors:0 dropped:0 overruns:0 frame:0
TX packets:196 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:16536 (16.1 Kb) TX bytes:16536 (16.1 Kb)

wlan0 Link encap:Ethernet HWaddr 00:26:C6:D0:49:B4
inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::226:c6ff:fed0:49b4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:121 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:39586 (38.6 Kb) TX bytes:1716 (1.6 Kb)
.
# Generated by dhcpcd from wlan0
# /etc/resolv.conf.head can replace this line
domain hsd1.tx.comcast.net.
nameserver 192.168.0.1
# /etc/resolv.conf.tail can replace this line
.
===== PCI INFO =====
lspci: 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
03:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
04:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
04:00.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
.
.
===== LOGS INFO =====
dmesg | tail
.
[ 1448.049962] e1000e 0000:00:19.0: eth0: changing MTU from 1500 to 1492
[ 1448.176961] e1000e 0000:00:19.0: eth0: changing MTU from 1492 to 1500
[ 1450.180942] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[ 1450.180949] e1000e 0000:00:19.0: eth0: 10/100 speed: disabling TSO
[ 1455.448952] e1000e 0000:00:19.0: eth0: changing MTU from 1500 to 1492
[ 1455.571984] e1000e 0000:00:19.0: eth0: changing MTU from 1492 to 1500
[ 1457.478922] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[ 1457.478929] e1000e 0000:00:19.0: eth0: 10/100 speed: disabling TSO
[ 1463.307950] e1000e 0000:00:19.0: eth0: changing MTU from 1500 to 1492
[ 1463.435868] e1000e 0000:00:19.0: eth0: changing MTU from 1492 to 1500
.
.
cat /var/log/messages | tail
.
Feb 28 12:31:15 (none) dhcpcd[4511]: eth0: carrier acquired
Feb 28 12:31:15 (none) dhcpcd[4511]: eth0: rebinding lease of 192.168.1.3
Feb 28 12:31:15 (none) dhcpcd[4511]: eth0: acknowledged 192.168.1.3 from 192.168.1.254
Feb 28 12:31:15 (none) dhcpcd[4511]: eth0: checking for 192.168.1.3
Feb 28 12:31:21 (none) dhcpcd[4511]: eth0: leased 192.168.1.3 for 259200 seconds
Feb 28 12:31:21 (none) kernel: [ 1463.307950] e1000e 0000:00:19.0: eth0: changing MTU from 1500 to 1492
Feb 28 12:31:21 (none) dhcpcd: eth0: MTU set to 1492
Feb 28 12:31:21 (none) dhcpcd[4511]: eth0: carrier lost
Feb 28 12:31:21 (none) dhcpcd: eth0: MTU restored to 1500
Feb 28 12:31:21 (none) kernel: [ 1463.435868] e1000e 0000:00:19.0: eth0: changing MTU from 1492 to 1500
..

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Problem with network connect

Post#2 by brokenman » 28 Feb 2011, 20:19

I was thinking someone else would have this problem. I also have it. Did you set up your connection via the pns-tool?

I ran the pns-tool and use the resulting module to connect at boot. Connection drops a couple of minutes later with repeated annoying 'dings' as connection tries to reconnect. Manually running the following keeps me connected indefinitely afterwards.

Code: Select all

killall dhcpcd
killall wpa_supplicant
wpa_supplicant -c /etc/wpa_supplicant.conf -iwlan0 -Dwext &
sleep 3
dhcpcd wlan0
I am not sure what is causing this, may need to collect further info from others with same problem. I can say that we have the same chipset and audio driver, but different wifi cards. I don't think this is at the kernel level but will do further testing. Latest kernel should be updated this week. If you want to test you can create the script above and drop it into /usr/bin/wifi.sh and remove the kickoff lines from rc.local. Then wait 1 minute after booting before running wifi.sh.

EDIT:
brokenman slaps himself - and has his first coffee for the day.

I see now "my network card (wired, not wireless)" i will leave the above info for others with wifi problem of the same nature. For wired .... i will have to test again. Is there anyone else on your network?
How do i become super user?
Wear your underpants on the outside and put on a cape.

sci_fi
Black ninja
Black ninja
Posts: 52
Joined: 28 Dec 2010, 18:25

Re: Problem with network connect

Post#3 by sci_fi » 28 Feb 2011, 22:40

Thanks, brokenman:

Yes, it has been Monday all day. Tougher than usual.

Yes, it is my wired NIC that is having problems. Wireless worked out of the box.

I have tried PNS but it makes no difference.

For what it is worth, I see the same problem on Puppy 5.2. However, on Tiny Core 3.5 things work perfectly.

My NIC is connecting to a router via a standard ethernet cable. Comcast is on the other side of the router. No one else is on the network.

This is not a showstopper as this is a notebook and will usually be used wireless. However being obsessive about getting the details right is a prerequisite of using linux. So I will fix it if I can. Please keep it on the list of things to think about for 1.0

Thanks again.

sci_fi

User avatar
Mike_P
White ninja
White ninja
Posts: 5
Joined: 03 Mar 2011, 11:31
Location: Germany
Contact:

Re: Problem with network connect

Post#4 by Mike_P » 03 Mar 2011, 23:23

Have you looked on the intel site? This is driver orientated as the carrier drops off after a time. This is set within the driver if no handshake is detected, basically on notebooks to save juice. On the Intel site they have Linux drivers that might need to be implemented into the kernel. These small pci boards have been around for some time and are well documented. What the difference between the built in driver and the one you can download from Intels website I cant say, but it would be worth a kernel rebuild to find out, good luck anyway.
http://www.intel.com/products/ethernet/ ... F/V&s3=all

Mike

Post Reply