Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Linux Mint 11 -- Auto Ethernet Corruption?


  • Please log in to reply
5 replies to this topic

#1 geeceem

geeceem

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:01:14 PM

Posted 15 January 2012 - 01:37 PM

Dual booting Windows XP and Linux Mint 11, with hard-wired connection to router. On the Windows side, connection has never failed. On the Linux Mint side, it was sometimes slow and sometimes not. Of late, it started disappearing altogether. The "Auto Ethernet" option doesn't show up any more in the "Network Connection" box. "Enable Networking" is checked.

Here are some reports:

inxi -Fc 0


System: Host arbiter Kernel 2.6.38-13-generic i686 (32 bit) Distro Linux Mint 11 Katya
CPU: Single core Intel Pentium 4 (-HT-) cache 2048 KB flags (lm nx sse sse2 sse3) bmips 5984.86
Clock Speeds: (1) 2992.430 MHz (2) 2992.430 MHz
Graphics: Card ATI RV370 5B60 [Radeon X300 (PCIE)] X.Org 1.10.1 Res: 1440x900@59.9hz
GLX Renderer Gallium 0.4 on ATI RV370 GLX Version 2.1 Mesa 7.10.2 Direct Rendering Yes
Audio: Card Intel N10/ICH 7 Family High Definition Audio Controller driver HDA Intel BusID: 00:1b.0
Sound: Advanced Linux Sound Architecture Version 1.0.23
Network: Card Intel N10/ICH 7 Family LAN Controller driver e100 v: 3.5.24-k2-NAPI at port c8c0 BusID: 03:08.0
Disks: HDD Total Size: 80.0GB (4.6% used) 1: /dev/sda WDC_WD800JD 80.0GB
Partition: ID:/ size: 26G used: 3.4G (14%) fs: ext4 ID:swap-1 size: 1.07GB used: 0.00GB (0%) fs: swap
Info: Processes 143 Uptime 3 min Memory 314.9/999.6MB Runlevel 2 Client Shell inxi 1.4.23


Here are ifconfig and sudo lshw -C network reports. Top reports are with Ethernet connected via auto Ethernet; bottom reports are Ethernet disconnected and no "Auto ethernet" option showing in Network Connections.

Functioning:

geeceem@arbiter ~ $ ifconfig
eth0 Link encap:Ethernet HWaddr 00:12:3f:bd:22:d0
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::212:3fff:febd:22d0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:44 errors:0 dropped:0 overruns:0 frame:0
TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13093 (13.0 KB) TX bytes:9729 (9.7 KB)

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:40 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2640 (2.6 KB) TX bytes:2640 (2.6 KB)

------------

description: Ethernet interface
product: N10/ICH 7 Family LAN Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:03:08.0
logical name: eth0
version: 01
serial: 00:12:3f:bd:22:d0
size: 100Mbit/s
capacity: 100Mbit/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.24-k2-NAPI duplex=full firmware=N/A ip=192.168.1.2 latency=64 link=yes maxlatency=56 mingnt=8 multicast=yes port=MII speed=100Mbit/s
resources: irq:20 memory:efbff000-efbfffff ioport:c8c0(size=64)


==============================================

Non-functioning

eth0 Link encap:Ethernet HWaddr 00:12:3f:bd:22:d0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

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:40 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2640 (2.6 KB) TX bytes:2640 (2.6 KB)


--------------------------

*-network
description: Ethernet interface
product: N10/ICH 7 Family LAN Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:03:08.0
logical name: eth0
version: 01
serial: 00:12:3f:bd:22:d0
size: 10Mbit/s
capacity: 100Mbit/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.24-k2-NAPI duplex=half firmware=N/A latency=64 link=no maxlatency=56 mingnt=8 multicast=yes port=MII speed=10Mbit/s
resources: irq:20 memory:efbff000-efbfffff ioport:c8c0(size=64)

I see a slight difference, but don't know enough to understand what I'm seeing. What wants fixing?

BC AdBot (Login to Remove)

 


#2 stiltskin

