Bug 25115

Summary: external monitor - bad resolution, detected as TV instead of VGA if plugged at startup
Product: xorg Reporter: zmiq2 <zzmiq2>
Component: Driver/intelAssignee: ykzhao <yakui.zhao>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium Keywords: NEEDINFO
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
lspci -vv detail
none
log before pluggin vga cable, when starting with monitor disconnected
none
log after pluggin the external monitor cable
none
current xorg.conf (almost empty, only virtual is defined)
none
dmesg detail with error regarding video card loading
none
vbios dump
none
dmesg - external monitor connected after logged into X
none
dmesg - external monitor connected before boot
none
xorg.0.log - external monitor connected after logged into X
none
xorg.0.log - external monitor connected before boot
none
Detect SDVO S-video after SDVO RGB none

Description zmiq2 2009-11-16 04:08:08 UTC
Created attachment 31227 [details]
lspci -vv detail

I have a fujitsu u810 just upgraded to ubuntu karmic.

I usually work with an external dell 24'' monitor (1920x1200), while lcd is 1024x600.

With ubunty jaunty (9.04) I also had problems with external monitor, but at the end all got fixed. After upgrading to karmic (9.10) it seems those problems are back:

- when starting the computer with the external monitor connected, I get:

$ /usr/bin/xrandr 
Screen 0: minimum 320 x 200, current 800 x 600, maximum 4096 x 4096
VGA1 connected 800x600+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1360x768       59.8  
   1152x864       60.0  
   1024x768       60.0  
   800x600        60.3* 
   640x480        59.9  
LVDS1 connected 800x600+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x600       59.9 +
   800x600        85.1     72.2     75.0     60.3*    56.2  
   640x480        85.0     72.8     75.0     59.9  
   720x400        85.0  
   640x400        85.1  
   640x350        85.1  

but I cannot disable LVDS:

$ /usr/bin/xrandr --output LVDS1 --off
/usr/bin/xrandr: cannot find output 0x3d

and a lot of gnome applets don't work, with an error when loading xrandr extension


- when starting the computer with the external monitor disconnected, after connecting the vga cable I get:

$ xrandr 
Screen 0: minimum 320 x 200, current 1360 x 768, maximum 4096 x 4096
VGA1 disconnected (normal left inverted right x axis y axis)
LVDS1 connected (normal left inverted right x axis y axis)
   1024x600       59.9 +
   800x600        85.1     72.2     75.0     60.3     56.2  
   640x480        85.0     72.8     75.0     59.9  
   720x400        85.0  
   640x400        85.1  
   640x350        85.1  
TV1 connected 1360x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1360x768       59.8* 
   1152x864       60.0  
   1024x768       60.0  
   800x600        60.3  
   640x480        59.9  

and all utilities work as expected.

- with ubuntu jaunty, I worked at 1920x1200; now, in both cases mentioned before, maximum resolution I get is 1360x768, the image appears vertically distorsioned
Comment 1 zmiq2 2009-11-16 04:09:11 UTC
Created attachment 31228 [details]
log before pluggin vga cable, when starting with monitor disconnected
Comment 2 zmiq2 2009-11-16 04:09:47 UTC
Created attachment 31229 [details]
log after pluggin the external monitor cable
Comment 3 zmiq2 2009-11-16 04:10:41 UTC
Created attachment 31230 [details]
current xorg.conf (almost empty, only virtual is defined)
Comment 4 Carl Worth 2009-11-16 16:45:02 UTC
This looks like a bug in the expertise of yakui.zhao@intel.com so reassigning.

-Carl
Comment 5 ykzhao 2009-11-18 02:16:21 UTC
Will you please try the Eric's drm-intel-next tree and add the boot option of "drm.debug=0x06"?
After the system is booted, please plug the VGA cable and see whether it is detected as TV.

After the test, please attach the output of dmesg, xorg.log.

Please also attach the output of vbios.dump. The vbios.dump can be obtained by using the following commands:
   a. echo 1 > /sys/devices/pci0000:00/0000:00:02.0/rom
   b. cat /sys/devices/pci0000:00/0000:00:02.0/rom >vbios.dump
   c. echo 0 > /sys/devices/pci0000:00/0000:00:02.0/rom

The Eric's drm-intel-next tree can be obtained by using the following command:
    1. git clone git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel.git
   2. git branch -r
   3. git checkout -b origin/drm-intel-next

Thanks.
   Yakui


Comment 6 zmiq2 2009-11-18 04:42:38 UTC
Hi Yakui,

I'm having problems installing eric's package:

- I have performed step 1

- at step 2, I get the error:

