Graphical desktop, l4con, mag

Matthias Lange matthias.lange at kernkonzept.com
Fri Jun 20 20:39:32 CEST 2014


> On 20 Jun 2014, at 20:06, teclis High Elf <teclis.high.elf at 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 at 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 at 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 at 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 at 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 at 8, RGB: 0(0):0(0):0(0) mode: bb
>>>> > > > fbdrv   | Mode: 0x110    640x480 at 15, RGB: 10(5):5(5):0(5) mode: bb
>>>> > > > fbdrv   | Mode: 0x111    640x480 at 16, RGB: 11(5):5(6):0(5) mode: bb
>>>> > > > fbdrv   | Mode: 0x112    640x480 at 24, RGB: 16(8):8(8):0(8) mode: bb
>>>> > > > fbdrv   | Mode: 0x103     800x600 at 8, RGB: 0(0):0(0):0(0) mode: bb
>>>> > > > fbdrv   | Mode: 0x113    800x600 at 15, RGB: 10(5):5(5):0(5) mode: bb
>>>> > > > fbdrv   | Mode: 0x114    800x600 at 16, RGB: 11(5):5(6):0(5) mode: bb
>>>> > > > fbdrv   | Mode: 0x115    800x600 at 24, RGB: 16(8):8(8):0(8) mode: bb
>>>> > > > fbdrv   | Mode: 0x105    1024x768 at 8, RGB: 0(0):0(0):0(0) mode: bb
>>>> > > > fbdrv   | Mode: 0x116   1024x768 at 15, RGB: 10(5):5(5):0(5) mode: bb
>>>> > > > fbdrv   | Mode: 0x117   1024x768 at 16, RGB: 11(5):5(6):0(5) mode: bb
>>>> > > > fbdrv   | Mode: 0x118   1024x768 at 24, RGB: 16(8):8(8):0(8) mode: bb
>>>> > > > fbdrv   | Mode: 0x107   1280x1024 at 8, RGB: 0(0):0(0):0(0) mode: bb
>>>> > > > fbdrv   | Mode: 0x119  1280x1024 at 15, RGB: 10(5):5(5):0(5) mode: bb
>>>> > > > fbdrv   | Mode: 0x11a  1280x1024 at 16, RGB: 11(5):5(6):0(5) mode: bb
>>>> > > > fbdrv   | Choosen mode:
>>>> > > > fbdrv   | Mode: 0x11a  1280x1024 at 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 at os.inf.tu-dresden.de
>>>> > >   Lackorzynski         http://os.inf.tu-dresden.de/~adam/
>>>> > >
>>>> > > _______________________________________________
>>>> > > l4-hackers mailing list
>>>> > > l4-hackers at os.inf.tu-dresden.de
>>>> > > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
>>>> > >
>>>> 
>>>> > _______________________________________________
>>>> > l4-hackers mailing list
>>>> > l4-hackers at os.inf.tu-dresden.de
>>>> > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
>>>> 
>>>> 
>>>> --
>>>> Matthias Lange, matthias.lange at 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 at os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://os.inf.tu-dresden.de/pipermail/l4-hackers/attachments/20140620/cd9a00ff/attachment-0001.html>


More information about the l4-hackers mailing list