Where the hell is the body of my post? Is it posible that it was too long and now nothing is been showed?

Use the "Preview post" button to make sure it is going to show.

It should, as it is based on HTML, and will just keep going down...

I really think I'm posting too much and something isn't working so I'll upload the buildlog files somwhere else and just post the links.

I can remember when I tryed 64 Studio 1.0 the only way to get my Graphic Card (an ati 9600XT) to work was to edit xorg.conf and change the device to vesa and after that to install the fglrx drivers.

Having the apropiate drivers is quite importantant (correct me here if I'm wrong) beacouse it relieves the processor and let the graphic card make the work it's supposed to do. I can remember how many xruns i got when I was using the vesa driver on 64 Studio 1.0.

So the problem is that I can't get the fglrx driver working properly in 64 Studio 2.0. I have been trying to install the 8.40.4 version of fglrx using this guide I found in german: http://wiki.debianforum.de/AtiTreiberInstallation. But when I get to the "m-a a-i fglrx" step I get an error saying it coudn't build the modules. At first I thought it had something to do with the kernel version because I read something about a problem with the fglrx driver and the 2.6.20 and 2.6.21 Kernel. So I tried the "workaround for linux 2.6.20" proposed at the end of the german guide I found, but it did not work. So I made an udate to the 2.6.22 kernel (I think i got it from the Studio 64 testing repos or from the updates repos, I'm not quite sure). But I got almost an identical error. Here is what I got in that try:

http://ratherbad.net/ftext/fglrx-kernel-src.buildlog.2.6.22-1-multimedia...

I think the log above is the one I got when I tried with the fglrx packages in the sid repos but I'm also quite sure that It's almost identical to the one I got when I tried the ones from ati's website. In both cases I get this "GPL-incompatible module fglrx.ko uses GPL-only symbol". I googled for that and most people say one should build it's own kernel without this paravirtualization thing. But not knowing much about this (beacous I have never build a kernel in my life), I thing in this case I have anothe problem because I'm not geting this "paravirt_ops" message. Insted I get this "__rcu_read_unlock" thing, and I have not been able to find anything about that.

So after that I removed all the fglrx pakages and tried again using the packages provided in the stable etch repos. And this is what I got in that try:

http://ratherbad.net/ftext/fglrx-kernel-src.buildlog.2.6.22-1-multimedia...

So people, any idea what I'm doing wrong? has any of you been abel to get the fglrx driver working properly?

Because I can replace ati for fglrx in my xorg.conf and I actually thought everything was just fine, until I noticed that mplayer wasn't working right with the new drivers. And when I give fglrxinfo in the console i get this Mesa crap. So that means things are not working as supposed.

I have not been able to achive the same performance I had with 64 Studio 1.0 with electric and that is because I don't have the right graphic drivers. This is not a small issue, and I know that most of the fault is ATI's. But again, I would like to throw my radeon out the window and buy an Nvidia card but I'm a poor student, and I just can't afford that at this moment.

I hope someone can help me with this.

I had the same problem with fglrx driver and 64 studio 2.0. (tried with kernels 2.6.21 and .22) with no luck building fglrx and ndiswrapper for my wifi card. My workaround for now is using the standard stable etch kernel (currently 2.6.18-5) for blender, games and wireless networking and if I need to do audio/music work, reboot into 64 studio kernel.

By the way there's a very good guide to install fglrx here:

http://wiki.cchtml.com/index.php/Debian_Installation_Guide

It happen this to me before (with ubuntu studio)

The problem was that I was using a real time kernel.

Just install a normal kernel and build the driver from there ...... it will work!
good luck!

so what am I supposed to do with a normal kernel?

If I'm using 64 studio is because I want to use it! If I install a normal kernel I could just installl debian and forget jack!

Looks like AMD is releasing a new fglrx driver soon and it's supposed to be a lot better than the one we have today. It is supposed to bring "significant graphics performance and compatibility enhancements". So hopefuly the new driver will work with 64 Studio!

I downloaded the new 8.41.7-1 fglrx driver and tryed again. Well, no luck. I wanted to make a new "clean" install of 64 Stdudio after geting the new drivers but now that I know that the new driver is not working I don't know what I'm doing next.

Btw. this time I got this error (if someone understand what it means):

FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol ▒
│ '__rcu_read_lock' ▒
│ make[2]: *** [__modpost] Error 1 ▒
│ make[1]: *** [modules] Error 2 ▒
│ make[1]: Leaving directory ▒
│ `/usr/src/linux-headers-2.6.22-1-multimedia-amd64' ▮
│ make: *** [build] Error 2

Is very similar to what I got with the last driver. So no luck with fglrx.

Maybe Free should look in the Kernel. If other people are getting things to work with a stable etch kernel then there must be something in the realtime kernel that is preventing the fglrx modules to compile. Maybe the problem can be solved easily.

I hope we get this problem solved soon, given the fact that I don't think I'm the only one using an ATI graphic card!

I second this motion. Just spent hours trying to get the fglrx kernel module to compile on 64Studio 2.0 32-bit, and all the time I thought it was because I was a spaz with linux...

Now all I gotta do is figure out how to boot an Etch kernel.

I withdraw my support for this motion - the ATI proprietary drivers aren't worth the hassle.

I got the fglrx kernel module running with Etch's 2.6.18-5, only to find out that it broke Ardour, Jack Control, Skype, and even the ATI Control Panel app. The last 3 in that list all reported 'Floating point exception' on the command line, while Ardour tried to allocate itself 3Gigs of RAM (on my 512MB system, heh).
Removed the fglrx packages, reverted to the 64studio kernel, and *poof*, everything worked again.

I have read that the ATI drivers weren't exactly great, but I had no idea...

I support the idea of a 64 studio kernel revision cause i cant build fglrx or ndiswrapper modules againts RT kernel (everything is fine with the regular etch kernel). Im using 2.0 64 bit and its a drag to change kernels if im doing audio work and then move to use openGL (blender or games) and/or wireless networking (and viceversa).
Cheers.

These steps apply to a 32-bit installation. I modified the instructions here, so if you're using a 64-bit install look there (Method 2) for the build steps but you'll still need to modify the source before you build the .deb packages.

I installed 64 Studio on my Toshiba M70 laptop with a Radeon Mobility video chip. No display.

After faffing about for a while with the driver from Etch, I reinstalled to a clean 64 Studio system and downloaded the Linux Radeon driver from the ATI website.

I had to modify two lines of code in the driver source to set the license to GPL rather than proprietary. I don't know the legal status of this, you're on your own but I guess as long as you don't redistribute you'll be alright. Don't expect help or sympathy from 64 Studio support or anybody else for that matter. This is a get-it-working solution.

I unpacked the drivers with:

./ati-driver-installer-8.42.3-x86.x86_64.run --extract fglrx

Then in the fglrx/common/lib/modules/fglrx/build_mod directory there are a few files, you need to modify two of them:

drm_compat.h
firegl_public.c

In drm_compat.h you need to change:

#define MODULE_LICENSE(x)
to
#define MODULE_LICENSE("GPL")

and in firegl_public.c you need to change:

MODULE_LICENSE("long license string I can't remember the exact detals of")
to
MODULE_LICENSE("GPL");

Then run:

./packages/Debian/ati-packager.sh --buildpkg etch

from the top level fglrx directory. Install the generated .deb files which end up in the directory where you first extracted the drivers, with

sudo dpkg -i fglrx*deb

Then:

sudo m-a a-i fglrx

Finally run:
sudo aticonfig --initial and reboot. You can then try different options to aticonfig to customise your display but this should be enough to get it working with full 3d acceleration.

Note I've not tested this with any audio apps, if you run JACK your system might crash or it might not, I have only just got my display working in the last twenty minutes, nothing more.

Hope this helps someone.

--
Michael Pacey

OK I've fired up jack with the ATI fglrx drivers working as described above, hooked up Zynaddsubfx and battered out a few notes, all works fine on xruns.

YMMV.

--
Michael Pacey

Using sydb's instructions i got the last fglrx driver installed und runing here. Well it was a catastrophe using aiglx+compiz. These drivers are really bad I think. I regret so much having bought an ATI cad...

This procedure no longer seems to work with 2.1 rc2 and/or the latest radeon drivers.

But I downloaded the ATI driver from their website onto a clean 2.1 rc2 install and just ran the installer, which worked.

The free radeon driver which comes with 64 Studio/Debian must be removed from the running kernel otherwise the fglrx module won't load. So you have to switch to a text console (ctrl+alt+f1), hit F2, login as root, /etc/init.d/gdm stop, rmmod radeon, aticonfig --initial then /etc/init.d/gdm start should bring up Gnome with your ATI fglrx driver loaded.
--
Michael Pacey

I've tried with the new driver ati-driver-installer-8-7-x86.x86_64.run.
There some problem in your procedure.

I've tried these changes

./ati-driver-installer-8-7-x86.x86_64.run --extract fglrx-install

cd fglrx-install

then I've followed your instructions

>Then in the fglrx/common/lib/modules/fglrx/build_mod directory there are a few >files, you need to modify two of them:

>drm_compat.h
>firegl_public.c

>In drm_compat.h you need to change:

>#define MODULE_LICENSE(x)
>to
>#define MODULE_LICENSE("GPL")

>and in firegl_public.c you need to change:

>MODULE_LICENSE("long license string I can't remember the exact detals of")
>to
>MODULE_LICENSE("GPL");

After this I've executed

./packages/Ubuntu/ati-packager.sh --buildpkg gutsy

All has worked perfectly, the ".deb" are created regularly and then with

sudo dpkg -i *.deb

they're been correctly installed without the fatal error ("FATAL: modpost:
GPL-incompatible module fglrx.ko uses GPL-only symbol '__rcu_read_lock'") I've
encountered with the original procedure.

So all OK? No, 'cause when gdm starts the screen goes irremediably to be black
(I'm not able to restore even doing F2 (or F3...) to change to text
mode console...

On the ati web-site I've read a not-so-clear advice about the agpgart module and
a possible conflict. But I have a via_agp module which uses agpgart, so what
I should have to do? The standard old driver installed with apt-get give some
problem and I'm not able to see movies on full-screen. (In this moment with many
attempts and many installations and de-installations of different drivers I've
even some problem with the gnome window-manager which seems non to be active in
a strange way...)

Have you got an idea?

I try again next days (not so soon, 'cause I've spent a whole long night and
I'm a bit discouraged) and I hope this can be useful for someone...

Forgive my poor english, I hope you're able to understand...

Bye

ATI is allegedly working on the drivers...