Forwarding this bug from a Ubuntu reporter: https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/353419 [Problem] Image on external monitor is shifted to the left, hiding 1/4th of the screen. [Original Report] I have a thinkpad T400 with Intel 4500 chipet hooked to a docking station, which is hooked up to a 24" LG L246WP LCD screen via DVI-HDMI cable. Using the GNOME Display tool, I turn off the laptop screen and turn on the LCD (proper resolution is detected). The problem is that the Image on the LCD screen is shifted to the left so I only see the 3/4 right most of the screen. Please see attachement for visual confirmation. I have tried with and without compiz, I tried panning multiple screens but this issue continue to persist. It is important to note that Intrepid worked with this same exact hardware and BIOS without any issues. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: xserver-xorg-video-intel 2:2.6.3-0ubuntu4 ProcEnviron: LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #38-Ubuntu SMP Fri Mar 27 09:00:52 UTC 2009 SourcePackage: xserver-xorg-video-intel Uname: Linux 2.6.28-11-generic i686 [lspci] 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) Subsystem: Lenovo Device [17aa:20e0] 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) Subsystem: Lenovo Device [17aa:20e4]
Created attachment 25626 [details] xrandr_output.txt
Created attachment 25627 [details] XorgConf.txt
Created attachment 25628 [details] XorgLog.txt
Created attachment 25629 [details] screenshot showing the shift on the LCD
Created attachment 25630 [details] xrandr_VGA_connection.txt the EDID data when connected via VGA is 00ffffffffffff001e6d3e56dd140100 031101030e342078ea5ad5a7564b9b24 135054a54b00a940818fb300814fd1c0 904001010101283c80a070b023403020 360006442100001a483f403062b03240 40c0130006442100001e000000fd0038 4b1e5311000a202020202020000000fc 004c32343657500a2020202020200011 while when conncected via HDMI it is 00ffffffffffff001e6d3f56dd140100 031101038e342078ea5ad5a7564b9b24 135054a54b00a940818fb300814f8180 010101010101283c80a070b023403020 3600b0441100001a483f403062b03240 40c01300b0441100001e000000fd0038 4b1e5311000a202020202020000000fc 004c32343657500a20202020202001b9 02031c714990050403011f1412132309 07078301000065030c001000023a8018 71382d40582c450006442100001e011d 8018711c1620582c250006442100009e 011d007251d01e206e28550006442100 001e8c0ad08a20e02d10103e96000644 2100001e023a80d072382d40102c4520 06442100001e000000000000000000bd
Hi Brace, Could you please upload you xorg log with modedebug option on? thanks Ma Ling
MaLing, as I mentioned, I'm forwarding someone else's bug report, so I don't think you want *my* Xorg.0.log. I have asked the original reporter to join this bug report so he can fulfill your request.
when you say Intrepid, do you mean 8.10 or 8.04? And, Is possible for you to use a Intrepid LiveCD to reproduce the working case and attach the xorg.log with ModeDebug option turns on?
And, please also help to try if the auto adjust in the monitor's OSD menu can resolve the problem or not..
ping ~
hello guys:(In reply to comment #8) > when you say Intrepid, do you mean 8.10 or 8.04? I mean 8.10 And, Is possible for you to > use a Intrepid LiveCD to reproduce the working case and attach the xorg.log > with ModeDebug option turns on? Can you please post instructions on how to do the ModeDebug option. I will do that upon my return from a work/Vacation trip post June 8th.
(In reply to comment #9) > And, please also help to try if the auto adjust in the monitor's OSD menu can > resolve the problem or not.. Moving the pictures to the sides is not an option when you are using a digital connection. If you are using the VGA one, then yer. Please note that I am using a DVI to HDMI cable since this LCD only accepts HDMI (no DVI). >
(In reply to comment #11) > hello guys:(In reply to comment #8) > > when you say Intrepid, do you mean 8.10 or 8.04? > > I mean 8.10 > > And, Is possible for you to > > use a Intrepid LiveCD to reproduce the working case and attach the xorg.log > > with ModeDebug option turns on? > > Can you please post instructions on how to do the ModeDebug option. I will do > that upon my return from a work/Vacation trip post June 8th. > > -- xorg.conf (with option "ModeDebug" "yes" added in the Device section, to dump more register information into Xorg.0.log. If your distribution doesn't ship xorg.conf, you can use 'X --configure' to let X spit out the default configuration it uses and save it as /etc/X11/xorg.conf.)
The issue may be from clock, for this chipset we have done a lot of work to find best clock in latest driver, could you please update your driver? Thanks for your help Ma Ling
I learned from google that T400 has two models, one with integrated gfx and one with switchable gfx. I assume your model is the one with integrated gfx, right?
(In reply to comment #11) > hello guys:(In reply to comment #8) > > when you say Intrepid, do you mean 8.10 or 8.04? > > I mean 8.10 > > And, Is possible for you to > > use a Intrepid LiveCD to reproduce the working case and attach the xorg.log > > with ModeDebug option turns on? > > Can you please post instructions on how to do the ModeDebug option. I will do > that upon my return from a work/Vacation trip post June 8th. > > ping
ping ~ if no respose until Jun 18, we will close it. Thanks Ma Ling
(In reply to comment #6) > Hi Brace, > > Could you please upload you xorg log with modedebug option on? > thanks > Ma Ling > Hello: Sorry for the late reply. the LCD was in use by a colleague. Anyhow, attached is the xorg.log.o with the ModeDebug mode enabled.
Created attachment 26809 [details] Xorg.log.0 with the ModeDebug option enabled.
(In reply to comment #15) > I learned from google that T400 has two models, one with integrated gfx and one > with switchable gfx. I assume your model is the one with integrated gfx, right? > Hello: Yes, my machine has only the integrated intel graphics. No ATI chip on this machine.
(In reply to comment #14) > The issue may be from clock, for this chipset we have done a lot of work to > find best clock in latest driver, could you please update your driver? > > Thanks for your help > Ma Ling > Hello: I am using the latest edge drivers from Ubuntu's Xorg PPA which is at: deb http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu jaunty main deb-src http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu jaunty main ii xserver-xorg 1:7.4~5ubuntu18 the X.Org X server ii xserver-xorg-core 2:1.6.0-0ubuntu14 Xorg X server - core server ii xserver-xorg-input-all 1:7.4~5ubuntu18 the X.Org X server -- input driver metapacka ii xserver-xorg-input-evdev 1:2.1.1-1ubuntu4 X.Org X server -- evdev input driver ii xserver-xorg-input-kbd 1:1.3.1-2ubuntu1 X.Org X server -- keyboard input driver ii xserver-xorg-input-mouse 1:1.4.0-1 X.Org X server -- mouse input driver ii xserver-xorg-input-synaptics 0.99.3-2ubuntu5 Synaptics TouchPad driver for X.Org/XFree86 ii xserver-xorg-input-wacom 1:0.8.2.2-0ubuntu2 X.Org X server -- Wacom input driver ii xserver-xorg-video-all 1:7.4~5ubuntu18 the X.Org X server -- output driver metapack ii xserver-xorg-video-apm 1:1.2.1-1 X.Org X server -- APM display driver ii xserver-xorg-video-ark 1:0.7.1-1 X.Org X server -- ark display driver ii xserver-xorg-video-ati 1:6.12.2-0ubuntu1~xup~1 X.Org X server -- ATI display driver wrapper ii xserver-xorg-video-chips 1:1.2.1-1 X.Org X server -- Chips display driver ii xserver-xorg-video-cirrus 1:1.2.1-3 X.Org X server -- Cirrus display driver ii xserver-xorg-video-fbdev 1:0.4.0-3 X.Org X server -- fbdev display driver ii xserver-xorg-video-geode 2.11.1-1 X.Org server -- Geode GX2/LX display driver ii xserver-xorg-video-i128 1:1.3.1-2ubuntu1 X.Org X server -- i128 display driver ii xserver-xorg-video-i740 1:1.2.0-2 X.Org X server -- i740 display driver ii xserver-xorg-video-intel 2:2.7.1-0ubuntu1~xup~1 X.Org X server -- Intel i8xx, i9xx display d ii xserver-xorg-video-mach64 6.8.0-3 X.Org X server -- ATI Mach64 display driver ii xserver-xorg-video-mga 1:1.4.9.dfsg-3 X.Org X server -- MGA display driver ii xserver-xorg-video-neomagic 1:1.2.2-1 X.Org X server -- Neomagic display driver ii xserver-xorg-video-nv 1:2.1.13-1ubuntu1~xup~1 X.Org X server -- NV display driver ii xserver-xorg-video-openchrome 1:0.2.903+svn741-1build1 X.Org X server -- VIA display driver ii xserver-xorg-video-r128 6.8.0+git20090201.08d56c88-1 X.Org X server -- ATI r128 display driver ii xserver-xorg-video-radeon 1:6.12.2-0ubuntu1~xup~1 X.Org X server -- ATI Radeon display driver ii xserver-xorg-video-rendition 1:4.2.0.dfsg.1-2ubuntu1 X.Org X server -- Rendition display driver ii xserver-xorg-video-s3 1:0.6.1-1 X.Org X server -- legacy S3 display driver ii xserver-xorg-video-s3virge 1:1.10.2-1 X.Org X server -- S3 ViRGE display driver ii xserver-xorg-video-savage 1:2.2.1-4ubuntu2 X.Org X server -- Savage display driver ii xserver-xorg-video-siliconmotion 1:1.7.0-1 X.Org X server -- SiliconMotion display driv ii xserver-xorg-video-sis 1:0.10.1-1 X.Org X server -- SiS display driver ii xserver-xorg-video-sisusb 1:0.9.1-1build1 X.Org X server -- SiS USB display driver ii xserver-xorg-video-tdfx 1:1.4.0-2 X.Org X server -- tdfx display driver ii xserver-xorg-video-trident 1:1.3.0-1ubuntu1 X.Org X server -- Trident display driver ii xserver-xorg-video-tseng 1:1.2.0-1ubuntu1 X.Org X server -- Tseng display driver ii xserver-xorg-video-v4l 1:0.2.0-1ubuntu5 X.Org X server -- Video 4 Linux display driv ii xserver-xorg-video-vesa 1:2.0.0-1ubuntu6 X.Org X server -- VESA display driver ii xserver-xorg-video-vmware 1:10.16.5-2 X.Org X server -- VMware display driver ii xserver-xorg-video-voodoo 1:1.2.0-1ubuntu1 X.Org X server -- Voodoo display driver
II) intel(0): Mode for pipe A: (II) intel(0): Modeline "(null)"x0.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync (74.0 kHz) (II) intel(0): chosen: dotclock 153600 vco 3072000 ((m 128, m1 22, m2 6), n 2, (p 20, p1 2, p2 10)) Above message shows you used 1920x1200, and clock paramerter also match spec, how about the issue ? If it doesn't work yet, has your monitor VGA output , if yes could you please try it to connect your machine and try the same resolution, or find another monitor whose HDMI (VGA or DVI) also provide 192x1200 resolution too? Thanks for your help Ma Ling
(In reply to comment #23) > II) intel(0): Mode for pipe A: > (II) intel(0): Modeline "(null)"x0.0 154.00 1920 1968 2000 2080 1200 1203 > 1209 1235 +hsync -vsync (74.0 kHz) > (II) intel(0): chosen: dotclock 153600 vco 3072000 ((m 128, m1 22, m2 6), n 2, > (p 20, p1 2, p2 10)) > > Above message shows you used 1920x1200, and clock paramerter also match spec, > how about the issue ? The issue continue to exists. the screen is shifted to the left and the colours are at a very high contrast. It almost feels like as if the chipset thinks it is a TV and not a monitor. > If it doesn't work yet, has your monitor VGA output , if yes could you please > try it to connect your machine and try the same resolution, I did try the VGA connection and it works fine. Unfortunately, I don't like to work in VGA mode since the analog to digital conversion makes the text less fuzzy. or find another > monitor whose HDMI (VGA or DVI) also provide 192x1200 resolution too? I have another NEC 20" screen that runs at 1600x1200 and it works perfectly fine with the same exact machine over DVI. > > Thanks for your help > Ma Ling >
(In reply to comment #23) > II) intel(0): Mode for pipe A: > (II) intel(0): Modeline "(null)"x0.0 154.00 1920 1968 2000 2080 1200 1203 > 1209 1235 +hsync -vsync (74.0 kHz) > (II) intel(0): chosen: dotclock 153600 vco 3072000 ((m 128, m1 22, m2 6), n 2, > (p 20, p1 2, p2 10)) > > Above message shows you used 1920x1200, and clock paramerter also match spec, > how about the issue ? > If it doesn't work yet, has your monitor VGA output , if yes could you please > try it to connect your machine and try the same resolution, or find another > monitor whose HDMI (VGA or DVI) also provide 192x1200 resolution too? > > Thanks for your help > Ma Ling > Does sync polarity matter here? Just noticed that the modeline from the monitor says vsync need to be negative. IIRC, our driver always set the syncs to positive... Just my $.02..
Created attachment 26822 [details] please try the patch on your machine, thanks The patch modify sync polarity according adjust mode. thanks Ma Ling
(In reply to comment #26) > Created an attachment (id=26822) [details] > please try the patch on your machine, thanks > > The patch modify sync polarity according adjust mode. > > thanks > Ma Ling > Thanks. i will late on in the week and let you know.
(In reply to comment #26) > Created an attachment (id=26822) [details] > please try the patch on your machine, thanks > > The patch modify sync polarity according adjust mode. > > thanks > Ma Ling > Hi. I tried the patch but he result is the same. Attached is the code for the Xorg.0.log.20090620.gz (The modedebug option is still open BTW)
Created attachment 26987 [details] debug log of the newly patched intel driver with modedeub on.
(In reply to comment #11) > hello guys:(In reply to comment #8) > > when you say Intrepid, do you mean 8.10 or 8.04? > > I mean 8.10 > > And, Is possible for you to > > use a Intrepid LiveCD to reproduce the working case and attach the xorg.log > > with ModeDebug option turns on? > > Can you please post instructions on how to do the ModeDebug option. I will do > that upon my return from a work/Vacation trip post June 8th. > > Anmar, you said this worked in Intrepid, could you please attach a log with ModeDebug turns on on Intrepid now? Also, pls try to use plain text as much as possible. To reduce the log file size, just upload the file after X bootup. thanks.
(In reply to comment #30) > (In reply to comment #11) > > hello guys:(In reply to comment #8) > > > when you say Intrepid, do you mean 8.10 or 8.04? > > > > I mean 8.10 > > > > And, Is possible for you to > > > use a Intrepid LiveCD to reproduce the working case and attach the xorg.log > > > with ModeDebug option turns on? > > > > Can you please post instructions on how to do the ModeDebug option. I will do > > that upon my return from a work/Vacation trip post June 8th. > > > > > Anmar, you said this worked in Intrepid, could you please attach a log with > ModeDebug turns on on Intrepid now? > Also, pls try to use plain text as much as possible. To reduce the log file > size, just upload the file after X bootup. thanks. ping~
hi Bryce, According our bug rule, we will close the issue if no reppose is over one month. Thanks Ma Ling
Created attachment 27415 [details] Xorg for Intrepid without ModeDebug
Created attachment 27416 [details] Xorg log for Intrepid with ModeDebug
(In reply to comment #32) > hi Bryce, > According our bug rule, we will close the issue if no reppose is over one > month. > Thanks > Ma Ling > Hello Ma: I attached the intrepid logs with and without Mode Debug. One thing struck me what that there were 3 screens showing up on the GNOME Display. One was laptop, one was unknown and one LG Electronics. Any how. I turned off the laptop and the unknown and kep the LG Electronics and managed to get it working (without Compiz). The Debug log is for it working without a problem (No shift). anmar
Created attachment 27509 [details] please try the patch under the same enviroment in comments #34 anmar, Because your use the version is 2.4.1, we have resolve the problem. However in order to work in this version, the dummy patch only remove HDMI-1 from output list simply, please try it and upload log file with modedebug option on under the same environment of comments #34. thanks for your help. Ma Ling
(In reply to comment #36) > Created an attachment (id=27509) [details] > please try the patch under the same enviroment in comments #34 > > anmar, > Because your use the version is 2.4.1, we have resolve the problem. > However in order to work in this version, the dummy patch only remove HDMI-1 > from output list simply, please try it and upload log file with modedebug > option on under the same environment of comments #34. > > thanks for your help. > > Ma Ling > ling, it was me who asked Anmar to try an intrepid , hoping to get a regdump to do comparison... so simply turns off the HDMI-1 may not help for the original issue.. Anmar, I wanted to ask for two regdump from you: 1) using latest driver or 2.7.1 on which you reported this bug, after you turns off LVDS and turns on your LG monitor using Gnome tool and set to native resolution ( it should shift now), please use reg_dump in xf86-video-intel package to grab a reg dump snapshot 2) using Intrepid, again, using Gnome tool turns off LVDS and turns on your LG monitor, trying to set it native resolution as well ( no shift ), please use the reg_dump to grab a snapshot then please attach the two reg_dump. thanks.
ping Anmar...
(In reply to comment #38) > ping Anmar... > Hey guys. work has been crazy so I apologize for not getting back to you sooner. Anyhow, I collected the necessary information and attached to this bug.
Created attachment 27745 [details] with laptop screen off and LG LCD turned on. this is done on Intrepid I have turned the laptop screen off and left the LG LCD on. All that was done on Intrepid. BTW, Compiz was turned off.
Created attachment 27746 [details] results of intel dump I have turned the laptop screen off and left the LG screen on. the shift continue to occurs . Log is attached
(In reply to comment #40) > Created an attachment (id=27745) [details] > with laptop screen off and LG LCD turned on. this is done on Intrepid > > I have turned the laptop screen off and left the LG LCD on. All that was done > on Intrepid. BTW, Compiz was turned off. > Armar, looks like in Intrepid, the mode is 1600x1200 instead of 1900x1200. could you check using xrandr to see if you can get 1900x1200 in Intrepid in above testing? and if so, does it work properly if you set it to 1900x1200, and would you please attach the reg_dump after setting it to 1900x1200? thanks.
(In reply to comment #42) > (In reply to comment #40) > > Created an attachment (id=27745) [details] [details] > > with laptop screen off and LG LCD turned on. this is done on Intrepid > > > > I have turned the laptop screen off and left the LG LCD on. All that was done > > on Intrepid. BTW, Compiz was turned off. > > > Armar, looks like in Intrepid, the mode is 1600x1200 instead of 1900x1200. > could you check using xrandr to see if you can get 1900x1200 in Intrepid in > above testing? and if so, does it work properly if you set it to 1900x1200, and > would you please attach the reg_dump after setting it to 1900x1200? thanks. ping ~ Another hint Audio Output Enable bit is disable in good case , enable in bad case.
Created attachment 27924 [details] This is the intel dump on Intrepid using the native resolution of the LCD screen as requested
Created attachment 27966 [details] pleaset try the patch on your machine in UMS mode, thanks. (In reply to comment #44) > Created an attachment (id=27924) [details] > This is the intel dump on Intrepid using the native resolution of the LCD > screen as requested when you set 1920x1200 on Intrepid, what's result, work or not ? if it works fine please try the debug patch. In this patch I enable audio for HDMI against Intrepid. If by this patch your Intrepid does not work on 1920x1200, I think we find the root cause. Thanks Ma Ling
ping~ Bryce,would you please help to ping the downstream bug reporter? thanks.
ping~, Bryce?
Downstream has been pinged since 2009/05, and again today.
Hello Guys: Sorry for the delay but I had a family crisis I had to deal with. Anyhow, after much trying I can confirm that this patch causes the same shifting I am seeing with Jaunty and Karmic. In other words, this patch breaks the display and causes it to shift in intrepid. Let me know what you need next. (In reply to comment #45) > Created an attachment (id=27966) [details] > pleaset try the patch on your machine in UMS mode, thanks. > > (In reply to comment #44) > > Created an attachment (id=27924) [details] [details] > > This is the intel dump on Intrepid using the native resolution of the LCD > > screen as requested > > when you set 1920x1200 on Intrepid, what's result, work or not ? > if it works fine please try the debug patch. In this patch I enable audio for > HDMI against Intrepid. > If by this patch your Intrepid does not work on 1920x1200, I think we find the > root cause. > > Thanks > Ma Ling >
thanks for the test. From the test it seems that it can work well if audio is disabled in HDMI. But from the EDID we know that the audio block can be found in extension EDID block and it is supported by HDMI monitor. Will you please try to switch to another resolution and see whether the issue still exists? Please use the following command to switch to another resolution(1920x1080) . a. Add a new mode. xrandr --newmode 1920x1080 148.5 1920 2008 2052 2200 1080 1084 1089 1125 "+HSync" "+VSync" b. xrandr --addmode HDMI-2 1920x1080 c. xrandr --output HDMI-2 --mode 1920x1080 Will you please also attach the register dump after changing to 1920x1080? Thanks.
(In reply to comment #51) > thanks for the test. > From the test it seems that it can work well if audio is disabled in HDMI. > But from the EDID we know that the audio block can be found in extension EDID > block and it is supported by HDMI monitor. I would like to point out that the screen has an HDMI input but the laptop I am hooking it to has a DVI outpot. Could that be the source of the problem? > > Will you please try to switch to another resolution and see whether the issue > still exists? Please use the following command to switch to another > resolution(1920x1080) . I tried multiple resolutions before on Jaunty (which didn't work) and I always had the same problem. The tests you want me to do below, are they with Intrepid? and if so, with or without the AUDIO patch that breaks it. Please let me know. > a. Add a new mode. > xrandr --newmode 1920x1080 148.5 > 1920 2008 2052 2200 > 1080 1084 1089 1125 > "+HSync" "+VSync" > b. xrandr --addmode HDMI-2 1920x1080 > c. xrandr --output HDMI-2 --mode 1920x1080 > > Will you please also attach the register dump after changing to 1920x1080? > Thanks. >
(In reply to comment #52) > (In reply to comment #51) > > thanks for the test. > > From the test it seems that it can work well if audio is disabled in HDMI. > > But from the EDID we know that the audio block can be found in extension EDID > > block and it is supported by HDMI monitor. > > I would like to point out that the screen has an HDMI input but the laptop I am > hooking it to has a DVI outpot. Could that be the source of the problem? > > might be. does your monitor has DVI interface? if so, you might want to try with it. And, does you monitor has any built-in speaker or audio jacket that you can connect a speaker to? > > The tests you want me to do below, are they with Intrepid? and if so, with or > without the AUDIO patch that breaks it. Please let me know. > yes. with the audio patch applied on Intrepid. thanks.
(In reply to comment #53) > (In reply to comment #52) > > (In reply to comment #51) > > > thanks for the test. > > > From the test it seems that it can work well if audio is disabled in HDMI. > > > But from the EDID we know that the audio block can be found in extension EDID > > > block and it is supported by HDMI monitor. > > > > I would like to point out that the screen has an HDMI input but the laptop I am > > hooking it to has a DVI outpot. Could that be the source of the problem? > > > > > > might be. does your monitor has DVI interface? if so, you might want to try > with it. The monitor has component video, VGA, and HDMI. There are no speakers attached to it However, it does have a 3.5mm headphone jack for audio out. I guess it gathers the audio from the HDMI connection and pushes it to the 3.5mm plug. This way you can connect speakers or headphones or whatever. > > And, does you monitor has any built-in speaker or audio jacket that you can > connect a speaker to? > > > > > The tests you want me to do below, are they with Intrepid? and if so, with or > > without the AUDIO patch that breaks it. Please let me know. > > > > yes. with the audio patch applied on Intrepid. thanks. I will do that in a couple of days. >
(In reply to comment #54) > > The monitor has component video, VGA, and HDMI. There are no speakers attached > to it However, it does have a 3.5mm headphone jack for audio out. > does your dock station has HDMI output? if so, can you try to connect it directly to HDMI input of your monitor?
Created attachment 29876 [details] [review] enable sending the NULL packet for HDMI port Will you please try the debug patch and see whether the issue still exists? Thanks.
Sorry but the back of my docking station has only VGS and DVI (no HDMI). The LCD has Component (RBG), HDMI, (In reply to comment #55) > (In reply to comment #54) > > > > The monitor has component video, VGA, and HDMI. There are no speakers attached > > to it However, it does have a 3.5mm headphone jack for audio out. > > > > does your dock station has HDMI output? if so, can you try to connect it > directly to HDMI input of your monitor? >
Sorry for the delay: I thought the patch was to go against the intrepid driver and not the Karmic one, i am using. Any how, I figured it out and gotten it compiled and test resultts are here. 1. The issues didn't get fixed. the screen is still shifted to the left but this time the shift is also to the right. See screenshot here http://www.flickr.com/photos/situmam/4001581205/sizes/l/ 2. Changing the resolution doesn't fix it either. the screen is cutt off on the right, left and top sides as per screenshot Attached is the reg-dump for this patched driver. Let me know what else needs to be done. (In reply to comment #56) > Created an attachment (id=29876) [details] > enable sending the NULL packet for HDMI port > > Will you please try the debug patch and see whether the issue still exists? > Thanks. >
Created attachment 30272 [details] reg dump
(In reply to comment #59) > Created an attachment (id=30272) [details] > reg dump From the register dump it seems that you don't try the patch in comment #56. Right? Please try to apply it and see whether it can work for you. Thanks. >
Created attachment 30279 [details] [review] [KMS] enable the NULL packet during the vsync Will you please try the debug patch on the latest linux kernel(2.6.32-rc3/4) and see whether it can work? Please do the test with KMS enabled. Please attach the output of xrandr, intel_reg_dump, dmesg. Thanks.
I was almost sure I got it but this time, I double checked. Attached is the output of the dump. Called it "with_nullpacket_patch.txt" (In reply to comment #60) > (In reply to comment #59) > > Created an attachment (id=30272) [details] [details] > > reg dump > From the register dump it seems that you don't try the patch in comment #56. > Right? Please try to apply it and see whether it can work for you. > Thanks. > > >
Created attachment 30286 [details] Dump with null packet patch
(In reply to comment #63) > Created an attachment (id=30286) [details] > Dump with null packet patch > Please do the test with KMS enabled (CONFIG_DRM_I915_KMS should be enabled in kernel configuration). And after the test, please attach the output of dmesg, Xorg.0.log, xrandr thanks.
I have tested with the latest Karmic release, which does have the CONFI_DRM_I915_KMS enabled and the new null patch with no change in problem. (In reply to comment #64) > (In reply to comment #63) > > Created an attachment (id=30286) [details] [details] > > Dump with null packet patch > > > Please do the test with KMS enabled (CONFIG_DRM_I915_KMS should be enabled in > kernel configuration). > And after the test, please attach the output of dmesg, Xorg.0.log, xrandr Attached comment_64_dmesg.txt, comment_64_xrandr.txt and comment_64_Xorg.0.log > > thanks. >
Created attachment 30601 [details] dmesg after reboot
Created attachment 30602 [details] Xorg.log
Created attachment 30603 [details] xrandr output
Hello Guys: An interesting observation today. I booted MS Windows, Evil I know :), and plugged in the monitor. I noticed that the problem still exists even though I am using Ms Windows Vista Home Basic edition. not sure if that is worth anything for you?
(In reply to comment #69) > Hello Guys: > > An interesting observation today. I booted MS Windows, Evil I know :), and > plugged in the monitor. I noticed that the problem still exists even though I > am using Ms Windows Vista Home Basic edition. It is very interesting that windows can't work well, either. Maybe this issue is related with the display device. So it will be better that you connect this monitor by using DVI-cable. It will be great that you can try another monitor and see whether this issue still exists. As windows can't work well either, IMO it is unnecessary to continue investigating this issue. BTW: we can't reproduce this issue on several display devices. And we can't buy the LG246WP monitor. So this bug will be rejected. > not sure if that is worth anything for you? >
(In reply to comment #70) I agree that it is indeed odd that this issue exists in Windows Vista. I think the problem stems from the docking station connection that I am using, which has DVI and the LCD monitor having only HDMI. Regardless, I will continue to try updates to the intel Xorg driver and see. For now, I agree with the current wonfix status. Thank you for supporting me in trying to resolve this issue. > (In reply to comment #69) > > Hello Guys: > > > > An interesting observation today. I booted MS Windows, Evil I know :), and > > plugged in the monitor. I noticed that the problem still exists even though I > > am using Ms Windows Vista Home Basic edition. > It is very interesting that windows can't work well, either. > Maybe this issue is related with the display device. > So it will be better that you connect this monitor by using DVI-cable. > > It will be great that you can try another monitor and see whether this issue > still exists. > > As windows can't work well either, IMO it is unnecessary to continue > investigating this issue. > BTW: we can't reproduce this issue on several display devices. And we can't buy > the LG246WP monitor. > > So this bug will be rejected. > > not sure if that is worth anything for you? > > >
For what it's worth, I have the same monitor (LG L246WP) and am experiencing this issue on the currently daily builds for Lucid. This is a desktop system running an ATI Radeon HD 4650 (R730PRO). The monitor works fine (but fuzzy) over DVI->VGA, and shows the same cropping as comment #58. Screenshot of expected output: http://media.thebadness.org/starbuck/screenshot.png Picture of actual output: http://media.thebadness.org/starbuck/picture.jpg This monitor has *worked fine* over DVI->HDMI for several years on my old desktop (Radeon 9600XT), and also *works fine* with this new system running Windows 7. I am not re-opening this bug at this moment, I would like to leave that up to someone more familiar with this system. If you choose to leave the status as-is, please let me know so that I can file a new bug report on Launchpad. Regards, -Scott
Here is my EDID data running from Radeon HD 4650, DVI->HDMI, under Lucid daily build 29-Mar-2010: DVI: 00ffffffffffff001e6d3f5662100100 011101038e342078ea5ad5a7564b9b24 135054a54b00a940818fb300814f8180 010101010101283c80a070b023403020 3600b0441100001a483f403062b03240 40c01300b0441100001e000000fd0038 4b1e5311000a202020202020000000fc 004c32343657500a202020202020013a VGA: 00ffffffffffff001e6d3e5662100100 011101030e342078ea5ad5a7564b9b24 135054a54b00a940818fb300814fd1c0 904001010101283c80a070b023403020 360006442100001a483f403062b03240 40c0130006442100001e000000fd0038 4b1e5311000a202020202020000000fc 004c32343657500a2020202020200092
I have the same problem. My current setup: Distribution: Ubuntu 10.04 (2.6.32-22) Display: LG L245WP Adapter: Radeon HD 4830 (Rv770 LE) The display works just fine with Windows XP and older Linux distributions. My current workaround is to add the nomodeset kernel parameter. Without KMS I have no problems. Fedora has a similar bug at https://bugzilla.redhat.com/show_bug.cgi?id=572480
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.