--
You received this message because you are subscribed to the Google Groups "PicoChess" group.
To unsubscribe from this group and stop receiving emails from it, send an email to picochess+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
How large are all these binaries for the ones that work with picochess? Maybe we can schedule them in the next image?! :)
--
The engines work without problems on my machine running Raspbian Wheezy (from Jonas' image). They were compiled with gcc 4.9.2 following the instructions given by the engine authors.
The engines were compiled on a Raspberry Pi 2 with a more recent gcc version installed than the gcc version on the v0.45 image. Most engines seem to pull in developer libraries that are present on my RPi2 but absent on the image.
So the engines are running on my installation, but I'm afraid that you'll have to recompile them from source on your Raspberry. In most cases this is not very difficult.
--
--
Traceback (most recent call last):File "./picochess.py", line 23, in <module>import chessImportError: No module named 'chess'
--
You received this message because you are subscribed to the Google Groups "PicoChess" group.
To unsubscribe from this group and stop receiving emails from it, send an email to picochess+...@googlegroups.com.
While you're working on the image: could you please have a look at the PyYAML installation? PyYAML is mentioned in requirements.txt. When I installed the necessary libraries for PicoChess using pip, there was an error while compiling PyYAML: compilation aborted because pyyaml.h could not be found. All other libraries installed and/or compiled without difficulties.
Thank you,
DJ
Yes, exactly.
Just wondering if anyone else is also experimenting with alternative engines for Picochess?I have compiled some UCI chess engines on my Raspberry Pi 2 (with gcc flag -march=armv6, so they should also run on RPi B+) and they all work in Picochess 0.50. A couple of engines are missing some UCI features, most notably setting the play level. I'm switching engines using the engine parameter in picochess.ini.The engines are in order of strength:1. Stockfish 6 (source)2. Senpai 1.0 (source)3. Texel 1.05 (source)4. Hakkapeliitta 3.0 (source)5. Arasan 18.0 (source)6. GreKo 12.9 (source)7. Zurichess Bern (source)8. Cinnamon 1.2c (source)9. Sayuri 2015.08.12 (source)The following two precompiled engines also work fine with Picochess:10. Toga II 1.3.1 (binary bundled with Scid vs. PC 4.14)11. Maverick 0.6 (binary)And this engine works on RPi/RPi 2 in Scid vs. PC 4.14, but I've not yet got it working with Picochess. It runs as a Winboard engine by default and needs a flag at startup to run as an UCI engine:12. GNUChess 6.2.1 (source)
--
Yes, the build file for the Dockers images are now on github in the docker folder. It seems to work fine now (did some testing).
I will release a new image reflecting the Dockers work in a few days.
Could you please explain how to "pull the master from github"?
Thanks and merry Christmas!
Regards
Torben
--
You received this message because you are subscribed to a topic in the Google Groups "PicoChess" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/picochess/CrBSjvlY7Xg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to picochess+...@googlegroups.com.
I prepared a disk image of PicoChess v0.55 that includes the necessary libraries (and also Scid vs. PC 4.14). You're welcome to try this image. If PicoChess does not start, then please use git to install PicoChess v0.56, and pip3 to get the libraries that are mentioned in requirements.txt. If Bluetooth doesn't connect, then please check /etc/bluetooth/rfcomm.conf.
The image is available at https://drive.google.com/open?id=0B9qWkOu8LbC8SlpOdTlneWpObk0
Scid vs. PC is not included on the standard PicoChess images at dl.picochess.org. With some effort, you can compile the current version 4.15 yourself from source. Perhaps it can be installed with sudo apt-get install scid, but I'm not sure about that.
Did you try to connect to the DGT board using Bluetooth Manager? To do this, log in with username "pi" and password "picochess" and type "startx" at the command prompt. You'll find Bluetooth Manager in the menu (BTW, you will also find Scid vs. PC there). Don't forget to set a serial connection and to mark the board as a trusted device. Reboot the Pi and the connection should now be made automatically.
Next, you should update PicoChess to the latest version using git, and update the libraries with pip3.
I haven't come across the problem with /var/lib/dpkg/status before. It should not interfere with PicoChess, but it needs solving for future updates of your system. I won't have access to my Pi for this week, so can't look at the offending file. From your screenshot it appears that there is some parsing error, so probably a misplaced colon or something like that. You can open the offending file and see if you find anything like that. Otherwise, you can restore a backup of this file from /var/backups and apt-get should be working again.
--
Perhaps you have got more than one Bluetooth device in the /dev directory? I remember having had /dev/rfcomm0 and /dev/rfcomm1 (instead of only /dev/rfcomm0) some time ago, which prevented the board from autoconnecting. I removed both devices manually (sudo rm /dev/rfcomm0 and sudo rm /dev/rfcomm1 -- don't worry about deleting them, a new device will be created), rebooted and reconnected with Bluetooth Manager, and the automatic connection was restored.
Greetings,
DJ
There is a Bluetooth problem with some of the linux kernels on saving the binding. You might be running into it.
I will take a look at this image and comment more. I think I have found a base image with working Bluetooth. Will test and upload my current version soon given all the recent interest.
Shiv
On Dec 29, 2015 10:45 AM, "DJ Dekker" <chess19...@gmail.com> wrote:
>
> Hmm, this is quite remarkable. Does it help if you specify dgt-port = /dev/rfcomm1 in picochess.ini?
>
> --
> You received this message because you are subscribed to the Google Groups "PicoChess" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to picochess+...@googlegroups.com.
sudo apt-get install bluez-utils (Complete reinstall of the utils)
reboot->
startx -> start a trusted bluetooth Connection with your board ->
Reboot
On the next start everthing should be fine.
Hope it helps
Michael
You received this message because you are subscribed to a topic in the Google Groups "PicoChess" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/picochess/CrBSjvlY7Xg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to picochess+...@googlegroups.com.
sudo apt-get install bluez && sudo apt-get install bluez-utils
To unsubscribe from this group and all its topics, send an email to picochess+unsubscribe@googlegroups.com.
I'm sorry to read that the image is still not working for you. Two suggestions in case you might want to give it a final try. ;)
1) My RPi2 has a USB Bluetooth adapter connected which needed particular firmware. This firmware was not on the original PicoChess image by Jonas, so I added it according to the instructions on the website below. Perhaps removing the firmware might help you?
http://plugable.com/2014/06/23/plugable-usb-bluetooth-adapter-solving-hfphsp-profile-issues-on-linux
2) I encountered the same problem as you when running Raspbian Jessie and Ubuntu 15.04 on my RPi2. Under these operating systems the Pi would only connect to the DGT board manually, never automatically at boot. It turned out that both Jessie and Ubuntu 15.04 use BlueZ 5, which changed the way in which Bluetooth serial devices get connected to the computer. Raspbian Wheezy, on the other hand, has the "old" BlueZ 4, which has always worked fine for PicoChess. Could it perhaps be the case that you somehow updated your BlueZ 4 to version 5, thus breaking autoconnection? This could have happened when /etc/apt/sources.list mentions "jessie" instead of "wheezy".
Greetings,
DJ
--
You received this message because you are subscribed to a topic in the Google Groups "PicoChess" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/picochess/CrBSjvlY7Xg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to picochess+...@googlegroups.com.
Fyi, i have an image almost ready except for the Bluetooth auto detection, trying to see if I can get that done before uploading..
Shiv
--
You received this message because you are subscribed to a topic in the Google Groups "PicoChess" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/picochess/CrBSjvlY7Xg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to picochess+...@googlegroups.com.