LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-11-2004, 02:57 AM   #1
zeekx4
LQ Newbie
 
Registered: Oct 2004
Posts: 18

Rep: Reputation: 0
Modprobe 8139too


I just upgarded to Slackware 10.0 and went to start my normal routine of getting the network to work. I always forget what I do, so I always start from ground zero. This time around though, the problem arises when I try to load the modules for my card. It's model is DFE-530TX+ which has worked before with the 8139too module. I run modprobe 8139too and get nothing. 8139cp is loaded, but it displays errors.

I can't get 8139cp to unload and I can't get 8139too to load, is there something I'm missing? If I have to, I'll figure out how to rebuild the kernel with 8139too incorporated, but I'm new and would rather play around before I get to the dirty stuff.
 
Old 12-11-2004, 03:17 AM   #2
nixcraft
Member
 
Registered: Nov 2004
Location: BIOS
Distribution: RHEL3.0, FreeBSD 5.x, Debian 3.x, Soaris x86 v10
Posts: 379

Rep: Reputation: 30
Here are commands to use:

lsmod : list all loaded modules.

rmmod <module> : remove a module from the Kernel

rmmod -f <module> : remove a module from the Linux Kernel forcefully. Note if above command does not work then use this command.

depmod : creates a list of module dependencies.

more /etc/modules.conf : Config file for modules. You may need to edit this file.

And make sure you compile NIC module in kernel. Try following to see if driver compiled or not

grep "DRIVER_NAME" /path/to/kernel/source/.config

Hope this helps.
 
Old 12-11-2004, 05:55 AM   #3
gbonvehi
Senior Member
 
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145

Rep: Reputation: 51
You could add 8139cp in /etc/hotplug/blacklist to avoid it being loaded by hotplug and add a line to modprobe it in /etc/modules.conf (nixcraft was refering to this too )
 
Old 12-13-2004, 08:55 PM   #4
zeekx4
LQ Newbie
 
Registered: Oct 2004
Posts: 18

Original Poster
Rep: Reputation: 0
okay, my mistake. It wasn't loading 8139cp, it was displaying error messages. 8139too is loaded and running fine, but it still wont get the address through DHCP.

Just to see if something was weird with my hardware, I booted up DSL and looked at the lsmod. Everythings the same, but DSL got the IP address and slackware doesn't. Any suggestions? cause I've got nothing.

P.S. this wasn't a problem with slack 9.1, so I'll probably end up going back to that
 
Old 12-14-2004, 03:18 AM   #5
Ipolit
Member
 
Registered: Nov 2003
Location: Bulgaria
Distribution: Vector Linux, Morphix
Posts: 316

Rep: Reputation: 33
try this
ifconfig eth0 down
ifconfig eth0 up
dhcpcd
if works check /etc/rc.d/rc.inet1
do you have uncommented line
dhcp=yes
and commented lines with IPADDR, NETMASK, NETWORK, BROADCAST
 
Old 01-10-2005, 03:28 AM   #6
tudo
LQ Newbie
 
Registered: Mar 2003
Location: Romania
Distribution: mandrake
Posts: 4

Rep: Reputation: 0
Hi,

I also have problems getting 8139too working with dhcp... (also, after an upgrade from mdk 10.0 to mdk 10.1, that got me 2.6.8.1 kernel...; and the network card worked before...)

From what I saw in the logs, there is an error regarding the hardware adddres: "unknown hardware address 776" (this is comes from dhcpd:sid0 (donno what sid0 is...))

I suspect I missed some config related for the kernel because:
- I have the same error when I try installing gentoo (which also uses kernel 2.6.8)
- the card worked before, I managed to configure it with a static IP and responded to echo request, however, the net was still down
- ethtool shows everything is ok, settings detected correctly, link detected...
- there is an error complaining about a function not being implemented (SIOCSIFFLAGS - or something like that - function not implemented) that is being logged in 2.6.8 but not in 2.4.7 (however, when I booted with 2.4.7 kernel the dhcp negotiation still failed because my card did not work correctly; the dhcp server is up and runnig ok for about 40-50 machines...)
- I found some other pages related to problems about 8139too and >2.6.8 kernels (but they were in german... :-) )

Does any body know anything about this ? It's unlikelly that 8139too was bugged somewhere around 2.6.8 but something is changed and I did not found a solution....

Regards,
tudo
 
Old 01-10-2005, 05:46 PM   #7
zeekx4
LQ Newbie
 
Registered: Oct 2004
Posts: 18

