Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 21

Thread: Network adapter bust - or is it?

  1. #11
    Join Date
    Mar 2010
    Location
    India
    Beans
    8,116

    Re: Network adapter bust - or is it?

    Is this a Gigabyte motherboard? Whether or not, is there a setting called IOMMU in the BIOS?

    If there is, try changing its state to whatever it currently is. If there is no IOMMU there, try resetting the BIOS to defaults.

    Depending on whether the system BIOS has the IOMMU feature, a few more options may be tried if the above doesn't work.

    In the meanwhile, please also try the lower speed with full duplex (if changing IOMMU or resetting BIOS doesn't work) -
    Code:
    sudo ethtool -s eth0 speed 10 duplex full autoneg off
    And.. please also check the dmesg log yourself (the /var/log/dmesg file). Are there any errors or otherwise interesting messages in it? If there are, please post those parts here. You may also check /var/log/syslog file which may sometimes contain useful messages that are not logged by dmesg.
    Varun
    Help others by marking threads as [SOLVED], if they are. (See how)
    Wireless Script | Use Code Tags

  2. #12
    Join Date
    Apr 2009
    Beans
    250
    Distro
    Xubuntu 20.04 Focal Fossa

    Re: Network adapter bust - or is it?

    Hi Varun and thanks for your patience

    Mainboard is ASUS, model P5KPL-AM SE

    No IOMMU setting found in BIOS.

    I found a setting LAN Option ROM which I enabled and then disabled again because it didn't have any apparent effect.

    I also found a setting in the "Tools" section called "AI NET 2" with the option to "Check Realtek LAN Cable". When enabled it would report "LAN cable not ready" and send me back to BIOS setup. If I tried to go into the IA NET 2 menu again BIOS would hang forcing me to hard reset. I had to reinstate BIOS defaults to disable LAN Cable check.

    BTW: I did, of course, plug the cable into another computer to make sure it works.

    Reinstated BIOS defaults -> nothing changes, i.e. network still down

    Reduced speed as per command you proposed -> no go

    I looked at /var/log/dmesg which I find kind of cryptic
    Searching for lines containing "eth0" I find, for example:

    Code:
    ADDRCONF(NETDEV_UP): eth0: Link is not ready
    
    r8169 0000:01:00.0: eth0: link down
    /var/log/syslog basically says the same but there is additional information that might be relevant:

    Code:
    Network Manager[762]: Ifupdown: get unmanaged devices count: 0
    Network Manager[762]: SCPlugin-Ifupdown: (16300848) ... get_connections.
    Network Manager[762]: SCPlugin-Ifupdown: (16300848) ... get_connections (managed=false): return empty list.
    Network Manager[762]: keyfile: parsing Wired connection 1 ...
    Network Manager[762]: keyfile:		read connection 'Wired connection 1'
    Network Manager[762]: Ifupdown: get managed devices count: 0
    Network Manager[762]: <info> modem manager is now available
    Network Manager[762]: <info> monitoring kernel firmware directory 'lib/firmware'.
    Network Manager[762]: <info> WiFi enabled by radio killswitch; enabled by statefile
    Network Manager[762]: <info> WWAN enabled by radio killswitch; enabled by statefile
    Network Manager[762]: <info> WiMAX enabled by radio killswitch; enabled by statefile
    Network Manager[762]: <info> networking is enabled by statefile
    Network Manager[762]: <warn> failed to allocate link cache: (-10) operation not supported
    Network Manager[762]: <info> (eth0): carrier is OFF
    Network Manager[762]: <info> (eth0): new Ethernet device (driver 'r8169' ifindex: 2)
    Network Manager[762]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
    Network Manager[762]: <info> (eth0): now managed
    Network Manager[762]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    Network Manager[762]: <info> (eth0): bringing up device.
    Network Manager[762]: <info> (eth0): preparing device.
    Network Manager[762]: <info> (eth0): deactivating device (reasong 'managed') [2]
    kernel: [   10.121108] r8169 0000:01:00.0: eth0: link down
    kernel: [   10.121651] ADDRCONF(NETDEV_UP): eth0: Link is not ready
    kernel: [   10.122120] ADDRCONF(NETDEV_UP): eth0: Link is not ready
    I had to copy this by hand (no network and I forgot to bring my pendrive) from the borked compter's screen, so there may be typos.

  3. #13
    Join Date
    Mar 2010
    Location
    India
    Beans
    8,116

    Re: Network adapter bust - or is it?

    Pretty good copy for a hand typed log.

    Not very sure but is the eth0 managed by the /etc/network/interfaces file? -
    Quote Originally Posted by texpat View Post
    Code:
    Network Manager[762]: <info> (eth0): deactivating device (reasong 'managed') [2]
    And do the classic ifconfig commands do anything? -
    Code:
    sudo ifconfig eth0 down
    sudo ifconfig eth0 up
    If not, I think I have tried all I could think of. The only thing left is to try the proprietary driver, assuming it is a driver bug (a serious one if it is).

    Accordingly, please download the r8168 driver from here : http://www.realtek.com.tw/downloads/...etDown=false#2

    Assuming you copied this driver package (r8101-1.024.00.tar.bz2) into your Home directory, extract and install it with -
    Code:
    tar xf r8101-1.024.00.tar.bz2
    cd r8101-1.024.00
    sudo ./autorun.sh
    It will automatically remove (and backup) the current driver, compile and install the proprietary one and load it. If that doesn't make the ethernet active either, we are probably beating a dead horse.
    Varun
    Help others by marking threads as [SOLVED], if they are. (See how)
    Wireless Script | Use Code Tags

  4. #14
    Join Date
    Jul 2010
    Location
    ozarks, Arkansas, USA
    Beans
    14,189
    Distro
    Xubuntu 22.04 Jammy Jellyfish

    Re: Network adapter bust - or is it?

    texpat; Hi !

    I have recently recovered in a similar situation; My steps:
    Hardwire procedure:
    1. network card detected ?
    sudo lspci | grep Ethernet
    2. IP address assigned ?
    ipconfig eth0 (or whichever the network is,eth1)
    -no address returned ?
    3. Check /etc/network/interfaces
    13.10 should be:
    # The primary network interface
    ##changed eth0 to eth1 26feb2014##
    auto eth1
    iface eth1 inet dhcp
    4. Disable the firewall (be prepared to know how to set it up again !)
    iptables -F
    ///
    What I found:
    a) Bent pin on my original inet card -> changed out the cable
    b) No response when pinging my router -> recloned the router mac addresses
    c) inappropriate setting in the control file /etc/network/interfaces -> set the correct device name
    ///
    With the above done, I had my internet connectivity established (4 days trouble shooting !)
    If you have to go to step 4 heed the warning and do your homework !

    just my little bit
    to try and help
    THE current(cy) in Documentation:
    https://help.ubuntu.com/community/PopularPages

    Happy ubuntu'n !

  5. #15
    Join Date
    Apr 2009
    Beans
    250
    Distro
    Xubuntu 20.04 Focal Fossa

    Re: Network adapter bust - or is it?

    @Varun: installed proprietary driver but still no fun

    Just for the heck of it I restared the machine to boot a live Linux (Parted Magic) from CD. Since I didn't get a network there either, I'm assuming I have a hardware problem.

    I checked for obvious damage, but I'm way out of my depth when it comes to hardware issues.

    @Bashing-om: thanks for chipping in.

    I ran through the first 3 points quickly:

    Network card is detected.
    No IP-address is assigned.
    etc/network/interfaces reads (just in case its important: the computer runs 12.04 LTS)
    Code:
    auto lo
    iface lo inet loopback
    I've decided to take the machine to the repair shop.

    Here's thanking you again for reading and contributing. Even though this time we couldn't solve the problem (possibly because it just couldn't be solved here), I've learnt a great deal again.

  6. #16
    Join Date
    Mar 2010
    Location
    India
    Beans
    8,116

    Re: Network adapter bust - or is it?

    Quote Originally Posted by texpat View Post
    Just for the heck of it I restared the machine to boot a live Linux (Parted Magic) from CD. Since I didn't get a network there either, I'm assuming I have a hardware problem.
    I happen to concur with you. If you haven't been removing the older kernels, try booting into one of them from the grub menu. If you don't get the grub menu by default at startup, tap the 'Shift' (or 'Esc' in some systems) key during the purple splash screen to get it.

    If the symptoms are same with the older kernel(s) also, then I'm fully convinced that it is a hardware fault.
    Varun
    Help others by marking threads as [SOLVED], if they are. (See how)
    Wireless Script | Use Code Tags

  7. #17
    Join Date
    Jul 2010
    Location
    ozarks, Arkansas, USA
    Beans
    14,189
    Distro
    Xubuntu 22.04 Jammy Jellyfish

    Re: Network adapter bust - or is it?

    texpat; Well.

    Taking the machine to the shop may well be the fastest solution, Overall, perhaps not the best. I am more than willing to do whatever I can to get ya up and running. As the card is recognized, the most likely cause is in configuration.
    Your /etc/network/interfaces file is correct for version 12.04 -> are you connecting through a router ? Is your wired connection through a cable modem to your ISP ? Does the output of "ifconfig" show that the loopback interface is good ? ( TX and RX number are all the same ?) Then we can assume that the card is good.

    Try RE-setting your router and modem ( do you get a blinking response on the link LED indicator on your modem ? ) - Maybe even the link is down between your hardware and the ISP ? ( maybe ask your provider to reset the cable modem for you ?)

    It would be a shame to spend good money only to find it is a config problem.

    where there are solutions there is no problem
    THE current(cy) in Documentation:
    https://help.ubuntu.com/community/PopularPages

    Happy ubuntu'n !

  8. #18
    Join Date
    Apr 2009
    Beans
    250
    Distro
    Xubuntu 20.04 Focal Fossa

    Re: Network adapter bust - or is it?

    I agree it may not be the best move to make, but the machine belongs to a small business I work for and, although not vital, is important enough to warrant throwing some money at it to get the problem solved in a more or less timely fashion.

    The problem is in the computer itself. I'm quite confident about that. Resetting the router was one of the first things I did. I checked the cable on another PC and it works perfectly well. I plugged another PC's ethernet cable (which I knew worked) into this computer and it remained mute. Other computers on the network can access Internet without problems.

    The problem is most likely a hardware problem. Although I didn't go through with Varun's proposal to boot an old kernel (by the time this was suggested the machine was already at the repair shop), I think Its safe to say its a hardware issue since the Parted Magic live CD also got no network, exhibiting the same symptoms as the native Ubuntu install (i.e. card checks out, but no IP and no traffic between computer and router, "network not accessible")

    I'm quite sure that there are many things you have in mind that may still prove me wrong, but unfortunately I don't have the time test them out.

    Nevertheless, thank you both and, by extension, the whole forum community. It isn't to be expected that we can solve all each other's problems here, but we'll sure give it our best shot!
    Last edited by texpat; February 28th, 2014 at 11:02 PM.

  9. #19
    Join Date
    Jul 2010
    Location
    ozarks, Arkansas, USA
    Beans
    14,189
    Distro
    Xubuntu 22.04 Jammy Jellyfish

    Re: Network adapter bust - or is it?

    texpat; Hey,

    OK, All then, as all is done presently we can do. We will await what the shop finds.

    Please to keep us informed -> and what else we can do.

    expediency is a
    harsh master
    THE current(cy) in Documentation:
    https://help.ubuntu.com/community/PopularPages

    Happy ubuntu'n !

  10. #20
    Join Date
    Apr 2009
    Beans
    250
    Distro
    Xubuntu 20.04 Focal Fossa

    Re: Network adapter bust - or is it?

    So the machine is up and running again. The problem was the network adapter.

    Repair shop installed a new one and BINGO!

    Marking this solved and hope that anyone with similar issues may benefit.

Page 2 of 3 FirstFirst 123 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •