Hello,
We just need some minor clarification for the installation of UberXMHF rpi3-cortex_a53-armv8_32 . We followed the steps in https://uberxmhf.org/docs/rpi3-cortex_a53-armv8_32/installing.html. Our only issue is for step 18. We don’t have a similar output in ~/mnt/pi-root/etc/fstab like in the doc. Instead we get something like:
PARTUUID=d9b3f436-01 /boot vfat defaults 0 2
PARTUUID=d9b3f436-02 /boot vfat defaults 0 2
We should comment the first line? Also we must have the rasbian mounted while the setup occur?
Thank you in advance
Hi @SavvasR1991,
I am assuming you followed all the instructions for build as described in:
https://uberxmhf.org/docs/rpi3-cortex_a53-armv8_32/build.html
In particular can you confirm that you are using Raspbian Jessie Lite distro as mentioned in step-1 of https://uberxmhf.org/docs/rpi3-cortex_a53-armv8_32/build.html ?
Also we must have the rasbian mounted while the setup occur?
Yes, the installation guide expects the SD card (with Raspbian installed) to be mounted at /dev/mmcblk0
Yes we are using the Raspbian Jessie Lite, is it possible to provide us of some screenshots of what we must expect after the installation and the boot is done properly? There will be some gui interface or some command prompt for example that we could interact?
Thank you in advance
There is currently no GUI installation interface available, but we can certainly try to resolve this if you can provide some more information as below.
You will have to gather the following information by booting into the Raspbian OS (without the micro-hypervisor) on the Pi3. You may have to edit /boot/config.txt on the SD card filesystem and replace the kernel and kernel_address variables with default values to boot the Raspbian Linux kernel (without the micro-hypervisor). Check https://www.raspberrypi.org/documentation/configuration/config-txt/boot.md for the default values.
Once you boot into Raspbian on the Pi3 issue the following commands:
sudo cat /etc/fstab > fstab_dumpsudo blkid > blkid_dumpsudo uname -a > uname_dump
Post your fstab_dump, blkid_dump, and uname_dump in this thread and we can go from there…
Hello
Thank you for your feedback , we will try to gather your requested information. Nevertheless, with the current implementation we should expect a command prompt for inderaction? And if so is there a specific command list for this?
Thank you
In addition we provide the output that you have requested above. We have also expand the file system.
One interacts with the micro-hypervisor and/or uapps via the rich-guest OS shell. i.e, you boot into the OS with the micro-hypervisor and then use the OS shell to issue appropriate hypercalls/trigger-events that are then handled by the core micro-hypervisor framework and/or uapps.
In addition we provide the output that you have requested above. We have also expand the file system.
I am a little confused. Your output of /etc/fstab (per the attached diagram) is consistent with what is currently described in the installation documentation (step-18). However, previously you had stated that the /etc/fstab had PARTUUIDs.
