Thanks!
I do have it running now. I found some older instructions that got me headed in the right direction: Armbian + KODI (Ubuntu\Debian) for SD & USB & eMMC
I now have it running off of sdcard. I’m not sure yet if/how I can install to EMMC.
Now I’m back to the question of how to build at least the kernel. I tried adding a driver using dkms, and it can’t find the kernel headers, and I don’t see a package with the appropriate kernel version.
Edit: I think I found how to build the kernel here: https://forum.armbian.com/topic/12162-single-armbian-image-for-rk-aml-aw/?do=findComment&comment=97291
I have everything working great running off sdcard. Is it possible to transfer what I have to emmc and/or nvme? I see there are scripts in the /root directory, but I tried running the install-aml-s905-emmc.sh script, and that didn’t work.
The script complained about not having room to copy the kernel, which doesn’t seem ideal. I could probably figure that out, but I think it may have messed up u-boot as well, since I now have a cyan background on the console, and I don’t fully understand all the issues with u-boot.
Do you have a model with an s905 chip ? The script is used for s905x\s912\s922 (install-aml.sh).
I have a VIM3L, so I believe I do have a s905 chip. I tried running the install-aml.sh, and that seemed to work, but I’ve been unable to boot from either EMMC or scdard.
I even re-installed android and re-ran the install-aml.sh script after stumbling through figuring out how to get it to boot from sdcard again. It did boot from sdcard, although the screen was blank.
After running the script it will no longer boot from either EMMC or sdcard. It just seem to be waking up the screen every few seconds like it’s in a boot loop.
Is there some documentation about installing Armbian on this board for the complete dummy? Not that I’m a dummy. I have an MS in EE, and a couple dozen different SBCs that mostly run Armbian, but this one is by far the most complex and worst documented.
Why won’t you let this image be installed by @hyphop krescue? That seems to be the only installation method that actually works, and if that would work it would eliminate all the issues that people seem to be having installing this.
I have two of these boards, and they seem like very good hardware, but I’m just about to throw them in the trash because I’ve spent so much time trying to find an OS that actually works. Your Armbian install seems to be very good (as is generally the case with Armbian in my experience), but it’s not usable if it can’t be installed.
This is the s905d3 chip, this is a completely different option, not compatible with s905.
Which version exactly do you use ? What tool was used to perform the installation ?
I don’t need any more trouble. At this link, you can see some of the problems that kreskue brings. It describes the simplest problems, but krescue also brings serious security problems and other side effects that make such an installation unacceptable.
I don’t have VIM3L and I don’t support this model. So with this model, I can only help you with General recommendations. For reference, Armbian installs perfectly and works from eMMC on VIM1 VIM2 VIM3 EDGE EDGE-V. If you want to install Armbian in eMMC, I will need a log from the UART console to find an error in the regular firmware in eMMC. Important. For the system to work correctly in eMMC, there should be no extraneous (hidden) elements, this is only possible when restoring the firmware via the regular USB Burn Tool, any other tools not guarantee the correct installation of the firmware in eMMC.
1 Like
sound configuration totally broken 
spdif not work, i2s same not works
kernel sometimes have segfaults after manipulation with hdmi sound mixer, pulseaudio cannot work (only dummy sound card) without special changes !
but armbian works fine 
1 Like
Do not mislead people! all manjaro-krescue presented images always was marked by test tag it means this one only for demo test !
1 Like
Well, that’s not so obvious…
I’ll try to get a boot log, but if you don’t support the VIM3L, I don’t see why you don’t let @hyphop support it. I don’t know all the politics behind this, but krescue is documented in the " VIM3 Beginners Guide", so I can’t believe it’s too bad. Even if it’s broken at times, condensing down a bunch of steps that are documented across multiple forum posts into a “click and install” seems like a win from a support perspective.
From an engineers perspective I appreciate trying to build a generic framework that works on multiple architectures, but the existing Armbian model of “find image for your SBC and burn it” works very well.
1 Like
Plz don’t trust some forum users
U can try and test how works krescue by you self
And install many different os
Its really easy and fast
Armbian not shared at this time because armbian have some trouble’s
I have prepare armbian for vim3l and other VIMS boards and still in test but already usable
1 Like
So far, Armbian has been the most stable for me. I’ve been running it for a while off sdcard, and it has worked very well.
The fenix-based distros seem to have issues with standard wifi drivers, at least the ones that I need, but that’s not the case with Armbian.
I come here asking some people for a little more respect with the developers. (people who take the time to help).
I have known the work of the balbes150 for many years, he has always dedicated his time to helping and providing the best for the users of his images (he has done an excellent job where many take advantage).
No matter what country we live in, today we really need each other because we are not only losing “numbers” to the Covid-19 virus, but losing our friends. Why insult?
I ask some developers and others here to stay in their spaces. (here in this house balbes are always judged and never praised).
@balbes150 makes a decision about this behavior and leaves the forum, I do not understand why the moderators allow insults without warning / prohibition. @Gouwa
Some people here didn’t buy Khadas vim3 waiting for @balbes150 and @chewitt in short, libreelec team finishes its work, so here is the tip for those who think they are important!
If anyone here didn’t like what was said by me do a better job than balbes150.
2 Likes
please freeze and close this discussion, and let’s focus on something more positive, another distro on another board for example…
peace.
2 Likes
I have found balbes150 to be universally arrogant and unhelpful.
And why wait for two years for a developer to get his shit together when there are perfectly adequate and functional alternatives which work since day one ?
Shoog
1 Like
- Audio via HDMI works for many months, but you need to follow the instructions correctly to use it. For older versions of images, you had to delete pulseaudio before using it (this information was given many times). In the new versions, you do not need to delete anything , everything works perfectly and you can choose different configurations in the settings, including multi-channel sound.
- I don’t have SPDIF and I don’t check it. If it doesn’t work - this is a claim primarily to you. You, as an official developer who receives a salary from Khadas, do not do your job, have not provided the necessary changes in the main core to support Khadas products.
I don’t care what doesn’t work in your images. I answered the user why I am against the release of such “semi-finished products” for my development, which increase the number of unknown problems.
You don’t understand the point, there is no support for VIM3L from hyphop. It only offers to build a dubious version of the image from the Armbian image exclusively for installation through its application. At the same time, this option immediately gets a number of problems that have absolutely nothing to do with my development. And users will start asking me to solve these problems, which I have nothing to do with.
You’re wrong there, too. External simplicity hides a number of serious problems, including security. I’m not going to discuss this publicly, so as not to give all sorts of freaks and hackers tips on how to use it.
I have already warned that no Armbian versions from my versions or sources can be released as images for kreskue. If there are any, I will consider it a gross violation of the author’s prohibition.
looking forward to Armbian-K-Rescue!
P.S. I do not allow unreasonably deleting my posts!
I’m sorry if I offended anyone, and I really don’t want to get involved in any of the, obviously complex politics. I just want to try to get Armbian running properly on the VIM3L.
It looks to me like the problem with getting Armbian installed on the EMMC is getting the proper u-boot installed. The script copies off the existing u-boot, creates the partitions and them copies it back, which, of course, requires that the u-boot on the EMMC already be the “proper” u-boot.
This leads to having to first have a properly installed (and configured?) Android installation on the EMMC, which boots from EMMC, which then requires some other procedure to make it boot off of sdcard again so that we can run the script that then reads the 4MB u-boot off the EMMC. Do I have that right?
Assuming that this u-boot is standard for e.g. all VIM3Ls, that seems like a very long and complicated process to get a single 4MB file.
I understand that the attempt is to make the Arbmian image somewhat generic, although it must at least have a dtb for each architecture. Wouldn’t it also require many different kernels? Would adding a few u-boot files be too much?
Is there somewhere that one could download just the u-boot image rather than copying it from the EMMC?
Yes all the dtb for amlogic devices are present in the boot partition in dtb/amlogic/ directory.
You might just have to change the dtb name accordingly to your device dtb inside UEnv file which is in the root of the Boot partition.
The kernel maintained by balbes have support for most of the devices he maintains which includes amlogic and rockchip devices.
Hope this helps.
I recommend that you read this message carefully. From the factory, all VIM comes with a working Android firmware, so the system starts and installs in eMMC for Armbian and Libreelec uses a regular u-boot, which guarantees the correct operation of all parts of the system, including subsequent automatic core updates and the absence of Trojans and other dishonest things to steal your personal data. If you want to risk your personal data - this is your personal business, you can use any questionable systems that destroy the security system. Personally, I do not want users of my systems to be exposed to this risk and then make claims to me that something is not working correctly or their personal (important) data has been stolen.
1 Like
there could be trojans as well inside the android installation and inside the EMMC, how would you know ?