users

users@lists.genode.org

2285 discussions

Re: Running Genode on a Raspberry Pi 3
by Simon Himmelbauer 06 Nov '20

06 Nov '20

Hi Stefan, > My first suspicion would be that u-boot and Fiasco.OC are using > different UART settings, e.g., the baudrate might be different. With > which baudrate do you connect to the serial line? I would expect > Fiasco.OC to use 115200. > > You could also try to find the place in Fiasco.OC/bootstrap where the > UART gets configured, and comment out any hardware access there, to > verify/falsify my idea. The UART is already configured properly by > u-boot, so Fiasco.OC should be able to send characters successfully > over serial line. Thanks, I will try this once I have slightly more time. Noteworthy, the UART is indeed configured to 115200. I have also tried to directly launch the image from the Pi to compare the output on a regular HDMI-screen. However, in this case, I receive no output at all after booting the image in uboot so I am not sure whether the source of the error is really the UART. Best regards, Simon On 05.11.20 12:00, users-request(a)lists.genode.org wrote: > Send users mailing list submissions to > users(a)lists.genode.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.genode.org/listinfo/users > or, via email, send a message with subject or body 'help' to > users-request(a)lists.genode.org > > You can reach the person managing the list at > users-owner(a)lists.genode.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of users digest..." > > > Today's Topics: > > 1. Re: Running Genode on a Raspberry Pi 3 (Stefan Kalkowski) > 2. Re: partial free/split for ds (Christian Helmuth) > 3. Re: partial free/split for ds (Alexander Tormasov) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 4 Nov 2020 13:10:40 +0100 > From: Stefan Kalkowski <stefan.kalkowski(a)genode-labs.com> > To: Genode users mailing list <users(a)lists.genode.org> > Subject: Re: Running Genode on a Raspberry Pi 3 > Message-ID: <20201104121040.43fbqvh3yju4mwp3(a)genode-labs.com> > Content-Type: text/plain; charset=utf-8 > > Hello Simon, > > On Wed, Nov 04, 2020 at 11:54:01AM +0100, Simon Himmelbauer wrote: >> Hi Genodians, >> >> I am trying to get a Genode image using the Fiasco.OC-kernel running on an >> RPi 3. I created an arm_v8a build directory and accordingly set the KERNEL >> and BOARD variable. I also compiled a u-boot image from the upstream >> repository. >> >> When I attempt to boot the image from the u-boot prompt, I receive the >> output below with no further reaction. I am still on Genode 19.05 because of >> a few modifications so I unless there is no other solution, I would like to >> avoid upgrading to a newer version. >> >> I also tried to run a few L4Re images provided here [0] with the same >> result, so the problem might not even be specific to Genode. >> >> Does anyone else have experiences with running on an RPi 3? Is there >> anything I am missing here? > My first suspicion would be that u-boot and Fiasco.OC are using > different UART settings, e.g., the baudrate might be different. With > which baudrate do you connect to the serial line? I would expect > Fiasco.OC to use 115200. > > You could also try to find the place in Fiasco.OC/bootstrap where the > UART gets configured, and comment out any hardware access there, to > verify/falsify my idea. The UART is already configured properly by > u-boot, so Fiasco.OC should be able to send characters successfully > over serial line. > > Regards > Stefan > >> Best regards, >> >> Simon >> >> [0] https://l4re.org/download/snapshots/pre-built-images/arm64/ >> >> U-Boot 2021.01-rc1-00243-g7a8ac9df5d (Nov 04 2020 - 01:56:08 +0100) >> >> DRAM: 948 MiB >> RPI 3 Model B (0xa22082) >> MMC: mmc@7e202000: 0, sdhci@7e300000: 1 >> Loading Environment from FAT... *** Warning - bad CRC, using default >> environment >> >> In: serial >> Out: vidconsole >> Err: vidconsole >> Net: No ethernet found. >> starting USB... >> Bus usb@7e980000: USB DWC2 >> scanning bus usb@7e980000 for devices... 3 USB Device(s) found >> scanning usb for storage devices... 0 Storage Device(s) found >> Hit any key to stop autoboot: 0 >> U-Boot> fatload mmc 0 $loadaddr image.elf >> 3208480 bytes read in 137 ms (22.3 MiB/s) >> U-Boot> bootelf >> ## Starting application at 0x01000000 ^��Z��%��XE��TmyAEDMe�@�*`)5��R[qP�� >> ��?�RQ@��VRY��5� �R A!��y=AA!y5YE)�}AG@A�Ţ�A��ӉR >> >> >> _______________________________________________ >> Genode users mailing list >> users(a)lists.genode.org >> https://lists.genode.org/listinfo/users

2 1

Running seoul-disc script
by Parfait Tokponnon 06 Nov '20

06 Nov '20