stiltskin

  • Members
  • 238 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Western MO
  • Local time:01:14 PM

Posted 16 January 2012 - 05:57 AM

I'm answering because you got no others. I'm not sure I can help. But I have a couple of suggestions.

You may need to use a different driver. Sometimes it happens that the wrong driver is selected by the OS. When that happens you have to manually make it select the right one, then mask the wrong one out so it doesn't keep picking it up. I don't know what driver that chip should use. But there are plenty of sites on google that can explain how to do the work, and there should be some that discuss that particular chipset.

I take it you're running network-manager (the default). Try replacing it with wicd and see if you still have the problem. I've had one of those packages flake out on me before, where the other would work fine.

#3 geeceem

geeceem
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:01:14 PM

Posted 16 January 2012 - 10:50 AM

I'm answering because you got no others. I'm not sure I can help. But I have a couple of suggestions.

You may need to use a different driver. Sometimes it happens that the wrong driver is selected by the OS. When that happens you have to manually make it select the right one, then mask the wrong one out so it doesn't keep picking it up. I don't know what driver that chip should use. But there are plenty of sites on google that can explain how to do the work, and there should be some that discuss that particular chipset.

I take it you're running network-manager (the default). Try replacing it with wicd and see if you still have the problem. I've had one of those packages flake out on me before, where the other would work fine.


Many thanks. For some reason, I'm having a dickens of a time identifying how Windows identifies this port, as there isn't anything in the hardware config list by the same name. It's Pro/100 or some such. Correspondingly, I'm going to have to scratch around some more to make sure I have the latest driver for it. (I'm presuming that Linux Mint uses the same driver....)

The machine booted up in Linux w/auto ethernet just fine this morning. Because I have a number of other things on my plate today, I guess I'll download wicd but wait to install it until the auto ethernet connection disappears again. Maybe I like dramatic fixes too much.

Whatever. I'll post here again when something changes.

#4 stiltskin

stiltskin

  • Members
  • 238 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Western MO
  • Local time:01:14 PM

Posted 16 January 2012 - 04:44 PM

I doubt they both use the same driver. There's surely a linux driver for it built into the kernel. Especially if it's and Intel device.

If you download wicd from the repositories, it will uninstall network-manager. Rather, I should say they couldn't both exist on the same install in the past. Maybe that's changed since I last used anything where I wanted to use wicd.

#5 geeceem

geeceem
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:01:14 PM

Posted 16 January 2012 - 04:55 PM

If you download wicd from the repositories, it will uninstall network-manager. Rather, I should say they couldn't both exist on the same install in the past. Maybe that's changed since I last used anything where I wanted to use wicd.


Good timing: I just downloaded and installed wicd about 30 minutes ago, rebooted, and it appears to be active--but the old network icon hasn't disappeared from the tray and is still showing current and what appears to be be valid connection information. The wicd icon is also showing in the tray, but isn't showing any IP address or anything else in the properties: it's blank. And I know I'm connected because I'm posting this from the Linux boot.

It will be interesting to see what happens if auto ethernet decides to take the day off again.

This Linux stuff could drive you nuts if you're not careful.

#6 geeceem

geeceem
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:01:14 PM

Posted 25 January 2012 - 08:55 AM

It will be interesting to see what happens if auto ethernet decides to take the day off again.


Just for follow-up: I've been running with wicd for a little over a week now. I'm still seeing the original networking panel in the tray, along with the new panel that appeared when I installed wicd.

Since wicd was installed, I've only had one or two boot-ups in which Ethernet failed to launch, which is far better than what it used to be under the orginal networking module.

I do note that the relevant LED on the Ethernet jack at the modem lights up even before the BIOS comes to life and stays lighted so long as I'm at the boot menu (I have a dual-booting machine). If Ethernet is going to fail, it fails almost the instant that the Linux boot is launched, i.e., the LED goes out and stays out. This may be an insignificant finding for diagnostic purposes, but it does tell me whether or not I'm going to have Ethernet when Linux (Mint 11) is fully booted.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users