Posts by flopflopfloppy

1) Message boards : GPUs : LINUX - No usable GPU found - Laptop - Nvidia - Optimus (Message 63291) Posted 29 Jul 2015 by flopflopfloppy Post: Before having no answers, I just want to know : Does somebody already had (even if no one know how): 1 - GPU computing working 2 - On a Nvidia GPU (850M) 3 - On a laptop who embeds an Intel HD4600 4 - but in LINUX..... ! I wonder because when looking after simple things working it's already complicated on Linux, but for this "complicated" (yeah...) thing, it seems that it is the desert. I'm beginin to think that I'm trying to do something that nobody succeeded in the past. For 1, 2 and 3 it's already working on Windows. I already have 1, 2 and 4 working on Linux (on 2 computers) It seems that because of the presence of and Intel HD GPU, boinc is blinded and doesn't see the Nvidia GPU (he's able to see this same GPU when running on Windows). I installed apt-get install bumblebee-nvidia primus and optirun glxgears -info is able to work with the GeForce 850M. Thank you so much in advance !
2) Message boards : GPUs : No usable GPU found (Message 63227) Posted 24 Jul 2015 by flopflopfloppy Post: I tried a second time (it seems that I love pain !), only with amd-libopencl1 : then, the problems I had were the "standard problems") and now it's working. I didn't install the boinc-amd-opencl package because it crashed my computer last time (seriously... sorry for my "hard" words about linux in my previous message, but this kind of thing turn me completely mad ! It's every time...) But only amd-libopencl1 this time. libOpenCL.so link was missing so I entered the following command : ln -s /usr/lib/libOpenCL.so.1 libOpenCL.so And it seems that, even when all this is done, "xhost +si:localuser:boinc" command should be done again at every start, at least before "boinc-client" start.
3) Message boards : GPUs : No usable GPU found (Message 63135) Posted 21 Jul 2015 by flopflopfloppy Post: Hello, Linux, 64 bits (Debian 8.1.0) AMD Radeon R9 270X I installed the AMD/Ati last driver from the AMD website. It seems to be correctly installed and seeing my GPU. Guess what : it doesn't work with boinc (no usable GPU found) I tried to restart boinc-client once everything is on Guess what : it doesn't work I tried to type this command like a monkey typing keys he doesn't understand xhost local:boinc &> /dev/null Guess what : typing blind commands NEVER works (or just once and only for 1 machine) and it's always what I'm doing with this never operating system. I'm tired ! I tried to run it as root by modifying the boinc-client script Guess what : it doesn't work I tried to type another command : apt-get install boinc-amd-opencl It installed a lot of things, but conflicted with files that have been "manually" installed by AMD drivers. I replaced those files by the ones it was trying to install (if I keep my not working configuration it's not usefull) My system doesn't start anymore (blinking cursor at the top-left part of the screen) -------------------------------------------------- As always on Linux, everything is delivered not working. As if billions of people tryied to work hard to make it impossible to work the same way on 2 differents machines. Add thousands of distributions and versions of it, apt-get as only chance to get something installed because of librairies conflicting with everything, new ones not working with scary old softwares that cannot be upgraded because they don't work for thousands of the sames reasons. And here we are : https://www.debian.org/Bugs/ an huge piece of outdated shit populated by tens of thousands of bugs (more than 80 000). If only (if only ! it would be a dream) GPU on boinc was the only thing that didn't work. Every year, I try. I never, never never never had a computer fully working on Linux. USB3 missing, sound missing, video driver buggy, going to sleep every 30 seconds on my laptops (know bug on last ubuntu few month ago), cannot be installed on EFI with Windows because apt-get upgrade failed to write correctly the EFI partition - system crashed, nvidia-intel hd 4600, optimus bumblebee etc not working, backlight : not working, and placing a shortcut on the desktop on "MATE" environnement : sometimes the desktop freezes (I had that on several computers) One year ago, LXDE decided to make huge font size and I realized after typing blind commands as root during 2 days that the only way to change that, was to create a "fake screen" that is defined as bigger as mine by creating new files somewhere on the file system. They told me to install the Nvidia driver but it didn't worked because of the Intel HD card. Here we are... I'm tired
4) Message boards : BOINC Manager : [SOLVED] wxWidgets Debug Alert - assert "c < 0x80" failed [...] (Message 60315) Posted 15 Feb 2015 by flopflopfloppy Post: Thank you (and thank Rom !) for that, in the name of everybody ;) By the way, thank to every BOINC programmer who read me, for all the problems that I didn't encounter (after all, every absence of problem is a well done hidden work !) Yes, time to sleep ;) good night !
5) Message boards : BOINC Manager : [SOLVED] wxWidgets Debug Alert - assert "c < 0x80" failed [...] (Message 60310) Posted 14 Feb 2015 by flopflopfloppy Post: Hi, Sorry I forgot this one - it was simply the last version Windows 64-bit (9.32 MB) BOINC 7.4.36
6) Message boards : BOINC Manager : [SOLVED] wxWidgets Debug Alert - assert "c < 0x80" failed [...] (Message 60308) Posted 14 Feb 2015 by flopflopfloppy Post: Done, It was computer name From "Caméra-PC" to "Camera-PC", it's now working :) PS : this horrible MessageBox is not a valid reaction to a "non-compatible" computer name. Even when a ongoing fatal error cannot be handled quietly by the program, the message should describe why the program will have no chance to work (at least before diving into the unavoidable crash). I guess it is what is missing on a lot of things of the linux world ! It could be a first correction, and honestly, maybe it is enough ! Alone or helped, people are often going to solve the problem if they have at least one clear clue about what is happenning. Something like "unknown error while getting computer's hostname" could be enough
7) Message boards : BOINC Manager : [SOLVED] wxWidgets Debug Alert - assert "c < 0x80" failed [...] (Message 60307) Posted 14 Feb 2015 by flopflopfloppy Post: Hi everybody May be somebody here would like me to search a litle more for a global subject for this problem or I don't know what. But I have a lot of things today ;) I will give my informations and it's up to everybody to use it or to throw it. I already got this error in the past, few month ago - one less computer running BOINC ! I had no time to search for a solution against a faulty sofware that I'm not developping. But now it's the second time, on a "background" computer user for CCTV cam. After a fresh install on this computer, BOINC doesn't works anymore. So, here is every information that I can give you ! Computer name : Caméra-PC User name : Caméra Installation date : today Windows 7 Ultimate SP1-U, 64, FR, ISO version : X17-59479.iso - ei.cfg removed with with eicfg_remover.exe in order to have every flavour available Previously installed software : VNC Server/Viewer 5.2.1 Total commander 8.51A - 64 bits "C:\Partage" is shared to "Tout le monde" (everybody) with R/W access For windows sharing, password authentification is disabled. Windows is beginning to download updates (but still not installing) And it's still not activated (30 days left) --------------------------- wxWidgets Debug Alert --------------------------- ..\..\src\common\string.cpp(1186): assert "c < 0x80" failed in wxString::FromAscii(): Non-ASCII value passed to FromAscii(). Call stack: [00] 000000013F22EC59 [01] 000000013F230184 [02] 000000013F1DAB17 [03] 000000013F1DB5F7 [04] 000000013F1E22EF [05] 000000013F141192 [06] 000000013F24636D [07] 000000013F215ED4 [08] 000000013F216D09 [09] 000000013F216DAD [10] 000000013F21708A [11] 000000013F216013 [12] 000000013F263F7C [13] 000000013F2958D3 [14] TranslateMessageEx [15] TranslateMessage [16] IsDialogMessageW [17] 000000013F376258 [18] 000000013F375E82 [19] 000000013F3761B8 [20] 000000013F22BDFE Do you want to stop the program? You can also choose [Cancel] to suppress further warnings. --------------------------- Oui Non Annuler --------------------------- I wonder if the problem is not generated because of the Name of the computer. This morning this computer name was "Surveillance-PC" and it was working well. For the previous time I got this error, it was "Clémence-PC" if I remember well ! I will try changing the computer's name, then create a new user name, and if it still doesn't works, try re-reinstalling Windows as "Surveillance-PC" and install boinc without touching anything. Bye !

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.