List, good afternoon,
During an upgrade attempt of a Lenny server to Wheezy (the Debian docs
say do this via Squeeze) I can't restart the Squeeze system after
executing
# apt-get upgrade
# apt-get dist-upgrade
The machine is awkward to see, or get at, so I'm fairly keen to have
an SSH link to it to finish whatever further changes I need.
The initial reboot sequence begins loading the Squeeze system but
(from screen flashing by)
(a) notes that statd fails - mentions NFS
(b) pauses for around 2 mins waiting for nfsd to start (it ultimately
does not)
(c) seems not to bring eth0 up
(d) X / Gnome doesn't start
(e) machine gives me a login prompt.
Logging in as ron is ok, I can su, and running mc I can see that
/etc/network/interfaces contains the same data as had been used on
Lenny. But, trying
# ifup eth0
or
# if-up eth0
the machine replies with command not found.
Any 'ping' attempt reports 'network unreachable'.
dmesg reports
r8169 Gigabit Ethernet Driver 2.2LK-NAPI loaded
and
eth0: RTL8168c/8111c
Looking at the Debian Reference manual on Debian's website I see that
ifup is a command, so something basic must be missing from my Lenny ->
Squeeze update, and perhaps is stopping the network coming up.
Boot is from LILO (previously installed by Debian-Installer in Lenny).
Machine config is Celeron, 1G memory, 2 x 2TB RAID1, Gigabit
Ethernet on the motherboard; no CD-ROM, nothing in USB sockets, no
additional network cards or wifi, etc. Lenny was running until a few
minutes ago.
If dmesg reports seeing the eth interface, appears to be loading a
driver, and /etc/network/interfaces has the same static eth0
definition that worked in Lenny, does anyone on the list have an idea
what might be missing between the driver, and getting eth0 up?
Grateful for any ideas,
regards, Ron
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53cc0206.3090...@tesco.net
