{"action":"created","issue":{"url":"https://api.github.com/repos/maxnet/berryboot/issues/484","repository_url":"https://api.github.com/repos/maxnet/berryboot","labels_url":"https://api.github.com/repos/maxnet/berryboot/issues/484/labels{/name}","comments_url":"https://api.github.com/repos/maxnet/berryboot/issues/484/comments","events_url":"https://api.github.com/repos/maxnet/berryboot/issues/484/events","html_url":"https://github.com/maxnet/berryboot/issues/484","id":306251681,"number":484,"title":"libreelec/openelec issue with pi 3b+ ?","user":{"login":"sneaker333","id":37510590,"avatar_url":"https://avatars3.githubusercontent.com/u/37510590?v=4","gravatar_id":"","url":"https://api.github.com/users/sneaker333","html_url":"https://github.com/sneaker333","followers_url":"https://api.github.com/users/sneaker333/followers","following_url":"https://api.github.com/users/sneaker333/following{/other_user}","gists_url":"https://api.github.com/users/sneaker333/gists{/gist_id}","starred_url":"https://api.github.com/users/sneaker333/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sneaker333/subscriptions","organizations_url":"https://api.github.com/users/sneaker333/orgs","repos_url":"https://api.github.com/users/sneaker333/repos","events_url":"https://api.github.com/users/sneaker333/events{/privacy}","received_events_url":"https://api.github.com/users/sneaker333/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":17,"created_at":"2018-03-18T15:48:07Z","updated_at":"2018-03-28T18:19:13Z","closed_at":null,"author_association":"NONE","body":"Not sure if this is just me but using the latest BerryBoot I am not able to add a working libreelec or openelec os to my sd card. If I add a fresh openelec install or if I backup and restore an existing libreelec install from a pi 2 BerryBoot setup then the pi3b+ appears to hang when launching libreelec/openelec. I appear to have no problem booting Raspbian with BerryBoot on the pi3b+\r\n\r\nI can also take that new sd card from the Pi3b+ (containing the new BerryBoot build and Raspian and LibreElec) and put that into a Pi 2 - everything then appears to works fine, including LibreElec. It just appears to be the combination of Pi3b+, BerryBoot and LibreElec/OpenElec which is problematic.\r\n\r\nIs anyone else experiencing this ? \r\n"},"comment":{"url":"https://api.github.com/repos/maxnet/berryboot/issues/comments/376985840","html_url":"https://github.com/maxnet/berryboot/issues/484#issuecomment-376985840","issue_url":"https://api.github.com/repos/maxnet/berryboot/issues/484","id":376985840,"user":{"login":"macmpi","id":16296055,"avatar_url":"https://avatars2.githubusercontent.com/u/16296055?v=4","gravatar_id":"","url":"https://api.github.com/users/macmpi","html_url":"https://github.com/macmpi","followers_url":"https://api.github.com/users/macmpi/followers","following_url":"https://api.github.com/users/macmpi/following{/other_user}","gists_url":"https://api.github.com/users/macmpi/gists{/gist_id}","starred_url":"https://api.github.com/users/macmpi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/macmpi/subscriptions","organizations_url":"https://api.github.com/users/macmpi/orgs","repos_url":"https://api.github.com/users/macmpi/repos","events_url":"https://api.github.com/users/macmpi/events{/privacy}","received_events_url":"https://api.github.com/users/macmpi/received_events","type":"User","site_admin":false},"created_at":"2018-03-28T18:19:13Z","updated_at":"2018-03-28T18:19:13Z","author_association":"CONTRIBUTOR","body":"The original patching-part is very straightforward: it just requires a system with `squashfs-tools` so that `mksquashfs` command can be run to add the relevant `berryboot-init` file in root of original squashfs image.\r\nFrom there, supported OS (Volumio, LibreELEC,...) will auto-patch any later update that will be obtained in normal use of that image (no further installscript required).\r\nSo explicit patching just needs to be done once at very first install: it's the purpose of the installXXX script.\r\n\r\nTherefore, if your server has `mksquashfs` program, you could patch original images yourself, after downloading my `berryboot-init `scripts: your users won't have to come back to your server anymore for later updates.\r\n\r\nNow, there's little catch, due to a [current limitation in berryboot in supporting MSD boot configurations](https://github.com/maxnet/berryboot/issues/433#issuecomment-334163562).\r\nFor that reason my scripts currently **enforce explicit declaration of berryboot `boot` partition into `cmdline.txt` file**. That's the reason my install scripts ask users to modify that file before doing anything, and patched image would not start without that.\r\nSo for, **now user intervention is required** the first time.\r\nI agree it is a bit harsh way to do it currently, but I wanted it in such conservative way, untill that issue can be adequately addressed by @maxnet in future berryboot releases: I would then tweak the scripts accordingly to suppress that requirement.\r\nSo, more than happy to make it easier as soon as possible!\r\n\r\n\r\n"}}
{"actor":{"display_login":"macmpi"}}