Page 2 of 2 FirstFirst 12
Results 11 to 20 of 20

Thread: System network broken, due to wrong installed driver (need help fast)

  1. #11
    Join Date
    Aug 2012
    Location
    UK
    Beans
    145
    Distro
    Lubuntu

    Re: System network broken, due to wrong installed driver (need help fast)

    that photo made my brain hurt, might seem like a daft question but have you checked that after you made changes to the device that it has the correct network information ie password etc?

  2. #12
    Join Date
    Jul 2007
    Beans
    15

    Re: System network broken, due to wrong installed driver (need help fast)

    No because I could not get to any settings anymore. See the second picture on the forum. And sorry yhe image hurt your eyes but I only have one computer. And switching from usb OS to the OS i have on the pc it takes to much time.

  3. #13
    Join Date
    Aug 2012
    Location
    UK
    Beans
    145
    Distro
    Lubuntu

    Re: System network broken, due to wrong installed driver (need help fast)

    was there an uninstall script that came with the driver? If not you could try looking in additional drivers in the settings menu and see if you can get rid of it from there.
    could also try some things found here http://ubuntuforums.org/showthread.php?t=838345
    such as: sudo /etc/init.d/networking restart
    Which is also what I found when looking around for a way to reset network drivers

  4. #14
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    20,782
    Distro
    Ubuntu 14.10 Utopic Unicorn

    Re: System network broken, due to wrong installed driver (need help fast)

    First, he needs no password with wired ethernet. Second, he already ran the uninstall script. Third, the original installed e1000e is what is now loading. Note in the brain hurting photo it says version 1.5.1-k. Here is modinfo from my stock machine:
    Code:
    $ modinfo e1000e
    filename:       /lib/modules/3.2.0-30-generic-pae/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
    version:        1.5.1-k
    license:        GPL
    description:    Intel(R) PRO/1000 Network Driver
    author:         Intel Corporation, <linux.nics@intel.com>
    <snip>
    So we know the original is now back in place. It is obviously not connecting for some other reason(s).

    Please click the Network Manager icon, Edit Connections and see if there are any extra settings you added in either or both wired or wireless. I am concerned about the ADDRCONF entry above. If there are any settings you added, remove them. NM ought to find and connect to your network without any human intervention.

    I would like to see some additional diagnostics. Rather than a huge photo, I suggest you put the results into a text document and transfer it to a USB key so you can then post it here after you boot into another computer. Please do:
    Code:
    sudo cat /var/log/syslog | grep -e eth0 -e e100 -e etwork | tail -n25 > wouser.txt
    Now look in your user directory and find the text file wouser.txt, drag it to your USB key and post it here.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D.

  5. #15
    Join Date
    Jul 2007
    Beans
    15

    Re: System network broken, due to wrong installed driver (need help fast)

    Code:
    Sep  9 00:36:42 wouter-tablet kernel: [    1.403910] e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
    Sep  9 00:36:42 wouter-tablet kernel: [    1.403921] e1000e 0000:00:19.0: setting latency timer to 64
    Sep  9 00:36:42 wouter-tablet kernel: [    1.417897] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X
    Sep  9 00:36:42 wouter-tablet kernel: [    1.610501] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:23:18:b0:b4:80
    Sep  9 00:36:42 wouter-tablet kernel: [    1.610505] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
    Sep  9 00:36:42 wouter-tablet kernel: [    1.610533] e1000e 0000:00:19.0: eth0: MAC: 7, PHY: 8, PBA No: FFFFFF-0FF
    Sep  9 00:36:42 wouter-tablet kernel: [   24.734168] ADDRCONF(NETDEV_UP): eth0: link is not ready
    Sep  9 00:36:42 wouter-tablet kernel: [   25.049333] type=1400 audit(1347143801.522:3): apparmor="STATUS" operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=592 comm="apparmor_parser"
    Sep  9 00:36:42 wouter-tablet kernel: [   25.087581] init: network-interface (eth0) pre-start process (598) terminated with status 1
    Sep  9 00:36:42 wouter-tablet kernel: [   25.115591] init: network-interface (eth0) post-stop process (615) terminated with status 1
    Sep  9 00:36:42 wouter-tablet kernel: [   25.272236] init: network-interface (lo) pre-start process (688) terminated with status 1
    Sep  9 00:36:42 wouter-tablet kernel: [   25.280912] init: network-interface (lo) post-stop process (720) terminated with status 1
    Sep  9 00:36:42 wouter-tablet kernel: [   25.399005] cdc_ether 1-4:1.7: wwan0: register 'cdc_ether' at usb-0000:00:1a.7-4, Mobile Broadband Network Device, 02:80:37:ec:02:00
    Sep  9 00:36:42 wouter-tablet kernel: [   25.623931] init: network-interface (wwan0) pre-start process (790) terminated with status 1
    Sep  9 00:36:42 wouter-tablet kernel: [   25.626514] init: network-interface (wwan0) post-stop process (805) terminated with status 1
    Sep  9 00:36:42 wouter-tablet kernel: [   25.645335] init: network-interface (wlan0) pre-start process (822) terminated with status 1
    Sep  9 00:36:42 wouter-tablet kernel: [   25.702673] init: network-interface (wlan0) post-stop process (835) terminated with status 1
    Sep  9 00:36:43 wouter-tablet kernel: [   26.663179] init: networking main process (962) terminated with status 1
    Sep  9 00:38:42 wouter-tablet kernel: [  145.797116] type=1400 audit(1347143922.270:9): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1012 comm="apparmor_parser"
    Sep  9 00:38:42 wouter-tablet vmnetBridge: RTM_NEWLINK: name:eth0 index:2 flags:0x00001002
    Sep  9 00:38:43 wouter-tablet kernel: [  146.841675] init: network-interface (vmnet1) pre-start process (1200) terminated with status 1
    Sep  9 00:38:43 wouter-tablet kernel: [  146.859440] init: network-interface (vmnet1) post-stop process (1202) terminated with status 1
    Sep  9 00:38:43 wouter-tablet vmnet-natd: RTM_NEWLINK: name:eth0 index:2 flags:0x00001002
    Sep  9 00:38:43 wouter-tablet kernel: [  146.996483] init: network-interface (vmnet8) pre-start process (1210) terminated with status 1
    Sep  9 00:38:43 wouter-tablet kernel: [  147.004740] init: network-interface (vmnet8) post-stop process (1214) terminated with status 1

  6. #16
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    20,782
    Distro
    Ubuntu 14.10 Utopic Unicorn

    Re: System network broken, due to wrong installed driver (need help fast)

    init: network-interface (eth0) pre-start process (598) terminated with status 1
    Sep 9 00:36:42 wouter-tablet kernel: [ 25.115591] init: network-interface (eth0) post-stop process (615) terminated with status 1
    Interesting! May I see:
    Code:
    cat /etc/network/interfaces
    ifconfig
    nm-tool
    Good job posting, by the way.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D.

  7. #17
    Join Date
    Jul 2007
    Beans
    15

    Re: System network broken, due to wrong installed driver (need help fast)

    Code:
    [wouter@wouter-tablet:~]
    [03:00|0] $ cat /etc/network/interfaces
    auto lo
    iface lo inet loopback
    
    �kd�kd�kd�kd�kd�kd�kd�kd�kd�kd�kd�kd�kd�kd�kd�ku�ku�ku�ku�ku�ku�ku�ku�ku�ku�ku�k[wouter@wouter-tablet:~]
    [03:02|0] $ ifconfig
    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:646 errors:0 dropped:0 overruns:0 frame:0
              TX packets:646 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:49740 (49.7 KB)  TX bytes:49740 (49.7 KB)
    
    vmnet1    Link encap:Ethernet  HWaddr 00:50:56:c0:00:01  
              inet addr:192.168.214.1  Bcast:192.168.214.255  Mask:255.255.255.0
              inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
    
    vmnet8    Link encap:Ethernet  HWaddr 00:50:56:c0:00:08  
              inet addr:192.168.153.1  Bcast:192.168.153.255  Mask:255.255.255.0
              inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
    
    [wouter@wouter-tablet:~]
    [03:02|0] $ nm-tool
    
    ** (process:2368): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files
    
    NetworkManager Tool
    
    State: unknown
    
    
    ** (process:2368): WARNING **: error: could not connect to NetworkManager

  8. #18
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    20,782
    Distro
    Ubuntu 14.10 Utopic Unicorn

    Re: System network broken, due to wrong installed driver (need help fast)

    ** (process:2368): WARNING **: error: could not connect to NetworkManager
    Was Network Manager working properly before? I assume this is a virtual machine.

    You might try to reinstall it:
    Code:
    sudo apt-get install --reinstall network-manager
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D.

  9. #19
    Join Date
    Jul 2007
    Beans
    15

    Re: System network broken, due to wrong installed driver (need help fast)

    Quote Originally Posted by chili555 View Post
    Was Network Manager working properly before? I assume this is a virtual machine.

    You might try to reinstall it:
    Code:
    sudo apt-get install --reinstall network-manager
    No it's not a virtual machine. I run however a virtual machine on my OS sometimes for work. That are proberbly those vmnet1 and vmnet2.

  10. #20
    Join Date
    Jul 2007
    Beans
    15

    Re: System network broken, due to wrong installed driver (need help fast)

    ps. sudo apt-get install --reinstall network-manager does not work because I dont have internet...

    -edit-

    Oh yeah! It worked! Downloaded from http://packages.ubuntu.com/precise/net/network-manager and installed it! Works fine now again!

    Woooot. Now again trying to solve the 2.4 GHz 5GHz problem xD
    Last edited by Wouser; September 9th, 2012 at 11:59 AM.

Page 2 of 2 FirstFirst 12

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
  •