Posts by oJPTo
-
-
Hi,
I just installed a fresh LE 11 on Raspberry 3B+.
Now I wanted to try my DVB-T/DVB-C USB stick: Terratec CINERGY TC2 Stick
But it doesn't work.
I already tried on my PC, where I had to fetch dvb-usb-it9303-01.fw, dvb-demod-si2168-b40-01.fw, dvb-usb-terratec-htc-stick-drxk.fw, dvb-demod-si2168-02.fw from OpenElec Github repo.
on the PC it does not work either, because the Si2157 "device is buggy" and it does not load the firmware.
is here someone who supports making it work?
I am currently building mainline kernel to check if a newer kernel helps.
The errors shown below look like what I was getting on my PC when the firmware wasn't installed yet. But here there are no requests for firmware?
The chips used are:
ITE IT9306, Silicon Labs Si2157 ("device is buggy") and Si2168-B40
thanks
JPT
PS. tried putting the firmware in /storage/.config/firmware but this did not change anything. Why doesn't it load the firmware?
Code
Display More[ 1870.870886] usb 1-1.3: new high-speed USB device number 7 using dwc_otg [ 1870.965058] usb 1-1.3: New USB device found, idVendor=0ccd, idProduct=10b2, bcdDevice= 1.00 [ 1870.965104] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1870.965123] usb 1-1.3: Product: TS Aggregator [ 1870.965139] usb 1-1.3: Manufacturer: CINERGY TC2 Stick [ 1871.083996] em28xx 1-1.3:1.0: New device CINERGY TC2 Stick TS Aggregator @ 480 Mbps (0ccd:10b2, interface 0, class 0) [ 1871.084027] em28xx 1-1.3:1.0: DVB interface 0 found: bulk [ 1871.140985] em28xx 1-1.3:1.0: unknown em28xx chip ID (0) [ 1871.198511] em28xx 1-1.3:1.0: reading from i2c device at 0xa0 failed (error=-5) [ 1871.198541] em28xx 1-1.3:1.0: board has no eeprom [ 1871.254173] em28xx 1-1.3:1.0: Identified as Terratec Cinergy H6 rev. 2 (card=101) [ 1871.254205] em28xx 1-1.3:1.0: dvb set to bulk mode. [ 1871.255632] usbcore: registered new interface driver em28xx [ 1871.268407] em28xx 1-1.3:1.0: Binding DVB extension [ 1871.272414] usbcore: registered new interface driver dvb_usb_af9035 [ 1871.302599] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5) [ 1871.302817] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5) [ 1871.303031] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5) [ 1871.303242] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5) [ 1871.303437] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5) [ 1871.372880] em28xx 1-1.3:1.0: reading from i2c device at 0x52 failed (error=-5) [ 1871.373121] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.373134] drxk: i2c write error at addr 0x29 [ 1871.390387] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.390417] drxk: i2c write error at addr 0x29 [ 1871.401052] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.401077] drxk: i2c write error at addr 0x29 [ 1871.412335] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.412357] drxk: i2c write error at addr 0x29 [ 1871.423610] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.423633] drxk: i2c write error at addr 0x29 [ 1871.434399] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.434426] drxk: i2c write error at addr 0x29 [ 1871.445681] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.445706] drxk: i2c write error at addr 0x29 [ 1871.456959] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.456985] drxk: i2c write error at addr 0x29 [ 1871.467736] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.467767] drxk: i2c write error at addr 0x29 [ 1871.479020] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.479046] drxk: i2c write error at addr 0x29 [ 1871.490309] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.490335] drxk: i2c write error at addr 0x29 [ 1871.501117] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.501144] drxk: i2c write error at addr 0x29 [ 1871.512432] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.512460] drxk: i2c write error at addr 0x29 [ 1871.523719] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.523744] drxk: i2c write error at addr 0x29 [ 1871.534423] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.534452] drxk: i2c write error at addr 0x29 [ 1871.545695] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.545717] drxk: i2c write error at addr 0x29 [ 1871.556979] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.557006] drxk: i2c write error at addr 0x29 [ 1871.567733] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.567758] drxk: i2c write error at addr 0x29 [ 1871.579025] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.579049] drxk: i2c write error at addr 0x29 [ 1871.590310] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1871.590336] drxk: i2c write error at addr 0x29 [ 1871.600888] drxk: Error -5 on power_up_device [ 1871.600913] drxk: Error -5 on init_drxk [ 1871.600921] drxk: frontend initialized. [ 1871.640750] tda18271 12-0060: creating new instance [ 1871.641081] em28xx 1-1.3:1.0: writing to i2c device at 0xc0 failed (error=-5) [ 1871.641101] tda18271_read_regs: [12-0060|M] ERROR: i2c_transfer returned: -5 [ 1871.641111] tda18271: Error reading device ID @ 12-0060, bailing out. [ 1871.641120] tda18271_attach: [12-0060|M] error -5 on line 1271 [ 1871.641130] tda18271 12-0060: destroying instance [ 1871.641308] em28xx: Registered (Em28xx dvb Extension) extension [ 1871.668037] em28xx 1-1.3:1.0: Registering input extension [ 1871.668128] em28xx: Registered (Em28xx Input Extension) extension [ 1873.482992] usb 1-1.3: USB disconnect, device number 7 [ 1873.483636] em28xx 1-1.3:1.0: Disconnecting em28xx [ 1873.483667] em28xx 1-1.3:1.0: Closing input extension [ 1873.486843] em28xx 1-1.3:1.0: Freeing device [ 1875.734726] usb 1-1.2: USB disconnect, device number 4 [ 1876.367563] usb 1-1.1.2: new low-speed USB device number 8 using dwc_otg [ 1876.489781] usb 1-1.1.2: New USB device found, idVendor=413c, idProduct=2113, bcdDevice= 1.08 [ 1876.489811] usb 1-1.1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 1876.489820] usb 1-1.1.2: Product: Dell KB216 Wired Keyboard [ 1876.504267] input: Dell KB216 Wired Keyboard as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/0003:413C:2113.0007/input/input8 [ 1876.564960] hid-generic 0003:413C:2113.0007: input,hidraw0: USB HID v1.11 Keyboard [Dell KB216 Wired Keyboard] on usb-3f980000.usb-1.1.2/input0 [ 1876.582118] input: Dell KB216 Wired Keyboard System Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.1/0003:413C:2113.0008/input/input9 [ 1876.641215] input: Dell KB216 Wired Keyboard Consumer Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.1/0003:413C:2113.0008/input/input10 [ 1876.641539] hid-generic 0003:413C:2113.0008: input,hidraw1: USB HID v1.11 Device [Dell KB216 Wired Keyboard] on usb-3f980000.usb-1.1.2/input1 [ 1878.300921] usb 1-1.3: new high-speed USB device number 9 using dwc_otg [ 1878.398031] usb 1-1.3: New USB device found, idVendor=0ccd, idProduct=10b2, bcdDevice= 1.00 [ 1878.398061] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1878.398070] usb 1-1.3: Product: TS Aggregator [ 1878.398078] usb 1-1.3: Manufacturer: CINERGY TC2 Stick [ 1878.398938] em28xx 1-1.3:1.0: New device CINERGY TC2 Stick TS Aggregator @ 480 Mbps (0ccd:10b2, interface 0, class 0) [ 1878.398966] em28xx 1-1.3:1.0: DVB interface 0 found: bulk [ 1878.454390] em28xx 1-1.3:1.0: unknown em28xx chip ID (0) [ 1878.514818] em28xx 1-1.3:1.0: reading from i2c device at 0xa0 failed (error=-5) [ 1878.514851] em28xx 1-1.3:1.0: board has no eeprom [ 1878.570921] em28xx 1-1.3:1.0: Identified as Terratec Cinergy H6 rev. 2 (card=101) [ 1878.570953] em28xx 1-1.3:1.0: dvb set to bulk mode. [ 1878.571060] em28xx 1-1.3:1.0: Binding DVB extension [ 1878.607950] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5) [ 1878.608169] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5) [ 1878.608376] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5) [ 1878.608572] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5) [ 1878.608781] em28xx 1-1.3:1.0: writing to i2c device at 0x82 failed (error=-5) [ 1878.620484] em28xx 1-1.3:1.0: reading from i2c device at 0x52 failed (error=-5) [ 1878.620701] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.620712] drxk: i2c write error at addr 0x29 [ 1878.631956] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.631985] drxk: i2c write error at addr 0x29 [ 1878.643223] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.643246] drxk: i2c write error at addr 0x29 [ 1878.654511] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.654539] drxk: i2c write error at addr 0x29 [ 1878.665798] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.665817] drxk: i2c write error at addr 0x29 [ 1878.676541] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.676567] drxk: i2c write error at addr 0x29 [ 1878.687810] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.687842] drxk: i2c write error at addr 0x29 [ 1878.699095] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.699118] drxk: i2c write error at addr 0x29 [ 1878.710366] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.710388] drxk: i2c write error at addr 0x29 [ 1878.721651] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.721674] drxk: i2c write error at addr 0x29 [ 1878.732917] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.732941] drxk: i2c write error at addr 0x29 [ 1878.744180] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.744220] drxk: i2c write error at addr 0x29 [ 1878.755455] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.755482] drxk: i2c write error at addr 0x29 [ 1878.766724] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.766748] drxk: i2c write error at addr 0x29 [ 1878.777833] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.777857] drxk: i2c write error at addr 0x29 [ 1878.789106] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.789129] drxk: i2c write error at addr 0x29 [ 1878.800391] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.800413] drxk: i2c write error at addr 0x29 [ 1878.811114] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.811137] drxk: i2c write error at addr 0x29 [ 1878.822457] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.822508] drxk: i2c write error at addr 0x29 [ 1878.833819] em28xx 1-1.3:1.0: writing to i2c device at 0x52 failed (error=-5) [ 1878.833851] drxk: i2c write error at addr 0x29 [ 1878.844246] drxk: Error -5 on power_up_device [ 1878.844271] drxk: Error -5 on init_drxk [ 1878.844284] drxk: frontend initialized. [ 1878.844312] tda18271 12-0060: creating new instance [ 1878.844574] em28xx 1-1.3:1.0: writing to i2c device at 0xc0 failed (error=-5) [ 1878.844593] tda18271_read_regs: [12-0060|M] ERROR: i2c_transfer returned: -5 [ 1878.844621] tda18271: Error reading device ID @ 12-0060, bailing out. [ 1878.844633] tda18271_attach: [12-0060|M] error -5 on line 1271 [ 1878.844651] tda18271 12-0060: destroying instance [ 1878.844859] em28xx 1-1.3:1.0: Registering input extension
-
Solved:
There is a small hole labeled RESET.
-
ah, thanks.
Well, I usually trust in those great open source projects and don't read release notesThe devel build has the same issue on my Raspy4
I just tried pause as well... pausing and waitung for a minute does not change anything. only full stop then restart at the last postition. to me this looks like a leak in the code somewhere.
For my Raspy3 I will go back to 9.2
I found a difference.
when it starts lagging the cpu usage of kodi.bin suddenly doubles from 25% to 50%
Code
Display Moretop - 10:22:36 up 16 min, 1 user, load average: 2.21, 2.03, 1.38 Tasks: 134 total, 1 running, 133 sleeping, 0 stopped, 0 zombie %Cpu(s): 3.3 us, 1.1 sy, 0.0 ni, 95.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 1848.8 total, 1325.9 free, 280.2 used, 242.7 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 1491.5 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 977 root 20 0 597828 150128 56124 D 25.8 7.9 5:06.75 kodi.bin top - 10:26:59 up 21 min, 2 users, load average: 2.16, 2.07, 1.57 Tasks: 136 total, 1 running, 135 sleeping, 0 stopped, 0 zombie %Cpu(s): 8.5 us, 5.6 sy, 0.4 ni, 85.1 id, 0.0 wa, 0.0 hi, 0.4 si, 0.0 st MiB Mem : 1848.8 total, 1318.0 free, 287.7 used, 243.1 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 1484.0 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 977 root 20 0 613816 149680 56044 D 50.5 7.9 6:38.67 kodi.bin
I believe it somehow loses timing. it tries to play the video as fast as possible instead of realtime.
-
Hi,
I am watching tons of videos in FullHD H264 from german ARD mediathek https://www.ardmediathek.de/
All of them start lagging after about 20 to 30 minutes of playback. I then stop and restart the video.
With lagging I mean the picture is stuttering and audio is out of sync.
H265 works fine.
any idea?
Raspy4B 2G
OpenElec 10, (doesn't show the version?!)
latest bootloader and USB firmware
original power supply, 42 °C under load
There is no obvious difference in bcmstat when playback stutters or when it doesn't.
btw, my Raspy3B suddenly started to lag with H265 videos (handbrake) which it didn't before. while H264 works fine (original power supply, too).
Maybe since upgrade from 9.2 to 10?
I used a Raspy1 for a year before, which did fine with H264 but always crashed with H265.
thanks
ps. there is something odd, why does it show only 1 gig of Memory?
Code
Display More# bcmstat.sh Config: v0.5.5, args "", priority lowest (+19) Board: 4 x cores available, ondemand governor (Pi4 Model B rev 1.2, BCM2838 SoC with 2GB RAM by Sony UK) Memory: 1024MB (split 948MB ARM, 76MB GPU) HW Block: | ARM | Core | H264 | SDRAM | Min Freq: | 600MHz | 250MHz | 0MHz | 3180MHz | Max Freq: | 1500MHz | 500MHz | 500MHz | 3180MHz | Voltages: | 0, 0.8500V | +0, 1.2000V | Other: temp_limit=85 Firmware: Mar 1 2022 14:22:32, version 969fb9b1521fc7ac2b88b15a3a9e942da7678c4d (clean) (release) (start_x) Codecs: H264 MJPG PCM Booted: Tue May 10 19:08:39 2022 Time ARM Core H264 Core Temp (Max) IRQ/s RX B/s TX B/s ======== ======= ======= ======= =============== ====== =========== =========== 19:34:49 700Mhz 233Mhz 278Mhz 41.87C (43.82C) 1,759 32 112 19:34:51 800Mhz 267Mhz 305Mhz 42.35C (43.82C) 2,435 33,598 484 19:34:53 800Mhz 500Mhz 305Mhz 42.84C (43.82C) 3,114 504,439 4,592 19:34:55 700Mhz 500Mhz 278Mhz 42.35C (43.82C) 2,964 437,037 3,705 19:34:57 700Mhz 500Mhz 278Mhz 41.87C (43.82C) 2,840 469,945 3,688 19:34:59 700Mhz 233Mhz 278Mhz 43.33C (43.82C) 2,738 469,837 4,994 19:35:01 700Mhz 500Mhz 278Mhz 42.84C (43.82C) 2,629 503,894 4,338 19:35:03 700Mhz 500Mhz 278Mhz 43.33C (43.82C) 2,602 368,617 2,597 19:35:05 700Mhz 500Mhz 278Mhz 42.84C (43.82C) 2,737 368,765 4,173 19:35:07 700Mhz 233Mhz 278Mhz 42.35C (43.82C) 2,757 337,102 2,972 19:35:09 700Mhz 500Mhz 278Mhz 41.38C (43.82C) 2,659 369,320 3,236
-
I already described my problem here:
ThreadUSB Remote Mele F10 Deluxe does not work any more
Hi,
I used my Mele F10 Deluxe for years. Currently on a Rasperry 3B running LibreElec 9.2
It does not work any more, no idea why. from dmesg:
(Code, 29 lines)
Now, is there any way to find out what exactly went wrong? Why isn't there a syslog?
I did experiment a bit, but I do not remember changing anything on the above system, see below:
I temporarly needed a second player and set up LibreElec 9.2 on a Raspberry 1B. Now I also needed a remote, because this TV does NOT support CEC.
I bought a used Mele…oJPToMarch 29, 2022 at 4:00 PM But as I did not get any answers I want to try a more general approach.
How exactly does a new USB HID device become a new input device for Kodi?
And how can I find out what exactly is happening?
In the meantime I figured out that
- all devices appear in LSUSB (Mouse, F10 Deluxe, F10 Pro)
- but only F10 Pro makes it to log entries in debug kodi.log (maybe because it delivers sound in- and output and joystick? see log below)
- mouse and F10 Pro work, F10 deluxe doesn't but did earlier
I found this:
https://wiki.libreelec.tv/configuration/ir-remotes
but it's rather IR focused, so it does not help much.
Not sure: does ALL input go through eventlirc or only IR?
how do I debug Eventlirc?
thank you very much
Code
Display MoreDevice 5 m_deviceName : @:CARD=Headset,DEV=0 m_displayName : Modiotek USB Headset m_displayNameExtra: Analog m_deviceType : AE_DEVTYPE_PCM m_channels : UNKNOWN1, FL, FR m_sampleRates : 48000 m_dataFormats : AE_FMT_S16NE,AE_FMT_S16LE m_streamTypes : No passthrough capabilities Device 6 m_deviceName : iec958:CARD=Headset,DEV=0 m_displayName : Modiotek USB Headset m_displayNameExtra: S/PDIF m_deviceType : AE_DEVTYPE_IEC958 m_channels : UNKNOWN1, FL, FR m_sampleRates : 16000,48000 m_dataFormats : AE_FMT_RAW,AE_FMT_S16NE,AE_FMT_S16LE m_streamTypes : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_512 AddOnLog: peripheral.joystick: Initialized joystick 0: "058F312D81A Modiotek USB Headset", axes: 8, hats: 0, buttons: 8 Loading controller layout: /usr/share/kodi/addons/game.controller.default/resources/layout.xml Loading controller layout: /storage/.kodi/addons/game.controller.mouse/resources/layout.xml ERROR AddOnLog: peripheral.joystick: Device "Sony Interactive Entertainment Wireless Controller": can't find <controller> tag Register - new joystick device registered on addon->peripheral.joystick/0: 058F312D81A Modiotek USB Headset
-
Hi,
I used my Mele F10 Deluxe for years. Currently on a Rasperry 3B running LibreElec 9.2
It does not work any more, no idea why. from dmesg:Code
Display Moreusb 1-1.3: New USB device found, idVendor=1915, idProduct=0196, bcdDevice= 1.20 usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-1.3: Product: RI usb 1-1.3: Manufacturer: MELE input: MELE RI as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:1915:0196.0001/input/input0 on usb-3f980000.usb-1.3/input0 input: MELE RI as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.1/0003:1915:0196.0002/input/input1 on usb-3f980000.usb-1.3/input1 input: MELE RI Consumer Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.2/0003:1915:0196.0003/input/input2 input: MELE RI System Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.2/0003:1915:0196.0003/input/input3 on usb-3f980000.usb-1.3/input2 on usb-3f980000.usb-1.3/input3 LibreELEC:~ # lsusb Bus 001 Device 004: ID 1915:0196 Nordic Semiconductor ASA Bus 001 Device 005: ID 0424:7800 Standard Microsystems Corp. Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub LibreELEC:~ # lsusb -t /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/3p, 480M |__ Port 1: Dev 5, If 0, Class=Vendor Specific Class, Driver=lan78xx, 480M |__ Port 3: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 3: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 3: Dev 4, If 2, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 3: Dev 4, If 3, Class=Human Interface Device, Driver=usbhid, 12M
Now, is there any way to find out what exactly went wrong? Why isn't there a syslog?
I did experiment a bit, but I do not remember changing anything on the above system, see below:
I temporarly needed a second player and set up LibreElec 9.2 on a Raspberry 1B. Now I also needed a remote, because this TV does NOT support CEC.
I bought a used Mele F10 Pro only to realize this got a completely different key layout and is missing the BACK button.I experimented with .kodi/userdata/keymaps but this did not help.
I switched remotes but the F10 Deluxe did not work at all on the Raspberry 1B.
I switched back and now it doesn't work on the Raspberry 3 any more, too.
Any idea?
ps. is there a way to monitor keypresses?
thanx
-
ah, thanks.
I took it from https://kodi.wiki/view/Keymap#Mouse
so, there is a mistake in there. could someone please fix it?
-
Hi,
I bought a Mele F10 Pro because it was used and cheap.
On the Mele F10 Deluxe there is a back button to the top right of the central circle.
On the Mele F10 Pro this is instead the right mouse button.
Not having a back button is a pain in the arse.
What I do not understand:
if I simply use a wireless mouse, the right mouse button works as both, back and context menu depending on where you click.
I already tried the Keymap Editor Addon, but I just don't get it. Assigning is somehow the other way round than the keymap file? It does not receive the mouse-right-click so it just doesn't do anything.
I tried this, but it doesn't work. Do I have to set this for every page not "global" alone?
thanks
-
- Kernel updated to latest 3.10.108 LTS
where can I find your kernel source and config?
-
In case anybody is interested:
You can open the case and solder a serial connector.
How to Open Tronsmart Vega S89 (Elite) and Access the Serial Console
Connect to your PC, switch on and immediately press enter to interrupt auto boot. (timeout is 1 or zero)
More or less bricked my Orbsmart. Tried to boot your Libreelec kernel of build 821. But the kernel doesn't boot. Do I need some params?
do you have any suggestion how to write the Libreelec system into rom? It's a squashfs archive. I cannot write this into /dev/block/system directly?
thanks
Code
Display Morem8_k200_v1#ext2load usb 0:1 0x1200000 libre821/KERNEL Loading file "libre821/KERNEL" from usb device 0:1 (usbda1) 6141952 bytes read m8_k200_v1#bootm 0x1200000 ## ANDROID Format IMAGE ## Booting kernel from Legacy Image at 01200000 ... Image Name: Linux-3.10.108 Image Type: ARM Linux Kernel Image (lzo compressed) Data Size: 4368132 Bytes = 4.2 MiB Load Address: 00208000 Entry Point: 00208000 Verifying Checksum ... OK Ramdisk start addr = 0x162b000, len = 0x1ab543 Flat device tree start addr = 0x17d6800, len = 0x4f62 magic=0xedfe0dd0 board_usb_stop cfg: 0 Uncompressing Kernel Image ... OK uboot time: 427475829 us. EFUSE machid is not set. Using machid 0xf81 from environment From device tree /memory/ node aml_reserved_end property, for relocate ramdisk and fdt, relocate_addr: 0x51b4001 Loading Ramdisk to 05008000, end 051b3543 ... OK Loading Device Tree to 05000000, end 05007f61 ... OK Starting kernel ... [ 5.073348@1] sd 0:0:0:0: [sda] No Caching mode page found [ 5.073492@1] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 5.084104@1] sd 0:0:0:0: [sda] No Caching mode page found [ 5.085004@1] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 5.095853@1] sd 0:0:0:0: [sda] No Caching mode page found [ 5.096706@1] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 5.375299@2] [RN5T618] NO BATTERY_PARAMETERS FOUND [ 5.382900@1] Error: Driver 'bt-dev' is already registered, aborting... m8_k200_v1#ext2load usb 0:1 ${loadaddr} libre703/KERNEL Loading file "libre703/KERNEL" from usb device 0:1 (usbda1) 7991296 bytes read m8_k200_v1#bootm ${loadaddr} ## ANDROID Format IMAGE ## Booting kernel from Legacy Image at 12000000 ... Image Name: Linux-3.10.99 Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 4905012 Bytes = 4.7 MiB Load Address: 00208000 Entry Point: 00208000 Verifying Checksum ... OK Ramdisk start addr = 0x124ae800, len = 0x2eb200 Flat device tree start addr = 0x1279a000, len = 0x4f62 magic=0xedfe0dd0 board_usb_stop cfg: 0 Uncompressing Kernel Image ... OK uboot time: 66475282 us. EFUSE machid is not set. Using machid 0xf81 from environment From device tree /memory/ node aml_reserved_end property, for relocate ramdisk and fdt, relocate_addr: 0x52f4001 Loading Ramdisk to 05008000, end 052f3200 ... OK Loading Device Tree to 05000000, end 05007f61 ... OK Starting kernel ... [ 5.037764@1] sd 0:0:0:0: [sda] No Caching mode page found [ 5.037911@1] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 5.048517@1] sd 0:0:0:0: [sda] No Caching mode page found [ 5.049421@1] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 5.060268@1] sd 0:0:0:0: [sda] No Caching mode page found [ 5.061123@1] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 5.589658@1] [RN5T618] NO BATTERY_PARAMETERS FOUND
-
Still trying.
The images are meant to flash with windows software? Tells "parse burning iamge fail". img files don't look like official android update imgs!
The zip files are meant to be installed through recovery update? Don't work either. Unzips to /tmp/ but to me it looks like it does not start the update script.
how do you install the tar files?
any help would be appreciated
-
Excuse me, could anybody give a hint how to load the LibreElec builds into ROM on my Orbsmart S82?
TWRP-k200 doesn't work. Android ROM Manager Apps all fail. Windows program doesn't load the libreelec images. stock recovery only does a factory reset.
If I use DD to write KERNEL into BOOT and copy the files from SYSTEM-squashfs into SYSTEM-ext4-partition... will that work?
thanx
-
Hi
Iv'e got the Orbsmart S82 and I cannot find a way to flash libreelec.
TWRP k200 does not boot. (installed with DD)
All those ROM apps just crash or don't do anything.
Tried one of the Windows programs to flash, did not accept the file formats of libreelec download.
So how the hell do you flash libreelec?
I could flash SYSTEM into SYSTEM and KERNEL into boot using DD. But if this fails the box will be bricked.
btw. did any of you succeed in opening the case? Maybe theres some serial line anywhere?
thanx
-
Hi
I would like to install libreelec to my Orbsmart S82.
I already installed TWRP but I cannot boot TWRP.
I did not find a software for flashing from windows. (except amlogic which did not accept any of the images you provide)
Could you give directions on how to install libreelec?
I will try ADB or a terminal app for image backup... and maybe for installation as well. Which image format should I use for installation via dd?
thanks