From: Anachron <Anachron@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New packages: rockpro64-base and rockpro64-uboot
Date: Mon, 21 Mar 2022 22:04:53 +0100 [thread overview]
Message-ID: <20220321210453.RUc3H7aI8drYnEAb2agKRb0fLxJIZ1ZeujZHhzmzceg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33556@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3739 bytes --]
New comment by Anachron on void-packages repository
https://github.com/void-linux/void-packages/pull/33556#issuecomment-1074358467
Comment:
After digging a bit more I believe the issue is that https://github.com/void-linux/void-mklive/blob/master/mkplatformfs.sh.in#L180 is not trigger for my `platformfs` build, even though I have the tools but not the files:
```sh
ls -lisah usr/bin/{mkimage,dracut}
919096 88K -rwxr-xr-x 1 root root 85K 14. Jul 2021 usr/bin/dracut
919116 300K -rwxr-xr-x 1 root root 299K 21. Jan 01:10 usr/bin/mkimage
```
```sh
LC_ALL=C ls -lisah boot/*nitrd
ls: cannot access 'boot/*nitrd': No such file or directory
```
Probably because of https://github.com/void-linux/void-mklive/blob/master/mkplatformfs.sh.in#L182, I build for `aarch64` but it checks for `arm` in `XBPS_TARGET_ARCH`.
Edit: Yes, it builds the `initrd` now by deleting https://github.com/void-linux/void-mklive/blob/master/mkplatformfs.sh.in#L182.
```sh
file boot/*
boot/config-5.15.30_1: Linux make config build file, ASCII text
boot/dtbs: directory
boot/initramfs-5.15.30_1.img: gzip compressed data, max compression, from Unix, original size modulo 2^32 69921792
boot/initrd: gzip compressed data, max compression, from Unix, original size modulo 2^32 69921792
boot/uInitrd: u-boot legacy uImage, Void Linux, Linux/ARM, RAMDisk Image (gzip), 48964431 bytes, Mon Mar 21 20:09:31 2022, Load Address: 00000000, Entry Point: 00000000, Header CRC: 0X254158BA, Data CRC: 0XCC2EB7BA
boot/vmlinux-5.15.30_1: Linux kernel ARM64 boot executable Image, little-endian, 4K pages
```
I'll transfer it to my sdcard once more and check if its bootable.
Edit: Still doesn't boot. I'll keep investigating.
Edit2: The `dtb` files are differing, just as the kernel configs. The `Armbian` file is a lot bigger.
```sh
file *rockpro64* # Armbian
rk3399-rockpro64-v2.dtb: Device Tree Blob version 17, size=78191, boot CPU=0, string block size=6679, DT structure block size=71456
rk3399-rockpro64.dtb: Device Tree Blob version 17, size=78191, boot CPU=0, string block size=6679, DT structure block size=71456
file boot/dtbs/dtbs-5.15.30_1/rockchip/*rockpro* # Void Linux
boot/dtbs/dtbs-5.15.30_1/rockchip/rk3399-rockpro64-v2.dtb: Device Tree Blob version 17, size=58656, boot CPU=0, string block size=3036, DT structure block size=55564
boot/dtbs/dtbs-5.15.30_1/rockchip/rk3399-rockpro64.dtb: Device Tree Blob version 17, size=58656, boot CPU=0, string block size=3036, DT structure block size=55564
```
Edit3: I'm sure the issue is somewhere in the boot area, but I'm running in circles right now. Maybe someone can chime in.
Edit4: Realized the initrams is not `arm64` but `arm` as per this line:
https://github.com/void-linux/void-mklive/blob/master/mkplatformfs.sh.in#L206 (needs to be replaced by `arm64`).
New initrams should be fine now:
```sh
file sdc/boot/*
sdc/boot/config-5.15.30_1: Linux make config build file, ASCII text
sdc/boot/dtbs: directory
sdc/boot/initramfs-5.15.30_1.img: gzip compressed data, max compression, from Unix, original size modulo 2^32 69921792
sdc/boot/initrd: gzip compressed data, max compression, from Unix, original size modulo 2^32 69921792
sdc/boot/uInitrd: u-boot legacy uImage, Void Linux, Linux/ARM 64-bit, RAMDisk Image (gzip), 48965024 bytes, Mon Mar 21 20:53:35 2022, Load Address: 00000000, Entry Point: 00000000, Header CRC: 0XF427FD20, Data CRC: 0XCBFFDDF3
sdc/boot/vmlinux-5.15.30_1: Linux kernel ARM64 boot executable Image, little-endian, 4K pages
```
Edit5: Still not booting. Giving up for now.
next prev parent reply other threads:[~2022-03-21 21:04 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 5:44 [PR PATCH] " tiemenwerkman
2021-10-15 21:53 ` CameronNemo
2021-10-24 13:54 ` tsndqst
2022-03-04 4:59 ` Anachron
2022-03-17 6:55 ` Anachron
2022-03-17 6:55 ` Anachron
2022-03-17 6:56 ` Anachron
2022-03-17 9:14 ` Anachron
2022-03-17 9:18 ` Anachron
2022-03-17 9:52 ` Anachron
2022-03-17 14:58 ` Anachron
2022-03-18 20:23 ` Anachron
2022-03-18 20:24 ` Anachron
2022-03-18 20:52 ` tsndqst
2022-03-18 20:53 ` tsndqst
2022-03-18 21:07 ` Anachron
2022-03-18 22:38 ` tsndqst
2022-03-21 13:09 ` Anachron
2022-03-21 15:34 ` Anachron
2022-03-21 20:02 ` Anachron
2022-03-21 20:15 ` Anachron
2022-03-21 20:26 ` Anachron
2022-03-21 20:34 ` Anachron
2022-03-21 20:42 ` Anachron
2022-03-21 20:43 ` Anachron
2022-03-21 20:46 ` Anachron
2022-03-21 21:01 ` Anachron
2022-03-21 21:04 ` Anachron [this message]
2022-03-22 1:17 ` tsndqst
2022-03-22 2:48 ` zen0bit
2022-03-22 6:30 ` Anachron
2022-03-22 6:31 ` Anachron
2022-03-22 7:25 ` Anachron
2022-03-22 7:40 ` Anachron
2022-03-22 7:46 ` Anachron
2022-03-22 9:12 ` Anachron
2022-03-22 20:35 ` CameronNemo
2022-03-22 20:36 ` CameronNemo
2022-03-22 21:02 ` Anachron
2022-03-23 12:22 ` Anachron
2022-03-23 17:25 ` Anachron
2022-03-25 13:00 ` [PR REVIEW] " tsndqst
2022-03-25 20:45 ` CameronNemo
2022-03-25 20:55 ` Anachron
2022-03-25 21:06 ` tsndqst
2022-04-10 5:45 ` Anachron
2022-04-10 5:48 ` Anachron
2022-04-10 5:53 ` Anachron
2022-07-10 2:14 ` github-actions
2022-07-25 2:14 ` [PR PATCH] [Closed]: " github-actions
2022-03-30 11:34 [PR PATCH] " tsndqst
2022-04-10 5:50 ` Anachron
2022-05-12 15:43 ` Anachron
2022-08-06 16:34 ` geekboy01
2022-08-08 7:24 ` Anachron
2022-08-08 22:03 ` geekboy01
2022-08-10 2:36 ` geekboy01
2022-11-09 2:13 ` github-actions
2022-11-13 21:41 ` geekboy01
2022-11-13 22:06 ` Anachron
2023-02-13 2:01 ` github-actions
2023-02-13 4:37 ` zen0bit
2023-02-13 14:38 ` geekboy01
2023-05-16 1:54 ` github-actions
2023-05-16 7:07 ` Anachron
2023-08-16 1:44 ` github-actions
2023-08-16 4:11 ` geekboy01
2023-11-15 1:46 ` github-actions
2023-11-15 1:55 ` geekboy01
2023-12-03 17:03 ` Anachron
2023-12-03 18:29 ` tsndqst
2023-12-03 18:32 ` tsndqst
2023-12-03 18:42 ` classabbyamp
2023-12-03 18:48 ` tsndqst
2023-12-03 18:49 ` classabbyamp
2023-12-03 18:49 ` classabbyamp
2023-12-03 18:50 ` classabbyamp
2023-12-03 19:24 ` tsndqst
2023-12-04 20:45 ` tsndqst
2024-05-01 1:47 ` github-actions
2024-07-23 14:34 ` classabbyamp
2024-07-23 16:06 ` Anachron
2024-07-23 16:39 ` tsndqst
2024-08-06 7:20 ` Anachron
2024-08-06 12:29 ` Anachron
2024-08-06 12:38 ` tsndqst
2024-08-06 12:55 ` Anachron
2024-08-06 13:07 ` tsndqst
2024-08-06 13:28 ` tsndqst
2024-08-06 19:15 ` classabbyamp
2024-08-06 20:43 ` Anachron
2024-08-06 21:09 ` tsndqst
2024-09-30 15:23 ` Anachron
2024-09-30 15:28 ` tsndqst
2024-09-30 16:03 ` Anachron
2024-09-30 16:29 ` Anachron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220321210453.RUc3H7aI8drYnEAb2agKRb0fLxJIZ1ZeujZHhzmzceg@z \
--to=anachron@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).