users September 2018

users@lists.genode.org

20 participants
36 discussions

usb_drv error -92 for RPi | Genode 18.05 with Fiasco.OC 79
by Alexander Weidinger 18 Apr '19

18 Apr '19

Hello everyone, when executing 'lwip' on the RPi 2, I get the following output for the usb_drv: > [init -> usb_drv] dev_info: DWC OTG Controller > [init -> usb_drv] dev_info: new USB bus registered, assigned bus number 1 > [init -> usb_drv] dev_info: irq 9, io mem 0x00000000 > [init -> usb_drv] dev_info: USB hub found > [init -> usb_drv] dev_info: 1 port detected > [init -> usb_drv] dev_info: new high-speed USB device number 2 using dwc_otg > [init -> usb_drv] dev_error: device descriptor read/all, error -92 > [init -> usb_drv] dev_info: new high-speed USB device number 3 using dwc_otg > [init -> usb_drv] dev_error: device descriptor read/all, error -92 > [init -> usb_drv] dev_info: new high-speed USB device number 4 using dwc_otg > [init -> usb_drv] dev_error: device descriptor read/8, error -92 > [init -> usb_drv] dev_error: device descriptor read/8, error -92 > [init -> usb_drv] dev_info: new high-speed USB device number 5 using dwc_otg > [init -> usb_drv] dev_error: device descriptor read/8, error -92 > [init -> usb_drv] dev_error: device descriptor read/8, error -92 > [init -> usb_drv] dev_error: unable to enumerate USB device Does anyone have an idea what I can do, to get the Ethernet adapter working? Any help is appreciated! I don't really understand the problem here, since the driver works flawlessly for the RPi 1 B+ (using foc_rpi as platform) - which uses the same chip as the RPi 2 (SMSC LAN9514). My Genode version [2] and Fiasco.OC version [3]. To the backstory: ----------------- I am currently in the process of "porting" Fiasco.OC/Genode to the Raspberry Pi 2 (Model B). As a basis I use Genode in the version 18.05 and Fiasco.OC in the version 79. I created a new device, the rpi2, and based it on the already available rpi model. The main changes I did for the rpi2 platform [1] are - the different arm architecture - from armv6 to armv7a in a few files - the different physical base address - from 0x2000:0000 to 0x3f00:0000 - a RAM size of 1008 MB starting at 0x0000:0000 (1024 MB - 16 MB for peripherals) I use version 79 of the Fiasco.OC kernel since it adds support for the three different BCM283X platforms. In order to get version 79 of the kernel running with Genode, I used the official 79 as a basis and cherry-picked commits from Genode's version of Fiasco.OC (72). [0] My setup works completely fine for the RPi 1 (Model B+), even for the usb/nic driver. As the RPi 1 (Model B+) makes use of the SMSC LAN9514, instead of the SMSC LAN9512 (used in RPi Model B) it should also work for the RPi 2 (Model B), since this SBC also uses the SMSC LAN9514. [0] https://github.com/skalk/foc/commits/r72 [1] https://github.com/irgendwie/genode/commits/foc-rpi2 [2] https://github.com/irgendwie/genode/tree/foc-rpi2 [3] https://github.com/irgendwie/foc/tree/genode-r79-rpi2 ----------------- Best regards Alexander

5 15

Request for feedback about "Genode Component Public License"
by Norman Feske 16 Nov '18

16 Nov '18

Dear Genode community, today, I'd like to present an idea that developed over the past three years during discussions with various contributors and users about the prospect of a Genode-based business ecosystem. As you certainly know, Genode Labs pursues a dual-licensing business model, which allows us to fund the development of Genode as an independent team. Our licensing business is enabled by the combination of the AGPLv3 as a strong copyleft license with the library-like nature of Genode. Until today, this model is limited to our company. To foster a sustainable ecosystem around Genode, we wish to enable others to pursue a similar business model while maintaining the spirit of open collaboration and free software. We eventually crafted a new license called "Genode Component Public License" (Genode CPL) specifically for components developed by 3rd parties, outside of Genode Labs. Please find the rationale, license text, and FAQ under the following link (which is not officially reachable from the website yet): https://genode.org/documentation/articles/component_public_license Before I go forward with publicly announcing the article at genode.org, I would very much appreciate your feedback, in particular: * How does the rationale and approach given in the description resonate with you? * Do you see any potential for controversies or uncertainties? * If you are in the business of producing proprietary software, would the Genode CPL create an incentive to open up your products without putting your business at risk? I'm very much aware that licensing is a delicate topic. To avoid hot-heated controversies and mis-interpretation, I encourage everyone to carefully read the "Questions and Answers" Section of the article before commenting. I'm looking forward to your feedback! Best regards 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 1

