users December 2022

users@lists.genode.org

16 participants
26 discussions

Start a nNew thread

ath9k usb Wi-Fi driver
by Colin Parker 23 Jun '23

23 Jun '23

4 24

Can Genode run on the Mixtile Blade 3?
by Jacek Rużyczka 06 May '23

06 May '23

Good evening Genodians, in a couple of months I'll receive a number of Mixtile Blade 3 SBCs (based on the RK3588) https://www.crowdsupply.com/mixtile-limited/mixtile-blade-3 and would like to (at least) try to equip them with the Genode OS. What's necessary for my project, is clustering four such nodes with a PCIe switch (supplied by Mixtile; see their web page) as well as using single SBCs as storage nodes, which will be connected to a hard drive. Is it possible to port Genode onto this platform, or is this impossible with the current version? I simply don't wanna start an infaust undertaking. Thank you. Regards Jacek Rużyczka

2 4

Regarding ARM on Genode
by Divya Sharma 10 Apr '23

10 Apr '23

hello genodians, I'm Trying to port Genode OS for i.MX 8MQ boards (arm_v8a). successfully generated .img file but don't know how to run this img file i don't have i.MX board so I have to run on Ubuntu (linux). I have tried qemu emulator but i think qemu doesn't supported board. (basically want to run genode os for ARM.) Please give some guidance on this. Thanks & Regards

6 25

Roadmap 2023
by Norman Feske 17 Jan '23

17 Jan '23

Dear Genode Community, hereby, I'd like to kick off our yearly brainstorming about Genode's road map for the upcoming year. Please feel invited to chime in, sharing your personal observations and plans. By mid of January, I will update Genode's official road map, trying to weave one reasonable plan out of our individual interests. Let me start with my personal reflection of the past year and the topics that I find tempting for 2023. Review of the past year ----------------------- My Genode year revolved all around the PinePhone, which was an extremely challenging and rewarding experience. Driven by the vision of a Genode-based smartphone, I had to tackle topics ranging from the schematics of the device, over plenty of peripheral drivers, up to the user-interface level. Along the way, I found myself entrenched in a staggering variety of topics. To name a few: A custom Forth interpreter for our firmware for the PinePhone's system-control processor, programmed in OpenRISC assembler. Implementing a low-complexity AT-protocol stack talking to the modem, enabling voice telephony and mobile-data connectivity. Coming up with a suitable user-interface concept for the mobile variant of Sculpt OS, and implementing it. The exploration and implementation of power-management features like voltage and frequency scaling. Reducing the time from cold start to the user interface to only 5 seconds. Getting the application performance up to an acceptable level, grabbing all straws in reach. This was of course not a one-man show but a team effort. I found myself very happy being strongly supported by Christian, Sebastian, Josef, and Stefan who played huge roles in wrestling with the hardware and ultimately enabling scenarios like media playback in the Morph browser on the PinePhone. The result makes me immensely proud. Moreover, we haven't just managed to get it to work, but we gained detailed guidance documentation [1] as a collateral effect. The main motivation behind my laborious writing effort was to lower the barrier of entry for others who wish to port Genode to further mobile platforms in the future. Let's see how this plays out. [1] https://genode.org/documentation/genode-platforms-22-05.pdf Interests for 2023 ------------------ Personally, there are four main interests, I'd like to focus on now. 1. Completing the support for the PinePhone Genode on the PinePhone evidently works now. But I want to make it rock! I'm eager to implement a prolonged standby mode that will allow me to leave the phone unplugged for a week while staying receptive for calls. I want to make the installation and use of custom software an easy and enjoyable experience. Finally, by integrating privacy-protecting functions like the file vault or WireGuard VPN support, the mobile version of Sculpt OS will give me the assurance I'm seeking for my personal mobile companion device. At the beginning of February, I'm going to present the current state at FOSDEM's "FOSS on Mobile" Devroom [2] and will invite the community for a field test. By May, I want to reach a state where we can offer a ready to use image for PinePhone for a broader user base. [2] https://fosdem.org/2023/schedule/event/genode_on_the_pinephone/ 2. Moving existing applications to Sculpt OS With Goa [3], we already have a nice starting point for bridging the gap between existing software and Genode. I want to elevate Goa from a personal project to an official Genode project. One particular ambition is the use of Goa for re-targeting existing mobile apps to the mobile version of Sculpt OS (e.g., using the APIs of Sailfish or Ubuntu touch UI). I'm thinking of an Open-Street-Map client and a messenger as particular examples. Should we manage to achieve a frictionless way to bringing existing apps to Sculpt OS, we may have a chance of spawning a broader active community. [3] https://github.com/nfeske/goa 3. Improved support for Intel GEN12 This month, I swapped out my trusty Lenovo x260 by a GEN12 Frame.work laptop as Genode development machine. It is a very nice laptop. Still, there are quite a few rough edges that need attention. The fan can get very noisy, which we can presumably fix by better driver support for CPU power and temperature settings. I know that Alexander has already done promising exploratory work, which I'd love to replicate and finally make it a regular feature. Closely related, I'm missing the battery-state applet on the new machine, and the of the PS/2-emulated touchpad is, well, an interim solution at best. I ultimately long for a proper touchpad driver with support for common gestures. 4. Distillation of Genode's base mechanisms Whereas the first three points address practical concerns, I also want to turn my attention to the framework architecture. During the past two years, I discovered several ways for simplifying the base system, slimming down the framework API, and lowering Genode's footprint. Think of my ambition to reduce the reliance on the C++ exception mechanism, consolidating core's PD and CPU services into one, streamlining the signalling mechanism, or re-implementing the page-fault handling across the various kernels. There is a lot of potential, which will ultimately open up new optimization opportunities. I restrained myself from exploring those ideas to retain my focus on the PinePhone. But they want out. The second half of 2023 would be a good time. What about you? --------------- Even though I hope that the thoughts above resonate with you, I'm pretty sure you have different perspectives. Please share them! How did you perceive the Genode year 2022? What directions are you most excited about? Which topics do you deem as interesting to explore yourself? Do you already happen to have rough plans about 2023? Cheers Norman -- Dr.-Ing. Norman Feske Genode Labs https://www.genode-labs.com · https://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

