Jump to content

vinser

Members
  • Posts

    12
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 😄 Sorry but I didn't get have you used KDE+Armbian on N2+ or any other SBC with S922X? Do you suggest trying the Armbian Jammy Gnome desktop distribution or installing KDE on a Armbian minimal distribution for N2+?
  2. @usual user Thanks for your response. I don't even try to play video, just start and browser with empty url string. To my regret now firefox gives the similar error and there is no wayland based desktop for Odroid N2+ SBC yet.
  3. Hi On fresh installed Armbian_23.5.1_Odroidn2_jammy_current_6.1.30_xfce_desktop when starting chromium-browser I get odroidn2:~$ chromium-browser Gtk-Message: 20:49:33.686: Failed to load module "xapp-gtk3-module" libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) [18372:18372:0625/204934.172288:ERROR:gpu_init.cc(537)] Passthrough is not supported, GL is egl, ANGLE is [18372:18372:0625/204934.232251:ERROR:gl_display.cc(508)] EGL Driver message (Error) eglQueryDeviceAttribEXT: eglQueryDeviceAttribEXT [18372:18372:0625/204934.232523:ERROR:gl_angle_util_vulkan.cc(189)] Failed to retrieve vkGetInstanceProcAddr [18372:18372:0625/204934.232712:ERROR:vulkan_instance.cc(91)] Failed to get vkGetInstanceProcAddr pointer from ANGLE. MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to open zink: /usr/lib/dri/zink_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) failed to load driver: zink MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) failed to load driver: kms_swrast MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) failed to load swrast driver After that browser starts and runs normally. Are there any suggestions to fix this?
  4. Hello. Two month ago there was mesa-driver release that mitigates this bug - DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory after some time of apps usage @Igor Do you know will mesa-driver be updated in Armbian distros? Or may be you'll be so kind to give the advice how one can update it itself?
  5. Use /sys/devices/virtual/thermal/thermal_zone0/trip_point_3_temp instead of trip_point_4
  6. Hi, Does anyone know how to get rid of the error on Odroid N2+ ? The error appears after some time of using GUI app on XFCE DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory Failed to create scanout resource
  7. I found the answer here https://forum.odroid.com/viewtopic.php?p=328617&sid=ffa8fb06890d3ba45a53f4796fdbe466#p328617
  8. @Igor And how do I can fix my changes to active trip point (/sys/devices/virtual/thermal/thermal_zone0/trip_point_3_temp) not to be overwritten on boot? Sorry for necroposting
  9. Hi, Odroid N2+ Armbian 22.05 Jammy Kernel 5.10.y, Size: 360Mb, Updated: Jul 1, 2022 + XFCE installed by means of armbian-config htop shows Systemd: degraded (1/372 failed) root@n2p-dev:~# systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● fwupd-refresh.service loaded failed failed Refresh fwupd metadata and update motd LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. root@n2p-dev:~# systemctl status fwupd-refresh × fwupd-refresh.service - Refresh fwupd metadata and update motd Loaded: loaded (/lib/systemd/system/fwupd-refresh.service; static) Active: failed (Result: exit-code) since Thu 2022-08-04 14:14:15 +05; 7h ago TriggeredBy: ● fwupd-refresh.timer Docs: man:fwupdmgr(1) Process: 10953 ExecStart=/usr/bin/fwupdmgr refresh (code=exited, status=1/FAILURE) Main PID: 10953 (code=exited, status=1/FAILURE) CPU: 79ms Aug 04 14:14:14 n2p-dev systemd[1]: Starting Refresh fwupd metadata and update motd... Aug 04 14:14:15 n2p-dev systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE Aug 04 14:14:15 n2p-dev systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. Aug 04 14:14:15 n2p-dev systemd[1]: Failed to start Refresh fwupd metadata and update motd. How do I can repair this? Where to look for? Thanx UPD: root@n2p-dev:~# /usr/bin/fwupdmgr refresh WARNING: UEFI capsule updates not available or enabled in firmware setup See https://github.com/fwupd/fwupd/wiki/PluginFlag:capsules-unsupported for more information. Updating lvfs Downloading… [***************************************] Downloading… [***************************************] Downloading… [***************************************] Successfully downloaded new metadata: 1 local device supported
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines