Hi,
I wanted to ask if the nitpicker component is compatible with sel4? When I tried to run the run/demo script I just got a black screen. Does it require any specific configuration that I might have missed while reading the docs? For reference I ran the following command:
```sh make -C build/x86_64 KERNEL=sel4 BOARD=pc run/demo ```
Best, Rumen
Hi,
On 11/5/25 08:00, Rumen Mitov wrote:
I wanted to ask if the nitpicker component is compatible with sel4? When I tried to run the run/demo script I just got a black screen. Does it require any specific configuration that I might have missed while reading the docs? For reference I ran the following command:
make -C build/x86_64 KERNEL=sel4 BOARD=pc run/demo
nitpicker is kernel independent, so it is supported definitely.
It is more likely that some resource configuration for some of the components is a bit too low for seL4. I run the run/demo script and the log output says, that indeed the resources for the framebuffer is insufficient. So, when increasing it a bit:
--- a/repos/os/recipes/raw/drivers_interactive-pc/drivers.config +++ b/repos/os/recipes/raw/drivers_interactive-pc/drivers.config @@ -83,7 +83,7 @@ </config> </start>
- <start name="fb" caps="130" ram="20M"> + <start name="fb" caps="150" ram="20M"> <binary name="vesa_fb"/> <route> <service name="ROM" label="config"> <parent label="fb.config"/> </service>
and re-creating the drivers-interactive package where this configuration steams from, for example
tool/depot/create genodelabs/pkg/x86_64/drivers_interactive-pc UPDATE_VERSIONS=1 FORCE=1
solves the issue for me.
Hope it helps,
Alex.