users February 2024

users@lists.genode.org

12 participants
8 discussions

Mailing List Migration on Thursday, February 8, 2024
by Christian Helmuth 12 Mar '24

12 Mar '24

Hello Genodians, after thorough planning, we finally migrate this mailing list to Mailman 3. Consequently, the list will not be operational tomorrow Thursday, February 8, 2024, all day All current list subscribers stay subscribed and will receive list postings latest starting Friday. Other changes coming with Mailman 3 are as follows. - Registration URL for new list members https://lists.genode.org/mailman3/postorius/lists/users@lists.genode.org - Account Management URL https://lists.genode.org/mailman3/accounts/login/ - Mailing list archive https://lists.genode.org/mailman3/hyperkitty/list/users@lists.genode.org The old archive at https://lists.genode.org/pipermail/users/ will be frozen and preserved. All previous and future postings are available in the new archive. See you on Friday after the migration -- Christian Helmuth Genode Labs https://www.genode-labs.com/ · https://genode.org/ https://floss.social/@genode · https://genodians.org/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 2

Announcement: Genode OS Framework version 24.02 released
by Norman Feske 29 Feb '24

29 Feb '24

I am happy to announce the release of Genode 24.02 today. https://genode.org/news/genode-os-framework-release-24.02 It is safe to say that the release cycle was dominated by infrastructure topics that clear the way for addressing the usability topics on our road map. For example, the new version dissolves a major road block for suspend/resume, namely the suspend-cycle awareness of drivers. It also lays the groundwork for the flexible and robust routing and mixing of audio signals. We are also celebrating the wrapped-up transition to our modern Linux device-driver environment by replacing our dated Linux-based TCP/IP stack to a new port based on DDE-Linux 6.1.20. The wealth of infrastructural topics notwithstanding, the new version also brings exciting news for application developers who can now use the Goa SDK to casually target Sculpt OS as a remote test target. Summary of improvements: - Revised audio infrastructure - Sculpt OS as remote test target for Goa SDK - TCP/IP based on DDE-Linux 6.1.20 - Suspend/resume awareness of GPU, AHCI, NVMe drivers - Improved human-interface device handling - Multi-client use of Vivante GPUs - De-privileged light-weight event tracing The complete story is given by the release documentation: https://genode.org/documentation/release-notes/24.02 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

1 0

Rust Project Ideas
by nsf＠ksu.edu 22 Feb '24

22 Feb '24

Hello Genodians, I am new to Genode and am looking into projects I might be able to do to help get practice with Genode and get a better understanding of rust. On the last rust update, it seemed like the Genode team determined one of the next steps would be to explore rust on top of native Genode framework. Would there be a project that would be able to help achieve this goal? I thought of working with the Gnode api to create a transition layer so that components written in rust can directly work with the api. Would this be a project be helpful or would something else be more appropriate? Thanks in advance for the help, and if I am off base, please let me know! Sincerely, Nathan

4 4

Testing pc_linux image
by Pirmin Duss 16 Feb '24

16 Feb '24

Hello Genodians I'm back to working on the integration of the Intel IGC driver in to the pc_nic_drv. I have rebased my work tree to latest master. I can run the driver and it starts up. The log output is as follows: [init -> nic_drv_igc] NR_IRQS: 4352, nr_irqs: 4352, preallocated irqs: 256 [init -> nic_drv_igc] time-clocksource: dde_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 3526361616960 ns [init -> nic_drv_igc] time-clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [init -> nic_drv_igc] time-clocksource: Switched to clocksource dde_counter [init -> nic_drv_igc] e1000-e1000_main: Intel(R) PRO/1000 Network Driver [init -> nic_drv_igc] e1000-e1000_main: Copyright (c) 1999-2006 Intel Corporation. [init -> nic_drv_igc] e1000e-netdev: Intel(R) PRO/1000 Network Driver [init -> nic_drv_igc] e1000e-netdev: Copyright(c) 1999 - 2015 Intel Corporation. [init -> nic_drv_igc] Intel(R) 2.5G Ethernet Linux Driver [init -> nic_drv_igc] Copyright(c) 2018 Intel Corporation. [init -> nic_drv_igc] igc 04:00.0: PCIe PTM not supported by PCIe bus/controller [init -> nic_drv_igc] igc 04:00.0 eth0: MAC: d8:bb:c1:5b:3a:18 [init -> nic_drv_igc] sched_clock: Marking stable (144026000, 246486000)->(405777000, -15265000) [init -> mac_report_rom] report 'nic_drv_igc -> devices' [init -> mac_report_rom] <devices> [init -> mac_report_rom] <nic name="eth0" mac_address="d8:bb:c1:5b:3a:18"/> [init -> mac_report_rom] </devices> [init -> nic_drv_igc] igc 04:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [init -> nic_drv_igc] create uplink for net device eth0 [init -> nic_router] [uplink_igc] NIC sessions: 1 [init -> nic_router] [uplink_igc] snd ETH d8:bb:c1:5b:3a:18 > ff:ff:ff:ff:ff:ff IPV4 0.0.0.0 > 255.255.255.255 UDP 68 > 67 DHCP DISCOVER d8:bb:c1:5b:3a:18 > 0.0.0.0 [init -> nic_router] [uplink_igc] rcv ETH b4:2e:99:f9:18:72 > d8:bb:c1:5b:3a:18 IPV4 0.0.0.0 > 0.0.0.0 The last two lines get repeated. In Wireshark I see that the DHCP server offers an IP to the MAC of the Intel IGC, but nic_router doesn't see that. To be sure, that nothing is missing from the binary I would like to test the Linux kernel Image that get built by run make pc_linux. From what I understand, this wouldn't even need a root filesystem, as the kernel can do DHCP on its own. Before I start piecing something together, I'd like to ask, if someone does have a ready solution which allows to boot that image via iPXE? Regards, Pirmin

