Click to See Complete Forum and Search --> : Gentoo Linux: Problems with modules
mreiland
07-06-2003, 07:39 AM
Alright, I've recently installed Gentoo Linux, but I can't seem to get my NIC working properly. the problem is that the module seems to be having problems. I've done a insmod on it, and it starts giving me undefined reference errors.
I have a DFE 530-TX+, and it uses the 8139too module. It works just fine with the liveCD, but I can't get it to work under my Gentoo install.
Ultimately what I need to do is find the drives, compile them as a module, and then insert them. I've never done this before, and I'd appreciate any help in doing this. I've googled around for tutorials on the subject, but I don't seem to be finding much.
The 8139too module can be installed at the time of the kernel config(via menuconfig), but it's obviously not working, and I don't know why. I've even gone so far as to try and compile it into the kernel, and it still won't work. If anyone can explain to me why, I'd be grateful.
I'm using the gentoo-sources to compile. If I can't get this figured out, I guess I'll try the vanilla sources, but I really didn't want to have to do that.
I'd <b>really</b> appreciate it if someone would help me on this, maybe even a bit of one on one advice. I'm using this as an excuse to really get into the guts of Linux, and I could definately use it. If anyone's interested, let me know, and I'll post an email addy that you can get ahold of me in.
mdwatts
07-06-2003, 08:10 AM
Ensure you have PnP OS disabled in the bios.
See if these JL forum search results for '8139too' (http://justlinux.com/forum/search.php?s=&action=showresults&searchid=662010&sortby=lastpost&sortorder=descending) help as some should have suggestions on how to load the module and what to check if further problems.
I just got Gentoo up and running too. I have a built in Realtek 8100 ethernet adapter which uses the 8139too driver, here's the relevent part of my /usr/src/linux/.config:
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_SUNLANCE is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNBMAC is not set
# CONFIG_SUNQE is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_APRICOT is not set
# CONFIG_NET_BCM4400 is not set
# CONFIG_CS89x0 is not set
# CONFIG_TULIP is not set
# CONFIG_DE4X5 is not set
# CONFIG_DGRS is not set
# CONFIG_DM9102 is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_LNE390 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_NE3210 is not set
# CONFIG_ES3210 is not set
# CONFIG_8139CP is not set
CONFIG_8139TOO=y
# CONFIG_8139TOO_PIO is not set
CONFIG_8139TOO_TUNE_TWISTER=y
CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_SUNDANCE_MMIO is not set
# CONFIG_TLAN is not set
# CONFIG_TC35815 is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_VIA_RHINE_MMIO is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_NET_POCKET is not set
I'm not certain it's strictly necessary to build those into the kernel as opposed to building them as modules, but it does save having to edit /etc/modules.autoload. Not that it's all that difficult, I'm just lazy.:D
Also from what I gathered reading Gentoo's ALSA documentation, after you compile a kernel you have to run make mrproper before compiling another one from the same kernel sources. If I understand correctly that will return them to their original state. This will also wipe out your current /usr/src/linux/.config file so make sure you back it up!! Unless of course you like going through every configuration option again.
cd /usr/src/linux
cp .config ~/
make mrproper
cp ~/.config
make menuconfig
You might also want to double check the network configuration as outlined in steps 20 - 23 in the installation guide, I overlooked the line in /etc/rc.conf that enables dhcp the first time around.
mreiland
07-07-2003, 04:51 PM
Hey, thanks for the help Naki. The make mrproper did the trick :)
I'm still having trouble getting it to work correctly though. I'm really inexpereince, so I have absolutely no idea where to go from here. I've searched the forums, and googled around, and I can't seem to find what I'm looking for. Part of the problem is that I really don't know what it is I'm looking for(I have no idea whats wrong).
The first thing I need to do is make sure that Linux is communicating through my NIC properly, but I don't know how to do that. I use SBC DSL, so I'd appreciate any hints. Also, what config files do I need to make sure I have set properly? I've followed the gentoo install guide, but I must be missing something.
I'm using rp-pppoe, and I'm running adsl-setup before adsl-start. It works when run through their live CD, so I've got the correct information.
I'm trying to give as many details I can, so here's some info I gathered, if anyone is willing to help me.
Here's excerpts from ifconfig:
eth0 Link encap:Ethernet HWaddr 00:05:5D:34:3F:DE
UP BROADCAST RUNNING MULTICAST MTU:1500 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:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:5 Base address:0x9000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 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
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
and part of my device listing from within proc
Bus 0, device 10, function 0:
Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 16).
IRQ 5.
Master Capable. Latency=32. Min Gnt=32.Max Lat=64.
I/O at 0x9400 [0x94ff].
Non-prefetchable 32 bit memory at 0xdc800000 [0xdc8000ff].
I appreciate any help I can get.
PS
The etho interface doesn't come up until I run adsl-start. Before that it's just the localhost.
It iooks like you have 2 problems. One, the second line should contain your IP address, Broadcast address and Netmask. If you have a static IP address just follow the instructions under " Manual Static Configuration " in the installation guide. Or try typing:
net-setup eth0
Two, you have to add adsl to your default runlevel. I'm not sure what the best way to do that is, but I would guess with the rc-update command. You might find if you run net-setup that you can set it in there.
I have cable with DHCP so I'm not really familiar with setting up DSL.
mreiland
07-08-2003, 08:16 PM
That's the part that confuses me. I'm not using DHCP, but I don't know what the IP dns servers are, they're given to me automatically by SBC. I know thats what DHCP is, but it's not DHCP.
I put copied the resolv.conf from my live cd over to my /etc/resolv.conf of my Gentoo install, but it's still not working. I tried to get emerge net-setup, but I couldn't get it to work.
Is there anything else I could check? rp-pppoe is running, it's just not connecting correctly when I boot straight into my Gentoo install.
Did you edit your /etc/conf.d/net ? I don't really know what else to try. Maybe take a look over on the Gentoo forum. I've noticed a couple of posts on the subject there.
I'll let you know if I come across anything that may help.
I found a tutorial on how to set up DSL with rp-ppoe, it walks you through setup step by step. It's not writen specifically for Gentoo, but it should help.
http://www.siliconvalleyccie.com/linux-hn/network-linux.htm
mdwatts
07-10-2003, 06:07 PM
and http://www.roaringpenguin.com/pppoe/ :)
mreiland
07-12-2003, 10:01 AM
Sorry for the slow reply, I've been really busy the last week and haven't had a chance to play with Gentoo that much.
I've used rp-pppoe in the past so I'm familiar with the setup, but thanks for the effort. I recompiled my kernel, and it started working. I'm not sure what the problem was before, but I suspect that I hadn't added in some of the support that I needed to. I would have bet money that I added pppoe, and the rest, but apparently I didn't.
Anyway, I got it working now, and I've been working on emerging kde. I have a 1ghz Duron with 512MB pc2100 RAM, and it crunched away for close to 20 hours before a power outage screwed everything up :(
Is it normal for kde to take that long from a fresh install? Also, how does portage handle interruptions like that? I've looked at the portage guide, but it didn't really go into any specifics. When I emerge again, will it have to start completely over, or does it keep track of where it was? I hope it doesn't start completely over because I don't think I'll have the time to just let it sit for a few days while it compiles kde :(
Once again, thanks for the help :)
mdwatts
07-12-2003, 10:17 AM
Originally posted by mreiland
Is it normal for kde to take that long from a fresh install? Also, how does portage handle interruptions like that? I've looked at the portage guide, but it didn't really go into any specifics. When I emerge again, will it have to start completely over, or does it keep track of where it was? I hope it doesn't start completely over because I don't think I'll have the time to just let it sit for a few days while it compiles kde :(
KDE and X will take at least 12 hours I believe.
I'm not sure about restarting as I haven't installed Gentoo for a while and when I did, I never had to restart.
I seem to remember a similiar problem being posted recently though I'm not sure what the answer was. Try searching the JL forums for ??
gentoo restart
gentoo emerge restart
or anything else you can think of.
I found this:
http://forums.gentoo.org/viewtopic.php?t=64837&highlight=restart+emerge
Mine took about 14 hrs to merge KDE on an 1800 AthlonXP.
mreiland
07-12-2003, 12:53 PM
heh, thanks for the quick response guys. I should have searched myself, but I was in a hurry, sorry about that.
I think KDE should be getting close to being finished. I was planning on emerging Gnome also, but now I'm thinking twice about it, heh. But atleast I'll have a desktop I can play with while Gnome is emerging so it won't be so bad :)