linux - eth0 disabled / eth0 does not seem to be present / after restoring image

28
2013-07
  • basic6

    The NIC doesn't work anymore on my Fedora 15 again after restoring the system from an image.

    ifconfig doesn't show the NIC anymore (only the loopback adapter). system-config-network says it (eth0 - the only NIC) is "disabled". When clicking "Activate", it says: Device eth0 does not seem to be present, delaying initialization.

    service network status shows both lo and eth0 under "Configured devices", but only lo under "Currently active devices". ifconfig eth0 up claims that there's "no such device". service network restart shows a big red "FAILED" (some other networking related services won't start either).

    Here's the important part of how this happened:

    I have backups of my system partition that I restore when the system freezes (happened this time after installing the ATI graphics driver for Linux) or power goes out. Those backups are made with Clonezilla. The external hard drive where they're stored is ok (no SMART complaints), not very old and I handle it very carefully. Plus I let Clonezilla calculate MD5 sums for every backup and I let it check those before restoring anything. Since I restore the latest backup after any system crash, all backups are "clean", so they represent a state in which the system has never crashed. So long story short - I think the backups are reliable and restoring one should bring the system back in a perfectly clean state.

    I've restored the system several times, this is (at least) the second time the network adapter doesn't work afterwards. The first time, (AFAIR) I have just successfully upgraded from Fedora 14 to 15, but the latest backup was F14. So I restored it and after (re-)upgrading to F15, the NIC was working perfectly fine. Another time the NIC was gone, I played around with network and NetworkManager. I don't exactly remember what I did, but apparently I got it working again (plus an ugly red X is in the tray since then, saying "No network interfaces" when hovering). Also notable is the fact that when this happens, the system doesn't seem to recognize USB drives anymore (I'm pretty sure it was the same last time). So I plug in a USB drive, but Dolphin won't show it (so I can't mount it) - lsusb will show it though.

    I've googled a little bit without success. I found tips for doing things I've already tried or stuff like the "ONBOOT=yes" line in some config which already looks like that. Any idea how to get this thing working again? But (almost) more importantly: The NIC was working just FINE when I made the image, then I restored the image, so the system partition (including all configs) should look EXACTLY like when it was working so how on earth is it possible that the NIC doesn't work anymore??

    Edit:
    For the record, I won't use Clonezilla anymore. dd does the job perfectly, every single dd restore was successful.

  • Answers
  • Zeroedout

    You may have r8169 loaded instead of r8168. Try doing lsmod |grep r81 If it shows r8169 then remove it modprobe -r r8169 and insert the correct one modprobe r8168

  • Indrek

    You need to edit /etc/udev/rules.d/70-persistent-net.rules. It probably does not contain the proper data.

    It should look something like this for slirp:

    # This file was automatically generated by the /lib/udev/write_net_rules
    # program run by the persistent-net-generator.rules rules file.
    # You can modify it, as long as you keep each rule on a single line.
    
    # PCI device 0x1a55:0x0005 (conet)
    SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:ff:09:25:4b:f8", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
    

  • Related Question

    fedora - Webcam nightmare on LINUX
  • Mike

    I have a computer relatively new with Fedora 10. I have bought a webcam, plugged it in, run cheese and the webcam works perfectly. So, it is supported by the kernel.

    Than, the hard part...

    I have tried to use X-LITE, Skype and now QNext and the camera does not works on these apps. All I see is a black or scrambled colored noise pattern.

    Qnext gave me this errro message

    Device 'v4l:5' detection failed: java.lang.Error: Can't open video card 5
          Video device 'v4l:6' detection failed: java.lang.Error: Can't open video card 6
          Video device 'v4l:7' detection failed: java.lang.Error: Can't open video card 7
          Video device 'v4l:8' detection failed: java.lang.Error: Can't open video card 8
          Video device 'v4l:9' detection failed: java.lang.Error: Can't open video card 9
    Finished detecting Video capture - 0 devices found
    

    The camera shows perfectly as /dev/video0 when I plug it in.

    So, if the kernel supports it, what is the matter with linux? WTF!

    I have tested on UBUNTU, on another box, and I have the same problem.

    Any suggestions?

    thanks for your time.


  • Related Answers
  • Niek Bergman

    It may be that the other programs you are running do not support cameras that only support V4L2 by default (e.g. the application does not support V4L2)

    Try the following:

    Run your application from the command-line, but prefix your command with the following:

    LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so
    

    This should allow compatibility with applications that use V4L1.

    Also, please make sure that no other application is using the camera. Using 1 camera in more than 1 application is usually not supported.

  • Nerdfest

    You may need to adjust your kernel module for various bits of improper behaviour by some camera models. try:

    rmmod uvcvideo
    
    modprobe uvcvideo quirks=2
    

    There are other quirks values ... 2 happens to work for me for a no-name camera.

  • Shadowfirebird

    In my limited experience, the application you are most likely to have success with is Ekiga. It's a standard part of Ubuntu.

    That said, Webcam support in Linux is pretty rough. Sorry.

  • user27450

    Is your platform 64-bit? If it is, sometimes the v4l libraries have compatibility issues. The LD_PRELOAD solution worked for me and skype.