FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I recently decided to install Fedora Core 5 on some computers and ran into something most peculiar. I installed it on my Laptop (Dell Inspiron 600m) with no problems. It was previously running FC4. Afterwards, I decided to install it on a desktop (Dell Pentium 4 system but I don't have access to more of the details of the sytem at the moment) and it seemed to have trouble connecting to the network using the NIC card. This is very strange because this same computer had FC4 previously and it had no trouble accessing the network.
When the system would start up, it would say that eth0 was setup with OK, and when I would go to the command prompt and type ifconfig, I would see correct IP information (the system is setup to automatically get the IP info from the router) but nothing would be accessable (cannot ping the router nor other computers on the network). I tried doing a ifdown eth0 and ifup eth0 and it would fail, giving out an error about not being able to ping (I'll try to get the exact error when I'm able to). When I try the use a linux rescue using the FC5 disk and tell it to setup the network connection it basically sits there doing nothing. The system isn't completely locked, however, because I can do a CTRL+ALT+DEL to restart the system, but it's surprising that it won't get past that if I try to start network services.
Interestingly enough, if I do the same thing (rescue) using the FC4 disk it can start the network services without problems. The system does have a wireless network card, so I suspected that perhaps FC5 tries to load that one in, too, where as FC4 ignored it, and maybe it's conflicting somehow. I tried booting the CD in rescue mode with the noprobe option and tried to add the network card (non-wireless) only and it gave me the same problem. I suspect there's an issue with the way FC5 detects hardware or sets up the drivers, but I don't know how to check, manually configure, or do any of that stuff. Am I on the right track? If not, what could be the problem? If yes, then how can I check and see hardware setting? Is it something with kudzu? Any help would be appreciated.
Is your card a pcmcia nic card or network card build into you laptop.
do a /sbin/ifconfig and post output here in your message.
do a /sbin/lspci -v and post that also.
Is your card a pcmcia nic card or network card build into you laptop.
do a /sbin/ifconfig and post output here in your message.
do a /sbin/lspci -v and post that also.
Also post the /etc/sysconfig/network-scripts/ifcfg-eth0 file.
Thank you for your reply. I don't have access to the system on the weekdays so it will take me a bit of time to get you the output.
Regarding your first question, this is a desktop computer. Both network cards are internal. No PCMCIA. I'm not sure if the NIC is integrated into the motherboard or not. I'll let you know on the weekend.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.