MandrivaThis Forum is for the discussion of Mandriva (Mandrake) 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 got 3.7.6 drivers to install with 0 problems.. except I still had to # out the busid of the card... (I thought it was supposed to be fixed in this version??? :shrugs
No luck making fglxgears run with 3.5 under 10.0 CE 2.6 kernel on an ATI 9800 pro OEM.
Installation had to be forced and some message blazed through the screen sating I needed to recomplile something. No 3d accel: glxgears in default screen was about 400fps and fglxgears would not run at all. Glxgears also complained about some missing DRI module.
Methinks that the 2.6 kernel in 10.0 CE is not ATI deiver friendly (and vice versa)
We probably just have to accept that CE is the bleeding edge and some things are bound to be tricky until the distro becomes final and gets installed in more systems.
Originally posted by mmassat No luck making fglxgears run with 3.5 under 10.0 CE 2.6 kernel on an ATI 9800 pro OEM.
Installation had to be forced and some message blazed through the screen sating I needed to recomplile something. No 3d accel: glxgears in default screen was about 400fps and fglxgears would not run at all. Glxgears also complained about some missing DRI module.
Methinks that the 2.6 kernel in 10.0 CE is not ATI deiver friendly (and vice versa)
We probably just have to accept that CE is the bleeding edge and some things are bound to be tricky until the distro becomes final and gets installed in more systems.
you mean 3.7 right?? what kind of problems are you having?? getting the driver to work?
Originally posted by trey85stang you mean 3.7 right?? what kind of problems are you having?? getting the driver to work?
As I stated before, the problem is getting 3d accel to work, 2d still works fine, so I reverted to the original installation drivers. Perhaps DRI has to be installed separately but that is probably beyond my capacity not-to-screw-up
Originally posted by mmassat As I stated before, the problem is getting 3d accel to work, 2d still works fine, so I reverted to the original installation drivers. Perhaps DRI has to be installed separately but that is probably beyond my capacity not-to-screw-up
Could you get 3D accel with the 2.6.x kernel?
Yes I have 3d access working! with the 2.6.3mdk kernel
Do you have MSN or IRC? Would you be willing to guide me through the install process? If so, please get in touch because Im a linux newbie and am a bit stuck. Radeon 9600 pro, Mandrake 10 CE
Originally posted by Twigathy Do you have MSN or IRC? Would you be willing to guide me through the install process? If so, please get in touch because Im a linux newbie and am a bit stuck. Radeon 9600 pro, Mandrake 10 CE
fellow newbies, note that he gives specific instructions on how to load the nForce2 specific agpgart.
Quote:
Success (at last)!!
Greetings comrades,
after intensive investigation and (almost neverending) trial-and-error sessions with MDK10 and the Radeon9600 my desktop crate is finally set up the way I intended it. I apoloigze for this posting in advance as it could get a bit lengthy, but I've spent quite some time to fix this issue, and I thought giving away a more detailled description including approaches that did not result in success might be helpful for other hardware-noobs like me. Also forgive my some occasional typos as it's late already here ... So here's a log of my activies (including "go's" and "no-go's").
======
NO_GO:
======
Kernel 2.6.4 with "everything built in but the kitchen-sink"
(phrase courtesy of J.Mullins - SOF II
I compiled and tried this kernel version with all ATI-relevant things built in - these were: nForce/2-, agpgart/nvidia-agp. This lead to a very compact kernel that limited "lsmod"-output to just 2 lines ... the codepage-modules. In this setup, running the ATI-rpm produces fatal errors upon final module insertion ("permission denied"). Consequently a manual "modprobe" <fglrx.ko> produced the same result. That lead me back to the kernel MDK-10 2.6.3mdk-kernel, as delivered "fresh out of the box".
>>>>
On a sidenote: If you are using USB-stuff you should stick with the MDK-kernel as it seems to be patched to supports "supermount" which 2.6.4 doesn't unless you apply the appropriate patch.
<<<
======
GO:
======
I booted into the standard MDK-installation as it has been installed in the first place by MDK10 and performed these tasks on the command line (so there, no "X") ...
STEP 1: Prepare the setup
root@machine ati_drv: rpm -Ui --force fglrx-4.3.0-3.7.6.i386.rpm
(this extracts installs the sources into the proper locations)
STEP 2: Build the core-module
root@machine ati_drv: cd /lib/modules/fglrx/build_mod
(change to dir. to build the driver-module)
(optional) ... perform a ...
root@machine build_mod: chmod a+x make.sh
(to make the script executable if necessary. For some peculiar reason the make-files here only had the "r"-attr. for owner set)
STEP 2.1: Built it
root@machine build_mod: ./make.sh
(this builds the core-driver-module)
STEP 3: Install the driver-module
root@machine build_mod: cd ..
(go up one directory, this should bring you to /lib/modules/fglrx)
(optional) ... perform the "chmod a+x"-command on "make_install.sh"-file if needed (see above)
STEP 3.1: Perform the installation
root@machine fglrx: ./make_install.sh
(this builds the core-driver-module)
If everything goes well up to this point, the fglrx-directory should contain a symbolic link like this ...
fglrx.ko -> /lib/modules/fglrx/fglrx.2.6.3-4mdk-SMP.ko
STEP 4: Checking the loaded AGP-modules
Type ...
root@machine fglrx: lsmod
to check if any AGP-relevant modules are loaded. In my case none was loaded so I inserted the one for my mobo (A7N8X-X, nForce2-chipset) ...
root@machine fglrx: modprobe nvidia-agp
A second "lsmod" should now list "agpgart" which is used by "nvidia-agp".
To make these settings permanent I added this line to "/etc/modprobe.conf" ...
STEP 5: Running fglrxconfig
Now it's time to run the ATI-XF86Config-tool ... type ...
root@machine fglrx: fglrxconfig
and follow the steps.
IMPORTANT:
When getting asked whether or not to use an external AGP-module, type Y. For me this was the cruical part as the fglrxconfig-tool has "[n]" preselected and the description is a fair bit misleading, insinuating that the "internal" AGP-module would be the right thing to do (which it wasn't here).
Well, before I get sued by the linuxcompatible-folks for being a forum-post-hog I call it quits at this point. Thanx again to all the folks here who replied and to the forum-crew for providing this platform.
This got my 9800 pro working, I just had to modprobe the right module and, since everything was already installed the blasted thing just works. Now If you will excuse me I have to save that Chromium ship from endless attacks.
If I feell lucky enough I might download the UT2k4 demo for linux.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.