If there is no WiFi network you can run an Ethernet cable between the two devices and assign them different static IPs in the same subnet, then configure two sources on each device; one for the local USB drive and one for the remote (SMB) share on the other device. If there's an objection to using cables due to different rooms etc. you really need to add a WiFi router (no need for internet, but you need a networking method to connect the devices).
Posts by chewitt
-
-
Then read https://kodi.wiki/view/NFO_files .. which ties in with the article on scrapers (scraping .nfo files).
-
I'll also have a go at switching the powerline adapter to a different socket.
^ so the RPi4 is connected to a powerline adapter? .. If so the interface/port speed might be Gigabit but I guarantee actual throughput on the link is nowhere near Gigabit. All you've done is prove that your powerline connection is slow. Connect the RPi4 and PC directly to a proper Gigabit switch and measure again.
-
Their emby add-on is the same as ours, because it is ours. CE is basically a fork of our codebase (including add-ons) with a few Amlogic specific extras included.
-
Apart from the lack of tuners and 1GB it's much the same as WP2 (another p200 clone). I'll share some docs with you.
-
The only real way to know is making a test install on a spare USB key and then (if there's an issue) share the boot log and "lsusb" output so we can check the PCI card IDs against upstream kernel drivers. Most PCI audio cards use generic drivers and should just work. Occasionally we need to enable the driver in kernel config. Occasionally we need to patch a new card ID.
-
There's a manual workaround to update the certificates that are used (some of the embedded ones have expired) but I'd suggest you look at dtech LE 9.2.8 images which should avoid the need for that (and are newer).
-
wedok I think the thread you started was deleted (as requested). I haven't had much feedback on the Minix U1 device-tree (why it's not been sent upstream yet) so I'd be interested in seeing some current logs. I've also added some experimental support for the headphone output on the box which I need to get tested.
Please put this on the box: https://chewitt.libreelec.tv/testing/LibreE…arm-10.85.0.tar
Run "dmesg | paste" and share the URL so I can see the boot log. The headphone output should just work if you connect something?
-
Beelink King Pro does not open. The screen remains in the libreelec logo. He was working in July versions.
Fixed with https://github.com/LibreELEC/LibreELEC.tv/pull/6790 two days ago
-
"dmesg | paste" and share the URL .. if there is no hardware found, the issue is with probably with kernel/drivers not userspace apps.
-
I'm not sure what the issue is, but (unrelated) I did notice that you've set the 'desktop' resolution to 4K which probably isn't going to give you the best GUI experience. Using 1080p and the whitelist to switch to 4K modes only when needed will be faster/smoother/better.
-
Hmm.. the Tbee dts has the device-tree plumbing in-place. Have you selected the S/PDIF output in Kodi settings? You shouldn't need to make any changes to alsa settings as the routing for S/PDIF should be set by default.
-
Optical outputs should work as long as the device-tree file has the necessary content. What box? What device-tree are you using?
-
Have a read of https://kodi.wiki/view/Scrapers and learn how to use scrapers.
-
Mac hardware isn't particularly well supported under Linux despite the general similarity to PC hardware. You're more likely to have success with a bleeding edge image rather than an old one. Perhaps force SSH on with "ssh" in boot params so you can connect and look for issues.
-
See https://test.libreelec.tv/11.0/Amlogic/odroid-c2/ for current LE11 test images. The loose plan is to resume support for older GXBB, GXL and GXM hardware with LE11.
-
Video driver is broken for S912 (Yoka KB2 3/32, both q200 and q201 dtbs): video glitches, decoding errors and freezing.
UI deadlocks randomly too.
In terms of technical value, your FEEDBACK is a bit like "my car drives funny, it has rattles and squeaks"
-
LE is multi-user in the sense that there are some internal accounts/groups for OS services, but really everything intentionally runs as root and trying to change that based on an understanding of how a conventional distro works (hint: we are not a conventional distro) falls under the "pushing water uphill" category of efforts. I'd advise settling for root login with SSH key auth, which is as simple as pushing your private keys to the required places under /storage/.ssh/ and then enabling "disable password authentication" in LE settings.