2 2

Genode::Registry blocking(?) on for_each call
by Zachary Zollers 15 Feb '24

15 Feb '24

Hello Genodians, I am attempting to familiarize myself with some of the provided data structures. When playing around with the Registry class, I encountered an interesting error. [1] is a GitHub gist containing the code I am running. I am wanting to use the Registry class to keep track of services announced by children on a parent component. When looking though the Genode repository, this seemed to be the accepted way to do this (please correct me if I am misunderstanding). When I run this code, I get the following output: Genode 23.11 87 MiB RAM and 63252 caps assigned to init [init -> parent] Child requested session: 'PD' Error: illegal READ at address 0x4 by pager_object: pd='init -> parent' thread='ep' ip=0x7acf4 I would like to pass a reference to the Registry to each instance of Child_policy so I can use services announced by other children. As an additional experiment however, I tried creating a new Registry as a class member for each Child_policy (see the comment at the top of the Tutorial::Child class). This resulted in the following output: Genode 23.11 87 MiB RAM and 63252 caps assigned to init [init -> parent] Child requested session: 'PD' To me, this indicates that the for_each call is blocking. I cannot see, however, what would be holding the mutex before I get to this point. Any pointers in the right direction would be greatly appreciated :) [1] https://gist.github.com/zgzollers/48181fbc2dac6e51015602c6329593f9 Thanks, Zachary Zollers

3 3

open/ close/ read
by Michael Grunditz 14 Feb '24

14 Feb '24

Hi Is open() read() close() supposed to work? For me they doesn’t. It works sometimes but not all times. It also doesn’t read the file it just reads the first bytes or kbytes if large file. fopen fread fclose is ok and stat. Michael

3 7

Child Component Not Starting
by Zachary Zollers 13 Feb '24

13 Feb '24

Hello Genodians, I am attempting to create my first Genode system scenario from scratch. After following some of the available tutorials, I feel like I have a foundational understanding of the client/server interfaces. I am now attempting to create a system that utilizes the parent/child interfaces. I am intentionally using the more bare-bones Child interface over the Sandbox API for educational purposes. [1] is a link to a GitHub gist containing my parent component and runscript. The child is the simple hello world program provided at the beginning of the Genode Foundations book. At present, everything seems to start without errors, but the output from the child is not displayed. After a couple of days of fumbling around, I have not been able to get this to work properly. Any suggestions you may have are greatly appreciated. As I said previously, this is my first attempt at creating a Genode system from scratch. Any feedback you may have is greatly appreciated (even if it is not directly related to the issue at hand). [1] https://gist.github.com/zgzollers/397f56b66179f3276e048be8a8a7a543 Thanks in advance, Zachary Zollers

3 3

link state with the new usb_net driver
by Pirmin Duss 02 Feb '24

02 Feb '24

Hello Genodians While testing my changed usb_net driver that supports SMSC95XX on arm_v8a I discovered, that the link state isn't propagated to the connected nic_router as it has been with the old version. With the old driver the log output of nic_router was as follows when the cable was connected/disconnected: <connect cable> [init -> nic_router] [secondary_nic] NIC sessions: 1 [init -> nic_router] [secondary_nic] dynamic IP config: interface 10.10.10.10/16, ... <disconnect cable> [init -> nic_router] [secondary_nic] dynamic IP config: none [init -> nic_router] [secondary_nic] NIC sessions: 0 With the new driver nic_router always reports: [init -> nic_router] [secondary_nic] NIC sessions: 1 As I do not have any other devices that need the usb_net driver, I'm not sure, if this only happens for my driver or if this is consistent with all other device types. Could someone with an other usb_net driven device give me feedback, if other devices show the same log outputs? Regards, Pirmin

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users February 2024