Hi all,
FINALLY!!! after a weeks struggle, I made it back to the net after upgrading from kernel 2.4.22 via 2.6.2 to 2.6.3!!!
I gave up on DHCP, and decided to put a static ip in /etc/rc.d/rc.inet.conf, as well as adding nameserver addresses in /etc/resolve.conf (tips from other LQ thread, to be found
here
BUT: now my cpu is going crazy, up to 100% at times?!
Anyone any idea why and what to do about it?
Here's the changes I made: (Slack9.1 btw)
bash-2.05b$ cat /etc/resolv.conf
nameserver 130.232.1.22
nameserver 130.232.1.1
search utu.fi
bash-2.05b$ cat /etc/rc.d/rc.inet1.conf
# /etc/rc.d/rc.inet1.conf
#
# This file contains the configuration settings for network interfaces.
# If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").
# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="" # <-- I don't need the onboard card
DHCP_HOSTNAME[0]=""
# Config information for eth1: # <-- this is my ethernet card
IPADDR[1]="130.232.59.57"
NETMASK[1]="255.255.254.0"
USE_DHCP[1]=""
DHCP_HOSTNAME[1]="leon-fyg"
# Config information for eth2:
IPADDR[2]=""
NETMASK[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""
# Config information for eth3:
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""
# Default gateway IP address:
GATEWAY="130.232.59.254" # <-- do I need this bit, and if so, for what?
# Change this to "yes" for debugging output to stdout. Unfortunately,
# /sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="no"
I tried to copy the boot msgs, but in dmesg there isn't that much info. Which log should I access for that? Please let me know which other info I should provide. I'love to!!
Happy Slacking again anyway, be it with a huge cpu overload...
Cheers, Leon.
EDIT: after calming down from this rush of joy (phew back on the net :-) I realise that after all, it works well! So, maybe I should give DHCP another try...
During boot cardmgr starts just fine, and finds my card (D-Link 600+, NE2000 compatable). But whatever I try, I get
"timed out waiting for DHCP response" Is there a way to keep the damn thing maybe waiting a bit longer for DHCP?
