system hard locks on reboot

Bug #6616 reported by peter branch on 2006-01-10
12
Affects Status Importance Assigned to Milestone
Ubuntu
Dapper
Medium
Unassigned
linux-restricted-modules-2.6.15 (Ubuntu)
Medium
Unassigned
nvidia-kernel-common (Ubuntu)
Medium
Unassigned

Bug Description

Nvidia 81xx series driver does not work on Toshiba Qosmio F10 . After using the built in driver(8178 ) in Dapper or installing the 8178 driver from nvidia on Breezy the system alway hardlocks on GDM initialision. My vidia card is Nvidia GeForce Go FX 5700 Rev a1.

0000:01:00.0 VGA compatible controller: nVidia Corporation NV36 [GeForce FX Go5700] (rev a1) (prog-if 00 [VGA])
 Subsystem: Toshiba America Info Systems: Unknown device 0002
 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 10
 Memory at cf000000 (32-bit, non-prefetchable) [size=16M]
 Memory at a0000000 (32-bit, prefetchable) [size=256M]
 Capabilities: [60] Power Management version 2
 Capabilities: [44] AGP version 3.0

Changed in nvidia-kernel-common:
assignee: nobody → adconrad
peter branch (ptrbee) wrote :

Hi again I also forgot to mention that the 7xxx series driver worked okay on my notebook but once installed on reboot or shutdown it would take about 4mins to complete.

Adam Conrad (adconrad) wrote :

You can always install "nvidia-glx-legacy" instead of "nvidia-glx", which will use the 7174 driver (and reboot after you do so). Let me know how that goes. If it works, then the new upstream driver hates you and there's (sadly) not much I can do about that, since it's proprietary. If both drivers break now, it may have something to do with recent kernel updates in Ubuntu and, while I'm not sure we can sort it, we can at least look more closely at way the cause may be.

Adam Conrad (adconrad) wrote :

You may also want to try posting about your bug to the nvnews forums <http://www.nvnews.net/vbulletin/forumdisplay.php?f=14>, where at least one NVIDIA employee ("zander") hangs out, and it's about as close to "upstream support" as most NVIDIA/Linux users ever get.

peter branch (ptrbee) wrote :

Hi Adam I'm currently using breezy 5.10 kernel 2.6.12-10-686 with 76.76 driver which works, (have the composite bugs though) I haven't tried any 7xxx series drivers on dapper as yet but can do if you wish, I also will speak to nvidia about it.

peter branch (ptrbee) wrote :

Hi Adam, I posted this http://www.nvnews.net/vbulletin/showthread.php?t=63158 and this https://launchpad.net/distros/ubuntu/+source/lm-sensors/+bug/29015 but still no joy or solution to any of my problems. Do you have any other ideas???

Peter Petersson (peter-pmb) wrote :

I still have problems with shutdown and reboot. Im now using the 2.6.15-13-amd64 kernel I used the 2.6.15-7-amd kernel the last time i reported on this problem in bugzila #20409.
My graphics card is a ati X800 and Im using the fglrx driver.

About ~1.5 seconds after shutdown or reboot from X I end up with a black sreen (no signal) and noting else is happening. I have to do a manual power off to shut down the comp.

When booting i don't get the normal console printout insted i get a black screen until gdm starts.
If i remove quiet splash from grub kernel line i get some consol output on startup but still nothing on shutdown or reboot.

I regularly do apt-get update; apt-get dist_upgrade so the system shuld be up to date with the latest in dapper.

MichelDeGouveia (afmdg) wrote :

I have the same problem with my toshiba laptop Pro 2100 when I want to enable nvidia.
I don't understand the problem.
The nv drivers work for the moment but it 's not a solution.

nurdin (nurdin-premji) wrote :

I have the same problem, Toshiba Satellite Pro M10, Geforce4 Go 420.
previously with 8xxx drivers and my geforce go card. I found that you have to load the nvidia module with the option NVreg_Mobile=1 but this seems not to work anymore under ubuntu.

In order to load module with that option I usually create a file in /etc/modprobe.d called nvidia with the line "options nvidia NVreg_Mobile=1"

However this no longer works for some reason... I get a black screen with an underline cursor in the top left corner.

MichelDeGouveia (afmdg) wrote :

I solved my problem in Dapper.

With the ubuntuforums, I find this link

http://doc.gwos.org/index.php/Latest_Nvidia_Dapper

15) If you own a GeForce4 420 Go you should follow these steps:

sudo nano /etc/modprobe.d/options

Add this option at the end of the file:

options nvidia NVreg_SoftEDIDs=0 NVreg_Mobile=1

CTRL+O to save CTRL+X to exit

Edit your xorg.conf:

sudo nano /etc/X11/xorg.conf

get to the "Section Device" and add the following options

Option "RenderAccel" "true"
Option "AllowGLXWithComposite" "true"
Option "IgnoreEDID" "true"
Option "IgnoreEdidFreqs" "true"
Option "GenerateRTList" "0"
Option "OverridePolarity" "1"

