Can't get higher resolution than 1280x720 w/ intel driver

Bug #471233 reported by David Laurell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: xorg

My plasma screen does only display the whole resolution if I choose 1024x768 or 1386x768 (hd-ready). The highest resolution I can choose is 1280x720. I really want to be able to choose the maximum resolution my screen supports.

When choosing 1280x720, a big chunk is cut of on the edges of the screen. When switching to terminal via CTRL+ALT+F1, it looks the same.

The 1386x768 resolution did work Ubuntu 8.10. In 9.04 it didn't. I have installed a clean installation of Ubuntu 9.10.

Some help would be nice, like a workaround with xorg or something in the meantime.

/David

ProblemType: Bug
Architecture: i386
CheckboxCommand: resolution_test
CheckboxData: I want 1386x768 or hd-ready resolution. The computer is connected to our plasma screen through HDMI
CheckboxDescription:
 This display is using the following resolution:

 $output

 Is this acceptable for your display?
CheckboxTest: resolution
Date: Mon Nov 2 17:03:56 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Shuttle Inc SG33
Package: xorg 1:7.4+3ubuntu7
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=235a3418-9ed9-4c0b-a6d7-b6aedaba741d ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu7
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: xorg
Tags: checkbox-bug
Uname: Linux 2.6.31-14-generic i686
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
XorgLogOld: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log.old'
XsessionErrors:
 (gnome-settings-daemon:1704): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1704): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:1806): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1804): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (nautilus:1883): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
dmi.bios.date: 04/25/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: FG33
dmi.board.vendor: Shuttle Inc
dmi.board.version: V10
dmi.chassis.type: 3
dmi.chassis.vendor: Shuttle Inc
dmi.chassis.version: G5
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd04/25/2008:svnShuttleInc:pnSG33:pvrV10:rvnShuttleInc:rnFG33:rvrV10:cvnShuttleInc:ct3:cvrG5:
dmi.product.name: SG33
dmi.product.version: V10
dmi.sys.vendor: Shuttle Inc
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-14-generic

Revision history for this message
David Laurell (daverix) wrote :
Revision history for this message
Bryce Harrington (bryce) wrote :

Thank you for seeking to improve Ubuntu. It seems you have filed a bug
against X using the new System Testing utility. Unfortunately, this tool
is filing bugs without collecting sufficient information to properly
diagnose the issues. I wish we could reply to every report to guide you
to gather the correct information, but it happens that so many people
are using this testing feature to file bug reports that we simply cannot
keep up with the influx. I'm replying in bulk so I can get everyone
pointed into a direction most likely to result in getting you a useful
workaround and us a complete bug report that can be solved.

Most of these problems describe issues that have documented
troubleshooting procedures, so perhaps the most helpful thing I can
do is point you to them:

  http://wiki.ubuntu.com/X/Troubleshooting

These guides explain why things break the way they do, and in some cases
provide workarounds.

I would ask that you first go through the appropriate guide for your
problem, particularly if you are having problems with resolution,
crashes, fonts, or blank screen issues, and then file a bug report using
the following command:

   ubuntu-bug xorg

This collects more detailed information than the System Testing tool
does. Please also write a detailed explanation, indicating when you
first discovered the problem, analysis steps you've done, workarounds
that work, and so on.

Changed in xorg (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.