You are not logged in.
hello wfk,
Can you post your .config file, the one you are using to compile hardkernel?
Thanks in Advance,
Best Regards,
tux
Best Regards,
tux
Offline
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
Offline
hello wtf,
Can you boot and have Ethernet in Devuan xu4 image?
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
Last edited by tuxd3v (2020-03-13 18:44:38)
Best Regards,
tux
Offline
Hello Illegalum,
I created a hardkernel version, if you could install it, to test, I apreciate
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,
Last edited by tuxd3v (2020-03-23 02:01:48)
Best Regards,
tux
Offline