Re: Loss of lan after memory upgrade
On Thursday 14 January 2016 14:27:04 Brian wrote:
> On Thu 14 Jan 2016 at 13:08:27 -0500, Gene Heskett wrote:
> > On Thursday 14 January 2016 12:59:08 jdd wrote:
> > > Le 14/01/2016 17:23, Gary L. Roach a écrit :
> > > > On reboot, my router connection light is lit until the bios is
> > > > finished and the OS starts to load. At this point the light goes
> > > > out.
> > >
> > > what kind of router? ethernet link to the computer - usb or
> > > plugged card in a slot?
> > >
> > > may be you moved the card when working on the memory. try
> > > reinserting all cards
> > >
> > > jdd
> >
> > I suspect the real problem here, and its devoured my lunch several
> > times, is udevs rule that increments the device number everytime
> > something new is installed, includeing system sw from an "upgrade"
> > eth0 should remain eth0 if its the first interface found.
>
> Which udev rule is this which changes the interface name when *any*
> new hardware is installed? Perhaps you could quote it?
>
70-persistent-net in /etc/udev/rules.d
I'd post it, but mine has been hacked, by moi, so it wouldn't apply very
many other places. So has the one on the machine that drove me to drink,
so here is what it is now:
gene@GO704:~$ cat /etc/udev/rules.d/70-persistent-net.rules
# 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 0x14e4:/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0 (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1a:a0:a7:a8:d4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
ISTR its also marked immutable to keep udevs rule generator from "fixing"
it. That hard drive, with a complete, debian wheezy based LinuxCNC install
on it, had been in 4 computers while I was looking for one that actually
worked well full time. And every time I moved the drive, I lost my networking,
so I finally fixed it my way. Now it works, even if that Dell Dimension
745 upchucks tomorrow and I have to go & buy another that has a different
network chip in it.
It may not be correct in the udev authors opinion, but at least it works
here, and that, to this user, IS the bottom line.
> > Check your dmesg after a fresh boot, it can be extremely
> > enlightening. grep for eth and see what falls out.
>
> Decent advice. He's on Stretch, so 'journalctl' may be something to
> use as well.
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)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Reply to: