Jump to content

Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates

  1. Past hour
  2. Pardon me for asking here. I need to re-install OPi PC 2 -which I use as a firewall/router- because the old Ubuntu from 2020 is EOL. - Is the kernel problem stated here still an issue? Latest DL is Armbian_community_24.5.0-trunk.667_Orangepipc2_jammy_current_6.6.31_gnome_desktop.img.xz - I also have Armbian_23.8.1_Orangepipc2_jammy_current_6.1.47_xfce_desktop.img.xz from the archives. Which one is to go? When I start, I'll probably lose my Internet connection...
  3. Yesterday
  4. Hi, I've build an SD card image with in a buildroot myself, used the stable branch as suggested. "For stable branch use --branch=v23.11"..and that all worked good so far. I'm no linux guy at all and begun some investigations, installed packages and configured the system, this was an desktop variant with xfce. Somewhere in the middle of work I've got the message that a security update is available and I should do an apt upgrade..done that. Interresting for me was, that I've got an Update to Armbian 24.2.1 jammy.. ok ..then this is so. I've noticed later that I don't have any video output from X11 anymore, after the login prompt the screen gets black with an cursor above left and later is shut off entirely, but the Xserver is still running, [pre] 1125 tty7 Ssl+ 0:06 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/ru n/lightdm/root/:0 -nolisten tcp vt7 -novtswitch [/pre] xrandr output: [pre] xrandr Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 16384 x 16384 DVI-I-0 disconnected primary (normal left inverted right x axis y axis) DVI-I-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 59.95*+ 1920x1080 60.00 59.93 1680x1050 59.95 1600x1200 60.00 1440x900 74.98 59.89 1280x1024 75.02 72.00 60.02 1024x768 75.03 70.07 60.00 800x600 75.00 72.19 60.32 640x480 75.00 72.81 65.99 59.94 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DVI-D-0 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 521mm x 293mm 1920x1080 60.00*+ 50.00 1680x1050 59.95 1600x900 60.00 1440x900 59.89 1280x1024 75.02 60.02 1280x800 59.81 1280x720 60.00 50.00 1152x864 75.00 1024x768 75.03 70.07 60.00 800x600 75.00 72.19 60.32 56.25 720x576 50.00 720x480 59.94 640x480 75.00 72.81 59.94 DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) [/pre] I've fiddeled around with some commands, but I'm unable to restore the Xserver Output on the DVI Output of the Cubieboard2. I have an DVI to VGA Connector plugged in and an TFT Display with the VGA Input to the converter. I'm unable to use the vga output that is provided at the DVK521 Board (WaveShare) too and already had planned to ask here how I can switch between the Video connectors with an actual Armbian. The last thing I've done where some entries in the armbianEnv to get an 2nd uart and the 1wire Interface enabled, that worked so far, but I was logged in with ssh from my host and haven't seen the X-Display from the Cubieboard2 since the monitor was switched to DVI which is connected to the host as 2nd monitor. I don't think that there is something wrong: [pre] armbianEnv: verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 rootdev=UUID=42951d58-2c17-42a5-af83-c6eaf7357967 rootfstype=ext4 overlay_prefix=sun7i-a20 overlays=uart3 w1-gpio param_uart2_rtscts=1 param_w1_pin=PB10 param_w1_pin_int_pullup=1 #extraargs=video=HDMI-A-1:1920x1080M@60 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u [/pre] The commented out extraargs line was from Igor suggested in another thread for a problem w/o connected monitor..but changed nothing. Can someone help me please? I hadn't much todo with Xserver setup in the last years..I'm tapping around pretty much in the dark.. Kind Regards, Holm
  5. I get all working with USB Tethering, after install miniarch WiFi works...
  6. I just bought 3 of these, 2 for me and one for a friend. I should have them by next week and can follow line by line instructions.
  7. Oh thanks a lot! I could probably use the 1st patch to the armbianEnv.txt file: the root volume is on a usb drive, so the 2nd option would not work for me. But I still believe there is some hardware issue because even when USB ports work, the voltage supplied to is far below 5V. And the issue I have has been getting worse over the years, as if a component was wearing out. I'll report back when I can give it a try.
  8. wifi operational with: ln -sf /lib/firmware/brcm/brcmfmac4330.bin /lib/firmware/brcm/brcmfmac4330-sdio.rockchip,rk3528-demo1-lp4-v10.bin ln -sf /lib/firmware/brcm/brcmfmac-ap6330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.rockchip,rk3528-demo1-lp4-v10.txt and a reboot, then nmtui to set up a connection
  9. Thank for the idea of the usb wifi i didn't buy it, i try a other dc power with 400ma i already have around originally I was using 300ma, now the wifi works like a charms, how high you think I can go 1a ? I want to add a fan
  10. base-files: hardcoded cache of base-files version per RELEASE/ARCH, as of 20240522 base-files: hardcoded cache of base-files version per RELEASE/ARCH, as of 20240522 packages.debian.org and packages.ubuntu.com are having a meltdown and builds are stuck this is a quick & dirty fix to get builds going we should urgently replace this with the 'right thing' trying to maintain this manually will cause insanity View the full article
  11. Mesa 24.1 is out, and the graphics team at Collabora has been working hard to bring a slew of new features and bug fixes to Panfrost, Zink, NVK, and Mesa in general. Here's a look at their contributions for this release cycle. View the full article
  12. @Nick A, Despite of your long instructions, several tries, spending hours with studying related topics, practically I could not reach any success. The most annoying thing is that when trying to boot the device from sdcard (using the uboot button), nothing happens, not even a single character appears on the console output. How the boot process supposed to work? My understanding, that the beginning part of the sdcard image contains an uboot, which is able to work with a partly initialized (powered up) hardware (starting to use SoC internal RAM), and would make minimal further hardware initialization, and load modules from the boot partition, like kernel, root-fs, device tree. Is it a valid assumption, that uboot should echoe the start of boot process already? (At least when the stock firmware starts, I see uboot messages.) Is it possible, that the uboot on the sdcard is not compatible with my hardware? Or simply the external boot is restricted by the software of the T95H android box? I also downloaded firmware for the box (found e.g. T95H-H616-X22.img), and checked, what file structure it shows: it is "PhoenixSuite image file", different format than an armbian (or other os) image...
  13. Whow..worked "out of the Box" with Overlays. Good Job Guys! Does anyone know if that Toch-LCD that is coming with that DVK521 Kit for the Cubieboards is working with armbian? I don't know anything about the hardware or even the original Software that came with the Cubieboard2 .. and the examples. The 3 boards I have are all used and none was complete with the original software to try out something. Regards, Holm
  14. Thank you! It looks like what I had was pretty close, anyway. The last one was: Armbian_23.8.1_Nanopineo_bookworm_current_6.1.47 from August 2023.
  15. this worked on a fresh installed armbian: apt update && apt upgrade -y wget -O armbian-config.deb 'https://forum.armbian.com/applications/core/interface/file/attachment.php?id=12473&key=a65459c80c08c1043133549c7b2b7b01' apt --fix-broken install dpkg -i armbian-config.deb Thanks @Igor! Note: I am on Armbian_23.02.2_Nanopim4v2_bullseye_current_5.15.93_minimal. And not on Armbian_community_24.5.0-trunk.667_Nanopim4v2_bookworm_current_6.6.31_minimal. I am using it for OpenMediaVault!
  16. Hi, I've been running the OMV7 latest with the armbian headless latest. I've set the power button for powering the system off in the OMV's gui. When the system is "on" I can power the system down by short press on the power button, the system powers off after aprox 10 seconds (so hopefully a clean shut down), the power led and network led get off, but the USB HDD (external 2.5in 320GB WD) still shows activity after power down - the activity led on it blinks (like 5 blinks per second) and I can hear a light clicking in aprox 1sec intervals. The disk does not spin, however (I cannot hear the spinning). I've been using a battery backup (3.7V lion) wired to the BPi M1 board permanently (there is an onboard controller for the battery backup management). What needs to be set in order the external USB HDD stops showing activity after the power down?
  17. - Update: Kernel 6.1 ✔️ HDMI Audio ✔️ WIFI 2.4 + 5ghz ✔️ Ethernet ❌ Bluetooth ❌ NPU ❌ VPU ❌ GPU Wifi-K610: https://drive.google.com/file/d/1B1LmAylalETcnBEWiPiJHL0MjK5xlIV4/view cd /lib/firmware/brcm/ sudo wget https://github.com/CoreELEC/brcmfmac_sdio-firmware-aml/raw/master/firmware/brcm/fw_bcm4335b0_ag.bin sudo ln -s fw_bcm4335b0_ag.bin brcmfmac4335-sdio.h96-TVbox,rk3566.bin sudo reboot now nmcli dev wifi sudo rmmod brcmfmac_wcc brcmfmac brcmutil modprobe brcmfmac - Image: Updated K610 test image: https://drive.google.com/file/d/1G3ne0N0DX-sKNr36uqGhnaVXHt6sqBMz/view?usp=sharing - BaseFiles: RK3566-H96-MAX-VENDOR-61-V3: https://drive.google.com/file/d/1Y5sGIE8uAo-eASNvkBkZ6SX3vdpiBFRU/view?usp=sharing edit Rockchip U-boot Legacy 4.19 DTS: https://github.com/hqnicolas/u-boot/blob/next-dev-v2024.03/arch/arm/dts/rk3566-h96.dts edit Rockchip U-boot Legacy 4.19 DEFCONFIG: https://github.com/hqnicolas/u-boot/blob/next-dev-v2024.03/configs/h96-rk3566_defconfig dmesg before install wifi & BT dmesg short: Full dmesg:
  18. Did you do code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } apt update beforehand? Images usually are shipped with empty lists to avoid having outdated ones packed which also increase image size.
  19. The video processor unit can decode your file but the rendering unit (GPU) can't display it. You can view your file at lower resolution and so you have half of 4k capabilities. Even at 1080p you get low FPS because the CPU can't resize fast enough. You need rk3588 or mabe rk3576 to view full 4k. An rk3566 with stand alone kodi can do the job but librelec or corelec are not supported for this CPU. Odroid M1 have this on its forum.
  20. Last week
  21. @specs A current 6.9.0 edge kernel (collabora version) is availale on beta.armbian.com (linux-dtb and linux-headers are available too). They can be downloaded to the filesystem using 'wget <URL>' and installed via 'dpkg -i linux*' (without armbian-config). After updating Armbian 24.2.1 (minimal) from linux 5.10.160 to 6.9.0: (system on emmc, data on a 4TB sata ssd (m.2)) ____ _ ____ ____ | _ \ ___ ___| | __ | ___|| __ ) | |_) / _ \ / __| |/ / |___ \| _ \ | _ < (_) | (__| < ___) | |_) | |_| \_\___/ \___|_|\_\ |____/|____/ Welcome to Armbian 24.2.1 Bookworm with Linux 6.9.0-collabora-rockchip-rk3588 No end-user support: community creations System load: 1% Up time: 27 min Memory usage: 3% of 7.35G IP: 192.168.xx.31 CPU temp: 45°C Usage of /: 33% of 14G I tried a network performance benchmark and it rocks: 2x 2.34 Gbits/s (bidirectional) ! (armbian-hardware-optimize disabled) # ./iperf3 -c 192.168.xx.31 -p 5201 (client -> rock 5b) Connecting to host 192.168.xx.31, port 5201 [ 5] local 192.168.xx.54 port 63943 connected to 192.168.xx.31 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.01 sec 284 MBytes 2.37 Gbits/sec [ 5] 1.01-2.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 2.00-3.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 3.00-4.00 sec 281 MBytes 2.35 Gbits/sec [ 5] 4.00-5.00 sec 281 MBytes 2.35 Gbits/sec [ 5] 5.00-6.01 sec 282 MBytes 2.35 Gbits/sec [ 5] 6.01-7.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 7.00-8.00 sec 281 MBytes 2.35 Gbits/sec [ 5] 8.00-9.00 sec 281 MBytes 2.35 Gbits/sec [ 5] 9.00-10.00 sec 280 MBytes 2.35 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.00 sec 2.74 GBytes 2.36 Gbits/sec sender [ 5] 0.00-10.01 sec 2.74 GBytes 2.35 Gbits/sec receiver # ./iperf3 -c 192.168.xx.31 -p 5201 -R (rock 5b -> client) Connecting to host 192.168.xx.31, port 5201 Reverse mode, remote host 192.168.xx.31 is sending [ 5] local 192.168.xx.54 port 63945 connected to 192.168.xx.31 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.01 sec 279 MBytes 2.33 Gbits/sec [ 5] 1.01-2.01 sec 281 MBytes 2.35 Gbits/sec [ 5] 2.01-3.01 sec 280 MBytes 2.35 Gbits/sec [ 5] 3.01-4.01 sec 281 MBytes 2.35 Gbits/sec [ 5] 4.01-5.00 sec 280 MBytes 2.35 Gbits/sec [ 5] 5.00-6.01 sec 281 MBytes 2.35 Gbits/sec [ 5] 6.01-7.01 sec 280 MBytes 2.35 Gbits/sec [ 5] 7.01-8.01 sec 281 MBytes 2.35 Gbits/sec [ 5] 8.01-9.01 sec 280 MBytes 2.35 Gbits/sec [ 5] 9.01-10.01 sec 281 MBytes 2.35 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.01 sec 2.74 GBytes 2.35 Gbits/sec 2 sender [ 5] 0.00-10.01 sec 2.74 GBytes 2.35 Gbits/sec receiver #./iperf3 -c 192.168.xx.31 -p 5201 --bidir (bidirectional) Connecting to host 192.168.xx.31, port 5201 [ 5] local 192.168.xx.54 port 63948 connected to 192.168.xx.31 port 5201 [ 7] local 192.168.xx.54 port 63949 connected to 192.168.xx.31 port 5201 [ ID][Role] Interval Transfer Bitrate [ 5][TX-C] 0.00-1.00 sec 278 MBytes 2.33 Gbits/sec [ 7][RX-C] 0.00-1.00 sec 273 MBytes 2.29 Gbits/sec [ 5][TX-C] 1.00-2.01 sec 280 MBytes 2.34 Gbits/sec [ 7][RX-C] 1.00-2.01 sec 281 MBytes 2.35 Gbits/sec [ 5][TX-C] 2.01-3.00 sec 278 MBytes 2.34 Gbits/sec [ 7][RX-C] 2.01-3.00 sec 279 MBytes 2.35 Gbits/sec [ 5][TX-C] 3.00-4.01 sec 280 MBytes 2.34 Gbits/sec [ 7][RX-C] 3.00-4.01 sec 281 MBytes 2.35 Gbits/sec [ 5][TX-C] 4.01-5.01 sec 279 MBytes 2.34 Gbits/sec [ 7][RX-C] 4.01-5.01 sec 280 MBytes 2.35 Gbits/sec [ 5][TX-C] 5.01-6.01 sec 279 MBytes 2.34 Gbits/sec [ 7][RX-C] 5.01-6.01 sec 280 MBytes 2.35 Gbits/sec [ 5][TX-C] 6.01-7.01 sec 279 MBytes 2.34 Gbits/sec [ 7][RX-C] 6.01-7.01 sec 280 MBytes 2.35 Gbits/sec [ 5][TX-C] 7.01-8.00 sec 278 MBytes 2.34 Gbits/sec [ 7][RX-C] 7.01-8.00 sec 279 MBytes 2.35 Gbits/sec [ 5][TX-C] 8.00-9.01 sec 280 MBytes 2.34 Gbits/sec [ 7][RX-C] 8.00-9.01 sec 281 MBytes 2.35 Gbits/sec [ 5][TX-C] 9.01-10.01 sec 279 MBytes 2.34 Gbits/sec [ 7][RX-C] 9.01-10.01 sec 280 MBytes 2.35 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID][Role] Interval Transfer Bitrate Retr [ 5][TX-C] 0.00-10.01 sec 2.72 GBytes 2.34 Gbits/sec sender [ 5][TX-C] 0.00-10.01 sec 2.72 GBytes 2.34 Gbits/sec receiver [ 7][RX-C] 0.00-10.01 sec 2.73 GBytes 2.35 Gbits/sec 1 sender [ 7][RX-C] 0.00-10.01 sec 2.73 GBytes 2.34 Gbits/sec receiver
  22. I realized that, and connected the pi5 to the lan port on my wifi router but wasn't able to see it in the clients list on my router dashboard (192.168.1.1). Waited for 10-15 mins.
  23. Description None. How Has This Been Tested? Not been. Checklist: [x] My code follows the style guidelines of this project View the full article
  24. Dear Armbian Community, We are excited to announce that our new release is approaching quickly, with an estimated release date of May 25th. Our team is working actively on the final touches, focusing on stability and fine-tuning advanced features such as 3D and video acceleration. We’re utilizing the best available methods, as there are multiple options to consider. We are adjusting our build targets to include stable, rolling and application-specific builds. Stable Releases: For those who prefer a more reliable and tested environment. Rolling Releases: For the latest updates and experimental features. Applications: Optimized builds for specific applications. We will continue to support Jammy (old stable Ubuntu) while gradually introducing Noble as the latter has numerous bugs from upstream user space applications. Official Partnership with Radxa: We are thrilled to announce a new official partnership with Radxa. This collaboration will enhance support for their newly released RK3588 boards, bringing more robust and reliable options to our users. Community Engagement and Giveaways: One of our current giveaways is nearing its end, but don’t worry – a new one is here! Stay tuned for more exciting opportunities. Focus Areas: As we approach the release date, we ask for your help, especially in the areas of desktop acceleration and desktop environments. While we have covered base OS system features well, your contributions and feedback are invaluable. Community Poll Results: We recently conducted a poll to understand our community’s involvement in open-source projects. Here are the results: I’m an active contributor: 28.6% Contributed occasionally: 31.7% Not yet, but I’d like to: 28.6% No, why?: 11.1% These results are based on 63 votes and show a vibrant and engaged community, with a significant number of active and occasional contributors. For those who haven’t contributed yet but would like to, we encourage you to get involved. Your participation can make a significant difference! Thank you for your continued support and contributions. Together, we can make Armbian even better! Best regards, The Armbian Team The post New Release Approaching Fast! first appeared on Armbian. View the full article
  25. Hi there. I have a Pine A64(+) board (https://pine64.org/documentation/Pine_A64/) I have been experiencing this issue since last year. I updated the SO (armbian version + kernel) several times and it didn't resolve the issue. It happens randomly. The CPU and storage are not overheated (30º C each) and I tested all physical components (board, ethernet wire, switch, ...) ambianmonitor -u -> https://paste.armbian.com/arozepuxen Things I tested for now: - Daily reboot. Sometimes eth0 is not wake up after boot and I have to physically power-toggle the board. - Stay on latest raspbian release (24.2.1) + latest kernel (6.6.16) + latest uboot. Same issue. - Stay on latest raspbian release (24.2.1) + legacy kernel (6.1.77) + latest uboot. Same issue. - Armbian 23.11.1 Jammy with Linux 6.1.63-current-sunxi64 was also some time the SO in the board. Same issue. - Also I set the segmentation and MTU as here but same issue: Notes: - CPU is "on demand". That's also why the temperature is OK. - Somehow is only 100Mbits available (the board has gigabit port). By the way, is not my concerning now. - https://github.com/jwrdegoede/rtl8189ES_linux/tree/rtl8189fs I saw this driver. Is this an option? Should I try? Any idea? Should I totally rebuild the microsd SO from zero with an ARMBIAN from 2021 or so? Any other suggestion? The board is totally unstable as it currently is and I guess is software related (driver maybe) Thank you.
  26. I ask this question purely out of curiosity - why is the userpatches folder not in the build folder when it is first cloned
  1. Load more activity
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines