Thanks soundcheck, that explains the absence of a PAIR command in Bluetooth Config.
Regards, Klaus
Since no one cares to help me. I decided to go the linux build option. Going better.
Funny thing - when I take the imaged SD card out of my linux computer and plug it into my Windows computer, it sees and empty card, but before when building on Windows, it would see the Boot partition and the empty partition. I somehow think that step #4 in option 2 with resizing the SD card when the image is created with Windows does not work. Tim, you may need to test this to ensure the Windows recipe is correct.
Hi,
I only have Mac and Raspberry Pi Linux. The Windows section has been tested by other users so I'm not sure what might have happened in your case.
The boot partition in Raspbian is fat32 format so it should be visible on Windows. If not then maybe the Stretch image that was downloaded in the beginning of the recipe is corrupt. You can find the SHA checksums for the image at the link below
Index of /raspbian_lite/images/raspbian_lite-2017-09-08
-Tim
Sorry to hear you're having problems. I have built several working images using v1.9 of Tim's recipe on my Win 10 laptop and not experienced the error you mention. Only problem I have experienced is with getting Qobuz access via UPNP in Moode 4 beta9 using Linn Kazoo.
I'm sure you are aware, but it is important to group the commands as shown.
After downloading and unzipping the stretch lite image I use Win32 disk imager to write the image to SD card. Then "insert folder" using File Manager to create new ssh folder and then use Notepad++ (or Wordpad) to create and edit wpa_supplicant.conf and cmdline.txt.
As they say, if at first......
Hope it's now working for you.
Ian
I tried it multiple times downloading a couple of different times. Don't know.
I did get further with building via Linux.
So now I have new problem:
After Step 10, it will not boot - "Cannot open access to console, the root account is locked."
Maybe I will try skipping Step 10 since 10 is optional and it rebooted fine after Step 8, and Step 9 is only installing the amixer. However I do see you are making changes to the usr directory. I did have an error that the command was unrecognized when entering "mpc enable only 1".
Last edited:
What issue are you having Ian?
Check the permissions on the upmpdcli.conf file which looks to have been causing some issues for some people.
you may need to chmod to 644.
Thx Steve. Tried chmod 644, but no change, so went back to 600. I'll have a look at the upmpdcli.conf file.
Ian
Rebuilt using Windows following careful at each step, copying and pasting commands (some line by line). Skipped Step 10 and Step 11 - Success!
I think the problem is with this in Step 10:
sudo -i
echo "/var/local/moode.sqsh /var/www squashfs ro,defaults 0 0" >>/etc/fstab
logout
Should there be a space between >> and /etc/fstab? I think it is this modification of the fstab that causes the locking of the root account.
I see that there was a short conversation about the rsize mount option a couple of days ago. I also experienced those skips that it can cause.
My config: moode 4.0 beta 9, Raspberry Pi Zero W, IQaudIO DAC PRO, flacs stored on NAS shared via SMB, wireless. The default rsize=1048576 caused skips in music right from the beginning. I figured this out by myself (narrowing the possible causes and finally comparing the settings to my old moode 3.1 setup) but I see others had problems with this. I set it to the old default value (61440) and it seems that the music plays perfect.
My config: moode 4.0 beta 9, Raspberry Pi Zero W, IQaudIO DAC PRO, flacs stored on NAS shared via SMB, wireless. The default rsize=1048576 caused skips in music right from the beginning. I figured this out by myself (narrowing the possible causes and finally comparing the settings to my old moode 3.1 setup) but I see others had problems with this. I set it to the old default value (61440) and it seems that the music plays perfect.
Hi,
No need for a space. The root userid is disabled in Raspbian Stretch. You have to log in using userid pi.
-Tim
The error occurs during startup before you login. I think it was my fault not realizing when rebooting after step 9 the WIFi is then controlled by MoOde. It wasn't showing up on my WiFi so I added the wpa_supplicant.conf back, so that must have caused the root account error. I realized this later when I got to this step again and without changing anything, plugged in HDMI and watched it boot up fine. So I just plugged up with the Ethernet, found my new IP, and continued.
Any reason why the advanced kernel option was taken away? And only option is TS?
So what is the best way to stream Tidal to MoOse using an Android phone then? Is this possible? If only Tidal could be added like the Tidal2 add on for Kodi.
You could probably cast the audio to moode from the Tidal app but what you want is to use a upnp app (iirc, bubbleupnp was suggested, I use Linn Kazoo on iOS) to control the front end and have your Pi stream the music from Tidal. To do that you must go through all the additional upnp steps in the build recipe and enable upnp in moode's System configuration screen, then enter your Tidal credentials in the upnp configuration screen. Afterwards when you run the upnp app it'll find moode-upnp as a media server and you access Tidal from there.
A master_preferences file might be able to do it. I have not done it myself but it appears from google searches that it will deploy settings into chromium on first run.
Tried several times to get zip file tonight. No luck. Did you have any problems accessing zip file? Thanks
I used " wget https://github.com/allocom/piano-fir...ive/master.zip"
