You should have checked the HCL here at LQ. You seem to be using the wrong module.

http://www.linuxquestions.org/hcl/sh...php?product=54

I was in a hurry before. This could possibly solve the problem.

That should look like this:
/etc/modules.conf
alias eth0 3c59x
alias usb-controller usb-ohci
alias usb-controller1 ehci-hcd
alias souund-slot-emu10k1

Check for IRQ conflicts with your NIC.

How can I do this: check for IRQ conflicts with NIC???
I don't know how to do it.

Type "lspci -v" (no parenthesis). This should give you a list of everything including it's irq.

I have the exact same problem. The temporary fix was the following:
Boot with windows (I know, it sucks), if you have a dual boot sys, or get another PC to boot on Windows on your current connection.
open and command prompt (Start>Run>command Start>Run>cmd)
at the DOS prompt type ipconfig -all
and get all the network information including:
IP
Netmask
Gateway
DNS1
DNS2
and the name attributed to your box.
Reboot with Linux and configure your eth0 with a static device using the information you obtained. If your DHCP lease is long enough, it should work.

I am still looking for a more permanent solution, but I think it's ISP related.

G

/etc/modules.conf
alias eth0 8139too
alias usb-controller usb-ohci
alias usb-controller1 ehci-hcd
alias souund-slot-emu10k1

This might be your problem.
I don't see an alias in there for your network card, and your system is configured to use DHCP on boot, therefore, it will always fail on boot until you add an alias for the module for your network device.

I don't know what the module is called for the Relatek network card but, this is the problem.

EXAMPLE:

That should look like this:
/etc/modules.conf
alias eth0 3c59x
alias usb-controller usb-ohci
alias usb-controller1 ehci-hcd
alias souund-slot-emu10k1


Loads modules at boot time.
try 'lsmod' to see the currently used modules.

I have the same problem! Only problem is, I'm not sure if I have the correct driver loaded, as I do not know what type of NIC I have... It's just some kind of Generic one bought from PC world around the end of 2001... thats about all I know! I cant get any info about it from windows, as the driver supplied just calls it a "10/100M Ethernet PCI Adapter." XP reckons its an Asound based card but whenever it tries to use that driver (not the one supplied) then it doesn't work! would I be better off getting a more well known type of card that I know has a linux driver for it???

EDIT: I forgot to mention... I'm using Red Hat 9 and it picks up the network card during install and its using the "fealnx" module/driver for it...

B_U_M_P

same problem:

unable to ifconfig eth0 up
the error message is written:
SIOCSIFFLAGS: Function not implemented

I have a VIA-RHINE onboard NIC in Mandrake 10.

If it's the same generic PC World card as mine, it uses the Myson MDT8xx chipset, which kernels above 2.4.5 have support for.

This doesn't mean it'll work of course (though suse, mandrake and windows have no problem with it). Mine will never start on boot, something that I'm working on at the moment (hence came across this thread), however if you manually initialize it ('# ifconfig eth0 up') then activate it with 'neat' it should work. fealnx.o is the correct module for it but lord alone knows why redhat won't start it properly on its own.

I'll post more if I can get it resolved, I'm pretty new to this too.

EDIT: adding '/sbin/dhclient eth0' to my /etc/rc.d/rc.local seems to have done the trick. It's still failing on boot but seems to have an IP address from the DHCP server by the time X starts. It's unlikely to be that the DHCP server is too slow for the system (as it's not for suse or mandrake) so i can only imagine it's probably a bug in the 'fealnx' stuff. Try this though, worked for me.

hi, thanks for the tips thing is, I have sorted the problem out on mine by just getting a new network card. Had another one spare which i knew linux had drivers for thanks anyway

I had this problem with Fedora Core 2 with a 3c905b and found a message on dclug.org.uk that fixed me right up: Disable kudzu... something about the probing process screws up the NIC. Once I disabled kudzu, I was good as gold.

If you prefer the GUI, disable kudzu like this:
"Redhat menu", "system settings", "server settings", "services" and uncheck "kudzu".

If you prefer the shell, disable kudzu like this:
cd /etc/rc.d/rc5.d/
mv *kudzu K99kudzu

http://www.dclug.org.uk/archive/2003/11/msg00194.html

-Nate

Make sure you have dhclient installed. Running "rpm -q dhclient" should show something like "dhclient-3.0.1rc14-1". If nothing is displayed, dhclient isn't installed, but needs to be. (Try "up2date dhclient" for that.)