1. Check ('pgrep dhcpcd' or 'ps -C dhcpcd') if /sbin/dhcpcd is running (should since you have USE_DHCP[1]="yes") -- got
Code:
root: pgrep dhcpcd
root: ps -C dhcpcd
PID TTY TIME CMD
root:
2. else restart inet1 service -- not sure about this, but I did this:
Code:
root: ifconfig eth1 up
root:
3. Now check ifconfig, route, lease file, /etc/resolv.conf contents and syslog -- made a few fumbles at first:
Code:
root: ifconfig eth1 up
root: ifconfig eth1
eth1 Link encap:Ethernet HWaddr 30:85:a9:eb:72:a5
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:1 overruns:0 frame:1
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:60 (60.0 B) TX bytes:0 (0.0 B)
Interrupt:17 Base address:0xa000
root: ifconfig
eth1 Link encap:Ethernet HWaddr 30:85:a9:eb:72:a5
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:2 errors:0 dropped:2 overruns:0 frame:2
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:120 (120.0 B) TX bytes:0 (0.0 B)
Interrupt:17 Base address:0xa000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
root:
root:
root: route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
loopback * 255.0.0.0 U 0 0 0 lo
root: route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
root:
root: cat /etc/resolv.conf
# Generated by dhcpcd for interface eth0
nameserver 217.32.171.21
root:
4. Else you could run dhcpcd manually with messages saved and on stdout: '/sbin/dhcpcd -k; /sbin/dhcpcd -d eth1 2>&1 | tee /flash/dhcpc.log'
Code:
root: /sbin/dhcpcd -k; /sbin/dhcpcd -d eth1 2>&1 | tee /flash/dhcpc.log
/sbin/dhcpcd: not running
Broadcasting DHCP_DISCOVER
timed out waiting for a valid DHCP server response
root:
Didn't know where to find syslog (man syslog and it's "see also"s didn't help) but I found what I think you meant in /var/log/syslog. Nothing that was obviously (to me) related to ethernet except what had already shown in boot messages or other screen messages (and given in earlier posts).
5. Else try reconfiguring with 'netconfig'. Wish I'd known about that one years ago! ... but it didn't help this time. It put rc.inet1.conf exactly back to where it was originally except for the "yes" in USE_DHCP[0]="yes" that was USE_DHCP[0]="" on the original installation (and that I didn't know back then to change) and many minor changes in comments, but only in comments.
However, in case netconfig had corrected other files that I didn't know about, I moved the "yes" back to USE_DHCP[1] and rebooted. No good. Everything was as before running netconfig. Maybe some other file(s) assume eth0? Wonder why it renamed it eth1?
So, as the hardware's OK (Windows can use it), I guess it must be one of
-- my drivers are too old for the new hardware, or
-- something was configured at install time (rather than copied from the installation disc and finalised at boot time) that's wrong for the new box, but would be fixed by re-installing, or
-- the Slack 12.2 installation disc as a whole is too old for the new box.
Just had a thought re re-installation -- it's a 32-bit system copied from a 32-bit box to a 64-bit box. There are various mismatch messages in the log files, and although the other devices seem to work (keyboard, mouse, monitor, USB, DVD), bulk copy from my USB HDD is sometimes fast and sometimes very slow.
Would it be worth installing from scratch to see what happens?
