Posts by chewitt
-
-
Remove old drive. Clean install LE to the new drive. Connect old drive to USB cable and plug into HTPC, wait for the drives to mount. Stop Kodi, copy over all the stuff you want from the old drive, restart Kodi and all your old config is there. Disconnect old drive, then in a few weeks when nothing went wrong with the new drive you can reformat the old one and use it for backups or something.
It's usually faster to copy data in a filesystem than make a block-by-block copy of the entire filesystem.
-
It's still not a debug log but there is no apparent attempt to install anything so nothing fails. I can see pvr.hts is present though, so at some point you have successfully installed the TVHeadend client from our repo.
If the repo's look blank, either force refresh them manually or add a "wait for network" startup delay of 10 seconds in LE settings.
-
piotrasd will be your new best friend
-
There are usually some installation challenges (especially on older Mac hardware that sucks at USB booting) but x86_64 compatible Mac hardware should be able to run the Generic image. It is not widely used though (new NUC's are considerably cheaper than new Mac minis) so there are some lingering grey areas on support.
-
It depends on how the backup was taken and then restored. Kodi is quite portable but the usual problem is the inclusion of filesystem paths that are not going to be the same under different OS platforms. You'll also have issues with binary add-ons.
-
-
You probably need to set the alsa audio configuration. What is the model number? - e.g. A1234 or like 4,1 in Apple's base,variant format.
-
You will not receive support in this forum while there are banned repo's installed on your device:
-
-
Is the router acting as an Ethernet switch between two devices in the same network, or is it actually routing between the HTPC in one network and a remote location where the server is located? (over the leased line).
100-BaseT is fast enough for streaming BR discs.
-
Ethernet or crappy wifi? In a local network there should be no need to fiddle with cache settings, ever.
-
If the bug is unresolved upstream, it remains unresolved downstream.
-
Performance under Windows has fcuk all to do with performance under Linux. One of these days Intel will release a reliable Linux WIFI driver and thousands of NUC users will rejoice.
-
Use the "date" command: UNIX Date Command Examples – nixCraft
If you want it to persist over reboots invest in one of the inexpensive mods that adds an RTC chip and battery to the Pi.
-
It is not possible to edit or add files to /usr/bin as that path is inside a read-only squashfs file (that expands into a virtual filesystem on boot). Any changes there need to be made a image compile time; with a small number of exceptions where we support boot-time override of embedded files with content in /storage/.config/
What exact file are you attempting to modify?
-
using a corrupted image? .. is the obvious explanation
-
If it works you'll see duplicate wireless network names in the connections list; one will be from the wlan0 interface and another will be from the wlan1 interface. In the long run (once you have a working USB device) it might make sense to blacklist the driver for the internal wireless card to prevent it loading at boot-time, then you will only see one set of networks.