Re: VIA KT400A and AGP/DRI?

Doug White, 24.02.04, 18:58h CET:

> > > I just replaced an old mainboard with a new one with a VIA KT400A
> > > chipset. Is it possible to get DRI working with that? It used to work
> > > with the old board (different chipset), but I had to turn off DRI in my
> > > X configuration for the new one, as it made X/the system freeze/hang
> > > immediately.
> 
> 
> What happens if you force it to AGP4x? I get crashes o my system if its
> run at AGP8x, at least under windows.

The mainboard's (MSI KT4AV) BIOS doesn't let me set the AGP mode.
Explicitly setting "AGPMode" to "1" in /etc/X11/XF86Config switched the
monitor to standby mode and hung the machine (no panic/dump, keyboard
LEDs didn't work any more, had to reboot via reset button); setting it
to "4" made it panic again, gdb said the following this time:

***
Fatal trap 12: page fault while in kernel mode
fault virtual address	= 0x2
fault code		= supervisor write, page not present
instruction pointer	= 0x8:0xc0500004
stack pointer	        = 0x10:0xd8695b8b
frame pointer	        = 0x10:0xd8695b90
code segment		= base 0x0, limit 0xfffff, type 0x1b
			= DPL 0, pres 1, def32 1, gran 1
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= 304 (syslogd)
trap number		= 12
panic: page fault
at line 819 in file /usr/src/sys/i386/i386/trap.c

syncing disks, buffers remaining... 3842 3842 3842 panic: bremfree: removing a buffer not on a queue
at line 647 in file /usr/src/sys/kern/vfs_bio.cUptime: 3h25m21s
Dumping 511 MB
 16 32 48 64 80[CTRL-C to abort]  96[CTRL-C to abort]  112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448 464 480 496
---
Reading symbols from /boot/kernel/acpi.ko...(no debugging symbols found)...
done.
Loaded symbols for /boot/kernel/acpi.ko
Reading symbols from /boot/kernel/blank_saver.ko...
(no debugging symbols found)...done.
Loaded symbols for /boot/kernel/blank_saver.ko
#0  0xc05438b0 in doadump ()
(kgdb) quit
***

AGP 8x doesn't seem to be supported by XFree86/the Radeon driver.

Google has a thread about a similar problem with Linux which might be
related:
http://groups.google.de/groups?selm=bmr2fm%2429lb%241%40toralf.uib.no

Stefan