This share here, contains the deb packages to try the hardkernel compiled kernel, and also the new boot.ini file..

Backup first your boot.ini file:
    cp boot.ini boot.ini.backup

Then copy to the sdcard, the contents of the shared folder:
    linux-headers-4.14.165_4.14.165-4_armhf.deb
    linux-image-4.14.165_4.14.165-4_armhf.deb
    linux-libc-dev_4.14.165-4_armhf.deb

Copy also 'boot.ini.new' to /boot,

then boot the board, install the new kernel:
    dpkg -i *.deb
change 'boot.ini.new' to 'boot.ini':
    mv /boot/boot.ini.new /boot/boot.ini

then restart and check if that kernel, works well in your board,

if it doesn't:
    dpkg -l |grep -E "linux-.*(image|headers|libc-dev)"
    See the 4.14.165 installed packages and remove them:
       apt-get remove --purge linux-headers-4.14.165 linux-image-4.14.165 linux-libc-dev
    get back your 'boot.ini' file:
        mv /boot/boot.ini.backup /boot/boot.ini

And restart..

It would be nice to get some feedback from you, since you own one of this boards

Best Regards,

Because that seems to be a difference,
Illegalum detected that he doesn't have Ethernet, on the devuan xu4 image.

Perhaps because of Power supply differences,
The supply voltage to the usb-ethernet controller comes from different places and so, Ethernet is not power properly..

Can you check with devuan xu4 image?
if that doesn't work( xua devuan image...ethernet ), can you install my compiled kernel and check if everything works then?

Thanks in advance,

EDIT: there are there a HC1 dts file even in hardkernel '4.14.165':
https://github.com/hardkernel/linux/blo … oidhc1.dts

Hi WFK as You say you have and the HC1 board and the HC2
are the boards the same and does the HC2 report as a HC1 or does it report as a HC2 ?
because for me the main difference looks to be the housing for the 3.5 inch disk

I only have xu3 and xu4 dtb files in my /boot.  As far as I can tell, with my kernels, the system identifies as "Odroid XU4" and uses the xu4 dtd.
So I don't know at what point the need for a separate hc1 dtd file in /boot was introduced.

Going through the dmesg, I see no indication of either HC1 or HC2, only XU4.

Afaict, the boards are identical except for the 5V vs 12V power circuit.

wfk

Thanks in Advance,

Best Regards,
tux

I understand it can take long time to compile , but in general if it gives a better result we can try to compile it on the odroid itself, just might need some help with the steps
Lum

The steps don't change its the same as above
you just don't need a crosscompiler , you would use a native one..
so were you have ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-, delete this from the commands

Regards,
tux

It would be nice to know if it boots, and if ethernet is working correctly,
The idea is creating a image for hc1, with zram as swap using lz4 algo on it

but we need first a stable kernel..
in the share folder bellow is also a 'log' file, with the compilation log process..

if this works nicelly, I will tune the kernel for big.LITTLE on hc1 cpu

Lum

At beguining I tought it would be nice to go with mainline, but there are problems with it..
I will create a image with 4.4.165 from hardkernel, with Illegalum, defconfig above, and devuan userspace

EDIT: In fact hardkernel does have a 'odroid-5.4.y' branch, but I don't know how good it is..

Lum

Unfortunately moving the boot.ini  to boot.ini.sav and then copy the boot.scr in /boot results in a message that boot.ini is not found. putting the boot.ini back results again in the same kernel panic.

Have some spare sd cards now so hope i can do some quicker tests
I actually found that from the debian source image witch I converted to devuan ascii it has some sources directed to a deb source oph.mdrjr.net_meveric_dists_all_xu3 and it pull a specific kernel from there  linux-image-4.14-armhf-odroid-xu4

Lum

I'm compiling native on the HC1.
I'm using the kernel source provided by Odroid on their site, which contains various Samsung cpu related patches.  It looks like Ubuntu is using that same source, as the kernel they deliver with their image is a similar version.

This is what comes with the standard Ubuntu SD card image:
Linux version 4.14.5-92 (root@1604_builder_armhf) (gcc version 5.4.1 20160904 (Ubuntu/Linaro 5.4.1-2ubuntu1~16.04)) #1 SMP PREEMPT Mon Dec 11 15:48:15 UTC 2017

What's running on my compile box is currently:
Linux version 4.14.141+ (root@eiger) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP PREEMPT Fri Oct 4 19:34:42 UTC 2019

The current Odroid version is newer than that.  They recently merged a 4.14 update.
I have seen no indications that they intend to go to 5.x any time soon.

wfk

Hi wfk,
For the work Illegalum have done, he experienced problems with the network card, I believe?!( using the devuan image for xu4.. )

I found there are indeed a dts in mainline for hc1..
I compiled 5.5.7 kernel, and I were checking it with Illegalum..

My Kernel gave a kernel panic( I also saw a compiler warning about a pointer not been initialized first.. in compilation process)..
But it could also be that my toolchain is the one to blame..

I am with Linaro 7.5 unfortunately, since ARM only provides amd64 cross toolchains...
So I am locked on 7.5 cross toolchains..

What kernel are you using?

Best Regards,
tux

The other week I tried to boot the Odroid XU4 image and found it, indeed, not booting.
I'ld be happy to help out with any testing, kernel building, or whatever.  I have a couple of "scratch" Odroid HC1 and HC2 machines here that I have been using to compile my own kernel and uboot for use with a devuan install that I created using debootstrap.  That worked quite well, although I found you have to be careful about which Odroid kernel source commit you use, as some are decidedly unstable.  I don't know what the "official" way is to build a Devuan arm embedded SD card image.

Regards,
wfk

Had some interesting times to get it booting with the old kernel again after i got the kernel panic , going to order another sd card so i have one install spare for killing so give me a few day to come back to you with this.

Kind regards,
Lum

we've got ourselfs a kernel panic ...
Lum

Indeed,
When I compiled that kernel I received a warning about a possibility of a pointer not been initialized, maybe its related to that..
I compiled it using the linaro crosscompiling toolchains 7.5, since the ARM ones only have as host amd64(I am on devuan i386..).

at same time it could also be something uboot config related( addresses or else.. )..
I created a basic 'boot.scr' file , its in the share, if you want to try a last time..

You only need to copy it to /boot,
rename '/boot/boot.ini'  to something like '/boot/boot.ini.backup',
and restart..

ofcourse this with the new kernel.. if you get again a kernel panic, get previous( original situation.. )..

In that case,
maybe the uboot version you have doesn't support yet the Odroid HC1.. for the few things I read about that board, still there are diferences between them, that's why you can boot XU4 and not HC1 with devuan image..