chill wrote:
> Is it possible to make a user at that stage too, before booting from
> the stick?
>
>
I don't know.
I tend to burn the image, connect everything to the joggler with a usb
hub, edit the .yaml, make the user and change the root password.
Reboot to see that all is OK, then
All done as root so far - still finding my feet with Linux permissions,
so didn't want any extra complications! The stray 'sudo' commands are a
left-over from copying and pasting the commands from various sources.
Yes, one nice thing about the network setup with this image is that you
can edit
chill wrote:
> If anyone else wants to go through the build steps, here's what I did
> (assuming I haven't missed anything out), starting with a fresh USB
> stick with Roobarb's 8GB Bionic image 'here'
>
make it with root access. (use sudo)
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations=U7JHY5WYHCNRU=GB_code=USD=PP%2dDonationsBF%3abtn_donateCC_LG%2egif%3aNonHosted)
if you
ralphy wrote:
> Just copy the modified InputToActionMap.lua to
> /home/tc/.jivelite/userpath/jive/InputToActionMap.lua and quit jivelite.
> When it automatically restarts jivelite will use your version instead of
> the default one.
>
> Make sure to backup your pcp configuration if you want your
ralphy wrote:
> You can safely remove these skin folders from your installed jivelite
> since you're only using JogglerSkin.
>
> share/jive/applets/{HDGridSkin,HDSkin}
> share/jive/applets/{WQVGAlargeSkin,WQVGAsmallSkin}
> share/jive/applets/{QVGAbaseSkin,QVGAlandscapeSkin,QVGAportraitSkin}
If anyone else wants to go through the build steps, here's what I did
(assuming I haven't missed anything out), starting with a fresh USB
stick with Roobarb's 8GB Bionic image 'here'
(https://birdslikewires.net/download/openframe/base/t1-ext2-8000-32-bionic-3.18.131op1.img.gz):
Code:
Got there! I had only a minimal /usr/local/etc/ts.conf, with just:
Code:
module_raw input
module linear
It turns out there's another important line (module pthres pmin=1)
So my full ts.conf file is now:
Code:
ralphy wrote:
> The Screen Switcher applet doesn't appear in the applet installer on
> Jivelite because the repo.xml doesn't include jivelite in the targets
> list.
Good to know. Maybe you can implement Screen Switcher or other applets
in that repo.xml in future releases of JiveLite. Since
ralphy wrote:
>
>
> If jivelite is still in fact using the system libSDL use the 'patchelf
> program' (https://nixos.org/patchelf.html) to set the RPATH inside the
> binary as I've found that setting LD_LIBRARY_PATH doesn't always work.
>
> patchelf --set-rpath "/usr/local/lib" jivelite
>
>
chill wrote:
> Jivelite may have linked to the old version of SDL that didn't have
> TSLIB support. That would explain why nothing I do with respect to
> TSLIB seems to make any difference to the behaviour of Jivelite.
Yes, I think that's likely what's happening.
chill wrote:
> They don't
ryangodammit wrote:
> Im trying to edit my maptoaction.lua. I understand I cant directly
> edit it but have to copy it to a different folder.
> That folder doesnt exist so I assume I have to create it as well as the
> new maptoaction.lua but it is write protected. Can I change this?
ralphy wrote:
>
> It would seem that you are getting into the same situation I had when I
> first started porting jivelite to picoreplayer from raspbian. In the
> end I uninstalled all the system provided SDL, libts, lua others and
> built them from squeezeplay. Squeezeplay creates a build
ralphy wrote:
> You can safely remove these skin folders from your installed jivelite
> since you're only using JogglerSkin.
>
> share/jive/applets/{HDGridSkin,HDSkin}
> share/jive/applets/{WQVGAlargeSkin,WQVGAsmallSkin}
> share/jive/applets/{QVGAbaseSkin,QVGAlandscapeSkin,QVGAportraitSkin}
chill wrote:
> 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
chill wrote:
> I guess my SDL build DOES have tslib support now:
> >
Code:
> > root@openframe:/usr/local/lib# ldd libSDL-1.2.so.0.11.4
> linux-gate.so.1 (0xb7719000)
> libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xb756a000)
> libts.so.0 =>
chill wrote:
>
> @Ralphy, when you said:
>
> did you mean:
> >
Code:
> > ../configure --enable-input-tslib=yes
> >
>
> ..or should that option be specified somewhere else?
Yes
Ralphy
*1*-Touch, *5*-Classics, *3*-Booms, *1*-UE Radio
Baxxy wrote:
> Sorry lalu01, that's not helpful. I point to that site in my first post
> and of course i tryed it out. My old SB-touch connected to my pCP with
> LMS shows the Screen Switcher Applet under
> settings-->advanced-->applet installer. There are applets like Album
> Flow, Daylight
I'll need to do some more experimenting this evening, but the impression
I have is that the mouse pointer is scaled down approx 50% when Jivelite
starts up, i.e. if I touch the bottom-right corner the cursor moves to
the centre of the screen, if I touch the top-right the cursor moves to
the
bernt wrote:
> Hi!
>
> I'm running LMS 7.9.1 on a ReadyNAS RN202. Will there be any performance
> benefits to run it on a RPi B and PiCorePlayer?
>
> RPi B
> CPU 700 MHZ
> RAM 512 MB
>
> RN202
> CPU 1,4 GHZ
> RAM 2 GB
>
> Regards
> Bernt
Its likely the readynas will be better, but it
A little more progress. With these environment variables:
Code:
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_TSDEVICE=/dev/input/event3
export TSLIB_CALIBFILE=/usr/local//etc/pointercal
export TSLIB_CONFFILE=/usr/local/etc/ts.conf
export
Hi!
I'm running LMS 7.9.1 on a ReadyNAS RN202. Will there be any performance
benefits to run it on a RPi B and PiCorePlayer?
RPi B
CPU 700 MHZ
RAM 512 MB
RN202
CPU 1,4 GHZ
RAM 2 GB
Regards
Bernt
SB Touch optical to Hegel H90, Boston Acoustics A26
Spare SB3
AirPlay Bridge to Audio Pro A10
22 matches
Mail list logo
