No WU can validate because of this error:

<core_client_version>7.18.1</core_client_version>
<![CDATA[
<stderr_txt>
16:51:19 (1967): initialisation
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.

Made sure the <allow_remote_gui_rpc> is set to 1 but this is about permissions to access the pci dev.
Guess I could somehow sudo the WUProp or run from the root account; but it should work properly without those solutions.
I'm not a Linux expert and not sure what's wrong.

Maybe it's because I didn't give BOINC an explicit data folder and it made /mnt/c/Windows/System32 it's data folder? (strange choice)

At least I successfully manually (no Windows store) installed Ubuntu 22 LST into WSL 1 on Windows Pro 2019, gave Windows an XServer then successfully ran the Linux BOINC Mgr GUI to access the WSL BOINC client and got Gerasim (Linux) and WUProp running.

Proud of my Linux-ignorant self for doing that all in a night.
But I thought a single BOINC Manager could control WSL and native Windows WU's from the same port. Not that I'd be running two BOINC clients and two BOINC Mgrs; guess this is where BoincTasks shines.

I'll try moving the data folder and then maybe just install Ubuntu in a VM so I can get this Gerasim (Linux) done.

The AntiX BOINC 7.18.1 install went badly. The install sh script doesn't place the boinc executables in the usr/lib/boinc-client folder and fails to start from the home dir. It complains about gtk+ libraries that appear to be installed. More permissions issues? I'm weak at permissions troubleshooting.

When I google the pcilib error most contain something around Raspbian.
Why WSL 1 vs WSL 2?

The first time I tried to monitor a client in WSL 2 on via BOINCTasks all on the same PC it was kinda finicky. WSL gave it some odd IP address but often BOINCTasks wouldn't monitor both the native client and the WSL client on the same PC. The last time I just used boinctui to view progress.

When I google the pcilib error most contain something around Raspbian.
Why WSL 1 vs WSL 2?

Turned off a lot of services, including Windows Update and the store, also it's Windows 18363.1556. I was planning on just wiping the OS drive and installing Linux but it's a badge hunter, with an AMD and NVidia card, so Windows + WSL2 is going to be the best choice, eventually.

Breaking things or taking the manual route can improve your skills. Things I learned that maybe could help someone else here:
1) You can Unzip the Linux.appx or Linux.AppBundle packages and install manually.
2) There are X servers for Windows (XMing is one) that let the WSL communicate with the display. In WSL BASH type 'export DISPLAY=:0' to send video output to the Windows X Server.
3) Windows File Manager can read the rootfs folder but even an admin can't always move Linux files (Like cc_config.xml) and, if you do, the permissions can get scrambled.
4) I found PCmanFM File Manager for KDE(?), installed it and was using in on the Windows X server. It successfully moved the xml BOINC config files out of /mnt/c/wondows/system32 to /var/lib/boinc-client where they belonged. Windows built in File Manager acted like they were moved but they were still there.
(I have some numb fingers and arthritis so command prompt typing errors slow me down.)
5) I completely forgot the Debian inet.d method of starting apps. Now I start BOINC with 'sudo /etc/init.d/boinc-client start' and the data folders are now properly placed.
6) Edited the boinc-client script in /etc/init.d with a decent Linux editor named Geany to add --gui_rpc_port 31414 so the WSl client had a different port.
7) Learned that Windows Notepad or 3rd party app, Notepad++, change the permissions of script files in the rootfs so they no longer execute...
8) Used PCmanFM to correct the boinc-client script permissions (nice product).
9) Never seriously used BoincTasks, but faced with two BOINC clients on one machine, d/led it and spent 2 hours learning to use it.
10) had to hunt down the correct gui_rpc_auth.cfg client passwords so that BoincTasks can log in.
11) BoincTasks showed how many BOINC clients are advertising theirselves on my network. Should have been none. I'll try using BoincTasks for central management later. Maybe it can manage the BOINC clients that or contained within VM's? Mikey and I were just discussing that.
12) Learned more about the BOINC Docker project and maybe I could have just ran Gerasim (Linux) in a Docker, or in the WSL, instead of developing my own Linux VM. Docker is a VM contained BOINC client and it can be managed by an external BOINC Manager or BoincTasks.

13) WUProps has some issues using the WSL (posting a new question about that in another post).


So, I went off the beaten path and learned a bunch of things. Worth it.
When I get to an WSL 2 install, I'll be able to contrast it to the things I learned on this WSL 1 experiment.

The first time I tried to monitor a client in WSL 2 on via BOINCTasks all on the same PC it was kinda finicky. WSL gave it some odd IP address but often BOINCTasks wouldn't monitor both the native client and the WSL client on the same PC. The last time I just used boinctui to view progress.

If you assign two different rpc_gui_port (add the --rpc_gui_port 31414 in init.d/boinc-client script BOINC_OPTS= string or in the Windows shortcut that starts the Windows BOINC client or in a Windows task schedule that start upon login) then that issue supposed to clear up. Has so far on mine. I also changed the WSL client name in cc_config.xml to NAME-WSL.

Maybe it's something different about the WSL 2 VM style that creates an alternate local IP. Port change still might help, IDK.

