Hi,
Has anyone tried this with a Minnowboard Turbot? It has a Dual-core Intel® Atom™ E3826 CPU which is x64.
I’m trying to boot from the microSD slot. I’m starting from a Windows machine, after flashing the img file I have 3 partitions on the microSD
1 of 487 MB
2 of 2.78 GB
3 of 361 MB
and 56.01 GB unallocated because this is a 64 GB drive.
I can’t see the contents of the drives since this is Windows. Does this sound right so far?
When I boot up the MinnowBoard it does not see the microSD drive as bootable.
Another thing, the firmware I have is setup for 32-bit OS. Is this a 32-bit OS? If not I can update the firmware to support 64-bit. The image file I used was:
Hi john,
you are running a 32-bit OS with Volumio, so your current setup is fine.
However, does your board allow boot from microSD?
Can you try a usb stick (or put the SD in an usb card reader)?
Something else you need to be aware of: the kernel of the official version is fairly old.
I doubt, that booting from SD is supported at all as this was only added later.
Could you check if you can boot using a development version instead?
You will find a download link in the OP of section Volumio Development/ Development talks/ Next X86.
Let us know how this worked…
Thanks. I used the instructions on the Download page to flash the SD card. It resulted in three partitions. Is that correct? Perhaps I should remove all the partitions and re-format to exFat and do the flash again. I flashed a brand new out-of the-box SD, sometimes these things come with factory partitions installed.
I think I will also update the firmware, mine is pretty old. Just wondering if per chance you knew of a good one that is compatible or at least known to work with Volumio. Here is the list of available ones:
So I update the firmware and also reformatted the source disk to make sure the the img flash was correct, and yes, 3 partitions are created from this img file. I now see the drive in the EFI shell and the bios as a possible boot disk.
Whether I boot from sdcard or usb stick I get the same error:
The first screen reads:
loading linux 3.18.25 ...
loading intial ramdisk ...
Then the second screen reads:
[code]findfs: unable to resolve ‘UUID=3fd8c0e4-1328-4011-b14b-85cdaad08440’
findfs: unable to resolve ‘UUID=B664-D157’
BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) built-in shell (ash)
Enter ‘help’ for a list of built-in commands
sh: can’t access tty: job control turned off
/ #
[/code]
OK, I need to look into this, the boot seems to be starting ok.
The problem you are facing is related to locating the partitions Volumio has been copied to.
This only works for devices for which the drivers are loaded at that particular point.
Likely a missing, but I’m not sure yet which one is missing here, likely the one for MMC/SD.
For kernel 3.18.25 we will not add anything, but the upcoming versions have a new kernel and lots more hardware support.
I suggest you try our dev image, see the opening post of Volumio Development/ Volumio talks/ “Next X86…”
The image you are looking for is version 2.394
OK, we are almost there, I loaded it onto a faster sd card and now it boots significantly faster and the USBStreamer is recognized. (FYI, it is supported by ALSA 2.0)
There is still a problem that my exFAT formatted sata drive with my music on it is seen by the efi shell and bios but not by Volumio.
Sorry, I’m not much of a linux user, but how do I get to the command shell once Volumio is loaded?
Regarding the music disk you might have to google the volumoi forum a little (sorry did not bother myself).
There are a few thread showing you how to mount and use them them.
This is going to be a little more easy in upcoming versions, but something we have to live with just now.