Hi,
the rtl8139 driver is a pci based driver. This driver needs more registry keys. A half year ago, I've used this registry entries for a realtec 8139 based nic:
; D-Link DRN-32TX PCI NIC Driver HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS","ErrorControl",0x00010001,0x 00000000 HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS","Group",0x00000000,"NDIS" HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS","ImagePath",0x00020000,"syst em32\drivers\DLKRTS.SYS" HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS","Start",0x00010001,0x0000000 4 HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS","Type",0x00010001,0x00000001 HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS\Linkage","Bind",0x00010000,"\ Device\DLKRTS1" HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS\Linkage","Export",0x00010000, "\Device\DLKRTS1" HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS\Linkage","Route",0x00010000," DLKRTS1" HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS\Enum","0",0x00000000,"PCI\VEN _10EC&DEV_8139&SUBSYS_81391186&REV_10\0815" HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS\Enum","Count",0x00010001,0x00 000001 HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS\Enum","NextInstance",0x000100 01,0x00000001 HKLM,"SYSTEM\CurrentControlSet\Enum\PCI\VEN_10EC&DEV_8139&SUBSYS_81391186&RE V_10\0815","Service",0x00000000,"DLKRTS" HKLM,"SYSTEM\CurrentControlSet\Enum\PCI\VEN_10EC&DEV_8139&SUBSYS_81391186&RE V_10\0815","Class",0x00000000,"Net" HKLM,"SYSTEM\CurrentControlSet\Enum\PCI\VEN_10EC&DEV_8139&SUBSYS_81391186&RE V_10\0815","ClassGUID",0x00000000,"{4D36E972-E325-11CE-BFC1-08002BE10318}"
; D-Link DRN-32TX PCI Adapter 1 HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS1","ErrorControl",0x00010001,0 x00000001 HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS1","Start",0x00010001,0x000000 04 HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS1","Type",0x00010001,0x0000000 4 HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS1\Linkage","Bind",0x00010000," \Device\DLKRTS1" HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS1\Linkage","Export",0x00010000 ,"\Device\DLKRTS1" HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS1\Linkage","Route",0x00010000, "DLKRTS1" HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS1\Parameters","SlotNumber",0x0 0000000,"9" HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS1\Parameters\Tcpip","DefaultGa teway",0x00010000,"192.168.1.0" HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS1\Parameters\Tcpip","IPAddress ",0x00010000,"192.168.1.5" HKLM,"SYSTEM\CurrentControlSet\Services\DLKRTS1\Parameters\Tcpip","SubnetMas k",0x00010000,"255.255.255.0"
It doesn't work with the current cvs. The start and type values are possible also incorrect. The value "9" from the key "SlotNumber" is a hex value which must point to the correct pci slot. The best way to get all this informations is a NT 4.0 or W2K installation.
An other problem is the loading of the real ne2000.sys driver. This is not a boot load driver but ros trys to load it like a boot load driver (after pci.sys). Ros trys it a second time after loading ndis. The start value of ne2000 is 4, this means do not load. if I change this value to 3, driver is loaded at the second point successful, but it doesn't find a nic.
- Hartmut
-----Original Message----- From: ros-dev-bounces@reactos.com [mailto:ros-dev-bounces@reactos.com] On Behalf Of Gge Sent: Sunday, October 17, 2004 10:34 PM To: ReactOS Development List Subject: [ros-dev] Loading failure of rtl8139.sys driver.
Hello,
The Realtek 8139 Nic driver fails to boot as indicated in the debug messages .
The hivesys registry used is ne2000 and the rtl3139.sys has been renamed to ne2000.sys + amd pcnet disabled
Note : this driver file is working fine with WinXP
Any idea ?
Regards Gerard