users June 2016

users@lists.genode.org

28 participants
30 discussions

Heeselicht scenario
by Stefan Kalkowski 11 Oct '16

11 Oct '16

Hello Genode folks, hereby, I'd like to announce my recent activity to turn the Turmvilla scenario published by Norman after last year's Hack'n'Hike into an USB live setup. Instead of the original variation, this scenario enables you to boot Genode natively from an USB stick on top of your favorite Intel x86 hardware. In parallel, you can execute your previous installed OS on disk inside a VirtualBox VM without further modifications. This setup offered me the opportunity to switch to Genode without the need to alter my current Linux working environment. Thinking that I'm not the only one that might be interested in such a setup, I've spent some time during our recent Hack'n'Hike in a nice old house in "Heeselicht" to facilitate the steps to reproduce this setup. If you are undaunted, and like to give it a try, you can have a look at the corresponding issue: https://github.com/genodelabs/genode/issues/2018 There are detailed instructions in the issue. For further assistance, leave a comment at the issue tracker or reply to this email. Regards Stefan -- Stefan Kalkowski Genode Labs http://www.genode-labs.com/ · http://genode.org/

1 1

booting the SABRE tablet from SD card
by Rijurekha Sen 13 Sep '16

13 Sep '16

Hi, I compiled the demo according to https://github.com/skalk/genode/blob/i.MX53_tablet_demo/os/src/server/vmm/i…. Next to run the demo in the SABRE tablet, I followed the instruction in http://genode-main.narkive.com/qJXUD6w5/arm-trustzone-demo-in-i-mx53-sabre-…. Created the u-boot.imx using https://eewiki.net/display/linuxonarm/i.MX53+Quick+Start#i.MX53QuickStart-B… for the step 2) 2) sudo dd if=$(U-BOOT-DIR)/u-boot.imx of=/dev/sdb seek=2 bs=512 conv=fsync But when I put in the MMC card in the tablet with the SD card in it and restart the tablet, it just powers on to the default Android which it came with. How to get the u-boot prompt, as mentioned in step 4)? 4) After power up the tablet, U-BOOT prompt (u-boot from MMC is not used), I did as follows: MX53-SMD U-Boot > ext2load mmc 0:1 0x70800000 image.bin How to get this u-boot prompt? https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0ahUKEwi… has a chapter 3 on various boot options. http://cache.freescale.com/files/32bit/doc/user_guide/IMX53SMDHUG.pdf shows the location of the switches sw26 and sw28 at the back of the board. Does that mean, I should open the back cover of the tablet to change these? Is this what http://genode-main.narkive.com/qJXUD6w5/arm-trustzone-demo-in-i-mx53-sabre-… did? Want to verify the correct thing to do as the tablet is expensive. Thanks! Riju

3 8

Session quota yielding
by Charles HH 05 Jul '16

05 Jul '16

Hi, I am currently using a Loader to deploy a subsystem, and in order to improve dynamism, I would like to implement resource trading between the Loader session client and the server. For resource requests, this is pretty straightforward using a notification and the upgrade session facility. However, I would also like the loader to be able to spontaneously yield resources when they are no longer needed. I looked at the yielding facility, but it seemed more focused on direct parent/child trading. Is there a way for a server to yield back resources to its clients symmetrically to the upgrading protocol, ideally that doesn't require modifying the parent interface? Regards, Charles

2 3

e1000 nic driver problem
by john stokes 01 Jul '16

01 Jul '16

i am trying to run l4linux on my x86 hardware but after commenting these lines l4linux boots fine. append_if $use_nic_driver config { <start name="nic_drv"> <resource name="RAM" quantum="3M"/> <provides><service name="Nic"/></provides> </start> } but i want the ethernet support my has no e1000 support it supports r8169 realtek driver i changed the e1000 from the l4linux.run to r8169 but it is showing errors . i have gone through many source codes related to nic_drv but i can't find where to change it can you please tell me how to add support for r8169 and the error is: Kernel: arch/l4/boot/Image is ready Building modules, stage 2. MODPOST 97 modules Program server/report_rom/report_rom Program core/spec/x86_32/core COMPILE version.o LINK core make[1]: `drivers/nic' is up to date. make[1]: `drivers/acpi' is up to date. make[1]: Leaving directory `/home/rishabh/genode-16.05/build/foc_x86_32' genode build completed Download initramfs ... using fiasco kernel /home/rishabh/genode-16.05/build/foc_x86_32/kernel/fiasco.oc/fiasco using sigma0/bootstrap at /home/rishabh/genode-16.05/build/foc_x86_32/l4 install bootloader creating ISO image... Warning: -follow-links does not always work correctly; be careful. Size of boot image is 4 sectors -> No emulation 79.64% done, estimate finish Thu Jun 30 19:27:48 2016 Total translation table size: 2048 Total rockridge attributes bytes: 3075 Total directory bytes: 10240 Path table size(bytes): 78 Max brk space used 22000 6283 extents written (12 MB) spawn qemu-system-i386 -no-kvm -m 160 -nographic -serial mon:stdio -smp 2,cores=2 -net nic,model=r8169 -net user -cdrom var/run/l4linux.iso qemu-system-i386: Unsupported NIC model: r8169 Aborting, received EOF Log step failed, retry. spawn qemu-system-i386 -no-kvm -m 160 -nographic -serial mon:stdio -smp 2,cores=2 -net nic,model=r8169 -net user -cdrom var/run/l4linux.iso -cdrom var/run/l4linux.iso qemu-system-i386: -cdrom var/run/l4linux.iso: drive with bus=1, unit=0 (index=2) exists Aborting, received EOF Log step failed, retry. spawn qemu-system-i386 -no-kvm -m 160 -nographic -serial mon:stdio -smp 2,cores=2 -net nic,model=r8169 -net user -cdrom var/run/l4linux.iso -cdrom var/run/l4linux.iso -cdrom var/run/l4linux.iso qemu-system-i386: -cdrom var/run/l4linux.iso: drive with bus=1, unit=0 (index=2) exists Aborting, received EOF Log step failed, retry. Boot process failed 3 times in series. I give up! make: *** [run/l4linux] Error 255

3 14

gdb_monitor not working on nova_x86_64
by Nobody III 01 Jul '16

01 Jul '16

I am planning on using gdb_monitor to debug components I write, but it doesn't seem to work. I have tried all the run scripts, and none of them succeed at attaching the debugger. I looked for any recent applicable commits in genodelabs/master, but none of them are more recent than the 16.05 release which my personal repo is currently based on. Here is the output from gdb_monitor.run: int main(): --- create local services --- int main(): --- start init --- int main(): transferred 86 MB to init [init] parent provides [init] service "ROM" [init] service "RAM" [init] service "IRQ" [init] service "IO_MEM" [init] service "IO_PORT" [init] service "PD" [init] service "RM" [init] service "CPU" [init] service "LOG" [init] child "timer" [init] RAM quota: 1863680 [init] ELF binary: timer [init] priority: 0 [init] provides service Timer [init] child "uart_drv" [init] RAM quota: 1863680 [init] ELF binary: uart_drv [init] priority: 0 [init] provides service Terminal [init] provides service Uart [init] child "gdb_monitor" [init] RAM quota: 3960832 [init] ELF binary: gdb_monitor [init] priority: 0 [init] child "timer" announces service "Timer" [init -> uart_drv] --- i8250 UART driver started --- [init] child "uart_drv" announces service "Uart" [init] child "uart_drv" announces service "Terminal" [init -> gdb_monitor] usinGDB monitor is up, starting GDB spawn /usr/local/genode-gcc/bin/genode-x86-gdb bin/ld.lib.so -n -ex target remote localhost:5555 -ex set interactive-mode off -ex b binary_ready_hook_for_gdb -ex c -ex delete 1 -ex file bin/test-gdb_monitor -ex b main -ex set solib-search-path bin -ex sharedlibrary -ex c -ex delete 2 2&>1 ----- test: breakpoint in 'main()' ----- g the pipe libc plugin [init -> gdb_monitor] int sigaction(int, const sigaction*, sigaction*): sigaction not implemented [init -> gdb_monitor] Process target created; pid = 1 [init -> gdb_monitor] unsupported ioctl (request=0x40047477) [init -> gdb_monitor] unsupported ioctl (request=0x80047476) [init -> uart_drv] Baudrate is not defined. Use default 115200 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/kingtux/genode/build/nova_x86_64/bin/ld.lib.so...[init -> gdb_monitor] Remote debugging using /dev/terminal [init -> gdb_monitor] fcntl(): command 4 args 66 not supported - terminal [init -> gdb_monitor] fcntl(): command 6 args 4294967295 not supported - terminal int main(): --- init created, waiting for exit condition --- done. Don't know how to attach. Try "help target". GDB can't read core files on this machine. localhost:5555: Connection timed out. Breakpoint 1 at 0xafd10: file /home/kingtux/genode/repos/base/src/lib/ldso/debug.cc, line 21. The program is not being run. Load new symbol table from "/home/kingtux/genode/build/nova_x86_64/bin/test-gdb_monitor"? (y or n) [answered Y; input not from terminal] Reading symbols from /home/kingtux/genode/build/nova_x86_64/bin/test-gdb_monitor...done. Breakpoint 2 at 0x1001678: file /home/kingtux/genode/repos/ports/src/test/gdb_monitor/main.cc, line 93. The program is not being run. (gdb) *** Error: Breakpoint in main() did not trigger Makefile:261: recipe for target 'run/gdb_monitor' failed make: *** [run/gdb_monitor] Error 255

