[i945G] A screen resolution problem of obtaining 1024x768

Bug #299007 reported by roshanjose
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Invalid
Undecided
Geir Ove Myhr

Bug Description

Binary package hint: xserver-xorg-video-intel

I had not much of a problem with screen resolution while working with Hardy Heron until lately when i upgraded my system to intrepid ibex. The problem now is that I dont get a resolution that matches my screen perfectly. I have tried all possible combinations of the resolution and refresh rates but still no use...

Details of my system

My motherboard: D945GCL

roshan@roshan-desktop:~$ lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)

roshan@roshan-desktop:~$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 6
model name : Intel(R) Pentium(R) D CPU 3.00GHz
stepping : 5
cpu MHz : 2400.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 6
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc pebs bts nopl pni monitor ds_cpl est cid cx16 xtpr lahf_lm
bogomips : 5988.63
clflush size : 64
cache_alignment : 128
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 15
model : 6
model name : Intel(R) Pentium(R) D CPU 3.00GHz
stepping : 5
cpu MHz : 2400.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 6
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc pebs bts nopl pni monitor ds_cpl est cid cx16 xtpr lahf_lm
bogomips : 5988.83
clflush size : 64
cache_alignment : 128
address sizes : 36 bits physical, 48 bits virtual
power management:

# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# Note that some configuration settings that could be done previously
# in this file, now are automatically configured by the server and settings
# here are ignored.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Device"
 Identifier "Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)"
Driver "intel"
 Option "UseFBDev" "true"
EndSection

Section "Monitor"
 Identifier "LG"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "LG"
 Device "Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)"
SubSection "Display"
Modes "1680x1050" "1280x1024" "1280x960" "1152x864" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection
EndSection

This was not the code originally. I did add my Device configuration and tried adding up the subsystems....

then i tried adding the resolution through command

roshan@roshan-desktop:~$ cvt 1024 768 60
# 1024x768 59.92 Hz (CVT 0.79M3) hsync: 47.82 kHz; pclk: 63.50 MHz
Modeline "1024x768_60.00" 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync

roshan@roshan-desktop:~$ xrandr --newmode 1024x768_60.00" 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync
> xrandr --addmode VGA 1024x768_60.00

This is it. I never knew how to to get out of this and get the right resolution. I concluded myself that 1024x768 fits best because it works fine for my Windows

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

[This is an automated message]

Hi joro-manage,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

Changed in xserver-xorg-video-intel:
status: New → Incomplete
Revision history for this message
roshanjose (joro-manage) wrote :
Download full text (10.1 KiB)

roshan@roshan-desktop:~$ lspci -vvnn
00:00.0 Host bridge [0600]: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub [8086:2770] (rev 02)
 Subsystem: Intel Corporation Device [8086:4c43]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
 Latency: 0
 Capabilities: <access denied>
 Kernel driver in use: agpgart-intel
 Kernel modules: intel-agp

00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02)
 Subsystem: Intel Corporation Device [8086:4c43]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 16
 Region 0: Memory at 50100000 (32-bit, non-prefetchable) [size=512K]
 Region 1: I/O ports at 20e0 [size=8]
 Region 2: Memory at 40000000 (32-bit, prefetchable) [size=256M]
 Region 3: Memory at 50180000 (32-bit, non-prefetchable) [size=256K]
 Capabilities: <access denied>
 Kernel modules: intelfb

00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller [8086:27d8] (rev 01)
 Subsystem: Intel Corporation Device [8086:0204]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 22
 Region 0: Memory at 501c0000 (64-bit, non-prefetchable) [size=16K]
 Capabilities: <access denied>
 Kernel driver in use: HDA Intel
 Kernel modules: snd-hda-intel

00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 [8086:27d0] (rev 01)
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
 Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
 BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
  PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
 Capabilities: <access denied>
 Kernel driver in use: pcieport-driver
 Kernel modules: shpchp

00:1c.2 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 [8086:27d4] (rev 01)
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
 Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
 BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
  PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
 Capabilities: <a...

Revision history for this message
roshanjose (joro-manage) wrote :
Revision history for this message
Geir Ove Myhr (gomyhr) wrote : Re: [945G] A screen resolution problem of obtaining 1024x768

Can you try and remove your xorg.conf? Xorg nowadays figures out resolutions pretty much on its own, and then having resolution stuff in xorg.conf can be confusing. Could you report back on whether removing xorg.conf changes anything and upload the Xorg.0.log you get when running Xorg without the config file?

Revision history for this message
roshanjose (joro-manage) wrote :

how can i remove xorg.conf file......do i have to simply empty it??? i mean just delete its contents

Revision history for this message
Geir Ove Myhr (gomyhr) wrote :

Remove the file so that there is no file called /etc/X11/xorg.conf. The bad solution is `sudo rm /etc/X11/xorg.conf` (deletes the file), the better solution is `sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup` (moves the file, so that you can move it back later if you wish).

When the file is gone, Xorg will automatically create a "minimal" xorg.conf, but there will be no settings that can disturb the screen resolution setting process. Basically, this eliminates the potential for errors due to problems in xorg.conf.

Revision history for this message
roshanjose (joro-manage) wrote :

