Manjaro Linux - KDE-Plasma & XFCE for VIM1

VIM1
183

good news :smiley:
I managed to build a kernel 5.3 rc4 and inject it into the SD card built with your 5.2 based manjaro image.

I had to

and Download commit aea90d as a zipfile

then booting from the refreshed SD card looked like this :
https://pastebin.com/W8W7tzVk
I know this is a very rough and rogue try, but at least it boot (i’ve seen some error dump in boot log, maybe some other patch need to be applied…)

I can upload the zImage file for anyone to try, upon request…

I wonder if uInitrd and /lib really need to be regenerated as well, I admit I do not know how to exactly regenerate them for now

1 Like
184

Please share the zImage. I have also compiled it but will get it tested in few hours time.

185

Image is @ https://mega.nz/#!UxoQzKDQ
just rename it ot zImage and crush your working zImage with it
and tell us what you end up with !

186

Its asking for decryption key

187

link w/ key : https://mega.nz/#!UxoQzKDQ!-_R7Yl7OHP_rCwzj9Mi3Ka2Lr_aV1tbAMP-69FOJiDU

188

is it because you compile kernel onboard the VIM itself that you need many so hours each time ?
anyway, I see no reason to need qemu to rebuild a kernel…

189

Tried this. Doesn’t seem to boot. Stuck on boot screen

190

…so try my boot.ini in addition

191

Tried that too still the same…

192

sorry i have no idea for now what else to try to make it work on your vim1,
but check you use the appropriate dtb (maybe i should upload mine as well) and show us the console traces you got using a serial usb cable

193

No. I have a working Manjaro 5.2 image and tested if it boots fine then I just replaced the zImage and tried to make it boot but its stuck on boot loop. I i replace the zImage to 5.2.1 from armbians it boots fine with the Manjaro image, So I know I am doing it the write way.

I need to compiling 5.3 somehow but I am not able to understand why it it troubling missing directory error. I will have to go through the compile codes one by one and test it. or make package manually and try it. I was able to compile just the kernel image without the package but that is still the same as

I would request you @chewitt to share the zImage, lib directory of ur compiled kernel with me please, I can try to replace it with my existing 5.2 and check if it works. Coz as you mentioned it worked for you.

Currently I am waiting for the VIM3 to arrive so I can use it to compile regularly without having to wait for long compilation time.

194

Hello @Spikerguy

Here is the linux image based on @chewitt 5.3-rc4 branch

https://dl.khadas.com/test/kernel/5.3.0-rc4/

195

I’m using uImage.gz kernel (bootm to avoid the booti kernel hack) with load and entry address set to 0x1980000 as 0x1080000 stopped working (for me) around Linux 5.1 although I have no explanation for the change. I’ve also noticed kernel build output reporting 0x2280000 to be used so might need to test that value at some point.

https://chewitt.libreelec.tv/vim/ has some test images (warning … file are symlinked from a private dir and the originals change randomly and may be deleted at any time) but LE packaging is different to a conventional distro so that might not get you very far.

196

thanks Nick, but with which linux distro deployed on your VIM1’s EMMC did you check that those file install and boot without error ?

197

@Spikerguy, how to install deb packages on arch ? dpkg is not installed, maybe because packaging method is not the same as ubuntu and debian ?

198

dpkg is he only method I am aware of, as I am not much on an expert on this. Maybe check with the arch forum please.

199

pacman seems the main choice for package installation on Archlinux (and Manjaro); dpkg could be installed via pacman, but some purist warn that using it can lead to issue anytime soon.
the recommended format seems to be PKGBUILD (used by pacman natively)

200

@Spikerguy
maybe we should try this method https://wiki.archlinux.org/index.php/Kernel/Arch_Build_System on top of your 5.2 working manjaro image to upgrade just the kernel to 5.3rc4 !? …via local compilation and deployment

201

Hello @ravelo

You can extract the deb package to get the files.

$ dpkg -x linux-image-amlogic-mainline_0.7_arm64.deb linux-image-amlogic-mainline_0.7_arm64
$ cd linux-image-amlogic-mainline_0.7_arm64
202

what I first tried on my 4.9.179 ubuntu bionic in EMMC was dpkg -i *deb

but upon reboot, I had bootloop, only maskrom + total erase&reflash from windows + usbC cable gave me back the control ! at least, now I 100% sure that my EMMC content is fully “official”