[i815] Max resolution not detected on compaq 7500

[batti5]

Binary package hint: xorg

Hi, i am a kubuntu 8.10 beta, i have a problem, my Intel 815 video card with a max of 1280x1024 24bit & a compaq 7500
color monitor, the system only detects a max of 1024x768 16bit, maybe this can be fixed i hope if you may need other information conntact me at <email address hidden>

[Jiri Bajer (sarimak)]

Hello batti5,

could you please add the following to simplify the troubleshooting?

$ uname -a
$ cat /etc/X11/xorg.conf
$ lspci | grep VGA
$ cat /var/log/Xorg.0.log
$ xrandr
$ dpkg -l | grep xorg

I'll mark the bug as Incomplete in the meantime. Thanks in advance!

[batti5 (batti3004)]

Linux batti5 2.6.27-7-generic #1 SMP Fri Oct 10 03:55:24 UTC 2008 i686 GNU/Linux

[batti5 (batti3004)]

My xorg.conf

[batti5 (batti3004)]

00:02.0 VGA compatible controller: Intel Corporation 82815 Chipset Graphics Controller (CGC) (rev 02)

Screen 0: minimum 640 x 350, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
   1024x768 85.0* 75.0 70.0 60.0
   832x624 75.0
   800x600 85.0 75.0 72.0 60.0 56.0
   640x480 85.0 75.0 60.0 73.0
   720x400 70.0 85.0
   640x400 85.0
   640x350 85.0

ii libglu1-xorg-dev 1:7.4~2ubuntu7 transitional package for Debian etch
ii python-xkit 0.3.6 library for the manipulation of the xorg.con
ii xorg 1:7.4~2ubuntu7 X.Org X Window System
ii xserver-xorg 1:7.4~2ubuntu7 the X.Org X server
ii xserver-xorg-core 2:1.5.1-1ubuntu3 Xorg X server - core server
ii xserver-xorg-input-all 1:7.4~2ubuntu7 the X.Org X server -- input driver metapacka
ii xserver-xorg-input-evdev 1:2.0.99+git20080912-0ubuntu3 X.Org X server -- evdev input driver
ii xserver-xorg-input-kbd 1:1.3.1-1ubuntu2 X.Org X server -- keyboard input driver
ii xserver-xorg-input-mouse 1:1.3.0-1build1 X.Org X server -- mouse input driver
ii xserver-xorg-input-synaptics 0.15.2-0ubuntu5 Synaptics TouchPad driver for X.Org/XFree86
ii xserver-xorg-input-vmmouse 1:12.5.1-1ubuntu3 X.Org X server -- VMMouse input driver to us
ii xserver-xorg-input-wacom 1:0.8.1.4-0ubuntu2 X.Org X server -- Wacom input driver
ii xserver-xorg-video-all 1:7.4~2ubuntu7 the X.Org X server -- output driver metapack
ii xserver-xorg-video-apm 1:1.2.0-1build2 X.Org X server -- APM display driver
ii xserver-xorg-video-ark 1:0.7.0-1build2 X.Org X server -- ark display driver ...

[batti5 (batti3004)]

view this link = http://brainstorm.ubuntu.com/idea/8688/

[batti5 (batti3004)]

This is the solution.

[Michael Rooney (mrooney)]

Thanks batti5 for adjusting the status, and I am glad you found a solution, although that is not the proper use of Fix Committed. I will set back to New as it should be fixed in Ubuntu and perhaps with your output someone can figure out why it didn't work out of the box.

[Ted Wilkinson (ted-wtribe)]

Hello,

Has anyone found a resolution to this problem? I have an old Sony Vaio PCG-R505TSK with a maximum resolution of 1024x768. But, he highest that the drivers is finding is 800x600. I see a lot of discussion about this, but I really haven't found a solution.

I see what batti5 did with his xorg.conf file. Unfortunately, I don't know all the mode settings for my screen so I can do the same for my system.

Any suggestions? I'm happy to send any info desired.

Thanks

[Ted Wilkinson (ted-wtribe)]

Sorry for the typo... so I *can't* do the same...

[Bryce Harrington (bryce)]

Perhaps a monitor quirk is needed. This is a pretty antique card tho, possibly it's just braindead. Please attach `lspci -vvnn`

[Jouni Mettala (jouni-mettala)]

Intel driver 2:2.5.1-1ubuntu7 in Jaunty detects correct resolution for me. I would suggest testing Jaunty livecd but bug 310075 and bug 312554 are blockers.

Are bug 288807 and bug 183746 duplicates of this bug?

[Bryce Harrington (bryce)]

[Still waiting on lspci -vvnn]

[Bryce Harrington (bryce)]

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.