Jump to content

Igor

Administrators
  • Posts

    14295
  • Joined

  • Last visited

Everything posted by Igor

  1. Remind me. Does WiFi works in image from download section? https://www.armbian.com/download/?device_support=Standard support This (EDGE kernels) raises support costs into the sky and since from open source developers position 99.5% costs are not yours ... use current kernel. Its a huge difference between those two, one has been stabilized, the other not, probably next year, most likely never and will be replaced with next EDGE, 6.14.y with stabilization attempt in more then one year from now. Also legacy 6.6.y would be better for this job. Higher number doesn't mean better functionality and less bugs, often right the opposite. Try this way: sudo ip link set wlan0 up sudo iw dev wlan0 scan
  2. If this is improvement as described, please provide a PR to configs: https://github.com/armbian/build/blob/main/config/kernel/linux-meson64-current.config https://github.com/armbian/build/blob/main/config/kernel/linux-meson64-edge.config Thank you!
  3. Bug in NetPlan / systemd-networkd or bug in Armbian implementation? We have no options to maintain NetPlan or any other similar complex user space component. Armbian uses Ubuntu / Debian packages without changes as we are focused into Kernel space, framework, tools, build automation. If there is a workaround, we can push it somewhere. Like this one: https://github.com/armbian/build/commit/7f32a5853513745ee6aa55b6d3856ac67ec036e2 Forum is just fine. Armbian itself don't have resources to touch any of this, but someone might know something and help you / everyone. I briefly understand what is the problem, but no idea how to solve it.
  4. Armbian is assembled from Ubuntu or Debian packages. If problems is there, problem is here too and there is little we can do about. https://docs.armbian.com/#what-is-armbian We have a mechanism which you can use to insert patched package to our repository, which is in use in some corner cases: https://github.com/armbian/os/wiki Perhaps this is a solution, perhaps not depending on possible dependency nightmare.
  5. First problem was fixed in predicted way. There is no more firmware warnings on upgrade / kernel install. New package is getting to the stable repository in a couple of hours, while it is already present in beta. Agree. While testing kernel, I installed Ubuntu Noble based image and ERROR: Unsupported initramfs version does not manifest there! I suspect this problem is caused by some script that is coming from RaspberryPi OS - on Debian based Armbian, we use userspace and Rpi related firmware packages from RPi OS (which is Bookworm based, so we have great / full packages compatibility). I will try to get to the bottom of this when possible. Basic problem is that in open source and especially in packages assemblies, there are always (tens of) thousands of potentially irritating issues. You noticed this one, we already have a list of many others that needs attention and there is endless list that well always be somewhere ...
  6. Warnings are safe to ignore, happens on other platforms too, but it looks like also error. CONFIG_USB_RTL8152=y -> m should probably do. I will make a config change: https://github.com/armbian/build/pull/8116 I have noticed the initramfs error too, but it doesn't looks it breaks anything. Need to be investigated.
  7. None of those boards are officially supported, so we are not aware on their hw support status. Those are also 32bit architecture, while we only provide 64bit support for Rpi. Did you use Armbian for Rpi? And which particular build? And on which Rpi? There are many unknown things - big difference. Hard to determine the reason from current informations.
  8. Trixie ... let me check and fix this. I only tested Bookworm.
  9. This is around 10 years old (!) demo / beta image that was deprecated cca. 8-9 years ago. If automated builds doesn't work (we can't cover for endless software support for endless ultra-cheap hardware), IMO your best (only) way is digging into https://docs.armbian.com/Developer-Guide_Build-Preparation/ and fixing reasons which are preventing latest kernel / boot loader to work. It might be trivial, it might be hard. Probably nobody knows without research. This will help you http://debug.armbian.de/
  10. This should be fixed, but there might be an error with firmware package. Fix is uninstalling armbian-bsp*, updating all packages, installing bsp againg.
  11. Struggling with repo management for past few days. It would be nice to write it from scratch, but time is an issue
  12. That is wrong approach as we follow kernel source / standards: and this (boot script) contains the mechanism for loading it: https://github.com/armbian/build/blob/main/config/bootscripts/boot-rk35xx.cmd It should work: https://github.com/armbian/build/blob/main/config/bootscripts/boot-rk35xx.cmd#L51-L52 Is your image an upgrade from some old one? As we indeed have issues with this at some point.
  13. We provide mainline based kernels via repository. They are up2date with what exists, but support is not complete and also not tested on this particular hardware.
  14. There is another feature of framework, "armbian-kernel", sections that applies on top of (basic) configs: https://github.com/armbian/build/blob/main/lib/functions/compilation/armbian-kernel.sh#L205-L336 (Docker as example)
  15. Armbian needs user space development too Examples: https://github.com/armbian/configng https://github.com/armbian/apa ... We have to deal with that. There is a lot of automation, infrastructure, ... everything has to be done in order that this machinery works. Ain't just kernel / low level stuff. Not to mention that project also needs (HTML) front-end developers and other profiles. As by the end of the day, that works falls to the people who knows kernel stuff, but if website is broken, kernel fixing has to wait ...
  16. Understand, likewise & most of people that knows this stuff, are very busy. Hardware donation was a thing years ago, today not so much. I can add hw donation (something else) and offer tools: https://forum.armbian.com/crowdfunding/ (example) This can be prepared by anyone and nothing is expected to happen over the night.
  17. Those older devices are patiently waiting for a dedicated enthusiast with plenty of free time and a passion for tinkering. Sadly, the current Armbian maintainers are already stretched to the limit, and expanding our support efforts just isn’t feasible right now. I had a wish, still have, to find and encourage a dedicated person to take a lead on maintaining those old devices (retro Armbian section) as we have to move them out of primary focus in order to survive. Reaching mainline is not enough. Most of our work is dealing with problems that are originating from there. Mainline is just common work, but its often in not very good state. And when problems are found, it takes months before they are fixed. And someday they are not fixed anymore as critical mass of developers, interested in this devices, is just too small or too inexperienced.
  18. tl;dr; It a business support / donation deal between Armbian and SBC maker. We have some budget, we aim on at least positive zero, and we have some people behind those boards. This doesn't mean we will be able to resolve all problems and in real-time as budget is still too small and resources remain limited. Support is better https://docs.armbian.com/User-Guide_Board-Support-Rules/ then on boards without.
  19. The software used by the Orange Pi "team" is, to a very large extent (estimates go as high as 99.9%), based on the work of developers from the Armbian project (and beyond). Their contribution mainly includes adding basic support for new boards, but unfortunately, without further maintenance or long-term support – which practically means that the entire burden of maintenance and support falls on the community. It should be noted that systems such as Orange OS Ubuntu and Debian on ARM architecture are the result of years of work by more than 500 people gathered around the Armbian project. Orange Pi only makes minor adjustments. In the past ten years, we have not seen a single contribution from any member of the Orange Pi team to the development of these key components. Absolutely nothing, while they keep signing under our work (even changed to some degree) ... on top of stealing software support. Which they don't provide in any way. The work of the Orange Pi team (which appears to be just one individual), on top of some old Armbian, can be tracked here: https://github.com/orangepi-xunlong/orangepi-build/commits/next (they removed other board configs)
  20. IIRC this was never integrated but was supported via community initiative:
  21. I assume you have a GitHub account (if not, make it)? Click "Subscribe" on that issue and you will get a notification when its closed down. 4 hours later, still not fixed. No, there is no cheap and quick solution to patch this problem. I would like to see that too.
  22. This is everyone's problem. Buy boards that are supported and maintained. We have not received any support from Orange Pi, contrary, their business model is very damaging to us and donations only pays coffee and beer. We do not maintain or officially support hardware you have, and AFAIK it is not maintained by anyone else - but if it is, it will get to Armbian too. However, given the similarities across these boards and the nature of open source, it’s difficult to prevent Orangepi and their customers (you) from abusing open source development. This is everyone's problem. Stop buying hardware that we don't and won't support as making a pressure to open source developers is worse thing you can do. Hardware dealer abuse is already big enough. Just a polite reminder that you are not a customer, so adjust your over-expectations.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines