I just updated my N2 to nightly_20200525.
Manual upgrade was smooth, install runs from emmc.
On my setup, nothing visibly broken.
Simple things really, some smb shares mounted for remote media,
an xbox tuner for DVB-T, + netflix addon.
Media playback up to 1080p via SMB looks ok.
DVB-T(1) works as before.
Pressing “O” still doesn’t show DVB reception values.
New Tvheadend 4.2 also works with no issues.
It needs more testing, but the issues I had with xbox tuner and rear usb ports
(as described: N2 9.2.2 & DVB-T issues.) seem to persist.
For now I will keep using an otg adapter with the front usb,
and I hope that the devs will find a better solution down the road.
Playback of media files via smb shares ok.
Netflix ok (still SD though, but that’s an other issue…).
On 4k/HDR/3D front i can’t comment/test.
One glitch I did notice:
CEC fails (or delays a lot…) to connect to tv (old samsung) on cold boot,
its ok on reboot.
It was connecting immediately on 9.2.2.
Other than that it looks ok to me.
Now patiently awaiting next stable…
Just tried nighly 20200525 on my N2
Everything seems ok like on 9.2.2 except the problem with hauppauge win dual DVB-T usb tuner like described here : 9.2.2 DVB tbs driver / Hauppauge USB wintv dual HD / Tvheadend conflict
So inusable for me
Have you tried your tuner with the other driver modules in this nightly?
Yes the same as 9.2.2 (was working on 9.2.1)
Crazycat or form latest kernel : doesn’t work
CE default drivers : working but only one tuner instead of two
see : 9.2.2 DVB tbs driver / Hauppauge USB wintv dual HD / Tvheadend conflict
Could you please try latest nightly to see if the problem is still there. I was wondering because I my case, with the latest nightlies my mygica/geniatech t230 is detected as dvb-c tuner in default module drivers and it wasn’t before.
@Vasco no it’s the same with latest nightly only one tuner detected with CE default drivers.
I have the problem, that by the new Odroid C4, the Green LAN LED is on. It’s not blinking, no its every time active an its to glow green. It’s glow also, if the C4 is shutdown. here is an UARt Log.
Lanled.log (10.5 KB)
As hinted by the devs and as reported earlier, I did install nightly 20200525 to test dvb functionality.
One possible issue:
My understanding is that nightlies auto-update(?) on every new nightly build.
Mine doesn’t detect 20200528, nor I get any prompt to update,
and update channel is empty on gui.
Something broken or something that I don’t understand?
Thanks.
I am on nightly 20200523:
yes, my network is Gigabit and on my C4 the green 100mbps LED is stable active and the orange 1000mbps LED is blinking (which is ok). But this is no functionality restriction, data transfer is gigabit-speed.
Yes, this is not a functional limitation. But I think the LED should be off and not 24/7 on. I have the feeling that the C4 does not shut down properly. I have never seen a device where the LED was permanently on, even when the device was shut down.
On my N2 the LAN LED sometimes flashes orange when it is switched off and does not light up permanently green.
Does HDMI-CEC work properly for you?
The LED colors and indicators are set by the driver in the kernel.
Green indicates 1gbps, blinking orange indicates transfers.
Here you can see what I mean. The device is off (red and blue LEDs are off) and the green LAN LED is on. Furthermore, I just saw that the orange LAN LED flashes, as I know it from the N2 and other devices.
the C4 description says:
Ethernet LED indicators
Green: 100mbps connection
Amber: 1000mbps connection
Summary
This text will be hidden
Yes, the colors are always an indication of the speed, but the LAN LEDs should also look when the device is off. They should not shine permanently. It is normal that the LAN LED sometimes flashes orange when the mode is switched off, but does not light up permanently green.
I am not aware of any device that the LAN LED is permanently lit.
And believe me, I have a lot of devices.
If the C4 is shut down, the green LED is stable on, the amber LED is blinking (network-interface is active).
WOL works. When I deactivate WOL in the CoreELEC-app, then WOL
does no longer work (that is ok), but the LED behaviour i the same as before.
And as @Mister-XY said, the green LED should be switched off when a gigabit network is connected.
And it should be off, when the whole device is switched off.
I would say…
sorry, I don’t use CEC at all, I use a Logitech Harmony for all my devices.
Off on Amlogic devices is not really off. The only difference to suspend is that on power off the device reboot. In suspend it just resume. The device is never “real” off, otherwise You are not able to start it like with IR. The LED are set to default in Kernel. Maybe the wiring is different to other devices, didn’t checked it.
The last change to the LEDs was this: https://github.com/CoreELEC/linux-amlogic/commit/b6f1207ba0461caa0552b3c1e982505edc8516ba#diff-cb01d62d258fc77cb7f9b39a91fcf97f
We have seen some devices where the LEDs are off in suspend/power off and other where not. So feel free to study the rtl8211f datasheet and make a pull request. It’s only a LED…
I have tested Debian for C4 and if i shutdown the C4 via Shutdown -h now, the green LED is off.
I think there are a error in kernel or u-boot.
Actualy i have no time for this, but now we come to the HDMI-CEC error.
Unfortunately I noticed that HDMI-CEC does not really work well there. As soon as I select Odroid as the source via TV (HDMI), it can happen that my Odroid does not start. I switch back to the SAT source, then my C4 starts. If I quit my C4 again, my C4 remains on the HDMI slot. if I then go back to the SAT source, my C4 will start again automatically. Unfortunately, the Auto Power function of the C4 does not really work.
At,
phy_addr_ab: 0x11, phy_addr_cd: 0x00, msg [4]: 0x10, msg [5]: 0x00
I go to the HDMI source of the C4 and here it should start, but it doesn’t. Only when I go back to the SAT source does it start.
https://discourse.coreelec.org/uploads/short-url/a9fvYxFgLnFPPceSAfuRZiP2GbU.log
http://ix.io/2nby
http://ix.io/2nmd
https://discourse.coreelec.org/uploads/short-url/w3epuN56VReROBI0v0ik96MwRol.log
I maybe found the issue about CEC on C4. C4 is using g12a architecture, not g12b like N2 so I missed some patches. Please copy this binary to /storage/backup on your C4 and then execute these command:
booted on eMMC:
dd if=/storage/backup/u-boot.bin.sd.bin of=/dev/mmcblk0 conv=fsync bs=1 count=112
dd if=/storage/backup/u-boot.bin.sd.bin of=/dev/mmcblk0 conv=fsync bs=512 skip=1 seek=1
reboot
booted on uSD:
dd if=/storage/backup/u-boot.bin.sd.bin of=/dev/mmcblk1 conv=fsync bs=1 count=112
dd if=/storage/backup/u-boot.bin.sd.bin of=/dev/mmcblk1 conv=fsync bs=512 skip=1 seek=1
reboot
The C4 will reboot and the new bootloader is ready to use. An update by tar will remove this manual installed bootloader again.
u-boot.bin.sd.bin (844.9 KB)
CoreELEC has its own configuration for the RTL8211, and it’s how I mentioned it to be.
Green for 1gbps link and amber for activity. This configuration can be configured in software, it’s not hardwired.