Skip to content
This repository has been archived by the owner on Feb 27, 2023. It is now read-only.

Lakka RasPi issue #554

Open
bdspvl opened this issue Sep 5, 2019 · 40 comments
Open

Lakka RasPi issue #554

bdspvl opened this issue Sep 5, 2019 · 40 comments

Comments

@bdspvl
Copy link

bdspvl commented Sep 5, 2019

Hello all new user on GitHub! Have an issue that started yesterday, Doing a now boot SD card for Pi and found out with Noobs, the Lakka RP2 DIY Retro emulation console has error and no download. Found out the download area is no longer there. Does anybody have a copy of the files and if so tell how to do a manual install without NOOBS? Or better still notify whoever to rebuild the site for downloading?
@lurch
Copy link
Collaborator

lurch commented Sep 5, 2019

Appears to be the same as libretro/Lakka-LibreELEC#769 (i.e. none of the Lakka downloads are working?)

@bdspvl
Copy link
Author

bdspvl commented Sep 6, 2019 via email

@XECDesign
Copy link
Contributor

@kivutar

@XECDesign
Copy link
Contributor

Lakka removed from os_list.

@kivutar
Copy link

kivutar commented Sep 10, 2019

@natinusala

@natinusala
Copy link

We had an internal issue that caused all our images to be removed from the build server - we are currently working on releasing Lakka 2.3. I will let you know when the files are back online, sorry for the trouble

@XECDesign
Copy link
Contributor

Thank you

@bdspvl
Copy link
Author

bdspvl commented Sep 14, 2019 via email

@natinusala
Copy link

Okay, the regular images are back online.

We have three different NOOBS archives: one for RPi, one for RPi2 and 3 and one for RPi4

Should I upload all three? How do you want to proceed?

@lurch lurch reopened this Sep 18, 2019
@XECDesign
Copy link
Contributor

All three would be alright.

@natinusala
Copy link

Sorry I'm unfamiliar with how NOOBS gets the files, I have to extract all the files of the archive to a webserver right? Or upload the whole archive as it is?

@XECDesign
Copy link
Contributor

You can use libreelec as a template. Look at their section here http://downloads.raspberrypi.org/os_list_v3.json

        {
            "description": "LibreELEC is a fast and user-friendly Kodi Entertainment Center distribution.",
            "icon": "http://releases.libreelec.tv/noobs/LibreELEC_RPi/LibreELEC_RPi.png",
            "marketing_info": "http://releases.libreelec.tv/noobs/LibreELEC_RPi/marketing.tar",
            "nominal_size": 1024,
            "os_info": "http://releases.libreelec.tv/noobs/LibreELEC_RPi/os.json",
            "os_name": "LibreELEC_RPi",
            "partition_setup": "http://releases.libreelec.tv/noobs/LibreELEC_RPi/partition_setup.sh",
            "partitions_info": "http://releases.libreelec.tv/noobs/LibreELEC_RPi/partitions.json",
            "release_date": "2019-05-04",
            "supported_hex_revisions": "2,3,4,5,6,7,8,9,d,e,f,10,11,12,14,19,0092",
            "supported_models": [
                "Pi Model",
                "Pi Compute Module Rev",
                "Pi Zero"
            ],
            "tarballs": [
                "http://releases.libreelec.tv/noobs/LibreELEC_RPi/System.tar.xz",
                "http://releases.libreelec.tv/noobs/LibreELEC_RPi/Storage.tar.xz"
            ]
        },

We just need to be able to reach each of the files os_list references. So I'd expect to see a file structure that looks like this http://releases.libreelec.tv/noobs/

@natinusala
Copy link

Okay thanks for the info

Do the three versions need to have a different os_name, or can the three of them be Lakka?

@lurch
Copy link
Collaborator

lurch commented Sep 19, 2019

I think it's probably best to give them a different name, in case somebody e.g. wants to use the same SD card on both a Pi1 and a Pi3? (and I've not checked the code, so I dunno what NOOBS would actually do if it did find multiple OSes with the same os_name?)

@natinusala
Copy link

Okay then I will upload the images with the 2.3.1 release in a few days, sorry for all the fuss

I will let you know here when all the files are published and ready, I'll also give you the os_list.json entry for all variants if needed

@natinusala
Copy link

Here you go

