screen size not detected correctly

Bug #89930 reported by zuzuf
2
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
New
Undecided
Unassigned
xresprobe (Ubuntu)
Incomplete
Undecided
Cristian Aravena Romero

Bug Description

just run the feisty herd 5 desktop cd ( amd64 ) on a Dell Precision M90, it starts in 1024x768 with vesa driver so it looks stretched on my 1920x1200 screen and it's slow. It worked with 6.10 - I got 1920x1200 with nv driver on, everything was detected and working. Everything else is working perfectly, good job guys :-)!!

ProblemType: Bug
Date: Mon Mar 5 19:35:00 2007
DistroRelease: Ubuntu 7.04
Uname: Linux ubuntu 2.6.20-9-generic #2 SMP Sun Feb 25 22:59:06 UTC 2007 x86_64 GNU/Linux

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the information requested from [WWW] https://help.ubuntu.com/community/DebuggingXAutoconfiguration as separate attachments.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

could you run 'xresprobe nv' and post the results?

Revision history for this message
zuzuf (zuzuf86-gmail) wrote : Re: [Bug 89930] Re: screen size not detected correctly

Here is what I am getting after launching the Desktop CD ( amd 64 ):
ubuntu@ubuntu:~$ xresprobe nv
grep: /tmp/xprobe.9106/xorg.log: No such file or directory
grep: /tmp/xprobe.9106/xorg.log: No such file or directory
id:
res:
freq:
disptype: lcd/lvds

my gfx card is a quadro FX 2500M ( even if it's seen as a GeForce 7 by
the KDE configuration tool but it's seen correctly by KInfoCenter )
and it worked fine on the same machine with kubuntu 6.10 ( still amd64
desktop CD ).

2007/3/5, Timo Aaltonen <email address hidden>:
> could you run 'xresprobe nv' and post the results?
>
> ** Changed in: xorg (Ubuntu)
> Sourcepackagename: xorg => xresprobe
>
> --
> screen size not detected correctly
> https://launchpad.net/bugs/89930
>

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

you need to run it with sudo or run 'sudo -s' and then that command. Also could you attach /var/log/casper.log.

Revision history for this message
zuzuf (zuzuf86-gmail) wrote :

this time it's not blank:
id:
res: 1920x1200
freq:
disptype: lcd/lvds

I hope it will help

keep making great distros :-) !!

2007/3/7, Timo Aaltonen <email address hidden>:
> you need to run it with sudo or run 'sudo -s' and then that command.
> Also could you attach /var/log/casper.log.
>
> --
> screen size not detected correctly
> https://launchpad.net/bugs/89930
>

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

Please attach your /etc/X11/xorg.conf and your /var/log/Xorg.0.log files

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

Also please attach the output from ddcprobe.

I think this is just another dupe of 27667. The output from ddcprobe would confirm it.

Revision history for this message
zuzuf (zuzuf86-gmail) wrote :

When I run ddcprobe, I get this:
vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: G71 Board - p469h5gs Chip Rev
memory: 262144kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x256
mode: 1280x1024x256
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
edid:
edidfail

it seems it only detects half the video memory, and lots of resolutions are
missing.

I hope it'll help.

2007/9/28, Bryce Harrington <email address hidden>:
>
> Also please attach the output from ddcprobe.
>
> I think this is just another dupe of 27667. The output from ddcprobe
> would confirm it.
>
> --
> screen size not detected correctly
> https://bugs.launchpad.net/bugs/89930
> You received this bug notification because you are a direct subscriber
> of the bug.
>

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

Ah, thanks, this is actually a dupe of the edidfail bug. Duping to that one.

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.