Where are you in oz? Ill have a beer with you next time I’m nearby 
1 Like
In general the DigiOne is supported. You can select it from the UI, and all the necessary ‘bits and pieces’ are there as well.
It’s just that we don’t have a user actually confirming to me “yes it works”. I’m in the beta program, so I expect the device to arrive asap. What that means is still a little bit unclear to me though 
Aaa ok I see good to know that @spockfish
As I just started to read about Ropieee I have som question. Does it support a touchscreen? Ploughing through more than 600 messages to find it well I dont really want to do that.
If it supports a screen what will it look like when Roon is playing?
Right now we’re in the middle of a beta with support for the 7 inch official Raspberry Pi touchscreen. So yeah, that one is supported.
I don’t have a recent screenshot lying around, so for that you need to have a look over here in the forum. And especially on this part stuff is far from ‘final’ yet.
The idea is simple: basically everything you could do in the past with the famous Squeezebox Touch is something that I want to achieve with RoPieee as well.
1 Like
Everything came up fine for me at this mornings reboot.
1 Like
@dabassgoesboomboom i’ve put out another update. This one is very small. Could you do a test with the cold boot/vpn?
Thanks!
Hey Harry,
After reading this very entertaining thread last night I received my new RPi3 today and trying to install Ropieee as I write this.
First and foremost, I am also experiencing the large card size problem. Mine is 64G and don’t have anything else at hand. I think the problem is resizing the large partition as last thing I can see in console is migrate_block commands from resize.f2fs. I tried changing the /RoPieee/bootstrap to restrict the partition size in the fdisk output to +8G but for whatever reason it didn’t work.
Any thoughts of a workaround?
This definitely needs to be properly resolved for Ropieee to be ready for primetime.
Thanks for a great work!
Darius
- a glass of Primitivo
Not sure what you mean. I just tested a fresh install with a 32GB card and I don’t have any issues.
You mentioned the migrate_block commands. Was it hanging?
I think this was mentioned somewhere in this thread. And not sure if that’s the same issue.
After a minute or two of Migrate data block rows it stops with this:
Rebooting goes again into the same screen and stops again.
Thanks,
Darius
I tried a different 64gb card, also tried downloading the beta iso, with the very similar end result:
ok. thanks for that.
not enough blocks to migrate…
I would say that with a 64GB card that would be enough
question: how did you burn your image?
I used Etcher on Mac. I can try dd as well, however just successfully installed Dietpi after burning with Etcher, too.
And on a side note: would be great if I can get the log files present on that image.
Considering you were trying to change a script I imagine you’re familair with a linux system.
Inside the image, on the first partition (FAT), there’s a directory ‘/RoPieee/log’. The files in that directory could help out in identifying what exactly goes wrong in this case.
No Etcher is great. Only thing you can try is to wipe the SD card first. That’s something Etcher can’t do.
Nothing too informative here:
Feb 01 02:11:04 ropieee ropieee[459]: Partition 2 has been deleted.
Feb 01 02:11:04 ropieee ropieee[459]: Command (m for help): Partition type
Feb 01 02:11:04 ropieee ropieee[459]: p primary (1 primary, 0 extended, 3 free)
Feb 01 02:11:04 ropieee ropieee[459]: e extended (container for logical partitions)
Feb 01 02:11:04 ropieee ropieee[459]: Select (default p): Partition number (2-4, default 2): First sector (67584-125042687, default 67584): Last sector, +sectors or +size{K,M,G,T,P} (67584-125042687, default 125042687):
Feb 01 02:11:04 ropieee ropieee[459]: Created a new partition 2 of type 'Linux' and of size 59.6 GiB.
Feb 01 02:11:04 ropieee ropieee[459]: Partition #2 contains a f2fs signature.
Feb 01 02:11:04 ropieee ropieee[459]: Command (m for help):
Feb 01 02:11:04 ropieee ropieee[459]: All space for primary partitions is in use.
Feb 01 02:11:04 ropieee ropieee[459]: Command (m for help): Disk /dev/mmcblk0: 59.6 GiB, 64021856256 bytes, 125042688 sectors
Feb 01 02:11:04 ropieee ropieee[459]: Units: sectors of 1 * 512 = 512 bytes
Feb 01 02:11:04 ropieee ropieee[459]: Sector size (logical/physical): 512 bytes / 512 bytes
Feb 01 02:11:04 ropieee ropieee[459]: I/O size (minimum/optimal): 512 bytes / 512 bytes
Feb 01 02:11:04 ropieee ropieee[459]: Disklabel type: dos
Feb 01 02:11:04 ropieee ropieee[459]: Disk identifier: 0xad167cd0
Feb 01 02:11:04 ropieee ropieee[459]: Device Boot Start End Sectors Size Id Type
Feb 01 02:11:04 ropieee ropieee[459]: /dev/mmcblk0p1 2048 67583 65536 32M c W95 FAT32 (LBA)
Feb 01 02:11:04 ropieee ropieee[459]: /dev/mmcblk0p2 67584 125042687 124975104 59.6G 83 Linux
Feb 01 02:11:04 ropieee ropieee[459]: Command (m for help): The partition table has been altered.
Feb 01 02:11:04 ropieee ropieee[459]: Calling ioctl() to re-read partition table.
Feb 01 02:11:04 ropieee ropieee[459]: Re-reading the partition table failed.: Device or resource busy
Feb 01 02:11:04 ropieee ropieee[459]: 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).No. Exactly it shows that repartioning the SD card works. So somehow the resizing screwed up, because it thinks there’s not enough room.
Would you be willing to retest this with an wiped SD card? On linux I use 'wipefs -a ’ for this, don’t know if there’s an alternative on Mac.
OK I’ll try to do that and report back. However I tried this with two separate 64GB microsd cards, I think one of them was brand new.
Just got the Dietpi up and running with RoonBridge, it works fine. Even more anxious to get the Ropieee running. 
yeah I need to sort this out. We’ve got more people reporting issues with SD cards bigger than 16 GB.
FWIW I have got into the habit of formatting my SD cards with https://www.sdcard.org/downloads/formatter_4/ before burning an image. Prior to adopting this ritual I experienced similar issues more than occasionally.
Just tested and cold boot is still failing (no extension showing in Roon and frozen 1:12 displa) behind a VPN even though Roon Core itself plays fine behind the VPN
No issues when VPN is turned off.