RE: Network problems

Dmesg | more does not include a line referring to eth0

etc/modules.conf shows
alias eth0 3c523
But I put that in when I was messing around with linuxconfig.  There is
no alias available for US Robotics that I could find.
Below in quotes is the US Robotics installation information to use for
UNIX SCO version 5.  Maybe it would work for linux too.
"Installation Procedure
----------------------
1. Now login to UNIX system as supervisor (root) and enter the
Maintenance 
   mode.
   Note: Make sure that the current directory is "/" using UNIX command
-- pwd.

   Please follow the following steps to uncompress the package file:
   > cd /tmp 
   (and inserts the package floppy in the proper drive, i.e. a:)
      > doscp a:/SCO5/USR7900.sc5 ./VOL.000.000
   Now the installation directory is ready for use.

2. The following sections describe the configuration of the driver. It
is 
   suggested that you should perform these instructions in the
singler-user
   environment.
   Run "custom" utility and select the "Install new package" option.
      Select Media Type "Media Image" and type Image Directory "/tmp "

   It will prompt with "u79n Prototype Network Drivers (ver 1.0.0)"
 
   After running the custom utility and the new package is installed,
you 
   should use the "netconfig" command to add the driver into your system

   like the step 4 below.

3. Run "netconfig". Add the desired chain.

4. When the chain has been configured, select 'q' from the netconfig
menu. 
   and relink the kernel at the prompt.
   
5. To activate the adapter, you must reboot."

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Ajai Khattri
Sent: Monday, February 24, 2003 11:25 AM
To: [email protected]
Subject: Re: Network problems


On Mon, Feb 24, 2003 at 09:18:04AM -0800, Vaughn Warriner wrote:

> It is USR997900 according to the SKU tag or Mod - 7900 according to 
> the box it came it.
> 
> I think the problem may be with this old computer I have.  It is a 
> CompaQ Deskpro 6000.  I can't get into the BIOS for some reason and it

> looks like it has an RJ45 port on the back already, so there may be a 
> conflict.

First, see if your network card is detected. Look at the bootup
messages:

dmesg | more

if it is, you should be able to see what make and model it is.

If the Deskpro comes with its own NIC, then why do you need to install
another? FWIW, the original NIC on the Deskpro mobo is based on the TLAN
chipset which is supported by Linux. I did not find any useful info on
the USR997900 - maybe you can look at the card itself to see what
controller chip it uses? Then we can see if it is supported as well.

Look in /etc/modules.conf for a line containing "eth0" - what does it
say?

On one of my machines, I have an Intel EE Pro NIC installed, so mine
says:

alias eth0 eepro100

For a NIC using the ThunderLAN chipset, it would say something like:

alias eth0 tlan

BTW, as far as getting into the BIOS: if memory serves, a lot of
brand-name PCs throw up a graphical logo during the POST so you can't
see the BIOS messages. In most cases you can hit ESCAPE to switch back
to the text console and see those messages. It will also tell you how to
get in the BIOS settings, you will see something like:

Press DELETE for setup.

(Usually, on most PCs Ive seen, its usually F2 or DELETE).

-- 
.jA
repoleveD \ .nimdA smetsyS



_______________________________________________
Guinness-list mailing list
[email protected]
https://listman.redhat.com/mailman/listinfo/guinness-list