Re: [cobalt-users] Re: [qube-users] [Qube2] Dies...

[Mike Vanecek <nospam99@xxxxxxxxxxxx>]

On Thu, 15 Jun 2000 17:00:36 -0400, "Gerald Waugh" <gerald@xxxxxxxxx> wrote:

:>> BTW, the CD instructions do not say which interface to use, I am assuming on
:>> uses the primary interface?
:>
:>used eth0 on a RaQ2, I have never restored a Qube2, although I do have one!
:>I just checked the Qube2 and eth0 is the primary interface, so I would say that
:>is the one to use.

The primary is eth0 on the Qube2.

:>> So now I will go buy a Netgear FA310TX ethernet card (Tulip 21143-based)?? and
:>> an RJ45 Crossover cable to put in my PC while using the CD (certainly do not
:>> intend to totally change out my Win2K setup just to get the Qube2 to work). It
:>> is only $22 so big deal.
:>
:>I think all the Netgear FA310-TX are tulip-21143 based, I think Cobalt says that
:>to distinguish
:>the driver from the generic 'tulip driver' "Lite-ON".
:>I would download the latest 'tulip' driver from
:>http://www.netgear.com/support/support.shtml
:>Somewhere I read that the 'public-domain' tulip driver that comes with most
:>linux distros will not

I bought exactly what is specified in the CD Restore manual, Netgear FA310-TX
Tulip-21143. Since it is listed as 1 of 4 that are suppose to work, then I am
assuming it is not the same as the generic mentioned below that does not work.


:>work properly. I used the driver from netgear, not the driver supplied with my
:>RH-6.1 system, I wrote the new
:>driver over the RH tulip.o file.
:>Best Wishes!

Uhm, I have no way to do that since I am booting off of the Restore CD and it
does not give me the option to load any drivers. Also, I have my hard disks
disconnected anyway.

As it stands now, the CD Restore system is sitting at Loading initrd.img ....
and the Qube2 is sitting at Net booting. The green lights on both cards are on
and I have seen them shake hands. However, nothing else happens. 

Supposedly, tech support is going to call be today to assist, but I am not
counting on it. If not, I think I will just bring up Win2K server and at least
get back on line. Very frustrating.