VIM3 commits in my branch depend on my changes to split device-trees into S922X/A311D, which depends on DVFS changes, which depend on various other bindings and GPIO changes, which depend upon … scroll backwards until you spot the 5.2.1 kernel bump commit, it’s a few pages.
Until much more code gets upstream in 5.3/5.4 you need to use a branch with lots of extra stuff, either one of mine or from @narmstronghttps://github.com/superna9999/linux/branches/active … the trick is understanding what the focus of each topic branch is focussed on. If you track over time it becomes clearer. Feel free to ask Q’s in #linux-amlogic on freenode - there’s usually someone doing similar things who can help.
Hi. Are you using the USB3 port? Wifi doesn’t seem to work when the USB3 port is in use with a USB3 device. My experience is that it slows down a lot with a USB2 mouse wifi dongle in it.
The wifi connector is right next to the USB3 port. And USB3 interferences on the 2.4Ghz frequency.
It’s a problem with all SBC’s with USB3 and using wifi dongles + using a USB3 device.
Having built and booted your kernel, I find that uname -a still lists the version as 4.9.179, even though my package is from your 5.2.1 branch and the Version numbers in the Makefile is 5.2.1.
So I boot from SD card, with a kernel 5.2.1 built. It boots fine. But uname still says it’s kernel 4.9.179-1, even though I used a 5.2.1 source for it.
So I am just wondering. Is the kernel version hardcoded into Uboot or something?
The kernel source I built from is the one linked in this thread, which has:
VERSION = 5
PATCHLEVEL = 2
SUBLEVEL = 1
EXTRAVERSION =
NAME = Bobtail Squid
In the Makefile. Why is this not getting honored?
PS: I have no trouble building kernels for other devices with my PKGBUILD’s that uname picks up fine.
There must still be some uboot left on your emmc and I would even say also some kernel
Emmc is partionned, which partitions did you really blank ?
Get inspiration from this
And then be sure to point to the good dtb file…
Then put it as boot.ini in your boot partition on your SD card once you have flashed it with your own home built firmware (kernel and manjaro)
I might be misunderstanding me.
The system boots fine from SD card. It boots, it works etc.
The issue is that my kernel (built from kernel source 5.2 linked previously in this thread) shows as kernel 4.9.179 by uname, while should, according to the makefile, be version 5.2.1.
I blanked all the partitions/devices listed by lsblk. And if I have no SD card in the device, it does not boot at all. So I am pretty sure, it has nothing on the eMMC.
I fully understand you, I was in the same situation, I solved it since then, by putting a good boot.INI on the SD card, which tells the vim to load all the correct files, especially the kernel 5
Classic mistake. If nothing is started from eMMC, it does not mean that EMMC is empty. This only means that you do not have a working u-boot on the eMMC or there is no necessary data for the root system. There is only one option when there is nothing in the eMMC, run the command “dd if=/dev/zero of=/dev/mmcblkX bs=64Mb” (substitute the eMMC number instead of X, as it is defined in the system).
In principle, there can be no situation, if the MAKEFILE specified kernel 5, get 4.9. The system will simply not build such a kernel.
Useful information. Kernel 5 does not see the partitions that are created for Android\Ubuntu (using the specific amlogic partition system) in eMMC (which contains the old kernel 4.9), so you will not see anything when using the standard Linux utilities.
@Strit
Get back to a well known situation: flash your whole emmc with some official (and preferably multiboot compatible) firmware , then the vim should be able to properly start your home built firmware as you expect, until then , good luck if you want to fix everything by yourself
Your vim visibly does not load your Linux 5 kernel but a 4.9 one you do not yet understand where it is hidden , these are the plain brutal facts my friend
I did this just now, which resulted in our 5.2 kernel not booting at all, so I expect there was something left on the eMMC that it booted from.
Our images with 4.9 does still boot, but not the ones we create with 5.2 now. So I guess we are probably missing something in regards to going more mainline.
To start the system from the Sd card (after erasing eMMC), you need to add u-boot to the SD card. You can use u-boot-2019, there is support for VIM1 and VIM2.
Then restore the firmware from Android and use the universal multi-boot. This is the best option to provide all users with a simple and proven way to run any system from external media.
