• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map





Everything posted by Slackstick

  1. Nice work, thank you! Great performance on the OPi PC where I tested. One problem: I can set the display resolution from UHD to Full HD. However, after next boot it is UHD again. Same with when I change resizing windows with frame to resizing directly. After reboot it is still with frame.
  2. I also had issues with mainline kernel an Allwinner (H3 and _H5). If your monitor has more than one HDMI input, tray the other ones. It helped for me.
  3. Glad I am not crazy :-) With current mainline, moving of the terminal window is very fast. Moving of any other window with same size is quite slow.
  4. Update: Changed to current nightly. Read that one HDMI input of my monitor is version 2.0 while the other is 1.4 changed the input sockets on my monitor and voila, display shows up in 4k resolution Thanks all!
  5. Welcome message for PC2 is: Welcome to ARMBIAN 5.27.170529 nightly Ubuntu 16.04.2 LTS 4.11.1-sun50iw2 Kernel is: Linux orangepipc2 4.11.1-sun50iw2 #29 SMP Sun May 28 03:59:44 CEST 2017 aarch64 aarch64 aarch64 GNU/Linux Don't know how to get u-boot version, but install is from nightly 170529. BTW, crappy OPi distribution showed a picture, so hardware should be o.k.
  6. Hello, installed nightly image on OPI PC 2. I get a black monitor saying "no signal" and screen is black. But it does not go into sleep mode. Dmesg output is : [ 1.273359] simple-framebuffer 7e05c000.framebuffer: framebuffer at 0x7e05c000, 0x1fa4000 bytes, mapped to 0xffff00000a000000 [ 1.273367] simple-framebuffer 7e05c000.framebuffer: format=x8r8g8b8, mode=3840x2160x32, linelength=15360 [ 1.420280] Console: switching to colour frame buffer device 480x135 [ 1.566153] simple-framebuffer 7e05c000.framebuffer: fb0: simplefb registered! AFAIK simple-framebuffer uses a framebuffer already initialized by the bootloader. So I suppose parameters between both don't match. Same problem with OPI PC and mainline. Is there a way to get hdmi output? Thanks.
  7. This is from old dmesg. Of course, I tested mode 28, but mode 10 is also significantly slower than before. And with significantly I mean I which to only move the frame of the window and not the complete window. [ 1.830076] [DISP] disp_device_attached_and_enable,line:159:attched ok, mgr0<-->device0, type=4, mode=10
  8. Monitor and display setting say it is still 1080P60 (and it definitely is 1080). Same as before. root@orangepipc:/lib/modules/3.4.113-sun8i# fbset mode "1920x1080" geometry 1920 1080 1920 1080 32 timings 0 0 0 0 0 0 0 rgba 8/16,8/8,8/0,8/24 endmode also see line: [ 17.951] (--) FBTURBO(0): Virtual size is 1920x1080 (pitch 1920)
  9. Below are the logs. Speed difference is significant. X11SHM even is faster with new version. These two lines of /var/log/Xorg.0.log look suspicious to me: [ 17.987] (II) FBTURBO(0): No sunxi-g2d hardware detected (check /dev/disp and /dev/g2d) [ 17.987] (II) FBTURBO(0): G2D hardware acceleration can't be enabled
  10. From Zadors reply to I learned there is a Video Engine for Video, Mali for 3d and a Display Engine for 2d. I used an old version of armbian on OPi PC (h3disp had no 4k option) . Moving desktop windows was very fast. In current desktop release legacy 3.4.113 moving large windows is very slow. So I guess Display Engine is not working correctly. How can I determine if it works? Mainline version gives me no display at all. Thanks.
  11. Thanks for the information. My recently received WLAN router also does not detect its µSD card. Could this be a batch fault of the socket manufacturer?
  12. Just to inform interested people. I tested mainline nightly release. Monitor switches on shortly without something visible and than goes off with "no signal". Dmesg shows: root@orangepipc:~# dmesg|grep frame [ 3.251293] simple-framebuffer 7e05c000.framebuffer: framebuffer at 0x7e05c000, 0x1fa4000 bytes, mapped to 0xf1c80000 [ 3.251303] simple-framebuffer 7e05c000.framebuffer: format=x8r8g8b8, mode=3840x2160x32, linelength=15360 [ 3.401661] Console: switching to colour frame buffer device 480x135 [ 3.550976] simple-framebuffer 7e05c000.framebuffer: fb0: simplefb registered! fbset shows: root@orangepipc:~# fbset mode "3840x2160" geometry 3840 2160 3840 2160 32 timings 0 0 0 0 0 0 0 rgba 8/16,8/8,8/0,0/0 endmode Legacy works so far, even with 3840x2160 but does not seem to be accelerated out of the box.
  13. Fourdee, Thomas said that "rootmydevice" does not increase security risk at DietPi. Please enlighten me how fixing this function increased security at DietPi. Thanks.
  14. I suppose he wants 4k resolution with OPi. And to answer the question: Current OPis are not capable to deliver 4k output. (I am also waiting for OPis with 4k ...)
  15. When WLAN didn't work on OPI PC, I could connect OPI to x86 PC via Ethernet and X86 PC to WLAN. Since WLAN now works on OPI PC (thanks Igor!), I would like to connect the x86 PC to the OPI PC via Ethernet and let it use Internet. How can this be done? Infos at't help.