root@lb-u:~/xorg-video-intel# ll
total 4
drwxr-xr-x 24 root root 4096 2009-11-18 13:38 drm-intel

root@lb-u:~/xorg-video-intel# git branch -r
fatal: Not a git repository (or any of the parent directories): .git

Thanks

Comment 7 zmiq2 2009-11-18 04:55:46 UTC
ok, before I did
 cd drm-intel/

and 
 git branch -r

didn't said any problem, so I'm continuing the test ...
Comment 8 zmiq2 2009-11-18 05:00:24 UTC
Hi again,

I did the step 3 checkout,

  now what to compile/install?

I'm running ubuntu karmic koala, so I'd like to just compile the intel driver, not the whole linux, with minimum depencies, since I may be missing many of those ....


Thanks again
Comment 9 ykzhao 2009-11-21 05:02:40 UTC
(In reply to comment #8)
> Hi again,
> I did the step 3 checkout,
>   now what to compile/install?
> I'm running ubuntu karmic koala, so I'd like to just compile the intel driver,
> not the whole linux, with minimum depencies, since I may be missing many of
> those ....
> Thanks again
It seems that the system works in KMS mode. In such case you will have to compile the linux kernel.

Will you please try to compile the linux kernel and attach the output of dmesg by adding the boot option of "drm.debug=0x06"?

Will you please attach the output of vbios.dump as required in comment #5?

Thanks.
Comment 10 zmiq2 2009-11-24 02:14:51 UTC
Created attachment 31434 [details]
dmesg detail with error regarding video card loading

Looking at dmesg, I've seen the errors attached in the log file, which may give some indication of what is happening.
Comment 11 zmiq2 2009-11-24 02:17:05 UTC
Hi,

- I have attached some errors messages I have seen in the dmesg, which can give some extra info of the problem


- it's a little difficult for me to recompile the kernel; can you please give me some indications, links where to find the info to install the DKMS environment or whatever it is?

Thanks
Comment 12 ykzhao 2009-11-30 06:07:27 UTC
(In reply to comment #11)
> Hi,
> - I have attached some errors messages I have seen in the dmesg, which can give
> some extra info of the problem
> - it's a little difficult for me to recompile the kernel; can you please give
> me some indications, links where to find the info to install the DKMS
> environment or whatever it is?
> Thanks


Will you please attach the vbios.dump required in comment #5?

Thanks.
Comment 13 zmiq2 2009-12-01 03:37:02 UTC
Hi ykzhao,

many thanks for your help.

As I mentioned in my previous comment #11, it is a little difficult for me to recompile the kernel, since I'm using stock ubuntu 9.10.

Is there any other way to give you the info you require, without recompiling the kernel? Is there any other ubuntu-style software source that I can setup in my computer to have the patch you are talking about installed?

Thanks in advance.
Comment 14 ykzhao 2009-12-01 18:11:06 UTC
(In reply to comment #13)
> Hi ykzhao,
> 
> many thanks for your help.
> 
> As I mentioned in my previous comment #11, it is a little difficult for me to
> recompile the kernel, since I'm using stock ubuntu 9.10.
Only the vbios.dump is required. And it can be obtained by using the following command:
   a. echo 1 > /sys/devices/pci0000:00/0000:00:02.0/rom
   b. cat /sys/devices/pci0000:00/0000:00:02.0/rom >vbios.dump
   c. echo 0 > /sys/devices/pci0000:00/0000:00:02.0/rom

> 
> Is there any other way to give you the info you require, without recompiling
> the kernel? Is there any other ubuntu-style software source that I can setup in
> my computer to have the patch you are talking about installed?
If you can't complie and install the kernel, you can add the boot option of "drm.debug=0x0e" and attach the output of dmesg.
Thanks.
> 
> Thanks in advance.
> 

Comment 15 zmiq2 2009-12-02 02:34:00 UTC
Created attachment 31651 [details]
vbios dump
Comment 16 zmiq2 2009-12-02 02:35:00 UTC
Created attachment 31652 [details]
dmesg - external monitor connected after logged into X
Comment 17 zmiq2 2009-12-02 02:35:36 UTC
Created attachment 31653 [details]
dmesg - external monitor connected before boot
Comment 18 ykzhao 2009-12-09 17:57:46 UTC
(In reply to comment #17)
> Created an attachment (id=31653) [details]
> dmesg - external monitor connected before boot
>
Hi, Zmiq
   From the log in comment #16 it seems that there exists the SDVO card. Sometimes it is detected as SDVO-TV. Sometimes it is also detected as SDVO-VGA.
   Will you please add the debug option of "modedebug" in xorg.conf and attach the output of Xorg.0.log? Please boot the system with KMS disabled by adding the boot option of "nomodeset".
   > option "Modedebug" "True"

    Of course it will be great if you can compile the latest Eric's drm-intel-next tree and attach the output of dmesg by adding the boot option of "drm.debug=0x06".

    Thanks.

   
  

Comment 19 zmiq2 2009-12-10 03:17:09 UTC
Created attachment 31925 [details]
xorg.0.log - external monitor connected after logged into X

Hi ykzhao,

- it is very difficult for me to recompile the kernel; this is a umpc, with limited disk space, and I'm using stock ubuntu...

- with Option "Modedebug" "True", and nomodeset kernel option, now, when plugging the external monitor it gets correctly recognized, and resolution and refresh rates are OK !!

I have attached the xorg.0.log file as requested.

Thanks again for your support.
Comment 20 ykzhao 2009-12-10 19:30:29 UTC
(In reply to comment #19)
> Created an attachment (id=31925) [details]
> xorg.0.log - external monitor connected after logged into X
> 
> Hi ykzhao,
> 
> - it is very difficult for me to recompile the kernel; this is a umpc, with
> limited disk space, and I'm using stock ubuntu...
> 
> - with Option "Modedebug" "True", and nomodeset kernel option, now, when
> plugging the external monitor it gets correctly recognized, and resolution and
> refresh rates are OK !!
> 
> I have attached the xorg.0.log file as requested.
> 
Will you please boot the system with the external monitor connected and attach the output of Xorg.0.log? Of course please still add the boot option of "nomodeset".
Thanks
> Thanks again for your support.
> 

Comment 21 zmiq2 2009-12-11 01:44:55 UTC
Created attachment 31972 [details]
xorg.0.log - external monitor connected before boot

With the nomodeset option in the kernel boot, and having the external monitor connected before boot the system correctly recognized the external monitor, as expected.

I also feel the graphics very snappy, so I even activated compiz and the system is very responsive; also, some little flickering I used to see when using ubuntu 9.04 is not there anymore, now the image is very clear!

Thanks
Comment 22 ykzhao 2009-12-23 22:45:23 UTC
Created attachment 32277 [details] [review]
Detect SDVO S-video after SDVO RGB

Will you please try the debug patch on the latest linus tree and see whether the issue still exists? Please add the boot option of "drm.debug=0x06" and attach the output of dmesg.

thanks.
Comment 23 Michael Fu 2010-05-05 02:11:04 UTC
The tip of the day on drm-intel-next kernel should fix this. would you please have a try?
Comment 24 zmiq2 2010-05-14 01:41:06 UTC
Hi Michael, which is this tip?
Comment 25 zmiq2 2010-05-14 02:48:04 UTC
This week I just upgraded to latest ubuntu, lucid lynx, and the problem got worse when I activated the x-swat ppa updates. Current status is that the problem is back:

Prior to this update, setting the option 'nomodeset' in the kernel worked very well, but this 'trick' doesn't work anymore.


1) Booting with 'nomodeset' in kernel, and external monitor plugged in:
the computer goes into 'low graphics mode' only (800x600), and no way to change, and doesn't detect the external monitor

2) Booting with 'nomodeset' in kernel, external monitor disconnected:
error appears: 'No kernel modesetting driver detected. Screen found, but none have a usable configuration', and it goes into low-graphics mode

After connecting external monitor, xrandr doesn't detect anything

3) Booting without 'nomodeset', and external monitor plugged in:
it goes into 800x600 resolution for the built-in lcd (which is 1024x600), external monitor not detected

4) Booting without 'nomodeset', external monitor disconnected:
built-in lcd works ok; after connecting the external screen (dell p1920), it detects it as TV1, with maximum resolution of 1360x768; then grabage appears in both screen until I turn off built-in lcd and activate only external monitor.

I'm currently working with my external 1900x1200-able monitor at only 1360x768, but I can see something.


I'd very much appreciate any help on this, since this issue is quite old, but still unresolved ....

Many thanks in advance
Comment 26 ykzhao 2010-05-19 17:44:47 UTC
Hi
   Will you please try the latest Eric's drm-intel-next tree and see whether the issue still exists?

thanks.
Comment 27 zmiq2 2010-05-20 02:24:10 UTC
Hi,

as I said before, my compile abilities are limited.

Is there any software source that I could activate in order to try this "Eric's drm-intel-next tree" using normal ubuntu software install tools?


Thanks
Comment 28 Jesse Barnes 2010-07-15 11:12:46 UTC
Looks like a dupe of 26833.  Should be fixed now; there's an xorg edgers repo for bleeding edge kernels you could try.  Check launchpad or ubuntu irc channels for help there (#ubuntu-x on freenode is a good one).

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

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.