Home of the Squeezebox™ & Transporter® network music players.
Page 1 of 158 1231151101 ... LastLast
Results 1 to 10 of 1572
  1. #1
    Senior Member JackOfAll's Avatar
    Join Date
    Dec 2005
    Location
    London, UK
    Posts
    2,749

    Community Squeeze OS R3

    CSOS-Wandboard-Dual-R3-20130412-1.img

    This thread is a continuation of the Plastic Box Which Plays Noises thread, which was the name of the first Fedora 18 based software image for the Wandboard, the predecessor to what is now the Community Squeeze OS (CSOS) image.

    The image should be downloaded and put onto the SDCARD with dd from a Linux machine or using win32diskimager from Windows. The Wandboard Quick Start Guide can be used as a guide to getting started, just remember that you need to account for the fact that you will be using our CSOS R3 image, rather than their recommended image.

    Another image that needs testing. This includes the systemd 201-2 update, latest LMS 7.8 1365679703 trunk, (squeezeboxserver service disabled by default), and latest version 31 Web-GUI.

    The systemd update resolves at least two of the hangs I have seen, the systemd spewing 1000's of "time change" messages to the serial console issue and the hang in the shutdown process if you have a cifs (Windows) share mounted. I must have rebooted 30 or so times today, on ethernet, on wi-fi, with nfs shares mounted, with cifs shares mounted. A couple of times I've experienced a slow shutdown sequence with services, (usually rsyslog, the system logger), seemingly taking ages to finish writing to the sdcard and close, (observed from the serial console), but it hasn't hung once.

    It uses the two partition layout, (50M ext2 boot partition 1 / ext4 rootfs partition 2), the same as the R2 image. But new to this image, the kernel is installed from an rpm package, (kernel-wand-3.0.35-cm25), which means that there is a simple upgrade path via yum for future kernel updates. It also uses the /boot/uboot/uEnv.txt, (ie. it's populated, rather than the empty file in R2), for kernel boot command line, so from a development point of view, it is easier to edit a text file and reboot rather than having to recompile uboot or mess around on the serial console. (Users should not edit the contents of the file unless you know what you are doing or you will more than likely end up with a system that won't boot.)

    Would appreciate it if the usual suspects, (Terry, Michael, .....), could dd the R3 image to a spare card and try it.

    (Note. The hiFace kernel module, snd-usb-hiface.ko, is included with the kernel package. I think I asked already if anyone had a hiFace to be able to say this is working with the Wandboard? EDIT 20130413: Now confirmed as working by Andrew!)

    CSOS-Wandboard-Dual-R3-20130412-1.img.7z

    As with the previous images, the unpacked size is 3904897024 bytes, so you'll need a >= 4GB sdcard to write it to.

    For first time users: Download the compressed image. Extract it from the 7-Zip archive. Write it, (using dd or equivalent), to a >= 4GB sdcard. Plug the sdcard into the slot on the Wandboard CPU board. (Important, that you plug it into the sdcard slot on the CPU board. It won't boot from the 2nd sdcard slot on the carrier board!) Plug in an ethernet cable and apply power to the device. Wait 30 seconds. Log into your router, which has hopefully allocated an IP Address to the Wandboard ethernet interface from its pool of dhcp addresses, (the device should have sent a clientId of 'Wandboard' to your router when it requested an address, making it easy to find the allocated IP, if your router shows that info), and use that IP Address to access the CSOS Web-GUI running on the device, http://wandboard_ip_address:8080/. From the Web-GUI you can configure the wi-fi interface, (set network name / pre-shared key), if you wish to use a wireless connection, or re-configure the Squeezelite Player to use a different audio output device. (The default is to use the sgtl5000 line-out.)
    Last edited by JackOfAll; 2013-04-18 at 05:48. Reason: First time users

  2. #2
    Senior Member JackOfAll's Avatar
    Join Date
    Dec 2005
    Location
    London, UK
    Posts
    2,749

    squeezelite-1.1-1.fc18.armv7hnl

    squeezelite-1.1-1.fc18.armv7hnl

    "Official" v1.1 release. (Cosmetic, version number change, beta -> release, no code changes over the previous beta package.)

    Code:
    sudo yum update squeezelite

  3. #3
    Senior Member
    Join Date
    Mar 2013
    Posts
    128

    Testing R3...

    Quote Originally Posted by JackOfAll View Post
    CSOS-Wandboard-Dual-R3-20130412-1.img

    Another image that needs testing. This includes the systemd 201-2 update, latest LMS 7.8 1365679703 trunk, (squeezeboxserver service disabled by default), and latest version 31 Web-GUI.

    The systemd update resolves at least two of the hangs I have seen, the systemd spewing 1000's of "time change" messages to the serial console issue and the hang in the shutdown process if you have a cifs (Windows) share mounted. I must have rebooted 30 or so times today, on ethernet, on wi-fi, with nfs shares mounted, with cifs shares mounted. A couple of times I've experienced a slow shutdown sequence with various services, (usually rsyslog, the system logger), seemingly taking ages to finish, (which I have observed from a serial console), but it hasn't hung once.

    It uses the two partition layout, (50M ext2 boot partition 1 / ext4 rootfs partition 2), the same as the R2 image, but now the kernel is installed from an rpm package, (kernel-wand-3.0.35-cm25), which means that there is a simple upgrade path via yum for future kernel updates. It also uses the /boot/uboot/uEnv.txt, (ie. it's populated, rather than the empty file in R2), for kernel boot command line, so from a development point of view, that is easy to edit rather than having to recompile uboot or mess around on the serial console. (Users should not edit the contents of the file unless you know what you are doing or you might end up with a system that won't boot.)

    Would appreciate it if the usual suspects, (Terry, Michael, .....), could dd it to a spare card and try it.

    (Note. The HiFace kernel module is included. I think I asked already if anyone had a HiFace to be able to say this is working with the Wandboard? EDIT: Now confirmed as working by Andrew!)

    CSOS-Wandboard-Dual-R3-20130412-1.img.7z

    Hi JackOfAll...

    Flashed to 16GB Sandisk ULTRA.
    Setup Static IP, Stuff under squeezelite.
    Playing Music...
    update squeezelite , restart service.

    Confirmed. Running on version 31.

    No Issues at all...

    /Michael

  4. #4
    Senior Member JackOfAll's Avatar
    Join Date
    Dec 2005
    Location
    London, UK
    Posts
    2,749
    Quote Originally Posted by michaelvv View Post
    Confirmed. Running on version 31.
    No Issues at all...
    Thank you, Michael.

    Over the weekend, I want to try and put together some better documentation on installing the image, first time configuration, etc. etc. that we can put on the CS web site as well as having it accessable from the device Web-GUI.

    I'd like to put together a list of known to be working USB sound cards/converters/devices. I'll start the list with.....

    EDIT: List moved to website FAQ.
    Which external DAC's have been tested with the Wandboard?

    Please post your working devices (Device Name, Web Site URL, Linux Driver, Max Supported Rate, and USB Class 1 or 2) and I'll add them to the list above.
    Last edited by JackOfAll; 2013-04-29 at 21:45. Reason: Add Musical Fidelity V-192

  5. #5
    Senior Member
    Join Date
    Jun 2011
    Posts
    131

    very nice!

    I have been tinkering with building a dedicated (Fedora based) ARM music device for a while now. Trying out the Raspberry Pi, cubox and now the wandboard. I got F18 running on my wandboard dual but I am glad to have found this thread. Very nice work! I gladly abandon my own efforts :-). Looking forward contributing...

  6. #6
    Senior Member
    Join Date
    Apr 2005
    Posts
    8,410
    Quote Originally Posted by JackOfAll View Post
    Please post your working devices (Device Name, Web Site URL, Linux Driver, Max Supported Rate, and USB Class 1 or 2) and I'll add them to the list above.
    Name: Audiolab M-Dac [Lakewest audio software]
    URL: http://www.audiolab.co.uk/M-DAC%20Series.aspx?lang=En
    Driver: snd-usb-audio
    Max Rate: 96k
    Class: UAC1
    Hub: Bus powered external high speed hub

    Note with the wandboard USB ports, as with many ARM SoC that I have tested, UAC1 devices require an external high speed hub as the internal transaction translator capability of the SoCs is cut down compared to full implementations.
    Last edited by Triode; 2013-04-13 at 02:38.

  7. #7
    Senior Member JackOfAll's Avatar
    Join Date
    Dec 2005
    Location
    London, UK
    Posts
    2,749
    Quote Originally Posted by Triode View Post
    Name: Audiolab M-Dac [Lakewest audio software]
    URL: http://www.audiolab.co.uk/M-DAC%20Series.aspx?lang=En
    Driver: snd-usb-audio
    Max Rate: 96k
    Class: UAC1
    Hub: Bus powered external high speed hub
    So you were already using the hiFace driver? Out of interest, do you know what the deal is with the M-DAC? They've used an OEM'd hiFace interface? Going a little off-topic, I'm surprised that it is only UAC1. I nearly bought an M-DAC, but I definitely wouldn't have bought one if I'd realised the USB interface was UAC1. I'm a big fan of John Westlake. I used to own the PT DAC he designed, many years ago. (That seems like a lifetime ago now! )

    Quote Originally Posted by Triode View Post
    Note with the wandboard USB ports, as with many ARM SoC that I have tested, UAC1 devices require an external high speed hub as the internal transaction translator capability of the SoCs is cut down compared to full implementations.
    Thanks for the reminder.
    Last edited by JackOfAll; 2013-04-13 at 02:40. Reason: snd-usb-audio

  8. #8
    Senior Member
    Join Date
    Apr 2005
    Posts
    8,410
    Quote Originally Posted by JackOfAll View Post
    So you were already using the hiFace driver? Out of interest, do you know what the deal is with the M-DAC? They've used an OEM'd hiFace interface? Going a little off-topic, I'm surprised that it is only UAC1. I nearly bought an M-DAC, but I definitely wouldn't have bought one if I'd realised the USB interface was UAC1. I'm a big fan of John Westlake. I used to own the PT DAC he designed, many years ago. (That seems like a lifetime ago now! )
    OPPS - No that's a typo - it's standard snd-usb-audio.

  9. #9
    Senior Member
    Join Date
    Apr 2005
    Posts
    8,410
    Quote Originally Posted by JackOfAll View Post
    So you were already using the hiFace driver? Out of interest, do you know what the deal is with the M-DAC? They've used an OEM'd hiFace interface? Going a little off-topic, I'm surprised that it is only UAC1. I nearly bought an M-DAC, but I definitely wouldn't have bought one if I'd realised the USB interface was UAC1. I'm a big fan of John Westlake. I used to own the PT DAC he designed, many years ago. (That seems like a lifetime ago now! )
    Many long threads on Pink Fish about this dac. It is standard usb audio with their own software not hiface (sorry typo - see other reply). I believe their new dac will be UAC2 based.

  10. #10
    Senior Member JackOfAll's Avatar
    Join Date
    Dec 2005
    Location
    London, UK
    Posts
    2,749
    Quote Originally Posted by Triode View Post
    OPPS - No that's a typo - it's standard snd-usb-audio.
    LOL. I've edited my posts to change it.

    I think after another positive user report on R3, (Terry are you out there?), I'm inclined to ask you to change the link in the General Forum announcement thread to point to the R3 image.
    Last edited by JackOfAll; 2013-04-13 at 02:53.

Posting Permissions

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