DoubleHP

Members
  • Content Count

    40
  • 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. 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 rPi).
  2. # 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.service └─1042 /usr/sbin/rsyslogd -n Aug 11 22:25:49 opi-06-app-c13 systemd[1]: Starting System Logging Service... Aug 11 22:25:49 opi-06-app-c13 systemd[1]: Started System Logging Service. # ls -lha /var/log.hdd/ | grep -e syslog -e message drwxrwxr-x 11 root syslog 4.0K Aug 11 22:25 . -rw-r----- 1 root root 0 Aug 11 22:15 syslog -rw-r----- 1 root root 28M Mar 4 06:25 syslog.1 -rw-r----- 1 root root 212K Mar 3 06:25 syslog.2.gz -rw-r----- 1 root root 2.9M Mar 2 06:25 syslog.3.gz -rw-r----- 1 root root 1.9M Mar 1 06:25 syslog.4.gz -rw-r----- 1 root root 791K Feb 28 06:25 syslog.5.gz it probably worked at some point ... forgot what I did to break it ...
  3. 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-video-all xserver-xorg-video-fbdev aterm xterm wmaker eterm xfonts-base xserver-xorg x11-utils x11-xserver-utils xinput-calibrator xinput dillo munin-plugins-extra zip # startx & # export DISPLAY=":0.0" # cvt 800 480 50 # 800x480 49.69 Hz (CVT) hsync: 24.70 kHz; pclk: 24.50 MHz Modeline "800x480_50.00" 24.50 800 824 896 992 480 483 493 497 -hsync +vsync # xrandr --addmode "HDMI-1" 800x480_50.00 # 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_60.00" 29.50 800 824 896 992 480 483 493 500 -hsync +vsync # xrandr Screen 0: minimum 320 x 200, current 1280 x 720, maximum 8192 x 8192 HDMI-1 connected primary 1280x720+0+0 (normal left inverted right x axis y axis) 697mm x 392mm 1280x720 60.00*+ 50.00 59.94 1920x1080 60.00 50.00 59.94 1920x1080i 60.00 50.00 59.94 1280x1024 75.02 1440x900 74.98 59.90 1024x768 75.03 70.07 60.00 800x600 72.19 75.00 60.32 56.25 720x576 50.00 720x480 60.00 59.94 640x480 75.00 72.81 60.00 59.94 720x400 70.08 800x480_50.00 49.69 800x480_60.00 (0x6d) 29.500MHz -HSync +VSync h: width 800 start 824 end 896 total 992 skew 0 clock 29.74KHz v: height 480 start 483 end 493 total 500 clock 59.48Hz # xrandr --addmode "HDMI-1" 800x480_60.00 # xrandr -s 800x480_50.00 # xrandr --output HDMI-1 --mode 800x480_60.00 Both last commands work ... do not return error. With the 3.5" LCD, in all 3 cases, I have an image (not fitting edges, but that's offtopic). And now my 19" monitor also works, but with a trick: - run xrandr to have an eye at things - unplug old monitor - run xrandr to have an eye at things, and check that less resolutions are listed (the only ones left are the current one, and the two manually added ones) - plug monitor; it may not produce any image - ask xrandr again to show supported resolutions - run xrandr -s to set any resolution, even the current one, and then, an image will appear. 5" LCD also worked immediately. So, the main difference I can see between the two attemps is the image used, and kernel. 3.4 vs 4.19
  4. 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: Failed to get size of gamma for output default xrandr: cannot find mode "800x480_50.00" # xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1280 x 720, current 1280 x 720, maximum 1280 x 720 default connected 1280x720+0+0 0mm x 0mm 1280x720 0.00* How to addmode 800x480 ? BOARD_NAME="Orange Pi One" Image: Armbian_5.75_Orangepione_Ubuntu_xenial_default_3.4.113_desktop.7z I have a correct image using a 3.5" HDMI LCD (without using GPIO/SPI at all); but when I plug a 5" or 19", they say "no signal". I am surprised by two facts: - pi unable to probe monitors correctly over HDMI - 5" LCD designed for rPi unable to accept a modline the opi sends (a modline that is 100% acceptable for the 3.5").
  5. 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
  6. 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
  7. 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.
  8. 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.
  9. 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/armbianEnv.txt loc="${file}.local" backup="${file}.backup.$(/bin/date +%Y-%m-%d_%H-%M-%S)" broken="${file}.broken.$(/bin/date +%Y-%m-%d_%H-%M-%S)" previous="$("ls" "${file}.backup."* | sort | tail -n1)" # is current file valid ? #cat "$file" | grep -e "overlay_prefix=sun8i-h3" >/dev/null && { cat "$file" | grep -e "rootdev=UUID=" >/dev/null && { #file is good. # create local ref if none [ ! -e "$loc" ] && { cp -a "$file" "$loc" } # create backup if none [ "$previous" = "" ] && { cp -a "$file" "$backup" } diff "$file" "$previous" >/dev/null || cp -a "$file" "$backup" true } || { # File is bad [ -e "$previous" ] && { cp -a "$file" "$broken" cp -a "$previous" "$file" reboot exit 0 } [ -e "$loc" ] && { cp -a "$file" "$broken" cp -a "$loc" "$file" reboot exit 0 } # Fallback on ref ... cp -a "$file" "$broken" cp -a "$ref" "$file" reboot }
  10. 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.
  11. 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.
  12. 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: failed (Result: exit-code) since Sun 2018-12-30 00:20:40 CET; 3min 8s ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 167 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) Main PID: 167 (code=exited, status=1/FAILURE) Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. Warning: systemd-modules-load.service changed on disk. Run 'systemctl daemon-reload' to reload units. # journalctl -f -b _PID=167 -- Logs begin at Sun 2018-12-30 00:20:45 CET. -- Dec 30 00:20:45 opi-06-app-c13 systemd-modules-load[167]: Failed to insert 'xradio_wlan': Connection timed out Dec 30 00:20:45 opi-06-app-c13 systemd-modules-load[167]: Inserted module 'g_serial' Dec 30 00:20:45 opi-06-app-c13 systemd-modules-load[167]: Inserted module 'xradio_wlan' ^C # cat /etc/modules #w1-sunxi #w1-gpio #w1-therm #sunxi-cir xradio_wlan g_serial xradio_wlan If I remove any xradio_wlan, then wlan0 is not available at boot. Is there a way to fix the boot error message, without loosing wlan0 ? Obviously, some one is aware of an issue, because some dev has put the same line twice in modules ...
  13. 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 SPI compatibility, author is using kernel 3. This is critical. - I got adressable LEDs working on both kernels, 3 and 4. Easier on 4. - SPI LCDs work only on kernel 3; I have spend days on kernel 4, just forget them; drivers exist, but they are broken. - con2fbmap is required only on kernel 3 - to get X working, you need to create /etc/X11/xorg.conf.d/99-fbturbo.conf - check your FB number with a command like this: dmesg | grep ili | grep graphics | grep -i fb . I have seen people using 0, 1 and 8. Now, I have ili9486 working perfectly fine ... with image Armbian_5.35_Orangepizero_Ubuntu_xenial_default_3.4.113 (kernel 3.4.113).
  14. What's your distribution and kernel ?