Any success using 32GB eMMC

Using Ubuntu 18.10, the installation is now recognizing Ryzen's GPU and provide the max. resolution.
Somehow, still cannot the eMMC recognized with various BIOS settings I found thru Google search.
Any suggestions?

 

Do you see something like this during bootup at the start?

"genirq: Flags mismatch irq 7. 00000088 (mmc0) vs . 00000008 (pinctrl_amd)"
"mmc0: Failed to request IRQ 7: -16"

-F

 

From dmesg?
Not noticed that (need to recheck...)
In dmesg, I found AMDI0400:00 error -16
Not sure what was that?

BTW, I've never seen the EFI shell. It's a bit unusual (to me).

 

Do this:

dmesg | grep mmc

See what you get for output.

 

Yes, same error message as in yours (post #2.) Still need some work on Ubuntu support of eMMC.

Win10, no problem recognizing the eMMC (29 GB after formatting.)
After initial installation, 14.4GB free space left (experience told me in reality, only 5GB usable.)

Geekbench 4:
Compute (Open CL tab): 35831 <-- search "Seco C40"
CPU bench 3676 (single) and 9641 (multi)

===========
P.S. use rufus 3.5 to create USB boot thumb drive from ISO file.
Need to disable Secure Boot and disable CSM Support in order to get Win10 installation started.

 

Yah something is definitely messed up. Linux has supported eMMC for a good decade. This is likely going to require a BIOS fix.

Hoping someone from Udoo can address this soon as this is a core use case for this board.

 

Yes, Windows 10, See's it native.
Speed tests out to about 215 - 250 MB/s Read, 180 Write 4k sec test of 5 write 1 GB pass.

Ubuntu.. I'm thinking must be a bios setting like legacy or something I haven't figured out yet.
Installer starts to continue but doesn't find installation.iso and when I list my devices at busybox bash, only the NVME part's show up and not the hard USB attached SD (the eMMC).

 

Found the solution.

To get the eMMC to show up during Ubuntu install you need to create an Ubuntu ISO that has AMDs modified kernel patch included. You can either do this yourself or download the premade Ubuntu 18.04.1 image here

https://www.udoo.org/docs-bolt/Software_&_OS_Distro/Linux/Known_issues.html

 

FYI... I find that the recommended tool 'rufus' is troublesome and often fails to give a bootable image. I find this most often on computers that have been infected with bitlocker. So, recommend using tried and true tools.
# dd if=<path to bootable ISO> of=/dev/<devnod for thumbdrive> bs=2048M conv=fsync
Example (as root):
# dd if=ubuntu-18.04-2.iso of=/dev/sdb bs=2048M conv=fsync

 

Yeah, follow the link in post #8 to download the 18.04LTS custom image.
Use rufus version 3.5 to write to a USB flash drive (make sure select GPT partition, which will automatically set to UEFI boot method.)

Boot from USB drive created above, in the "grub boot selection MENU", press "e", ...
< --- the instruction is in the above link
Basically, it is to use nomodeset boot flag to force-use the VGA (800x600) driver to start the installation process.
This time, the DF4032 eMMC does show up.

.... continue as instructed in the above listed article.

Some additional info:
AMD kernel that supports the amdgpu (pick kernel 4.19.8), its size is 351 MB. Install per instruction in that article.
The special kernel needed to gain eMMC support (in the link in the above article), its size is 61MB. Install per instruction in that article to replace the kernel in previous step.

 

From the kickstarter page:

the UDOO BOLT is plug and play.

Linux® (any x64 distro)

 

Hehe...

Ryzen "Embedded" is fairly new. I guess Linux distribution needs time to catch up.
For example, when I use the Ubuntu 18.10, I did get the Graphics driver working out of box (but not eMMC support.)
As the Linux community says, it's not if but when... (also LTS version always has to wait for back-porting from the latest/greatest...)

(Still enjoying the first model year new car smell...

 

Eh. It was new last year when that document was written, the patches exist, is there any particular reason they haven't yet been submitted to the main Linux tree?

 

Just got my system going last night. Fedora does not see it. At this point, I am not going to try to get it going. Maybe I will try in the future.

 

@Chad Ringstrom
After boot my emmc works, but after a while it just goes to 100% active time and becomes 100% unresponsive. Does yours still work after say 5/10 minutes ? (windows 1903 , and amd drivers for that windows version) ... I have copied 2 windows images and both versions of the amd driver to the emmc , maybe it just stops working when it has some content on it ?

 

Fedora 30 now sees the 32GB eMMC drive. Sorry, I am not sure when this happened. I noticed it last night when I ran gparted. I did not see the drive when I first installed Fedora. uname output below:
Linux 5.2.7-200.fc30.x86_64 #1 SMP Thu Aug 8 05:35:29 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

 

link 404!, anyone ese have a premade image?

 

looks like the key is Linux kernel 5.0.0 or better, since Ubuntu 19.04 is that and Fedora 30 is newer

 

Ubuntu 19.04 doesn't support the emmc on the Udoo.

 

Looks like this is the page that link should be pointing to: https://www.udoo.org/docs-bolt/Operating_Systems/Linux/Known_issues.html