Hi Mirko,
There is no setting to turn Eth0 off, just a setting that enables or disables a longer wait for an ip address to be assigned to eth0. Here is the help text for this setting:
CAUTION: Only turn this OFF if running a WiFi-only configuration.
Leave this setting ON if connected via Ethernet cable.
Wait up to 9 secs for an IP address to be assigned to eth0.
-Tim
Hi Moshel,
Post more details about the file and also post the output from System info.
-Tim
Hi Keith,
View contents of table
sqlite3 /var/local/www/db/moode-sqlite3.db "select * from cfg_source"
Delete all rows from table
sqlite3 /var/local/www/db/moode-sqlite3.db "delete from cfg_source"
Verify existence of NAS directory. If its not present then mkdir /mnt/NAS
pi@rp2:~ $ ls -l /mnt
total 12
drwxr-xr-x 2 root root 4096 Feb 16 17:28 NAS
drwxr-xr-x 3 root root 4096 Dec 8 12:12 SDCARD
drwxr-xr-x 2 root root 4096 Dec 8 12:12 UPNP
pi@rp2:~ $
-Tim
Hello Tim,
i have tried these settings, sorry for the wrong understanding of this setting.
Also i tried to setup a fixed Ip address to get the boot process a little bit faster.
But nothing helped to get no grey screen after the boot.
Only to wait until the Wlan AP gets online and make a refresh.
Is there any way to get the start of the Chromium Browser at the end of the boot, so that the Wlan AP is up and then it should work fine.
Best Regards, Mirko
i have tried these settings, sorry for the wrong understanding of this setting.
Also i tried to setup a fixed Ip address to get the boot process a little bit faster.
But nothing helped to get no grey screen after the boot.
Only to wait until the Wlan AP gets online and make a refresh.
Is there any way to get the start of the Chromium Browser at the end of the boot, so that the Wlan AP is up and then it should work fine.
Best Regards, Mirko
Hi Phil,
Correct, it depends on how the Samba server is configured. i should probably some text to the help for the Mount flags input. Currently it has only the following:
"Adding sec=ntlm may be needed if SMB (Samba) mount fails."
New could be something like
"Other mount flags including sec=ntlm | vers=1.0 | vers=2.0 may be needed depending on what the Samba server requires."
-Tim
Hi Mirko,
Its not started by moOde startup (worker.php) but by systemd. you could try adding network.target to the systemd service file After= line. This should result in Chrome not being started until after the network is "up".
/lib/systemd/system/localui.service
After=nginx.service php7.0-fpm.service mpd.service network.target
Also remove the first line in the # header that has the bash shebang. Its harmless but nonetheless should not be there.
-Tim
Hi,
Amazing amount of progress from these new devs
In addition to initial volume they have also added session hooks that could enable coordination with MPD similar to how moOde implements Airplay/MPD coordination.
The problem however is that the code is written in Rust which requires installation and configuration of a Rust build environment in order to compile and generate a binary. I'm not particularly interested in doing this unless its super-easy.
The Rust Programming Language
The old librespot project used to have a fork that provided pre-made binaries compiled for alas-backend and I see that this new librespot.org project has "binaries" on its TODO list. When that happens I'll have a look.
-Tim
Hi,
Amazing amount of progress from these new devs
In addition to initial volume they have also added session hooks that could enable coordination with MPD similar to how moOde implements Airplay/MPD coordination.
The problem however is that the code is written in Rust which requires installation and configuration of a Rust build environment in order to compile and generate a binary. I'm not particularly interested in doing this unless its super-easy.
The Rust Programming Language
The old librespot project used to have a fork that provided pre-made binaries compiled for alas-backend and I see that this new librespot.org project has "binaries" on its TODO list. When that happens I'll have a look.
-Tim
The only rust I know is the one you get on old cars[emoji4]
I use the raspotify - it does the job for me and comes compiled. [emoji6] it uses the librespot library. And you can update it via the apt command.
I have Raspotify installed on Moode 4.0, and it now initiates at a safe 50% volume here.
You can change it to another initial volume if you want. Anywhere between 0 and 100. Mine is set to 85
@streamerguy
Wow. This is outside my experience.
A little Internet searching tells me the "skb_over_panic" error relates to the buffers used by the kernel to manage network packets (as one might guess from the mention of dev: eth0).
I can't say what your USB DAC is doing that would cause network buffer overruns. I just downloaded the manual for the Marantz NA11S1 (what a box, by the way!). It says the interface is "USB 2.0: USB High speed/USB Audio Class V2.0" compliant. It says a driver is needed for Windows XP (no surprise) but not for MacOS. From this I infer a driver isn't needed for Linux either. However, since one controller on the RPi manages both USB and ethernet interfaces, I suppose there is the possibility of some USB incompatibility causing a problem with networking.
Searching on the next error "kernel: Internal error: Oops - BUG: 0 [#1] SMP ARM" is even less illuminating. This reminds me of my granddaughter looking innocent as she declares "something happened"! Maybe it's just an aftermath of the buffer overrun but tracing all this back to some change that took place in the Linux kernel between the releases of moOde 3.7 and moOde 4.0 is beyond my pay grade.
I suppose you could try backporting moOde 4.0 to the kernel used in 3.7. Tim can tell you if this has no chance of working.
Regards,
Kent
[added in edit]: I focused on the kernel but the two releases of moOde are also based on different releases of Raspbian.
Last edited:
When the build has begun you will see an option to build the image on a single card. Use wired Ethernet if possible.
Awesome, thanks for the quick reply. What is the command to check the status of the install after I start the process? Thanks again!
Builder with direct install (no sd/usb adapter) require a fresh install of Raspbian.
You can’t launch the builder on the SD with beta12 ... you need to install a fresh Raspbian before on it
Builder with direct install (no sd/usb adapter) require a fresh install of Raspbian.
You can’t launch the builder on the SD with beta12 ... you need to install a fresh Raspbian before on it
Okay now I am confused. Even though I can download the Image Builder through Moode Beta 12 I can't run it if Moode is already built on the card? I was able to start Mosbuild.sh but after the first reboot I am lost as to what happens next.
I love using Moode but all of this complication in getting it updated makes me just want to stick with what works.