users

users@lists.genode.org

7 participants
2332 discussions

Change to usb_drv? (17.11 -> 18.05)
by Steven Johnston 16 Aug '18

16 Aug '18

Hi All: One of my components that handles a USB device was working in 17.11 (x86_32, nova), but is causing problems when I attempt to run it in 18.05. The device is an FTDI-based USB-GPIO adapter (FT232H chip), along with a port of libftdi. The USB hub setup seems to work, but the FTDI setup generates an error in the log "ftdi_usb_reset failed", occurring when libusb_control_transfer() fails during a USB reset. There is a similar sounding issue mentioned in the release notes regarding usb_block_drv. Might it be the same? If so, has this been resolved in some general way? Thank you for any input, Steven

3 2

Genode Foundations book format
by astian 14 Aug '18

14 Aug '18

Hi, Looking for interesting things to read I came across this book, but would like to know if the last version (apparently 18.05) is available in some format less damned inflexible than PDF. Searching around turned up this URL: https://genode.org/documentation/genode-foundations-16-05.epub Which is ideal, except that an "...-18-05.epub" does not seem to exist. Thanks.

2 2

gdb_monitor does not work
by Alexander Senier 09 Aug '18

09 Aug '18

Hi all, I'm debugging an application on base-nova and trying to get remote gdb set up for that. Using gdb on base-linux is not an option right now, as the application exposes a different issue there. To verify that gdb works, I adapted the simple run/log example (see the attached delta). I'm using current master (f4ea50c6). When starting the run file, I see: [snip] Genode 18.05-203-gf4ea50c6f <local changes> 469 MiB RAM and 63253 caps assigned to init [init -> uart_drv] --- UART driver started --- [init -> gdb_monitor] using the pipe libc plugin [init -> gdb_monitor] Warning: sigaction: sigaction not implemented [init -> gdb_monitor] Process target created; pid = 1 [init -> gdb_monitor] Warning: unsupported ioctl (request=0x40047477) [init -> gdb_monitor] Warning: unsupported ioctl (request=0x80047476) [init -> uart_drv] open IRQ 3 [init -> uart_drv] [init -> gdb_monitor] Remote debugging using /dev/terminal [init -> gdb_monitor] Warning: fcntl(): command 4 args 66 not supported - terminal [init -> gdb_monitor] Warning: fcntl(): command 6 args 4294967295 not supported - terminal Then, I start gdb on the host from within the debug directory of the build: $ ln -s ld-nova.lib.so ld.lib.so $ genode-x86-gdb test-log GNU gdb (GDB) 7.3.1 Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=x86_64-unknown-linux-gnu --target=x86_64-pc-elf". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /home/alex/Documents/Componolit_GmbH/Devel/src/genode-master/build/x86_64/debug/test-log...done. (gdb) target remote localhost:5555 Remote debugging using localhost:5555 Reading symbols from ld.lib.so...done. Loaded symbols for ld.lib.so warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. _start () at /home/alex/Documents/Componolit_GmbH/Devel/src/genode-master/repos/base/src/lib/startup/spec/x86_64/crt0.s:43 43 leaq _GLOBAL_OFFSET_TABLE_(%rip), %r15 (gdb) The Genode log says: [init -> gdb_monitor] Warning: ptrace(PTRACE_GETREGSET (0x4204)) called - not implemented! [init -> gdb_monitor] Warning: read: no memory at address 0x1005d08 [init -> gdb_monitor] Warning: read: no memory at address 0x1005d08 [init -> gdb_monitor] Warning: read: no memory at address 0x1005d08 GDB does not seem to work correctly: (gdb) bt #0 _start () at /home/alex/Documents/Componolit_GmbH/Devel/src/genode-master/repos/base/src/lib/startup/spec/x86_64/crt0.s:43 Cannot access memory at address 0x0 [init -> gdb_monitor] Warning: read: no memory at address 0x0 Any ideas what's wrong here? Cheers, Alex -- Componolit GmbH · Königsbrücker Straße 124 · 01099 Dresden · Germany Amtsgericht Dresden · HRB 36670 · Sitz Dresden Geschäftsführer: Alexander Senier · USt-IdNr. (EU VATIN): DE312113634 http://componolit.com · @Componolit

2 2

loading core symbols for debugging purpose
by Parfait Tokponnon 08 Aug '18

08 Aug '18

Hello, My goal is to set breakpoint at some instruction address in the core process to trace its execution. To achieve this, I use this command in gdb. *add-symbol-file <filename> <load address>* But I cannot access the core load address. *objdump -h debug/core-nova.o *yields LMA for the .text section : 0x0000000000000000 And the ld-nova.lib.so does not help too. Can someone point me, in order to trace the core process execution, at which address to load the core symbols file? Thanks, -- Parfait T.

2 2

width of log window in sculpt 18.06
by Pirmin Duss 07 Aug '18

07 Aug '18

Hello Genodeans Today I switched from Sculpt 18.05 to 18.06. The automatic arrangement of the inspect window inside the free area of the Leitzentrale is very convenient. Only one thing doesn't work for me at the moment. In 18.05 it was possible to increase the width of the log window by changing the configuration for log_nit_fb in /config/leitzentrale. I used this a lot for better readability of the log. Best regards, Pirmin

