Bug 16553 - Console font is overwritten by a vram buffers allocation (seen when switching from X).
Console font is overwritten by a vram buffers allocation (seen when switching...
Status: RESOLVED FIXED
Product: DRI
Classification: Unclassified
Component: DRM/other
unspecified
x86 (IA32) Linux (All)
: medium normal
Assigned To: Default DRI bug account
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-28 03:16 UTC by Aleksej R. Serdyukov
Modified: 2008-06-29 11:30 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Save and restore the framebuffer offset. (1.62 KB, patch)
2008-06-28 04:39 UTC, Maarten Maathuis
no flags Details | Splinter Review
dmesg of the bug (cleaned up from some of the irrelevant stuff) (13.93 KB, text/plain)
2008-06-28 07:02 UTC, Aleksej R. Serdyukov
no flags Details
Xorg.0.log of the bug (109.32 KB, text/plain)
2008-06-28 07:03 UTC, Aleksej R. Serdyukov
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aleksej R. Serdyukov 2008-06-28 03:16:32 UTC
After X, the console has all the characters except for a few replaced with pseudographics.

NV43 GeForce 6600LE
Debian lenny/sid (testing)
X.Org X Server 1.4.0.90
git drm and nouveau.


git-bisect:

b9ed0f995077f69ae806aae2e83085738ea5e651 is first bad commit
commit b9ed0f995077f69ae806aae2e83085738ea5e651
Author: Ben Skeggs <skeggsb@…>
Date:   Mon Jun 23 01:00:42 2008 +1000

    nouveau: allocate drm-use vram buffers from end of vram.
    
    This avoids seeing garbage from engine setup etc before X gets around
    to pointing the CRTCs at a new scanout buffer.  Not actually a noticable
    problem before G80 as PRAMIN is forced to the end of VRAM by the hardware
    already.

:040000 040000 f5abf3d72faefdbf8030d38cce3f778b74f80708 b1cd605e9c9c882f7a75b1aea2fc76feec2be383 M	shared-core
Comment 1 Maarten Maathuis 2008-06-28 04:39:34 UTC
Created attachment 17442 [details] [review]
Save and restore the framebuffer offset.

This is a blind guess, let me know if it works out ;-)
Comment 2 Aleksej R. Serdyukov 2008-06-28 05:58:53 UTC
(In reply to comment #1)
It didn’t.
Comment 3 Aleksej R. Serdyukov 2008-06-28 07:02:10 UTC
Created attachment 17444 [details]
dmesg of the bug (cleaned up from some of the irrelevant stuff)
Comment 4 Aleksej R. Serdyukov 2008-06-28 07:03:13 UTC
Created attachment 17445 [details]
Xorg.0.log of the bug
Comment 5 Aleksej R. Serdyukov 2008-06-28 08:07:26 UTC
(In reply to comment #3)
> Created an attachment (id=17444) [details]
> dmesg of the bug (cleaned up from some of the irrelevant stuff)
This was missing in the /var/log/dmesg:

agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.

agpgart: Xorg tried to set rate=x12. Setting to AGP3 x8 mode.

agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode

agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode

[drm] Allocating FIFO number 0

[drm] nouveau_fifo_alloc: initialised FIFO 0

[drm] Allocating FIFO number 1

[drm] nouveau_fifo_alloc: initialised FIFO 1