Bug 13897 - vga-out: modes not recognized, screen stays black
Summary: vga-out: modes not recognized, screen stays black
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
: 8274 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-01-02 11:35 UTC by Guenter Grodotzki
Modified: 2018-06-12 19:08 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Guenter Grodotzki 2008-01-02 11:35:35 UTC
Ubuntu Hardy/Gutsy: xrandr recognizes the correct modes, but when activating vga-0, the monitor stays black (the led switches on, like it was getting a signal)

Debian testing/unstable/(ati-driver: experimental/git 6.7.198*): same as above, additionally modes are not recognized.

A super-friendly person from IRC (bg***in @#debian-x/oftc.net) tried to solve the problem and adviced me to remove some options. Therfor I will post 2x my xorg.conf and xorg.log:


my xorg.conf (before):
--------------------------
Section "Device"
        Identifier      "ATI Technologies Inc Radeon Mobility U1"
        Driver          "radeon"
        BusID           "PCI:1:5:0"
        Option          "AGPMode" "4"
        Option          "AGPFastWrite" "On"
        Option          "EnablePageFlip" "On"
EndSection

Section "Module"
        Load "glx"
        Load "dri"
EndSection

Section "DRI"
        Mode 0666
EndSection


my xorg.log (before)
---------------------------
http://91.121.73.90/debian/xorg_log_before.txt




xorg.conf (after)
-------------------------
Section "Device"
        Identifier      "ATI Technologies Inc Radeon Mobility U1"
        Driver          "radeon"
        BusID           "PCI:1:5:0"
        Option          "AGPMode" "4"
#       Option          "AGPFastWrite" "On"
#       Option          "EnablePageFlip" "On"
EndSection

Section "Monitor"
        Identifier      "VGA-0"
        Modeline "1280x1024_60.00"  108.88  1280 1360 1496 1712  1024 1025 1028$
        #-HSync +Vsync
        Option "PreferredMode" "1280x1024_60.00"
EndSection



xorg.log (after)
------------------------------
http://91.121.73.90/debian/xorg_log_after.txt
Comment 1 Alex Deucher 2008-01-02 12:08:36 UTC
Did this ever work in the past?  There were several IGP cards where dualhead never worked correctly.
Comment 2 Guenter Grodotzki 2008-01-02 12:35:32 UTC
(In reply to comment #1)
> Did this ever work in the past?  There were several IGP cards where dualhead
> never worked correctly.
> 

nope I actually never managed to get a dual-head setup with randr on this laptop (under linux).
Comment 3 Alex Deucher 2008-01-02 12:42:38 UTC
Try again with ati git master.
Comment 4 Guenter Grodotzki 2008-01-02 17:02:20 UTC
(In reply to comment #3)
> Try again with ati git master.
> 

as I made a clean/fresh reinstall of debian unstable, I noticed that xrandr in unstable suddenly recognized the (correct) modes of my connected 2nd monitor.

The new driver version did not work for me. The Screen still stays black (although this time, the Led is blinking which some how indicates wrong/no-input)

Just being curious I ran glxgears and got approx 1000 fps, with the older driver I get only 650fps - but I don't know if there is a connection.
Comment 5 Benjamin Close 2008-01-11 02:39:20 UTC
Bugzilla Upgrade Mass Bug Change

NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO.

  - benjsc
    fd.o Wrangler
Comment 6 Alex Deucher 2008-01-11 11:41:18 UTC
*** Bug 8274 has been marked as a duplicate of this bug. ***
Comment 7 Alex Deucher 2008-12-03 01:01:54 UTC
Is this still an issue with a newer driver (6.9.0 or newer)?
Comment 8 Guenter Grodotzki 2008-12-03 01:36:24 UTC
yes, I tested it recently again with the newest version of Ubuntu (8.10). Monitor is being recognized, and I can activate, but the screen remains black. (via gui-tool and cl xrandr)

I assigend 128MB (shared memory) to the graphic-card to be sure this is not a memory issue.

But I am not using that notebook any more productive (due to that issue), so I am gladly to help for testing new drivers - if needed/required :)

Thanks for still being active with this ticket :)
Comment 9 Alex Deucher 2010-10-19 16:04:26 UTC
Is this still an issue with kms or newer versions of the driver?
Comment 10 Adam Jackson 2018-06-12 19:08:06 UTC
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.


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.