{
    "description": "The DIY retro emulation console",
    "icon": "http://le.builds.lakka.tv/noobs/Lakka_RPi4/Lakka_RPi4.png",
    "marketing_info": "http://le.builds.lakka.tv/noobs/Lakka_RPi4/marketing.tar",
    "nominal_size": 1024,
    "os_info": "http://le.builds.lakka.tv/noobs/Lakka_RPi4/os.json",
    "os_name": "Lakka_RPi4",
    "partition_setup": "http://le.builds.lakka.tv/noobs/Lakka_RPi4/partition_setup.sh",
    "partitions_info": "http://le.builds.lakka.tv/noobs/Lakka_RPi4/partitions.json",
    "release_date": "2019-09-20",
    "supported_hex_revisions": "",
    "supported_models": [
        "Pi 4"
    ],
    "tarballs": [
        "http://le.builds.lakka.tv/noobs/Lakka_RPi4/System.tar.xz",
        "http://le.builds.lakka.tv/noobs/Lakka_RPi4/Storage.tar.xz"
    ]
},
{
    "description": "The DIY retro emulation console",
    "icon": "http://le.builds.lakka.tv/noobs/Lakka_RPi2/Lakka_RPi2.png",
    "marketing_info": "http://le.builds.lakka.tv/noobs/Lakka_RPi2/marketing.tar",
    "nominal_size": 1024,
    "os_info": "http://le.builds.lakka.tv/noobs/Lakka_RPi2/os.json",
    "os_name": "Lakka_RPi2",
    "partition_setup": "http://le.builds.lakka.tv/noobs/Lakka_RPi2/partition_setup.sh",
    "partitions_info": "http://le.builds.lakka.tv/noobs/Lakka_RPi2/partitions.json",
    "release_date": "2019-09-20",
    "supported_hex_revisions": "1040,1041,2082",
    "supported_models": [
        "Pi 2",
        "Pi 3"
    ],
    "tarballs": [
        "http://le.builds.lakka.tv/noobs/Lakka_RPi2/System.tar.xz",
        "http://le.builds.lakka.tv/noobs/Lakka_RPi2/Storage.tar.xz"
    ]
},
{
    "description": "The DIY retro emulation console",
    "icon": "http://le.builds.lakka.tv/noobs/Lakka_RPi/Lakka_RPi.png",
    "marketing_info": "http://le.builds.lakka.tv/noobs/Lakka_RPi/marketing.tar",
    "nominal_size": 1024,
    "os_info": "http://le.builds.lakka.tv/noobs/Lakka_RPi/os.json",
    "os_name": "Lakka_RPi",
    "partition_setup": "http://le.builds.lakka.tv/noobs/Lakka_RPi/partition_setup.sh",
    "partitions_info": "http://le.builds.lakka.tv/noobs/Lakka_RPi/partitions.json",
    "release_date": "2019-09-20",
    "supported_hex_revisions": "2,3,4,5,6,7,8,9,d,e,f,10,11,12,14,19,0092,0093"
    "supported_models": [
       "Pi Model",
       "Pi Compute Module",
       "Pi Zero"
    ],
    "tarballs": [
        "http://le.builds.lakka.tv/noobs/Lakka_RPi/System.tar.xz",
        "http://le.builds.lakka.tv/noobs/Lakka_RPi/Storage.tar.xz"
    ]
}

@natinusala
Copy link

I just left nominal_size at 1024 because I don't know what it refers to

@lurch
Copy link
Collaborator

lurch commented Sep 21, 2019

IIRC it's the sum of the partition_size_nominal values in partitions.json ? (which the NOOBS GUI uses to decide if there's enough free space on the SD card to install the OS)

@natinusala
Copy link

Then 1024 is correct

@procount
Copy link
Contributor

@natinusala
Please could you add the following to each of your OS entries for better support in PINN:

        "url": "http://www.lakka.tv/",
        "group": "Games",
        "supports_backup" : true,
        "download_size": XXXXX,

Where XXXXX is the sum of the filesizes (in bytes) of system.tar.xz and storage.tar.xz for each OS respectively.

@natinusala
Copy link

@procount done!

@XECDesign
Copy link
Contributor

Should be in os_list_v3.json now

@natinusala
Copy link

Excellent, thank you very much

@lurch
Copy link
Collaborator

lurch commented Sep 26, 2019

@bdspvl Would you like to test this, and close this issue if it's fixed?

@XECDesign
Copy link
Contributor

XECDesign commented Sep 26, 2019 •
edited
Loading

Trying to test it, but the server seems a little slow.

@procount
Copy link
Contributor

