Jump to content

Kernel 6.2 (HDMI USB LAN etc) for OPI5


balbes150

Recommended Posts

Ohhhh with that one I now do get the GPU detected with glxinfo -B !

Nice one! :)


[ I kept updating this maybe skip to the end for the success part? ]

 

There are some very cool and strong graphical artifacts in some areas now and then and there's a error message from the glxinfo.

Is there a device file I need to flip some permission on or something maybe?

 

Using gnome+wayland.

 

fred@orangepi5:~$ glxinfo -B
name of display: :0
DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
Failed to create scanout resource
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Mesa (0xffffffff)
    Device: Mali-G610 (Panfrost) (0xffffffff)
    Version: 23.0.0
    Accelerated: yes
    Video memory: 7695MB
    Unified memory: yes
    Preferred profile: compat (0x2)
    Max core profile version: 0.0
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.1
OpenGL vendor string: Mesa
OpenGL renderer string: Mali-G610 (Panfrost)
OpenGL version string: 3.0 Mesa 23.0.0-devel (git-cbe80448cc)
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
Failed to create scanout resource

OpenGL ES profile version string: OpenGL ES 3.1 Mesa 23.0.0-devel (git-cbe80448cc)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10

 

 

 

Trying this but it doesn't help,

sudo chmod a+rw /dev/dri/*

 

I'll google around a bit!

Don't worry if this is eating up your time and you'd rather spend that on other things.

If that's the case I'll just leave this until its more mature.

If not I'm happy to keep trying stuff.

 

UPDATE: trying glmark2-es2-wayland but it doesn't find the GPU it is running with llvm.

Both these ways of running:

> glmark2-es2-wayland

and

> LD_LIBRARY_PATH="/usr/lib/aarch64-linux-gnu" glmark2-es2-wayland

libEGL warning: egl: failed to create dri2 screen
libEGL warning: failed to get driver name for fd 0

libEGL warning: MESA-LOADER: failed to retrieve device information

libEGL warning: failed to get driver name for fd 0

 

 

glxgears also not happy:

DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
Failed to create scanout resource
Segmentation fault


Checking dmesg for drm:

[just the tail of output]

 

[    2.449518] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable [rockchipdrm]] dclk_out0 div: 0 dclk_core0 div: 2
[    2.449565] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable [rockchipdrm]] set dclk_vop0 to 148500000, get 148500000
[    2.861015] rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device
[    2.878911] [drm] Initialized rockchip 3.0.0 20140818 for display-subsystem on minor 1
[    3.117857] [drm:rockchip_drm_fault_handler [rockchipdrm]] *ERROR* iommu fault handler flags: 0x0
[    3.243729] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0
[    3.244607] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0
[    3.245466] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0
[    3.246323] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0
[    3.247183] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0
[    3.248039] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0
[    3.248895] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0
[    3.249757] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0
[    4.753891] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...
[    4.802028] systemd[1]: modprobe@drm.service: Deactivated successfully.
[    4.803050] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm.
[   24.800483] [drm:rockchip_drm_fault_handler [rockchipdrm]] *ERROR* iommu fault handler flags: 0x0
[   24.801159] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0

 

 

 

 

UPDATE 2:
Waaiiit a minute. It seems my custom build Mesa was interfering even after I had reset the ld conf files + sudo ldconfig.

Now I was able to run,
> LD_LIBRARY_PATH="/usr/lib/aarch64-linux-gnu" glmark2-es2-wayland

 

and without changing the default governor I got:
glmark2 Score: 2189
Success!! :D


There were still some strong glitching in the following,

[jellyfish] 

[terrain]

[refract]

but maybe something in my own Mesa install still interefered.
I still also get the

DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied

from glxinfo.

 


UPDATE 3:
After sticking the governor to performance  glmark2-es2-wayland returns:


glmark2 Score: 3455

 

A new record for me on this board! :D

The other issues mentioned above are still there but maybe I'll have to re-run on a clean flashed SD card and see what goes away. That'll be for later because now I'm itching to try Dolphin again on this setup!  :)

 

Edited by fredrum
Link to comment
Share on other sites

5 часов назад, fredrum сказал:

There are some very cool and strong graphical artifacts in some areas now and then and there's a error message from the glxinfo.

Is there a device file I need to flip some permission on or something maybe?

 

 

Please note, this is a test version of mesa for the initial evaluation of the work, some of the functions do not work in it and there may be bugs.

With x11, the system works more stably, but the test results are lower than in gnome+wayland.

 

 

 

Link to comment
Share on other sites

I understand the Mesa drivers are development and there may be bugs. 

To be clear, I'm not getting any video out on USB-C at all. Even during the boot sequence, before the mesa drivers are loaded. I get output for other Armbian images, just not the one I've tested above. 

 

Would that still be due to mesa? 

Link to comment
Share on other sites

22 часа назад, threz_ сказал:

I'm not getting any video out on USB-C at all. Even during the boot sequence, before the mesa drivers are loaded. I get output for other Armbian images, just not the one I've tested above. 

I don't have such testing equipment. I have no idea what's wrong with him.

 

 

Ver 20230421-current - update pancsf.

Link to comment
Share on other sites

Test version 20230421-EDK2-EFI with support for system startup control on a monitor screen with a keyboard, as on a regular PC.

Please note, this is a test version and bugs are possible. The process of starting the system before the image appears on the screen may take 10-30 seconds (depends on the speed of the SD card).

Link to comment
Share on other sites

15 часов назад, waltercool сказал:

Any way to share the source code containing the dts and changes applied into kernel 6.2?

All the sources from which these images are assembled (including the kernel) are freely available in my git.

 

11 часов назад, TheFlash сказал:

Are those the official images wrapped up with kernel 6.2?

The images from this topic are not related to the current official build system (the new official build system is broken).

Link to comment
Share on other sites

Ok, so there are unofficial armbian builds with kernel 6.2. Sorry, i`am an early linux user and OPi5 is my first SBC. I have some docker containers on an NVME. Can i install one of your images on microsd without messing with the current bootloader. Will they work with the current bootloader?. 

 

Thanky You for your hard work!

Link to comment
Share on other sites

21 минуту назад, TheFlash сказал:

Will they work with the current bootloader?. 

Try. Starting from an SD card does not affect the installed system (if you yourself do not manually run special procedures for installing\replacing the system on NVMe\MTD). If you are lucky and your current u-boot is able to work with normal systems, the system will work from an SD card.

Link to comment
Share on other sites

Thanks for the test builds balbes150, currently testing 'Armbian_23.04_Orangepi5_lunar_current_6.2.0_gnome_desktop' build, is there a way to enable/install the mali-g610-firmware & rockchip-multimedia-config packages on Lunar to enable 3D acceleration? (Could only find the repo for Jammy).

 

Thanks.

Link to comment
Share on other sites

20.05.2023 в 15:25, mrbishi сказал:

on Lunar to enable 3D acceleration?

 

20.05.2023 в 15:25, mrbishi сказал:

Armbian_23.04_Orangepi5_lunar_current_6.2.0_gnome_desktop

 

 

Ver 20230526-edge kernel 6.4-rc3 (HDMI not works).

Link to comment
Share on other sites

03.06.2023 в 20:32, Jean-Philippe сказал:

Is it just the upstream git or are there any patches for pancsf?

Build from GIT without patches.

 

11 часов назад, Дмитрий Батин сказал:

I have a question - do you have any success with build mpv \ ffmpeg with that board, that can support play 4k hdr video?

No

Link to comment
Share on other sites

Ver 20230609-edge (use u-boot) kernel 6.4-rc5 (no HDMI)

20230609-EDK2-EFI-edge kernel 6.4-rc5 - HDMI work only EDK2 (grub), HDMI in system not work

 

 

root@192.168.1.16's password: 
  ___  ____  _   ____  
 / _ \|  _ \(_) | ___| 
| | | | |_) | | |___ \ 
| |_| |  __/| |  ___) |
 \___/|_|   |_| |____/ 
                       
Welcome to Armbian 23.04 Lunar with bleeding edge Linux 6.4.0-rc5-media

No end-user support: built from trunk

System load:   13%           	Up time:       5 min	
Memory usage:  2% of 7.76G  	IP:	       192.168.1.16
CPU temp:      37°C           	Usage of /:    51% of 3.4G   	
RX today:      5.4 KiB  	

[ 29 security updates available, 34 updates total: apt upgrade ]
Last check: 2023-06-09 09:18

[ General system configuration (beta): armbian-config ]

Last login: Fri Jun  9 12:18:35 2023
root@orangepi5:~# neofetch 
                                 root@orangepi5 
                                 -------------- 
      █ █ █ █ █ █ █ █ █ █ █      OS: Armbian (23.04) aarch64 
     ███████████████████████     Host: Orange Pi 5 
   ▄▄██                   ██▄▄   Kernel: 6.4.0-rc5-media 
   ▄▄██    ███████████    ██▄▄   Uptime: 5 mins 
   ▄▄██   ██         ██   ██▄▄   Packages: 549 (dpkg) 
   ▄▄██   ██         ██   ██▄▄   Shell: bash 5.2.15 
   ▄▄██   ██         ██   ██▄▄   Terminal: /dev/pts/0 
   ▄▄██   █████████████   ██▄▄   CPU: (8) 
   ▄▄██   ██         ██   ██▄▄   Memory: 193MiB / 7943MiB 
   ▄▄██   ██         ██   ██▄▄
   ▄▄██   ██         ██   ██▄▄                           
   ▄▄██                   ██▄▄                           
     ███████████████████████
      █ █ █ █ █ █ █ █ █ █ █

root@orangepi5:~# lspci 
0004:40:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01)
0004:41:00.0 Non-Volatile memory controller: Sandisk Corp PC SN520 NVMe SSD (rev 01)
root@orangepi5:~# fdisk -l
Disk /dev/ram0: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram4: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram5: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram6: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram7: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram8: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram9: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram10: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram11: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram12: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram13: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram14: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram15: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram0: 3.88 GiB, 4164530176 bytes, 1016731 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mtdblock0: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 209E9F6E-F3DE-4E2D-9674-F497A9BE8D63

Device           Start   End Sectors  Size Type
/dev/mtdblock0p1    64  7167    7104  3.5M Linux filesystem
/dev/mtdblock0p2  7168  7679     512  256K Linux filesystem
/dev/mtdblock0p3  7680  8063     384  192K Linux filesystem
/dev/mtdblock0p4  8064  8127      64   32K Linux filesystem
/dev/mtdblock0p5  8128  8191      64   32K Linux filesystem
/dev/mtdblock0p6  8192 16383    8192    4M Linux filesystem
/dev/mtdblock0p7 16384 32734   16351    8M Linux filesystem


Disk /dev/nvme0n1: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: WDC PC SN520 SDAPMUW-128G-1101          
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x027e8210

Device         Boot     Start       End   Sectors  Size Id Type
/dev/nvme0n1p1 *         2048 208058367 208056320 99.2G 83 Linux
/dev/nvme0n1p2      208058368 250068991  42010624   20G 82 Linux swap / Solaris


Disk /dev/sda: 3.7 GiB, 3967811584 bytes, 7749632 sectors
Disk model: Silicon-Power4G 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: BFDA5BCE-6452-AB45-9B78-7749AD770D18

Device     Start     End Sectors  Size Type
/dev/sda1  32768 7340032 7307265  3.5G Linux filesystem


Disk /dev/zram1: 50 MiB, 52428800 bytes, 12800 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

 

Link to comment
Share on other sites

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines