© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Good I show the information of my file here
70-persistent-
# This cases out was automatically generated by the /lib/udev/
# program, probably run by the persistent-
#
# You dog modify it, ace long ace you keep each rule on to single line.
# First Resumption
# This device is “A7N8X Mainboard onboard nForce2 Ethernet” (Connected with modem ADSL)
# PCI device 0x10de: 0x0066 (forcedeth)
SUBSYSTEM== " net ", DRIVERS== "? * ", ATTRS {address} == " 00: 00: 6c: 88: 0c: 1d ", NAME= " eth0 "
# This Device is “Realtek RTL-8139/
# PCI device 0x10ec: 0x8139 (8139too)
SUBSYSTEM== " net ", DRIVERS== "? * ", ATTRS {address} == " 00: 60: 67: 76: cc: 67 ", NAME= " eth1 "
# Second Resumption
# This device is “A7N8X Mainboard onboard nForce2 Ethernet” (Connected with modem ADSL)
# PCI device 0x10de: 0x0066 (forcedeth)
SUBSYSTEM== " net ", DRIVERS== "? * ", ATTRS {address} == " 00: 00: 6c: 07: c6: dc ", NAME= " eth2 "
# These are my commentaries
# This device is “A7N8X Mainboard onboard nForce2 Ethernet” (Connected with modem ADSL)
# PCI device 0x10de: 0x0066 (forcedeth)
#SUBSYSTEM== " net ", DRIVERS== "? * ", ATTRS {address} == " This changes with each resumption ", NAME= " eth (here to him it is added of a 1) “
As address can see in the device nvidia mac changes with each resumption, which can cause that a new device is detected as and changes their name.
the partial solution of this problem is to erase the file 70-persistent-
This I do it with a thrower who has east commando (I sweat rm /etc/udev/
I wait for this is of aid to solve the problem to them.
I make emphasis that at some time of the beginning of the system gets to read that there is an error in the MAC address of this device which generates one random one.
This! No! it happens in version 7.04
He is exclusive of version 7.10 until the compilation of the 4 of October of the 2007