Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (โ‹ฎ) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Kuba

Members
  • Joined

  • Last visited

  1. Thank you @Igor It works right only at 60Hz, tried 100Hz ,80Hz - same result as 120Hz Memory clock: kuba@uefi-arm64-dt:~$ sudo cat /sys/kernel/debug/clk/emc/clk_rate 204000000 Regards Kuba PS. Once again thanks for help. I am ready to test anything in future. BTW. Is there any set of (unit)tests one should use when testing new Armbian builds for example? What I already tested is USB/BT, USB/Z-wave, WiFi, ETH, DP (as above), HDMI (with manual config, ...) - all work from start. PWM works as well (tested under stress test). From the other hand serial console on pins 6/8/10 does not wake up (even I added extra support into kernel (7.3), extra grub config,, tested loops with pins 8/10 connected together, .... - guess it's a device tree config thing) Main purpose of my production device is to host about 20 containers covering different home automation processes - that also works fantastically well from the very beginning (docker installed by apt as standard), migration to Armbian went without issues.
  2. Hi @Igor It works much better! - monitor switches to 120MHz. It is stable if no changes on the screen but if I start to print a lot ... - it starts to be "cryptographic monitor" (screens attached) debug_modes_fix.log debug_dmesg_fix.log debug_armbian-debug_fix.log IMG_4380.HEIC IMG_4381.HEIC
  3. Hi @Igor If you are willing to help, I am more than happy to test as many times as needed . All the data included Cheers Kuba debug_uname.log debug_modes.log debug_dpkg.log debug_dmesg.log debug_armbian-debug.log
  4. Hi @Igor Downloaded from % cat .git/HEAD ref: refs/heads/tegra-sor-dp-mode-valid Unfortunately same result https://paste.armbian.com/oyuboketug
  5. Compiling . I will test tomorrow and share results.
  6. Thanks @Igor ! Here it is 1. video option removed / jetson nano restarted 2. https://paste.armbian.com/jabemeteno 3,4 attached (+ example how DP screen looks like, HDMI shows just black) Kuba HDMI_DP_debug.txtIMG_4377.HEIC
  7. Hi all First of all big thank you to everyone who worked on adding nvidia Jetson nano back to list of supported boards. I was able to do upgrade to Ubuntu 24.04 by myself but still on old kernel. Now, after recent changes to Armbian - the little board received new live!! Thanks! Kuba Hint: Somehow my LG monitor required extra grub config before DisplayPort & HDMI ports started to work properly (frequency was an issue). If anyone faced similar problems - here is what worked for me. GRUB_CMDLINE_LINUX="video=DP-1:2560x1440@60 video=HDMI-A-1:1920x1080@60e"
  8. Kuba replied to balbes150's topic in Other families
    can this be a problem? [๐Ÿณ|๐Ÿšธ] Kernel DTB-only for development [ Copying preprocessed version of nvidia/tegra210-p3450-0000.dtb ] '/armbian/cache/sources/linux-kernel-worktree/6.1__arm64__arm64/arch/arm64/boot/dts/nvidia/.tegra210-p3450-0000.dtb.dts.tmp' -> '/armbian/output/nvidia-tegra210-p3450-0000.dtb--6.1-legacy.preprocessed.dts' arch/arm64/boot/dts/nvidia/tegra210.dtsi:1874.15-1885.4: Warning (unique_unit_address): /usb@7d000000: duplicate unit-address (also used in node /usb-phy@7d000000) arch/arm64/boot/dts/nvidia/tegra210.dtsi:1912.15-1923.4: Warning (unique_unit_address): /usb@7d004000: duplicate unit-address (also used in node /usb-phy@7d004000) arch/arm64/boot/dts/nvidia/tegra210.dtsi:410.37-421.4: Warning (interrupt_provider): /interrupt-controller@50041000: Missing #address-cells in interrupt provider arch/arm64/boot/dts/nvidia/tegra210.dtsi:442.37-453.4: Warning (interrupt_provider): /interrupt-controller@60004000: Missing #address-cells in interrupt provider arch/arm64/boot/dts/nvidia/tegra210.dtsi:488.22-503.4: Warning (interrupt_provider): /gpio@6000d000: Missing #address-cells in interrupt provider arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts:174.17-416.5: Warning (interrupt_provider): /i2c@7000d000/pmic@3c: Missing #address-cells in interrupt provider arch/arm64/boot/dts/nvidia/tegra210.dtsi:841.26-948.4: Warning (interrupt_provider): /pmc@7000e400: Missing #address-cells in interrupt provider also defined at arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts:419.15-428.4 arch/arm64/boot/dts/nvidia/tegra210.dtsi:1420.39-1430.5: Warning (interrupt_provider): /aconnect@702c0000/interrupt-controller@702f9000: Missing #address-cells in interrupt provider also defined at arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts:618.33-620.5 [๐Ÿณ|๐Ÿšธ] Kernel DTB-only for development [ Preprocessed FDT dest: /armbian/output/nvidia-tegra210-p3450-0000.dtb--6.1-legacy.preprocessed.dts ] [๐Ÿณ|๐Ÿšธ] Kernel DTB-only for development [ Preprocessed FDT normalized: /armbian/output/nvidia-tegra210-p3450-0000.dtb--6.1-legacy.preprocessed.normalized.dts ] [๐Ÿณ|๐Ÿšธ] Kernel DTB-only for development [ Preprocessed FDT normalized, no phandles: /armbian/output/nvidia-tegra210-p3450-0000.dtb--6.1-legacy.preprocessed.normalized.nophandles.dts ]
  9. Kuba replied to balbes150's topic in Other families
    Hi friends Anyone being able to run any of the newest Armbian builds on Jetson Nano + HDMI and/or DisplayPort? PS. I have updated bootloader, system starts itself. It's simply super frustrating that the board lost support even it's still fine to play with. Happy to test any ideas - I have 3 jetson nano devices (one running docker + home assistant and few services organizing IoT home stuff on custom build ubuntu 22), 2 ready for any tests, quite power-full laptop so I can do builds in minutes and some knowledge. Need someone to team-up with so maybe we can finally get the Armbian's build fully functional?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions โ†’ Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.