Active threads
Showing topics posted in for the last 365 days.
- Past hour
-
I found an incredibly roundabout way of doing this. ./compile.sh \ kernel \ BOARD=$OPT_ARMBIAN_BOARD \ BRANCH=$OPT_ARMBIAN_KERNEL \ CLEAN_LEVEL=make,alldebs,images,cache \ EXPERT=yes \ PREFER_DOCKER=yes \ KERNEL_GIT=shallow KERNEL_CONFIG=$(find $KERNEL_DIR/cache/sources/linux-kernel-worktree -name .config) if [ ! -f $KERNEL_CONFIG ] then echo "Failed to find .config" exit 1 fi FULL_KERNEL_VERSION=$(cat $KERNEL_CONFIG | grep "Kernel Configuration" | grep -oE '[0-9]+\.[0-9]+\.[0-9]+') if [ "$FULL_KERNEL_VERSION" == "" ] then echo "Failed to get full kernel version." exit 1 fi
-
T95 Max + (Plus) S905x3, 4GB RAM / 32B ROM
Offeacy61 replied to Pita Bread's topic in TV Boxes running Armbian
Thanks for the detailed description! Very useful post, especially for those who are just starting to tinker with Armbian on TV boxes. I had a similar situation with another S905X3 box - neither Wi-Fi nor Bluetooth worked, and there was trouble with HDMI audio. Special thanks for the advice on disabling unattended-upgrades and systemd-networkd-wait-online, I just encountered problems with long loading, now I understand where the legs are growing from. Regarding USB audio - an excellent solution, I didn't even know that it was so easy to bypass the lack of built-in sound. I will try with a similar adapter. If you have a chance, tell me later whether you managed to set up Wi-Fi via a USB adapter or in another way. And I wonder if you tried other window environments besides XFCE? LXQt, for example? In any case - a great guide, thanks for your work! - Today
-
Hi ... thanks for your hint. Actually I forced on the old system sata speed to 3.0 GB ... which I did not on the new installation. Setting also the link speed to 3.0 GB did however not solve the issue, I had to set it down to 1.5 GB. Now the issue seems to be gone. Performancewise it is not noticeable for harddisks, but for the SSD I have it is - need to look further into it. I'm just wondering what (still) the difference is. Forcing link speed down to 1.5 GB was not needed before ... I'm tending to exclude "hardware" as source of issues, as the hardware is in both cases identicial, no single cable touched. CU Alex
-
Description The idea is to introduce the possibility to cache downloads from GH runners to lower downstream bandwidth used and increase overall speed. Especially on machines with lots of runner this could save quite some bandwidth while sacrificing disk space. http caching has been tested and seem to work nicely. https caching is a lot more tricky and may be introduced later. This PR has two parts: set apt repository to http instead of https where possible. Packages are signed anyways. Pass various proxy environment variables to docker so it respects those. Doesn't make sense not to pass them since when using PREFER_DOCKER=no and any of these variables are set beforehand they just work. So this more or less just harmonizes overall behavior. There is still an issue on line 4838 caused by https://github.com/armbian/build/blob/c0da65087aad628ba0714f23d8d29800f152d97c/lib/functions/rootfs/apt-install.sh#L67 due to absence of apt proxy setting there. Not sure why this is not added here? How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] build random image: https://paste.armbian.de/xopitiguyo , look for 10.100.0.87 to see where it is used [x] built the same random image but having all proxy env variables unset beforehand: builds just fine as well: https://paste.armbian.de/ozidivugor Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
-
Bluetooth doesn't appear after boot very often in Orange Pi 2W
IBV replied to sminder's topic in Orange Pi Zero 2
Hi, without owning this board, chatgpt is pointing out to an initialisation issue of the bluetooth system caused by the GPIO pin not being correctly handled at boot. [ 6.024062] WCN: marlin chip en dummy pull up -- need manually set GPIO The correct solution would be to handle the init in the dtb file, but you can try the following systemd initialisation as a workaround to see if it works. Create (as root) the following service file /etc/systemd/system/bt-gpio.service with the contents: [Unit] Description=Enable GPIO for Bluetooth chip Before=bluetooth.service [Service] Type=oneshot ExecStart=/bin/sh -c 'echo 225 > /sys/class/gpio/export || true; echo out > /sys/class/gpio/gpio225/direction; echo 1 > /sys/class/gpio/gpio225/value' [Install] WantedBy=multi-user.target Then enable it (as root): systemctl daemon-reexec systemctl daemon-reload systemctl enable bt-gpio.service Reboot and check if the bluetooth starts correctly. Post the boot log if it does not. -
Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. This PR adds the RT kernel config file for TI devices. If RT_KERNEL=yes is passed as an argument to ./compile.sh, a PREEMPT_RT image is built. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. Tested this on SK-AM62B. Test 1: boot test: the board successfully booted Test 2: uname -a test: PREEMPT_RT string was present in the output, thus suggesting that its indeed an RT image Test 3: zcat /proc/config.gz | grep -i RT: Further confirmed that the PREEMPT_RT config is enabled in the running image Checklist: Please delete options that are not relevant. [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] My changes generate no new warnings cc: @glneo @Grippy98 @nmenon @sadik-smd View the full article
-
direct boot from nvme isn't possible. Boot loader (u-boot to say) must be present on SPI, eMMC or microSD.
-
sudo armbian-config
-
Put a multi meter on the PSU you are using to power the pi a flakey PSU can cause strange intermittent issues same for router.
-
Package `base-files` 25.* not built for trixie
Zoom replied to Zoom's topic in Software, Applications, Userspace
Related issue: https://github.com/armbian/build/issues/8261 Currently resolved for the beta repository. Now it's possible to switch to beta, update base-files and switch back to `apt.armbian.com`. Fixing for stable marked as "todo". - Yesterday
-
Armbian for an old Allwinner A10 tablet
Ryzer replied to thewiseguyshivam's topic in Allwinner sunxi
Ok that is a promising start at least. Are the 'BUG: bad page state messages' every boot or occasionally? The route cause will probably be difficult to find, possibly a deep route kernel or hardware issue. I tend to find that sometimes I will get the bad page state messages and then on another occassion get no kind of faults. You shouldnt need to enter any credientials on first boot, that only applies to setup over network connection. Once you have been able to login and if wireless works then you can install memtester to see if that picks up an errors. not a problem, looking forward to hearing your progress Ryzer -
Hi pcduino2user, Nice to see a fellow Pcduino user, I guess not many people interested in over a decade old hardware at this point. I try my best, I am by no means an expert, most of my current changes are just corrections to the device tree. Anyway, there appear to breaking changes in kernel 6.12 which breaks hdmi output. The intial patches for adding the hdmi display nodes are in my pcduino2-and-3-improvements branch however they are for much older kernel versions so need to be re-created, something I plan to do within the coming week. Additional the display driver needs a minor tweak. I currently have a userpatch derived from: https://patchwork.kernel.org/project/linux-arm-kernel/patch/20241130-hdmi-mode-valid-v5-10-742644ec3b1f@linaro.org/ Thanks Ryzer
-
@usual user But the filesystem was never currupt and the issue was only with the boot partition which is not a journaling filesystem. The Odruids is also known to work reliably without UPS.
-
Description Update odroidxu4-current kernel to 6.6.93. How Has This Been Tested? [x] Reboot of my Odroid HC1 Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
- Last week
-
Hi @Faheem, are you do it armbian install and working in this board? I use rk3228 boxes and want know more about this H313 boards, i see a mx10 with this chip in aliexpress, but before to buy, i should want sure it working linux! The H313, is it too problematic so or not? Thanks!
-
Question. Are there any owners of this R57 model?
-
Description The current script can overwrite drivers which are set as built-in in the board-specific config. This is not desirable. Add a check to ensure we do not convert built-in stuff into modules. First encountered it when pocketbeagle 2 kernels was enabling EXT4 as module instead of being built-in, which makes the current rootfs (using ext4) fail to run. How Has This Been Tested? Tested on PocketBeagle 2 Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article
-
Run dkms after armbian-upgrade
Marcos Alano replied to Marcos Alano's topic in Software, Applications, Userspace
Thanks. I'm still analyzing the problem. It seems it has the hook under /etc/kernel, so it should call dkms normally. -
The same bug also occurs on the Orange Pi Zero non-LTS board: shutdown instead of reboot (Armbian 25.5.1, kernel 6.12.30).
-
P.S. LibreElec for rk3588 and kernel 6.15 https://forum.libreelec.tv/thread/20823-unofficial-le-for-rk356x-rk3328-rk3399-rk3588-s-rk3576/?postID=200570#post200570
-
I'm interested too.
-
Efforts to develop firmware for H96 MAX V56 RK3566 8G/64G
mvpwar replied to Hqnicolas's topic in Rockchip CPU Boxes
do you remember your commit id for your success github action build ? @Hqnicolas by the way, I found the panther-x2 armbian image works, but the usb3.0 not works, do you know how to enable the USB3.0 port? -
3a vendor seems to work nicely. Not your images but built from sources just a few days ago. Should be pretty much identical. emmc is not detected. Though is the first time I tried emmc on this board and I don't know if the modules even work. Edge seems to work nicely as well. Also emmc is detected. I bet the cause of the non-working emmc on vendor is the garbage 2017.09 uboot.