Bug 14935 - How to get 1200x800 on Intel 965GM with Xorg on Sony Vaio?
Summary: How to get 1200x800 on Intel 965GM with Xorg on Sony Vaio?
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Hong Liu
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks: 15000
  Show dependency treegraph
 
Reported: 2008-03-10 06:40 UTC by G. Georgiev
Modified: 2008-04-11 20:26 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg log file (57.36 KB, text/plain)
2008-03-10 06:40 UTC, G. Georgiev
no flags Details
Xorg log with ModeDebug YES (84.91 KB, text/plain)
2008-03-16 06:14 UTC, G. Georgiev
no flags Details
915resolution -l log file (1.31 KB, text/plain)
2008-03-16 06:16 UTC, G. Georgiev
no flags Details
dmesg output from the computer (24.01 KB, text/plain)
2008-03-16 06:17 UTC, G. Georgiev
no flags Details
xorg.conf file (4.30 KB, text/plain)
2008-03-16 06:18 UTC, G. Georgiev
no flags Details
xrandr report (4.50 KB, text/plain)
2008-03-16 06:19 UTC, G. Georgiev
no flags Details
Loaded kernel modules list (3.11 KB, text/plain)
2008-03-16 06:37 UTC, G. Georgiev
no flags Details
Xorg.0.log with 1280x800 resolution just fine (76.99 KB, text/plain)
2008-03-23 16:33 UTC, G. Georgiev
no flags Details
fix i9xx ssc calc (524 bytes, patch)
2008-03-23 19:20 UTC, Hong Liu
no flags Details | Splinter Review
Xorg log file with the patch applied (102.35 KB, text/plain)
2008-04-10 18:43 UTC, G. Georgiev
no flags Details
Xorg log file with the patch applied (107.87 KB, text/plain)
2008-04-11 10:11 UTC, G. Georgiev
no flags Details

Description G. Georgiev 2008-03-10 06:40:13 UTC
Created attachment 15001 [details]
Xorg log file

Hello,

  I did recently purchase a Sony Vaio VGN-NR160Q with an Intel 965GM video card, and I can not yet make Xorg work on full screen - it starts on 1024x768 instead of 1200x800. Does someone have an idea how I can use the entire screen?

  What did I try:
  - Use 915resolution;
  - Switch to 16bpp, as xorg does not support 32bpp.
  - Tried intel and i810 drivers; look to be the same.
  - I also have intelfb and i810fb drivers loaded in the kernel for the framebuffer. They should not affect anything, I believe.

  I attach the xorg.conf, 915resolution detected modes, and Xorg.0.log files. Below are few lines of interest:

  Any help appreciated,
  Thanks,
  G. Georgiev


  --------- 915resolution -l: --------------
Intel 800/900 Series VBIOS Hack : version 0.5.3
Chipset: 965GM
BIOS: TYPE 1
Mode 6f : 1280x800, 8 bits/pixel
Mode 70 : 1280x800, 16 bits/pixel
Mode 71 : 1280x800, 32 bits/pixel

  --------- /etc/X11/xorg.conf: -----------
Section "Device"
    Identifier     "intel"
    Driver         "intel"
EndSection
Section "Screen"
    Identifier     "Default Screen"
    Device         "intel"
    Monitor        "Monitor0"
    DefaultDepth    16
     SubSection     "Display"
        Depth       16
        Modes      "1280x800"
    EndSubSection
    SubSection     "Display"
        Depth       24
        Modes      "1280x800"
    EndSubSection
EndSection

  ----------- Xorg.0.log: -------------
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Debian (xorg-server 2:1.3.0.0.dfsg-12lenny2)
Current Operating System: Linux vaio 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686

