Crashes on console switch (HP/Compaq laptop)

[tmchardy]

Laptop: Compaq Presario v6030 (AMD/nVidia based)
OS: FC6 x86_64
Video: Built-in GeForce GO 6150
Drivers: nvidia 9629

1) Install the nVidia video drivers.

Ok, so after this my machine boots up, loads into X with no problems, network works, system isn't crashing as long as I stay in X. However, now when I change to another console (Ctrl-Alt-Fx) the whole system crashes and I need to do a hard-reboot.

Results of this Ctrl-Alt-Fx are either:
1) Get a solid coloured screen (usually Red) and the machine is just frozen.
2) Get an odd coloured screen (i.e. blue) with white text and the machine will crash in under 60 seconds (i.e. I might have just enough time to type in the username/password to log in).

I've heard of others having this same problem with HP laptops, but haven't seen a working solution yet. Everything else works great (there is an occasional crash on shutdown, but without this problem resolved I can't tell if it's related). I can use Direct Rendering, OpenGL, etc... but just can't switch to a console. I can not run the nv bug report tool after the crash as it is a hard crash (can not remote in from another machine).

I've tried about a dozen "potential" solutions, and still have yet to find one that actually works - so here I am looking for more ideas. Anyone?

[netllama]

If this problem perists with 1.0-9746 (1.0-9629 is no longer supported), then please generate and attach an nvidia-bug-report.log.

Thanks,
Lonni

[tmchardy]

This has been requested from me before. Can this log be generated after a system reboot to provide the appropriate information? There is no way to generate this log "after" a crash.

[netllama]

Yes, the bug report can be generated after rebooting, as long as X isn't started yet.

[tmchardy]

Well!
I upgraded to the 9746 (apparently i had 9631, not 9629) and get different results!

Now, when I ctrl-alt-Fx to another screen, all I get is a black screen. It is no longer a full system lock up. This is a step in the right direction. I can type, even though i can't see what I'm typing. Because of this, I was able to run the nvidia-bug-report.sh in the console that wasn't working.

So, here it is.

[netllama]

Does this problem persist if you remove 'rhgb quiet' from grub.conf and reboot?
Have you verified that you're using the latest BIOS for the motherboard?

Thanks,
Lonni

[tmchardy]

Updated to latest kernel and reinstalled the drivers. Didn't help.
Removed rhgb quiet line from grub. Didn't help.

I have found that this is not restricted to just switching to a console anymore though. i don't get any display in a text console at all. Whether I 'init 3' or select to shutdown ('init 0'). As soon as the nvidia drivers are loaded once, I get a black screen on any console output forever more. The only way to get console output is to reboot the machine straight into runlevel 3.

This even occurs if I boot into runlevel 3, start x, then select to log off - I will just go to a black screen.

[netllama]

Have you verified that you're using the latest BIOS for the motherboard?

[tmchardy]

Second to latest. I specify this just to rule it out. HP does not support BIOS update except from a windows utility. I did manage to track down phlash16 and gave that a try (after many hours of trying to get a dos boot - i have no floppy) - but it just complained about descriptor media or some such. It seems there will be no new bios updates unless I reinstall windows some day for some reason.

The good thing is that I'm not alone in this problem. Searching this forum, and others, I was able to track down other people with similar problems. For example, right here:
http://www.nvnews.net/vbulletin/showthread.php?t=83592
Though they do not specify their hardware. I know at least one other person on a different forum has an HP laptop with a GO 6150 though, so it seems this laptop is just the cream of the crop. (Hurray for cheap laptops!)

At least the drivers have slowly been making their way to usable:
8776: Computer crashes on X startup.
9625: First version that worked with "tweaks" before compiling.
9631: Computer crashes when Ctrl-Alt-Fx to other console.
9746: Computer black screen when Ctrl-Alt-Fx to other console (or closing X).

Seems like I'm only one version off for a perfectly working version.

I am happy to provide any other system logs that I can. It now seems that this isn't just for my use anymore, but for all those people getting black-screens. I will just be a little slow in my turn-around time as my laptop is unaccessible from my workplace.

[netllama]

I have an HP/Compaq notebook here with a C51 (it has the latest BIOS), and I'm not able to reproduce this problem with FC6. When I VT switch, the console is restored and fully functional.

[tmchardy]

Ok, took me... a full week! But the bios is now updated to the latest and hopefully greatest and I never had to wipe linux from my machine (This was an exercise in ingenuity to say the least).

As suspected. No change. However, I did find out one thing. In my first ctrl-alt-fx test after upping the bios, I accidentally bumped the mouse. When I did this I saw a strange white streak across the screen - like the resolution or syncs weren't quite right. It almost looks like it's not restoring the appropriate ones when switching to a console or killing the x server. A step in the right direction at the very least. If this is the case, any suggestions on what to try?

[sambo57u]

I think I found a solution to ctrl+alt+Fn problems:

If you are using KDM, edit your kdmrc file (usually in /etc/X11/xdm)
and insert the line:

TerminateServer=true

In all the blocks that contain -Core in their heading.

If you are using GDM try editing gdm.conf and put in the line:

AlwaysRestartServer=true

Hope this helps!
Sammy