SqueezePlay OS (Version 3) for OpenFrame

[roobarb!]

Hi..
What king of video drivers does this build has ? Can it play 720p ?

Just the GMA500 kernel drivers, but it'll play 720p just fine. It won't handle 1080p, but the scaling for the 800x480 screen looks pretty terrible anyway.

[-=xXx=-]

That's good...
I'm waiting for OpenFrame 2 with dect want to install softphone on SqueezePlay OS with video support, Do you think it would work ?
As I know you have one of this devices....

[roobarb!]

I'm waiting for OpenFrame 2 with dect want to install softphone on SqueezePlay OS with video support, Do you think it would work ?
As I know you have one of this devices....

The hardware support should be fine, it'd just be a case of making sure the drivers are firing up. If you find that a piece of hardware has kernel driver support, I can always add it to a new kernel if it's not already there. Just let me know which drivers are required.

Other than that, I can't see any reason it couldn't be made to work.

[mattg]

Sorry if this has been covered elsewhere and my google foo is not strong enough.

But since moving to v3.03 I have found that auto reconnect of the jogglers back to lms seems to fail if my wireless router is rebooted.
If I go in to the network settings, the IP is still valid, but I cannot connect to the device via ssh, and the device is unable to communicate with the LMS unless I reboot the joggler.

Any thoughts?

O2 Jogglers
SQPOS 3.03 in internal memory
Wireless connection
LMS on windows server
Reserved IPs

[roobarb!]

But since moving to v3.03 I have found that auto reconnect of the jogglers back to lms seems to fail if my wireless router is rebooted.

Hmm. That's a new one on me; I assume you're using the normal RT2770 internal wireless card?

I've not got much to offer on this, though I'll test it on my system at home and see if I can replicate the problem.

[mattg]

Well I guess its that, yes I'm using the std internal wireless.

Although I guess the only other thing that has happened are updates to my wireless ap. So I'll revert to an older version just to check. And i'll downgrade my LMS just in case it could be that.

I'm happy to believe its not 3.03 but it was the obvious first choice and I only noticed it with that. If its not a known issue and you can't reproduce, I guess I'll script something for the time being until I get to the bottom of it.

Thanks for the reply, I'll update as I know more.

Cheers.

[roobarb!]

Although I guess the only other thing that has happened are updates to my wireless ap. So I'll revert to an older version just to check. And i'll downgrade my LMS just in case it could be that.

If you can't ping the Joggler from another device, LMS won't be causing the issue. It does sound like a genuine wireless reconnection issue, either on behalf of the Joggler or the AP.

I'm happy to believe its not 3.03 but it was the obvious first choice and I only noticed it with that. If its not a known issue and you can't reproduce, I guess I'll script something for the time being until I get to the bottom of it.

I gave it a shot last night and both of the Jogglers I had hooked up to wireless, one with the RT2700 (normal internal wireless card) and the other with the WNDA3200 (802.11n 5GHz), reconnected shortly after the wifi signal came back. It's not exactly an exhaustive test, I know!

You mention scripting something; you could pop together a bash script that tries to ping your router every minute or so - if it fails more than a couple of times, you could then get it to trigger an ifdown, ifup on wifi0. That might do the trick.

[Finchlean]

I also had problems with SqPOS v3.03 and wireless access to LMS, wired network was fine.
Fixed by updating (SSH to Joggler) and type:

sudo apt-get clean
sudo apt-get update
sudo apt-get upgrade

Now wireless works fine

[Finchlean]

Different problem here with SqPOS Ver 3.
I have my Joggler connected to USB DAC - Audiolab 8200.
Most of my music is 16/44.1 and some is 24/96 but it all plays at 24bit/44.1KHz.

Any ideas?
Cheers

[mattg]

Thanks roobarb! for taking some of your own time to try it out, you are a gent.

Yes, by restarting the network or rebooting the device it seems to fix it. Before trying a fix I will give Finchleans update suggestion a go and then see what happens before relying on a home made bodge

Thanks for the help.
Matt

[sutty81]

Hi Roobarb/All,

Thanks for the great program! I've been using squeezeplay OS on my three home jogglers for a while and I love it. Just having a small issue with the triode spotify plugin - I've posed over at slimdevices but there doesn't seem to be an obvious solution - thought I might put it on your radar as it could possibly be a refresh issue with squeezeplay?

Does anyone else have to do this to refresh their playlists in triode's spotify plugin?

eg. playlists are like this <before changes>

inbox
starred
pl1
pl2
pl3

then I go and make some changes on mobile or desktop:

inbox
starred
pl4
pl5
pl6
pl1
pl2
pl3

If I make any new playlists on another device, when I go back to the joggler, the list of playlists remains as i left it, but when I go in to the playlist, it's in the new order:

inbox
starred
pl1 ->pl4 content
pl2 ->pl5 content
pl3 ->pl6 content
etc.

I can manually refresh the order by navigating into a new playlist, then exiting back to the main spotify menu, then entering 'playlists' again. Not a huge issue but would be nice to enter a refreshed playlists list each time.

Just thinking as well, might be worth me dropping a line to the developer of the joggler software (squeezeplay os - also great) as it could possibly be an issue there.

LMS 7.7.3 on Windows 7.

Thanks for any suggestions.

[mattg]

So I tried the update, ans still no difference. When it stops working, if I go into the networking settings, it shows "no network address has been assigned to the wireless interface (wlan0)." at the top.

Choosing relaunch from the quit option doesn't resolve it, only a full reboot does. I am working on a few other tests, but wanted to let you know the situation so far.

[chris]

I haven't been able to use my joggler with sqpos because it gets stuck trying to launch squeezeplay. I'm using a sabre DAC now that I've given up on trying to get the schiit modi to work but am having the same exact problem .

With the sabre DAC and running sqpos either internally or externally it boots using the internal audio interface. If I go to audio settings, change it to external and reboot, it gets stuck in a loop trying to launch just constantly cycling between the squeezeplay logo and "last tty1 login", adding another "last tty1 login" line for failed attempt at launching squeezeplay. It tries and fails once every 2.5 seconds.

Does anyone have any ideas (logs to check, things to try manually) to help me get this working?

[Man in a van]

Have you installed EDO?


ronnie

[chris]

Have you installed EDO?


ronnie

well now I have. seems too obvious...

thanks

EDIT:
I spoke too soon. Still busted.

BUT... It turns out what actually fixed it was getting rid if .xinitrc and launching squeezeplay.sh manually. So...

Launching it manually works (but I get these 'errors')

Code: Select all

Last login: Sun Mar 22 23:33:36 2015
joggler@openframe:~$ /opt/squeezeplay/bin/squeezeplay.sh 
amixer: Unable to find simple control 'Auto-Mute Mode',0

shairport: no process found
joggler@openframe:~$ Starting Shairport as SqueezePlay...
Listening for connections.

Squeezeplay 7.7.2 r9710
20150322 23:34:13.285 INFO   squeezeplay - JiveMain.lua:273 SqueezePlay version 7.7.2 r9710
20150322 23:34:13.435 INFO   squeezeplay.ui.draw - jiveL_initSDL:181 800,480 32 bits/pixel 4 bytes/pixel [R<<16 G<<8 B<<0]
20150322 23:34:13.436 INFO   squeezeplay.ui.draw - jiveL_initSDL:182 Hardware acceleration is not available
20150322 23:34:13.598 INFO   squeezeplay.applets - AppletManager.lua:91 User Path: /home/joggler/.squeezeplay/userpath
20150322 23:34:13.786 INFO   squeezeplay.applets - AppletManager.lua:317 Registering: EnhancedDigitalOutput
20150322 23:34:13.786 INFO   applet.EnhancedDigitalOutput - EnhancedDigitalOutputMeta.lua:117 playbackDevice: hw:CARD=Audio bufferTime: 20000 periodCount: 2
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM disabled
20150322 23:34:14.288 ERROR  audio.output - decode_alsa_fork:178 jive_alsa failed to start

