DoubleHP

Members
  • Content Count

    41
  • Joined

  • Last visited

About DoubleHP

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Yes, much better: # ls -lha /var/log | grep -e syslog -e message drwxrwxrwx 11 root syslog 660 Oct 19 19:46 . -rwxrwxrwx 1 root root 6.7K Oct 19 20:43 syslog Thanks
  2. I also would perform a sleep 1 or sleep 3 between the two. GPIO handling may take some time, on chipset side. If the pins we talk about are power, or ENABLE pins for the client, even longer time may be required (for internal firmware to startup). Before complaining /dev/video0 does not appear, you need to report the output of dmesg, which gives details about what driver found ... or not. Also check 10 times your sunxi line; many tuto may give wrong addresses; and sometimes even for the same board, different libs may use different numbering schemes ... (had the issue on
  3. # df -h | grep log armbian-ramlog 50M 5.7M 45M 12% /var/log # ls -lha /var/log | grep -e syslog -e message drwxrwxr-x 11 root syslog 660 Aug 11 22:26 . -rw-r----- 1 root root 0 Aug 11 22:15 syslog # systemctl status syslog ● rsyslog.service - System Logging Service Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2019-08-11 22:25:49 CEST; 9min ago Docs: man:rsyslogd(8) http://www.rsyslog.com/doc/ Main PID: 1042 (rsyslogd) CGroup: /system.slice/rsyslog.se
  4. I have completely reinstalled the system. Beh ... I don't understand the difference. image: Armbian_5.75_Orangepione_Debian_stretch_next_4.19.20.7z BOARD_NAME="Orange Pi One" BOARDFAMILY=sun8i VERSION=5.75 PRETTY_NAME="Debian GNU/Linux 9 (stretch)" NAME="Debian GNU/Linux" VERSION_ID="9" VERSION="9 (stretch)" ID=debian Linux opi55 4.19.20-sunxi #5.75 SMP Sat Feb 9 19:02:47 CET 2019 armv7l GNU/Linux # aptitude install rcconf sqlite3 sed awk bc munin-node netcat bc socat facter xinit xserver-xor g-video-all xserver-xorg-video-fbdev xinit xserver-xorg
  5. What's the difference between gtf and cvt ? # gtf 800 480 60 # 800x480 @ 60.00 Hz (GTF) hsync: 29.82 kHz; pclk: 29.58 MHz Modeline "800x480_60.00" 29.58 800 816 896 992 480 481 484 497 -HSync +Vsync cvt 800 480 60 # 800x480 59.48 Hz (CVT) hsync: 29.74 kHz; pclk: 29.50 MHz Modeline "800x480_60.00" 29.50 800 824 896 992 480 483 493 500 -hsync +vsync # xrandr --newmode "800x480_50.00" 24.50 800 824 896 992 480 483 493 497 -hsync +vsync xrandr: Failed to get size of gamma for output default root@orangepione:~# xrandr --addmode "default" 800x480_50.00 xrandr: Faile
  6. Mike R9FT, I have huge doubts ... you claim to be able to make things work with Armbian_5.27.170521_Orangepione_Ubuntu_xenial_dev_4.11.1.7z , but you quote "overlays=spi-spidev" which is a kernel v3 specific option, and ignored by kernels v4 ... After adding sun8i-h3-spi-ads7846.dts , my /dev/fb0 goes away. orangepi zero 4.14.18-sunxi user_overlays=myili9431
  7. At last, I have found something that works, and produces images. In short, use ubuntu_lxde_desktop_OrangePipc_v0_9_1.img . Long story is here: http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=4270&page=1&extra=#pid25253 Edit: I also suceeded with image Armbian_5.75_Orangepione_Ubuntu_xenial_default_3.4.113_desktop.7z
  8. In short, there is no hope to get the camera working on 4.x kernels, because they don't have CSI support ATM. I did not get it to work yet, but, first, grab something using 3.4.x kernel. Spent 3 days on it, still stuck. Also, try gc_2035 ... just in case ... or with dash ... not sure.
  9. dd I am not. Many other people have issues with armbianEnv.txt, and with other files dues to sync issues. After fixing the issue for this file using my scripts, I don't encontour any other issue on oPi0.
  10. Here are core parts of my service: Makefile: TARGET = /etc/cron.d/armbian_env_txt_checker all: install install: $(TARGET) $(TARGET): Makefile bash -c "echo -e \"# file generated by $$(pwd)/$<\" >$@" bash -c "echo -e \"@reboot\troot\t/srv/doublehp/share/armbianEnv_txt/armbianEnv_txt_checker.sh\" >>$@" touch $@ /srv/doublehp/share/armbianEnv_txt/armbianEnv_txt_checker.sh #!/bin/bash [ ! -f /usr/sbin/armbian-config ] && exit 0 sleep 90 ref=/srv/doublehp/share/armbianEnv_txt/armbianEnv.txt.ref file=/boot/
  11. It could by a bad SD, or broken ext4 ... but fact is ... I had this issue on 100% opis, and, only on this specific file. So, yes there is an issue with ext4; but there is an issue with the way this file is modified. This file is savagely altered by boot or initscripts, without any check. To the point the things introduce twice the same line. The issue may even be in how temp files is handled.
  12. Backup the whole system after install. For this specific file, I keep local backups with dates, and diff them after each reboot. When it looks corrupted, the script restaures the last BU.
  13. Hello. Armbian_5.35_Orangepizero_Ubuntu_xenial_default_3.4.113.7z Orange Pi Zero 256 I am rading the bootlog via serial console. [FAILED] Failed to start Load Kernel Modules. See 'systemctl status systemd-modules-load.service' for details. # systemctl status systemd-modules-load.service â systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-modules-load.service.d ââ10-timeout.conf Active: fail
  14. Random tips : - orange pi zero all have 2 SPI bus: one in the main GPIO port, and one for the flash on the back side. If you don't have the plus model, you can unsolder the FLASH and use the port. FLASH is port 1, so, GPIO is port 1. This is very important when you follow tutorials written for other opis - before you start following a tutorial, you need to understand which kernel you are using. If the turial is written after jan 2017, and mentions adding an overlay in armbianEnv.txt, then it's for kernel 4; if the tuto is before feb 2018, and does not mention altering armbianEnv.txt for SP