[GH-ISSUE #38] White Screen on boot - Swiotlb Buffer is Full in log. Perhaps adding update routine to installation script? #36

New issue

Closed

opened 2026-03-03 11:13:34 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 11:13:34 +03:00

Owner

Originally created by @andiohn on GitHub (Oct 3, 2024).
Original GitHub issue: https://github.com/debloper/xiosk/issues/38

I'm running in to the dreaded white screen with the following error:

[ 137.266069] vc4-drm gpu: swiotlb buffer is full (sz: 13312000 bytes), total 32768 (slots), used 412 (slots)

This is immediately after first boot with the settings set. I'm thinking it might be an update thing. Perhaps the script should:

"sudo apt update && sudo apt upgrade -y"

Right off the bat. I just ran this on my machine even without rebooting and it suddenly worked. :)

Originally created by @andiohn on GitHub (Oct 3, 2024). Original GitHub issue: https://github.com/debloper/xiosk/issues/38 I'm running in to the dreaded white screen with the following error: [ 137.266069] vc4-drm gpu: swiotlb buffer is full (sz: 13312000 bytes), total 32768 (slots), used 412 (slots) This is immediately after first boot with the settings set. I'm thinking it might be an update thing. Perhaps the script should: "sudo apt update && sudo apt upgrade -y" Right off the bat. I just ran this on my machine even without rebooting and it suddenly worked. :)

kerem

2026-03-03 11:13:34 +03:00

closed this issue
added the
invalid
label

kerem commented

2026-03-03 11:13:34 +03:00

Author

Owner

@andiohn commented on GitHub (Oct 4, 2024):

It is very possible this is because my websites are too heavy all at once, perhaps this isn't an issue because it seems like it's resolved after about 5 minutes or so. That or the updates did, in fact, fix it. It's hard to say.

@andiohn commented on GitHub (Oct 4, 2024): It is very possible this is because my websites are too heavy all at once, perhaps this isn't an issue because it seems like it's resolved after about 5 minutes or so. That or the updates did, in fact, fix it. It's hard to say.

kerem commented

2026-03-03 11:13:35 +03:00

Author

Owner

@debloper commented on GitHub (Oct 7, 2024):

Perhaps the script should:
"sudo apt update && sudo apt upgrade -y"

github.com/debloper/piosk@04431828f3/scripts/setup.sh (L9)

If you look into the content of the script, the apt update/upgrades are applied during the nodejs installation already.

In future we may move away from needing to install nodejs (by using single executable application mechanism); that's when explicit apt updates would be necessary.

FWIW, the swiotlb log isn't related or relevant for userspace operations (i.e. it doesn't care about specific applications & their memory usage, including but not limited to Chrome).

@debloper commented on GitHub (Oct 7, 2024): > Perhaps the script should: > "sudo apt update && sudo apt upgrade -y" https://github.com/debloper/piosk/blob/04431828f3136bb61f78458a2580895f6de328ec/scripts/setup.sh#L9 If you look into the content of the script, the apt update/upgrades are applied during the nodejs installation already. In future we may move away from needing to install nodejs (by using [single executable application](https://nodejs.org/api/single-executable-applications.html) mechanism); that's when explicit `apt` updates would be necessary. FWIW, the `swiotlb` log isn't related or relevant for userspace operations (i.e. it doesn't care about specific applications & their memory usage, including but not limited to Chrome).

kerem referenced this issue

2026-03-03 11:13:35 +03:00

[GH-ISSUE #37] Internet source of configured websites, or even all settings #34