Console corrupted when X is started

[BrianzaMan]

Hi all,

I have a Vaio S4M/S laptop with a Nvidia Geforce 6200 go and the lastest drivers 9755 installed on FreeBSD 6.2.

The problem is simple.

As X starts the textual consoles (ttyv0 to 7) are corrupted. Even shutting X off will not do any better.

X works without problems, but the consoles are unaccessible.

Any hints?

My X configuration is clean (no particular options enabled like RenderAccel or such)

Thanks

Marcello

[alexdupre]

I have the same problem with a GeForce 6200 (driver 1.0.9746 from FreeBSD ports). I had a FX 5900 on the same system and the problem was not present. Once X is started, switching to the textual console give me a black screen and my LCD monitor says "No signal". It seems a problem related to 6200 cards, but I'd like to see it fixed, since the importance of textual consoles.

[BrianzaMan]

Linux driver is also broken

[alexdupre]

So? Do you confirm the problem? Are you working on a fix?

[lanjoe9]

Got the same problem, FreeBSD 6.2, 9746 driver.
Problem also seen in Debian GNU/Linux "etch" with the latest driver..

And I've got a few anomalies in Xorg in FreeBSD as well -- part of the rightmost border of the screen appears at the left, like when you play Super Mario Bros, you can cross from one side of the screen to the other.....

