Re: Accessing internet via cable modem

From: horsager(at)comcast(dot)net ("horsager)
Date: 01/21/04


Date: Tue, 20 Jan 2004 22:45:54 -0800

Chuck,

You are welcome to email me if you like.

Jeff

horsager(at)comcast(dot)net wrote:
> Chuck Leviton wrote:
>
>> Thanks for the reply. I have done as you suggested.
>>
>> "horsager(at)comcast(dot)net" <"horsager(at)comcast(dot)net"> wrote in
>> message news:9tednUOXLa5YJpHdRVn-jA@comcast.com...
>>
>>> Are you sure that you need to install drivers for your cards? Maybe
>>> your leaving some things out, but it seems like your making the whole
>>> process harder than it needs to be.
>>>
>>> 1. What is the output of ifconfig?
>>> (# ifconfig)
>>
>>
>>
>> ifconfig returns a bunch of information. I will try and reproduce it as
>> faithfully as I can
>> lo link encap:local loopback
>> inet addr:127.0.0.1 Mask:255.0.0.0
>> UP LOOBACK RUNNING MTU:3924 Metric:1
>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:0
>>
>
> That's the loopback interface. What you wanted to see are references to
> eth0 and eth1 (you said you had two cards installed). This, in itself,
> doesn't necessarily mean they aren't recognized.
>
> You are able to cut and paste output from the terminal, I feel for you
> if you entered the above by hand.
>
>>
>>> 2. Are the cards being recognized at boot?
>>> (# dmesg | grep eth)
>>
>>
>> I think the answer is no, this command returned nothing. I just ran
>> "dmesg"
>> by itself and the output's last line is
>> "Adding swap:.....". I think the eth0 would come after this, right?
>>
>
> The first command should have caught any references to ethernet cards if
> they were recognized at boot. Here is an example of what you're looking
> for (or some variation):
>
> e100: eth0: Intel(R) PRO/100 Network Connection
> e100: eth0 NIC Link is Up 100 Mbps Full duplex
>
> The e100 is the module and the eth0 is the nic. You say you're running
> RedHat? Have you tried to configure them through the gui tool?
>
>
>> So what do I need to do to make it recognise the cards? I had earlier
>> followed the instructions in the book on "Installing and setting Up a
>> network card" as follows
>> a) Start control panel,
>> b) launch kernel daemon configuration applet,
>> c) add a module of type eth
>> d) chose module of 3c509 for the 3Com card as I saw the following
>> information on the card viz. 3C509B-TP0
>> e) chose module of tulip for the LinkSys card (I think I saw that on the
>> Ethernet HOW-TO site)
>> f) restarted the kernel as per instructions. I got a message Starting
>> kerneld version 2.1.121 and nothing further happened after that
>> g) After some time I got fed up and rebooted
>>
>
> WTF? You can see if modules are loaded by running:
>
> # lsmod
>
> And insert them with:
>
> # modprobe <module-name>
>
> If you see no references to hardware in the tab of the gui tool, please
> post the output to the following commands:
>
> # lspci
>
> # lsmod
>
> And just for kicks:
>
> # cat /etc/modules.conf
>
> (remember, cut and paste)
>
>
> Jeff
>
>
>>> Try the above commands as root and post the output.
>>>
>>> Jeff
>>>
>>> charles leviton wrote:
>>>
>>>> Hi guys,
>>>> I have loaded RH 7.2 on my old HP Pavilion. Got it working as far as
>>>> desktop apps and so on. I want to connect to the web via my
>>>> RoadRunner. I did some looking around and it looks like
>>>> a) I need to enable ethernet connectivity on my PC
>>>> b) enable DHCP
>>>> c) connect to the modem.
>>>>
>>>> Is this OK?
>>>>
>>>> If so then I have 2 ethernet cards on my PC. One is a LinkSys that
>>>> was there already when I used to have Win 98 on this PC and other is a
>>>> 3Com card I just put in
>>>>
>>>> Q1) What is the procedure to install Linux drivers for these cards? I
>>>> have a book Mastering Red Hat Linux and all it says I have to "install
>>>> the hardware according to instructions that came with the card" But I
>>>> am woefully short of instructions and the "Ethernet How-to" is not
>>>> very clear about this
>>>>
>>>> Q2) After this do I have to do the kernel configurator deal of adding
>>>> eth0 and eth1?
>>>>
>>>> Q3 Is there anything special to do reg enabling ethernet connectivity
>>>> or is it just choosing that in the network configuration window?
>>>>
>>>> Q4) My modem is connected to a router to which I already have an XP
>>>> box connected. Do I need to do anything special 'cos I have a router
>>>> or can I connect the card to the router without any extra
>>>> configurations?
>>>>
>>>> I would like to say that I am not trying to take the easy way out
>>>> here, I have read lots of stuff online but I don't seem to have found
>>>> the right answers especially for Q1.
>>>>
>>>> Thanks
>>>
>>>
>>
>>
>



Relevant Pages

  • Re: Phils Test for the gospel standard of righteous judgement
    ... They are your instructions Jeff. ... 36 Did the word of God originate with you? ... let him acknowledge that what I am writing to you is the Lord's command. ... 15 And they said unto her, ...
    (uk.religion.christian)
  • ORIGINS 2006 Tournament Reports and Winning Decks [LONG]
    ... Rank Name PrelimGWs PrelimVPs FinalVPs TPs ... Deck Name: Lasombra Creation Boon ... This deck was directly inspired by Jeff "The Lasombra" ... Library: (90 cards) ...
    (rec.games.trading-cards.jyhad)
  • Re: Command Prompt
    ... Keep having fun, Jeff. ... MS-MVP Windows Shell/User ... 'xxxx' is not recognized as an internal or external command, ... comfortable ground using the command prompt way because that's how i did ...
    (microsoft.public.windowsxp.basics)
  • Re: Suggestions for X10/Automation Widgets
    ... X-Lock" by Jeff Mazur that was along the lines of what The Alien is ... It listened to the powerline and, when it heard an alien X-10 ... command, jammed it by corrupting the signal. ... You need physical control of a device to enroll ...
    (comp.home.automation)
  • Re: [BUG] 2.6.24 refuses to boot - ATA problem?
    ... ata1: soft resetting link ... Now Jeff, ... That argument causes the kernel to log this as its responding to that command: ...
    (Linux-Kernel)