Posts by milhouse

I've uploaded a NOOBS LibreELEC 9.0/Kodi 18a1 test build for RPi2, here: Index of /noobs/LibreELEC_RPi2/

This includes the shortened partition labels and renamed tar files (does not include the old tar files) - basically everything in NOOBS: shorten partition labels, add $DEVICE support by MilhouseVH · Pull Request #2243 · LibreELEC/LibreELEC.tv · GitHub.

If anyone can test this it would be appreciated.

I've got a branch for libreelec-8.2 with essentially the same changes, Comparing LibreELEC:libreelec-8.2...MilhouseVH:le82_fix_noobs · LibreELEC/LibreELEC.tv · GitHub - this branch doesn't require all the extra $DEVICE changes so it's basically just the partition and tar filename changes.

OK many thanks. Now, the PR is in master which is for LibreELEC 9.0. I'll work with chewitt and see what we can do with libreelec-8.2 - hopefully have something for you to test soon.

Well I'm not a NOOBS expert, so I'm having to take direction from this thread at the moment. Adding the tarball filenames into the partitions.json sounds better than relying on the label names which are simply too short to be of much use for anything.

Quote from procount

(I can't remember if NOOBS works this way too and if it works with the recent download function)

Is there any way either of you could confirm that adding the tarball filename into partitions.json will work with NOOBS? This wouldn't change the System/Storage partition labels, but would avoid the external changes resulting from a tarball filename change.

If you have any comments about the PR you can make them in this thread.

Is the System 0, System1 issue something a user is ever made aware of, or is it something only someone such as yourself gets to see (and is a mostly cosmetic issue)?

I'm thinking we should cut our loses and stick with a simple no-prefix name for partitions as whatever name we choose we run the risk of a partition name clash, and if we did add a prefix we then need to implement rules for what can be used as a prefix (ie max 3-4 chars, to avoid busting the FAT limit again, and a prefix that doesn't conflict with an existing prefix - and I've no idea how to prevent that!)

Is it possible to install both RPi1 and RPi2 LibreELEC images on the same NOOBS/PINN SD card, say if a user transports a single SD card between RPi1 and RPi2 devices? If so, even with a prefix, we'd have another unavoidable partition name clash.

The only remaining solution would be to contrive a unique partition name, eg. lerpi2sys, but then almost no user will understand this (assuming they even need to) and it becomes almost as meaningless as System0.

So, as long as NOOBS/PINN handles any partition name clash gracefully, then I hope that using the simple, without prefix, partition name as per the PR will suffice. It might not be perfect, but it should work... right?

procount would you mind reviewing NOOBS: shorten partition labels, add $DEVICE support by MilhouseVH · Pull Request #2243 · LibreELEC/LibreELEC.tv · GitHub ? Thanks.

OK, so looking at os_list_v3.json:

os_list_v3.json

the vast majority of distributions just call their partitions "boot" and "root", and name their tar files accordingly.

Since this will issue will affect Lakka too, I think calling the partitions (and tar files) simply "System" and "Storage" should work. There seems little point trying to use an "LE" prefix (not sure what Lakka would use, and this has to be codified somehow).

Quote from Arutha

Do you know why my old usb sata adapter not work with the new drive?

Because the chipset your old SATA-to-USB adapter is using is incapable of "seeing" the full capacity of the 8TB HDD. As chewitt said, not all SATA Bridges are the same and the cheap ones can cause problems with the latest high capacity HDDs. From what I could make out in your truncated log the kernel thought your 8TB HDD had a capacity of about 1.4TB - then you chopped the rest of the information off after that.

The posted dmesg.txt is unusable as it's truncated at 80 columns.

Arutha upload your dmesg to a pastebin site with "dmesg | pastebinit" then paste the link. And please do the same with "journalctl -a | pastebinit" and paste that link. In both cases make sure the 8TB HDD is connected.

Quote from spinecho

So basically I have to wait until 8.2.1 is released?

I think so. You could try rolling back to an an earlier release, eg. 8.0.2, add the authenticated share, entering your username/password and checking the "Remember" box (which automatically creates passwords.xml), then upgrade again to 8.2.0.1 and I think your shares should continue to work.

Quote from spinecho

Is there a simple guide that includes what I need to do in Windows, LibreELEC and Kodi to achieve sharinf files over Wi-Fi?

There's nothing special you need to do to access a Windows share over WIFi - the steps require are the same as a wired ethernet connection.

Once you've created your Windows share (password protection enabled, added a username/password), Kodi (in LibreELEC) should then automatically prompt you for the username/password when you first try to access the Windows share.

Unfortunately, it's this last step which is currently broken due to a bug in the latest Samba (and fixed in 8.2.1) which doesn't return the correct error code so Kodi reports a bogus/misleading error.

1) "I've enabled samba in LibreElec" means you've enabled the Samba server in LibreELEC which has nothing to do with a client (ie. Kodi) accessing your Windows shares.

2) "browse shows nothing": as explained in the 8.2 announcement, network browsing is no longer supported.

3) "I get an error "File exists".": there's a bug in Samba which is causing this error when accessing an authenticated share, you could be prompted for a username/password but unread you get this bogus error. It will be fixed in LibreELEC 8.2.1 which is undergoing internal testing, so please wait for that release.

Does the filename used for the tarfiles, here:

LibreELEC.tv/image at master · LibreELEC/LibreELEC.tv · GitHub

have to match the partition label names?

I'd be inclined to just use "LEStorage" and "LESystem" as the label names, and leave everything else the same. But I don't think any of us on the team are NOOBS users so we'll have to take guidance on this.

The NOOBS usage of ${PROJECT} is all wrong anyway as it doesn't take ${DEVICE} into account.

Quote from Cryologic

Same problem. Can't acsess to USB-HDD folder media via Windows.

/var/media working.

Rpi3 Libre 8.2.0.1

Same answer to you: read the release notes.

The Extended Info addon seems to be broken for a number of users on different Kodi platforms so this is not a LibreELEC specific issue. It appears that Kodi 17.6 may fix whatever has been broken so you may have to wait for LE 8.2.1 (or go back to whatever version of LE works until 8.2.1 is released).

Quote from kamaron

And the bootable device is for Raspberry 2/3 so it must be a SD card, no USB drive

An SD card in a USB adapter is a "USB drive".

I'll ask the OP the other obvious question: are you sure you have a Raspberry Pi3?

You would not be the first person to think they have a Raspberry Pi3 when in fact the device is a Raspberry Pi1.

Can you confirm what is written on the PCB just below the GPIO header pins - the following image is of a Raspberry Pi3 Model B:

so your PCB should be similar. If not, then your device is not a Raspberry Pi3 but most likely a Raspberry Pi1.

Quote from kamaron

Just to be sure that the SD itself is bootable I downloaded the Raspbian Lite image and again using Startup Disk Creator I got a bootable SD.

Alternatively, boot into Raspbian, and paste the contents of /proc/cpuinfo.

Note that, unlike LibreELEC, the same Raspbian image will boot both RPi1 and RPi2/RPi3.

Also, try a different SD card.

Quote from CanGuy

However, after restarting samba on my Ubuntu machine, I still get "Unable to mount location" "Failed to retrieve share list from server: connection timed out".

Am I missing something?

Read the announcement again. Network browsing (the "share list") is no longer supported now that SMB1 is disabled. You'll need to manually enter the share path in order to establish the mount.

The net-snmpd addon builds without error for me - I'm building tip of LE master (currently: cf3baeb33c1cf91f19a9c8202e4658faa3671c49).

Post your build error, as that would be useful.