Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KioskMode not working on armv6 on future3 #2209

Closed
AlvinSchiller opened this issue Jan 6, 2024 · 19 comments · Fixed by #2217
Closed

KioskMode not working on armv6 on future3 #2209

AlvinSchiller opened this issue Jan 6, 2024 · 19 comments · Fixed by #2217
Labels
bug future3 Relates to future3 development wontfix

Comments

@AlvinSchiller
Copy link
Collaborator

Describe your problem

Since Bullseye the installation fails on choosing option "KioskMode" on an armv6 device cause chromium-browser has no installation candidate.

What's your hardware set up?

Docker with armv6 qemu.
Raspberry Pi OS bullseye 32bit lite + bookworm 32bit lite

If possible, try to attach logs from ... (paths from RPi)

Setup Kiosk Mode
Install Kiosk Mode dependencies
E: Package 'chromium-browser' has no installation candidate
Configure Kiosk Mode

@AlvinSchiller AlvinSchiller added bug needs triage future3 Relates to future3 development labels Jan 6, 2024
@s-martin
Copy link
Collaborator

s-martin commented Jan 6, 2024

The package is called chromium vs chromium-browser, but wasn't this already the case for buster?

@AlvinSchiller
Copy link
Collaborator Author

chromium-browser
Don't know if it would work with just chromium as the code later calls also chromium-browser.

I get a Pi Zero 1 the next days, so i could then test this on the device.

@s-martin
Copy link
Collaborator

s-martin commented Jan 6, 2024

Here I find only the package name chromium for all Debian versions and architectures https://packages.debian.org/search?suite=all&arch=any&searchon=names&keywords=Chromium

But this would mean it never worked... 🤔

@s-martin
Copy link
Collaborator

s-martin commented Jan 6, 2024

@AlvinSchiller
Copy link
Collaborator Author

AlvinSchiller commented Jan 7, 2024

chromium apparently has also no installation candidate for the armv6 platform

E: Package 'chromium' has no installation candidate

@s-martin
Copy link
Collaborator

s-martin commented Jan 7, 2024

Isn't armv6 (and armv7) rather armhf in Debian nomenclature?

@AlvinSchiller
Copy link
Collaborator Author

As far as i understood till armv6 it's armel and from armv7 it's armhf

@s-martin
Copy link
Collaborator

s-martin commented Jan 7, 2024

Googling provided mixed results, which architecture name matches which release name. 😏🫣🤔

@AlvinSchiller
Copy link
Collaborator Author

@s-martin
Copy link
Collaborator

s-martin commented Jan 7, 2024

I understand this means at least Raspian uses armhf for armv6 architecture?

There are or have-been at least two unofficial ports outside the Debian infrastructure.
Raspbian - Uses the hard-float version of the "new" ABI (EABI) like Debian armhf but targets v6 rather than v7. Currently tracks Debian jessie and stretch. Primarily but not exclusively targeted at the Raspberry Pi. GNU Triplet: arm-linux-gnueabihf

@AlvinSchiller
Copy link
Collaborator Author

Looks like. But that could mean it behaves different on a real pi.
I will test this as soon as I get the pi zero

@pabera
Copy link
Collaborator

pabera commented Jan 7, 2024

I just installed chromium-browser on my Pi 1 successfully. My question would be, does it really make sense to actually offer Kiosk Mode on armv6 machines, cause it'll be pretty slow anyways. (the installation itself took 15 mins)
It uses armhf.

I didn't connect a screen yet to actually test it, it's just a wild guess.

Thoughts?

@s-martin
Copy link
Collaborator

s-martin commented Jan 7, 2024

Possible approach: detecting slow machines and then suggesting the user on slow machines to not install kiosk mode?

Minimum suggestion ARMv7?

@AlvinSchiller
Copy link
Collaborator Author

I just installed chromium-browser on my Pi 1 successfully. My question would be, does it really make sense to actually offer Kiosk Mode on armv6 machines, cause it'll be pretty slow anyways. (the installation itself took 15 mins) It uses armhf.

I didn't connect a screen yet to actually test it, it's just a wild guess.

Thoughts?

Good to know its working and its "just" an emulation problem.
Thought of this too. As of what I read it was discontinued for armv6 as it was nearly unusable slow.

I would also suggest either don't offer this feature for armv6 devices or give a warning that it can be slow, like other features/installations already do.

Maybe depends if it would still be usable ? @pabera ?

@AlvinSchiller
Copy link
Collaborator Author

I tested this on a Raspberry Pi Zero 1 W and the installation was succesfull.
So the inital reported error is just the case for the ci tests and docker. Probably because of the unofficial ports described above.

BUT after startup the UI show an error "chromium is supported on Raspberry Pi Zero W". So it seems its nevertheless unsupported for arm6 devices.
@pabera could you verify this for the Pi 1? I used the official develop branch on bullseye.

Possible approach: detecting slow machines and then suggesting the user on slow machines to not install kiosk mode?

Minimum suggestion ARMv7?

I think we should add this, but give the message that its not supportedf on this device model and can't be installed.
I would not just leave it out, as users might ask, why this is not available.

@s-martin
Copy link
Collaborator

s-martin commented Jan 17, 2024

Possible approach: detecting slow machines and then suggesting the user on slow machines to not install kiosk mode?
Minimum suggestion ARMv7?

I think we should add this, but give the message that its not supportedf on this device model and can't be installed. I would not just leave it out, as users might ask, why this is not available.

yeah, let's add this, so users know that it will not work

so this issue is a wontfix

AlvinSchiller added a commit to AlvinSchiller/RPi-Jukebox-RFID that referenced this issue Jan 17, 2024
@AlvinSchiller
Copy link
Collaborator Author

Would it be desired to fix this with another browser?
Some suggest dillo as replacement, but i dont know if there are any tutorials.

AlvinSchiller added a commit to AlvinSchiller/RPi-Jukebox-RFID that referenced this issue Jan 17, 2024
@pabera
Copy link
Collaborator

pabera commented Jan 17, 2024

Let's not go this route now. We can create an issue to investigate dillo another time.

@AlvinSchiller
Copy link
Collaborator Author

AlvinSchiller commented Jan 18, 2024

Kiosk mode install option deactivated for armv6 devices with #2217

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug future3 Relates to future3 development wontfix
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants