Summary: | iface 'lo' is not recognized | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Roel Groeneveld <roel.groeneveld> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Roel Groeneveld
2005-05-19 02:42:29 UTC
One addition: the usb_kings device that shows up under 'ifconfig -a' is my usb stick. Why did shows up there is beyond me, because it isn't plugged in. what does `ls -l /etc/init.d/net.lo` show ? what happens if you do this: ifconfig lo 127.0.0.1 up ifconfig lo (In reply to comment #2) > what does `ls -l /etc/init.d/net.lo` show ? > > what happens if you do this: > ifconfig lo 127.0.0.1 up > ifconfig lo Well: marvin ~ # ls -l /etc/init.d/net.lo -rwxr-xr-x 1 root root 512 Dec 17 10:56 /etc/init.d/net.lo marvin ~ # ifconfig lo 127.0.0.1 up SIOCSIFADDR: No such device lo: unknown interface: No such device lo: unknown interface: No such device marvin ~ # ifconfig lo lo: error fetching interface information: Device not found chances are good your kernel is configured wrong then Does /sys/class/net/lo/ exist? (In reply to comment #5) > Does /sys/class/net/lo/ exist? No, it doesn't. (In reply to comment #6) > (In reply to comment #5) > > Does /sys/class/net/lo/ exist? > > No, it doesn't. Anyway, I did some more testing with a more linux and gentoo savvy friend (icq support rulez). The following did work: ifconfig usb_kingston 127.0.0.1 up After that command, I can reach localhost again. Just pinging, and also managing cups via localhost:631 Now I'll try to figure out why this is happening and why lo just doesn't come up. Any pointers are welcome. Ah- something is renaming lo to "usb_kingston". Probably udev or nameif - remove any customizations you have made. (In reply to comment #8) > Ah- something is renaming lo to "usb_kingston". Probably udev or nameif - remove > any customizations you have made. I removed my local udev rules, rebooted, and now lo is up. So it must have been something related to that. I'll try to find the part of the rules that caused this and post it back here, in case someone else has the same issue in the future. fyi, this is what I had in 10-local.rules BUS="usb", SYSFS{serial}="L98040406292041500", SYSFS{manufacturer}="EPSON", NAME="%k", SYMLINK="printers/epson_stylus", GROUP="plugdev" BUS="usb", SYSFS{serial}="0831564033A0D1B3", SYSFS{manufacturer}="Kingston", SYSFS{product}="DataTraveler2.0", NAME="usb_kingston", SYMLINK="usbstorage/kingston_datatraveler", GROUP="plugdev" BUS="usb", SYSFS{serial}="000A27001013446F", SYSFS{manufacturer}="Apple", NAME=$ SYMLINK="ipod/shuffle", GROUP="plugdev" closing (In reply to comment #9) > (In reply to comment #8) > > Ah- something is renaming lo to "usb_kingston". Probably udev or nameif - remove > > any customizations you have made. > > I removed my local udev rules, rebooted, and now lo is up. > So it must have been something related to that. > > I'll try to find the part of the rules that caused this and post it back here, > in case someone else has the same issue in the future. fyi, this is what I had > in 10-local.rules > > BUS="usb", SYSFS{serial}="L98040406292041500", > SYSFS{manufacturer}="EPSON", NAME="%k", SYMLINK="printers/epson_stylus", > GROUP="plugdev" > BUS="usb", SYSFS{serial}="0831564033A0D1B3", > SYSFS{manufacturer}="Kingston", SYSFS{product}="DataTraveler2.0", > NAME="usb_kingston", SYMLINK="usbstorage/kingston_datatraveler", > GROUP="plugdev" > BUS="usb", SYSFS{serial}="000A27001013446F", SYSFS{manufacturer}="Apple", NAME=$ > SYMLINK="ipod/shuffle", GROUP="plugdev" > Since the Kingston rule is the only rule where I defined a NAME, and this NAME is the usb_kingston that showed up with an ifconfig, it must be related to that. Thanks for the help, dsd and SpanKY. :) |