removing all BOINC/SETI files ?? |
![]() |
| log in |
Questions and Answers : Unix/Linux : removing all BOINC/SETI files ??
| Author | Message |
|---|---|
|
When I run_manager the screen comes up, but EVERYTHING freezes (which it should not do on Linux!) ctrl-alt-delete ? no. All I can do is reset: sooo Windows. | |
| ID: 946256 · | |
When I run_manager the screen comes up, but EVERYTHING freezes (which it should not do on Linux!) ... All rather odd... Have you got a mix of having installed boinc from the Ubuntu package manager AND also installed locally a copy from the boinc downloads ...sh script? I would guess that multiple boincs running would get things a little confused... For the time being, you'll likely need to stay with the boinc 6.6.x series unless you're adventurous enough to manually upgrade the nVidia drivers to then be able to use the boinc 6.10.x series. Meanwhile, try uninstalling your present boinc, and then keep with the Ubuntu packaged version of boinc or look up the various instructions for installing boinc manually. The Ubuntu install installs boinc as a service. The ...sh script installs boinc into the directory BOINC wherever it is that you run the script. You must then start boinc manually also. For the cuda stuff to work, boinc must have read-write access to the /dev/nvidia* device files... And that's another story! (My trick is to set those device files group rw for the "video" group and then add the boinc user to the video group.) Hope that's helped a little... Good luck, Martin ____________ Mandriva Linux A user friendly OS! See new freedom Mageia2 The Future is what We make IT (GPLv3) | |
| ID: 946575 · | |
|
Thank you for your reply--sorry mine has been delayed; a lot of work, a lot of crunching! | |
| ID: 947765 · | |
|
OK -- I removed everything with boinc or BOINC in it -- and tried to reinstall 6.6.41. | |
| ID: 948368 · | |
Linux still ought not completely freeze! Quite so. The nVidia drivers are 'proprietary' and infiltrate the kernel despite being 'untrusted'. Hence why there is a requirement that those drivers announce themselves as such and the kernel declares itself "Tainted". You'll see that in the boot up logs. If something goes wrong in an untrusted driver in a tainted kernel, there's nothing much that can be easily debugged. The untrusted driver is proprietary. Who knows?! A strong design requirement for linux is that as much as possible is OUTSIDE of the kernel so that the kernel is as robust as possible. The latest versions of Xorg have moved yet more of the display code outside of the kernel for example. Meanwhile, Microsoft Windows has an unbelievable amount of application type code embedded into the Microsoft kernel including I believe all of the display code. One small error in any of that lot and you get the infamous BSOD. Or it just all freezes. Add into that the system level interception that is done by "antivirus" software that is to vet every system action... Quite a nightmare! All good fun! The extreme of using a small bug-free kernel has got to be the (highly parallel) GNU HURD system. However, development of that appears to be slow and the monolithic linux kernel is very successful and far less imperfect than certain other systems. Who knows... As we get to run ever more multiple processing cores, favour may shift to developing something similar to the GNU HURD, or even GNU HURD itself. Wikipedia GNU HURD GNU HURD home Happy crunchin', Martin (All just my own opinion as ever!) ____________ Mandriva Linux A user friendly OS! See new freedom Mageia2 The Future is what We make IT (GPLv3) | |
| ID: 948502 · | |
Meanwhile, Microsoft Windows has an unbelievable amount of application type code embedded into the Microsoft kernel including I believe all of the display code. One small error in any of that lot and you get the infamous BSOD. Or it just all freezes. Windows Vista and all future Windows OSes have moved all display code to CPU Ring 3 thereby reducing the number of blue screens and preventing the entire system from crashing from a faulty display driver. This also allows the display driver on these OSes to be upgraded without a reboot. ____________ | |
| ID: 948510 · | |
Questions and Answers : Unix/Linux : removing all BOINC/SETI files ??
| Copyright © 2013 University of California |