No problem, thanks
I can imagine it would be a time consuming frustration limping things along with that old kernel.
No problem, thanks
I can imagine it would be a time consuming frustration limping things along with that old kernel.
I noticed that there is no longer the option to install the LibreELEC Module drivers (especially Crazycat) in 8.90.004 or 8.90.005 for Odroid C2.
At the moment I'm just copying the patches and package.mk from 8.90.003.......modify the Amlogic project option file......then build.
This at least allows me to get my dvb tuners (including the Xbox One tuner) working again for 8.90.005.
Is the Module driver install option going to be enabled again in future Odroid versions (especially beyond kernel 3.14)?
konetzed It's better to do a clean install, I've noticed a few things improve and just work better than upgrading to 8.90.003.
Caesium I've been watching TV with my C2 on 8.90.003 and noticed the odd minor frame skip or 2 on some channels with marginal reception, but perfect with good reception.
The great thing is now I'm finally finding the Xbox One tuner I have is working flawlessly.
Great to see the transition to LE for the MK808B+.
Thanks kszaq!!
Oversun's version doesn't work with frame rate switching. Outside of that, everything else seems to work just fine. Test hour version when you get home to see if it works.
It appeared to work fine (24Hz) on a few videos (720p) until I played a H264 1080p video.......it just killed the display and needed to reboot.
I tried it with "Adjust display refresh rate" at "On start/stop" and "Pause during refresh rate change" at 2 seconds.
Unfortunately I don't have too much content to try it with as I'm "watch once and delete" type of person.
Edit: the problem at 1080p could just be my 7 year old plasma tv throwing a spasm.
what he means is that the u-boot binary generated on lrusak's tree doesn't allow to make a bootable imageyou need to get hardkernel u-boot binaries and apply the included fuse script on you sdcard to make it boot .
Thanks. Yes exactly
[hr]
Oversun's version doesn't work with frame rate switching. Outside of that, everything else seems to work just fine. Test hour version when you get home to see if it works.
I will.
It is also probably worth seeing where surkovalex (Alex on amlinux) is at with sorting out some of the remaining problems like this.
I did almost the same, but used the github sourcesGitHub - surkovalex/libamcodec: libamcodec
seems to play, only a bit of delay before the video starts.
I saw that, but tried out the amlinux link first as I thought it might have been the latest version.
I don't seem to get the delay with the amlinux version, but will still checkout the github source you tried to see if it is any different.
I haven't had time to try OverSun's version yet, but will when I get home from work this afternoon.
It is great that there have been multiple solutions from different people to fix this problem.
Hopefully there can eventually be an "official" Odroid C2 branch of LE now that this major problem has a workaround or solution.
I think I might have managed to get video working with @lrusak's Odroid C2 branch.
OverSun posted his build about the same time.
OverSun's build might be better as it has a working u-boot.
Just saw @lrusak's post here ODROID Forum • View topic - OpenELEC for Odroid-C2
Great news!!
Mine is as per LibreELEC.tv/linux.aarch64.conf at aarch64-odroid-c2 · lrusak/LibreELEC.tv · GitHub with the 2 changes; [font="Open Sans, sans-serif, Arial"]CONFIG_MALI_SHARED_INTERRUPTS=y and # CONFIG_AMLOGIC_ION is not set[/font]
[font="Open Sans, sans-serif, Arial"]That, once built, boots only to the splash screen but at least has the blue "heart beat" LED now flashing. [/font]
[font="Open Sans, sans-serif, Arial"]I found a USB to TTL converter so should hopefully be able to make a console cable soon to try to see what is going on.[/font]
lrusak appears to have made a few recent changes to the Odroid-C2 branch, so may be worth cloning again and trying.
I wouldn't make many changes to [font="Open Sans, sans-serif, Arial"]linux.aarch64.conf as it can make building a real pain in the arse and may only make things worse.[/font]
I think kodi is already running. But maybe I'm wrong...
I really have to hurry up and make a console cable to try see if that is the case.
From @lrusak's post on the Hard Kernel forum ODROID Forum • View topic - OpenELEC for Odroid-C2 it doesn't appear so.
Some slight progress.....I think;
Before rebuilding, I modified the linux config file (linux.aarch64.conf) in /LibreELEC/projects/Odroid_C2/linux to set CONFIG_MALI_SHARED_INTERRUPTS=y and CONFIG_AMLOGIC_ION to not set.
The result was that instead of the blue LED staying on solid (indicating a lockup during boot), it was flashing (indicating that at least the kernel was now running).
Unfortunately it still didn't progress beyond the LibreELEC splash screen.
I guess much more work is still needed, possibly on boot.ini.
Did anyone else have the flashing blue LED or did it just stay on?
[hr]
any ideas?
Here's the difference between OpenELEC working on a s905 box compared to what's in the linux.aarch64.conf we are using.
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_GOV_COMMON=y
CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_HOTPLUG is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_INTERACTIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_HOTPLUG=y
# CONFIG_CPU_FREQ_GOV_INTERACTIVE is not set
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
CONFIG_GENERIC_CPUFREQ_CPU0=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARM64_CPU_SUSPEND=y
Display More
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_GOV_COMMON=y
CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_HOTPLUG is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_INTERACTIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_GOV_ONDEMAND is not set
CONFIG_CPU_FREQ_GOV_HOTPLUG=y
# CONFIG_CPU_FREQ_GOV_INTERACTIVE is not set
# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set
# CONFIG_GENERIC_CPUFREQ_CPU0 is not set
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARM64_CPU_SUSPEND=y
Display More
Could the differences here maybe be causing a problem?
its actualy ARCH=aarch64 PROJECT=Odroid_C2 make -j8
Ah, thanks. Will try that.
Display MoreOOps, I pasted the wrong thing. I did do the PROJECT=Odroid ARCH=aarch64 make image.
I see that there are some "devices" directories for C1, U2 and XU3, but I don't see any way to specify one or the other. I'm assuming that this is resolved at run time and that all of them are supported by the same image file and that the C1 collection is what is used by the C2. Does that sound reasonable?
[hr]
EDIT: Okay, now I'm getting an interesting error. It looks like wants to download some kernel source, but doesn't have the proper version numbers:[font="Courier New"] GET linux
[/font]
[font="Courier New"]--2016-03-30 08:13:36-- linux-0.0invalid.tar.xz[/font]
[font="Courier New"]Resolving freeweb.mine.nu (freeweb.mine.nu)... 178.32.220.211[/font]
[font="Courier New"]Connecting to freeweb.mine.nu (freeweb.mine.nu)|178.32.220.211|:80... connected.[/font]
[font="Courier New"]HTTP request sent, awaiting response... 404 Not Found[/font]
[font="Courier New"]2016-03-30 08:13:36 ERROR 404: Not Found.[/font]This repeats over and over using different servers, then finally fails:
[font="Courier New"]Cant't get linux sources : linux-0.0invalid.tar.xz
[/font]
[font="Courier New"] Try later !![/font]
[font="Courier New"]make: *** [image] Error 1[/font][font="Arial"]I don't think trying again later is going to help. ;)[/font]
[font="Arial"]Any ideas???
[/font]
I don't think the C1 project from @zalaare's fork will work at all on a C2.
If you did want to build it to test, use PROJECT=Odroid ARCH=arm DEVICE=C1 make (image or release...etc)
If trying @lrusak's version, I don't think you cloned the aarch64-odroid-c2 branch and ended up with the main fork.
Try git clone GitHub - lrusak/LibreELEC.tv: 'Just enough OS' for Kodi --branch aarch64-odroid-c2
To build, use PROJECT=Odroid_C2 ARCH=aarch64 make image
DD'ing the resulting image didn't work at all for me, so instead did this;
To set up a microSD, just follow the instructions at en:c2_building_u-boot [Odroid Wiki]
Rename the kernel file in the Target folder to KERNEL and the system file to SYSTEM and copy them on to the prepared microSD (or just extract and copy them from the .tar or .img.gz files in the Target folder).
Copy the boot.ini file from /http://LibreELEC.tv/projects/Odroid_C2/bootloader folder to the microSD.
There's probably an easier way to do this.
This got me to the splash/boot screen with a prompt.....
Aaaargh......I shouldn't have used an Evo card. I've had trouble with the early Evo's before.
This time I tried with another card (properly set up with bootloader) and at least got to the boot screen before stopping. Will try fiddling around with it more when I make a console cable and can get more time from work.
Did you just dd the .img file straight to the flash card? I'm no expert, but I'm thinking that you might have to do a little more work on the SD card first, such as creating partitions and loading information into them. Maybe this will help, though I'm not sure that it is exactly right for ARM:
Manual Installation - OpenELEC
I think you're right, and I'm literally just blindly bumbling my way through this at the moment.
zalaare has some make scripts for the C1 that might work for the C2 with some modifications.
OpenELEC-Odroid/scripts at odroid-6.0 · zalaare/OpenELEC-Odroid · GitHub
Another thing I noticed, and possibly doesn't matter too much, is that the boot.ini looks a bit different to the C1 boot.ini.
GitHub - mdrjr/c2_bootini
I'll keep trying with the lrusak branch and then hopefully eventually try with LE.
Even if I get nowhere with this (which is highly likely), at least I'm learning a lot.
[hr]
I will give it another go with, i have already successfully gotten gentoo to run on the c2, probably need to fuse the uboot manualy to the sd.
Please let us know how you go
I had a go at building that branch (with ARCH=aarch64).
It appeared to build successfully, giving me an image with boot.ini, KERNEL and SYSTEM. (I'm not sure if we don't need INITRD and meson64_odroidc2.dtb as well).
Unfortunately after dd'ed to a microSD, it wouldn't progress beyond uboot (solid blue LED).
Beyond this, I'm a bit out of my league, but will keep trying a few things towards any sort of improvement.
Me 3.
The Odroid C2 appears that it could be an excellent platform for LibreELEC.