@natinusala - Thanks for adding the extra fields for PINN.
Could they be added to the entries in os_list_v3.json too?
(In fact, the download_size entry only makes sense in os_list_v3.json and can be deleted from os.json, but it's not essential.)
Maybe @XECDesign could assist?

@XECDesign
Copy link
Contributor

Manually updating download_size in os_list_v3.json each time isn't something I'm keen on.

@XECDesign
Copy link
Contributor

download_size entry only makes sense in os_list_v3.json

Does that imply the other entries make sense in os.json? What's the difference in how they're handled in the two files?

@lurch
Copy link
Collaborator

lurch commented Sep 26, 2019

@procount Just a suggestion, but I wonder if you could modify PINN to work out the (total) size of the download tarballs using http HEAD requests?

@procount
Copy link
Contributor

Does that imply the other entries make sense in os.json?

Yes.

What's the difference in how they're handled in the two files?

os_list_v3.json contains just enough meta-data for "remote" OSes on a server to be displayed in NOOBS/PINN and downloaded. For these OSes, os.json is not actually used.
When the OS is stored locally on the SD card (like in NOOBS-FULL) or on the USB stick, there is no os_list_v3.json, so os.json is used instead. (Partitions.json is used for both local and remote OSes.)
I don't know why it is like that, it's before my time!
So the extra fields need to be in both files.

"download_size" is only used for progress indication, and does not have to be accurate, although it does help. So you don't need to update it every time. In any case, I can override it if it gets too far out of step with each update.

But on a new release of an OS, you have to update the OS entries in os_list_v3.json anyway (release date, version, description maybe), so what is the difference if the maintainer can update this field? You just need to cut n' paste the whole OS entry into os_list_v3.json.

@lurch, in fact PINN already does calculate the download size for each OS, but only if the download_size field is not present. It takes a relatively long time to calculate it for 60-ish OSes, so it slows the startup time down. This was a way of caching the data to speed it up. Likewise I cache the OS icons to speed up the startup.

@XECDesign
Copy link
Contributor

Sounds good, I'll copy the entries. Thanks, Kevin.

@procount
Copy link
Contributor

Maybe @XECDesign could assist?

I just meant "on this occasion" (in case you took it the wrong way). Thereafter it would be ideal if the maintainers could update this field themselves on each update.

@natinusala
Copy link

in fact PINN already does calculate the download size for each OS, but only if the download_size field is not present. It takes a relatively long time to calculate it for 60-ish OSes, so it slows the startup time down.

But why do you need to know the size of every OS? Can't you do the size check only when the user wants to install the OS?

@XECDesign
Copy link
Contributor

Added

@procount
Copy link
Contributor

Can't you do the size check only when the user wants to install the OS?

Probably because it fitted with the current workflow of gathering all information upfront before the user selects any OS. But it's an interesting suggestion so I may consider it for a future version.

@XECDesign - thanks!

@lurch
Copy link
Collaborator

lurch commented Sep 26, 2019

It takes a relatively long time to calculate it for 60-ish OSes, so it slows the startup time down.

I'd forgotten how many OSes you have in PINN! 🙇‍♂️

@procount
Copy link
Contributor

procount commented Sep 26, 2019 •
edited
Loading

Well, it depends on the model of RPi as to how many are available, but I still have to read them all in.

According to http://pinn.mjh.nz/ there are 62 OSes available for the 3B, 20 for the 4B and 47 for most others, all spread over 4 separate source repositories. Which explains why it sometimes takes me a while to update them to the latest version!

Edit: Mind you, 9 of those might be attributed to the ProjectSpaces and Data Partition, so maybe subtract 9 from all figures to be more accurate.

@procount
Copy link
Contributor

@natinusala - I don't see any "supports_usb" options, so I'm assuming these latest lakka versions are ok to install to usb (either fully or just the rootfs)?

I ask because some PINN users using the previous Lakka versions had found it was possible to install them to USB, but were blocked from doing so due to these options previously being set to false.

@natinusala
Copy link

I'm not sure, I think the RPi2/3 version can but not the RPi4 (because the bootloader doesn't support it?)

@procount
Copy link
Contributor

procount commented Sep 26, 2019 •
edited
Loading

Of course, pi4 excepted for the time being.

Edit: I don't think that has been accounted for in any of the Pi4 OSes, but it's a limitation of the PI4 bootloader rather than the OS, so providing it will potentially work when the bootloader is updated, then I think that is fine. (IIRC, the support_usb option was more to do with the partition references).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@kivutar @lurch @natinusala @XECDesign @procount @bdspvl