Version bump to 100.14.23. Works as expected. Reproducible: Always Steps to Reproduce:
Created attachment 134090 [details] nvidia-drivers-100.14.23.ebuild
Confirming, works fine...
Has anyone tested this on a 2.6.23 kernel?
(In reply to comment #3) > Has anyone tested this on a 2.6.23 kernel? Yes, the submitter. Linux hydra 2.6.23 #1 SMP Thu Oct 11 16:59:15 CEST 2007 i686 Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz GenuineIntel GNU/Linux
There's no sandbox violation issues with it? I got them in 100.14.19, which I'll submit a new bug on.
(In reply to comment #5) > There's no sandbox violation issues with it? I got them in 100.14.19, which > I'll submit a new bug on. The sandbox violation has nothing to do with the ebuild itself. I guess the problem lies somewhere in portage. I'm getting the sandbox violation on any kernel module ebuild. For now, try FEATURES="-sandbox" emerge nvidia-drivers but be careful what you're doing.
(In reply to comment #5) > There's no sandbox violation issues with it? I got them in 100.14.19, which > I'll submit a new bug on. Fixed in sys-apps/sandbox-1.2.18.1 and later (see comment 118 in bug 135745). As I said before, the violation has nothing to do with this ebuild - or any other module ebuild for that matter.
Can confirm, upgrading sandbox resolves emerge problem. I simply used the 100.14.19 ebuild and renamed it, digested and emerged and it emerged fine, so far operating fine. This is an important package as Nvidia claims they have fixed the problem of going back and forth from a vt when running compiz-fusion. This should also solve the return from screensaver issue I hope. I am testing it now. Till now Ive had to disable dpms and use electricsheep as a screensaver with no power management whatsoever in order to avoid problems when returning to my boxes.
Thanks for the ebuild - the .19 release fails to compile for me. Some details: Linux noddy 2.6.23-gentoo #2 SMP Sat Oct 27 17:08:42 BST 2007 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux 01:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce 7600 GT] (rev a1) Monitor is a NEC Multisync LCD 2080UX+ running at 1600x1200 CFLAGS="-O2 -march=prescott -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CXXFLAGS="${CFLAGS}" MAKEOPTS="-j3" FEATURES="parallel-fetch sandbox usersandbox userfetch userpriv" glxgears: 51771 frames in 5.0 seconds = 10354.041 FPS 52197 frames in 5.0 seconds = 10439.235 FPS nvidia-settings works nicely. Hoorah!
These are beta drivers. They're not officially released drivers. The officially supported drivers are 100.14.19. When there is an official release, those will be added to Portage.
(In reply to comment #10) > These are beta drivers. They're not officially released drivers. > The officially supported drivers are 100.14.19. Obviously not in Germany: http://www.nvidia.de/object/linux_de.html Whatever, I don't care anymore.
http://www.nvidia.com/object/unix.html is the US page. As you can see 100.14.19 is the latest there. Checking their forums, where they also post the latest version information, http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14 shows 100.14.19 as well. Only going to the beta page, http://www.nvidia.com/Download/betadrivers.aspx?lang=en-us can you see the 100.14.23 drivers. Lastly, I asked NVIDIA employees and was told 100.14.23 were beta status only.
Well someone tell the Germans and Phoronix that it's beta, stop reporting that it's not!
Phoronix forums clearly mark it as beta but their news article makes no mention. Then again, Phoronix isn't really known to take the stable path. They typically jump on the latest anything and run with it and complain that it's not 100% polished. Case in point, reporting on 2.6.24-rc1 release, Nouveau articles on a weekly basis, testing Fedora 8 2 weeks before it's released, the list can go on.
Adding to the tree as masked.
Added to the tree but masked and with a note that they're beta drivers and unsupported.
