IgorS

Members
  • Content Count

    55
  • Joined

  • Last visited

About IgorS

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ubuntu issued mesa 19.2.8, still not working with kernel 5 on H3 an H5
  2. I narrowed a bit the problem. Just mesa packages causing rendering problem, drm packages are ok. So, bad guys are: libegl-mesa0 libegl1-mesa libgbm1 libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libglx-mesa0
  3. In description of this ppa: "Supported architectures: amd64, arm64, i386" and there is problem on 32 bit armhf (H3 i.e.) However, I tryed on H5 (OrangePi PC2, OrangePI Prime) without success. After updating drivers and configuring Xorg, problem remains exactly the same as before.
  4. " you could try to blacklist lima or panfrost. or add 02-driver.conf to /etc/X11/Xorg.conf.d with below " Thanks for that, I know this, but I would like to have accelerated gfx.
  5. I did this. Even newest kernel 5.4.13 works just fine with older mesa version.
  6. Yesterday ubuntu issued updates related to DRM, packages: ii libdrm-amdgpu1:armhf 2.4.99-1ubuntu1~18.04.1 armhf Userspace interface to amdgpu-specific kernel DRM services -- runtime ii libdrm-common 2.4.99-1ubuntu1~18.04.1 all Userspace interface to kernel DRM services -- common files ii libdrm-etnaviv1:armhf 2.4.99-1ubuntu1~18.04.1 armhf Userspace interface to etnaviv-specific kernel DRM services -- runtime ii libdrm-nouveau2:armhf 2.4.99-1ubuntu1~18.04.1 armhf Userspace interface to nouveau-specific kernel DRM services -- runtime ii libdrm-radeon1:armhf 2.4.99-1ubuntu1~18.04.1 armhf Userspace interface to radeon-specific kernel DRM services -- runtime ii libdrm2:armhf 2.4.99-1ubuntu1~18.04.1 armhf Userspace interface to kernel DRM services -- runtime ii libegl-mesa0:armhf 19.2.1-1ubuntu1~18.04.1 armhf free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:armhf 19.2.1-1ubuntu1~18.04.1 armhf transitional dummy package ii libgbm1:armhf 19.2.1-1ubuntu1~18.04.1 armhf generic buffer management API -- runtime ii libgl1-mesa-dri:armhf 19.2.1-1ubuntu1~18.04.1 armhf free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:armhf 19.2.1-1ubuntu1~18.04.1 armhf transitional dummy package ii libglapi-mesa:armhf 19.2.1-1ubuntu1~18.04.1 armhf free implementation of the GL API -- shared library ii libglx-mesa0:armhf 19.2.1-1ubuntu1~18.04.1 armhf free implementation of the OpenGL API -- GLX vendor library After updating, my OrangePiPlus 2E with kernel 5.4 starts to have problems with screen rendering. Colors were strange, no bit images were rendered, no transparencies etc. XFCE desktop, but also lightdm login screen was rendered very wrong. Same happened to H5 based boards also, OrangePi Prime and OrangePi PC2. I tried different versions of the kernel, 5.4.6, 5.4.8, 5.4.12, but also 5.3.13, always with the same result. But, on kernel 4.19.xx everything work good. I also tried several versions of 4.19 kernels, an everything had been always ok. Previous version of this libraries: hi libdrm-amdgpu1:armhf 2.4.97-1ubuntu1~18.04.1 armhf Userspace interface to amdgpu-specific kernel DRM services -- runtime hi libdrm-common 2.4.97-1ubuntu1~18.04.1 all Userspace interface to kernel DRM services -- common files hi libdrm-etnaviv1:armhf 2.4.97-1ubuntu1~18.04.1 armhf Userspace interface to etnaviv-specific kernel DRM services -- runtime hi libdrm-nouveau2:armhf 2.4.97-1ubuntu1~18.04.1 armhf Userspace interface to nouveau-specific kernel DRM services -- runtime hi libdrm-radeon1:armhf 2.4.97-1ubuntu1~18.04.1 armhf Userspace interface to radeon-specific kernel DRM services -- runtime hi libdrm2:armhf 2.4.97-1ubuntu1~18.04.1 armhf Userspace interface to kernel DRM services -- runtime hi libegl-mesa0:armhf 19.0.8-0ubuntu0~18.04.3 armhf free implementation of the EGL API -- Mesa vendor library hi libegl1-mesa:armhf 19.0.8-0ubuntu0~18.04.3 armhf transitional dummy package hi libgbm1:armhf 19.0.8-0ubuntu0~18.04.3 armhf generic buffer management API -- runtime hi libgl1-mesa-dri:armhf 19.0.8-0ubuntu0~18.04.3 armhf free implementation of the OpenGL API -- DRI modules hi libgl1-mesa-glx:armhf 19.0.8-0ubuntu0~18.04.3 armhf transitional dummy package hi libglapi-mesa:armhf 19.0.8-0ubuntu0~18.04.3 armhf free implementation of the GL API -- shared library hi libglx-mesa0:armhf 19.0.8-0ubuntu0~18.04.3 armhf free implementation of the OpenGL API -- GLX vendor library don't have any problems with kernel 5. There are my limits of knowledge, so I reverted my boards to kernel 4.19.96 until somebody more experienced find what is going on.
  7. Today I noticed something strange about packages : armbian-config and armbian-firmware (bionic all) Repository version becomes 19.11.3 (via apt update) but self built packages created via kernel build script are version 5.98 Other kernel packages are ok, version 4.19.85 What about this?
  8. I'll take my chances. systemd-tmpfiles just creates and cleans directories based on coniguration, wjhile rest of systemd handles other things. Recently was, as far aa I know disovered security risk in systemd which ie possible to exploit from remote, therefore I wold like to keep last version and I really don't expect troubles because of this. Apt, in other hand cant know nothing about this, bec<use it just keep itts darabase of package versions.
  9. I faced with same problem on OPiplus2e, Ubuntu Xenial, legacy kernel 3.4.113-sun8i. After systemd update to version 229-4ubuntu21.15 program /bin/systemd-tmpfiles which creates tmp directories on start stopped working. For each dir (configured in /usr/lib/tmpfiles.d) message is the same: Failed to validate path /some_path: Bad file descriptor This can be checked by executing as root command: SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create sshd I had old backup from august last year, systemd version 229-4ubuntu21.4 I just copied this file (/bin/systemd-tmpfiles) from backup an everything start to work. What is exactly wrong with it I am not sure.
  10. /proc/driver/rtc ... the system clock RTC may expose itself https://www.kernel.org/doc/Documentation/rtc.txt Obviously kernel dependent Rasperry3b: igor@pi-ubuntu:~$ uname -a Linux pi-ubuntu 4.14.34-v7+ #1110 SMP Mon Apr 16 15:18:51 BST 2018 armv7l armv7l armv7l GNU/Linux igor@pi-ubuntu:~$ ls /proc/driver/rtc /proc/driver/rtc igor@pi-ubuntu:~$ cat /proc/driver/rtc rtc_time : 17:23:12 rtc_date : 2018-04-17 alrm_time : 06:17:00 alrm_date : 2018-04-18 alarm_IRQ : no alrm_pending : no update IRQ enabled : no periodic IRQ enabled : no periodic IRQ frequency : 1 max user IRQ frequency : 64 24hr : yes igor@pi-ubuntu:~$ sudo hwclock [sudo] password for igor: Uto 17 Tra 2018 19:23:48 .676962 seconds OrangePi +2e, legacy kernel: igor@orangepiplus2e:~$ uname -a Linux orangepiplus2e 3.4.113-sun8i #18 SMP PREEMPT Wed Jan 24 22:10:49 CET 2018 armv7l armv7l armv7l GNU/Linux igor@orangepiplus2e:~$ ls /proc/driver/rtc /proc/driver/rtc igor@orangepiplus2e:~$ cat /proc/driver/rtc rtc_time : 06:05:49 rtc_date : 1970-01-09 alrm_time : 11:53:47 alrm_date : 1970-01-08 alarm_IRQ : no alrm_pending : no update IRQ enabled : no periodic IRQ enabled : no periodic IRQ frequency : 1 max user IRQ frequency : 64 24hr : yes igor@orangepiplus2e:~$ sudo hwclock [sudo] password for igor: Tue 17 Apr 2018 07:20:29 PM CEST .904616 seconds igor@orangepiplus2e:~$ OrangePi +2e, mainline kernel: igor@websrv:~$ uname -a Linux websrv 4.14.18-sunxi #24 SMP Fri Feb 9 16:24:32 CET 2018 armv7l armv7l armv7l GNU/Linux igor@websrv:~$ ls /proc/driver/rtc ls: cannot access '/proc/driver/rtc': No such file or directory igor@websrv:~$ sudo hwclock [sudo] password for igor: Tue 17 Apr 2018 07:39:22 PM CEST .052402 seconds
  11. As far as I know there is no way to wake Orange Pi +2e with DS3231 widouth additional circuitry.