Posts by person0nInternet

Problem solved, btw - much appreciated.

Well I suppose actually reading the release notes instead of just skimming them would be a good move next time.

Any reason that the installer didn't simply rename samba.conf ---> samba.conf.old, and then just replace samba.conf with the updated file?

Sure, it would have caused a different group of people to have issues, but those people would probably be the ones running old crappy hardware/software that can't deal with SMB 2/3 anyway. Just kidding... (kinda).

Hi everyone,

I just upgraded from LibreELEC 8.0.2 to 8.1.1. I initiated the update directly through the LibreELEC settings menu.

For probably 6 months, I haven't had to touch anything - LibreELEC = most reliable SMB connections I've ever encountered. My Mac is configured to mount two specific folders on the "LIBREELEC" share.

"LIBREELEC," has always been displayed in the sidebar. Immediately after the upgrade, that changed. Only the NetBIOS alias "%H" is displayed now. Please help - I've been spinning my wheels for about 4 hours now - no exaggeration...

Yeah, I'll give that a try. Thanks.
[hr]

Quote from Jaaxx

This is your second thread with a title taking passive-aggressive swings at the community for what you perceive is a lack of timely responses to your questions (Other time here.)

I think you need to calm down a bit and exercise some patience. We've all been in the position of being frustrated with little nagging problems before (users and devs.) The fact is most of the time no one has an answer OR the one person on the planet who does hasn't come across your post yet OR the answer is complicated enough that the person needs to carve out a portion of their day to help you out.

No one is intentionally ignoring you and your threads/posts seem to imply that.

I wanted to add - as you know, I essentially explained earlier that I get nobody is intentionally ignoring my posts.

But scenarios involving buried posts of course aren't unheard of. I found an interesting example of a cool and simple function that could be useful for any forum:

I understand your point as well.

With regard to the older thread, it had been (I believe) 3 days since my first post, and I was concerned that it was simply buried. (Also, there was a note on the topic in the FAQ instructing to reference the wiki, which WAS a dead link.)

Also, it was stated by Klojum that I was not exercising autodidacticism, yet I'm starting to think that you're right - I consider myself a noob, while in fact, the questions that I ask would involve a very limited number of people who actually know the answer to my questions because I HAVE researched like crazy before posting.

I apologize for the tone of the posts involved - I always use a to-do list app, and when I've moved the same to-do item to the next day 6 times, and invested 30 hours into finding an answer that is likely a command or checkbox away, I simply get frustrated.

I just didn't realize that my questions were out of the grasp of most as you stated.

Klojum,

I completely get what you're saying, and I understand why I may have come off that way to you - however - you've got me wrong, and if you notice, I was quite polite in the post, asking for assistance with posting technique. I've experienced this trend whereby I simply don't receive responses to politely asked questions yet I see others post after me and receive a response before me. I literally want to know - am I giving too much detail and scaring people away? I'll often post and get 200 views and zero responses.

I also want to mention - my first post on the linked thread was NINE days ago. Chewitt made some great suggestions - things that, by the way, I didn't know how to do, but instead of asking, I figured out myself, as you can see from the screenshots on the thread.

I have posted the question on the official Kodi forum, the LinuxQuestions (LQ) forum, the Shield TV forum and before ANY post I make, I try to learn more about what I'm doing and see if I can fix something on my own.

Am I ready to solve the problem and be done with it? Yes! Have I actually been working on fixing this for about 20 days? Yes!

Please don't suggest that I'm acting like a child when I ask for guidance on how to improve my posts.

Hi everyone!

As stated in the subject, I'm having trouble getting answers sometimes - I realize many, including myself, have so much going on, that they're often on here to ask questions and not answer them, but I'm really looking for assistance on a particular matter after teaching myself quite a bit and still managing to fail. What do you guys try when you don't receive a response regarding something you're really trying to resolve.

I may see better results with more concise questions; anyway - at this point I'm referring to one particular thread: thread-7147.html

