RE: what is wrong with this RTL 8139 Registry setting

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Hi Coney,

Yes It was PCI based device, Thanks, for the providing the fix, it works.
It seems like WINCE 5.0 help on Ne2000 PCI ethernet registry setting is
misleading and it should be fixed. Any way it fixed our problem

thanks again
ED

"Corey Burke [MS]" wrote:

> Is this a PCI RTL card? If so, I think you need "PCI\RTL8139" instead of
> just "RTL81391" in certain places. You need this because the PCI driver
> loads NDIS which in turns loads the miniport driver. The PCI driver looks
> at certain registry keys and without them you'll get the default settings.
>
> -Corey
>
> For Example:
>
> IF IMGNOKITL
> IF BSP_NIC_RTL8139
> ;new RTL8139driver entry
> ; Template the PCI bus driver uses to match RTL
> [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"
> "DeviceID"=multi_sz:"1300","1211","8139","8138","AB06"
> "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:0 ; 1= io status read/write 0= memory space
> read/write
> "PortOffset"=dword:3E ; address of interrupt status register
> "PortSize"=dword:2 ;access is 16 bit
> "PortMask"=dword:C07F ;valid mask for interrupt status register
> "UseMaskReg"=dword:1
> "MaskOffset"=dword:3c
>
> [HKEY_LOCAL_MACHINE\Comm\RTL8139]
> "DisplayName"="Realtek RTL8139 based Fast Ethernet Driver"
> "Group"="NDIS"
> "ImagePath"="rtl8139.dll"
>
> [HKEY_LOCAL_MACHINE\Comm\RTL8139\Linkage]
> "Route"=multi_sz:"PCI\\RTL81391"
>
> [HKEY_LOCAL_MACHINE\Comm\PCI\RTL81391\Parms]
> "BusNumber"=dword:0
> "BusType"=dword:5
> "PhysicalAddressBase"=dword:06000000
> "RxBufLen"=dword:3;
> "DuplexMode"=dword:1
> "SharedInterrupt"=dword:0
> "ScanMethod"=dword:0 ;0:PCI scan(default),
>
> [HKEY_LOCAL_MACHINE\Comm\PCI\RTL81391\Parms\TcpIp]
> "EnableDHCP"=dword:0
> "IpAddress"="192.168.0.3"
> "DefaultGateway"="192.168.0.254" ;set to your static tcpip setting
> "UseZeroBroadcast"=dword:"0x0"
> "Subnetmask"="255.255.0.0"
>
> [HKEY_LOCAL_MACHINE\Comm\Tcpip\Linkage]
> "Bind"=multi_sz:"PPP","PCI\\RTL81391"
>
> [HKEY_LOCAL_MACHINE\DebugZones]
> "rtl8139"=dword:FF
> "pcibus"=dword:3F
> ENDIF BSP_NIC_RTL8139
> ENDIF IMGNOKITL
>
>
.



Relevant Pages

  • Re: Transparent bridges (a. k. a. HUB-to-PCI bridges)?
    ... While I was booting Linux, I saw a 'transparent bridge' from dmesg and ... We do exactly this already in our pci pci bridge code. ... But I don't see any special treatment in FreeBSD's PCI driver. ... We already have the relevant code. ...
    (freebsd-current)
  • vm_fault when accessing PCI address space
    ... to work on 88F5181L SoC which have embedded PCI controller. ... PCI driver detects resources and recognizes Atheros wlan card, ...
    (freebsd-hackers)
  • Re: Generic PCI target driver
    ... Is anybody aware of the existence of a generic PCI driver for a PCI target ... which could allow to access memory mapped ... I've never seen anything but complaints from Jungo ...
    (microsoft.public.development.device.drivers)
  • Re: vm_fault when accessing PCI address space
    ... to work on 88F5181L SoC which have embedded PCI controller. ... PCI driver detects resources and recognizes Atheros wlan card, ...
    (freebsd-hackers)
  • RE: [PATCH 2.6.33 1/3] net: Micrel KSZ8841/2 PCI Ethernet driver
    ... pointer actually change during the lifetime of the PCI driver? ... If the PCI device is removed, like physically removing the card, ... shouldn't the kernel also close the network device assocated with the ... That makes sense as those PCI devices are outside PCI driver control. ...
    (Linux-Kernel)