False. Our default disk layout for the Generic image is two partitions in a GPT partition scheme. If you want to install to the disk manually boot the installer in live mode or use an Ubuntu LiveUSB to create a GPT disk, first partition is 512MB and second is remaining space. Make both ext4 and install syslinux to the first partition. Now copy the KERNEL, SYSTEM and extlinux.conf to the first partition. That's all the installer does.
Posts by chewitt
-
-
Not possible as-is or out of the box. It would need someone to repackage the code as a binary add-on. That means it's possible, but unless you write the code or find a willing volunteer it's unlikely to happen.
-
You probably need to tweak the key-repeat time settings for the remote control. We set some sensible defaults but some devices need a little adjustment. As there are multiple device-dependent methods for doing this you'll need to explain what you're using?
-
It's not an add-on that we provide or create so our ability to diagnose/support the issue is limited. You're better off posting the question/issue to the Kodi forum support thread for the add-on - where its author will see the post.
-
In what previous release were they working?
-
Code
[ 1.297421] scsi 0:0:0:0: CD-ROM PIONEER BD-RW BDR-TD05 2.00 PQ: 0 ANSI: 5 [ 1.338136] sr 0:0:0:0: [sr0] scsi3-mmc drive: 62x/62x writer dvd-ram cd/rw xa/form2 cdda tray [ 1.338140] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 1.338657] sr 0:0:0:0: Attached scsi CD-ROM sr0 [ 1.338870] sr 0:0:0:0: Attached scsi generic sg0 type 5^ that looks like a Blue-Ray drive in /dev/sr0 (the normal place for one under Linux).
NB: Kodi does not show the 'disc' menu unless there is a readable disc inserted, and if you are inserting encrypted BR media you will need to add a KEYDB.cfg file to /storage/.cache/aacs/ else the media remains encrypted and unreadable. It is not possible to legally play your legally owned BR media under Linux as there are no legally licensed player apps (they only exist on Windows/macOS). We cannot provide the KEYDB file and we will stop short of providing URLs to them to avoid violating laws, so you will need to Google and source the file and violate them yourself
-
Do you have that code in GitHub anywhere?
-
Kodi versions are not cumulative, i.e. stuff gets removed as well as added, so Krypton != Jarvis.
-
LE 8.2 will go into private team testing in the next week or so with the aim of a public beta towards end of July (after some team people are back from vacations) and all being well, release in August.
-
Kodi "builds" and "wizards" exists to bulk-install pirate streaming add-ons. We follow the same general principles as the Kodi forum and refuse all support regardless of issue to any user with pirate streaming add-ons installed. You now need to show us a Kodi debug log to prove your system is free of pirate add-on crapware before support will continue. Thanks.
-
Kodi has a general bug where it returns to the first item in the list after completing a video library item. The bug is in Krypton which is why an older OE release with Jarvis/Helix etc. didn't have the problem.
-
The connection manager (connman) service manages the functionality of the hotspot and aside from the options I mentioned above all behaviour is internal and hard-coded. There is no config file hidden somewhere that you can tweak.
-
As a broad rule NUC's are plentiful in number so issues are seen early in testing so we're not aware of any major issues. Current OE and LE releases should be using the same kernel series and driver/firmwares so will be broadly the same. Older OE and current LE will have larger differences. I'd start by making sure all have the latest BIOS/firmware available as that's what the newer drivers etc. are developed against. Then if that didn't cure anything run "dmesg | paste" and share URLs so we can see boot processes and look for error messages.
-
I'd guess the SATA controller hardware isn't supported, which is either simple or horribly complicated to resolve (in software) depending on what chipsets are involved. Run "dmesg | paste" and "lscpi | paste" from the console and share the URL(s) please.
-
Then cross fingers and hope there are no undiscovered vulnerabilities in the TVH webserver that has been exposed to the Internet. I'd advocate using a private VPN to securely access the home network, then navigate (as normal) to the TVH device.
-
Please run "lsusb | paste" and "dmesg | paste" and share the URL's generated so we can see what chipset is in the DAC or how it identifies with the kernel during boot. Then we can see what's required to support it.
-
It will not give you complete instructions on how to configure dual-audio, but with some fiddling about you can probably do dual-streaming. It will just require some different pulse modules to be loaded first.
It is not possible to edit content in /etc because the filesystem is read-only.
-
Not possible. ON/OFF, SSID and password are the only config options. It is functionally the same as the hotspot on your phone.
The only thing you could try is connecting the other way.. i.e. tether LE device to phone hotspot. As long as the remote app and box are in the same IP subnet they should be able to talk.