Run "lsusb | paste" and "dmesg | paste" and share the URLs generated.
Posts by chewitt
-
-
What am I missing?
We looked in our crystal ball but couldn't figure out your undocumented boot issue. UART logs would be more informative.
-
-
There are users who've wanted centralised logging before so if you have Logstash in your stack we have an existing rsyslog daemon add-on in our repo. I don't recall ever hearing/seeing someone capture logs with Filebeat, but since we can run Docker and there is probably an ARM container with Filebeat on a docker repo somewhere, it should be do-able.
-
-
There is no list - we've always refused to create one on the principle it will be immediately out of date and it's yet another thing we'll have to (and forget to) maintain over time. Anything that has driver support in the upstream Linux kernel is or can be supported today, and anything that needs "out of tree" vendor drivers will be politely refused. LE has some vendor drivers only for a subset of Realtek devices that shipped as official WiFi cards for older Pi boards (as they didn't have on-board WiFi at the time). Over time the percentage of these boards in active use is declining (and RPi0/1 are no longer supported) and at some point we will switch from wpa_supplicant to IWD which will drive a large nail in the coffin of those drivers.
-
-
Most of the time the upstream focus on "board" devices is making the HDMI output work and you only see support for the 3.5mm Jack on devices that run ChromeOS. Does the upstream kernel (device-tree) for your board support the 3.5mm audio jack?
-
-
It will allow the widevine-helper add-on to download a 7MB libwidevinecdm.so file from Pi Foundation servers instead of having to download a 1.7GB ChromeOS update to unpack and extract the file, which is a nice improvement to user experience. It will make no difference to how widevine using streaming services operate, i.e. the formats or resolutions that can be used for media playback - there are no changes to widevine certification status.
-
Ahh ok. Best to ask in the Kodi forums where the scraper authors hang out.
-
Next time it has problems .. leave it 10 mins then "journalctl | paste" and share the URL so we can see the full boot log.
-
frakkin64 the images here Index of /testing/ have some tweaks to ffmpeg to improve (but not fix) seeking. It needs a proper coding community developer to take interest (or a large $$ sum to fund proffesional interest) to make progress.
-
IIRC the default scraper changed from TVDB (v17) to TMDB (v18) due to TVDB switching to a commercial model and removing their user forums and other support methods. So the change will have nothing to do with RPi3 vs RPi4 but you probably switched hardware when switching to v18 and thus picked up the change at the same time. There are some tips in Add-on:TMDb TV Shows - Official Kodi Wiki to help with picking the correct show.
-
Kernel drivers should see that 120Hz modes are available on the HDMI connection and filter them out so that userspace applications cannot see or use them.
-
In the new video pipeline modes above 85Hz should be hidden since the hardware decoder(s) are not expected to work at those frame rates (bitrate is one variable but not the main one). It looks like there may be some scenarios where >85Hz rates are still visible, but now the Pi Foundation devs are aware I'd expect that to change in the near-term future. TL/DR; not supported.
-
Remove the SD card, add "ssh" to kernel boot params in extlinux.conf on the card, then boot and SSH into the box to use "kodi-remote" to navigate on the screen. Or plug a USB keyboard in..
-
They attempted to PR an Argon40 add-on to the Kodi repo; but it was Python2 and also LE specific so it was (correctly) rejected. I've since noticed an LE package in their GitHub repo; but it's a standalone package and it's not in a fork of our repo which is a rather odd approach (first time I've seen a dev get that wrong). The code is still Python2 and the package.mk had numerous other issues. I was kind of expecting them to reach out and ask Q's on how to submit to our repo .. but I've not noticed any emails. I'm sure they'll figure it out eventually.
