OSX drivers would be worthless on Linux. Job security would be terrible because everyone expects drivers for free (even the manufacturers)
Posts by chewitt
-
-
milhouse images don't contain the Slice overlays or drivers for the DAC/LED's. Unless you're self-building images you'll need to wait for alpha releases to start up.
-
Moonlight is in our add-on repo. No steam stuff.
-
Your add-on allows the TV and BT headphones dual audio, correct?
Incorrect. It auto-switches to BT when a speaker (or headphones) are connected and switches back to normal audio when disconnected.
-
Windows allows you to force resolutions regardless of what the TV advertises. Linux does not. We don't intentionally support running on old laptops so you are probably better off using Kodi on Windows.
-
Post a Kodi debug log.
-
You need to share "dmesg" within a few minutes of boot. The log you posted has rotated and contains nothing useful.
-
Python things need to be baked into the OS image, it's not possible to install them.
-
Nothing leaps out to me as being wrong but I'm no Samba genius. If you use smbclient from the console, what error message is returned?
-
He already tried "FR" which is a valid regdom. It appears to be something else .. but debugging wireless connectivity issues requires rather specialist knowledge of radio properties and without some nice error messages to Google progress will be non-existent.
MikeKL sprunge.us is offline (and may not return) so can you repost the files to ix.io or pastebin.com?
-
Hmm.. looking in sources it appears to have been added a while back and I'd not noticed. I must work on my omnipresence
So if that's the location. I'd guess there is some issue with the changes you're trying to make. Alsa config is a bit of a dark art and few people understand it so advice is often not forthcoming.
-
AFAIK LibreElec supports dual audio output (analog + hdmi) out of the box.
Not with alsa reconfiguration, and in Harry Potter terminology this is a 'dark art' that few people understand.
-
Like finance investments "past performance is not a guarantee of future performance" and with GPU drivers we are ultimately dumb consumers of what the vendors publish. I'm far from being an expert on the history of things, but VDPAU is dead and newer AMD drivers use VAAPI (as does Intel) which is still evolving. It's worth Googling the driver mailing lists and vendor bug trackers for issue reports and responses, because ultimately that's where things need to be reported and resolved.
-
Have you enabled BT under 'services' in the LE settings add-on? It is not on by default.
-
MT7610U has a Linux driver that "works" but makes crappy Realtek drivers look like polished perfection. It does not follow basic kernel standards for important things like wireless regulatory domain and is not of sufficient quality to consider adding into LE. The related but older MT7601U was ground-up rewritten and has had in-kernel support for about 18-months, but there are no signs of it being extended to the the newer mediatek chips. As is usual for far-east wireless chip vendors, they appear to have no interest in Linux.
-
UPnP uses "bonjour" networking which is TCP/UDP multicasted on the source (first) subnet. If the RPi is behind a NAT gateway the multicast traffic is blocked so devices in a second subnet (behind the gateway) will not be able to see bonjour devices in the first. The router is handling normal TCP/IP traffic so Samba shares etc. can be reached.
I typically see this when people have an internet router and then use a second router to extend wireless into another part of the house. The second router creates a second subnet with NAT on the 'WAN' interface. Despite 'double NAT' it will work for internet access, but devices in the second subnet cannot see broadcast data from the first. In this scenario the easiest fix is to configure the 'router' to be a 'bridge' interface to the original network and not actually route. Most routers support this; it's just not the default option.
-
So I should edit QNAP's smb.conf and add the settings. Or should I edit LibreELEC smb.conf and add these settings?
QNAP .. because you are setting "client" min protocol and it's the client.
-
Security for local private network isnt big issue, SMB1 is used more as 20years...
People who experienced the WannaCry ransomware attack might disagree with your bad advice.
zx-9r Samba versions from 4.1 > 4.6 will always attempt to connect at SMB1 unless smb.conf forces SMB2 via "client min protocol" and I'd guess the Samba version in the QNAP falls in that range. If LE samba is set for SMB1-3 it connects at SMB1 and things work. If LE is set for SMB2-3 the client still attempts to connect at SMB1 and things fail. From Samba 4.7 onwards the connection default is SMB3_11 and the client auto-negotiates lower versions if required.