2 1

ARM/sel4 compatibility
by Edward Sandberg 07 Aug '18

07 Aug '18

Hello, Can someone please provide an up-to-date ARM hardware compatibility list for Genode 18.05 and seL4: boards and drivers? Which boards are tested regularly? We have tried building run/demo for several ARM boards without a lot of luck: * Raspbery Pi Build fails with: Library-description file rpi_usb.mk is missing make[2]: *** No rule to make target 'rpi_usb.lib', needed by 'usb.lib'. Stop. I got past this by running: cp ./dde_linux/lib/mk/spec/foc/rpi_usb.mk ./dde_linux/lib/mk/spec/sel4/ but then I hit: Library-description file kernel-sel4.mk is missing Library-description file syscall-sel4.mk is missing make[2]: *** No rule to make target 'syscall-sel4.lib', needed by 'startup-sel4.lib'. Stop. * Wandboard Quad Build completes, but when loading UImage all we see is: ## Booting kernel from Legacy Image at 12000000 ... Image Name: Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 697455 Bytes = 681.1 KiB Load Address: 10001000 Entry Point: 10001000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK So it is unclear whether sel4 has started or not. * Arndale Build fails with: Library-description file syscall-sel4.mk is missing var/libdeps:21: *** Recursive variable 'DEP_A_kernel-sel4' references itself (eventually). Stop. For each of these we had the following repositories enabled: REPOSITORIES += $(GENODE_DIR)/repos/base REPOSITORIES += $(GENODE_DIR)/repos/os REPOSITORIES += $(GENODE_DIR)/repos/demo REPOSITORIES += $(GENODE_DIR)/repos/libports REPOSITORIES += $(GENODE_DIR)/repos/ports REPOSITORIES += $(GENODE_DIR)/repos/dde_linux Thanks! -- Edward Sandberg Adventium Labs 111 3rd Avenue S. Suite #100 Minneapolis, MN 55401 ed.sandberg(a)adventiumlabs.com

4 4

Run sculpt under Xen domU
by Jan Siddartha Hussmann 06 Aug '18

06 Aug '18

Dear all, has anyone successfully been able run a sculpt.iso image with nova in a domU? Is that even possible? I did some research and found https://github.com/genodelabs/genode/issues/2504 I changed line in build.conf from QEMU_RUN_OPT := --include power_on/qemu --include log/qemu --include image/disk to: QEMU_RUN_OPT := --include boot_dir/$(KERNEL) --include power_on/xen --include power_off/xen --include log/xen --include image/iso However when trying to boot the image I get Booting Genode on nova and then a blank screen. Has anyone experience with this? How do I analyze what went wrong? Yours truly, Sid

2 1

fetchurl with lxip socket in separate vfs
by Stefan Thöni 03 Aug '18

03 Aug '18

Hello Genodians, I noticed that after switching from 18.05 to 18.06 a fetchurl component using an lxip socket in a separate vfs component couldn't resolve hostnames any more. Resolving still works when the lxip sockets is in the vfs of the fetchurl component itself. Is there any change in 18.06 that might lead to this problem? Best regards Stefan -- Freundliche Grüsse Stefan Thöni Senior Security Architect +41 79 610 64 95 gapfruit AG Baarerstrasse 135 6300 Zug https://gapfruit.com

1 0

Definition of ram quota
by Jan Siddartha Hussmann 01 Aug '18

01 Aug '18

Hello Genodeans I was wondering what the difference is when stating how much ram a component gets. There is the attribute version like in runtime: <runtime ram="1000M" caps="2600" binary="init"> or int the deploy config: <start name="vm1" ram="3400M" pkg="insidioussid/pkg/vm_slice/2018-06-06" version="1"> However starting a package inside a runtime it usually is like this: <start name="ram_fs"> <resource name="RAM" quantum="2M"/> ... What is the reason for these two different versions? Kind regards, Sid

2 1

vfs_cow
by Roman Iten 30 Jul '18

30 Jul '18

Hello I created a vfs package archive containing vfs and vfs_cow and start it within the sculpt runtime providing the following configuration: <config> <vfs> <dir name="immutable"> <fs label="template_data"/> </dir> <dir name="mutable"> <fs label="user_data"/> </dir> <dir name="cow"> <cow ro="/immutable" rw="/mutable"/> </dir> </vfs> <default-policy root="/cow" writeable="yes"/> </config> Then, I changed the "target" file system of the noux package to use the above copy-on-write file system to play around with it... First thing I noticed is that the directories and files of "template_data" are not populated. I guess that's a feature that is not yet or will not be implemented and for my use case it doesn't bother me right now. But when I open/write a file (that exists in template_data), cow_vfs writes the following output: [runtime -> cow_fs] Warning: COW: block for replication... [runtime -> cow_fs] Warning: COW: block for replication... ...and never unblocks afterwards. If immutable is something like </ram> or </inline ...>, it works as I would expect it. Is this a known limitation? Or can someone point me to the right direction to solve it? I love the idea of the vfs_cow component and I guess it may cover many other use cases! Cheers, Roman

2 4

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users