Hello, I want to boot a guest OS from hard (rather than ram disc and I think the seoul-disc scenario is the best choice to start. When reading the following part of the script, > <config> > <policy label="seoul -> VirtualDisk 0" partition="5" writeable="yes"/> > <policy label="rump_fs -> " partition="4" writeable="yes"/> > </config> > I guess it expect to locate the guest OS boot disk on partition 5, but I cannot figure out what would be placed on partition 4. assuming the script generates the Genode image disk with 3 partitions. How is it supposed to work? Please, find attached the output log as well as the script files I used. -- Parfait T.

2 1

Reporting use-after-free type bugs in Genode.
by Piotr Tworek 05 Nov '20

05 Nov '20

Hello Genodians, I've recently stumbled upon a use-after-free bug in one of the Genode core base classes. I think I have a pretty good understanding of the problem and would like to fill a bug report with my findings. Given the potential security implications of UAF type bugs I'm not sure what it the best course of action here. Should I report this using github issue tracker which AFAIU will result in the report being public? Or is there some other way to report bugs like this? /ptw

2 2

fs_rom closing and re-opening watches
by Pirmin Duss 04 Nov '20

04 Nov '20

Hello Genodians While debugging an error int the watch implementation of lx_fs, I observed, that fs_rom often closes and re-opens the watch handles. Whenever the file is read, the watch is closed and then re-opened. This also happens, when the read was triggered by a watch notification from the file system. Is there a special reason for that? Or is this an oversight? In https://github.com/genodelabs/genode/issues/3897 Norman already stated, that fs_rom will probably undergo a rework to clean up some design issues he has spotted. If this is an oversight, I think it would be best to fix this when the rework is done. Best regards, Pirmin

2 2

SYS_ioperm aarch64
by Michael Grunditz 03 Nov '20

03 Nov '20

Hi! I am trying to bringup Genode/Linux on aarch64. I have ported the syscall*.S files. But many of the SYS_ defines areen't defined, SYS_ioperm for example. I checked with x86_64 and it built. In both x86_64 and aarch64 it isn't defined in toolchain or Genode. In system includes both platforms has a #Ifdef __NR_ etc. But neither of the systems define that. I am all confused! Michael

2 4

Hello from aarch64/linux
by Michael Grunditz 03 Nov '20

03 Nov '20

[init -> hello] Hello world Problems was two.. I accidental put Genode:log instead of Genode:raw in syscall headers. Seccomp call does crash. Still doesn't start from make run. Michael

2 3

Sculpt Falkon browser package update
by Christian Prochaska 30 Oct '20

30 Oct '20

Hello, an updated Falkon browser package is available now in the 'cproc' depot for Sculpt 20.08 and 20.09 (staging), which fixes some memory leaks and reduces the maximum number of open sockets to lower the chance of file descriptor exhaustion. Christian

1 1

RPCEmu on Genode
by Michael Grunditz 21 Oct '20

21 Oct '20

Hi I am working on getting the RPCEmu (RiscPC emulator) to run on Genode. I have a some problems , and will list some of them, 1) Graphics doesn't update without exposing it. I have used testnit as a base and uses blit function to push out pixels to screen. How can I make it redraw? 2) When trying ro use the JIT version Genode complains about non executable memory. Any idea what that might be? I use base hw on x86_64. Screenshot: https://twitter.com/QtARM/status/1316535724959727620 (real hw) Best regards Michael Grunditz

3 12

running virtualbox5 on genode
by fixed-term.peter.jacobi＠sojus-software.de 20 Oct '20

20 Oct '20

Greetings. My name is Peter new to Genode and just trying to run the vbox5_win10_64.run script, btw. any of the scripts in genode/repos/ports/run/ are giving me the same result. It seems that the building works fine but I get no kind of output. A help and some indication on my wrong'ings would be much apreciated. My execution command: make run/vbox5_win10_64 KERNEL=nova BOARD=x86_64 My "build.conf" file and the building output called "out" are attached. My work operating system is Linux Ubuntu 20.04. My goal, create an mikrokernel with genode-framework starting 2 linux Virtualbox applications creating a simple communication between them. Best regards, Peter

2 1

Suggestions for contributing
by Mihail Feraru 16 Oct '20

16 Oct '20

Hello everyone, I've recently asked my Operating Systems professor about an interesting project to contribute to, and he recommended Genode. After a glimpse of the docs and playing a little bit with the tutorial repo, it really got my interest. It would be great if any of you would like to guide me a little bit about how I could be useful to the project. Maybe there are good issues for a new contributor or any feature testing to be done, anything that you consider relevant. About me, I have a little bit of experience with kernel development as I've worked on a hobby kernel project. Regards, Mihail PS. I've seen this strange output message after running hello_tutorial: "17592186044415 MiB RAM and 8997 caps assigned to init" and it feels pretty wrong, maybe it's a bug.

3 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users