I reinstalled Redhat 7.1 on my computer at school and I am unable to connect to the internet. I have only been using Linux for about 7-8 months and I am still a novice. When I was using Redhat 7.1 last spring, it worked fine. I am using a 3com Etherlink card (the driver is 3c905c-tx in windows) and my computer seems to detect it correctly. However, it is using the 3com59* driver. I tried to switch to the driver to 3com90*, but my computer stopped recognizing the card so I doubt it is a driver problem. (Plus, it was using the same driver last spring.) I also tried pump -i eth0 and it failed. Also, I entered an IP hoping that it would pick something up but that does not work either. Does anyone know what could be done to resolve the problem or at least direct me somewhere. Thanks, Eric
On Mon, 10 Sep 2001, Eric Frederick wrote: EF>I reinstalled Redhat 7.1 on my computer at school and I am unable to EF>connect to the internet. I have only been using Linux for about 7-8 EF>months and I am still a novice. When I was using Redhat 7.1 last EF>spring, it worked fine. what happened between then and now? new hard drive? (just curious; i'm of the If-it-ain't-broke-don't-fix-it school... <g>) EF>I am using a 3com Etherlink card (the driver EF>is 3c905c-tx in windows) and my computer seems to detect it correctly. you know this from the boot up screen? EF>However, it is using the 3com59* driver. I tried to switch to the EF>driver to 3com90*, but my computer stopped recognizing the card so I EF>doubt it is a driver problem. (Plus, it was using the same driver last EF>spring.) how were you doing this? usually, all you should need to do is re-compile the kernel if support for your Network Interface Card (NIC) isn't there already. EF>I also tried pump -i eth0 and it failed. i'm not familiar with "pump"... does it have something to do with DHCP? EF>Also, I entered an IP hoping that it would pick something up but that EF>does not work either. generally, you can't just "assign" an IP address, unless it's for your own LAN. if you're connecting that system to a LAN AND a dial-up, then you need to be careful that your network address isn't something that technically belongs to someone else. (for example, it might be nice to have a LAN at home with 18.100.x.x, but i'll bet MIT would have something to say to you if you tried to connect that to the 'Net...) for private networks, there are a few generally accepted networks that work out, since they are Officially Unassigned. try something in the 192.168.x.x range. if the LAN and the Dial Up are on the same machine, there might be a routing issue on the local box. EF>Does anyone know what could be done to resolve the problem or EF>at least direct me somewhere. worst-case, you could always try checking the wire to make sure that it's connected securely. you'd be surprised how many times i've found that to be a problem. <sigh> ;) hope this helps... -- William Smith wsmith@chezsmith.com Fall River, MA http://www.chezsmith.com
EF>I reinstalled Redhat 7.1 on my computer at school and I am unable to EF>connect to the internet. I have only been using Linux for about 7-8 EF>months and I am still a novice. When I was using Redhat 7.1 last EF>spring, it worked fine.
WS>what happened between then and now? new hard drive? (just curious; i'm WS>of the If-it-ain't-broke-don't-fix-it school... <g>)
I updated the system using Redhat's upgrade system and I recieved errors messages > and things stopped working. Since I had no clue how to fix it, I said forget it.
EF>I am using a 3com Etherlink card (the driver EF>is 3c905c-tx in windows) and my computer seems to detect it correctly.
WS>you know this from the boot up screen?
I got the information about the NIC by using the command "ifconfig eth0." The command displays the driver installed for the device.
EF>However, it is using the 3com59* driver. I tried to switch to the EF>driver to 3com90*, but my computer stopped recognizing the card so I EF>doubt it is a driver problem. (Plus, it was using the same driver last EF>spring.)
WS>how were you doing this? usually, all you should need to do is re-compile WS>the kernel if support for your Network Interface Card (NIC) isn't there WS>already.
Since I have no clue about recompiling the kernel, I made the changes using linuxconf. It is a GUI program that is supposed to reconfigure things for you.
EF>I also tried pump -i eth0 and it failed.
WS>i'm not familiar with "pump"... does it have something to do with DHCP?
EF>I reinstalled Redhat 7.1 on my computer at school and I am unable to EF>connect to the internet. I have only been using Linux for about 7-8 EF>months and I am still a novice. When I was using Redhat 7.1 last EF>spring, it worked fine.
WS>what happened between then and now? new hard drive? (just curious; i'm WS>of the If-it-ain't-broke-don't-fix-it school... <g>)
I updated the system using Redhat's upgrade system and I recieved errors messages > and things stopped working. Since I had no clue how to fix it, I said forget it.
EF>I am using a 3com Etherlink card (the driver EF>is 3c905c-tx in windows) and my computer seems to detect it correctly.
WS>you know this from the boot up screen?
I got the information about the NIC by using the command "ifconfig eth0." The command displays the driver installed for the device.
EF>However, it is using the 3com59* driver. I tried to switch to
EF>driver to 3com90*, but my computer stopped recognizing the card so I EF>doubt it is a driver problem. (Plus, it was using the same driver last EF>spring.)
WS>how were you doing this? usually, all you should need to do is re-compile WS>the kernel if support for your Network Interface Card (NIC) isn't
WS>already.
Since I have no clue about recompiling the kernel, I made the changes using linuxconf. It is a GUI program that is supposed to reconfigure things for you.
EF>I also tried pump -i eth0 and it failed.
WS>i'm not familiar with "pump"... does it have something to do with DHCP?
From what I understand, pump a the program that works with DHCP to get IP addresses. I am using the DHCP client rather than BOOTP (something
that.) since that is what I am supposed to use.
EF>Also, I entered an IP hoping that it would pick something up but
EF>does not work either.
WS>generally, you can't just "assign" an IP address, unless it's for your own WS>LAN. if you're connecting that system to a LAN AND a dial-up,
WS>need to be careful that your network address isn't something that WS>technically belongs to someone else. (for example, it might be nice to WS>have a LAN at home with 18.100.x.x, but i'll bet MIT would have something WS>to say to you if you tried to connect that to the 'Net...) WS>for private networks, there are a few generally accepted networks
WS>work out, since they are Officially Unassigned. try something in
WS>192.168.x.x range. if the LAN and the Dial Up are on the same machine, WS>there might be a routing issue on the local box.
The IP address was for my LAN at school. The network officials recommended that I take this action to resolve the problem. Also, they told me
they know hardly anything about Linux so I am not about to ask them for more help.
EF>Does anyone know what could be done to resolve the problem or EF>at least direct me somewhere.
WS>worst-case, you could always try checking the wire to make sure
it's
WS>connected securely. you'd be surprised how many times i've found
to
WS>be a problem. <sigh> ;)
The NIC works on my DOS drive so I doubt that it is a problem. :) However, could this problem occur if I let the Redhat install program reformat
i thought the fact that my 3com nic [a 3c905] was odd in the fact it was using the module 3c59* until i looked for the driver via google and looked at the doc's on it in the kernel help page ... the module that is called 3c59* supports all of these nics: x "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) x "Boomerang" (EtherLink XL 3c900 or 3c905) x "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) x "Tornado" (3c905) x "Hurricane" (3c555/3cSOHO) ... the original driver was meant for the 3c59* nic's, but the original coder found that other, similar 3com nic's had no linux support, so he added in a bunch of 3c90* nic's to his module, but retained the original name. thus, keep the 3c59* module and dont change it, when i forced usage of 3c90*, it broke my nic [i.e. it didnt work], but the 3c59* worked fine -mike ----- Original Message ----- From: "Eric Frederick" <efreder1@hotmail.com> To: <wlug@mail.wlug.org> Sent: Thursday, September 13, 2001 02:55 AM Subject: Re: [Wlug] Unable to obtain an IP the there like that then you that the that that that the
drive for me? Should I format the drive myself and then reinstall and see if the problem is resolved?
WS>hope this helps...
Thank you very much for the advice. I know I should learn to fix the system rather than format it, but it is hard for me to do that while I am at school. I have very little time to learn Linux, but I like Linux much better than Windows and I am trying to convert. I have learned not to upgrade until I know more about the OS and how to fix it. :-)
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
participants (3)
-
Eric Frederick -
Mike Frysinger -
William Smith