16 45

using GOA to port libraries
by Pirmin Duss 10 Jan '23

10 Jan '23

Hello Genodians As part of a project, I will port WasmEdge [1] to Genode. As WasmEdge uses cmake as build system my idea is to use GOA to port it. There is already a port of WasmEdge to the SEL4 kernel [2]. WasmEdge uses several libraries of which some also use cmake as build system. To start small I first want to port the `spdlog` library. Before working on the big dependency in form of the `lld` library from the `llvm` project. If I issue `goa build` successfully runs `cmake` but building fails afterward. There are a lot of `[-Werror=effc++]`. I tired different ways to set `CC_CXX_WARN_STRICT=` in the files `cmake_args` and `make_args`. Unfortunately none of them helped. Can anybody give me some hints how I could achive this? My project is located at [3]. Regards, Pirmin [1] https://github.com/WasmEdge/WasmEdge [2] https://github.com/second-state/wasmedge-seL4.git [3] https://github.com/trimpim/wasmedge-genode

3 10

Re: Roadmap 2023
by Sam Crow 06 Jan '23

06 Jan '23

------ Original message------From: Sam Crow Date: Thu, Dec 29, 2022 10:42 AMTo: users(a)lists.genode.org;Cc: Subject:Re: Roadmap 2023 Hello Genodians,I'd like to reiterate the mobile emphasis without tracking features. My spare SSD is occupied by Haiku release1 beta4 and I see little chance of that being evicted in favor of another desktop OS. My PinePhone would be a much better target, however. I bought it specifically to see how secure a mobile platform could be! Genode was one of the mobile targets I was hoping to try.My primary SSD on my desktop (a 3rd-gen i7), my laptop (a PineBook Pro) and my PinePhone (3GB RAM, 32GB internal storage) are presently all running Manjaro Linux. If I could evict Manjaro from all 3 places, that would be a good year for me. Despite liking the desktop experience, Manjaro has no privacy features that I'm aware of. Microkernels that keep every driver in user-mode and don't allow drivers to "call home" to their manufacturer or their manufacturer's government would be an ideal privacy feature. Binary blobs should be disallowed from such behavior.Finally, I foresee an involvement with WebAssembly to be a replacement for most binary blobs in a short period of time and as soon as that takes place, address sanitizers and other sandboxing technologies could be complimentary to the AGPL license strategy. I have already submitted some patches to the W2C2 project on GitHub at https://github.com/turbolent/w2c2 and would like to hear your thoughts on the subject of using bytecodes to sandbox drivers and other binary blobs.Note: presently drivers cannot be represented in the WASI standard APIs so another API variant will be needed. There is a discussion started on the subject at https://github.com/WebAssembly/WASI/discussions/501#discussioncomment-41887… if interested.Thanks for your time and efforts,Samuel D. Crow

