2.6.0-test1 + matroxfb = unuusable VC
Quoted 7 lines · nick black
Petr Vandrovec assumed the extended riemann hypothesis and showed:
Quoted 2 lines
I do not think that it has anything to do with AGP, as matroxfb does not initiate any AGP transfers.
indeed, the issue would only happen after switching from x back to console. regardless, not building agp worked aorund the 2.4 problem for me.
In this case, does it happen if you exit X, or only if you are switching to the console while X are active? If it happens only in second case, then it is bug (I believe fixed long ago) in XFree mga driver: it was sometime reprogramming color depth and line length in the accelerator even when inactive (Gnome1 clock applet running in top right corner was known to trigger this, depending on clock settings matroxfb would cease to work in one second or (up to) one minute after VT switch, depending on clock applet setting... it is possible that it happened only with kernel mga dri driver active, but I'm not 100% sure).
I know no other workaround than using same color depth and same xres_virtual (vxres on fbdev & desktop width in X) in X and on the console.
Best regards,
Petr Vandrovec [email protected]
Petr Vandrovec assumed the extended riemann hypothesis and showed:
Quoted 3 lines
In this case, does it happen if you exit X, or only if you are switching to the console while X are active? If it happens only in second case, then it is bug (I believe fixed long ago) in XFree mga driver: it was sometime
it is the latter case, thanks for the info! regardless, the 2.6.0-test1 problems continue; i'll update my x this evening if my version doesn't contain the fix.
Signature · 3 lines
nick black <[email protected]> "np: nondeterministic polynomial-time the class of dashed hopes and idle dreams." - the complexity zoo
Greetz,
Quoted 7 lines
Quoted 3 lines
In this case, does it happen if you exit X, or only if you are switching to the console while X are active? If it happens only in second case, then it is bug (I believe fixed long ago) in XFree mga driver: it was sometime
it is the latter case, thanks for the info! regardless, the 2.6.0-test1 problems continue; i'll update my x this evening if my version doesn't contain the fix.
After reading this, I enthousiastically upgraded from Xfree 4.2.0 to 4.3.0, but nothing changed. :-( The problem is indeed X-related, but refuses to go away after the upgrade.
Also, I've had 4.2.0 and several earlier X versions working just fine with the "old" matroxfb in the same setup that I'm using now. Was there a bug workaround for this issue in the old driver? If so, is there any hope of it returning?
MCE