request for nvidia 100 series driver in restricted-modules

[dean]

Binary package hint: linux-restricted-modules-2.6-386

We are requesting enablement of the new nvidia 100 series driver package to be included in the linux-restricted-modules package for feisty.
This is needed for our upcoming vnidia chipsets:
8300, 8600, and 84M

[dean (dean-oliver)]

This affects upstream for project redfish.

[Amit Bhutani (amit.bhutani)]

Dean- "84M" should be "8400M". Also, please subscribe the "redfish" group to this issue as we've seen that the only way for other folks from Dell inside the redfish team to access private issues.

> -----Original Message-----
> From: <email address hidden> [mailto:<email address hidden>] On Behalf Of
> dean
> Sent: Monday, June 18, 2007 5:46 PM
> To: Bhutani, Amit
> Subject: [Bug 121096] request for nvidia 100 series driver inrestricted-modules
>
> Public bug reported:
>
> Binary package hint: linux-restricted-modules-2.6-386
>
> We are requesting enablement of the new nvidia 100 series driver package to be
> included in the linux-restricted-modules package for feisty.
> This is needed for our upcoming vnidia chipsets:
> 8300, 8600, and 84M
>
> ** Affects: linux-meta (Ubuntu)
> Importance: Undecided
> Status: Unconfirmed
>
> --
> request for nvidia 100 series driver in restricted-modules
> https://bugs.launchpad.net/bugs/121096
> You received this bug notification because you are a member of The
> Redfish Team, which is a direct subscriber.

[Sitsofe Wheeler (sitsofe)]

Punting from linux-meta -> linux-restricted-modules-2.6.20

Bug #120943 addresses this for Gusty, however I suspect it is unlikely such an invasive change like this would be made for Feisty. In an ideal world you would "just" turn nvidia-glx-new into (which is currently 1,0-9755 series) into 100.14.09. However doing so WILL cause regressions and various issues on cards that currently work with with the 1,0-9755 driver. Introducing a fourth nvidia-glx package would be... tough... given that we are still seeing fallout from the creation of nvidia-glx-new (see Bug #105756 and Bug #98641 ). Trying to manage the migration path alone would be a headache.

[Jose De la Rosa (jose-de-la-rosa)]

I compiled 3D NV driver from NVIDIA on Lanai and it worked. Here are the instructions provided by Roger:

Compiling Nvidia 100.14.09 on 7.04:

1. apt-get update
2. apt-get install binutils linux-source-2.6.20 libc-dev
3. cd /usr/src
4. tar -jxvf linux-source-2.6.20.tar.bz2
5. ln -s linux-source linux
6. apt-get install linux-headers-2.6.20-15 linux-headers-2.6.20-15-386
7. Download NVIDIA-Linux-x86-100.14.09-pkg1.run from http://www.nvidia.com/object/unix.html
8. Switch to a virtual terminal, killall gdm or it will complain about xsever running.
9. sh NVIDIA-Linux-x86-100.14.09-pkg1.run, follow the instructions.
10. Reboot your done.

[Sitsofe Wheeler (sitsofe)]

(Subscribing Jose so reply is seen)
Jose:
If you are going to hand install the NVIDIA binary driver then I would look at https://help.ubuntu.com/community/NvidiaManual because there are some things on that page (like disabling the Ubuntu NVIDIA drivers) that it is not clear that you are doing and they can come back to haunt you later down the line (e.g. when you reboot)...

[Jose De la Rosa (jose-de-la-rosa)]

Installed new NVIDIA driver NVIDIA-Linux-x86-100.14.11-pkg1.run:

Linux Display Driver - x86
Version: 100.14.11
Operating System: Linux x86
Release Date: June 21, 2007

I then ran the following:

1. lsmod | grep nvidia
    [ nvidia driver is loaded ]

