users

users@lists.genode.org

2285 discussions

Sculpt EA On VirtualBox
by John J. Karcher 06 Mar '18

06 Mar '18

Hello, I have downloaded, built, and begun testing Sculpt EA, following the instructions linked to in the 18.02 release notes. Everything went well during the build process. Since I primarily run everything I do in VirtualBox (and don't have the recommended hardware anyway), I created a VM as close to the recommendations as possible. It booted fine from a virtual CD, the system came up using the VESA framebuffer driver, the mouse worked, and I was able to follow the instructions until I got to the part about storage. Unfortunately, there are no "<device>" nodes under "<block_devices>" in "/report/drivers/block_devices". I have the VM set up with a "SATA" controller and a single virtual drive. Has anyone tried this? Do you have any hints on how to diagnose what is going wrong? Also, I modified the config to use wired networking (using a virtual Intel-based NIC), but I couldn't think of a way to easily test whether it is working or not. (I'm sure I'm missing something obvious here, but I appreciate any hints.) If I can get those two items working, it looks like I'll be in good shape! Thanks, -- John J. Karcher devuser@...544...

2 5

RasPi 3 build problem
by Ken.Dickey 05 Mar '18

05 Mar '18

Greetings, I git cloned Genode, downloaded last version of tools, and am following the instructions in doc/getting_started.txt I seem to be close but am lacking usb. Tried both sel4 and foc. I am totally unfamiliar with the build tools. Can some kind person help me out? Thanks much, -KenD vvv======================================vvv ## Did: ## ./tool/ports/prepare_port foc ## ./tool/create_builddir rpi ## -- then uncommented 'libports' directive in etc/build.conf Linux:x86.64:/mnt/sda4/genode >>> make -C build/rpi KERNEL=foc run/demo make: Entering directory '/mnt/sda4/genode/build/rpi' including /mnt/sda4/genode/tool/run/boot_dir/foc including /mnt/sda4/genode/repos/os/run/demo.run building targets: core init drivers/timer server/nitpicker app/pointer app/status_bar app/global_keys_handler app/nit_focus server/liquid_framebuffer app/launchpad app/scout test/nitpicker server/nitlog drivers/framebuffer drivers/input server/report_rom server/rom_filter drivers/usb drivers/gpio drivers/platform spawn make core init drivers/timer server/nitpicker app/pointer app/status_bar app/global_keys_handler app/nit_focus server/liquid_framebuffer app/launchpad app/scout test/nitpicker server/nitlog drivers/framebuffer drivers/input server/report_rom server/rom_filter drivers/usb drivers/gpio drivers/platform make[1]: Entering directory '/mnt/sda4/genode/build/rpi' Error: target 'drivers/usb' does not exist Makefile:214: recipe for target 'error_missing_targets' failed make[1]: *** [error_missing_targets] Error 1 make[1]: Leaving directory '/mnt/sda4/genode/build/rpi' Error: Genode build failed Makefile:312: recipe for target 'run/demo' failed make: *** [run/demo] Error 252 make: Leaving directory '/mnt/sda4/genode/build/rpi' Linux:x86.64:/mnt/sda4/genode >>> uname -a Linux tranquil 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ^^^=======================================^^^

4 5

Bender and GRUB1 "legacy"
by Valery V. Sedletski 05 Mar '18

05 Mar '18

Hi, I tried to boot Genode scenarios from my bootable flash stick. It uses GRUB 1 "Legacy".Â Tried to boot Genode/Nova with bender with GRUB "legacy" (actually, GRUB4DOS). I have the following entries in menu.lst: titleÂ Sculpt scenario (Genode/Nova) kernel /genode/bender module /genode/hypervisor hypervisor iommu serial novpid novga module /genode/sculpt/image.elf image.elf This scenario just hangs when booting. Does this work with GRUB2 only? In GRUB2, I see loading the "multiboot2.mod" module. Is this a new version of Multiboot protocol? Could Bender work with older version of multiboot protocol? Or, is it possible to use Genode/Nova without Bender somehow with GRUB1? Also, is it possible for Genode build system to avoid assembling all modules into image.elf, so I could load them separately as multiple modules? (at least, older Genode versions did so) 10nx in advance! WBR, valery

4 19

keyboard/keymap issues
by Nobody III 05 Mar '18

05 Mar '18

In Sculpt, I have noticed 2 major keyboard issues: 1. The caps lock and shift keys are treated identically, which gives unexpected results (symbols instead of numbers) when a user types numbers with caps lock enabled. 2. The delete, end, and home keys don't work properly in bash. They are equivalent to typing the '~' character. Those keys work fine in vim, however.

2 1

Sculpt questions, briefly answered
by Norman Feske 05 Mar '18

05 Mar '18

Hello everyone, it's really great to see your interest in Sculpt! Hereby, I'd like to clarify a few things about Sculpt that were raised in the discussion. Question: Is any kernel supported other than NOVA? No. Please stick to NOVA because it is the only kernel used with Sculpt at Genode Labs. (this may change throughout the year) Question: How about using disk partitions? We deliberately left this topic out of the scope of Sculpt EA because it is not essential for a minimum-viable general-purpose setup. It goes without saying that Sculpt will support partitions down the road. You can use part_blk manually but it is not the official Sculpt path today. Question: Improving the detection of the default block device? The current heuristics is overly simplistic and of course not here to stay. Our current idea is to let the drivers subsystem scan the available block devices for one that hosts a partition with a magic label like "GENODE". Question: Do we plan to introduce any boot-time options? No. Genode's core has no boot-time arguments. User-provided configuration enters the picture at the level of the init component. Question: How to debug driver-related issues? If Sculpt does not run out of the box, please start experimenting with running simpler scenarios on your hardware first. E.g., Sculpt's drivers subsystem can be executed without the rest of Sculpt using the gems/run/driver_manager.run script, which - in contrast to Sculpt - outputs driver messages to core's LOG service that prints the message to the serial line. Question: What is the scope of features of the drivers subsystem? Since the drivers subsystem is not managed or configured by the user, it must stay as simple and generic as possible. Everything that can in principle be realized as part of the runtime subsystem should be part of the runtime, not the drivers subsystem. E.g., part_blk does not belong into the drivers subsystem. Question: What is the vision behind the Leitzentrale? Eventually, all actions that we perform manually via Noux as of today will become available via a graphical user interface. Under the hood, this user interface will "emulate" the user's manual interaction with the report and config file systems. Once all (common) boot-time operations are covered by the graphical user interface, Noux will be removed from the boot image. Question: How will the end result of Sculpt look like? We don't know. Sculpt EA is just a stepping stone that we use to explore the design space. 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

1 0

[SPAM] Sculpt scenario and block devices
by Tomasz Gajewski 04 Mar '18

04 Mar '18

After few glitches I've managed successfully boot Sculpt to the point where Leitzentrale console is working. It's interactive nature is really cool and makes me want to play with it further. I can see block devices reported in /report/drivers/block_devices but I have two disks so driver_manager is not marking any of my disks as default. Both disks are partitioned and I could give one partition exclusively to Genode to continue playing with it but not whole disk. Additionally I can see that usb storage devices are properly detected and reported so alternatively I could use a pendrive as storage for genode data. I think there are two possibilities to continue. First is to change Sculpt configuration during preparing image to match my configuration. Second is to change implementation of some component (?driver_manager?0 to be flexible enough to automatically handle all my devices: disks (ahci), partitions on disks (part_blk on ahci devices), usb drives (usb), partitions on usb drives and expose them. Later it should be possible to just select a block device which user would like to user for Genode. I'd like to try to work a little to make a second solution working (although probably I'll have to make the first (static) version working before making a dynamic one). I think that for each disk device (either ahci or usb) something should start part_blk for it, check if it properly detected partitions and expose them. Addtionally there should be a configuration option that could be easily set in some config that would make a specific block device a default one (instead of policy that marks it as default if there is only one device). I think you already have some vision how you plan to implement that part of system. Do you plan to extend driver manager implementation? Would such work be a good contribution? Or maybe you plan to reimplement this functionality in a less low level language? Nim? Tomasz Gajewski

3 3

VFS FIFO plugin
by Nobody III 02 Mar '18

02 Mar '18

I've started writing a (single-file) FIFO VFS plugin. I have gotten it to compile, but I still need a little help. How should I test my plugin? I'm not aware of a good run script to base a test on. How should I register signal handlers? I can use a list of List_element<Signal_context_capability>, but that requires extra dynamic memory allocations. How should I handle this to properly account for memory?

1 0

Sculpt not accepting input from touchpad
by Nobody III 02 Mar '18

02 Mar '18

When I run the Sculpt scenario on my laptop, the touchpad doesn't work, unlike in the old Turmvilla scenario. How can I fix this?

1 0

QProcess/QProcessEnvironment not declared
by Nobody III 01 Mar '18

01 Mar '18

I've been trying to port various Qt apps, including qt5ct, and I've run into errors such as "error: ‘QProcessEnvironment’ was not declared in this scope". I get that QProcess doesn't work on Genode, given its lack of fork() support outside noux, but why won't anything using QProcess or QProcessEnvironment compile, and how do I fix this?

2 1

Genode OS Framework version 18.02 released
by Norman Feske 28 Feb '18

28 Feb '18

Hereby, I proudly announce the release of Genode 18.02, which features the first revision of Sculpt OS, which is the Genode-based operating system that our team at Genode Labs has been using for several months now. For the release, we have taken the time to polish and document it so that like-minded people can join us with using and improving Genode day to day. Even though most topics of the release are closely related to Sculpt, many of them are interesting on their own account. The highlights are: - Sculpt for Early Adopters (EA) - On-target package installation and deployment - Improved networking stack - Support for servers written in the Nim language - VirtualBox version 5.1.32 - New trace-logging component - Ethernet-driver for i.MX-based Wandboard - SMP support for Xilinx Zynq hardware The complete release documentation is available at: https://genode.org/documentation/release-notes/18.02 I wish you a lot of fun with exploring the new release! 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

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users