HeyBig Posted November 14, 2018 Posted November 14, 2018 I have the same issue on my Tinkerboard, here's the armbianmonitor -U output: https://paste.ubuntu.com/p/jggvYDMbCX/
Igor Posted November 14, 2018 Posted November 14, 2018 1 hour ago, HeyBig said: I have the same issue on my Tinkerboard, here's the armbianmonitor -U output: Don't understand the nature of the problem. BTW. Nightly images are not supported.
Tido Posted November 14, 2018 Posted November 14, 2018 On 11/12/2018 at 8:40 PM, TonyMac32 said: I would very much like the dmesg output you get when plugging your monitors in, and of course any serial debug output you can provide on failed boot events. I connected UART 2 and repeated the procedure before the update root@tinkerboard:~# armbianmonitor -u System diagnosis information will now be uploaded to http://ix.io/1rU6 after the update and after reboot: root@tinkerboard:~# armbianmonitor -u System diagnosis information will now be uploaded to http://ix.io/1rUc Cold start, disconnect every power, also UART -> no more boot: Spoiler U-Boot SPL 2018.09-armbian (Nov 12 2018 - 23:55:40 +0100) Returning to boot ROM... U-Boot 2018.09-armbian (Nov 12 2018 - 23:55:40 +0100) Model: Tinker-RK3288 DRAM: 2 GiB MMC: dwmmc@ff0c0000: 1, dwmmc@ff0f0000: 0 Loading Environment from EXT4... Card did not respond to voltage select! In: serial Out: vidconsole Err: vidconsole Model: Tinker-RK3288 Net: eth0: ethernet@ff290000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 1485 bytes read in 1 ms (1.4 MiB/s) ## Executing script at 00000000 U-boot loaded from eMMC 155 bytes read in 2 ms (75.2 KiB/s) ** File not found /boot/dtb/rk3288-miniarm.dtb ** ** Unrecognized filesystem type ** ** File not found dtb/rk3288-miniarm.dtb ** 4609312 bytes read in 205 ms (21.4 MiB/s) 8581872 bytes read in 378 ms (21.7 MiB/s) ## Loading init Ramdisk from Legacy Image at 21000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4609248 Bytes = 4.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... starting USB... USB0: USB1: scanning bus 0 for devices... 4 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: unknown device ethernet@ff290000 Waiting for PHY auto negotiation to complete... done Speed: 100, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.11.2 (147 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-2c-4d-54-42-c5-6f Speed: 100, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A80B02 Speed: 100, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A80B0 Speed: 100, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A80B Speed: 100, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A80 Speed: 100, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8 Speed: 100, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A Speed: 100, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0 Speed: 100, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C Speed: 100, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-rockchip Speed: 100, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm Speed: 100, full duplex *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default Speed: 100, full duplex *** ERROR: `serverip' not set Config file not found wasn't easy to get that out of the terminal. I hope it helps. Here you can see what the SDcard looks like: https://forum.armbian.com/topic/3327-asus-tinkerboard/?do=findComment&comment=65557 hmm, this file is no longer there: Linux version 4.14.59-rockchip, but the 4.14.50 sit's still there.
TonyMac32 Posted November 14, 2018 Posted November 14, 2018 Why on Earth is it looking for miniarm dtb... Sent from my Pixel using Tapatalk [Edit] Hang on, why is it showing u-boot from mmc and showing 2 mmc devices? Is this a tinker S?
Tido Posted November 15, 2018 Posted November 15, 2018 This is the very first tinker board. Just SDcard
TonyMac32 Posted November 15, 2018 Posted November 15, 2018 3 minutes ago, Tido said: This is the very first tinker board. Just SDcard Fascinating. Well then.
TonyMac32 Posted November 15, 2018 Posted November 15, 2018 As far as no boot after cold start, @Tido, I have to ask if you added "fdt_file=rk3288-miniarm.dtb" to the armbianEnv.txt file at some point, or if you upgraded from the 4.4 kernel. There was a link in place so anything looking for rk3288-miniarm.dtb would get forwarded to the rk3288-tinker.dtb, @Igor had added it when the file names didn't match between mainline and Rockchip/ASUS code. I can't remember where/how exactly it was stuck in there, but that could be it. <--Found it: https://github.com/armbian/build/commit/9dbc69e0ed609185abbaf28144db714684b1f395#diff-92fd175af58f1b9b7cf350b58398929d If you change the armbianEnv.txt file to have "rk3288-tinker.dtb" it should work. Curiosity, how long have you been maintaining/upgrading this particular install? None of mine go more than a couple weeks due to testing/etc.
TonyMac32 Posted November 15, 2018 Posted November 15, 2018 Split from main discussion as this appears to be a specific problem. Re-created the symlink patch so future updates won't break.
Tido Posted November 15, 2018 Posted November 15, 2018 This was a fresh install. I have chosen 4.14 because 4.4 at that time didn't support 1280x1024 whereas mainline did. 6 hours ago, TonyMac32 said: if you added "fdt_file=rk3288-miniarm.dtb" to the armbianEnv.txt file I don't think so, I just took a backup and run the update every couple months until it finally broke. 11 hours ago, Tido said: this file is no longer there: Linux version 4.14.59-rockchip, but the 4.14.50 sit's still there. and why was the .59 Kernel removed and the .50 is still there ? Is this an error in the script ? 6 hours ago, TonyMac32 said: If you change the armbianEnv.txt file to have "rk3288-tinker.dtb" it should work. This would be awesome, but what happen to my tinker with the next update ? 6 hours ago, TonyMac32 said: Curiosity, how long have you been maintaining/upgrading this particular install? Well, if you look at the posting here of my backups, I installed circa March. The 1 of March Image 4.4 still hadn't had 1280x1024 Not to forget, 4.4 armbian image still has random reboots I guess.. The MultiMedia Image
Tido Posted November 15, 2018 Posted November 15, 2018 16 hours ago, TonyMac32 said: it should work. You were right, it does boot again but.. it dies now exactly the same way as the 4.4 does :-(
TonyMac32 Posted November 15, 2018 Posted November 15, 2018 You were right, it does boot again but.. it dies now exactly the same way as the 4.4 does :-(This I have not experienced, I used it for some web browsing/etc. Any logs of the crash this time?Sent from my Pixel using Tapatalk
Recommended Posts