users

users@lists.genode.org

1 participants
2310 discussions

For Nova under VirtualBox I get that error
by Paul Dufresne 20 Sep '16

20 Sep '16

NOVA Microhypervisor v7-23e7882 (x86_32): Aug 29 2016 10:39:41 [gcc 4.9.2] [ 0] CORE:0:0:0 f:4:9:4 [0] Intel(R) Celeron(R) CPU 2.66GHz [ 0] Killed EC:0xc23ca160 SC:0xc23cb100 V:0x6 CS:0x8 EIP:0xc000002c CR2:0x0 ERR:0x0 (EXC) paul@...445...:~$

3 7

random number generator
by Claudius Laumanns 19 Sep '16

19 Sep '16

Dear Genode Devs, i have been system building (playing around) with genode for some times, when the following question came up: Where can i get random numbers from in genode? Do you use a hardware random number generator? Which one? Best regards Claudius P.S.: Your tool chain binaries are not signed. -- -------------------------------------------------------------------------------------------------- Claudius Laumanns Mac Help & Cloud Team, Arbeitsgruppe "Anwendungs- und Informationssysteme" Tel.: +49 551 201-1881, E-Mail: claudius.laumanns@...447... -------------------------------------------------------------------------------------------------- Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen (GWDG) Am Faßberg 11, 37077 Göttingen, URL: http://www.gwdg.de Tel.: +49 551 201-1510, Fax: +49 551 201-2150, E-Mail: gwdg@...447... Service-Hotline: Tel.: +49 551 201-1523, E-Mail: support@...447... Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen, Handelsregister-Nr. B 598 -------------------------------------------------------------------------------------------------- Zertifiziert nach ISO 9001 --------------------------------------------------------------------------------------------------

2 1

Writing sel4.iso on a CD/DVD vs. on an USB key
by Paul Dufresne 18 Sep '16

18 Sep '16

At first I had burned sel4.iso on a CD, but no computer was able to boot from it. Then rereading the instructions, I saw it was asked to DD it to an USB key, which I did, and was getting much better results: a grub menu that disappears so fast that it only goes to loading the first module, then the boot module. I kind of know that sectors on CD are supposed to be 2k in size, and 0.5k on most other mediums, like USB key normally... I think. I know Linux distribution can often be put on both DVD and USB keys without thinking much. Why (is?) Genode would be different?

2 2

some error of sel4.iso on VirtualBox (1495Mo)
by Paul Dufresne 18 Sep '16

18 Sep '16

Because I have only 2GB, I had to lessen the memory in the virtual machine to 1495 Mo. Then I get some error, that I was able to capture by redirecting COM1 to /tmp/sel4 file: [some parsing cut ... ask if needed] Kernel loaded to: start=0x100000 end=0x147000 size=0x47000 entry=0x10003e ACPI: RSDP paddr=0xe0000 ACPI: RSDP vaddr=0xdfce0000 ACPI: RSDT paddr=0x5d6f0000 ACPI: RSDT vaddr=0xdfef0000 ACPI: MADT paddr=0x5d6f0240 ACPI: MADT vaddr=0xdfef0240 ACPI: MADT apic_addr=0xfee00000 ACPI: MADT flags=0x1 ACPI: MADT_ISO bus=0 source=0 gsi=2 flags=0x0 ACPI: MADT_ISO bus=0 source=9 gsi=9 flags=0xd ACPI: MADT_APIC apic_id=0x0 ACPI: MADT_IOAPIC ioapic_id=1 ioapic_addr=0xfec00000 gsib=0 ACPI: 1 CPU(s) detected Detected 1 CPUs. Only just 1 Detected 1 boot module(s): module #0: start=0x1c2000 end=0x65f77a0 size=0x64357a0 name='/image.elf' ELF-loading userland images from boot modules: size=0x6435000 v_entry=0x2000000 v_start=0x2000000 v_end=0x8435000 p_start=0x65f8000 p_end=0xca2d000 Moving loaded userland images to final location: from=0x65f8000 to=0x147000 size=0x6435000 PCI: Detected device @ bus=0x0 dev=0x0 fun=0x0: vid=0x8086 did=0x1237 type=normal PCI: Detected device @ bus=0x0 dev=0x1 fun=0x0: vid=0x8086 did=0x7000 type=normal PCI: Detected device @ bus=0x0 dev=0x1 fun=0x1: vid=0x8086 did=0x269e type=normal PCI: BAR[4] ignored: PCI IO space not supported PCI: Detected device @ bus=0x0 dev=0x2 fun=0x0: vid=0x80ee did=0xbeef type=normal PCI: BAR[0] address=0xe0000000 size=0x1000000 PCI: Detected device @ bus=0x0 dev=0x4 fun=0x0: vid=0x80ee did=0xcafe type=normal PCI: BAR[0] ignored: PCI IO space not supported PCI: BAR[1] address=0xf0000000 size=0x400000 PCI: BAR[2] address=0xf0400000 size=0x4000 PCI: Detected device @ bus=0x0 dev=0x7 fun=0x0: vid=0x8086 did=0x7113 type=normal Starting node #0 Caught cap fault in send phase at address 0x0 while trying to handle: user exception 0x6 code 0x0 in thread 0xff7e0900 "rootserver" at address 0x200b78f With stack: 0x28026ec: 0x20a3854 paul@...445...:/tmp$ Is it a fancy way to say I am missing memory, or is it more serious (real CPU is a Celeron D)?

