odoll

OK thx - rather than Jammy I think I finally got bookworm to "fly", but the freshly flashed image booted without network, and thus the initial setup is a bit cumbersome. As from the "logs" below I had to unmask the systemd-networkd.service first, before the network ports became usable ... PS: Beside just unmasking the service with systemctl unmask systemd-networkd.service it has to be enabled as well with systemctl enable systemd-networkd.service to have it started after a reboot.

BTW: How would you (easily) install armbian-config, if you don't have internet connection? 😉 But yes, as it's part of the jammy / booksworm builds: I've tried set stauts of some ports to managed, or to set a static IP address - no success.

Sorry folks, I think I'm suffering from the the same 'disease', but I'm still 'blind' to see the solution to the following issue. I'm on a v5 board to which I flashed the "new" uboot version a long time, ago. (I think I flashed flash-image-DDR3-1g_2cs_2-800_800.bin that time as I had timing issues with the version with higher speed.) Though I could get the system to boot after the reset of the uboot environment I never was able to get the i-net running on the applied images, so I gave up in the end. "Messing around" with my Cubietrucks atm I thought I would give the espressobin a second try, but still without success. To me it looks like network manager is running and when I set "/sbin/ip link set dev wan up" as suggested by @y52 the wan-port will get ipv6 addresses (I have to connections to the i-net), but no ipv4 ones. So what do I have to do to get those (in the meantime community versions of bookworm etc.) to work? (thx!) root@espressobin:~# nmcli device show GENERAL.DEVICE: eth0 GENERAL.TYPE: ethernet GENERAL.HWADDR: 5A:FD:04:25:F9:14 GENERAL.MTU: 1508 GENERAL.STATE: 10 (unmanaged) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- WIRED-PROPERTIES.CARRIER: on IP4.GATEWAY: -- IP6.ADDRESS[1]: fe80::58fd:4ff:fe25:f914/64 IP6.GATEWAY: -- IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 256 GENERAL.DEVICE: lan0 GENERAL.TYPE: ethernet GENERAL.HWADDR: 5A:FD:04:25:F9:14 GENERAL.MTU: 1500 GENERAL.STATE: 10 (unmanaged) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- WIRED-PROPERTIES.CARRIER: off IP4.GATEWAY: -- IP6.GATEWAY: -- GENERAL.DEVICE: lan1 GENERAL.TYPE: ethernet GENERAL.HWADDR: 5A:FD:04:25:F9:14 GENERAL.MTU: 1500 GENERAL.STATE: 10 (unmanaged) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- WIRED-PROPERTIES.CARRIER: off IP4.GATEWAY: -- IP6.GATEWAY: -- GENERAL.DEVICE: wan GENERAL.TYPE: ethernet GENERAL.HWADDR: 5A:FD:04:25:F9:14 GENERAL.MTU: 1500 GENERAL.STATE: 10 (unmanaged) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- WIRED-PROPERTIES.CARRIER: on IP4.GATEWAY: -- IP6.ADDRESS[1]: 2a02:908:nnnn:nnnn:58fd:4ff:fe25:f914/64 IP6.ADDRESS[2]: 2002:mmmm:mmmm:0:58fd:4ff:fe25:f914/64 IP6.ADDRESS[3]: fe80::58fd:4ff:fe25:f914/64 IP6.GATEWAY: fe80::1eed:6fff:fe07:29bd IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 256 IP6.ROUTE[2]: dst = ::/0, nh = fe80::1eed:6fff:fe07:2> IP6.ROUTE[3]: dst = 2a02:908:nnnn:nnnn::/64, nh = ::, > IP6.ROUTE[4]: dst = ::/0, nh = fe80::b2f2:8ff:fe23:29> IP6.ROUTE[5]: dst = 2002:mmmm:mmmm::/64, nh = ::, mt > GENERAL.DEVICE: lo GENERAL.TYPE: loopback GENERAL.HWADDR: 00:00:00:00:00:00 GENERAL.MTU: 65536 GENERAL.STATE: 10 (unmanaged) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- IP4.ADDRESS[1]: 127.0.0.1/8 IP4.GATEWAY: --

It does, thx!

Folks, it has been a long time since I messed around with my ebin v5, but just wanted give it a second chance as I need to do something about my EOL Cubietruck (and my "broken" NT4 domain). So I started a second attempt with "Armbian_22.08.1_Espressobin_bullseye_current_5.15.63" just a few days ago, but didn't got much further than updating uboot and to apt update / upgrade the system, before I got distracted again. In the meantime I noticed the new "Armbian_22.11.1_Espressobin_bullseye_current_5.15.80" and I thought it would be a better idea starting from scratch with that version. However, when I boot this up from SD the only interface shown ("ifconfig") is lo. (I 'see' the other port with "ifconfig -a", but I don't get an IP set (via DHCP) whatever physical port I use on the topaz switch, though the leds are happily blinking indicating a proper link.

Yes, but the the LTS support for Jessie is till end of June 2022! https://www.debian.org/releases/stretch/ "Debian 9 has been superseded by Debian 10 (buster). Security updates have been discontinued as of July 6th, 2020. However, stretch benefits from Long Term Support (LTS) until the end of June 2022. The LTS is limited to i386, amd64, armel, armhf and arm64. All other architectures are no longer supported in stretch. For more information, please refer to the LTS section of the Debian Wiki." --> "Debian Long Term Support (LTS) is a project to extend the lifetime of all Debian stable releases to (at least) 5 years. Debian LTS is not handled by the Debian security team, but by a separate group of volunteers and companies interested in making it a success. Thus the Debian LTS team takes over security maintenance of the various releases once the Debian Security team stops its work."

Thx! Yes, I'm trying to connect to the console of a cubietruck. (Access from the cubietruck to the console of the espressobin works). Mine is a (fake) Prolific [177708.603331] usb 1-1: USB disconnect, device number 12 root@espressobin:~# ls -al /dev/tty* > tty.a [177965.718765] usb 1-1: new high-speed USB device number 13 using orion-ehci [177965.878745] usb 1-1: config 1 interface 0 altsetting 0 bulk endpoint 0x2 has invalid maxpacket 64 [177965.878792] usb 1-1: config 1 interface 0 altsetting 0 bulk endpoint 0x83 has invalid maxpacket 64 [177965.881592] usb 1-1: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 3.00 [177965.881624] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [177965.881649] usb 1-1: Product: USB-Serial Controller [177965.881673] usb 1-1: Manufacturer: Prolific Technology Inc. root@espressobin:~# ls -al /dev/tty* > tty.b root@espressobin:~# diff tty.a tty.b 66c66 < crw------- 1 root tty 252, 0 Aug 23 11:20 /dev/ttyMV0 --- > crw------- 1 root tty 252, 0 Aug 23 11:26 /dev/ttyMV0 But also any other tried didn't work 1st [446317.220494] usb 1-1: new high-speed USB device number 3 using orion-ehci [446317.408480] usb 1-1: Using ep0 maxpacket: 8 [446317.505569] usb 1-1: device descriptor read/all, error -71 [446317.632451] usb 1-1: new high-speed USB device number 4 using orion-ehci [446317.820467] usb 1-1: Using ep0 maxpacket: 8 [446317.917604] usb 1-1: device descriptor read/all, error -71 [446317.917783] usb usb1-port1: attempt power cycle [446318.568487] usb 1-1: new high-speed USB device number 5 using orion-ehci [446318.598617] usb 1-1: Using ep0 maxpacket: 8 [446318.700609] usb 1-1: device descriptor read/all, error -71 [446318.828458] usb 1-1: new high-speed USB device number 6 using orion-ehci [446318.858618] usb 1-1: Using ep0 maxpacket: 8 [446318.960611] usb 1-1: device descriptor read/all, error -71 [446318.960787] usb usb1-port1: unable to enumerate USB device 2nd [446648.177351] usb 1-1: new high-speed USB device number 7 using orion-ehci [446648.461621] usb 1-1: device descriptor read/all, error -71 [446648.589356] usb 1-1: new high-speed USB device number 8 using orion-ehci [446648.873612] usb 1-1: device descriptor read/all, error -71 [446648.873772] usb usb1-port1: attempt power cycle [446649.525309] usb 1-1: new high-speed USB device number 9 using orion-ehci [446649.649613] usb 1-1: device descriptor read/8, error -71 [446649.873634] usb 1-1: device descriptor read/8, error -71 [446650.109294] usb 1-1: new high-speed USB device number 10 using orion-ehci [446650.233608] usb 1-1: device descriptor read/8, error -71 [446650.457645] usb 1-1: device descriptor read/8, error -71 [446650.565446] usb usb1-port1: unable to enumerate USB device 3rd [446906.516659] usb 1-1: new high-speed USB device number 11 using orion-ehci [446906.672640] usb 1-1: Using ep0 maxpacket: 8 [446906.674543] usb 1-1: device descriptor read/all, error 8 [446906.808639] usb 1-1: new high-speed USB device number 12 using orion-ehci [446906.964630] usb 1-1: Using ep0 maxpacket: 8 [446906.966544] usb 1-1: device descriptor read/all, error 8 [446906.972787] usb usb1-port1: attempt power cycle [446907.624628] usb 1-1: new high-speed USB device number 13 using orion-ehci [446907.654614] usb 1-1: Using ep0 maxpacket: 8 [446907.661636] usb 1-1: device descriptor read/all, error 8 [446907.796623] usb 1-1: new high-speed USB device number 14 using orion-ehci [446907.826606] usb 1-1: Using ep0 maxpacket: 8 [446907.833639] usb 1-1: device descriptor read/all, error 8 [446907.840740] usb usb1-port1: unable to enumerate USB device 4th [447330.134465] usb 1-1: new high-speed USB device number 15 using orion-ehci [447330.290446] usb 1-1: Using ep0 maxpacket: 8 [447330.292544] usb 1-1: device descriptor read/all, error 8 [447330.426458] usb 1-1: new high-speed USB device number 16 using orion-ehci [447330.582432] usb 1-1: Using ep0 maxpacket: 8 [447330.584658] usb 1-1: device descriptor read/all, error 8 [447330.590518] usb usb1-port1: attempt power cycle [447331.242448] usb 1-1: new high-speed USB device number 17 using orion-ehci [447331.272618] usb 1-1: Using ep0 maxpacket: 8 [447331.279637] usb 1-1: device descriptor read/all, error 8 [447331.414424] usb 1-1: new high-speed USB device number 18 using orion-ehci [447331.443595] usb 1-1: Using ep0 maxpacket: 8 [447331.451608] usb 1-1: device descriptor read/all, error 8 [447331.458557] usb usb1-port1: unable to enumerate USB device

