Am Dienstag 07 Februar 2006 16:42 schrieb Bjoern Doebel:
Hello,
We did not manage to arping ore_test_arping this time, but complete logs are attached.
humm, ... please update your version of ORe from our public CVS and try to run some minimal setup with only the arping client and w/o L4Linux. See my example below and report us your experiences.
Thank you! Arping now works again, but configuring eth0 in L4Linux fails with
ore | [B.2] thread/lib/src/exit.c:273:l4thread_shutdown(): ore | Error: thread 0 not active ore | [B.2] thread/lib/src/exit.c:273:l4thread_shutdown(): ore | Error: thread 0 not active ore | [B.2] thread/lib/src/exit.c:273:l4thread_shutdown(): ore | Error: thread 0 not active
Additionally dmesg says:
eth0: Overwriting IRQ type for IRQ 0 with l4ore type! eth0: request_irq(0, ...) failed. eth0: Overwriting IRQ type for IRQ 0 with l4ore type! eth0: request_irq(0, ...) failed. eth0: Overwriting IRQ type for IRQ 0 with l4ore type! eth0: request_irq(0, ...) failed.
My menu.lst:
title = ORe Gentoo kernel (hd0,3)/boot/tcb/svpn/bootstrap -sigma0 -roottask -serial -comport=1 modaddr 0x02000000 module (hd0,3)/boot/tcb/svpn/fiasco -nokdb -comport 1 -serial -nowait module (hd0,3)/boot/tcb/svpn/sigma0 module (hd0,3)/boot/tcb/svpn/roottask -sigma0 task modname "bmodfs" module module module module module (hd0,3)/boot/tcb/svpn/names module (hd0,3)/boot/tcb/svpn/dmon module (hd0,3)/boot/tcb/svpn/dm_phys module (hd0,3)/boot/tcb/svpn/simple_ts -t 380 module (hd0,3)/boot/tcb/svpn/rtc module (hd0,3)/boot/tcb/svpn/l4io module (hd0,3)/boot/tcb/bench/ore "--debug" module (hd0,3)/boot/tcb/bench/ore_test_arping
module (hd0,3)/boot/tcb/svpn/bmodfs module (hd0,3)/boot/tcb/svpn/run module (hd0,3)/boot/tcb/svpn/libloader.s.so module (hd0,3)/boot/tcb/bench/vmlinuz26-ore module (hd0,3)/boot/tcb/bench/l4linux26ramdisk-ore.cfg
module (hd0,3)/boot/tcb/svpn/l4exec module (hd0,3)/boot/tcb/svpn/l4dope --l4io module (hd0,3)/boot/tcb/svpn/loader --fprov=BMODFS l4linux26ramdisk-ore.cfg vbeset 0x117
Regards, Michael