.jpg.cff48b1a9d2ce236b80e0709413054db.jpg)
Z11ntal33r
-
Posts
56 -
Joined
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Z11ntal33r
-
-
Same issue here as well. I have ended up in this situation multiple times for the last year and I think it's time to move over to a more powerful board. Not sure yet which one I should pick up yet. One option might be Orange Pi 5.
For everyone else with kernel issues, here is what I do when I use an. eMMC setup
1. Burn new raw image to SD (e.g. `Armbian_23.11.2_Odroidn2_jammy_current_6.1.68`)
2. Power it on and make sure it works and libs are fine. E.g `dm_mod`
3. Mounts eMMC partition
4. Move both boot folder and libs (E.g. folder `6.1.68-current-meson64` in /lib/modules to lib/modules) to eMMC
5. Run the following in both boot folders: `mkimage -A arm64 -O linux -T kernel -C none -a 0x1080000 -e 0x1080000 -n Linux -d vmlinuz-* uImage`6. Reboot and verify that setup on eMMC works
-
It seems that I am not able to boot directly from eMMC and use the second method Boot from eMMC from armbian-install. However, I am able to set mmcblk1 (eMMC) as SD and choose method 1 Boot from SD where I end up by booting from SD and using my eMMC as root. Prior I could boot without the SD carad, which is what I want, but at least this way I am able to use my eMMC.
mmcblk0 is my SD cardmmcblk1 is my eMMC
___ _ _ _ _ _ ____ / _ \ __| |_ __ ___ (_) __| | | \ | |___ \ | | | |/ _` | '__/ _ \| |/ _` | | \| | __) | | |_| | (_| | | | (_) | | (_| | | |\ |/ __/ \___/ \__,_|_| \___/|_|\__,_| |_| \_|_____| Welcome to Armbian 23.8.1 Jammy with Linux 6.1.50-current-meson64 No end-user support: community creations System load: 5% Up time: 1 min Memory usage: 5% of 3.69G IP: 192.168.45.19 CPU temp: 42°C Usage of /: 12% of 15G RX today: 154.5 MiB user@odroidn2:~$ sudo lsblk [sudo] password for gzjlspxwkh: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk0 179:0 0 14.8G 0 disk └─mmcblk0p1 179:1 0 14.7G 0 part /boot /media/mmcboot mmcblk1 179:32 0 14.6G 0 disk └─mmcblk1p1 179:33 0 14.4G 0 part /var/log.hdd / mmcblk1boot0 179:64 0 4M 1 disk mmcblk1boot1 179:96 0 4M 1 disk zram0 252:0 0 1.8G 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk -
I am actually not able to boot from eMMC at all after the upgrade earlier, even after a clean install to eMMC with either Armbian_23.8.1_Odroidn2_jammy_current_6.1.50 or Armbian_23.5.1_Odroidn2_jammy_current_6.1.30. Not sure if I should delete /dev/mmcblk1boot0/1 as well before each clean install or what to do to be able to boot from eMMC again
-
Same issue here with Odroid N2 as the kernel did not update successfully it seems, but armbian-config did (from 6.1.11-meson64 and armbian 23.02). I ended up with re-installing from a clean image. However, after upgrading packages, the welcoming message now says: "No end-user support: community creations". Not sure why I would receive it as I only have ran apt update and upgrade after booting up before doing a restart.
Image: Armbian_23.8.1_Odroidn2_jammy_current_6.1.50
-
-
Thanks for reaching out
I've default settings and I did a clean install yesterday. The few steps I did was to run cryptstetup benchmark which was fine, ran a script to install and setup packages and so on, tried to mount the drive, but Illegal instruction showed. After that, all cryptsetup benchmarks failed.
I can try a new clean build later today, lower the cpu freq and see if that's better. I am also thinking about switching from Jammy to Bullseye in order to apt-pin newer packages of cryptsetup to see if that solves the issue. I that doesn't help, I will think about buying a new SBC, unless I switch to something else than Armbian, which I would like to avoid -
Hi, I have two meson64 SBCs where one is Khadas VIM 3 and the other is Odroid N2. They have been running almost the same setup and there has been minor differences with time.
For the past months, I have had issues with the error Illegal instruction for my Odroid N2 server. I did a clean install earlier today (Armbian_23.02.2_Odroidn2_jammy_current_6.1.11) without success. For instance, I often face the error when running cryptsetup benchmark. Most of the time I have to reboot multiple times, reinstall cryptsetup packages, try the armhf packages and more. I have never had the same issue with Khadas VIM 3.
The issue seems to be related to argon2i and the question is what and where should I look further regarding how to solve this. I've tried switching supported kernel versions, 6.1.*, 5.19.*, 5.10.*, without success. Trying legacy kernel 4.9.* had some issues resulting in the board not booting.
Output when everything is fine
| => sudo cryptsetup benchmark
Spoiler# Tests are approximate using memory only (no storage IO). PBKDF2-sha1 575508 iterations per second for 256-bit key PBKDF2-sha256 1057032 iterations per second for 256-bit key PBKDF2-sha512 412825 iterations per second for 256-bit key PBKDF2-ripemd160 328501 iterations per second for 256-bit key PBKDF2-whirlpool 128501 iterations per second for 256-bit key argon2i 4 iterations, 628524 memory, 4 parallel threads (CPUs) for 256-bit key (requested 2000 ms time) argon2id 4 iterations, 631733 memory, 4 parallel threads (CPUs) for 256-bit key (requested 2000 ms time) # Algorithm | Key | Encryption | Decryption aes-cbc 128b 631.9 MiB/s 947.2 MiB/s serpent-cbc 128b 43.6 MiB/s 47.7 MiB/s twofish-cbc 128b 77.6 MiB/s 80.4 MiB/s aes-cbc 256b 545.1 MiB/s 840.0 MiB/s serpent-cbc 256b 43.8 MiB/s 47.6 MiB/s twofish-cbc 256b 78.0 MiB/s 80.3 MiB/s aes-xts 256b 704.5 MiB/s 697.8 MiB/s serpent-xts 256b 43.9 MiB/s 48.2 MiB/s twofish-xts 256b 79.9 MiB/s 82.6 MiB/s aes-xts 512b 638.0 MiB/s 637.8 MiB/s serpent-xts 512b 44.8 MiB/s 48.2 MiB/s twofish-xts 512b 81.4 MiB/s 82.6 MiB/s
Output when facing the issue. It's always after trying to open with cryptsetup prior and I think it's in general| => sudo cryptsetup benchmark
Spoiler# Tests are approximate using memory only (no storage IO). PBKDF2-sha1 574877 iterations per second for 256-bit key PBKDF2-sha256 1057032 iterations per second for 256-bit key PBKDF2-sha512 412825 iterations per second for 256-bit key PBKDF2-ripemd160 328501 iterations per second for 256-bit key PBKDF2-whirlpool 129007 iterations per second for 256-bit key Illegal instruction
-
I receive "No end-user support: built from trunk" at MoTD even though I used a stable and recommended img: Armbian_21.05.4_Odroidn2_buster_current_5.10.43.img. Is that correct given it's a stable build?
Furthermore, I've received a kernel panick - not syncing: kernel stack overflow "Insufficient stack space to handle exception!". Are the logs saved a place? Can't find it in journalctl.
-
This is a minor issue, but I'm hoping to get it solved as I've enjoyed the welcome screen for so long. For whatever reason after running my installation script which I've been using for years, the welcome screen changes when logging in over ssh. This happened some months ago. Any ideas on how or where I should look?
SpoilerFROM: ___ _ _ _ _ _ ____ / _ \ __| |_ __ ___ (_) __| | | \ | |___ \ | | | |/ _` | '__/ _ \| |/ _` | | \| | __) | | |_| | (_| | | | (_) | | (_| | | |\ |/ __/ \___/ \__,_|_| \___/|_|\__,_| |_| \_|_____| Welcome to Armbian 20.08.17 Focal with Linux 5.8.16-meson64 System load: 2% Up time: 7 min Memory usage: 4% of 3.55G IP: 192.168.0.28 CPU temp: 27°C Usage of /: 1% of 480G [ General system configuration (beta): armbian-config ] To run a command as administrator (user "root"), use "sudo <command>". See "man sudo_root" for details. To: Last login: Tue Oct 27 23:17:54 2020 from MYIP USER@HOSTNAME:~$
-
I think I found the root of the issue I had. It seems to be related to resolvconf and particularly resolvconf-pull-resolved where I had systemd-resolved installed and handling resolv.conf with a symlink. Removing the resolvconf package did the trick. I'll let the server run for some days, yet it seems fine some far. I'm going to make sure that I remove resolvconf in my installation script to prevent this mess from happening again... This is something to be aware of as others might be a victim of the issue as well. It's a quite serious one too.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968015
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967906
-
Thanks again for a great reply! I'll stay put to mainline and use 5.7 until 5.8 has matured.
I do not have high expectations or hope for a extremely stable experience with N2, but if it can somewhat give me a decent experience that will be more than enough. I bet I've changed my arm device in a year or two. Out of couriosity, do you have any similar boards you would recommend for NAS usage in the $100-150 price range? -
So if you were going to setup N2 as a home NAS, you would rather use 5.7 for some time before jumping to a higher stable kernel (>= 5.9) rather than setup 4.9 and staying there?
-
Thanks for letting me know! I'll do a new clean install using Armbian_20.08.1_Odroidn2_focal_current_5.8.5 and change kernel to use legacy in armbian-config forwards. I'm looking for a much more stable experience running a home server than what I've encountered the last few months running mainline.
-
Armbianmonitor:
Odroid-N2 using Armbian_20.08.1_Odroidn2_focal_current_5.8.5
I've recently got a "Connection timed out" issue. For instance, I can open files with nano, use htop, armbian-config, update and upgrade packages, but I can't reboot (everything over ssh). I'm having a feeling that the issue started when I tried to figure out if it's possible to get HDMI to work with my 4K TV when the HDMI cable is not plugged in at boot. In that case, I booted several times and chaged boot.ini with setenv display_autodetect "false", setenv hdmimode "1080p60hz" and setenv disablehpd "true" without success. armbianmonitor -u information is attached at the end in my post where this line might be of interest: "[ 0.000000] [Firmware Bug]: Kernel image misaligned at boot, please fix your bootloader!".
Conection timed out message:Spoiler$ sudo systemctl reboot Failed to set wall message, ignoring: Connection timed out Failed to reboot system via logind: Connection timed out Failed to start reboot.target: Connection timed out See system logs and 'systemctl status reboot.target' for details. It is possible to perform action directly, see discussion of --force --force in man:systemctl(1). $ sudo systemctl reboot --force Failed to execute operation: Connection timed out It is possible to perform action directly, see discussion of --force --force in man:systemctl(1). $ sudo systemctl status reboot.target Failed to get properties: Connection timed out
Running armbianmonitor -v:Spoiler$ sudo armbianmonitor -v Starting package integrity check. This might take some time. Be patient please... It appears you may have corrupt packages. This is usually a symptom of filesystem corruption caused by SD cards or eMMC dying or burning the OS image to the installation media went wrong. The following changes from packaged state files were detected: /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf
Does armbianmonitor -v give any useful information? It detects corrupted pacakges, but which? The 10-globally-managed-devices.conf does not seem to exist. At least I can't read it with cat or nano.
sysctl --systemSpoiler$ sudo sysctl --system * Applying /etc/sysctl.d/10-console-messages.conf ... kernel.printk = 4 4 1 7 * Applying /etc/sysctl.d/10-ipv6-privacy.conf ... net.ipv6.conf.all.use_tempaddr = 2 net.ipv6.conf.default.use_tempaddr = 2 * Applying /etc/sysctl.d/10-kernel-hardening.conf ... kernel.kptr_restrict = 1 * Applying /etc/sysctl.d/10-link-restrictions.conf ... fs.protected_hardlinks = 1 fs.protected_symlinks = 1 * Applying /etc/sysctl.d/10-magic-sysrq.conf ... kernel.sysrq = 176 * Applying /etc/sysctl.d/10-network-security.conf ... net.ipv4.conf.default.rp_filter = 2 net.ipv4.conf.all.rp_filter = 2 * Applying /etc/sysctl.d/10-ptrace.conf ... kernel.yama.ptrace_scope = 1 * Applying /etc/sysctl.d/10-zeropage.conf ... vm.mmap_min_addr = 32768 * Applying /usr/lib/sysctl.d/50-default.conf ... net.ipv4.conf.default.promote_secondaries = 1 sysctl: setting key "net.ipv4.conf.all.promote_secondaries": Invalid argument net.ipv4.ping_group_range = 0 2147483647 net.core.default_qdisc = fq_codel fs.protected_regular = 1 fs.protected_fifos = 1 * Applying /usr/lib/sysctl.d/50-pid-max.conf ... kernel.pid_max = 4194304 * Applying /etc/sysctl.d/99-sysctl.conf ... kernel.printk = 3 4 1 3 vm.swappiness = 30 net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.lo.disable_ipv6 = 1 kernel.sysrq = 0 net.ipv4.tcp_sack = 0 net.ipv4.tcp_timestamps = 0 net.ipv4.icmp_echo_ignore_all = 1 net.ipv6.icmp.echo_ignore_all = 1 kernel.randomize_va_space = 2 fs.suid_dumpable = 0 kernel.dmesg_restrict = 1 kernel.yama.ptrace_scope = 1 kernel.unprivileged_bpf_disabled = 1 net.core.bpf_jit_enable = 1 net.core.bpf_jit_harden = 1 net.ipv4.tcp_syncookies = 1 net.ipv4.tcp_syn_retries = 2 net.ipv4.tcp_synack_retries = 2 net.ipv4.tcp_max_syn_backlog = 4096 net.ipv4.ip_forward = 0 net.ipv4.conf.all.forwarding = 0 net.ipv4.conf.default.forwarding = 0 net.ipv6.conf.all.forwarding = 0 net.ipv6.conf.default.forwarding = 0 net.ipv4.conf.all.accept_redirects = 0 net.ipv4.conf.default.accept_redirects = 0 net.ipv4.conf.all.secure_redirects = 0 net.ipv4.conf.default.secure_redirects = 0 net.ipv6.conf.all.accept_redirects = 0 net.ipv6.conf.default.accept_redirects = 0 net.ipv4.conf.all.send_redirects = 0 net.ipv4.conf.default.send_redirects = 0 net.ipv4.conf.all.accept_source_route = 0 net.ipv4.conf.default.accept_source_route = 0 net.ipv6.conf.all.accept_source_route = 0 net.ipv6.conf.default.accept_source_route = 0 net.ipv4.conf.all.bootp_relay = 0 net.ipv4.conf.all.proxy_arp = 0 net.ipv4.conf.all.arp_ignore = 1 net.ipv4.conf.all.arp_announce = 2 net.ipv4.tcp_rfc1337 = 1 net.ipv4.conf.default.log_martians = 0 net.ipv4.conf.all.log_martians = 0 net.ipv4.icmp_ignore_bogus_error_responses = 1 net.ipv4.icmp_echo_ignore_broadcasts = 1 net.ipv4.route.flush = 1 net.ipv6.route.flush = 1 * Applying /usr/lib/sysctl.d/protect-links.conf ... fs.protected_fifos = 1 fs.protected_hardlinks = 1 fs.protected_regular = 2 fs.protected_symlinks = 1 * Applying /etc/sysctl.conf ... kernel.printk = 3 4 1 3 vm.swappiness = 30 net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.lo.disable_ipv6 = 1 kernel.sysrq = 0 net.ipv4.tcp_sack = 0 net.ipv4.tcp_timestamps = 0 net.ipv4.icmp_echo_ignore_all = 1 net.ipv6.icmp.echo_ignore_all = 1 kernel.randomize_va_space = 2 fs.suid_dumpable = 0 kernel.dmesg_restrict = 1 kernel.yama.ptrace_scope = 1 kernel.unprivileged_bpf_disabled = 1 net.core.bpf_jit_enable = 1 net.core.bpf_jit_harden = 1 net.ipv4.tcp_syncookies = 1 net.ipv4.tcp_syn_retries = 2 net.ipv4.tcp_synack_retries = 2 net.ipv4.tcp_max_syn_backlog = 4096 net.ipv4.ip_forward = 0 net.ipv4.conf.all.forwarding = 0 net.ipv4.conf.default.forwarding = 0 net.ipv6.conf.all.forwarding = 0 net.ipv6.conf.default.forwarding = 0 net.ipv4.conf.all.accept_redirects = 0 net.ipv4.conf.default.accept_redirects = 0 net.ipv4.conf.all.secure_redirects = 0 net.ipv4.conf.default.secure_redirects = 0 net.ipv6.conf.all.accept_redirects = 0 net.ipv6.conf.default.accept_redirects = 0 net.ipv4.conf.all.send_redirects = 0 net.ipv4.conf.default.send_redirects = 0 net.ipv4.conf.all.accept_source_route = 0 net.ipv4.conf.default.accept_source_route = 0 net.ipv6.conf.all.accept_source_route = 0 net.ipv6.conf.default.accept_source_route = 0 net.ipv4.conf.all.bootp_relay = 0 net.ipv4.conf.all.proxy_arp = 0 net.ipv4.conf.all.arp_ignore = 1 net.ipv4.conf.all.arp_announce = 2 net.ipv4.tcp_rfc1337 = 1 net.ipv4.conf.default.log_martians = 0 net.ipv4.conf.all.log_martians = 0 net.ipv4.icmp_ignore_bogus_error_responses = 1 net.ipv4.icmp_echo_ignore_broadcasts = 1 net.ipv4.route.flush = 1 net.ipv6.route.flush = 1
armbianmonitor -uSpoilerFull log: https://pastebin.com/MeJdigT8
Snippets:[ 0.000000] [Firmware Bug]: Kernel image misaligned at boot, please fix your bootloader! ... [ 1.977141] thermal thermal_zone0: binding zone cpu-thermal with cdev thermal-cpufreq-0 failed:-17 [ 1.977817] cpufreq: cpufreq_online: CPU2: Running at unlisted freq: 999999 KHz [ 1.977878] cpufreq: cpufreq_online: CPU2: Unlisted initial frequency changed to: 1000000 KHz [ 1.978854] thermal thermal_zone0: binding zone cpu-thermal with cdev thermal-cpufreq-1 failed:-17 ...
I guess the only way to reboot is to pull the plug? Or could it be done without pulling the plug if I connect to the N2 with UART? I'm thinking about doing a new fresh install, but before that, is it worth trying to use the legacy kernel (4.9)? Thanks for the awesome work with Armbian! It has truly been a blessing since I first discovered it! -
25 minutes ago, balbes150 said:
Ver 20.05.0 20200211
What stands trunk for in the filename Armbian_20.05.0-trunk_Arm-64_*? And is there a particular reason for not compiling using latest stable kernel or mainline as 5.5-rc6 is almost a month old?
-
I've done multiple installations on VIM3 using a clean SD card with both Armbian_19.11.5_Arm-64_buster_current_5.5.0-rc6_20200127 and Armbian_20.02.0-rc1.030_Arm-64_buster_current_5.5.0-rc6_20200129. The color issue appear on both of the images as well as earlier and the simple fix by swapping u-boot files fixes it.
My main concern is the following error which I've never seen before and apply to both images. There are thousands of the same error message in journalctl.
SpoilerFeb 03 21:17:46 aml agetty[1689]: /dev/ttyS2: not a tty Feb 03 21:17:50 aml systemd[1]: systemd-fsckd.service: Succeeded. Feb 03 21:17:53 aml systemd[1]: systemd-hostnamed.service: Succeeded. Feb 03 21:17:56 aml systemd[1]: serial-getty@ttyS2.service: Succeeded. Feb 03 21:17:57 aml systemd[1]: serial-getty@ttyS2.service: Service RestartSec=100ms expired, scheduling restart. Feb 03 21:17:57 aml systemd[1]: serial-getty@ttyS2.service: Scheduled restart job, restart counter is at 3. Feb 03 21:17:57 aml systemd[1]: Stopped Serial Getty on ttyS2. Feb 03 21:17:57 aml systemd[1]: Started Serial Getty on ttyS2.
Update:
Running systemctl disable serial-getty@ttyS2.service && systemctl disable serial-getty@ttyS2.service fixed it. -
46 minutes ago, balbes150 said:
I do not know
No problem. Then I'll do a clean install later today. Thanks for the incredible work!
-
I'm getting the following error after normal upgrade with apt from a clean install earlier in January on a VIM3. Never encountered this issue before. I'm thinking about doing a new clean install after overwriting the whole SD card with zeros. @balbes150, are you going to do new builds for kernel 5.5.* in the next 2-3 days for current? Otherwise I'll use Armbian_20.02.0-rc1.030_Arm-64_*_current_5.5.0-rc6_20200129.img. I guess there isn't much of a change between latest rc6 to final.
mount: /boot: wrong fs type , bad option , bad superblock, missing codepage or helper program, or other error
-
@bxm, In both functions, syncToDisk () and syncFromDisk (), it should be "sync /" instead of only "sync" (without the quotes) and the issue is fixed? If that's the case, could you add a PR request on Github for the change?
Update
I can confirm that changing "sync" to both "sync /" or "sync /var" did not wake up my hdds or trigger any hdd-spinup logging according to "systemctl status hd-idle". Thanks!
-
On 9/19/2019 at 10:22 AM, balbes150 said:
This text is outdated and it is not necessary to pay attention to it.
Good to know! Choosing "default" worked perfectly and I built kernel 5.3.0 with the latest commit v20190918. I can see from GH source that you did include the patch dwc3/core: xHCI host not responding to stop endpoint command into commit v20190918. Thanks!
For meson-g12 users: If you want to upgrade kernel to 5.3.0 with balbes150 v20190918 patches, the .deb files can be downloaded at: Armbian 5.96 and kernel 5.3.0 for meson-g12 devices (v.20190918) -
14 hours ago, balbes150 said:
Build version NEXT is very naughty and is intended for experienced users who know the process of kernel build and the build Armbian (used source code directly from GIT Linux), also requires additional manual operations to configure a shared build (disable wireguard, etc.). You'd better use the "default" option.
Current fixes address only a few model specific errors.
The reason for why I did not choose "default" was that it states: "Vendor provided / legacy". I do not want a vendor kernel, I want to update my 5.3RC6 kernel to 5.3.0.
I ask again: Your build Armbian_5.96_Aml-g12_Ubuntu_bionic_dev_5.3.0_20190917 you uploaded fixed the IO errors over USB3.0 interface for g12 devices. Did you actually include the patch i referred to into this build or is it pure kernel 5.3.0? -
13 hours ago, balbes150 said:
Use the DTB from the previous image. There is an error in the current DTB for VIM3.
Yeah, that did the trick! With the build Armbian_5.96_Aml-g12_Ubuntu_bionic_dev_5.3.0_20190917 you uploaded, I'm finally able to copy/move files over the USB3.0 interface without any IO errors. Did you actually include the patch i referred to into this build or is it pure kernel 5.3.0?
One more thing. I tried to build the kernel files by following your guide at https://github.com/150balbes/Build-Armbian, but when I was building, I faced an error as seen from the picture attached. I've only followed your guide and selected "U-boot and kernel packages" -> "Do not change the kernel configuration" -> "aml-g12" -> "next". I want to upgrade my current installed build to the latest kernel with the patch. Any ideas why it fails? Let me know if you want the whole output or any logs.Spoiler
Thanks for the great help BTW! It's awesome when someone from the community aid much more support than the actually support team who released the SBC...
-
6 hours ago, balbes150 said:
Try this version, it has a kernel with all the latest changes.
Unfortunately, with the build above I'm in a boot loop. I tried both booting from mSD slot and booting from a USB 3.0 mSD card reader. The latest line I can see on my TV is "OK Mounted /tmp." before it boots again. So I guess that the next line where it fails is "Found device /dev/...." etc.
This is what I did:- Installed the build to a brand new mSD card and changed both /extlinux/extlinux.conf and uEnv.ini to meson-g12b-a311d-khadas-vim3.dtb.
- Activated multi-boot and booted to mSD card. No other devices were connected expect from a keyboard.
PS: Which means that both Android VIM3_Pie_V190907 and my current Armbian_5.95_Aml-g12_Debian_buster_default_5.3.0-rc6_20190904 build is installed to eMMC.
I think it's easier to just upgrade kernel with my current system, so I will build the latest kernel files tomorrow both with and without the patch. I'll let you know when I've tested this, balbes150 -
19 minutes ago, balbes150 said:
This patch is for an old kernel, I don't work with this old kernel.
I understand. It's an unfortunate situation as the USB3.0 interface for meson-g12b devices is broken and neither Amlogic or Hardkernel devs want to send the patch upstream to mainline and follow it up (https://forum.odroid.com/viewtopic.php?f=176&t=33993&p=268688#p268598)... One should absolutely avoid using meson-g12b devices if you want to use USB3 then. At the current state, my VIM3 is pointless as I can't move files between my micro SD and USB Harddrives. So I guess I've to build my own kernel and include this patch
Tinkerboard not booting after updates
in Tinkerboard
Posted · Edited by Z11ntal33r
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