memory size in tz_vmm
by lzSun 01 Nov '18

01 Nov '18

Hello, I am very interested in genode and I am working on tz_vmm demo using i.mx53-qsb board now. After the tz_vmm start, I find a boot message like this: " Genode 18.05 <local changes> 211 MiB RAM and 64535 caps assigned to init " To my understanding, it's present that the available memory that the genode os in secure world is 211MB. And After the system boot up, I use Top command to observe the memroy that normal world have which gives me like this: " Mem: 37956K used, 49444K free, 0K shrd, 68K buff, 26456K cached " This shows that the total memory the linux in the normal world can use is less than 150MB. And I have some questions about this: 1. Can this memory size be increased? For example, I want to increase the memory size that genode can use. To my understanding, this memory distribution between two worlds(secure and normal) can be configured. So I wonder whether I can determine this memory distribution. If it's indeed configurable, where I can find the source file to configure this and whether this configuration can be changed dynamically when the system is running. 2. As far as I know, the i.mx53-qsb have 1GB, but from the situation above, the total memory size is about 400MB which is far less than 1GB. So why can this situation happened? Thanks, Best wishes

2 1

First steps with Sculpt on Dell XPS 13
by Roman Iten 17 Oct '18

17 Oct '18

Hi, for some time now I've been thinking about upgrading:) my day-to-day operating system from bare metal Linux to Sculpt. My Dell XPS 13 (9350) doesn't boot out of the box and I didn't had the time to investigate. Now the cool new report_dump gives me a chance to easily spot problems when using Sculpt on my laptop. So I prepared "Sculpt as a hardware-probing instrument" as described in the release notes [1]. But it seems like the XPS doesn't boot far enough as no reports are dumped... I suspected there's probably an issue related to the XPS' display resolution of 3200 x 1800. After all it's clearly been declared in Sculpts hardware requirements [2], that displays with a higher resolution than 2560 x 1440 "are not expected to work". I tried to artificially restrict the resolution to FHD [3]. The internal display still doesn't work, but when an external monitor is connected via an USB-C dock or adapter (!), the Leitzentrale is displayed and the report_dump subsystem dumps reports to the flash memory. Using Leitzentrale, I then updated config/fb_drv to enable the internal display with it's native resolution. All screens go blank, but now I have a log to share [4] (the reconfiguration of the fb_drv happens after line 500) So far my very first experiences with Sculpt on the Dell XPS 13. And here some related questions: 1. What do you think about the idea to generally restrict the resolution of the initial fb_drv configuration to the maximum resolution supported by Sculpt (instead of that of the connected display(s), which may break Sculpt), similar to [3]? This would also help if, for example, an external 4K TV is connected during boot. 2. On Sculpt, most/all? internal displays report only their native resolution. On the XPS this is 3200 x 1800 and I can't force a lower resolution. Although under Linux, xrandr reports a bunch of supported resolutions from 3200 x 1800 down to 640 x 360. Does the intel_fb_drv under Genode intentionally reports and supports only the native resolution? 3. Should I create an issue regarding [4] on GitHub? 4. Instead of installing Sculpt directly on my current laptop I consider to buy a new XPS 13 (9370). It has a Killer 1435 wireless module featuring a Qualcomm Atheros QCA6174A chip which seems to be supported on Linux by the ath10k module... Has someone any experience (or assumptions) whether there's a chance that it will work on Sculpt (right now or in the near future)? Cheers, Roman [1] https://genode.org/documentation/release-notes/18.08 [2] https://genode.org/documentation/articles/sculpt-tc [3] https://github.com/rite/genode/commit/ba65d4307e892320b791b52cdccca1d421694… [4] https://gist.github.com/rite/1e5602c9ed55a810fe9306475e3962c0#file-log-L501

10 19

timestamp value too big
by lzSun 28 Sep '18

28 Sep '18

