Installation Problem (solved)

[DigitalProf]

I have downloaded and extracted the image:

RuneAudio_rpi2_rp3_0.4-beta_20160321_2GB.img

I have placed the image multiple times on the SD card (Samsung 32 GB EVO), using two different Windows packages:

Win32DiskImager-0.9.5-install
USB Image Tool

For each trial on my brand new Raspberry Pi 3, the power light comes on just fine. The green SD access light then comes on, and goes off a few times as if the boot process is proceeding. Unfortunately I get no rainbow screen on my monitor, and the monitor remains blank. About every three seconds the green LED comes on then goes off immediately.

After re-imaging the SD card a few times with RuneAudio, I installed NOOBS on the very same SD card and the system came up just fine. The only difference between the two configurations is trying to use the RuneAudio image versus the NOOBS installation process.

I found a reference that suggested pressing 1, 2, or 3 on the keyboard to change the graphics display mode. This makes no difference and the screen remains blank. In addition, the disk partition I can see on Windows shows only 17.4 MB as used with 82.3 MB still free. Confirming this, the Disk Management app on Windows shows the primary partition as "100 MB FAT" with a second partition of 2 GB and 27.7 GB as "Unallocated."

To double-check, I did NOOBS again, which continues to work just fine.

Finally, when I return the SD card to my Windows computer, I invariably get an error message "There is a problem with this drive. Scan the drive now and fix it."

I have no idea what to do to try to determine the problem.

[hondagx35]

[DigitalProf]

Thanks, Frank, for your excellent guidance!

This does indeed make perfect sense, given the optimization of the RuneOS for that specific monitor. My monitor is an older unit to which I connect with an HDMI to DVI adapter. Given the fact that a boot sequence seemed to be taking place, based on the flashes of the LED, the next step on my own was for me to actually connect the system to a newer monitor to check out the possibility that the monitor

Unfortunately I am unable to see the RuneAudio unit on my home network router, so something might be glitching there. I will be able to check that out once I get a monitor connected.

So, I will edit the /boot/config.txt file on my PC. The trick will be to do some research to figure out the preferred mode of this old Princeton Graphics monitor. I should be able to do that, however.

Many thanks!

Cheers,

Mike

[DigitalProf]

I was never able to get the old model monitor running but I am now running with a newer monitor. Unfortunately, the fact that the system is apparently optimized for use with a touch screen, I cannot see the mouse cursor. In addition the unit does not appear on my network, so I cannot access the system using http://runeaudio.local.

[hondagx35]

[DigitalProf]

Frank,

I had connecting using Wi-Fi, but it did not work. I have iTunes on my PC, so installing an Avahi / Bonjour client should not be necessary, right? In any case, I could not connect via wireless.

This morning I connected it to my router via Ethernet cable, and the RuneAudio device was then visible on the router. I was then able to configure the wireless, which I just tested. It works great, using an Ethernet cable connect or via Wi-Fi! Either way, I am now able to control the player perfectly in Chrome. I was even able to connect RuneAudio to a shared directory on my home theater computer (running Windows 10) using SMB, which provided the first MP3 file to be played. Yay!

I will now connect via SSH to extend the size of the partition from the default 2 GB to the full 32 GB of the microSD card.

Many thanks again for your help!

Cheers,

Mike

[hondagx35]