Guten Tag,
I've got the Hello app runing with fiasco and l4re in qemu, how do I get the graphical UI and console running that I see on the screen shots page? Do I need to use l4con and mag? I don't see an entry with l4con in modules.list.
danke * http://german.about.com/library/media/Audio/gutentag.wav*
Hi,
please check the x86-fb.cfg in src/l4/conf/examples This is a lua script that sets up a sample application in a mag window on the framebuffer. You can see all the binaries and files required in the cfg file (look out for the :start lines).
You will of course also need ned to interprete the x86-fb.cfg file and the usual l4re binary.
Best regards,
- Marcus
On 2014-06-10 15:10, teclis High Elf wrote:
Guten Tag,
I've got the Hello app runing with fiasco and l4re in qemu, how do I get the graphical UI and console running that I see on the screen shots page? Do I need to use l4con and mag? I don't see an entry with l4con in modules.list.
danke
_ [1]_
Links:
[1] http://german.about.com/library/media/Audio/gutentag.wav
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Es tut mit leid*, *
I think there is still a piece I am missing or my build configuration is incorrect. ls builddir/bin/x86_pentium4/l4f/ hello l4re loader lua moe ned sigma0
so I'm missing: module x86-legacy.devs module io module fb-drv module mag module ex_fb_spectrum_cc
* http://german.about.com/library/media/Audio/estutmirleid.wav*
On Tue, Jun 10, 2014 at 9:22 AM, Marcus Hähnel < mhaehnel@os.inf.tu-dresden.de> wrote:
Hi,
please check the x86-fb.cfg in src/l4/conf/examples This is a lua script that sets up a sample application in a mag window on the framebuffer. You can see all the binaries and files required in the cfg file (look out for the :start lines).
You will of course also need ned to interprete the x86-fb.cfg file and the usual l4re binary.
Best regards,
- Marcus
On 2014-06-10 15:10, teclis High Elf wrote:
Guten Tag,
I've got the Hello app runing with fiasco and l4re in qemu, how do I get the graphical UI and console running that I see on the screen shots page? Do I need to use l4con and mag? I don't see an entry with l4con in modules.list.
danke
_ [1]_
Links:
[1] http://german.about.com/library/media/Audio/gutentag.wav
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Ok I solved the build problem. This command:
*svn cat http://svn.tudos.org/repos/oc/tudos/trunk/repomgr http://svn.tudos.org/repos/oc/tudos/trunk/repomgr | perl - init http://svn.tudos.org/repos/oc/tudos http://svn.tudos.org/repos/oc/tudos fiasco l4re*
from: http://l4re.org/download.html doesn't grab all the l4 packages. I downloaded the latest tarball snapshot and they were all there.
Then I built it with the command: make grub2iso E=x86-fb-example MODULES_LIST=/home/teclis/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/conf/examples/x86-fb.list MODULE_SEARCH_PATH=/home/teclis/fiasco/src/kernel/fiasco/mybuild:/home/teclis/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/conf/examples:/home/teclis/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/pkg/io/config/
and it built ok. Now when it runs fbdrv page faults. Has anyone seen this before? danke
fbdrv | Trying execution of ``set VBE mode'' using x86emu fbdrv | Found VESA BIOS version 2.0 fbdrv | OEM VGABIOS Cirrus extension fbdrv | Scanning for 'best' possible mode: fbdrv | Trying to read DDC info fbdrv | DDC function not supported fbdrv | EDID not available (-19), finding best possible mode ... fbdrv | Mode: 0x101 640x480@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x110 640x480@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x111 640x480@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x112 640x480@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x103 800x600@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x113 800x600@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x114 800x600@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x115 800x600@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x105 1024x768@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x116 1024x768@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x117 1024x768@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x118 1024x768@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x107 1280x1024@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x119 1280x1024@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Choosen mode: fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | To force a specific setting use a '-m <mode>' option. fbdrv | L4Re[rm]: mapping for page fault failed with -34 @1a0000 pc=1006452 fbdrv | L4Re: unhandled exception: pc=0x1006452
On Tue, Jun 10, 2014 at 11:59 AM, teclis High Elf <teclis.high.elf@gmail.com
wrote:
Es tut mit leid*, *
I think there is still a piece I am missing or my build configuration is incorrect. ls builddir/bin/x86_pentium4/l4f/ hello l4re loader lua moe ned sigma0
so I'm missing: module x86-legacy.devs module io module fb-drv module mag module ex_fb_spectrum_cc
On Tue, Jun 10, 2014 at 9:22 AM, Marcus Hähnel < mhaehnel@os.inf.tu-dresden.de> wrote:
Hi,
please check the x86-fb.cfg in src/l4/conf/examples This is a lua script that sets up a sample application in a mag window on the framebuffer. You can see all the binaries and files required in the cfg file (look out for the :start lines).
You will of course also need ned to interprete the x86-fb.cfg file and the usual l4re binary.
Best regards,
- Marcus
On 2014-06-10 15:10, teclis High Elf wrote:
Guten Tag,
I've got the Hello app runing with fiasco and l4re in qemu, how do I get the graphical UI and console running that I see on the screen shots page? Do I need to use l4con and mag? I don't see an entry with l4con in modules.list.
danke
_ [1]_
Links:
[1] http://german.about.com/library/media/Audio/gutentag.wav
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
On Tue Jun 10, 2014 at 14:20:54 -0400, teclis High Elf wrote:
Ok I solved the build problem. This command:
*svn cat http://svn.tudos.org/repos/oc/tudos/trunk/repomgr http://svn.tudos.org/repos/oc/tudos/trunk/repomgr | perl - init http://svn.tudos.org/repos/oc/tudos http://svn.tudos.org/repos/oc/tudos fiasco l4re*
from: http://l4re.org/download.html doesn't grab all the l4 packages.
Indeed, it only checks out a subset. To fetch all, 'all' could be specified instead of 'fiasco l4re'.
I downloaded the latest tarball snapshot and they were all there.
The other possibility.
and it built ok. Now when it runs fbdrv page faults. Has anyone seen this before? danke
fbdrv | Trying execution of ``set VBE mode'' using x86emu fbdrv | Found VESA BIOS version 2.0 fbdrv | OEM VGABIOS Cirrus extension fbdrv | Scanning for 'best' possible mode: fbdrv | Trying to read DDC info fbdrv | DDC function not supported fbdrv | EDID not available (-19), finding best possible mode ... fbdrv | Mode: 0x101 640x480@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x110 640x480@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x111 640x480@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x112 640x480@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x103 800x600@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x113 800x600@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x114 800x600@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x115 800x600@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x105 1024x768@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x116 1024x768@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x117 1024x768@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x118 1024x768@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x107 1280x1024@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x119 1280x1024@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Choosen mode: fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | To force a specific setting use a '-m <mode>' option. fbdrv | L4Re[rm]: mapping for page fault failed with -34 @1a0000 pc=1006452 fbdrv | L4Re: unhandled exception: pc=0x1006452
This looks like io does not like to hand out the framebuffer memory. Any change when specifying, for example, -m 0x114 ? Does io say something noteworthy, possibly with some -v options supplied?
Adam
I'm not sure its IO and the frame buffer memory. It fails on X86EMU_exec() in x86emu_int10_set_vbemode() called from Vesa_fb::setup_drv() before the first call to l4io_request_iomem()
On Tue, Jun 10, 2014 at 5:17 PM, Adam Lackorzynski < adam@os.inf.tu-dresden.de> wrote:
On Tue Jun 10, 2014 at 14:20:54 -0400, teclis High Elf wrote:
Ok I solved the build problem. This command:
*svn cat http://svn.tudos.org/repos/oc/tudos/trunk/repomgr http://svn.tudos.org/repos/oc/tudos/trunk/repomgr | perl - init http://svn.tudos.org/repos/oc/tudos <http://svn.tudos.org/repos/oc/tudos
fiasco l4re*
from: http://l4re.org/download.html doesn't grab all the l4 packages.
Indeed, it only checks out a subset. To fetch all, 'all' could be specified instead of 'fiasco l4re'.
I downloaded the latest tarball snapshot and they were all there.
The other possibility.
and it built ok. Now when it runs fbdrv page faults. Has anyone seen this before? danke
fbdrv | Trying execution of ``set VBE mode'' using x86emu fbdrv | Found VESA BIOS version 2.0 fbdrv | OEM VGABIOS Cirrus extension fbdrv | Scanning for 'best' possible mode: fbdrv | Trying to read DDC info fbdrv | DDC function not supported fbdrv | EDID not available (-19), finding best possible mode ... fbdrv | Mode: 0x101 640x480@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x110 640x480@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x111 640x480@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x112 640x480@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x103 800x600@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x113 800x600@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x114 800x600@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x115 800x600@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x105 1024x768@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x116 1024x768@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x117 1024x768@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x118 1024x768@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x107 1280x1024@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x119 1280x1024@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Choosen mode: fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | To force a specific setting use a '-m <mode>' option. fbdrv | L4Re[rm]: mapping for page fault failed with -34 @1a0000 pc=1006452 fbdrv | L4Re: unhandled exception: pc=0x1006452
This looks like io does not like to hand out the framebuffer memory. Any change when specifying, for example, -m 0x114 ? Does io say something noteworthy, possibly with some -v options supplied?
Adam
Adam adam@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
On Mon, Jun 16, 2014 at 11:12:22AM -0400, teclis High Elf wrote:
I'm not sure its IO and the frame buffer memory. It fails on X86EMU_exec() in x86emu_int10_set_vbemode() called from Vesa_fb::setup_drv() before the first call to l4io_request_iomem()
Are testing your setup on qemu? In that case the VGA bios may attempt to access the Qemu debug IO port at 0x402. You can try adding that port to the VGA device.
Matthias.
On Tue, Jun 10, 2014 at 5:17 PM, Adam Lackorzynski < adam@os.inf.tu-dresden.de> wrote:
On Tue Jun 10, 2014 at 14:20:54 -0400, teclis High Elf wrote:
Ok I solved the build problem. This command:
*svn cat http://svn.tudos.org/repos/oc/tudos/trunk/repomgr http://svn.tudos.org/repos/oc/tudos/trunk/repomgr | perl - init http://svn.tudos.org/repos/oc/tudos <http://svn.tudos.org/repos/oc/tudos
fiasco l4re*
from: http://l4re.org/download.html doesn't grab all the l4 packages.
Indeed, it only checks out a subset. To fetch all, 'all' could be specified instead of 'fiasco l4re'.
I downloaded the latest tarball snapshot and they were all there.
The other possibility.
and it built ok. Now when it runs fbdrv page faults. Has anyone seen this before? danke
fbdrv | Trying execution of ``set VBE mode'' using x86emu fbdrv | Found VESA BIOS version 2.0 fbdrv | OEM VGABIOS Cirrus extension fbdrv | Scanning for 'best' possible mode: fbdrv | Trying to read DDC info fbdrv | DDC function not supported fbdrv | EDID not available (-19), finding best possible mode ... fbdrv | Mode: 0x101 640x480@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x110 640x480@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x111 640x480@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x112 640x480@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x103 800x600@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x113 800x600@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x114 800x600@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x115 800x600@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x105 1024x768@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x116 1024x768@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x117 1024x768@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x118 1024x768@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x107 1280x1024@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x119 1280x1024@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Choosen mode: fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | To force a specific setting use a '-m <mode>' option. fbdrv | L4Re[rm]: mapping for page fault failed with -34 @1a0000 pc=1006452 fbdrv | L4Re: unhandled exception: pc=0x1006452
This looks like io does not like to hand out the framebuffer memory. Any change when specifying, for example, -m 0x114 ? Does io say something noteworthy, possibly with some -v options supplied?
Adam
Adam adam@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Its already there (from x86-legacy.devs): VGA = Hw.Device { hid = "PNP0900"; Res.io(0x3b0, 0x3bf); -- MDA Res.io(0x3c0, 0x3df); -- EGA/VGA Res.io(0x1ce, 0x1d0); -- Vbox Res.io(0x402, 0x402); -- QEMU Debug Port Res.mmio(0xa0000, 0xbffff); },
On Wed, Jun 18, 2014 at 8:14 AM, Matthias Lange < matthias.lange@kernkonzept.com> wrote:
On Mon, Jun 16, 2014 at 11:12:22AM -0400, teclis High Elf wrote:
I'm not sure its IO and the frame buffer memory. It fails on
X86EMU_exec()
in x86emu_int10_set_vbemode() called from Vesa_fb::setup_drv() before the first call to l4io_request_iomem()
Are testing your setup on qemu? In that case the VGA bios may attempt to access the Qemu debug IO port at 0x402. You can try adding that port to the VGA device.
Matthias.
On Tue, Jun 10, 2014 at 5:17 PM, Adam Lackorzynski < adam@os.inf.tu-dresden.de> wrote:
On Tue Jun 10, 2014 at 14:20:54 -0400, teclis High Elf wrote:
Ok I solved the build problem. This command:
*svn cat http://svn.tudos.org/repos/oc/tudos/trunk/repomgr http://svn.tudos.org/repos/oc/tudos/trunk/repomgr | perl - init http://svn.tudos.org/repos/oc/tudos <
http://svn.tudos.org/repos/oc/tudos
fiasco l4re*
from: http://l4re.org/download.html doesn't grab all the l4
packages.
Indeed, it only checks out a subset. To fetch all, 'all' could be specified instead of 'fiasco l4re'.
I downloaded the latest tarball snapshot and they were all there.
The other possibility.
and it built ok. Now when it runs fbdrv page faults. Has anyone seen
this
before? danke
fbdrv | Trying execution of ``set VBE mode'' using x86emu fbdrv | Found VESA BIOS version 2.0 fbdrv | OEM VGABIOS Cirrus extension fbdrv | Scanning for 'best' possible mode: fbdrv | Trying to read DDC info fbdrv | DDC function not supported fbdrv | EDID not available (-19), finding best possible mode ... fbdrv | Mode: 0x101 640x480@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x110 640x480@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x111 640x480@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x112 640x480@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x103 800x600@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x113 800x600@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x114 800x600@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x115 800x600@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x105 1024x768@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x116 1024x768@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x117 1024x768@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x118 1024x768@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x107 1280x1024@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x119 1280x1024@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Choosen mode: fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | To force a specific setting use a '-m <mode>' option. fbdrv | L4Re[rm]: mapping for page fault failed with -34 @1a0000 pc=1006452 fbdrv | L4Re: unhandled exception: pc=0x1006452
This looks like io does not like to hand out the framebuffer memory. Any change when specifying, for example, -m 0x114 ? Does io say something noteworthy, possibly with some -v options supplied?
Adam
Adam adam@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
-- Matthias Lange, matthias.lange@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129. Geschäftsführer: Dr.-Ing. Michael Hohmuth
I noticed in x86-fb.io there is a:
dev3 => wrap(hw-root.match("PNP0100"));
but no matching device in x86-legacy.devs
On Wed, Jun 18, 2014 at 8:30 AM, teclis High Elf teclis.high.elf@gmail.com wrote:
Its already there (from x86-legacy.devs): VGA = Hw.Device { hid = "PNP0900"; Res.io(0x3b0, 0x3bf); -- MDA Res.io(0x3c0, 0x3df); -- EGA/VGA Res.io(0x1ce, 0x1d0); -- Vbox Res.io(0x402, 0x402); -- QEMU Debug Port Res.mmio(0xa0000, 0xbffff); },
On Wed, Jun 18, 2014 at 8:14 AM, Matthias Lange < matthias.lange@kernkonzept.com> wrote:
On Mon, Jun 16, 2014 at 11:12:22AM -0400, teclis High Elf wrote:
I'm not sure its IO and the frame buffer memory. It fails on
X86EMU_exec()
in x86emu_int10_set_vbemode() called from Vesa_fb::setup_drv() before
the
first call to l4io_request_iomem()
Are testing your setup on qemu? In that case the VGA bios may attempt to access the Qemu debug IO port at 0x402. You can try adding that port to the VGA device.
Matthias.
On Tue, Jun 10, 2014 at 5:17 PM, Adam Lackorzynski < adam@os.inf.tu-dresden.de> wrote:
On Tue Jun 10, 2014 at 14:20:54 -0400, teclis High Elf wrote:
Ok I solved the build problem. This command:
*svn cat http://svn.tudos.org/repos/oc/tudos/trunk/repomgr http://svn.tudos.org/repos/oc/tudos/trunk/repomgr | perl - init http://svn.tudos.org/repos/oc/tudos <
http://svn.tudos.org/repos/oc/tudos
fiasco l4re*
from: http://l4re.org/download.html doesn't grab all the l4
packages.
Indeed, it only checks out a subset. To fetch all, 'all' could be specified instead of 'fiasco l4re'.
I downloaded the latest tarball snapshot and they were all there.
The other possibility.
and it built ok. Now when it runs fbdrv page faults. Has anyone
seen this
before? danke
fbdrv | Trying execution of ``set VBE mode'' using x86emu fbdrv | Found VESA BIOS version 2.0 fbdrv | OEM VGABIOS Cirrus extension fbdrv | Scanning for 'best' possible mode: fbdrv | Trying to read DDC info fbdrv | DDC function not supported fbdrv | EDID not available (-19), finding best possible mode ... fbdrv | Mode: 0x101 640x480@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x110 640x480@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x111 640x480@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x112 640x480@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x103 800x600@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x113 800x600@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x114 800x600@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x115 800x600@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x105 1024x768@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x116 1024x768@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x117 1024x768@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x118 1024x768@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x107 1280x1024@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x119 1280x1024@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Choosen mode: fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | To force a specific setting use a '-m <mode>' option. fbdrv | L4Re[rm]: mapping for page fault failed with -34 @1a0000 pc=1006452 fbdrv | L4Re: unhandled exception: pc=0x1006452
This looks like io does not like to hand out the framebuffer memory. Any change when specifying, for example, -m 0x114 ? Does io say something noteworthy, possibly with some -v options supplied?
Adam
Adam adam@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
-- Matthias Lange, matthias.lange@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129. Geschäftsführer: Dr.-Ing. Michael Hohmuth
I tried forcing the mode using the -m option and I get this:
IO | Executed 0 _INI methods requiring 1 _STA executions (examined 53 objects) IO | ACPICA-Version:20121018, System in ACPI MODE, 32bit timer IO | <0xb120>IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=44201) IO | <0x16b38>IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=44201) IO | rom/x86-fb.io:18.30-38: warning: could not find 'PNP0100' IO | Ready. Waiting for request. mag | Hello from MAG mag | Error: Exception: Void capability invoked: requesting goos info: backtrace ... mag | 1002260 mag | 100253e mag | 1065ef6 mag | 1000e34 mag | 106f105 mag | 10001c1 mag | mag | MAG: destroy FB svc Ned[lua]: Warning: Capability 42e000 does not support the meta protocol: -2004 Ned: ERROR: rom/x86-fb.cfg:61: attempt to call method 'create' (a nil value)
On Wed, Jun 18, 2014 at 1:56 PM, teclis High Elf teclis.high.elf@gmail.com wrote:
I noticed in x86-fb.io there is a:
dev3 => wrap(hw-root.match("PNP0100"));
but no matching device in x86-legacy.devs
On Wed, Jun 18, 2014 at 8:30 AM, teclis High Elf < teclis.high.elf@gmail.com> wrote:
Its already there (from x86-legacy.devs): VGA = Hw.Device { hid = "PNP0900"; Res.io(0x3b0, 0x3bf); -- MDA Res.io(0x3c0, 0x3df); -- EGA/VGA Res.io(0x1ce, 0x1d0); -- Vbox Res.io(0x402, 0x402); -- QEMU Debug Port Res.mmio(0xa0000, 0xbffff); },
On Wed, Jun 18, 2014 at 8:14 AM, Matthias Lange < matthias.lange@kernkonzept.com> wrote:
On Mon, Jun 16, 2014 at 11:12:22AM -0400, teclis High Elf wrote:
I'm not sure its IO and the frame buffer memory. It fails on
X86EMU_exec()
in x86emu_int10_set_vbemode() called from Vesa_fb::setup_drv() before
the
first call to l4io_request_iomem()
Are testing your setup on qemu? In that case the VGA bios may attempt to access the Qemu debug IO port at 0x402. You can try adding that port to the VGA device.
Matthias.
On Tue, Jun 10, 2014 at 5:17 PM, Adam Lackorzynski < adam@os.inf.tu-dresden.de> wrote:
On Tue Jun 10, 2014 at 14:20:54 -0400, teclis High Elf wrote:
Ok I solved the build problem. This command:
*svn cat http://svn.tudos.org/repos/oc/tudos/trunk/repomgr http://svn.tudos.org/repos/oc/tudos/trunk/repomgr | perl - init http://svn.tudos.org/repos/oc/tudos <
http://svn.tudos.org/repos/oc/tudos
fiasco l4re*
from: http://l4re.org/download.html doesn't grab all the l4
packages.
Indeed, it only checks out a subset. To fetch all, 'all' could be specified instead of 'fiasco l4re'.
I downloaded the latest tarball snapshot and they were all there.
The other possibility.
and it built ok. Now when it runs fbdrv page faults. Has anyone
seen this
before? danke
fbdrv | Trying execution of ``set VBE mode'' using x86emu fbdrv | Found VESA BIOS version 2.0 fbdrv | OEM VGABIOS Cirrus extension fbdrv | Scanning for 'best' possible mode: fbdrv | Trying to read DDC info fbdrv | DDC function not supported fbdrv | EDID not available (-19), finding best possible mode ... fbdrv | Mode: 0x101 640x480@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x110 640x480@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x111 640x480@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x112 640x480@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x103 800x600@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x113 800x600@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x114 800x600@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x115 800x600@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x105 1024x768@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x116 1024x768@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x117 1024x768@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x118 1024x768@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x107 1280x1024@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x119 1280x1024@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Choosen mode: fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | To force a specific setting use a '-m <mode>' option. fbdrv | L4Re[rm]: mapping for page fault failed with -34 @1a0000 pc=1006452 fbdrv | L4Re: unhandled exception: pc=0x1006452
This looks like io does not like to hand out the framebuffer memory. Any change when specifying, for example, -m 0x114 ? Does io say something noteworthy, possibly with some -v options supplied?
Adam
Adam adam@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
-- Matthias Lange, matthias.lange@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129. Geschäftsführer: Dr.-Ing. Michael Hohmuth
On 20 Jun 2014, at 20:06, teclis High Elf teclis.high.elf@gmail.com wrote:
I tried forcing the mode using the -m option and I get this:
IO | Executed 0 _INI methods requiring 1 _STA executions (examined 53 objects) IO | ACPICA-Version:20121018, System in ACPI MODE, 32bit timer IO | <0xb120>IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=44201) IO | <0x16b38>IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=44201) IO | rom/x86-fb.io:18.30-38: warning: could not find 'PNP0100' IO | Ready. Waiting for request. mag | Hello from MAG mag | Error: Exception: Void capability invoked: requesting goos info: backtrace ... mag | 1002260 mag | 100253e mag | 1065ef6 mag | 1000e34 mag | 106f105 mag | 10001c1 mag | mag | MAG: destroy FB svc Ned[lua]: Warning: Capability 42e000 does not support the meta protocol: -2004 Ned: ERROR: rom/x86-fb.cfg:61: attempt to call method 'create' (a nil value)
Please run io with a couple of "-v" options to make it more verbose. It should print the hardware device tree as read from ACPI.
Matthias.
On Wed, Jun 18, 2014 at 1:56 PM, teclis High Elf teclis.high.elf@gmail.com wrote: I noticed in x86-fb.io there is a:
dev3 => wrap(hw-root.match("PNP0100"));
but no matching device in x86-legacy.devs
On Wed, Jun 18, 2014 at 8:30 AM, teclis High Elf teclis.high.elf@gmail.com wrote: Its already there (from x86-legacy.devs): VGA = Hw.Device { hid = "PNP0900"; Res.io(0x3b0, 0x3bf); -- MDA Res.io(0x3c0, 0x3df); -- EGA/VGA Res.io(0x1ce, 0x1d0); -- Vbox Res.io(0x402, 0x402); -- QEMU Debug Port Res.mmio(0xa0000, 0xbffff); },
On Wed, Jun 18, 2014 at 8:14 AM, Matthias Lange matthias.lange@kernkonzept.com wrote: On Mon, Jun 16, 2014 at 11:12:22AM -0400, teclis High Elf wrote:
I'm not sure its IO and the frame buffer memory. It fails on X86EMU_exec() in x86emu_int10_set_vbemode() called from Vesa_fb::setup_drv() before the first call to l4io_request_iomem()
Are testing your setup on qemu? In that case the VGA bios may attempt to access the Qemu debug IO port at 0x402. You can try adding that port to the VGA device.
Matthias.
On Tue, Jun 10, 2014 at 5:17 PM, Adam Lackorzynski < adam@os.inf.tu-dresden.de> wrote:
On Tue Jun 10, 2014 at 14:20:54 -0400, teclis High Elf wrote: > Ok I solved the build problem. This command: > > > *svn cat http://svn.tudos.org/repos/oc/tudos/trunk/repomgr > http://svn.tudos.org/repos/oc/tudos/trunk/repomgr | perl - init > http://svn.tudos.org/repos/oc/tudos http://svn.tudos.org/repos/oc/tudos > fiasco l4re* > > from: http://l4re.org/download.html doesn't grab all the l4 packages.
Indeed, it only checks out a subset. To fetch all, 'all' could be specified instead of 'fiasco l4re'.
> I downloaded the latest tarball snapshot and they were all there.
The other possibility.
> and it built ok. Now when it runs fbdrv page faults. Has anyone seen this > before? danke > > fbdrv | Trying execution of ``set VBE mode'' using x86emu > fbdrv | Found VESA BIOS version 2.0 > fbdrv | OEM VGABIOS Cirrus extension > fbdrv | Scanning for 'best' possible mode: > fbdrv | Trying to read DDC info > fbdrv | DDC function not supported > fbdrv | EDID not available (-19), finding best possible mode ... > fbdrv | Mode: 0x101 640x480@8, RGB: 0(0):0(0):0(0) mode: bb > fbdrv | Mode: 0x110 640x480@15, RGB: 10(5):5(5):0(5) mode: bb > fbdrv | Mode: 0x111 640x480@16, RGB: 11(5):5(6):0(5) mode: bb > fbdrv | Mode: 0x112 640x480@24, RGB: 16(8):8(8):0(8) mode: bb > fbdrv | Mode: 0x103 800x600@8, RGB: 0(0):0(0):0(0) mode: bb > fbdrv | Mode: 0x113 800x600@15, RGB: 10(5):5(5):0(5) mode: bb > fbdrv | Mode: 0x114 800x600@16, RGB: 11(5):5(6):0(5) mode: bb > fbdrv | Mode: 0x115 800x600@24, RGB: 16(8):8(8):0(8) mode: bb > fbdrv | Mode: 0x105 1024x768@8, RGB: 0(0):0(0):0(0) mode: bb > fbdrv | Mode: 0x116 1024x768@15, RGB: 10(5):5(5):0(5) mode: bb > fbdrv | Mode: 0x117 1024x768@16, RGB: 11(5):5(6):0(5) mode: bb > fbdrv | Mode: 0x118 1024x768@24, RGB: 16(8):8(8):0(8) mode: bb > fbdrv | Mode: 0x107 1280x1024@8, RGB: 0(0):0(0):0(0) mode: bb > fbdrv | Mode: 0x119 1280x1024@15, RGB: 10(5):5(5):0(5) mode: bb > fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb > fbdrv | Choosen mode: > fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb > fbdrv | To force a specific setting use a '-m <mode>' option. > fbdrv | L4Re[rm]: mapping for page fault failed with -34 @1a0000 > pc=1006452 > fbdrv | L4Re: unhandled exception: pc=0x1006452
This looks like io does not like to hand out the framebuffer memory. Any change when specifying, for example, -m 0x114 ? Does io say something noteworthy, possibly with some -v options supplied?
Adam
Adam adam@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
-- Matthias Lange, matthias.lange@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129. Geschäftsführer: Dr.-Ing. Michael Hohmuth
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Ned: loading file: 'rom/x86-fb.cfg' IO | Dev_factory: register factory for N2Hw11Gpio_deviceE IO | GTF: register factory for N2Hw12Msi_resourceE IO | GTF: register factory for 7Pci_dev IO | Dev_factory: register factory for N2Hw6DeviceE IO | Io service IO | Verboseness level: 7 IO | unused physical memory space: IO | [00000018000000-000000febfffff] IO | [000000fec01000-000000fedfffff] IO | [000000fee01000-000000fffbffff] IO | Hello from L4-ACPICA IO | Find root Pointer IO | new iomem region: p=0 v=400000 s=400000 (bmb=0x36a8) IO | map mem: p=0 v=400000 s=1000: done(0) IO | AcpiOsMapMemory(40e, 2) = 40040e IO | map mem: p=9f000 v=49f000 s=1000: done(0) IO | AcpiOsMapMemory(9f400, 400) = 49f400 IO | map mem: p=e0000 v=4e0000 s=20000: done(0) IO | AcpiOsMapMemory(e0000, 20000) = 4e0000 IO | Find root Pointer: fd9a0 IO | AcpiOsMapMemory(fd9a0, 24) = 4fd9a0 IO | ACPI: RSDP 0xfd9a0 00014 (v00 BOCHS ) IO | new iomem region: p=17c00000 v=800000 s=400000 (bmb=0x3750) IO | map mem: p=17ffd000 v=bfd000 s=1000: done(0) IO | AcpiOsMapMemory(17ffd7b0, 24) = bfd7b0 IO | ACPI: RSDT 0x17ffd7b0 00034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001) IO | AcpiOsMapMemory(17ffd7b0, 34) = bfd7b0 IO | map mem: p=17fff000 v=bff000 s=1000: done(0) IO | AcpiOsMapMemory(17ffff80, 24) = bfff80 IO | /home/jbutler/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:344:AcpiOsPhysicalTableOverride(0xbfff80, 0x80007b78, 0x80007b7c): UNINPLEMENTED IO | ACPI: FACP 0x17ffff80 00074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001) IO | AcpiOsMapMemory(17ffff80, 74) = bfff80 IO | AcpiOsMapMemory(17ffd9b0, 24) = bfd9b0 IO | /home/jbutler/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:344:AcpiOsPhysicalTableOverride(0xbfd9b0, 0x80007b58, 0x80007b5c): UNINPLEMENTED IO | ACPI: DSDT 0x17ffd9b0 02589 (v01 BXPC BXDSDT 00000001 INTL 20100528) IO | AcpiOsMapMemory(17ffff40, 24) = bfff40 IO | /home/jbutler/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:344:AcpiOsPhysicalTableOverride(0xbfff40, 0x80007b58, 0x80007b5c): UNINPLEMENTED IO | ACPI: FACS 0x17ffff40 00040 IO | AcpiOsMapMemory(17ffd910, 24) = bfd910 IO | /home/jbutler/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:344:AcpiOsPhysicalTableOverride(0xbfd910, 0x80007b78, 0x80007b7c): UNINPLEMENTED IO | ACPI: SSDT 0x17ffd910 0009E (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001) IO | AcpiOsMapMemory(17ffd830, 24) = bfd830 IO | /home/jbutler/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:344:AcpiOsPhysicalTableOverride(0xbfd830, 0x80007b78, 0x80007b7c): UNINPLEMENTED IO | ACPI: APIC 0x17ffd830 00072 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001) IO | AcpiOsMapMemory(17ffd7f0, 24) = bfd7f0 IO | /home/jbutler/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:344:AcpiOsPhysicalTableOverride(0xbfd7f0, 0x80007b78, 0x80007b7c): UNINPLEMENTED IO | ACPI: HPET 0x17ffd7f0 00038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001) IO | map mem: p=17ffe000 v=bfe000 s=1000: done(0) IO | AcpiOsMapMemory(17ffd9b0, 2589) = bfd9b0 IO | Parsing all Control Methods: IO | Table [DSDT](id 0001) - 383 Objects with 77 Devices 118 Methods 8 Regions IO | AcpiOsMapMemory(17ffd910, 9e) = bfd910 IO | Parsing all Control Methods: IO | Table [SSDT](id 0002) - 8 Objects with 0 Devices 4 Methods 0 Regions IO | tbxfload-0274 [02] TbLoadNamespace : ACPI Tables successfully acquired IO | enable ACPI subsystem IO | evxfevnt-0175 [02] Enable : Transition to ACPI mode successful IO | AcpiOsMapMemory(17ffff40, 40) = bfff40 IO | evgpeblk-0523 [04] EvCreateGpeBlock : GPE 00 to 0F [_GPE] 2 regs on int 0x9 IO | /home/jbutler/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:60:AcpiOsInstallInterruptHandler(9, 0x1083ef0, 0x3a48): UNINPLEMENTED IO | initialize ACPI objects IO | Completing Region/Field/Buffer/Package initialization:..................... IO | Initialized 8/8 Regions 0/0 Fields 8/8 Buffers 5/5 Packages (400 nodes) IO | Initializing Device/Processor/Thermal objects by executing _INI methods: IO | Executed 0 _INI methods requiring 0 _STA executions (examined 80 objects) IO | Interpreter enabled IO | scanning for PCI root bridge IO | Found PCI root bridge... IO | Using IOAPIC for interrupt routing IO | ACPI subsystem initialized IO | ACPICA-Version:20121018, System in ACPI MODE, 32bit timer IO | (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKS][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKB][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKC][0]) (dev[_SB_.LNKD][0]) (dev[_SB_.LNKA][0]) (dev[_SB_.LNKB][0]) WARNING: phys mmio resource allocation failed IO | <0x18058>IOMEM * [000000000a0000-000000000bffff 20000] non-pref (32bit) (align=1ffff flags=c002) IO | WARNING: phys mmio resource allocation failed IO | <0x18058>IOMEM * [000000000a0000-000000000bffff 20000] non-pref (32bit) (align=1ffff flags=c002) IO | <0x18458>IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=44201) IO | requesting IRQ resource: Hw::Device[S3__] IO | 0000:00:03.0: network controller [0] IO | 0x10ec 0x8139 IO | Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ IO | <0x18458> IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=44201) IO | at ACPI IRQ routing resource IO | <0x184e0>IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=44201) IO | requesting IRQ resource: Hw::Device[PX13] IO | 0000:00:01.3: bridge device [0] IO | 0x8086 0x7113 IO | Intel Corporation 82371AB/EB/MB PIIX4 ACPI IO | <0x184e0> IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=44201) IO | at ACPI IRQ routing resource IO | WARNING: ignoring ACPI resource (unkown type: 1) IO | Loading: config 'rom/x86-legacy.devs' IO | WARNING: phys mmio resource allocation failed IO | <0x30370>IOMEM [00000000000000-00000000000fff 1000] non-pref (32bit) (align=fff flags=c002) IO | WARNING: phys mmio resource allocation failed IO | <0x30370>IOMEM [00000000000000-00000000000fff 1000] non-pref (32bit) (align=fff flags=c002) IO | WARNING: phys mmio resource allocation failed IO | <0x303c0>IOMEM [0000000009f000-0000000009ffff 1000] non-pref (32bit) (align=fff flags=c002) IO | WARNING: phys mmio resource allocation failed IO | <0x303c0>IOMEM [0000000009f000-0000000009ffff 1000] non-pref (32bit) (align=fff flags=c002) IO | WARNING: phys mmio resource allocation failed IO | <0x30410>IOMEM [000000000c0000-000000000fffff 40000] non-pref (32bit) (align=3ffff flags=c002) IO | WARNING: phys mmio resource allocation failed IO | <0x30410>IOMEM [000000000c0000-000000000fffff 40000] non-pref (32bit) (align=3ffff flags=c002) IO | WARNING: phys mmio resource allocation failed IO | <0x31458>IOMEM [000000000a0000-000000000bffff 20000] non-pref (32bit) (align=1ffff flags=4002) IO | WARNING: phys mmio resource allocation failed IO | <0x31458>IOMEM [000000000a0000-000000000bffff 20000] non-pref (32bit) (align=1ffff flags=4002) IO | allocated resource: <0x31458>IOMEM [00000018000000-0000001801ffff 20000] non-pref (32bit) (align=1ffff flags=4002) IO | allocated resource: <0x31458>IOMEM [00000018000000-0000001801ffff 20000] non-pref (32bit) (align=1ffff flags=4002) IO | Loading: config 'rom/x86-fb.io' IO | rom/x86-fb.io:18.30-38: warning: could not find 'PNP0100' IO | Add IRQ resources to vbus: <0x31710>IRQ [00000000000001-00000000000001 1] none (32bit) (align=0 flags=4001) IO | Add IRQ resources to vbus: <0x31760>IRQ [0000000000000c-0000000000000c 1] none (32bit) (align=0 flags=4001) IO | P6Device: gui "" IO | P6Device: (noname) "L40009" IO | P6Device: ps2dev "PNP0303" IO | <0x31670> IOPORT [00000000000060-00000000000060 1] non-pref (32bit) (align=0 flags=4003) IO | <0x316c0> IOPORT [00000000000064-00000000000064 1] non-pref (32bit) (align=0 flags=4003) IO | <0x31710> IRQ [00000000000001-00000000000001 1] none (32bit) (align=0 flags=4001) IO | <0x31760> IRQ [0000000000000c-0000000000000c 1] none (32bit) (align=0 flags=4001) IO | P6Device: ps2dev "PNP0F13" IO | <0xc2d8> IRQ [0000000000000c-0000000000000c 1] raising edge (32bit) (align=0 flags=104001) IO | P6Device: ps2dev "PNP0303" IO | <0xc240> IOPORT [00000000000060-00000000000060 1] non-pref (32bit) (align=0 flags=c003) IO | <0xc268> IOPORT [00000000000064-00000000000064 1] non-pref (32bit) (align=0 flags=c003) IO | <0xc290> IRQ [00000000000001-00000000000001 1] raising edge (32bit) (align=0 flags=104001) IO | P6Device: fbdrv "" IO | P6Device: (noname) "L40009" IO | P6Device: PCI0 "PNP0A03" IO | P6Device: host_bridge_dummy "" IO | P6Device: pci_gfx[0000] "" IO | <0x172f0> IOMEM [000000fc000000-000000fdffffff 2000000] pref (32bit) (align=1ffffff flags=4e02) IO | <0x18410> IOMEM [000000febf0000-000000febf0fff 1000] non-pref (32bit) (align=fff flags=4a02) IO | P6Device: dev1 "BIOS" IO | <0x30370> IOMEM [00000000000000-00000000000fff 1000] non-pref (32bit) (align=fff flags=c002) IO | <0x303c0> IOMEM [0000000009f000-0000000009ffff 1000] non-pref (32bit) (align=fff flags=c002) IO | <0x30410> IOMEM [000000000c0000-000000000fffff 40000] non-pref (32bit) (align=3ffff flags=c002) IO | P6Device: dev2 "PNP0900" IO | <0x30a00> IOPORT [000000000003b0-000000000003bf 10] non-pref (32bit) (align=f flags=4003) IO | <0x30a50> IOPORT [000000000003c0-000000000003df 20] non-pref (32bit) (align=1f flags=4003) IO | <0x30aa0> IOPORT [000000000001ce-000000000001d0 3] non-pref (32bit) (align=2 flags=4003) IO | <0x31408> IOPORT [00000000000402-00000000000402 1] non-pref (32bit) (align=0 flags=4003) IO | <0x31458> IOMEM [00000018000000-0000001801ffff 20000] non-pref (32bit) (align=1ffff flags=4002) IO | Real Hardware ----------------------------------- IO | P6Device: System Bus "" IO | Hw::Device[System Bus] IO | P6Device: PCI0 "PNP0A03" IO | Hw::Device[PCI0] IO | PCI IRQ ROUTER: 18Pci_irq_router_resIN12_GLOBAL__N_122Acpi_pci_irq_router_rsEE (0x185f0) IO | <0x17348> BUS * [00000000000000-000000000000ff 100] non-pref (32bit) (align=ff flags=c004) IO | <0x101e8> IOPORT [00000000000cf8-00000000000cff 8] non-pref (32bit) (align=7 flags=c003) IO | <0x17380> IOPORT* [00000000000000-00000000000cf7 cf8] non-pref (32bit) (align=cf7 flags=c003) IO | <0x18020> IOPORT* [00000000000d00-0000000000ffff f300] non-pref (32bit) (align=f2ff flags=c003) IO | <0x18058> IOMEM * [000000000a0000-000000000bffff 20000] non-pref (32bit) (align=1ffff flags=c002) IO | <0x18090> IOMEM * [000000e0000000-000000febfffff 1ec00000] non-pref (32bit) (align=1ebfffff flags=c002) IO | P6Device: S1__ "" IO | Hw::Device[S1__] IO | 0000:00:01.0: ISA Bridge [128] IO | 0x8086 0x7000 IO | Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] IO | P6Device: S2__ "" IO | Hw::Device[S2__] IO | 0000:00:02.0: display controller [0] IO | 0x1013 0x00b8 IO | Cirrus Logic GD 5446 IO | <0x172f0> IOMEM [000000fc000000-000000fdffffff 2000000] pref (32bit) (align=1ffffff flags=4e02) IO | <0x18410> IOMEM [000000febf0000-000000febf0fff 1000] non-pref (32bit) (align=fff flags=4a02) IO | P6Device: S3__ "" IO | Hw::Device[S3__] IO | 0000:00:03.0: network controller [0] IO | 0x10ec 0x8139 IO | Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (#2) IO | <0x18458> IRQ [0000000000000b-0000000000000b 1] level high (32bit) (align=0 flags=304201) IO | <0x18480> IOPORT [0000000000c000-0000000000c0ff 100] non-pref (32bit) (align=ff flags=4a03) IO | <0x184b8> IOMEM [000000febf1000-000000febf10ff 100] non-pref (32bit) (align=ff flags=4a02) IO | P6Device: S4__ "" IO | Hw::Device[S4__] IO | P6Device: S5__ "" IO | Hw::Device[S5__] IO | P6Device: S6__ "" IO | Hw::Device[S6__] IO | P6Device: S7__ "" IO | Hw::Device[S7__] IO | P6Device: S8__ "" IO | Hw::Device[S8__] IO | P6Device: S9__ "" IO | Hw::Device[S9__] IO | P6Device: S10_ "" IO | Hw::Device[S10_] IO | P6Device: S11_ "" IO | Hw::Device[S11_] IO | P6Device: S12_ "" IO | Hw::Device[S12_] IO | P6Device: S13_ "" IO | Hw::Device[S13_] IO | P6Device: S14_ "" IO | Hw::Device[S14_] IO | P6Device: S15_ "" IO | Hw::Device[S15_] IO | P6Device: S16_ "" IO | Hw::Device[S16_] IO | P6Device: S17_ "" IO | Hw::Device[S17_] IO | P6Device: S18_ "" IO | Hw::Device[S18_] IO | P6Device: S19_ "" IO | Hw::Device[S19_] IO | P6Device: S20_ "" IO | Hw::Device[S20_] IO | P6Device: S21_ "" IO | Hw::Device[S21_] IO | P6Device: S22_ "" IO | Hw::Device[S22_] IO | P6Device: S23_ "" IO | Hw::Device[S23_] IO | P6Device: S24_ "" IO | Hw::Device[S24_] IO | P6Device: S25_ "" IO | Hw::Device[S25_] IO | P6Device: S26_ "" IO | Hw::Device[S26_] IO | P6Device: S27_ "" IO | Hw::Device[S27_] IO | P6Device: S28_ "" IO | Hw::Device[S28_] IO | P6Device: S29_ "" IO | Hw::Device[S29_] IO | P6Device: S30_ "" IO | Hw::Device[S30_] IO | P6Device: S31_ "" IO | Hw::Device[S31_] IO | P6Device: VGA_ "" IO | Hw::Device[VGA_] IO | P6Device: ISA_ "" IO | Hw::Device[ISA_] IO | P6Device: RTC_ "PNP0B00" IO | Hw::Device[RTC_] IO | <0xc160> IOPORT [00000000000070-00000000000071 2] non-pref (32bit) (align=1 flags=c003) IO | <0xc188> IRQ [00000000000008-00000000000008 1] raising edge (32bit) (align=0 flags=104001) IO | <0xc1b0> IOPORT [00000000000072-00000000000077 6] non-pref (32bit) (align=5 flags=c003) IO | P6Device: KBD_ "PNP0303" IO | Hw::Device[KBD_] IO | <0xc240> IOPORT [00000000000060-00000000000060 1] non-pref (32bit) (align=0 flags=c003) IO | <0xc268> IOPORT [00000000000064-00000000000064 1] non-pref (32bit) (align=0 flags=c003) IO | <0xc290> IRQ [00000000000001-00000000000001 1] raising edge (32bit) (align=0 flags=104001) IO | P6Device: MOU_ "PNP0F13" IO | Hw::Device[MOU_] IO | <0xc2d8> IRQ [0000000000000c-0000000000000c 1] raising edge (32bit) (align=0 flags=104001) IO | P6Device: FDC0 "PNP0700" IO | Hw::Device[FDC0] IO | <0xc370> IOPORT [000000000003f2-000000000003f5 4] non-pref (32bit) (align=3 flags=c003) IO | <0xc398> IOPORT [000000000003f7-000000000003f7 1] non-pref (32bit) (align=0 flags=c003) IO | <0xc3c0> IRQ [00000000000006-00000000000006 1] raising edge (32bit) (align=0 flags=104001) IO | P6Device: LPT_ "PNP0400" IO | Hw::Device[LPT_] IO | <0xc418> IOPORT [00000000000378-0000000000037f 8] non-pref (32bit) (align=7 flags=c003) IO | <0xc440> IRQ [00000000000007-00000000000007 1] raising edge (32bit) (align=0 flags=104001) IO | P6Device: COM1 "PNP0501" IO | Hw::Device[COM1] IO | <0xc1d8> IOPORT [000000000003f8-000000000003ff 8] non-pref (32bit) (align=7 flags=c003) IO | <0xc200> IRQ [00000000000004-00000000000004 1] raising edge (32bit) (align=0 flags=104001) IO | P6Device: COM2 "PNP0501" IO | Hw::Device[COM2] IO | <0xc0e0> IOPORT [000000000002f8-000000000002ff 8] non-pref (32bit) (align=7 flags=c003) IO | <0xc108> IRQ [00000000000003-00000000000003 1] raising edge (32bit) (align=0 flags=104001) IO | P6Device: PX13 "" IO | Hw::Device[PX13] IO | 0000:00:01.3: bridge device [0] IO | 0x8086 0x7113 IO | Intel Corporation 82371AB/EB/MB PIIX4 ACPI (#2) IO | <0x184e0> IRQ [0000000000000a-0000000000000a 1] level high (32bit) (align=0 flags=304201) IO | P6Device: SL3_ "" IO | Hw::Device[SL3_] IO | P6Device: SL4_ "" IO | Hw::Device[SL4_] IO | P6Device: SL5_ "" IO | Hw::Device[SL5_] IO | P6Device: SL6_ "" IO | Hw::Device[SL6_] IO | P6Device: SL7_ "" IO | Hw::Device[SL7_] IO | P6Device: SL8_ "" IO | Hw::Device[SL8_] IO | P6Device: SL9_ "" IO | Hw::Device[SL9_] IO | P6Device: SL10 "" IO | Hw::Device[SL10] IO | P6Device: SL11 "" IO | Hw::Device[SL11] IO | P6Device: SL12 "" IO | Hw::Device[SL12] IO | P6Device: SL13 "" IO | Hw::Device[SL13] IO | P6Device: SL14 "" IO | Hw::Device[SL14] IO | P6Device: SL15 "" IO | Hw::Device[SL15] IO | P6Device: SL16 "" IO | Hw::Device[SL16] IO | P6Device: SL17 "" IO | Hw::Device[SL17] IO | P6Device: SL18 "" IO | Hw::Device[SL18] IO | P6Device: SL19 "" IO | Hw::Device[SL19] IO | P6Device: SL20 "" IO | Hw::Device[SL20] IO | P6Device: SL21 "" IO | Hw::Device[SL21] IO | P6Device: SL22 "" IO | Hw::Device[SL22] IO | P6Device: SL23 "" IO | Hw::Device[SL23] IO | P6Device: SL24 "" IO | Hw::Device[SL24] IO | P6Device: SL25 "" IO | Hw::Device[SL25] IO | P6Device: SL26 "" IO | Hw::Device[SL26] IO | P6Device: SL27 "" IO | Hw::Device[SL27] IO | P6Device: SL28 "" IO | Hw::Device[SL28] IO | P6Device: SL29 "" IO | Hw::Device[SL29] IO | P6Device: SL30 "" IO | Hw::Device[SL30] IO | P6Device: SL31 "" IO | Hw::Device[SL31] IO | P6Device: "" IO | Hw::Device[] IO | 0000:00:00.0: Host/PCI Bridge [0] IO | 0x8086 0x1237 IO | Intel Corporation 440FX - 82441FX PMC [Natoma] IO | P6Device: "" IO | Hw::Device[] IO | 0000:00:01.1: mass storage contoller [0] IO | 0x8086 0x7010 IO | Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] IO | <0x18508> IOPORT [000000000001f0-000000000001f7 8] non-pref (32bit) (align=7 flags=4a03) IO | <0x18530> IOPORT [000000000003f6-000000000003f6 1] non-pref (32bit) (align=0 flags=4a03) IO | <0x18568> IRQ [0000000000000e-0000000000000e 1] raising edge (32bit) (align=0 flags=104001) IO | <0x18590> IOPORT [00000000000170-00000000000177 8] non-pref (32bit) (align=7 flags=4a03) IO | <0x185b8> IOPORT [00000000000376-00000000000376 1] non-pref (32bit) (align=0 flags=4a03) IO | <0xc090> IRQ [0000000000000f-0000000000000f 1] raising edge (32bit) (align=0 flags=104001) IO | <0xc0b8> IOPORT [0000000000c100-0000000000c10f 10] non-pref (32bit) (align=f flags=4a03) IO | P6Device: HPET "PNP0103" IO | Hw::Device[HPET] IO | <0x172a0> IOMEM [000000fed00000-000000fed003ff 400] non-pref (32bit) (align=3ff flags=c002) IO | P6Device: LNKA "PNP0C0F" IO | Hw::Device[LNKA] IO | <0x172c8> IRQ [0000000000000a-0000000000000a 1] level high (32bit) (align=0 flags=304001) IO | P6Device: LNKB "PNP0C0F" IO | Hw::Device[LNKB] IO | <0x17240> IRQ [0000000000000a-0000000000000a 1] level high (32bit) (align=0 flags=304001) IO | P6Device: LNKC "PNP0C0F" IO | Hw::Device[LNKC] IO | <0x17318> IRQ [0000000000000b-0000000000000b 1] level high (32bit) (align=0 flags=304001) IO | P6Device: LNKD "PNP0C0F" IO | Hw::Device[LNKD] IO | <0x17268> IRQ [0000000000000b-0000000000000b 1] level high (32bit) (align=0 flags=304001) IO | P6Device: LNKS "PNP0C0F" IO | Hw::Device[LNKS] IO | <0x180c8> IRQ [0000000000000a-0000000000000a 1] level high (32bit) (align=0 flags=304001) IO | P6Device: BIOS "BIOS" IO | Hw::Device[BIOS] IO | <0x30370> IOMEM [00000000000000-00000000000fff 1000] non-pref (32bit) (align=fff flags=c002) IO | <0x303c0> IOMEM [0000000009f000-0000000009ffff 1000] non-pref (32bit) (align=fff flags=c002) IO | <0x30410> IOMEM [000000000c0000-000000000fffff 40000] non-pref (32bit) (align=3ffff flags=c002) IO | P6Device: P80 "P80" IO | Hw::Device[P80] IO | <0x2cf48> IOPORT [00000000000080-00000000000080 1] non-pref (32bit) (align=0 flags=4003) IO | P6Device: RTC "PNP0B00" IO | Hw::Device[RTC] IO | <0x318d8> IOPORT [00000000000070-00000000000071 2] non-pref (32bit) (align=1 flags=4003) IO | P6Device: VGA "PNP0900" IO | Hw::Device[VGA] IO | <0x30a00> IOPORT [000000000003b0-000000000003bf 10] non-pref (32bit) (align=f flags=4003) IO | <0x30a50> IOPORT [000000000003c0-000000000003df 20] non-pref (32bit) (align=1f flags=4003) IO | <0x30aa0> IOPORT [000000000001ce-000000000001d0 3] non-pref (32bit) (align=2 flags=4003) IO | <0x31408> IOPORT [00000000000402-00000000000402 1] non-pref (32bit) (align=0 flags=4003) IO | <0x31458> IOMEM [00000018000000-0000001801ffff 20000] non-pref (32bit) (align=1ffff flags=4002) IO | P6Device: PS2 "PNP0303" IO | Hw::Device[PS2] IO | <0x31670> IOPORT [00000000000060-00000000000060 1] non-pref (32bit) (align=0 flags=4003) IO | <0x316c0> IOPORT [00000000000064-00000000000064 1] non-pref (32bit) (align=0 flags=4003) IO | <0x31710> IRQ [00000000000001-00000000000001 1] none (32bit) (align=0 flags=4001) IO | <0x31760> IRQ [0000000000000c-0000000000000c 1] none (32bit) (align=0 flags=4001) IO | Ready. Waiting for request. IO | request resource: <0x80007bb0>IOPORT [000000000003b0-000000000003bf 10] non-pref (32bit) (align=f flags=4003) IO | IO | request resource: <0x80007bb0>IOPORT [000000000003c0-000000000003df 20] non-pref (32bit) (align=1f flags=4003) IO | IO | request resource: <0x80007bb0>IOPORT [000000000001ce-000000000001cf 2] non-pref (32bit) (align=1 flags=4003) IO | IO | request resource: <0x80007bb0>IOPORT [000000000001d0-000000000001d0 1] non-pref (32bit) (align=0 flags=4003) IO | IO | request resource: <0x80007bb0>IOPORT [00000000000402-00000000000402 1] non-pref (32bit) (align=0 flags=4003) IO | fbdrv | Trying execution of ``set VBE mode'' using x86emu IO | map mem: p=c0000 v=4c0000 s=20000: done(0) mag | Hello from MAG fbdrv | Found VESA BIOS version 2.0 fbdrv | OEM VGABIOS Cirrus extension fbdrv | Scanning for 'best' possible mode: fbdrv | Trying to read DDC info fbdrv | DDC function not supported fbdrv | EDID not available (-19), finding best possible mode ... fbdrv | Mode: 0x101 640x480@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x110 640x480@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x111 640x480@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x112 640x480@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x103 800x600@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x113 800x600@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x114 800x600@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x115 800x600@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x105 1024x768@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x116 1024x768@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x117 1024x768@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Mode: 0x118 1024x768@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x107 1280x1024@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x119 1280x1024@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Choosen mode: fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | To force a specific setting use a '-m <mode>' option. fbdrv | x86emu_int10_set_vbemode, /home/jbutler/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/pkg/x86emu/lib/int10/int10.cc, 622 fbdrv | x86emu_int10_set_vbemode, /home/jbutler/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/pkg/x86emu/lib/int10/int10.cc, 624 fbdrv | x86emu_int10_set_vbemode, /home/jbutler/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/pkg/x86emu/lib/int10/int10.cc, 626 fbdrv | x86emu_int10_set_vbemode, /home/jbutler/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/pkg/x86emu/lib/int10/int10.cc, 629 fbdrv | L4Re[rm]: mapping for page fault failed with -34 @1a0000 pc=1006452 fbdrv | L4Re: unhandled exception: pc=0x1006452
On Fri, Jun 20, 2014 at 2:39 PM, Matthias Lange < matthias.lange@kernkonzept.com> wrote:
On 20 Jun 2014, at 20:06, teclis High Elf teclis.high.elf@gmail.com wrote:
I tried forcing the mode using the -m option and I get this:
IO | Executed 0 _INI methods requiring 1 _STA executions (examined 53 objects) IO | ACPICA-Version:20121018, System in ACPI MODE, 32bit timer IO | <0xb120>IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=44201) IO | <0x16b38>IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=44201) IO | rom/x86-fb.io:18.30-38: warning: could not find 'PNP0100' IO | Ready. Waiting for request. mag | Hello from MAG mag | Error: Exception: Void capability invoked: requesting goos info: backtrace ... mag | 1002260 mag | 100253e mag | 1065ef6 mag | 1000e34 mag | 106f105 mag | 10001c1 mag | mag | MAG: destroy FB svc Ned[lua]: Warning: Capability 42e000 does not support the meta protocol: -2004 Ned: ERROR: rom/x86-fb.cfg:61: attempt to call method 'create' (a nil value)
Please run io with a couple of "-v" options to make it more verbose. It should print the hardware device tree as read from ACPI.
Matthias.
On Wed, Jun 18, 2014 at 1:56 PM, teclis High Elf < teclis.high.elf@gmail.com> wrote:
I noticed in x86-fb.io there is a:
dev3 => wrap(hw-root.match("PNP0100"));
but no matching device in x86-legacy.devs
On Wed, Jun 18, 2014 at 8:30 AM, teclis High Elf < teclis.high.elf@gmail.com> wrote:
Its already there (from x86-legacy.devs): VGA = Hw.Device { hid = "PNP0900"; Res.io(0x3b0, 0x3bf); -- MDA Res.io(0x3c0, 0x3df); -- EGA/VGA Res.io(0x1ce, 0x1d0); -- Vbox Res.io(0x402, 0x402); -- QEMU Debug Port Res.mmio(0xa0000, 0xbffff); },
On Wed, Jun 18, 2014 at 8:14 AM, Matthias Lange < matthias.lange@kernkonzept.com> wrote:
On Mon, Jun 16, 2014 at 11:12:22AM -0400, teclis High Elf wrote:
I'm not sure its IO and the frame buffer memory. It fails on
X86EMU_exec()
in x86emu_int10_set_vbemode() called from Vesa_fb::setup_drv() before
the
first call to l4io_request_iomem()
Are testing your setup on qemu? In that case the VGA bios may attempt to access the Qemu debug IO port at 0x402. You can try adding that port to the VGA device.
Matthias.
On Tue, Jun 10, 2014 at 5:17 PM, Adam Lackorzynski < adam@os.inf.tu-dresden.de> wrote:
On Tue Jun 10, 2014 at 14:20:54 -0400, teclis High Elf wrote: > Ok I solved the build problem. This command: > > > *svn cat http://svn.tudos.org/repos/oc/tudos/trunk/repomgr > http://svn.tudos.org/repos/oc/tudos/trunk/repomgr | perl - init > http://svn.tudos.org/repos/oc/tudos <
http://svn.tudos.org/repos/oc/tudos
> > fiasco l4re* > > from: http://l4re.org/download.html doesn't grab all the l4
packages.
Indeed, it only checks out a subset. To fetch all, 'all' could be specified instead of 'fiasco l4re'.
> I downloaded the latest tarball snapshot and they were all there.
The other possibility.
> and it built ok. Now when it runs fbdrv page faults. Has anyone
seen this
> before? danke > > fbdrv | Trying execution of ``set VBE mode'' using x86emu > fbdrv | Found VESA BIOS version 2.0 > fbdrv | OEM VGABIOS Cirrus extension > fbdrv | Scanning for 'best' possible mode: > fbdrv | Trying to read DDC info > fbdrv | DDC function not supported > fbdrv | EDID not available (-19), finding best possible mode ... > fbdrv | Mode: 0x101 640x480@8, RGB: 0(0):0(0):0(0) mode: bb > fbdrv | Mode: 0x110 640x480@15, RGB: 10(5):5(5):0(5) mode:
bb
> fbdrv | Mode: 0x111 640x480@16, RGB: 11(5):5(6):0(5) mode:
bb
> fbdrv | Mode: 0x112 640x480@24, RGB: 16(8):8(8):0(8) mode:
bb
> fbdrv | Mode: 0x103 800x600@8, RGB: 0(0):0(0):0(0) mode: bb > fbdrv | Mode: 0x113 800x600@15, RGB: 10(5):5(5):0(5) mode:
bb
> fbdrv | Mode: 0x114 800x600@16, RGB: 11(5):5(6):0(5) mode:
bb
> fbdrv | Mode: 0x115 800x600@24, RGB: 16(8):8(8):0(8) mode:
bb
> fbdrv | Mode: 0x105 1024x768@8, RGB: 0(0):0(0):0(0) mode: bb > fbdrv | Mode: 0x116 1024x768@15, RGB: 10(5):5(5):0(5) mode:
bb
> fbdrv | Mode: 0x117 1024x768@16, RGB: 11(5):5(6):0(5) mode:
bb
> fbdrv | Mode: 0x118 1024x768@24, RGB: 16(8):8(8):0(8) mode:
bb
> fbdrv | Mode: 0x107 1280x1024@8, RGB: 0(0):0(0):0(0) mode: bb > fbdrv | Mode: 0x119 1280x1024@15, RGB: 10(5):5(5):0(5) mode:
bb
> fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode:
bb
> fbdrv | Choosen mode: > fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode:
bb
> fbdrv | To force a specific setting use a '-m <mode>' option. > fbdrv | L4Re[rm]: mapping for page fault failed with -34 @1a0000 > pc=1006452 > fbdrv | L4Re: unhandled exception: pc=0x1006452
This looks like io does not like to hand out the framebuffer memory. Any change when specifying, for example, -m 0x114 ? Does io say something noteworthy, possibly with some -v options supplied?
Adam
Adam adam@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
-- Matthias Lange, matthias.lange@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129. Geschäftsführer: Dr.-Ing. Michael Hohmuth
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
On Fri Jun 20, 2014 at 19:16:46 -0400, teclis High Elf wrote:
fbdrv | Mode: 0x118 1024x768@24, RGB: 16(8):8(8):0(8) mode: bb fbdrv | Mode: 0x107 1280x1024@8, RGB: 0(0):0(0):0(0) mode: bb fbdrv | Mode: 0x119 1280x1024@15, RGB: 10(5):5(5):0(5) mode: bb fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | Choosen mode: fbdrv | Mode: 0x11a 1280x1024@16, RGB: 11(5):5(6):0(5) mode: bb fbdrv | To force a specific setting use a '-m <mode>' option. fbdrv | x86emu_int10_set_vbemode, /home/jbutler/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/pkg/x86emu/lib/int10/int10.cc, 622 fbdrv | x86emu_int10_set_vbemode, /home/jbutler/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/pkg/x86emu/lib/int10/int10.cc, 624 fbdrv | x86emu_int10_set_vbemode, /home/jbutler/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/pkg/x86emu/lib/int10/int10.cc, 626 fbdrv | x86emu_int10_set_vbemode, /home/jbutler/fiasco-l4re-snapshot/l4re-snapshot-2014053111/src/l4/pkg/x86emu/lib/int10/int10.cc, 629 fbdrv | L4Re[rm]: mapping for page fault failed with -34 @1a0000 pc=1006452 fbdrv | L4Re: unhandled exception: pc=0x1006452
Could you tell me the Qemu version you're using? Further you could do a 'make exportpack' and provide me the files, esp. the fbdrv binary?
Adam
Hi L4 hackers,
and it built ok. Now when it runs fbdrv page faults. Has anyone seen
this before?
The same story: page fault https://pbs.twimg.com/media/DBPuT-sUMAAuhvU.png
I svn co all pkgs, and mkiso like this:
make grub2iso E=framebuffer-example-x86 MODULE_SEARCH_PATH=/home/zhaixiang/project/l4re/kernel/fiasco/build:/home/zhaixiang/project/l4re/l4/conf/examples:/home/zhaixiang/project/l4re/l4/pkg/io/io/config
then run by qemu:
make qemu E=framebuffer-example-x86 MODULE_SEARCH_PATH=/home/zhaixiang/project/l4re/kernel/fiasco/build:/home/zhaixiang/project/l4re/l4/conf/examples:/home/zhaixiang/project/l4re/l4/pkg/io/io/config
equals to:
qemu-system-x86_64 -kernel /home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/bootstrap -append "bootstrap -modaddr 0x01100000" -initrd "/home/zhaixiang/project/l4re/kernel/fiasco/build/fiasco -serial_esc,/home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/sigma0 ,/home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/moe rom/x86-fb.cfg,/home/zhaixiang/project/l4re/l4/conf/examples/x86-fb.cfg ,/home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/l4re ,/home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/ned ,/home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/io ,/home/zhaixiang/project/l4re/l4/pkg/io/io/config/x86-legacy.devs ,/home/zhaixiang/project/l4re/l4/conf/examples/x86-fb.io ,/home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/fb-drv ,/home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/mag ,/home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/ex_fb_spectrum_cc "
and I even changed x86-legacy.devs
Index: pkg/io/io/config/x86-legacy.devs =================================================================== --- pkg/io/io/config/x86-legacy.devs (revision 72) +++ pkg/io/io/config/x86-legacy.devs (working copy) @@ -23,7 +23,7 @@ Resource.iop2 = Res.io(0x3c0, 0x3df); -- EGA/VGA Resource.iop3 = Res.io(0x1ce, 0x1d0); -- Vbox Resource.iop4 = Res.io(0x402, 0x402); -- QEMU Debug Port - Resource.mmio = Res.mmio(0xa0000, 0xbffff); + Resource.mmio = Res.mmio(0xa0000, 0xbffff, 0xc000); end);
RTC = Hw.Device(function()
but it doesn't help, what did I miss? please give me some advice, thanks a lot!
On 01/06/17 17:35, Leslie Zhai wrote:
Hi L4 hackers,
and it built ok. Now when it runs fbdrv page faults. Has anyone seen
this before?
The same story: page fault https://pbs.twimg.com/media/DBPuT-sUMAAuhvU.png
This does not look like a page fault in fbdrv. If the system boots up correctly the boot sequence looks like follows:
MOE: virtual user address space [0-7fffffffffff] MOE: rom name space cap -> [C:103000] BOOTFS: [17d7000-17d76e8] [C:105000] x86-fb.cfg BOOTFS: [17d8000-19d0040] [C:107000] l4re BOOTFS: [19d1000-1dbd478] [C:109000] ned ... BOOTFS: [3e68000-40f5568] [C:115000] ex_fb_spectrum_cc MOE: cmdline: /home/.../build/tmp/l4re/bin/amd64_K8/l4f/moe rom/x86-fb.cfg MOE: Starting: rom/ned rom/x86-fb.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/x86-fb.cfg' IO | Io service
In your boot sequence the last line is the hello message from ned. So it looks like ned is dereferencing a null pointer (read access to 0 + 0x18 at instruction pointer 0x102d72a). Maybe you could use addr2line/objdump to figure out, what happens at address 0x102d72a in ned.
regards, Jean
Hi Jean,
Thanks for your reply! but I met the same story for L4Linux https://pbs.twimg.com/media/DBSQtoNUIAEE2HY.png
---> make grub2iso E=L4Linux-basic MODULE_SEARCH_PATH=/home/zhaixiang/project/l4re/kernel/fiasco/build:/home/zhaixiang/project/l4re/l4/conf/examples:/home/zhaixiang/project/l4linux/build:/home/zhaixiang/project/l4re make[1]: Entering directory '/home/zhaixiang/project/l4re/l4' Use of uninitialized value in string ne at /usr/lib64/perl5/vendor_perl/File/Spec/Unix.pm line 176. Use of uninitialized value in string ne at /usr/lib64/perl5/vendor_perl/File/Spec/Unix.pm line 176. Processing entry 'L4Linux-basic' Using the following files: /home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/l4re /home/zhaixiang/project/l4linux/build/vmlinuz /home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/moe /home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/sigma0 /home/zhaixiang/project/l4re/ramdisk-amd64.rd /home/zhaixiang/project/l4re/kernel/fiasco/build/fiasco /home/zhaixiang/project/l4re/l4/conf/examples/l4lx.cfg /home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/ned /home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/bootstrap xorriso 1.4.6 : RockRidge filesystem manipulator, libburnia project.
Drive current: -outdev 'stdio:/home/zhaixiang/project/l4re/l4/build/images/l4linux-basic.iso' Media current: stdio file, overwriteable Media status : is blank Media summary: 0 sessions, 0 data blocks, 0 data, 72.0g free Added to ISO image: directory '/'='/tmp/grub.vevqvj' xorriso : UPDATE : 320 files added in 1 seconds Added to ISO image: directory '/'='/tmp/cauUjpFlVZ' Added to ISO image: file '/l4re'='/home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/l4re' Added to ISO image: file '/vmlinuz'='/home/zhaixiang/project/l4linux/build/vmlinuz' Added to ISO image: file '/moe'='/home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/moe' Added to ISO image: file '/sigma0'='/home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/sigma0' Added to ISO image: file '/ramdisk-amd64.rd'='/home/zhaixiang/project/l4re/ramdisk-amd64.rd' Added to ISO image: file '/fiasco'='/home/zhaixiang/project/l4re/kernel/fiasco/build/fiasco' Added to ISO image: file '/l4lx.cfg'='/home/zhaixiang/project/l4re/l4/conf/examples/l4lx.cfg' Added to ISO image: file '/ned'='/home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/ned' Added to ISO image: file '/bootstrap'='/home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/bootstrap' xorriso : UPDATE : 332 files added in 1 seconds xorriso : NOTE : Copying to System Area: 512 bytes from file '/usr/lib/grub/i386-pc/boot_hybrid.img' xorriso : UPDATE : 40.97% done ISO image produced: 14360 sectors Written to medium : 14360 sectors at LBA 0 Writing to 'stdio:/home/zhaixiang/project/l4re/l4/build/images/l4linux-basic.iso' completed successfully.
---> make qemu E=L4Linux-basic MODULE_SEARCH_PATH=/home/zhaixiang/project/l4re/kernel/fiasco/build:/home/zhaixiang/project/l4re/l4/conf/examples:/home/zhaixiang/project/l4linux/build:/home/zhaixiang/project/l4re make[1]: Entering directory '/home/zhaixiang/project/l4re/l4' Use of uninitialized value in string ne at /usr/lib64/perl5/vendor_perl/File/Spec/Unix.pm line 176. Use of uninitialized value in string ne at /usr/lib64/perl5/vendor_perl/File/Spec/Unix.pm line 176. '/home/zhaixiang/project/l4linux/build/vmlinuz' is a zipped file, uncompressing to '/tmp/vmRbIvyLPB/vmlinuz' qemu-system-x86_64 -kernel /home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/bootstrap -append "bootstrap -modaddr 0x01100000" -initrd "/home/zhaixiang/project/l4re/kernel/fiasco/build/fiasco -serial_esc,/home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/sigma0 ,/home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/moe rom/l4lx.cfg,/home/zhaixiang/project/l4re/l4/conf/examples/l4lx.cfg ,/home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/l4re ,/home/zhaixiang/project/l4re/l4/build/bin/amd64_K8/l4f/ned ,/tmp/vmRbIvyLPB/vmlinuz ,/home/zhaixiang/project/l4re/ramdisk-amd64.rd " make[1]: Leaving directory '/home/zhaixiang/project/l4re/l4'
So it looks like ned is dereferencing a null pointer (read access to
0 + 0x18 at instruction pointer 0x102d72a).
I am using clang analyzer to Check NULL pointer dereference issue https://reviews.llvm.org/D31868 analyzer is not well managed, there might be false positive and negative, but I will implement more null pointer dereference checkers :)
Maybe you could use addr2line/objdump to figure out, what happens at address 0x102d72a in ned.
cd /home/zhaixiang/project/l4re/l4/build addr2line -p -e bin/amd64_K8/l4f/ned 0x102d72a
but there is no output easy to read for humans, I am not familiar with addr2line, please give me some advice, thanks a lot!
objdump -D bin/amd64_K8/l4f/ned > ned.S
... 27b9e: 00 00 add %al,(%rax) ... 102d72a: 66 0f 12 05 9e 7b 02 movlpd 0x27b9e(%rip),%xmm0 # 10552d0 <_ZL7HOOKKEY+0x 8> ...
is it enough to figure out what happened? if not, I will upload the disassemble to my Google drive.
l4-hackers@os.inf.tu-dresden.de
-
Adam Lackorzynski -
Jean Wolter -
Leslie Zhai -
Marcus Hähnel -
Matthias Lange -
teclis High Elf