Deep problem, need help

Hello All,

I've been banging my head against a problem for several month now with no
luck. I've posted here before and gotten exccellent help but still haven't
been able to solve this. I wanna give it one more shot, so I've made up a
little web page where I can put screen shots of what I'm doing and
hopefully that will help someone steer me in the right direction

http://www.drobbins.net/fedora/help.html

below is one of my earlier posts describing the problem
It's a little dated, I think I've ruled out a hardware problem at this point
but it describes the problem and shows where I started from
I'd appreciate it if anyone would look at the little page I made and make
suggestions

TIA
Dave

/////////////////////////////////////////////////////////////////////////////////

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.

///////////////////////////////////////////////////////////////////////////////////

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
--
Bjørn Tore Sund "When in fear, and when in doubt;
(E-Mail Removed) Run in circles, scream and shout!"
Interaction! - Anonymous
http://www.interaction.worldcon.org.uk/

Dave wrote:
> Hello All,
>
> I've been banging my head against a problem for several month now
with no
> luck. I've posted here before and gotten exccellent help but still
haven't
> been able to solve this. I wanna give it one more shot, so I've made
up a
> little web page where I can put screen shots of what I'm doing and
> hopefully that will help someone steer me in the right direction
>
> http://www.drobbins.net/fedora/help.html

[snip]

Just a quick note before I forget.

The loopback is not in your routing table -- very important for IGMP
like arp.

My route table:
[me@pbrain]$ /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
xxx.xxx.208.0 0.0.0.0 255.255.248.0 U 0 0 0
eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
lo
0.0.0.0 xxx.xxx.208.1 0.0.0.0 UG 0 0 0
eth0

I will think on this some more, but _for_sure_ you want the loopback in
the route table.

Another quick note: write down and duplicate the ifconfig, route, and
network config files from the "good" FC1 to the boinking FC3. Posting
them would not be a bad idea either. Make sure to get all the network
config files. If you don't know what they are look at some RH9 docs
from Redhat's site. I'll make a confirmation list for the next post.

I suspect there's some config hole you haven't filled in yet
hth,
prg
email above disabled

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

prg wrote:

>
> Dave wrote:
>> Hello All,
>>
>> I've been banging my head against a problem for several month now
> with no
>> luck. I've posted here before and gotten exccellent help but still
> haven't
>> been able to solve this. I wanna give it one more shot, so I've made
> up a
>> little web page where I can put screen shots of what I'm doing and
>> hopefully that will help someone steer me in the right direction
>>
>> http://www.drobbins.net/fedora/help.html
>
> [snip]
>
> Just a quick note before I forget.
>
> The loopback is not in your routing table -- very important for IGMP
> like arp.
>
> My route table:
> [me@pbrain]$ /sbin/route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> xxx.xxx.208.0 0.0.0.0 255.255.248.0 U 0 0 0
> eth0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
> lo
> 0.0.0.0 xxx.xxx.208.1 0.0.0.0 UG 0 0 0
> eth0
>
> I will think on this some more, but _for_sure_ you want the loopback in
> the route table.
>
> Another quick note: write down and duplicate the ifconfig, route, and
> network config files from the "good" FC1 to the boinking FC3. Posting
> them would not be a bad idea either. Make sure to get all the network
> config files. If you don't know what they are look at some RH9 docs
> from Redhat's site. I'll make a confirmation list for the next post.
>
> I suspect there's some config hole you haven't filled in yet
> hth,
> prg
> email above disabled

ok, I added the loopback interface to the routing table
I think I had removed it in an earlier attempt to solve this
if you do a directory listing I think all the config files are under the etc
dir

http://www.drobbins.net/fedora/

Dave wrote:
> prg wrote:
>
> >
> > Dave wrote:
> >> Hello All,
> >>
> >> I've been banging my head against a problem for several month now
> > with no
> >> luck. I've posted here before and gotten exccellent help but still
> > haven't
> >> been able to solve this. I wanna give it one more shot, so I've
made
> > up a
> >> little web page where I can put screen shots of what I'm doing and
> >> hopefully that will help someone steer me in the right direction
> >>
> >> http://www.drobbins.net/fedora/help.html
> >
> > [snip]
> >
> > Just a quick note before I forget.
> >
> > The loopback is not in your routing table -- very important for
IGMP
> > like arp.
> >
> > My route table:
> > [me@pbrain]$ /sbin/route -n
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref
Use
> > Iface
> > xxx.xxx.208.0 0.0.0.0 255.255.248.0 U 0 0
0
> > eth0
> > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
0
> > lo
> > 0.0.0.0 xxx.xxx.208.1 0.0.0.0 UG 0 0
0
> > eth0
> >
> > I will think on this some more, but _for_sure_ you want the
loopback in
> > the route table.
> >
> > Another quick note: write down and duplicate the ifconfig, route,
and
> > network config files from the "good" FC1 to the boinking FC3.
Posting
> > them would not be a bad idea either. Make sure to get all the
network
> > config files. If you don't know what they are look at some RH9
docs
> > from Redhat's site. I'll make a confirmation list for the next
post.
> >
> > I suspect there's some config hole you haven't filled in yet
> > hth,
> > prg
> > email above disabled
>
> ok, I added the loopback interface to the routing table
> I think I had removed it in an earlier attempt to solve this
> if you do a directory listing I think all the config files are under
the etc
> dir

Yes, but do you know off the top of your head _all_ the _files_ in
which dirs below /etc? I can never remember them for more than a week
;-) Guess this time I'll make a handy list for personal reference.

This is why RH recommends the gui took for setting up/maintaining these
files since the tool writes to _all_ the necessary files. But editing
by hand gets to be habit.

Eg.,
/etc/host
/etc/host.conf
/etc/nsswitch << not likely unless you've tweaked it
/etc/resolv.conf
/etc/sysconfig/network << single file
/etc/sysconfig/networking << dir with many files
/etc/sysconfig/networking/ifcfg-lo
/etc/sysconfig/networking/devices/ifcfg-eth0
/etc/sysconfig/networking/profiles/default/hosts
/etc/sysconfig/networking/profiles/default/ifcfg-eth0
/etc/sysconfig/networking/profiles/default/network
/etc/sysconfig/networking/profiles/default/resolv.conf

Then you need to keep an eye on this if the interface comes up and
you're using dhcp:
/var/lib/dhcp/dhclient-eth0.leases

And not sure if this is complete. I'll still have to convince myself.
regards,
prg
email above disabled

prg wrote:

>
> Dave wrote:
>> prg wrote:
>>
>> >
>> > Dave wrote:
>> >> Hello All,
>> >>
>> >> I've been banging my head against a problem for several month now
>> > with no
>> >> luck. I've posted here before and gotten exccellent help but still
>> > haven't
>> >> been able to solve this. I wanna give it one more shot, so I've
> made
>> > up a
>> >> little web page where I can put screen shots of what I'm doing and
>> >> hopefully that will help someone steer me in the right direction
>> >>
>> >> http://www.drobbins.net/fedora/help.html
>> >
>> > [snip]
>> >
>> > Just a quick note before I forget.
>> >
>> > The loopback is not in your routing table -- very important for
> IGMP
>> > like arp.
>> >
>> > My route table:
>> > [me@pbrain]$ /sbin/route -n
>> > Kernel IP routing table
>> > Destination Gateway Genmask Flags Metric Ref
> Use
>> > Iface
>> > xxx.xxx.208.0 0.0.0.0 255.255.248.0 U 0 0
> 0
>> > eth0
>> > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
> 0
>> > lo
>> > 0.0.0.0 xxx.xxx.208.1 0.0.0.0 UG 0 0
> 0
>> > eth0
>> >
>> > I will think on this some more, but _for_sure_ you want the
> loopback in
>> > the route table.
>> >
>> > Another quick note: write down and duplicate the ifconfig, route,
> and
>> > network config files from the "good" FC1 to the boinking FC3.
> Posting
>> > them would not be a bad idea either. Make sure to get all the
> network
>> > config files. If you don't know what they are look at some RH9
> docs
>> > from Redhat's site. I'll make a confirmation list for the next
> post.
>> >
>> > I suspect there's some config hole you haven't filled in yet
>> > hth,
>> > prg
>> > email above disabled
>>
>> ok, I added the loopback interface to the routing table
>> I think I had removed it in an earlier attempt to solve this
>> if you do a directory listing I think all the config files are under
> the etc
>> dir
>
> Yes, but do you know off the top of your head _all_ the _files_ in
> which dirs below /etc? I can never remember them for more than a week
> ;-) Guess this time I'll make a handy list for personal reference.
>
> This is why RH recommends the gui took for setting up/maintaining these
> files since the tool writes to _all_ the necessary files. But editing
> by hand gets to be habit.
>
> Eg.,
> /etc/host
> /etc/host.conf
> /etc/nsswitch << not likely unless you've tweaked it
> /etc/resolv.conf
> /etc/sysconfig/network << single file
> /etc/sysconfig/networking << dir with many files
> /etc/sysconfig/networking/ifcfg-lo
> /etc/sysconfig/networking/devices/ifcfg-eth0
> /etc/sysconfig/networking/profiles/default/hosts
> /etc/sysconfig/networking/profiles/default/ifcfg-eth0
> /etc/sysconfig/networking/profiles/default/network
> /etc/sysconfig/networking/profiles/default/resolv.conf
>
> Then you need to keep an eye on this if the interface comes up and
> you're using dhcp:
> /var/lib/dhcp/dhclient-eth0.leases
>
> And not sure if this is complete. I'll still have to convince myself.
> regards,
> prg
> email above disabled