2. dpkg -l | grep nvidia*
    [ don't have "nvidia-glx", nvidia-glx-legacy", "nvidia-glx-new" and "nvidia-settings" packages installed ]

3. In file /etc/default/linux-restricted-modules-common, I added the following:
           Set DISABLED_MODULES="nv nvidia_new"
4. Rebooted once.

Driver works fine. However, Suspend does not work. Hibernate works fine.

[Sitsofe Wheeler (sitsofe)]

Jose:
It would be more useful to know whether suspend works when you aren't running the NVIDIA binary driver as that will indicate whether the issue lies with the binary driver. Typically, you will need to disable graphics card POSTing when using the binary driver (see https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend ). Depending on your system and card you may find that disabling the default agpgart and using NvAGP is also required to solve the problem... However such issues really aren't a part of this particular bug.

(Other useful information can be found on https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia ).

[Neil Ord (neil-explodingpanda)]

I too have had major issues with suspend and switching VTerms. I have tried endless 'fixes' and got nowhere, and always ended up being told the nvidia binary driver was at fault...

Surprise surprise, manually installing 100.x myself, everything works beautifully... I know it's a widely reported problem too - so we really need this driver in the repository somehow...

[Sitsofe Wheeler (sitsofe)]

Perhaps this would be a good backport (https://help.ubuntu.com/community/UbuntuBackports ) candidate if this driver is made available for Gutsy...

[Jose De la Rosa (jose-de-la-rosa)]

I installed the latest NVIDIA driver NVIDIA-Linux-x86-100.14.11-pkg1.run on a Dell 1420n (lanai) system. I had to add DISABLED_MODULES="nv nvidia_new" in /etc/default/linux-restricted-modules-common for the display to work. I also tried the instructions in https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend but Suspend still does not work. Hibernate works ok.

[Sitsofe Wheeler (sitsofe)]

Jose:
Can you spin the suspend problem into a bug of its own and also indicate whether you see the problem when using the open source nv driver?

[Ben Collins (ben-collins)]

Test 100 series driver packages for feisty:

http://people.ubuntu.com/~bcollins/lrm-feisty-nvidia-100/

[Serge (serge-de-souza)]

Will this be going into gutsy too, or is it too late?

Serge

[Jose De la Rosa (jose-de-la-rosa)]

Installed packages from http://people.ubuntu.com/~bcollins/lrm-feisty-nvidia-100 on Dell 1420 laptop:

linux-restricted-modules-2.6.20-16-generic_2.6.20.5-16.29_i386.deb
linux-restricted-modules-common_2.6.20.5-16.29_all.deb
nvidia-glx-new_100.14.11+2.6.20.5-16.29_i386.deb
nvidia-glx-new-dev_100.14.11+2.6.20.5-16.29_i386.deb

$ sudo /etc/init.d/gdm stop
$ sudo dpkg -i *.deb
$ sudo dpkg-reconfigure xserver-xorg
(went throught setup screens)
$ sudo /etc/init.d/gdm start

Does not work, I get a blank screen. Attaching relevant files.

[Jose De la Rosa (jose-de-la-rosa)]

Attachment from previous post.

[Sitsofe Wheeler (sitsofe)]

Jose:
Make sure you reboot after installing new kernel modules. However, your problem sounds exactly like the libwfb problem in Bug #98641 (which I mentioned in an earlier comment). Be careful, don't install the .deb over the top of a system using manually installed drivers - this is the path to ruin! Uninstall any manual drivers first. Additionally, any changes you made to DISABLED_MODULES will need to be undone.

[Sitsofe Wheeler (sitsofe)]

Hang about... You can't change the distro this bug refers to Gutsy without having this bug simply duplicate on Bug #120943 (see earlier comments for the bug link)...

[pauls (paulatgm)]

We now have a new nvidia driver 100.14.19 which claims bug fixes and compatability with xorg-1.3 in gutsy. It was released on 9/18/07. Request it be the default nvidia-glx instead of the older and buggy 9755 in gutsy.

[Mikael Nilsson (mini)]

ons 2007-09-19 klockan 13:11 +0000 skrev pauls:
> *** This bug is a duplicate of bug 120943 ***
> https://bugs.launchpad.net/bugs/120943
>
> We now have a new nvidia driver 100.14.19 which claims bug fixes and
> compatability with xorg-1.3 in gutsy. It was released on 9/18/07.
> Request it be the default nvidia-glx instead of the older and buggy 9755
> in gutsy.

Well, we have 100.14.11 already, so it's not *that* bad.

/mikael

>
--
<email address hidden>

Plus ça change, plus c'est la même chose

[slamdunk (antongiulio05)]

Curiosity:

I have installed kernel 2.6.22-10-generic and 2.6.22-11-generic (with all relatives modules restricted etc. for both kernels) but nvidia driver works just for 2.6.22-10-generic. With 2.6.22-11-generic, Xorg enter in a kind of auto-configurer (new feature).

Is it a configuration problem or is it a bug???

[Sitsofe Wheeler (sitsofe)]

slamdunk:
That's more of a support request ( https://answers.launchpad.net/ ) than a bug report but the odds are the necessary linux-restricted driver is missing due to a meta package not being installed (so as your kernel is updated a new linux-restricted is not being installed t). Thttps://answers.launchpad.net/oohis is a very rough guess though as there isn't much information to go on (this isn't really the right place for that question).

[slamdunk (antongiulio05)]

I dont' know if it's a real support request. I just know that it's a hell for me!

With every new kernel upgrade with nvidia I need to start:

# killall -9 gdm Xorg
# modprobe -r nvidia
# modprobe nvidia_new
# gdm

I do everything (nvidia-xconfig etc.) but the top is:

# nvidia-glx-config enable

where a jerk:

Section "Device"
        Identifier "ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE]"
        Driver "nvidia"
        BusID "PCI:0:5:0"
EndSection

I didn't know about ATI-Nvidia fusion company (ok it's just an identifier...)

for desperation I have installed all 2.6.22-11 packages and removed all 2.6.22-10 packages but manual launch is required everytime... probably with next upgrades this will work until upgrade from 2.6.22-11 to 2.6.22-12...

Sorry for this vent but I hate lose two hours at work to get a working system...

[Sitsofe Wheeler (sitsofe)]

slamdunk:
Unfortunately if you are raising valid complaints it is important to do so in the right place otherwise the people who can fix it may never see it. I'm afraid I can't follow up on your comment in this area so I will leave any further responses here to someone else. If you wanted to improve your chances I would recommend carefully writing a NEW support request including information like whether you have ever manually installed the binary driver, Xorg.0.log, the output of sudo sh -x /sbin/lrm-video nvidia, your dmesg output after doing the previous on a fresh boot and other bits and pieces.

[Jose De la Rosa (jose-de-la-rosa)]

unsubscribe

[Timothy R. Chavez (timrchavez)]

The bug task for the somerville project has been removed by an automated script. This bug has been cloned on that project and is available here: https://bugs.launchpad.net/bugs/1305602