Re: rtl8139 problem

From: kamaal (kamaalwince_at_rediffmail.com)
Date: 08/13/04


Date: 13 Aug 2004 06:43:35 -0700

Hi,
I tried as u said :[HKEY_LOCAL_MACHINE\Comm\PCI\RTL81391\Parms\TcpIp]

But the system would hang by doing so.

Also ipconfig shows Physical address as:ff ff ff ff ff ff ,and not the
MAC address of RTL8139 card.
Is there anything wrong with the interrupt? Do I need to assign IRQ or
SysIntr value?The IRQ I'm using is 0x10(IRQ=dword:10).
Also,where can I find the error code discription?
Sometimes ping gives-"transmit failed:error code 87" and sometimes
error code 11010.

Kamaal

"K. S. Huang" <ks_huang@alphanetworks.com.remove.this> wrote in message news:<ela6tsHgEHA.2468@TK2MSFTNGP12.phx.gbl>...
> if you want to set the default IP address of a PCI NIC,
> you sould set valuse under [HKEY_LOCAL_MACHINE\Comm\PCI\XXX\Parms\TcpIp]
>
> for example
> [HKEY_LOCAL_MACHINE\Comm\PCI\RTL81391\Parms\TcpIp]
>
> you could also try to ping from other PC to your device,
> and try to use arp -a to see if the IP->MAC is got properly!
>
> "kamaal" <kamaalwince@rediffmail.com>
> ???????:dd2f4359.0408120407.e007e6e@posting.google.com...
> > Hi all,
> > I'm getting my RTL8139 driver loaded at last!!.
> > I put the following in my registry settings and it got loaded.
> >
> > In project.reg:
> >
> > [HKEY_LOCAL_MACHINE\Comm\RTL81391]
> > "DisplayName"="RTL8139"
> > "Order"=dword:10
> > "Group"="NDIS"
> > "ImagePath"="RTL8139.dll"
> >
> > [HKEY_LOCAL_MACHINE\Comm\RTL8139\Linkage]
> > "Route"=multi_sz:"RTL8139"
> >
> > [HKEY_LOCAL_MACHINE\Comm\Tcpip\Linkage]
> > "Bind"="RTL81391"
> >
> > [HKEY_LOCAL_MACHINE\Comm\RTL8139\Parms]
> > "FriendlyName"="RTL8139"
> > "BusNumber"=dword:0
> > "BusType"=dword:5
> > "IoBase"=dword:xxxxxxxx
> > "IRQ"=dword:yy
> > "MediaType"=dword:1
> > "AdapterType"=dword:0
> >
> > [HKEY_LOCAL_MACHINE\Comm\RTL8139\Parms\TcpIp]
> > "EnableDHCP"=dword:0
> > "DefaultGateway"=multi_sz:"xxx.xxx.x.1"
> > "IpAddress"=multi_sz:"xxx.xxx.x.xxx"
> > "Subnetmask"=multi_sz:"255.255.255.0"
> > "UseZeroBroadcast"=dword:0
> >
> >
> > Now, I run ipconfig and it shows the ip configuration.
> >
> > If I try to ping to any other port in the network,the ping fails
> > giving the error as: transmit failed:error code 11010
> >
> > Now what can I do?I am almost nearing the solution.But I'm stuck at
> > some point.How can I successfully ping?Do I need to put some other
> > registry settings?
> >
> > -Kamaal
> >
> >
> >
> >
> > "K. S. Huang" <ks_huang@AlphaNetworks.com_remove.this> wrote in message
> news:<OaLHc0BgEHA.3024@TK2MSFTNGP10.phx.gbl>...
> > > do you check out the registr under [HKLM\BuiltIn\PCI\Instance]??
> > > the keys under Instance will be created by PCIBUS.DLL, you don't need to
> set
> > > any default value for it.
> > >
> > >
> > >
> > > "kamaal" <kamaalwince@rediffmail.com>
> > > ???????:dd2f4359.0408110255.4f0f3ac5@posting.google.com...
> > > > Hi,
> > > > I'm using a on-board ethernet port to download image/KITL.This is not
> > > > the RTL8139 port.
> > > >
> > > > I want to use a seperate RTL8139 NIC mounted on PCI back plane as
> > > > product ethernet.I want to use it to establish connection with host
> > > > for CETK.
> > > > This is a headless platform without display.
> > > > If I disable KITL, how can I run clientside.exe?Does RTL8139 driver
> > > > really conflict with KITL?
> > > >
> > > > Thanks and Regards,
> > > > Kamaal
> > > >
> > > >
> > > >
> > > > "K. S. Huang" <ks_huang@AlphaNetworks.com_remove.this> wrote in
> message
> news:<eoaE241fEHA.2984@tk2msftngp13.phx.gbl>...
> > > > > Is there only one 8139 on your device??
> > > > > If so, please diable the KITL.
> > > > > Even you diable the VMini, the KITL is still using your 8139 as its
> EthDBG
> > > > > port.
> > > > >
> > > > > "kamaal" <kamaalwince@rediffmail.com>
> > > > > ???????:dd2f4359.0408101958.70558239@posting.google.com...
> > > > > > Hi folks,
> > > > > >
> > > > > > Thanks for all ur suggestions.
> > > > > > I have taken care that IMGNOSHAREETH=1 and BSP_NOSHAREETH=1 so as
> to
> > > > > > disable VMINI.
> > > > > > I have also made sure that BSP_NIC_RTL8139=1.
> > > > > >
> > > > > > The driver is also included in OS image(\windows directory).
> > > > > >
> > > > > > But what could be the problem that it is getting stuck at
> > > > > > NdisMAllocateSharedMemory()?
> > > > > > It's really frustrating.
> > > > > > Do I need to write registry entries under PCI\Instance key
> also?(like
> > > > > > subvendorid,subsystemid etc).
> > > > > >
> > > > > > I'd be very greatful to u all if I can come out of this jungle.
> > > > > >
> > > > > > Kamaal
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > kamaalwince@rediffmail.com (kamaal) wrote in message
> news:<dd2f4359.0408100624.54cafc48@posting.google.com>...
> > > > > > > Hi folks,
> > > > > > >
> > > > > > > I'm getting a peculiar problem in using rtl8139D network
> card(PCI
> > > > > > > based).
> > > > > > >
> > > > > > > 1.Does the driver for rtl8139 support RTL8139D chipset?
> > > > > > > 2.I'm unable to load the driver successfully and use it as a
> product
> > > > > > > ethernet.
> > > > > > > When I build image in debug mode I get the following messages:
> > > > > > >
> > > > > > >
> > > > > > > Welcome to the Windows CE Shell. Type ? for help.
> > > > > > >
> > > > > > > 4294768140 PID:27fa92ba TID:27f764a2 0x87fac670: Shell: No
> extension
> > > > > > > DLLs found
> > > > > > > 4294768160 PID:e7f768ca TID:e7f7647a 0x87f76660: >>> Loading
> module
> > > > > > > ceddk.dll at address 0x03EF0000-0x03EF7000 (RW data at
> > > > > > > 0x01FF5000-0x01FF5068)
> > > > > > > Loaded symbols for
> 'E:\WINCE420\PUBLIC\MORNING_21\RELDIR\XYZDEBUG\CEDDK.DLL'
> > > > > > > 4294768161 PID:e7f768ca TID:e7f7647a 0x87f76660:
> > > > > > > Ceddk!CalibrateStallCounter: Enter
> > > > > > > 4294768162 PID:e7f768ca TID:e7f7647a 0x87f76660:
> > > > > > > Ceddk!CalibrateStallCounter: Could not find stall counter
> > > > > > > 4294768162 PID:e7f768ca TID:e7f7647a 0x87f76660:
> > > > > > > Ceddk!BeginCalibration: min(0) max(0)
> > > > > > > 4294768163 PID:e7f768ca TID:e7f7647a 0x87f76660:
> > > > > > > Ceddk!BeginCalibration: elapsed is 0
> > > > > > > 4294768164 PID:e7f768ca TID:e7f7647a 0x87f76660:
> > > > > > > Ceddk!BeginCalibration: delay is 10
> > > > > > > 4294768164 PID:e7f768ca TID:e7f7647a 0x87f76660:
> DEVICE!DevloadInit
> > > > > > > 4294768165 PID:e7f768ca TID:e7f7647a 0x87f76660:
> DEVICE!InitDevices:
> > > > > > > Root Key is Drivers\BuiltIn.
> > > > > > > 4294768166 PID:e7f768ca TID:e7f7647a 0x87f76660:
> > > > > > > DEVICE!ActivateDeviceEx(Drivers\BuiltIn) entered
> > > > > > > 4294768171 PID:e7f768ca TID:e7f7647a 0x87f76660: >>> Loading
> module
> > > > > > > regenum.dll at address 0x03F50000-0x03F57000 (RW data at
> > > > > > > 0x01FFD000-0x01FFD49C)
> > > > > > > Loaded symbols for
> 'E:\WINCE420\PUBLIC\MORNING_21\RELDIR\XYZDEBUG\REGENUM.DLL'
> > > > > > > 4294768202 PID:e7f768ca TID:e7f7647a 0x87f76660:
> > > > > > > DEVICE!ActivateDeviceEx(Drivers\BuiltIn\PCI) entered
> > > > > > > 4294768212 PID:e7f768ca TID:e7f7647a 0x87f76660: >>> Loading
> module
> > > > > > > XYZpcibus.dll at address 0x03C20000-0x03C39000 (RW data at
> > > > > > > 0x01FCE000-0x01FCE71C)
> > > > > > > Loaded symbols for
> 'E:\WINCE420\PUBLIC\MORNING_21\RELDIR\XYZDEBUG\XYZPCIBUS.DLL'
> > > > > > > 4294768257 PID:e7f768ca TID:e7f7647a 0x87f76660: device ID 8139
> vendor
> > > > > > > ID 10ec
> > > > > > > 4294768418 PID:e7f768ca TID:e7f7647a 0x87f76660:
> > > > > > > DEVICE!ActivateDeviceEx(Drivers\BuiltIn\PCI\Instance) entered
> > > > > > > 4294768421 PID:e7f768ca TID:e7f7647a 0x87f76660:
> > > > > > > DEVICE!ActivateDeviceEx(Drivers\BuiltIn\PCI\Instance\RTL81391)
> entered
> > > > > > > 4294768440 PID:e7f768ca TID:e7f7647a 0x87f76660: >>> Loading
> module
> > > > > > > ndis.dll at address 0x03D80000-0x03DEF000 (RW data at
> > > > > > > 0x01FE1000-0x01FE1AB4)
> > > > > > > Loaded symbols for
> 'E:\WINCE420\PUBLIC\MORNING_21\RELDIR\XYZDEBUG\NDIS.DLL'
> > > > > > > 4294768484 PID:e7f768ca TID:e7f7647a 0x87f76660: NDIS:
> > > > > > > RebindAdaptersOnResume = 0
> > > > > > > 4294768494 PID:e7f768ca TID:87f3c26a 0x87f3c738: NDIS:
> > > > > > > +ProcessPcmciaDeviceNotificationMessages
> > > > > > > 4294768496 PID:e7f768ca TID:87f3c26a 0x87f3c738: NDIS:
> > > > > > > -ProcessPcmciaDeviceNotificationMessages
> > > > > > > 4294768506 PID:e7f768ca TID:e7f7647a 0x87f76660: >>> Loading
> module
> > > > > > > rtl8139.dll at address 0x03D50000-0x03D5C000 (RW data at
> > > > > > > 0x01FDD000-0x01FDD6E8)
> > > > > > > Loaded symbols for
> 'E:\WINCE420\PUBLIC\MORNING_21\RELDIR\XYZDEBUG\RTL8139.DLL'
> > > > > > > 4294768537 PID:e7f768ca TID:e7f7647a 0x87f76660: RTL8139:
> > > > > > > DLL_PROCESS_ATTACH
> > > > > > > 4294768538 PID:e7f768ca TID:e7f7647a ==>NdisInitializeWrapper
> > > > > > > 4294768539 PID:e7f768ca TID:e7f7647a <==NdisInitializeWrapper
> > > > > > > 4294768540 PID:e7f768ca TID:e7f7647a ==>NdisMRegisterMiniport:
> > > > > > > NdisWrapperHandle 00040800
> > > > > > > 4294768541 PID:e7f768ca TID:e7f7647a
> ==>ndisRegisterMiniportDriver:
> > > > > > > NdisWrapperHandle 00040800
> > > > > > > 4294768543 PID:e7f768ca TID:e7f7647a
> <==ndisRegisterMiniportDriver:
> > > > > > > MiniBlock 00040870
> > > > > > > 4294768543 PID:e7f768ca TID:e7f7647a NdisMRegisterMiniport:
> MiniBlock
> > > > > > > 00040870
> > > > > > > 4294768544 PID:e7f768ca TID:e7f7647a <==NdisMRegisterMiniport:
> > > > > > > MiniBlock 00040870, Status 0
> > > > > > > 4294768546 PID:e7f768ca TID:e7f7647a
> > > > > > > 4294768548 PID:e7f768ca TID:e7f7647a ndisMInitializeAdapter:
> Miniport
> > > > > > > 00040A70,
> > > > > > > 4294768550 PID:e7f768ca TID:e7f7647a
> ==>ndisQueueMiniportOnDriver:
> > > > > > > Miniport 00040A70, MiniBlock 00040870
> > > > > > > 4294768551 PID:e7f768ca TID:e7f7647a
> <==ndisQueueMiniportOnDriver:
> > > > > > > Miniport 00040A70, MiniBlock 00040870, rc 1
> > > > > > > 4294768552 PID:e7f768ca TID:e7f7647a 0x87f76660: RTL8139:: Will
> > > > > > > attempt NdisMAllocateSharedMemory()..
> > > > > > > 4294768554 PID:e7f768ca TID:e7f7647a ==>NdisMSetAttributesEx:
> Miniport
> > > > > > > 00040A70
> > > > > > > 4294768554 PID:e7f768ca TID:e7f7647a 0x87f76660: RTL8139:: Use
> > > > > > > NdisMAllocateSharedMemory().
> > > > > > > 4294768557 PID:e7f768ca TID:e7f7647a Speed/Duplex Mode
> selected:1
> > > > > > > 4294768557 PID:e7f768ca TID:e7f7647a WriteOurCapability
> > > > > > > 4294768558 PID:e7f768ca TID:e7f7647a Setup link, link is up
> > > > > > > 4294768559 PID:e7f768ca TID:e7f7647a Setup link, peer do not
> support
> > > > > > > it, write our speed/duplex,disable autonegotiation
> > > > > > > 4294768559 PID:e7f768ca TID:e7f7647a 0x87f76660: Exception 005
> > > > > > > Thread=87f76660 Proc=e7f768ca
> > > > > > > 4294768560 PID:e7f768ca TID:e7f7647a 0x87f76660: AKY=00000009
> > > > > > > PC=87f51df0 RA=03d54440 BVA=03d504bf
> > > > > > > 4294768560 PID:e7f768ca TID:e7f7647a 0x87f76660: Process
> 'device.exe'
> > > > > > >
> > > > > > >
> > > > > > > My registry settings are as follows:
> > > > > > >
> > > > > > > Common.reg:
> > > > > > > ; @CESYSGEN IF CE_MODULES_RTL8139
> > > > > > > IF BSP_NOPCIBUS !
> > > > > > > IF BSP_NOETHER !
> > > > > > > IF BSP_NIC_RTL8139
> > > > > > >
> > > > > > > [HKEY_LOCAL_MACHINE\Comm\RTL8139]
> > > > > > > ;LOC_FRIENDLYRTL8139
> > > > > > > "DisplayName"=mui_sz:"netmui.dll,#9011"
> > > > > > > "Group"="NDIS"
> > > > > > > "ImagePath"="RTL8139.dll"
> > > > > > >
> > > > > > > ;
> > > > > > > ; Template the PCI bus driver uses to match DLINK RTL cards and
> built
> > > > > > > in RTL on Geode.
> > > > > > > ;
> > > > > > >
> > > > > > > [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Template\RTL8139]
> > > > > > > "Dll"="NDIS.dll"
> > > > > > > "Class"=dword:02
> > > > > > > "SubClass"=dword:00
> > > > > > > "ProgIF"=dword:0
> > > > > > > ; "VendorID"=multi_sz:"1186","1113","10ec","10ec","13D1"
> > > > > > > "VendorID"=multi_sz:"10EC"
> > > > > > > ; "DeviceID"=multi_sz:"1300","1211","8139","8138","AB06"
> > > > > > > "DeviceID"=multi_sz:"8139"
> > > > > > > ; This is replaced by Prefix key to support CardBus adapter.
> > > > > > > ; Adapter will now be instantiated via NDS_INIT.
> > > > > > > ;
> > > > > > > ; "Entry"="NdisPCIBusDeviceInit"
> > > > > > > ;
> > > > > > > "Prefix"="NDS"
> > > > > > > "Transceiver"=dword:3
> > > > > > > "DuplexMode"=dword:1
> > > > > > > "EarlyTxThreshold"=dword:10000
> > > > > > >
> > > > > > > ;
> > > > > > > ; Use shared ISR handler for the RTL8139
> > > > > > > ;
> > > > > > > "IsrDll"="giisr.dll"
> > > > > > > "IsrHandler"="ISRHandler"
> > > > > > > "PortIsIO"=dword:1
> > > > > > > "PortOffset"=dword:3E
> > > > > > > "PortSize"=dword:2
> > > > > > > "PortMask"=dword:C07F
> > > > > > > "UseMaskReg"=dword:1
> > > > > > > "MaskOffset"=dword:3c
> > > > > > >
> > > > > > > ENDIF BSP_NIC_RTL8139
> > > > > > > ENDIF BSP_NOETHER !
> > > > > > > ENDIF BSP_NOPCIBUS !
> > > > > > > ; @CESYSGEN ENDIF CE_MODULES_RTL8139
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > platform.reg:
> > > > > > >
> > > > > > > ; @CESYSGEN IF CE_MODULES_RTL8139
> > > > > > > IF BSP_NIC_RTL8139
> > > > > > > [HKEY_LOCAL_MACHINE\Comm\ConnectionSharing]
> > > > > > > "PrivateInterface"="PCI\\RTL81391"
> > > > > > >
> > > > > > > [HKEY_LOCAL_MACHINE\Comm\PCI\RTL81391\Parms\TcpIp]
> > > > > > > "EnableDHCP"=dword:0
> > > > > > > "DefaultGateway"=""
> > > > > > > "UseZeroBroadcast"=dword:0
> > > > > > > "IpAddress"="192.168.0.1"
> > > > > > > "Subnetmask"="255.255.255.0"
> > > > > > >
> > > > > > > ; @CESYSGEN IF SERVERS_MODULES_WEBPROXY
> > > > > > > ; DHCP Scope option for proxy auto-discovery
> > > > > > > [HKEY_LOCAL_MACHINE\Comm\PCI\RTL81391\DhcpAllocator\DhcpOptions]
> > > > > > >
> > > > >
> > >
> "252"=hex:68,74,74,70,3a,2f,2f,31,39,32,2e,31,36,38,2e,30,2e,31,3a,38,30,38,
> > > > > 30,2f,70,72,6f,78,79,2e,70,61,63,00
> > > > > > > ; @CESYSGEN ENDIF SERVERS_MODULES_WEBPROXY
> > > > > > >
> > > > > > > ENDIF BSP_NIC_RTL8139
> > > > > > >
> > > > > > >
> > > > > > > Apart from these,I added the following entries in project.reg.
> Do
> the
> > > > > > > IRQ and IOBase entries mandatory?
> > > > > > >
> > > > > > > project.reg:
> > > > > > >
> > > > > > > [HKEY_LOCAL_MACHINE\Comm\RTL81391]
> > > > > > > "DisplayName"="RTL8139"
> > > > > > > "Group"="NDIS"
> > > > > > > "ImagePath"="RTL8139.dll"
> > > > > > >
> > > > > > > [HKEY_LOCAL_MACHINE\Comm\RTL8139\Linkage]
> > > > > > > "Route"=multi_sz:"RTL8139"
> > > > > > >
> > > > > > > [HKEY_LOCAL_MACHINE\Comm\Tcpip\Linkage]
> > > > > > > "Bind"="RTL81391"
> > > > > > >
> > > > > > > [HKEY_LOCAL_MACHINE\Comm\RTL8139\Parms]
> > > > > > > "FriendlyName"="RTL8139"
> > > > > > > "BusNumber"=dword:0
> > > > > > > "BusType"=dword:5
> > > > > > > ; "IoBase"=dword:16000000
> > > > > > > ; "IoLen"=dword:100
> > > > > > > ; "IRQ"=dword:10
> > > > > > >
> > > > > > >
> > > > > > > [HKEY_LOCAL_MACHINE\Comm\RTL8139\Parms\TcpIp]
> > > > > > > "EnableDHCP"=dword:0
> > > > > > > "DefaultGateway"=multi_sz:"192.168.9.1"
> > > > > > > "IpAddress"=multi_sz:"192.168.9.131"
> > > > > > > "Subnetmask"=multi_sz:"255.255.255.0"
> > > > > > > "UseZeroBroadcast"=dword:0
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Regards,
> > > > > > > Kamaal



Relevant Pages

  • Re: Intel Pro Wireless 3945 ABG no probs connecting, but dead line
    ... Did DHCP deliver an IP address to your laptop from the Tekram? ... ipconfig /release ... ping 192.168.1.1. ...
    (alt.internet.wireless)
  • Re: Winsock provider catalog
    ... PING: transmit failed, error code 65. ... info Using home Internet connection ... info Network connection: Name=Local Area Connection 3, ...
    (microsoft.public.windowsxp.general)
  • Re: HELP- Intermittent Connection Problems....Blamed on XP!!??
    ... Error code 65 can be caused by Internet Connection Sharing. ... because we are at the limit of my expertise. ... As you suggested, here's the PING results: ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: HELP- Intermittent Connection Problems....Blamed on XP!!??
    ... I don't think we can fix this via a help forum, ... On the resulting screen type in "ipconfig" and press Enter; ... Then the next time you lose the connection: ... On the resulting screen type "ping 127.0.0.1" without the quotes. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: New PC Cannot Connect to Internet
    ... can you ping each machine by name and not timeout? ... Try opening a command prompt and type the commands below pressing Enter after each. ... ipconfig /all **Does all look proper and fit? ... Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm ...
    (microsoft.public.windowsxp.general)