Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a question about uploading the kernel packages. Should I update the bootloader files at the same time? It seems like this is necessary when switching kernel branches. However, if I am upgrading from 4.4.268 to 4.4.269, should I also update the files that get put into the boot-***.txz archive?
If so, what would the exact commands be? I am able to do this on the Pinebook with these instructions, just for reference:
What would be the equivalent commands for the three files that get created for the Rock64? (idbloader.img, rkspi_loader.img, u-boot.itb) Specifically, what would the seek values be?
thank you.
the bootloader generally does not need to be rewritten, even when migrating from kernel versions.
bootloader entry for rock64
Now, there seems to be an issue building u-boot. I am trying to build a legacy server image for rock64, and this happens during the u-boot build:
Code:
CC lib/display_options.o
LD lib/built-in.o
LD u-boot
OBJCOPY u-boot-nodtb.bin
./"arch/arm/mach-rockchip/make_fit_atf.py" \
arch/arm/dts/rk3328-rock64.dtb > u-boot.its
RELOC u-boot-nodtb.bin
MKIMAGE u-boot.itb
/home/user/code/images_build_kit/build/source/u-boot /home/user/code/images_build_kit/build/source/u-boot
tools/mkimage: Can't open /home/user/code/images_build_kit/build/source/rkbin/bin/rk33/rk3328_ddr_333MHz_v1.16.bin: No such file or directory
Error: Bad parameters for image type
Usage: tools/mkimage -l image
-l ==> list image header information
tools/mkimage [-x] -A arch -O os -T type -C comp -a addr -e ep -n name -d data_file[:data_file...] image
-A ==> set architecture to 'arch'
-O ==> set operating system to 'os'
-T ==> set image type to 'type'
-C ==> set compression type 'comp'
-a ==> set load address to 'addr' (hex)
-e ==> set entry point to 'ep' (hex)
-n ==> set image name to 'name'
-d ==> use image data from 'datafile'
-x ==> set XIP (execute in place)
tools/mkimage [-D dtc_options] [-f fit-image.its|-f auto|-F] [-b <dtb> [-b <dtb>]] [-E] [-B size] [-i <ramdisk.cpio.gz>] fit-image
<dtb> file is used with -f auto, it may occur multiple times.
-D => set all options for device tree compiler
-f => input filename for FIT source
-i => input filename for ramdisk file
-E => place data outside of the FIT structure
-B => align size in hex for FIT structure and header
Signing / verified boot not supported (CONFIG_FIT_SIGNATURE undefined)
tools/mkimage -V ==> print version information and exit
Use '-T list' to see a list of available image types
Now, there seems to be an issue building u-boot. I am trying to build a legacy server image for rock64, and this happens during the u-boot build:
Code:
CC lib/display_options.o
LD lib/built-in.o
LD u-boot
OBJCOPY u-boot-nodtb.bin
./"arch/arm/mach-rockchip/make_fit_atf.py" \
arch/arm/dts/rk3328-rock64.dtb > u-boot.its
RELOC u-boot-nodtb.bin
MKIMAGE u-boot.itb
/home/user/code/images_build_kit/build/source/u-boot /home/user/code/images_build_kit/build/source/u-boot
tools/mkimage: Can't open /home/user/code/images_build_kit/build/source/rkbin/bin/rk33/rk3328_ddr_333MHz_v1.16.bin: No such file or directory
Error: Bad parameters for image type
Usage: tools/mkimage -l image
-l ==> list image header information
tools/mkimage [-x] -A arch -O os -T type -C comp -a addr -e ep -n name -d data_file[:data_file...] image
-A ==> set architecture to 'arch'
-O ==> set operating system to 'os'
-T ==> set image type to 'type'
-C ==> set compression type 'comp'
-a ==> set load address to 'addr' (hex)
-e ==> set entry point to 'ep' (hex)
-n ==> set image name to 'name'
-d ==> use image data from 'datafile'
-x ==> set XIP (execute in place)
tools/mkimage [-D dtc_options] [-f fit-image.its|-f auto|-F] [-b <dtb> [-b <dtb>]] [-E] [-B size] [-i <ramdisk.cpio.gz>] fit-image
<dtb> file is used with -f auto, it may occur multiple times.
-D => set all options for device tree compiler
-f => input filename for FIT source
-i => input filename for ramdisk file
-E => place data outside of the FIT structure
-B => align size in hex for FIT structure and header
Signing / verified boot not supported (CONFIG_FIT_SIGNATURE undefined)
tools/mkimage -V ==> print version information and exit
Use '-T list' to see a list of available image types
In my opinion you did a fantastic job here. I tried a couple of systems like Armbian, Manjaro, Arch Linux. None of them worked satisfactory. Armbian stopped providing an image, due to a lack of maintainers. Besides your slackware image, none of them provided a workable resolution. Good work, thank you. Now I can still keep using my rock64!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
