samyc@xxxxxxx wrote:
Hello,
I could get dri work on
-Chipset ATI Radeon IGP320M (U1) 4336 found
-kernel 2.4.24
-XFree86-4.3+fix+DRI-cvs+MEsa-cvs branches
Just to clarify things a bit: I _have_ had DRI working in the past with my card on 2.4.x kernels, but I really need it working on 2.6.x because I would also like to make use of 2.6.x's features such as CPU frequency scaling.
The problem is, for some reason X restarts my computer after DRI is loaded... but verifying the XFree86 log file after booting into runlevel 3, here's what shows up:
(II) RADEON(0): Acceleration enabled (==) RADEON(0): Backing store disabled (==) RADEON(0): Silken mouse enabled (II) RADEON(0): Using hardware cursor (scanline 770) (II) RADEON(0): Largest offscreen area available: 1024 x 7413 (II) RADEON(0): Direct rendering enabled (==) RandR enabled
So it seems that DRI is being enabled, but I can't seem to figure out why X is totally panicking after loading it.
For the record, I've tried disabling acpi.. but my computer won't even boot up when I add in "acpi=off" to the kernel line.
I know there's some little problem or something... but I'm at the end of my rope. I've done what I could... but I'm just not experienced enough to figure this out all by myself. My log files show no sign of errors at all........
ok... Just as I was typing that line, I realized I didn't even check my kernel messages :P
Here's something that sounds kinda related to the problem:
Jan 26 20:16:12 localhost kernel: [drm] Initialized radeon 1.10.0 20020828 on minor 0: ATI Radeon RS100 Mobility U1
Jan 26 20:16:12 localhost kernel: mtrr: 0xf6000000,0x1000000 overlaps existing 0xf6000000,0x800000
Jan 26 20:16:12 localhost kernel: agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Jan 26 20:16:12 localhost kernel: agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
Jan 26 20:16:12 localhost kernel: agpgart: Putting AGP V2 device at 0000:01:05.0 into 4x mode
Jan 26 20:16:13 localhost kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
Jan 26 20:16:13 localhost kernel: atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
Jan 26 20:16:13 localhost kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
Jan 26 20:16:13 localhost kernel: atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
That's the last message in my log file for a while, then about... 2 minutes later there's another one... involving klogd and bios info... so I guess that means that, before the crash, there was some problem related to atkbd.c
Any help greatly, super-dooperly appreciated!
PS: Am I posting this to the right place? Or should it be sent to the developers? Please let me know.
Logan.
_______________________________________________ XFree86 mailing list XFree86@xxxxxxxxxxx http://XFree86.Org/mailman/listinfo/xfree86
