Nvidia Driver + Consolle ttyXX = Problem

Bug #35930 reported by Gnuton
42
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.15 (Ubuntu)
Fix Released
Medium
Unassigned
linux-restricted-modules-2.6.24 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

On my Laptop Sony Vaio Fr-102, nvidia propetary driver don't work properly with vesafb (switched on by kernel parameters vga=791).
After start X the consolle ttyXX is not usable!!
I've try a solution using vesa-ng (gentoo kernel).

PS: The SuSE 10.0 kernel work fine!

Revision history for this message
Ben Collins (ben-collins) wrote :

You'll need to be more specific on what "unusable" means. Does the console work up to the point where X starts? Does it not allow you to switch to the console, is the console blank, or is it corrupted?

Revision history for this message
Gnuton (antonio-aloisio) wrote : Re: [Bug 35930] Nvidia Driver + Consolle ttyXX = Problem

The consolle work fine before X starts (with 'nvidia.ko' driver)
After X starts, the consolle is corrupted and isn't readable!

On 3/23/06, Ben Collins <email address hidden> wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/35930
>
> Task: ubuntu linux-meta
> Sourcepackagename: linux-meta => linux-restricted-modules-2.6.15
> Binarypackagename: linux-restricted-modules-2.6-k7 => None
>
> Comment:
> You'll need to be more specific on what "unusable" means. Does the
> console work up to the point where X starts? Does it not allow you to
> switch to the console, is the console blank, or is it corrupted?
>
>

Revision history for this message
Deimos (t-ludewig) wrote :

I've a similar problem on my Dell Latitude 800 (Nvidia Go 5200) with the nv driver everything works fine. With the nvidia driver (8756) the virtual terminals are blank. I could switch between the virtual terminals and if i switch back to X i could work on but there is nothing shown on the virtual terminals and also until the shutdown sequence.

Revision history for this message
Paolo Borelli (pborelli) wrote :

I used to have blank consoles too with nvdia driver in previous ubuntu versions.

On edgy with nvidia drivers 8774 it all works fine.

Revision history for this message
Gnuton (antonio-aloisio) wrote : Re: [Bug 35930] Re: Nvidia Driver + Consolle ttyXX = Problem

Yes, in edgy work fine!

On 10/9/06, Paolo Borelli <email address hidden> wrote:
> I used to have blank consoles too with nvdia driver in previous ubuntu
> versions.
>
> On edgy with nvidia drivers 8774 it all works fine.
>
> --
> Nvidia Driver + Consolle ttyXX = Problem
> https://launchpad.net/bugs/35930
>

Revision history for this message
Michael DePaulo (mikedep333) wrote :

I think this problem is occurring again for those of us with HP pavilion TX1000 series (TX1000z, TX1100 series, TX1200 series, and TX1300 series) and probably the TX2000 series laptops/Tablet PCs.

Here is someone else who experienced the problem.
http://ubuntuforums.org/showpost.php?p=4514822&postcount=697

For me specifically, I have noticed at least two cases. There may be more that are a combination of the two.:
1. switching to the console (tty1 or other ones) after loading X w/ nvidia causes the screen to become a light blue, which changes a little bit. I can then switch back to X and use X again. However, if I try to shutdown, it fails to. I get the corrupt output screen and the shutdown sound repeats.
2. Switching to the console causes X to crash. In the console, there are blue lines going up and down. I can however shutdown the computer, and as it shuts down it still has the lines.

Revision history for this message
Michael DePaulo (mikedep333) wrote :
Revision history for this message
Michael DePaulo (mikedep333) wrote :

BTW, I'm not sure if I am using vesafb or whatever. I am not using any specific resolutions for the console, just everything set at the default.

Revision history for this message
Michael DePaulo (mikedep333) wrote :

I am also noticing this problem whenever the display is turned off, such as by inactivity or by closing the lid. I then have to restart X. This makes it a very serious problem for the casual user.

Revision history for this message
Chris Halse Rogers (raof) wrote :

It looks very much like you have a separate problem, since the initial problem was vesafb & nvidia fighting. Please file a separate bug. Marking the l-r-m-2.6.24 task as invalid.

Changed in linux-restricted-modules-2.6.24:
status: New → Invalid
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

fixed in edgy..

Changed in linux-restricted-modules-2.6.15:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.