users

users@lists.genode.org

2285 discussions

Possible Sculpt VC Problem On VirtualBox
by John J. Karcher 04 Sep '18

04 Sep '18

Hello, Note: Please disregard this if you can't reproduce it - I can wait for the official images. I built Sculpt VC from GitHub (both "disk" and ISO images), but there seems to be a problem with the USB pointing device in VirtualBox. (I tested using the VM from the Sculpt TC appliance, so there shouldn't be a VM configuration problem.) Leitzentrale displays fine, with the Manager window, Log window, and the new VC Diagram. The F12 key works to show/hide Leitzentrale, so I know the system is alive, but the mouse doesn't work. In the Log window, the following is the only relevant message that stays long enough to read: [leitzentrale -> wm] Warning: no focus model available There are other USB-related messages, but without the mouse, I don't know how to examine the log. Thanks! -- John J. Karcher devuser(a)alternateapproach.com

2 2

Caution: potential loss of local changes when preparing dde_linux
by Norman Feske 03 Sep '18

03 Sep '18

Hello, I want to bring the following issue to your attention: https://github.com/genodelabs/genode/issues/2959#issuecomment-418133022 Please be extra careful when issuing a 'prepare_port dde_linux' command! It works well when issued for the first time. But should you issue it twice, you are at risk of losing local changes within your genode git tree. See the description given in the linked issue for the details. To be safe, I recommend removing any existing 'contrib/dde_linux-*' directories manually before issuing the 'prepare_port dde_linux' command. The following commit contains an interim fix that I merged to the master branch just now: https://github.com/genodelabs/genode/commit/bbff6ae52998c3faeb41fd508e99878… However, note that the commit is not able to fix the issue for an already prepared 'contrib/dde_linux-' directory. So better remove such directories after updating to the current master branch. Regards 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

WARNING: do not (re-) prepare dde_linux port!
by Stefan Kalkowski 03 Sep '18

03 Sep '18

Dear genodians, a recent regression within the dde_linux port description may lead to data-loss! When preparing the dde_linux port although it is already available, e.g., to overwrite local changes in the contrib sources, non-commited changes of any git repository above your contrib directory (normally this will be your genode repository) will get reset hard. This regression went into the codebase with the update of 'wpa_supplicant' within the last release. Have a look at: https://github.com/genodelabs/genode/issues/2959 for further details. We will provide a fix for this issue soon. In the meantime it is safe to do a prepare_port for dde_linux when it is not prepared yet. Sorry for the inconvenience & regards Stefan -- Stefan Kalkowski Genode labs https://github.com.skalk | https://genode.org

1 0

Sculpt 18.08 runtime_view
by Pirmin Duss 03 Sep '18

03 Sep '18

Hello Genodeans I like the new runtime_view in sculpt 18.08. It lests me explore my system in a whole new way. If I start multiple virtual machines, that have some surrounding components, the runtime_view requests more ram and the graph disappears. log output: [runtime -> runtime_view] resource_request: ram_quota=808991 [runtime] child "runtime_view" requests resources: ram_quota=808991 I fixed this for me by doubling the memory sculpt_manager assigns to it. my fix: diff --git a/repos/gems/src/app/sculpt_manager/runtime/runtime_view.cc b/repos/gems/src/app/sculpt_manager/runtime/runtime_view.cc index db6492f46..198f0874a 100644 --- a/repos/gems/src/app/sculpt_manager/runtime/runtime_view.cc +++ b/repos/gems/src/app/sculpt_manager/runtime/runtime_view.cc @@ -20,7 +20,7 @@ void Sculpt::gen_runtime_view_start_content(Xml_generator &xml, float font_size) { - gen_common_start_content(xml, "runtime_view", Cap_quota{200}, Ram_quota{9*1024*1024}); + gen_common_start_content(xml, "runtime_view", Cap_quota{200}, Ram_quota{18*1024*1024}); gen_named_node(xml, "binary", "menu_view"); Best regards, Pirmin

2 1

Explicit routing
by Guido Witmond 03 Sep '18

03 Sep '18

Hi Genodians, I'm stuck with service routing. When I use the default routes the hello-application works. When I remove the default and create explicit routes for the ROM-service these fail. Here's my writeup: I added this line to repos/os/src/init/child.cc: Init::Child::resolve_session_request( + log("child \"", name(), "\" resolves \"", service_name, "\" label [", label, "]"); It logs which child is resolving what service and label. With default routing, I get this output (for ROMs) in make run/hello: Genode 18.05-203-gf4ea50c6f <local changes> [init] child "hello_client" resolves "ROM" label [hello_client] [init] child "hello_client" resolves "ROM" label [ld.lib.so] [init] child "hello_server" resolves "ROM" label [hello_server] [init] child "hello_server" resolves "ROM" label [ld.lib.so] [init] child "hello_server" resolves "ROM" label [hello_server -> config] [init] child "hello_client" resolves "ROM" label [hello_client -> config] [init] child "hello_server" resolves "ROM" label [hello_server -> session_requests] ... [init -> hello_client] hello test completed So far so good. However, when I take out the <default-route> entry and add explicit routes to hello.run for the hello-client serivce: <route> <service name="PD"> <parent/> </service> <service name="CPU"> <parent/> </service> <service name="LOG"> <parent/> </service> <service name="Hello"> <child name="hello_server"/> </service> <service name="ROM" label="hello_client"> <parent/> </service> <service name="ROM" label="ld.lib.so"> <parent/> </service> <service name="ROM" label="hello_client -> config"> <parent/> </service> <service name="ROM" label="hello_client -> session_requests"> <parent/> </service> </route> I get these errors: (skipping things that go well) [init] child "hello_client" resolves "ROM" label [hello_client] [init] Warning: hello_client: no route to service "ROM" [init] Error: hello_client: ROM environment session denied ... [init] child "hello_client" resolves "ROM" label [ld.lib.so] [init] Warning: hello_client: no route to service "ROM" [init] Error: hello_client: ROM environment session denied ... Makefile:312: recipe for target 'run/hello' failed What's happening here? Why are my explicit routes to the labels I find in the first log not working? How can I make explicit routes work for these services? Cheers, Guido.

2 1

porting 3rd-software to Genode
by lzSun 03 Sep '18

03 Sep '18

Hello, I am porting a 3rd-party software to Genode framework. I follow this tutorial(https://genode.org/documentation/developer-resources/porting). When I execute the run command, the compilation process is complete, but there's a problem occurred when linking: "libc.lib.so: undefined reference to `Libc::Component::construct(Libc::Env&)' collect2: error: ld returned 1 exit status I have no idea how to fix this problem, can anyone give me some help? Thanks, ------------------ Best wishes

2 1

Sculpt VC Launcher GUI?
by Nobody III 31 Aug '18

31 Aug '18

In Sculpt VC, I haven't seen any launcher GUI. Does such a component exist? Or do I still have to use the text interface (vim) to launch components?

1 0

Re: Wandboard Quad GPIO mapping
by Edward Sandberg 31 Aug '18

31 Aug '18

Hi Stefan, Thanks very much for your detailed reply! > You are writing that you use Genode 18.05 nova? The nova kernel does > not run on ARM platforms. Certainly, you are using the base-hw kernel? Sorry, I meant seL4. > The imx6 gpio driver allows to set 7*32=224 pins to be set. It > controls 7 dedicated GPIO controllers with 32 pins for each. When you > want to address a pin of a controller > 0, you have to add an offset > accordingly. Yes, after I sent my original message I realized the the MAX_PINS variable was per bank and that the pin mapping to jp4 is the same as in linux. I am now able to read and write to the expected pins on jp4 extender. Next I am going to attempt to get the framebuffer working on the Wandboard Quad by modifying the imx53 framebuffer source code included with genode. So far I have modified: repos/base/include/drivers/defs/imx6.h to add the needed IPU_BASE, IPU_SIZE, PWM2_BASE and PWM2_SIZE variables. I see two interesting things when I boot: * Info: Not using supported FPU as FPU is disabled in the build configuration * [init -> fb_boot_drv] Error: No boot framebuffer information available. Perhaps if I fix the first issue the information will be provided and the second bullet point will be resolved as well. I will update the mailing list as I make progress. -- Edward Sandberg Adventium Labs 111 3rd Avenue S. Suite #100 Minneapolis, MN 55401 ed.sandberg(a)adventiumlabs.com

1 0

10th anniversary of the first public Genode release
by Norman Feske 31 Aug '18

31 Aug '18

Dear Genode community, as announced in the most recent Genode-Labs newsletter [1], we can celebrate the 10th anniversary of Genode this year. [1] https://www.genode-labs.com/news/newsletter/newsletter-2018-07 ------ Genode has reached the age of one decade! This is fascinating from various perspectives. First, we still vividly remember the time when we founded the project like if it was yesterday. We remember asking ourselves the question how we imagine Genode Labs in ten years. Well, it actually looks pretty much exactly like we had envisioned: A tight- knit group of enthusiastic and energetic minds working without friction in an enjoyable environment, a healthy open-source ecosystem, having earned the trust and recognition of highly reputable people. Our dream has become reality. Second, it took us more then 10 years to transform our initial vision of an ideal operating system into the software that runs so nicely on our laptops now. With the common perception of a rapid and ever accelerating evolution of technology as a background, this time frame feels like an eternity. But now, we are here. Third, maintaining a sustainable business over this long period while retaining independence is not easy. But it is possible and a fulfilling experience we would not want to miss. To celebrate the anniversary together with the community, friends, and families around Genode, we continue our tradition of holding a barbecue at the banks of the river Elbe: Google Maps: http://goo.gl/maps/C0luj Thursday August 30, 6 pm near Eisenberger Strasse in Dresden If you are planning to attend, please let us know by writing a short note to: info(a)genode-labs.com ------ 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

3 4

Wandboard Quad GPIO mapping
by Edward Sandberg 30 Aug '18

30 Aug '18

I'm working with the imx6 GPIO driver on Wandboard Quad, using the gpio_led run file as a smoke test. Unfortunately, I've had only limited success controlling the GPIO pins exported to the Wandboard's JP-4. It is unclear where these pins map in the Genode imx6 driver (18.05, nova). In Linux, I can successfully toggle them all via /sys/class/gpio. The imx6 driver allows for 32 pins to be set to high or low and I have modified the run file and the main.cc file to blink sets of pins rather than just a single pin. If I set all 32 pins as output with an initial value of "0" in the run file and then blink the following sets of pins I see these results: 0-31: I read 3 pins blinking with a voltage meter 0-15: I read 2 pins blinking 0-6: I read no pins blinking 7-15: I read no pins blinking It seems as though it takes combinations of pins set to high and low at the same time to get a reading of high or low off of a particular pin, but I cannot divine the pattern. This leads me to think that there is a step missing in the initial configuration. Does anyone have a suggestion of what step I am missing to get predictable results? -- Edward Sandberg Adventium Labs 111 3rd Avenue S. Suite #100 Minneapolis, MN 55401 ed.sandberg(a)adventiumlabs.com

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users