Michal Jaegermann wrote in <200008251448.IAA19487@ellpspace.math.ualberta.ca>:
> > My money is still on the unresolved symbols in the network
> > drivers.
> If that would be the case then you would get loud complaints
> from a compiler and/or when loading network driver modules.
> 'insmod -v' is pretty specific about that.
It's funny -- I remember insmod complaining, but loading the
module anyway; but when I tried it just now, it worked without
> "Identical" cards does not exclude hardware problems. Broken
> NICs happen from time to time. Did you try to switch cards
Since my first message, yes, I have. The problems remain on
the same machine.
> > Is redhat 6.1
> > somehow deficient in a way that slackware 7.0 isn't?
> You mean that you have an Alpha kernel from Slackware which works
> and another one from Red Hat which does not? Nothing really prevents
> you from taking a kernel from one distribution and dropping it,
> with modules, into another one; or configuring and recompiling your
No, the Slackware side is x86. The alpha I'm connecting it to
runs redhat 6.1. I have compiled my own kernels on both sides.
'depmod -e pci-scan' says that most unresolved symbols are pci-
related. I checked my kernel .config, and I enabled pci quirks,
but not pci optimizations. Relevant? I don't know.
> Most problems, when they show up, are actually platform independent.
> But I would be inclined to check first a configuration (like
> DNS which points into a non-existing or non-reachable server,
> or configured NIS when really there is not such thing).
I'll explain more of the story -- these two machines have been
hooked up with 10Mbps ethernet for months. I bought a pair of
10/100 NICs to increase the throughput. The one in the PC works,
but not the one in the alpha. In fact, my current working setup
is the old card in the alpha connected to the new one in the PC.
I think this would rule out configuration problems. And I
ruled out NIC hardware problems. If it were a network client
problem (ping, telnet), it should at least respond to pings,
which it doesn't. (Though TCP connections can be started but
not established -- SYN_RECV/SYN_SENT on both ends.) This would
seem to me to narrow it down to a driver problem, though I could
easily be forgetting something. Though the same drivers work on
the PC end. The unresolved symbols in the drivers on the alpha
are the only clue I have.
I'm a little out of my depth, so I do appreciate the help.
-- Bryan Medsker firstname.lastname@example.org
_______________________________________________ Axp-list mailing list Axpemail@example.com https://listman.redhat.com/mailman/listinfo/axp-list
This archive was generated by hypermail version 2a22 on Fri Sep 1 05:03:58 2000 PDT
Send any problems or questions about this archive to firstname.lastname@example.org.