Jump to content

rpardini

  • Posts

    45
  • Joined

  • Last visited

Other groups

Profile Information

  • Gender
    Male
  • Location
    Amsterdam

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. rpardini

    Odroid M1

    This is most probably a bug on my side. I build with all repos and mirrors disabled (SKIP_ARMBIAN_REPO=yes) so everything is built locally, but clearly I've a bug when you don't have that option. Try with it and let me know... meanwhile I'll try to find and fix the bug.
  2. rpardini

    Odroid M1

    Hi Nexus. It seems you're trying to build on arm64, but my code is using the u-boot + rkbins from HardKernel, which unfortunately only work on x86 / amd64. Also, you're better off building from "armbian/build" branch "armbian-next' instead of my "extensions" branch, which is very (very!) volatile.
  3. Rock 5b test images, from armbian-next. Using vendor u-boot + patches, and vendor kernel, both straight from radxa's git XFCE desktop with "browsers" app group - https://github.com/rpardini/armbian-release/releases/download/20220710b/Armbian_20220710b-rpardini_Rock-5b_jammy_legacy_5.10.66_xfce_desktop.img.xz CLI - https://github.com/rpardini/armbian-release/releases/download/20220710b/Armbian_20220710b-rpardini_Rock-5b_jammy_legacy_5.10.66.img.xz PR: https://github.com/armbian/build/pull/3984 (against master) All work by @amazingfate I just gathered stuff and built images. Thanks to @monkaBlyat @lanefu @piter75 @amazingfate for tests / patches etc
  4. Nope, can't confirm... mentioned image no longer exists... And the VIM3L is hard at work, testing the 5.19-rcX builds!
  5. Yes. GitHub Actions workflow is setup to run everyday at 3am UTC. https://github.com/rpardini/armbian-git-shallow/blob/main/.github/workflows/main-latest.yml#L6 If you look at the GHA logs it is already working, everytime I push a commit but also everyday at 3am by itself: https://github.com/rpardini/armbian-git-shallow/actions 👍 ----- Apart from that, I am still investigating some vendor kernels (HardKernel, but also others) specially in 4.19 series, if I pre-seed the local copy with linux 4.19 shallow bundle, and then pull from that vendor's kernel tree, it comes down a lot (1.5Gb). I suspect that is because the vendor started his kernel Git from somewhere _way_ before 4.19-rc1, and there is a mismatch during git negotiation for the fetch, and ends up pulling a lot. @going I think you also regularly pull from "megous" repository that would be interesting to test too. ------ Another possible problem are developers/users in China which can't get to github.com for downloads. For this case we could publish, in addition to GH Releases, also to some other FTP or rsync that we already have @Igor?
  6. The reference for why this was written: https://github.com/armbian/build/pull/3476#issuecomment-1042063299 (mricon is from the Linux Foundation, who appeared after our CI was banned from kernel.org due to too much shallow fetching) Also https://github.com/armbian/build/pull/3476#issuecomment-1042322996
  7. Thanks for the attention guys. I guess I did not explain this correctly... The shallow_kernel_tree.sh script is run on GitHub Actions (not any user machine, ever), it downloads a lot of stuff (including a 2.4GB bundle, indeed), updates it, massages it into shallow, and publishes the output. The output is here: https://github.com/rpardini/armbian-git-shallow/releases/tag/latest Each kernel version gets a shallow bundle (file) around 250mb each. That output would then (later) be used by armbian/build to seed a kernel tree, downloading from GH CDNs via HTTPS, instead of pulling everything from kernel.org's (or mirrors) git server. After seeding, pulling from the git server is very fast / small download (a few megabytes). That way people or CI servers building Armbian will only download those 250mb + a few. Combining all this allows us to have a small, shallow git tree, that has the tags we need, and can be kept updated cheaply, without ever fetching/cloning it using shallow, and thus does not put any load on the git server.
  8. Hello, I've finally gotten around to writing the GitHub Actions based Linux Kernel Shallow git trees exporter. It's very simple, a single shell script and GHA workflow. It prepares shallow bundle (and ready-to-go .tar too) everyday on a schedule and publishes to GitHub Releases. Please take a look https://github.com/rpardini/armbian-git-shallow - theres a README that shows how to use the bundles outside of Armbian. If this is a good idea, I'd move it to armbian/kernel-git-shallow in GitHub. And then I'd start using those in armbian-next first as a test ground. I mention I few people I know are interested in the subject @Igor and @going but of course everyone welcome to pitch in Thanks (PS: No idea why I'm required to tag a board for this post)
  9. rpardini

    Odroid M1

    Ok here's a new version, 5.18-rc7 from tobetter's tree. Still very early days. tobetter is doing a fantastic job this time around, keeping his tree rebased properly this time. This version has working NVMe (!), panfrost somewhat works, some hangs when panfrost is used. eMMC does NOT work in my experience, it hangs the machine if trying to use it. use SD card. unzstd, burn to SD, boot either with or without holding the button. (it should NOT go into or through Petitboot either way, instead the SPL in SPI should find and boot uboot in the SD card, or with button boot all blobs from SD). https://github.com/rpardini/armbian-release/releases/download/20220522c/Armbian_20220522c-rpardini_Odroidm1_jammy_edge_5.18.0.img.zst (4.x stuff still does not have HDMI, I've no idea why, it's otherwise stable, but I won't post it here since most people just assume it does not work at all if HDMI does not work)
  10. rpardini

    rpardini

  11. @Excel I've an image. Unofficial. Unsupported. unzstd it, burn it to SD, put jumper J3 in Maskrom mode, UART at 1500000. https://github.com/rpardini/armbian-release/releases/download/20220522c/Armbian_20220522c-rpardini_Tinkerboard_jammy_edge_5.17.9.img.zst (WRONG! That is for the TB1!) UPDATE: https://github.com/rpardini/armbian-release/releases/download/20220522c/Armbian_20220522c-rpardini_Tinkerboard-2_jammy_edge_5.17.9.img.zst (correct for the TB2) Good luck! Sorry boss, I've all these images laying around and can't help myself. 😉
  12. rpardini

    Odroid M1

    Cool stuff, thanks for the explanation. I've similar setup, although I don't use root LVM, and cloud-init meta is in /boot ext4 or /boot/efi (vfat). Partitioning is quite complex intermingled code between partitioning proper, calculating sizes, and setting up filesystems. I've added hooks to be able to "override it all" but haven't had time to make it better composable, much less in bash. But what I was asking about was the your original mention of "docker-shell" or something, for image build? kernel build? I've probably messed that up in -next.
  13. rpardini

    Odroid M1

    Thanks for testing, I'll test some future build and report back when I'm confident it boots. I messed up some (unrelated to M1) initrd stuff in those builds.
  14. rpardini

    Odroid M1

    Eh, no idea. Fragments of code handling docker are scattered all over the codebase, and haven't been properly handled yet in armbian-next. (1-line explanation: armbian-next has error control enabled, and command invocations that previously failed and were ignored now make the build stop). Would be great if you could explain the use case for what you're trying to do...
  15. rpardini

    Odroid M1

    Should be doable, patch dirs are empty so just drop stuff in there. legacy == 4.19 from HK official repo. edge == 5.18-rcX from tobetter's repo. both with vendor u-boot so all moving targets, tobetter has finally taken to rebasing his branch.
×
×
  • Create New...