Alright great - thanks. So it sounds like I’m on the right track getting my hands on your Armbian_5.89_Aml-s905_Debian_buster_dev_5.2.0-rc4_20190621.img.xz then.
I’ve yet to be able to get it to boot from an SD card. I imaged it to SD and tried booting with the button version boot mode, but it just sits at the Khadas logo indefinitely when I try.
img on eMMC is Ubuntu VIM3_Ubuntu-server-bionic_Linux-4.9_arm64_EMMC_V20190621.img, which works fine.
Any tips to point me in the right direction to boot would be great. Thanks!!
Okay thanks, @balbes150 . You’re right: I looked at the DTB but wasn’t clear if I had to change anything–was seeing mixed instructions from place to place. The docs said to copy the dtb file overwriting the one in root. I like your solution instead: edit the ini file to point to the file I want for my board. Will give it a try.
You’re brilliant. I opted for the dtb-5.2.0-rc4-aml-s905 DTB for the VIM3 and it booted perfectly. Thanks again for your work and for the speedy assistance.
@balbes150 is it possible, once I have the image working the way I’d like on SD card, to then transfer it to the eMMC and boot from that? Ie., can an SD image be used as an eMMC image on the VIM3, perhaps with a little customisation? THANKS!
Yes, this is possible. Installation in eMMC works on the principle of copying the existing system in external media (at the time of installation) to eMMC. That is, you can perform a full configuration of your system on external media and then run the installation in eMMC. By the way, I recommend using USB 3.0 media, it is more convenient than SD card and good USB 3.0 is faster than SD card. Importantly. I don’t know exactly how EMMC is defined on VIM3 (mmc0 or mmc1) yet, before starting the installation be sure to check the real EMMC number and install it in the script “install.sh”
The Ubuntu and Debian repositories do not yet have the necessary support for MESA, so I do not include the Lima\Panfrost modules in the images. You can build your kernel version with these options enabled.
The script is part of the image (/root/install.sh). It performs the installation if the installation function is selected in (armbian-config)
Excellent, thank you. I see the MMC device is hard-set in the script. I’ll gladly have a look at my VIM3 today and let you know what the block device name is. If you have it on Github, I could issue a PR, otherwise I’ll publish my changes and you can adopt whatever you like.
@balbes150 could this be something missing from the 5.2.0-rc4 kernel?
lm-sensors is already the newest version (1:3.5.0-3).
Output from sensors-detect:
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
modprobe: FATAL: Module cpuid not found in directory /lib/modules/5.2.0-rc4-aml-s905
Failed to load module cpuid.
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 16h thermal sensors... No
AMD Family 17h thermal sensors... No
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Intel digital thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
Intel 5500/5520/X58 thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Sorry, no supported PCI bus adapters found.
Next adapter: DesignWare HDMI (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Client found at address 0x53
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
Thank you for confirming my suspicion. Do you know of an ETA? Will this come in via a dist-upgrade? Or would I just be better to revert to the 4.9 kernel?
I have CPU frequency control working on the v10 (S922X) version of the VIM3 and hopefully in a few days we’ll have a device-tree for the v11 (A311D) production version. Thermal code has been sent to the mailing-list but it attacted a lot of feedback so i’m expecting it to take a few more iterations before code gets merged.
for VIM3
The script of the images amlg-12 already included in the activation script of sound (started manually it is no longer necessary, at first start, the system itself needs to run).
VIM3 pre-production samples with the S922X chip can use meson-g12b-s922x-khadas-vim3.dtb and the customer shipping versions with A311D can use meson-g12b-a311d-khadas-vim3.dtb … the only difference is the A311D dtb supports faster CPU speeds.
@balbes150 note that the latest version of my kernel sources renamed meson-g12b-ugoos-am6.dtb to meson-g12b-s922x-ugoos-am6.dtb so the chip type is obvious. N2 was also renamed.
