From: Dag B. <da...@ba...> - 2004-09-21 22:46:11
|
----- Original Message ----- From: Alan Cox <al...@lx...> Date: Tue, 21 Sep 2004 21:40:54 +0100 To: Dag Bakke <da...@ba...> Subject: Re: [r300] - likely compatibility w rv360? > On Maw, 2004-09-21 at 19:18, Dag Bakke wrote: > > 1. Is the rv360 (9600xt) close enough to the developers hardware to=20 > > a) benefit from the 2d improvements already made w.r.t. CP acceleration > > b) be of any use for testing purposes >=20 > The 6.8.0 server supports 2D acceleration up to the PCI Express cards > like the V5100. I don't personally know which PCI Express are tested > beyond the M300. --------------------------------------------------------- [pardon the trashed message-id and the broken mailer I am using. Soon, I = promise, I will start using a real mail client.] Yes. Knew that. I was referring to r300.sf.net: "Current status * DRM kernel module updated. * 2d driver updated - CP acceleration appears to work correctly." I have tried the two patches for linux-2.6.9-rc2 and xorg-x11-6.8.0. A fe= w notes: kernel patch: Added my pci id to drm_pciids.txt, and got: [drm] Initialized radeon 1.11.0 20020828 on minor 0: ATI Technologies Inc RV350 AR [Radeon 9600] Not sure if I should add the secondary pci id. The README doesn't say. BTW: 2.6.9-rc2 shows a duplicate pci id in drm_pciids.h : {0x1002, 0x4242, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \ {0x1002, 0x4242, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \ # lspci 0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AR [Radeon 9600] 0000:01:00.1 Display controller: ATI Technologies Inc RV350 AR [Radeon 96= 00] (Secondary) # lspci -n 0000:01:00.0 Class 0300: 1002:4152 0000:01:00.1 Class 0380: 1002:4172 But my card is an XT (rv360). I bought it as an XT. The print on the chip says XT. And X agrees.=09 Xorg patch: I added the patch on top of gentoo's 6.8.0-rc1. Gentoo do use a few patch= es on top of vanilla Xorg... (II) Primary Device is: PCI 01:00:0 (--) Assigning device section with no busID to primary device (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) fo= und (--) Chipset ATI Radeon 9600XT AR (AGP) found If I load "dri" in my xorg.conf, the graphics gets wedged as soon as I start X. I get more or less garbled stuff from the previous session.= I can move the cursor, but that's it. I can not exit from X with ctrl-alt-backspace, or shift to the console with ctrl-alt-f1. I also trie= d without radeonfb, just in case. I see no evidence of problems in the Xorg log with dri, which I can review after rebooting via sysrq. Of course, if the machine panicked, nothing got to the kernel log. And no, my wireless keyboard does not have keyboard leds.. I am currently without a secondary machine, so i am unable to (try to) lo= g in via the network to check the kernel log. Will do later this week. I have attached a diff between Xlog with and without dri, in case it is o= f any use to anyone. dagb-home ~ # diff -u /var/log/Xorg.0.log /root/xlog.dri = =20 --- /var/log/Xorg.0.log 2004-09-22 07:06:38.778552072 +0200 +++ /root/xlog.dri 2004-09-22 07:06:14.861188064 +0200 @@ -11,7 +11,7 @@ Markers: (--) probed, (**) from config file, (=3D=3D) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. -(=3D=3D) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 22 07:06:36 2004 +(=3D=3D) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 22 07:04:13 2004 (=3D=3D) Using config file: "/etc/X11/xorg.conf" (=3D=3D) ServerLayout "configured by hand" (**) |-->Screen "Screen 1" (0) @@ -50,7 +50,7 @@ =20 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 -(II) PCI: stages =3D 0x03, oldVal1 =3D 0x80008d48, mode1Res1 =3D 0x80000= 000 +(II) PCI: stages =3D 0x03, oldVal1 =3D 0x00000000, mode1Res1 =3D 0x80000= 000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0269 card 1043,8122 rev 80 class 06,00,00 h= dr 80 (II) PCI: 00:00:1: chip 1106,1269 card 1043,8122 rev 00 class 06,00,00 h= dr 00 @@ -338,6 +338,18 @@ (II) Module v4l: vendor=3D"X.Org Foundation" compiled for 6.8.0, module version =3D 0.0.1 ABI class: X.Org Video Driver, version 0.7 +(II) LoadModule: "dri" +(II) Loading /usr/X11R6/lib/modules/extensions/libdri.a +(II) Module dri: vendor=3D"X.Org Foundation" + compiled for 6.8.0, module version =3D 1.0.0 + ABI class: X.Org Server Extension, version 0.2 +(II) Loading sub module "drm" +(II) LoadModule: "drm" +(II) Loading /usr/X11R6/lib/modules/linux/libdrm.a +(II) Module drm: vendor=3D"X.Org Foundation" + compiled for 6.8.0, module version =3D 1.0.0 + ABI class: X.Org Server Extension, version 0.2 +(II) Loading extension XFree86-DRI (II) LoadModule: "radeon" (II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.o (II) Module radeon: vendor=3D"X.Org Foundation" @@ -784,9 +796,44 @@ (=3D=3D) RADEON(0): Write-combining range (0xa0000000,0x8000000) (II) RADEON(0): Dynamic Clock Scaling Disabled (WW) RADEON(0): Direct rendering support is highly experimental for Rade= on 9500/9700 and newer cards +drmOpenDevice: node name is /dev/dri/card0 +drmOpenDevice: open result is 6, (OK) +drmOpenDevice: node name is /dev/dri/card0 +drmOpenDevice: open result is 6, (OK) +drmOpenByBusid: Searching for BusID pci:0000:01:00.0 +drmOpenDevice: node name is /dev/dri/card0 +drmOpenDevice: open result is 6, (OK) +drmOpenByBusid: drmOpenMinor returns 6 +drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 +(II) RADEON(0): [drm] DRM interface version 1.2 +(II) RADEON(0): [drm] created "radeon" driver at busid "pci:0000:01:00.0" +(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe087c000 +(II) RADEON(0): [drm] mapped SAREA 0xe087c000 to 0xafd0d000 +(II) RADEON(0): [drm] framebuffer handle =3D 0xa0000000 +(II) RADEON(0): [drm] added 1 reserved context for kernel +(II) RADEON(0): [agp] Mode 0x1f000a09 [AGP 0x1106/0x0269; Card 0x1002/0x4152] +(II) RADEON(0): [agp] 8192 kB allocated with handle 0x00000001 +(II) RADEON(0): [agp] ring handle =3D 0xe0000000 +(II) RADEON(0): [agp] Ring mapped at 0xafc0c000 +(II) RADEON(0): [agp] ring read ptr handle =3D 0xe0101000 +(II) RADEON(0): [agp] Ring read ptr mapped at 0xafc0b000 +(II) RADEON(0): [agp] vertex/indirect buffers handle =3D 0xe0102000 +(II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0xafa0b000 +(II) RADEON(0): [agp] GART texture map handle =3D 0xe0302000 +(II) RADEON(0): [agp] GART Texture map mapped at 0xaf52b000 +(II) RADEON(0): [drm] register handle =3D 0xfd800000 +(II) RADEON(0): [dri] Visual configs initialized +(II) RADEON(0): CP in BM mode +(II) RADEON(0): Using 8 MB GART aperture +(II) RADEON(0): Using 1 MB for the ring buffer +(II) RADEON(0): Using 2 MB for vertex/indirect buffers +(II) RADEON(0): Using 5 MB for GART textures (II) RADEON(0): Memory manager initialized to (0,0) (1280,8191) (II) RADEON(0): Reserved area from (0,1024) to (1280,1026) (II) RADEON(0): Largest offscreen area available: 1280 x 7165 +(II) RADEON(0): Will use back buffer at offset 0x1400000 +(II) RADEON(0): Will use depth buffer at offset 0x1900000 +(II) RADEON(0): Will use 100352 kb for textures at offset 0x1e00000 (II) RADEON(0): Render acceleration unsupported on Radeon 9500/9700 and newer. (II) RADEON(0): Render acceleration disabled (II) RADEON(0): Using XFree86 Acceleration Architecture (XAA) @@ -809,9 +856,15 @@ (**) Option "dpms" (**) RADEON(0): DPMS enabled (II) RADEON(0): v4l[/dev/video0]: using hw video scaling [YUY2]. -(II) RADEON(0): Direct rendering disabled +(II) RADEON(0): X context handle =3D 0x00000001 +(II) RADEON(0): [drm] installed DRM signal handler +(II) RADEON(0): [DRI] installation complete +(II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers +(II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers +(II) RADEON(0): [drm] dma control initialized, using IRQ 16 +(II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808 +(II) RADEON(0): Direct rendering enabled (=3D=3D) RandR enabled -Symbol drmGetClient from module /usr/X11R6/lib/modules/drivers/radeon_dr= v.o is unresolved! (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST @@ -854,3 +907,4 @@ (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD) (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) (II) Mouse0: ps2EnableDataReporting: succeeded +AUDIT: Wed Sep 22 07:04:16 2004: 9425 X: client 1 rejected from IP 127.0= .0.1 Feel free to comment/ask/flame... Dag |
From: Dag B. <da...@ba...> - 2004-09-22 17:19:04
|
----- Original Message ----- From: Vladimir Dergachev <vo...@mi...> Date: Wed, 22 Sep 2004 01:23:38 -0400 (EDT) To: Dag Bakke <da...@ba...> Subject: Re: [r300] - likely compatibility w rv360? >=20 > Hi Dag, >=20 > Try this: before starting X switch to another console and execute: >=20 > sleep 15 ; dmesg > dmesg.1 ; sync >=20 > Then start X, wait 30 seconds and shutdown your machine after that - th= is=20 > will let you look at dmesg messages. Indeed. [drm] Initialized radeon 1.11.0 20020828 on minor 0: ATI Technologies Inc= RV350=20 AR [Radeon 9600] agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. agpgart: Badness. Don't know which AGP mode to set. [cmd:1f000a0a tmp:1f0= 00a0a f ell back to:- cmd:1f000a08 tmp:1f000a0a] agpgart: Bridge couldn't do AGP x4. agpgart: Graphic card couldn't do AGP x4. agpgart: Badness. Don't know which AGP mode to set. [cmd:1f000a08 tmp:ff0= 0021b f ell back to:- cmd:1f000208 tmp:ff00021b] agpgart: Bridge couldn't do AGP x4. agpgart: Putting AGP V3 device at 0000:00:00.0 into 0x mode agpgart: Putting AGP V3 device at 0000:01:00.0 into 0x mode [drm] Loading R300 Microcode (last line) I have: Linux agpgart interface v0.100 (c) Dave Jones agpgart: Detected VIA KT880 chipset agpgart: Maximum main memory to use for agp memory: 439M agpgart: AGP aperture is 128M @ 0xe0000000 I have Cc:ed davej.=20 If he is in his normal mode (swamped by email), he'll read it really fast= ... ..with the 'd' key. :-) > Alternatively, it might be that these new chips need a new microcode, > the first thing to do would be to check BeOS drivers, this is one of th= e=20 > public places where one can find R300 one. I checked the BeOS 5.1 driver. Don't think 9600XT is mentioned specificly= , but the R300 ucode appears to cover anything [r|rv]3xx. > thank you for testing :) Thank you for coding! Dag B |
From: Vladimir D. <vo...@mi...> - 2004-09-22 17:27:37
|
On Wed, 22 Sep 2004, Dag Bakke wrote: > > [drm] Initialized radeon 1.11.0 20020828 on minor 0: ATI Technologies Inc RV350 > AR [Radeon 9600] > agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. > agpgart: Badness. Don't know which AGP mode to set. [cmd:1f000a0a tmp:1f000a0a f > ell back to:- cmd:1f000a08 tmp:1f000a0a] > agpgart: Bridge couldn't do AGP x4. > agpgart: Graphic card couldn't do AGP x4. > agpgart: Badness. Don't know which AGP mode to set. [cmd:1f000a08 tmp:ff00021b f > ell back to:- cmd:1f000208 tmp:ff00021b] > agpgart: Bridge couldn't do AGP x4. > agpgart: Putting AGP V3 device at 0000:00:00.0 into 0x mode > agpgart: Putting AGP V3 device at 0000:01:00.0 into 0x mode > [drm] Loading R300 Microcode I think I've seen this one - check your BIOS settings - maybe you need to enable something AGP related there. best Vladimir Dergachev |
From: Alex D. <ale...@gm...> - 2004-09-22 18:02:20
|
On Wed, 22 Sep 2004 13:27:23 -0400 (EDT), Vladimir Dergachev <vo...@mi...> wrote: > > > On Wed, 22 Sep 2004, Dag Bakke wrote: > > > > [drm] Initialized radeon 1.11.0 20020828 on minor 0: ATI Technologies Inc RV350 > > AR [Radeon 9600] > > agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. > > agpgart: Badness. Don't know which AGP mode to set. [cmd:1f000a0a tmp:1f000a0a f > > ell back to:- cmd:1f000a08 tmp:1f000a0a] > > agpgart: Bridge couldn't do AGP x4. > > agpgart: Graphic card couldn't do AGP x4. > > agpgart: Badness. Don't know which AGP mode to set. [cmd:1f000a08 tmp:ff00021b f > > ell back to:- cmd:1f000208 tmp:ff00021b] > > agpgart: Bridge couldn't do AGP x4. > > agpgart: Putting AGP V3 device at 0000:00:00.0 into 0x mode > > agpgart: Putting AGP V3 device at 0000:01:00.0 into 0x mode > > [drm] Loading R300 Microcode > > I think I've seen this one - check your BIOS settings - maybe you need to > enable something AGP related there. As I recall, since the X server doesn't have official 8x agp support yet for radeons, you have to force the bridge into 4x mode in the bios so it comes up in 4x mode. Alex > > best > > Vladimir Dergachev > > > |
From: Vladimir D. <vo...@mi...> - 2004-09-22 22:56:45
|
>> I think I've seen this one - check your BIOS settings - maybe you need to >> enable something AGP related there. > > As I recall, since the X server doesn't have official 8x agp support > yet for radeons, you have to force the bridge into 4x mode in the bios > so it comes up in 4x mode. How very interesting. Alex - could you tell me what is involved in providing AGP 8x mode ? I thought the speed was invisible to software. thank you ! Vladimir Dergachev |
From: Alex D. <ale...@gm...> - 2004-09-22 23:20:57
|
On Wed, 22 Sep 2004 18:56:40 -0400 (EDT), Vladimir Dergachev <vo...@mi...> wrote: > >> I think I've seen this one - check your BIOS settings - maybe you need to > >> enable something AGP related there. > > > > As I recall, since the X server doesn't have official 8x agp support > > yet for radeons, you have to force the bridge into 4x mode in the bios > > so it comes up in 4x mode. > > How very interesting. Alex - could you tell me what is involved in > providing AGP 8x mode ? I thought the speed was invisible to software. This patch: http://penguinppc.org/~daenzer/DRI/radeon-agp8x.diff although I hear the speed difference between 4x and 8x is minimal...at least on r200 hardware. r300 may be different. I don't have an 8x motherboard to test. If someone could test the patch we should probably apply it at some point. Alex > > thank you ! > > Vladimir Dergachev > |
From: Roland S. <rsc...@hi...> - 2004-09-23 00:16:57
|
Alex Deucher wrote: > On Wed, 22 Sep 2004 18:56:40 -0400 (EDT), Vladimir Dergachev > <vo...@mi...> wrote: > >>>>I think I've seen this one - check your BIOS settings - maybe you need to >>>>enable something AGP related there. >>> >>>As I recall, since the X server doesn't have official 8x agp support >>>yet for radeons, you have to force the bridge into 4x mode in the bios >>>so it comes up in 4x mode. >> >>How very interesting. Alex - could you tell me what is involved in >>providing AGP 8x mode ? I thought the speed was invisible to software. > > > This patch: > http://penguinppc.org/~daenzer/DRI/radeon-agp8x.diff > > although I hear the speed difference between 4x and 8x is minimal...at > least on r200 hardware. r300 may be different. I don't have an 8x > motherboard to test. > > If someone could test the patch we should probably apply it at some point. That doesn't look though like it would fix (didn't test) the problem I have with agpgart: Sep 22 18:35:31 ZakTower kernel: agpgart: Found an AGP 3.5 compliant device at 0000:00:0 0.0. Sep 22 18:35:31 ZakTower kernel: agpgart: Device is in legacy mode, falling back to 2.x Sep 22 18:35:31 ZakTower kernel: agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode Sep 22 18:35:31 ZakTower kernel: agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode Sep 22 18:35:31 ZakTower kernel: agpgart: Putting AGP V2 device at 0000:01:00.1 into 0x mode Seems to happen with AGP 3.0 (or only 3.5? whatever that is) bridges and AGP 2.0 cards. Don't think though that's a radeon problem, not even sure it really is a problem (still works, though I don't know what happens if agpgart tries to set a 0x mode?), but it certainly is confusing... Roland |
From: Dave J. <da...@re...> - 2004-09-23 00:52:22
|
On Wed, Sep 22, 2004 at 09:18:55AM -0800, Dag Bakke wrote: > agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. > agpgart: Badness. Don't know which AGP mode to set. [cmd:1f000a0a tmp:1f000a0a f > ell back to:- cmd:1f000a08 tmp:1f000a0a] > agpgart: Bridge couldn't do AGP x4. > agpgart: Graphic card couldn't do AGP x4. > agpgart: Badness. Don't know which AGP mode to set. [cmd:1f000a08 tmp:ff00021b f > ell back to:- cmd:1f000208 tmp:ff00021b] > agpgart: Bridge couldn't do AGP x4. > agpgart: Putting AGP V3 device at 0000:00:00.0 into 0x mode > agpgart: Putting AGP V3 device at 0000:01:00.0 into 0x mode Is this with a current (2.6.9rc2) kernel ? I thought I fixed this up a while back. If it is, can you mail me an lspci -x output please? > I have Cc:ed davej. > If he is in his normal mode (swamped by email), he'll read it really fast... > ..with the 'd' key. :-) I'm somewhat latent right now due to me being in the middle of a relocation, but I'm trying to stay on top of stuff I'm Cc'd on at least.. (Though no promises right now on turnaround time) Dave |
From: Dag B. <da...@ba...> - 2004-09-22 21:10:57
|
----- Original Message ----- From: Alex Deucher <ale...@gm...> Date: Wed, 22 Sep 2004 14:02:16 -0400 To: Vladimir Dergachev <vo...@mi...> Subject: Re: [r300] - likely compatibility w rv360? > On Wed, 22 Sep 2004 13:27:23 -0400 (EDT), Vladimir Dergachev > <vo...@mi...> wrote: > >=20 > >=20 > > On Wed, 22 Sep 2004, Dag Bakke wrote: [snip] > > > agpgart: Bridge couldn't do AGP x4. > > > agpgart: Putting AGP V3 device at 0000:00:00.0 into 0x mode > > > agpgart: Putting AGP V3 device at 0000:01:00.0 into 0x mode > > > [drm] Loading R300 Microcode > >=20 > > I think I've seen this one - check your BIOS settings - maybe you nee= d to > > enable something AGP related there. >=20 > As I recall, since the X server doesn't have official 8x agp support > yet for radeons, you have to force the bridge into 4x mode in the bios > so it comes up in 4x mode. >=20 > Alex Bingo. My rv360 now runs all the r300_demo tests. They look about the same as th= e snapshots on r300.sf.net. --triangles comes out a bit different than=20 http://r300.sourceforge.net/files/how_it_looks.1.png I get one multicolored and one white triangle. But it does not hang the graphics. Looking forward to a steady stream of improvements! Thanks, Dag B |
From: Vladimir D. <vo...@mi...> - 2004-09-22 22:55:35
|
>> so it comes up in 4x mode. > >> >> Alex > > > Bingo. > > My rv360 now runs all the r300_demo tests. They look about the same as the snapshots on r300.sf.net. --triangles comes out a bit different than > http://r300.sourceforge.net/files/how_it_looks.1.png > I get one multicolored and one white triangle. Yep, that's how it is supposed to look - I changed the code around a bit. > > But it does not hang the graphics. Great ! > > Looking forward to a steady stream of improvements! > If you want to play with this, e-mail me your SourceForge handle, so I can give you access to the CVS. best Vladimir Dergachev > > > Thanks, > > Dag B > |
From: Vladimir D. <vo...@mi...> - 2004-09-22 05:23:46
|
Hi Dag, Try this: before starting X switch to another console and execute: sleep 15 ; dmesg > dmesg.1 ; sync Then start X, wait 30 seconds and shutdown your machine after that - this will let you look at dmesg messages. Also see below: On Tue, 21 Sep 2004, Dag Bakke wrote: > I have tried the two patches for linux-2.6.9-rc2 and xorg-x11-6.8.0. A few > notes: > > kernel patch: > Added my pci id to drm_pciids.txt, and got: > [drm] Initialized radeon 1.11.0 20020828 on minor 0: ATI Technologies Inc > RV350 AR [Radeon 9600] > > Not sure if I should add the secondary pci id. The README doesn't say. No, do not add secondary pci id. In fact, check that you added the primary one: 4152 > > BTW: 2.6.9-rc2 shows a duplicate pci id in drm_pciids.h : > {0x1002, 0x4242, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \ > {0x1002, 0x4242, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \ > > > # lspci > 0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AR > [Radeon 9600] > 0000:01:00.1 Display controller: ATI Technologies Inc RV350 AR [Radeon 9600] > (Secondary) > > # lspci -n > 0000:01:00.0 Class 0300: 1002:4152 > 0000:01:00.1 Class 0380: 1002:4172 > > But my card is an XT (rv360). I bought it as an XT. The print on the chip > says XT. And X agrees. Ohh, these are just strings. I am not sure what XT means, but likely you just got a faster clock speed - not enough change to warrant a different pci id. > > > Xorg patch: > I added the patch on top of gentoo's 6.8.0-rc1. Gentoo do use a few patches > on top of vanilla Xorg... Try starting bare X - say X, xterm and twm if you like it. Also I suggest you try regular X.org. I got reports that this patch is sensitive to other components - not sure why. If nothing helps, try plain vanilla 6.7.0 with original 6.7.0 patch - you can configure ProjectRoot to install in a directory different from /usr/X11 - just for testing. The first order of business is to make sure you can start X fine and run simple programs like xterm or twm. Alternatively, it might be that these new chips need a new microcode, the first thing to do would be to check BeOS drivers, this is one of the public places where one can find R300 one. thank you for testing :) Vladimir Dergachev > > (II) Primary Device is: PCI 01:00:0 > (--) Assigning device section with no busID to primary device > (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found > (--) Chipset ATI Radeon 9600XT AR (AGP) found > > > > If I load "dri" in my xorg.conf, the graphics gets wedged as soon > as I start X. I get more or less garbled stuff from the previous session. I > can move the cursor, but that's it. I can not exit from X with > ctrl-alt-backspace, or shift to the console with ctrl-alt-f1. I also tried > without radeonfb, just in case. I see no evidence of problems in the Xorg > log with dri, which I can review after rebooting via sysrq. Of course, if > the machine panicked, nothing got to the kernel log. And no, my wireless > keyboard does not have keyboard leds.. > > I am currently without a secondary machine, so i am unable to (try to) log > in via the network to check the kernel log. Will do later this week. > > I have attached a diff between Xlog with and without dri, in case it is of > any use to anyone. > > dagb-home ~ # diff -u /var/log/Xorg.0.log /root/xlog.dri > --- /var/log/Xorg.0.log 2004-09-22 07:06:38.778552072 +0200 > +++ /root/xlog.dri 2004-09-22 07:06:14.861188064 +0200 > @@ -11,7 +11,7 @@ > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > -(==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 22 07:06:36 > 2004 > +(==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 22 07:04:13 > 2004 > (==) Using config file: "/etc/X11/xorg.conf" > (==) ServerLayout "configured by hand" > (**) |-->Screen "Screen 1" (0) > @@ -50,7 +50,7 @@ > > (II) PCI: Probing config type using method 1 > (II) PCI: Config type is 1 > -(II) PCI: stages = 0x03, oldVal1 = 0x80008d48, mode1Res1 = 0x80000000 > +(II) PCI: stages = 0x03, oldVal1 = 0x00000000, mode1Res1 = 0x80000000 > (II) PCI: PCI scan (all values are in hex) > (II) PCI: 00:00:0: chip 1106,0269 card 1043,8122 rev 80 class 06,00,00 hdr > 80 > (II) PCI: 00:00:1: chip 1106,1269 card 1043,8122 rev 00 class 06,00,00 hdr > 00 > @@ -338,6 +338,18 @@ > (II) Module v4l: vendor="X.Org Foundation" > compiled for 6.8.0, module version = 0.0.1 > ABI class: X.Org Video Driver, version 0.7 > +(II) LoadModule: "dri" > +(II) Loading /usr/X11R6/lib/modules/extensions/libdri.a > +(II) Module dri: vendor="X.Org Foundation" > + compiled for 6.8.0, module version = 1.0.0 > + ABI class: X.Org Server Extension, version 0.2 > +(II) Loading sub module "drm" > +(II) LoadModule: "drm" > +(II) Loading /usr/X11R6/lib/modules/linux/libdrm.a > +(II) Module drm: vendor="X.Org Foundation" > + compiled for 6.8.0, module version = 1.0.0 > + ABI class: X.Org Server Extension, version 0.2 > +(II) Loading extension XFree86-DRI > (II) LoadModule: "radeon" > (II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.o > (II) Module radeon: vendor="X.Org Foundation" > @@ -784,9 +796,44 @@ > (==) RADEON(0): Write-combining range (0xa0000000,0x8000000) > (II) RADEON(0): Dynamic Clock Scaling Disabled > (WW) RADEON(0): Direct rendering support is highly experimental for Radeon > 9500/9700 and newer cards > +drmOpenDevice: node name is /dev/dri/card0 > +drmOpenDevice: open result is 6, (OK) > +drmOpenDevice: node name is /dev/dri/card0 > +drmOpenDevice: open result is 6, (OK) > +drmOpenByBusid: Searching for BusID pci:0000:01:00.0 > +drmOpenDevice: node name is /dev/dri/card0 > +drmOpenDevice: open result is 6, (OK) > +drmOpenByBusid: drmOpenMinor returns 6 > +drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 > +(II) RADEON(0): [drm] DRM interface version 1.2 > +(II) RADEON(0): [drm] created "radeon" driver at busid > "pci:0000:01:00.0" > +(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe087c000 > +(II) RADEON(0): [drm] mapped SAREA 0xe087c000 to 0xafd0d000 > +(II) RADEON(0): [drm] framebuffer handle = 0xa0000000 > +(II) RADEON(0): [drm] added 1 reserved context for kernel > +(II) RADEON(0): [agp] Mode 0x1f000a09 [AGP 0x1106/0x0269; Card > 0x1002/0x4152] > +(II) RADEON(0): [agp] 8192 kB allocated with handle 0x00000001 > +(II) RADEON(0): [agp] ring handle = 0xe0000000 > +(II) RADEON(0): [agp] Ring mapped at 0xafc0c000 > +(II) RADEON(0): [agp] ring read ptr handle = 0xe0101000 > +(II) RADEON(0): [agp] Ring read ptr mapped at 0xafc0b000 > +(II) RADEON(0): [agp] vertex/indirect buffers handle = 0xe0102000 > +(II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0xafa0b000 > +(II) RADEON(0): [agp] GART texture map handle = 0xe0302000 > +(II) RADEON(0): [agp] GART Texture map mapped at 0xaf52b000 > +(II) RADEON(0): [drm] register handle = 0xfd800000 > +(II) RADEON(0): [dri] Visual configs initialized > +(II) RADEON(0): CP in BM mode > +(II) RADEON(0): Using 8 MB GART aperture > +(II) RADEON(0): Using 1 MB for the ring buffer > +(II) RADEON(0): Using 2 MB for vertex/indirect buffers > +(II) RADEON(0): Using 5 MB for GART textures > (II) RADEON(0): Memory manager initialized to (0,0) (1280,8191) > (II) RADEON(0): Reserved area from (0,1024) to (1280,1026) > (II) RADEON(0): Largest offscreen area available: 1280 x 7165 > +(II) RADEON(0): Will use back buffer at offset 0x1400000 > +(II) RADEON(0): Will use depth buffer at offset 0x1900000 > +(II) RADEON(0): Will use 100352 kb for textures at offset 0x1e00000 > (II) RADEON(0): Render acceleration unsupported on Radeon 9500/9700 and > newer. > (II) RADEON(0): Render acceleration disabled > (II) RADEON(0): Using XFree86 Acceleration Architecture (XAA) > @@ -809,9 +856,15 @@ > (**) Option "dpms" > (**) RADEON(0): DPMS enabled > (II) RADEON(0): v4l[/dev/video0]: using hw video scaling [YUY2]. > -(II) RADEON(0): Direct rendering disabled > +(II) RADEON(0): X context handle = 0x00000001 > +(II) RADEON(0): [drm] installed DRM signal handler > +(II) RADEON(0): [DRI] installation complete > +(II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers > +(II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers > +(II) RADEON(0): [drm] dma control initialized, using IRQ 16 > +(II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808 > +(II) RADEON(0): Direct rendering enabled > (==) RandR enabled > -Symbol drmGetClient from module /usr/X11R6/lib/modules/drivers/radeon_drv.o > is unresolved! > (II) Initializing built-in extension MIT-SHM > (II) Initializing built-in extension XInputExtension > (II) Initializing built-in extension XTEST > @@ -854,3 +907,4 @@ > (II) XINPUT: Adding extended input device "Keyboard0" (type: > KEYBOARD) > (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) > (II) Mouse0: ps2EnableDataReporting: succeeded > +AUDIT: Wed Sep 22 07:04:16 2004: 9425 X: client 1 rejected from IP 127.0.0.1 > > > Feel free to comment/ask/flame... > > > Dag > > > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > -- > _______________________________________________ > Dri-devel mailing list > Dri...@li... > https://lists.sourceforge.net/lists/listinfo/dri-devel > |
From: Nicolai H. <pre...@gm...> - 2004-09-22 10:04:07
|
Hi, On Wednesday 22 September 2004 00:45, Dag Bakke wrote: > If I load "dri" in my xorg.conf, the graphics gets wedged as soon > as I start X. I get more or less garbled stuff from the previous session.= =20 I > can move the cursor, but that's it. I can not exit from X with > ctrl-alt-backspace, or shift to the console with ctrl-alt-f1. I also tried > without radeonfb, just in case. I see no evidence of problems in the Xorg > log with dri, which I can review after rebooting via sysrq. Of course, if > the machine panicked, nothing got to the kernel log. And no, my wireless > keyboard does not have keyboard leds.. Whenever this has happened to me, it was caused by bad microcode. Check you= r=20 syslog for a message "Loading Rx00 microcode", and make sure it says R300. If it does, then maybe this chip does need different microcode, as Vladimir= =20 said. cu, Nicolai |