[tulip] Newbie Alert - Linksys/Network Everywhere NC100 - Help!
tempest_skye
tempest_skye@hotmail.com
Thu, 8 Jun 2000 19:18:16 -0400
This is a multi-part message in MIME format.
------=_NextPart_000_000D_01BFD17E.4C7B59A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I have Linux Mandrake 6.5 installed and it automatically detected the =
driver as being tulip compatible.
I'm connected to the Internet via a cablemodem.
I'm using the KDE interface (which might be why I can't seem to solve =
this problem). I'm growing more familiar with the command line =
interface, so I have no problems compiling drivers if I get complete =
instructions.
In Linxconf | Network, my settings are as follows:
Main tab:
host: skye
Adapter 1 tab:
(manual configuration)
primary + domain: skye.gw.total-web.net
IP address: (the one the cable company assigned me)
Subnet Mask: 255.255.255.0
port?: eth0
driver: tulip
I've even put in the values for the DNS server and gateway. (Tried =
setting the optional IRQ port too, to no avail.)
When Linux first boots up, all the processes pop up as being OK (unlike =
when I fiddle with what driver it uses, then eth0 comes up as failed). =
But as soon as it passes the eth0 initialization, my cable modem LNK =
light & activity lights die - basically leaving PWR and RF (cablemodem =
to network connection) lights on.
I can ping myself: localhost, loopback, and assigned IP address.=20
I've checked around and many things are saying I might need to compile a =
new version of tulip - BUT this is a very recent version of Linux - even =
before I got the network cards. (I know, that doesn't really count for =
much....)
Help! (Oh someone tell me I can use another driver on my list! *lazy =
grin*)
What can I do to determine exactly where the connection dies out between =
Linux, the NIC, and the cablemodem? Any diagnostic programs out there? =
Anyone else had this problem before? =20
Oh, and I'm on a COMPAQ Presario 450MHz PC - but the NIC wasn't with the =
unit when I bought it. My Windows98 setup works fine. No problems with =
the NIC there.
Thanks!
tempest_skye
newbie-to-linux-geekette ;)
------=_NextPart_000_000D_01BFD17E.4C7B59A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I have Linux Mandrake 6.5 installed and =
it=20
automatically detected the driver as being tulip =
compatible.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I'm connected to the Internet via a=20
cablemodem.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I'm using the KDE interface (which =
might be why I=20
can't seem to solve this problem). I'm growing more familiar with =
the=20
command line interface, so I have no problems compiling drivers if I get =
complete instructions.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>In Linxconf | Network, my settings are =
as=20
follows:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Main tab:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>host: skye</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Adapter 1 tab:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>(manual configuration)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>primary + domain: =20
skye.gw.total-web.net</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>IP address: (the one the cable company =
assigned=20
me)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Subnet Mask: 255.255.255.0</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>port?: =
eth0</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>driver: =
tulip</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I've even put in the values for the DNS =
server and=20
gateway. (Tried setting the optional IRQ port too, to no=20
avail.)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>When Linux first boots up, all the =
processes pop up=20
as being OK (unlike when I fiddle with what driver it uses, then eth0 =
comes up=20
as failed). But as soon as it passes the eth0 initialization, my =
cable=20
modem LNK light & activity lights die - basically leaving PWR and RF =
(cablemodem to network connection) lights on.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I can ping myself: localhost, =
loopback, and=20
assigned IP address. </FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I've checked around and many things are =
saying I=20
might need to compile a new version of tulip - BUT this is a very recent =
version=20
of Linux - even before I got the network cards. (I know, that =
doesn't=20
really count for much....)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Help! (Oh someone tell me I can =
use another=20
driver on my list! *lazy grin*)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>What can I do to determine exactly =
where the=20
connection dies out between Linux, the NIC, and the cablemodem? =
Any=20
diagnostic programs out there? Anyone else had this=20
problem before? </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Oh, and I'm on a COMPAQ Presario 450MHz =
PC - but=20
the NIC wasn't with the unit when I bought it. My Windows98 setup =
works=20
fine. No problems with the NIC there.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanks!</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>tempest_skye</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>newbie-to-linux-geekette =
;)</FONT></DIV>
<DIV> </DIV></BODY></HTML>
------=_NextPart_000_000D_01BFD17E.4C7B59A0--