belegdol

There is something fishy going on. I have just installed the 5.4.91 update from the official repos and the issue came back. I then installed the binaries I built myself and the problem is still there. Super strange.

With https://github.com/armbian/build/pull/2569 and https://github.com/armbian/upload/pull/33 the problem seems to finally be gone.

Oh, what determines the MOTD then, and why does it keep changing? Right now it says: ___ _ _ _ _ _ ____ _ / _ \ __| |_ __ ___ (_) __| | | | | |/ ___/ | | | | |/ _` | '__/ _ \| |/ _` | | |_| | | | | | |_| | (_| | | | (_) | | (_| | | _ | |___| | \___/ \__,_|_| \___/|_|\__,_| |_| |_|\____|_| Welcome to Armbian 20.11.6 Buster with Linux 5.4.83-odroidxu4 But after a while it changes back to XU4. Regarding the kernel, it is supported by upstream but not by hardkernel it seems. My HC1 is easily accessible to a c

I have now tried adding board_name=hc1 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u as well as setenv board_name "hc1" setenv usbstoragequirks "0x2537:0x1066:u,0x2537:0x1068:u" to boot.ini directly. Neither seem to have any effect whatsoever, on the model shown when ssh-ing to the machine or on the sata drives being missing after reboot. Cold boot make sata drives appear but does nothing to MOTD. The only way I can change the MOTD is by using armbian-config. After the reboot the MOTD says HC1 but sata drives are gone. Cold boot after that restores the drives while keeping the

My boot.ini is also much longer, I only pasted the relevant part. Sorry for being unclear. I will see if adding board_name to the file directly changes anything. I am not running any CPU-intensive code on my HC1 so the thermal issues should be irrelevant. Wysłane z mojego XT1580 przy użyciu Tapatalka

The strange thing is that the armbian-config change does actually change the dtb (or the login message at least) until the next kernel update is installed.

My armbianEnv.txt looks as follows: board_name=hc1 board_name=hc1 board_name=hc1 board_name=hc1 board_name=hc1 board_name=hc1 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u This is the boot.ini: # Load kernel, initrd and dtb in that sequence ext4load mmc 0:1 0x40008000 /boot/zImage || fatload mmc 0:1 0x40008000 zImage || ext4load mmc 0:1 0x40008000 zImage ext4load mmc 0:1 0x42000000 /boot/uInitrd || fatload mmc 0:1 0x42000000 uInitrd || ext4load mmc 0:1 0x42000000 uInitrd # this is for mainline only if test "${board_name}" = "xu4"; then setenv fdtfile "exynos5422-odroidxu4.dtb";

armbian-config

I am not sure whether this has anything to do with the issue at hand, but I have just noticed that after every kernel update the dtb gets reset from HC1 to XU4.

Posted to hardkernel forum: https://forum.odroid.com/viewtopic.php?f=96&t=40978

Would it make sense to report it on hardkernel forums? How has the attitude towards armbian been so far? I cannot test hardkernel's Ubuntu currently.

root@odroidxu4:~# hdparm -C /dev/sda /dev/sda: SG_IO: bad/missing sense data, sb[]: 70 00 04 00 00 00 00 0a 00 00 00 00 44 81 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 drive state is: unknown This is how the output looks like after power cycle: root@odroidxu4:~# hdparm -C /dev/sda /dev/sda: drive state is: active/idle

How do i check whether the drive sleeps with hdparm? In any case, the issue is very likely related to kernel-5.4 because this was not happening with 4.14.

This is how the dmesg output looks when the drive is working: [ 6.171505] usbcore: registered new interface driver usb-storage [ 6.192233] scsi host0: uas [ 6.193251] usbcore: registered new interface driver uas [ 6.194240] scsi 0:0:0:0: Direct-Access JMicron Generic 3102 PQ: 0 ANSI: 6 [ 6.364216] usb 6-1: reset SuperSpeed Gen 1 USB device number 2 using xhci-hcd [ 6.448262] r8152 6-1:1.0 eth0: v1.10.11 [ 6.707791] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB) [ 6.707841] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 6.708407

Hi, I have recently installed armbian-config on my HC1 running OMV and switched to -current kernel from -legacy. Unfortunately, now whenever I soft-reboot following a kernel update, the sda drive is missing: [ 6.161366] usbcore: registered new interface driver usb-storage [ 6.180240] scsi host0: uas [ 6.181260] usbcore: registered new interface driver uas [ 6.182155] scsi 0:0:0:0: Direct-Access JMicron Generic 3102 PQ: 0 ANSI: 6 [ 6.193271] sd 0:0:0:0: [sda] Unit Not Ready [ 6.193290] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] [ 6.193302] sd