users August 2018

users@lists.genode.org

17 participants
18 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

Sculpt/wifi_drv regression: no IP address
by Nobody III 10 Sep '18

10 Sep '18

I updated to the 18.08 Genode release, built a Sculpt image, then booted it on my Dell Latitude 6430u laptop. I discovered that the WiFi driver, which worked in 18.05 (Sculpt TC) no longer works properly. In particular, the WiFi driver detects the access points and can connect to them, but doesn't get an IP address. I tried multiple access points, both my wireless router and my phone. With my phone, I used a clean lowercase alphabetic SSID ("bensphone"), to avoid any issues with problematic characters. I am using an Intel Ultimate-N 6300 wireless card.. Wired networking still works.

2 3

Sculpt VC Launcher GUI?
by Nobody III 31 Aug '18

31 Aug '18

In Sculpt VC, I haven't seen any launcher GUI. Does such a component exist? Or do I still have to use the text interface (vim) to launch components?

1 0

Re: Wandboard Quad GPIO mapping
by Edward Sandberg 31 Aug '18

31 Aug '18

Hi Stefan, Thanks very much for your detailed reply! > You are writing that you use Genode 18.05 nova? The nova kernel does > not run on ARM platforms. Certainly, you are using the base-hw kernel? Sorry, I meant seL4. > The imx6 gpio driver allows to set 7*32=224 pins to be set. It > controls 7 dedicated GPIO controllers with 32 pins for each. When you > want to address a pin of a controller > 0, you have to add an offset > accordingly. Yes, after I sent my original message I realized the the MAX_PINS variable was per bank and that the pin mapping to jp4 is the same as in linux. I am now able to read and write to the expected pins on jp4 extender. Next I am going to attempt to get the framebuffer working on the Wandboard Quad by modifying the imx53 framebuffer source code included with genode. So far I have modified: repos/base/include/drivers/defs/imx6.h to add the needed IPU_BASE, IPU_SIZE, PWM2_BASE and PWM2_SIZE variables. I see two interesting things when I boot: * Info: Not using supported FPU as FPU is disabled in the build configuration * [init -> fb_boot_drv] Error: No boot framebuffer information available. Perhaps if I fix the first issue the information will be provided and the second bullet point will be resolved as well. I will update the mailing list as I make progress. -- Edward Sandberg Adventium Labs 111 3rd Avenue S. Suite #100 Minneapolis, MN 55401 ed.sandberg(a)adventiumlabs.com

1 0

10th anniversary of the first public Genode release
by Norman Feske 31 Aug '18

31 Aug '18

Dear Genode community, as announced in the most recent Genode-Labs newsletter [1], we can celebrate the 10th anniversary of Genode this year. [1] https://www.genode-labs.com/news/newsletter/newsletter-2018-07 ------ Genode has reached the age of one decade! This is fascinating from various perspectives. First, we still vividly remember the time when we founded the project like if it was yesterday. We remember asking ourselves the question how we imagine Genode Labs in ten years. Well, it actually looks pretty much exactly like we had envisioned: A tight- knit group of enthusiastic and energetic minds working without friction in an enjoyable environment, a healthy open-source ecosystem, having earned the trust and recognition of highly reputable people. Our dream has become reality. Second, it took us more then 10 years to transform our initial vision of an ideal operating system into the software that runs so nicely on our laptops now. With the common perception of a rapid and ever accelerating evolution of technology as a background, this time frame feels like an eternity. But now, we are here. Third, maintaining a sustainable business over this long period while retaining independence is not easy. But it is possible and a fulfilling experience we would not want to miss. To celebrate the anniversary together with the community, friends, and families around Genode, we continue our tradition of holding a barbecue at the banks of the river Elbe: Google Maps: http://goo.gl/maps/C0luj Thursday August 30, 6 pm near Eisenberger Strasse in Dresden If you are planning to attend, please let us know by writing a short note to: info(a)genode-labs.com ------ 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

3 4

Wandboard Quad GPIO mapping
by Edward Sandberg 30 Aug '18

30 Aug '18

I'm working with the imx6 GPIO driver on Wandboard Quad, using the gpio_led run file as a smoke test. Unfortunately, I've had only limited success controlling the GPIO pins exported to the Wandboard's JP-4. It is unclear where these pins map in the Genode imx6 driver (18.05, nova). In Linux, I can successfully toggle them all via /sys/class/gpio. The imx6 driver allows for 32 pins to be set to high or low and I have modified the run file and the main.cc file to blink sets of pins rather than just a single pin. If I set all 32 pins as output with an initial value of "0" in the run file and then blink the following sets of pins I see these results: 0-31: I read 3 pins blinking with a voltage meter 0-15: I read 2 pins blinking 0-6: I read no pins blinking 7-15: I read no pins blinking It seems as though it takes combinations of pins set to high and low at the same time to get a reading of high or low off of a particular pin, but I cannot divine the pattern. This leads me to think that there is a step missing in the initial configuration. Does anyone have a suggestion of what step I am missing to get predictable results? -- Edward Sandberg Adventium Labs 111 3rd Avenue S. Suite #100 Minneapolis, MN 55401 ed.sandberg(a)adventiumlabs.com

2 1

Announcement: Genode OS Framework version 18.08 released
by Norman Feske 30 Aug '18

30 Aug '18

I have the pleasure to announce the release of Genode 18.08, which continues our story of sculpting Genode into a general-purpose OS. The release specifically addresses the device-driver support of modern PC hardware, the concern of applying microcode updates to Intel CPUs in a timely fashion, the scalability of application workloads, and the interactive usability of the system. The highlights of Genode 18.08 are: - Sculpt OS with live runtime view - Device drivers - Linux device-driver environment based on kernel 4.16.3 - Updated and enhanced Intel framebuffer and wireless drivers - De-componentized USB stack, support for isochronous devices - Improved device compatibility of NIC and PS/2 drivers - Experimental runtime for Zircon-based drivers - Base framework and OS-level infrastructure - NIC-router support for multiple uplinks - New VFS plugin for using LwIP as TCP/IP stack - Cached file-system-based ROM service - VFS plugin for importing initial content - Enhanced Ada language support - Libraries and applications - Python 3 - VirtualBox 5.1.38 - Platforms - New Intel Microcode update mechanism - Multiprocessor support for our custom kernel on x86 - Updated NOVA and Fiasco.OC kernels All of these and more improvements are covered in detail by the release documentation: https://genode.org/documentation/release-notes/18.08 Have fun with exploring the new version! 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

endless repeating message when starting vbox with RAW format diks
by Pirmin Duss 27 Aug '18

27 Aug '18

Hello Genodeans I Try to run a Linux in a RAW disk partition. The boot loader runs and starts the kernel but then something goes wrong. [runtime -> work -> vbox] Warning: VMM: map_memory - write fault on ROM region!? gp=0xffff0000 [runtime -> work -> vbox] Warning: VMM: map_memory - write fault on ROM region!? gp=0xffff0000 [runtime -> work -> vbox] VMM: error: unmap not implemented The last line is endlessly repeating. If I let the guest run, like this, for about 1 minute, the whole system becomes unusable. If I dd a Windows 10 image in to the partition the guest boots without any problem. Does anybody have an idea, what could cause this issue? Attached are the VBOX and VMDK-template file. We have a small component, that creates the VMDK file form the template with the size of the partition. Best regards, Pirmin

1 0

Expanding an NVME partition to 1T hangs
by Duss Pirmin 27 Aug '18

27 Aug '18

Hello Genodeans I have upgraded my Sculpt notebook with a 1T NVME disk as I want to use different virtual machines. When I hit expand and configm, the expansion starts and about 20 seconds later the following message is printed: [runtime -> nvme-0.3.resize2fs] resource_request: ram_quota=30535680 [runtime] child "nvme-0.3.resize2fs" requests ressource: ram=30535680 A reboot is required, to use the disk again. If I boot the system afterwards, the partition is resized to 1T. Best regards Pirmin

3 4

Change to usb_drv? (17.11 -> 18.05)
by Steven Johnston 16 Aug '18

16 Aug '18

Hi All: One of my components that handles a USB device was working in 17.11 (x86_32, nova), but is causing problems when I attempt to run it in 18.05. The device is an FTDI-based USB-GPIO adapter (FT232H chip), along with a port of libftdi. The USB hub setup seems to work, but the FTDI setup generates an error in the log "ftdi_usb_reset failed", occurring when libusb_control_transfer() fails during a USB reset. There is a similar sounding issue mentioned in the release notes regarding usb_block_drv. Might it be the same? If so, has this been resolved in some general way? Thank you for any input, Steven

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users August 2018