soon after deleting the file according to your second method..i saved the copy of the xorg.0.log onto the desktop and here's the attachement...

Revision history for this message
roshanjose (joro-manage) wrote :

And one more thing i forgot to mention is that i never installed any seperate hardware drivers on ubuntu.....

Revision history for this message
Geir Ove Myhr (gomyhr) wrote :

I guess I should have been a bit more specific... The X server only reads or looks for xorg.conf on startup, so after you removed/moved the file you would need to restart the X server. THEN, a new Xorg.0.log will be written. The one you uploaded looks basically the same as the previous one. Here is a detailed recipe:

1. Open a terminal
2. Type `rm /etc/X11/xorg.conf` (just to make sure it's gone, you still have the backup)
3. Log out (this will restart the X server)
4. Log in
5. Copy /var/log/Xorg.0.log and upload it here

Do you still have the same problem after doing this?
What is the output of the command `xrandr` at this point?

Revision history for this message
roshanjose (joro-manage) wrote :
Download full text (47.1 KiB)

I used rm /etc/X11/xorg.conf and then logged off and signed back in.

Then I edited the Xorg.0.log file...these are the contents of xorg.0.log:

X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-16-server x86_64 Ubuntu
Current Operating System: Linux roshan-desktop 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:06 UTC 2008 x86_64
Build Date: 24 October 2008 09:06:49AM
xorg-server 2:1.5.2-2ubuntu3 (<email address hidden>)
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Nov 21 21:15:26 2008
(EE) Unable to locate/open config file
(II) Loader magic: 0x7b7320
(II) Module ABI versions:
 X.Org ANSI C Emulation: 0.4
 X.Org Video Driver: 4.1
 X.Org XInput driver : 2.1
 X.Org Server Extension : 1.1
 X.Org Font Renderer : 0.6
(II) Loader running on linux
(++) using VT number 7

(--) PCI:*(0@0:2:0) Intel Corporation 82945G/GZ Integrated Graphics Controller rev 2, Mem @ 0x50100000/524288, 0x40000000/268435456, 0x50180000/262144, I/O @ 0x000020e0/8
(II) Scanning /usr/share/xserver-xorg/pci directory for additional PCI ID's supported by the drivers
(II) Matched intel from file name intel.ids
(==) Using default built-in configuration (48 lines)
(==) --- Start of built-in configuration ---
 Section "Device"
  Identifier "Builtin Default intel Device 0"
  Driver "intel"
 EndSection
 Section "Screen"
  Identifier "Builtin Default intel Screen 0"
  Device "Builtin Default intel Device 0"
 EndSection
 Section "Device"
  Identifier "Builtin Default intel Device 0"
  Driver "intel"
 EndSection
 Section "Screen"
  Identifier "Builtin Default intel Screen 0"
  Device "Builtin Default intel Device 0"
 EndSection
 Section "Device"
  Identifier "Builtin Default i810 Device 0"
  Driver "i810"
 EndSection
 Section "Screen"
  Identifier "Builtin Default i810 Screen 0"
  Device "Builtin Default i810 Device 0"
 EndSection
 Section "Device"
  Identifier "Builtin Default vesa Device 0"
  Driver "vesa"
 EndSection
 Section "Screen"
  Identifier "Builtin Default vesa Screen 0"
  Device "Builtin Default vesa Device 0"
 EndSection
 Section "Device"
  Identifier "Builtin Default fbdev Device 0"
  Driver "fbdev"
 EndSection
 Section "Screen"
  Identifier "Builtin Default fbdev Screen 0"
  Device "Builtin Default fbdev Device 0"
 EndSection
 Section "ServerLayout"
  Identifier "Builtin Default Layout"
  Screen "Builtin Default intel Screen 0"
  Screen "Builtin Default intel Screen 0"
  Screen "Builtin Default i810 Screen 0"
  Screen "Builtin Default vesa Screen 0"
  Screen "Builtin Default fbdev Screen 0"
 EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default intel Screen 0" (0)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default intel Device 0"
(==) No monitor specified for screen "Builtin Default intel Screen 0...

roshanjose (joro-manage)
Changed in xserver-xorg-video-intel:
assignee: nobody → gomyhr
Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel:
status: Incomplete → Confirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automatic notice.]

We'd like to forward your bug upstream, however upstream requires
that you first test it against their newer driver code.

To save you the effort of building the driver from source, we've built
packages for the driver and its new dependencies.

So you have a couple options:

 1. Download and test .debs for intrepid, from:
     https://edge.launchpad.net/~intel-gfx-testing/+archive

 -or-

 2. Download and test the Jaunty alpha-2 (or newer) Live CD,
     (which includes a beta of the new xserver 1.6 as well).
     See http://cdimage.ubuntu.com/releases/9.04/ for ISOs

Thanks ahead of time! You can simply reply to this email to report your
findings.

P.S., if you wish to forward your bug upstream yourself, please follow
these directions to do so:
  http://intellinuxgraphics.org/how_to_report_bug.html

Changed in xserver-xorg-video-intel:
status: Confirmed → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in xserver-xorg-video-intel:
status: Incomplete → 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.