3 3

Re: Roadmap 2023
by Colin Parker 04 Jan '23

04 Jan '23

Hello Genodians, Last year was a good year in Genode for me. I poke around with it at the hobby level, but this year I saw the drivers system substantially re-worked and I was able to successfully port a Linux driver. > What directions are you most excited about? Although many others are excited about Sculpt on phones and SOC/SBC scenarios, I remain excited about the prospect of improving Sculpt on “conventional” machines like laptops and (mini)towers. My thoughts on where things could be: 1) The default Sculpt image can probably be made to boot already on almost any x86 system. A few tweaks could help such as allowing command-line arguments from the boot loader to boot in “safe” mode, forcing fallback to the boot loader’s frame buffer. 2) The default Sculpt configuration is great and provides a low barrier to new users to at least try Sculpt. But to work seriously in Sculpt one wants to install a VM, which is many steps, and to virtualize and already-installed OS is even more steps. It would be fantastic if one could, out-of-the box, virtualize an installed OS. If that’s too much, it might be worth curating USB stick images with pre-installed VM partitions. > > Which topics do you deem as interesting to explore yourself? I might poke around with (2) above, at least trying to follow the existing instructions. I may also try to port some more Linux drivers. I’m curious where Sculpt will go with that - will it be towards live selection of drivers at boot time, like in most Linux distros, or is the idea for lean purpose-built images that contain only the drivers necessarily for a given system? Happy new year to all!

3 3

VMM ARM examples: Issues.
by Sid Agrawal 04 Jan '23

04 Jan '23

