Posts by mrness


    The latest RR build (20190221) has an issue with w1-gpio support. My .config/ contains the following commands:

    dtoverlay w1-gpio gpiopin=4

    modprobe w1-gpio

    modprobe w1-therm

    In this build loading w1-gpio module fails with the following errors:

    [ 6.854425] w1-gpio [email protected]: prop pinctrl-0 index 0 invalid phandle

    [ 6.854453] w1-gpio: probe of [email protected] failed with error -22

    I've discovered the way to fix $subj problem and is quite simple:

    echo 0 > /sys/module/hid_apple/parameters/fnmode

    This Chinese device pose as an Apple item (vendor ID 0x5ac), hence the usage of hid_apple driver:

    Nov 06 09:18:36 rpi kernel: apple 0005:05AC:022C.0012: unknown main item tag 0x0

    Nov 06 09:18:36 rpi kernel: input: Bluetooth 3.0 Macro Keyboard as /devices/platform/soc/3f201000.serial/tty/ttyAMA0/hci0/hci0:11/0005:05AC:022C.0012/input/input19

    Nov 06 09:18:36 rpi kernel: apple 0005:05AC:022C.0012: input,hidraw0: BLUETOOTH HID v1.1b Keyboard [Bluetooth 3.0 Macro Keyboard] on b8:27:eb:4f:ff:99

    Nov 06 09:18:36 rpi systemd-logind[11943]: Watching system buttons on /dev/input/event0 (Bluetooth 3.0 Macro Keyboard)

    Just to give you a "warning" cputemp: give RPi SoC sensor priority by MilhouseVH · Pull Request #3073 · LibreELEC/ · GitHub your problem lead to some updates for the cputemp script so once it's merged might you have to check it first if something is broken ;)

    Turns out the problem it is not located in the /usr/bin/cputemp script, the current version of this script correctly reports the CPU temperature as it is read from /sys/class/thermal/thermal_zone0/temp. It seems that Kodi does not use this script, probably reads the temperature directly from /sys/class/hwmon/hwmon0/temp1_input.

    Can you check if you have more devices in /sys/class/thermal/thermal_zone0/temp or /sys/class/thermal/thermal_zone1/temp or something like this? Also check if  /sys/class/hwmon/hwmon0/device/temp1_input exists.

    I've connected a temperature sensor and used /sys/bus/w1/devices/*/w1_slave to read its value, but now I see there is another way to read it via /sys/class/hwmon/hwmon0/temp1_input.

    I've fixed it with an advancedsettings.xml like this:

    1. <advancedsettings>
    2. <cputempcommand>sed -e 's/\([0-9]*\)[0-9]\{3\}.*/\1 C/' /sys/class/thermal/thermal_zone0/temp</cputempcommand>
    3. </advancedsettings>

    Thanks a bunch!

    LE: For Confluence skin fans, here is a favourites.xml file that would allow you to run RetroArch and EmulationStation:

    1. <favourites>
    2. <favourite name="EmulationStation">RunScript(/usr/bin/</favourite>
    3. <favourite name="RetroArch">RunScript(/usr/bin/</favourite>
    4. </favourites>

    First of all kudos for keeping this distro up and running, it contains everything I want.:)

    I encountered a minor annoyance. I use RR on a rpi3 B+ and I noticed that CPU temperature displayed in Kodi's system info is utterly wrong, it says CPU is at 18-19 C degrees while vcgencmd measure_temp and /sys/class/thermal/thermal_zone0/temp correctly report a temperature above 55 degrees.

    This issue appeared the moment I placed this command in my /storage/.config/

    dtoverlay w1-gpio gpiopin=4

    I grepped for "cputemp" in .kodi and found nothing relevant. Any idea how to fix this?

    kszaq Sorry about that, this is the output of "tail -f ~/kodi/temp/kodi.log"

    Please let me know if you need other traces or you need me to test something else.

    I'm using 7.95.beta5 and I have problems with hardware acceleration of am-h264 decoder on a 1280x720 25 fps video stream. If I'm using h264 acceleration the screen remains black and there is no sound. My box has a S905X SoC (A95x 2/16GB) and this is what I see in the kodi logs:

    I have Bluetooth issues on build, bluetooth service (or driver) does not run properly on A95x 2/16GB TV box (S905X).

    The build was able to detect and pair with my Rii i8+ BT keyboard, but not with my Logitech MX Anywhere 2 mouse. Here are the bluetoothd logs related to this issue:

    1. Jan 25 08:44:59 nexbox bluetoothd[2785]: No cache for E5:1F:0F:F9:9F:80
    2. Jan 25 08:45:04 nexbox bluetoothd[2785]: input-hog profile probe failed for E5:1F:0F:F9:9F:80