Created attachment 18090 [details] Xorg log I'm experiencing this: http://img354.imageshack.us/my.php?image=dscf0434ju7.jpg On Debian (which, as far as I heard uses VGA console), I experience this on VT switch, while on Arch I only get this on shutdown (probably because Arch uses vesafb console). This is Biostar TA780G M2+ (AMD 780G chipset), AMD Athlon 64 X2 4000+, 4GB RAM. Memory for onboard graphics card is set to "Auto" in BIOS. From what I have heard, this doesn't occur on all cards; it is apparently a hardware issue, but direct VGA access could be implemented to work around this. I'm attaching Xorg.0.log, which mentions that card doesn't properly deal with memory access: RADEONHD(0): RHDVGASave: VGA FB Offset (0xC0000000) is out of range of the Cards Internal FB Address (0xD0000000)
I seem to have a similar setup however cannot reproduce the problem here.
I saw this yesterday on my new system with an HD4850 card connected to a Gigabyte EP45-DS3P motherboard, running Fedora Rawhide.
Luc Verhaegen said that this only happens on cards and IGPs with broken BIOS, not all of them, but fixing it won't be a problem since we already do a sanity check beofre applying any hacks, so non-broken cases won't be affected. Egbert, what board do you have?
(In reply to comment #3) > Luc Verhaegen said that this only happens on cards and IGPs with broken BIOS, > not all of them, but fixing it won't be a problem since we already do a sanity > check beofre applying any hacks, so non-broken cases won't be affected. > > Egbert, what board do you have? > I don't think that's the reason. Since VGA has its own VGAHDP we should not compare the VGAHDP address to the HDP address but the the MC_FB_LOCATION (or a comparable register on later hardware). The reason why most people are not seeing this bug is because the kernel restores everything. I cannot even see a restore problem when I completely disable VGA save/restore. This is because the Linux kernel does font save restore as well as repaint the screen. Looking at the screen shot suggests the following: the space character in the font data is broken while the fonts are ok? What do you get when you type on the console? Does a space also produce a broken character? What happens when you do 'setfont' on the console?
While I'm not the original reported, I've just tried what was suggested in the last comment (http://bugs.freedesktop.org/show_bug.cgi?id=16969#c4) and that diagnosis seems to be correct. Typing a space shows the squiggle character. If I enter 'setfont', the incorrect characters disappear.
*** Bug 17168 has been marked as a duplicate of this bug. ***
I was finally able to reproduce this bug. It should be fixed with this commit: 6fae60c005fba479af66d0dc13704c88d2008fb4 which made it go away here.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.