NOBL

My lsusb just shows the "ids" of the controller of connected drives but not the drives themselves. Neither the external disks nor the Ethernet HW were detected. I checked the directories/files in /etc/modules/6.1.x-meson64. The directory structures of kernel 6.1.11, 6.1.30 nd 6.1.42 are the same. However, kernel 6.1.11 seems to expect that the modules are compressed, it loads the modules and everything is fine for me. The filenames all end with .ko.xz while the modules from kernel 6.1.30 (Armbian bookworm version in the official download images) and the modules for kernel 6.1.42 are not compressed. Those filenames all end with .ko. I didn't check whether compressing the required modules (in kernel/drivers/firmware) can be loaded by the kernels 6.1.30 or 6.1.42 if they are compressed. So, if the first error message you see during reboot shows an error regarding "Failed: ...loading kernel modules" then try to compress the modules in /lib/modules/6.1.30-meson64/kernel/drivers/firmware and reboot. Hope this helps.

Hi Unfortunately no solution here, but "mee too" only. My USB keyboard works fine, that's it. In addition, I suddenly no longer have any Ethernet hardware onboard. This happened sometime during last night. However, I suspect the kernel version which is unmaintained now, again. I am still using bullseye and kernel 6.1.42 - no alternative kernel is available on the internal disk. Are you using the same kernel version ? Thank you for your answer. Edit: The last known kernel version which worked was 6.1.11 from a backup done with fsarchiver. Will try to fall back to this one and report results, here. Of course, I don't know which kernel version broke the Ethernet port und the USB disk support. There is an error message during boot stating that kernel modules can not be loaded. Perhaps this is related ? We'll see. New edit: Solved ! I replaced the broken kernel (6.1.42) setup by using the 6.1.11 kernel. I think the problem is with the modules of kernel 6.1.42 and that's why the external disks are not detected. The output from kernel 6.1.42 showed an error message saying that loading kernel modules failed. The same happened to me with kernel 6.1.11 because I forgot to add the modules directory to /lib/modules. As soon as I added /lib/modules/6.1.11-meson64 correctly my nextcloud now boots and works. I'll disable automatic updates now.

It does not just reboot automatically, but it crashes after a few hours of use. In addition it automaticall shuts down after a while. I am sick of opening the case, remove the eMMC, put it on the Micro-SD adapter, put it into the Micro-SD slot on my computer, edit the apache2 startup script, put the eMMC back on board and start the Odroid N2 again and repeat this several times a day. OK, I'll try to figure out myself how to stop using /dev/zram1 as /var/log.

Hi I had to upgrade my Odroid N2 from Armbian Buster to Armbian Bullseye to run newer versions of Nextcloudpi (24.x). So I did the upgrade by writing the Armbian 22.05 version to the eMMC and started Armbian. Works fine. Then I installed a fresh nextcloudpi (23.0.2) which is the same version I used on Armbian Buster. Works fine. I added the external disks (ncdata und ncbackup). After a restore of my nextcloudpi backup everything was well. But the next reboot did nothing, i.e. no output on the HDMI Interface, nothing. So, I did a power-off and looked at the eMMC via a Micro-SD adapter I have. Of course, no logs, nothing. Of course, there are no logs in /var/log because of the /dev/zram1 mounted at /var/log. Mounting /dev/zram1 on /var/log might be good if everything works, but if a reboot fails, you are host. I found a work-around: disable apache2 startup by editing the systemd unit file - I couldn't use systemctl because the system did not boot. After plugging in the external disks (nc-automount was enabled) and correcting the unit file, I could start apache2 and nextcloudpi is running well - until the next reboot. So, how do I disable the mount of /dev/zram1 to /var/log to find the real culprit ? Is it sufficient to delay the start of apache2 by adding ExecStartPre=/bin/sleep 30 ? Thanks for your advice. Kind regards Norbert

Thank you for the hint to use the menu. Yes, it did work fine :-) I'm very happy that the Odroid N2 is now supported and can run the mainline kernel.

Thanks a lot for your quick response Igor ! What a shame that I didn't come myself with this easy solution.

Happy new year and thanks for the good work ! I see there is a (buster) image available for my Odroid N2 with kernel 5.4. A few weeks ago I set up the build environment and started building my own images. First images were build using the 4.9 kernel from Hardkernel. Later the images were build with kernel 5.1 (and BRANCH=default). However, the image with kernel 5.4 was not build today but the kernel 5.1 is still used for the image, although I changed the BRANCH=default (as it was before) to BRANCH=dev. How can I create a new armbian image with kernel 5.4 ? I read some posts about a new u-boot. Is this new u-boot required for the new kernel ? I would like to boot, e.g. from USB as well. Kind regards Norbert

I was happy but much too early ! I removed the micro SD card from the Odroid N2 to make a backup (with fsarchiver and borg) on my PC. After putting the micro SD card in the Odroid, again, it didn't boot. Then I tried it several times until I moved the micro SD card in and halfway out of the slot several times. And, surprise, surprise, it booted without problems. So, in addition to the setting of my TV (in Europe = 50 Hz ?) to see the output during the boot sequence there is definitely a problem with the contacts on the board or on the SD card(s). Both cards I tried have the same problem, though and one of those is brand new. Although bought at the same time in the same store as the faked one mentioned above. Just another hint for people to check out, if the Odroid N2 doesn't boot from a known-good micro SD card ! Hope this helps others !

Solved ! Thanks a lot for your help. Solution were "just" modifications to boot.ini for my standard TV (not for my PC monitor): setenv condev "console=tty0" setenv display_autodetect "false" setenv hdmimode "1080p50hz" Now the message "Signal not supported, Check your input device" from the TV is gone as well as the boot procedure is started and the output is now on my TV. The SD card I used for the tests (not the faked one) did work fine.

I know that the serial output is the white one with four pins. ameridroid did send me just enough information of the layout and where the interfaces are. Of course, I need a serial device on the other side of the cable, right ? Because no current laptop has a serial interface, I need a USB to serial, too. And I have that one. I could, of course, write the Armbian image to the eMMC but I hate overwriting the only OS that runs on my Odroid N2 and the hassle involved (creating a disk image from eMMC and hope to be able to restore it) and risk to loose that one, too. Getting an empty or preloaded eMMC chip in Switzerland is not really possible. Who needs this, anyway ;-) There is a club which builds a "fair laptop" (repair-frendly modules) in Switzerland and they use eMMC in that laptop. I wrote mail to them to ask for a source of eMMC chips, but didn't get an answer, yet. NicoD might be right about the fake SD card. Do you think etcher is not right in stating "operation successful" at the end ? Is it reading the data it wrote from the OS cache ? I'll try another SD card. That's the only thing left to try at the moment waiting for new stuff to arrive.

OK, I already have an USB to Serial connector but the other side, i.e. on the N2 is missing. I'll order one in the states. It just takes two weeks .to arrive ... I can see the SPI output on my monitor but can't change any settings. It'll fallback to the default. Is there a trick to save my changes to any non-volatile RAM ?

Thanks ! I'll try the SPI setting and see, whether my monitor/TV will display anything. I have just one HDMI - HDMI and one HDMI - DVI cable to try. The former is Version 1.4 while the latter version is unknown. I'll try a different SD card. Writing ArchLinux image for Odroid N2 to the same card results in the same: not booting. Because I want to use it as a nextcloud server and nextcloudpi provides an install script for Debian Buster I want to use a Debian Buster on my N2. I had it running on my Raspberry Pi 3 but that is now used for pihole and would be to slow for nextcloud, anyway.

At my home there is a Microsoft and Apple and (almost) Google free zone :-) Using Unix/Linux/FreeBSD/Solaris since more than 30 years ! I did use etcher to flash the SD card, the verification was fine. Neither with "autodetect" = true nor with the DVI and 1680x1050 settings (and autodetect = false) did the system boot, at all. I tried it with the TV HDMI (1920x1080) and autodetect on and on the DVI monitor (HDMI to DVI cable). It seems to me that the system does not even try to boot on my Odroid N2 from SD card. I can boot into Ubuntu 18.04 Mate but the TV indicates that the signal is not supported - perhaps up to the time when the GUI starts. I don't know. It is very difficult to figure out what is going on when there is no display and I didn't buy an UART for this board. If I boot Ubuntu Mate, there is a LED light in red and later there is a blue LED blinking (OS running). However, if I remove the eMMC from the board and put the SD card in it there is just the red LED light and that's it. So the SD card seems to be fine. Question is: Is it the OS/SD card or the Hardware (or even my monitor) ? Any help appreciated - any moderator can put this into a different froum group or tell me to start a new post or whatever. Thanks Edit: Forgot to mention the image I am using. It is Armbian_5.95_Odroidn2_Debian_buster_default_4.9.190_minimal.7z

Thanks a lot. Obviously I missed the autodetect flag :-( I'll try it tonight. The reason is that: I bought two 32 GB SD cards labeled SanDisk at MediaMarkt in Germany for 5 EUR each. Unfortunately one was just 32 MB (!) after first use ! No wonder were the two cards damn cheap. So my tests were not successful because of that. I wanted to be sure that no other troubles are in the way.