Krescue - take full control of your VIM device! easy way to install ANY OS! + back/restore your system

i have seen sometimes some strange behavior with Ethernet
its problem for all mainline Kernel on VIM3

i think need more testing!

  1. board booted from emmc? and which uboot version ?
  2. clear emmc boot ! and try start krescue fully from sd and check what happens with ethernet

hyphop
VIM1.Android.Pie_V190823.emmc.kresq

can you add root?

not at the address, Terry does the firmware, and yes, there has been a root update for a long time

the last time i used fenix, it was still not able to produce mainline kernel debian for emmc, and your khadas recue initiative was our only solution to get mainline kernel install to emmc and booting from emmc, please push harder fenix to become compatible with mainline linux debian kresq :sob:

i have made this one (like a fork) already but in test mode yet (after testing it will be integrated to master branch )

git clone https://github.com/hyphop/fenix.git
cd fenix
git checkout hyphop
../scripts/make_debian_mainline_server.sh [VIM1] [VIM2] [VIM3] [VIM3L]

NOTE: last script generate raw and compressed image which suitable write both to EMMC same as SD

NOTE: mainline uboot + mainline kernel + debian 10 buster base

PS: after complete testing we will make announce about new debian images

2 Likes

UPDATED & FIXED MAINLINE UBOOT kresq image

DOWNLOAD uboot files for each VIMx devices

1 Like

This looks good. So I can just flash this on the SDcard while emmc have legacy uboot, will that be fine ? or this should be on the eMMC ?

  1. can write it to SD/eMMC
  2. VIM3 VIM3L always start from emmc if uboot presented on emmc and sd uboot was ignored
  3. if u have legacy uboot on emmc - u will have same problem with GREEN screen

That means this will not help those you want to keep the android on EMMC and use Linux on SD :frowning:

i still not find elegant universal solution for multiboot - but i try :wink:

  • u can patch your kernel for usage with legacy uboot

We cannot patch it for every use case. So Instead we will just wait for a fixed solution to follow.

at this moment i think krescue installation to emmc its best choice

because if u try to boot somthing from sd u can always depend from emmc uboot

1 Like

I dont have any problem. I am just trying to give a stable solution to normal regular home users who like Khadas Hardware :smiley:
Thanks for your work.

Hey, this does not work, but
./scripts/make_debian_mainline_server.sh VIM1
gives…

# cd ./scripts/..
# ln -sf build/linux-mainline-* linux
[i] build uboots: VIM1
[i] build VIM1
./scripts/create_image.sh

***********************PARAMETERS************************
Fenix Version:         0.8.3
Khadas Board:          VIM1
Uboot Version:         mainline
Uboot Configuration:   khadas-vim_defconfig
Uboot Branch:          master
Linux Version:         mainline
Linux Configuration:   defconfig
Linux DTB:             arch/arm64/boot/dts/amlogic/meson-gxl-s905x-khadas-vim.dtb
Linux Branch:          master
Distribution:          Debian
Distribution Release:  buster
Distribution Type:     server
Distribution Arch:     arm64
Install Type:          SD-USB
Final Image:           VIM1_Debian-server-buster_Linux-5.5-rc2_arm64_SD-USB_V0.8.3-20200310.img
*********************************************************

Info: Build host: bionic
Info: Installing build dependencies
Info: Requires root privileges, please enter your passowrd!
Hit:1 http://fr.archive.ubuntu.com/ubuntu bionic InRelease
Hit:2 http://fr.archive.ubuntu.com/ubuntu bionic-updates InRelease                                         
Hit:3 http://ppa.launchpad.net/eh5/pulseaudio-a2dp/ubuntu bionic InRelease                                 
Get:4 http://fr.archive.ubuntu.com/ubuntu bionic-backports InRelease [74,6 kB]                             
Get:5 http://security.ubuntu.com/ubuntu bionic-security InRelease [88,7 kB]                                
Hit:6 http://ppa.launchpad.net/teejee2008/ppa/ubuntu bionic InRelease                                      
Get:7 https://dl.yarnpkg.com/debian stable InRelease [17,1 kB]                                             
Err:7 https://dl.yarnpkg.com/debian stable InRelease                              
  The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx>
Fetched 163 kB in 1s (213 kB/s)
Reading package lists... Done
Building dependency tree       
Reading state information... Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx>
W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease  The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx>
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libusb-1.0-0-dev : Depends: libusb-1.0-0 (= 2:1.0.21-2) but 2:1.0.23-2build1 is to be installed
E: Unable to correct problems, you have held broken packages.
Makefile:7: recipe for target 'all' failed
make: *** [all] Error 100

My build machine runs ubuntu 18.04.4, and I had issues regarding unmet dependencies,
any idea to fix this ?
May I suggest that you provide a docker solution ? fenix is much easier with docker image ready to use…
tks

Ok,
in the past, I’ve had issue setting up a perfect build environement for fenix. Then I tried (successfully) to use the provided instruction for doing it in docker container as seen in https://docs.khadas.com/vim2/FenixScript.html#Run-Fenix-in-Docker

I need to combine them with your instructions before…
and we’ll hopefully see some positive result I’ll report once the current build is finished

Here are my steps inside docker :

khadas@9d6fa07dc338:~/fenix$./scripts/make_debian_mainline_server.sh VIM1

LD vmlinux
SORTEX vmlinux
SYSMAP System.map
OBJCOPY arch/arm64/boot/Image
Building modules, stage 2.
MODPOST 1746 modules
warning: same module names found:
fs/exfat/exfat.ko
drivers/staging/exfat/exfat.ko
make[1]: Leaving directory ‘/home/khadas/fenix/build/linux-mainline-5.5-rc2’
Info: Building debs…
Building package: linux-u-boot-vim1-mainline
dpkg-deb: error: control directory has bad permissions 777 (must be >=0755 and <=0775)
Makefile:7: recipe for target ‘all’ failed
make: *** [all] Error 2

Something needs to be fixed, I’ll try t o find how,
@numbqq do you have any idea ?
tks

UPDATE: as my FS in NTFS, and according to https://unix.stackexchange.com/questions/252244/dpkg-deb-error-control-directory-has-bad-permissions
the problem is know, I need to move thing on an ext3 or ext4 FS…

UPDATE2:
I fixed the filesystem issue, but this is how it still ends…

  LD [M]  sound/usb/line6/snd-usb-variax.ko
  LD [M]  sound/usb/snd-usbmidi-lib.ko
warning: same module names found:
  fs/exfat/exfat.ko
  drivers/staging/exfat/exfat.ko
make[1]: Leaving directory '/home/khadas/fenix/build/linux-mainline-5.5-rc2'
Info: Building debs...
cp: cannot stat '/home/khadas/fenix/linux/arch/arm64/boot/dts/amlogic/meson-gxl-s905x-khadas-vim.dtb': No such file or directory
Makefile:7: recipe for target 'all' failed
make: *** [all] Error 1
khadas@38b1d52425fb:~/fenix$

and…
khadas@38b1d52425fb:~/fenix$ cd /home/khadas/fenix/linux/arch
bash: cd: /home/khadas/fenix/linux/arch: No such file or directory

ah ha !!

You use the source code from @hyphop. And this issue already has beed fixed in Khadas Repo. But @hyphop have not fetch the latest patches.

You can cherry-pick this patch and try again.

1 Like

I applied your patch and retried,
this time it goes farther but we still have some error as we see below:

wiringpi_debs-c1f48d2dbe [ <=> ] 120.17K 375KB/s in 0.3s

2020-03-12 23:24:31 (375 KB/s) - ‘wiringpi_debs-c1f48d2dbe0417cf34699f2edd6bc0ff6bf86f40.tar.gz’ saved [123054]

Calculated checksum is: 281c2711485b3495d076825fc3c933fe3d911879ff96bb82252aa36aa2f687c3
Extracting 'wiringpi_debs-c1f48d2dbe0417cf34699f2edd6bc0ff6bf86f40.tar.gz' to '/home/khadas/fenix/build'...
./scripts/create_image.sh:111 Warning: This script requires root privileges, trying to use sudo, please enter your passowrd!
Info: Preparing rootfs for VIM1-buster
Info: Creating new rootfs for buster
Info: Installing base system - Stage 1/2
/usr/sbin/debootstrap: 1455: /usr/sbin/debootstrap: cannot create /home/khadas/fenix/build/images/.tmp/rootfs-VIM1-buster-server/test-dev-null: Permission denied
E: Cannot install into target '/home/khadas/fenix/build/images/.tmp/rootfs-VIM1-buster-server' mounted with noexec or nodev
Cleanup...
Makefile:7: recipe for target 'all' failed
make: *** [all] Error 1
khadas@38b1d52425fb:~/fenix$

maybe this is related to this apparently unsloved github issue ? :cold_face:https://github.com/khadas/fenix/issues/58

No idea yet, haven’t tested Debian buster.

plz open new thread or use other exist for fenix build ! we can try to solve it

please join me in this new thread Fenix, docker build, debian buster, krescue
@numbqq and @hyphop and whoever is interested
thx

1 Like