users

users@lists.genode.org

2 participants
2336 discussions

How to enable Virtualbox EFI firmware on sculpt
by Johannes Schlatow 22 Feb '19

22 Feb '19

Hi, I'd would like to boot my native Linux installation from within Sculpt using Virtualbox. First, let me briefly describe what I have done so far: I created a raw disk image that contains the relevant partitions (ESP, root and home), added the Block devices to the vfs of Virtualbox, and routed the Block sessions to the corresponding part_blk server. I also made the EFI firmware file available to Virtualbox. I created a vbox file and tested it on another Linux system. However, when using this vbox file on sculpt, I noticed that vbox does not respect the '<Firmware type="EFI"/>', i.e. neither my boot manager nor the UEFI shell appears. I had a look in the Genode repository and noticed that there is a vbox patch that removes (ifdef 0) the Nvram initialisation which is supposed to happen if the firmware type is EFI. Thus it appears that EFI support has been 'patched-out' from the virtualbox port. Is this intentional? Are there any major blockers that prevent us from using Virtualbox with some EFI firmware? Cheers Johannes

3 3

memory allocations problems on kernel sel4
by Pirmin Duss 20 Feb '19

20 Feb '19

Hello Genodeans I'm building a system similar to sculpt (a sub init for drivers, leitzentrale and runtime), that runs on iMX6. As kernel I use sel4. The static driver subsystem and the leitzentrale work without problems so far. At first init starts a ram_fs and a part_block. Then the following components should be started vfs, noux, and three chroot. This fails, as the runtime init can no longer allocate memory (see log below). The runtime init has a RAM quota of 360M and the components to start use about 120M. ... [init -> runtime] child "public_rw" [init -> runtime] RAM quota: 1896K [init -> runtime] cap quota: 68 [init -> runtime] ELF binary: chroot [init -> runtime] priority: 0 [init -> runtime] provides service File_system Error: static Genode::addr_t Genode::Untyped_memory::alloc_pages(Genode::Range_allocator&, Genode::size_t): allocation of untyped memory failed Warning: unexpected exception during PD-session creation [init -> runtime] Error: depot_rw: environment PD session denied (label="depot_rw", ram_quota=98304, cap_quota=13, diag=0) ... Kernel: Thread 'ep' died because of an uncaught exception [init -> runtime] Error: Uncaught exception of type 'Genode::Service_denied' [init -> runtime] Warning: abort called - thread: ep Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x100 [init] child "runtime" exited with exit value 1 Might this be related to the following messages we also see in the log? Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x40 The last number starts with 0x01 and increases as follows 0x02, 0x04, 0x10, 0x20, 0x40, 0x80, 0x100. Tests on base-hw did not show any allocation errors. Best regards, Pirmin

1 1

Sculpt w/ Visual Composition, outdated Debian URL
by baconicsynergy＠protonmail.ch 12 Feb '19

12 Feb '19

Greetings from Genode/NOVA on my new Thinkpad X250 :) Almost everything is working perfectly! I'm very excited about my new system. However, when I try to run the Debian installation, it fails to find the proper URL and nothing happens. What configuration file can I modify to fix this issue so I can point the URL in the right direction? Enthusiastically, Joel

3 3

genodians content
by Guido Witmond 11 Feb '19

11 Feb '19

Hi Genodians, I've written some pages[1] in the style of Nix-pills[2] but on the subject of Genode. Please review and give me your feedback. When its good enough, I ask Genode Labs to publish it on genodians. 1: https://github.com/gwitmond/genodian/ 2: https://nixos.org/nixos/nix-pills/index.html

2 2

Genodians.org BETA is live
by Josef Söntgen 30 Jan '19

30 Jan '19

Hello fellow Genodians, as already hinted to by Norman in the roadmap discussion, the Genodian's website [1] is now live. It is a federated microblogging platform operated by Genode Labs and running on a Genode system (it uses base-hw and runs within an KVM-based VM). All recipes needed for building the system image are available in the genodians.org repository [2]. [1] http://genodians.org [2] https://github.com/genodelabs/genodians.org The repository also contains the list of all authors whose content is aggregated and published on the website. For more information, e.g. how to participate, please look into the README file. Since there is probably one or the other rough edge left and we have not yet decided on a plan to replace the self-signed certificate, the current version should be treated as BETA - stuff is allowed to fall off :-). Regards Josef -- Josef Söntgen Genode Labs http://www.genode-labs.com/ · http://genode.org/

4 4

Amateur Radio
by Tyrell Jentink 30 Jan '19

30 Jan '19

Hello everyone, I am new to this mailing list, and to Genode generally; I will probably be doing most of my experiments in the near future with a Raspberry Pi, and I'm likely to be fairly quiet about it, but I haven't actually fired anything up yet. My background is with Linux, and I anticipate a bit of discomfort as I try to adapt to the Genode Way... My interest is largely in Amateur Radio; The Linux community has a long history of supporting Amateur Radio with protocol stacks (Such as AX.25) and both hardware and virtual Terminal Node Controllers in the kernel. There are also userland implimentations. Some of those run on Windows... some are open source... In other words, lots of code is out there... In various levels of loyalty to the Unix philosophy... Putting it in the kernel may have never made sense... And the "Genode Way" has value in organizing the complexity of the AX.25 networking stack, similar to how it separates the organization of the Ethernet stack... How much, if any, actually belongs in Genode and/or Sculpt OS is beyond me... It all probably deserves to be an installable package, rather than a core package... But it probably also benefits from Capabilities, as it will interface with hardware, so probably more than just an untrusted Linux instance... Fldigi also seems like it could benefit from being broken apart into smaller components, with a stronger capability based trust model... Or not, I really don't know... Anyway... I'm new... And I'm still trying to wrap my head around the "Right" way to think about these things... Are there any other hams out there interested in bouncing around ideas? 73, Tyrell Jentink, KD7TKJ

2 1

Genode on RPI
by Tomasz Gajewski 29 Jan '19

29 Jan '19

Hi, I'll try to quickly move discussion about rpi to new thread to not pollute thread about Roadmap 2019. Bob Stewart <robjsstewart(a)gmail.com> writes: > I'm working on implementing a base-hw kernel on a Cortex A53 platform > (not Rpi) which is what the Rpi 3x is based on. So, that means a > significant amount of work to convert from the existing Genode code > supporting the armv7 architecture to support the armv8 > architecture. I'm focused initially on only the aarch64 instruction > set, but will later add support for aarch32. This is a retirement > project for me so my progress is not driven by any great need and is > slow. After about six months of casual working I'm at the stage of > debugging a virtual memory translation table enhancements need to > support 64-bit memory (a new Level-0 table in the page table code in > lpae.h). The means all the assembly code changes required have been > made (and about 12 other areas of change) and I clean compile a from a > log run script. My plans did not include targetting 64 bit implementation as seems to be too big target for amount of time I can devote to it. I just wanted to fix/workaround some problems which I expected to find when dealing with device drivers - not earlier. And only trying to use code available in Genode already (so 32bit for ARMv7). If I correctly understand 32bit instruction set for ARMv8 should be compatible with ARMv7. Am I wrong with this assumption? > For debugging at this level, you really only have two choices: Either > delve into the ARM hardware debugging facilites (CoreSight) or insert > small pieces of code to poke variable values or a trace number into a > currently unused region of memory. Code like: > > using ull = unsigned long long; > ull volatile * debug_ptr = (ull *)0x91000600; > *debug_ptr = MAX_ENTRIES; > debug_ptr += 0x01; > *debug_ptr = BLOCK_SIZE_LOG2; > debug_ptr += 0x01; > > if your booting into uboot to start up, you can inspect the memory > region through uboots' md command. Breakpoints can be implemented with > the assembly code line: asm volatile("hlt #01\n"); . Objdump gives > you the assembly code listing if you need it. Do I correctly understand, that I can go back to u-boot after running Genode with 'hlt #01' and analyze content of memory there? I would be surprised but definitely it would be useful. > I sincerely hope Genode does not implement a version of the Linux > DT. It is an error prone approach developed many years ago in the > embedded world. There are more elegant, syntax checkable, > configuration description approaches available today. Could you give some hints about those alternatives? I have no experience in this area and what seems to be tempting in device tree is that when you look into linux sources there are already dts files for all flavours of RPI including mine. U-boot uses this too - I wanted to use source from this due to smaller amount of code but that probably doesn't matter much. > Let me know if I can help with any compile/link issues you have, I > probably came across most of them in my work to-date. I'm using a > Linaro tool chain for aarch64. There is a separate one for aarch32 > which I don't currently use. Currently my "problem" is that my RPI doesn't pass through marked line in crt0.s /***************************************************** ** Setup multiprocessor-aware kernel stack-pointer ** *****************************************************/ mov sp, #0 /* for boot cpu use id 0 */ --> cps #31 /* change to system mode */ .global _start_setup_stack /* entrypoint for all cpus */ _start_setup_stack: I think it is due to RPI firmware is leaving processor in HYP mode - not SVC. But currently this is all I know. I tried to put code from FOC that is used switch processor back to SVC mode but as I don't understand details of it yet something is not working. There is some similar code in Genode implementation for Arndale board. On the other hand - maybe running in HYP mode is what is better for Genode? Some hints? If I comment out section with 'cps #31' it goes further and I it does not return from 'Bootstrap::Platform & p = Bootstrap::platform();' in 'extern "C" void init()' and last place which I found that is executing is constructor: Bootstrap::Platform::Board::Board in 'repos/base-hw/src/bootstrap/spec/rpi/platform.cc' I'll try to find out more and ask more specific questions about this part. Tomasz Gajewski

