ore problems

Bjoern Doebel doebel at tudos.org
Tue Jun 17 10:48:48 CEST 2008


Hi Li,

Please consider using the l4-hackers mailing list for such questions,
because you might get faster answers there.


> I install ore in my machine and start it in qemu, but I get 
> these informations, what's the problem, thanks.
>
> First I'll show you my menu.lst 
>
> title ORe
> kernel /bootstrap -serial -modaddr 0x2000000
> module /fiasco -serial_esc -comport 1   
> module /sigma0
> module /roottask task modname "bmodfs" attached 1 modules
> module /names
> module /log
> module /l4io
> module /events
> module /dm_phys
> module /simple_ts
> module /bmodfs
> module /ore
> module /loader -fprov=BMODFS ore  

The menu.lst looks fine so far.

> The output in qemu is 
>
> io      | Using platform configuration 'x86'
> io      | PCI: Using configuration type 1
> io      | PCI: Probing PCI hardware
> io      | PCI: Probing PCI hardware (bus 00)
> io      | PCI: PIIX3: Enabling Passive Release on 00:01.0
> io      | Limiting direct PCI/PCI transfers.
> io      | Activating ISA DMA hang workarounds.
> io      | 00000000-ffffffff : PCI mem
> io      |   e0000000-e1ffffff : Cirrus Logic GD 5446
> io      |   e2000000-e2000fff : Cirrus Logic GD 5446
> io      |   e3000000-e30000ff : Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/
> io      : 8139C+

Ok. So you configure Qemu to emulate an RTL8139 network interface.

> io      | 0000-ffff : PCI IO
> io      |   0cf8-0cff : PCI conf1
> io      |   1000-100f : Intel Corporation 82371SB PIIX3 IDE
[Natoma/Triton II]
> io      |   1400-14ff : Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+
> io      |   b100-b11f : Intel Corporation 82371AB/EB/MB PIIX4 ACPI
> bmodfs  | Passed the following modules:
> bmodfs  |   module "/ore" (2176kB)
> loader  | "ore" is a valid binary image
> loader  | ore: Starting sigma0-style application
> loader  | ore: Loading binary
> loader  | ore,#d: Entry at 00009f8c => 01800000
> loader  | ore,#d: Started
> io      | Available IRQs=[ <!0> 1 <!2> 3 <!4> 5 6 7 8 9 a b c d e f
10 11 ]
> ore     | Softirq daemon starting
> ore     | Initializing DDE page cache
> ore     | unimplemented: pci_fixup_device
> ore     | unimplemented: pci_fixup_device
> ore     | _add_ddekit_device: Detected device: 8086:7000
> ore     | unimplemented: pci_fixup_device
> ore     | unimplemented: pci_fixup_device
> ore     | _add_ddekit_device: Detected device: 8086:7010
> ore     | unimplemented: pci_fixup_device
> ore     | unimplemented: pci_fixup_device
> ore     | _add_ddekit_device: Detected device: 8086:7113
> ore     | unimplemented: pci_fixup_device
> ore     | unimplemented: pci_fixup_device
> ore     | _add_ddekit_device: Detected device: 1013:b8
> ore     | unimplemented: pci_fixup_device
> ore     | unimplemented: pci_fixup_device
> ore     | _add_ddekit_device: Detected device: 10ec:8139
> ore     | <6>e100: Intel(R) PRO/100 Network Driver, 3.5.17-k2-NAPI
> ore     | <6>e100: Copyright(c) 1999-2006 Intel Corporation

Here we see, that the e100 NIC driver is trying to initialize.
However, there is no such NIC in your setup and therefore there is no
eth0 available.

Go to l4/pkg/ore/server and run "make config" and configure ORe to use
the RTL8139 network driver.

> ore     | unimplemented: pci_fixup_device
> ore     | unimplemented: pci_fixup_device
> ore     | unimplemented: pci_fixup_device
> ore     | unimplemented: pci_fixup_device
> ore     | unimplemented: pci_fixup_device
> ore     | l4dde26_register_rx_callback: New rx callback @
0x018012f0.
> ore     | main(): initialized DDELinux2.6
> ore     | main(): loopback: 0
> ore     | <6>device lo entered promiscuous mode
> ore     | main(): Initialized 1 network devices.
> ore     | Device =   lo, IRQ =  0, MAC = 00:00:00:00:00:00
> ore     | main(): Registering 'ORe' at names...
> ore     | main(): Ready for service.

Kind regards,
Bjoern





More information about the l4-hackers mailing list