dante6913

I know, I was just testing panfrost. Gnome without hardware acceleration is a no, but I'm happy that panfrost work is on way

download and install Armbian_20.06.0_Arm-64_focal_current_5.7.2_20200619 from balbes150 #install ubuntu desktop sudo apt update sudo apt install ubuntu-desktop # add mesa master ppa (https://launchpad.net/~oibaf/+archive/u ... cs-drivers) sudo add-apt-repository ppa:oibaf/graphics-drivers sudo apt upgrade #Then set panfrost drive in enviroment sudo sh -c "echo 'PAN_MESA_DEBUG=bifrost' >> /etc/environment" #reboot sudo reboot #after boot set in the GDM wayland and panfrost should be working

I installed ubuntu focal minimal then ubuntu desktop, booted in wayland followed the above guide and hardware acceleration works until crashes in my x86 air P3. This is the earlier support of panfrost, so I see bright feature for amlogic s905x3 specially when vdec working is finished

Saw this at Collabora site "Michal Lazo: Jun 15, 2020 at 03:17 PM I have Odroid C4 SBC And I have armbian build of ubuntu 20.04 with mesa master (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) I also added PAN_MESA_DEBUG=bifrost to /etc/environment And it looks like ubuntu desktop is wokring There are some glitches with ubuntu settings (gtk) but glmark2-es-wayland is working Nice job!!!" My x96 air didn't yet arrive, can any one try this?

sudo apt-get install libgles2-mesa-dev=20.1.0-1

To enable lima on debian you have to use this script https://packagecloud.io/install/repositories/zhangn1985/mesa/script.deb.sh to install mesa on debian, then edit your xorg as you do in ubuntu The crashes that I had in ubuntu happened when I had to click two time on a icon. The script only works with debian buster, it will add a repository then you have to sudo apt install mesa

Yes I know tha hardware accelaration should be provided from meson-vdec that I think that is allready in the kernel 5.7. But until now no one could provied a away to make it work.

But do you have hardware video acceleration with mpv? I tried ubuntu focal with lima, but I felt it was heavy, and had a lot o crashes so I'm going to change to debian buster an see how will go

I will try tonight with debian kernel 5.7 r6 with lima hardware acceleration. Just a question did you manage to have hardware video (decoding) acceleration with kodi?(not GUI with lima but video acceleration)

I tried mpv with vo=gpu opengl-pbo hwdec=auto With Armbian_20.05.4_Arm-64_bullseye_current_5.7.0-rc5_desktop_20200514 but didn't have no luck video doesn't play. Can you please tell us, please, how to get hardware decoding?

Ok, Is working fine ODROIDC2-UBOOT-CONFIG did the trick in all configuration. Thanks balbes150 for all your time

Ok thanks

On your image there are these files boot.ini and boot-emmc.ini that have the key string as ODROIDN2-UBOOT-CONFIG should I modify Them to ODROIDC2-UBOOT-CONFIG?

you're damn right, since the beginning I had this error

thanks, when I'm back home I will try it

Just to be clear? The boot.ini file to be replace is the one from the android in the emmc?

Thanks balbes150, I'm going to try when I'm home. Now I am at my working place (lunnch time). I will feed back the result.

I tried an android image on a sd (fresh install) an armbian from an usb but that failed too. That why I'm thinking that maybe I have some issue with the hardware that doesn't let me use multiboot. But as I said thats very strange because I was able to boot with android in the emmc and armbian in usb one time. But after reboot I couldn't boot anymore. So if I can't multiboot maybe I can install your ambian image on my emmc

Android 6 in emmc and have an sd and usb. Last Sunday I tried multiboot with usb with boot.ini of the android DROIDC2-UBOOT-CONFIG usb start fatload usb 0 1020000 s905_autoscript autoscr 1020000 Managed to bootone time but after that allways failled to boot

armbian bullsyey on the c2. I'm following your c1 sub forum, I see that you made some changes on the boot.ini from the experimental images. I was thinking trying this changes on my C2. I know that they are diferent systems, but I am so frustated that I'm not able to multiboot that I'm willing to try anything.

