Home of the Squeezebox™ & Transporter® network music players.
Page 9 of 22 FirstFirst ... 789101119 ... LastLast
Results 81 to 90 of 217
  1. #81
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Posts
    957
    I've built Jivelite on the Bionic stick, using the same instructions as previously, and I've also built tslib again, and I can run ts_calibrate to create the /etc/pointercal file. The command I used to run ts_calibrate was:
    Code:
    TSLIB_FBDEVICE=/dev/fb0 TSLIB_TSDEVICE=/dev/input/event2 TSLIB_CALIBFILE=/etc/pointercal TSLIB_CONFFILE=/etc/ts.conf TSLIB_PLUGINDIR=/usr/local/lib/ts /usr/bin/ts_calibrate
    But if I run JiveLite using the command:
    Code:
    TSLIB_FBDEVICE=/dev/fb0 TSLIB_TSDEVICE=/dev/input/event2 TSLIB_CALIBFILE=/etc/pointercal TSLIB_CONFFILE=/etc/ts.conf TSLIB_PLUGINDIR=/usr/local/lib/ts /home/joggler/jivelite/bin/jivelite
    then all I get is the JiveLite splash screen before it drops back to a command line prompt without an error message. What would cause this? Is there something wrong with my Lua setup perhaps, or my tslib setup?

  2. #82
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    2,159
    Check if your SDL library even has support for tslib built in I suspect probably not. None of the intel systems I checked were linked against libts.

    From picoreplayer
    Code:
    tc@rpibp-wls:/opt/jivelite/lib$ ldd libSDL-1.2.so.0.11.4
            libm.so.6 => /lib/libm.so.6 (0xb6e6a000)
            libts-1.0.so.0 => /usr/local/lib/libts-1.0.so.0 (0xb6e56000)
            libdl.so.2 => /lib/libdl.so.2 (0xb6e43000)
            libpthread.so.0 => /lib/libpthread.so.0 (0xb6e19000)
            librt.so.1 => /lib/librt.so.1 (0xb6e02000)
            libc.so.6 => /lib/libc.so.6 (0xb6cc4000)
            /lib/ld-linux-armhf.so.3 (0xb6f5f000)
    You'll need to build SDL and enable tslib support using the same tslib that you built previously using --enable-input-tslib=yes when you run configure.
    Ralphy

    1-Touch, 5-Classics, 3-Booms, 1-UE Radio
    Squeezebox client builds donations always appreciated.

  3. #83
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Posts
    957
    Thanks Ralphy - I'll look into that.

  4. #84
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    2,159
    Quote Originally Posted by chill View Post
    all I get is the JiveLite splash screen before it drops back to a command line prompt without an error message. What would cause this? Is there something wrong with my Lua setup perhaps, or my tslib setup?
    My jivelite sources have all logging off by default except for the version. do you at least see

    JiveLite 0.1.0

    on the console?

    If you do, then copy the attached file into $HOME/.jivelite/userpath/logconf.lua of the user you run JL as.

    I recommend redirecting the output to a file so you can wade through it afterward. ie.

    jivelite > jivelite.log 2>&1
    Attached Files Attached Files
    Ralphy

    1-Touch, 5-Classics, 3-Booms, 1-UE Radio
    Squeezebox client builds donations always appreciated.

  5. #85
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Posts
    957
    Quote Originally Posted by ralphy View Post
    Check if your SDL library even has support for tslib built in I suspect probably not. None of the intel systems I checked were linked against libts.
    Code:
    joggler@openframe:/usr/lib/i386-linux-gnu$ ldd libSDL-1.2.so.0.11.4
    	linux-gate.so.1 (0xb77c5000)
    	libasound.so.2 => /usr/lib/i386-linux-gnu/libasound.so.2 (0xb75f4000)
    	libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xb74f2000)
    	libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xb74ed000)
    	libpulse-simple.so.0 => /usr/lib/i386-linux-gnu/libpulse-simple.so.0 (0xb74e7000)
    	libpulse.so.0 => /usr/lib/i386-linux-gnu/libpulse.so.0 (0xb748d000)
    	libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xb7343000)
    	libXext.so.6 => /usr/lib/i386-linux-gnu/libXext.so.6 (0xb732e000)
    	libcaca.so.0 => /usr/lib/i386-linux-gnu/libcaca.so.0 (0xb7264000)
    	libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xb7245000)
    	libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb7069000)
    	librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xb705d000)
    	/lib/ld-linux.so.2 (0xb77c6000)
    	libpulsecommon-11.1.so => /usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-11.1.so (0xb6fd0000)
    	libdbus-1.so.3 => /lib/i386-linux-gnu/libdbus-1.so.3 (0xb6f75000)
    	libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xb6f49000)
    	libslang.so.2 => /lib/i386-linux-gnu/libslang.so.2 (0xb6d6f000)
    	libncursesw.so.5 => /lib/i386-linux-gnu/libncursesw.so.5 (0xb6d39000)
    	libtinfo.so.5 => /lib/i386-linux-gnu/libtinfo.so.5 (0xb6d16000)
    	libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xb6cf7000)
    	libsystemd.so.0 => /lib/i386-linux-gnu/libsystemd.so.0 (0xb6c67000)
    	libwrap.so.0 => /lib/i386-linux-gnu/libwrap.so.0 (0xb6c5c000)
    	libsndfile.so.1 => /usr/lib/i386-linux-gnu/libsndfile.so.1 (0xb6bcb000)
    	libasyncns.so.0 => /usr/lib/i386-linux-gnu/libasyncns.so.0 (0xb6bc4000)
    	libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xb6bc0000)
    	libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xb6bb9000)
    	liblzma.so.5 => /lib/i386-linux-gnu/liblzma.so.5 (0xb6b8d000)
    	liblz4.so.1 => /usr/lib/i386-linux-gnu/liblz4.so.1 (0xb6b77000)
    	libgcrypt.so.20 => /lib/i386-linux-gnu/libgcrypt.so.20 (0xb6a96000)
    	libnsl.so.1 => /lib/i386-linux-gnu/libnsl.so.1 (0xb6a7b000)
    	libFLAC.so.8 => /usr/lib/i386-linux-gnu/libFLAC.so.8 (0xb6a1c000)
    	libogg.so.0 => /usr/lib/i386-linux-gnu/libogg.so.0 (0xb6a13000)
    	libvorbis.so.0 => /usr/lib/i386-linux-gnu/libvorbis.so.0 (0xb69e6000)
    	libvorbisenc.so.2 => /usr/lib/i386-linux-gnu/libvorbisenc.so.2 (0xb695a000)
    	libresolv.so.2 => /lib/i386-linux-gnu/libresolv.so.2 (0xb6942000)
    	libbsd.so.0 => /lib/i386-linux-gnu/libbsd.so.0 (0xb6927000)
    	libgpg-error.so.0 => /lib/i386-linux-gnu/libgpg-error.so.0 (0xb690f000)
    Looks like you've pinpointed the (or at least 'a') problem

  6. #86
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Posts
    957
    Quote Originally Posted by ralphy View Post
    My jivelite sources have all logging off by default except for the version. do you at least see

    JiveLite 0.1.0

    on the console?

    If you do, then copy the attached file into $HOME/.jivelite/userpath/logconf.lua of the user you run JL as.

    I recommend redirecting the output to a file so you can wade through it afterward. ie.

    jivelite > jivelite.log 2>&1
    Thanks Ralphy. Yes, I do get that message on the screen, but nothing else. With that logconf file in place I now get a tonne of output! I guess these last two lines are the important ones:
    Code:
    20190127 14:52:59.312 ERROR  jivelite.ui.draw - jive_surface_set_video_mode:855 SDL_SetVideoMode(640,480,0): Couldn't set console screen info
    20190127 14:52:59.312 ERROR  jivelite.ui.draw - jiveL_set_video_mode:902 Video mode not supported: 640x480
    EDIT: This is without rebuilding SDL of course.

    EDIT2: Here's the full logfile in case it's useful:
    Attached Files Attached Files
    Last edited by chill; 2019-01-27 at 08:07.

  7. #87
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Posts
    957
    I've started again from a fresh copy of the raw Bionic image, but I still get the same error.

    Here are the steps I've taken to get to that point, after logging in as root over SSH:

    Code:
    apt-get update
    
    apt-get install build-essential
    
    apt-get install automake libtool 
    
    apt-get install git-core
    
    apt-get install libluajit-5.1-dev libsdl1.2-dev libsdl-ttf2.0-dev libsdl-gfx1.2-dev libsdl-image1.2-dev libexpat1-dev
    
    git clone git://github.com/kergoth/tslib.git
    cd tslib
    ./autogen.sh
    ./configure
    make
    sudo make install
    sudo cp -P /usr/local/lib/libts* /lib/i386-linux-gnu/
    
    wget https://www.libsdl.org/release/SDL-1.2.15.tar.gz
    tar -xvzf SDL-1.2.15.tar.gz
    cd SDL-1.2.15/
    mkdir build
    cd build
    ../configure --enable-input-tslib=yes
    make
    sudo make install
    
    cd
    mkdir luajit
    cd luajit
    git clone http://luajit.org/git/luajit-2.0.git
    cd luajit-2.0
    make
    sudo make install
    sudo ldconfig
    
    cd
    git clone https://github.com/ralph-irving/jivelite.git
    cd jivelite
    sudo make PREFIX=/usr/local
    
    #Edit /usr/local/etc/ts.conf to contain only
    module_raw input
    module linear
    
    #Use cat '/proc/bus/input/devices' to find event number for TSLIB_TSDEVICE.  Look for the section 'N: Name="AmSC OpenPeak Touchscreen Hyup05_3"', then get the event number from the line starting with 'H:', e.g. 'H: Handlers=mouse0 event3 js0'
    
    TSLIB_FBDEVICE=/dev/fb0 TSLIB_TSDEVICE=/dev/input/event3 TSLIB_CALIBFILE=/etc/pointercal TSLIB_CONFFILE=/usr/local/etc/ts.conf TSLIB_PLUGINDIR=/usr/local/lib/ts ts_calibrate
    
    #Make a $HOME/.jivelite/userpath/logconf.lua file with the contents as supplied by Ralphy above.
    
    TSLIB_FBDEVICE=/dev/fb0 TSLIB_TSDEVICE=/dev/input/event3 TSLIB_CALIBFILE=/etc/pointercal TSLIB_CONFFILE=/usr/local/etc/ts.conf TSLIB_PLUGINDIR=/usr/local/lib/ts /root/jivelite/bin/jivelite
    After doing all that, I still get the JiveLite splash screen for a moment, and the last two lines of the logfile are:
    Code:
    20190127 22:04:46.397 ERROR  jivelite.ui.draw - jive_surface_set_video_mode:855 SDL_SetVideoMode(640,480,0): Couldn't set console screen info
    20190127 22:04:46.397 ERROR  jivelite.ui.draw - jiveL_set_video_mode:902 Video mode not supported: 640x480
    The joggler screen is 800x480, so which part of this setup is responsible for asking for 640x480?
    Last edited by chill; 2019-01-28 at 11:07. Reason: Missed off a couple of steps in the libsdl build

  8. #88
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    2,159
    The splash.png image is 640x480 as that's the size of the default skin Triode used when he create Jivelite.

    Replace share/jive/jive/splash.png with the pcp splash.png I've attached or create an 800x480 png image yourself.

    and apply the attached jivelite-defaultjogglerskin.patch to change the default skin to be for the Joggler to avoid SDL trying to open the fb at 640x480 a second time.
    Attached Images Attached Images  
    Attached Files Attached Files
    Ralphy

    1-Touch, 5-Classics, 3-Booms, 1-UE Radio
    Squeezebox client builds donations always appreciated.

  9. #89
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Posts
    957
    Thanks Ralphy - I'll try those this evening.

    Changing the default skin was going to be a question for the future, as this is a very specific build for fixed hardware. In fact, I don't see a need to keep all the other skin options in the build, or the option to choose between them, so maybe I'll look at trimming those bits out later. But setting a sensible default is a good first step.

    Chris

  10. #90
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Posts
    957
    Quote Originally Posted by ralphy View Post
    Replace share/jive/jive/splash.png with the pcp splash.png I've attached or create an 800x480 png image yourself.
    I realise the pCP splash screen you posted was only for testing purposes, but I've made an 800x480 version of the original 'Jive Lite' splash screen, just by enlarging the canvas width, so the lettering is still the same size. It's white text on a transparent background, so it doesn't look right on here - the wording is properly centred, I promise!
    Attached Images Attached Images  

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •