fortdevv Posted March 5 Share Posted March 5 Tinkerboard (not 2) not booting after kernel updates for some reason. Who knows how to fix this? 0 Quote Link to comment Share on other sites More sharing options...
Werner Posted March 6 Share Posted March 6 Providing more information would be a good point to start. https://debug.armbian.de 0 Quote Link to comment Share on other sites More sharing options...
MMinga Noise Posted March 8 Share Posted March 8 (edited) I have the same issue after update my system does not boot anymore Tinkerboard 2S. I flashed then the SD card, I did not install any software and after update/upgrade the system does not boot anymore. Ony the red LED is on not the yellow. Is it a known issue? Update: This image causes the issue: Armbian_23.8.1_Tinkerboard_jammy_current_6.1.50_xfce_desktop.img The new downloaded image works: Armbian_24.2.1_Tinkerboard_jammy_current_6.6.16_xfce_desktop.img Edited March 8 by MMinga Noise 0 Quote Link to comment Share on other sites More sharing options...
Z11ntal33r Posted March 14 Share Posted March 14 (edited) Same issue here. Upgraded from Armbian 23.8.1 Bookworm with Linux 6.1.63-current-rockchip and now my Tinkerboard won't boot Here is the log from the upgrade process. Unfortunately, I am not home and hence cannot debug any further with an UART for the next weeks Spoiler Preparing to unpack .../0-armbian-bsp-cli-tinkerboard_24.2.1_armhf.deb ... Unpacking armbian-bsp-cli-tinkerboard (24.2.1) over (23.8.1) ... Preparing to unpack .../1-armbian-bsp-cli-tinkerboard-current_24.2.1_armhf.deb ... Armbian 'armbian-bsp-cli-tinkerboard-current' for '1-PC13d1-V3fd0-Hd02b-Ba537-R6632': 'preinst' starting. Armbian 'armbian-bsp-cli-tinkerboard-current' for '1-PC13d1-V3fd0-Hd02b-Ba537-R6632': 'preinst' finishing. Unpacking armbian-bsp-cli-tinkerboard-current (24.2.1) over (23.8.1) ... Armbian 'armbian-bsp-cli-tinkerboard-current' for '1-PC2036-V9269-He24e-B55b9-R6632': 'postrm' starting. Armbian 'armbian-bsp-cli-tinkerboard-current' for '1-PC2036-V9269-He24e-B55b9-R6632': 'postrm' finishing. dpkg: warning: unable to delete old directory '/usr/lib/chromium-browser': Directory not empty Preparing to unpack .../2-armbian-firmware_24.2.1_all.deb ... Unpacking armbian-firmware (24.2.1) over (23.11.1) ... Preparing to unpack .../3-linux-dtb-current-rockchip_24.2.1_armhf.deb ... Armbian 'linux-dtb-current-rockchip' for '6.6.16-current-rockchip': 'preinst' starting. Armbian 'linux-dtb-current-rockchip' for '6.6.16-current-rockchip': 'preinst' finishing. Unpacking linux-dtb-current-rockchip (24.2.1) over (23.11.1) ... Preparing to unpack .../4-linux-image-current-rockchip_24.2.1_armhf.deb ... Armbian 'linux-image-current-rockchip' for '6.1.63-current-rockchip': 'prerm' starting. Armbian 'linux-image-current-rockchip' for '6.1.63-current-rockchip': 'prerm' finishing. Armbian 'linux-image-current-rockchip' for '6.6.16-current-rockchip': 'preinst' starting. Armbian 'linux-image-current-rockchip' for '6.6.16-current-rockchip': 'preinst' finishing. Unpacking linux-image-current-rockchip (24.2.1) over (23.11.1) ... Armbian 'linux-image-current-rockchip' for '6.1.63-current-rockchip': 'postrm' starting. Armbian 'linux-image-current-rockchip' for '6.1.63-current-rockchip': 'postrm' finishing. Preparing to unpack .../5-linux-u-boot-tinkerboard-current_24.2.1_armhf.deb ... Unpacking linux-u-boot-tinkerboard-current (24.2.1) over (23.11.1) ... Preparing to unpack .../6-tailscale_1.62.0_armhf.deb ... Unpacking tailscale (1.62.0) over (1.60.1) ... Setting up linux-dtb-current-rockchip (24.2.1) ... Armbian 'linux-dtb-current-rockchip' for '6.6.16-current-rockchip': 'postinst' starting. Armbian: DTB: symlinking /boot/dtb to /boot/dtb-6.6.16-current-rockchip... 'dtb' -> 'dtb-6.6.16-current-rockchip' Armbian 'linux-dtb-current-rockchip' for '6.6.16-current-rockchip': 'postinst' finishing. Setting up linux-image-current-rockchip (24.2.1) ... Armbian 'linux-image-current-rockchip' for '6.6.16-current-rockchip': 'postinst' starting. dkms: autoinstall for kernel 6.6.16-current-rockchip was skipped since the kernel headers for this kernel do not seem to be installed. update-initramfs: Generating /boot/initrd.img-6.6.16-current-rockchip W: Possible missing firmware /lib/firmware/mrvl/sdiouart8997_combo_v4.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sdsd8997_combo_v4.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8987_uapsta.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sdiouartiw416_combo_v0.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sdsd8977_combo_v2.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8887_uapsta.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8897_uapsta.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8797_uapsta.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8787_uapsta.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8786_uapsta.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/rt73.bin for built-in driver rt73usb W: Possible missing firmware /lib/firmware/bfubase.frm for built-in driver bfusb W: Possible missing firmware /lib/firmware/intel/ibt-12-16.ddc for built-in driver btintel W: Possible missing firmware /lib/firmware/intel/ibt-12-16.sfi for built-in driver btintel W: Possible missing firmware /lib/firmware/intel/ibt-11-5.ddc for built-in driver btintel W: Possible missing firmware /lib/firmware/intel/ibt-11-5.sfi for built-in driver btintel W: Possible missing firmware /lib/firmware/mrvl/sdsd8997_combo_v4.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8987_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sdsd8977_combo_v2.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8897_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8887_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8797_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8787_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8688.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8688_helper.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852cu_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852cu_fw_v2.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852cu_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852bu_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852bu_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852bs_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852bs_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852au_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852au_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8851bu_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8851bu_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8822cu_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8822cu_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8821cs_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8821cs_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8821a_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8821a_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761bu_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761bu_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761b_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761b_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761a_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761a_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8723d_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8723d_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8723a_fw.bin for built-in driver btrtl update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.16-current-rockchip Image Name: uInitrd Created: Thu Mar 14 20:29:00 2024 Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 8966378 Bytes = 8756.23 KiB = 8.55 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.6.16-current-rockchip to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.6.16-current-rockchip' update-initramfs: Armbian: done. Remove unused generated file: /boot/uInitrd-6.1.63-current-rockchip Remove unused generated file: /boot/initrd.img-6.1.63-current-rockchip Armbian: update last-installed kernel symlink to 'zImage'... '/boot/zImage' -> 'vmlinuz-6.6.16-current-rockchip' Armbian: Debian compat: linux-update-symlinks install 6.6.16-current-rockchip boot/vmlinuz-6.6.16-current-rockchip I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.6.16-current-rockchip I: /initrd.img.old is now a symlink to boot/initrd.img-6.6.16-current-rockchip I: /vmlinuz is now a symlink to boot/vmlinuz-6.6.16-current-rockchip I: /initrd.img is now a symlink to boot/initrd.img-6.6.16-current-rockchip Armbian 'linux-image-current-rockchip' for '6.6.16-current-rockchip': 'postinst' finishing. Setting up armbian-firmware (24.2.1) ... Setting up tailscale (1.62.0) ... Setting up linux-u-boot-tinkerboard-current (24.2.1) ... Armbian 'uboot-tinkerboard-current' for '2022.04-Se4b6-P0e83-H2fb1-Vf3af-B11a8-R448a': 'postinst' starting. Updating u-boot on /dev/mmcblk2 dd: error reading '/usr/lib/linux-u-boot-current-tinkerboard/': Is a directory 0+0 records in 0+0 records out 0 bytes copied, 0.000870923 s, 0.0 kB/s Armbian 'uboot-tinkerboard-current' for '2022.04-Se4b6-P0e83-H2fb1-Vf3af-B11a8-R448a': 'postinst' finishing. Setting up armbian-bsp-cli-tinkerboard-current (24.2.1) ... Armbian 'armbian-bsp-cli-tinkerboard-current' for '1-PC13d1-V3fd0-Hd02b-Ba537-R6632': 'postinst' starting. Armbian 'armbian-bsp-cli-tinkerboard-current' for '1-PC13d1-V3fd0-Hd02b-Ba537-R6632': 'postinst' finishing. Processing triggers for initramfs-tools (0.142) ... update-initramfs: Generating /boot/initrd.img-6.6.16-current-rockchip W: Possible missing firmware /lib/firmware/mrvl/sdiouart8997_combo_v4.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sdsd8997_combo_v4.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8987_uapsta.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sdiouartiw416_combo_v0.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sdsd8977_combo_v2.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8887_uapsta.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8897_uapsta.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8797_uapsta.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8787_uapsta.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8786_uapsta.bin for built-in driver mwifiex_sdio W: Possible missing firmware /lib/firmware/rt73.bin for built-in driver rt73usb W: Possible missing firmware /lib/firmware/bfubase.frm for built-in driver bfusb W: Possible missing firmware /lib/firmware/intel/ibt-12-16.ddc for built-in driver btintel W: Possible missing firmware /lib/firmware/intel/ibt-12-16.sfi for built-in driver btintel W: Possible missing firmware /lib/firmware/intel/ibt-11-5.ddc for built-in driver btintel W: Possible missing firmware /lib/firmware/intel/ibt-11-5.sfi for built-in driver btintel W: Possible missing firmware /lib/firmware/mrvl/sdsd8997_combo_v4.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8987_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sdsd8977_combo_v2.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8897_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8887_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8797_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8787_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8688.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8688_helper.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852cu_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852cu_fw_v2.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852cu_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852bu_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852bu_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852bs_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852bs_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852au_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852au_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8851bu_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8851bu_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8822cu_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8822cu_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8821cs_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8821cs_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8821a_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8821a_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761bu_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761bu_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761b_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761b_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761a_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761a_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8723d_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8723d_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8723a_fw.bin for built-in driver btrtl update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.16-current-rockchip Image Name: uInitrd Created: Thu Mar 14 20:29:18 2024 Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 8967062 Bytes = 8756.90 KiB = 8.55 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.6.16-current-rockchip to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.6.16-current-rockchip' update-initramfs: Armbian: done. Setting up armbian-bsp-cli-tinkerboard (24.2.1) ... Current status: 0 (-7) upgradable. Edited March 14 by Z11ntal33r 0 Quote Link to comment Share on other sites More sharing options...
Scott Picton Posted March 18 Share Posted March 18 I have the same issue and just tried to get a serial dump but I get absolutely nothing. I've connected to pins 32 TX and 33 RX + GND. I confirmed I have the right pins by booting a known good image and get something starting with `U-Boot TPL 2022.04-armbian (Nov 25 2023 - 12:49:32)`. Is there anything we can check on the SD as to why it doesn't boot? 0 Quote Link to comment Share on other sites More sharing options...
Scott Picton Posted March 19 Share Posted March 19 @Z11ntal33r thanks for posting the log. It looks obvious to me that the issue is the u-boot update process. In your logs I can see: `dd: error reading '/usr/lib/linux-u-boot-current-tinkerboard/': Is a directory` A bit of a dig into the code shows there's probably a dd process before that step that zeros out the boot sectors. Hence no boot at all on our boards. Might be an easy I'm not really sure how to patch any of this but thought I'd share what I found to help move this along. 0 Quote Link to comment Share on other sites More sharing options...
Scott Picton Posted March 19 Share Posted March 19 I've repaired my install by manually applying the failed dd step. 1. Mount the SD card on another Linux machine and open up a terminal. 2. `cd` to the SD card, for me it's `cd /media/scott/sdcard/` 3. `cd` to the u-boot image directory `cd usr/lib/linux-u-boot-current-tinkerboard/` 4. make note of which device the sd card is, you could use `mount | grep media` for example 5. for me it's `/dev/sdb` but it could be something like `/dev/mmcblk1` 6. IMPORTANT make sure you absolutely have the right device 7. run the following, replacing XXX with your target device `dd if=u-boot-rockchip-with-spl.bin of=/dev/XXX bs=32k seek=1 conv=notrunc` 0 Quote Link to comment Share on other sites More sharing options...
mhel Posted March 20 Share Posted March 20 I have the same problem, I had it working for a year. Yesterday I decided to upgrade and I thought I burned the board. Luckily the SD-card still works. @Scott Picton I tried your fix didn't work for me. I forced boot the board with the sdcard in it but with the jumper on for eMMC. and tried to dd the .spl, but nothing changed. did you dd the .spl from the same image of the latest released? or from an older release? 0 Quote Link to comment Share on other sites More sharing options...
Scott Picton Posted March 20 Share Posted March 20 (edited) @mhel if you're talking about eMMC then I think you're talking about the Tinker Board S? I imagine that might have slight differences to the Tinker Board that my fix works for. The .spl.bin image is read from and dd'd to the affected SD card. Edited March 20 by Scott Picton add @ 0 Quote Link to comment Share on other sites More sharing options...
mhel Posted March 20 Share Posted March 20 (edited) Yeah, it's the S version that I have. Wha'ts puzzling about it is, the same image file loaded to the sdcard works. Edit: It's working now again, I dd'd the image this time. last time I used balena etcher. There must be something different with how it write image file. Thanks for the continuous support of this aging board. Edited March 20 by mhel 0 Quote Link to comment Share on other sites More sharing options...
kalekulan Posted March 20 Share Posted March 20 I also have the Tinkerboard S running on eMMC. I can't boot either. I tried connecting it with USB to my computer, but it cannot read the USB device anylonger Is there any way fixing this? 0 Quote Link to comment Share on other sites More sharing options...
tinker Posted March 20 Share Posted March 20 (edited) I can confirm the same problem for the original tinkerboard and debian bookworm 6.6.16-current-rockchip. No boot after update, no HDMI output, just red LED. I have root elsewhere, so I reflashed the sd-card and copied /boot back to the sd-card to fix. Edited March 20 by tinker 0 Quote Link to comment Share on other sites More sharing options...
Scott Picton Posted March 21 Share Posted March 21 I'm a bit out of my depth now. @Gunjan Gupta might be the right person to fix this bug? 0 Quote Link to comment Share on other sites More sharing options...
mhel Posted March 21 Share Posted March 21 (edited) @kalekulan I had the same. When I upgraded emmc can't boot anymore. It doesn't get detected when plugged to usb by itself. SD card still works tho you can try to force boot it. Put the jumper on the mask rom mode, and place a bootable sdcard, then plugged it to USB. It might help if you can monitor the serial port. The sdcard will boot but it will detect the eMMC mode and the eMMC will be detected by the pc. Then you can do the usual dd'ing. EDIT: with the eMMC booting now, it still don't get detected by the pc when you plug it in, but atleast it boot now. And somehow it just shutdown on me just now, over temperature. only got mariadb and freeradius running on it. My tiny rpi copper heatsink is most likely no enough. Edited March 21 by mhel 0 Quote Link to comment Share on other sites More sharing options...
jock Posted March 24 Share Posted March 24 Hello everyone, the broken upgrade process is my fault and I apologize everyone for the inconvenience. The reason behind the broken upgrade process is the merge of the rockchip and rk322x families, which introduced this regression. The problem went undetected because upgrades happens once in a while when there are armbian new releases. I will address the issue as soon as possible, in the meantime please avoid upgrading to latest armbian version. I will post here when I will be sure the issue is fixed! Thanks! 2 Quote Link to comment Share on other sites More sharing options...
jock Posted March 26 Share Posted March 26 Hello all, bootloader packages have been rebuilt and now upgrades should be fine! 1 Quote Link to comment Share on other sites More sharing options...
fortdevv Posted March 27 Author Share Posted March 27 Hello! Thank you jock for fixing the problems! I am just updated, and it's really working now. Thanks! 0 Quote Link to comment Share on other sites More sharing options...
jock Posted March 28 Share Posted March 28 @fortdevv you're welcome and thanks for reporting 👍 1 Quote Link to comment Share on other sites More sharing options...
tj13 Posted March 30 Share Posted March 30 I have two tinker boards that both bricked after the last update. 0 Quote Link to comment Share on other sites More sharing options...
jock Posted March 31 Share Posted March 31 17 hours ago, tj13 said: I have two tinker boards that both bricked after the last update. The installation script has been fixed and should work as intended right now. Perhaps your boards bricked for other reasons? If you don't provide details it is extremely difficult to give support. 0 Quote Link to comment Share on other sites More sharing options...
tj13 Posted March 31 Share Posted March 31 Sorry to be a pain. I really do appreciate all the work that goes in to maintaining the OS. So I don't want to sound like I am complaining. It is kind of hard for me to get detail, when they don't boot. The only thing I did was apply updates. I also can't run the installation script if they don't boot. It's probably easier if I just re-flash them, from scratch. Thanks, Tom 0 Quote Link to comment Share on other sites More sharing options...
SteeMan Posted March 31 Share Posted March 31 @tj13You get details by hooking up a USB uart adapter and reading the serial console output of the boot process. 1 Quote Link to comment Share on other sites More sharing options...
jock Posted March 31 Share Posted March 31 @tj13 don't worry, it's no pain. Bug reports are always appreciated, but without logs or whatever it is very uneasy to guess if the problem is related with the broken installation script or whatever. Surely you can follow the posts of this thread to get a clue; if you installed the system in eMMC perhaps you can try the Multitool from this page and see if it works (I never tried it on TInkerboard), so at least you have a way to backup and access the filesystem. At last, the uart adapter suggested by @SteeMan can give some important hints about what went bad. 0 Quote Link to comment Share on other sites More sharing options...
Ikesankom Posted March 31 Share Posted March 31 (edited) Good evening I have Tinkerboard 1 and have the same problem upgrading from Ubuntu 23.02 to 23.10. As I have seen this thread, I decided to try again today, but I keep getting the same thing (see attachment) I had always upgraded smoothly from one version to another by doing the do-release-upgrade command. It saves me that I am backing up the image from time to time. It should be noted that before rebooting the computer to load the new system, I checked the UUID of / in /etc/fstab (in case it had changed during the upgrade). Is it a GRUB problem perhaps? How could I solve it? Thank you very much Edited April 1 by Ikesankom 0 Quote Link to comment Share on other sites More sharing options...
jock Posted April 1 Share Posted April 1 @Ikesankom Hello, your problem seems different than the bootloader issue described in this thread. In your case the bootloader is ok and the kernel boots fine, but the rootfs is not detected. It could be due to a missing module in the initramfs, which is weird because emmc/sdcard storage are built in the kernel and not as modules. It would be useful if you can submit the output of dmesg and blkid. initramfs has a limited set of commands, but you should be perfectly able to mount devices and write the output there. 0 Quote Link to comment Share on other sites More sharing options...
Ikesankom Posted April 1 Share Posted April 1 @jock Yes, It is a USB drive attached (for storage purposes). But It has always been connected in other upgrades and had no problem. It is true that not long ago I changed its format from NTFS to EXT4 but it should be indifferent. In /etc/fstab I have it as automount. Thanks! 0 Quote Link to comment Share on other sites More sharing options...
jock Posted April 1 Share Posted April 1 @Ikesankom there are some messages in dmesg I don't like at all, but surely the the rootfs UUID seems to be the wrong one. You can alter it editing /boot/armbianEnv.txt and pasting the right one. When you are in the initramfs you have to manually mount /dev/sda1 somewhere and then you can edit the file. The right one is the one you get from blkid 4ca8....43ad; I don't know why the UUID changed after the upgrade, perhaps an sdcard was plugged in during the upgrade? 0 Quote Link to comment Share on other sites More sharing options...
Ikesankom Posted April 2 Share Posted April 2 @jock /dev/sda1 4ca8....43ad is a USB drive that is permanently connected to the Tinkerboard, which acts as a second partition and has always been connected even during system updates. The good drive, the Armbian one, is: /dev/mmcblk2p1 bfdcf9c9-e3b6-4f2e-a89a-f9d17289d118 which is the one it doesn't find. 0 Quote Link to comment Share on other sites More sharing options...
jock Posted April 2 Share Posted April 2 @Ikesankom sorry but you did not share details on your system: you didn't tell where your rootfs is installed (emmc? sdcard? usb?), just a "yes, it is an USB drive attached", so I supposed the rootfs was on the USB drive. The rootfs is elsewhere and from the piece of dmesg you posted it looks like the eMMC (mmc@ff0f0000) is "busy" for some reason and sdcard (mmc@ff0c0000) initialization is getting delayed. I did not experience such glitch, but I can try later to double check if my board is ok. In order to get decent support, you should tell first of all what Tinkerboard version (regular? version S? version 2?) and revision you have, if the eMMC is soldered on board or added as separate module. 0 Quote Link to comment Share on other sites More sharing options...
Ikesankom Posted April 2 Share Posted April 2 @jock Quote "yes, it is an USB drive attached" Sorry, I was typing and attaching images and finally the answer was weird. Is a Tinkerboard "regular" (doesn't have eMMC). The system is installed in a microSD and the rootfs is /dev/mmcblk2p1. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.