karmic beta live cd X settings out of range

[mjhooker]

Beta Live CD unusable with X (TTY works) with this configuration.

booted machine with -

c75f9f1cb29ae1d51d4586b2a13b88b2207fa5404ef170480e972117e36f5156 *ubuntu-9.10-beta-desktop-i386.iso

Graphics is integrated nVidia GeForce 7050 PV NForce 630a rev (a2)
Screen is Acer AL1511 (connected via VGA)

9.04 works.

[mjhooker (mjhooker)]

Same CD, Same monitor, different computer
- no issues with (AGP) - nVidia Corporation NV44A [GeForce 6200] (rev a1)

[Xavier Navarro (xvnavarro)]

Tested with desktop cd RC also fail.

The same hardware with Live CD 9.04 works without problems.

[mjhooker (mjhooker)]

Also tested RC CD, not working for me.

I have access to three machines with exactly the same hardware, am preparing a Persistent-Live-USB so I can load updates, via another machine, when they become available and test.

[jolo (joop-loep)]

I did have de same problem with mine AGP Club 3D 7600GS.
The videocard did work fine until Ubuntu Karmic Alpha 5 as LiveCD

cat /var/log/Xorg.0.conf | grep NV
(II) NV(0): <default monitor>: Using hsync range of 24.00-83.00 kHz
(II) NV(0): <default monitor>: Using vrefresh range of 55.00-76.00 Hz

cat /var/log/Xorg.0.log | grep nv
Identifier "Builtin Default nv Device 0"
  Driver "nv"
  Identifier "Builtin Default nv Screen 0"
  Device "Builtin Default nv Device 0"
  Screen "Builtin Default nv Screen 0"
(**) |-->Screen "Builtin Default nv Screen 0" (0)
(**) | |-->Device "Builtin Default nv Device 0"
(==) No monitor specified for screen "Builtin Default nv Screen 0".
(II) LoadModule: "nv"
(II) Loading /usr/lib/xorg/modules/drivers//nv_drv.so
(II) Module nv: vendor="X.Org Foundation"
 "Builtin Default nv Screen 0" for depth/fbbpp 24/32

But I confirm the out of range bug with Ubuntu Karmic Alpha 6, Bèta and the Release Candidate

cat /var/log/Xorg.0.log | grep nv
Identifier "Builtin Default nv Device 0"
  Driver "nv"
  Identifier "Builtin Default nv Screen 0"
  Device "Builtin Default nv Device 0"
  Screen "Builtin Default nv Screen 0"
(**) |-->Screen "Builtin Default nv Screen 0" (0)
(**) | |-->Device "Builtin Default nv Device 0"
(==) No monitor specified for screen "Builtin Default nv Screen 0".
(II) LoadModule: "nv"
(II) Loading /usr/lib/xorg/modules/drivers//nv_drv.so
(II) Module nv: vendor="X.Org Foundation"
(II) UnloadModule: "nv"
(II) Unloading /usr/lib/xorg/modules/drivers//nv_drv.so

cat /var/log/Xorg.0.log | grep VESA
(II) VESA(0): <default monitor>: Using hsync range of 31.50-1259.20 kHz
(II) VESA(0): <default monitor>: Using vrefresh range of 56.00-60.00 Hz

[Péter Molnár (inclitus)]

I can confirm the 'out of range' problem both in beta and rc versions using GeForce 7050PV integrated video card.

[Sam Thursfield (sam.thursfield)]

I have this issue using the 9.10 final live CD. Graphics card is also an onboard GeForce 7050PV. I have tried with 2 different monitors and same story (I attach an xorg.log for each).

In this situation I can access the terminal, but it doesn't scroll up until I switch to a different console - eg. when using less, I press page down and the next line appears at the bottom of the screen, but no more scrolling happens until I change to a different VT and back. And my keyboard mapping isn't loaded.

I mention all this because in 'safe graphics mode' everything works fine, including the console.

[jolo (joop-loep)]

@Sam Thursfield, I do not see anything wrong in your Xorg.0.log files. De NV drivers are used. Are the digimate and the viewsonic hsync even than out of range?

