Werner
-
Posts
5155 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by Werner
-
Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
-
https://github.com/armbian/community Support status is unknown. May work, may not.
-
Balbes maintains his own fork of the Armbian Build Framework but pushes his changes frequently into Armbian. So for now only his pre-built images are available until next push.
-
Nobody prevents you from using any available kernel in any available userspace by simply building the combination of your choice via our build framework. However there is no guarantee that this will work/boot or even compile properly. https://docs.armbian.com/User-Guide_FAQ/ And it is our choice which prebuilt images we provide for convenience since building and providing those takes lots of computing and storage ressources
-
So you download the wrong image and wonder why it does not work? M4 (non V2 does not have a maintainer attached (feel free to volunteer) and therefore no images are directly provided for download. You can try those from archive: https://fi.mirror.armbian.de/archive/nanopim4/archive/
-
Restoring Orange PI 3 LTS 2GB/8GB EMMC boot partition
Werner replied to Iain Dooley's topic in SD card and PSU issues
Yes but no idea how well they work https://www.armbian.com/orangepi3-lts/ -
We do not provide support for 3rd party images.
-
Rock Pi S Jammy image fails, Bullseye image works
Werner replied to Matthijs Kooijman's topic in Radxa Rock Pi S
Increase verbosity to 7 in your /boot/armbianEnv.txt. Otherwise nobody knows what's going on inside. -
moving to unsupported
-
Maybe @NicoD or @seclorumgets a chance to both confirm the issue and check if the commit fixes it.
-
https://github.com/armbian/build/pull/4296
-
Apologies for the short downtime about an hour ago. Both forums and main website have been relocated to new hardware. You may notice a significant performance improvement, especially in forums. Enjoy
-
Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
-
Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
-
Might (Shot in the dark since nobody of you provided any debug logs) have been fixed: https://github.com/armbian/build/pull/4376 Try building/running an image with this fix.
-
Thanks for reporting
-
For reference: https://github.com/armbian/build/pull/4369#event-7698677956
-
If you mean by installation moving the OS to onboard memory (eMMC) then first write image to and SD card (check docs if necessary) and then use armbian-install (or nand-sata-install on older images) to move OS to eMMC.
-
You are using VERY old firmware. Try using armbian-config to switch to a newer kernel and then retry upgrading the firmware package.
-
Build User Configuration - lib.conf
Werner replied to ALIGMSTEN's topic in Advanced users - Development
Might be an undocumented switch then. However its usage is not recommended since the kernel patchset follows upstream so sooner or later applying the patchset will fail on older branches. -
Build User Configuration - lib.conf
Werner replied to ALIGMSTEN's topic in Advanced users - Development
There is no such switch. https://docs.armbian.com/Developer-Guide_Build-Options/ -
In theory it should perform as the OPi4 LTS with the exemption that a case has been molded around
-
Agree. At the bottom line it is up to the user to decide if a strong password is mandatory or not. A confirmation should do it. Everything else is out of scope for us anyways. Enforcing a strong password also often leads to cause the user to use kind a bare-mininum-working password like qawsed123.