2 2

TRACE API: trace identification
by Joscha Benz 30 Jun '16

30 Jun '16

Hi, im currently using genode's TRACE API to trace communication paths between multiple threads. For that to work properly I need to be able to map all corresponding trace events to each other. For example a RPC_CALL event to the corresponding RPC_DISPATCH event. The problem is as follows. Since a trace event is logged _before_ the related action is executed, it is possible that a thread is preempted between those two actions. In that case I'm unable to do the mapping just using the information provided by the TRACE API or am I missing something? Best regards, Joscha

1 0

multiboot l4linux and ubuntu
by john stokes 30 Jun '16

30 Jun '16

after building the l4linux using make run/l4linux i got the iso file of l4linux now i want to create a grub2 entry for l4linux along with ubuntu how should i do it? i have followed methods given on other places they all are distro specific i have also seen nova hypervisor multiboot mailing list doubt it is of not much help is there any way to use create_grub2 tool? my l4linux file is at <build-dir>/foc_x86_32/var/run/l4linux/boot <build-dir>/foc_x86_32/var/run/l4linux/genode <build-dir>/foc_x86_32/var/run/l4linux/fiasco <build-dir>/foc_x86_32/var/run/l4linux/boot/grub <build-dir>/foc_x86_32/var/run/l4linux/boot/isolinux <build-dir>/foc_x86_32/var/run/l4linux/boot/bender <build-dir>/foc_x86_32/var/run/l4linux/boot/grub/menu.lst contains following things timeout 0 default 0 title Genode on Fiasco.OC kernel /boot/bender module /fiasco/bootstrap module /fiasco/fiasco -serial_esc module /fiasco/sigma0 module /genode/core module /genode/config module /genode/init module /genode/timer module /genode/kdb_uart_drv module /genode/l4linux module /genode/initrd.gz module /genode/ps2_drv module /genode/fb_drv module /genode/nic_drv module /genode/platform_drv module /genode/acpi_drv module /genode/report_rom vbeset 0x117 506070

2 2

allocator out of memory error during creation of File_system::Connection
by Nobody III 30 Jun '16

30 Jun '16

I have been working on my fs_filter (vfs-like) component, and it compiles, but fails to successfully create a File_system::Connection. Even with a ram quota of 1G, I get the following error: Uncaught exception of type 'Genode::Allocator::Out_of_memory' What am I doing wrong? I have tried multiple different allocator configurations (e.g. Allocator_avl(sliced_heap), Allocator_avl(Genode::env()->heap()), Allocator_avl(0)), but nothing fixes or changes the error.

1 0

File_system signals
by Nobody III 30 Jun '16

30 Jun '16

In my fs_filter component (much like the vfs server), I am trying to allow multiple clients fast, non-blocking access to multiple filesystems. To do this without several threads, my component needs to know when each filesystem server unblocks so it can send more packets. Unfortunately, the File_system::Client interface (which File_system::Connection inherits) doesn't provide a way to receive signals when the server acknowledges packets or is ready for more packets, given that it only provides a Session:Tx::Source object for accessing the packet stream. The Session::Tx::Source interface provide the methods sigh_ack_avail() and sigh_ready_to_submit(), which allow a cilent to get the signal handlers currently in use, but doesn't allow registering new signal handlers. I added a workaround that exposes the Packet_stream_tx::Client object to the client, but it would be good to have a better way to register these signal handlers. Is there currently a way to do this, or does this require a modification to the API, like what I did?

2 2

error related to block device while running make run/l4linux
by john stokes 29 Jun '16

29 Jun '16

after doing make menuconfig and selecting block device support for l4linux so that when i boot it on real hardware the root file system can be mounted easily.but i am getting this infinite loop is there any solution for bloc device support ? [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users June 2016