[15:09:57] jybz I have spent hours trying to run create_arm_image.sh but it refuses to accept a config file irrespective of where it is put, with or without full path, allowing it to move the template into platforms and edit it etc. etc. Is it just broken or is it me. I give up (again) for now :( [00:00:00] - {Day changed to Friday, 8 September 2023} [00:00:00] - {Day changed to Saturday, 9 September 2023} [08:51:07] Hi barjac, I've tuned a cauldron iso (then it boots) and run mageia4arm on it in order to regenerate an iso. [08:51:24] I wasn't able to properly build the initrd on my x86 [08:51:37] Let me share the resulting file [08:53:42] barjac: http://mageianana.freeboxos.fr:50222/ [00:00:00] - {Day changed to Sunday, 10 September 2023} [07:53:35] barjac: got it ? [10:46:11] jybz: Downloading now - thanks! Will test in my RPi4b shortly :) [11:08:42] jybz: Boot fails and drops to grub prompt with no keyboard. http://mtf.duckdns.org/pub/linux/barjac/test/photo_2023-09-10_11-04-02.jpg [11:21:14] jybz: There is an EFI directory in the boot partition but there is no separate EFI system partition which I guess is what it's complaining about? [11:36:40] jybz: Out of curiosity I added an empty 300M 'EFI System' partition in the free space hoping that the error message may change but it did not. [12:02:00] jybz: Also tested card in RPi3b with same output :( [12:19:08] what ?! [12:20:34] There is an efi partition [12:24:05] jybz: Nope! [12:26:02] I used the tar.gz not the .img download (and extracted it locally of course ;) [12:26:24] [jybz@jeeebztop mageia4arm (master)]$ cp /run/media/jybz/mga4arm/build/Mageia-9-rpi-aarch64-noDE.img ~/tmp/ [12:26:28] [jybz@jeeebztop mageia4arm (master)]$ udisksctl loop-setup --file ~/tmp/Mageia-9-rpi-aarch64-noDE.img [12:26:32] Mapped file /home/jybz/tmp/Mageia-9-rpi-aarch64-noDE.img as /dev/loop2. [12:26:37] [jybz@jeeebztop mageia4arm (master)]$ udisksctl mount --block-device /dev/loop2 [12:26:45] /dev/loop2 /dev/loop2p1 /dev/loop2p2 [12:26:49] [jybz@jeeebztop mageia4arm (master)]$ udisksctl mount --block-device /dev/loop2 [12:27:20] There is two partition, the loop2p1 (the efi) and loop2p2 (the root) [12:28:26] Device Boot Start End Sectors Size Id Type [12:28:26] /dev/sdg1 * 2048 264191 262144 128M c W95 FAT32 (LBA) [12:28:26] /dev/sdg2 264192 6291455 6027264 2.9G 83 Linux [12:28:26] /dev/sdg3 6291456 6905855 614400 300M 83 Linux [12:28:26] [baz@localhost ~]$sdg3 is the test one I added [12:28:51] sdg1 is the efi partition [12:29:13] Maybe it does not has the esp flag [12:30:11] It's not of type 'EFI System' - generally it has to be but OK I beleive you, [12:30:54] EFI system type is just (IIRC) just the esp flag. I will try to add the flag next time [12:31:04] But this is very strange [12:31:13] I will remove the one I added and change the type of the boot partition to see if it helps. [12:31:23] I made this image from an Rpi4B [12:31:51] and it is written that the elf (executable) is NOT for an Rpi4B architecture [12:34:17] (and I use this image :s) [12:34:45] barjac: can you break the boot by pressing any key while uboot ? [12:35:31] (during "hit any key to stop autoboot: 2" ) [12:35:46] I would like to know if usb is working at that stage [12:37:58] No it did not stop it. [12:39:25] unbelievable... [12:40:48] Can you mount the sd card then doing a md5sum /run/media/jybz/1E59-29B5/bcm2711-rpi-4-b.dtb [12:40:52] 382a44150bbeebdff6e25276be78250c /run/media/jybz/1E59-29B5/bcm2711-rpi-4-b.dtb [12:43:22] Not valid now as I converted the card to gpt and changed the boot partition to 'EFI System', but the error message has now changed - getting further than before. Let me take a photo. [12:44:33] You can still do the md5sum of the dtb file [12:47:35] Oh OK yes - sorry see new image in same folder as last one. [12:49:06] https://upload.disroot.org/r/fbKbk8ac#Kttl4w2VW75/rxfdK2ljMcy2oX7AiN+SH08oc1ET2PU= [12:49:59] barjac: you mean, you put on the card the official image from Mga ? [12:52:23] jybz: No the one from that link you gave from the tar.gz unless that held a different .img from the one that was in the same directory? [12:53:22] I assumed that they were both the same. Just one was in a tarball? [12:53:37] Faster downmload. [12:53:44] Yes exactly [12:54:00] either downloading 1,1GB or downloading 3.0GB [12:54:07] Yes [12:54:26] Did you check the dtb checksum ? [12:55:45] Ah well now I changed to gpt there is only one partition, and I did not find it yet. Hang on. [12:57:24] No there are two: [12:57:28] [baz@localhost ~]$ sudo gdisk /dev/sdg [12:57:28] GPT fdisk (gdisk) version 1.0.9 [12:57:28] Partition table scan: [12:57:28] MBR: protective [12:57:28] BSD: not present [12:57:28] APM: not present [12:57:28] GPT: present [12:57:28] Found valid GPT with protective MBR; using GPT. [12:57:28] Command (? for help): i [12:57:28] Partition number (1-2): 2 [12:57:28] Partition GUID code: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (Linux filesystem) [12:57:28] Partition unique GUID: AAB21263-5803-4CE8-862C-377F6BED90D1 [12:57:28] First sector: 264192 (at 129.0 MiB) [12:57:28] Last sector: 6291455 (at 3.0 GiB) [12:57:28] Partition size: 6027264 sectors (2.9 GiB) [12:57:28] Attribute flags: 0000000000000000 [12:57:28] Partition name: 'Linux filesystem' [12:57:28] Command (? for help): i [12:57:28] Partition number (1-2): 1 [12:57:28] Partition GUID code: C12A7328-F81F-11D2-BA4B-00A0C93EC93B (EFI system partition) [12:57:28] Partition unique GUID: 3F2F747F-36AE-4C0E-8ABA-04394C62C956 [12:57:28] First sector: 2048 (at 1024.0 KiB) [12:57:28] Last sector: 264191 (at 129.0 MiB) [12:57:28] Partition size: 262144 sectors (128.0 MiB) [12:57:28] Attribute flags: 0000000000000000 [12:57:28] Partition name: 'EFI system partition' [13:02:19] 382a44150bbeebdff6e25276be78250c bcm2711-rpi-4-b.dtb [13:02:39] jybz: ^^ [13:03:07] :'5 [13:03:11] :'( [13:03:19] What's wrong with rpis... [13:03:39] then, the dtb is correct, the usb should work. [13:05:43] jybz: If you look into raspbian sources you will see dozens of patches that have rpi in the name - beyond my comprehension sadly. [13:06:12] did you see the 2nd photo I took? [13:07:11] http://mtf.duckdns.org/pub/linux/barjac/test/photo_2023-09-10_12-45-13.jpg [13:09:17] oh... since you set it efi, it tries to read ubootefi.var [13:09:18] There are of course still 2 partitions, but the EFI System partition does not show in dolphin. [13:09:55] it still find the efi/boot/bootaa64.efi grub first stage [13:10:27] then, grub fails because it does not find the partition... I don't know which one [13:10:48] I wonder if this is due to the gpt change, the labels changed [13:11:42] do you have a link to raspbian sources? [13:11:55] (the partition labels changed) [13:12:19] then you might regenerate the grub .efi file. Mission impossible. [13:13:05] jybz: No it was months ago when I was just googling around that I saw all those patches - not sure whwere now. [13:13:42] barjac: how old is you card ? [13:14:09] It's one of the latest from Pi Hut [13:16:46] cat /proc/device-tree/model ; echo '' [13:16:48] Raspberry Pi 4 Model B Rev 1.5 [13:16:57] my bad... [13:17:04] Not possible as long as it does not boot [13:19:54] barjac: it is a 8GB or 4GB ? [13:19:58] https://elinux.org/RPi_HardwareHistory [13:20:11] I could boot into raspbian, but I will need to re-write the card from a backup as I am short of SD cards :( Not a quick process) 8GB [13:21:55] I agree; this is why I'm trying to do smallest images as possible, 3GB is the smallest. [13:22:06] This is due to the non-free wifi driver. [13:22:19] Mageia's package for nonfree driver is really big. [13:22:48] (be back later, i've to cut a pinapple) [13:24:24] jybz: Yes I also have stuff to do so I will go, but later I will re-write it and only change the boot partition type and not the gpt change. Catch you later. [14:30:47] No difference - same 'invalid arch-independent ELF magic' [14:33:17] barjac: it looks like... it is armv7 instead of armv8. I can not imagine something else. [14:33:53] some arm64 is mentionne somewhere ? [15:29:24] It reads efi/boot/bootaa64.efi [15:29:38] See the photo [15:31:44] At that point it had big U-BOOT logo top right of screen. [15:35:27] jybz: ^^ [16:03:41] Maybe if I was to mount the mageia partitions in a chroot in Raspbian and re-install grub2 in the chroot it may get somewhere? Did you have grub2-efi installed in the iso, or grub2? Maybe it should not be using uefi at all? [19:56:11] barjac_: I don't know the uboot logo, because i exclusivly used the UART interface. [19:56:38] yes; sounds like a good idea to reinstall grub from raspbian. [19:57:07] grub2-efi is from mageia, generated with grub2-install [19:57:42] I use efi for multiples advantages : [19:58:47] 1) the bootchain can be static up to the efi from grub2, then mageia handles the update (new kernel; new initrd, update grub2) as for aarch64 as for x86_64. [20:00:29] 2) we don't have to develop mechanism to update rpi firmware of rework the bootchain; nor re-calculate the uncompressed size of the files (kernel+initrd) [20:00:34] if not, uboot fails [20:01:28] Or 3) redevelop thing for modifying the config.txt of raspberrypi. [20:10:35] hi, there. late to the party. are you disscussing the rpi image dev blokade? [00:00:00] - {Day changed to Monday, 11 September 2023}