(Shout-out to Chewitt for your earlier assistance - I know that you have me headed at least in the right direction.)

Alex

It says Active, yet in the line above it says disabled AND vendor preset disabled. (I switched it on in LibreELEC settings, so I understand why it says vendor preset disabled...but what about the other disabled remark?)

Anyone out there?

Quote from chewitt

Creating /storage/.config/samba.conf will not cause a boot failure. That code is relatively unchanged since OE 1.0 days and we would see thousands of forum posts if it were true. The boot message says it cannot find the SYSTEM file in the boot partition (first partition of two used by LE) which is normally because some other process messed with the bootloader config so the partition is wrongly identified or the file is not present or corrupted (cannot uncompress).

I've also tested this out now that I'm not on vacation and (sorry) it doesn't work quite as expected. It's not blocking creation of a directory; samba docs only talk about blocking files so it might be that explicit. Also, blocking a Thumbs.db file that I copy/paste prompts macOS/finder to ask for credentials instead of the copy operation silently failing. It may be easier to let Android do its thing uninterrupted and just run a regular find/delete command via cron instead.

You can ignore my last long babbling post; I overcame a couple hurdles, but got nowhere. I finally got the OS to allow the presence of a manually edited samba.conf file with the two veto files lines added to each share.

AND - I have a cron job running every 10 minutes that is supposed to delete the Android folders. (It works manually, but not via cron, as you can see in the screenshot below. Notice that the find command returns no results after I manually execute the remove command.) But even with BOTH of these in place, the Android folders are still appearing.

Quote from chewitt

Creating /storage/.config/samba.conf will not cause a boot failure. That code is relatively unchanged since OE 1.0 days and we would see thousands of forum posts if it were true. The boot message says it cannot find the SYSTEM file in the boot partition (first partition of two used by LE) which is normally because some other process messed with the bootloader config so the partition is wrongly identified or the file is not present or corrupted (cannot uncompress).

I've also tested this out now that I'm not on vacation and (sorry) it doesn't work quite as expected. It's not blocking creation of a directory; samba docs only talk about blocking files so it might be that explicit. Also, blocking a Thumbs.db file that I copy/paste prompts macOS/finder to ask for credentials instead of the copy operation silently failing. It may be easier to let Android do its thing uninterrupted and just run a regular find/delete command via cron instead.

NB: In MacOS you can prevent write of _ and . files: Mac OS X v10.4 and later: How to prevent .DS_Store file creation over network connections - Apple Support so no need to do that with Samba

Thanks for your help Chewitt!

I included the steps I followed from fellow board member Klojum below for my multi-boot setup. I'm new to Linux but a lot of the CLI stuff is of course quite similar to using Terminal in macOS.

I agree that it's not the .conf file, though when I reverted to the embedded .conf (leaving only the sample) bootup went back to normal. I think it's some trouble I had post-installation when I was doing using "Grub Customizer" - it nuked my grub.cfg. I ended up using a repair tool that 95% fixed things. I think it was this: boot-repair-disk download | SourceForge.net. I ended up with two Windows references on my Grub2 screen though. Unsure why.

---START KLOJUM TUTORIAL---
(Mind you, this tutorial is all with no guarantee whatsoever if you yourself fcuk up.)
Since you are using Ubuntu and talk about extended partitions, you should also be comfortable using bootable tools like Gparted Live. If so, create 2 EXT4 partitions : one 512MB system partition, the another one using up the rest of the availabe free space for LibreELEC's storage partition. Whether those are primary or extended is up to you. All primary is possible when you have no seperate partitions for Linux's home, boot, or its other options. So if you have currently only a single EXT4 partition for Ubuntu along with a SWAP partition, it's possible. Otherwise, create the 2 EXT4 partitions in the extended partition area. Also, give the new partitions labels, to identify them more easily.

Reboot the machine, Ubuntu should start.
Go into a terminal. Type sudo blkid
You will get a list of drives/partitions, pick out your two new partitions, and remember their device numbers. You will need them later on.
Now you need to add the LibreELEC menu item to the GRUB2 boot system.
In the terminal, type sudo nano /etc/grub.d/40_custom .
Paste in the following text:
menuentry "LibreELEC 8.0 Krypton" {
set root=(hd0,6)
linux /KERNEL boot=/dev/sda6 disk=/dev/sda7 quiet
}

Replace all three drive numbers (in my case, twice 6 & 7) with the ones you got for your respective system and storage partitions from the blkid command.
CTRL-O for storing the file changes
CTRL-X for leaving the nano editor

Update the GRUB2 menus: sudo update-grub2 .
---END KLOJUM TUTORIAL---

Everything worked great except for the audio, but I'd been warned. After all the fuss with Grub Customizer + the repair tool, I knew there were probably some deep-seated issues, but I figured I'd leave it alone after LibreELEC finally started producing multi-channel audio with new Intel HDMI firmware. That whole situation is probably why I'm having issues now.

I attached /boot/grub/grub.cfg as grub.txt if anyone cares to take a look at it and see what the heck happened between Grub Customizer and the repair tool.

I have no experience with cron jobs unfortunately. After all the time I've spent on this I'm just drained. I'll take a look but I'm worried that I'll destroy something else in the process at this point.

I'll execute that command in macOS - I noticed it in your original post as well. Btw, when I read the veto files instructions, I thought I saw it say files or directories. Hmm.

I'd love some help here from any of you fine folks, pretty please! Simply tell me what you need me to provide.

I'm also running into errors on bootup. (see TEXT below - screenshot is just a directory listing for the heck of it)

I do have a Win10/Ubuntu/LibreELEC setup, but I followed very explicit instructions for a multi-boot to set it up correctly from one of the LibreELEC board regulars, and LibreELEC had been working fine since. (Until this attempt to stop my Nvidia Shield TV from its Android folder generation spree...)

I would not normally have 3 operating systems, but my 2017 NUC had a lot of audio issues that Intel needed to sort out before I could get Kodi to properly output multichannel PCM to my older receiver - this has been a multi-month process.

Now that I've created the samba.conf from samba.conf.sample, all of this is happening. Does anyone see any any syntax errors in my editing of the samba.conf file above? I believe I followed Chewitt's instructions correctly.

*** Error in mount_storage: mount_common: Could not mount /dev/sda8 ***

LibreELEC is actually (for sure) /dev/sda7, and it said sda7 on the 1st reboot, but when I tried to boot again the error now says sda8, and I'm worried I may be in some deep doo doo.

----BEGIN ABNORMAL BOOTUP MESSAGES----
### Starting debugging shell... type exit to quit ###
sh: can't access tty; job control turned off
# exit
cp: can't stat '/flash/SYSTEM' : No such file or directory
*** Error in prepare_sysroot: mount_common: Could not mount /dev/SYSTEM ***
### Starting debugging shell... type exit to quit ###
sh: can't access tty; job control turned off
# _<---cursor
----END ABNORMAL BOOTUP MESSAGES----

Edits made, followed by what I see after a reboot. I went ahead and included some of the annoying macOS items as well for obvious reasons.

Hi folks,

I have LibreELEC 8.0.1 running flawlessly on my recently acquired Intel NUC. I have a 4TB HDD attached to the NUC via USB 3.0. The consistency of LibreELEC's network reliability is stunning compared to Windows or Mac, and I love it.

I just need to make a small change and I found a discussion online somewhere, but it really didn't elaborate enough.

My Nvidia Shield TV, in another room, regularly accesses the LibreELEC share I've created for my media. The problem is - the Android OS marks its territory with the creation of an "Android" folder in EVERY directory and subdirectory that I navigate to.

I consistently check my media manager software counts, Kodi counts, and item counts in my shares, and I'd like them to be right without having to subtract 1 for "Android" in each shared folder.

Is it possible to create a rule in LibreELEC as specific as *Remote Android SMB User cannot create folders.* (something to that effect) Or do I need to fix this another way?