1 1

EDID (interrogating the monitor for display modes supported) support
by Paul Dufresne 18 Sep '16

18 Sep '16

On some real x86 hardware, I have seen the monitor say that it does not support the video mode generated by Genode. Am I right to suggest that vesa driver does not yet use EDID? Or is it a more complicated issue (here using rv516 ATI video card). On archive ( https://sourceforge.net/p/genode/mailman/message/33088931/ ) it seems to suggest it is harder for laptops than on a box, although up to date for me it has been the reverse (until now, I was only able to see the screen on one laptop ... out of 3 laptops and 2 boxes).

1 0

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

VirtualBox on Genode
by Yevgeny Lavrov 10 Sep '16

10 Sep '16

Hello I'm currently trying to reproduce VertualBox with Tinycore Linux running on top of NOVA hypervisor scenario on x86-64 hardware. The steps I've taken so far are: 1) ./tool/ports/prepare_ports for nova and virtualbox 2) ./tool/create_builddir nova_x86_64 3) uncommented REPOSITORIES += $(GENODE_DIR)/repos/libports line in <Genode-dir>/build/nova_x86_64/etc/build.conf 4) Downloaded Tinycore Linux .iso image Questions: 1) Where should I put Tinycore Linux .iso file? It says save it as bin/test.iso in the similar thread "running VirtualBox on Genode" on Genode mailing lists. Is it <Genode-dir>/build/nova_x86_64/bin directory that gets created after executing make run/demo? 2) Where should I add "<config><image type="iso" file="/iso/test.iso"/></config>" ? 3) Where to execute make run/virtualbox? I assume it's my build directory. However, executing it in my build directory results in Error: no run script for virtualbox. Please advise Thank you

3 7

Basic ISO Boot to Command Prompt
by Chris Rothrock 09 Sep '16

09 Sep '16

I am trying to build the most basic Genode build that creates a bootable ISO image that, once booted, brings me to a command prompt and outputs to a screen, not to a serial connection. I'm fairly familiar with the build process and I have made numerous demo builds work from within qemu but I am trying to make a stand-alone bootable image. So far I am only getting the boot loader message where the kernel loads (in this round I am simply using the Nova hypervisor but any kernel is fine for my demo boot). What am I missing to make this happen? Chris -- Thank You, Chris Rothrock Senior System Administrator (315) 308-1637

2 4

Partitioned Scheduling
by Edinger, Stefan 05 Sep '16

05 Sep '16

Hi, we are using Genode on Fiasco.OC and want to use different Scheduler for different CPU-Cores. Is there a way to assign a Scheduler to a CPU-Core in Genode? Thank you Stefan Edinger

3 2

Segfault when calling (Cancelable)Lock.unlock?
by Menno Valkema 31 Aug '16

31 Aug '16

Hi Everyone, I'm currently using a Nic_connection to exchange data data between components on linux_x86. Before sending data from the Nic server I first check whether any data can be freed. Even before the first packet is send out, using the code below: while ( _rx.source()->ack_avail() ) { _rx.source()->release_packet( _rx.source()->get_acked_packet() ); } Whenever I'm sending data out from an extern "C" method (callback passed to a c library), the application crashes. Looking with GDB, the issues seems to be with the destructor of the lock guard from the code from packet_stream.h (full GDB output at the bottom of this email). bool ready_for_rx() { Genode::Lock::Guard lock_guard(_rx_queue_lock); return !_rx_queue->empty(); } The destructor of the Guard simply calls the unlock method for the lock. However this crashes. Could it be that the unlock method throws an exception in the destructor, or that there might be uninitialized variables within the lock itself? I'm sort of lost here, because I've used the Nic_connection in similar settings in the past (also called from an extern "C" context as a c code callback). However this time it consistently breaks, whenever I try to sent out the first packet from an extern "c" context (it does work when sending the packet out from normal c++ code. Any suggestions what might causes the crash in my application? Cheers, Menno Program received signal SIGSEGV, Segmentation fault. 0x0000000001143c22 in ~Lock_guard (this=<optimized out>, __in_chrg=<optimized out>) at <project-path...>/repos/base/include/base/lock_guard.h:42 42 ~Lock_guard() { _lock.unlock(); } (gdb) bt #0 0x0000000001143c22 in ~Lock_guard (this=<optimized out>, __in_chrg=<optimized out>) at <project-path...>/repos/base/include/base/lock_guard.h:42 #1 ready_for_rx (this=<optimized out>) at <project-path...>/repos/os/include/os/packet_stream.h:400 #2 ack_avail (this=<optimized out>) at <project-path...>/repos/os/include/os/packet_stream.h:686 ....

2 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users