feeling a bit like a schitzophrenic here talking to myself... just
wanted to let you know I solved the problem... by getting the person
at the remote site to go to the computer shop downstairs with a
printout of the tier 1 compatable hardware from the redhat site, and
buy one of the cards listed there.
he ended up getting a Netgear FA-310-TX which was installed in 2
minutes, the NE2000 pulled out (and now sitting in the bin) and
booted the machine - I logged in over the ppp connection, changed the
conf.modules to reflect that the card was now wanting the tulip
driver instead of the ne module, changed the options to debug=1 (just
incase! ;) and brought up the interface - and well - eveything works
smooth and happy - even rebooted to make sure and all is 100% now...
anyway - just letting y'all know it wasn't a config problem - but a
HW one... which seems to have arisen coincidentally when upgrading
linuxconf?
- dan.
At 1:46 PM +1100 31/8/00, Dan Horth wrote:
>Having announced last night that I had fixed the problem I now have
>to reply to one of my postings once again to announce that the
>problem is there - bigger and badder than ever... actually it's a
>different problem now...
>
>basically I can get the interface recognised but it's not receiving
>or transmitting anything as far as I can tell - basically the
>network segment it's serving is pretty dead as far as the clients
>are concerned. Following are some diagnostic type things that may
>help....
<SNIP>
--
Nitro - 3D Visualisation, Graphics & Animation
Ph (+61 2) 9810 5177 - Fx (+61 2) 9810 0199
http://www.nitro.com.au/
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
