Re: RTL 8139

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

On Apr 25, 10:27 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:
So, you're NOTusingthe RTL adapter as an ordinary Ethernet adapter, but as
a KITL-over-Ethernet connection to your Platform Builder machine? It
appears that this is the case. If so, you *CAN'T* also use the adapter
driver; that won't work because you'll have both the kernel and the driver
trying to talk to the hardware. You can a) use VMini and leave the KITL
stuff or, b) change the BSP so that it's notusingKITL-over-Ethernet and
use the real RTL driver. How, exactly, you do b), is BSP-specific, so I'll
have to leave that to you. If you want to do a), remove the RTL driver from
the OS and make sure that you've followed the instructions in Ethernet
Debugging Services in the help to turn on VMini.

PaulT.

<ashsa...@xxxxxxxxx> wrote in message

news:13059dc4-9fbc-49a0-ad08-175d74447de9@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Pls check following debug message pls give me the solution
SysInit: GDTBase=8118d0e8 IDTBase=811deec0
KData=811fd800
WindowsCEKernel for i486 Built on Jun 24 2004 at
18:23:42
g_pPageDir = 81200000
InitKitlNIC: Searching for PCI Ethernet NIC
(dwIrq = 0,
dwI
oBase = 0, dwDfltType = 0) ...
InitKitlNIC: Found PCI Ethernet NIC (type = 4, IRQ=11,
IOBase=0x1000).
RTL8139InitDMABuffer():: Start[0x811E2B40]-[0x811E2B40] -
Size[0x10000]
[0x0]
Tx[0x811E2B40] - Rx[0x811E4340] - RxLength[0x8000] -
RxLengthBit[0x1000]tRx[0x2117FF] [0x77400700] RCR
[0x181A] TCTR [0xA99ED
RTL8139:: built on [Apr 25 2008]
[14:47:12]
RTL8139Init():: BaseIO[0x1000] : MemOffset[0x1000]
RTL8139Init:: MAC = 00-08-A1-45-A6-77
RTL8139Init():: TxBuff[0x811E2B40] - RxBuff[0x811E4340] -
LastRx[0x811EC33F][0x10] CONFIG1
[0x8D]
RTL8139Init:: MAC = 00-18-4D-6F-24-3FTL8139HWSetMCRegs():: Set all to
0x00
RTL8139ethdbg library: perform auto negotiate.
M
+RTL8139EnableInts().. [0xE5] MULI
RTL8139:: RTL8139HWSetMCRegs():: Set all to
0x00L8139EnableInts()..D [0x10]
VBridge:: built on [Apr 25 2008] time [14:47:14]
VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
Tx buffer [0xA11F2CE0] to [0xA11F6CE0].
Rx buffer [0xA11F6D00] to [0xA11FAD00].
VBridge:: NK add MAC: [0-18-4D-6F-24-3F]
ERROR: OALKitlInit: KitlInit failed
RTC - Status Reg B - 0x02
X86Init done, OEMAddressTable = 80229378.
OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
VBridge:: VB_INITIALIZED returns [1]
VBridge:: RESET_BUFFER received.
DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
at (Driver
s\BuiltIn\AFD). Driver cannot be unloaded.
DeviceFolder::LoadDevice!
Enumerate Fou
nd deprecated load instructions at (Drivers\BuiltIn\PPP). Driver
cannot be unloa
ded.
PCIbus!PCIEnum: WARNING: Resource request for device 0:0:0 failed
Lyg.p: Layout Manager successfully initialized to 1
Explorer(V2.0) taskbar thread started.
NDISPWR:: Found adapter [VMINI1]
NDISPWR:: Found adapter [PCI\RTL81391]

Hello sir,

Error : RealTek Driver (rtl8139) is not acting as a simple adapter for
my wince Image

My Hardware : NETGEAR rtl8139D

My Tool : Platform Builder winCE5.0

Below is my target PC platform configuration for RealTek
Added to the platform

1. CEPC:X86 = Device Drivers - Networking-Local Area Networking (LAN)
devices - RealTekRTL8139

2.Custom Device[Display based devices] -Communication Services and
Networking - Local Area Network (LAN) -
Wired Local Area Network(802.3,802.5)

3. Custom Device[Display based devices]-Communication Services and
Networking - Networking features - NDIS &Networking
utilities(ipconfig,pimg,route)

RTL 8139 was detected in the image and i configured it to
static ip address 192.168.10.199

but when i tried to ping other device on the network
it gave me the following error:

Transmit error :11010


Following were the debug messages seen on Hyperterminal on COM port

SysInit: GDTBase=8165d0e8 IDTBase=816aeec0 KData=816cd800
Windows CE Kernel for i486 Built on Jun 24 2004 at 18:23:42
g_pPageDir = 816d0000
InitKitlNIC: Searching for PCI Ethernet NIC
(dwIrq = 0, dwI
oBase = 0, dwDfltType = 0) ...
InitKitlNIC: Found PCI Ethernet NIC (type = 4, IRQ=11, IOBase=0x1000).
RTL8139InitDMABuffer():: Start[0x816B2B40]-[0x816B2B40] -
Size[0x10000]
Tx[0x816B2B40] - Rx[0x816B4340] - RxLength[0x8000] -
RxLengthBit[0x1000]
RTL8139:: built on [Apr 24 2008] [15:42:24]
RTL8139Init():: BaseIO[0x1000] : MemOffset[0x1000]
RTL8139Init():: TxBuff[0x816B2B40] - RxBuff[0x816B4340] -
LastRx[0x816BC33F]
RTL8139Init:: MAC = 00-18-4D-6F-24-3F
RTL8139 ethdbg library: perform auto negotiate.
RTL8139:: RTL8139HWSetMCRegs():: Set all to 0x00
x86KitlCreateName: Using Device Name 'CEPC9279'
OALKitlCreateName: Using Device Name 'CEPC9279'
KITL: *** Device Name CEPC9279 ***

VBridge:: built on [Apr 24 2008] time [15:42:27]
VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
Tx buffer [0xA16C2CE0] to [0xA16C6CE0].
Rx buffer [0xA16C6D00] to [0xA16CAD00].
VBridge:: NK add MAC: [0-18-4D-6F-24-3F]
ERROR: OALKitlInit: KitlInit failed
RTC - Status Reg B - 0x02
X86Init done, OEMAddressTable = 80229368.
OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
at (Driver
s\BuiltIn\AFD). Driver cannot be unloaded.
DeviceFolder::LoadDevice!
Enumerate Fou
nd deprecated load instructions at (Drivers\BuiltIn\PPP). Driver
cannot be unloa
ded.
PCIbus!PCIEnum: WARNING: Resource request for device 0:0:0 failed
Lyg.p: Layout Manager successfully initialized to 1
Explorer(V2.0) taskbar thread started.
NDISPWR:: Found adapter [PCI\RTL81391]
NDISPWR:: BIND notification for adapter [PCI\RTL81391]
.

Relevant Pages

  • Re: RTL 8139
    ... a KITL-over-Ethernet connection to your Platform Builder machine? ... driver; that won't work because you'll have both the kernel and the ... DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions ... Networking - Networking features - NDIS &Networking ...
    (microsoft.public.windowsce.platbuilder)
  • Re: RTL 8139
    ... no instrument no spam DOT com> wrote: ... driver; that won't work because you'll have both the kernel and the ... DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions ... Networking - Networking features - NDIS &Networking ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Epia Mini-ITX ce installation
    ... Install Platform Builder on you development PC. ... Epia BSP to the catalog. ... Goto "New Platform Wizard" and create new workspace based ... the audio driver to work with you current image (if you have the ...
    (microsoft.public.windowsce.embedded)
  • Re: AFD inability to load
    ... What I have under communication services and networking are: ... Dial up Networking, Telephony API, NDIS User-mode I/O Driver, ... 0x83fc98c8: FS: Creating signal event SYSTEM/DevMgrApiSetReady ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Linux Distribution that Works out of the box on Virtual PC 2007??
    ... Many emulated interfaces may need their own driver which should come with the emulation program. ... Two major problems I find are networking, especially wireless networking, and soundcard support including mp3 codecs. ... As it seems to have issues (may be deliberately included by microsoft), you should try another, so go with Mr Styvels suggestion. ...
    (alt.os.linux)