users

users@lists.genode.org

2 participants
2322 discussions

Cache invalidation issue on arm
by Tomasz Gajewski 13 Mar '19

13 Mar '19

Hi, during my attempts to make framebuffer driver working on rpi3b+ I had problems with memory caching. Effect was that I received from gpu information that result message was processed but couldn't see results - read memory always contained content of message and not response. Before I found a simple fix - ask dataspace for an uncached memory - I tried to call 'Kernel::update_data_region' but it didn't work for me. During my experiments I tried to dump memory from 'Kernel::Thread::_call_update_data_region()' for virtual address range passed to this function and it worked. In that function there is a comment that states that kernel operates in different address space than the caller for threads other than core. In that case different method of cache invalidation was called: 'clean_invalidate_data_cache', that should invalidate all cache. For core threads 'clean_invalidate_data_cache_by_virt_region' was used. Successfully dumping memory passed to _call_update_data_region() (using virtual address) made me think that a comment there about address spaces is wrong and - as an attempt to see what happens - I changed code to always call invalidating memory for given region only. This change [1] resolved issues with not seeing responses from gpu regarding framebuffer setup. If I'm not mistaken then: 1. Comment in 'Kernel::Thread::_call_update_data_region()' is not true anymore and code can be changed to always call more efficient version that invalidates always only cache for region of memory. 2. 'clean_invalidate_data_cache' is not working on rpi3b+ properly. I wouldn't be really surprised as I used code from Cortex A15, available already in Genode, without checking if Cortex A53 requires a different code (even for AArch32 mode). Please give me information if kernel is now mapped into every address space (as is stated in the aforementioned comment as a future goal) and my change is a correct one. If it is not the case can you provide some other possible explanation of this? Tomasz Gajewski PS. As a minor addtion I found a trivial function documentation bug that I fixed in [2]. [1] https://github.com/tomga/genode/commit/5a5adc06d9889129f2f1efd9a36be0ef52bb… [2] https://github.com/tomga/genode/commit/f25fad3c2957b843b549665cd7bcb50bec1d…

2 2

Porting Node.js
by Max 12 Mar '19

12 Mar '19

