LinuxQuestions.org
Page 2 of 3 1 2 3
Show 50 post(s) from this thread on one page

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Running fglrx with -current (https://www.linuxquestions.org/questions/slackware-14/running-fglrx-with-current-796669/)

gtludwig 04-06-2010 08:49 AM
err... problems...

Code:
gtl@cpc-5564:~$ glxinfo
name of display: :0.0
X Error of failed request:  BadRequest (invalid request code or no such operation)
  Major opcode of failed request:  135 (GLX)
  Minor opcode of failed request:  19 (X_GLXQueryServerString)
  Serial number of failed request:  15
  Current serial number in output stream:  15
gtl@cpc-5564:~$

adamk75 04-06-2010 09:25 AM
Show us your /var/log/Xorg.0.log file.

Adam

gtludwig 04-06-2010 11:01 AM
Here's the link to pastebin.

A less /var/log/Xorg.0.log | grep EE gives this:
Code:
(EE) fglrx(0): Hasn't establisted DRM connection
(EE) fglrx(0): Hasn't establisted DRM connection
(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
(EE) fglrx(0): XMM failed to open CMMQS connection.
Kernel is stock from Slackware64-current.

mlpa 04-06-2010 11:03 AM
So what card do you have?

adamk75 04-06-2010 11:25 AM
From his log file, he has a 3100.

The kernel module isn't loading for some reason... What's the output of 'modprobe fglrx'? Did you blacklist the radeon kernel module, by the way?

Adam

gtludwig 04-06-2010 11:32 AM
Code:
root@cpc-5564:/home/gtl# modprobe fglrx
WARNING: All config files need .conf: /etc/modprobe.d/sound, it will be ignored in a future release.
FATAL: Error inserting fglrx (/lib/modules/2.6.33/drivers/char/drm/fglrx.ko): Invalid module format
I haven't blacklisted the radeon kernel module that I know of.

adamk75 04-06-2010 11:35 AM
So what's the output of 'lsmod | grep radeon' and 'dmesg'?

Adam

gtludwig 04-06-2010 11:50 AM
dmesg output is here.

Code:
root@cpc-5564:/home/gtl# lsmod | grep radeon
root@cpc-5564:/home/gtl#

adamk75 04-06-2010 11:57 AM
This seems to be the source of the problem:

Code:
fglrx: version magic '2.6.33 SMP preempt mod_unload ' should be '2.6.33 SMP mod_unload '
I've seen this mentioned on IRC, too, with various kernel modules built outside of the kernel source tree. Perhaps the kernel config file you compiled the module against doesn't match the config file of the kernel you are using. It looks to me like the kernel module was built with preempt support, but the kernel itself wasn't.

Adam

mlpa 04-06-2010 12:27 PM
You sure your slackware is 64 bits?
If it's 32 bit's you should apply another patch.

gtludwig 04-06-2010 12:40 PM
@adamk75
We discussed this issue you last week on irc. What should I pay attention to when (re)compiling the 2.6.33 kernel?

@mlpa
Slackware64-current here

adamk75 04-06-2010 12:42 PM
Yeah, I thought you might be one of the people I had talked with :-)

I would just compile the kernel without whatever settings you want, and then recompile the kernel module. It should pick up the new kernel config file you used for your kernel and compile the fglrx module accordingly.

Adam

gtludwig 04-06-2010 01:55 PM
kernel 2.6.33.1 for -current is out...
upgrading to it now!

kenjiro 04-06-2010 03:03 PM
Well, today I upgraded slackware64-13.0 to slackware64-current (now kernel 2.6.33.1)... and my ati driver (fglrx) doesn't install anymore (10.3).

So... I have to follow the steps mlpa described or I can get the proprietary driver (10.3) to install? Before I was running bluewhite64-13.0 with kernel 2.6.32.8 and the driver (10.3) would work nicely.

Well, I am downloading the driver from ubuntu site, let's see what happens.

EDIT:
I just followed those steps (until before "run X") and everything is fine till now. Since I am messing with my home computer from work... the "run X' will have to wait a bit.

gtludwig 04-06-2010 04:21 PM
it works with the latest -current!
thanks all!


All times are GMT -5. The time now is 02:53 PM.
Page 2 of 3 1 2 3
Show 50 post(s) from this thread on one page