Problems after installing ATI radeon drivers in Mandrake 10
 

I successfully got my ATI radeon 9600SE working properly in Mandrake 10 (finally) using instructions in a thread several lines down (apparently you can't post an url until you've made 5 posts). It's titled "ATI on Mandrake 10 with nforce 2"

However, I now don't have internet access (I'm writing this in windows, I dual boot). Let me emphasize that though I think I'm doing great so far, I'm quite new to linux, so you'll have to speak real slowly :)

Some basic specs:

AMD athlon 1Ghz
ATI Radeon 9600SE

Here is what the Mandrake 10 control center has to say about my network card:

Vendor: ADMtek
Bus: PCI
Desc: ADM983 linksys etherfast 10/100
Module: tulip
Media Class: NETWORK_ETHERNET

Upon selecting config module, it says there are no parameters
Upon selecting Run config tool:
1) selected LAN
2) Only option available is manual
3) Out of the large selection of modules, I selected tulip
4) Two windows briefly appear, too fast for me to read them
5) I'm back at step 2

My roomie, who's far more experienced with linux than I am, says he's 90% sure that the module needed would be sis900, not tulip. However, when I try to select sis900, the same thing happens as with tulip, and the module shown in the control center doesn't change to sis900.

Help!

Post the output of lsmod (this must be done as root)

Post the contents of /etc/modules.conf

Post the contents of /etc/modprobe.preload


And we'll go from there. With that information I can better explain what I did, in the previous forum we spoke in, in terms of what you need to do.

Here goes:

lsmod info:

Module Size Used by
sg 37820 -
sr_mod 16868 -
nfsd 92552 -
exportfs 5728 -
fglrx 207524 -
lp 11140 -
ipv6 227616 -
snd 51524 -
soundcore 8896 -
af_packet 20200 -
hid 32832 -
usbcore 98652 -
ide-floppy 18624 -
ide-tape 34704 -
ide-cd 40068 -
cdrom 37056 -
floppy 58196 -
nls_iso8859-1 3808 -
ntfs 85420 -
sis-agp 5472 -
agpgart 30760 -
ppa 12200 -
parport_pc 32640 -
imm 12232 -
scsi_mod 114360 -
parport 38696 -
rtc 11384 -
ext3 103624 -
jbd 54168 -



contents of modules.conf:

probeall scsi_hostadapter imm ppa
probeall usb-interface usb-ohci
alias eth0 tulip
above snd-emu10k1 snd-pcm-oss
alias sound-slot-0 snd-emu10k1



contents of modprobe.preload:

# /etc/modprobe.preload: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a `#', and everything on the line after them are ignored.
# this file is for module-init-tools (kernel 2.5 and above) ONLY
# for old kernel use /etc/modules

scsi_hostadapter
sis-agp


Hope this helps

In Linux you need to have the appropriate module loaded in order to access the devices it covers (you said you use Windows, in Windows you need drivers to access hardware - its the same in linux only you need to use modules or have support compiled into your kernel, but thats the topic of a different thread). I can see from the output of your lsmod (a simple command that displays the currently loaded modules) that you do not have the tulip or the sis900 modules loaded.

In order to load the modules type the command (as root):

modprobe tulip

this would load the tulip module, to load the sis900 try:

modprobe sis900

My suggestion would be to load one module (start with tulip) and then try running Mandrake's internet connection wizard (or whatever its called). If loading the tulip module doesn't show your network device as one of the choices in the wizard try removing the module with:

rmmod tulip

and then try loading the sis900 module and trying the wizard again.

If you are able to load an appropriate module that allows you to configure your internet card then you will need to instruct Mandrake to load this module everytime it boots, or you will have to load the module manually each time you want to use the internet.

To have modules loaded at boot time you need to simply add their name to the last line in your /etc/modprobe.preload file (**keep in mind /etc/modprobe.preload is the place to put modules to load at boot in 2.5.x kernels and above, /etc/modules.conf is for 2.4.x kernels**), also editing this file must be done as root.

For example if the tulip module is the module you need to use then your /etc/modprobe.preload should look like this:

# /etc/modprobe.preload: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a `#', and everything on the line after them are ignored.
# this file is for module-init-tools (kernel 2.5 and above) ONLY
# for old kernel use /etc/modules

scsi_hostadapter
sis-agp
tulip

If you still can't get the wizard to recognize your card then post back and we can manually write a configuration file. If this does work post back with any further info that you think may help others dealing with the same problem. And of course - good luck :)

Thanks for the excellent, clearly written help. I think we're on the right track. In fact I tried what you suggested before, and it didn't work. I think I know why (explained further down).

First off, I did some research and it looks like ADMtek cards do use tulip, and not sis900.

