ATI Radeon 9600 M10 and fglrx rpm package
 

I'm trying to install ATI's xfree86 drivers to get my mobile 9600 m10 card working. Last time I checked these drivers didn't work for laptops but, now I'm finding a lot of forums that claim they are working great with them.

So I execute 'rpm -Uhv --force fglrx_4_3_0-8.10.19-1.i386.rpm'

and I get these error messages, which are seemingly unrelated to my hardware, etc. and look like some sort of rpm problem. I have no idea what unresolved symbols are, unfortunately. I've tried 'rpm -Uhv --youbetterinstallthisdamnit!' but, that doesn't seem to correct the problem.

Anyone have ideas?

I've seen that F3 users seem to be enjoying the Mobile Radeon drivers. I used F2 and it wouldn't even boot from the install so, here I am wishing I bought F3 (if even just to try to enjoy it despite the boot problems) I figure xfree86 is "tried and true" so hopefully something comes from this distro.

Thanks for any help!

Redhat 9
xfree86 4.3.0
GNOME
ECS G736 lappy

Preparing... ########################################### [100%]
1:fglrx_4_3_0 ########################################### [100%]
depmod: *** Unresolved symbols in /lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o
/lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o: unresolved symbol __free_pages_Rsmp_8b5bac83
/lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o: unresolved symbol register_chrdev_Rsmp_81aab63a
/lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o: unresolved symbol unlock_page_Rsmp_37b8de42
/lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o: unresolved symbol lock_page_Rsmp_43cf7616
/lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o: unresolved symbol add_wait_queue_Rsmp_d91fb263
/lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o: unresolved symbol remove_wait_queue_Rsmp_b2c44425
/lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o: unresolved symbol mem_map_Rsmp_411fe2f0
/lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o: unresolved symbol remap_page_range_Rsmp_415188d1
/lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o: unresolved symbol _alloc_pages_Rsmp_c57832b3
/lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o: unresolved symbol init_mm_Rsmp_d84869e6
/lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o: unresolved symbol highmem_start_page
/lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o: unresolved symbol kmap_prot
/lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o: unresolved symbol __wake_up_Rsmp_b76c5f1e
/lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o: unresolved symbol kmap_pte
/lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o:
Hint: You are trying to load a module without a GPL compatible license
and it has unresolved symbols. The module may be trying to access
GPLONLY symbols but the problem is more likely to be a coding or
user error. Contact the module supplier for assistance, only they
can help you.

/lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o: insmod /lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o failed
/lib/modules/2.4.20-8smp/kernel/drivers/char/drm/fglrx.o: insmod fglrx failed

ok i see, you should install the kernel source of current running kernel, and retry it again,
may help.

I found a post on linuxquestions.org that dealt with the reason why Fedora 2 did not run on my computer and ended up ditching RH9 for F3 to fix the problem.

What I had to do (about the Fedora problem) to get F3 running on my system was a "nosmp" boot option in order to get F3 up on my lappy. From then I had to boot up and disable irq balancing? I think -I lost the link to the post. Apparently the ECS g736 laptop doesn't work good with smp. I'm glad it's working now (without it even)

Anyway, the system is up and running linux for the first time (except knoppix but, it doesn't count cause I've never seen it NOT boot perfectly) I have F3 with great resolution and it's own M10 driver! I'm very excited. It's too bad I don't get 3d acceleration too but, I'm just happy I have 2d! lol

I saw a lot of reads on this post and I'd just like to say thanks to those who considered the rh9 problem. (though I doubt any of them will read this again) It seems I won't be using rh9 anymore though.

Cheers.

Oh, I'd just like to add to this, for anyone else who has my laptop model. Not only did I have to disable smp at the bootloader with "nosmp" I also had to boot from the kernel image which didn't have a .smp extention on it which indicates it is an smp image (I think)

Another thing you may need to consider is disabling the graphical boot screen which is done by deleting the "rhgb" or whatever it is called (you'll know if you see it) from the bootloader start options as well.

d3xtrom3thorpha - many thanks for taking the time to post back with what worked for you, it likely will be a big help to future readers. And of course congrats on solving the problem -- J.W.