LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Radeon kms works! (https://www.linuxquestions.org/questions/slackware-14/radeon-kms-works-760963/)

onebuck 11-25-2009 07:48 AM

Hi,

Quote:

excerpt from 'Xorg.0.log';

(II) RADEON: Driver for ATI Radeon chipsets:

...
ATI Radeon HD 3600 Series, ATI Radeon HD 3650 AGP,
ATI Radeon HD 3600 PRO, ATI Radeon HD 3600 XT,
ATI Radeon HD 3600 PRO, ATI Mobility Radeon HD 3650,
ATI Mobility Radeon HD 3670, ATI Mobility FireGL V5700,
ATI Mobility FireGL V5725, ATI Radeon HD 3200 Graphics,
ATI Radeon 3100 Graphics, ATI Radeon HD 3200 Graphics,
ATI Radeon 3100 Graphics, ATI Radeon HD 3300 Graphics,
ATI Radeon HD 3200 Graphics, ATI Radeon 3000 Graphics,
ATI Radeon HD Graphics, ATI Radeon Graphics,
ATI Mobility Radeon HD Graphics, ATI Mobility Radeon Graphics,
ATI Radeon Graphics

Your device is in the radeon driver.

:hattip:

dolphin77 12-08-2009 09:49 AM

Hello again.

Just wanted to report, that if you tried the above recipe (http://www.linuxquestions.org/questi...75#post3758275) in the period 24.11.2009-04.12.2009, probably you got a wrong impression that it doesn't work stable enough. There were an issue in mesa git. Some new code was introduced which caused wrong behavior of Kwin and other 3d apps. There were missing parts of screen and many many other buggy stuff. But do not give up. Mesa developing team is still working hard. They reverted the buggy part of code and now everything works very nice.

And of course it is reasonable to update kernel to recently released 2.6.32. I've installed it the next day it was released. so far so good. No negative impressions.

Best regards,
Vladimir

onebuck 12-08-2009 02:39 PM

Hi,

I'm still working with the '2.6.32' kernel on an experimental basis.

I'll continue to work with 'git' for mesa, drm and 'ATI' on the separate install just to get an idea of adjusting things in hopes of getting things shook out.

:hattip:

BrZ 12-08-2009 03:43 PM

Not going to kms now, just trying to gain some fps but I'm learning with this thread. My weak rs482 is giving almost 1400 fps with glxgears. It's running with kernel-2.6.32, patched mesa-761rc2, ddx-6.12.14, libdrm-2.4.15. Except the kernel, all of them was built with SlackBuilds.

I'm tempted to build libdrm-2.4.16, ddx patched with some code from git and mesa761rc3 to see if this mess will work and sustain 1300+ fps.

Please, keep sharing your findings. Thanks.

octoberblu3 12-10-2009 05:15 PM

Quote:

Originally Posted by BrZ (Post 3784511)
I'm tempted to build libdrm-2.4.16, ddx patched with some code from git and mesa761rc3 to see if this mess will work and sustain 1300+ fps.

Please, keep sharing your findings. Thanks.

I am currently running KMS with kernel 2.6.32, libdrm-2.4.16 with --enable-radeon-experimental-api, mesa-7.7-rc2 including r600, and xf86-video-ati from git master. It's working great thus far. (~1250 fps on glxgears) KWin compositing works just fine, and fullscreen video at 1920x1080 works better than ever.

This is running on an ATI HD 2600 Pro.

zvzi 12-10-2009 11:37 PM

i tried kms with kernel 2.6.32 and the bleeding edge mesa, drm and ati from git. Didn't work at first then i removed the "vga" line from lilo.conf and works fine. Performance in kwin dropped however, as they were visible stuttering in a couple of effects compared to running in non-kms. I'm sure these will improve in future releases though. Btw im running on an ATI Mobility Radeon x1700 (R500).

dolphin77 12-11-2009 03:22 AM

I am not sure that glxgears is giving a good measuring. It is very relative measurements. I have 1000-1200 fps with desktop effects switched on and if I switch it off while glxgears running, I can get 1800-1900 fps. Kernel 2.6.32, mesa, libdrm and xf86-video-ati from git of yesterday.

01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3400 Series (prog-if 00 [VGA controller])
Subsystem: Sony Corporation Device 9033
I think it is actually HD3470

BroX 12-20-2009 11:38 AM

I'm trying to get kms working with kernel 2.6.32.2. Upgraded libdrm, mesa and xf86-ati-video as per above.

The screen blanks when drm should be loaded. When I boot with radeon.modesetting=0 I find the following in Xorg.0.log:
Code:

$ grep drm /var/log/Xorg.0.log
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(WW) Warning, couldn't open module fglrxdrm
(II) UnloadModule: "fglrxdrm"
(EE) Can't load FireGL DRM library (libfglrxdrm.so).

This is my card:
Code:

$ lspci|grep VGA
01:00.0 VGA compatible controller: ATI Technologies Inc RV730XT [Radeon HD 4670]

I removed fglrx packages and have no xorg.conf. Why is it still looking for FireGL stuff???

adamk75 12-20-2009 12:29 PM

Please show us the full /var/log/Xorg.0.log file. I have a feeling that you still have fglrx at least partially installed.

As for your KMS issues (which is probably not related)... Did you compile the radeon DRM into the kernel or as a module? How about framebuffer console support?

Adam

BroX 12-20-2009 12:56 PM

1 Attachment(s)
Quote:

Originally Posted by adamk75 (Post 3799079)
Please show us the full /var/log/Xorg.0.log file. I have a feeling that you still have fglrx at least partially installed.

As for your KMS issues (which is probably not related)... Did you compile the radeon DRM into the kernel or as a module? How about framebuffer console support?

Adam

Both drm and framebuffer support are built as modules. I have blacklisted radeon and radeonfb, and load radeon from rc.modules.
Code:

$ grep RADEON build/linux-2.6.32.2/.config
CONFIG_DRM_RADEON=m
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set
CONFIG_DRM_RADEON_KMS=y

Full Xorg.0.log attached.

Cheers, Leon.

adamk75 12-20-2009 01:19 PM

Alright, well let's start with the easiest thing:

Code:

(II) LoadModule: "glx"
(II) Loading /usr/lib64/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="FireGL - ATI Technologies Inc."
        compiled for 7.4.0, module version = 1.0.0

You did not completely remove fglrx, because the glx module that is getting loaded is from the fglrx package/driver.

Code:

(II) LoadModule: "ati"
(WW) Warning, couldn't open module ati
(II) UnloadModule: "ati"
(EE) Failed to load module "ati" (module does not exist, 0)

You also don't seem to have the necessary updated 2D driver installed. I'm guessing you removed the xf86-video-ati package that Slackware installed but you did not properly install xf86-video-ati from git.

As for your console issues. I would personally recommend building with CONFIG_FB=y and removing CONFIG_FB_RADEON altogether, but first it's probably worth just getting those other two parts working and seeing if it improves the console situation any.

Adam

BroX 12-20-2009 01:51 PM

Quote:

Originally Posted by adamk75 (Post 3799120)
Alright, well let's start with the easiest thing:

Code:

(II) LoadModule: "glx"
(II) Loading /usr/lib64/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="FireGL - ATI Technologies Inc."
        compiled for 7.4.0, module version = 1.0.0

You did not completely remove fglrx, because the glx module that is getting loaded is from the fglrx package/driver.

Ok, got that sorted by reinstalling xorg-server package:
Code:

(II) LoadModule: "glx"
(II) Loading /usr/lib64/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
        compiled for 1.6.3, module version = 1.0.0
        ABI class: X.Org Server Extension, version 2.0

Quote:

Code:

(II) LoadModule: "ati"
(WW) Warning, couldn't open module ati
(II) UnloadModule: "ati"
(EE) Failed to load module "ati" (module does not exist, 0)

You also don't seem to have the necessary updated 2D driver installed. I'm guessing you removed the xf86-video-ati package that Slackware installed but you did not properly install xf86-video-ati from git.
I will see if reinstalling xf86-video-ati will make a difference.

Thanks for the help!

Cheers, Leon.

dolphin77 12-20-2009 02:01 PM

there is a bug in 2.6.32.2. I've seen a patch for it somewhere, but I am to busy for now. Try Googling if you want, or better stick to 2.6.32 or 2.6.32.1 for a while.

BroX 12-20-2009 02:19 PM

Quote:

Originally Posted by dolphin77 (Post 3799154)
there is a bug in 2.6.32.2. I've seen a patch for it somewhere, but I am to busy for now. Try Googling if you want, or better stick to 2.6.32 or 2.6.32.1 for a while.

Thanks!

The xf86-video-ati package hadn't been build at all because xorg macros were not updated. Was in too much hurry to notice the obvious error message... Following this guide solved that.
Will now downgrade to 2.6.32.1 and see what it all brings.

Cheers, Leon.

BroX 12-20-2009 02:51 PM

Solved!

Although I get the following when running glxgears:
Code:

$ glxgears
Mesa: Mesa 7.8-devel DEBUG build Dec 20 2009 20:54:44
Mesa warning: couldn't open libtxc_dxtn.so, software DXTn compression/decompression unavailable
Mesa: Initializing x86-64 optimizations                                                       
Mesa: 3Dnow! detected                                                                         
do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.                 
Try adjusting the vblank_mode configuration parameter.                                       
10465 frames in  5.000 seconds = 2093.000 FPS

How can I adjust the vblank_mode configuration?

And:
Code:

$ grep WW /var/log/Xorg.0.log
(WW) Warning, couldn't open module fbdev
(WW) Falling back to old probe method for vesa
(WW) RADEON(0): Color tiling is not yet supported on R600/R700

$ grep EE /var/log/Xorg.0.log                           
(EE) Failed to load module "fbdev" (module does not exist, 0)

Is this because I disabled radeonfb support?


All times are GMT -5. The time now is 11:41 PM.