Original Poster
Rep: Reputation: 0
My problem wasn't related the module (even though I thought it was). It was related to Slack 10 thinking that I had a wireless card. I made rc.wireless unreadable and that took care of my problem.

Don't know what to tell you with your situation. I'd try a different (cheap) network card and see if that worked before I dug around too much. No use making life harder than it is.
 
Old 01-11-2005, 02:41 AM   #8
tudo
LQ Newbie
 
Registered: Mar 2003
Location: Romania
Distribution: mandrake
Posts: 4

Rep: Reputation: 0
Yeah... we think alike :-)
This is the same thing I was thinking about...
However, just in case I solve the problem afterwards, I will post here the details...


Regards,
tudo
 
Old 01-11-2005, 07:08 AM   #9
trigggl
Member
 
Registered: Dec 2004
Location: Jacksonville, AR
Distribution: Debian Etch, AIX, Slackware
Posts: 117

Rep: Reputation: 15
I have that card and have never had a problem. Here is what my "lsmod" showed:

8139too 14376 1
mii 2272 0 [8139too]
crc32 2880 0 [8139too]
 
Old 01-12-2005, 03:09 AM   #10
tudo
LQ Newbie
 
Registered: Mar 2003
Location: Romania
Distribution: mandrake
Posts: 4

Rep: Reputation: 0
Hi,

I strongly think there is something wrong with the kernel 2.6.8.1 configurations that I have (on a gentoo live cd and on mandrake 10.1 - either one cannot get the ethernet up)... because I tested another netcard (that uses the tulip module) and I have the same results (i.e. the net is still down)

Does anyone know anything about the log messages mentioned above ("unkown hardware address" and "SIOCSIFFLAGS: function not implemented" that came when trying to ifup eth0 ?)


Regards,
tudo

P.S. sorry about discussing this on the slackware forum, but this is where I found the thread about 8139too)
 
Old 01-12-2005, 08:51 AM   #11
brancalessio
LQ Newbie
 
Registered: Aug 2004
Posts: 22

Rep: Reputation: 0
Re: Modprobe 8139too

You can try this way.

Put the module you don't want to loaded in /etc/hotplug/blacklist, then reboot your computer and look with lsmod for the loaded modules. If the other module is loaded, use netconfig. If it is not use modprobe to load it and then netconfig.

Hope it helps...

Quote:
Originally posted by zeekx4
I just upgarded to Slackware 10.0 and went to start my normal routine of getting the network to work. I always forget what I do, so I always start from ground zero. This time around though, the problem arises when I try to load the modules for my card. It's model is DFE-530TX+ which has worked before with the 8139too module. I run modprobe 8139too and get nothing. 8139cp is loaded, but it displays errors.

I can't get 8139cp to unload and I can't get 8139too to load, is there something I'm missing? If I have to, I'll figure out how to rebuild the kernel with 8139too incorporated, but I'm new and would rather play around before I get to the dirty stuff.
 
Old 01-12-2005, 09:05 AM   #12
trigggl
Member
 
Registered: Dec 2004
Location: Jacksonville, AR
Distribution: Debian Etch, AIX, Slackware
Posts: 117

Rep: Reputation: 15
Quote:
Originally posted by zeekx4
okay, my mistake. It wasn't loading 8139cp, it was displaying error messages. 8139too is loaded and running fine, but it still wont get the address through DHCP.

Just to see if something was weird with my hardware, I booted up DSL and looked at the lsmod. Everythings the same, but DSL got the IP address and slackware doesn't. Any suggestions? cause I've got nothing.

P.S. this wasn't a problem with slack 9.1, so I'll probably end up going back to that
Now that I think about it, I probably don't use DHCP on my ethernet card. Since there's only one connection, I just specify its address myself. I don't like using DHCP when I don't have to.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Making modprobe pcspkr stick with modprobe.preload? gm4jjj Fedora 3 06-16-2004 04:27 AM
8139too problem in 2.4.20-8 nikhil93 Linux - Networking 6 01-12-2004 06:39 PM
modprobe: modprobe: Couldn't locate module nvnet.o/nvaudio.o xiojqwnko Linux - Newbie 2 12-08-2003 06:41 PM
modprobe: modprobe can't locate module ppp0 in redhat 7.1 while shutting down. cyberdude3k Linux - Networking 1 09-08-2003 01:01 PM
Error with 'modprobe 8139too' Rum Linux - General 7 03-25-2003 06:31 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:35 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration