Environment setup done.
Type 'make' to build.
khadas@92f7a138ad22:~/fenix$ make
./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-20200326.img
*********************************************************
Info: Build host: bionic
config/functions/common-functions:79 Error: Building Debian Buster(10) images requires a Ubuntu Focal(20.04) build host, please upgrade your build host or try to build in Docker.
Makefile:7: recipe for target 'all' failed
make: *** [all] Error 255
khadas@92f7a138ad22:~/fenix$
you did not say I now need to upgrade my whole machine into ubuntu 20 !! that’s not funny …
is there anyone else already using ubuntu 20 that can test this docker build please ?
tks.
ok, i bypassed the OS version test and it started,
but ubfortunately ended again like this…
CHK include/generated/compile.h
UPD include/generated/compile.h
CC init/version.o
AR init/built-in.a
LD vmlinux.o
MODPOST vmlinux.o
MODINFO modules.builtin.modinfo
LD .tmp_vmlinux1
KSYM .tmp_kallsyms1.o
LD .tmp_vmlinux2
KSYM .tmp_kallsyms2.o
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
khadas@92f7a138ad22:~/fenix$
to be honest, the physical disk on which I installed the fenix directory is an USB3 hard disk, but it is an ext4 partition (as ntfs is know to be bad for building linux kernel)
Generally it is a bad idea to use usb drive to build anything.
Put it on ssd if you can.
I used to build ubuntu xfce vim3 image with docker on linux mint 19.3 without any problems, so no you don’t need to have ubuntu as host OS
@hyphop, now that I can build buster in docker but only for TF card , how can I go further and generate kresq file ? it seem that your fenix fork does not include the make_debian_mainline_server.sh anymore
do you mean that when VIM1 is booted from its SD having krescue, then its MMC drive can be seen as /dev/sdc (or other letter) from the host linux computer and then I just burn EMMC with the image file built by fenix for SD card ??
I do not currently have any TF card with krescue on it,but if I make one, why not just add the .img file on that same card and then just use dd from the openwrt shell to burn the .img into the EMMC ?
cd fenix/packages/linux-mainline
edit package.mk, change PKG_VERSION="5.5-rc2" into PKG_VERSION="5.5"
and change into
PKG_SHA256=“aca303b87c818cb41c2ddfd4c06d3fcaa85e935fbd61ea203232ccd2a81844bb”
into
PKG_SHA256=“87c2ecdd31fcf479304e95977c3600b3381df32c58a260c72921a6bb7ea62950”
cd patches
cp -r 5.5-rc2 5.5
cd ..
docker start fenix
docker exec -ti fenix bash
source env/setenv.sh
time make | tee buildLog 2>&1
but build fails with these errors:
…
patching file drivers/gpu/drm/meson/meson_rdma.h
patching file drivers/gpu/drm/meson/meson_crtc.c
patching file drivers/gpu/drm/meson/meson_osd_afbcd.c
patching file arch/arm64/boot/dts/amlogic/meson-gxl.dtsi
patching file arch/arm64/boot/dts/amlogic/Makefile
patching file arch/arm64/boot/dts/amlogic/meson-gx-libretech-pc.dtsi
patching file arch/arm64/boot/dts/amlogic/meson-gxl-s905d-libretech-pc.dts
patching file arch/arm64/boot/dts/amlogic/meson-gxm-s912-libretech-pc.dts
patching file drivers/clk/clk.c
Hunk #1 succeeded at 3277 with fuzz 2 (offset 28 lines).
Hunk #2 FAILED at 3294.
Hunk #3 FAILED at 3442.
Hunk #4 succeeded at 4331 with fuzz 2 (offset 22 lines).
Hunk #5 succeeded at 4370 with fuzz 2 (offset 24 lines).
2 out of 5 hunks FAILED – saving rejects to file drivers/clk/clk.c.rej
make: *** [all] Error 1
Makefile:7: recipe for target ‘all’ failed
real 2m52.703s
user 1m21.318s
sys 0m23.211s
I need to check what’s wrong while patching file clk.c
Visibly, I need the appropiate patchset for VIM / amlogic boards for linux 5.5 as at least one file has changed since rc2…
Where can I find the patchset for 5.5 @chewitt and @numbqq please ?
but if I make one, why not just add the .img file on that same card and
sure we have many ways and this one same ok!
then just use dd from the openwrt shell to burn the .img into the EMMC ?
remember !!! if your current os works from emmc , u can broke everything becouse emmc can used by os same time
another situation with krescue because its special system which works fully from RAM, and didnt use emmc/sd after booting! and u can write any data to emmc safety already
as i already have a tf card with bootable ubuntu on it, i will copy the img on it, boot from it and will dd the img from there to the emmc, will that succeed ? or paybe just use amlogic flashing tools on linux after erasing emmc and put vim1 in flash ready mode ?
ok, i’m trying to flash the new image,
I copied the file to a TF card having ubuntu 18 on it;
then I booted from that ubuntu,
I installed lsscsi but it shows no partition
so i tried to identify the emmc partitions names like that: