Jump to content

Z11ntal33r

Members
  • Posts

    56
  • Joined

Recent Profile Visitors

2041 profile views
  1. 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
  2. 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
  3. 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 card mmcblk1 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
  4. 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
  5. 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
  6. @hexdump it seems that you were absolutely right regarding the issue here! After lowering the max CPU speed from 1900 to 1800, I've done more than 100 benchmarks without facing Illegal instruction Thank you very, very much!
  7. 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
  8. 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 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
  9. 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.
  10. 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?
  11. 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
  12. 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?
  13. 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?
  14. 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.
  15. 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: Running armbianmonitor -v: 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 --system armbianmonitor -u 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!
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines