Pastebin a Kodi debug log file.
Posts by chewitt
-
-
CONFIG_HID_MAGICMOUSE needs to be set in our kernels
-
Samba versions before 4.7 default to making NT1 (SMB1) connections and since 8.1.0 our embedded Samba server only speaks SMB2+
Remove "protocol = SMB2" because this is a server configuration item that has no effect on smbclient. You need to set this instead:
This assumes the version of Samba installed on Mint is 4.1+ to support SMB2. It will also 'break' connectivity with anything else in your network that can only speak SMB1 as the client is now forced to SMB2 or higher.
This should not be required once the version of Samba installed in Mint is 4.7+
-
Full and clean logs after a reboot, not the last 6 mins after everything has rotated.
-
LE settings controls the embedded Samba server. Kodi settings control the smb client that accesses shares on the Win7 box.
In other words; changing server settings will not result in the Kodi client using SMB1.
-
In recent times most Broadcom stuff is mainlined and should be reliable. There is a lot of old crap still in circulation though, where there's a dogs-breakfast mix of things that require different (ID overlapping) drivers and things that are not supported on Linux for some reason. Not the worst offender (Realtek have that crown) but not blameless either.
-
settings > player > videos > skip steps
-
Not supported, and will not be supported. Time to invest in a Raspberry Pi to sit alongside the NAS.
-
Index of /test/ has 8.2.0.1 files with the same patch applied
-
Change the disk label and then change extlinux.conf to use disk=LABEL=newlabel .. beware there are two instances depending on whether the box EFI boots or not, the second is under the EFI folder.
-
With the fixed image the box might struggle but it won't deadlock when opening the file. Don't expect miracles on an RPi2 though.
-
Console on CTRL+ALT+F3 depends on the device and whether a local console is configured in boot commands (which vary by device).
What hardware?
-
-
The ability to play HEVC will be no different from before, but the codebases are aligned so we have to 'fix' all of them the same.
-
It's up to the board manufacturer to decide whether their product has power management and support for sleep/suspend and related features like waking on USB activity. However this costs $€£ so 99.999% of manufacturers believe their product is power efficient and can be left on permanently so they do not include it. I doubt Rockchip manufacturers will be different from Amlogic et. al.
Wake from IR is normally possible with customised uboot. Our challenge will be providing support with Generic uboot, so no guarantees.
-
Provide the full log not the snippet you think might be relevant.
-
-
If you don't complain back to RTL they will continue to churn out more new drivers that do not follow kernel architecture or quality standards. You need to complain. Lots of other people need to complain too. Unless people actively complain nothing will change.