Page 1 of 7 123 ... LastLast
Results 1 to 10 of 69

Thread: Can't connect to wired network.

  1. #1
    Join Date
    Jun 2010
    Beans
    5

    Can't connect to wired network.

    Hi all, I am a rather new Ubuntu user. I have an hp netbook.

    I got the computer to use as a sort of "total emerssion" tool to learn ubuntu (I really like the idea of Ubuntu and open-source software in general.) So it no longer has Windows on it. When I installed Ubuntu 10.4 I was able to connect to the internet using an ethernet cable. I had to follow some online instrutions to get the wireless set up.


    I had everything set up perfectly and running smoothly. And then I did the unthinkable: I installed some update packages a few days ago. Now, I cannot connect to the internet using either an ethernet cable nor wirelessly.


    Perhaps there is some hardware problem, I don't know. But I am hoping that one of you guys can help me.


    When I enter the command "ifconfig' here is what I get:
    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:1275 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1275 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:144049 (144.0 KB) TX bytes:144049 (144.0 KB)


    So, this seems odd to me (though I might be wrong) since it isn't even listing ethernet connections.

    Thanks for the help, guygs.

  2. #2
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    24,145
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Can't connect to wired network.

    Let's begin at the beginning. We'll use the terminal to list your PCI devices.
    Code:
    lspci -nn
    Omit all the items not related to your ethernet device and post the result here. We'll then have a better idea how to proceed.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D.

  3. #3
    Join Date
    Jun 2010
    Beans
    5

    Re: Can't connect to wired network.

    01:00.0 PCI Express Fast Ethernet controller [10ec:8136] (rev 02)
    02:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:
    4325] (rev01)


    Thanks.

  4. #4
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    24,145
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Can't connect to wired network.

    01:00.0 PCI Express Fast Ethernet controller [10ec:8136] (rev 02)
    This device is supposed to use the module r8169. Let's load it and see if your ethernet comes alive:
    Code:
    sudo modprobe r8169
    Is an interface created?
    Code:
    iwconfig
    If not, please post:
    Code:
    dmesg | grep 816
    Thanks.
    Last edited by chili555; June 8th, 2010 at 04:19 PM.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D.

  5. #5
    Join Date
    Feb 2007
    Beans
    286
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Can't connect to wired network.

    I think he means
    Code:
    ifconfig
    iwconfig is for wireless devices.

    If ifconfig does not show your Ethernet controller run
    Code:
    ifconfig -a
    ifconfig by itself only lists active controllers, if config -a will list all controllers, active and inactive.
    Floyd
    Ault, CO, USA
    Registered Linux User 436727
    Registered Ubuntu User # 13092

  6. #6
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    24,145
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Can't connect to wired network.

    I think he means
    Code:

    ifconfig

    iwconfig is for wireless devices.
    Quite correct. Sorry for the error.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D.

  7. #7
    Join Date
    Jun 2010
    Beans
    5

    Re: Can't connect to wired network.

    OK, I entered the commands, and here is the output:

    sudo modprobe r8169:
    WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored it a future release.


    ifconfig (I did this after entering ifconfig eth0 up and ifconfig eth1 up):
    eth0 Link encap:Ethernet HWaddr c8:0a:a9:22:e0:e1
    inet6 addr: fe80::ca0a:a9ff:fe22:e0e1/64 Scope:Link
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:23 errors:0 dropped:0 overruns:0 frame:0
    TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1975 (1.9 KB) TX bytes:468 (468.0 B)
    Interrupt:27 Base address:0x4000

    eth1 Link encap:Ethernet HWaddr c4:17:fe:bd:db:31
    inet6 addr: fe80::c617:feff:febd:db31/64 Scope:Link
    UP BROADCAST RUNNING 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)
    Interrupt:17

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

    dmesg | grep 816:
    [ 1.068329] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
    [ 1.068374] r8169 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    [ 1.068442] r8169 0000:01:00.0: setting latency timer to 64
    [ 1.068603] r8169 0000:01:00.0: irq 26 for MSI/MSI-X
    [ 774.394366] r8169 0000:01:00.0: PME# enabled
    [ 774.821199] r8169 0000:01:00.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
    [ 775.064768] r8169 0000:01:00.0: PME# disabled
    [ 779.388164] Synaptics: Clickpad mode enabled
    [ 787.192875] r8169 0000:01:00.0: PME# enabled
    [ 787.621189] r8169 0000:01:00.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
    [ 787.864775] r8169 0000:01:00.0: PME# disabled
    [ 2573.692889] r8169 0000:01:00.0: PME# enabled
    [ 2574.121187] r8169 0000:01:00.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
    [ 2574.364776] r8169 0000:01:00.0: PME# disabled
    [ 2630.536888] r8169 0000:01:00.0: PME# enabled
    [ 2630.965192] r8169 0000:01:00.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
    [ 2631.208773] r8169 0000:01:00.0: PME# disabled
    [ 2851.664889] r8169 0000:01:00.0: PME# enabled
    [ 2852.093201] r8169 0000:01:00.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
    [ 2852.336774] r8169 0000:01:00.0: PME# disabled
    [ 3174.766358] r8169: eth0: link up
    [ 3174.766380] r8169: eth0: link up
    [ 3369.838238] r8169: eth0: link up
    [ 3447.933741] r8169: eth0: link up
    [ 3607.754283] r8169: eth0: link down
    [ 3629.304951] r8169 0000:01:00.0: PME# enabled
    [ 3629.733188] r8169 0000:01:00.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
    [ 3629.881613] [drm] Big FIFO is enabled
    [ 3629.976832] r8169 0000:01:00.0: PME# disabled
    [ 3629.992154] r8169: eth0: link down
    [ 3630.543292] r8169: eth0: link up
    [ 3668.066332] r8169: eth0: link up
    [ 3728.213553] r8169: eth0: link down
    [ 3730.191077] r8169: eth0: link up
    [ 4273.839424] r8169: eth0: link down
    [ 4284.216945] r8169 0000:01:00.0: PME# enabled
    [ 4284.645189] r8169 0000:01:00.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
    [ 4284.888830] r8169 0000:01:00.0: PME# disabled
    [ 4284.904155] r8169: eth0: link down
    [ 4391.712950] r8169 0000:01:00.0: PME# enabled
    [ 4392.141187] r8169 0000:01:00.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
    [ 4392.384830] r8169 0000:01:00.0: PME# disabled
    [ 4392.400152] r8169: eth0: link down
    [ 4396.654157] r8169: eth0: link up
    [ 4397.346118] r8169: eth0: link down
    [ 4398.918372] r8169: eth0: link up
    [ 4529.868162] uhci_hcd 0000:00:1d.3: PCI INT D disabled
    [ 4530.016947] r8169 0000:01:00.0: PME# enabled
    [ 4530.445197] r8169 0000:01:00.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
    [ 4530.688827] r8169 0000:01:00.0: PME# disabled
    [ 4530.704152] r8169: eth0: link down
    [ 4531.255014] r8169: eth0: link up



    I still cannot connect to the internet.

    By the way, what does modprobe do? And what does dmesg | grep 816 do? Is there some resource online where I can learn the commands? I know several, things like mkdir, mv, etc., but there are a lot that I don't know and some like chmod 777 that I use, but I don't really understand the syntax or why "chmod 777" makes a file executable. I'd really like to learn as much as I can about Ubuntu and other open-source stuff as I can so I can contribute at some point. So, I'm sorry if some of this stuff is too basic, but I appreciate your help.

  8. #8
    Join Date
    Feb 2007
    Beans
    286
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Can't connect to wired network.

    OK, we have established that your network controller, eth0 is present. Now I want you to follow my instructions in post #7 in this thread.

    http://ubuntuforums.org/showthread.php?t=1494628
    Floyd
    Ault, CO, USA
    Registered Linux User 436727
    Registered Ubuntu User # 13092

  9. #9
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    24,145
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Can't connect to wired network.

    I had to follow some online instrutions to get the wireless set up.
    If he has and uses a wireless connection, why do you suggest he remove Network Manager? If he is a beginner at terminal commands, how is he going to switch to wireless when needed?

    I am skeptical that this is the best solution.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D.

  10. #10
    Join Date
    Feb 2007
    Beans
    286
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Can't connect to wired network.

    Once he gets his wired network up and running, I will have him install wicd. And if my way fails to get his wired network running, we can always reinstall network manager from the CD.
    Last edited by Detonate; June 8th, 2010 at 09:47 PM.
    Floyd
    Ault, CO, USA
    Registered Linux User 436727
    Registered Ubuntu User # 13092

Page 1 of 7 123 ... LastLast

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
  •