(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
        i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
        E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, 965G, 965Q, 946GZ,
        965GM, 965GME/GLE, G33, Q35, Q33
(II) Primary Device is: PCI 00:02:0
(--) Assigning device section with no busID to primary device
(WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found
(--) Chipset 965GM found

(**) intel(0): Depth 16, (--) framebuffer bpp 16
(==) intel(0): RGB weight 565
(==) intel(0): Default visual is TrueColor
(II) intel(0): Integrated Graphics Chipset: Intel(R) 965GM
(--) intel(0): Chipset: "965GM"
(--) intel(0): Linear framebuffer at 0xD0000000
(--) intel(0): IO registers at addr 0xFC000000
(II) intel(0): 2 display pipes available.

(II) intel(0): Not using default mode "1280x800" (exceeds panel dimensions)
Comment 1 Hong Liu 2008-03-10 18:46:37 UTC
Please turn on modedebug option and repost the xorg.log.

Thanks,
Hong
Comment 2 Michael Fu 2008-03-11 01:43:37 UTC
Georgiev, please also take a look at http://www.intellinuxgraphics.org/how_to_report_bug.html on what info needed for bug fixing. thanks.
Comment 3 G. Georgiev 2008-03-16 06:14:37 UTC
Created attachment 15177 [details]
Xorg log with ModeDebug YES
Comment 4 G. Georgiev 2008-03-16 06:16:31 UTC
Created attachment 15178 [details]
915resolution -l log file
Comment 5 G. Georgiev 2008-03-16 06:17:28 UTC
Created attachment 15179 [details]
dmesg output from the computer
Comment 6 G. Georgiev 2008-03-16 06:18:20 UTC
Created attachment 15180 [details]
xorg.conf file
Comment 7 G. Georgiev 2008-03-16 06:19:12 UTC
Created attachment 15181 [details]
xrandr report
Comment 8 G. Georgiev 2008-03-16 06:36:30 UTC
  Hi Hong,

  Please find attached requested log files, if need for more, you can contact me directly at ggeorgiev-at-videotron.ca or via this bug tracking facility. 

  Computer description:
  Sony Vaio portable, a very recent purchase,I had not yet enough time to check all subsystems and functionalities under linux, but I will gladly work with your side for the graphic adapter problem.

  I tried to run X with the framebuffer driver loaded, as well as without it, same result. The only difference is that without the framebuffer I can not switch to the console - CTRL_ALT_F1 makes screen greenish or pink, or other color and there is no way out. No switch back to X either. CTRL_ALT_DEL reboots the system however, as well as init 6 (typed blindly). Exiting X normally also jams the screen without the frame buffer. No such problems however when fb (i810fb) is loaded, switch to the console and exiting X works. 

  Thanks,
  G. Georgiev
Comment 9 G. Georgiev 2008-03-16 06:37:39 UTC
Created attachment 15183 [details]
Loaded kernel modules list
Comment 10 Hong Liu 2008-03-16 19:23:57 UTC
Which Linux distribution are you using? Would you please try a newer X server and Intel driver?

You are using the vesafb to program the graphic driver and this makes the Xorg 2D intel driver failed to detect the correct resolution of your LVDS output.

Trying a newer X server and Intel 2d driver may fix your VT switch problem, and please try it without any kernel framebuffer driver loaded (including vesafb, intelfb).

Comment 11 G. Georgiev 2008-03-23 16:33:18 UTC
Created attachment 15407 [details]
Xorg.0.log with 1280x800 resolution just fine
Comment 12 G. Georgiev 2008-03-23 16:34:41 UTC
  Hello,
  
  I was able to get full resolution for my Sony Vaio VGN-NR160Q portable by installing latest updates to my debian distribution by prepending the 'testing' branch before the main one, like:
deb http://gulus.usherbrooke.ca/debian/ testing main contrib non-free
what came very handy, in saving the build of the Xorg compile environment. 

  I removed the frame buffer, and it runs fine now. No need of 915resolution either. No frame buffer, however, so no nice images on start-up.

  For record, I attach the Xorg.0.log file here with the screen on 1280x800. Few extracts are just below.

  I would like to thank for your help again, and I will leave your side to mark this bug as resolved.

  Everything the best,
  G. Georgiev.


---------- Xorg.0.log extract ----------

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Debian (xorg-server 2:1.3.0.0.dfsg-12lenny2)
Current Operating System: Linux vaio 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686
Build Date: 19 January 2008

(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
        i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
        E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, 965G, 965Q, 946GZ,
        965GM, 965GME/GLE, G33, Q35, Q33
(II) Primary Device is: PCI 00:02:0
(--) Assigning device section with no busID to primary device
(WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found
(--) Chipset 965GM found


Comment 13 Hong Liu 2008-03-23 19:20:17 UTC
Created attachment 15414 [details] [review]
fix i9xx ssc calc

Hi, G.Georgiev

I've found a clock calculation problem in our driver, the correct dotclock for your LVDS output should be 70.71MHz while we got a 67.89MHz.

(II) intel(0): probed mode:
(II) intel(0): Modeline "1280x800"x0.0   67.89  1280 1296 1344 1430  800 804 807 825 (47.5 kHz)

But currently your LVDS display seems OK with this mode.
Would you please try the attached patch to see if it breaks anything?

Thanks,
Hong
Comment 14 Wang Zhenyu 2008-04-06 19:07:53 UTC
Georgiev, could you tell us if Hong's patch works for you or not?
Comment 15 G. Georgiev 2008-04-10 18:43:17 UTC
Created attachment 15826 [details]
Xorg log file with the patch applied

Sorry for the delay - I was really busy recently, had to work in the evenings and on the week-end.
Comment 16 Hong Liu 2008-04-10 18:59:04 UTC
Thanks for the test, but it seems your X server still loads the old driver.
(II) intel(0): probed mode:
(II) intel(0): Modeline "1280x800"x0.0   67.89  1280 1296 1344 1430  800 804 807 825 (47.5 kHz)

We want to change the 67.89 to 70.71 with the patch.

Would you please try to see if the file /usr/lib/xorg/modules/drivers//intel_drv.so is really the one you compiled with patch applied?
Comment 17 G. Georgiev 2008-04-11 10:11:07 UTC
Created attachment 15837 [details]
Xorg log file with the patch applied

   Hi,

        OK, I forgot --prefix=/usr and installation went to /usr/local and the X server did not load the updated driver. There is the 
log with your patch running.

        Thanks,
        George.
Comment 18 Wang Zhenyu 2008-04-11 20:24:52 UTC
So this bug is gone right? as Hong's patch is upstream, we should close this one.


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.