Hello, I have implemented a service in Genode OS based on tz_vmm demo on i.mx53-qsb. And I want to measure the performance of my service. I have included the "timer driver" in my Genode OS and added the 'perf_counter' to specs.conf file. Because my service implementation include some C language files, so I use 'gettimeofday()' function to get time in .c files. However, when the system running, it prints "Warning: timestamp value too big" many times. And the results is incorrect: I measure several period of the service, some of the period is quite long(about 30 seconds I observe from the print message, I know this is inaccuracy but I think it will not far from the actual execution time ) but the calculate time interval is about 9 seconds. Also, I use elapsed_time() function at the beginning(t1) and the ending(t2) of the service respectively, and t2-t1 is about 19193 ms, while I use time command to measure in linux is about 1m19s. At the side of linux, I just open my help module to use SMC to request my service in Genode OS and get back while the service is done, so I think the linux measure time will not far from the service excution time. So my question is, how can I measure quite long time period in the Genode ? It seems the method I used above to measure time is inaccurate. ------------------ Best wishes

1 0

Re: Increase VM memory size
by lzSun 27 Sep '18

27 Sep '18

>Hi, >it crossed my mind, if you do not need more than half of the memory >(512 MiB) inside Linux, you can easily assign the second memory bank >to the non-secure guest without further adaptions. Here is a patch: >diff --git a/repos/base-hw/include/spec/imx53/drivers/trustzone.h >b/repos/base-hw/include/spec/imx53/drivers/trustzone.h >index 8a65fea02..0f8d51b4c 100644 >--- a/repos/base-hw/include/spec/imx53/drivers/trustzone.h >+++ b/repos/base-hw/include/spec/imx53/drivers/trustzone.h >@@ -28,8 +28,8 @@ namespace Trustzone >*/ > SECURE_RAM_BASE = Imx53::RAM_BANK_0_BASE, >SECURE_RAM_SIZE = 256 * 1024 * 1024, >- 256NONSECURE_RAM_BASE = Imx53::RAM_BANK_0_BASE + SECURE_RAM_SIZE, >- RAM_BANK_0_BASENONSECURE_RAM_SIZE = 256 * 1024 * 1024, >+ 256NONSECURE_RAM_BASE = Imx53::RAM_BANK_1_BASE, >+ Imx53NONSECURE_RAM_SIZE = 512 * 1024 * 1024, > }; > } >Please keep in mind to *not* increase the secure ram area. It needs to >be protected by the M4IF TrustZone aware IP core, which is somehow >limited in its configuration of secure address ranges. >Regards >Stefan Hi, Thank you Stefan, It works for me now!

1 0

Increase VM memory size
by lzSun 27 Sep '18

27 Sep '18