Michel

davie (daviemoston) wrote :

I had exactly the same problem. The work around suggested by MichelDeGouveia fixes the problem for me.

peter branch (ptrbee) wrote :

Seems everyone else are finding solutions & i'm using windows more & more on a daily basis because I can't find one. My saga continues. Now that 2.6.16 is out I can no longer use 7676 driver, or any other driver than nv. 7676 can no longer build the kernel module & 8178 still black screens. Please see these post:-
http://forums.fedoraforum.org/forum/showthread.php?p=494420#post494420
http://www.nvnews.net/vbulletin/showthread.php?p=856811&posted=1#post856811
http://www.nvnews.net/vbulletin/showthread.php?t=66851

HELPPPPPP!!!!! soerry but i'm tearing my hair out here, or whats left of it.

Peter.

Hi peter, we are very sorry about your problem. However, there is little Ubuntu can do about this. You should really insist NVIDIA. Please, if you find a solution, report it here so others can benefit from it. Thanks for your understanding.

da1l6 (da1l6) wrote :

Hello, I had a somewhat similar problem (Crash an logout and Ctrl-Alt+Fx).
Activating framebuffer solved the problem for me.

I added
vga=792 at the end of the kernel lines in /boot/grub/menu.lst

This is just a workaround, but better than nothing.
Hope it helps someone.

a5t3r0 (tquerette) wrote :

I found the solution for my Toshiba Satellite.

In the /etc/modprobe.d/options file add this line:

options nvidia NVreg_SoftEDIDs=0 NVreg_Mobile=1

You can play with "NVreg_Mobile" if you don´t have a mobile.

If you have a black bar apearing on the right of your Toshiba LCD - like mine, those lines in xorg.conf under the Screen section will do the job:

 Option "ExactModeTimingsDVI" "TRUE"
 Option "ModeValidation" "DFP-0: NoEdidDFPMaxSizeCheck, NoVesaModes"

Hope to help someone.

Ben Monnahan (monnahan) wrote :

FWIW I have a Toshiba Qosmio F15 with the same problem. Sometime in the breezy cycle it stopped working and hasn't worked since. (I've tried it with each release up till Edgy) It locks up starting up X at the nVidia splash if enabled or a black screen if not. I don't have another machine to SSH in with and the only method I've found is a hard reboot. Using at to reboot in the future doesn't seem to work.

lspci:

01:00.0 VGA compatible controller: nVidia Corporation NV36 [GeForce FX Go5700] (rev a1) (prog-if 00 [VGA])
        Subsystem: Toshiba America Info Systems Unknown device 0002
        Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 10
        Memory at cf000000 (32-bit, non-prefetchable) [size=16M]
        Memory at a0000000 (32-bit, prefetchable) [size=256M]
        Capabilities: [60] Power Management version 2
        Capabilities: [44] AGP version 3.0

I had that problem when upgrading to Ubuntu Edgy.

The problem is with the most recent Nvidia driver, it hangs my computer. My
Toshiba only works until the 1.0.8776 version.

I´ve attached my xorg.conf and /etc/modprobe.d/options files to help you.

Some wrong NVidia options in the /etc/modprobe.d/options file can really
hang your computer.

Note that I´m using xgl for compiz/beryl so maybe there´s some parameters in
the xorg.conf file that you may not need or they may help if you want to
play with beryl!

Good luck!

On 11/26/06, Ben Monnahan <email address hidden> wrote:
>
> FWIW I have a Toshiba Qosmio F15 with the same problem. Sometime in the
> breezy cycle it stopped working and hasn't worked since. (I've tried it
> with each release up till Edgy) It locks up starting up X at the
> nVidia splash if enabled or a black screen if not. I don't have another
> machine to SSH in with and the only method I've found is a hard reboot.
> Using at to reboot in the future doesn't seem to work.
>
> lspci:
>
> 01:00.0 VGA compatible controller: nVidia Corporation NV36 [GeForce FX
> Go5700] (rev a1) (prog-if 00 [VGA])
> Subsystem: Toshiba America Info Systems Unknown device 0002
> Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 10
> Memory at cf000000 (32-bit, non-prefetchable) [size=16M]
> Memory at a0000000 (32-bit, prefetchable) [size=256M]
> Capabilities: [60] Power Management version 2
> Capabilities: [44] AGP version 3.0
>
> --
> system hard locks on reboot
> https://launchpad.net/bugs/6616
>

Changed in linux-restricted-modules-2.6.15:
assignee: adconrad → ubuntu-kernel-team
Timo Aaltonen (tjaalton) wrote :

Closing the bug since it's very old. If you can reproduce the bug on 8.04 or Intrepid (current devel-version), please file a bug against nvidia-graphics-drivers-173 (or the version you use).

Changed in nvidia-kernel-common:
status: New → Invalid
Changed in linux-restricted-modules-2.6.15:
assignee: ubuntu-kernel-team → nobody
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers