Adding a Samba share via the "Add a network location..." browse option, including adding full credentials, should also work.
network browsing is dependent on use of SMB1 and there is no equivalent in the SMB2/3 protocol; blame Microsoft
Posts by chewitt
-
-
You cannot "Network browse" to the box unless it has SMB1 active, but you can provide the full \\server\share path in the Kodi GUI and Kodi should connect to the share and prompt for username/password. I personally find it easiest to edit /storage/.kodi/userdata/sources.xml but Windows people tend to have irrational command line phobias.
-
Nope. Go into the services tab and enable BT first, then the BT devices screen will be active.
-
Running a torrent client is not a banned practice because bittorrent does have legitimate uses. However it's quite obvious from the log that you are using yours to steal the new Baywatch movie using a torrent file from TPB. This project does not endorse content theft/piracy and this is not one of the legitimate uses of bittorent we might entertain support for.
-
Not possible in Krypton. Might be possible in Kodi Leia if I continue to nag people on the Kodi side (as it's something I'd like to see too). No promises though as it requires core code changes (not just skin things) for it to happen.
-
-
It's a skin-specific setting. It is not present in Estuary.
-
Fix for ffwd/rew events will be in the next 8.1 beta or 8.2 final release (not sure which it will be yet).
-
You can also remove the custom NTP servers because we already use (fall back to if nothing specified) ntp.pool.org servers.
-
It's probably easier to go find a Windows 7 VM for the task.
-
I doubt there is any programmatic method to tell Kodi "wait until this python add-on command has finished" so as it shuts down slice.service is forcibly unloaded and that terminates playback of the shutdown LED pattern. The overall OS shutdown process does have a dependency on unmounting HDD(s) so if they respond differently in terms of time (which I think is likely) the pattern will play for a different time period. It might be possible to add a systemd service to the Slice image that runs a simple delay/countdown .. but figuring that out (as I'm no systemd expert) will be a super-super-low priority. If others want to poke around and figure it out, it would be welcome.
The same file is used for normal rewind and faster rewind, but maybe something in the python? (as I don't do/read python):
LibreELEC.tv/default.py at slice-8.2 · chewitt/LibreELEC.tv · GitHub
-
Just rename samba.conf to samba.disabled before rebooting, then it's easier to compare and make changes to the new samba4 template
-
It's probably somewhere in /storage/.kodi/addons/service.tvheadend42/ not the dir where Kodi stores add-on settings?
-
No drivers seem to be activated.
I can't see a Xbox type driver anywhere in Device Manager.
That's because the LibreELEC USB/SD creator app does not install Pi Foundation CM drivers. You've imagined that capability
Flashing the Compute Module eMMC - Raspberry Pi Documentation
tells you to install this: rpiboot_setup.exe
Using Win7 I have never seen/experienced the drivers executing rpiboot.exe automatically, but manually connecting the box, running rpiboot.ext with admin rights, then applying power, seems to work. Once the eMMC storage shows up in Windows you can run the USB/SD app to image it.
-
kszaq, can you tell me, what is the situation with libreelec for RK3399 with ARM Mali-T860 MP4 Quad-Core GPU?
Completely unsupported and no near-term plan to support.
I found instruction, how to install Ubuntu on FireFly board with that CPU - Firefly-RK3399/Build Ubuntu rfs/en - Firefly wiki .
Does Ubuntu contains Mali-T860 drivers?
You're asking questions about hardware we don't support on an OS we don't support. Please go ask in the Ubuntu forums.
-
The update process only replaces files in /flash it does not touch /storage in any way. So update vs. clean install is all about Kodi caching or config and not the type of update file used or the actual update process.
I've seen the random green LED (nearest power socket) a few times on both 8.0.2 and 8.1.0 and I have no clue. I'm wondering if some extra blank pixels need to be added to ensure the LED's are cleared in some scenarios?
-
Code
Display More[ 3.491608@1] mmcblk0: sd:1388 NCard 14.8 GiB (ro) [ 3.514280@1] mmcblk0: p1 [ 3.919301@0] mmcblk1: emmc:0001 NCard 7.21 GiB [ 3.919434@0] mmcblk1boot0: emmc:0001 NCard partition 1 4.00 MiB [ 3.919562@0] mmcblk1boot1: emmc:0001 NCard partition 2 4.00 MiB [ 3.920731@0] mmcblk1: p1 [ 3.922404@1] [mmcblk1p01] bootloader offset 0x000000000000, size 0x000000400000 [ 3.922604@1] [mmcblk1p02] reserved offset 0x000002400000, size 0x000004000000 [ 3.922789@1] [mmcblk1p03] cache offset 0x000006c00000, size 0x000020000000 [ 3.922977@1] [mmcblk1p04] env offset 0x000027400000, size 0x000000800000 [ 3.923164@1] [mmcblk1p05] logo offset 0x000028400000, size 0x000002000000 [ 3.923338@1] [mmcblk1p06] recovery offset 0x00002ac00000, size 0x000002000000 [ 3.923506@1] [mmcblk1p07] misc offset 0x00002d400000, size 0x000002000000 [ 3.923720@1] [mmcblk1p08] boot offset 0x00002fc00000, size 0x000002000000 [ 3.923903@1] [mmcblk1p09] system offset 0x000032400000, size 0x000060000000 [ 3.924074@1] [mmcblk1p10] data offset 0x000092c00000, size 0x00013b500000 [ 3.925427@1] mmcblk1boot1: p1 [ 3.925450@1] mmcblk1boot1: p1 start 16065 is beyond EOD, truncated [ 3.926875@1] mmcblk1boot0: p1 [ 3.926892@1] mmcblk1boot0: p1 start 16065 is beyond EOD, truncated [ 6.115749@1] EXT3-fs (mmcblk1p9): error: couldn't mount because of unsupported optional features (40) [ 6.116116@1] EXT2-fs (mmcblk1p9): error: couldn't mount because of unsupported optional features (40) [ 6.123021@1] EXT4-fs (mmcblk1p9): mounted filesystem with ordered data mode. Opts: (null) [ 6.272221@1] EXT3-fs (mmcblk1p10): error: couldn't mount because of unsupported optional features (40) [ 6.272595@1] EXT2-fs (mmcblk1p10): error: couldn't mount because of unsupported optional features (40) [ 6.280626@2] EXT4-fs (mmcblk1p10): mounted filesystem with ordered data mode. Opts: (null)"It works in Windows" because Windows blindly trusts whatever disk/partition geometry data is presented to the OS before it goes ahead and mounts the partitions on the storage device. In comparison; Linux validates the geometry data presented to prevent data loss issues. In this case the partition data is invalid so Linux correctly refuses to mount the damaged partitions. Id guess the SD card is going bad, or there are traces of previous partition schemes on the storage that cause conflict.
Use our USB/SD creator app to restore bootsector.img to the SD card then reformat the media in Windows (any format scheme you like) and try again.
-
I don't care how the video is encoded. I care about seeing a debug log from Kodi that shows how it plays.
