Posts by chewitt

  • [S905] WiFi issues (w/ test builds)

    Code
    kernel: mt7601u 1-1.3:1.0: ASIC revision: 76010001 MAC revision: 76010500
kernel: mt7601u 1-1.3:1.0: Direct firmware load for mt7601u.bin failed with error -2
kernel: mt7601u 1-1.3:1.0: probe with driver mt7601u failed with error -2

    There is no Realtek WiFi hardware visible in any of the logs shared. There IS a Mediatek USB WiFi device visible in all logs shared and this is missing firmware (as above). The Linux 6.18-rc7 kernel images posted to my test share a few days ago (mentioned in post #4) have the missing firmware added. The latest logs you shared show a Linux 6.17.4 kernel image that does not contain the firmware (although you can always add it manually using the commands in post #2). If you believe there to be Realtek WiFi hardware inside the box you need to pastebin the old vendor kernel dmesg log somewhere so I can maybe see what chip is present.

    NB: LE has its own paste server so in the AMLGX images all you need to do is run "pastekodi" and share the URL generated.

  • [RPi5] GUI colors and resolution problem

    Random thoughts:

    a) Always use the HDMI port nearest the PSU connector

    b) Are you using any kind of micro-HDMI to HDMI adapter? .. or a proper micro-HDMI to HDMI cable? - If you are using an adapter, this is probably the source of the problem.

    c) If using a proper micro-HDMI to HDMI cable (no adapter) put Kodi in debug mode, reboot, then SSH in and run "pastekodi" and share the URL .. perhaps we can see something.

  • [RPi5] GUI colors and resolution problem

    video=HDMI-A-1:1920x1080M@60D

    Add that ^ to boot params in cmdline.txt and the initial DRM state is forced to 1080p and that should stop the image being in 1/4 of the screen?

    The colour change is probably the projector switching itself to a different RGB output mode. It’s nothing that LE/Kodi can control.

  • Web Browser for Non-Legacy LE?

    No. Docker virtualises the app not the environment it runs in. So the container provides ann app which still requires a windowing environment to run under, and this still does not exist.

    There is a browser called Ozone which can in theory run under GBM, but this needs to be built from sources and has a ton of dependencies so nobody has ever volunteered for the huge effort of trying to implement it for LE.

  • [RPi5] HiFiBerry Digi2 Pro Setup

    Quote from thedogg

    I was pretty sure pi5 allows for multiscreens.

    RPiOS can create a single 'desktop' over mutiple displays but then Kodi runs in a window on the desktop and you have to choose which desktop you want full-screen output on (as Kodi does not handle multiple screens) and you cannot 'adjust-refresh' display mode to suit the media being played (as Wayland does not allow this).

    The closest you can get is stopping Kodi, editing config files with scripts to change outputs, then restarting Kodi. There is no way arouond the stop and restart because Kodi does not support dynamic change of video output.

    I would describe the scripting approach as fragile. Feel free to experiment, but don't be surprised when it isn't reliable.

  • [RPi5] HiFiBerry Digi2 Pro Setup

    Kodi supports outputting at 1080p and switching to 4K only when required, but it cannot handle dynamic changes of HDMI output and it has no concept of fallback logic for HDMI connections. IMHO the best solution will be to send everything to the AVR and use the video/audio source mapping functions there to deliver the output routing you want.

    In short, LE will not do what you require, and as the Kodi featureset is pretty consistent on all platforms I don't think any other distro or OS platform will do it either.

  • [RK3566] LE for Pine64 Quartz64 Model A

    I've updated the RK356X images (and .tar) in my test share to pick the CEC fixes and include a 'getedid' script. Please test without using getedid and if the issue is solved I will add the patches to the list of things that I can nag Kwiboo about :)

    Not sure about the video stutters, although if that's only in the lastest image (last 24h) it's possibly due to an ffmpeg bump; it would help to see a Kodi debug log to understand config/environment and media. I will dig up a Rock 3C board and experiment in the next couple of days.

    Also no idea on Kodi profiles. The patch you flagged was dropped with the Python 3.9.10 bump aeons back, so if there's an issue it's presumably a new bug as that fix is upstream. You'll need to share a Kodi debug/crashlog for someone to look at.

  • [x86-64] No Bluetooth device found

    The listing of the device in "lsusb" only proves the USB bluetooth receiver is connected, not that it works or is working.

    To eliminate the LE settings add-on from the process (not known to have issues, but not impossible) you can use "bluetoothctl" to scan for devices and pair them from the console. See how that goes.

  • [x86-64] Videos freeze due to CPU at 100% on mini PC

    Quote from mibane

    As I can read here in the wiki, audio has to work. As the device is currently connected to a standard monitor without speakers, I wonder if this may contribute to all the issues?

    Kodi appears to read some HDMI audio capabilities from the DRM driver layer, but the EDID data from the monitor presumably shows no speakers so Kodi ends up running in circles trying and failing to open an audio sink. This eventually fails but only after generating a ton of log noise. It will be more productive (and less log-noisy) to run tests with the TV. You must also run "getedid delete" as the previous inappropriate advice to run it will force the kernel to always see the monitor (with no speakers) attached instead of the TV .. thus guaranteeing bad results.

  • [x86-64] Videos freeze due to CPU at 100% on mini PC

    Code
    2025-11-23 12:12:46.454 T:900     error <general>: SMBFile->Open: Unable to open file : 'smb://192.168.178.13/VIDEO/SPIELFILME/JAMES%20BOND/James%20Bond%20007%20-%20In%20t%c3%b6dlicher%20Mission%20(1981).mkv'
                                                   unix_err:'16' error : 'Invalid argument'
2025-11-23 12:12:46.454 T:900     error <general>: CFileCache::Open - <smb://192.168.178.13/VIDEO/SPIELFILME/JAMES BOND/James Bond 007 - In tödlicher Mission (1981).mkv> failed to open
2025-11-23 12:12:46.454 T:900     error <general>: InputStream: Error opening, smb://192.168.178.13/VIDEO/SPIELFILME/JAMES BOND/James Bond 007 - In tödlicher Mission (1981).mkv

    The first error looks like Kodi is configured to use the default HDMI device (#0) when the active/connected HDMI device is #2 so the alsa audio sink cannot be opened.

    The second error is related to SMB (invalid argument) so check that you are using a valid IP/path and credentials in sources.xml and the SMB protocol versions used by the Kodi SMB client are correct for the NAS.