From the live USB mount the first partition on the SSD and find extlinux.conf. There are two; one in the root folder, or if the box is EFI booting you need to edit the second in the EFI subfolder. Just add the same radeon.dpm=0 to boot params.
Posts by chewitt
-
-
I personally find it easiest to add/edit things /storage/.kodi/userdata/sources.xml .. but then I'm a console junkie
-
Just run a Leia image and use the retroplayer capabilities in Kodi
-
Put the three files in projects/Generic/filesystem/usr/lib/firmware/brcm/ .. create folders as required. The filesystem folder is a hack vs. properly modifying the sources of something, but it's the most expedient option for something this simple.
-
-
You cannot update the running kernel from the console in LE, it has to be done via the build-system and baked into the OS image.
-
LE 8.2 (including 8.1.x) uses SMB2/3 so there is no 'network browsing' in Kodi (as it requires SMB1). You will need to configure the full server/path to add the shares.
-
Everything is possible with appropriate time, effort and skills. It's not a simple task though. Supporting a new device platform requires a lot more than rebuilding a couple of drivers.
-
Just read an online howto/guide for the "tar" command.
-
also to write on nand-Flash on Amlogic Devices is not in Wiki...
Good. It reduces the opportunity for people to make the LE install process even more complicated.
-
milhouse images exist today with pre-alpha Leia code; current ETA for first alpha releases from Kodi would be around year end.
-
You can also upload/share a sample file somewhere
-
If it's no WSL .. just clean packages and remove ccache and try again. I build official releases on 16.04.3 and there are no known issues.
-
Not possible - You need to reboot to change between LE and Lakka. If this is an x86_64 box you can use a milhouse Leia build and use the Game functions there which are different, but also based on Retroplayer.
-
LE has no issue with GPT partitions and although it's not impossible we run a fairly current version of parted so it's unlikely the issue is there. I've no idea whether F2FS is fully supported though. If the kernel is trying to mount partitions there is clearly some config in the kernel but we don't use it ourselves (we use EXT4) so you might want to check and see if everything required is set.
Go back and test in Ubuntu (on a LiveUSB stick) before attempting anything else.
-
It requires a different graphics stack to our current one for nVidia and probably requires a different EFI bios, e.g. MrChromebox.tech (which does not list that Acer device as supported). I don't want to sound negative, but from past experience this is one of those situations where "those who can, get on with it" and "those who can't, ask us how to do it" .. i.e. if you don't already understand our build-system and what needs to be done in detail the chances of success are low, because there are no howto guides or scripts or instructions for this. Sorry..
-
Code
mv /storage/.kodi/userdata/advancedsettings.xml /storage/.kodi/userdata/advancedsettings.old wget http://chewitt.libreelec.tv/advancedsettings.xml -O /storage/.kodi/userdata/advancedsettings.xml systemctl restart kodi < wait until it hangs on restart > cat /storage/.kodi/temp/kodi.log | paste^ then share the URL generated
-
The technical answer is "depends on what combination of patches are on the Win10 box" .. hence the release notes cannot be explicit, but in the long-term MS is pushing the removal of guest and unauthenticated access so the sooner you bite the bullet and move to authenticated shares, the sooner you (probably) don't have to reconfigure things again