Hi balbes150 I wasn't able to start multiboot even with the same usb configuration that I before had for a short period sucess . I'm starting to think tha I have some issue with my hardware. So, I would like to ask you if is possible to boot your images without multiboot? Thanks

tried now with an old usb 2 but got the same result. Maybe is time to stop and try it another day. I'm worry about the amount of time that I have taken from you. Thank you for everything

DROIDC2-UBOOT-CONFIG usb start fatload usb 0 1020000 s905_autoscript autoscr 1020000 fatload usb 1 1020000 s905_autoscript autoscr 1020000 fatload usb 2 1020000 s905_autoscript autoscr 1020000 fatload usb 4 1020000 s905_autoscript autoscr 1020000 # Resolution Configuration # 'hdmimode' must be one of below to configure display resolution within # supported by your TV or monitor. # Symbol | Resolution # ----------------------+------------- # "480x320p60hz" | 480x320 Progressive 60Hz # "480p60hz" | 720x480 Progressive 60Hz # "576p50hz" | 720x576 Progressive 50Hz # "720p60hz" | 1280x720 Progressive 60Hz # "720p50hz" | 1280x720 Progressive 50Hz # "1080p60hz" | 1920x1080 Progressive 60Hz # "1080p50hz" | 1920x1080 Progressive 50Hz # "1080p30hz" | 1920x1080 Progressive 30Hz # "1080p24hz" | 1920x1080 Progressive 24Hz # "1080i60hz" | 1920x1080 Interlaced 60Hz # "1080i50hz" | 1920x1080 Interlaced 50Hz # "2160p60hz" | 3840x2160 Progressive 60Hz # "2160p50hz" | 3840x2160 Progressive 50Hz # "2160p30hz" | 3840x2160 Progressive 30Hz # "2160p25hz" | 3840x2160 Progressive 25Hz # "2160p24hz" | 3840x2160 Progressive 24Hz # "2160p60hz420" | 3840x2160 Progressive 60Hz YCbCr 4:2:0 # "2160p50hz420" | 3840x2160 Progressive 50Hz YCbCr 4:2:0 # "640x480p60hz" | 640x480 Progressive 60Hz # "800x480p60hz" | 800x480 Progressive 60Hz # "800x600p60hz" | 800x600 Progressive 60Hz # "1024x600p60hz" | 1024x600 Progressive 60Hz # "1024x768p60hz" | 1024x768 Progressive 60Hz # "1280x800p60hz" | 1280x800 Progressive 60Hz # "1280x1024p60hz" | 1280x1024 Progressive 60Hz # "1360x768p60hz" | 1360x768 Progressive 60Hz # "1440x900p60hz" | 1440x900 Progressive 60Hz # "1600x900p60hz" | 1600x900 Progressive 60Hz # "1600x1200p60hz" | 1600x1200 Progressive 60Hz # "1680x1050p60hz" | 1680x1050 Progressive 60Hz # "1920x1200p60hz" | 1920x1200 Progressive 60Hz # "2560x1080p60hz" | 2560x1080 Progressive 60Hz # "2560x1440p60hz" | 2560x1440 Progressive 60Hz # "2560x1600p60hz" | 2560x1600 Progressive 60Hz # "3440x1440p60hz" | 3440x1440 Progressive 60Hz setenv hdmimode "1080p60hz" setenv rootopt "root=/dev/mmcblk0p2 rw init=/init rootwait" setenv consoleopt "console=ttyS0,115200" setenv androidopt "androidboot.hardware=odroidc2 androidboot.serialno=${fbt_id#}" setenv logoopt "osd1,loaded,${fb_addr},${hdmimode}" setenv selinuxopt "androidboot.selinux=disabled" # HDMI/DVI Mode Configuration # This will enforce the signal type of display # "hdmi" - For HDMI interface # "dvi" - For DVI interface setenv vout_mode "hdmi" # Display Auto Detection # "false" or "true" setenv display_autodetect "true" # HPD enable/disable option setenv disablehpd "false" # Overscan offset configuration # All offsets are zero and can be tuned by manual or ODROID Utility setenv overscan_top "0" setenv overscan_left "0" setenv overscan_bottom "0" setenv overscan_right "0" setenv led_onoff "on" suspend_hdmiphy=0 # Force HDMI to use RGB colorspace regardless of TV request setenv hdmi_forcergb "0" # Disabled # setenv hdmi_forcergb "1" # Enabled # max cpu frequency in dvfs table / in MHz unit # setenv max_freq "2016" # 2.016GHz # setenv max_freq "1944" # 1.944GHz # setenv max_freq "1920" # 1.920GHz # setenv max_freq "1896" # 1.896GHz # setenv max_freq "1752" # 1.752GHz # setenv max_freq "1680" # 1.680GHz # setenv max_freq "1656" # 1.656GHz # setenv max_freq "1536" # 1.536GHz setenv max_freq "1536" # max cpu-cores # setenv maxcpus "1" # setenv maxcpus "2" # setenv maxcpus "3" setenv maxcpus "4" # disable vu7 setenv disable_vu7 "false" # invert touch screen x,y setenv touch_invert_x "false" setenv touch_invert_y "false" # gpio power key : J2 (2x20) Pin#35, GPIOY.BIT3 #setenv gpiopower "214" # usb timing tweak setenv usbmulticam "false" setenv hdmitx "hdmitx=${cecconfig}" if test "${hdmi_forcergb}" = "1"; then setenv hdmitx "hdmitx=forcergb"; fi if test "${display_autodetect}" = "true"; then usb pwren; hdmitx edid; fi if test "${hdmimode}" = "custombuilt"; then setenv cmode "modeline=${modeline}"; fi # Enable backlight_pwm # disable : backlight "no" # ODROID-VU5/7 : backlight "yes" # ODROID-VU8 : backlight "invert" setenv backlight_pwm "no" setenv test_mt_vid "0000" setenv test_mt_pid "0000" showddrclk setenv bootargs "${rootopt} ${consoleopt} hdmimode=${hdmimode} ${cmode} ${hdmitx} vout=${vout_mode} disablehpd=${disablehpd} logo=${logoopt} ${androidopt} ${selinuxopt} suspend_hdmiphy=${suspend_hdmiphy} led_onoff=${led_onoff} max_freq=${max_freq} maxcpus=${maxcpus} disable_vu7=${disable_vu7} touch_invert_x=${touch_invert_x} touch_invert_y=${touch_invert_y} usbmulticam=${usbmulticam} gpiopower=${gpiopower} backlight_pwm=${backlight_pwm} ddrclock=${ddrclock} test_mt_pid=${test_mt_pid} test_mt_vid=${test_mt_vid}" save showlogo ${hdmimode} #usb pwren movi read dtb 0 ${dtbaddr} # load kernel from vat or boot partition. movi read boot 0 ${loadaddr} #fatload mmc 0:1 ${loadaddr} Image_android booti ${loadaddr} - ${dtbaddr}

