In this case, the NTFS device does NOT report error with Linux.
Yep, I think that's the issue here. It's not LE-specific.
Posts by Da Flex
-
-
It came that way out of the box, unfortunately.
Come on, from what I've seen in your posts, you're not the out-of-the-box guy.
-
NTFS is obviously supported, because you can mount it. Things get nasty when an NTFS device has errors on Linux.
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Wolkenstuermer Please edit your post, and translate into English. We don't accept other languages.
-
Code
2024-05-01 11:52:09.857 T:1005 info <general>: Disabled debug logging due to GUI setting. Level 0.Another log at log level 2 please.
Code2024-05-01 11:52:09.515 T:1005 info <general>: Local hostname: rpi4Maybe you should start with an installation from scratch.
-
Thx! Big milestone for all OPi3 LTS users!
-
Yep, docsuess84 does weird IT things, so he probably just needed the web browser from Generic-legacy.
-
Generic-legacy seems to work on Chromebox:
-
Oh, one thing I was curious about is if there can be spaces when you’re mounting a drive. Should the share be entered as “My Book” or would it be “My_Book” ?
Special characters in Samba filenamesWhen serving files containing special characters such as "()?:" in the filename through Samba, the names get transformed into an unrecognizable format. For…serverfault.comSo space sign is legit.
-
A modern web browser is a media player on its own. So it goes to a wrong direction on LE. If one needs Kodi and a web browser, install a regular OS like Ubuntu or Raspberry Pi OS.
-
Skin developers are responsible for compatibility. Ask at Kodi forum, where those devs are.
-
-
My NAS is permanently mounted on Ubuntu. I've used this guide:
https://ubuntu.com/server/docs/how-to-mount-cifs-shares-permanently
-
When I connect it to the AV receiver however it can't boot further than to the LibreELEC splash-screen. I didn't set LibreELEC up to only output 4k or something. LibreELEC worked fine in the otherwise same setup running from the Raspberry.
So your current setup is NUC -> AVR -> Projector, and former setup RPi -> AVR -> Projector worked.
We had cases where an HDMI firmware update made things work. Make sure it's up-to-date.
I decided to upgrade the hardware from a Raspberry Pi 2 B to an Intel NUC 13.
The NUC provides a higher resolution by default, compared to RPi. There is a chance that your AVR can't handle such a resolution, and video pass-through doesn't work anymore. So test another setup:
NUC (first HDMI port) -> Projector
NUC (second HDMI port) -> AVR
-
SMB is a file service, which works on top of a block-based file system. So in theory the underlying file system doesn't matter. However, I recently switched from exFAT to Ext4 on my NAS, since I had trouble to access files after a while. I guess Ext4 is easier to scan for errors under Linux, and such scans are triggered periodically. I suggest Ext4 for Linux.
SMB default port numbers are 139 or 445, so that's OK.
-
With projector and AVR connected, run getedid create from SSH, and reboot. If the issue persists...
- create an advancedsettings.xml with log level 1 activated (use nano editor on SSH)
- reboot
- run pastekodi from SSH, and post the resulting URL
-
Are there any plans in the future to replace X11 with a more up to date window system?
No.