Hi, Genodians! I want to port Node.js for Genode OS, but I understand that it is not a simple matter. Maybe someone has already started to do this work and I would connect to this process. If answer is NO, then maybe someone will tell something sensible (for a starting point, I familiarized myself with information described at https://genode.org/documentation/developer-resources/porting_noux_packages). I would be very grateful for any useful information. Thanks!

3 2

Genode (x86_64) reboots on Thinkpad T420
by Valery V. Sedletski 10 Mar '19

10 Mar '19

Hi, Genodians! Some days ago, I ordered a Thinkpad T420, which is listed in Genode unofficial HCL by cnuke. I set up Genode booting remotely via PXE+Intel AMT. It boots the system image (x86_32 arch) just fine on real hardware. But if I try booting an x86_64 image, it reboots on most kernels, or traps on Fiasco.OC. Last messages in the log I see are from "bender" [1]. This is when booting using NOVA kernel. If I try Fiasco.OC as a kernel ([2]), It goes until "bootstrap", and last I see in the log are "bootstrap" messages, until it attempts to start the kernel. And at the same time, I see the following trap screen from bootstrap: [3]. All registers are zeroes, except a few ones. So, with "foc" kernel, I see a Trap #0 (division by zero). In case of "NOVA" and "base-hw" kernel, it does not trap, but just reboots. I tried to remove the "novga" parameter from NOVA kernel, but I still see a blank screen. BIOS memory map is here: [4], [5] Looking at the memory map, I don't see any memory holes at the same place where modules were loaded. Any ideas? [1] Boot log with NOVA kernel: sculpt64-nova.log (attached) [2] Boot log with Fiasco.OC kernel: sculpt64-foc.log (attached) [3] A trap screen from bootstrap, Fiasco.OC kernel: ftp://osfree.org/upload/img/20190307_004.jpg [4] BIOS memory map (part 1): ftp://osfree.org/upload/img/20190307_001.jpg [5] BIOS memory map (part 2): ftp://osfree.org/upload/img/20190307_002.jpg WBR, valery

2 6

Problems with some partitions detection/mounting
by Valery V. Sedletski 10 Mar '19

10 Mar '19

Hi again! Also, in addition to problems described in my previous letter, I have two other ones (I can install Sculpt to a flash stick, though, so this is not so big problem): 1) Sculpt boots (only with x86_32 case, so far) fine until the desktop, it detects my Intel Gigabit LAN and Intel wifi just fine, and the network interface is up and assigned an IP. Also, it correctly detects the size of my 750 GB hard disk (actually, 698 GB, because 1 GB == 1024^3 bytes, not 1000^3 bytes). But the Leitzentrale lists only first three partitions, not all ones (see the screenshot below). My hard disk partitioning scheme is the following: [1]. The 1st primary partition is a 64 GB FAT32 partition. I tried to use it as a Genode partition, but Sculpt has problems mounting it, for some reason. The extended partition contains the following logical partitions within it: 1) a 3 GB HPFS partition with OS/2 2) another 3 GB HPFS partition (empty) 3) a 420 GB JFS partition, shared by OS/2 and Linux 4) 40 GB Linux swap partition 5) a 55 GB Linux ext3 partition 6) a 10 GB BeFS Haiku partition 7) a 90 GB freespace [2] is the Sculpt log (I commented-out the routing rules in the config file, so all logs go to the Core LOG service) [3] is the Sculpt screenshot when loaded, LAN interface up, and there was an attempt to mount a FAT32 partition. So, there are two problems: 1) Sculpt fails to mount a FAT32 partition 2) part_blk seems to detect not all existing partitions. The hard disk is a Seagate with a 4096 bytes physical sector, though, it is not aligned at 4096-byte boundary, but aligned on a cylinder boundary (which is a requirement for OS/2). So, I'd suspect some alignment problems here. Also, hard disk geometry in partition table is 127 sectors per track, 255 heads, -- maybe this could cause some problems too? Though, several OS'es had no problems seeing and mounting partitions. I tried Linux, OS/2, Haiku, KolibriOS, ReactOS, WinXP -- all these have no problems with seeing or mounting partitions. So, any help would be appreciated. [1] Hard disk partitioning: ------------------------------------------------------------ Disk /dev/sda: 698,7 GiB, 750156374016 bytes, 1465149168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xdf5ee156 Device Boot Start End Sectors Size Id Type /dev/sda1 * 127 134235824 134235698 64G c W95 FAT32 (LBA) /dev/sda4 134235825 1271305559 1137069735 542,2G 5 Extended /dev/sda5 134235952 140550899 6314948 3G 7 HPFS/NTFS/exFAT /dev/sda6 140551027 146865974 6314948 3G 7 HPFS/NTFS/exFAT /dev/sda7 146866102 1054131749 907265648 432,6G 7 HPFS/NTFS/exFAT /dev/sda8 1054131877 1136065799 81933923 39,1G 82 Linux swap / Solaris /dev/sda9 1136065927 1250314596 114248670 54,5G 83 Linux /dev/sda10 1250320207 1271305559 20985353 10G 7 HPFS/NTFS/exFAT ------------------------------------------------------------ [2] Sculpt boot log: sculpt-nova32.log (attached) [3] A screenshot when booted: ftp://osfree.org/upload/img/20190308_001.jpg WBR, valery

2 2

Window Manager help
by Joel Desermeau 08 Mar '19

08 Mar '19

Hello friends :) Working on Sculpt CE with framework version 19.02. I've got Debian downloaded but I'm doing a terrible job of getting it to run. Running without any window manager has the Debian install boot up but I can't interface with it at all. So Im guessing I need to build my GUI software stack before it will work. I just have no idea where to begin! It was all done almost automatically with Sculpt VC. Can anyone show me how to properly setup the window manager so I can properly run vbox5-nova-sculpt? Joel

3 3

Window Manager help
by Joel Desermeau 08 Mar '19

08 Mar '19

Thank you Dr. Feske for helping me get used to the new system :) I appreciate it a lot. I've got Debian up and running and I'm getting myself excited for a new year of Genode. I have been using Genode as my primary operating system for several weeks now! What new programs should we expect to be able to run natively in Genode in the near future? What kind of obstacles would be needed to overcome before Firefox can run natively in Genode? Also, I am unable to get your vbox5-nova-sculpt depot pkg to run on my system. It doesn't boot up anything and the last error message is "Error: SystemPropertiesWrap : Cannot determine default Guest Additions ISO location. Most likely they are not available" Anyway, I'm really happy with everything on my system! Joel Desermeau

2 1

Wish List
by Joel Desermeau 07 Mar '19

07 Mar '19

Is there an existing program/feature request list for Genode? What would all of you like to see on the list? I personally would like to see a way to store, organize, and read my ebooks :) My next would be an audio player but that's already planned for later this year! I can't wait to see Genode Sculpt evolve

