I am still around, still going mad, and still wondering what is causing
me all this grief.
As one part of the investigation, I tried to boot my PC164 without
a disk controller, but with a network card installed. Using the
PC164 kernel from ftp.digital.com, I can boot the redhat3.0.3 ramdisk
and get to a shell prompt.
I can then type "ifconfig lo" and get the loopback interface. I can
even "up" the loopback interface. "ifconfig eth0" will give me the
correct hardware address of my ethernet card.
However, doing "ifconfig eth0 192.32.242.21" will immediately hang the
machine, hard. Not even console switching works anymore.
Is it suppposed to do that? Is that caused by the combination of 1.3.xx
networking user programs (from redhat) and the 2.0.10 kernel? Or is this
just another manifestation of a hardware problem?
The network card in question is a noname-PCI NE2000 clone; Actually,
there is two of them (one of which has worked flawlessly in the Pentium
for the last 6 months or so), from different vendors, but with the exact
same reaction to "ifconfig".
Any ideas? Anything I should try out?
Thanks,
Bernie
P.S.: If I ever get this thing going, I promise I will do something really
nice for linux/AXP. I don't know what, yet, but I will find something ;-/
-- To unsubscribe: mail -s unsubscribe axp-list-request@redhat.com < /dev/null
Copyright © 1995-1997 Red Hat Software. Legal notices