Posts by louis_nichols

Quote from louis_nichols

I tried following these steps and am having a bit of trouble.

Unfortunately, I don't have enough free space on my local drive to do this. So I am trying off an external drive, but it fails with an error.

To start with, when I follow these instructions to the letter, the build works, but fails when it fills the available space. I stayed with it for some 10 minutes, then left it to run overnight and when I came back, the error message was pretty explicit with "drive full", well into the build.

Now, I am trying off an external HDD connected to USB and it fails after about 1 minute with this:

Code

make  install-exec-hook
make[4]: Entering directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu/src'
rm /home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/toolchain/bin/sem || true
rm: cannot remove '/home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/toolchain/bin/sem': No such file or directory
ln -s parallel /home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/toolchain/bin/sem
make[4]: Leaving directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu/src'
make[3]: Leaving directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu/src'
make[2]: Leaving directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu/src'
make[2]: Entering directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu'
make[3]: Entering directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu'
make[2]: Leaving directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu'
make[1]: Leaving directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu'
Packages loaded : 857
Build trigger(s): 1 [image]
Package steps   : 251

config/functions: line 1257: /home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/.threads/locks/ccache:host.build: Invalid argument
FAILURE: scripts/build ccache:host has failed!
[001/251] [FAIL] build   ccache:host

The following logs for this failure are available:
  stdout: /home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/.threads/logs/3/stdout
  stderr: /home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/.threads/logs/3/stderr

parallel: This job failed:
package_worker 3 3 251 'build ccache:host'
Parallel build failure - see log for details. Time of failure: Sun Dec 19 19:42:01 CET 2021
make: *** [Makefile:12: image] Error 1

Display More

stdout and stderr don't show any additional info:

stdout:

Code

# cat build.LibreELEC-RPi2.arm-9.2-devel/.threads/logs/3/stdout
config/functions: line 1257: /home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/.threads/locks/ccache:host.build: Invalid argument
FAILURE: scripts/build ccache:host has failed!

stderr

Code

# cat build.LibreELEC-RPi2.arm-9.2-devel/.threads/logs/3/stderr 
[001/251] [FAIL] build   ccache:host

The following logs for this failure are available:
  stdout: /home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/.threads/logs/3/stdout
  stderr: /home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/.threads/logs/3/stderr

I tried to trick it by using ln -s from the external drive to ~/LibreELEC.tv/, but the result is the same.

In fact, these outputs are from such an attempt with ln -s. But, without it, the result was exactly the same.

After having these failures twice, I checked again that the build works out of a native folder and it does. So it really is something about using the external drive.

Any suggestions?

Display More

Nevermind. It occurred to me that it was all very silly and the only difference between "local" folders and the external drive was they way they were mounted. The external drive was mounted through gnome vfs. So I remounted the external drive the old school way with sudo mount and now the build is churning.

Thank you for these instructions!

Later edit: some 7 or 8 hours later, the build was succesful. It did have a couple of hiccups and I had to restart the build 3 times. The first time I deleted .ccccache, but for the next ones I didn't bother. And it got to the end. It was all quite exciting. And then I realized I compiled for the wrong platform. :))) OK, well, one more try...

In a ny case, this is probably the most complex build I've made since Compiz first came out.

Quote from smp

You can add the rtl88x2bu driver to the LE build system and compile an image.

e.g.:

Code

cd ~
git clone https://github.com/LibreELEC/LibreELEC.tv
cd LibreELEC.tv/packages/linux-drivers
mkdir RTL88x2BU
cd RTL88x2BU
touch package.mk

add this to package.mk:

Code

PKG_NAME="RTL88x2BU"
PKG_VERSION="439c7dbd9e43acd91d5704a50b68647716c52505"
PKG_LICENSE="GPL"
PKG_SITE="https://github.com/cilynx/rtl88x2bu"
PKG_URL="https://github.com/cilynx/rtl88x2bu/archive/$PKG_VERSION.tar.gz"
PKG_DEPENDS_TARGET="toolchain linux"
PKG_NEED_UNPACK="$LINUX_DEPENDS"
PKG_LONGDESC="Realtek RTL88x2BU Linux driver"
PKG_IS_KERNEL_PKG="yes"

pre_make_target() {
  unset LDFLAGS
}

make_target() {
  make V=1 \
       ARCH=$TARGET_KERNEL_ARCH \
       KSRC=$(kernel_path) \
       CROSS_COMPILE=$TARGET_KERNEL_PREFIX \
       CONFIG_POWER_SAVING=n
}

makeinstall_target() {
  mkdir -p $INSTALL/$(get_full_module_dir)/$PKG_NAME
    cp *.ko $INSTALL/$(get_full_module_dir)/$PKG_NAME
}

Display More

Edit distributions/LibreELEC/options file, add RTL88x2BU to "ADDITIONAL_DRIVERS=" :

ADDITIONAL_DRIVERS="RTL8192CU RTL8192DU RTL8192EU RTL8188EU RTL8812AU RTL88x2BU"

Build an image:

cd ~/LibreELEC.tv

PROJECT=RPi ARCH=arm DEVICE=RPi2 make image

Display More

I tried following these steps and am having a bit of trouble.

Unfortunately, I don't have enough free space on my local drive to do this. So I am trying off an external drive, but it fails with an error.

To start with, when I follow these instructions to the letter, the build works, but fails when it fills the available space. I stayed with it for some 10 minutes, then left it to run overnight and when I came back, the error message was pretty explicit with "drive full", well into the build.

Now, I am trying off an external HDD connected to USB and it fails after about 1 minute with this:

make  install-exec-hook
make[4]: Entering directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu/src'
rm /home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/toolchain/bin/sem || true
rm: cannot remove '/home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/toolchain/bin/sem': No such file or directory
ln -s parallel /home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/toolchain/bin/sem
make[4]: Leaving directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu/src'
make[3]: Leaving directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu/src'
make[2]: Leaving directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu/src'
make[2]: Entering directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu'
make[3]: Entering directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu'
make[2]: Leaving directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu'
make[1]: Leaving directory '/media/louisnichols/Seagate_Expansion_Drive/build.LibreELEC-RPi2.arm-9.2-devel/parallel-20190722/.x86_64-linux-gnu'
Packages loaded : 857
Build trigger(s): 1 [image]
Package steps   : 251

config/functions: line 1257: /home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/.threads/locks/ccache:host.build: Invalid argument
FAILURE: scripts/build ccache:host has failed!
[001/251] [FAIL] build   ccache:host

The following logs for this failure are available:
  stdout: /home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/.threads/logs/3/stdout
  stderr: /home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/.threads/logs/3/stderr

parallel: This job failed:
package_worker 3 3 251 'build ccache:host'
Parallel build failure - see log for details. Time of failure: Sun Dec 19 19:42:01 CET 2021
make: *** [Makefile:12: image] Error 1

stdout and stderr don't show any additional info:

stdout:

# cat build.LibreELEC-RPi2.arm-9.2-devel/.threads/logs/3/stdout
config/functions: line 1257: /home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/.threads/locks/ccache:host.build: Invalid argument
FAILURE: scripts/build ccache:host has failed!

stderr

# cat build.LibreELEC-RPi2.arm-9.2-devel/.threads/logs/3/stderr 
[001/251] [FAIL] build   ccache:host

The following logs for this failure are available:
  stdout: /home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/.threads/logs/3/stdout
  stderr: /home/louisnichols/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2-devel/.threads/logs/3/stderr

I tried to trick it by using ln -s from the external drive to ~/LibreELEC.tv/, but the result is the same.

In fact, these outputs are from such an attempt with ln -s. But, without it, the result was exactly the same.

After having these failures twice, I checked again that the build works out of a native folder and it does. So it really is something about using the external drive.

Any suggestions?

I started seeing this exact error yesterday. Anyone else seeing it?

LE: Nevermind. Fixed now. My automated updates had stopped working for some reason.

Yes, that worked. I got an email to reset the password.

Thank you!

It's the same, without the underscore: louisnichols.

I can't imagine why it would be blocked. I'm not sure I ever even posted with it. Do they expire?

Hi!

I have been trying to recover a password I forgot for my initial account on this forum, but there is an issue.

After I enter my username (or email attached to that account - the behavior is the same with both), I see the message from Picture 1. After a few seconds, the one from Picture 2.

Please look into it.

Picture 1:

Picture 2:

CvH No, I didn't mean to insinuate that it was trivial. Just that it is sad in a personal sense, because even Raspbian would not be an option, if worse comes to worst. I was just trying to make a little joke, perhaps not in the best taste. I appreciate the work everyone is doing on both sides.

HiassofT Yes, I noticed that too, so fingers crossed that it leads to a solution. Still, it sounds like it will take a while.

JohnWayne111 Hopefully not so long, but let's see.

In the meantime, just to perhaps bring this thread to a conclusion, I can report that, indeed, flashing 9.2.8 and replacing start.elf and fixup.dat from my old working image solved the problem. I must have changed them and forgotten (and that would have been 8 months ago, so it's strange that I have absolutely no recollection of it - I must be getting seriously old). So it looks that those of us who want to use Hyperion are for the moment stuck at 9.2.x, with this workaround in the case of Rpi400.

For me personally, that is not actually an issue, as for the moment I don't have plans for the good stuff from LE10. And for WiFi and Bluetooth I've been using dongles I had laying around and got used to it. And Hyperion is honestly too beautiful to give up. Especially after putting time and money into making it (not a lot, but still).

Let's just hope Widevine doesn't completely break that before we get a solution for LE10. I'm not sure how long the LE team will be willing to support the 9.2.x branch with such fixes.

Thank you all for your support!

CvH that just makes it sadder, doesn't it?

Understood, thank you. I might just do that.

I tried the upgrade to LE10beta, but the showstopper turns out to be Hyperion NG not working (I think it was the same last time I tried the upgrade).

I found this thread where you explain that it basically doesn't look good. I also found on their forums where they say LE must implement the grabber. Looks like a stalemate. Bummer about that one.

Thanks for the hints.

I had tried an update to LE10 alpha or beta a few months ago, but had trouble getting all my addons to work, so I reverted (I think that is why I had a 9.2.6 image laying around).

I have made some changes a while ago, trying to get WiFi and BT to work, but I didn't manage and defaulted to USB dongles. I also have Hyperion running off this RPi 400, but I don't think I made any firmware changes for that - just enabled SPI in the config file (same as on RPi4) - it was some time ago and I don't completely remember.

In any case, in all such instances, the worst I have ever had was that the hardware was not working. It has never happened to me that the RPi400 would not boot.

So what you're saying is that I might try to overwrite the contents of the folder 'firmware' from my old image to the current and I might get lucky?

Hi all!

I'm having this very weird problem. I have searched the forums and couldn't find a solution.

I use LibreELEC on a Raspberry Pi 400, booting off a SanDisk SD card, 64GB.

In short, when I (try to) upgrade from 9.2.6 to 9.2.7 or 9.2.8 (I tried both, with the same results), it does not boot anymore. I see the splash screen and then the RPi shuts down. The power LED turns off and I can hear the external HDD power off when this happens. So it's really powered off, not a display/cable issue or anything.

All this happens very early in the boot process and the syslog does not contain anything about it.

Information that I have gathered:

• 9.2.6 and previous versions have been working great for several months now (I forgot when I got the RPi 400). Before this, I had been using incremental updates of LE from the same SD card for years on an RPi4 and an RPi3.
• The exact same SD card, with 9.2.7, booted fine on an RPi4. I haven't tried this with 9.2.8, but I think it's safe to assume it would be the same.
• I have tried several power supplies, with the same result: the RPi400 official one, a laptop supply from a Lenovo ThinkPad of 2A@5V and a smartphone charger of 2A@5V
• This is really interesting
  • I tried to downgrade from 9.2.7 to 9.2.6 using a "raw" (downloaded) image and after, the issue was still there with 9.2.6. It wouldn't boot.
  • However, after I restored a previous image of 9.2.6, which I had backed up a few months ago (just the system partition), it worked. It booted fine.
  • Again, I haven't tried the same with 9.2.8, but I think the result would be similar.

In fact, after the bad experience I had with the upgrade 9.2.6 -> 9.2.7, I wanted to stay on 9.2.6, but the lack of support for widevine became an issue. I tried to upgrade to 9.2.8 in the hopes that this might contain the fix for my issue, but no joy.

In any case, I would exclude the SD card or power supply as possible causes, which are the only suspects I could find on the forums.

Any suggestion will be appreciated.