Bug 15888 - VGA-0 configured correctly but does not work.
Summary: VGA-0 configured correctly but does not work.
Status: RESOLVED DUPLICATE of bug 15708
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.3 (2007.09)
Hardware: x86 (IA32) Linux (All)
: high critical
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-09 04:53 UTC by Kamalakar
Modified: 2008-05-11 11:42 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.o.log (58.38 KB, text/x-log)
2008-05-09 04:53 UTC, Kamalakar
no flags Details
xorg.conf after inserting vesa driver (1.62 KB, application/octet-stream)
2008-05-10 02:41 UTC, Kamalakar
no flags Details
Xorg.o.log with vesa driver in xorg.conf (60.98 KB, application/octet-stream)
2008-05-10 02:43 UTC, Kamalakar
no flags Details

Description Kamalakar 2008-05-09 04:53:56 UTC
Created attachment 16451 [details]
Xorg.o.log

I use HP COMPAQ Presario 2500 series Laptop whose LCD screen is damaged (I can see colors on small patches and recognize the GDM login screen, Ubuntu Desktop, Kubuntu Desktop etc.). It is hooked up to COMPAQ V45 external monitor and being used as a Desktop.

I am presently using Ubuntu Gutsy Gibbon and the display works even after deleting xorg.conf file. This means auto detection by X window system is working. Gutsy also has xrandr 1.2 and xrandr -q tells me that both VGA-0 and LVDS configurations are correct.

I downloaded Ubuntu 8.04 alternate iso, and used it to install Hardy Heron on another partition on the Laptop. It is a perfect installation but I am unable to use. Everything is ok till GDM starts, the VGA monitor comes to standby mode on login screen. I can see through the patches on Laptop the GDM login screen, enter userid and password, hear the welcome music of Ubuntu desktop and confirm its loading (through the patches) but alas! the monitor remains on standby mode.

On pressing Ctrl alt F1, I can get the console on the monitor, login and verify that the monitor is configured correctly through the command:
xrandr -display :0.0 -q

The settings I get for VGA-0 and LVDS are same which I get in Gutsy.

Assuming that VGA-0 which is shown connected is disabled by GDM (or X), I try to enable it (through --auto):
xrandr -display :0.0 --output VGA-0 --auto --mode 1024x768

But when I go back to X through Ctrl Alt F7 the monitor returns to standby.

I know about the new GUI utility displayconfig-gtk to set up the second monitor but can't use it since the Laptop screen does not work.

My video card is:
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon IGP 330M/340M/350M

I have seen similar bug report for this card but it is for xserver 1.3. Ubuntu Gutsy has this xserver and VGA-0 is working in my case.

Since in my case it is xserver 1.4 I am reporting it.

Kamalakar
Comment 1 Kamalakar 2008-05-10 02:41:53 UTC
Created attachment 16462 [details]
xorg.conf after inserting vesa driver
Comment 2 Kamalakar 2008-05-10 02:43:07 UTC
Created attachment 16463 [details]
Xorg.o.log with vesa driver in xorg.conf
Comment 3 Kamalakar 2008-05-10 02:52:36 UTC
I was using dpkg-reconfigure xserver.xorg command to write xorg.conf file till Ubuntu 7.10. This does not work on Ubuntu 8.04 Hardy Heron.

After reading xorg.conf manual in Hardy Heron I attempted to create xorg.conf file. It did not work with ati driver.

When I replaced ati with vesa driver my VGA monitor works. xrandr -q, however, produces peculiar output which is copied below:
:~$ xrandr -q
Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
   1024x768       61.0* 
   800x600        73.0  
   640x480        86.0

Unlike earlier output this is not showing VGA-0, LVDS, S-Video etc.

Anyway, I am happy to report that my external VGA monitor now works with vesa driver.

Comment 4 Alex Deucher 2008-05-11 11:42:37 UTC

*** This bug has been marked as a duplicate of bug 15708 ***


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.