Moode Audio Player for Raspberry Pi

Jump to Latest
#10,741
BryceJ said:
Hi Kent,

Thanks for the confirmation of the use-and-delete action.

The hostname in the DHCP Clients List table was raspberrypi. It is now moode.

Once I had SSHed in and followed the script to the point where you change the hostname and password nothing else would work. Trying a copy command, or a shutdown command would error saying hostname raspberrypi could not be found.

I then unplugged and replugged the RPi. Now I SSH in as always and I am proceeding through the script with no other issues.

Cheers, Bryce.
Click to expand...

Sounds like a persistence of DNS. Rebooting your router would have prolly sorted it.
 
#10,743
Hi All
I'm having problems with the clock radio
If i set it it works fine the first time but after that it fails to come on the next morning

I noticed this in the system info
20171103 130104 worker: Ready
20171104 230556 worker: Job reloadclockradio
20171105 002804 watchdog: PHP restarted (fpm child limit 18 exceeded)
20171106 134210 worker: Job reloadclockradio
20171106 162054 watchdog: PHP restarted (fpm child limit 18 exceeded)
20171106 225856 watchdog: PHP restarted (fpm child limit 18 exceeded)
20171107 141146 watchdog: PHP restarted (fpm child limit 18 exceeded)
20171107 175404 watchdog: PHP restarted (fpm child limit 18 exceeded)
20171109 052416 watchdog: PHP restarted (fpm child limit 18 exceeded)

is this my problem and what can i do about it ?
Moode 3.84, piano2.1 dac, standard install with raspotify added

lx
 
#10,744
Zootalaws said:
Tim, when using ‘make’, if you append the ‘-jn’ parameter make will use multiple cores.

So, on a Pi2/3:

Code: 
5. Compile and install.

// Enjoy a Coffee and listen to some Tunes while the compile runs :-)

sudo make -j4

Should save considerable time.

I’ve been busy building a wifi-enabled cnc controller, but have been fiddling with an interactive bash installation script in my down time - in fits and starts. I only have a Pi3 until my boxes arrive, so it would be good if someone can test some commands for me to find the different responses for Pi1,2,3, Zero and W.

If I can crack how to resume after reboot (prolly just set a file flag is easiest) I think I’ll have it sorted.

I will try and finish it for the Pi3 today, then we can work on the other boards.
Click to expand...

Hi Mike,

From the help for make:

" -j [N], --jobs[=N] Allow N jobs at once; infinite jobs with no arg."

I read this as it will use as many cores as are present. I ran quick test and top shows all cores active on a compile. Try top -d .5 so it refreshes more often.

-Tim
 
#10,745
Zootalaws said:
...
I’ve been busy building a wifi-enabled cnc controller, but have been fiddling with an interactive bash installation script in my down time - in fits and starts. I only have a Pi3 until my boxes arrive, so it would be good if someone can test some commands for me to find the different responses for Pi1,2,3, Zero and W.

If I can crack how to resume after reboot (prolly just set a file flag is easiest) I think I’ll have it sorted.

I will try and finish it for the Pi3 today, then we can work on the other boards.
Click to expand...

Hi, Mike.

Always happy to be a crashtest dummy. I have RPi2B, Rpi3B, and RPi0W at hand.

As for resume after reboot, the subject comes up from time to time. See, e.g.,How to continue a script after it reboots the machine? - Unix & Linux Stack Exchange

Regards,
Kent
 
#10,747
TimCurtis said:
Hi Mike,

From the help for make:

" -j [N], --jobs[=N] Allow N jobs at once; infinite jobs with no arg."

I read this as it will use as many cores as are present. I ran quick test and top shows all cores active on a compile. Try top -d .5 so it refreshes more often.

-Tim
Click to expand...

So no need to specify a number of cores, make -j will use as many as you have?

Excellent. I need to “man” up more 😉
 
#10,751
TimCurtis said:
Hi Mike,

I tested with no -j at all.

Try a compile with top -d .5 in another ssh session and see if you can confirm my results that all cores are utilized.

-Tim
Click to expand...

Ok. I guess it’s for limiting, rather than adding more grunt. For some reason there was a nag in the back of my head that make only used a single core - but that may be a different platform (Solaris or SGI most likely, where you wouldn’t want it to nick all the resources).
 
#10,752
e_fortier said:
Hi,

Been using MoOde v3.1 for about 1 year and it hasn't crashed once with RPi2

Thinking of buying the RPi3-B, is MoOde compatible? If so is it with 3.7 ? Would 3.1 be ok ?

Thanks for such a great and reliable software.
Eric
Click to expand...

Moode 3.1 runs great on a RPi3 B. I am not sure where you will get any later version images for download. At the moment if you want Moode 4 beta you need to build your own image. It sounds daunting but the last build recipe makes it very easy. You just need to follow the steps exactly and type accurately.

Plus it is a good way to learn more about the RPi and how Raspbian works.
 
#10,753
Mars67 said:
Moode 3.1 runs great on a RPi3 B. I am not sure where you will get any later version images for download. At the moment if you want Moode 4 beta you need to build your own image. It sounds daunting but the last build recipe makes it very easy. You just need to follow the steps exactly and type accurately.

Plus it is a good way to learn more about the RPi and how Raspbian works.
Click to expand...

Good words. And I didn’t type anything, used copy and paste in Mac Terminal. I hope Windows putty allows you to do the same.

It does take time though.
 
#10,754
I have already set up one moode rpi and am now starting me second using build recipe 1.6.

I am on STEP 3 (Expand the root partition to 3GB) point 4 and have run

Code: 
sudo ./resizefs.sh start
I get the following output with the 2 error lines highlighted in red. Is this an issue?

Cheers
Nick

Code: 
pi@raspberrypi:~ $ sudo ./resizefs.sh start

Welcome to fdisk (util-linux 2.29.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): Disk /dev/mmcblk0: 14.9 GiB, 15931539456 bytes, 31116288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x11eccc69

Device         Boot Start     End Sectors  Size Id Type
/dev/mmcblk0p1       8192   93813   85622 41.8M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      94208 3622247 3528040  1.7G 83 Linux

Command (m for help): Partition number (1,2, default 2):
Partition 2 has been deleted.

Command (m for help): Partition type
   p   primary (1 primary, 0 extended, 3 free)
   e   extended (container for logical partitions)
Select (default p): Partition number (2-4, default 2): First sector (2048-31116287, default 2048): Last sector, +sectors or +size{K,M,G,T,P} (94208-31116287, default 31116287):
Created a new partition 2 of type 'Linux' and of size 3 GiB.
[COLOR=Red]Partition #2 contains a ext4 signature.[/COLOR]

Command (m for help):
Disk /dev/mmcblk0: 14.9 GiB, 15931539456 bytes, 31116288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x11eccc69

Device         Boot Start     End Sectors  Size Id Type
/dev/mmcblk0p1       8192   93813   85622 41.8M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      94208 6238207 6144000    3G 83 Linux

Command (m for help): The partition table has been altered.
Calling ioctl() to re-read partition table.
[COLOR=Red]Re-reading the partition table failed.: Device or resource busy[/COLOR]

The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8).

Root partition has been resized.\nThe filesystem will be enlarged upon the next reboot
SYSTEMD 1
BOOT_DEV mmcblk0
ROOT_PART mmcblk0p2
PART_NUM 2
LAST_PART_NUM 2
PART_START 94208
PART_END +3000M
 
#10,756
aBrianH said:
Good words. And I didn’t type anything, used copy and paste in Mac Terminal. I hope Windows putty allows you to do the same.

It does take time though.
Click to expand...


I was using a slightly older version of Putty which sadly does not allow you to copy from the Win10 machine and paste in the terminal. It never occurred to me to try a later version which I actually downloaded today. Will see if it works over the weekend.
 
#10,758
@ Mars67

Using this on win10 laptop


PuTTY

Release 0.70

Build platform: 64-bit Windows
Compiler: clang 5.0.0 (http://llvm.org/git/clang.git dba970f4d143480b964f77b363ec23f22cea0390) (http://llvm.org/git/llvm.git 52ebe03cb0a728134e66d04f85281bc5a60d7091), emulating Visual Studio 2013 / MSVC++ 12.0 (_MSC_VER=1800)
Source commit: 3cd10509a51edf5a21cdc80aabf7e6a934522d47

© 1997-2017 Simon Tatham. All rights reserved.
Click to expand...

Ronnie

@ Everyone, don't forget to give the Putty guy some love too😉
 
Last edited:
#10,760
perryni said:
I have already set up one moode rpi and am now starting me second using build recipe 1.6.

I am on STEP 3 (Expand the root partition to 3GB) point 4 and have run

Code: 
sudo ./resizefs.sh start
I get the following output with the 2 error lines highlighted in red. Is this an issue?

Cheers
Nick

Code: 
pi@raspberrypi:~ $ sudo ./resizefs.sh start

Welcome to fdisk (util-linux 2.29.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): Disk /dev/mmcblk0: 14.9 GiB, 15931539456 bytes, 31116288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x11eccc69

Device         Boot Start     End Sectors  Size Id Type
/dev/mmcblk0p1       8192   93813   85622 41.8M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      94208 3622247 3528040  1.7G 83 Linux

Command (m for help): Partition number (1,2, default 2):
Partition 2 has been deleted.

Command (m for help): Partition type
   p   primary (1 primary, 0 extended, 3 free)
   e   extended (container for logical partitions)
Select (default p): Partition number (2-4, default 2): First sector (2048-31116287, default 2048): Last sector, +sectors or +size{K,M,G,T,P} (94208-31116287, default 31116287):
Created a new partition 2 of type 'Linux' and of size 3 GiB.
[COLOR=Red]Partition #2 contains a ext4 signature.[/COLOR]

Command (m for help):
Disk /dev/mmcblk0: 14.9 GiB, 15931539456 bytes, 31116288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x11eccc69

Device         Boot Start     End Sectors  Size Id Type
/dev/mmcblk0p1       8192   93813   85622 41.8M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      94208 6238207 6144000    3G 83 Linux

Command (m for help): The partition table has been altered.
Calling ioctl() to re-read partition table.
[COLOR=Red]Re-reading the partition table failed.: Device or resource busy[/COLOR]

The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8).

Root partition has been resized.\nThe filesystem will be enlarged upon the next reboot
SYSTEMD 1
BOOT_DEV mmcblk0
ROOT_PART mmcblk0p2
PART_NUM 2
LAST_PART_NUM 2
PART_START 94208
PART_END +3000M
Click to expand...

Hi, Nick.

Not errors in this context, just geek-speak. The new partition table will be read when you boot from the uSD card (or go through the losetup/mount rigmarole again).

Regards,
Kent
 
You must log in or register to reply here.
Top Bottom