Can't even ping my router!

krtaeous · 11-16-2005, 11:42 AM

Okay, things have gone from bad to what the f*ck! I decided to reinstall FC4 fresh. it found my network card, called it eth0, and I was right back where I began - a seemingly valid DHCP configuration but no functionality.

After a couple of reboots, during the boot process, I suddenly get a message that says, "eht0 does not appear to be present"

Also, my sound card creates some "fatal error" during the boot process.

So I went sorting through the output of dmesg and found...

tulip: Unknown parameter 'irq'
tulip: Unknown parameter 'irq'
snd_intel8x0: Unknown parameter `'
snd_intel8x0: Unknown parameter `'
snd_intel8x0: Unknown parameter `'

Does this relate to modprobe.conf? The first line says:

alias eth0 tulip

what is tulip? there is no man for it.

also the last line of modprobe.conf says:

options tulip irq=15

Any thoughts? Maybe I should just try Debian?

linuxamateur-two-too · 11-17-2005, 05:25 AM

Tulip is evidently the chip on your networkcard. (not the former computer Tulip). The most recent driver, dated 11 nov 2005 can be found at the Linux Arkiv via

http://sourceforge.net/forum/forum.php?forum_id=400090 and should soon be in every distros update-site (?)

sigsegv · 11-17-2005, 09:51 AM

The tulip driver is standard equipment in the kernel (lots of cards use the tulip chipset).

If you want to see all the options for the driver, do modinfo tulip and that will (should) spit out all the available flags for the module.

You can see if that option is the problem by running the following commands:

Code:

rmmod tulip
modprobe tulip
service network restart

The first command removes the module from the kernel. The second one loads it again, but this time without the irq=15 option. Then you restart the network to get a dhcp lease and all that good stuff.

If it doesn't work with no options, you'll need to read the docs for the driver and figure out what options it does need (they should be in the "Documentation" directory under the kernel source somewhere).

Darin · 11-17-2005, 12:23 PM

Quote:

TX packets:0 errors:7 dropped:0 overruns:0 carrier:7

That sticks out as something important. I've had problems with some network cards due to BIOS issues, aside from mii-tool and checking cabling, you could try one of these kernel paramaters:

apic
acpi=noirq
pci=noapic
pci=bios

they go in your /boot/grub/grub.conf file, at the end of the kernel line that should have the word quiet in it.

kernel (hd0,2)/vmlinuz-2.4.308 root=/dev/hda2 ro quiet

becomes:

kernel (hd0,2)/vmlinuz-2.4.308 root=/dev/hda2 ro quiet pci=noapic

*Note your kernel line will be different than this, just add the line to the end of it.

lagu2653 · 11-17-2005, 12:29 PM

I have SUSE. I had to set up the standard route to the IP-address of my router and I had to enter my two name-servers.

krtaeous · 11-20-2005, 03:07 PM

thanks for all the tips guys, but this thing still doesn't work!

i tried adding those arguments to my grub.conf (btw, the system didn't seem to like pci=apic)

i tried rmmod tulip and restarting the network.

nothing seems to work. i've got a lot on my plate right now, so I'm afraid i have to give up for now...