On Wednesday 28 August 2019 10:54:56 Curt wrote: > On 2019-08-28, Gene Heskett <ghesk...@shentel.net> wrote: > > It may, looks as if it could, but by itself lacks sufficient > > context to ring any bells. > > https://www.mail-archive.com/debian-user@lists.debian.org/msg747147.ht >ml > > Drop Revert-udev-network-device-renaming-immediately-give.patch. > ... > In case you rely on the udev renaming mechanism now would be a good > time to switch to the new scheme > > AFAIK, '/etc/udev/rules.d/70-persistent-net.rules' is the udev network > device renaming mechanism (which won't work without the patch, I > guess). > > > Cheers, Gene Heskett
What I am getting out of all this, is that its worked once before, renaming eth0 to eth1, as it says in /e/n/i now. But its now trying to bring up eth2. But eth2 does not exist. I'll search dmesg again to make sure. So: delete /etc/udev/rules.d/70-persistent-net.rules AND edit /e/n/i to put it back on eth0 where it belongs and it should work. But I want that file deleted at every bootup before any attempt to use it is made. So I'm going to go out and see if that can be made to work by deleting that file as the first line of if-up... But still couldn't find what looked like the right place. So I used the grub line above. Works. A new 70-persistent-net.rules file is created and its correct for eth0. Now I've got to figure out whats blown in the interfaces, the symptoms resemble a failure of the high speed seriel communications. But thats a different problem entirely, this instant problem seems to be solved. Thanks to all that contributed to my education on this. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
