|
Pages: [1]
|
 |
|
Author
|
Topic: HOW TO: 64-bit LPL Beta (Read 2444 times)
|
po
Newbie
Posts: 18
|
I have successfully installed LPL Beta (twice), and was able to connect a LoggerPro and collect data with a UMD in a 64-bit 9.04 Ubuntu environment. I am thinking this is probably going to work for many Unixes, as Cappy's getlibs package is pretty powerful.
First, retrieve lpl.beta.tar and getlibs.deb from
wget http://www2.vernier.com/linux/lpl.beta.tar
and
wget http://frozenfox.freehostia.com/cappy/getlibs-all.deb
, respectively.
Next, install getlibs:
dpkg -i getlibs-all.deb
Now untar LPL:
tar -xvf lpl.beta.tar
Change into the Install directory:
cd Installers/
Force the install of LoggerPro and its drivers:
sudo dpkg -i --force-all vstdrivers_1.0_i386.deb
and
sudo dpkg -i --force-all vstloggerpro_3.7_i386.deb
Now they are 'installed,' but loggerpro will look for libraries that are specific to 32-bit [Ubuntu-only?] platforms.
Invoke getlibs and install these four libraries for loggerpro:
getlibs -l libgtkmm-2.4.so.1 libpangomm-1.4.so.1 libcairomm-1.0.so.1 libglibmm-2.4.so.1
After confirming their installation, your instance of loggerpro should launch and operate in the 64-bit environment:
Applications > Education > Logger Pro, or
loggerpro &
My testing was getting LPL running, hooking it to a LoggerPro, and recording some data with a UMD. By no means an extensive test, but hopefully this forum can make or break this method--until a 64-bit version of LPL is developed.
If the above doesn't work and you're in a 64-bit Ubuntu environment, simply attempting to run "loggerpro" from the command line should tell you what libraries loggerpro is looking for. Ideally this will be the case with any linux, and the libraries should be 'out there' for installation.
I didn't look too closely at Cappy's script, but hopefully those with linuxes not playing nicely with LPL can invoke --apt-file to find the libraries they need.
|
|
|
|
|
Logged
|
|
|
|
Garth
Global Moderator
Full Member
Posts: 169
|
This is fantastic. Thanks for doing all this and then publishing the results!
We've had problems in the 64-bit environment with the kernel module (vstusb.ko) that is used to communicate with LabPro and LabQuest. Go devices seemed to work ok, but not LP or LQ. Have you tried these devices?
We are investigating a solution, but it's not ready for you all yet *grin*.
-Garth
|
|
|
|
|
Logged
|
|
|
|
po
Newbie
Posts: 18
|
My labs have the green LabPro interfaces, which I misnamed above as LoggerPro boxes (woops).
The forced install of the driver package seems to have no issues at all, and the information stored in udev aligns with the 32-bit installs.
|
|
|
|
|
Logged
|
|
|
|
Kendall
Newbie
Posts: 2
|
Thank you, thank you!
Also on 64-bit Ubuntu 9.04. Works for everything I've tried so far (three temp probes, light sensor) on a LabPro, UI of course being every bit as great as usual.
|
|
|
|
|
Logged
|
|
|
|
Garth
Global Moderator
Full Member
Posts: 169
|
This is fantastic!
We've seen some issues on 64-bit systems and are working to address those, but more power to everyone who can get it going now!
-Garth
|
|
|
|
|
Logged
|
|
|
|
po
Newbie
Posts: 18
|
Great to see it worked for you as well, Kendall.
|
|
|
|
|
Logged
|
|
|
|
nc10rgro
Newbie
Posts: 2
|
After installing vstdrivers_1.0_i386.deb and vstloggerpro_3.7_i386.deb on amd64 edition of Ubuntu 9.10 i get the following error.
user@host:~$ loggerpro
loggerpro: error while loading shared libraries: libGoIO.so.2: cannot open shared object file: No such file or directory
user@host:~$
Also getdeb is unable to fetch this lib:
user@host:~$ getlibs -l libGoIO.so.2
No match for libGoIO.so.2
No packages to install
user@host:~$
|
|
|
|
|
Logged
|
|
|
|
po
Newbie
Posts: 18
|
nc:
If you're running Ubuntu 9.10, and it is up-to-date, you will probably be running the 2.6.31-19 kernel (or 16 or 17 if not). I have only had luck getting this to work with the 17 kernel--I haven't tried updating any of the working 17s to 19.
libGoIO should exist on your computer after doing the force install (it is contained within the drivers deb), do a locate on the file to confirm (locate -i libgoio). The first thing to try is rebooting.
Try a locate on vstusb.ko and make sure one exists in the folder for your kernel version. If it doesn't, you might want to look through the vstusb.ko thread, the readme in the source folder for the makefile, and try building the kernel object for your kernel version. If you are interested in trying that, I have a very simple script that will do all the work.
Finally, the libusb version of the LPL Beta shouldn't be plagued by any of these issues. I hope it is released soon!
|
|
|
|
|
Logged
|
|
|
|
Garth
Global Moderator
Full Member
Posts: 169
|
Thanks.
Yes, we will be releasing a 64-bit version that uses libusb instead of the vstusb kernel module very, very soon.
Thanks, again.
-Garth
|
|
|
|
|
Logged
|
|
|
|
Garth
Global Moderator
Full Member
Posts: 169
|
The most recent release uses libusb and thus does not need vstusb.ko.
|
|
|
|
|
Logged
|
|
|
|
|
Pages: [1]
|
|
|
|
|
|
