Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Pi 3 #357

Closed
lukyluke112 opened this issue Feb 29, 2016 · 66 comments
Closed

Pi 3 #357

lukyluke112 opened this issue Feb 29, 2016 · 66 comments
Milestone
v0.7.0

Comments

@lukyluke112
Copy link

So I just bought a pi 3 and it will come in a couple of days and I would like to know if pi music box will work out of the box with the pi 3
@kingosticks
Copy link
Member

You’ll need a recent NOOBS or Raspbian image from our downloads page

(source: https://www.raspberrypi.org/blog/raspberry-pi-3-on-sale)

Since Musicbox v0.6 is built on a really old image I doubt it'll boot. Usually it's a case of copying over out boot.elf and fixup.dat files but I really can't be sure until mine turns up (also in a few days, I hope).

This is yet another great reason why we really need a new release but time has been against me lately.

@lukyluke112
Copy link
Author

Thanks I'll try that when I get mine and see if it works

@prankstr
Copy link

Hi,

I can confirm that it doesn't boot out of the box, however copying boot.elf and fixup.dat with respective _cd files did make it boot as kingosticks thought, thanks!

I haven't got around to do much testing yet but it seems like the on-board WiFi will need some attention.

@kingosticks
Copy link
Member

Thanks @sdbakker . The onboard wifi is reportedly the same as the official wifi dongle (the BCM43143?) which uses the brcmfmac driver. Wheezy has firmware-brcm80211 v0.36 which doesn't appear to contain the necessary firmware files (Jessie has v0.43 and definitely does).

@lukyluke112
Copy link
Author

but if I want to update the raspian would i reck my musicbox?

@kingosticks
Copy link
Member

Yes. I'm still working on a new jessie based version. You should be also able to copy the extra firmware files over if you want to use the onboard wifi. Or you might even get away with directly installing the deb from wheezy-backports since it's not architecture dependent...

@lukyluke112
Copy link
Author

Cool ill try that thanks

@davidpronk
Copy link

I can confirm that it doesn't boot out of the box, however copying boot.elf and fixup.dat with respective _cd files did make it boot as kingosticks thought, thanks!

@kingosticks can you specify exactly what files you copied. I'm not sure which ones to include.

edit: I also managed to get the Pi 3 running after copying some files from 2016-02-26-raspbian-jessie-lite.img Unfortunately I am not exactly sure which ones... I'll try and figure that out.

Now let's see if I can get the web interface running and maybe the wifi as well...

@kingosticks
Copy link
Member

I think you'd be better off directing that question at @Subsack but I would guess:

  • *.dat
  • *.elf

would be sufficient. Maybe bootcode.bin too, but I'm not sure if that's actually needed.

@davidpronk
Copy link

My bad... I meant to do so but copied the name from the wrong post.

@davidpronk
Copy link

👍
By overwriting all *.dat and *.elf files from 2016-02-26-raspbian-jessie-lite.img to Volumio2 2.0.0-alpha4 I got the Pi 3 up and running Volumio.

@jonbrohauge
Copy link

Got MusicBox to rock like this:
mounting jessie-lite gives two mount points boot and 1.3G
mounting musicbox-0.6 gives two mount points MUSICBOX and 8.0G

The two secondary mount points will probably be called something else for you
For the sake of argument I'll call them Jessie1.3 and MusicBox8.0

Copy files....
cp -r boot/ MUSICBOX/

cp -r [Jessie1.3]/lib/modules [MusicBox8.0]/

Boot your raspberrypi

Update apt-repositories from wheezy to jessie
apt-get update && apt-get upgrade
reboot

There were a few differences of some scripts upon upgrading, but I choose "keep maintainer" in most cases. I kept current version for watchdog

Update firmware
apt-get install rpi-update
rpi-update
reboot

I have yet to get wifi working....

@jonbrohauge
Copy link

A quick showdown of my config in regards to wifi:

root@MusicBox:~# cat /etc/network/interfaces                                           
auto lo
iface lo inet loopback

#auto eth0
allow-hotplug eth0
iface eth0 inet dhcp

auto wlan0
allow-hotplug wlan0
iface wlan0 inet dhcp

wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

wireless-power off
iface default inet dhcp

Remove a nag about wireless p80211 driver that keeps my wireless from working:

apt-get remove linux-wlan-ng

My configuration of the wpa_supplicant.conf:

root@MusicBox:~# cat /etc/wpa_supplicant/wpa_supplicant.conf 
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
    ssid="MY_SSID"
    psk="MY_WPA_KEY"
}