:(

[zander]

Are you using standard VGA or high resolution (VESA) consoles?

[alexdupre]

Standard text console, 80x25, no VESA.

[Harvey Pooka]

I can confirm that with 6-STABLE (built on June 1st, 2007). Driver 9746 exhibits out-of-sync (according to my monitor) problems on the console once X has run at least one time. Before X has run, there are no apparent problems. 9631 does not exhibit the same problem.

Notes:
1. Running nVidia AGP.
2. BFG 6800 OC AGP 128MB (http://www2.bfgtech.com/bfgr68128oc.aspx)
3. DVI
4. dmesg (verbose) boot:
nvidia0: <GeForce 6800> mem 0xfc000000-0xfcffffff,0xb0000000-0xb7ffffff,0xfd0000
00-0xfdffffff irq 16 at device 0.0 on pci1
nvidia0: Reserved 0x1000000 bytes for rid 0x10 type 3 at 0xfc000000
nvidia0: Reserved 0x8000000 bytes for rid 0x14 type 3 at 0xb0000000
nvidia0: Reserved 0x1000000 bytes for rid 0x18 type 3 at 0xfd000000
ioapic0: routing intpin 16 (PCI IRQ 16) to vector 49
nvidia0: [GIANT-LOCKED]

[alexdupre]

Any news on this issue?

[zander]

Have you tried the 100.14.11 driver release?

[alexdupre]

Yes, just tried, same result :-( How can I help you?

[Harvey Pooka]

Have you tried the 100.14.11 driver release?

I finally tried the 100.14.11 release. The monitor no longer shows the out-of-sync message. It now goes to sleep when I switch to a console.

# sysctl hw.nvidia
hw.nvidia.agp.card.rates: 8x 4x
hw.nvidia.agp.card.fw: supported
hw.nvidia.agp.card.sba: supported
hw.nvidia.agp.card.registers: 0xff000e1b:0x1f000302
hw.nvidia.agp.status.status: enabled
hw.nvidia.agp.status.driver: nvidia
hw.nvidia.agp.status.rate: 8x
hw.nvidia.agp.status.fw: disabled
hw.nvidia.agp.status.sba: enabled
hw.nvidia.version: NVIDIA UNIX x86 Kernel Module 100.14.11 Wed Jun 13 15:15:08 PDT 2007
hw.nvidia.registry.EnableVia4x: 0
hw.nvidia.registry.EnableALiAGP: 0
hw.nvidia.registry.NvAGP: 1
hw.nvidia.registry.EnableAGPSBA: 0
hw.nvidia.registry.EnableAGPFW: 0
hw.nvidia.registry.SoftEDIDs: 1
hw.nvidia.registry.Mobile: 4294967295
hw.nvidia.registry.ResmanDebugLevel: 4294967295
hw.nvidia.registry.FlatPanelMode: 0
hw.nvidia.registry.DevicesConnected: 0
hw.nvidia.registry.RmLogonRC: 1
hw.nvidia.registry.DetectPrimaryVga: 1
hw.nvidia.registry.dwords:
hw.nvidia.cards.0.model: GeForce 6800
hw.nvidia.cards.0.irq: 16
hw.nvidia.cards.0.vbios: 05.40.02.12.65
hw.nvidia.cards.0.type: AGP

# pciconf -lv
nvidia0@pci1:0:0: class=0x030000 card=0x00000000 chip=0x004110de rev=0xa1 hdr=0x00
vendor = 'NVIDIA Corporation'
device = 'GeForce 6800 [NV40.1]'
class = display
subclass = VGA

Portion of Xorg.0.log:
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "RandRRotation" "True"
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(II) NVIDIA(0): NVIDIA GPU GeForce 6800 (NV40) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 131072 kBytes
(--) NVIDIA(0): VideoBIOS: 05.40.02.12.65
(II) NVIDIA(0): Detected AGP rate: 8X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 6800 at PCI:1:0:0:
(--) NVIDIA(0): Sony SDM-M81 (DFP-0)
(--) NVIDIA(0): Sony SDM-M81 (DFP-0): 155.0 MHz maximum pixel clock
(--) NVIDIA(0): Sony SDM-M81 (DFP-0): Internal Single Link TMDS
(II) NVIDIA(0): Assigned Display Device: DFP-0
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "1280x1024"
(II) NVIDIA(0): "1024x768"
(II) NVIDIA(0): "800x600"
(II) NVIDIA(0): "640x480"
(II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024
(--) NVIDIA(0): DPI set to (90, 89); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(II) NVIDIA(0): Setting mode "1280x1024"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(**) NVIDIA(0): Option "BackingStore" "True"
(**) NVIDIA(0): Backing store enabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled

[Fatman-UK]

After reluctantly switching from amd64 to i386, I also have garbled consoles. The driver seems fine apart from this one problem when I stop X. I've only noticed it on Ctrl-Alt-F1 or after issuing a "shutdown -p now" command. It looks like the console is still alive but it's so distorted I can't make anything out.

This sync problem wouldn't physically damage an LCD screen, right? I seem to recall CRTs could get severely borked by this sort of thing.

Unfortunately I'm not able to generate a crash dump. Although I can cause what looks like a kernel panic [bold white text, lots of it], I can't be sure because a) I can't make it out and b) it doesn't leave a dump behind for savecore.

So, 'fraid this is the best I can do for now:

% sysctl hw.nvidia.version
hw.nvidia.version: NVIDIA UNIX x86 Kernel Module 100.14.11 Wed Jun 13 15:15:08 PDT 2007

% sysctl hw.nvidia.cards.0.model
hw.nvidia.cards.0.model: GeForce Go 7600

% uname -rims
FreeBSD 6.2-RELEASE-p7 i386 SMP-GENERIC

Let me know if any other info would be handy.

Fatman

[EDIT]
ps. please excuse the lack of nvidia-bug-report.log file. I do not seem to have nvidia-bug-report.sh on my system.

[alexdupre]

UP. The bug is still present and I'm open to offer help for debugging/testing.

[alexdupre]

The problem persists with 100.14.19 driver release.
Here is the nvidia-bug-report.log.

[alexdupre]

Same issue with 169.04 beta driver.

[alexdupre]

Still present with 169.07.

[shogun1970]

same issue with 169.09

100.14.19 is ok

[nael]

same issue with 169.09

100.14.19 is ok

Same issue in 169.09 (GeForce 6200, Linux).
I have to use the 96.31. :(

It will be fixed someday?

[ulelopippi]

I have the same issue on four pc's:

FX 5700 LE (Slackware)
6600 (SuSE)
6600 GT (Linuxfromscratch)
6800 GT (Linuxfromscratch)

With every driver newer than 1.0-9639, when i pass from X to any TTY, i get corrupted screen (either with VESAFB or with plain VGA): characters are colored blocks.

Despite this, TTY's are still functional (i can blindly type commands).

Any chance to get this corrected in new drivers? In this forum there are lots of posts like this, but no solutions are given.

NVIDIA Men, are you alive? ;)

[inXistant]

Same problem here Linux 169 GeForce 6 series... What is even more annoying is when the monitor awakes after being down, I have the same type of corruption in X that I get into the console!!!