hello, I have written an email about to increase the tz_vmm demo's memory size before, but haven't get any answer yet. The thing is, I want to increase the memory size that linux in the normal world can use. During these days, I found the related file which is at " /genode/repos/base-hw/include/spec/imx53/drivers/trustzone.h " . In this file I found the NONSECURE_MEMORY_SIZE = 256*1024*1024. So I increase this size to 512*1024*1024, however, when the system booting, it print the error message like: [init -> tz_vmm] Start virtual machine ... [init -> tz_vmm] Error: failed to handle data abort [init -> tz_vmm] Cpu state: [init -> tz_vmm] Register Virt Phys [init -> tz_vmm] ------------------------------------ [init -> tz_vmm] r0 = 0xc0888294 0x80888294 [init -> tz_vmm] r1 = 0x00000000 0x00000000 [init -> tz_vmm] r2 = 0x00000020 0x00000000 [init -> tz_vmm] r3 = 0xd5001000 0x95001000 [init -> tz_vmm] r4 = 0xc0c28000 0x80c28000 [init -> tz_vmm] r5 = 0xd50000c0 0x950000c0 [init -> tz_vmm] r6 = 0xc0888294 0x80888294 [init -> tz_vmm] r7 = 0xd50000a0 0x950000a0 [init -> tz_vmm] r8 = 0xd5000000 0x95000000 [init -> tz_vmm] r9 = 0x00000000 0x00000000 [init -> tz_vmm] r10 = 0x00000000 0x00000000 [init -> tz_vmm] r11 = 0xffffffff 0x00000000 [init -> tz_vmm] r12 = 0x00000001 0x00000000 [init -> tz_vmm] sp = 0x00000000 0x00000000 [init -> tz_vmm] lr = 0x00000000 0x00000000 [init -> tz_vmm] ip = 0xc00cde10 0x800cde10 [init -> tz_vmm] cpsr = 0x60000093 0x00000000 [init -> tz_vmm] sp _und = 0xc08e59d8 0x808e59d8 [init -> tz_vmm] lr _und = 0xc08e59d8 0x808e59d8 [init -> tz_vmm] spsr _und = 0x00000000 0x00000000 [init -> tz_vmm] sp _svc = 0xc0887f30 0x80887f30 [init -> tz_vmm] lr _svc = 0xc00cddf0 0x800cddf0 [init -> tz_vmm] spsr _svc = 0x00000000 0x00000000 [init -> tz_vmm] sp _abt = 0xc08e59cc 0x808e59cc [init -> tz_vmm] lr _abt = 0xc08e59cc 0x808e59cc [init -> tz_vmm] spsr _abt = 0x00000000 0x00000000 [init -> tz_vmm] sp _irq = 0xc08e59c0 0x808e59c0 [init -> tz_vmm] lr _irq = 0xc08e59c0 0x808e59c0 [init -> tz_vmm] spsr _irq = 0x00000000 0x00000000 [init -> tz_vmm] sp _fiq = 0x00000000 0x00000000 [init -> tz_vmm] lr _fiq = 0x00000000 0x00000000 [init -> tz_vmm] spsr _fiq = 0x00000000 0x00000000 [init -> tz_vmm] ttbr0 = 0x80004019 [init -> tz_vmm] ttbr1 = 0x80004019 [init -> tz_vmm] ttbrc = 0x00000000 [init -> tz_vmm] dfar = 0xc088829c 0x8088829c [init -> tz_vmm] exception = data_abort Did I missed something ? Any help will be grateful, thanks a lot! ------------------ Best wishes

2 2

Sculpt OS with Visual Composition (VC)
by Norman Feske 26 Sep '18

26 Sep '18

Hello everyone, we just published the third official version of Sculpt OS: https://genode.org/download/sculpt This version - called Sculpt with Visual Composition (VC) - introduces a novel graphical user interface for the interactive deployment of subsystems. For the first time, Sculpt can be explored without editing any text files. Furthermore, the new version increases the compatibility with modern hardware thanks to the vast device-driver improvements of Genode 18.08. Sculpt VC is available as ready-to-use disk image and is accompanied with updated documentation: https://genode.org/documentation/articles/sculpt-vc I wish you a lot of fun with exploring the new version! 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

4 4

Questions about genode os from a prospective user (moving from Qubes)
by Mr Oxide 24 Sep '18

24 Sep '18

I am a former qubes user. Currently on Linux MInt. Thinking of moving to Genode. Questions are (and this is for the Nova kernel with VirtualBox): 1. Can you assign PCI device hardware to virtual machines? 2. Can VMs be networked to each other? My idea with qubes was to setup an HVM with a dedicated HBA card and then install freenas within it. I would then use this as a nas for all of my vms to share. Is this possible with genode? 3. Is there anything that is not compatible (compared to qubes os)? 4. How is net security in dom0? In qubes os there is no dom0 networking.

2 1

EHCI HID not working on my hardware
by Nobody III 24 Sep '18

24 Sep '18

Genode has always had issues with interrupts on my desktop computer. This broke the AHCI and USB drivers, but recent developments have begun to fix/avoid this problem. While using 18.05/18.08, I discovered that the PS/2 driver worked fine, and later that if I only enabled XHCI, the USB driver worked for my USB 3.0 ports. A recent change (probably commit 76e9645 <https://github.com/genodelabs/genode/commit/76e964578780b4681dee0b94c0ac68b…>) in 18.09 (Sculpt VC) further improved USB support for my desktop computer, allowing me to use USB devices on the unmodified Sculpt VC system. It even allowed me to access, and, after adding an ext2 partition, use my USB flash drive, even in my USB 2.0 ports. However, my mouse and keyboard still generally only work in my USB 3.0 ports. I say generally because sometimes, if I move my mouse's receiver from a USB 3.0 port to a USB 2.0 port, it will continue to work. Does anyone have any ideas on how to get USB HID devices to work in USB 2.0 ports, or does anyone have any insight into what this means about my computer, or how to enable other drivers (e.g. AHCI) to work on it?

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users September 2018