I have a problem.
I can't boot into Weston, no matter how many times I try.
Heres what the program throws at me:
Code:
# / start-weston.sh
Date: 2032-06-19 UTC
[22:32:56.796] weston 9.0.0
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: 2020.11-312-gfd5eeabac0
[22:32:56.800] Command line: weston -Bfbdev-backend.so --config=/weston.ini
[22:32:56.800] OS: Linux, 5.10.0+, #3 SMP Sat Dec 19 20:31:54 CET 2020, armv61
[22:32:56.800] Using config file '/weston.ini'
[22:32:56.804] Output repaint window is 7 ms maximum.
[22:32:56.804] Loading module '/usr/lib/libweston-9/fdev-backend.so'
[22:32:56.812] initializing fbdev backend
[22:32:56.832] Opening fbdev framebuffer.
[22:32:56.832] Calculating pixman format from:
- type: 0 (aux. 0)
- visual: 2
- bpp: 24 (grayscale: 0)
- red: offset: 16, length: 8, MSB: 0
- green: offset: 8, length: 8, MSB: 0
- blue: offset: 0, length: 8, MSB: 0
[22:32:57.216] event0 - Nintendo 3DS input: device removedoved".I
No matter how many times I try, it's always the same error.
Is there any reason this happens?
Thanks in advance.
Pretty sure weston has been broken for a little while. Think it was a change in the kernel framebuffer.
EDIT:
@squat1115 I checked in the build system, and weston is indeed broken. The backend that it relies on has been removed from the buildroot project as of Feb 2022 ("Weston FB Dev Removed" is in the buildroot legacy options, meaning it is no longer supported and the build fails if you enable it). You may be able to build a working version by grabbing a commit of the buildroot before that date.
---
NOTE: The below is meant to be separate from the reply above, but I wasn't about to double post.
I've seen too many people who think themselves "Linux Developers" lately who skim a look at the project and go "I wanna port <This Distribution>", clone it, mess with it and go "That's not even Linux, that's a toy".
You people who do this are distribution "porters" (AT BEST), NOT Linux developers. We need people who want to work on making the project functional, not pretty.
Hardware support just isn't there yet to make this a full blown eye-candy distribution, nor do we need nor want it due to memory constraints. Instead of taking a look at user-space and going "Oh, it's just a toy", MAKE IT BETTER, CONTRIBUTE TO THE HARDWARE SUPPORT. I, myself, am not a kernel developer so I can't help with the hardware support, but instead just like to poke around to see what I can do. That's fine, and should be encouraged, but this is simply not ready yet for distribution porters to do their work on top of it yet. It's not that this is a toy, think of it as a baby kernel that needs nourishing.
Don't just be some "porter" who styles themselves as a "Linux developer" who thinks they know everything but can't understand what a simple buildroot is.
This post was inspired by a reddit conversation I had about this exact topic, a so-called "Developer" came in boasting about porting Void Linux to another system, so naturally, I tried to help him get acquainted with the 3DS Linux development buildroot slightly (I gave him tips), and was given the line "Yeah that's not even a linux environment, that just sounds like a toy". Could be that I'm just in a particularly bad mood today (I am), but after seeing this behavior multiple times it's kinda rubbed me the wrong way.. Like why bitch about something not being up to your standards instead of helping to make it better in the ways it needs it?