Unpack.
Log in to the resulting directory and run the media script as ROOT.
After the script is finished.
Be sure to reboot the system with the new kernel.
Check and fix references to libMali libraries as described in the previous post.
Run commands as ROOT.
depmod
modprobe mali
To check the operation of the MPV with the regime of HW.
If the sound doesnât work. Run the command as ROOT
ok so I copied Armbian_5.73_Aml-s912_Ubuntu_bionic_next_5.0.0-rc4-next-20190130-g02495e76d-dirty.img file to SD card and renamed it to Khadas-emmc.img
Booted to VIM2 from another armbian on SD
mount /dev/sda1 /ddbr
and ran ddbr restore as I said before.
And no magic happened - system doesnât boot anymore.
Why would you do that ? You violated every instruction. You recorded the image from Sd card to eMMC. Where did you see such a recommendation ? Utility DDBR is intended solely for the backup with the eMMC and then restoring from the backup.
Recovery via M-register. If you are going to create your own partitions, then from the beginning correctly install the system in eMMC with the transition to u-boot-2018 (Strictly according to the instructions in this topic). You check that the system normally started from eMMC. After that, start the system from the SD card and carefully (using GPARTED) redistribute the partitions created during the installation (reduce the last partition and create your new additional ones).
ok soâŚ
according to this instruction Armbian + KODI (Ubuntu\Debian) for SD & USB & eMMC
Iâve downloaded u-boot-2018.img
booted to my old and stable armbian sd i donât wanna touch
in instruction it is said i need to dd uboot to mmcblk1 (sd card) - I donât want to ruin it so what I did (and failed):
I made new bootable sd with Armbian_5.75_Aml-s912_Ubuntu_bionic_default_4.20.5_20190211.img using âburn card makerâ from https://dl.khadas.com/Tools/
booted to working sd and repartitioned new sd with my needs.
mounted sda1 and edited uEnv.ini to boot root from new partition (sda3)
unmounted sda1
dd if=u-boot-2018.img of=/dev/sda (instead of mmcblk1 witch is my working sd)
dd if=u-boot-2018.img of=/dev/mmcblk0 (itâs doesnât work anyway so why not)
poweroff and replaced old SD with new SD with armbian 5.75
and booting freeze at this point:
To install in the eMMC with uboot-2018, you need to first rename one of the existing files on the media " Sxxx-uboot.img " to â uboot.img â (select the option for your model). After renaming the file âuboot.imgâ, to install Armbian in eMMC, you need to run the script â /root/install-2018.sh â.
p/s/
I wonder why You make up your steps instead of just following the instructions ?
I just tested your latest image Armbian_5.75_Aml-s905_Ubuntu_bionic_dev_4.19.21_desktop_20190214.img and install media script, glmark2-es2 and mpv work well, but I canât open Chromium web browser, it stucks.
If execute it in command line I found some errors.
Unable to revert mtime: /usr/local/share/fonts
[2821:2821:0214/100237.917050:ERROR:gl_surface_egl.cc(336)] eglChooseConfig failed with error EGL_BAD_ATTRIBUTE
[2821:2821:0214/100237.922833:ERROR:gl_surface_egl.cc(336)] eglChooseConfig failed with error EGL_BAD_ATTRIBUTE
[2821:2821:0214/100237.923985:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process.
[2780:2780:0214/100238.261334:ERROR:x11_input_method_context_impl_gtk.cc(144)] Not implemented reached in virtual void libgtkui::X11InputMethodContextImplGtk::SetSurroundingText(const base::string16 &, const gfx::Range &)
[2821:2821:0214/100238.496363:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.510963:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.518842:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.552954:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.568570:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.589042:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.618748:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.632883:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.657986:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.687092:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.714420:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.720949:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.747974:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.754484:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.781004:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.787984:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.814975:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.827632:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.847922:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
[2821:2821:0214/100238.854870:ERROR:gles2_command_buffer_stub.cc(310)] ContextResult::kTransientFailure: Failed to make context current.
Do you have this issue?
If I delete /etc/chromium-browser/default then I can open Chromium web browser well, but no HW accel.
I checked at myself the regular browser, video works is accelerated in YouTube on a full screen (I donât put options Chrome from a media script). What browser are you trying ?
because I canât find clear step-by-step instructions. And everything is strange
I created SD card with Armbian_5.73_Aml-s912_Ubuntu_bionic_next_5.0.0-rc4-next-20190130-g02495e76d-dirty.img
It booted and showed me
Welcome to ARMBIAN 5.73 user-built Ubuntu 18.04.1 LTS 4.9.40
not 5.0.0 But okâŚ
I copied /boot/S912-uboot.img to /boot/uboot.img
Ran as you told me:
./install-2018.sh
rebooted - uboot still 2015 and system booted to old khadas ubuntu Iâve installed before
plugged in SD card again and booted to Armbian
/boot is mounted with mmcblk1p1 but all files from it disappeared
I donât understand⌠All I need is a fdisk partitioned emmc with kernel 5.x on one vim2 and kernel 4.x on another vim2. And I canât get it for two days. What instruction I need to follow? Please help meâŚ
The manual is written for use when eMMC is FULL firmware Android. You have Ubuntu in eMMC, this is a completely different installation procedure. Either install the standard Android firmware (which comes from the factory) into eMMC or use another installation procedure.
Booted to Vim2 and entered run update to boot from SD
And got kernel panic on boot - reset doesnât help. With Khadas ubuntu on emmc it was booting.
Ok moving to 5.75 dd if=./Armbian_5.75_Aml-s912_Ubuntu_bionic_default_4.20.5_20190211.img of=/dev/disk2 bs=8m
Booted to Linux aml 4.20.5-aml-s912
cp /boot/s912-uboot.img /boot/uboot.img
./install-2018.sh - finished without errors
rebooting to EMMC - and it booted ok⌠phewâŚ
Can you please tell me why your image 5.0.0-rc4 shows kernel 4.9.40? Do you have an image with 5.x kernel?
Write in detail what "run update"means. The image must be written by programs, not by the "dd"utility. This has been discussed many times in the Armbian forum - do not use âddâ. Writing through âddâ caused a lot of problems.
What reset doesnât help ?
I have no images with core 4.9.40. Where do you get this core, I do not know.