prg,

first of all, thanks for looking at my problem
I may be wrong but I kinda thought that all that was needed to ping another
machine on my local subnet by its IP address was that my IP address and
subnet mask be properly set. Obviously it takes more to get out onto the
net but I'm not there yet. When I look at all these config scripts I'm
kinda lost, since it looks like everything you mentioned is under /etc I'll
just dump the whole dir on the webpage. I'm not sure if you can look at
that stuff and find a bug, I know I can't. The other guy who responded said
he thought it sounded like an interrupt conflict. I told him I have a tool
called xosview that shows a lot of system info including irq activity and
it doesn't show any activity on the interrupt that's servicing the NIC when
I try to ping the machine. That's kinda the direction I'm leaning, although
I moved the NIC around so it uses a different interrupt and it didn't make
any difference. All the files under /etc will be ther in a few minutes

Thanx
Dave

Dave wrote:
[snip]
>
> prg,
>
> first of all, thanks for looking at my problem
> I may be wrong but I kinda thought that all that was needed to ping
another
> machine on my local subnet by its IP address was that my IP address
and
> subnet mask be properly set. Obviously it takes more to get out onto
the
> net but I'm not there yet. When I look at all these config scripts
I'm
> kinda lost, since it looks like everything you mentioned is under
/etc I'll
> just dump the whole dir on the webpage. I'm not sure if you can look
at
> that stuff and find a bug, I know I can't. The other guy who
responded said
> he thought it sounded like an interrupt conflict. I told him I have a
tool
> called xosview that shows a lot of system info including irq activity
and
> it doesn't show any activity on the interrupt that's servicing the
NIC when
> I try to ping the machine. That's kinda the direction I'm leaning,
although
> I moved the NIC around so it uses a different interrupt and it didn't
make
> any difference. All the files under /etc will be ther in a few
minutes
>
> Thanx
> Dave

With FC1 working OK, I would be inclined to make sure the config is
correct before exploring hardware -- just my approach. I'm 3 weeks
behind getting FC2 on this old clunker (PII 350 -RH8).

Unless the release nots state otherwise, I would assume that FC3 uses
the same config files for networking, so the files from FC1 should
provide config confirmation. You can change FC3 settings in gui by
typing system-config-network IIRC.

Once confirmed that the config is OK, _then_ I would look for hardware
conflict troubles. In fact, I was planning to google snoop when I get
more time

hang in there,
prg
email above disabled

> 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.

Sorry if this is a silly question, but have you ruled out a firewall
problem? Try the following:

iptables --policy INPUT ACCEPT
iptables --policy OUTPUT ACCEPT
iptables --policy FORWARD ACCEPT

iptables -t nat --policy PREROUTING ACCEPT
iptables -t nat --policy POSTROUTING ACCEPT
iptables -t nat --policy OUTPUT ACCEPT

iptables -t mangle --policy PREROUTING ACCEPT
iptables -t mangle --policy INPUT ACCEPT
iptables -t mangle --policy FORWARD ACCEPT
iptables -t mangle --policy OUTPUT ACCEPT
iptables -t mangle --policy POSTROUTING ACCEPT

for table in filter nat mangle ; do

iptables -t $table --flush # flush all chains
iptables -t $table --delete-chain # delete all user-defined chains
iptables -t $table --zero # zero counts

done

--
To reply by email, replace "deadspam.com" by "alumni.utexas.net"