Using a Shuttle nForce2 mobo on SuSE 9.0, can't connect to 'net using DSL router.
 

I have recently subscribed to my local DSL service. However, I have done pretty much as far as my capability reaches (I'm a SuSE Linux Newb), with regards to hooking up my box to the net. I have a Shuttle mobo, mod. AN35N-Ultra, w/ nForce 2 chipset, 10/100 ethernet on-board LAN. Linux OS I'm using is Suse 9.0.

I know my router is working fine, and my computer recognizes the on-board LAN, but I can't hook-up to the damn 'net. The DSL service provider doesn't support Linux, so they can't help me in the instillation, but they said that ANY OS/platform should be able to dial-in. I've tried YaST install for my DSL service and net-card config, so far, the computer recognizes that I have a distinct ethernet card specific to the system, but YaST installer doesn't recognize it. Also, YaST can't seem to know if I am connected or whatever; it can't tell me if I'm even able to connect. Kinternet is not working for me.

Also, the DSL providers said that I need to hook-up to the net first, so that I could get my login and pass setup, but again, YaST installation asks for a login and pass to hook-up the DSL. So I am in a friggin' catch-22; need to login to the service to setup DSL account, but because of software needing login and pass to hook-up to the service...arrgh!


So any input upon this quandary I am having would be GREATLY appreciated. Thanks!

:scratch:

I had some problems with suse myself,I have dsl with a modem which uses DHCP.Just try to go to network card and configure that and then DHCP,every time I used dsl it would not work,I think I used modem,also if you have knoppix boot that and if it works,see how it set it up,as I understand it my isp programs this modem for this address,I never need to log in,as it is allways on,good luck,david

Thanks, I'll try that, and see if it works. I can't wait to go online and play UT2K4!

Hoping it all ends well...and thanks.

http://forums.suselinuxsupport.de/in...t=ST&f=5&t=303 check this out and and who is your provider and what kind of router and how are you connected ect.ect. the more information you give then someone most likely can get you going,david

It seems that my solution lies in the utilization of the tool 'forcedeth' How do I go on in using this?

I just googled it and there is a ton of imformation ,must be common,again good luck,david

I also have a Shuttle and I think I know what the problem is -- the necessary kernel modules to support the nForce2 chipset are not built into the default kernel. (nVidia uses proprietary drivers which are not GPS'd, and Suse therefore does not include them in their distros. If you want them, you need to d/l them from nVidia and install them manually.) Anyway forcedeth is reverse-engineered hack (in the good sense of the word) of the nForce module, and it is built into the latest release of the 2.6 kernel. You therefore have several choices:

1. Install the latest stable 2.6 kernel, making sure that the forcedeth module is compiled into the kernel or at least built as a module. (If you go with the module route, you will need to manually load it using the "insmod" command as root.) Compiling a kernel may be daunting for a newbie but check out a thread here at LQ by DaOne regarding how to compile a kernel -- it's a goldmine of info.

2. Download the drivers from nVidia and install them manually. http://www.nvidia.com/object/linux_nforce_1.0-0261.html

2. Abandon the built in LAN and install a NIC that actually is supported by the existing Suse installation. This is what I ended up doing, mainly because it's easier and faster for me to spend $15 on a NIC than it is to spend hours of time downloading stuff and configuring it. It's a shame to waste one of the two PCI slots, but if it's going unused anyway it doesn't hurt.

Bottom line - your machine and installation are basically OK - this is just due to a conflict with the onboard chipset. Good luck with it. -- J.W.