http://bugs.freedesktop.org/show_bug.cgi?id=14219 --- Comment #2 from Joachim Deguara 2008-01-30 15:38:54 PST --- So there is something up with this message: (II) RADEONHD(0): Mapped FB at 0x2ab86a56d000 (size 0x10000000) (II) RADEONHD(0): FUNCTION: rhdSave (II) RADEONHD(0): FUNCTION: RHDSaveMC (II) RADEONHD(0): FUNCTION: RHDVGASave (EE) RADEONHD(0): RHDVGASave: VGA FB Offset (0xE0000000) is out of range of the Cards Internal FB Address (0xD0000000) and I wonder if it has to do with this message: (II) RADEONHD(0): The detected amount of videoram exceeds the PCI BAR aperture. (II) RADEONHD(0): Using only 262144kB of the total 524288kB. (--) RADEONHD(0): VideoRAM: 262144 kByte plus it just doen't make send why the code in RHDVGASave can say that 32MB (VGA->FBOffest) is greater than 256MB(pScrn->VideoRam) **. **these values are not dumped at the time of execution but interpreted from the log. -- 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

http://bugs.freedesktop.org/show_bug.cgi?id=14219 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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

http://bugs.freedesktop.org/show_bug.cgi?id=14219 --- Comment #4 from Egbert Eich 2008-02-05 15:31:50 PST --- Joachim, i doubt it's the offset issue. We don't touch the memory where the vga framebuffer is located at all. When i sat at the movies tonight i had a bunch of ideas what else could be causing this. 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.) 2. when the screen is blank, is this only empty or is it in power save mode? (the led should tell you). 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? -- 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

http://bugs.freedesktop.org/show_bug.cgi?id=14219 --- Comment #6 from Egbert Eich 2008-02-05 16:12:24 PST --- (In reply to comment #5)

(In reply to comment #4)

...

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.

Right. still it shouldn't matter as the memory used by vga isn't touched.

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 ;)

Not at all :)

...

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)

ok. this strongly suggests that something else is causing this. When in framebuffer mode the kernel draws every pixel. So when you type or scroll the screen should get refreshed. In vga text mode setfont should reload a font. So something should appear on the screen afterwards.

...

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.

ok.

...

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).

ok. Now it get's 'interesting' to debug. Is there any chance we can do a debug session interactively (with you editing around in the code)? Alternatively you could just box up the hw and ship it here ;) -- 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

http://bugs.freedesktop.org/show_bug.cgi?id=14219 --- Comment #8 from Joachim Deguara 2008-02-15 15:23:02 PST --- With the latest git a9af866 plus the patch diff.radeonhd_mc_idle I have been able to switch back to console and have it be correct and switch back to X and have it correct but this is limited. I say limited because the first time I only did the once. The second time I was able to switch back and forth 3 times before the screen went blank. It always goes blank when I go to the console and never to X. Tried again and after 3 times it went blank again. So it works...almost -- 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

http://bugs.freedesktop.org/show_bug.cgi?id=14219 --- Comment #10 from Egbert Eich 2008-02-16 06:41:17 PST --- Created an attachment (id=14354) --> (http://bugs.freedesktop.org/attachment.cgi?id=14354) Make sure GRAPH and CRTC engine are disabled before changing surface. Joachim, we at least seem to be on the right track. I've got two more patches to try. This attachment has one of them. -- 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

http://bugs.freedesktop.org/show_bug.cgi?id=14219 --- Comment #12 from Joachim Deguara 2008-02-18 09:56:33 PST --- I have applied all three patches from Egbert and switching to console is working fine. Plus it was locking up when I did not have a fbdev and would switch to console but that is no longer the case. All is working on my side. -- 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