hegge

Hi, I just found the problem: the board has just a green led - no red one and no blue one, so the line (117) echo heartbeat >/sys/class/leds/*red*/trigger 2>/dev/null || echo heartbeat >/sys/class/leds/*blue*/trigger 2>/dev/null fails. After I changed it to echo heartbeat >/sys/class/leds/*green*/trigger 2>/dev/null || echo heartbeat >/sys/class/leds/*red*/trigger 2>/dev/null || echo heartbeat >/sys/class/leds/*blue*/trigger 2>/dev/null it works like a charme: rebooted and not ran again. Thanks again, hegge @edit: After the reboot the green led heartbeat blinking is gone - is this the aim?

Hi again, after I changed the first lines of /etc/init.d/firstrun to #!/bin/bash -x exec &>>/var/log/firstrun.log the firstrun script works again and gives an output to /var/log/firstrun.log: + '[' Xstart '!=' Xstart ']' + export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin + PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin + cat ++ awk '-F ' '/^MemTotal/ {print $2}' ++ apt-cache policy ramlog ++ grep Installed + chmod +x /tmp/create_swap.sh + main + check_prerequisits + for needed_tool in fdisk parted partprobe resize2fs + which fdisk + for needed_tool in fdisk parted partprobe resize2fs + which parted + for needed_tool in fdisk parted partprobe resize2fs + which partprobe + for needed_tool in fdisk parted partprobe resize2fs + which resize2fs + collect_informations ++ uname -r ++ sed 's/\([0-9]\+\.[0-9]\+\)\..*/\1/' + CURKERNE=4.5 ++ lsb_release -cs + DISTRIBUTION=jessie ++ awk '/Hardware/ {print $3}' + HARDWARE=Allwinner + '[' -f /proc/device-tree/model ']' ++ awk '/Hardware/ {print $4}' + HARDWARE=sun7i + case ${DISTRIBUTION} in ++ findmnt / ++ awk '-F ' '/\/dev\// {print $2"\t"$3}' + ROOTFS='/dev/mmcblk0p1 ext4' + set /dev/mmcblk0p1 ext4 + root_partition=/dev/mmcblk0p1 + rootfstype=ext4 + set -e + [[ ext4 == \e\x\t\4 ]] + [[ ! -f /root/.no_rootfs_resize ]] + display_alert 'Resizing root filesystem.' + '[' jessie == wheezy ']' + '[' jessie == jessie ']' + echo -e '[\e[0;32m OK \x1B[0m] Resizing root filesystem.' + do_expand_rootfs ++ lsblk -idn -o NAME ++ grep -w mmcblk0 + DEVICE=/dev/mmcblk0 + '[' /dev/mmcblk0 = /dev/ ']' ++ echo /dev/mmcblk0 ++ sed 's:/:\\\/:g' + QUOTED_DEVICE='\/dev\/mmcblk0' ++ grep -c mmcblk0p /proc/partitions + PARTITIONS=1 ++ tail -1 ++ cut -d: -f2 ++ parted /dev/mmcblk0 unit s print -sm ++ sed s/s// + PARTSTART=32768 ++ tail -1 ++ parted /dev/mmcblk0 unit s print -sm ++ head -3 ++ cut -d: -f3 ++ sed s/s// + PARTEND=31438847 + STARTFROM=31438848 + [[ 1 == 1 ]] + STARTFROM=32768 + '[' -f /root/.rootfs_resize ']' ++ parted /dev/mmcblk0 unit s print -sm ++ awk -F: '/^\/dev\/mmcblk0/ {printf ("%0d", $2 / ( 1024 / $4 ))}' + CAPACITY=15719424 + '[' 15719424 -lt 4000000 ']' + fdisk /dev/mmcblk0 + echo d + echo 1 + echo n + echo p + echo + echo 32768 + echo + echo w 1: unknown command Re-reading the partition table failed.: Device or resource busy + true + s=0 + fsck -f /dev/mmcblk0p1 + true + partprobe /dev/mmcblk0 + resize2fs /dev/mmcblk0p1 ++ awk '/\// {print $(NF-2)}' ++ df -hm / + FREESIZE=13655 + [[ jessie == \w\h\e\e\z\y ]] + [[ 0 != \0 ]] + [[ 13655 -lt 152 ]] + return 0 + display_alert 'Starting 128Mb emergency swap area creation.' + '[' jessie == wheezy ']' + '[' jessie == jessie ']' + echo -e '[\e[0;32m OK \x1B[0m] Starting 128Mb emergency swap area creation.' + display_alert 'Starting SSH keys recreation.' + '[' jessie == wheezy ']' + '[' jessie == jessie ']' + echo -e '[\e[0;32m OK \x1B[0m] Starting SSH keys recreation.' + touch /tmp/firstrun_running + '[' Xsun7i = Xsun8i -o Xsun7i = Xsun7i ']' + autodetect_sunxi + /tmp/create_swap.sh + echo heartbeat /etc/init.d/firstrun: line 117: /sys/class/leds/*red*/trigger: No such file or directory + echo heartbeat /etc/init.d/firstrun: line 117: /sys/class/leds/*blue*/trigger: No such file or directory I hope you can find the bug, since the problem with recreated ssh keys on every reboot is also back now... Thanks again in advance, hegge

...ou sry, I just noticed there was thrown an error: [FAILED] Failed to start LSB: PLEASE BE PATIENT AND DO NOT DISTURB UNTIL FIRST REBOOT... systemctl -l status firstrun.service gives: â— firstrun.service - LSB: PLEASE BE PATIENT AND DO NOT INTERRUPT THE FIRST REBOOT Loaded: loaded (/etc/init.d/firstrun) Active: failed (Result: exit-code) since Mon 2016-05-02 06:23:42 CEST; 8min ago Process: 1137 ExecStart=/etc/init.d/firstrun start (code=exited, status=127) May 02 06:23:42 lamobo-r1 firstrun[1137]: + exec 2 May 02 06:23:42 lamobo-r1 firstrun[1137]: /etc/init.d/firstrun: line 2: exec: 2: not found May 02 06:23:42 lamobo-r1 systemd[1]: firstrun.service: control process exited, code=exited status=127 May 02 06:23:42 lamobo-r1 systemd[1]: Failed to start LSB: PLEASE BE PATIENT AND DO NOT INTERRUPT THE FIRST REBOOT. May 02 06:23:42 lamobo-r1 systemd[1]: Unit firstrun.service entered failed state. Tyvm, hegge

...after replacing the lines you order I don't have to remove the ssh key. And it's nothing inside your /var/log/firstrun.log... @edit that's the first lines looks like #!/bin/bash -x exec 2 >>/var/log/firstrun.log ### BEGIN INIT INFO # Provides: firstrun # Required-Start: $all # Required-Stop: # Should-Start: armhwinfo # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: PLEASE BE PATIENT AND DO NOT INTERRUPT THE FIRST REBOOT # Description: Something needs to be done when is # starting at first time. # regenerate ssh host key ### END INIT INFO in case I've made a mistake...

Hi, thank you so much for your replies... That's the url given by sudo armbianmonitor -u http://sprunge.us/QTUX Hope that helps... @edit: all is working fine now except this messages and having to delete ssh keys anytime I rebooted. Kind regards and tyvm again, hegge

...it's Armbian_5.10_Lamobo-r1_Debian_jessie_4.5.2.raw, I had the same behavior with Armbian_5.10_Lamobo-r1_Debian_jessie_3.4.112.raw... Thank you, hegge

Hi, how can I disable the post install scripts? On every reboot I get following messages: Starting LSB: Armbian gathering informations about hardware. Starting LSB: PLEASE BE PATIENT AND DO NO DISTURB UNTIL FIRST REBOOT... Resizing root filesystem. Starting 128MB emergency swap area creation. Starting SSH keys recreation. So I have to delete also my ssh key when I want to connect via ssh on every reboot... Thanks in advance, hegge

Hi, I just want to report back: I installed the vanilla version and now all works fine. Thank you very very much again, hegge

Tyvm master igor for the fast reply. The linked hostapd works but after I can't connect to it I tried to use the other driver with: make ARCH=arm sudo make install After reboot i get 3 [FAILED] Failed to start Load kernel Modules and a [DEPEND] Dependency failed for netfilter persistent configuration. after the first one. When it's ready, lsmod shows that 8192cu is loaded - and modinfo 8192cu shows version 3.3.2 and driver file is in the ...wireless/rtl8192cu/ directory instead of ...wireless/ where the compiled driver is. That one should be blacklisted, or?! The bridged LAN ports also doesnt work anymore... When I want to use kernel 4.5.2 I have to switch to vanilla with wget -q -O - http://upgrade.armbian.com | bash right? Thank you so much again...

Hi again, with 5.10 jessie wondershaper seems to work but now I've got problems running wlan in ap mode: http://forum.armbian.com/index.php/topic/1096-wlan-ap/ Another strange behavior is ssh key seems to change on every reboot - I always have to remove the old key to connect via ssh again - is there a fix for that? Thanks in advance, hegge

Hi, after I had trouble running wondershaper with wheezy I tried the jessie img for my Lomobo. With this I can't get AP mode running: hostapd-rt /etc/hostapd.conf-rt (which should be correct for the onboard RTL8192CU chip) gives me: Line10: invalid/unknown driver 'rtl871xdrv' With the non rtl hostapd.conf the driver intitalization fails. Can someone help me pls?! Thanks in advance, hegge

Whoohoo, you're great! I'll try 5.1...

Hi, tyvm for your fast reply! Do you know, when this will happen? Would upgrading to jessie do the trick? Is there another solution to priorize network interfaces? Thanks again in advance, hegge

Hi, I just installed ambian 5.0 legacy wheezy on my bpi-r1 but wondershaper wont run: RTNETLINK answers: No such file or directory RTNETLINK answers: Invalid argument We have an error talking to the kernel It seems a module is missing. Can someone help me pls? Thanks in advance, hegge