Hi, I'm using an esprossobin with Debian Stretch with Armbian Linux 4.19.56-mvebu64. However regardless inwhat USB-TTL / Serial adapter I connect to he espressobin's USB2.0 port I don't get a ttyUSB0 device I tried to use a Prolific and a couple of others I got lend from a friend

I know it's not you to blame, but it's again disappointing with a GlobalScale product, which I bought as *up* to 1.2 GHz, just to find, that it's not even good enough to scale down to 1000/800, but even down to 800/800 to get a stable service.

Started from 5.75 image again and installed the below one by one with a reboot in between linux-u-boot-espressobin-next 5.85 --> OK linux-stretch-root-next-espressobin 5.85 --> OK linux-image-next-mvebu64 5.84 --> hangs (linux-dtb-next-mvebu64 5.85) PS: Once again 5.75 -> linux-u-boot-espressobin-next 5.85 --> OK linux-stretch-root-next-espressobin 5.85 --> OK linux-dtb-next-mvebu64 5.85 --> OK but as there's no image between 5.75 and 5.84 I'll leave it that way for now (and I think you should revoke 5.84 as well!?)

OT: when the PSUs of my SheevaPlugs started to fail I "swore" myself not buy any other device from Globalscale in the future, but even though I did it again ...

OK, imaged Armbian_5.75_Espressobin_Debian_stretch_next_4.19.20.img to other SD and started from scratch --> OK Did apt-get update & upgrade which brought me back to 5.85 (5.84 image), but system hangs again after reboot So I think it's up to you now ;-)

booting from SD, too. Checked FS of the SD which is clean and dd'ed to another SD, but same issue

Just updated both my cubietruck and espressobin to 5.85, however the latter doesn't up come again after the update (from 5.83 IMO). (Had to get it out of the basement and) the console gives me the following error msg, now: Marvell>> boot starting USB... USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found / ** Bad device usb 0 ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ ** Bad device usb 0 ** ## Executing script at 06d00000 Wrong image format for "source" command scanning bus for devices... Device 0: unknown device / ** Bad device scsi 0 ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ ** Bad device scsi 0 ** ## Executing script at 06d00000 Wrong image format for "source" command / Card did not respond to voltage select! ** Bad device mmc 1 ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ Card did not respond to voltage select! ** Bad device mmc 1 ** ## Executing script at 06d00000 Wrong image format for "source" command / ** File not found /boot.scr ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ 1119 bytes read in 13 ms (84 KiB/s) ## Executing script at 06d00000 221 bytes read in 5 ms (43 KiB/s) 16488960 bytes read in 706 ms (22.3 MiB/s) 6196865 bytes read in 275 ms (21.5 MiB/s) ** File not found /boot/dtb/marvell/armada-3720-community.dtb ** 8942 bytes read in 9 ms (969.7 KiB/s) ## Loading init Ramdisk from Legacy Image at 01100000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 6196801 Bytes = 5.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 06000000 Booting using the fdt blob at 0x6000000 Loading Ramdisk to 3f042000, end 3f62ae41 ... OK Using Device Tree in place at 0000000006000000, end 00000000060052ed Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 4.19.41-mvebu64 (root@armbian.com) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f8e1a2eed33b1edc85d4] (Linaro GCC 7.4-2019.02)) #5.85 SMP PREEMPT Wed May 8 16:07:35 CEST 2019 [ 0.000000] Machine model: Globalscale Marvell ESPRESSOBin Board [ 0.000000] earlycon: ar3700_uart0 at MMIO 0x00000000d0012000 (options '') [ 0.000000] bootconsole [ar3700_uart0] enabled Loading, please wait... starting version 232 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.29.2 [/sbin/fsck.ext4 (1) -- /dev/mmcblk1p1] fsck.ext4 -a -C0 /dev/mmcblk1p1 /dev/mmcblk1p1: clean, 55272/444624 files, 453885/1900644 blocks done. done. Begin: Running /scripts/local-bottom ... /scripts/local-bottom/mdadm: 2: /scripts/local-bottom/mdadm: rm: not found done. Begin: Running /scripts/init-bottom ... done. [ 6.537013] SError Interrupt on CPU1, code 0xbf000001 -- SError [ 6.537017] CPU: 1 PID: 1 Comm: init Not tainted 4.19.41-mvebu64 #5.85 [ 6.537019] Hardware name: Globalscale Marvell ESPRESSOBin Board (DT) [ 6.537021] pstate: 20000005 (nzCv daif -PAN -UAO) [ 6.537023] pc : get_page_from_freelist+0x5c/0x10e8 [ 6.537025] lr : __alloc_pages_nodemask+0xf4/0xb48 [ 6.537026] sp : ffffff8008033970 [ 6.537028] x29: ffffff8008033970 x28: 0000000000000002 [ 6.537032] x27: 00000000006200ca x26: 0000000000000081 [ 6.537035] x25: 0000000000000000 x24: 0000000000000000 [ 6.537039] x23: 0000000000000000 x22: ffffff8008033b38 [ 6.537042] x21: ffffffc03ffeb500 x20: 0000000000000081 [ 6.537046] x19: ffffffc03ffea180 x18: 0000000000000000 [ 6.537049] x17: 0000000000000000 x16: 0000000000000000 [ 6.537053] x15: 0000000000000000 x14: 0000000000000000 [ 6.537056] x13: 0000000000000000 x12: 0000000000000000 [ 6.537060] x11: 0000000000000000 x10: 0000000000000000 [ 6.537063] x9 : 0000000000000000 x8 : 0000000000000000 [ 6.537066] x7 : 0000000000000000 x6 : 0000000000000000 [ 6.537070] x5 : 0000000000000014 x4 : 0000000000000000 [ 6.537073] x3 : 0000000000000000 x2 : 00000000000000c0 [ 6.537077] x1 : 0000000000000001 x0 : 0000000000000068 [ 6.537081] Kernel panic - not syncing: Asynchronous SError Interrupt [ 6.537083] CPU: 1 PID: 1 Comm: init Not tainted 4.19.41-mvebu64 #5.85 [ 6.537085] Hardware name: Globalscale Marvell ESPRESSOBin Board (DT) [ 6.537087] Call trace: [ 6.537088] dump_backtrace+0x0/0x1a0 [ 6.537089] show_stack+0x14/0x20 [ 6.537091] dump_stack+0x9c/0xbc [ 6.537092] panic+0x130/0x2a4 [ 6.537093] nmi_panic+0x6c/0x70 [ 6.537095] arm64_serror_panic+0x74/0x88 [ 6.537096] do_serror+0x134/0x138 [ 6.537098] el1_error+0x7c/0xdc [ 6.537099] get_page_from_freelist+0x5c/0x10e8 [ 6.537101] __alloc_pages_nodemask+0xf4/0xb48 [ 6.537102] alloc_pages_vma+0x88/0x210 [ 6.537104] __handle_mm_fault+0x3e8/0xdc8 [ 6.537105] handle_mm_fault+0x11c/0x1e0 [ 6.537107] do_page_fault+0x1c0/0x480 [ 6.537108] do_translation_fault+0x58/0x60 [ 6.537110] do_mem_abort+0x54/0x100 [ 6.537111] el0_da+0x20/0x24 [ 6.537130] SMP: stopping secondary CPUs [ 6.537131] Kernel Offset: disabled [ 6.537133] CPU features: 0x0,2080200c [ 6.537134] Memory Limit: none [ 6.755334] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---

Thx for the reply. That's odd, so the issue might be caused by the fact, that I'm not using an original Prolific, but cheap "China" clone cable!? I though this wouldn't cause an issue with Linux, as it does with Windows (with the latter I had to downgrade to a former Prolific driver to get it working, as the actual would detect the "fake".)

Hello, I own boards of two different manufactures, namely a Cubietruck and an Espressobin. Before a recent Kernel update these days I was still greeted with the following messages: Welcome to ARMBIAN 5.73 stable Debian GNU/Linux 9 (stretch) 4.19.17-sunxi Welcome to ARMBIAN 5.73 stable Debian GNU/Linux 9 (stretch) 4.19.18-mvebu64 But even after the update - IMO apt-get was telling we're going from 5.73 to 5.75 versions of the files the version number in the greeting is still 5.73 Welcome to ARMBIAN 5.73 stable Debian GNU/Linux 9 (stretch) 4.19.20-sunxi Welcome to ARMBIAN 5.73 stable Debian GNU/Linux 9 (stretch) 4.19.20-mvebu64 I know that this might be a more cosmetic issue/question, but what criteria(s) drive(s) the version numbering?

thx! - but don't think so (using armbian as didn't want to bother with those details myself ;-)

no, but now: CT y EB n

Sorry for hijacking this thread, but I'm also having (two) issues with having USB Serial Support not working. Background: I plan to migrate my setup off a Cubiertuck over to an Espressobin, and as both devices are "remote" in the basement I thought I could ease my life by cross-connecting their "uart/serial/usb/jtag" ports. So a micro-usb cable is connected from the CT's USB to the EB's micro-USB port Cubietruck with ARMBIAN 5.70 stable Debian GNU/Linux 9 (stretch) 4.19.13-sunxi root@share:~# lsusb Bus 003 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port root@share:~# dmesg | grep -i usb usb 3-1: new full-speed USB device number 2 using ohci-platform usb 3-1: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 4.00 usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 3-1: Product: USB-Serial Controller D usb 3-1: Manufacturer: Prolific Technology Inc. usbcore: registered new interface driver usbserial_generic usbserial: USB Serial support registered for generic usbcore: registered new interface driver pl2303 usbserial: USB Serial support registered for pl2303 usb 3-1: pl2303 converter now attached to ttyUSB0 and an USB-TTL cable is connected from the EB's USB2.0 port to the CT's JTAG pins Espressobin with ARMBIAN 5.70 stable Debian GNU/Linux 9 (stretch) 4.19.14-mvebu64 root@espressobin:~# lsusb Bus 001 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port root@espressobin:~# dmesg | grep -i USB usb 1-1: new high-speed USB device number 2 using orion-ehci usb 1-1: config 1 interface 0 altsetting 0 bulk endpoint 0x2 has invalid maxpacket 64 usb 1-1: config 1 interface 0 altsetting 0 bulk endpoint 0x83 has invalid maxpacket 64 usb 1-1: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 3.00 usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-1: Product: USB-Serial Controller usb 1-1: Manufacturer: Prolific Technology Inc. usbcore: registered new interface driver uas Issue #1: On the CT I can connect to the EB via root@share:~# minicom -b 115200 --device /dev/ttyUSB0, but though I e.g. see the message on "the console" while rebooting the EB I can't interact with it, e.g. hitting "CR" during uboot does not work, nor can I logon via the console as it seems that no keystroke gets there. Issue #2: is even worse, as I don't have a ttyUSB0 port on the EB for CB's JTAG port at all. What's going wrong here? Why is it registered as an UAS? Using the same connection with puTTY on Windows I have noch issue to get to the CB's serial port. (Only issue is that the USB-TTL cable which I brought seems to be Prolific fake, which is disabled by recent Prolific's device drivers. Is that the same with Debian?)

BTW: fell into the same pit and also got it working again with flash-image-1g-1cs-1000_800_boot_sd_and_usb.bin (v? from May 10th 2018). Got mine with only one chip on the back just a few days ago shipped from Amazon/US. However to You can obtain numbers from the current boot prompt., what are the appropriate commands to figure the right u-boot version for a board? It might be helpful to mention those on the site as well ;-)

Maybe a long shot: rather than setting up armbian on my new ESPRESSObin (epb), installing needed SW and tools, porting configs off my Cubietruck (cbt), would it be possible to tweak the cbt's SDcard / FS to boot on the ESPRESSObin? If I'm not mistaken the cbtis armhf based and all those binaries should also run on the epb!? Would it be "good enough" to add the arm64 architecture to the CBT with "dpkg --add-architecture arm64" and then to install linux-u-boot-espressobin-next linux-image-next-mvebu64 linux-headers-next-mvebu64 linux-firmware-image-next-mvebu64 linux-dtb-next-mvebu64 linux-$(lsb_release -cs)-root-next-espressobin shut down the cbt and put the card into the epb, booting it in the epb?

We're 10 days later and I'm happy to report that I haven't experienced any crashes or issues on this quoted setup (since upgraded back to v5.41 (or latest for dtb, image and u-boot)), though still having frozen tvheadend at 4.3-1067~g68d0bc5~xenial.

I had another freeze though having downgraded my Cubietruck to v5.35 and I also had a suspicion about tvheadend and downgraded that to 4.3-1067~g68d0bc5~xenial and froze it as well. As the CB was running stable since the last 10 days I just unfroze the kernel and updated to v5.41, but left tvheadend at 4.3-1067~g68d0bc5~xenial. Will keep you updated

Yes, I use the Ubuntu xenial version on my Cubietruck with Armbian Debian stretch deb https://dl.bintray.com/tvheadend/deb xenial unstable # deb-src https://dl.bintray.com/tvheadend/deb stretch stable #4 components are available: # release - for the latest official release # stable - for nightly build of latest release branch (will pick up fixes quicker than release) # unstable - for nightly build of master branch (don't use on production systems) # obsolete - historic 3.4 build to keep older users happy However you have to be aware that the last time I looked not all "components" have available arm binaries

My cubietruck was also running very stable for month, but I found this thread, because I also seem to have this "freezing" issue since I updated from v5.37? to v5.38. Hoped v5.41 "bugfix update on sunxi/sunxi64 kernel" solved it, but I still have those freezes after a couple of hours / few days. (ssh still connects, but I don't get to a prompt, thus I have to power cycle.) I'll make a backup of the SD in tomorrows maint window (when family's gone ;-) and try to downgrade as advised by Igor. PS: downgraded to v5.35 (there's no 5.37 for me) apt install linux-image-next-sunxi=5.35 linux-dtb-next-sunxi=5.35 and froze kernel updates via armbian-config ____ _ _ _ _ / ___| _| |__ (_) ___| |_ _ __ _ _ ___| | __ | | | | | | '_ \| |/ _ \ __| '__| | | |/ __| |/ / | |__| |_| | |_) | | __/ |_| | | |_| | (__| < \____\__,_|_.__/|_|\___|\__|_| \__,_|\___|_|\_\ Welcome to ARMBIAN 5.38 stable Debian GNU/Linux 9 (stretch) 4.13.16-sunxi Linux share 4.13.16-sunxi #20 SMP Fri Nov 24 19:50:07 CET 2017 armv7l