Are there others who can confirm using de bad VESA drivers for their nvidia card, in Karmic Koala Bèta, Release Candidate and the Final Release as LiveCD? For mine AGP Club 3D 7600GS, the Ubuntu 9.10 Bèta, Release Candidate and the Final Release LiveCD's are even out of range in 'safe graphics mode'.

[Sam Thursfield (sam.thursfield)]

@Jolo yeah it's odd. I can't tell you how far out of range they are, all I know is they each come up with a box saying "Out of range" :)

For me safe graphics mode works fine, setting the driver to Vesa works fine (I assume that's the same thing :) and the proprietary NVIDIA driver works fine. I've now installed 9.10 using this driver and no problems at all.

I can help trying to find the issue but I don't know much about Xorg drivers and that sort of thing, so I don't really know where to start.

[karlrhs (karlrhs)]

I also have the same problem with this video card MSI NX7600GS-TD256 GeForce 7600GS 256MB 128-bit GDDR2 AGP 4X/8X Video Card. I am still trying to get Koala to work for the first time.

Help anyone?

[Sam Thursfield (sam.thursfield)]

Here's how I got my system running for the record.
* Booted the live CD in safe graphics mode (F4 at the boot screen I think?), and ran the installer from there. The alternative (text-mode) installer would presumably also worked.
* Booted my new install in recovery mode, and went to a console.
* Edited my /etc/X/xorg.conf and inside Screen "default" there's a line which says something like Driver "nv" or "nvidia" or some such ... I changed this to "vesa"
* Now X would work, although it looked pretty bad
* Then Jockey told me proprietary drivers are available, and installed the proprietory driver.
* Now everything works fine

Hope this helps!

[jolo (joop-loep)]

It seems I have found a work-around for mine Karmic Koala LiveCD out of range problem. Mine AGP Club 3D 7600GS video card did have D-sub (VGA) and DVI ports. It seems the out of range only occurs, when I use the D-sub port. When I did use the DVI port there are no problems. I think the VESA drivers only support the DVI port. En the NV drivers did support both ports.

[karlrhs (karlrhs)]

You know, if I were one attempting Ubuntu for the first time I would have
abandoned my attempt right there. I would have went and looked for windows
7. You have to have a live CD that works out of the box. We need to push
back the release cycle if this is what continues to happen. Yes I fixed the
problem as well, but this does not make Ubuntu look good. There should be
no need for a work around. I love the Ubuntu community and have some
loyalty, but if this kind of after final release problems continue I will
need to look inot moving my customers to Red Hat.

Come on Ubuntu developers we need to test our final product better. It must
work better than windows right off the bat. No need for work arounds at
all. Thank you.

Karl

Salt Lake City,
Utah

Foundation for Children and Youth with Diabetes Webmaster
fcydcamp.org

On Fri, Nov 13, 2009 at 12:00 PM, jolo <email address hidden> wrote:

> It seems I have found a work-around for mine Karmic Koala LiveCD out of
> range problem. Mine AGP Club 3D 7600GS video card did have D-sub (VGA)
> and DVI ports. It seems the out of range only occurs, when I use the
> D-sub port. When I did use the DVI port there are no problems. I think
> the VESA drivers only support the DVI port. En the NV drivers did
> support both ports.
>
> --
> karmic beta live cd X settings out of range
> https://bugs.launchpad.net/bugs/453567
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Foundation for Children and Youth with Diabetes Webmaster
fcydcamp.org

[getaceres (getaceres)]

I confirm this bug in the final Karmic Live CD. I have a Geforce 7600GT and it was working fine with the Jaunty Live CD.

[Bryce Harrington (bryce)]

Thank you for reporting this issue about xserver-xorg-video-nv. Starting
with Lucid, Ubuntu is transitioning to using the -nouveau video driver
by default instead of -nv. The reason for this change is because
upstream development for the -nv driver has been quite slow. We are
quite pleased with the upstream development speed for -nouveau, and hope
this will translate into swifter bug fixes as well.

Because of this, I'm closing this bug report at this time. I'm marking
it wontfix because what you describe is probably a valid issue, but we
do not have further plans to work on it in Ubuntu. If you would still like
to see this issue investigated, I would encourage you to file it
upstream at http://bugs.freedesktop.org/.