-
Posts
14295 -
Joined
-
Last visited
Other groups
Management
Contributor/Maintainer
Profile Information
-
Gender
Not Telling
-
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
-
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!
-
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.
-
LibVIPS - Can AVIF support be added please?
Igor replied to FrenzyBiscuit's topic in Framework and userspace feature requests
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. -
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 ...
-
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.
-
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.
-
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/
-
Armbian with preinstalled OpenMediaVault (OMV)
Igor replied to Igor's topic in Software, Applications, Userspace
This should be fixed, but there might be an error with firmware package. Fix is uninstalling armbian-bsp*, updating all packages, installing bsp againg. -
Bookworm no longer has a Release file
Igor replied to Rogier's topic in Software, Applications, Userspace
Struggling with repo management for past few days. It would be nice to write it from scratch, but time is an issue -
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.
-
Bookworm no longer has a Release file
Igor replied to Rogier's topic in Software, Applications, Userspace
Was fixed already. -
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.
-
A couple of basic questions on image customization
Igor replied to jgauthier's topic in Software, Applications, Userspace
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)