hi i just installed suse 9.1, everything went fine until the internet test on install
the message "dhcp client already running on eth0" occured

my realtek rtl8029 card was recognised and configured though (but with dhcp option, not static)
later, when i first booted it said "dhcp already running" and it couldn't get an ip from the dhcp
so that failed

once in suse, i tried ifconfig which returned

"lo .. somethingblablabla"

and

"eth0 ....
up broadcast notrailers running multicast
...
rx packets: 0 errors: 0 ....
tx packets: 0 errors: 60 ....
etcetera ...."

when i try ifdown eth0 and then ifup eth0 it sais
"starting DHCP Client Daemon on eth0 . . . . no ip address yet . . . backgrounding"

now when i try to ping my router (192.168.123.254) it sais "network is unreachable"

when i set ip as static (192.168.123.198) and in extra set default gateway as 192.168.123.254 and ping i just get that basic ping fail message

i can ping localhost though (so my card works)

typing dhcpcd doesn't help
it just does nothing for like 2 minutes and then returnes to konsole

i have disables iptables and set 192.168.123.198 as dmz in router

i can perfectly use the network card in windows on the same computer

has anyone had the same problem ??? i'm sorry the ifconfig msg isn't complete btw but that's because i couldn't copy it from linux to windows without any connection offcourse

try this from the command line:
(since I run redhat it might not be quite the same but similar)

. /etc/init.d/network stop

then type:

. /etc/init.d/network start

If you get starting eth0 and it fails to pull a connection then something is up with the dhcp or your router.
I know that I had big problems with a 3c905B card and redhat 8.0.

thanx for your reply, but ./etc/init.d/network stop & start didn't help
the command was recognised in suse and stop worked, but when i started some text showed up very quickly and then konsole shut down so i wasn't able to read the text ... i suppose that isn't normal

when i ifconfig'ed afterwards

only lo showed up, not eth0

oh by the way , the wonders of modern technology have allowed me to store everything on usb stick so i can give u more specific results


ifconfig :


pingin my router

OK I didn't expect the stop start thing to work. What I wanted to see is if it created an error. Do this type

script
. /etc/init.d/network stop
. /etc/init.d/network start

this will create a file called typescript that you can then look at and see what happened.

the script showed no errors network stop went fine
and network start showed something like this

eth0 device: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
eth0 configuration: eth-id-00:80:c8:dd:fd:e3 Starting DHCP Client Daemon on eth0... . . . . . no IP address yet... waiting
...

this isn't the real text, just a copy of my last post, but is sais +/- the same except for some "[" stuff etc ...

no errors except "no ip address"

should i make my "waiting for mandatory services" time longer ?

well your current problem is that you are not pulling an IP addy so you can't do anything. I am not totally sure how SUSE does dhcp. I know that redhat waits for a specified amount of time and then it will time out and give you an error stating it didn't get an IP. Not sure where to go from here. You might want to see if there is an updated driver for your NIC.

hmm my card just uses the ne2k-pci module which comes with any distro these days...
too bad .. i really don't know how to solve this problem
strange, i have been able to use this card on red hat 8 for a while , untill i got my new router i think
chould the problem be my router because i can perfectly use it in windows xp
i guess i'll just have to keep using windows xp pro for now

do you think it matters whether i use coax or utf because for some strange reason red hat 8 worked with coax while windows also worked with utp

in this case it doesn't work with both

i think i have found the problem ... when in windows the 'link' light that confirms the physical connection with my card starts lighting up when windows has loaded

while in linux the lights doesn't light up at all ... never ... chould that be because i allways switch between windows an linux by rebooting, and never turning off my computer completely ?
maybe my nic is still expecting a connection with a windows enviroment or something ...

i will now try turning my computer off completely

hi , err i 'll try to be as complete as possible, because what i found out might be a little confusing, since you're not here ... behind my computer

when i used to use red hat linux 8 , at first, i also couldn't access the internet, but, by accident, i found out that when using a coax cable instead of utp ( coax = round plug, in europe same cable as cable tv ) i COULD use internet, and since everything worked, i really didn't bother finding out why utp didn't work ...

now .. as said in my last reply, i have tried shutting down completely but with an utp cable, the link light just doesn't light up ... so, now knowing a 'link' wasn't obvious, i tried connection a coax cable to my card, transforming the other end in utp with a cross-blabla thingy, and then plugging it into my router ...
the result was that there was a link ! yet, the light staid continous for like 5 seconds, and after that , it just flickered very fast ( like 4 times a second )
i tried pinging my router but host was still unreachable
i then brought down and back up my card, which also didn't work
so ... now ..

i really don't mind using that extra cable for linux but what chould the reason be that there still isn't a decent connection ?? i must tell you that in windows ... the link light from the coax cable also flickers rapidly ...

i hope this isn't too confusing

Well since I have never used coax on a network before I am not too sure how to set that up.

But try this. In windows (I am assuming XP or 2k here) go to start run, type cmd and hit enter. Then type ipconfig /all and record all the information there about your network setup. Then reboot into linux.

Now we want to manually setup the IP address on the NIC card. I am not exactly sure how to do this in SuSe. However you could also simply edit some file instead of doing the GUI way. The files I have to edi ton a redhat system are located here:
/etc/sysconfig/network-scripts/ifcfg-eth0
Now I bet yours will be similar if not the same.
In there should be some "variables" that you can set. Just change the values on the right side of the = sign. This will setup a statically assigned IP so that you won't have to worry about dhcp in case this is the problem. Once you have done this try to ping the router.

Hi,

I am having similar problem. And found following document from Suse support web site, will try it and see.

---
Waiting for Mandatory Device
Applies to: SUSE LINUX 9.1

Symptom
During the boot process, the following message appears: ...waiting for mandatory device...
...

---

Please use the URL to find the document.

http://portal.suse.com/sdb/en/2004/0...evices_91.html

Let me know if it work for you.

Frank

hi, thanx for your replies, but the problem 's solved now . i realized that i had the exact same nic in an older computer of mine. thinking it would probably not help, just for the heck of it, i tried using that card instead of my current realtek 8029(as).
guess what .. everything worked immediately !!
my card was automatically configured by dhcp, i could ping my router, and web pages, after deleting the configuration of the other card, so i guess i'll never know what the problem was, because the exact same card, in the same computer, using the same router DID work ...

Hi

Good to hear that your NIC is working now. For my case, I have to disable the APM and ACPI when system boot. I added options to the grub.conf file like:

apm=off, acpi=off, noapic

and Suse is then able to get the IP address from DHCP server properly. I did not do further research about ACPI. It is something call Advanced configuration & Power Interface - and it is able to take some device configuration such as address/IRQ from PC's bios.

Frank

Hello!

I have the same problem on my laptop, a Toshiba Satellite A100-529,with a dual boot Suse 9.3 with Windows XP. I edited the /etc/grub.conf file, which looks like this:
[HTML]setup --stage2=/boot/grub/stage2 (hd0) (hd0,6)
quit[/HTML]
and added just before "quit" the line that yylam suggested:
[HTML]apm=off, acpi=off, noapic[/HTML]
but the problem persists.....I have no idea why in Windows the network connection works fine, and in Suse it doesn't. I had several distros installed on dual boot, Ubuntu 6.06, FC5, FC6, Debian 3.1, and never had this sort of issue with them. On the other hand, i read on the internet that this is some sort of bug of Suse 9.3, and also of Suse 10.1 (perhaps even in other later versions, can't remember exactly)


I know this is an old thread, but maybe someone will be able to give me a hand in solving this.


Cheers!