Hard lockup switching to X from vc; Matrox G400 AGP
REF: Linux 2.4.5, 2.4.4, 2.4.3 (and probably earlier);
devfs;
SMP (dual PIII);
< 1GB main memoryHi,
Has anyone noticed their Linux box lock up hard (as in cannot even be pinged from the local network) when switching from a text vc to a vc running X? This has happened for me even without the mga.o and agpgart.o modules being loaded. My current workaround has been to swap out the Matrox-supplied mga_drv.o and mga_hal_drv.o modules and replace them with the ones from the standard X 4.03 distribution, but these are userspace objects and shouldn't be capable of bringing the kernel down. (Like I said, the machine can't even be pinged.)
My best guess is that the mga_hal_drv.o object is ticking an obscure kernel bug. I am raising this with the Matrox support line as well.
Cheers,
Chris
Quoted 4 lines
out the Matrox-supplied mga_drv.o and mga_hal_drv.o modules and replace them with the ones from the standard X 4.03 distribution, but these are userspace objects and shouldn't be capable of bringing the kernel down. (Like I said, the machine can't even be pinged.)
Not really. The matrox code and X server run priviledged and bang on hardware directly. Its quite easily an X11 bug. Nice to know the free software one works better than the vendors 8)
I experienced lost of the signal when switching from X to the console when booting with vga=ext or some of the graphic modes. It was reported here that the problem was the Matrox drivers.
Recently, with kernel 2.4.4+ and XFree 4.0.3 (@1280x1024/head)+ Matrox drivers (http://matrox.com/mga/support/drivers/files/linux_06.cfm) and booting with vga=794 (1280x1024) I have not had problems. I've a G450.
Signature · 1 line
Rafael