Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

hjheins

Members
  • Joined

  • Last visited

  1. thank you @umiddelb, That looks definitely similar, but not the same; it might have the same origin though (the firmware). It seems also the emmc card itself play a role here: as I mentioned I also have a 16GB emmc with armbian that works flawlessly every time on the same N2 with the same microcode (==the old one from 2019) The difference between the 2 emmc cards is this: the working one is orange, the failing one is red: https://wiki.odroid.com/accessory/emmc/reference_chart I am not even sure why this makes a difference, but apparently it does. I guess I will get curious enough a couple of days and try if with the updated microcode on the N2, the red one will behave, and can hold it's armbian. But that day is not today 🙂
  2. As a small update: I did an update of petitboot (apparently I never did that since I owned the N2), and installed Debian bookworm over the petitboot net installer. This worked and for some reason seems to be rock solid; no issues with loosing or corrupting boot files whatsoever. I have no clue what is diffent between the Armbian image and the netboot one to make such a big difference in behaviour. (well, I see some differences, but they seem to be minor and not obviously related to the issue at hand) I' ll keep an eye on this, and see if I can find out more of the reasons behind the differences.
  3. that looks really interesting. I'll dive into it. thanks a lot @usual user!
  4. Hi @usual user, when you say "flaky firmware" do you mean the spi boot/petitboot on teh Odroid N2? or do you mean flaky on the emmc module? The module I have is indeed of an older variety, so maybe that could have something to do with it? How can I find more info on your firmware build please? thanks
  5. Hello all, I am using an Odroid N2 with a 16Gb emmc and Armbian Bookworm. However as this got a bit small, I installed Armbian Bookworm to a new 64Gb emmc (Armbian is installed on an SD and can then be copied/installed to emmc). This seemed to work fine, and I had a running system. However, on the 3rd or 4th reboot, I got the error that the file "boot.scr" wasn't readable. With that, the emmc was not bootable anymore. I reinstalled multiple times, and each time, the emmc would work for a 2-5 boots, but no more. Each time, i got the error as above, or the error as below (partition could not be found) I never had this issue with the 16Gb emmc? Does anyone know this behaviour, or better: does anyone know what is causing this and how to solve it? thanks,

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.