Igor

Yes. If you are in NA and you will point to https://apt.armbian.com, our system will anyway serve you closest mirror out of those. We have improved and refactor this system quite a lot since. Its open source and your are welcome to peek into the code and understand how it works: https://github.com/armbian/armbian-router

Release Candidate Code Freeze Date: 2022-11-16 Release Planning Meeting Date: skipped, forum only - post concerns to this topic Release Date: 2022-11-28 2022-12-03 Release Coordinator: Igor Board maintainers @Contributor/Maintainer please check status of your board. Report a bug or try to fix it by the final release date. Developers, check if your contribution is recorded in Jira as otherwise it won't fit into the release log: https://armbian.atlassian.net/projects/AR/versions/10012/tab/release-report-all-issues 64 Issues in version 61 Issues done 0 Issues in progress 3 Issues to do This release should be in bug fix mud as we stay at 5.15.y / 5.19.y for CURRENT kernel branches.

Check this thread. Working for me.

@Presto@tony013 https://github.com/armbian/build/pull/4436 Someone has to verify and approve.

Does fresh image from download section works for you?

Partition type is not relevant as boot process happens outside. Don't know exactly how different is RK3308 from this https://opensource.rock-chips.com/wiki_Boot_option but you get the picture. Are you listening on correct UART? Stock firmware could use a different one. You are clearly having different hardware revision as our test device and this could already be good enough reasons why it doesn't boot. Perhaps modern boot loader does not have support for different memory chips or similar. We can help dealing you with your problem more, when our problems are covered. Since budget for what you are asking here is way less then zero, we can only provide best effort support. If you want to help boosting this hardware support for you, everyone else and our competition, just find a way to finance development. If you want to help, forget about your problem and focus on common problems. List is a bit outdated, because HR staff also wants to eat something.

For at least 6 months at usual location.

Check community rolling releases of armhf arm64 riscv and x86 Armbian Linux images. Fresh from development for testings and meeting with the bleeding edge: https://github.com/armbian/community

Those few Armbian developers that finance your addiction to cheap new hardware has nothing to do with broken PWM fan control. We haven't designed this hardware, we don't sell this hardware, we don't support anything you plug to the machine. It can work or not. If you want that its fixed, we provide you build tool and if you pay, we can find you someone to fix it for you. We can finance bug resolving more then we already do. Its pointless. You don't even say thanks. We already agree with you that better security is not for general population https://armbian.atlassian.net/browse/AR-1385 and there is nothing I can do to fix it faster without your help. Raspi has over million dollar budget for deal with you, we can cover like 5-10% of the costs we have it with you. Show some respect.

I have absolutely no idea.

Sid / Kinetic user land is good enough for hardware that is fresh from the PCB assembly machinery. Stability is defined by components that have nothing to do with Debian (boot loader "bios", kernel and testing of those components). Even legacy kernel is pretty stable, real mainline Linux support with stability Armbian is satisfied is IMO at least a year away. This is how hardware is brought up nowadays ... https://docs.armbian.com/User-Guide_FAQ/ If you need Bullseye / Jammy, you can always build an image for it https://github.com/armbian/build Another option is that you take responsibility dealing with users complains https://docs.armbian.com/Board_Maintainers_Procedures_and_Guidelines/ and stable userland builds can be enabled. Its a long term commitment.

Good evening This image (I assume you tried that) https://redirect.armbian.com/rockpi-s/Bullseye_edge boots on my Rockpi S Logs: https://paste.armbian.com/huvaluwuvi Armbian images are not using vendors proprietary partition arrangements. Most (almost all) our images are single partition. Irrelevant information. "Debian" plays not role here: https://docs.armbian.com/User-Guide_FAQ/ https://www.armbian.com/bugs (console boot log would be extremely helpful) My has it and in that case you need to follow instructions on this page https://www.armbian.com/rockpi-s/ Perhaps your hardware revision is unable to boot modern software? @brentr Any ideas?

There is around 1000 x more ideas, wishes and bugs than resources behind the project. Check that graph below https://armbian.atlassian.net/jira/dashboards/10103 Perhaps that will help you understand. Most of things are not even recorded as recording is already an effort. This is community project 1st and you are welcome to contribute a small part of your time https://docs.armbian.com/Process_Contribute/ an resolve a problem for all of us. I know we made this part, but if you need a quick solution, its on you. Without community help, this giant software project can't be maintained.

I don't understand this request, but if you want to change kernel configuration, they are here https://github.com/armbian/build/tree/master/config/kernel and proceed from here: https://docs.armbian.com/Process_Contribute/

What if you have a problem and I will lost my precious time for nothing? You will cover it? We even got an email today stating: "The no start odroidc2 bug I had with the oct27 release was fixed in the newest November release;" Be a hero and I will check it again. This is the only motive left.

https://www.armbian.com/radxa-zero2/

Fixed. 10x

You want to be on the same network as your LAN? Than you need to create a bridged hotspot.

Understand, but you will need to workaround each time ... He hasn't showed up for a while, but we recreated and tested images last night https://www.armbian.com/pinebook-pro/ (kernel 6.0.6) and they boot normally. From SD and from (some) eMMC. It is Pine64 responsibility to deal with low level problems. Its only our good will if we invest into their business. Do they deserve? https://blog.brixit.nl/why-i-left-pine64/

Link fixed. We only have images here https://github.com/armbian/build/releases for now. When we get more feedback, we'll placed them to expected location and CDN.

Which image exactly did you try from here https://www.armbian.com/rock64/ ?

Start with https://github.com/armbian/build ./compile.sh EXPERT=yes CREATE_PATCHES="yes" When prompted for kernel patch, go to cache/sources/KERNEL_SOURCE_DIR ... and change in the DTS what needs to be changed. Then add a patch to: https://github.com/armbian/build/tree/master/patch/kernel/archive/rockchip64-6.0 and https://github.com/armbian/build/tree/master/patch/kernel/archive/rockchip64-5.19 following by creating a pull request.

Try some older image to see if older u-boot supports your eMMC well. Its also possible of eMMC failure.

This is not supported hw ... Try with fresh image from https://github.com/armbian/community and install armbian-firmware-full package (via armbian-config or by hand) since there are some errors that it couldn't find firmware files. You need to re-flash boot loader.

Another one to try https://raspap.com/