SqueezePlay OS Beta Test

[roobarb!]

----------------------------
SqueezePlay OS Beta Test
----------------------------
Version 3.01b1 - 27th August 2014
----------------------------

It was only February when I released v2, but what with Ubuntu Trusty coming out and finally managing to get a more recent kernel to work properly with the weird internal audio on the OpenFrame 1 / Joggler, I thought I'd throw together a beta for brave souls to try out.

SqueezePlay OS v3 Beta is based on Ubuntu Trusty 14.04 and Kernel 3.14.

This is unfinished. It's not far from finished, but there are things that need testing.

To Test:

• Reliability of the original, unmodified RT2770F internal Joggler wireless card. Just configure your network see how it compares to previous versions.
• Reliability of the internal audio, particularly automatic muting of internal speakers when inserting and removing headphones.
• Does it work at all on an OpenFrame 2? I've not tried.

Known Bugs / Unusuals:

• Reading of the light sensor is currently broken, therefore automatic backlight regulation is broken. - FIXED
• Image size is rather larger than usual, as development tools are still present.
• No startup splash - output is verbose to screen. - FIXED
• External USB devices ONLY at this time.

If you'd like to try this out, please feel free. If you wish to report bugs, please do so here - but only if you have not modified your Joggler in any way (or you've put it back to how it was out of the box!).

Thanks in advance to those that give it a whirl!

[castalla]

Installed and running okay via wifi. SSH lacks root access - had to use nano to edit sshd_config file. Latest LMS 7.8.1 nightly installed - working fine

[roobarb!]

Good to hear wifi is working for you - that's pretty much my top concern with this at the moment.

SSH never had root access enabled by default... unless I made a mistake! It's always been intended to be 'sudo' via the joggler user. What did you need to edit - anything I should bear in mind?

[castalla]

I usually edit fstab - to set up a external fileserver for LMS. I usually also set a fixed ip address for wifi - so that's an edit for interfaces. I also need the root access to more easily setup the Shairplay plugin for LMS.

I like to use WinSCP which is easier to use with root access compared to the clunky nano and vi ! I'm pretty confident that sudo passwd root worked in previous versions, but not this one.

The most frustrating part of SqPlay is the setup which defaults to the 'connect to mysqueezebox.com' - which for me invariably fails! and results in a time-consuming procedure to connect to a local server. I can see why it's the default procedure . but it's a pain. I guess a option to connect to EITHER mysb or an existing LMS server mght be complicated to implement.

[roobarb!]

Huh, I wonder if that's a change in Trusty I wasn't aware of (regarding the root account). I'll check it out.

Yes, the mysqueezebox.com connection always happens when it can't see a local LMS. It used to connect reasonably reliably, but it's become worse and worse over time. I'm not sure what to do about it, to be honest - it is annoying, but perhaps some people need it and persist.

[roobarb!]

Huh, I wonder if that's a change in Trusty I wasn't aware of (regarding the root account). I'll check it out.

Checked it out - Trusty defaults to public key authentication for root, disabling the password. I should probably change that back for the Joggler.

[castalla]

Possible hitch - I did a shutdown from the menu. It got stuck at killing processes [FAIL] Had to unplug.


No more time today to test further.

[roobarb!]

Possible hitch - I did a shutdown from the menu. It got stuck at killing processes [FAIL] Had to unplug.

Something obviously didn't want to let go! This can happen from time to time; it's not necessarily a disaster. Thanks for reporting, though.

[castalla]

Another shutdown FAIL

Also, I moved the Joggler to it's usual position - on the outer reaches of my router range (which works okay with 1.09 ) . Unable to connect to network - similar behaviour to what I found with version 2 - which also struggled to connect at a distance.

[roobarb!]

Another shutdown FAIL

Could you post a picture of this, or the item it fails on - you mentioned it was killing processes. Did you install anything additional or alter any other files, or is it just as shipped? You mentioned that you hook up to a share - does this unmount cleanly if you umount it? I've got this running on three OF1 units now and no sign of a repeatable shutdown failure.

