It's not clear which device you do want to use, but assuming it's the AMD card the following will blacklist the nVidia driver module and prevent it from being loaded at boot time; at which time only the AMD card should be usable and xorg.conf(s) shouldn't come into play.
echo "blacklist nvidia" > /storage/.config/modprobe.d/nvidia.conf
rebootLooks like the device ID exists in both drivers (bcma and wl) so whichever one happens to be loaded by the kernel first (roll dice) tries to claim the device. We should probably patch out the device ID to prevent that.
I wonder if there's a workaround or if there's a working addon somewhere.
It only works on LE 9.0 images. Update.
what does "lsmod" show?
Oct 19 23:54:25 kernel: bcma: bus0: Found chip with id 0x4360, rev 0x03 and package 0x01
Oct 19 23:54:25 kernel: bcma: bus0: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev 0x2B, class 0x0)
Oct 19 23:54:25 kernel: bcma: bus0: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x2A, class 0x0)
Oct 19 23:54:25 kernel: bcma: bus0: Core 2 found: ARM CR4 (manuf 0x4BF, id 0x83E, rev 0x02, class 0x0)
Oct 19 23:54:25 kernel: bcma: bus0: Core 3 found: PCIe Gen2 (manuf 0x4BF, id 0x83C, rev 0x01, class 0x0)
Oct 19 23:54:25 kernel: bcma: bus0: Core 4 found: USB 2.0 Device (manuf 0x4BF, id 0x81A, rev 0x11, class 0x0)
Oct 19 23:54:25 kernel: bcma: Unsupported SPROM revision: 11
Oct 19 23:54:25 kernel: bcma: bus0: Invalid SPROM read from the PCIe card, trying to use fallback SPROM
Oct 19 23:54:25 kernel: bcma: bus0: Using fallback SPROM failed (err -2)
Oct 19 23:54:25 kernel: bcma: bus0: No SPROM available
Oct 19 23:54:25 kernel: bcma: bus0: Bus registered^ looks like the card is trying to use the in-kernel brcmfmac driver instead of the vendor wl driver, so perhaps blacklist it and reboot:
echo "blacklist brcmfmac" > /storage/.config/modprobe.d/brcmfmac.conf
rebootsorted?
только английский пожалуйста
It's not sure it's possible to damage the CM1 unless you've opened the case and done anti-static nastiness. There's an element of timing and sequence to the flashing process though. It's a bit fiddly.
CM1 is fine for audio only. If it's works, no need to fix it.
If you share the log we can see if there's an obvious problem. If you don't share the log .. we are not clairvoyant. It's entirely your choice.
There is no need to unsquash/squash. Just create /storage/.config/xorg.conf with whatever content you require for your GPU and it will be used in preference to the any of the embedded conf files on next boot.
AMD supports GBM (Generic Buffer Management) which facilitates the future V4L2 pipeline same as every other GPU/SoC vendor. nVidia has decided to follow their own "standard" that nobody else uses. Team Kodi are done with supporting proprietary standards due to all the extra code spaghetti and support work it entails so AMD (and basically all other current vendors except nVidia) are fine and support for nVidia in Kodi will almost certainly die off. We see it as nVidia's responsibility to start following standards, not our responsibility to rewrite everything around nVidia.
Not at the moment. Maybe in the future (but in a different fashion) once things go mainline, although that will require a complete reinstall anyway as the mainline kernel does not support Amlogic's custom partition scheme.
Find a 3.14 kenel buildroot release from Amlogic that supports S905 and you should be able to use the FIPS to make something. It's all Amlogic provides to basic partners anyway. Have a look at the NanoPi K2 sources that FriendlyElec uses.
IPTV simple is installed from the LE addon repo. If you install the addon from anywhere else it's not our code and not our problem to solve.
Another approach would be using systemd mounts (see /storage/.config/system.d/ for samples) to locally mount the remote file shares. Each mount can use different options for protocol versions. Then set sources to the local mounts and scrap to the library.
It depends on the specific hardware. In some cases you can flash the firmware to be region free accepting any disc forevermore without extra input. In other cases the drive will still behave as if region locked; it will prompt for a region change and counts down the number of allowed region changes until zero is reached and it self-resets back to 5-6 attempts remaining (or whatever the magic number is). It's still rare to find region free drives, but these days there are numerous websites where you can acquire modified firmware and the flashing utilities needed.
I'd create a webpage that sends JSON-RPC commands to play specific media (from the local filestore) on a specific device. Kodi has a full API for that kind of thing - it's how the Android/iOS remote apps and WebGUI(s) are implemented. You can place media in a central location and use cron + rsync to run a nightly sync job to update local media.
The main factor is the hardware and what it's technically capable of playing. For example; Odroid C2 has an S905 chip (not S905X, S905D or other lettered variants). This means it can play 8-bit H.264 media and 8-bit or 10-bit H.265 (HEVC) media. It will not play 10-bit H.264 (it will try to software decode it, but the CPU can't cope) and it will not play 10-bit HEVC files with HDR encoding (as the original S905 doesn't support HDR). To get a more specific answer you'll need to share a Kodi debug log that shows the problem media being played. The log has information on the encoding (and other factors) and from there we can make more educated guesses on what the problems are. Sometimes it's unsupported media. Sometimes it's just badly encoded media.