PDA

View Full Version : odd DHCP reboot issue


cprice
2007-03-02, 05:58 PM CST
hey guys,

i'm a new fedora user, and relatively new to linux. i've installed fedora core 6 recently, and during the install process i noticed an odd problem with my network card, and i'm not sure if it's software or hardware related. when i reboot my computer to switch from win XP pro to linux or vice versa, or if i simply reboot my computer within OS, my network card does not work upon boot. that is, i get this error message:

via-rhine device eth0 does not seem to be present

originally, when i noticed the internet problem, i noticed it in win xp. in win xp, i would run ipconfig, and no network card would be detected. the only fix for this problem that i've found is to completely shut down the computer, unplug my computer and wait about 10 seconds and plug it back in. the waiting time indeed matters, as the network lights have to be off for a few seconds. if you only wait 5 seconds, for example, you reboot without any changes to the situation.

this unplug and replug and reboot fix is bizarre for me because i've never had any problem like this before. any ideas?

cheers,
cprice

Dies
2007-03-02, 06:09 PM CST
Sounds familiar, sounds like a bug. Maybe someone here has that card and can give you a solution. The only thing I would try would be to bring it down, maybe rmmod the module it uses before rebooting - lsmod will show you which modules are loaded.

ifdown eth0
rmmod <name of the module>

just to see what happens.

cprice
2007-03-02, 07:17 PM CST
ifdown command gives command not found

as does ifconfig

Dies
2007-03-02, 11:15 PM CST
You have to be root to issue those commands:

su -
ifdown eth0
rmmod <something>

cprice
2007-03-03, 09:51 AM CST
i looked some earlier posts and tried those commands, too, both as user and su. same result. i'll give it another shot, but for now i received the same command not found error even as su.

cprice
2007-03-05, 09:10 PM CST
ok, i found out the problem with the diagnosis, and i feel like a dunce ... so now lookin at fixing the issue ...

http://www.linuxquestions.org/questions/showthread.php?t=389491

Dies
2007-03-05, 09:57 PM CST
ok, i found out the problem with the diagnosis, and i feel like a dunce ... so now lookin at fixing the issue ...

http://www.linuxquestions.org/questions/showthread.php?t=389491


There is no need to "fix" anything since nothing is broken.
If you want to add it to your path that's fine but you really just need to type the commands I gave correctly

su -

is not the same as

su

cprice
2007-03-06, 08:25 PM CST
no, i meant that i am now trying to figure out why my card is no longer responding when i reboot.

i can run ifdown eth0, and everything seems fine. if i run ifup eth0, it finds my IP again just fine. no error messages appear. i'll add some more info as i get it. it's a busy week with classes, exams, and such

cprice
2007-03-08, 08:44 PM CST
so the problem has not resolved itself. some information about the setup. i'm running a xen setup.

when i ifconfig when my networking is working, i get five devices:

lo, eth0, peth0, vif0.0, and xenbr0. i looked up some info on these and found that xenbr0 sort of coordinates the peth0, eth0, vif0.0, etc. when my networking is not working, only the lo and xenbr0 are up. i assume xen runs a script to set up the dom0 and so forth to link up eth0 and peth0 and the virtual eth0. so something is going wrong here when i restart.

i hope this helps. sometimes i have other devices running, such as sit0, sit1, sit2 if ipv6 is up. i've been playing around with ipv6. i can disable it if need be, but the problems i've been having were occurring before i played around with ipv6.

any ideas?