http://bugs.freedesktop.org/show_bug.cgi?id=14219
--- Comment #5 from Joachim Deguara
Joachim, i doubt it's the offset issue. We don't touch the memory where the vga framebuffer is located at all. It would still happen becuase the Framebuffer looks to be at location 256MB which is the size of the Ram. I instrumented the driver before your scaling fix for so the RamSize is in kB and location is normal address.
(EE) RADEONHD(0): RHDVGASave: VGA FB Offset (0xE0000000) is out of range of the Cards Internal FB Address (0xD0000000) (EE) RADEONHD(0): RHDVGASave: FBOffset (0x10000000) is less than videRam(0x00040000)
When i sat at the movies tonight i had a bunch of ideas what else could be causing this.
I hope the thoughts of this bug did not disrupt your movie going experience ;)
So a few qustions: 1. what mode are you using? a vga text mode or a graphical text mode? (On suse graphical is the default on most systems.)
It happened with vesafb and no framebuffer (no vga= in kernel command line)
2. when the screen is blank, is this only empty or is it in power save mode? (the led should tell you).
The screen is not in power save mode as the LED stays green.
3. if it's only blank, does it get filled when you type something? if it's in vga text mode: can you restore content when you do a setfont?
It does not get filled when I type something and blindly logging in and calling setfont does nothing either (I checked that the blind login was succesful so that was not the problem). -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team@lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org