blah blah blah

20150322 23:34:17.905 WARN   net.comet - Comet.lua:888 Comet {mysqueezebox.com}: _response, /9062231Xf19059c76befd3dacc1f156195da0d83XdfdfdfdfbfffX0X1427067256X5cf91cef/slim/request id=nil failed: request ["df:df:df:df:bf:ff", ["menu", 0, 100, "direct:1"]] failed with error: Bad dispatch!
20150322 23:34:17.906 ERROR  net.comet - Comet.lua:940 No id. event:
stack traceback:
	/opt/squeezeplay/share/jive/jive/net/Comet.lua:940: in function '_response'
	/opt/squeezeplay/share/jive/jive/net/Comet.lua:816: in function </opt/squeezeplay/share/jive/jive/net/Comet.lua:807>

It still works with those errors so maybe it's an issue with /etc/init/tty1.conf and thats why I keep getting the login/logout cycle every 3 seconds? I just don't get why I can run it manually but it fails with .xinitrc?

[Man in a van]

Chris, a quick google gave me this


http://forums.slimdevices.com/showthrea ... ugin/page8


I don't know if this applies to you as I don't understand the shairport thing.

I seem to recall reading on a post somewhere, that it does take exclusive control or something (in what context I can't remember)

Not much help am I

Ronnie

We are talking the EDO supplied by Wilberforce?

[chris]

Chris, a quick google gave me this


http://forums.slimdevices.com/showthrea ... ugin/page8


I don't know if this applies to you as I don't understand the shairport thing.

I seem to recall reading on a post somewhere, that it does take exclusive control or something (in what context I can't remember)

Not much help am I

Ronnie

We are talking the EDO supplied by Wilberforce?

Indeed, we are talking about Wilberforce's EDO port. The problem with EDO is it breaks shairport. I'm not convinced that shairport is the issue though since it looks to me like it's checking to see if shairport is already running, it isn't, then it starts.

It seems like the issue is the joggler/tty1 respawn. I'm not sure why it's constantly logging out/back in, whether it's something crashing or it's runtime isn't correct? The whole getty respawn thing is out of my league.

[Man in a van]

Chris, a quick google gave me this


http://forums.slimdevices.com/showthrea ... ugin/page8


I don't know if this applies to you as I don't understand the shairport thing.

I seem to recall reading on a post somewhere, that it does take exclusive control or something (in what context I can't remember)

Not much help am I

Ronnie

We are talking the EDO supplied by Wilberforce?

Indeed, we are talking about Wilberforce's EDO port. The problem with EDO is it breaks shairport. I'm not convinced that shairport is the issue though since it looks to me like it's checking to see if shairport is already running, it isn't, then it starts.

It seems like the issue is the joggler/tty1 respawn. I'm not sure why it's constantly logging out/back in, whether it's something crashing or it's runtime isn't correct? The whole getty respawn thing is out of my league.

Is that the film about a group of students goingfoe for a walk in a wood

[vinnielo]

Trying SqueezePlay OS for the first time (onto 2GB USB).
Not going as smoothly as I would have liked.

1) It seems to keep losing connectivity to mysqueezebox, which shows as timing out when loading menu items.
2) I also can't seem to install LMS from the SqueezePlay menu.. it reports as installing in the background before the dialog box disappears.
The installation log shows no entries. Subsequently, I'm unable to log on to http://JOGGLER-IP:9000.

I'm able to access the Joggler via SSH.

I'd formatted my USB stick as FAT 32. Is this correct?
I'll check out if there might be anything up with the stick, e.g. with it being stuck in read-only, but I would have expected at least an error report in the installation log.

[gegs]

Try with a bigger USB stick than 2GB (heck, do they still make 'em that small?)
I use 8GB Sandisk ones and I've not had a problem installing LMS.