Hi, I am attempting to run the *vmm_arm run scripts* and am running into a few issues. I am running this on Ubuntu 22.04 with x86_64. The scenario I am trying is to run a with the *hw kernel with arm_v8a arch.* First Issue: '*src/libc' not found - unable to guess version* *Steps:* *git clone ...* *cd genode-dir* *tool/create_builddir arm_v8a* *# Add additional repos in the build.conf file.* *cd build* *make KERNEL=hw BOARD=virt_qemu_arm_v8a* *make KERNEL=hw BOARD=virt_qemu_arm_v8a run/vmm_arm* # Returns the following errors: including /home/siagraw/genode-hw/tool/run/power_on/qemu including /home/siagraw/genode-hw/tool/run/log/qemu including /home/siagraw/genode-hw/tool/run/boot_dir/hw including /home/siagraw/genode-hw/repos/os/run/vmm_arm.run Error: recipe for 'src/libc' not found - unable to guess version make: *** [Makefile:431: run/vmm_arm] Error 1 So, I removed the libc line from vmm_arm.run, as per the diff below: *diff --git a/repos/os/run/vmm_arm.run b/repos/os/run/vmm_arm.run* index d80052352..a4ec448ab 100644 --- a/repos/os/run/vmm_arm.run +++ b/repos/os/run/vmm_arm.run @@ -16,7 +16,6 @@ if { ![have_board imx7d_sabre] && ![have_board imx8q_evk] && create_boot_directory t import_from_depot [depot_user]/src/[base_src] \ [depot_user]/src/init \ - [depot_user]/src/libc \ [depot_user]/src/log_terminal \ [depot_user]/src/nic_router \ [depot_user]/src/terminal_crosslink \ After that, the VM boots up as below. Second Issue: *Failing mount command and no interactive shell.* [...] [init -> vm] [ 6.227743] NET: Registered PF_PACKET protocol family [init -> vm] [ 6.233521] Key type dns_resolver registered [init -> vm] [ 6.249367] Loading compiled-in X.509 certificates [init -> vm] [ 6.310832] Sending DHCP requests ., OK [init -> vm] [ 6.361405] IP-Config: Got DHCP answer from 10.0.1.1, my address is 10.0.1.2 [init -> vm] [ 6.372772] IP-Config: Complete: [init -> vm] [ 6.378516] device=eth0, hwaddr=02:02:02:02:04:05, ipaddr=10.0.1.2, mask=255.255.255.0, gw=10.0.1.1 [init -> vm] [ 6.387958] host=10.0.1.2, domain=, nis-domain=(none) [init -> vm] [ 6.394173] bootserver=10.0.1.1, rootserver=10.0.1.1, rootpath= [init -> vm] [ 6.394275] nameserver0=10.0.1.1 [init -> vm] [ 6.441325] Freeing unused kernel memory: 1152K [init -> vm] [ 6.458228] Run /bin/sh as init process [init -> vm] /bin/sh: can't access tty; job control turned off [init -> vm] / # mount /dev/vda /root; cp -r /etc /root; ls /root/etc; umount /root [init -> vm] mount: mounting /dev/vda on /root failed: No such file or directory <--- This seems to failing as there is nothing inside /dev in the VM. I tried an "ls" in my run script and that showed that /dev is empty. [init -> vm] fstab init.d resolv.conf Run script execution successful. I have a few questions here: - Was it ok to remove the libc line from the run script? - I was expecting the VM to hang around with a shell. Is that not the expected behavior? - I should be able to run this scenario of a rpi3, right? Instead of running inside Qemu(where I have effectively 2 level of virtualization from the point of the VM). Best, Sid

2 1

u-boot requirements for genode
by Michael Grunditz 03 Jan '23

03 Jan '23

Hello I would like to know the requirements from u-boot in order to properly start genode. I know you are using bootm command, but that doesn't work at all with rockchip boards. Not sure if it is rockchip specific, but bootm will in the end try to switch to el2 which will surely fail in my case, since it's already there. It also requires dt blob and or atags, if not there - hang. I have tried to drop to el1 from uboot and with genode image as EP. That works a bit better then just jumping to it from el2. But strange things happens. No output from Genode can be seen. I can output characters to uart , but the uart driver or something in between fails. I have tested with adding a crash the last thing it does in enable_mmu , and I get that crash. My guess is that it actually starts, but not sure. One thing that struck me was that it looked a bit like a serial communication error, like a baud rate issue. rockchip insists on running a silly high baud rate. So the first question is what I want to know,, the requirements. I have no problems with adjusting things . Best regards, Michael

3 3

Sculpt OS - A Truly Alternative OS blog post
by Will Senn 03 Jan '23

03 Jan '23

OK. I've wrapped up my week with Sculpt OS by writing up a using sculpt article for posterity, etc, and so on :). Lemme know if you find fault with it. It covers much of the same ground as the getting started tutorial in the docs, just in a different way. Thanks for introducing me to such an amazing effort. I'll be exploring more of the OS in the coming days and look forward to learning more from y'all. Here's the link: https://decuser.github.io/operating-systems/genode/sculpt/2022/12/30/sculpt… Will

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users December 2022