4 15

Amateur Radio
by Tyrell Jentink 29 Jan '19

29 Jan '19

1 0

target 'lib/ld/linux' does not exist
by Wouter van Oijen 28 Jan '19

28 Jan '19

Hi, When I try to run a scenario with "KERNEL=nova" on platform "linux", in most cases I get the following error: Error: target 'lib/ld/linux' does not exist Does anybody know what causes this and how I can resolve this error? (NB: I'm currently working with Genode 18.08 on Ubuntu 16.04.10) Kind regards, Wouter van Oijen

2 3

Networking under linux platform
by Chris 28 Jan '19

28 Jan '19

Dear Genodians, I have been successfully playing around with Networking in the 16.XX releases using the linux_x86 platform as a target. My genode instance used to run in a Ubuntu 14.04 LTS VM with a Windows host. Despite the "creative" setup, the tun/tap setup bridged with one of the VM's adapters worked like a charm. After a jump to 18.11, using the linux platform as a target, I am experiencing troubles with the linux_nic_drv: The creation the driver component seems to fail during the creation of the file descriptors for its dataspaces: lx_mmap in _map_local fails with 22 (EINVAL) (see attached console output from the lwip_lx example). I tested under Ubuntu 14.04 LTS in my old build environment as well as on a vanilla 16.04 LTS with a freshly installed genode toolchain & the current master. Other examples, such as the demo scenario, run without any problems. I have found an older discussion on the list from 2014 about failed memory mappings, but the thread ended without coming to a real conclusion. I'd be more than glad for any idea what where to look for possible reasons for this behavior. Best regards, Chris ======= console log, for run/lwip_lx =========== using 'core-linux' as 'core' using 'linux_timer_drv' as 'timer' using 'ld-linux.lib.so' as 'ld.lib.so' spawn ./core Genode 18.11-117-ged65267 <local changes> 17592186044415 MiB RAM and 8998 caps assigned to init [init] parent provides [init] service "ROM" [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: 776K [init] cap quota: 68 [init] ELF binary: timer [init] priority: 0 [init] provides service Timer [init] child "linux_nic_drv" [init] RAM quota: 3848K [init] cap quota: 68 [init] ELF binary: linux_nic_drv [init] priority: 0 [init] provides service Nic [init] child "test-lwip_httpsrv" [init] RAM quota: 4872K [init] cap quota: 68 [init] ELF binary: test-lwip_httpsrv [init] priority: 0 [init -> linux_nic_drv] Error: _map_local: lx_mmap failed(addr_in=0x0, addr_out=0xffffffffffffffea/-22) overmap=0 [init -> linux_nic_drv] Error: LD: exception during program load: 'Genode::Region_map::Region_conflict' [init -> linux_nic_drv] Error: Uncaught exception of type 'Genode::Region_map::Region_conflict' [init -> linux_nic_drv] Warning: abort called - thread: ep Warning: blocking canceled in entrypoint constructor [init] child "linux_nic_drv" exited with exit value 1 [init -> test-lwip_httpsrv] Error: LD: symbol not found: '_nsyyin' [init -> test-lwip_httpsrv] Error: Uncaught exception of type 'Linker::Not_found' [init -> test-lwip_httpsrv] Warning: abort called - thread: ep [init] child "test-lwip_httpsrv" exited with exit value 1 [init] child "timer" announces service "Timer"

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users