Skip to contentSkip to conversation

Linux 2.4.20-pre4 & ff. blows away Xwindows with Matrox G400 and agpgart

DISCUSSION Allan Duncan 3 participants 4 messages Sep 12, 2002

lore
Share & tools
lore
#0 lore raw

This is a reissue of an earlier report, and I've since done some more digging.

Up to kernel 2.4.20-pre2 there was no problem, agpgart et al ran fine etc, but from 2.4.20-pre4 onwards when Xwindows starts to load these modules I am instantly thrown back to a booting machine.
The same kernels on a VIA MVP3 chipset box with a Matrox G200 are fine.

I have ascertained that any attempt to use agpgart triggers it.

Rather than clutter up the list with lots of log files, I've made a web page at
http://www.users.bigpond.com/allan.d/bug/Matrox.html
with all the info I could gather.

Any suggestions of how to improve the error messages around the failure point are welcome. Nothing is written into dmesg at the time of failure.

#1 lore raw
Quoted 13 lines · Allan Duncan

This is a reissue of an earlier report, and I've since done some more digging.

Up to kernel 2.4.20-pre2 there was no problem, agpgart et al ran fine etc, but from 2.4.20-pre4 onwards when Xwindows starts to load these modules I am instantly thrown back to a booting machine.
The same kernels on a VIA MVP3 chipset box with a Matrox G200 are fine.

I have ascertained that any attempt to use agpgart triggers it.

Rather than clutter up the list with lots of log files, I've made a web page at
http://www.users.bigpond.com/allan.d/bug/Matrox.html
with all the info I could gather.

Quoted 8 lines

Any suggestions of how to improve the error messages around the failure point are welcome. Nothing is written into dmesg at the time of failure. -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Might be good to check with a previous bug report I posted if there are any similarities. My problem is that the kernel panics when opengl is used when I have some highmem available.

#2 lore raw
In reply to Allan Duncan
Quoted 9 lines · Allan Duncan

This is a reissue of an earlier report, and I've since done some more digging.

Up to kernel 2.4.20-pre2 there was no problem, agpgart et al ran fine etc, but from 2.4.20-pre4 onwards when Xwindows starts to load these modules I am instantly thrown back to a booting machine.
The same kernels on a VIA MVP3 chipset box with a Matrox G200 are fine.

I have ascertained that any attempt to use agpgart triggers it.

I've seen the same thing with 2.4.20-pre5-ac1, and I'm just building pre5-aa2 to see if there's any difference. This is with an AMD 751 system (an Asus K7M), an original Radeon, and the DRI CVS code. I couldn't get any log messages out of it, though.

Simon

Signature · 4 lines
PGP public key Id 0x144A991C, or ftp://bg77.anu.edu.au/pub/himi/himi.asc
(crappy) Homepage: http://bg77.anu.edu.au
doe #237 (see http://www.lemuria.org/DeCSS) 
My DeCSS mirror: ftp://bg77.anu.edu.au/pub/mirrors/css/ 
#3 lore raw
In reply to Allan Duncan
Quoted 8 lines · Allan Duncan

This is a reissue of an earlier report, and I've since done some more digging.

Up to kernel 2.4.20-pre2 there was no problem, agpgart et al ran fine etc, but from 2.4.20-pre4 onwards when Xwindows starts to load these modules I am instantly thrown back to a booting machine.
The same kernels on a VIA MVP3 chipset box with a Matrox G200 are fine.

Quoted 8 lines

I have ascertained that any attempt to use agpgart triggers it.

Rather than clutter up the list with lots of log files, I've made a web page at
http://www.users.bigpond.com/allan.d/bug/Matrox.html
with all the info I could gather.

Any suggestions of how to improve the error messages around the failure point are welcome. Nothing is written into dmesg at the time of failure.

Uh, the logs for -pre5 with AGP_VIA enabled are NOW referred to (instead of duplicating the -pre5 w/o VIA).