Re: [Trisquel-devel] Trying to boot Trisquel on rockpro64
Le samedi 01 février 2025 à 06:36 +0100, Denis 'GNUtoo' Carikli a écrit : > First locate the address of the __log_buf symbol inside the kernel: > > $ sudo grep __log_buf boot/System.map-5.15.0-130-generic > > 8423a770 b __log_buf > Thanks for the tip, but where should I find this boot/System.map-5.15.0-130- generic? When I mount the .img file, all what I find there is: drwxr-xr-x 31 root root 1536 déc. 5 03:13 dtbs drwxr-xr-x 2 root root 512 déc. 5 03:13 extlinux -rwxr-xr-x 1 root root 59761301 déc. 5 03:13 initrd.gz -rwxr-xr-x 1 root root 17286526 déc. 5 03:13 vmlinuz drwxr-xr-x 31 root root 1536 déc. 5 03:13 dtbs drwxr-xr-x 2 root root 512 déc. 5 03:13 extlinux -rwxr-xr-x 1 root root 59761301 déc. 5 03:13 initrd.gz -rwxr-xr-x 1 root root 17286526 déc. 5 03:13 vmlinuz The initrd.gz does not include any boot directory. I also looked into the linux-image-5.15.0-130-generic-64k_5.15.0- 130.140+11.0trisquel30_arm64.deb file but I can't find any such file either. So I don't know where to look. -- David Lecompte ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
Re: [Trisquel-devel] Trying to boot Trisquel on rockpro64
On Fri, 31 Jan 2025 18:53:24 +0100 David Lecompte wrote: > I followed the advice at > https://wiki.debian.org/FreedomBox/Hardware/RockPro64 to flash U-boot to the > SPI flash. > > If I try booting the debian installer from > https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images/, (I > dot the concatenation as in the README) it works (I continued to > install Debian on an SSB connected via USB, afterwards, it boots). > > In > https://builds.trisquel.org/debian-installer-images/debian-installer-images_20210731+deb11u12+11.0trisquel18_arm64.tar.gz, > I did the same using similar files found in installer- > arm64/20210731+deb11u12+11/images/netboot/SD-card-images, after > "Starting kernel ...", nothing happens any more. > > I attach the boot logs obtained via serial console. I noticed > differences in addresses at the end, I don't know whether this > reflects a problem or it is just something normal. You could try to get more logs in this way: First locate the address of the __log_buf symbol inside the kernel: > $ sudo grep __log_buf boot/System.map-5.15.0-130-generic > 8423a770 b __log_buf In the above it's on x86, so you'd need to do the same with the ARM Trisquel installation. Then you need to boot the Trisquel installation, and find the reset button on your rockpro64. Press the reset button and in u-boot interrupt the boot with ctrl+c. Once in u-boot you can try to see the kernel logs with the 'md' u-boot command: you need to give it the __log_buf address (here maybe it's 0x8423a770 or 0x8423a770 I'm not sure) and then it will print the 'dmesg' content. And you can then press enter multiple times and it will repeat the last command and this way give you the full log. The log is then not very convenient to read as you get 8 or 16 characters per line but it's better than nothing at all. Also note that I also have a rockpro64 but I use it with Guix. Denis. pgpPVL7vhOCwJ.pgp Description: OpenPGP digital signature ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
[Trisquel-devel] Trying to boot Trisquel on rockpro64
I followed the advice at https://wiki.debian.org/FreedomBox/Hardware/RockPro64 to flash U-boot to the SPI flash. If I try booting the debian installer from https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images/, (I dot the concatenation as in the README) it works (I continued to install Debian on an SSB connected via USB, afterwards, it boots). In https://builds.trisquel.org/debian-installer-images/debian-installer-images_20210731+deb11u12+11.0trisquel18_arm64.tar.gz, I did the same using similar files found in installer- arm64/20210731+deb11u12+11/images/netboot/SD-card-images, after "Starting kernel ...", nothing happens any more. I attach the boot logs obtained via serial console. I noticed differences in addresses at the end, I don't know whether this reflects a problem or it is just something normal. logs.tar.gz Description: application/compressed-tar ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
