Re: Deep problem, need help

From: Dave (NO_SPAM_drobbins_at_drobbins.net)
Date: 01/13/05 

Date: Thu, 13 Jan 2005 10:55:25 -0500

Bjørn Tore Sund wrote:

> On Thu, 13 Jan 2005 10:06:38 -0500, Dave wrote:
>>
>> I've been trying to setup fedora core 3 on a box with an Abit VP-6
>> motherboard (dual cpu). The install goes fine. When I start the machine
>> up, the networking doesn't work. All the little GUI tools say eth0 is
>> active. The output of ifconfig looks like it should, but if I try to
>> ping someone it just times out. This problem occures with core 2 as
>> well. I'm running core 1 on the machine as I write this, so it appears
>> that the problem comes with the 2.6 kernel which is in core 2 and 3 and
>> not in 1. I installed core 3 on another machine and it works great. I'm
>> looking for ideas on debugging this. It appears to be some kind of
>> hardware problem. I've tried 2 different NIC's, no difference. I've
>> tried running ethereal and then pinging some machine and I don't see any
>> outgoing ping packets. If I ping this machine from another I see the
>> little light on the NIC blink but ethereal sees no incoming packets.
>> I've got a DSL connection to the net and one of those linksys soho
>> routers. There is a little 5 port switch between the machine and the
>> router. Now, this is real interesting, I've found a neat little tool,
>> mii-tool, it give you info about you network link. If I run it it tells
>> me I've got a 100 MB/s full duplex link to the switch. If I replace the
>> switch with an old 10 MB/s one I've got laying around, it reports that
>> it's 10 MB/s. So the link is up and working. No interesting stuff in
>> /var/messages. Any good ideas on how to try to debug this problem?
>> Anybody have any experience with the 2.6 kernel and this Abit
>> motherboard? It seems the problem is tied to this mobo.
>
> I've seen similar stuff, usually it's been related to IRQ conflicts.
> And yes, there's a BIG difference in how different motherboards handle
> this. You've tried different NICs, but have you tried the same NIC in
> several different PCI slots? How many other cards to you have in there?
> How many and which units does 'lspci -v' show to be sharing the same
> IRQs?
>
> Bjørn

That sounds like a likely solution, I just don't know how to debug it
I read about the path a packet takes when it enters the NIC
It hits the NIC and triggers a hardware interrupt that tells the driver to
come get the data. It sound like that's not happening. I added the output
of lspci -v at the end of the page I made
the machine has a soundcard and the NIC in it
the soundcard doesn't work either
I yanked the soundcard out and moved the NIC to a different slot before I
made those sceenshots
still no luck

Thanks
Dave

Relevant Pages