eth0 fails on loading - Suse 8.2

[jimscafe]

I have Windows XP, Red Hat, Win 98 and Suse installed on my PC. Red Hat and Suse are very recent additions.

The motherboard is the Epox 8RDA which uses the nefarious nvidia drivers. I seem to have got the drivers installed correctly on Red Hat and on Suse but when I boot Suse it hangs when checking eth0. If I boot in Safe mode all is well.

I saw in another thread someone was recommended to type ifup eth0 but I don't know why - I did and it just returned to the prompt without displaying anything.

ifconfig returns if this helps.

eth0 Link encap:Ethernet HWaddr 00:04:61:46:5B:72
inet addr:192.168.2.22 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::204:61ff:fe46:5b72/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:460 (460.0 b)
Interrupt:11

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:190 errors:0 dropped:0 overruns:0 frame:0
TX packets:190 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:12388 (12.0 Kb) TX bytes:12388 (12.0 Kb)

I know the card is working because I am using it to write to this forum in XP, but I haven't used the card in either Red Hat or Suse yet. (To use the card to connect to my DSL provider, they will come to the house and set it up, I don't want to call them out unless I am certain the network card works in the Linux environment).

[mdwatts]

Originally posted by jimscafe

I saw in another thread someone was recommended to type ifup eth0 but I don't know why - I did and it just returned to the prompt without displaying anything.


That would indicate that the command was successful with no errors.

Have you setup the eth0 config files so it comes up at boot?

/etc/sysconfig/network/ifcfg-eth0

BOOTPROTO='static'
BROADCAST='192.168.1.255'
IPADDR='192.168.1.4'
NETMASK='255.255.255.0'
NETWORK='192.168.1.0'
REMOTE_IPADDR=''
STARTMODE='onboot' <--- THIS ONE ----
UNIQUE='ZcKW.SYXZLk83VE3'
WIRELESS='no'

[DMR]

Another member posted an identical problem in this thread (http://justlinux.com/forum/showthread.php?threadid=111114). The fix turned out to be disabling the apm power management.

[jimscafe]

Entering the following setting worked fine, added it grub

apm=off acpi=off

Thank you :)

[DMR]

You're welcome, glad it worked. :)

[Cadillac84]

Wow! That wasn't what I was going to guess!

Nice job! I was going to suggest YaST because I've noticed that when I install a new SuSE O/S, I don't get DHCP the first couple times around, and I am able to use YaST to "tweak" the network settings in all the right places to get it cranked up.

Great job noticiing that and solving the problem so quickly.

I won't have to worry about that one for a while, because all the machines I put SuSE on are too old for power management to be an issue.

But, I'll try to file that item in my little grey cells for future reference.

C