Arch Linux

report to nvidia. there is nothing we can do here since nvidia is closed source.

Looks like this issue will be fixed in 304.xx:

http://www.nvnews.net/vbulletin/showpost.php?p=2564669&postcount=51

same problem here, when will the 304.xx driver be released?

With the /lib removal, those of us who have downgraded (and asked pacman to ignore nvidia packages in order to keep the working version of nvidia) might end up with upgrade problems.

Would the best way to deal with this, when the "final leg of /lib removal" is completed, be to remove nvidia, perform the upgrade and then reinstall the 295.59-1 version of nvidia?

those of you who have downgraded, should upgrade to the latest release.

But we downgraded, because the latest release doesn't work for us.

I think I'll write a PKGBUILD for 295.59 that installs to /usr/lib/modules
looks like there are only 5 or 6 lines to change.

i don't really care about old and unmaintained stuff.

I agree with you completely, but considering 302.17 killed suspend for everyone with nvidia; the old and unmaintained is the only option for people wanting a working system. That's 37.80% of arch users according to https://www.archlinux.de/?page=PackageStatistics

Edit: + 2.09% for the -lts people

@wonder
It's just that this bug isn't fixed upstream yet…
But that's not your problem, you're right.

@Soup, I think installing my modified version before rebooting after the /lib removal will fix this…
or quick and dirty: move the nvidia kernel module manually, that should work too but I think that will cause conflicts when upgrading to a fixed version.

i still don't care.

I also downgraded the nvidia package and got the described problems caused by the new /lib symlink. For me the following steps worked quite well.

1) remove ignoring the nvidia 302 packages by IgnorePkg from pacman.conf
2) do the full system upgrade initially ignoring glibc according to the solution from the archlinux forum "pacman -Syu --ignore glibc" plus "pacman -Su"
3) after the /lib directory has been moved and the symlink has been created again downgrade nvidia.

Now everything seems to work again like before, using nvidia 295, while 302 still breaks standby.

The bug was fixed upstream in 304.22
If you don't want to ignore every nvidia package when upgrading, you can install nvidia-ll or nvidia-beta from the aur until 304.xx is in extra.

I have the same problem on my notebook.
As experiment I've tried to switch video driver to VESA. And I've got the same problem. I think, it's not only bug of NVIDIA.

Alex, your problem is probably something else. I work with several Nvidia GPUs and the problem is fixed entirely with beta 304 in AUR.

For those wanting to downgrade nvidia drivers, the most-recent-version dependent packages that you must install is this:

* Nvidia drivers:
- nvidia-295.53-2
- nvidia-utils-295.53-1
- opencl-nvidia-295.53-1

* Latest kernel providing support to the above nvidia drivers:
- linux-3.4.5-1

* If you have virtualbox, the most recent version compatible with the above linux package is this:
- virtualbox-modules-4.1.18-3

Finally, you have to add a line like this in your /etc/pacman.conf file:

- IgnorePkg = nvidia nvidia-utils opencl-nvidia linux virtualbox-modules

Now you can run 'pacman -Syu' seamlessly.

I hope this work around helps anyone while a new version of nvidia driver isn't released.

Regards.

this is also fixed in nvidia-beta in aur, 304.22 http://www.nvidia.com/object/linux-display-amd64-304.22-driver.html

New nvidia driver 304.32 available in Extra repository is fixing this issue.

Regards.