At current I get wireless access through to my MusicBox, although the throughput is terrible. I guess the drivers for rpi3 have yet to mature.

Hope alle this helps others, cheers all.

@bonelifer
Copy link

There's something about turning off power management to fix the RPi3's wifi for the time being. I believe theres a fix upstream, but currently would require using rpi-update. Here's one topic showing a command to fix this for now: https://www.raspberrypi.org/forums/viewtopic.php?p=928480#p928480

@jonbrohauge
Copy link

@bonelifer - It appears to have helped to do an apt-get update && apt-get upgrade today. The article you mention basically tells you to insert wireless-power off into your interfaces and upgrade to the latest firmware. - Thx for the reminder

@lukyluke112
Copy link
Author

I tried to get the .elf and .dat files but flashing it via noobs and I flashed raspbian a couple of times. I could not find any .dat files and only 1 .elf file

@jonbrohauge
Copy link

@lukyluke112 sound like you do not have the correct folder mounted

@vantezzen
Copy link

If someone still can't get it work, here's a tutorial: http://bennetthollstein.de/wordpress/?p=147

@rnamdos
Copy link

rnamdos commented May 8, 2016 •
edited

Just here to say that I followed @fumblingwithit instructions and I got my rpi3 to stream over my iPhone 4G hotspot. Every other attempt failed miserably at firmware update.

You might also need to also install the Broadcom driver. Follow this (copied from this thread)

#Remove the Driver
modprobe -r brcmfmac
#Load in the Driver
modprobe brcmfmac

Check Dmesg for any errors

dmesg

List all network ports

ifconfig -a

If you see an error in the dmesg log like this, then your likley missing the needed firmware files
brcmfmac_sdio mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.bin failed with error -2

In that case go to https://github.com/RPi-Distro/firmware- ... 80211/brcm
and download the brcmfmac43430-sdio.bin and brcmfmac43430-sdio.txt files into the directory
/lib/firmware/brcm/ then try again

@kingosticks kingosticks added this to the v1.0 Packaged milestone May 13, 2016
@rgov
Copy link

rgov commented Aug 17, 2016 •
edited

What is the latest release of Raspbian that you have successfully installed? I tried the above with 2016-05-27-raspbian-jessie-lite.img without success. I'll try with 2016-02-26 since that's the last version explicitly mentioned by @davidpronk above.

Update: So far so good with 2016-02-26. However it does not work to use rpi-update to get to rpi-4.4.y.

  1. Flash the musicbox0.6.img image to the SD card. Delete all of the .dtb, .bin, and .elf files from the boot partition and copy the new files from the 2016-02-26-raspbian-jessie-lite.img image (download link), as described on Bennett Hollstein's blog.
  2. Connect the Raspberry Pi to Ethernet and boot it. Navigate to http://musicbox.local/settings/ and expand the Network settings. Enable SSH and click "Update Settings." The device will reboot.
  3. SSH into the Raspberry Pi as root@musicbox.local, password musicbox. It's a good idea to update the time right away, to prevent SSL connection issues: ntpdate pool.ntp.org
  4. Update the apt sources list for Mopidy: wget -q -O /etc/apt/sources.list.d/mopidy.list https://apt.mopidy.com/wheezy.list
  5. Now update all packages: apt-get update && apt-get dist-upgrade.

This gets you to the latest Wheezy with kernel version 4.1.19-v7+. Next to figure out Wi-Fi.

@rgov
Copy link

rgov commented Aug 17, 2016 •
edited

Update: This worked to get from Wheezy to Jessie (though perhaps it is outside the scope of this bug):

  1. Copy the config.txt file from the boot partition of the 2016-05-27-raspbian-jessie-lite.img (download link) over /boot/config.txt.
  2. Edit /etc/apt/sources.list and all of the files in /etc/apt/sources.list.d to replace wheezy with jessie. For mopidy.list, execute wget -q -O /etc/apt/sources.list.d/mopidy.list https://apt.mopidy.com/jessie.list.
  3. Run apt-get update && apt-get dist-upgrade. This takes a while.
  4. Choose "no" when prompted if you want to disable SSH as the root user. Choose "yes" when prompted if you want Apt to automatically restart services after upgrading their dependencies.
  5. Whenever asked if you want to replace a configuration file, say "yes". The originals will be backed up. More on this below.
  6. Run rpi-update. (If you don't have it, apt-get install rpi-update first.)
  7. Apply my patch to re-apply MusicBox-specific configuration changes: curl https://gist.githubusercontent.com/rgov/5726b9ab25e3acaa2464c4c55f548ce8/raw/290848dc07b5ee61a7dce0a20735b01e901d4ede | (cd / && patch -p0)
  8. (Experimental.) I was having a 90 second delay during boot waiting for /dev/mmcblk0p3 to become available, but it doesn't exist. I removed its entry from /etc/fstab. This probably disables swap completely and might have deleterious effects.
  9. Reboot.

At this point the Wi-Fi interface is available but isn't connecting, and audio does work. (I got Wi-Fi to associate after a little fiddling but I don't remember how, sorry.)