Also, I moved the Joggler to it's usual position - on the outer reaches of my router range (which works okay with 1.09 ) . Unable to connect to network - similar behaviour to what I found with version 2 - which also struggled to connect at a distance.

I don't know where this difference comes from, and it's not likely to be something I can fix. This release is the closest thing to a vanilla Ubuntu I've ever put together. Ironic that the problem appeared with v2 (which uses the same wifi driver as v1) and not here with v3 (which uses a completely different wifi driver!).

[castalla]

1'll try to replicate the Fail tomorrow ...

One strange feature - the network menu said it was connected with a fixed ip address - but it totally failed to connect to LMS on the same address or to another LMS on the network. 1.09 sees both LMS servers without any problems.

As said, it's a vanilla install but with LMS added and interfaces set to a fixed ip.

I'll check the share situation

[Man in a van]

I have tried to install this from two different USB sticks (which both work with the current OS).

No go.

This message is given,

dd writing '/dev/mmcblk0': No space left on device

Gone back to v2.

atb.

Ronnie.

[roobarb!]

I have tried to install this from two different USB sticks (which both work with the current OS).

dd writing '/dev/mmcblk0': No space left on device

You didn't read the article.

External USB devices ONLY at this time.

It's too big to write to internal memory at the moment.

[Man in a van]

I have tried to install this from two different USB sticks (which both work with the current OS).

dd writing '/dev/mmcblk0': No space left on device

You didn't read the article.

External USB devices ONLY at this time.

It's too big to write to internal memory at the moment.

Well I did read the post but did not pay attention to the USB devices bit,

atb

Ronnie

[chris]

I was finally able to set my joggler back up after moving in January. I tired v2 it booted once no problem, found my DAC (schiit modi) and all was well until it rebooted and got stuck in a boot loop. I got it to boot with the DAC unplugged; plugged it in, changed audio settings to external and did a reboot only to get in some other "loop" about my last tty login (tty7 maybe?). It was just text and would get update with another "last login" every few seconds or so.

So I know all of that is really for another thread but... I decided to try beta 3 and it started up flawlessly!

I'll post back with anything else I find. This schiit DAC has really lived up to it's name as far as compatibility with sqpos is concerned.

[roobarb!]

Mmm, bizarre about the boot loops, but happy the beta is working for you.

Post back if you have more (or fewer!) issues with the Schiit Modi - with the output of lsusb -v as well. There might be something lovely in the kernel that I could compile in for the next release... Then again, there might not be.

[chris]

So after a few days of not using the joggler I went to play something and sound was coming from the internal speakers. I changed it to external, rebooted, and now have an fsck error I can't get past. Grrr. I guess I'll look for a USB keyboard?

[chris]

So, what can I do to troubleshoot? I popped the drive in another machine and did fsck and fixed something, popped it back in the joggler and this is all I can make out...

efi ioremap failed
io8042: no controller found
isch_smbus isch_smbus.33049 SMBus region 0x0 already in use!
gma500: Invalid ROM contents
gma500: VBT signature missing
gma500 trying to get vblank count for disabled pipe 0


Then it cycles between the squeezeplay logo and
Last login... on tty1. Each time it cycles another "last login" line gets added

[roobarb!]

Hmm, weird. That gubbins at the start is fine - don't worry about it. Those messages will all be there in the release too, except for that one about the SMBus region. It sounds like the OS is reasonably okay, but SqueezePlay is damaged in some way.

If you want to troubleshoot, SSH in and comment out the lines in .bashrc that start /opt/squeezeplay/bin/squeezeplay.sh. Then it should just drop to a shell prompt. You can then run squeezeplay.sh from the SSH session and should see all the info text output as it launches on the Joggler display. Something in that might point to what's wrong, but frankly it sounds like damage to the filesystem somehow, which we'd not find anything out about.

[chris]

Code: Select all

20140818 17:39:16.621 ERROR  squeezeplay - segv_handler:300 SIGSEGV squeezeplay 7.7.2 r9710
Segmentation fault

so, c filesystem? I can pastebin the rest of the startup if you'd like.