Bug 65378 - Screen resolution (definition) failure with Intel G33 and monitor Iiyama E1902S
Summary: Screen resolution (definition) failure with Intel G33 and monitor Iiyama E1902S
Status: RESOLVED NOTOURBUG
Alias: None
Product: freedesktop.org
Classification: Unclassified
Component: Bugzilla (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Rodrigo Vivi
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-04 21:13 UTC by David
Modified: 2013-10-21 12:14 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
2013-06-04 Xog logs (10.66 KB, application/zip)
2013-06-04 21:13 UTC, David
Details
Reply to comment #1 (to Rodrigo Vivi 2013-06-27 19:52:23 UTC) (10.43 KB, text/html)
2013-06-29 22:16 UTC, David
Details
dmesg output (with boot option "drm.debug=0x06") (71.23 KB, text/plain)
2013-10-08 13:12 UTC, David
Details

Description David 2013-06-04 21:13:38 UTC
Created attachment 80310 [details]
2013-06-04 Xog logs

-----------------------
In reference to my question in : https://01.org/linuxgraphics/node/86

Hello, I wish to report this issue. I'm not sure if this is related to Linux graphics or to my Linux distribution.

OS : Ubuntu v13.04, 32 bits ( ubuntu-13.04-desktop-i386.iso ).

Screen : Iiyama E1902S screen resolution is 1280x1024, but is detected as 1024x768.

Computer : desktop HP dx2400 microtower series, graphics chipset is « Intel G33/G31 chipset family ».

I am a beginner on Linux, but a expert on Windows. I may provide more technical informations or tests if you need. Regards.
---------------------
Comment 1 Rodrigo Vivi 2013-06-27 19:52:23 UTC
Could you please post output of this command:

lspci -nn | grep VGA

Also attach:
-- dmesg output (with boot option "drm.debug=0x06")
-- xorg.conf (if you changed any default options)
-- output of "xrandr --verbose" for display mode issue
Comment 2 David 2013-06-29 22:12:47 UTC
(In reply to comment #1)

I attach the output I could get, in a LibreOffice file.
Comment 3 David 2013-06-29 22:16:01 UTC
Created attachment 81726 [details]
Reply to comment #1 (to Rodrigo Vivi 2013-06-27 19:52:23 UTC)
Comment 4 Rodrigo Vivi 2013-09-17 14:56:42 UTC
From: http://askubuntu.com/questions/19486/how-do-i-add-a-kernel-boot-parameter

1.Start your system and wait for the GRUB menu to show (if you don't see a GRUB menu, press and hold the left Shift key right after starting the system).
2.Now highlight the kernel you want to use (usually first option), and press the e key. You should be able to see and edit the commands associated with the highlighted kernel.
3.Go down to the line starting with linux and add your parameter drm.debug=0xe to its end.
4.Now press F10 to boot.
Comment 5 David 2013-10-08 13:12:22 UTC
Created attachment 87277 [details]
dmesg output (with boot option "drm.debug=0x06")
Comment 6 Rodrigo Vivi 2013-10-17 12:47:58 UTC
Hi David,

It seems your monitor isn't sending a proper EDID witch is the data block with supported resolutions info.
I guess the only alternative for you is to manually add this mode you belive to be monitor maximum manually with
xrandr --newmode "1280x1024" 109.00  1280 1368 1496 1712  1024 1027 1034 1063 -hsync +vsync
xrandr --addmode default "1280x1024"
xrandr -s "1280x1024"

If this works properly go ahead and add the mode to your /etc/X11/xorg.conf file.

I'm closing this bug here, so if you need more help to add this configuration please post a comment at https://01.org/linuxgraphics/node/86

Thanks,
Rodrigo.
Comment 7 David 2013-10-21 09:31:39 UTC
Thank you for trying :)

At the second line ("xrandr --addmode default "1280x1024"") I get the following reply " xrandr: cannot find output "default" ", is there a mistake ?
Comment 8 David 2013-10-21 12:14:40 UTC
I found the solution (in askubuntu.com), I had to type xrandr then look at the name of the screen ("VGA1 connected") and replace the word "default" by "VGA1". It is working, this monitor supports 1280x1024.


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.