Myy

Members
  • Content count

    139
  • Joined

  • Last visited

About Myy

  • Rank
    Elite member

Contact Methods

  • Website URL
    https://github.com/Miouyouyou/RockMyy

Profile Information

  • Gender
    Not Telling
  • Interests
    https://pledgie.com/campaigns/33598

Recent Profile Visitors

547 profile views
  1. There is no /dev/watchdog :-(

    Did you enable the Synopsys DesignWare Watchdog Driver ? Check in your .config file if DW_WATCHDOG=m or DW_WATCHDOG=y is present. It's the only watchdog driver compatible with snps,dw-wdt DTB entries. /* drivers/watchdog/dw_wdt.c */ static const struct of_device_id dw_wdt_of_match[] = { { .compatible = "snps,dw-wdt", }, { /* sentinel */ } };
  2. GPU driver?

    Are you sure the driver is installed ? I'll see if I can put a tutorial on how to install Rockchip libmali Debian packages ( https://github.com/rockchip-linux/rk-rootfs-build/tree/master/packages/armhf/libmali ) and their Xserver ( https://github.com/rockchip-linux/rk-rootfs-build/tree/master/packages/armhf/xserver ). Anyway, if you don't care about X11, install the libmali package and launch glmark2-es2-drm. Else, try to install the Xserver first, then the libmali package. The reason being that the official XServer glamor extension does not play well with the Mali drivers, it seems. Could you give the output of glmark2-es2-drm --debug ?
  3. GPU driver?

    Be sure to use the git version of glmark2, as Debian or Ubuntu's version of glmark2 might not have the Udev DRM node selection code. Also, be sure to execute this from a real terminal (CTRL+ALT+F1 if your keyboard is connected to the RK3288 device, or chvt 1 if you're connected through SSH). At last, try this as root in order to be sure that you don't have any issue due /dev/mali0 access rights.
  4. GPU driver?

    Ah ! Good to know ! I'll still keep it in the "To be done or documented" list, though.
  5. GPU driver?

    So, since I received my microSD correctly, I've been able to test the Tinkerboard with my kernels, using an Armbian image as a basis (along with some microSD cards), and I hit one of the bugs that were reported on my Github page. This bug triggers an endless stream or error messages which talk about the DRM driver trying to bind something through the MIPI output and failing. Which is perfectly normal since I didn't plug anything in MIPI (nor HDMI when the bug was triggered). Still, blocked the boot phase. With the original boot.scr, it seemed to trigger a quick reboot continuously, but I don't know if it's because of that bug since I got no output on the serial console when that happened with that configuration (just U-boot output, booting, and U-boot output again, ...). Switching to extlinux/extlinux.conf configuration displayed the error messages, with no reboot. Anyway, the only solution I found to sidestep the issue at the moment is to avoid adding a mipi_dsi node to the Tinkerboard DTS which... removes the MIPI DSI capabilities of the board, yeah... So, basically, I don't apply the patch that adds the mipi_dsi node to the rk3288-tinker.dts for the moment. However, if I get a touchscreen, I'll still try to see if I can enable such functionnality without triggering the same issue.
  6. rk3288 tinker: Ubuntu image not booting

    Is the CPU becoming burning hot during when it hangs ? Your issue sounds like @Tido's issue in the GPU Driver? thread. What kind of display do you use ? And also what is its resolution ?
  7. The VPU driver

    Well, after upgrading to artful, I discovered that the official FFMPEG project pulled a patch provided by LongChair which enable MPP support in FFMPEG directly... So I now need to recompile FFMPEG... On Ubuntu... I'll try to recompile ffmpeg with just h264 support for now.
  8. The VPU driver

    I've ported the new code provided by Ayaka but I still need to test it. Since I'm using a different MiQi, I have to recompile mpp (done) and mpv. The last one is posing several issues since it wants a pretty recent version of FFMPEG. I'll see whether I compile a new local version of ffmpeg of if I upgrade from Ubuntu Xenial to Ubuntu Artful to resolve this issue.
  9. 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.
  10. 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.
  11. 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 https://github.com/rockchip-linux/libmali/raw/rockchip/lib/arm-linux-gnueabihf/libmali-midgard-t76x-r14p0-r1p0-wayland.so -O libmali.so for file_to_link in libGLESv1_CM.so{,.1} libGLESv2.so{,.2} libEGL.so{,.1} libgbm.so{,.1,.1.0.0} libOpenCL.so{,.1,.1.0.0}; do ln -s libmali.so $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.
  12. GPU driver?

    if you type file /home/tido/myy-s/mali/libmali.so what does it return ?
  13. 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 libmali-midgard-t76x-r14p0-r0p0-wayland.so 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-* libmali.so for file_to_link in libGLESv1_CM.so{,.1} libGLESv2.so{,.2} libEGL.so{,.1} libgbm.so{,.1,.1.0.0} libOpenCL.so{,.1,.1.0.0}; do ln -s libmali.so $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 libmali.so. Aren't you glad that these drivers are so easy to install... Yeah I should create a wrapper script for that thing... seriously.
  14. 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.
  15. 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.