Thanks a lot for that Clive, will go through it when I get home One thing though - when I run fah6 -bidadv -smp 8 - verbosity 9 and get the screenshot above the CPU usage is at 0% if the cores were working I would have left it going but after 15 mins on that screen with no CPU activity I thought it was busted! Will have another fiddle later on with it, might try re-installing it, you know the -bigadv etc switches, do you need to add them when you do the -configonly command or do you just add them on the end of fah6 when you run it if that makes any sense? lol
Next part ..... It seems rpmfusion repo is lagging the official updates ..... (Basically the builsys packages that we need for kernel modules are lagging behind the kernel that has been pushed to the updates repo. In the meantime I've updated the buildsys packages for kernel-2.6.29.6-217.2.8.fc11.x86_64 which you'll install as part of the instructions below.) To start, let's update to the latest kernel if you haven't already got it. Code: sudo yum clean all sudo yum update kernel* Now go edit /etc/yum.conf (using sudo). Add a line to the end of the file, on its own before we configure rpmfusion. We need to stop later versions of the nVidia driver (> 180.60) being installed, or CUDA won't work with the wine wrapper. Code: exclude=*nvidia* Now lets add the livna and rpmfusion repos. Code: sudo rpm -Uvh http://rpm.livna.org/livna-release.rpm http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm Download fedora11.tar.gz. Right click, save as. cd to the dir where you downloaded the archive and extract it. Code: tar zxvf fedora11.tar.gz cd fedora11 Now run the script I've created.... Code: ./nvidia-install.sh This is going to install the following for you and pull in any deps. That's the rt2870 packages (patched for Fedora so it plays nice with NetworkManager) for your wireless, the nvidia drivers, cuda and wine cuda wrapper. NB. There are akmod packages for the nvidia and rt2870 kernel drivers. What this means is that anytime you update to a new kernel, the drivers will be automatically built and installed for the new kernel as part of the kernel update, no manual intervention required. Just reboot after the kernel update and away you go. Much better than having to manually compile and install for a new kernel. Code: The following is contained in the nvidia-install.sh script, so you don't have to type by hand. sudo yum --nogpgcheck localinstall \ buildsys-build-rpmfusion-11-0.17.x86_64.rpm \ buildsys-build-rpmfusion-kerneldevpkgs-current-11-0.17.x86_64.rpm \ akmod-rt2870-2.1.2.0-1.fc11.9.x86_64.rpm \ kmod-rt2870-2.1.2.0-1.fc11.9.x86_64.rpm \ kmod-rt2870-2.6.29.6-217.2.8.fc11.x86_64-2.1.2.0-1.fc11.9.x86_64.rpm \ akmod-nvidia-180.60-2.fc11.x86_64.rpm \ kmod-nvidia-2.6.29.6-217.2.8.fc11.x86_64-180.60-2.fc11.x86_64.rpm \ kmod-nvidia-180.60-2.fc11.x86_64.rpm \ nvidia-cuda-toolkit-2.1-8.fc11.x86_64.rpm \ nvidia-cuda-toolkit-devel-2.1-8.fc11.i586.rpm \ nvidia-cuda-toolkit-devel-2.1-8.fc11.x86_64.rpm \ nvidia-cuda-toolkit-libs-2.1-8.fc11.i586.rpm \ nvidia-cuda-toolkit-libs-2.1-8.fc11.x86_64.rpm \ wine-cuda-runtime-2.1-2.fc11.i586.rpm \ xorg-x11-drv-nvidia-180.60-1.fc11.x86_64.rpm \ xorg-x11-drv-nvidia-devel-180.60-1.fc11.i586.rpm \ xorg-x11-drv-nvidia-devel-180.60-1.fc11.x86_64.rpm \ xorg-x11-drv-nvidia-libs-180.60-1.fc11.i586.rpm \ xorg-x11-drv-nvidia-libs-180.60-1.fc11.x86_64.rpm Here, I'm assuming you have a single nvidia card installed that's currently using the nouveau driver. We need to rebuild the initrd image for your kernel. (The nouveau driver will have been blacklisted by installing the nvidia packages above but your kernel will still try to load the driver because it was blacklisted after the initrd was first built when the kernel was installed. This is a one time only. Any future kernel upgrades will build the initrd automatically without the nouveau driver.) Code: cd /boot sudo cp initrd-2.6.29.6-217.2.8.fc11.x86_64.img initrd-2.6.29.6-217.2.8.fc11.x86_64.img.orig sudo mkinitrd -f initrd-2.6.29.6-217.2.8.fc11.x86_64.img 2.6.29.6-217.2.8.fc11.x86_64 Now if you reboot, on the next start X should use the nvidia kernel driver. But before you do that. Suggestion. Edit (sudo) /etc/grub.conf. Find the line with 'timeout=0'. Change it to 'timeout=5'. This will give a 5 second countdown, during which time it will show the grub menu when you boot. Hopefully, all being well, you'll login to X and then, remember the archive you downloaded, open a terminal, cd to the fedora11 dir from the tar extract and run './deviceQuery'. You should get output similar to this ..... Code: [clivem@c7p6t:~/tmp/fedora11]$ ./deviceQuery There is 1 device supporting CUDA Device 0: "GeForce 8800 GS" Major revision number: 1 Minor revision number: 1 Total amount of global memory: 401932288 bytes Number of multiprocessors: 12 Number of cores: 96 Total amount of constant memory: 65536 bytes Total amount of shared memory per block: 16384 bytes Total number of registers available per block: 8192 Warp size: 32 Maximum number of threads per block: 512 Maximum sizes of each dimension of a block: 512 x 512 x 64 Maximum sizes of each dimension of a grid: 65535 x 65535 x 1 Maximum memory pitch: 262144 bytes Texture alignment: 256 bytes Clock rate: 1.46 GHz Concurrent copy and execution: Yes Test PASSED Press ENTER to exit... In which case, a CUDA GPU device is recognised and your ready to start configuring a GPU2 client! Hooray! More later.
No problem. Hope it helps. 'top' is your friend. Run 'top' from the cmd line. If the CPU client is running a bigadv, you should have 8x FahCore_a2.exe processes all chewing up CPU. What you got? It shouldn't make any difference, the -bigadv being there or not when you run -configonly. I tend to create a start.sh script like the following in the client dir. Code: #!/bin/bash ./fah6 -verbosity 9 -smp 8 -bigadv $* The '$*' in the script means that any cmd line arguments to the script are passed to fah6. Just create a file called 'start.sh' with those contents. 'chmod 775 start.sh' to make it executable. Then start your client with './start.sh' instead of starting the client with './fah6 ....'. To configure the client you'd, './start.sh -configonly' and the -configonly will be passed to fah6 and do what you'd expect it to.
Yes, it would be better in the folding forum. But it doesn't matter. After I finish working through this with Rob, I'll write it up as a proper howto and post it in the folding forum. Hopefully then, a mod can do something useful, like sticky it! I'm probably going to do the thing that I wasn't going to do, create a repo for the folding specific packages, like fahmon, nvidia driver, CUDA, etc. etc. I've spent a while this afternoon dealing with things to make this fly, like bumping the epoch of the 180.60 nvidia driver packages so they are considered later than the semi-official 185.xx rpmfusion packages, and doing away with needing to 'hack' excludes into the yum.conf.
Just started going through your code mate, I edited the vncserver file fine like you put above, saved it, exited from root back to my username and typed 'vncpasswd' and I get this: [rob@FEDORA64 sysconfig]$ vncpasswd vncpasswd: error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory
Erm, you downloaded and installed vnc binaries? Might be using another binary other than the one from the Fedora rpm. That's what it looks like. Could be in your PATH before the one from /usr/bin. Let's check the vncpasswd in /usr/bin is the 'right' exe by having a look what libs its linked to. Code: [clivem@c7p6t:~/tmp/repo]$ ldd /usr/bin/vncpasswd linux-vdso.so.1 => (0x00007fffde7b0000) libz.so.1 => /lib64/libz.so.1 (0x0000003610400000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0000003613000000) libm.so.6 => /lib64/libm.so.6 (0x000000360f800000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003612800000) libc.so.6 => /lib64/libc.so.6 (0x000000360f400000) /lib64/ld-linux-x86-64.so.2 (0x000000360f000000) And let's check that's the one your actually using .... Code: [clivem@c7p6t:~/tmp/repo]$ which vncpasswd /usr/bin/vncpasswd Do you get '/usr/bin/vncpasswd' returned?
Your going to wish you hadn't offered to help me Clive! lol I will have a look now at the vnc issue, heres the next one!.... Moved on to the lm_sensors stuff and when I got to stopping the service it says lm_sensors: not configured, run sensors-detect I tried typing ./lm_sensors -detect and it says Permission Denied even though im in as root
That's alright. I've got the patience of a saint! Worse comes to the worse, if you can forward port 22 from your router to the Linux box, I can ssh into it and help. But we're not there yet. Run sensors-detect, not ./lm_sensors -detect!!!! Answer yes to everything when the detect is running. Then go look at /etc/sysconfig/lm_sensors and compare it to what I posted earlier. I'm guessing it's going to choose the w83627ehf module and it'll be preferable to use the asus_atk0110 module instead. So run sensors-detect and then jump back to my instructions.
Heres what I get: Code: [root@FEDORA64 bin]# ldd vncpasswd linux-vdso.so.1 => (0x00007fffd27ff000) libz.so.1 => /lib64/libz.so.1 (0x0000003275800000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0000003283600000) libm.so.6 => /lib64/libm.so.6 (0x0000003274c00000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003281e00000) libc.so.6 => /lib64/libc.so.6 (0x0000003274800000) /lib64/ld-linux-x86-64.so.2 (0x0000003274400000) Code: [root@FEDORA64 bin]# which vncpasswd /usr/local/bin/vncpasswd Looks like the above is wrong for some reason?
Yes, looks like you did a 'make install' of whatever vnc package you downloaded before I told you about the Fedora rpm? /usr/local/bin is in your $PATH before /usr/bin. run vncpasswd with the full path to the one in /usr/bin. ie .... Code: /usr/bin/vncpasswd
Cool... So even without using a GUI app, 'sensors' from the cmd line should give you plenty of info. Here's mine from a Rampage II Extreme, (which has a few more sensors that the P6T Deluxe, but you should see similar.) Code: [clivem@c7p6t:~]$ sensors atk0110-acpi-0 Adapter: ACPI interface +3.3V: +3.33 V (min = +2.97 V, max = +3.63 V) +5V: +4.90 V (min = +4.50 V, max = +5.50 V) +12V: +11.91 V (min = +10.20 V, max = +13.80 V) VCore: +1.31 V (min = +0.80 V, max = +1.80 V) CPU PLL Voltage: +1.86 V (min = +1.50 V, max = +2.00 V) QPI/DRAM Core Voltage: +1.38 V (min = +0.80 V, max = +1.50 V) IOH Voltage: +1.14 V (min = +0.90 V, max = +1.35 V) IOH PCIE Voltage: +1.51 V (min = +1.20 V, max = +1.80 V) ICH Voltage: +1.12 V (min = +0.90 V, max = +1.35 V) ICH PCIE Voltage: +1.51 V (min = +1.20 V, max = +1.80 V) DRAM Bus Voltage: +1.65 V (min = +1.40 V, max = +1.90 V) CPU Fan: 4381 RPM (min = 600 RPM) CH1 Fan: 0 RPM (min = 600 RPM) CH2 Fan: 0 RPM (min = 600 RPM) CH3 Fan: 3928 RPM (min = 600 RPM) PWR Fan: 1635 RPM (min = 600 RPM) OPT1 Fan: 0 RPM (min = 600 RPM) OPT2 Fan: 0 RPM (min = 600 RPM) OPT3 Fan: 0 RPM (min = 600 RPM) CPU Temp: +59.0°C (high = +60.0°C, crit = +65.0°C) MB Temp: +39.0°C (high = +45.0°C, crit = +55.0°C) SB Temp: +52.0°C (high = +65.0°C, crit = +65.0°C) NB Temp: +53.0°C (high = +80.0°C, crit = +80.0°C) OPT1 Temp: +0.0°C (high = +45.0°C, crit = +45.0°C) OPT2 Temp: +0.0°C (high = +45.0°C, crit = +45.0°C) OPT3 Temp: +0.0°C (high = +45.0°C, crit = +45.0°C) coretemp-isa-0000 Adapter: ISA adapter Core 0: +72.0°C (high = +80.0°C, crit = +100.0°C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +69.0°C (high = +80.0°C, crit = +100.0°C) coretemp-isa-0002 Adapter: ISA adapter Core 2: +70.0°C (high = +80.0°C, crit = +100.0°C) coretemp-isa-0003 Adapter: ISA adapter Core 3: +67.0°C (high = +80.0°C, crit = +100.0°C) coretemp-isa-0004 Adapter: ISA adapter Core 4: +72.0°C (high = +80.0°C, crit = +100.0°C) coretemp-isa-0005 Adapter: ISA adapter Core 5: +69.0°C (high = +80.0°C, crit = +100.0°C) coretemp-isa-0006 Adapter: ISA adapter Core 6: +70.0°C (high = +80.0°C, crit = +100.0°C) coretemp-isa-0007 Adapter: ISA adapter Core 7: +67.0°C (high = +80.0°C, crit = +100.0°C)
Yeah that would explain it, have done that and set a password but it says: Starting VNC server: no displays configured [FAILED]
Yup tried that and now got a little dashboard thing on the desktop with the core temps in which was my aim with that Im going to have a look at cuda in a min but my main pain is going to be wireless I think
OK, if you've set up /etc/sysconfig/vncservers as instructed this is probably more of the same. ie. the vnc software you installed before the rpm. Where did you get it from? How did you install it. Basically, let's find the best way to remove it. Or, try this for a quick fix, 'sudo rm /usr/local/bin/*vnc*' and 'sudo service vncserver restart'.
OK. That's good, good, good, good, good. Well, you need to install those rt2870 rpms from the archive. After that, I expect with a couple of minutes fiddling with NetworkManager, it'll work. I'm not using it, but others have it working OK. The only thing I flagged as a potential issue was security. There was some wibble about WPA2 in one of the README's. What you using - WEP, WPA, WPA2?
Tried that and still says same message From memory I downloaded vnc from their website and extracted it and in the readme it said to run ./vncinstall /usr/local/bin and thats all I done
Just done this bit and I got all this, looks like their could be a problem.... [root@FEDORA64 fedora11]# ./nvidia-install.sh Loaded plugins: refresh-packagekit Setting up Local Package Process Examining buildsys-build-rpmfusion-11-0.17.x86_64.rpm: 10:buildsys-build-rpmfusion-11-0.17.x86_64 Marking buildsys-build-rpmfusion-11-0.17.x86_64.rpm to be installed fedora/metalink | 28 kB 00:00 livna | 2.4 kB 00:00 livna/primary_db | 2.7 kB 00:00 rpmfusion-free | 3.3 kB 00:00 rpmfusion-free/primary_db | 322 kB 00:00 rpmfusion-free-updates | 3.8 kB 00:00 rpmfusion-free-updates/primary_db | 197 kB 00:00 rpmfusion-nonfree | 3.3 kB 00:00 rpmfusion-nonfree/primary_db | 79 kB 00:00 rpmfusion-nonfree-updates | 3.8 kB 00:00 rpmfusion-nonfree-updates/primary_db | 55 kB 00:00 updates/metalink | 16 kB 00:00 Excluding Packages in global exclude list Finished Examining buildsys-build-rpmfusion-kerneldevpkgs-current-11-0.17.x86_64.rpm: 10:buildsys-build-rpmfusion-kerneldevpkgs-current-11-0.17.x86_64 Marking buildsys-build-rpmfusion-kerneldevpkgs-current-11-0.17.x86_64.rpm to be installed Examining akmod-rt2870-2.1.2.0-1.fc11.9.x86_64.rpm: akmod-rt2870-2.1.2.0-1.fc11.9.x86_64 Marking akmod-rt2870-2.1.2.0-1.fc11.9.x86_64.rpm to be installed Examining kmod-rt2870-2.1.2.0-1.fc11.9.x86_64.rpm: kmod-rt2870-2.1.2.0-1.fc11.9.x86_64 Marking kmod-rt2870-2.1.2.0-1.fc11.9.x86_64.rpm to be installed Examining kmod-rt2870-2.6.29.6-217.2.8.fc11.x86_64-2.1.2.0-1.fc11.9.x86_64.rpm: kmod-rt2870-2.6.29.6-217.2.8.fc11.x86_64-2.1.2.0-1.fc11.9.x86_64 Marking kmod-rt2870-2.6.29.6-217.2.8.fc11.x86_64-2.1.2.0-1.fc11.9.x86_64.rpm to be installed Examining akmod-nvidia-180.60-2.fc11.x86_64.rpm: akmod-nvidia-180.60-2.fc11.x86_64 Examining kmod-nvidia-2.6.29.6-217.2.8.fc11.x86_64-180.60-2.fc11.x86_64.rpm: kmod-nvidia-2.6.29.6-217.2.8.fc11.x86_64-180.60-2.fc11.x86_64 Examining kmod-nvidia-180.60-2.fc11.x86_64.rpm: kmod-nvidia-180.60-2.fc11.x86_64 Examining nvidia-cuda-toolkit-2.1-8.fc11.x86_64.rpm: nvidia-cuda-toolkit-2.1-8.fc11.x86_64 Examining nvidia-cuda-toolkit-devel-2.1-8.fc11.i586.rpm: nvidia-cuda-toolkit-devel-2.1-8.fc11.i586 Examining nvidia-cuda-toolkit-devel-2.1-8.fc11.x86_64.rpm: nvidia-cuda-toolkit-devel-2.1-8.fc11.x86_64 Examining nvidia-cuda-toolkit-libs-2.1-8.fc11.i586.rpm: nvidia-cuda-toolkit-libs-2.1-8.fc11.i586 Examining nvidia-cuda-toolkit-libs-2.1-8.fc11.x86_64.rpm: nvidia-cuda-toolkit-libs-2.1-8.fc11.x86_64 Examining wine-cuda-runtime-2.1-2.fc11.i586.rpm: wine-cuda-runtime-2.1-2.fc11.i586 Marking wine-cuda-runtime-2.1-2.fc11.i586.rpm to be installed Examining xorg-x11-drv-nvidia-180.60-1.fc11.x86_64.rpm: xorg-x11-drv-nvidia-180.60-1.fc11.x86_64 Examining xorg-x11-drv-nvidia-devel-180.60-1.fc11.i586.rpm: xorg-x11-drv-nvidia-devel-180.60-1.fc11.i586 Examining xorg-x11-drv-nvidia-devel-180.60-1.fc11.x86_64.rpm: xorg-x11-drv-nvidia-devel-180.60-1.fc11.x86_64 Examining xorg-x11-drv-nvidia-libs-180.60-1.fc11.i586.rpm: xorg-x11-drv-nvidia-libs-180.60-1.fc11.i586 Examining xorg-x11-drv-nvidia-libs-180.60-1.fc11.x86_64.rpm: xorg-x11-drv-nvidia-libs-180.60-1.fc11.x86_64 Resolving Dependencies --> Running transaction check ---> Package akmod-rt2870.x86_64 0:2.1.2.0-1.fc11.9 set to be updated --> Processing Dependency: rt2870-kmod-common >= 2.1.2.0 for package: akmod-rt2870-2.1.2.0-1.fc11.9.x86_64 --> Processing Dependency: akmods for package: akmod-rt2870-2.1.2.0-1.fc11.9.x86_64 --> Processing Dependency: kmodtool for package: akmod-rt2870-2.1.2.0-1.fc11.9.x86_64 ---> Package buildsys-build-rpmfusion.x86_64 10:11-0.17 set to be updated ---> Package buildsys-build-rpmfusion-kerneldevpkgs-current.x86_64 10:11-0.17 set to be updated --> Processing Dependency: kernel-devel-uname-r = 2.6.29.6-217.2.8.fc11.x86_64 for package: 10:buildsys-build-rpmfusion-kerneldevpkgs-current-11-0.17.x86_64 ---> Package kmod-rt2870.x86_64 0:2.1.2.0-1.fc11.9 set to be updated ---> Package kmod-rt2870-2.6.29.6-217.2.8.fc11.x86_64.x86_64 0:2.1.2.0-1.fc11.9 set to be updated ---> Package wine-cuda-runtime.i586 0:2.1-2.fc11 set to be updated --> Processing Dependency: nvidia-cuda-toolkit-libs-i586 = 2.1 for package: wine-cuda-runtime-2.1-2.fc11.i586 --> Processing Dependency: libcudart.so.2 for package: wine-cuda-runtime-2.1-2.fc11.i586 --> Running transaction check ---> Package akmods.noarch 0:0.3.6-3.fc11 set to be updated --> Processing Dependency: rpm-build for package: akmods-0.3.6-3.fc11.noarch --> Processing Dependency: /usr/bin/rpmdev-vercmp for package: akmods-0.3.6-3.fc11.noarch --> Processing Dependency: gcc for package: akmods-0.3.6-3.fc11.noarch ---> Package kernel-devel.x86_64 0:2.6.29.6-217.2.8.fc11 set to be installed ---> Package kmodtool.noarch 0:1-18.fc11 set to be updated ---> Package rt2870.noarch 0:2.1.2.0-2.fc11 set to be updated ---> Package wine-cuda-runtime.i586 0:2.1-2.fc11 set to be updated --> Processing Dependency: nvidia-cuda-toolkit-libs-i586 = 2.1 for package: wine-cuda-runtime-2.1-2.fc11.i586 --> Processing Dependency: libcudart.so.2 for package: wine-cuda-runtime-2.1-2.fc11.i586 --> Running transaction check ---> Package gcc.x86_64 0:4.4.0-4 set to be updated --> Processing Dependency: cloog-ppl >= 0.15 for package: gcc-4.4.0-4.x86_64 --> Processing Dependency: glibc-devel >= 2.2.90-12 for package: gcc-4.4.0-4.x86_64 ---> Package rpm-build.x86_64 0:4.7.1-1.fc11 set to be updated --> Processing Dependency: elfutils >= 0.128 for package: rpm-build-4.7.1-1.fc11.x86_64 ---> Package rpmdevtools.noarch 0:7.3-1.fc11 set to be updated --> Processing Dependency: fakeroot for package: rpmdevtools-7.3-1.fc11.noarch ---> Package wine-cuda-runtime.i586 0:2.1-2.fc11 set to be updated --> Processing Dependency: nvidia-cuda-toolkit-libs-i586 = 2.1 for package: wine-cuda-runtime-2.1-2.fc11.i586 --> Processing Dependency: libcudart.so.2 for package: wine-cuda-runtime-2.1-2.fc11.i586 --> Running transaction check ---> Package cloog-ppl.x86_64 0:0.15-0.9.gitb9d79.fc11 set to be updated --> Processing Dependency: libppl.so.7()(64bit) for package: cloog-ppl-0.15-0.9.gitb9d79.fc11.x86_64 --> Processing Dependency: libppl_c.so.2()(64bit) for package: cloog-ppl-0.15-0.9.gitb9d79.fc11.x86_64 ---> Package elfutils.x86_64 0:0.141-1.fc11 set to be updated --> Processing Dependency: elfutils-libs-x86_64 = 0.141-1.fc11 for package: elfutils-0.141-1.fc11.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.127)(64bit) for package: elfutils-0.141-1.fc11.x86_64 --> Processing Dependency: libasm.so.1(ELFUTILS_1.0)(64bit) for package: elfutils-0.141-1.fc11.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.126)(64bit) for package: elfutils-0.141-1.fc11.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.138)(64bit) for package: elfutils-0.141-1.fc11.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.122)(64bit) for package: elfutils-0.141-1.fc11.x86_64 --> Processing Dependency: libdw.so.1()(64bit) for package: elfutils-0.141-1.fc11.x86_64 --> Processing Dependency: libasm.so.1()(64bit) for package: elfutils-0.141-1.fc11.x86_64 ---> Package fakeroot.x86_64 0:1.12.2-21.fc11 set to be updated --> Processing Dependency: fakeroot-libs = 1.12.2-21.fc11 for package: fakeroot-1.12.2-21.fc11.x86_64 ---> Package glibc-devel.x86_64 0:2.10.1-4 set to be updated --> Processing Dependency: glibc-headers = 2.10.1-4 for package: glibc-devel-2.10.1-4.x86_64 ---> Package wine-cuda-runtime.i586 0:2.1-2.fc11 set to be updated --> Processing Dependency: nvidia-cuda-toolkit-libs-i586 = 2.1 for package: wine-cuda-runtime-2.1-2.fc11.i586 --> Processing Dependency: libcudart.so.2 for package: wine-cuda-runtime-2.1-2.fc11.i586 --> Running transaction check ---> Package elfutils-libs.x86_64 0:0.141-1.fc11 set to be updated ---> Package fakeroot-libs.x86_64 0:1.12.2-21.fc11 set to be updated ---> Package glibc-headers.x86_64 0:2.10.1-4 set to be updated --> Processing Dependency: kernel-headers >= 2.2.1 for package: glibc-headers-2.10.1-4.x86_64 --> Processing Dependency: kernel-headers for package: glibc-headers-2.10.1-4.x86_64 ---> Package ppl.x86_64 0:0.10.2-3.fc11 set to be updated ---> Package wine-cuda-runtime.i586 0:2.1-2.fc11 set to be updated --> Processing Dependency: nvidia-cuda-toolkit-libs-i586 = 2.1 for package: wine-cuda-runtime-2.1-2.fc11.i586 --> Processing Dependency: libcudart.so.2 for package: wine-cuda-runtime-2.1-2.fc11.i586 --> Running transaction check ---> Package kernel-headers.x86_64 0:2.6.29.6-217.2.8.fc11 set to be updated ---> Package wine-cuda-runtime.i586 0:2.1-2.fc11 set to be updated --> Processing Dependency: nvidia-cuda-toolkit-libs-i586 = 2.1 for package: wine-cuda-runtime-2.1-2.fc11.i586 --> Processing Dependency: libcudart.so.2 for package: wine-cuda-runtime-2.1-2.fc11.i586 --> Finished Dependency Resolution wine-cuda-runtime-2.1-2.fc11.i586 from /wine-cuda-runtime-2.1-2.fc11.i586 has depsolving problems --> Missing Dependency: nvidia-cuda-toolkit-libs-i586 = 2.1 is needed by package wine-cuda-runtime-2.1-2.fc11.i586 (/wine-cuda-runtime-2.1-2.fc11.i586) wine-cuda-runtime-2.1-2.fc11.i586 from /wine-cuda-runtime-2.1-2.fc11.i586 has depsolving problems --> Missing Dependency: libcudart.so.2 is needed by package wine-cuda-runtime-2.1-2.fc11.i586 (/wine-cuda-runtime-2.1-2.fc11.i586) Error: Missing Dependency: nvidia-cuda-toolkit-libs-i586 = 2.1 is needed by package wine-cuda-runtime-2.1-2.fc11.i586 (/wine-cuda-runtime-2.1-2.fc11.i586) Error: Missing Dependency: libcudart.so.2 is needed by package wine-cuda-runtime-2.1-2.fc11.i586 (/wine-cuda-runtime-2.1-2.fc11.i586) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest
