Re: Genode 16.08 nova.iso rebooting on real Core 2 Duo after relocating modules

Sorry, my mistake. that's Console::enable in console.hpp which seems to have nothing with interruptions. -- ___ genode-main mailing list genode-main@lists.sourceforge.net

Re: Genode 16.08 nova.iso rebooting on real Core 2 Duo after relocating modules

Well, now that you mentions things that does not seems to make sense in Console_VGA constructor, it ends with: enable() which I would presume is enable interruptions (did not check). But Idt::build(); (Interrupt Descriptor Table) will be called only after Hip::build too in init.

Re: Genode 16.08 nova.iso rebooting on real Core 2 Duo after relocating modules

About not reading any info from the bootloader, since we(now even me) use bender, this is bender that ask info the boot loader, and I will not be surprised if it give it to the nova hypervisor that knows how to read the command line, the list of modules, and the memory map if it is given to it.

Re: Genode 16.08 nova.iso rebooting on real Core 2 Duo after relocating modules

I now think the problem is with the expression: p = new (quota) P Will try the novga, even if I have doubt nova can react to cmdline arguments, because I belive it ask no information to the boot loader (including not asking the command line arguments).

Re: Genode 16.08 nova.iso rebooting on real Core 2 Duo after relocating modules

Looks like I was ok in my previous post. In fact I seem to have isolated to a line in pte.cpp in function walk: template P *Pte::walk (Quota , E v, unsigned long n, bool a) { unsigned long l = L; for (P *p, *e = static_cast(this);; e = static_cast(Buddy::phys_to_ptr

Re: Genode 16.08 nova.iso rebooting on real Core 2 Duo after relocating modules

2016-09-23 14:20 GMT-04:00 Christian Helmuth : ... > So your reboot is induced by Console_vga::Console_vga() in > src/console_vga.cpp. You may now proceed with moving 'while(1);' into > the constructor function. ... Good! So it seems to be that line in

Re: Genode 16.08 nova.iso rebooting on real Core 2 Duo after relocating modules

2016-09-23 4:47 GMT-04:00 Christian Helmuth <christian.helm...@genode-labs.com>: > Hello Paul, > > I like the approach of narrowing the issue with 'while(1);' and > suggest to go further (see below). > > On Thu, Sep 22, 2016 at 10:02:51PM -0400, Paul Dufresne wrote: >

Re: Genode 16.08 nova.iso rebooting on real Core 2 Duo after relocating modules

Oh well, I guess I get the very big picture. As Nova is written in C++, not C, the code contains constructors that somehow must be called almost as the first thing the hypervisor do. It seems the compilers make an array of function pointers to constructors functions (pointing inside .text I

Re: Genode 16.08 nova.iso rebooting on real Core 2 Duo after relocating modules

I see the following in hypervisor.ld but it is beyond my understanding: .init_array : AT (ADDR (.init_array) - OFFSET) { PROVIDE (CTORS_L = .); KEEP (SORT_BY_INIT_PRIORITY(*)(.init_array.65534 .ctors.1)) PROVIDE (CTORS_C = .); KEEP

Nova multiboot v.1 flags == 0 ???

I think I have a problem with Nova multiboot specification. In https://github.com/udosteinberg/NOVA/blob/master/src/start.S : /* * Multiboot Header */ __boot_header: .long 0x1badb002 .long 0x0 .long -0x1badb002 This is multiboot v.1 (current version is 2). 3.1.1 The layout of Multiboot header

Re: Genode 16.08 nova.iso rebooting on real Core 2 Duo after relocating modules

But I seems to have problems on first file compiled when using gcc v6: In file included from ../src/acpi.cpp:28:0: ../include/acpi_rsdt.hpp:45:26: error: flexible array member in union uint32 rsdt[]; ^ ../include/acpi_rsdt.hpp:46:26: error: flexible array

Re: Genode 16.08 nova.iso rebooting on real Core 2 Duo after relocating modules

2016-09-21 8:20 GMT-04:00 Christian Helmuth : >> Need 05df2000 bytes to relocate modules. >> Relocating to 7980d000: >> Copying 483168 bytes... > [...] >> Copying 114820 bytes... > > If my calculations from this output are correct the boot modules cover > RAM

My P4 Netvista works fine on real hardware with both nova and sel4 CD

I decided to test my computers in reverse side: P4 would test the CD Core 2 Duo would run minicom to capture log files. I was not expecting it to work, although I had some doubt because a quite older version was running on that P4. It appears both my CDs of Genode 16.08 (sel4.iso and nova.iso)

Genode 16.08 nova.iso rebooting on real Core 2 Duo after relocating modules

I thought rebooting computer as soon has coming to boot line was for old low memories computer only, but I get it with nova.iso burnt on a CD on my Core 2 Duo, 2 GB (well 3 GB, but 2 Gb memory stick recognized as only 1 Gb + one other 1 Gb). Capture log with null-modem RS232: Bender: Hello

boot loader did not provide information about modules

boot loader did not provide information about modules This is from my 'new' Core 2 Duo, booting Genode 16.08 sel4.iso on an usb key. I got it with a null-modem. I am attaching the full capture log file. I had the same symptoms on most computers I have tried... hanging on boot line doing

Re: For Nova under VirtualBox I get that error

I got my hands on a Core2 Duo computer, that allows me to run this in VirtualBox without problems. On real hardware, it had hang on boot line however... but since that computer still have a com port I might be able to figure out why when I will have enough time.

Re: For Nova under VirtualBox I get that error

Ok, first this talk about saving MSR is for AMD instructions (SYSENTER/SYSRET), not for Intel SYSEXIT. And indeed, the CPU simulated, a pentium 4, does not support SysEnter/SysExit. I know because when I go to Machine menu, show journal I can see: ... 00:00:02.740255 VM: fHMEnabled=true

Re: For Nova under VirtualBox I get that error

Well,I never got understanding clearly these SYSENTER/SYSEXIT instructions. Trying to google it a bit, I find this that seems to make some kind of sense (but not too much honestly). Basically, someone in similar situation was told it need to save MSR (most particularly IA32_STAR MSR), for using

Re: For Nova under VirtualBox I get that error

Oh well, it seems I get the error only under Virtuabox (which is version 5.1.4). I just burn a CD with that nova.iso, and after showing fast invalid hints messages, goes to the not handled by monitor video mode. This is the same computer I tried under VirtualBox (Debian 4.6.0-1-amd64, Celeron D,

Re: Writing sel4.iso on a CD/DVD vs. on an USB key

Just burn a new CD. New CD works as fine as the USB now. That is my monitor generate a flying window: "Not Optimum Mode Recommended Mode: 1280X1024 60Hz" Well, that's the price for using xfburn (that does not check burn image). I have now install and used Brasero. At least I learn something

For Nova under VirtualBox I get that error

NOVA Microhypervisor v7-23e7882 (x86_32): Aug 29 2016 10:39:41 [gcc 4.9.2] [ 0] CORE:0:0:0 f:4:9:4 [0] Intel(R) Celeron(R) CPU 2.66GHz [ 0] Killed EC:0xc23ca160 SC:0xc23cb100 V:0x6 CS:0x8 EIP:0xc02c CR2:0x0 ERR:0x0 (EXC) paul@arcturus:~$

Re: some error of sel4.iso on VirtualBox (1495Mo)

Oh well, might be usefull to say that VirtualBox is running with VT-X/AMD-V inactive, most probably because the real processor does not support it: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm

some error of sel4.iso on VirtualBox (1495Mo)

Because I have only 2GB, I had to lessen the memory in the virtual machine to 1495 Mo. Then I get some error, that I was able to capture by redirecting COM1 to /tmp/sel4 file: [some parsing cut ... ask if needed] Kernel loaded to: start=0x10 end=0x147000 size=0x47000 entry=0x10003e ACPI: RSDP

EDID (interrogating the monitor for display modes supported) support

On some real x86 hardware, I have seen the monitor say that it does not support the video mode generated by Genode. Am I right to suggest that vesa driver does not yet use EDID? Or is it a more complicated issue (here using rv516 ATI video card). On archive (

Writing sel4.iso on a CD/DVD vs. on an USB key

At first I had burned sel4.iso on a CD, but no computer was able to boot from it. Then rereading the instructions, I saw it was asked to DD it to an USB key, which I did, and was getting much better results: a grub menu that disappears so fast that it only goes to loading the first module, then

What is going on for february release?

Well, february 2013 is at our door now, and I would like to remember us of the plan for it according to our 2013 roadmap: -Low-latency audio support The current audio_out-session interface was our first shot into the direction of audio processing. To enable use cases where streaming audio and

Re: build directory outside of Genode dir xor vim error

Norman Feske said: --- This looks like your build directory is somehow broken. Haven't you built the run/demo for NOVA before? I wonder what happened to your build directory. Please try again, taking one step after the other. 1. use tool/create_build_dir nova_x86_32 to create a fresh build

Re: build directory outside of Genode dir xor vim error

Now that the bug I had in staging with okl4 is fixed, make run noux_bash work quite similarly on OKL4 than on Pistachio. cannot Esc :q in vim either lots of could not unmap page errors in the terminal. But overall, yes it does work quite a bit.

Re: build directory outside of Genode dir xor vim error

Ah, sure it must be it! Let me check that. -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200

Re: build directory outside of Genode dir xor vim error

Yes, vim works better now. :-) -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video

[Genode] why do I need to rebuild ports for different platforms? was: buid directory outside ...

I said: --- While trying the different 'platforms' (kernels), the build system seems a bit unoptimized. To me, rebuilding libports, ports, gems in each different kernels don't make much sense. I don't expect them to apply patch platform-specifics, only Genode-specifics. So it would make sense to

Re: [Genode] why do I need to rebuild ports for different platforms? was: buid directory outside ...

Ok, thanks, this clarify some misconceptions about the IPC I had. I was finding a bit odd that there was no kind of Interruption, or exact address to communicate for passing messages around. I was thinking a bit like if all programs were sharing the same address space (I must have been too much

build directory outside of Genode dir xor vim error

Well, I have tried maybe too many new things at once and it I have now broken pieces I would wish to share with you. :-) First change: staging rather than master. Second change: try make run/noux_bash Third change: ./tool/create_builddir linux_x86 BUILD_DIR=./build.lx rather than the usual:

Re: build directory outside of Genode dir xor vim error

Well, I have this one: Skip target noux-pkg/coreutils because it requires prepare_coreutils The build system support some 'requires X' ? Would it be just a missing 'requires coreutils' to noux_bash.run file? I'll try to do a: paul@paul-P5GZ-MX:~/mygenode/ports$ make prepare PKG=coreutils (well,

Re: build directory outside of Genode dir xor vim error

Ok, made make clean then make run/bash_noux still on staging. I now have the bash window: base-4.1# ls Maybe it was not a correct command to ask for, because the system seems to be hang there: [init - terminal] int main(int, char**): --- terminal service started --- [init - noux] --- noux

About Enlightenment and EFL

It looks like Qt is the currently (prefered) GUI library for Genode. I am trying to push it toward EFL with this message. ;-) Ok, frankly, I did not begin to develop any application either with Qt or EFL. I am still kind of searching which GUI libs I should learn. Anyway, what is Enlightenment?

Re: About Enlightenment and EFL

There seems to be a problem however: It seems to depend quite a bit on X. While reading: http://trac.enlightenment.org/e/wiki/Installation I now see it depends on the following libs: libc libm libpthread zlib freetype fontconfig opengl2.0/opengles-2 (depending on

Re: About Enlightenment and EFL

Now that I am reading the README of Evas 1.7.4 (I would think only this lib deals with backend buffers), the restriction seems much less strict: Must: libc eina (1.1.0 or better) freetype (2.1.9 or better) Recommended: libX11 + libXext + libXrender OpenGL2.0 or OpenGL-ES 2.0

Re: Nova 32 bits on older Pentium 4 computer.

Hi! This 0-1000 address you are trying to give VESA... this is virtual memory? I was asking because when I did read that one of the goal about 2013.2 release was: * IOMMU support on NOVA I remember to have read that IOMMU is often found on motherboard having PCI express. This one is AGP I think.

Re: Nova 32 bits on older Pentium 4 computer.

Ah no, I think I can guess (all my understanding is rather fuzzy). This 0-1000 thing, is my old real mode interrupt table (256 entries, of 4 bytes each). Well, I am surprised to see how this x86emu can be coded in user mode. But I find strange that so much assembler seems to need to be emulated,

Re: Nova 32 bits on older Pentium 4 computer.

My current guess is that you don't use virtual 8086 mode but rather, emulate it in protected mode (as user code) mostly to call (euh run, much as an assembler interpreter) Vesa BIOS int 0x10 to set video mode and ask it where it has put the framebuffer. avl.diff applied. Much better, from there

Re: Nova 32 bits on older Pentium 4 computer.

Ok, I added a config element for the vesa driver in my demo.run file: append_if [have_spec vesa] config { start name=vesa_drv config width=640 height=480 depth=16 buffered=no / resource name=RAM quantum=1M/

Re: A GUI for Genode

Rather than having the notification area to the right, I want it at the bottom. It should contains 2 or 3 lines of text with the following fields: Origin application: ex.: gedit(3) Clicking it change the application area to that application. hour: 13h15:23 Up/Down arrow to switch to other same

Re: Nova 32 bits on older Pentium 4 computer.

Well, the cause of my problem seems to be: static int map_code_area(void) { int err; Ram_dataspace_capability ds_cap; void *dummy; printf(map_code_area will map_io_mem\n); /* map page0 */ if ((err = Framebuffer_drv::map_io_mem(0x0, PAGESIZE, false, dummy)))

Re: Tested run/demo on nova: liquid_fb tried to call an invalid object

Nova 64 bits rebooting in loop on my older Pentium 4 computer was not a surprised. This morning I tested Nova 32 bits. Nova 32 bits seems to work well on my Celeron D computer, but not on my older (about 2002) IBM Netvista computer where I get when trying to boot the demo.iso CD: Nova

Re: Nova 32 bits on older Pentium 4 computer.

Ok... will try to see what I can make with these new info. I was reading a bit about IO-APIC and Local APIC. Frankly, it does goes above my head (not fully understanding, not so much interested). At this site: http://osdev.berlios.de/pic.html I am reading something that looks like could be

Re: Nova 32 bits on older Pentium 4 computer.

The result of testing with just the hypervisor seems the same on both of my computer: -I see the Killed EC: ... (No ELF) -spinner spin (actually at least on my Pentium 4, a cyan, a blue and a yellow text digit counting) down the screen

Re: Tested run/demo on nova: liquid_fb tried to call an invalid object

and two lines after the clone is reset to the revision specified in GIT_REV and then the custom patches are applied Ah, yes, indeed. Thanks! It's the first time I see this reset command. I was expecting to clone a specific version, rather than resetting. And the fact that the patches when

Re: [memory issue] i see a issue when i build demo with linux_x86 mode.

I find this value quite big on my 1 Gb computer while make run/sdl on Linux 64b: spawn ./core int main(): --- create local services --- int main(): --- start init --- int main(): transferred 17592186044415 MB to init int main(): --- init created, waiting for exit condition --- Quota exceeded!

Re: Tested run/demo on nova: liquid_fb tried to call an invalid object

Ok, so I burn my var/run/demo.iso file from my build directory (8 MB, impressively small!) to a CD and tried it. My big surprise when I ran it on my computer was to hear the 56k modem call a number. I heard the operator voice, so that I know it did not join it's destination fine. I first tought

Re: HelenOS kernel (Spartan) as a Genode platform

I believe that 'platform' refer to the thing the rest of the thing sit on. For applications you can see the platform as the OS, but for a microkernel based OS, that can support many microkernels, it make sense for me to call platform, the microkernel choosed. HelenOS sit on it's own microkernel

Re: Genode 12.11 on Ubuntu 64 bits: Could not open file ld.lib.so seems to cause black window

he he, I wish I would have read tool_chain.txt before. I was merely following instructions in getting_started.txt that is not very clear: Furthermore, you will need to install the official Genode toolchain, which you can download at [http://genode.org/download/tool-chain].; That's probably where

HelenOS kernel (Spartan) as a Genode platform

I believed that an HelenOS GoogleSummerOfCode (GSOC) project for 2012 was: https://www.google-melange.com/gsoc/project/google/gsoc2012/kurbel/20001 http://trac.helenos.org/ticket/419 Basically no GSOC 2012 projects was accepted for Genode, but it was for the HelenOS. So Tobias Börtitz did work on

libpulse symbols beginning by pa_ not found while linking fb_sdl (newbie)

Hi, I am new to Genode and love it (particularly the release notes!). I am having a problem linking fb_sdl with while compiling Genode 12.11 on LuninuxOS (based on Ubuntu Quantal) 64 bits: paul@paul-P5GZ-MX:~/Bureau/Genode/genode-12.11/build.lx$ make run/demousing run script

Re: libpulse symbols beginning by pa_ not found while linking fb_sdl (newbie)

Just found the libs on my system, but I don't know what to do next: paul@paul-P5GZ-MX:/usr/lib/x86_64-linux-gnu$ locate libpulse /usr/lib/libpulsecore-2.1.so /usr/lib/vlc/plugins/access/libpulsesrc_plugin.so /usr/lib/vlc/plugins/audio_output/libpulse_plugin.so

Re: libpulse symbols beginning by pa_ not found while linking fb_sdl (newbie)

Problem solved by: paul@paul-P5GZ-MX:/usr/lib/x86_64-linux-gnu$ sudo cp pulseaudio/libpulsecommon-2.1.so . [sudo] password for paul: paul@paul-P5GZ-MX:/usr/lib/x86_64-linux-gnu$ ls libpuls* libpulsecommon-2.1.solibpulse-simple.solibpulse.so.0 libpulse-mainloop-glib.so

Re: MSI support in Genode

Just in case someone else is asking himself/herself the same question I did: What is MSI anyway? the answer is in 3. of: http://www.mjmwired.net/kernel/Documentation/MSI-HOWTO.txt -- Master Visual Studio, SharePoint, SQL,

Re: Genode 12.11 on Ubuntu 64 bits: Could not open file ld.lib.so seems to cause black window

if your Ubuntu GCC version is 4.7.x, you need to apply the patch from this bugtracker issue: https://github.com/genodelabs/genode/issues/550 Yep, manually applying the patch make the launchpad window to work. Thanks! That said, I was using the Genode toolchain which is gcc 4.7.2 from: