Beta Release of Picoscope for Linux - RPM packages

Alongside releases for Debian based systems we have compiled another range of packages destined for distribution using RPM for package management. To get your copy of the software run following commands in the terminal:

OpenSuSE 12/13 (should work for 11.4 too, untested)

Code: Select all

sudo zypper addrepo http://labs.picotech.com/rpm picoscope
sudo rpmkeys --import http://labs.picotech.com/rpm/repodata/repomd.xml.key
sudo zypper refresh
sudo zypper install picoscope


Fedora 20*

Code: Select all

sudo curl -o /etc/yum.repos.d/picoscope.repo http://labs.picotech.com/rpm/picoscope.repo
sudo rpmkeys --import http://labs.picotech.com/rpm/repodata/repomd.xml.key
sudo yum check-update
sudo yum install picoscope


* Installation method for Fedora distribution should work for others using yum updater, given they provide mono compilation. Currently there are no packages for Centos or Scientific Linux covering this requirement.

Detailed information on getting mono for CentOS6 are provided in this thread: topic13433.html

Thanks for posting - this works for me in FC19! I've got to run picoscope as su though or I get a segfault, but it does work!

I'm also not sure if it's properly configuring the user groups on RPM devices? On install I had these errors (same one for ever RPM):

Code: Select all

  Installing : picoscope-6.8.5-4r29.noarch                                                                                                         11/11
Can't exec "/var/tmp/rpm-tmp.AyUZLT": Permission denied at /usr/share/perl5/IPC/Open3.pm line 273.
open2: exec of /var/tmp/rpm-tmp.AyUZLT 1 failed at /usr/share/perl5/vendor_perl/Debconf/ConfModule.pm line 59.
warning: %post(picoscope-6.8.5-4r29.noarch) scriptlet failed, exit status 13


It's easy enough to manually create the pico user & add yourself though of course, so not a big problem! But running it as my user generates this crash:

The actual error occurs in the opening of the instrument, as this stacktrace shows (last line)

Code: Select all

Native stacktrace:
   /usr/bin/mono() [0x49df09]
   /usr/bin/mono() [0x4eecbb]
   /usr/bin/mono() [0x42214d]
   /lib64/libpthread.so.0() [0x3b81e0ef90]
   /lib64/libusb-1.0.so.0(libusb_close+0x41) [0x3ffd605361]
   /opt/picoscope/lib/libps6000.so(+0x4a536) [0x7fb603b32536]
   /opt/picoscope/lib/libps6000.so(+0x4a642) [0x7fb603b32642]
   /opt/picoscope/lib/libps6000.so(+0x4a94d) [0x7fb603b3294d]
   /opt/picoscope/lib/libps6000.so(+0x13995) [0x7fb603afb995]
   /opt/picoscope/lib/libps6000.so(+0x13a9e) [0x7fb603afba9e]
   /opt/picoscope/lib/libps6000.so(ps6000OpenUnit+0x198) [0x7fb603affdd8]
   [0x417fc8fa]


I also get an error if attemping to use the API via libps6000 under my regular username, but works under su.

Again thanks for your hard work - it's great to see it functioning, even if there are some permission issues (which are always the bane of Linux distributions of things which need to touch hardware).

-Colin

That's maybe unusual that your installation of Fedora has debconf installed (need to confirm whether it isn't standard). In the postinstall script I've made this assumption that if system has debconf -> therefore it uses dpkg -> deb packages provide configure scripts which rpm has not.

The workaround - add your user to pico group and make sure udev rules exist

1. Check if group exists, if not create it

Code: Select all

getent group pico || sudo addgroup --system pico


2. Add your user to pico supplementary group

Code: Select all

sudo bash -c "usermod -G $(groups $SUDO_USER | awk -F' ' '{ for (i = 3; i < NF ; i++) if ( $i != "pico" ) print $i }' | tr '\n' ',' | sed 's/,$//' )",pico" \$SUDO_USER"


3. Check if udev rule exists, if not create it

Code: Select all

sudo bash -c 'test -f /etc/udev/rules.d/95-pico.rules || echo ATTRS{idVendor}=="0ce9", MODE="664", GROUP="pico" > /etc/udev/rules.d/95-pico.rules'


After those elaborate one-liners PicoScope should work, as it takes effective permissions via sg (reconnect scope though). Console program may still have problems. To be sure restart your system.

Permanent fix will be included in next release...