Click to See Complete Forum and Search --> : Cable Modem Problems


Kami_Diesel
07-20-2001, 05:21 PM
This is a kinda long story, but i installed linux mandrake 7.2 on my compaq presario (400 mhz AMD athlon). I used my better monitor which i use on another comp, so when i switched the monitors the settings where wrong and the monitor wouldnt display, so i reinstall linux (bad idea :() and by accident didnt click on the cable modem. Now when i try to get back online using my cable modem i cant :(. it looks for a dial up which i dont have. I tried to config using drakconf but it dosent seem to work or im not doing something right, does anyone know how to fix this or know somewhere to look, i tried the files on this site but none deal with cable modems :(

[ 20 July 2001: Message edited by: Kami_Diesel ]

bdg1983
07-20-2001, 07:31 PM
Probably the reason you haven't reveived a reply yet, is do to the amount of questions and responses to setting up cablemodems.

I'm sorry as it's been a long day at LNO, so unless someone responds to your question, I would suggest you search the forums for 'cablemodem' as I'm sure you will find enough prior posts to get it resolved.

Isn't there a NHF on Cablemodems? I'll have a look. Also the online documentation at www.linux-mandrake.com (http://www.linux-mandrake.com) should give you specific instructions.

honkeyman
07-20-2001, 07:51 PM
the problem is that amd never made the athlon at 400 mhz. They started at 500 or 550. That is the problem. Really. I am not sure about Mandrake but go into linuxconf command and modify your network settings there.

DMR
07-20-2001, 08:17 PM
Ouch and bummer. All you probably had to do for the monitor was to configure it using Xconfigurator.

The network card/cable modem setup issue has actually been discussed many, many times here. Try a Forum Search (http://www.linuxnewbie.org/cgi-bin/ubbcgi/ultimatebb.cgi?ubb=search) using keywords like "cable", "NIC", "DHCP", etc. to view past threads on the subject. The basic things that you need to do, most of which can be done through drakeconf/linuxconf/netconf, are:
- get your NIC recognized
- load the NIC's driver
- Configure for DHCP or, if you use static addressing, assign the relevant IP information (IP, netmask, gateway, DNS, etc.) provided by your ISP.

The one catch might be that, having not indicated a cable connection, the dhcp client may not have been installed.

The step-by-step instructions for all of this are a much longer story, so I'd suggest that you use the forum search for answers, then post back here with more specific info. Since I already had some of the generic basics written up: 1. Check the screen output at bootup. If the NIC is being properly initialized, you should see a line that says: "Bringing up eth0- O.K." If you see "failed" or "delaying" instead, you've got problems (see #3).

2. Assuming the NIC comes up, you can do the configuration with the graphical configuration tools linuxconf or netconf. Click on Basic host information->Adaptor 1. From there, select eth0 as the device, choose the correct module for your NIC from the drop-down list of kernel modules, and enable the device. Then either choose DHCP (if you're using it), or enter your IP information manually. After that, fill in your DNS and gateway/routing info under the appropriate sections.

3. If you get a failure on bootup, you may have a resource conflict with another device. Try turning off Plug-N-Play support in your BIOS, it can cause conflicts with some cards.

4. Log in as root, go to the command line or terminal window, and type "cat /proc/pci" and verify that your NIC is being recognized.
Type "cat /proc/interrupts" and make sure your NIC's IRQ isn't conflicting with another device. Type "cat /proc/ioports" and check the address ranges for conflicts. If you have resource conflicts, you can try rearranging the slot order of your PCI cards.

5. You can also verify the IRQ/address info by typing "ifconfig". There should be stats for the loopback device (lo) and eth0.

6. If you get card recognized, but the module isn't loading, try to load it manually by typing "insmod <your module's name>" or "modprobe <your module's name>". After that, type "lsmod" to list all loaded modules; the module should show up there.

7. You can then manually configure the NIC by typing "ifconfig eth0 xxx.xxx.xxx.xxx up", where xxx.xxx.xxx.xxx is your IP address.

8. Last, type "alias eth0 <your module's name>.

[ 20 July 2001: Message edited by: DMR ]