Hi,

I have the test 2.6 kernel and.... the XF86Config seems OK.....
Hmm... I can't get KDE work with DRI....
I have a radeon 9000 and via KT-133 cs.


The error is :
(==) RADEON(0): Write-combining range (0xd0000000,0x8000000)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
(WW) LoadKernelModule No such file or directory
[drm] failed to load kernel module "radeon"
(II) RADEON(0): [drm] drmOpen failed
(EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI.
(II) RADEON(0): Memory manager initialized to (0,0) (1600,8191)
(II) RADEON(0): Reserved area from (0,1200) to (1600,1202)
(II) RADEON(0): Largest offscreen area available: 1600 x 6989
(II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)

And there is a warnind too...:
(II) Primary Device is: PCI 01:00:0
(II) ATI: Candidate "Device" section "VESA Framebuffer".
(WW) ATI: PCI/AGP Mach64 in slot 1:0:1 could not be detected!
(WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found
(--) Chipset ATI Radeon 9000 If (AGP) found

These seems to be a probelm with the secondary device....

I load agpgart and dmesg | grep agp "> nothing"....
hmm I load the agpgart module ...

Please help this is eating nerves.

I think I fixed the error, dir there's still no DRI in KDE....

The WW is....
(==) RADEON(0): Write-combining range (0xd0000000,0x8000000)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmGetBusid returned ''
(II) RADEON(0): [drm] loaded kernel module for "radeon" driver
(II) RADEON(0): [drm] created "radeon" driver at busid "PCI:1:0:0"
(II) RADEON(0): [drm] added 8192 byte SAREA at 0xf882f000
(II) RADEON(0): [drm] mapped SAREA 0xf882f000 to 0x48271000
(II) RADEON(0): [drm] framebuffer handle = 0xd0000000
(II) RADEON(0): [drm] added 1 reserved context for kernel
(WW) RADEON(0): [agp] AGP not available
(II) RADEON(0): [drm] removed 1 reserved context for kernel
(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xf882f000 at 0x48271000
(II) RADEON(0): Memory manager initialized to (0,0) (1600,8191)
(II) RADEON(0): Reserved area from (0,1200) to (1600,1202)
(II) RADEON(0): Largest offscreen area available: 1600 x 6989
(II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Lines
Scanline Image Writes
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
(II) RADEON(0): Acceleration enabled
(==) RADEON(0): Backing store disabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Using hardware cursor (scanline 1202)
(II) RADEON(0): Largest offscreen area available: 1600 x 6986
(II) RADEON(0): Direct rendering disabled

Hmm.... I tryed "alias /dev/dri/* radeon" in the rc.modules and..... hmm..
the log:
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmGetBusid returned ''
(II) RADEON(0): [drm] created "radeon" driver at busid "PCI:1:0:0"
(II) RADEON(0): [drm] added 8192 byte SAREA at 0xf882f000
(II) RADEON(0): [drm] mapped SAREA 0xf882f000 to 0x48271000
(II) RADEON(0): [drm] framebuffer handle = 0xd0000000
(II) RADEON(0): [drm] added 1 reserved context for kernel
(WW) RADEON(0): [agp] AGP not available

ts close .... another error showed up in dmesg :

Ok... thaLinux agpgart interface v0.100 (c) Dave Jones
[drm] Initialized radeon 1.9.0 20020828 on minor 0
[drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
[drm:radeon_unlock] *ERROR* Process 338 using kernel context 0
Loosing too many ticks!
TSC cannot be used as a timesource. (Are you running with SpeedStep?)
Falling back to a sane timesource.
[drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
[drm:radeon_unlock] *ERROR* Process 793 using kernel context 0

H E L P ......

it looks as if you have same problem like me.
Linux 2.6.0 XFree 4.2.1 on a Libretto L5i/800TNLN with Radeon M6 L
modprobe agpgard - works fine
modprobe radeon - works fine
startx - works nearly fine - but :

(EE) RADEON(0): [agp] AGP not available
resulting in :
(II) RADEON(0): Direct rendering disabled
and substandard OpenGL performance.

the Debian 2.4.21 kernel was unable to load agpgart, and
I currently wonder, where the problem is.
Would XFree 4.3 improve it ?
Are there any agpgart patches for Libretto L5 ?

Wow, another L5 user!

It's just a shame you're posting my question and not the answer to it...

I'm having the same trouble you are, but the L5 has no AGP bus, right? I'm a bit confused as to why you're trying to load agpgart, but I may be misunderstanding what it is.

X is complaining about no AGP available, but I can use DRM over PCI... can't I?

I get those two dmesg errors too.

Can anybody help?

Okay peep

Let's get the skinny here..


The BIG Question is ....

What version of Xfree are you using?

Cuz you're using developmental drivers of radeon.. which require Xfree 4.3.99.12

Anything less than the that will cause those drivers to fail.

1.7.0 is probably ths last version that will work with Xfree 4.3.0

1.9.0 are bleeding edge..

So either you compile the developmental Xfree or get some older kernel modules..?


The other question is...

Do you have some other driver IE FGLRX ati binaries installed.. cuz it looks too like something is also trying to grab the lock on Direct rendering. You can't have both..



Have fun,

Gary