You are not logged in.
Yea same deal here. I also got the same version, doesnt work. Its the same version I originally upgraded to.
Offline
skottish wrote:twiistedkaos wrote:hmm can't seem to install nvidia from testing, it isn't found . Odd, enough...
Sorry about that. It got moved into extra after all. I know it's not posted at easynews yet, but easynews is still syncing. Try a different mirror.
Which version? I have nvidia-173.14.12-2, it didn't work for me, and according to ftp://ftp.archlinux.org/$repo/os/i686 it's the most recent version available. Is there a nvidia-173.14.12-3 available somewhere?
I'm running 173.14.12-2 on my 64 bit workstation with the most recent kernel (2.6.26.2-1). I've had installed for the last five days. This includes with the last 2.6.26 kernel from testing. And no, there isn't a 173.14.12-3, it's not necessary. The current nvidia is compiled against the current kernel. Is your nvidia-utils up to date?
Last edited by skottish (2008-08-11 02:00:45)
Offline
I'm running 173.14.12-2 on my 64 bit workstation with the most recent kernel (2.6.26.2-1). I've had installed for the last five days. This includes with the last 2.6.26 kernel from testing. And no, there isn't a 173.14.12-3, it's not necessary. The current nvidia is compiled against the current kernel. Is your nvidia-utils up to date?
Well in my case:
[maddog39@desktop ~]$ pacman -Qi nvidia-utils | grep Version
Version : 173.14.12-1
[maddog39@desktop ~]$ pacman -Si nvidia-utils | grep Version
Version : 173.14.12-1
Version numbers are identical on easynews. Restarting X now to try the package you linked to however I think I will continue to have the same issue.
Last edited by maddog39 (2008-08-11 02:14:06)
Offline
what version of nvidia-utils is available? an update only shows extra/nvidia-utils 173.14.12-1 whereas the drivers are nvidia-173.14.12-2.
thanks
- eskay
Offline
[skottish@iasE ~]$ pacman -Q nvidia nvidia-utils
nvidia 173.14.12-2
nvidia-utils 173.14.12-1
For anyone still having trouble, post the output of:
cat /var/log/Xorg.0.log | grep EE
Also, have you checked with other threads talking about the kernel upgrade breaking things for similarities with your setup?
Offline
This is all I get from running that command after a crashing while starting GNOME using the nvidia driver:
Current Operating System: Linux desktop 2.6.26-ARCH #1 SMP PREEMPT Sun Aug 10 12:29:20 UTC 2008 i686
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(EE) Failed to load module "type1" (module does not exist, 0)
Offline
This is all I get from running that command after a crashing while starting GNOME using the nvidia driver:
Current Operating System: Linux desktop 2.6.26-ARCH #1 SMP PREEMPT Sun Aug 10 12:29:20 UTC 2008 i686 (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (II) Loading extension MIT-SCREEN-SAVER (EE) Failed to load module "type1" (module does not exist, 0)
That error is normal. In fact, I have two more than that. I think there's something else wrong with your setup. X should have complained if the nVidia driver was failing. You could try to check the output of everything.log to see if anything else comes up. You'll need to do this as root:
cat /var/log/everything.log | tail
You can also try to launch X explicitly from the command line to see if you get any other errors. I don't know how to start Gnome that way. startx? Or maybe even 'gdm'. Hopefully someone that know more than I do will be able to help here.
I'm not sure what else I can do, but I'm fairly certain that this is not a problem with the graphics drivers.
Offline
it is nvidia driver.
nv works fine but when nvidia is enabled and glxinfo is run the system will lockup. doesn't matter the window manager. i installed the beta driver from nvidia and am fine.
Offline
Yea I kinda agree. Here is my everything.log tail output:
Aug 10 23:07:46 desktop gdmgreeter[3522]: GLib-CRITICAL: g_key_file_get_locale_string: assertion `key_file != NULL' failed
Aug 10 23:07:46 desktop gdmgreeter[3522]: GLib-CRITICAL: g_key_file_get_locale_string: assertion `key_file != NULL' failed
Aug 10 23:07:46 desktop gdmgreeter[3522]: GLib-CRITICAL: g_key_file_get_locale_string: assertion `key_file != NULL' failed
Aug 10 23:07:46 desktop gdmgreeter[3522]: GLib-CRITICAL: g_key_file_get_locale_string: assertion `key_file != NULL' failed
Aug 10 23:07:46 desktop gdmgreeter[3522]: GLib-CRITICAL: g_key_file_get_locale_string: assertion `key_file != NULL' failed
Aug 10 23:07:46 desktop gdmgreeter[3522]: GLib-CRITICAL: g_key_file_get_locale_string: assertion `key_file != NULL' failed
Aug 10 23:07:46 desktop gdmgreeter[3522]: GLib-CRITICAL: g_key_file_get_locale_string: assertion `key_file != NULL' failed
Aug 10 23:07:46 desktop gdmgreeter[3522]: GLib-CRITICAL: g_key_file_get_locale_string: assertion `key_file != NULL' failed
Aug 10 23:07:46 desktop gdmgreeter[3522]: GLib-CRITICAL: g_key_file_get_locale_string: assertion `key_file != NULL' failed
Aug 10 23:07:46 desktop gdmgreeter[3522]: GLib-CRITICAL: g_key_file_free: assertion `key_file != NULL' failed
Also, while I was doing that I looked farther back in the log but didnt find much of anything.
Offline
Well I just installed the beta drivers from the AUR as well. Although, because they require the 2.6.25 kernel, building/installing them also downgraded the kernel back to 2.6.25 which would in turn resolve all the problems I am/was having with the current version in extra with kernel 2.6.26. I hope this issue still gets resolved and I will wait about a month before I upgrade to 2.6.26 now. This took way too much time out of doing other things.
[Edit]
Nevermind, the latest nvidia drivers in extra require the latest kernel.
Last edited by maddog39 (2008-08-11 03:54:47)
Offline
I've got the same problem here. After upgrading to the new kernel and nvidia driver, every time the nvdia driver tries to open an application that uses OpenGL (for example glxgears, glxinfo or compiz) my computer completely freezes. Now I have to use the vesa driver. :-(
The worst thing about this is that I cannot downgrade my kernel because there are other packages very important for my hardware which older versions are not available in /var/cache/pacman/pkg and the updated ones cannot work with the old kernel.
Last edited by [DoodoM] (2008-08-11 04:37:30)
Offline
it is nvidia driver.
nv works fine but when nvidia is enabled and glxinfo is run the system will lockup. doesn't matter the window manager. i installed the beta driver from nvidia and am fine.
Yes, same here. I am using geforce 8600m GT with nvidia driver version 173.14.12-2.
I downgrade the kernel and nvidia driver and acceleration 3d works fine again (tip of RagingDragon). I will wait the solution for this problem.
Last edited by alessandro_ufms (2008-08-11 05:08:47)
Offline
Because this I love Arch. I've been install nvidia driver verion 173.14.12-3 and works fine.
Offline
Ok, nvidia 173.14.12-3 is working for me too.
Offline
Same here, 173.14.12-3 works fine.
PS: Does anyone know why 173.14.12-2 didn't work? I checked the svn entry for -3 but I couldn't find any changes. .-.
If I understood correctly, the only thing needed was a rebuild, because of the new kernel : 2.6.26.2-1
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
I had the same problem, but I have just build and installed the nvidia-173.14.12-2 from AUR instead of the pacman one, and everything works fine again.
Some applications are WYSIWYG, and some are WYSIWTF.
Offline
With the new nvidia-173.14.12-3 drivers seems to be solved.
This is being so fast solving problems. Thanks to the repositories maintainers!
(I migrated from Ubuntu for problem like these)
Last edited by [DoodoM] (2008-08-11 14:47:19)
Offline
The -3 revision to the package solved the issues for me as well.
Offline
Yep, -3 solved my issue also.
Offline
foutrelis wrote:Same here, 173.14.12-3 works fine.
PS: Does anyone know why 173.14.12-2 didn't work? I checked the svn entry for -3 but I couldn't find any changes. .-.
If I understood correctly, the only thing needed was a rebuild, because of the new kernel : 2.6.26.2-1
then the update was a little misleading to me. the -2 nvidia update was with the .26 kernel upgrade. seems in the past new nvidia drivers were released with kernel upgrades, so i didn't think of it. oh well, all is well.
Offline