The configuration files that get overwritten with upstream versions are the following. The original Pi MusicBox configuration files are here, and a backup copy is also made alongside the original with a .dpkg-old extension.

  • /etc/issue - ignore
  • /etc/skel/.bashrc - ignore
  • /etc/security/limits.conf - MusicBox adds a few lines to change audio prioritization
  • /etc/sysctl.conf - MusicBox sets vm.min_free_kbytes = 32768 at the bottom
  • /etc/login.defs - ignore
  • /etc/init.d/avahi-daemon - ignore
  • /etc/monit/monitrc - MusicBox adds a 5 minute delay before scanning for music
  • /etc/watchdog.conf - MusicBox enables a watchdog timer so the device is rebooted if it crashes

@shawaj
Copy link

shawaj commented Aug 21, 2016

@kingosticks can you send me an email to shawaj at gmail - got something to discuss with you if that's OK?

@kingosticks kingosticks mentioned this issue Aug 27, 2016
Closed
@frob
Copy link

frob commented Sep 8, 2016

Curios if it is possible to just run the install script on the latest raspian on a Pi3 instead of trying to upgrade.

@Canz2
Copy link

Canz2 commented Dec 30, 2016

Hello is what it would be possible to have all the necessary files in a file compiled
Because I start in raspberry and I am a little feneant

PS: I'm French so small mistakes are normal

@shanehull
Copy link

Any update on Pi 3 support?

@kingosticks
Copy link
Member

Yes! v0.7 (support for Pi 3, Zero and ZeroW) is very nearly ready. A few last things to fix up (wireless being one) and it's good to go. If you are really keen you can test the beta at https://drive.google.com/open?id=0ByrmzcQJL5t1c1V0NzhheWl6Tlk

@shanehull
Copy link

Wow, that was quick! Thank you! I'll give it a test now

@rgov
Copy link

rgov commented Mar 2, 2017 •
edited

I gave up on trying to use PiMusicbox on Pi 3, but it was quite simple to install Mopidy. I can't give any tech support for this but you can try to follow along.

https://gist.github.com/rgov/ae3a2ceb3bde964b8836d83c88b11924

Edit: Saw @kingosticks's reply, looks like there's a new version coming.

@shawaj
Copy link

shawaj commented Mar 14, 2017 via email

@kingosticks
Copy link
Member

As @shawaj said, Premium only.

v0.7.0 RC3 is at https://github.com/pimusicbox/pimusicbox/releases/tag/v0.7.0RC3

@shawaj
Copy link

shawaj commented Mar 16, 2017 via email

@francesco-vannini
Copy link

francesco-vannini commented Mar 16, 2017 via email

@shawaj
Copy link

shawaj commented Mar 16, 2017 via email

@shawaj
Copy link

shawaj commented Mar 16, 2017

@kingosticks - we (myself and @francesco-vannini ) have been testing today...has support for JustBoom boards been built in at the moment?

What do we need to get this sorted for the Pi3 release? See #366 also

@kingosticks
Copy link
Member

kingosticks commented Mar 16, 2017 via email

@kingosticks
Copy link
Member

kingosticks commented Mar 16, 2017 •
edited

Hang on!? Do you guys know someone from JustBoom? Do you know who I was emailing, can I get back in contact with whoever I need to and get it working? i.e do you have the hardware to test it?

@shawaj
Copy link

shawaj commented Mar 16, 2017

@kingosticks it was probably me or John you were talking to :-)

And really sorry - never intended to leave you hanging whatsoever! We have just been so slammed since the JustBoom launch and because there was only slow progress here and we were not exactly sure what to do (we have also been unfortunately delayed in hiring a full time software dev) we didn't get very far with it. In any case - we want to do everything we can do to help build in support for JustBoom...and happy to provide our support/updates as well as hardware samples to send you of all the boards.

