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.

Thank you for your effort

Featured Replies

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"

 

Edited by Kuba

23 hours ago, Kuba said:

First of all big thank you to everyone who worked on adding nvidia Jetson nano back to list of supported boards.

Thank you! It took few days and now almost everything works. If you can provide more data, I can try to fix problem you have.

  1. test without the video= options.

  2. Post armbianmonitor -u.

  3. Post the output of dmesg | grep -iE 'drm|tegra|sor|dpaux|hdmi'.

  4. Post the EDID for each port: cat /sys/class/drm/card*-DP-1/edid | edid-decode and the same with HDMI-A-1.

Thanks. The log looks the same as before, so I need more data:

  1. dpkg -l | grep linux-image and uname -a

  2. Boot with drm.debug=0x6 log_buf_len=4M added to the kernel command line, without video=. Then share dmesg via paste.

  3. cat /sys/class/drm/card1-DP-1/modes

Unfortunately, this is what R&D often looks like. A lot of time spent troubleshooting, with plenty of frustration along the way. :(

Having direct access to the hardware makes this process much easier and faster. We really need to develop a service (add on to this) that allows users to enable remote debugging with a single click. Right now, there is simply too much manual back-and-forth involved.

Test kernel with the fix. It has the same version string as your current kernel, so install it with dpkg, not apt: sudo dpkg -i linux-image-edge-uefi-arm64-dt_26.11.0-trunk_arm64__7.3.1-*-Pa723-*.deb Reboot without video= and with drm.debug=0x6. Expected: no failed to choose link: -34, and DP shows 2560x1440@120. The 144 Hz and 165 Hz modes need more than the 600 MHz pixel clock the SOR supports. Please share dmesg and cat /sys/class/drm/card1-DP-1/modes.

linux-dtb-edge-uefi-arm64-dt_26.11.0-trunk_arm64__7.3.1-S79a9-D68f5-Pa723-Cf941-Hd102-HK01ba-V3428-B0577-R448a.deb linux-image-edge-uefi-arm64-dt_26.11.0-trunk_arm64__7.3.1-S79a9-D68f5-Pa723-Cf941-Hd102-HK01ba-V3428-B0577-R448a.deb

Thanks for testing. The DP link now works correctly at 2560x1440@120. The garbage during heavy screen output is a different problem. The memory clock probably cannot increase on this boot path. The kernel has no memory timing table for the Nano ("no memory timings for RAM code 0" in your log). At 120 Hz, the display then does not get enough memory bandwidth when the screen changes a lot. Workaround for now: use a lower refresh rate. Add one of these to the kernel command line and test with a lot of text output: video=DP-1:2560x1440@100

If 100 Hz still shows garbage, use video=DP-1:2560x1440@60. Please also send the output of this command. It shows the current memory clock:

sudo cat /sys/kernel/debug/clk/emc/clk_rate

The real fix needs (a lot) more work in the kernel memory driver. I cannot do it right now. Your answers will tell which fix is necessary.

  • Author

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.

Edited by Kuba

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

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.