You are not logged in.
Pages: 1
I charge my iphone from my Archlinux X220 and when I boot with it attached I have headaches, despite having a UDEV rule to try ensure e1000e is *always* on eth0.
As you can see from this log: https://gist.github.com/3517356
e1000e gets put on eth1
the udev rule doesn't work
*Help*. Thanks!
Offline
I think the iphone has nothing to do with it. A lot of people have been hit with network device naming issues lately. From what I understand, the only solution and the only option long-term is to use a name other than ethX for all devices. I moved to netX for my four wired nics:
SUBSYSTEM=="net", ATTR{address}=="xx:xx:xx:xx:xx:xx", NAME="net0"
SUBSYSTEM=="net", ATTR{address}=="xx:xx:xx:xx:xx:xx", NAME="net1"
SUBSYSTEM=="net", ATTR{address}=="xx:xx:xx:xx:xx:xx", NAME="net2"
SUBSYSTEM=="net", ATTR{address}=="xx:xx:xx:xx:xx:xx", NAME="net3"
Last edited by alphaniner (2012-08-29 19:34:57)
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
I would rather think the iPhone is causing a re-ordering of your hard disks and that your system doesn't find the correct bootdevice?
Offline
What makes you think the bootdevice is wrong? I boot up Arch just fine ...
LABEL=nocti / ext4 defaults 0 1
Offline
Just to clarify, when I said 'the iphone has nothing to do with it' I meant the iphone qua iphone. As I understand the situation, anything that caused a new eth device to be created would have the same effect.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
Pages: 1