Using the nightly from july 1st, for the first time, my flirc will consistently disconnect / become unresponsive. Unplugging all my usb devices and plugging the flirc back in does not yield any fix. The only way to fix it Is to reboot the device. If I wait about 20 minutes or so (of inactivity) my flirc will again become unresponsive. There was absolutely no issue what so ever with my flirc until the last two nighties.
Any ideas? Could the usb ports have gone into a sleep state?
Thanks!
EDIT: I Think it may have been just low batteries after all ā¦ doh
The stable build is a good option for anyone not comfortable with frequent updates to development builds.
For those who like living on the edge and help testing and providing feedback on the most recent developments, the nightly builds will continue as before.
Were there any USB related updates performed lately ?
I have serveral tv tuners, and some of them stop working (sundtek) after a short while with the following error in the kernel log:
Blockquote
usb 1-1.1: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 6 len 1 ret -71
Until I restart the odroid, it wonāt tune to the correct frequency.
It used to work correctly with older buildsā¦
Maybe you can use a USB hub and power the tuners externally. I do only have one tuner and it is plugged there. I had this problems before. There were several kernel updates recently but it seems the issue is still not solved. There are discussions ongoing in the odroid forum, however, I donāt know about a final solution.
I do have a second N2 running Ubuntu and it does random restarts caused by heavy load and kernel panics I suppose. There is also a discussion ongoing about that. However, no solution neither.
Is there a tracker issue, or forum discussion on the Hard Kernel site for those of us interested in tracking the status of the multichannel PCM implementation? I couldnāt fine one.
@Ray I heard from @tobetter about a possible fix of the USB issue. As far as I understood there were updates applied to the kernel and uboot. Could you bring this (latest kernel and uboot) to Coreelec?
Iām not sure if it works but I guess it is worth a try.
I supposed to share the patch after having some report from a user and after Petitboot update. But, yesā¦definitely worth to try to see if it works for others as well.
Since you mentioned you have 2nd ODROID-N2 running Ubuntu, you would be able to update it. Please do sudo apt update and sudo apt upgrade before rebooting.
I updated it accordingly to your description in the odroid forum. sudo is not required for me since Iām logged in as root. I added the command in the boot.ini as described.
By the way @tobetter, I face random restarts on the N2 running Ubuntu. It might be caused by kernel panics during heavy load as some users suggest at the odroid forum. Any help for this issue? I donāt see it happening for Coreelec.
Hi @tobetter , I have read above that there is a uboot update.
I wonder if you have also fixed the problem that @anon88919003 was writing about: āsometimes the device halts on rebootā
This āhalt on power onā is known and I am searching for reason. Some module freeze the kernel on booting. Sometimes every second boot, sometimes every 1 of 100 boots.
Use suspend mode instead of power off until this issue got fixed, this is now the work around
