

RSS Bot
Bot-
Posts
4209 -
Joined
-
Last visited
Never
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by RSS Bot
-
Description working:WiFi,HDMI,SATA,ETH not work:digital display,IR... 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] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article
-
Description These are dead kernels with no ties to either vendor or mainline support. Remove patchsets to reduce clutter and confusion for any/all future contribution. (Example: Fixes should be posted to all LTS and current stable mainline kernel, not to these dead ones) How Has This Been Tested? Kernels have to be manually selected be editing config files, they aren't being used in the build system itself, any niche use for them can be accomplished by pulling them from history by the user. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
-
Description RTL8153B - does not initialize correctly on boot. Reboot is okay. Start delay work-around in the board file needs tweaking for longer boot time. Jira reference number AR-1910 How Has This Been Tested? [x] Kernel 6.1y tested on Orange Pi R1 Plus LTS [x] Kernel 6.6y tested on Orange Pi R1 Plus LTS 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
-
Description Some high-resolution monitors (QHD/4K) will not output the desktop, and will enter sleep mode, directly after booting up an Armbian 23.8.1 desktop image and completing the initial setup questions. When such a monitor is attached, the kernel will auto-detect the SimpleDRM graphics driver, which is then prioritized over the Panfrost graphics driver. However, SimpleDRM outputs to a virtual output, while Panfrost outputs to the actual HDMI port. This causes the monitor to not receive any data. By blacklisting the simpledrm kernel module, Panfrost will take care of accelerated graphics (for any monitor) by default. Advanced users can still access simpledrm if required. Jira reference number [AR-1908] How Has This Been Tested? An Armbian image with a Cinnamon desktop has been build using the default options. That image has been written to a SD-card and tested on both a QHD monitor (that had the initial problem) and an older Full HD monitor (that worked fine before as well). In both test cases, the simpledrm kernel module was not loaded. The desktop was visible on the HDMI output both on initial boot and after subsequent reboots. 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 [N/A] I have made corresponding changes to the documentation [X] My changes generate no new warnings [N/A] Any dependent changes have been merged and published in downstream modules View the full article
-
rk3588: experimental UEFI edk2 support core extensions: fix: don't redefine extension_function_info when recursing otherwise when there's a chain of enable_extension() we lose the original info extensions: grub-with-dtb: add UMS menu entry to GRUB if initramfs ums hook is detected this allows user to enter UMS mode from GRUB for usage with the initramfs-usb-gadget-ums extension has no effect unless initramfs-usb-gadget-ums extension is enabled together with grub-with-dtb extensions: initramfs-usb-gadget-ums: kernel cmdline enables initramfs UMS of all block devices this optional extension adds an initramfs script that: enumerates and filters all block devices exposes each device as an UMS (USB Mass Storage) in an USB Gadget loops forever with info (board never boots) the idea here is to compensate for UEFI's lack of "ums" or "rockusb" mode that's present in u-boot it also allows to expose USB/NVMe devices that might or not be detected by bootloader, if the kernel works extensions: uefi-edk2-rk3588: deploy edk2 (not u-boot) for rk3588 boards this extension is 100% optional and shouldn't adversely affect any builds if not enabled requires UEFI_EDK2_BOARD_ID to be set in board file, so we know which UEFI/edk2 build to use it finds the latest edk2 version from GitHub automatically (currently v0.9.1) it downloads (and caches) the correct edk2 build image automatically if forces certain aspects of the image: must use GPT partitioning must NOT use a separate /boot partition it disables the building and deploying of u-boot completely (thus blobs etc are from edk2) it creates a GPT "uboot" partition pointing to edk2's FIT, required by SPL this extension: automatically enables 'grub-with-dtb' automatically enable 'initramfs-usb-gadget-ums', to compensate for lack of ums/rockusb since we dont have u-boot anymore rk3588: configure UEFI_EDK2_BOARD_ID for all UEFI-supported boards From https://github.com/edk2-porting/edk2-rk3588/releases/tag/v0.9.1 For example, for rock-5b_UEFI_Release_v0.9.1.img UEFI_EDK2_BOARD_ID is rock-5b Important: this has no effect unless optional extension is enabled to test this out: make sure to read carefully the instructions at https://github.com/edk2-porting/edk2-rk3588/blob/master/README.md suppose you previously built the regular u-boot version with: ./compile.sh BOARD=rock-5b BRANCH=legacy RELEASE=jammy now you can build the UEFI version with: ./compile.sh BOARD=rock-5b BRANCH=legacy RELEASE=jammy EXT=uefi-edk2-rk3588 write the produced image to SD or eMMC and boot it use normally, or enter "UMS" mode by selecting that option in the grub menu You can write image to eMMC, boot it, enter UMS, write it again to NVMe, reboot, press in UEFI and boot from NVMe Also works if .img is written to eg USB stick, and UEFI edk2 is separately deployed to SPI flash Important: make absolutely sure you are able to force Maskrom mode (by shorting pins, pressing buttons, etc) before writing an UEFI image to eMMC; UEFI has no RockUSB ("Loader mode" support) at all. The new "initramfs-usb-gadget-ums" extension hopes to address this, but it is not guaranteed to work. View the full article
-
1
-
Description Adjusting text, remove broken coloring scheme View the full article
-
Description This tries to lower the DRAM frequency of Tritium H5 like what is done on other H5 boards, because I met stability issues when running Klipper on it. How Has This Been Tested? I built a U-Boot deb and flashed it to my Tritium H5, and the stability enhances. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] 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
-
No descriptionView the full article
-
To ensure the Linux kernel is running smoothly, it requires maintenance from a variety of levels. Those working on the lower levels, or the plumber layers, of the kernel will have a chance to convene next week at the annual Linux Plumbers Conference. View the full article
-
Description media: fix firefly-rk3399 mini-pcie slot. Problem description: The 3G/4G module is not available on the firefly-rk3399. According to the schematic, the "MINI PCIE" on the firefly-rk3399 only has USB2 functionality. Comparing with the official kernel device tree, it is found that the vcc3v3-3g-regulator power supply node is missing. However, the pins used by this node conflict with the leds node referenced in the kernel device tree for roc-rk3399-pc. This node is redundant in firefly-rk3399, so it is defined as "node deletion". Summary of modifications: Added vcc3v3-3g-regulator power supply node. Defined node deletion. How Has This Been Tested? [x] Successfully built. [x] System startup. [x] The USB2 functionality of "MINI PCIE". 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 [x] Any dependent changes have been merged and published in downstream modules View the full article
-
Update maintainers and board status synced status from the database rename to .csc where we don't have anyone If you want to become a board maintainer, adjust data here. Ref: Board Maintainers Procedures and Guidelines View the full article
-
Pull Request Description Documentation-Focused: Armbian Build Framework Wrapper Script Overview This pull request introduces a user-friendly wrapper script that acts as a bridge to interact with the Armbian Build Framework. Its main goal is to enhance accessibility and facilitate communication for users who may not be familiar with the underlying script. Key Features Provides a simplified interface for easier interaction. Improves documentation with enhanced help messages. Supports multiple system languages (English, German, Spanish). Future Enhancements Implementation of man pages generation. Integration for markdown documentation. Potential flexibility for JSON output. Testing Extensive testing will be conducted to ensure accurate and complete documentation generation, as well as fine-tuning of output formats for optimal readability. Additional Information The primary focus of this implementation is to enhance the accessibility and comprehensibility of the Armbian Build Framework through robust documentation. View the full article
-
Description As per description. How Has This Been Tested? [x] Patch test 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
-
Description Add support for onboard eeprom in JetHub D1+ devices. Jira reference number AR-1907 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] current/edge build [ ] Test B 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
-
Description In #4352 the kaslrseed command is added. This results in "Unknown command ' kaslrseed ' - try 'help'"; but does continue with booting. This is not the cleanest message; rather check for the command before executing. How Has This Been Tested? N/A [ ] Test A 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 [X] Any dependent changes have been merged and published in downstream modules View the full article
-
No descriptionView the full article
-
basic support for Hyper-V and Azure uefi-{arm64|x86} edge 6.6: kernel .config: update .config, no changes uefi-{arm64|x86} edge 6.6: kernel .config: enable Hyper-V (also, Azure) support (as modules / requires initrd) extensions: image-output-vhd: outputs the image in VHD format (for HyperV/Azure) with correct size View the full article
-
Description Enable BINFMT_MISC for box86. Enable UHID for bluetooth LE keyboard I have a bluetooth LE keyboard with pairing issue: unexpected SMP command 0x06 unexpected SMP command 0x07 The root cause might be a race condition, but the kernel patch which just pass two SMP code check just works. 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] xiaomi-elish kernel build success [x] My bluetooth keyboard is paired and work fine. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] 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 P.S.: @igorpecovnik it's my bad to push the branch to the main repo, this pr is from my own repo so you can delete that branch if necessary: https://github.com/armbian/build/tree/sm8250-6.6-config View the full article
-
Description Add patches as Justin Green mentioned to enable DMA buffer caching on hantro and rkvdec driver. Hantro and rkvdec driver have set dst_vq->dma_attrs to DMA_ATTR_ALLOC_SINGLE_PAGES | DMA_ATTR_NO_KERNEL_MAPPING and it will not pass check in dma_alloc_noncontiguous, so I add a patch to deal with it. 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] rockchip64-edge build success [x] chromium v4l2 decoder works on orangepi3b. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] 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
-
Description Some patches are modified to get applied to kernel 6.6. Add a new patch 0026-Enable-non-coherent-dst-bufs-for-Venus-V4L2-driver.patch from Justin Green so that chromium will have better performace. 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] Kernel build success for xiaomi-elish [x] Kerne boots fine on xiaomi-elish Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] 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
-
Description cpufrequtils is due to removal. Its not present in trixie anymore ... How Has This Been Tested? [x] Build armhf image / rootfs Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
-
Description thead: update linux to 6.6, enable on-board 8723ds wifi chip 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] Successfully built. [x] System startup(EMMC). 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 [x] Any dependent changes have been merged and published in downstream modules View the full article
-
MLBench enables developers and maintainers to effortlessly gauge how their frameworks perform compared to other implementations, prior code versions, or across different boards, with respect to both runtime performance and other metrics. View the full article