ASword
-
Posts
12 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by ASword
-
-
Yes, I'm building up a setup script so rebuilding my OS config isn't such a big deal. Just starting to go systematically through the steps again to see where the boot fails again. Should have more details soon.
Okay, so to be clear: there is a known hang at boot that requires a manual power cycle? Good to know while diagnosing my setup script, plus that's a show stopper for me since my application requires automatic and dependable restart after a reboot. I presume this is being debugged and we can expect an eventual solution?
Unfortunately I don't seem to be able to get my N2 to boot at all anymore, using either eMMC nor an SDCard, all with fresh flashes of the latest Armbian build. A bit mystified by how that can be.
-
Heh, no, no, not at all.
Unfortunately, after I installed a few more things I need (daemons, compilers, etc) it has stopped booting again. It all seems innocuous and not the kind of things that ought to stop the OS from booting! I’ll have to start over and reboot after every item to narrow down the cause.
-
Well this build certainly works a lot better (so far). Thanks for pointing me in the right direction.
-
lol... that was the latest build when I grabbed it. I guess more time went by since than I was aware. Will give it a go.
-
I've noticed that after powering it on there is a period when ssh waits until it says operation timed out, and after a while there is a period when it immediately says the host is down, then it goes back to waiting for it to time out. Seems to be repeating that at some cadence, so... trying to boot, failing and starting again?
-
Armbian_20.08.22_Odroidn2_buster_current_5.9.6.img
Booted, created 4 users. Then apt update, then apt upgrade. Then reboot again, and it doesn't come back up (that I can tell).
-
I've power cycled quite a few times... how many should I expect? And is this an "always" problem with Armbian, or just after an update? Bit of a non-starter for me if its an always.
-
I have an N2+ that I'm flashing Debian Buster onto an emm card. Have tried numerous times in several variations -- flash emm, boot system, log in via ssh, set up personal account, "apt update", "apt upgrade", reboot. After that I cannot log in via ssh anymore. I am using the system in headless mode and don't currently have a working serial connection (SiLabs hasn't updated their drivers to Big Sur yet) so I can't tell if the system is booting but ssh isn't working. Anyone know why "apt upgrade" would cause it to not boot or not present an ssh server properly?
-
Hello, new here. I'm trying to build a headless environment for my ORDOID N2 based on a stable Debian (hence Buster), but I need some packages which aren't in the Buster repo (e.g. a CLang >7). I've tried following some instructions I found for adding Bullseye testing repo, and it makes the packages available, but the installation doesn't go well. Is this an unreasonable thing to attempt? Can anyone offer any guidance for how to get newer packages onto my Buster build?
(anyone know when Bullseye will become the stable release?)
Debian Buster -- Cannot ssh after apt update/upgrade
in Beginners
Posted
unfortunately SiLabs haven’t updated their OS X drivers to make them BigSur friendly yet, and I needed BigSur for another project.
Well this is curious (and probably not usefully reproducible). My N2+ was refusing to boot and re-flashing the eMMC wasn't helping, so I flashed an SDCard and tried that (with eMMC removed). Didn't work. In frustration I flipped the MMC/SPI switch to SPI and back, and powered it back on (with both the eMMC and SDCard installed). Lo'and'behold it booted! So I went through the initial set-password-and-create-user-account process, then rebooted again... after which I had to do the initial setup process _again_. Now it boots as expected -- so for some reason the first time it booted from the SDcard, and the second time it booted from the eMMC (with both flash devices inserted). The docs seem to say it ought to prefer the eMMC if it is present, but apparently it didn't.
Anyhow, haven't gotten any further yet.
I think my residual problem arose because I installed too much while backports was in the apt sources list. By only having it active while I installed clang/llvm 8, and nothing else, I seem to end up in a good state. So far.