Re: [ipxe-devel] [ipxe/pipxe] Raspberry Pi 4? (#2)
Hi team,
I finally had some time to sit down and poke at this again.
I went ahead and wiped my old git copy and resynced from scratch just to make
sure there weren't any lingering issues with testing.
I upgraded to GCC 11.1.0 in the meantime, however I still seem to be getting
the infiniband errors I mentioned previously @stappersg as well as another
error, though the build continues after this first error in the "encode" library
Running a standard `make -j16` shows this error, but continues
```
enc/encode.c:1435:20: error: argument 5 of type 'const uint8_t *' {aka 'const
unsigned char *'} declared as a pointer [-Werror=vla-parameter]
1435 | const uint8_t* input_buffer, size_t* encoded_size,
| ~~~^~~~
In file included from enc/encode.c:9:
./include/brotli/encode.h:293:19: note: previously declared as a variable
length array 'const uint8_t[*encoded_size]' {aka 'const unsigned
char[*encoded_size]'}
293 | const uint8_t input_buffer[BROTLI_ARRAY_PARAM(input_size)],
| ~~^~~~
enc/encode.c:1436:14: error: argument 7 of type 'uint8_t *' {aka 'unsigned char
*'} declared as a pointer [-Werror=vla-parameter]
1436 | uint8_t* encoded_buffer) {
| ~^~
In file included from enc/encode.c:9:
./include/brotli/encode.h:295:13: note: previously declared as a variable
length array 'uint8_t[input_size]' {aka 'unsigned char[input_size]'}
295 | uint8_t encoded_buffer[BROTLI_ARRAY_PARAM(*encoded_size)]);
| ^
```
After that it will switch to the bin-arm64-efi ipxe build, before eventually
erroring out with
```
drivers/infiniband/flexboot_nodnic.c: In function 'flexboot_nodnic_create_qp':
drivers/infiniband/flexboot_nodnic.c:368:53: error: implicit conversion from
'enum ib_queue_pair_type' to 'nodnic_queue_pair_type' [-Werror=enum-conversion]
368 | status = nodnic_port_create_qp(>port_priv, qp->type,
| ~~^~
drivers/infiniband/flexboot_nodnic.c: In function 'flexboot_nodnic_destroy_qp':
drivers/infiniband/flexboot_nodnic.c:409:45: error: implicit conversion from
'enum ib_queue_pair_type' to 'nodnic_queue_pair_type' [-Werror=enum-conversion]
409 | nodnic_port_destroy_qp(>port_priv, qp->type,
| ~~^~
```
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/pipxe/issues/2#issuecomment-853112641___
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo/ipxe-devel
Re: [ipxe-devel] [ipxe/pipxe] Raspberry Pi 4? (#2)
@PeterSurda Update! It took some finesseing to get it to work on my build box (Gentoo needed the `iasl` package for those relevant files) I ran into an ipxe build error with some junk relating to "infiniband" (possibly an issue with using GCC 10.2?) but commenting that out fixed it Embedding my boot script seemed to work as well. It pulls down a kernel + initrd and (attempts) to boot them However it now hangs at `EFI stub: Booting Linux Kernel...` `EFI stub: Generating empty DTB` `EFI stub: generating boot services and installing virtual address map...` But I know that's (probably) outside the scope of iPXE and likely a kernel configuration issue on my side Thank you very much for all your help however :) Hopefully this thread helps others in future too -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/ipxe/pipxe/issues/2#issuecomment-813004102___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo/ipxe-devel
Re: [ipxe-devel] [ipxe/pipxe] Raspberry Pi 4? (#2)
I will give this a try in a few days and report back, thank you @PeterSurda! -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/ipxe/pipxe/issues/2#issuecomment-809059667___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo/ipxe-devel
Re: [ipxe-devel] [ipxe/pipxe] Raspberry Pi 4? (#2)
Additional: While I was writing the above comment. My Pi 4 booted, gave a "net0 no such network device" error. Looped through the "Start PXE over IPv4" and then IPv6 And then actually found net0 and attempted to boot! Could this perhaps be a bug in either iPXE or the UEFI firmware I'm using? -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/ipxe/pipxe/issues/2#issuecomment-806958701___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo/ipxe-devel
Re: [ipxe-devel] [ipxe/pipxe] Raspberry Pi 4? (#2)
Apologies for the necro-post. But this was one of the first results in Google I've been tearing my hair out for several hours now trying to get a scripted iPXE to boot on my Raspberry Pi 4. I've tried using both the iPXE upstream, as well as the version 1.20.1 build that @rgl's repository provides No matter what version I build, executing a `make bin-arm64-efi/ipxe.efi EMBED=myscript.ipxe` or even building without the script builds a binary that boots, but then does not show any ethernet devices :( I've got the latest EFI 1.24 firmware running, and have also tried 1.16 and 1.17 due to at least one thread noting that it may have errors netbooting I've found a few pre-made iPXE binaries that do already work, but I want to embed a script in to mine for HTTP booting Is `make bin-arm64-efi/ipxe.efi` still the correct build command for the Raspberry Pi 4? Or am I missing some step somewhere -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/ipxe/pipxe/issues/2#issuecomment-806956094___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo/ipxe-devel
