|Latest product reviews|
I continue to try and pursue the source/cause of this problem which is proving all too repeatable. Please see this screen recording of my Minix Neo X5 when an HDMI cable is plugged into it. Video capture was performed on Windows XP via a VNC connection to the Neo X5. Initially, there is no HDMI cable plugged in. Then when an HDMI cable is plugged in (about 17 seconds into the video), an image is flashed onto the screen. This would seem to indicate that the hardware (and maybe the kernel) is alerted when the cable is plugged in and some action is taken. I am not sure if the image is displayed directly by the hardware or if there is something in the kernel which does this.
When my Neo is connected to my HDTV and the TV power is turned on, it is generally followed by a crash/hang of the Neo X5. This does not happen when plugged into my BenQ HDMI monitor. What is happening to cause the crash? It does not occur with every TV power on. But it occurs at least once a day - generally after the Neo and TV have been sitting unused for several hours.
I would guess that the vast majority of Neo X5 users never see this because of the timing and that their monitors/TVs are only just being turned on. I often connect to my Neo X5 using VNC or TeamViewer and it happens that last night I was doing this at the time my wife powered on the TV in the other room to watch the news. I saw this image for the first time and immediately the VNC session locked up and pings to the Neo X5 failed to be returned. I had to power the unit down and restart it.
So today I was able to replicate the image being shown and recorded it. If anyone can shed some light on what is happening here, I would appreciate it. In the kernel code I have seen references to an EDID interrupt and I wonder if this or something like it is being triggered when the TV is powered on causing the image to be displayed and then something else inside the kernel which ultimately faults for reasons unknown. I am not saying the display of the image itself is the problem but it seems to happen in concert with the problem and I am thinking it all must be related.
BTW - my X5 is currently running Karel's KitKat ROM. But this problem happened on Finless 1.3 as well (and likely Finless 1.2b but I wasn't aware enough of the pattern back then to see it). I note that both the KitKat ROM and Finless 1.3 use the same version kernel (3.0.36+) but I would guess that the actual kernels are different since the KitKat was compiled from source and I think that Finless uses the original Minix distribution.
Any information, especially from Minix or other Rockchip techies, is appreciated. Thanks
Most Users Ever Online: 749
Currently Browsing this Page:
Devices in use: Desktop (110), Phone (14)
Guest Posters: 43
Moderators: globula_neagra, exelletor, JochenKauz, Oma7144, cracktech