Hi Valery,
> Yes, looks like a redraw problem indeed.
FYI, I fixed this problem today:
https://github.com/genodelabs/genode/commit/e0ac419ecd50594a4a001711c54413e799abc2a9
Cheers
Norman
--
Dr.-Ing. Norman Feske
Genode Labs
https://www.genode-labs.com · https://genode.org
Genode Labs GmbH ·
On 05.03.2018 13:16, Alexander Boettcher wrote:
On 01.03.2018 02:01, Valery V. Sedletski via genode-main wrote:
and re-create the interactive driver package (as shown above).
Yes, I increased caps quota for fb_drv now, and commented "throw" out in
acpi.cc, this
Can you please test commit [0],
On 05.03.2018 14:09, Norman Feske wrote:
Hello Valery,
On 04.03.2018 17:06, Valery V. Sedletski via genode-main wrote:
Though, trying to run "sculpt_test" on NOVA in QEMU, I see "drivers" and
"leitzentrale",
and "runtime" starting, and then silence (no progress). I commented the
routing rules
Hello Valery,
On 04.03.2018 17:06, Valery V. Sedletski via genode-main wrote:
> Though, trying to run "sculpt_test" on NOVA in QEMU, I see "drivers" and
> "leitzentrale",
> and "runtime" starting, and then silence (no progress). I commented the
> routing rules
> in all three subsystems out, so
On 01.03.2018 02:01, Valery V. Sedletski via genode-main wrote:
>> and re-create the interactive driver package (as shown above).
> Yes, I increased caps quota for fb_drv now, and commented "throw" out in
> acpi.cc, this
Can you please test commit [0], which should ignore the invalid ACPI
table
On 04.03.2018 13:53, Tomasz Gajewski wrote:
"Valery V. Sedletski via genode-main"
writes:
These messages:
[init -> drivers -> driver_manager] [31mError: Could not open ROM session for
"platform_info"[0m[0m
[init -> drivers -> driver_manager] [31mError:
"Valery V. Sedletski via genode-main"
writes:
> These messages:
>
> [init -> drivers -> driver_manager] [31mError: Could not open ROM session for
> "platform_info"[0m[0m
> [init -> drivers -> driver_manager] [31mError: Uncaught exception of type
>
On 01.03.2018 11:25, Norman Feske wrote:
Hi Valery,
[init] [31mError: RAM preservation exceeds available memory[0m[0m
[init] [34mWarning: runtime: assigned RAM exceeds available RAM[0m[0m
...
[init] [34mWarning: specified quota exceeds available quota, proceeding
with a quota of
Hi Valery,
> [init] [31mError: RAM preservation exceeds available memory[0m[0m
> [init] [34mWarning: runtime: assigned RAM exceeds available RAM[0m[0m
> ...
> [init] [34mWarning: specified quota exceeds available quota, proceeding
> with a quota of 3424667716[0m[0m
> [init] [34mWarning:
On 28.02.2018 15:25, Alexander Boettcher wrote:
On 28.02.2018 00:58, Valery V. Sedletski via genode-main wrote:
[1] https://imgur.com/a/kSptw
The ACPI table named ATKG seems to cause also trouble on other Linux
machines according to my search results. Maybe you can apply the latest
BIOS
On 28.02.2018 00:58, Valery V. Sedletski via genode-main wrote:
> [1] https://imgur.com/a/kSptw
The ACPI table named ATKG seems to cause also trouble on other Linux
machines according to my search results. Maybe you can apply the latest
BIOS update to that machine, since the root cause of the
On 27.02.2018 22:31, Alexander Boettcher wrote:
Hello,
On 23.02.2018 18:47, Valery V. Sedletski via genode-main wrote:
scenarios, so far. NOVA seems to hang on my three available
machines, for some reason. So, I tried the Fiasco.OC kernel instead.
(But VirtualBox and Seoul are working on NOVA
Hello,
On 23.02.2018 18:47, Valery V. Sedletski via genode-main wrote:
> scenarios, so far. NOVA seems to hang on my three available
> machines, for some reason. So, I tried the Fiasco.OC kernel instead.
> (But VirtualBox and Seoul are working on NOVA only). So far, my
> attempts to run Sculpt
On 23.02.2018 14:55, Norman Feske wrote:
Hello Valery,
I have the impression that your undertaking goes very much against the
grain of our regular work flow. Frankly speaking, I miss the point of
bypassing our tooling and instead manually working with boot modules. We
deliberately moved away
Hello Valery,
I have the impression that your undertaking goes very much against the
grain of our regular work flow. Frankly speaking, I miss the point of
bypassing our tooling and instead manually working with boot modules. We
deliberately moved away from relying on the boot loader to load
On 21.02.2018 22:43, Valery V. Sedletski via genode-main wrote:
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)
Ok, I commented
# exec rm -rf
On 20.02.2018 01:24, Valery V. Sedletski via genode-main wrote:
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
Installed GRUB2 on another flash stick (with FAT32) and trying to boot
the same setup as above:
set timeout=0
set gfxpayload="0x0x32"
menuentry 'Genode on NOVA' {
insmod multiboot2
insmod gzio
insmod part_msdos
insmod fat
multiboot2 /boot/bender
module2 /boot/hypervisor hypervisor iommu
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
19 matches
Mail list logo