-
-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Questions and Bugs #56
Comments
I'll investigate. In the mean time you can also build using make commands Is it actually producing an img? If so this may just be a dialog error. |
Thanks for a prompt response. But that file date is too early for it to be my RT build and I would have expected to see RT in the file name |
So I might start again with: |
Nah. It is just telling you the rootfs tarball is already there. I have the builder setup, so if it finds the tarball, it skips the build process. Since it is time and bandwidth consuming. If you wanna really purge everything, you need to remove the tarball ur self. |
NOw its really crazy. when I say purge all, it starts to build the kernel! |
Recloned. Here is another bug. MENUCONFIG="1"01 |
Cloned again so Brand new RT patch from kernel.org in userpatches |
Yes, looks good to me. |
Thanks, building now. The patches seemed to be applied and menuconfig came up. The dialog actually caught me out every time so I check it in a text editor to get it right. |
I'm thinking that menuconfig bit might have something to do with this piece of code.
It doesn't know what you entered and is just putting quotes around what it is looking for. |
It actually flagged it as invalid data and said it was ignoring it. First time through, I had no idea what that meant :) |
I just saw what you wrote. And I'm not sure how Craziness. I even tried to make it happen, which shouldn't work and didn't. |
Yes, I think by then, it was totally screwed! I must have broken it.... |
Hmm, |
OK, must all be lower case..I didn't know that. So I changed the userdata.txt to my name and reran |
That is interesting, I also didn't know this. I normally don't get complicated with my user information though. This worked fine for me.
Last I checked the only variable you really need to be careful with here is NAME="". GOOD
FAIL
It doesn't like blank spaces. |
Thanks I finally got success! I set name = user = password = cnc |
That wasn't it. There is a FAT16 Boot partition mmcblk0p1 |
I no longer own a Pi4, but I wonder if me turning off LBA has in some way created an issue? Let us check and see. You'll need a Linux box for this. Put the SD in the CARD reader and plug it in to ur linux box. Now find the /dev/$node and run: Example:
You can check and make sure if you like.
|
Hmm. Apparently this is an issue; https://forums.raspberrypi.com/viewtopic.php?t=278295 I'll investigate. Thanx for the report. |
This should fix the following issue. #56 https://forums.raspberrypi.com/viewtopic.php?t=278295 Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
Sorry about all that. This should resolve it: f3f48ad |
A very interesting article even if its annoying! I might try your LBA tweak, then erase the MBR this way |
Thanks. Just going to bed. so will try tomorrow night. |
Required: Raspberry Pi 4 pyavitz/rpi-img-builder#56 https://forums.raspberrypi.com/viewtopic.php?t=278295 Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
It worked! |
I only ran a basic test, but looks right?
|
Sorted. Missing a " in lib/boards. I must have done that before you suggested function0 and deleted too much! |
Great, Still building function2 here but far enough along to see that cmdline.txt is perfect! |
WHere should this go? I don't think it stuck. I had it in function2
Hmm, it was not commented out. Do you need to do it on the pi? (works there) |
If you have it in Try:
If for some reason that doesn't work, comment out the lines in stage2.
That should be it? |
I'll see how I go. I am rebuilding without the sudo. I might leave it to the user to decide how he wants to do sudo.. Main thing I want to get sorted is to get more cores building the Linuxcnc debs. They are masssive! I have had one go at it a while ago and it errored. Hoping this will add another 15 threads into play to the build (-j'nproc' failed) The last image I built failed to boot. Maybe becasue I did not purge-all, so trying again with a clean purge-all |
Might be easier to build the debs native on one of the units and then install the required depends and pre-built debs inside the chroot of the builder. Personally, I find building native is faster inside the chroot. But I don't have any x86_64's with that many threads. :) Yes, it is easy for things to go wrong sometimes. |
Hi again. There is one thing I don't understand is how to create a defconfig. On a normal kernel build it seems this is done with make savedefconfig. Does CUSTOM_DEFCONFIG save the defconfig? There is no mention of it being saved in the docs. I've had a wierd data corruption here with a 699 byte userdata.txt file that showed no data in the file. That has held me up for a few days but a couple of other linuxcnc users are working with this too. Finally burning what I hope is a good image again right now! It would be good to be able to lock in the defconfig settings. |
Grr, my build failed again, going to try one someone els has built. Also, does COMPRESS_IMG compress the image? My image is 6.4 gb and my mates is 2 gb for the same thing! |
Yes, it compresses the img to an img.xz so it can be easily uploaded or transferred. As for the defconfig, it looks like I didn't add the save to output/$BOARD directory yet. I'll add the feature and fix the ccache compiles today or tomorrow. |
This commit significantly improves ccache support. bananapicm4: tmp $ ccache -s Cacheable calls: 35430 / 41386 (85.61%) Hits: 15902 / 35430 (44.88%) Direct: 15686 / 15902 (98.64%) Preprocessed: 216 / 15902 ( 1.36%) Misses: 19528 / 35430 (55.12%) Uncacheable calls: 5956 / 41386 (14.39%) Local storage: Cache size (GB): 0.29 / 5.00 ( 5.82%) Cleanups: 16 This helps kernel builds on the 2nd go around finish in minutes or seconds depending on the HOST machine. Compiler bits moved to: lib/function/compilers Added depends: gcc-$VERSION-plugin-dev If menuconfig is enabled your defconfig with be saved in the output directory. bananapicm4: tmp $ ls -ls output/bcm2711 total 55656 224 -rw-r--r-- 1 root root 229029 Sep 5 12:16 bcm2711-config_defconfig 40 -rw-r--r-- 1 root root 39258 Sep 5 12:16 bcm2711_defconfig 12316 -rw-r--r-- 1 root root 12608436 Sep 5 12:28 linux-headers-bcm2711-rpi-4_6.1.51-1_arm64.deb 43076 -rw-r--r-- 1 root root 44108380 Sep 5 12:28 linux-image-bcm2711-rpi-4_6.1.51-1_arm64.deb Issue: #56 Builder: 5.6 Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
Thanks for the new commit. Sounds like it will be a great enhancement. Thanks again for working with me. |
One more question. my stage2 script builds the linuxcnc debs in /tmp and installs them. How can I save them into the output directory? I thought it was outside of the chroot. That is the most logical place to put them. |
I tend to neglect this builder, as I also have another one, which is where most of my focus goes. But yes, you have found a couple bugs I wasn't aware of, which I appreciate and have prompted me to back port features from the other builder into this one.
Technically, you could copy them out before the img is unmounted using the stage1 script. Super generic way to do it.
|
Thanks, I have worked with Armbian, with limited sucess with the RT kernel even with the help of an Armbian RT guy. Should we use the other builder for the Pi? I tackled this specific board becasue Linuxcnc has an existing but quite broken 32 bit Pi image. PS I have another builder too. For linuxcnc on X86 hardware. Its a lot easier as there is buildbot for all the debs. I need to finish this one and get back to it. |
I don't use RT kernels, but with the other builder, it should be a lot easier to get that compiled. I focus most of my attention on Amlogic and the current AML patch set I'm using seems pretty solid. At least on a headless level... I don't mess around with GUI's on ARM all that much. As for Pis and that builder. No, not really. Any personal Pi builds I create for my self, I use this builder as the other one is primarily mainline centric. |
Back at it again. Is there anything I need to do to enable caching on future runs? |
looks like rpi-commit is opening the wrong folder. Should be the commit number. |
#56 Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
Thanks, that seems to be working now thanks. I will say I'm easilly confused tonight. A friend who is building with this flat out calls himself Cornholio on our forum and you are C0rnelius on your emails. I think I should just call myself Confused :) |
Why would you want too? All that does is save the defconfig(s) to output/$BOARD dir and give you the option to continue on or quit. If you actually wanna use the defconfig in future builds going forward you need to enable it in the userdata file and put the defconfig in the defconfig dir. |
Is this a Stage 1 function?
The ultimate goal is to have a fully automated process. Once we have run menuconfig once and created a custom defconfig (saved in my repo), we don't need to touch anything . |
Don't worry about the automated build. It does what I want now. I will try using stage1 scripts. I finally get the difference in file paths between the stages :) |
OK. So you run Now edit the userdata.txt file ### CUSTOM
CUSTOM_DEFCONFIG="1"
MYCONFIG="bcm2711_defconfig" NOTICE: The file must end in |
As an aside you can also ask questions or report bugs on IRC or Discord. Libera; #arm-img-builder |
When building the installer on Bookworm X86 host, I got this silly error which displays in a window
Building for a Pi 4b 64 bit
The file displayed exists in the root folder complete with the
--
prefixFirst encountered doing a
make all
from make menuReran again to build a patched preempt_rt kernel (no other changes except adding a patch and changing menuconfig to fully preemptible kernel) and it happened again. I noticed the kernel was built so I tried selecting make bootable file system and the error was immediately displayed again.
Deleted the file and the error persisted.
I don't know how to debug make here. Help would be appreciated.
The text was updated successfully, but these errors were encountered: