Posts by escalade

Quote from bite_your_idols

Yes, I can mount first partition using "sudo udevil mount /dev/loop2p1" and I get this output: Mounted /dev/loop2p1 at /media/root/LAKKA

Also I can mount the second one "sudo udevil mount /dev/loop2p2" and I get this one: Mounted /dev/loop2p2 at /media/root/LAKKA_DISK

What I can not get is how to browse "/media/root/..." since it is a forbidden folder...

Also I don't understand this step (or what path I should I use):

"udevil —mount /media/LIBREELEC/SYSTEM"

UPDATE: another issue I see is what I need is to browse or unzip "SYSTEM" file that is in the fat32 partition... I tried a couple of windows apps to browse linux drives and always get stuck when trying to "enter" SYSTEM file, that is inside 0.fat if I unzip the image. When I try to do the same with the Lakka image for Generic devices I can extract that "SYSTEM" file and browse inside it, the problem is with Raspberry images.... Si I guess if I can mount and browse any of the partitions, maybe that "SYSTEM" file is not available, since Lakka need an installation first boot to expand and get all files as it needs... this is just my guess...

sorry for my noobness

Display More

You can mount the SYSTEM file directly, so in case of Lakka, the mount command to get the root filesystem would be:

# udevil --mount /media/LAKKA/SYSTEM

There is no such thing as a "forbidden folder", and Lakka does not do anything differently from LibreELEC. The SYSTEM file is a filesystem (squashfs) that is mountable by the kernel. It's not expanded on boot or install, it's mounted.

I can't see any issue actually, looks like RetroArch exits cleanly after starting. I have uploaded a build that I think will fix it

Ok, I’ve reverted the kernel to 5.4 branch same as LE master, perhaps the 5.5 branch isn’t quite ready yet. Just uploaded, let me know how it goes.

I synced up the brcmfmac_sdio-firmware-rpi from master and updated to the recently updated 5.5.0 kernel, could someone test the latest RPi4?

You’ll want to mount the first partition, so loop2p1, not loop2.

I assumed you were doing it on an LE system, udevil might be set up differently. Use «losetup -l» to see which loop device you should use. You can use mount manually as well, dont be scared of the manpages 😜

Could you try the one I just uploaded? It should fix the glcore issue by adding gles3, I see that it’s correctly enabled in the build. The wireless issue sounds odd though, does it work in Kodi? The lakka features is enabled in all my builds. I will look into the RA restarting issue.

No problem, wish I could do the same with PCSX2 but it would require adding 32 bit versions of all the many required libs. I will probably add a script that downloads Firefox instead of including it in the image to get it below 512MB again.

Another small utility I added is virtboard, which has to be run from cli at this point. It’s an On-screen keyboard that should be able to pop ip when input is needed but I haven’t looked much into it yet. It’s too large but works for cases where you dont have a kb available.

bite_your_idols

Decompress with gunzip, then «losetup -Pf file.img» then «udevil —mount /dev/loop1p1» to mount the flash partition, then «udevil —mount /media/LIBREELEC/SYSTEM».

Not sure why that happens, unfortunately I don't have an RPi4 or even the time to troubleshoot at the moment. Could you try updating from the previous working build?

The latest image under the «test» folder has integrated Firefox 72.0.2 using official binaries, now running natively on LibreELEC / Wayland. The image has crossed over 512MB though so can only be updated to for those who installed LE with my images which have 1024 MB /flash. Works terrific

Some other improvements are fine tuned fontconfig setup with beautiful sub pixeled rendered DejaVu truetype for all GUI apps i.e. Firefox, RPCS3 and PCSX2. I’ve also added Thai fonts (ttlwg).

mtk1

Sorry, I don't. I could build it but it's not at the top of my list just this moment. Good news is that I've been hacking away at including the few missing libs needed for running Arch Firefox directly on LibreELEC. Bad news is that I've done so, got the browser up and running but it won't actually load up any sites. I should be able to work it out though, time to get a decent Wayland capable browser running natively in this image

RomMon

Np

jaykass

The slang shaders requires either the glcore or vulkan driver. Check that you are using glcore, which should be selected automatically by the retroarch.sh script. With the gl driver only glsl shaders would be visible.

I don't configure Firefox at all, it's the upstream Arch package. I updated the container today, go ahead and run the following:

# docker pull escalade1/arch-browser

# docker pull escalade1/arch-pcsx2

The containers run entirely separate from the LibreELEC userland, so has it's own Mesa etc. I should probably redo the launcher scripts to pull the latest container on startup.

The best thing would be to compile Firefox with the LE toolchain, but that would require way too much work to set up and maintain.

mtk1

Looks like Sway triggers a bug in the i915 kernel driver. Doesn't happen here on the latest image, give it a try.

slacker666

I have no idea, so go with generic.

Nope, nothing there.

jaykass

That depends on what kind of PR's, adding packages for them isn't an issue. I might add them for RPi/Odroid, but the generic images is almost at 512MB already.

Liquidmercury

No worries, just explaining that the PCSX2 emulator there is the exact same as I use so I can't really understand that you were able to launch games with your Celeron. Perhaps he made a build with the new "Play" core, I don't know.

New generic image is out.

My "competitor" copied all my packages:

Dockerfile for PCSX2:

Docker/Dockerfile at f6b7e34feed2871fd958dff47674a87234476ec9 · escalade/Docker · GitHub

Docker/PCSX2 at master · 5schatten/Docker · GitHub

PCSX2 config:

RetroELEC/GSdx.ini at le9 · escalade/RetroELEC · GitHub

LibreELEC-RR/GSdx.ini at master-rr · 5schatten/LibreELEC-RR · GitHub

As you can see, there's zero difference PCSX2. Same Arch Linux base, same packages, same config.

AFAIK there's an AVX2 requirement.

jaykass

Yeah, I did the same with the RPi3b, it performs a lot better at 720p. I agree with you that it would make sense to set 1080p as a default for the RPi4. Hardware accelerated video playback at 4k is a totally different thing from being able to rendering graphics at 4k. Could you tell me a bit about how it performs in different cores? Is it powerful enough to use any shaders? I'd be interested to know if it can use the crt-frutbunn shader for example.

Liquidmercury

Your logs doesn't contain anything, I guess you rebooted. In any case, I don't know how you expected a Celeron 1017U to run PCSX2, it requires AVX2: PCSX2 - The Playstation 2 emulator - Getting Started

I doubt Dolphin will run any games satisfactory on that CPU either. You should be able to use a real wiimote though.

As for the latest generic image, looks like I set wrong compiler optimization by mistake. I've removed it and currently building a new image.