Support of NIC Realtek 8139

[Gge]

PLease find the status of the Reactos support for the Nic Realtek8139 as 
per my testing.

1) Detection of Pci Bus2 = Fixed

The problem of enumerating cards located on PCI BUS 2 has been fixed by 
Eric Khol . The bug# 436 can be closed

2) Start Nic driver failure

The RTL8139.SYS driver loads successfully but fails to start due to the 
"NdisMQueyAdapterResources" function which is unimplemnted .

The Bug#446 has been created
=> This is a blocking point for networking with this popular Nic

Best regards
Gerard

[Jonathan Wilson]

Does this work mean anything for users of cards using the RTL8180.sys 
driver (i.e. with Realtek 8180 chipset)?

I have one of these cards and may (if I can find the time and once a method 
becomes available to use my USB mouse with ROS or failing that, a way to 
use the needed ROS bits without a mouse) be able to do testing on the card 
to help get it to function.

"Jonathan Wilson" [e-mail] wrote:
> Does this work mean anything for users of cards using the RTL8180.sys
> driver (i.e. with Realtek 8180 chipset)?

No, because most of our computers don't have a motherboard with 3 PCI buses.
Devices on the third bus (bus #2) were not enumerated. This bug was fixed.

Regards,
Eric

[Filip Navara]

Gge wrote:
> The RTL8139.SYS driver loads successfully but fails to start due to 
> the "NdisMQueryAdapterResources" function which is unimplemnted .

Try this workaround please: www.volny.cz/xnavara/rtl_bins/io_res.patch
(binaries also available at www.volny.cz/xnavara/rtl_bins/)

NOTE FOR DEVELOPERS:  I released an example filter driver that 
implements custom PnP Arbiter for Windows. It's available at 
www.volny.cz/xnavara/arbfilter.zip. If someone wants to adapt the code 
for ReactOS and implement the other parts it would be great. 
Unfortunately I don't have enough time to do that now...

Regards,
Filip

[Gge]

Filip Navara wrote:
> Gge wrote:
> > The RTL8139.SYS driver loads successfully but fails to start due to 
> > the "NdisMQueryAdapterResources" function which is unimplemnted .
>
> Try this workaround please: www.volny.cz/xnavara/rtl_bins/io_res.patch
> (binaries also available at www.volny.cz/xnavara/rtl_bins/)
>
> NOTE FOR DEVELOPERS:  I released an example filter driver that 
> implements custom PnP Arbiter for Windows. It's available at 
> www.volny.cz/xnavara/arbfilter.zip. If someone wants to adapt the code 
> for ReactOS and implement the other parts it would be great. 
> Unfortunately I don't have enough time to do that now...
>
> Regards,
> Filip

Thanks Filip,

I shouild use both Ntoskrnl and ndis binaries as a workaround ?

Reagrds
Gerard

[Filip Navara]

Gge wrote:
> I shouild use both Ntoskrnl and ndis binaries as a workaround ?

The NTOSKRNL is the one from CVS (as of the date of the file) with the 
workaround applied and the NDIS is just actual build from my NDIS branch 
(I wasn't sure if you have it). Both of them are needed...

Regards,
Filip

[Gge]

Filip Navara wrote:
> Gge wrote:
> > I shouild use both Ntoskrnl and ndis binaries as a workaround ?
>
> The NTOSKRNL is the one from CVS (as of the date of the file) with the 
> workaround applied and the NDIS is just actual build from my NDIS branch 
> (I wasn't sure if you have it). Both of them are needed...
>
> Regards,
> Filip

I used both of them  .  so ntoskrnl.exe has been used with workaround 
and it bugchecks.

Gerard

"Filip Navara" [e-mail] wrote:
> NOTE FOR DEVELOPERS:  I released an example filter driver that
> implements custom PnP Arbiter for Windows. It's available at
> www.volny.cz/xnavara/arbfilter.zip. If someone wants to adapt the code
> for ReactOS and implement the other parts it would be great.
> Unfortunately I don't have enough time to do that now...

Thanks for releasing that code! I already wrote some stuff for the arbiter
interface in pci.sys and the io manager.

Regards,
Eric