Display limited to 800x600 in Ubuntu 9.10 on Intel 82G35 Display Controller

[apjjr]

Binary package hint: xorg

Run U9.10 from CD or upgrade from U9.04 and display is limited to 800x600. 9.04 handled this motherboard (DG35EC) without incident.

lspci -v displays:
00:00.0 Host bridge: Intel Corporation 82G35 Express DRAM Controller (rev 03)
        Subsystem: Intel Corporation Device d701
        Flags: bus master, fast devsel, latency 0
        Capabilities: [e0] Vendor Specific Information <?>
        Kernel driver in use: agpgart-intel
        Kernel modules: intel-agp

00:02.0 VGA compatible controller: Intel Corporation 82G35 Express Integrated Graphics Controller (rev 03)
        Subsystem: Intel Corporation Device d701
        Flags: bus master, fast devsel, latency 0, IRQ 28
        Memory at e0200000 (32-bit, non-prefetchable) [size=1M]
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at 2440 [size=8]
        Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
        Capabilities: [d0] Power Management version 2
        Kernel driver in use: i915
        Kernel modules: i915

00:02.1 Display controller: Intel Corporation 82G35 Express Integrated Graphics Controller (rev 03)
        Subsystem: Intel Corporation Device d701
        Flags: bus master, fast devsel, latency 0
        Memory at e0100000 (32-bit, non-prefetchable) [size=1M]
        Capabilities: [d0] Power Management version 2

ProblemType: Bug
Architecture: i386
CheckboxCommand: resolution_test
CheckboxDescription:
 This display is using the following resolution:

 $output

 Is this acceptable for your display?
CheckboxTest: resolution
Date: Sun Nov 1 23:49:48 2009
DistroRelease: Ubuntu 9.10
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: xorg 1:7.4+3ubuntu7
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz 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'
dmi.bios.date: 02/03/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: ECG3510M.86A.0112.2009.0203.1136
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DG35EC
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE29266-208
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrECG3510M.86A.0112.2009.0203.1136:bd02/03/2009:svn:pn:pvr:rvnIntelCorporation:rnDG35EC:rvrAAE29266-208:cvn:ct3:cvr:
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-14-generic

[Bryce Harrington (bryce)]

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.

[apjjr (alex-ourwoods)]

Bryce Harrington 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
>
>
Bryce,
Thank you for redirecting me to the right place. I am not a linux guru
and need all the help I can get when in trouble. I always seem to find
it in the linux community, though.
Just to put this to bed, I have included my manually assembled xorg.conf
file to fix my issue with the Intel board and driver.
*** xorg.conf ***
Section "Monitor"
    Identifier "Monitor0"
    VendorName "Viewsonic"
    ModelName "VA1703wb"
    HorizSync 24.0 - 70.0
    VertRefresh 50.0 - 75.0
    DisplaySize 365 228
EndSection

Section "Device"
  Option "NoDDC" "true"
    Option "IgnoreEDID" "true"
    Identifier "Card0"
    Driver "intel"
    VendorName "Intel Corporation"
    BoardName "82G35 Express Integrated Graphics Controller"
    BusID "PCI:0:2:0"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
        Depth 24
        Modes "1440x900" "1360x768" "1152x864" "1024x768" "800x600"
"640x480"
    EndSubSection
EndSection
***

--
Ourwoods.org
 Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. - Albert Einstein (275)

[Doug Hindle (douglashindle)]

Many thanks to the comment from apjjr written on 2009-11-07.

I copied the above sections to my /etc/X11/xorg.conf replacing the similar sections and all the available resolutions even beyond the ones written were available as options. I appreciate the effort and the post.