EvIl_DeViL

Hi all, I'm writing this post because I had an issue upgrading my lamobo-r1 from the previous version to the current one (Armbian_5.20_Lamobo-r1_Ubuntu_xenial_4.7.3). On reboot hwclock doesn't start so I get my clock set to epoch, wan doesn't go UP, postfix says "time stamp 2015-11-25 01:40:22 is 1448411826.350146139 s in the future", random says "uninitialized urandom read"... a total mess. As pointed out on some sites, looks like "/etc/init/hwclock.conf" has "start on starting mountall" so failing to mount could cause a failing in hwclock initialization. I also found on bugs.launchpad.net/ubuntu that in recent versions with systemd, mountall became fussy about finding all the devices specified in /etc/fstab so I removed all entries but the sd (which is where the installation boot and reside), even swap and data=writeback option, but I get the same error. I tried updating from a previous backup but got the same issue, so that's not failed upgrade but a consistent issue. Herein I attach a level 7 bootlog but I don't know if it's useful because it would be nicer adding verbosity to mountall and hwclock on start (as of now I don't know how) I have UART access and manually fixing clock and connection allows me to get it working as usual but that's utterly unlovely. I also have a backup to a recent working state so I can make all the tests I need. Thanks all! capture.txt

Hi I have updated to kernel 4.3 armbian 4.6 manually but I still can't boot. I checked a "virgin" flashed sd with armbian, and /sbin/init is a simple file and not a symlink to /lib/systemd/systemd I feel all my hopes flied away once again... kernel_43.txt

yup but everything on *nix could be addressed as critical... even changing the desktop's background XD Anyway I have Ubuntu Trusty on the board and although I have the /sbin/init file it says it's a "shared library (application/x-sharedlib)" and not a symlink to /lib/systemd/systemd which actually doesn't even exists. maybe trusty's using upstart? $/lib/systemd$ ls -l total 536 drwxr-xr-x 8 root root 4096 set 28 13:41 system -rwxr-xr-x 1 root root 50868 set 11 13:35 systemd-hostnamed -rwxr-xr-x 1 root root 54872 set 11 13:35 systemd-localed -rwxr-xr-x 1 root root 177736 set 11 13:35 systemd-logind -rwxr-xr-x 1 root root 21992 set 11 13:35 systemd-multi-seat-x -rwxr-xr-x 1 root root 59032 set 11 13:35 systemd-timedated -rwxr-xr-x 1 root root 165536 set 11 13:35 systemd-udevd did we found the culprit? *_*

Thing is this happened a couple of times yet with this board and I went for the easy way twice; but I don't like when computers win so this time I tried the hard way but without luck. I don't like that out of the blue this board would betray me once more. This time I'll keep my eyes wide open and I'll reboot every install I do to see if the system works and I will find the unholy package.

ok I removed it but no luck. Only thing new is that it came back hanging to *random* It seems strange that there's no log or a way to debug this o.o maybe there's a way to block all the non-vital systemd stuff and adding them back one by one? p.s. I saw you removed the stuff about /etc/bash.bashrc.custom but what's this for? and why that could have helped? newKernel2.txt

No success I unpacked the four *.deb in the root of my sd card following the "How to unbrick the system?" guide. I had the 4.2.0 version and after I unpacked the *.deb and replaced everything I saw the new version is 4.2.2 I also relinked the zImage as stated and boot log confirm that now I'm booting the 4.2.2 I post herein a log with 3 boot: the first is a boot with init=/bin/bash, the second is your fix, the third is the boot after the fix hanging now even before the *random* stuff. newkernel+initbash.txt

@zador 3) I taught maybe the "broken boot" could undo the changes made with the custom booting... who knows I posted a log with loglevel=7 so you can see all the messages. I didn't altered my boot in any way AFAIK. maybe some strange install? (samba, apache, mysql, gparted) But I installed everything from default repository via apt-get or synaptic 4) I found something interesting: https://www.kernel.org/doc/Documentation/serial-console.txt (<- seems pretty official to me ) You can specify multiple console= options on the kernel command line. Output will appear on all of them. The last device will be used when you open /dev/console. So, for example: console=ttyS1,9600 console=tty0 I tried and it works! now I have output echoed on both interfaces so I can plug it via HDMI or TTLSerialUSB without altering the uboot script. @Igor 1) in fact uboot log says "Unknown command 'usb' - try 'help'"... I panicked a little when I read "hit any key to stop autoboot" and nothing happend after I did so XD luckily I had the said adapter. (Remembered a little the old MS "no keyboard found: press f1 to continue...") what kind of datas/configs could I loose if I follow said procedure? could the startup hang be caused by something not related to those /mnt files? (udev, init.d, systemd, video drivers) as always thank you guys! loglevel7.txt

1) that 4 bucks cheap-o ttl serial converter turns out to be one of the best investments I made in the last few years XD 2) woo good hint about the double quotes! I didn't know it and it looks that now my boot args are working... just to clarify: why someone shouldn't double quote boot args by default? 3) I already tried those steps but it looks like my corrupted uboot conf file was bothering the fix. Anyway I repeated the procedure after the boot fix and startup now hangs on [ 4.419814] random: init urandom read with 7 bits of entropy available and doesn't give me the bash shell. 4) is it possible to specify both ttyS0,115200 and tty1 as console (like before kernel starts)? Just to have a little more flexibility... I attached a new boot log got for completeness. Thank you zador. Once again you pointed me in the right direction bootFix_Lamobo_R1.txt

Hi all, Igor: I wanted to say many thank you and congratulate for the awesome job you made with armbian! I have a little big problem: I'm using the BPI-R1 (a.k.a. Lamobo R1 Linux version 4.2.0-sunxi (root@kitchen) (gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-16ubuntu4)) but out of the blue I got the well known problem of the RCP reset to the 1970. I followed the instructions reported here https://github.com/igorpecovnik/lib/issues/111#issuecomment-145634651 but I got some strange issues 1) If I plug my USB keyboard I cannot interrupt the boot process to get a shell before the kernel loads. 2) If I change my boot.cmd and update the boot.scr settings with verbosity=9 and init=/bin/fixme.sh it has no effect; it seems to load a "default/standard" boot.scr located somewhere (even if pre kernel boot says /boot/boot.scr loaded) 3) If I plug my uart/USB adapter I can get a shell, but after I follow the procedure described here https://github.com/igorpecovnik/lib/issues/111#issuecomment-147452433 RTC resets again Strange thing: I don't get the log of the kernel loading on the dmesg; it seems like it logs to the RAM and after it mounts the SD the system dump the log into the dmeseg. I think this doens't happen because it never mounts the SD card. the dump I'm attaching herein has been captured with my serial terminal which by now is the only way I can access my system. Relevant logs are: setenv - set environment variables Usage: setenv [-f] name value ... - [forcibly] set environment variable 'name' to 'value ...' setenv [-f] name - [forcibly] delete environment variable 'name' [ 0.000000] Kernel command line: [empty!!! I swear that here in the past I saw the envs var defined in the /boot/boot.cmd!!! maybe setenv usage is a hint about a failed setenv command?] [ 3.573034] sunxi-rtc 1c20d00.rtc: setting system clock to 1970-01-01 00:00:13 UTC (13) [ 3.607353] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 sorry to bother but I'm struggling after this issue since about two weeks and I don't know where I can begin to fix that... Tell me if I need to open an issue on github (I saw Igor closed the previous one so I didn't open a new one) many thanks! captureNoBootUART_wrongboot.txt boot.cmd.txt