Re: DUAL Lan Adapter:No Network Connection
From: Seung Yi (seungyi_at_codetelligence_NOSPAMMERS_.com)
Date: 03/19/04
- Next message: Geoff Smith: "Re: DRIVERS- XXX_IOCONTROL- DeviceIoControl and so on."
- Previous message: jm: "Re: EXDI related PB crash"
- In reply to: Erwin: "DUAL Lan Adapter:No Network Connection"
- Next in thread: Erwin: "Re: DUAL Lan Adapter:No Network Connection"
- Reply: Erwin: "Re: DUAL Lan Adapter:No Network Connection"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 19 Mar 2004 14:13:26 -0800
You may want to check the interrupt line, if the DLL is loaded and the
NDIS is trying to bind the adapter with an IP address, the driver has
gotten pretty far. I would suggest turning on as many zones in the
RTL81391 driver. This could be a PCI interrupt routing problem on the
hardware board. Since its PC104+, there should be a rotary dial or switch
block allowing you to select which IDSEL, INT A,B,C or D pins to connect
to. Even though PCI interrupts are technically shareable, your
motherboard may not have routed INT B,C or D or .... the chipset has not
been initialized far enough to route the INTx pins from the PCI bus to the
interrupt controller (8259) and assigned IRQ numbers.
On Thu, 18 Mar 2004 16:45:06 +0100, Erwin <sperwin@NO-SPAMquicknet.nl>
wrote:
> Hi,
>
> We Have:
> -Inside PC104 GX1LCD Inside board
> -Image created with Platform builder 4.1
> -External PC104+ ethernet module with RTL8139C network controller
>
> Basicly the problem is that I don't have a network connection with the
> external network card.
> So no IP recieved via DHCP or no lan connection configured with a static
> IP.
>
> I can see the two adapters in the bottom right of my display.
> The external card is 'detected' by the PCI scan and i can see the info in
> the [HKLM\Comm\PCI\RTL81391 registry key, so that means it is recognized
> by
> the RTL8139 template?
>
> What registry settings (or other confiurations) are needed to configure
> this?
>
> some log from Platform builder:
> 4294891063 PID:837cb712 TID:837d6c62 0x837cb000:
> IPNotifyClientsIPEvent: PendingIPGetIPEventRequest 5a0a0
>
> 4294891064 PID:837cb712 TID:837d6c62 0x837cb000:
> IPNotifyClientsIPEvent: PendingIrp 5a0a0
>
> 4294891065 PID:837cb712 TID:837d6c62 0x837cb000:
> IPNotifyClientsIPEvent: SetEvent
>
> 4294891066 PID:837cb712 TID:837d6c62 0x837cb000:
> IPNotifyClientsIPEvent: remove old
>
> 4294891067 PID:837cb712 TID:837d6c62 0x837cb000: -IPAddInterface
> [SUCCESS]
>
> 4294891070 PID:837cb712 TID:837d6c62 0x837cb000:
> PPP: -AddAdapter:NdisOpenAdapter(PCI\RTL81391) failed with 0xC0010019
>
> 4294891075 PID:837cb712 TID:837d6c62 0x837cb000:
> DEVICE!ActivateDeviceEx(Drivers\BuiltIn\PCI\Instance\KITL) entered
>
> 4294891080 PID:837cb712 TID:837367b2 0x83791800: ************DHCP MEDIA
> STATUS************
>
> 4294891081 PID:837cb712 TID:837367b2 0x83791800: SeqNo: 2
>
> 4294891081 PID:837cb712 TID:837367b2 0x83791800: MediaStatus:
> 11026
>
> Unloaded symbols for 'C:\WINCE410\PUBLIC\TEST\RELDIR\GX1DEBUG\PCIBUS.DLL'
>
> 4294891082 PID:837cb712 TID:837367b2 0x83791800: Context: 3 - 3
>
> 4294891082 PID:837cb712 TID:837367b2 0x83791800: AdapterName:
> PCI\RTL81391
>
> 4294891083 PID:837cb712 TID:837367b2 0x83791800: Media Status is:
> IP_BIND_ADAPTER
>
> 4294891083 PID:837cb712 TID:837367b2 0x83791800: IPDispatchDeviceControl
> returned Status 103
>
>
>
> hope somebody can help...
> many thanks in advance
>
> Erwin
>
>
-- Seung Yi Chief Technologist Codetelligence, Inc. Web : www.codetelligence.com
- Next message: Geoff Smith: "Re: DRIVERS- XXX_IOCONTROL- DeviceIoControl and so on."
- Previous message: jm: "Re: EXDI related PB crash"
- In reply to: Erwin: "DUAL Lan Adapter:No Network Connection"
- Next in thread: Erwin: "Re: DUAL Lan Adapter:No Network Connection"
- Reply: Erwin: "Re: DUAL Lan Adapter:No Network Connection"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
