eth0 module
 

I am trying to manually install my netgear 310 ne ethernet card . It is not recognized on boot . what files do I need to access to find out what module is being called up and if I am experiencing any conflicts with other devices. I am a newbie and am still feeling my way around this command line stuff, any help would be appreciated thanks

Here's some stuff I posted in an earlier thread (11 earlier threads, actually ;) ):

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 tulip 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. Update:: Redhat stopped including linuxconf and netconf as of version 7. I'm not familiar with their current config utilities.

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. As root, type "lspci" 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. Type ifconfig. There should be stats for the loopback device (lo) and eth0. Verify that the IP infomation for eth0 is correct, and note the IRQ/base address information. If eth0 doesn't show up, type ifconfig -a. The -a option tells ifconfig to report on all interface, regardless of whether they are active or not.

6. If you get card recognized, but the module isn't loading, try to load it manually by typing "insmod tulip". After that, type "lsmod" to list all loaded modules; the tulip module should show up there.

7. You can then assign the NIC a static IP (if you need to) by typing "ifconfig eth0 xxx.xxx.xxx.xxx", where xxx.xxx.xxx.xxx is your IP address.

8. Look in /etc/conf.modules (/etc/modules.conf in some distros/versions for the line: alias eth0 tulip.
If it doesn't exist, and lsmod did not list the tulip driver as being loaded, add the line to the file.

If none of the above does the trick, tell us the results you get. Also (important), tells us what distro you're using.

eth0 problems
 

when i type in Ispci I get command not found
when i type in ismod I get command not found
insmod tulip tells me module named tulip already exists
using /lib/modules/2.2/17-21 mdk/net/tulip.o
checked interrupts and it is on irq 11 no conflicts
checked ioports and it is on c7059foo-c705a2ff
no apparent conflicts
I am using the mandrake 7.2 distro. I can get the card to load using linux config gui but when i reboot the command line give me an error couldnot load molule eth0 failed
this is what
ifconfig brings after I go to linuxconfig gui
eth0 Link encap:ethernet HWaddr 02:00:07:e3:96:f2
broadcast mtu:1500 metric :1
rx packets:0 errors:0 dropped:0overruns:0 frame:0
tx packers:0 errors:4 dropped:0 overruns:0carrier:8
collisions:0 txqueuelen:100
Interrupt:9 base address: 0x6f00

Lo Link encap:Local Loopback
Inet addr:127.0.0.1 Mask: 255.0.0.0
Up Loopback Running Mtu:3924 Metric:1
rx packets:0 errors:0 dropped:0 overruns:0 frame:0
tx packets: 0 errors:0 dropped:0 overruns;0 carrier:0
collisions:0 txqueuelen:0


I really don't know where to go from here Help anybody?
thanx

"when i type in Ispci I get command not found"
> OK, try "cat /proc/pci" instead.

"when i type in ismod I get command not found"
> The first letter of the command is a lower-case "L", not an "i" (the commmand name is short for LiSt MODules I believe) It's easy to to confuse the two characters.

>The output of ifconfig isn't showing any IP information for eth0. There should be a line similar to the following:
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
Are you using static addressing, or DHCP? If DHCP, the NIC may be failing to obtain an IP from the DHCP server.

>So, when you boot, you get "Failed" at the "bringing up eth0:" message, yes?

>Do "dmesg |grep eth0" and "dmesg |grep tulip". Post the results.

>Post the contents of your /etc/modules.conf file.

eth0 module
 

I appreciate the help. I went back and double checked everything and I believe I had a conflict with sound card on irq 11
removed the sound card and moved the ethcard over a slot, it now will recognize eth0 but only if I have dhcp off. If I try using dhcp it will not initilize the card. I am on a network with a linksys router, I have 2 other machines on the network, one has xp and the other has win2k, i have no problems accessing the net with either machine, how do I get the router to give the linux box an ip address, so I can surf the net with the linux box.



/etc/modules.config/
pre=install pcmcia_core /etc/rc.d/init.d/pcmcia start
alias parport _lowlevel parport_pc
pre-install plip modprobe parport_pc ; echo 7> /proc/parport/0/irq
alias eth0 tulip
alias sound-slot-0 ad1848
options sound dmabuf=1
alias midi op13
options op13 io=0x388
alias midi mpu401
options mpu401 io=0x330 irq=9
options as 1848 io=0x530 irq=11 dma=1 soundpro=1

i am not sure about the character you have between the

dmdsg grep eth0 what is that line and how do you type that??

your help has been and is greatly appreciated thanx

Congratulations on sorting out the IRQ voodoo, that's the first step.

The | character is the "pipe" symbol. It's the SHIFTed function of the backslash key; on the key, it shows up as two short vertical dashes, but on the screen is shows up as a single, longer vertical line.

As for the DHCP issue, it's possible that you don't have the DHCP client daemon (dhcpcd, not to be confused with the DHCP server daemon dhcpd) running. Your distro might use "pump" to configure DHCP instead of dhcpcd, though.

You can do a Google search using the keywords dhcpcd and pump to get a lot more info on the subject than I can give you (I set up my network using static IPs).

Let us know what you find.

:)