• Content count

  • Joined

  • Last visited

About Myy

  • Rank
    Elite member

Contact Methods

  • Website URL

Profile Information

  • Gender
    Not Telling
  • Interests

Recent Profile Visitors

418 profile views
  1. GPU driver?

    Yeah, I only care about the the Direct Rendering Manager system (・ω・`;) Now, I understand everyone requests for a better documentation on how to install and use the Mali user-space binary drivers. This has been asked on my repository too, and I just started and untested draft in the Wiki of my repository, until I find a better way to format and distribute such documentation. Still, I repeat, this is untested for now.
  2. GPU driver?

    Indeed, the DRM tests are VSync'ed by default. So you'll get ~1 FPS/Hz . I got 59 on a cold boot but when using a proper power supply, it stays at 60 for most of the tests, beside crystal bunny and that ugly terrain. Note that the special X server can be installed more easily if you have you use Zesty or Arftul repositories. However, I really doubt that any Armbian people could help you if that patched X Server becomes broken. If I have the time, I'll try, once again, to use plasma-desktop + KWin Wayland/DRM with the Mali drivers and see how it goes... It will probably fail miserably though, with no useful error messages.
  3. GPU driver?

    @Tido Glad you make it through. As always, ugly terrain and crystal bunny are the most GPU intensive operations. I guess that you're screen works at 55Hz ? Anyway, scripting the Mali user-space binary drivers sound nice and all until you realize that, besides wayland (weston only I'd say), DRM (used by almost nobody currently) and fbdev (used only by mediacenter-like distros), they won't be very useful. The X11 ones require a specific X Server, or you'll get a terrific crash when X starts... Anyway, something like : mkdir -p ~/.local/lib cd ~/.local/lib wget -O for file_to_link in{,.1}{,.2}{,.1}{,.1,.1.0.0}{,.1,.1.0.0}; do ln -s $file_to_link; done echo "alias mali_exec LD_LIBRARY_PATH=\$LD_LIBRARY_PATH:`echo ~/.local/lib`" >> ~/.bashrc Might do the trick for now. This is actually untested though. This should add a "mali_exec" command that can be used like this : mali_exec glmark2-es2-drm Providing a Nvidia Optimus bumblebee-like execution mechanism.
  4. GPU driver?

    if you type file /home/tido/myy-s/mali/ what does it return ?
  5. GPU driver?

    If you read this when running glmark2 : GL_RENDERER: Gallium 0.4 on llvmpipe (LLVM 4.0, 128 bits) Then you're not using the Mali user-space binary drivers. You're using CPU-bound renderer provided by Mesa. Now, the user-space binary drivers are a pain in the ass tricky to install, since they require a special snowflake X server from Rockchip. What I'd suggest is to : Create a folder Download from rockchip-linux/libmali repository Copy the file in the folder you created, then open a shell in this folder and type mv libmali-midgard-* for file_to_link in{,.1}{,.2}{,.1}{,.1,.1.0.0}{,.1,.1.0.0}; do ln -s $file_to_link; done LD_LIBRARY_PATH=. glmark2-es2-drm Be sure that your user have read-write access to /dev/mali0. Else the test might also fail. This should recreate all the necessary library file names that are searched by the OpenGL ES 2.x binary and use the instructions stored in Aren't you glad that these drivers are so easy to install... Yeah I should create a wrapper script for that thing... seriously.
  6. GPU driver?

    No, you'll have to : Reinstall the Mali drivers somehow, or get them in a folder and use the LD_LIBRARY_PATH trick. If X11 is currently using the display, you'll have to type : sudo chvt 1 # Equivalent of CTRL+ALT+F1 on a keyboard To reattach the TTY 1, which will provide a non-locked CRTC, since the X11 CRTC, generally attached to TTY 7, is locked by the X11 process for various valid reasons. The binary looks good though.
  7. GPU driver?

    I remember that I compiled it with only doing something like : apt install libjpeg-dev libpng-dev libdrm-dev libgbm-dev libudev-dev libegl1-mesa-dev libgles2-mesa-dev The error message is incorrect. The project only needs libpng 1.2 OR 1.5 OR 1.6. Not all at once. Anyway, no need to compile the required libraries. You should be able to grab them through apt and standard Debian/Ubuntu repositories. Just try to be as generic as possible when searching for the development headers.
  8. GPU driver?

    @Tido What version of glmark2 do you have ? The old versions seemed to have a broken DRM detection system based on some whitelist, that I kind of fixed in the later versions. I highly suggest using the GIT version of glmark2 and uninstalling glmark2 Debian packages for the moment. sudo apt remove glmark2 git clone --depth 1 cd glmark2 ./waf configure --with-flavors=drm-glesv2 ./waf sudo ./waf install glmark2-es2-drm Also, be sure to execute that version from a TTY (Ctrl+ALT+F1 or chvt 1)
  9. GPU driver?

    Now that I have access to my MiQi, here's the /boot/extlinux/extlinux.conf I'm using to boot my kernels : root@miqi:~# cat /boot/extlinux/extlinux.conf label kernel-4.4 kernel /boot/zImage fdt /boot/rk3288-miqi.dtb append earlyprintk console=ttyS2,115200n8 rw root=/dev/mmcblk1p1 rootfstype=ext4 init=/sbin/init Note that I'm not using a /boot partition. Anyway, here's ls -l /boot root@miqi:~# ls -l /boot total 92172 -rw-r--r-- 1 root root 78 May 3 2017 armbianEnv.txt -rw-r--r-- 1 root root 1557 May 3 2017 armbian_first_run.txt -rw-r--r-- 1 root root 129427 May 3 2017 config-4.11.0+ -rw-r--r-- 1 root root 155497 Sep 12 00:36 config-4.13.0-RockMyy-XIII -rw-r--r-- 1 root root 155497 Sep 10 19:44 config-4.13.0-RockMyy-XIII.old -rw-r--r-- 1 root root 156664 Sep 16 07:53 config-4.14.0-rc4-RockMyy-XIV-A-Myy-Reborn -rw-r--r-- 1 root root 156664 Sep 16 07:36 config-4.14.0-rc4-RockMyy-XIV-Myy-Returns -rw-r--r-- 1 root root 156664 Nov 2 09:05 config-4.14.0-rc7-RockMyy-XIV-A-Myy-Reborn -rw-r--r-- 1 root root 125351 Aug 12 17:31 config-4.4.81-rockchip drwxr-xr-x 2 root root 4096 Jun 20 15:42 dtb-4.11.0-rockchip drwxr-xr-x 2 root root 4096 Aug 7 16:50 dtb-4.13.0-rockchip drwxr-xr-x 2 root root 4096 Aug 18 16:49 dtb-4.4.81-rockchip drwxr-xr-x 2 root root 4096 Sep 12 00:26 extlinux -rw-r--r-- 1 root root 4438628 Oct 30 16:10 initrd.img-4.11.4-rockchip -rw-r--r-- 1 root root 4421353 Aug 18 16:55 initrd.img-4.4.81-rockchip drwx------ 2 root root 4096 Jul 16 22:17 lost+found -rw-r--r-- 1 root root 40525 Nov 2 09:05 rk3288-evb-act8846.dtb -rw-r--r-- 1 root root 40922 Nov 2 09:05 rk3288-evb-rk808.dtb -rw-r--r-- 1 root root 37039 Nov 2 09:05 rk3288-fennec.dtb -rw-r--r-- 1 root root 40777 Nov 2 09:05 rk3288-firefly-beta.dtb -rw-r--r-- 1 root root 40769 Nov 2 09:05 rk3288-firefly.dtb -rw-r--r-- 1 root root 41955 Nov 2 09:05 rk3288-firefly-reload.dtb -rw-r--r-- 1 root root 39656 Nov 2 09:05 rk3288-miqi.dtb -rw-r--r-- 1 root root 41029 Jul 18 16:59 rk3288-miqi.dtb.bak -rw-r--r-- 1 root root 39604 Nov 2 09:05 rk3288-popmetal.dtb -rw-r--r-- 1 root root 37310 Nov 2 09:05 rk3288-r89.dtb -rw-r--r-- 1 root root 40289 Nov 2 09:05 rk3288-rock2-square.dtb -rw-r--r-- 1 root root 41026 Nov 2 09:05 rk3288-tinker.dtb -rw-r--r-- 1 root root 39316 Nov 2 09:05 rk3288-veyron-brain.dtb -rw-r--r-- 1 root root 47442 Nov 2 09:05 rk3288-veyron-jaq.dtb -rw-r--r-- 1 root root 47495 Nov 2 09:05 rk3288-veyron-jerry.dtb -rw-r--r-- 1 root root 39921 Nov 2 09:05 rk3288-veyron-mickey.dtb -rw-r--r-- 1 root root 48314 Nov 2 09:05 rk3288-veyron-minnie.dtb -rw-r--r-- 1 root root 45862 Nov 2 09:05 rk3288-veyron-pinky.dtb -rw-r--r-- 1 root root 47270 Nov 2 09:05 rk3288-veyron-speedy.dtb -rw-r--r-- 1 root root 3702224 Sep 12 00:36 -rw-r--r-- 1 root root 3702224 Sep 10 19:44 -rw-r--r-- 1 root root 3781860 Sep 16 07:53 -rw-r--r-- 1 root root 3781964 Sep 16 07:36 -rw-r--r-- 1 root root 3782323 Nov 2 09:05 lrwxrwxrwx 1 root root 23 Oct 30 16:10 uInitrd -> uInitrd-4.11.4-rockchip -rw-r--r-- 1 root root 4438692 Oct 30 16:10 uInitrd-4.11.4-rockchip -rw-r--r-- 1 root root 4421417 Aug 18 16:55 uInitrd-4.4.81-rockchip -rw-r--r-- 1 root root 19873868 Sep 10 19:44 vmlinuz-4.13.0-RockMyy-XIII -rw-r--r-- 1 root root 19897976 Sep 16 07:09 vmlinuz-4.14.0-rc4-RockMyy-XIV-Myy-Returns -rwxr-xr-x 1 root root 8039272 Aug 21 05:05 vmlinuz-4.4.81-rockchip -rwxr-xr-x 1 root root 8167960 Nov 2 09:05 zImage And the motd SSH output : __ __ _ ___ _ | \/ (_)/ _ \(_) | |\/| | | | | | | | | | | | |_| | | |_| |_|_|\__\_\_| Welcome to ARMBIAN 5.30 stable Ubuntu 16.04.2 LTS 4.14.0-rc7-RockMyy-XIV-A-Myy-Reborn System load: 0.52 0.19 0.07 Up time: 0 min Memory usage: 7 % of 2009MB IP: CPU temp: 61°C Usage of /: 27% of 15G [ 0 security updates available, 97 updates total: apt upgrade ] Last check: 2017-11-02 09:08 [ General system configuration: armbian-config ] Last login: Mon Oct 30 16:21:04 2017 from To run a command as administrator (user "root"), use "sudo <command>". See "man sudo_root" for details. Anyway, I still have some issues with the HDMI screen that I have to unplug / plug back sometimes. I'll try to see if adding back some the old DRM patches fix the issue. Here's my modules list btw : root@miqi:~# lsmod Module Size Used by bnep 20480 2 mali_kbase 512000 1 dw_hdmi_i2s_audio 16384 0 dw_hdmi_cec 16384 0 rk_crypto 24576 0 Why is the bnep loaded ? Well, that's a good question ! I have no single idea, since there's no Bluetooth chip integrated into the MiQi, as far as I remember. When launching glmark2, you should get that kind of output : root@miqi:~# glmark2-es2-drm ======================================================= glmark2 2017.07 ======================================================= OpenGL Information GL_VENDOR: ARM GL_RENDERER: Mali-T760 GL_VERSION: OpenGL ES 3.2 v1.r14p0-01rel0-git(966ed26).810f535757d8c9adaaa72f5da29c688e ======================================================= [build] use-vbo=false: FPS: 59 FrameTime: 16.949 ms [build] use-vbo=true:^C FPS: 60 FrameTime: 16.667 ms ======================================================= glmark2 Score: 59 ======================================================= The ^C is due to me hitting CTRL+C. The first batch should be at 59 fps generally, after a cold start.
  10. GPU driver?

    And that's how @TonyMac32 became a SnowMan. Anyway, I guess I'll have to find a Tinkerboard during December, since that clearly needs special testing.
  11. GPU driver?

    The boot went : Tiut ! I guess that you get nothing after that ?
  12. GPU driver?

    Ah, yeah, the boot.scr is the binary file and boot.cmd is the one used to generate it so comment the ramdisk line in the boot.cmd and regenarate the boot.scr... if the kernel doesn't boot of course.
  13. GPU driver?

    Also try to comment the initrd line in the boot.scr if it doesn't boot, just to see if that changes anything...
  14. GPU driver?

    I don't have my MiQi here so I can't paste the extlinux/extlinux.conf I'm using. Still, instead of copying zImage bluntly, you could do cp zImage /boot/Myy-Kernel and then configure your bootloader to boot Myy-Kernel instead of zImage
  15. GPU driver?

    The only thing that *might* generate issues would be the initrd. But I don't think that it would cause the system to not boot and not print anything on the serial output. Now, since you got a working kernel, try to list the modules used by your system, just in case |`・ω・)ノ . Also try to use the rk3288-miniarm.dtb too, since we're sure that it works.