l4linux-2.6.22 starting

Adam Lackorzynski adam at os.inf.tu-dresden.de
Sun Oct 7 15:16:34 CEST 2007


On Fri Oct 05, 2007 at 21:02:40 +0800, ¶¡Ó¨ wrote:
> Hi,everyone:
>               Is there anybody have started the latest l4linux-2.6.22 on
> slackware 12.0? I do the job these days,but I couldn't start it,and the
> problem is strange.When I start the l4linux ,the dope is OK and the l4linux
> has started ,but finally the l4linux will stop with following  error
> message:
> 
> l4dope  | SharedMem(get_adr): address = 0x21000
> l4dope  | dope: paddr=88000000 size=8000KiB
> l4dope  | Mapped video memory at 88000000 to 00800000+000000 [8000kB] via
> L4IO
> l4dope  | mapping: vaddr=0x800000 size=8192000(0x7d0000) offset=0(0x0)
> l4dope  | Frame buffer base:  0x800000
> l4dope  | Resolution:         1024x768x16
> l4dope  | Bytes per scanline: 2048
> l4dope  | Current video mode is 1024x768 red=11:5 green=5:6 blue=0:5 res=0:0
> l4dope  | SharedMem(alloc): hl.raw=100000, id=82, size=96000
> l4dope  | SharedMem(get_adr): address = 0x400000
> l4lx    | l4lx_thread_create: Created thread 0f.08 (DOpE refresher)
> l4lx    | l4lx_thread_create: Created thread 0f.09 (L4DOpEinput)
> l4lx    | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 14.
> l4lx    | l4lx_thread_create: Created thread 0f.0a (IRQ14)
> l4lx    | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 15.
> l4lx    | l4lx_thread_create: Created thread 0f.0b (IRQ15)
> l4lx    | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 12.
> l4lx    | acquire_irq: Error attaching to IRQ 12
> l4lx    | l4lx_thread_create: Created thread 0f.0c (IRQ12)
> l4lx    | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1.
> l4lx    | acquire_irq: Error attaching to IRQ 1
> l4lx    | l4lx_thread_create: Created thread 0f.0d (IRQ1)
> l4dope  | atkbd.c: Spurious ACK on isa0060/serio0. Some program, like
> XFree86,
> l4dope  : might be trying access hardware directly.
> l4dope  | atkbd.c: Spurious ACK on isa0060/serio0. Some program, like
> XFree86,
> l4dope  : might be trying access hardware directly.
> l4dope  | atkbd.c: Spurious ACK on isa0060/serio0. Some program, like
> XFree86,
> l4dope  : might be trying access hardware directly.
> l4dope  | atkbd.c: Spurious ACK on isa0060/serio0. Some program, like
> XFree86,
> l4dope  : might be trying access hardware directly.
> 
> And I have disable the keyboard and mouse when compiling the
> l4linux.

Seems not so as the warnings are still being printed. Check
if CONFIG_SERIO_I8042 and/or CONFIG_SERIO_LIBPS2 is enabled.

> Butwhen I put this binary which compilered on slackware
> 12.0 to ubuntu 6.06,the l4linux-2.6.22 started ,and some other people have
> tested it on Qmenu,its also started ,my binary have put to the
> ftp://mirror.lzu.edu.cn/temp.Everyone who intresting in it could test it.
> So may be it is the problem with slackware 12.0 inittab? But I can't fix
> it,i am just a new both in l4linux and linux.The slackware 12.0 inittab is
> as follow:

You can do the following to worker fruther on this. Disable X in your
Slackware by disabling the X init-script (/etc/init.d/xdm or whatever
it's called in Slackware, add an exit 0 or similar at the beginning) and
then boot normal Linux and see what happens. Does the login-prompt
appear?



Adam
-- 
Adam                 adam at os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/




More information about the l4-hackers mailing list