LINUX=/zImage INITRD=/uInitrd # rk-3399 #FDT=/dtb/rockchip/rk3399-rock-pi-4.dtb #FDT=/dtb/rockchip/rk3399-nanopc-t4.dtb #APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff1a0000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 # rk-3328 #FDT=/dtb/rockchip/rk3328-box-trn9.dtb #FDT=/dtb/rockchip/rk3328-box.dtb #APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff130000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 # aw h6 #FDT=/dtb/allwinner/sun50i-h6-tanix-tx6.dtb #APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 #APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 mem=2048M video=HDMI-A-1:e # aml s9xxx #FDT=/dtb/amlogic/meson-g12a-x96-max-no-cvbs.dtb #FDT=/dtb/amlogic/meson-g12b-ugoos-am6-no-cvbs.dtb FDT=/dtb/amlogic/meson-gxbb-odroidc2.dtb APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

Yes same is hapenig here, but just boots in android, No luck with DROIDC2-UBOOT-CONFIG usb start fatload usb 0 1020000 s905_autoscript autoscr 1020000 fatload usb 1 1020000 s905_autoscript autoscr 1020000 fatload usb 2 1020000 s905_autoscript autoscr 1020000 fatload usb 4 1020000 s905_autoscript autoscr 1020000 Going to try another usb stick