Official moOde 7.3.0 support thread

[Wheel_nut]

@Wheel_nut Do you mean manually through the CLI or through the GUI? I can try that for sure.

I used the GUI to manually enter the SSID and Passphrase and it worked for me. YMMV

[Ouchita]

Hi, 3 problems for my first non-introductory post !

A) Previously:- Pi 3B+, Moode r531, Suptronics 400 V2, connect with wifi, to Windows 10 PC and android tablets
                  USB boot off 16Gb thumb-drive, music library on separate 64Gb USB thumb-drive.
                  Powered from 19V 3.42A XP Power adapter.
It worked...

Now, have installed r730 on the 16Gb drive, and rebuilt the music library.
Problem:-    If the library USB drive is in the Pi then a Moode restart or a shutdown/restart (I press the wall switch!) will not boot the system. I have to leave the library USB drive out and replace it after the system has booted and is running. This did not occur on r531.

I have the same issue on 2 other rigs as described above, except that one has Suptronics V1, the other IqAudio Pi Dac Pro.

B) On r730, it takes a much longer time to create the AP.

C) I can't see how to get past the list of radio stations to get to the point where it suggests that I can access from the SDCARD or a Folder to play music. Sometimes I get there by luck !

[Tim Curtis]

C) Menu, Quick help

A) Try using an SDCard instead of a USB drive as the boot media.

[Ouchita]

C) Menu, Quick help

A) Try using an SDCard instead of a USB drive as the boot media.

Hello,

C) - Yep.....

A) Of course, that approach works but it means the Moode data will be on the (less- reliable) sdcard, whereas I wanted it to be on the USB stick for maximum longevity.

I am looking at the option of "boot from sdcard, run OS from a USB stick" (with music files on the 2nd USB stick).
Before I go down this route I imagine that others, including The Master might have determined whether or not this is feasible, as there could be the possibility that Moode expects the boot and the OS to be on the same physical device. I'd be obliged if you can comment on my idea.
I'd be following the procedure "STICKY: HOWTO: Move the filesystem to a USB stick/Drive"
from raspberrypi.org/forums/viewtopic.php?f=29&t=44177

tia
Tony

[Tim Curtis]

I don't think it's necessary. Just get high quality cards like Sandisk Ultra, Extreme or Extreme Pro. I use Sandisk Ultra Class 10 cards and they have been very reliable especially since my cards get heavy write activity during development which means all the time. Sandisk also makes Automotive and Industrial lines of cards but these are mainly designed to survive temperature and vibration extremes that would otherwise damage "normal" cards. I might use one of these if the Pi were being used for car audio and sitting in a hot trunk or interior all day.

If you really want the highest reliability Flash memory then check out SLC NAND based SDCards which have something like ~10X "endurance" as compared to MLC NAND storage. Delkin and Cactus are two suppliers and their cards can be purchased through Digi-Key or Mouser. Max capacity for the uSD form factor is 4GB though so moOde image would prolly need to be truncated a bit to fit since I think it's just a tad over 4GB in size.

[TheOldPresbyope]

@Ouchita

I choose not to get into debates about reliability of various memory technologies.

However, I do wonder about your issue A.

ATM I'm testing moOde 7.4.0tr1 on an RPi4B. The case I'm using makes exchanging the uSD card awkward so I'm using a USB thumbdrive (16GB Cruzer Fit) for moOde and another USB thumbdrive (32GB SanDisk Gen1) for my library. I can boot moOde just fine,

Code:

Disk /dev/sda: 28.7 GiB, 30752636928 bytes, 60063744 sectors
Disk model:  SanDisk 3.2Gen1
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: 0x00000000

Device     Boot Start      End  Sectors  Size Id Type
/dev/sda1          32 60063743 60063712 28.7G  c W95 FAT32 (LBA)


Disk /dev/sdb: 14.3 GiB, 15376318464 bytes, 30031872 sectors
Disk model: Cruzer Fit      
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: 0x067e19d7

Device     Boot  Start     End Sectors  Size Id Type
/dev/sdb1         8192  532479  524288  256M  c W95 FAT32 (LBA)
/dev/sdb2       532480 8724479 8192000  3.9G 83 Linux

I'm not sure why this configuration is working for me but not for you. Yes, I'm working with a test release but I was using the same dual-thumbdrive setup with 7.3.0 without issue. 

Another difference is that I'm booting an RPi4B and you're booting an RPi3B+. The RPF has quite a lot of model-specific information starting from https://www.raspberrypi.org/documentatio...t-sequence

Regards,
Kent

[eraser1320]

So I did a full reinstall with a fresh 7.3.0 image.

After going through the initial setup by connecting to the moode AP, entering in my wifi info and rebooting, it it connected to my wifi network and I was able to start the rest of my configuration. No ethernet plugged in the entire setup process.

However, after doing more setup that required another reboot, the second reboot after the fresh install, I'm back to the exact same behavior as my other posts. It goes into AP mode, unless I have an ethernet cable plugged in. :-(

[Tim Curtis]

I would look in your Router WLAN logs to see if there are any messages indicating why it might be rejecting the association.

[eraser1320]

I would look in your Router WLAN logs to see if there are any messages indicating why it might be rejecting the association.

Nothing is being rejected every and never has. I see in my logs during the initial wifi configuration from AP mode on the first boot, it associates just fine and wifi works normally. However after rebooting again, moOde switches into AP mode, no more association attempts to my router. Then if I plug in ethernet, moOde switches out of AP mode and associates wifi just fine. As soon as I unplug the ethernet, it switches back into AP mode. There are never any association rejection in my router logs, only successful ones.

[fdealexa]

I would look in your Router WLAN logs to see if there are any messages indicating why it might be rejecting the association.

Nothing is being rejected every and never has. I see in my logs during the initial wifi configuration from AP mode on the first boot, it associates just fine and wifi works normally. However after rebooting again, moOde switches into AP mode, no more association attempts to my router. Then if I plug in ethernet, moOde switches out of AP mode and associates wifi just fine. As soon as I unplug the ethernet, it switches back into AP mode. There are never any association rejection in my router logs, only successful ones.

Hello,
sometimes the simplest thing is not considered: eg. the toaster does not work: has the power been connected?
So I hope I'm not offended to ask if the option:

Menu
Configure
System
System Modifications
Wait for eth0 address

is it set to "OFF" 
Sorry for the banality and greetings,
Francesco