But yes - do you want us to send you all the hardware accross? It is just a case of pulling in the latest Kernel - all the drivers for JustBoom are in there already (justboom-dac and justboom-digi) and they work the same way as the HiFiBerry and IQaudio drivers with the config.txt file (or they auto configure with the onboard EEPROM on the HATs - but the Pi Zero boards do not have EEPROMs).

The only thing we aren't really sure of, is what changes we would need to make in PiMusicBox to get it working

@kingosticks
Copy link
Member

kingosticks commented Mar 16, 2017 •
edited

Sounds good, let's take this off into #366

EDIT:
And I hope you'll accept my apology for my previous negative comment. It's my fault the project didn't see an updated release that supported the JustBoom stuff. I have no right to criticise anyone else, particularly anyone who actually releases stuff!

@shawaj
Copy link

shawaj commented Mar 16, 2017

@kingosticks ok see you in #366 - and we will keep testing anyway and will report any bugs back here 👍

No worries at all either - we did say we could help and I am truly sorry we couldn't have helped more, we have just had a bit of a crazy couple of months and haven't managed to find a suitable software dev to join our team yet so have just been struggling along without one for now....

@francesco-vannini is primed to create guides and do testing on these releases as they come though.

will help in any way we can :-)

@kingosticks kingosticks modified the milestones: v0.7.0, v1.0 Packaged Mar 16, 2017
@iamandiradu
Copy link

iamandiradu commented Mar 17, 2017 •
edited

I don t know if this is v0.7 RC3 related or not, but I can t acces the browser interface with musicbox.local (in my case: music.local) anymore. It only works with the IP. Is there a quick fix for this, is it my network s fault or it s an issue locally on v0.7? Thanks :)

@shawaj
Copy link

shawaj commented Mar 17, 2017 via email

@kingosticks
Copy link
Member

It seems to be a v0.7 issue that avahi/zeroconf/bonjour is broken. Regular dns works if your home router is any good (but I appreciate most are not) I.e http://music/

I think it's just a problem with using the old config with the new version but Ive not found the solution to that one yet.

@iamandiradu
Copy link

@shawaj I m using Ubuntu, W10 and Android 6.0. I was able to acces the page using musicbox.local with the 0.6 version but I wanted to use it on my RPi W and it didn t work so I browsed a lil deeper and found this thread with 0.7 which supports W. Then I remembered that I read that 0.7 doesn t work with W s WiFi yet and that I don t have a USB hub so I decided to put it in my RPI 2.

@iamandiradu
Copy link

I installed MusicBox only to listen a radio online (best radio in my country, the others stream 💩 and ads) and it works. I d love to run it on my W, I m using my RPi 2 for different projects. I m please with MusicBox, keep it up and ,if possible, make it work on W :). Thanks!

@kingosticks
Copy link
Member

@iamandiradu Wifi for Pi3 and Pi0W is fixed in 0.7rc4, see #393. And .local issue is tracked in #397 (also fixed in 0.7rc4).

@iamandiradu
Copy link

PERFECT! Thank you :)

@iamandiradu
Copy link

Can you give me a link to grab this 0.7rc4? :)

@shawaj
Copy link

shawaj commented Mar 20, 2017

https://github.com/pimusicbox/pimusicbox/releases

@iamandiradu
Copy link

Latest one is RC3 which does not have a fix for RPi 0 W s WiFi :(. kingosticks talked about rc4, but I can t seem to find it.

@shawaj
Copy link

shawaj commented Mar 21, 2017 via email

@kingosticks
Copy link
Member

I found a problem late last night where pi zero W boards are given the wrong clock and voltage settings and consequently run horribly slow, almost unusably slow. This is due to a firmware bug in the 'latest stable' version of the kernel I updated to in rc4. It's supposedly fixed in the later 'unstable' kernels but there are reports of driver incompatibilities with those.

Pi0W support is a big part of this release and so I think it's worth upgrading to 'unstable' (v4.9.something?) and sticking that in rc4 to see if anything falls apart. The reported driver problems so far have been ones we don't use (I think). Once I've verified it at least vaguely works I'll upload it later today. It'll be on the release page, if you watch the project you should be notified of releases automatically. I'll post here too.

@kingosticks
Copy link
Member

@shawaj @iamandiradu https://github.com/pimusicbox/pimusicbox/releases/tag/v0.7.0RC4

@shawaj
Copy link

shawaj commented Mar 21, 2017 via email

@iamandiradu
Copy link

I`ll test it tomorrow :)

@kingosticks
Copy link
Member

I think I can finally close this issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v0.7.0
Development

No branches or pull requests