Thanks in advance!

Quote from Jeremia

Well, I assume I can't help you directly on this, but I'm at least also a 2017 NUC user (NUC7I3BNK). In my case HD audio format passthrough is also not working, but DTS and AC3 passthrough is. In addition I'm pretty sure PCM also does it's job for HD audio formats. I selected 7.1 channels in Kodi, but I only have a 5.0 setup at the moment. I can check again if PCM works for more than two channels when I'm back home.

Actually, thank you - you made me realize that I should try turning on passthrough but disabling the DTS-HD and TrueHD switches; most devices (my Nvidia Shield for example) will pass the core of a DTS-HD track (regular DTS) if it has trouble passing the HD version, but maybe LibreELEC or the NUC can't do that.

I think I already tried selecting 7.1 (even though I only have a 5.1 system) and that didn't work, but I'll do some more testing.

I'm fine with regular DTS or AC3 for the time being, IF there is a solution in sight. Moving forward, though, I have to figure out if the Linux community (and/or LibreELEC) is going to figure out a way to make HD audio work. These sound formats (DTS-HD Master Audio and Dolby TrueHD) are a decade old and shouldn't be difficult to handle, but it's far beyond my own capabilities to create the solution myself. Intel is getting ready to patch their NUC Windows audio driver for the NUC to allow current-generation formats DTS:X and Dolby Atmos (which are already almost 5 years old in truth) within a month!

LibreELEC is absolutely fantastic in so many ways (especially file sharing), but regardless of whether it's a driver issue or a coding issue, I have to focus my efforts on a platform that works. Right now, the only environment that has absolutely zero issue taking full advantage of the NUC's audio capabilities is Kodi for Windows. I highly doubt the Linux community is going to be ready for DTS:X and Dolby Atmos within 30 days - but I am!

I promise I'm not trying to be a jerk about this, but would it help to contact Kodi directly regarding this issue?

I'm really trying to solve a problem here, and I don't know if they can help me or not, but (based on zero answers to the specific question) nobody seems to know why LibreELEC will only output 2 channel audio from the Intel NUC.

I'm wondering if I'm not explaining it well enough?

The ALSA output identifies my receiver by brand/model.

Passthrough: No Audio (Known Issue)

Passthrough Disabled: 2 channels (PCM) only - I was mistaken earlier when I said there were no vocals - the setting on my AVR was processing the audio in a special way.

The bottom line: I cannot get LibreELEC to put out more than stereo PCM.

Please, someone point me in the right direction! Thanks!

Yes that's correct - which is why I mentioned that I am fine with allowing Kodi to output PCM. (Long-term I prefer the visual confirmation of audio format on my receiver.)

The problem is that, with Kodi set to 5.1 or 7.1 channels, my AVR reports receiving only 2 channels over HDMI.

Reboot to Windows? Full 7.1 out.

But again, there is a problem with the audio driver on the NUC for Linux at the moment, so I'm just trying to find out why LibreELEC is seemingly mishandling PCM output.

Hello,

I understand that there is currently no support for audio passthrough on the newest (possibly older as well) Intel NUC models.

As others have suggested, I disabled passthrough, expecting to let Kodi decode the audio and pass it to my receiver via PCM.

Even though I have selected 5.1 channels under System Settings ----> Audio, my receiver reports that it is receiving PCM 2.0 audio. I hear only ambient sound from these two channels, making LibreELEC in its current form ENTIRELY unusable.

All of my videos have only one audio track: either DTS-HD Master Audio, or Dolby TrueHD, so I don't believe optical is an option, unless PCM makes it an option.

I'm running LibreELEC 8.0.

I just tried to export a log but it's giving me an issue.

Any idea? I really wanted LibreELEC to be the primary operating system on my NUC.

PS Windows handles the audio fine but is of course much less friendly as a HTPC OS.

Found "Boot-Repair" tool and fixed it, but now Ubuntu is default again. It's tolerable, but I wish I could make LibreELEC default without destroying something.