Jump to content

Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates

  1. Past hour
  2. Should not be anything to be worried about. That just means the kernel module for the mentioned PHY is there but it lacks firmware binary. Though that board does not use that chip anyways AFAIK.
  3. Today
  4. Only a shot in the dark. Download this firmware and extract it with: tar -xzf u-boot-meson.tgz Write it to your with Armbian prepared SD card: dd bs=512 seek=1 conv=notrunc,fsync if=u-boot-meson.bin of=/dev/${entire-card-device-to-be-used} Boot with this SD card and report if this changes anything.
  5. After reading this thread maybe the cause is related to missing jumpers shorting P10 and P11 ... but why isn't been written in the wiki that for boot from microsd should be shorted P10 & P11 jumper? and why console don't start even if isn't found the bootloader code ? console is contained inside armbian image? Another question: here https://wiki.kobol.io/helios64/troubleshoot/ there is the section bootloader Old bootloader¶ On October 5th, 2020 there was device tree (dtb) filename change. It applied to Armbian 20.08.8. Originally the filename is rk3399-helios64.dtb and changed into rk3399-kobol-helios64.dtb Boot from microSD card and execute following commands sudo mkdir -p /mnt/system sudo mount /dev/mmcblk1p1 /mnt/system sudo ln -sf rk3399-kobol-helios64.dtb /mnt/system/boot/dtb/rockchip/rk3399-helios64.dtb sudo umount /mnt/system sudo poweroff Remove the microSD card and power on the system. After boot successfully to eMMC, we strongly suggest to update the bootloader using armbian-config. this step update emmc memory? the updated bootloader is present in the last armbian buster image?
  6. According to Armbian documentation only kernel 4.4 has support for emmc, actually tried and seems true, I had settled with Jammy on 5.18 since it has been working flawlessly on my machine and video has been better then ever, but 5.18 is not supported for emmc, so wanted to make it a permanent shift, are you guys planning to give any of your new Kernels for the rp64 emmc support? would be very much appreciated, at least on one of the stable builds?
  7. I agree with @Werner, I was asking if an adapter was in use to understand if there could be an interference with the HDMI signal. The output of these commands can be useful: xrandr --verbose get-edid | parse-edid (you may wish to install read-edid package first for get-edid and parse-edid utils)
  8. Currently adopted 5.20-1 Reboot board. Change from regulator-boot-on to regulator-always-on. reg_dcdce: dcdce { regulator-always-on; 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. Jira reference number [AR-9999] 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. [ ] Test A [ ] Test B 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
  9. Hm I though there should be a menu entry called "hardware" to enable various overlays... Since it is media kernel @balbes150d Got an idea if overlays are missing or something? Thanks
  10. Hi there, I need to install below libraries on my orange pi lite, on a virtual environment tensorflow 2 keras numpy pandas OrangePi.GPIO does anyone have a armbian image including all these libraries pre-installed. because everytime I try to do it, I face lots of odd errors, mostly for installing tensorflow 2, and installing anyone of libraries on virtual environment.
  11. You could perhaps use armbian-config System Nightly switch to the nightly build to see if the issues have been fixed.
  12. LilyGO has launched yet another ESP32 board with an integrated color display. The TTGO T4 offers a 2.2-inch or 2.4-inch color display, LiPo battery support, but in contrast to many other boards from the company, features a battery charging circuitry based on Injonic IP5306 “fully-integrated power bank system-on-chip with 2.1A charger, 2.4A discharger”. The WiFi and Bluetooth IoT board is also equipped with 4MB flash, a MicroSD card socket, 8MB PSRAM, a 20-pin GPIO header and a 5-pin I2C connector for expansion, and a few buttons for programming and user control. TTGO T4 v1.3 specifications: Wireless MCU – Espressif Systems ESP32 dual-core Tensilica LX6 microcontroller @ up to 240 MHz with 520 KB SRAM, wireless connectivity RAM – 8MB SPRAM (ISSI PN18S32) Storage – 4MB SPI NOR flash, MicroSD card slot Connectivity (ESP32) 2.4 GHz 802.11 b/g/n Wi-Fi 4 Bluetooth 4.2 BR/EDR and Bluetooth LE 3D antenna and u.FL connector [...] The post TTGO T4 ESP32 board features 2.4-inch color display, IP5306 battery charging IC appeared first on CNX Software - Embedded Systems News. View the full article
  13. Yesterday
  14. I just cannot access spi on my Rock64. I read a couple posts of it but none works out for me I'm running Armbian 22.05.3 Focal with Linux 5.15.52-rockchip64 on it. Tried enabling spi-jedec-nor and spi-spidev overlay, but with none of them I get output when executing ls /dev/spi*. Is it maybe a hardware issue, reading this post suggests that to me: https://forum.pine64.org/showthread.php?tid=5473&pid=34616#pid34616 But I cannot make much sense out of it. Can anyone help me get spi working?
  15. My strategy to boot from SD with / on the eMMC didn't work. All I get is a spinning Armbian pinwheel. All the other distros I've run on the PBP use a separate boot partition and a different file structure than Armbian. A reply to one post that I found here on the forums requesting information about armbianENV.txt documentation seems to imply that the entire system must be rebuilt and there's no documentation (it's too simple to benefit form it ) I really like Armbian but we should not have to run / off of an SD card.
  16. And fixing the "Adding a module" documentation... It still will require a full fledged guide at some point, though. View the full article
  17. Maybe it's in the name (also Chris), but I have the same problem. Can't get HDMI out on the new images on a nanopim4v2. I will try another monitor (mine is a ultrawide 5K). Never had a problem with the previous images (though never could get the edid resolutions to work), but 1920 x 1080 did work. I also think the reaction of balbes150 is quite harsh. It's sad that we have to communicate this way between forum members.
  18. I vaguely remember having trouble with this myself. The 2mm pins were a problem too so I switched to a different board. Are you absolutely sure you have shorted the right two pins? One of those $10 USB logic analysers from eBay can be handy to see if the TX is actually TXing. They work with Pulseview from Sigrok.
  19. I think many of us want to use arm sbc as NAS, but remember, your data is expensive, but you put it on cheep server... at least you need an arm device designed for NAS, not any SBC.
  20. First of all, for this multimedia integration to work, you need to be running the legacy kernel (4.4.x). You don't specify which kernel you are running. Second, AFAIK the only option to make HW encoding to work is gstreamer. This solution will install the required gstreamer plugin (see first post). But Jellyfin uses ffmpeg, so it is difficult that you can make it work with gstreamer, without editing the code and recompiling. Maybe another option is using a wrapper script that uses a ffmpeg pipe, and pointing the custom ffmpeg version from Jellyfin menu, but I have never tried something like that. Third, and most important, if you want to post any question, please follow the forum guidelines and provide all the necessary information.
  21. Hi, MMGen, thank you for your contribution here. I have a Rock Pi 4A+ and am trying to install Armbian to the eMMC module, fully encrypted. After running your script for /dev/mmcblk1 (the eMMC module) I am getting the following error: armbian_rootenc_setup.sh:841: copy_system_root() failed at command 'cryptsetup luksOpen "/dev/$ROOT_DEVNAME" $ROOTFS_NAME' I tried to unlock it manually but it doesn't work: cryptsetup luksOpen /dev/mmcblk1p2 temp No key available with this passphrase. (Yes I did use the correct key which I entered during the setup script's prompt) Any suggestions on how to fix this? Found the problem; the script isn't creating the encrypted partition correctly. If I make the luks partition manually, the script works.
  22. Description Issue #4031 supports label. But the flag for label in mkfs.vfat and mkfs.f2fs isn't -L. How Has This Been Tested? [X] Build Checklist: [ ] 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
  23. Firefly Station M3 is a mini PC powered by Rockchip RK3588S octa-core Cortex-A76/A55 processor, the cost-down version of the RK3588, and equipped with up to 16GB RAM, 128GB eMMC flash storage, support for M.2 SATA and NVMe SSD, 8K capable HDMI and DisplayPort (USB-C) video outputs, Gigabit Ethernet, WiFi 5, and more. The new model follows the Station M1 and Station M2 mini PCs with Rockchip RK3328 and RK3566 respectively and will deliver 4 times the CPU performance and up to 8 times the 3D graphics performance compared to the M2 model, but in a slightly larger and about twice as thick enclosure – probably for active cooling – than the first two Station M fanless mini PCs. Firefly Station M3 specifications: SoC – Rockchip RK3588S octa-core processor with 4x Cortex-A76 cores @ up to 2.4 GHz, four Cortex-A55 cores, Arm Mali-G610 MP4 quad-core GPU with OpenGL ES 3.2, OpenCL [...] The post Firefly Station M3 – A Rockchip RK3588S mini PC with up to 16GB RAM appeared first on CNX Software - Embedded Systems News. View the full article
  24. Last week
  25. Are you trying to power the board via the GPIO? I don't think there is a GPIO to shut off the 5V pins from within the board itself.
  26. https://github.com/armbian/build/blob/master/config/sources/families/include/meson64_common.inc#L20 This is the default for Meson64. No one added the actual top speeds for the Vims apparently https://github.com/armbian/build/blob/master/config/sources/families/meson-g12a.conf#L5 is the override for the Meson G12A. G12B needs something similar in here: https://github.com/armbian/build/blob/master/config/sources/families/meson-g12b.conf
  27. Glad to hear it. I'm not sure how you had the old environment that only attempted tftpboot; but I'm glad "restore defaults" remains a good fix.
  28. Nexus

    Odroid M1

    Hello again. Thanks for that tip. I spun up an x86 Ubuntu 22.04 VM and tried again on armbian-next. Still, no luck, with this time the issue being the unavailability of the file `jammy-cli-arm64.4adfa3833e0441b5fb7bfe6607347039.tar.zst` on Armbian mirrors. Any clue on what mirror to get this/where to find it (if that is actually the issue here)? I've tried numerous different mirrors on different machines and in different configurations. Logs are attached. Thank you very much for your help with this. logs.tar.zst
  1. Load more activity
×
×
  • Create New...