The error changed now that BOINC is started with 'sudo /etc/init.d/boinc-client start'.

The WUProp WU running under WSL is attempting to track the Windows BOINC client WU's. I reset WUProp in the WSL and changed the RPC port. The WUProp WU running under Windows BOINC client does not see the Gerasim (Linux) hours and is functioning like it was.


Here's the errors (I think they are all WU's running under Windows client):

<core_client_version>7.18.1</core_client_version>
<![CDATA[
<stderr_txt>
pp) - app_name:
02:21:58 (1327): Erreur assignation user_friendly_name (node app) - app_name:
02:21:58 (1327): Erreur assignation user_friendly_name (node app) - app_name:
02:22:58 (1327): Erreur assignation project_name (node result) - project_url: https://www.sidock.si/sidock/
02:22:58 (1327): Erreur assignation project_name (node result) - project_url: https://www.sidock.si/sidock/
02:22:58 (1327): Erreur assignation project_name (node result) - project_url: http://srbase.my-firewall.org/sr5/
02:22:58 (1327): Erreur assignation project_name (node result) - project_url: http://srbase.my-firewall.org/sr5/
02:22:58 (1327): Erreur assignation project_name (node result) - project_url: http://srbase.my-firewall.org/sr5/

No WU can validate because of this error:

<core_client_version>7.18.1</core_client_version>
<![CDATA[
<stderr_txt>
16:51:19 (1967): initialisation
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.

Made sure the <allow_remote_gui_rpc> is set to 1 but this is about permissions to access the pci dev.
Guess I could somehow sudo the WUProp or run from the root account; but it should work properly without those solutions.
I'm not a Linux expert and not sure what's wrong.

Maybe it's because I didn't give BOINC an explicit data folder and it made /mnt/c/Windows/System32 it's data folder? (strange choice)

At least I successfully manually (no Windows store) installed Ubuntu 22 LST into WSL 1 on Windows Pro 2019, gave Windows an XServer then successfully ran the Linux BOINC Mgr GUI to access the WSL BOINC client and got Gerasim (Linux) and WUProp running.

Proud of my Linux-ignorant self for doing that all in a night.
But I thought a single BOINC Manager could control WSL and native Windows WU's from the same port. Not that I'd be running two BOINC clients and two BOINC Mgrs; guess this is where BoincTasks shines.

I'll try moving the data folder and then maybe just install Ubuntu in a VM so I can get this Gerasim (Linux) done.

The AntiX BOINC 7.18.1 install went badly. The install sh script doesn't place the boinc executables in the usr/lib/boinc-client folder and fails to start from the home dir. It complains about gtk+ libraries that appear to be installed. More permissions issues? I'm weak at permissions troubleshooting.

It's been a problem for awhile now that Boinc doesn't work like it used to in the latest Linux versions, yes it's a permission thing but no I don't know how to fix it. This was discussed in the Einstein forums awhile back and I think it was Keith Myers who posted the needed command line stuff to fix it.

Turning off <allow_remote_rpc_gui> brings back:

pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.

It still tries to watch over the Windows apps:

03:22:13 (1499): Erreur assignation project_name (node result) - project_url: https://www.sidock.si/sidock/
03:22:13 (1499): Erreur assignation project_name (node result) - project_url: http://srbase.my-firewall.org/sr5/
03:22:13 (1499): Erreur assignation user_friendly_name (node app) - app_name:

And then reports it can't connect to 3 diff localhosts ports:

04:21:14 (1499): can't connect to localhost04:21:14 (1499): Erreur reception active_result
04:22:14 (1499): can't connect to localhost04:22:14 (1499): Erreur reception cc_status
04:22:45 (1499): Mise en veille (derniere requete date de moins de 30 secondes
04:22:45 (1499): can't connect to localhost04:22:45 (1499): Erreur reception result (new WU)
04:22:45 (1499): called boinc_finish(0)

IDK how to fix this.
Guess the AntiX BOINC needs to upgrade or a fresh Linux install somewhere, if I find some time today.

To run WuProp on WSL, you have to create a file named app_config.xml.

<app_config>

<app_version>
<app_name>data_collect_v4</app_name>
<plan_class>nci</plan_class>
<avg_ncpus>0.01</avg_ncpus>
<cmdline>-p 31422</cmdline>
</app_version>

</app_config>

Replace 31422 by the GUI RPC port number used in WSL.

To run WuProp on WSL, you have to create a file named app_config.xml.

<app_config>

<app_version>
<app_name>data_collect_v4</app_name>
<plan_class>nci</plan_class>
<avg_ncpus>0.01</avg_ncpus>
<cmdline>-p 31422</cmdline>
</app_version>

</app_config>

Replace 31422 by the GUI RPC port number used in WSL.

I slept on it and was fixing breakfast, wondering if there was a command line to communicate WUProp the proper port. Did an app_config.xml for WUProp years back and just remembering it after reading your post.

Thanks.

Damn, the default forum search on here is 30 days.
If you do advanced search: unlimited then this question has been answered many times.

EDIT:
Ah geesh, here is my past self having the same question in 2015:
http://wuprop.boinc-af.org/forum_thread.php?id=374&postid=3560#3560