Nazar Gerasymchuk

  • Content Count

  • Joined

  • Last visited

About Nazar Gerasymchuk

  • Rank

Profile Information

  • Gender
  • Location
  • Interests
    Programming: C++, Qt, QML, Python. Calligraphy. Sound design.

Contact Methods

  • Website URL

Recent Profile Visitors

555 profile views
  1. @Clum @Memo Here is a link to a script that should do all the job for you: Hope it helps!
  2. Thank you for quick response, @martinayotte > Could be that you mistakenly crossed SDA and SCL ? Checked and re-checked for a lots of times, tried different jumpers and different breadboards. Unfortunately I have no oscilloscope to check if i2c bus is working, but are there any ways to test the bus? E.g.: what does it means if i2cdetect scan takes so much time? Could it signalize something?
  3. I have few of i2c devices that was successfully tested working with RPi Zero W (Tiny RTC, BME280), but no one is visible to NanoPi Neo Air board with Armbian. I can't get it to work on latest few versions of Armbian. As soon as I add i2c0 to overlays there appears two of i2c devices (both silent): $ ls -la /dev/i2c* crw-rw---- 1 root i2c 89, 0 Jan 28 14:58 /dev/i2c-0 crw-rw---- 1 root i2c 89, 1 Jan 28 14:58 /dev/i2c-1 I need to admit that scan itself took quite significant amount of time. $ sudo time i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e
  4. Is there any way to configure alternative sources and/or timeout options and/or any general recommendations?
  5. Good day, What is the best and easiest way to deal with situation: The following packages have unmet dependencies: armbian-config : Depends: debconf-utils but it is not going to be installed Depends: html2text but it is not going to be installed Depends: html2text but it is not going to be installed mc : Depends: mc-data (= 3:4.8.18-1) but it is not going to be installed nfs-kernel-server : Depends: libtirpc1 (>= 0.2.4) but it is not going to be installed Depends: nfs-common (= 1:1.3.4-2.1) but it is not going to b
  6. Customers: for example me and you (I suppose), since we both purchased H3 boards, and its GPU can't be used with mainline. I'm Ok with running closed-sourced or partially open-sourced drivers, but how can I do it on H3 with mainline? If this is possible, I'd like to ask you to share any useful documentation here. Thanks.
  7. @Tido Thank you for your quick answer. I've heard about Lima, and I can see that it is in deep development right now (at least as it is stated on Sunxi site My main confusion came from situation that there are lots of H3 boards that works quite well with mainline kernel, and there is no option to use GPU. from customer side it looks very strange. --- One more (silly) question, what does it means that there is dts already in mainline kernel --
  8. Sorry if this is silly question, but I can't find any straight-forward documentation on this topic. I've seen that Mali drivers was available for older kernel, but what about mainline? Asking this especially in context with this finding -- Maxime Ripard's article "Mali OpenGL support on Allwinner platforms with mainline Linux". Currently on clean Armbian install on NanoPi Neo Air I can't load mali: $ modinfo mali modinfo: ERROR: Module mali not found.
  9. Hello @Igor! I'm ready for testing. Have few of NanoPi Neo Air and will be able to find some spare time for it.
  10. My problem is that each time I try to do anything related to LCD over frame buffer I got next error: ioctl FBIOGET_VSCREENINFO: Inappropriate ioctl for device LCDs (ili9341, st7735s) I'm able to test behave exactly the same way -- every time lighted up white screen, but nothing more. I have NanoPi Neo Air with Armbian (5.59 Nanopiair Debian stretch 4.14.65) on it. All packages in system already updated to latest available versions. Problem remains as on stable kernel, same on nightly build. Currently I have: $ uname -a && cat /etc/issue Linux nanopiair 4.14