3 2

port patches
by Nobody III 05 Mar '19

05 Mar '19

Is there a standard method/tool for easily generating patches for ports?

2 1

Version release 19.02 fixes my problem :) Leaves me with a question...
by baconicsynergy＠protonmail.ch 01 Mar '19

01 Mar '19

I was successfully able to build a new sculpt disk image based on 19.02 :) Erased my VM and am starting from scratch again. What should I choose for my File System (Target) for cnuke's Download Debian procedure?

2 1

Genode on RPI - second round
by Tomasz Gajewski 28 Feb '19

28 Feb '19

Hi to all. In my last message I wrote: "Now I'm starting again from start but with different knowledge level." and now I have some preliminary results and another set of issues/questions. After making run/log work on single core I had two possible directions to take: device drivers or enable smp. I started with smp as with the device drivers I need an advice about build system (later in this email). For SMP on RPI I implemented new timer driver as the current one was not capable to support multiple independent timers for cores and new PIC driver - for timer and inter processor interrputs. Current code is in (rewritten) same branch as previously at [1] in case you wanted to look. run/smp test is almost working on all cores with the exception for thread cleanup (which will be another question later in email). 1. Register sets. On multicore Raspbery Pi there are sets of registers in which each register has the same structure and each is "assigned" to different core. Currently I replicated definitions of registers for each core [2] but it's obviously not a good solution. Additionally it forces to write ugly code when cpu_id is in the variable as in [3]. Is there some support in Genode for such structures? If not, do you see how that could be implemented? Some wrapper for Register? I fail to see how dynamic value of 'cpu_id' could be nicely mixed with register offsets passed as template arguments. I think ideally it would be to define something like this: struct CoreTIrqCtl : RegisterSet<0x40, 32, COUNT, OFFSET> and use it like this: write<CoreTIrqCtl>(CPU_ID, 0); Any thoughts? 2. Interrupts handling I have doubts about interrupts processing. I have limited knowledge in this area so I may be totally wrong but based on what I read for RPI I think that: a. On one IRQ there can be more than one interrupt flag marking an exception. During this one entry to 'Thread::exception(Cpu&)' and later to 'Cpu_job::_interrupt(unsigned const)' all pending interrupts should be handled in some loop. Without that some interrupts may stay unhandled. And I don't see such loop in this code. One exception is taken from Pic driver, handled and that's all. b. I don't know where clearing an interrupt should be handled. I would have thought that 'Pic::finish_request()' would be good for this, but there are many empty implementations. Should code in 'Pic::take_exception(...) also clear the exception condition? My doubts come from feeling that if I do this too early "something" can happen before handling of interrupt is finished. If 'finish_request()' is a proper place to clear interrupt as handled than it would be useful to pass to it interrupt number earlier returned from 'take_request'. Otherwise there would have to be separate storage for each core in Pic to store information about currently handled exception on a given core. Am I right? Does it work properly in [4]? 3. run/smp test hangs during threads destruction Like I wrote earlier run/smp test is almost working on multiple cores. It hangs somewhere in [5] during destructing thread running non-zero core (destroying first one does not cause problems). I don't have any concrete questions here. The only ones are: a. Does this test properly work on arndale? b. Do you have any thoughts what can go wrong? Maybe I haven't implemented something important for smp yet? Only timer and IPI? 4. Drivers reused for different configurations Currently to support RPI3 I created configurations named 'rpi3bplus'. How should I proceed to reuse a driver written for rpi? For example framebuffer driver has 'REQUIRES = rpi' in target.mk [6] and that causes that it does not compile for my 'rpi3bplus'. It would be nice to have: 'REQUIRES = rpi|rpi3bplus' but I don't think it is possible. Can you suggest something? Tomasz Gajewski [1] https://github.com/tomga/genode/tree/rpi3bplus [2] https://github.com/tomga/genode/blob/rpi3bplus/repos/base-hw/src/core/spec/… [3] https://github.com/tomga/genode/blob/rpi3bplus/repos/base-hw/src/core/spec/… [4] https://github.com/tomga/genode/blob/rpi3bplus/repos/base-hw/src/lib/hw/spe… [5] https://github.com/tomga/genode/blob/rpi3bplus/repos/base/src/test/smp/main… [6] https://github.com/tomga/genode/blob/rpi3bplus/repos/os/src/drivers/framebu…

3 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users