Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
|
06-25-2001, 04:27 PM
|
#1
|
Member
Registered: Jun 2001
Posts: 30
Rep:
|
network card problems
Hi all
I am new to Linux. I have SUSE linux professional up and running but it cannot find my network card which is a
NETGEAR FA311 Fast Ethernet PCI Adapter. it works under windows 2000 fine. I have tried alot of things like YAST etc but it jusrt cannot see it. Can any1 help me plz
thanks alot
mkhan
|
|
|
06-25-2001, 05:18 PM
|
#2
|
Member
Registered: Mar 2001
Location: Manchester UK
Distribution: Mainly Fedora
Posts: 496
Rep:
|
Hi
Don't know SUSE or YAST as I'm in the RedHat camp, but I know the FA311 well! If you search these forums looking for FA311, you'll find the answers. The natsemi driver in the 2.4.2 kernel runs mine fine at boot, not as a module.
Jim
|
|
|
06-25-2001, 07:37 PM
|
#3
|
Member
Registered: Jun 2001
Location: Fairfax, California
Distribution: RH 9.0, RH 7.3, Mandrake 8.0
Posts: 986
Rep:
|
As drjimstuckinwin said, if the natsemi module is built into your kernel, you should be able to just select it in SuSE's network config program. I don't know SuSE, so I can't help you with that. If the module isn't listed, you'll need to compile it. The source files and instructions can be found here.
Here are a few of the standard things to try when your NIC is being uncooperative (I'm using RH 6.2, but the basics should apply):
1. Check the screen output at bootup. If the NIC is being properly initialized, you should see a line that says: "Bringing up eth0- O.K." If you see "failed" or "delaying" instead, you've got problems (see #3).
2. Assuming the NIC comes up, you can do the configuration with the graphical configuration tools linuxconf or netconf. Click on Basic host information->Adaptor 1. From there, select eth0 as the device, choose the natsemi driver from the drop-down list of kernel modules, and enable the device. Then either choose DHCP (if you're using it), or enter your IP information manually. After that, fill in your DNS and gateway/routing info under the appropriate sections.
3. If you get a failure on bootup, you may have a resource conflict with another device. Try turning off Plug-N-Play support in your BIOS, it can cause conflicts with some cards.
4. Log in as root, go to the command line or terminal window, and type "cat /proc/pci" and verify that your NIC is being recognized. Type "cat /proc/interrupts" and make sure your NIC's IRQ isn't conflicting with another device. Type "cat /proc/ioports" and check the address ranges for conflicts. If you have resource conflicts, you can try rearranging the slot order of your PCI cards.
5. You can also verify the IRQ/address info by typing "ifconfig". There should be stats for the loopback device (lo) and eth0.
6. If you get card recognized, but the module isn't loading, try to load it manually by typing "insmod natsemi" or "modprobe natsemi". After that, type "lsmod" to list all loaded modules; the natsemi module should show up there.
7. You can then manually configure the NIC by typing "ifconfig eth0 xxx.xxx.xxx.xxx up", where xxx.xxx.xxx.xxx is your IP address.
8. Last, type "alias eth0 natsemi" to associate the driver with the card.
Those are the most basic steps; try them and see what happens. If you still have issues, repost with specifics on the problems.
Hope this helps.
Last edited by DMR; 07-03-2001 at 08:23 PM.
|
|
|
06-26-2001, 07:07 AM
|
#4
|
Member
Registered: Jun 2001
Posts: 30
Original Poster
Rep:
|
thanks DMR
DMR and drjimstuckinwin
thanku so much for those helpful hints. I am at work right now and when i get home im going to try these things out. I will keep u updated. thanks once again!
mkhan
|
|
|
06-26-2001, 10:42 AM
|
#5
|
LQ Newbie
Registered: Jun 2001
Posts: 6
Rep:
|
Ethernet card not recognized by Linux
Hi !
As described by DMR (step 1), the screen at bootup says "failed" and "delaying" about eth0.
(step 3) PNP support is turned off in my PC's BIOS.
(step 4) "cat /proc/pci" doesn't display any network card.
I have RedHat Linux 6.2 and a D-LINK DE-220 ethernet card (on an ISA slot).
What can I do to make it work ?
Thanks
|
|
|
06-26-2001, 03:04 PM
|
#6
|
Member
Registered: Jun 2001
Location: Fairfax, California
Distribution: RH 9.0, RH 7.3, Mandrake 8.0
Posts: 986
Rep:
|
FNJ Mancini,
For an ISA card, try to configure the NIC's resources (IRQ and base address) using the DOS diagnostic/setup utilities which should have come with the card.
Also, try turning BIOS Plug-N-Play on. While the usual suggestion is to turn PNP off, enabling it sometimes gets certain cards working.
|
|
|
06-26-2001, 07:23 PM
|
#7
|
Member
Registered: Jun 2001
Posts: 30
Original Poster
Rep:
|
NETGEAR FA311 STILL NOT WORKING
Hi again
I have tried what DMR told me but still no luck.
can someone step me through the process? if i try to do "insmod natsemi" or "modprobe natsemi" i get a msg saying that module is compiled for kernel 2.4 and your kernel is 2.4.16
( a newer kernel).
I also have drivers (FA311) and my eth0 is not being picked up at boot time
i need help!
mkhan
|
|
|
06-26-2001, 09:06 PM
|
#8
|
Member
Registered: Jun 2001
Location: Fairfax, California
Distribution: RH 9.0, RH 7.3, Mandrake 8.0
Posts: 986
Rep:
|
O.K., it's all coming back to me now:
When I first installed my FA-311 in Redhat 6.2 (which didn't natively support the card) I tried to use the precompiled natsemi.o module which came on a floppy with the NIC. I got the same complaints about kernel versions, and needless to say, it didn't work.
I thought that the driver was part of the 2.4.x kernels, but if not, you're going to have to compile a module for your kernel version. As I recall, this was a bit of a pain in the arse, but if you follow the directions very carefully it should work. The source code can be found here, and the instructions are here. One important ommission in the instructions:
after executing the compile command (gcc -DMODULE etc...), but before doing "insmod natsemi.o", do "depmod -a" to resolve the dependencies between natsemi and pci_scan. You can also just use "modprobe natsemi.o" instead of insmod, it should accomplish the same thing.
Good Luck!
|
|
|
06-27-2001, 04:16 PM
|
#9
|
Member
Registered: Mar 2001
Location: Manchester UK
Distribution: Mainly Fedora
Posts: 496
Rep:
|
Hi
I found the relevant number! If you recompile your kernel, and select the pci and other (I think that's the wording) NIC support then enable the natsemi dp83810 option. I put it directly into the kernel, but module is OK. It should work fine.
Jim
|
|
|
06-27-2001, 05:32 PM
|
#10
|
Member
Registered: Jun 2001
Posts: 30
Original Poster
Rep:
|
DMR - i seriusly need help
Dear DMR
I have tried everything but im getting no where - to segmentation faults to other stupidness
can i call you? i think this wud be alot easier becoz i urgently need my network card working and im losing so much time
if it is ok for me to call you then i REALLY would appreciate it
Regards,
m khan
u can email on mubashar_khan@hotmail.com
thanks alot
|
|
|
06-28-2001, 05:07 AM
|
#11
|
Member
Registered: Jun 2001
Posts: 30
Original Poster
Rep:
|
kernel version
actually i got it wrong: my kernel is version 2.2.16 and not 2.4.x.x. So i am using an older kernel. Damn can someone email me the driver???
mkhan
|
|
|
06-28-2001, 09:13 AM
|
#12
|
Member
Registered: Mar 2001
Location: Manchester UK
Distribution: Mainly Fedora
Posts: 496
Rep:
|
go to www.sonnik.com/fa311 and grab the one there. If I've got the address wrong, search the networking forum, it's in a few of the threads.
Jim
|
|
|
07-03-2001, 03:33 AM
|
#13
|
LQ Newbie
Registered: Jun 2001
Posts: 6
Rep:
|
Hello DMR :
I turned Plug-and-Play ON and configured the IRQ (3) and I/O address (0x300) into netconf, but I still have no device /dev/eth0...
|
|
|
07-03-2001, 08:35 PM
|
#14
|
Member
Registered: Jun 2001
Location: Fairfax, California
Distribution: RH 9.0, RH 7.3, Mandrake 8.0
Posts: 986
Rep:
|
Quote:
Originally posted by FNJ Mancini
Hello DMR :
I turned Plug-and-Play ON and configured the IRQ (3) and I/O address (0x300) into netconf, but I still have no device /dev/eth0...
|
When you say you "have no device /dev/eth0", do you mean that you literally have no entry for "eth0" in your /dev directory?! That would be odd, but if that's really the case, you can use the MAKEDEV command to recreate the device entry. I did it once when I accidentally deleted the entry for my floppy from /dev, but that was a long time ago and I don't remember the specific command syntax. Try man MAKEDEV for more info.
mkahn:
My free time is very limited (and fractured) right now, and I think I'm out of suggestions concerning your problem, so I don't think a troubleshoot over the phone is going to be very productive. I hate not being able to solve a problem, but I really am out of ideas. Sorry I couldn't be of more help.
Last edited by DMR; 07-03-2001 at 08:43 PM.
|
|
|
07-05-2001, 02:40 AM
|
#15
|
LQ Newbie
Registered: Jun 2001
Posts: 6
Rep:
|
DMR :
I have no entry eth0 in the /dev directory indeed.
To use the command mknod, I would have to know the minor and major number of the device, as well as wether it is a block or character device...
Maybe I should search the D-LINK web page.
|
|
|
All times are GMT -5. The time now is 06:47 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|