Wrong resolution with an nvidia GeForceGo 7300

 status needsinfo
 assignee <email address hidden>
 subscribe <email address hidden>

Thanks for your bug report. Feisty Fawn Herd 3 was released last week
and it would help us to know if your bug is still an issue with that
version. Thanks in advance.

This bug is still an issue with ubuntu feisty fawn herd 3.

To put it in a nutshell :
 -> the resolution is wrong
 -> the display is very slow (jerky when you use the scrollbar)

Sorry for my (very) poor English.

Could you please add the output of 'sudo xresprobe nv' and your '/var/log/Xorg.0.log' file? Thanks in advance.

This is what I get when I type sudo xresprobe nv (on edgy and on feisty) :

id :
res : 1280x800
freq :
distype : lcd/lvds

The xorg.0.log comes from ubuntu feisty herd 3, in a live session.

Have you tried with the Herd 4 release?

Yes, and it didn't fix the problem.

I installed Kubuntu Herd 4 AMD_64 on an emachines M6810 (amd64 w/ATI radeon 9600), and experience this same problem. So it may be a larger X problem, not just nv.
Initial install selected 1024x768, when I have a 1280x800 widescreen.
  I changed resolution to 1280x768, and the 'test' showed a scrambled screen. I crossed my fingers, clicked 'keep' anyway, and rebooted. The desktop came up clean, but at some intermediate resolution (1152x768??). I again changed it to 1280x800. This time, the test was clean, I clicked 'keep', and went on to other things. Upon shutdown, it went to black screen, no disk activity, so I ended up holding power switch to power down.
  When I booted this morning, the KDM login screen was huge - apparently 640x480, and when X came up, was so scrambled that only the upper left quadrant was readable. Bottom and right side were apparently 'folded' back on themselves several times.

This morning I've tested a daily vuild with xorg 7.2 and the problem doesn't seem to be fixed.

However, I have foud the cause of the problem. As a matter of fact, xorg doesn't detect my graphic card. I could see it with a sudo dpkg-reconfigure xserver-xorg. Reconfiguring xorg with nv (it seemed to use vesa before or a failsafe mode, it even didn't detect the touchpad) fix it and all works fine.

To put it in a nutshell : - the graphic card isn't detected, so xorg seems to use a failsafe mode (maybe vesa, without touchpad support, with a wrong resolution and a slow display)
- sudo dpkg-reconfigure xserver-xorg fixes the prolem and the screen resolution is well detected by xorg after (the touchpad works very well after that)

I hope it will help you.

Let me add one screenshots to show you what happens.

Your bug is looking more and more like mine: #87496

I'm on herd 4, AMD_64 with ATI radeon 9600. While I've messed with the X config using the system settings GUI, so I can't be absolutely sure, here is the relevant section of xorg.conf.1, which I think is the original one from the installation:

Section "InputDevice"
        Identifier "Configured Mouse"
        Driver "mouse"
        Option "CorePointer"
        Option "Device" "/dev/input/mice"
        Option "Protocol" "ExplorerPS/2"
        Option "ZAxisMapping" "4 5"
        Option "Emulate3Buttons" "true"
EndSection

Section "Device"
        Identifier "ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]"
        Driver "ati"
        BusID "PCI:1:0:0"
EndSection

Section "Monitor"
        Identifier "Generic Monitor"
        Option "DPMS"
        HorizSync 28-51
        VertRefresh 43-60
EndSection

Section "Screen"
        Identifier "Default Screen"
        Device "ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]"
        Monitor "Generic Monitor"
        DefaultDepth 24
        SubSection "Display"
                Depth 1
                Modes "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth 4
                Modes "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth 8
                Modes "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth 15
                Modes "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth 16
                Modes "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth 24
                Modes "1024x768" "800x600" "640x480"
        EndSubSection
EndSection

Section "ServerLayout"
        Identifier "Default Layout"
        Screen "Default Screen"
        InputDevice "Generic Keyboard"
        InputDevice "Configured Mouse"
        InputDevice "stylus" "SendCoreEvents"
        InputDevice "cursor" "SendCoreEvents"
        InputDevice "eraser" "SendCoreEvents"
EndSection

...so it appears that it detected the radeon correctly, but missed it on the touchpad and monitor. Somehow, in my playing, I ended up with this monitor definition:

Section "Monitor"
  identifier "Generic Monitor"
  modelname "Custom 1"
  modeline "640x480@60" 25.2 640 656 752 800 480 490 492 525 -vsync -hsync
  modeline "800x600@56" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
  modeline "800x600@60" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
  modeline "1024x768@60" 65.0 1024 1048 1184 1344 768 771 777 806 -vsync -hsync
  modeline "1152x768@54" 64.995 1152 1178 1314 1472 768 771 777 806 +hsync +vsy
nc
  modeline "1280x854" 80.0 1280 1309 1460 1636 854 857 864 896 +hsync +vsync
  gamma 1.0
EndSection

...so I've got a better display...

Richard, please make a seperate bugreport for your problem. If they're similar then you can mention that here.

On Fri, 2 Mar 2007, Duncan Lithgow wrote:

> Richard, please make a seperate bugreport for your problem. If they're
> similar then you can mention that here.
>
>
I did:
  #88691 (LCD backlight set to dim at boot)
  #88692 (touchpad not fully functional)

When replying by email please delete the quoted text, otherwise it clutters up launchpad with duplicate texts.

Richards - this bug is about display resolution with an NVidia card, if your ATI card is having similar trouble with display resolution then please open a specific bug report for that. Otherwise we have a jumble of hardware mixed into one bug report. You might be right that this is a bigger X problem, but we need to keep the different hardware in seperate reports until we know. If it turns out that the ATI problem is quite different it's not possible to delete your comments from this report - that's a limitation of Launchpad we have to work around by not mixing hardware. Thanks for taking the time to record your bugs in the system - keep it up!

Done, #89289

Who is still seeing this bug? It's fixed for me.

Shouldn't the affected package be 'discover-data'.

As a matter of fact, the bug is fixed in gutsy.

Good to hear. The driver has had some updates, which involves getting the right mode on startup.

Duncan: Discover-data only maps pci-id's to drivers.