- This topic has 5 replies, 3 voices, and was last updated Apr 2-6:02 pm by Anonymous.
-
Posts
-
delix02
on my Dell machine with an internal Ethernet chip this chip is found on eth0. However, it is changed later during the boot procedure to eth1.
In /var/log/messages I found the linesApr 1 19:20:01 dell kernel: [ 6.849098] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12 Apr 1 19:20:01 dell kernel: [ 6.894285] e1000e 0000:00:19.0 eth1: renamed from eth0 Apr 1 19:20:01 dell kernel: [ 7.454245] fb: switching to nouveaufb from simpleLater on I get an error message by the DHCP client that eth0 could not be found.
I had to set the LAN port to eth1 in wicd and this way I get internet access.
So it’s not really I problem for me, but the error message from the DHCP client is irritating.I searched the web for a solution and I thought it is a udev issue.
However, my /etc/udev/rules.de/70-persistent-net.rules contains# 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, and change only the value of the NAME= key. # PCI device 0x10de:0x0269 (forcedeth) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:19:99:15:b9:07", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"My question : is it save to remove the
KERNEL=="eth*"
entry and is it indeed the solution for the issue ?Note : I moved the hard disk with already installed antiX17 from another PC to the Dell. Is this the reason for the renaming ?
- This topic was modified 4 years, 1 month ago by delix02.
Anonymous
Note : I moved the hard disk with already installed antiX17 from another PC to the Dell. Is this the reason for the renaming ?
Yes.
That’s exactly what I tried to explain here:
https://www.antixforum.com/forums/topic/see-active-network-connection-in-liveusb/page/2/#post-19948delix02, here’s a snippet found via websearch which explicitly answers
is it save to remove the KERNEL==”eth*” entry and is it indeed the solution for the issue ?how-to-write-rules-for-persistent-net-names
it’s best to remove the KERNEL=”eth*” part of your rules otherwise they will not apply in cases where, during boot, the kernel gives a name that is not like eth* to an interface (in my case it was p9p1. I removed the KERNEL constraint and the rules got applied as expected).
thx for the answers !
I’ll give it a trial.https://unix.stackexchange.com/questions/91085/udev-renaming-my-network-interface
is the discussion I found, but I guess it is a bit of a “unfinished business”
(in my case) the removing of the “KERNEL==eth0” entry didn’t help. No changes.
I had to remove the whole rule file.
The next boot process created a new one with the correct ID for the Dells’ eth interface.- This reply was modified 4 years, 1 month ago by delix02.
delix02, thanks for reporting the solution.
- You must be logged in to reply to this topic.
