Bug 17403

Summary: Switching to console doesn't work (screen corrupted)
Product: xorg Reporter: Rafał Miłecki <zajec5>
Component: Driver/radeonhdAssignee: Luc Verhaegen <lverhaegen>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: major    
Priority: medium CC: marc
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Photo of corrupted screen
none
xorg.conf
none
Xorg.0.log using broken aa4fe63d32e53091f56f7180ece6272037edc1bb
none
my xorg.conf
none
my xorg log none

Description Rafał Miłecki 2008-09-02 00:02:05 UTC
Using git version starting from

commit aa4fe63d32e53091f56f7180ece6272037edc1bb
Author: Egbert Eich <eich@freedesktop.org>
Date:   Fri Aug 29 19:53:16 2008 +0200

    AtomBIOS/Options: Fix AtomBIOS option handling.

    Only get option value when option has actually been set.

I can not switch back to console after starting X. Everything was fine using earlier versions, including:

commit afa3d84886df8548527f30016655142b6c6834fb
Author: Hans Ulrich Niedermann <hun@n-dimensional.de>
Date:   Fri Aug 29 14:15:03 2008 +0200

    Comment on which options to document in man page

    Document those options in a single place (i.e. the definition
    of enum RHDOpts), and add references to that place where one
    might look for options to document.
Comment 1 Rafał Miłecki 2008-09-02 00:03:12 UTC
Created attachment 18628 [details]
Photo of corrupted screen

After switching to console screen slowly changes to something visible on photo. It takes about 10 secs.
Comment 2 Rafał Miłecki 2008-09-02 00:03:43 UTC
Created attachment 18629 [details]
xorg.conf
Comment 3 Rafał Miłecki 2008-09-02 00:05:47 UTC
My card is M82 (RV620):

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Mobilitiy Radeon HD 3400 Series [1002:95c4] (prog-if 00 [VGA controller])
        Subsystem: Sony Corporation Device [104d:9035]
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at c0000000 (32-bit, prefetchable) [size=256M]
        I/O ports at 6000 [size=256]
        Memory at d0020000 (32-bit, non-prefetchable) [size=64K]
        Expansion ROM at d0000000 [disabled] [size=128K]
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Legacy Endpoint, MSI 00
        Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
        Capabilities: [100] Vendor Specific Information <?>
Comment 4 Rafał Miłecki 2008-09-02 00:10:45 UTC
Created attachment 18630 [details]
Xorg.0.log using broken aa4fe63d32e53091f56f7180ece6272037edc1bb
Comment 5 Marc Fournier 2008-09-02 02:50:56 UTC
Hello,

I just wanted to let you know I recently experimented exactly the same problem after changing kernel from 2.6.25.11 to 2.6.26.2. I use linux debian/testing packages and my radeonhd version isn't the most up to date (commit 761940fde7fef72bff18a8b8e840540452cf675a from 14. april).

I also used to have this problem with kernels prior to 2.6.25.


01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400
	Subsystem: Lenovo Device 2006
	Flags: bus master, fast devsel, latency 0, IRQ 11
	Memory at d8000000 (32-bit, prefetchable) [size=128M]
	I/O ports at 2000 [size=256]
	Memory at ee100000 (32-bit, non-prefetchable) [size=64K]
	[virtual] Expansion ROM at ee120000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel modules: fglrx

I hope I'm not interfering with irrelevant info.

Thanks !
Comment 6 Marc Fournier 2008-09-02 02:51:49 UTC
Created attachment 18634 [details]
my xorg.conf
Comment 7 Marc Fournier 2008-09-02 02:52:43 UTC
Created attachment 18635 [details]
my xorg log
Comment 8 Egbert Eich 2008-09-03 02:56:21 UTC
Rafal: should be fixed now. Please retest.
@Marc: your problem is different. Could it be that you have the fglrx module loaded? Please make sure it has never been loaded since the last boot.
Comment 9 Rafał Miłecki 2008-09-03 03:36:48 UTC
Thanks Egbert, current git works fine.

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.