The results of the modprobes: sis900 loads fine, but the internet connection still won't fire up. Same thing happens in the internet connection wizard: I select sis900 from the list, a couple popup windows briefly appear, and I'm back to square one with no connection.

However, when I modprobe tulip, it says "Fatal: module tulip not found". Strange, since it was obviously present before. I also tried modprobe eth0, since eth0 is an alias for tulip, but that gave the same error.

I then looked in the package program. This is where I got the kernel source from, but searching for "tulip" turned up nothing.

An internet search turned up a dizzying array of sites. I'd like to hear back from you before I go searching through them and wind up doing something I shouldn't ;)

Edit: Oh yeah you'll be interested to know that modprobing snd-pcm-oss and
snd-emu10k1 works. (They weren't loading either, so the sound card wasn't working).

Sounds like if I can just reinstall tulip, everything will be peachy.

hmmmm interesting

for the tulip module try running the command (as root):

depmod

then try the command:

modprobe tulip

If this doesn't work enter the command (as root):

updatedb

and then the command:

locate tulip

and post the output.


As for the sound modules that you had to load using modprobe (snd-pcm-oss and snd-emu10k1) , if you want to load them at boot append just the names of the modules to the end of your /etc/modprobe.preload file (must be root to edit), remember to list only one per line.

[jason@localhost jason]$ su
Password:
[root@localhost jason]# depmod
[root@localhost jason]# modprobe tulip
FATAL: Module tulip not found.
[root@localhost jason]# updatedb
[root@localhost jason]# locate tulip
/usr/src/linux-2.6.3-4mdk/Documentation/DocBook/tulip-user.tmpl
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/ChangeLog
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/21142.c
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/Makefile
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/Kconfig
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/tulip_core.c
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/de2104x.c
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/de4x5.c
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/de4x5.h
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/dmfe.c
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/eeprom.c
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/interrupt.c
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/media.c
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/pnic.c
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/pnic2.c
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/timer.c
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/tulip.h
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/xircom_tulip_cb.c
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/winbond-840.c
/usr/src/linux-2.6.3-4mdk/drivers/net/tulip/xircom_cb.c
/usr/src/linux-2.6.3-4mdk/include/config/net/tulip.h
/lib/modules/2.6.3-4mdk/kernel/drivers/net/tulip
/lib/modules/2.6.3-4mdk/kernel/drivers/net/tulip/winbond-840.ko.gz
/lib/modules/2.6.3-4mdk/kernel/drivers/net/tulip/de2104x.ko.gz
/lib/modules/2.6.3-4mdk/kernel/drivers/net/tulip/de4x5.ko.gz
/lib/modules/2.6.3-4mdk/kernel/drivers/net/tulip/dmfe.ko.gz
/lib/modules/2.6.3-4mdk/kernel/drivers/net/tulip/tulip.ko.gz
/lib/modules/2.6.3-4mdk/kernel/drivers/net/tulip/xircom_tulip_cb.ko.gz
/lib/modules/2.6.3-4mdk/kernel/drivers/net/tulip/xircom_cb.ko.gz
/lib/modules/2.4.25-2mdk/kernel/drivers/net/pcmcia/xircom_tulip_cb.o.gz
/lib/modules/2.4.25-2mdk/kernel/drivers/net/tulip
/lib/modules/2.4.25-2mdk/kernel/drivers/net/tulip/tulip.o.gz
[root@localhost jason]#

Another interesting point: I ran make modules_install again, and tulip was NOT in the list of installed modules, despite the source code being present. Am I correct in assuming that if I can get modules_install to build tulip, I'll be good to go? And if so how would I do that?

You were using make modules_install? Then I'm assuming that you've compiled a new kernel for your installation. If you are in fact compiling a new kernel then I would assume that you did not include tulip, or possibly support for it somewhere higher up the tree, in the form of a module. Try running make menuconfig from your /usr/src/linux-<your kernel number here> directory and make sure you have tulip labeled as "m" for module.

Success!

*leaps out of his chair and does a little dance*

Ah dang, figured you would have read the post on how to get ati's radeon drivers working in mandrake 10. Wish I could post urls. Anyways, rebuilding the kernel was one of the requisite steps.

For anyone who is interested, this is what I did:

make sure you're root and in your kernel source directory (usr/src/linux something or other)
make menuconfig
You're presented with a list of options
1) select Device Drivers
2) select Networking support
3) select Ethernet (10 or 100Mbit)
4) select Tulip family network device support
5) I just set each driver to "M" and the options for DECchip Tulip (dc2114x) PCI support to "*"

Then exit, being sure to save the settings

make
(I was delighted to see that it only builds the changes, and not the entire kernel. I was afraid I'd have to wait 2 hours)
make modules_install
depmod
modprobe tulip

voila!

Now I just have to add tulip to modprobe.preload to ensure it gets loaded on startup

Thanks, hope people find this usefull.