|
1)
Message boards :
Android :
BOINC Android Client 7.18.1 available
(Message 109532)
Posted 7 Aug 2022 by Masse Post: Thanks again! |
|
2)
Message boards :
Android :
BOINC Android Client 7.18.1 available
(Message 109527)
Posted 7 Aug 2022 by Masse Post: Thanks! |
|
3)
Message boards :
Android :
BOINC Android Client 7.18.1 available
(Message 109525)
Posted 7 Aug 2022 by Masse Post: I thought about that at first, but everything is a mess over there. It doesn't make any sense with my dyslexia ... |
|
4)
Message boards :
Android :
BOINC Android Client 7.18.1 available
(Message 109523)
Posted 7 Aug 2022 by Masse Post: I have been running BOINC projects on PC for awhile and wanted to make use of all the ARMv7/8 stuff I have (several SBCs, mobiles and a tablet). Those are using Android 4.4.2 to 11, all with BOINC 7.18.1. Most of them are running fine, but a couple are some pain. All of the devices are 100% dedicated to BOINC, with unnecessary stuff disabled/removed (mobiles+tablet). BOINC is excluded from optimization in all mobiles, but not in the tablet (not available) and SBCs (no need). All devices are air cooled. Case #1 - Xiaomi Redmi Note 9 Pro (Android 11) * Works fine when display is active, but slows down when display is inactive. May be an Android issue. Optimization settings does not seems to matter. All the other mobiles I have, do not have this issue. (None of the SBCs either.) Case #2 - Huawei MediaPad M3 Lite 10 (Android 7) * The same as Redmi Note 9 Pro. * When reactivating the display on the MediaPad, the app occasionally crash. At next startup, all the running tasks have restarted from the beginning. Case #3 - MBX MXQ (Android 4.4.2) * BOINC installs fine and receives WUs, but refuses to do anything. Claims that battery needs to be charged above 10% (minimum setting). The MXQ have no battery and is DC supplied only. When disabling battery use in the settings, BOINC demands DC power to be connected first. At this point, BOINC is hogging the system, regardless of settings and has to be removed/uninstalled completely, before regaining the normal performance. Have also tried BOINC 7.16.5, but the same. It has been working with an earlier version, but can not recall which. Have tried BOINC 7.4.41/43 and 7.4.51/53, but all of them have other issues, like not connecting to projects. Not even with URLs. Have not checked 7.0.x, 7.1.x and 7.2.x versions. |
|
5)
Message boards :
Questions and problems :
Issues after every [L]Ubuntu system update.
(Message 108381)
Posted 9 Jun 2022 by Masse Post: Thanks for the tip! |
|
6)
Message boards :
Questions and problems :
Issues after every [L]Ubuntu system update.
(Message 108380)
Posted 9 Jun 2022 by Masse Post: Checked accordingly to your instructions and from the terminal it reported only 'boinc' and 'video render' as members. Added myself and still not a member. Checked via GUI and I was the only member. |
|
7)
Message boards :
Questions and problems :
Issues after every [L]Ubuntu system update.
(Message 108378)
Posted 9 Jun 2022 by Masse Post: OK, prior to my posting, I have been searching for the error code on the Internet and found nothing but other BOINC related codes. The directory, sub directories and files of concern have all the correct privileges (boinc/boinc), except for symlinks, but it shouldn't matter. Interesting enough, the remaining computer which I have not rebooted yet have been somewhat problematic regarding filesystems. The system rejects write operations on a internal disk with NTFS, where I keep data used both in Linux and Windows. I even for awhile had a secondary disk with fs4, that was 'write protected'. Reinstalling the OS have not changed any thing. (I have experienced that Windows traditionally mess with hard drives that contain file systems other than those creates by M$. Windows ignores fs* and Debian/Ubuntu can use, but don't always behave properly with exFAT, according to own experience.) This computer behave nicely with Windows, so I can rule out hardware issues. All files and directories are set to root privileges for some unknown reason and it can not be changed, even logged in as root. Used as external drive with USB, no problems, but that's not a long term solution ... I have posted this issue on the Ubuntu forum several months ago, but no respond. One of the two computers where BOINC don't start had this issue once, but disappeared after reinstalling the OS. Something I remembered from earlier occurrences. Every time BOINC failed to start after a system update (with required reboot), the Nvidia driver was updated to some degree. Now with driver v510 and earlier sometimes with v495, but not always. I doubt it relates, but I have noticed that Nvidia drivers has been picky when rearranging GPUs between my computers due to thermal issues. (L)Ubuntu may then end up in emergency mode due to failed video driver. (Never had this specific kind of issue with Windows. If eventually failed, Windows falls back to standard VGA resolution and it's an easy fix) Unfortunately, I'm not experienced enough with Linux yet to fix it, so it's much faster process to reinstall everything from scratch. This time, I would like to avoid that, due to all hours spent. |
|
8)
Message boards :
Questions and problems :
Issues after every [L]Ubuntu system update.
(Message 108377)
Posted 9 Jun 2022 by Masse Post: Yes, I started to remove those in the directories which the client was complaining about and later the rest. No change, except for complaining about other slots. (Interesting that lock files are used. I remember those from the early days of Windows, before M$ learned how to skip them.) I always start the client using a terminal and got all the status from there. Next the manager. In this situation, the manager complaint about the client not running. Earlier times when this happened, I didn't have any unreported WU's and not that many in progress, so I uninstalled both the client and the manager, emptied the /var/lib/boinc-client/ directory and started over. Problem "solved" "quick 'n' dirty". This time, it's different ... |
|
9)
Message boards :
Questions and problems :
Issues after every [L]Ubuntu system update.
(Message 108367)
Posted 9 Jun 2022 by Masse Post: After recent (L)Ubuntu (critical) system updates, the client refuses to start after required reboot. This is the 7.18.1 version, supplied by the Ubuntu update system. I have experienced this issue with 7.16.x too, but less frequent. The only thing reported by the client is "status=192/n/a" and a random number of "dir_open: Could not open directory 'slot/xx' from '/var/lib/boinc-client'." A huge number of empty "http_temp_xxxx" files are generated in /var/lib/boinc-client/. (File system is OK.) Log files, except for project related, are empty too. So far, the only way I found around it, is to remove projects (WU's and all) one by one and test. Always ending up removing all of it. Reinstalling client and manager don't change anything. If I 'reset it' again, I will be loosing a number of completed and unreported WU's. (Yes, Collats Conjecture is down due to a physical move, due to several political issues ...). I have now two computers with this issue and one that I need to reboot (client still working) ... Downloaded 7.4.22, but installing it creates a new work directory (not capable to handle finished WU's and in progress ...), so no go. |
|
10)
Message boards :
Questions and problems :
Issues with connecting to some projects
(Message 105613)
Posted 3 Oct 2021 by Masse Post: It's kind of solved ... Installed an extra hard drive with Lubuntu. Now, it's working and have to find a way to replace Windows completely ... |
|
11)
Message boards :
Questions and problems :
Issues with connecting to some projects
(Message 105607)
Posted 2 Oct 2021 by Masse Post: Realised that this file was not included in any of the mentioned installers for Windows. Started to check one of my Lubuntu boxes and yes, there was one. Installed fine in Windows, but didn't help. Copied the stuff in your '#4540' link and after creating the file, it installed fine too, but same result (thanx anyway). Noticed that this one is valid to 2028-01-28, while the one from the Lubuntu box is valid to 2030-12-31, which doesn't matter right now. (Also the publisher also differed.) I will continue to check any progress the #4540 for any progress. BOINC doesn't seem persistent checking the projects of concern either, as after every forced update, it starts to count down for an automatic attempt 24h later ... With computer hardware experience since mid 1980's, I wish I had started with Linux earlier than late May this year (when I started with BOINC again) and left Windows behind years ago ... :( |
|
12)
Message boards :
Questions and problems :
Issues with connecting to some projects
(Message 105601)
Posted 2 Oct 2021 by Masse Post: I have a couple of computers running BOINC and have issues with just one - the only one that is running Windows (7 SP1 - Did a OS and project comparison a couple of month ago and all projects tested in Win10 [21H1] is notably slower than in both Win7SP1 and Lubuntu 21.04. Win10 also have serious security issues, actually more than Win7 [which I have seen at work] ... and I use some software that only run in Windows. I could set up a Lubuntu system and run Windows virtually, but I don't have the time required and the desire to do that. In the end, it will slow down the computer and I don't like that ...). For some reason, I can't figure out why BOINC can not connect to several projects. I noticed this yesterday due to the low stat's. These do not work - Collatz Conjecture (my primary GPU project of choice) Moo! Wrapper (not interested in this, as long as they refuse to deal with their long time team creation issue - reCAPTCHA) Universe@Home (my primary CPU project of choice) but these do - Cosmology@Home (same as Moo! Wrapper) Einstein@Home (just for connection test, bad rewards ...) MilkyWay@Home (my 'backup' CPU/GPU project of choice, when any of the two primary fails) Rosetta@Home (just for connection test, don't like some of their present stuff) Asteroids@Home is shut down due to hardware breakdown, so no testing available. Excerpt from log - 2021-10-02 13:06:55 | collatz | update requested by user At first, it looks like the issue is related to the projects of concern, but all my other computers with Lubuntu 21.04 works fine and don't have this issue. Have checked the local network and have also full Internet access (I remotely check/control the other clients from the Win box). Anti-virus/firewall software don't interfere and router firewall don't block (Have earlier experience of anti-virus software like Comodo may persistently put BOINC into quarantine!). If the router did, all the other computers would have been blocked in the same manner. Windows own [crappy] firewall is turned off. Have even tried to do a rollback on Windows, but it didn't change anything. Have tried different clean installs of BOINC 7.16.11 (using this one), 7.8.3 and 7.6.22, but no difference. (Upgraded VirtualBox to 6.1.26 some days ago and the installer included in the 'vbox' versions of BOINC installer overwrites with 6.1.12, 5.1.26 and 5.0.12 respectively - no version check, so it downgrade.) Have also tried to restart the projects in BOINC. |
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.