DebianThis forum is for the discussion of Debian Linux.
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.
My PC connects via wire to a belkin wireless router. It takes about ten minutes after I boot untill I can ping the router. Then for another 10 minutes I get huge % of packet loss. Once up and running, it is often okay for a long period of time. If the network is working, and I reboot, the network will come right up, unless I let it sit for a few hours of more.
I have no idea what's going on. I have connected other PCs to the same router via cable, and they work fine.
I am guess there is something wrong with my nic. So if I put in a new nic, will debian detect it? And what do I do if debian does not detect it?
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
It can be a buggy module for the nic on the kernel you are using. You can goto www.kernel.org and look through the changelogs on the version you have. Maybe it says there is a patch or you upgrade to the latest kernel if it mentions fixes to the module it uses.
Post the output of the following
/sbin/lspci -v ( info related to the nic )
/sbin/lsmod ( the module that is loaded for the nic )
Have you tried a different nic cable or plugged into a different port?
I don't know the inner workings of the debian to say what it does to new hardware. Usually for me I manually change the needed configuration files.
Odd's are it's the NIC. if you install a new one it should detect it, it will probably come up as eth1 instead of eth0 though .. which can be fixed if it bothers you.
I have tried a different patch cord, and it didn't help. I have also tried plugging in to different ports on the router. I dual boot, and the windows side is flaky also.
Didn't work. I but in another card, but it was not detected.
The interface that seems to be malfunctioning in a realtek 8139, it is built in to the motherboard. I tried putting another realtek 8139 into a pci slot, but second card was discovered.
I get the same problem. Debian 6.0 box.
I moved the HD to another computer that has a different nic.
The new nic shows up as eth1 instead of eth0.
What file do I have to delete or edit in order to make the new nic show up as eth0.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.