SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am new to Slackware, but I have been using Ubuntu for about 2 years now. I installed Slackware 13 about a week ago, and I have been struggling to get it on the internet. I have looked up many different posts on this site that are very similar to my problem.
For a little bit of info about my computer, I am running Slackware 13 64 bit with the 2.6.29.6 kernel. My motherboard is an ASUS PN5-D.
When i do an lspci -vv i get:
Code:
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
Subsystem: ASUSTeK Computer Inc. Device 8221
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0 (250ns min, 5000ns max)
Interrupt: pin A routed to IRQ 5
Region 0: Memory at fe02b000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at f200 [size=8]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
The slackbook said netconfig should automatically setup most of it, but it really doesnt seem to do anything. It changes what i have in /etc/rc.d/rc/inet1.conf, but it doesnt do the other things it says it should do like create an rc.netdevice file.
From what i've seen from other posts, it looks like i dont have the right module loaded. I have looked through the modules in /etc/rc.d/rc.modules, but none of them look like they are right for mine.
I am very interested in getting this up and running, and appreciate any help I can get.
How did you search the kernel modules for the driver?
Code:
find /lib/modules -iname "mcp"
If this does not lead to success there might be the chance that the modules are not compiled within your actual kernel. But before doing this see if lspci gives other names to look for inside the modules dir.
See if you can find the driver when you configure a new/old kernel.
Nother way to get some names for your nic is by skimming through dmesg
Code:
dmesg | less
Just a hint. Maybe it might be worth to get used to the ip command its the next generation tool to fiddle with network options
Wow that was a quick reply. The drivers that are on the ASUS website have a part with linux drivers, but the names are all short abbreviations, I don't know which one would work with slackware.
The only thing that i keep seeing over again in dmesg and lspci is MCP51, but I don't know if it is the module name. That seems to be the big problem right now... trying to figure out the name of it.
The linux drivers download from ASUS are named: Fedora6, RHEL3_U7, RHEL3_U8, RHEL4_U4, RHEL4_U5, RHEL5, SLES10, SuSE10.2.
SLES10 looks like it could be the closest, but I just don't know. When i compiled my kernel I looked into the network modules part and looked through everything I could find in there, but nothing was close to anything with mine.
This is supported by the forcedeth kernel module which is available in Slackware 13.
The OP also posted output from ifconfig:
Quote:
inet addr:127.0.0.1 Mask:255.0.0.0
Those settings are for the local host, which will not work for internet connection.
To the OP,
What settings did you use when running Ubuntu? Use the netconfig tool and use the settings that worked previously.
I asked for the lsmod AFTER running netconfig. (netconfig may have been skipped during install. Wouldn't be the first time. I've done it myself)
And, yes, I know what modules SHOULD be installed. (Same chipset on this mobo)
I was asking for the OP to:
DO THINGS IN ORDER.
Skipping around can just cause confusion. ("My new DVD movie doesn't work"..."Did you look at frame 45678?"..."Plug it into a HDTV..."..."Did you replace the cables?"..."What Hz in your line?"...)
When the issue COULD be..."Did you plug it in?"
So we'll start with running netconfig, and we'll go from there.
Last edited by cwwilson721; 12-15-2009 at 07:45 AM.
Well first off when I installed Slackware 13 originally i followed the instructions EXACTLY out of the slackbook. It makes
Code:
netconfig
look like it actually does something... You can only enter the hostname and domain name there, and is supposed to auto-find the correct module for it. It doesnt do that on mine.
This is really fun having to copy all my outputs from my computer to this crappy laptop without using the internet, but here is my output from lspci:
and sadly this is all that comes up when i run lsmod:
Code:
Module Size Used by
Like I said, I was following the instructions in the slackbook until this point. When netconfig didn't autofind it, it said to make sure that the module you are using is in your kernel, and that's exactly where I am stuck right now.
When I used Ubuntu the internet always works right out of the box, so I haven't had to mess with it very much.
The domain name line that you have to enter in netconfig confuses me too, because our router uses DHCP and when I look up what our domain name is it is blank.
Is it possible that for some reason (crappy linksys router) that you aren't getting a dhcp offer from the dhcp server? Have you tried to run netconfig and use a static ip (that won't conflict with other clients on the network)? Also, what is the output of ifconfig after running netconfig?
edit: Just to cover all the bases, we'll follow cwwilson721's line of thinking. Is the network cable good, plugged in, etc....?
edit2: Are you using the huge kernel? If so, try using the generic with an initrd.
Last edited by manwichmakesameal; 12-15-2009 at 12:15 PM.
Yes it's plugged in, don't be silly :P. I guess I also forgot to mention that i multi boot Ubuntu 9.10 and Windows XP on the computer as well, and there are no networking issues at all.
Setting up netconfig with the exact ip and everything that is assigned to me automatically on ubuntu or windows wont work here either. Neither will a different ip that my router isn't using. Also I get the same output from ifconfig that i posted above, even after running netconfig.
When allend replied he mentioned that my motherboard should be using the forcedeth module. I don;t have it on my computer that I can tell, i tried recompiling my kernel and looking for it. I found only one that that could have been close and it was in the lan 10-100mb section of the network drivers. It was already included though, but wasn't directly called forcedeth. It was an nVidia driver, the only time it was mentioned in all of the kernel setup.
How can I get the forcedeth module on my computer?
-edit Nevermind, I have it on there now. Now the next problem, i can't get my ethernet card to use forcedeth.
Does nothing, if that's what you were asking me to do.
And i just compiled the 2.6.29.6 kernel like it says to do in the slackbook, so I'd think it would be the generic one, wouldn't it? Should I be running the huge.s kernel to do this or what?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.