Bug #29

/usr/src/sys/dev/netif/ndis/if_ndis.c

Added by esmith over 8 years ago. Updated almost 8 years ago.

Status:ClosedStart date:
Priority:HighDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

All cases ( about seven ) of "ifp->serializer" in the file
/usr/src/sys/dev/netif/ndis/if_ndis.c
need to be changed because "serializer" is not a member of struct ifnet.
They should be changed to "if_serializer", I believe.

This compiles, however, when the generated kernel module is loaded the
system panics ( on a call to lwkt_serialize_enter() ), so there is still
more work to be done.

History

#1 Updated by dillon over 8 years ago

:
:
:All cases ( about seven ) of "ifp->serializer" in the file
: /usr/src/sys/dev/netif/ndis/if_ndis.c
:need to be changed because "serializer" is not a member of struct ifnet.
: They should be changed to "if_serializer", I believe.
:
:This compiles, however, when the generated kernel module is loaded the
:system panics ( on a call to lwkt_serialize_enter() ), so there is still
:more work to be done.

I will fix this completely before the release. I have a laptop that
uses ndis and I will upgrade it and make sure it NDIS compiles and
operates properly.

-Matt
Matthew Dillon
<>

#2 Updated by esmith over 8 years ago

Matthew Dillon wrote:
> I will fix this completely before the release. I have a laptop that
> uses ndis and I will upgrade it and make sure it NDIS compiles and
> operates properly.
>

Using 1.4 rc2, I can now kldload if_ndis.ko without freezing the system,
however, it does not yet create interface ndis0.

#3 Updated by dillon over 8 years ago

:Using 1.4 rc2, I can now kldload if_ndis.ko without freezing the system,
:however, it does not yet create interface ndis0.

if_ndis alone will not create an interface. You have to follow the
instructions in the README to associate a windows device driver
with it. Then it comes down to it probing the device properly.

-Matt
Matthew Dillon
<>

#4 Updated by esmith over 8 years ago

Matthew Dillon wrote:
> if_ndis alone will not create an interface. You have to follow the
> instructions in the README to associate a windows device driver
> with it. Then it comes down to it probing the device properly.

I did follow the instructions and at step four where it states, "you
should something similar to the following system console messages:", I
get one blank line of output when using Xorg. ifconfig shows no ndis0
interface.

When I'm only using the console and I do the last kldload, I see this
error:

Function Extension: ...
..
CIS reading done
ndis0: <Belkin Wireless ... Adapter> mem ... irq 11 at device 0.0 on
cardbus1
can't re-use a leaf (FrameBursting)!
ndis0: NDIS API version 5.0
ndis0: NDIS ERROR: c000138d (unknown error)
ndis0: NDIS NUMERRORS: 1
ndis0: argptr: 0x103
ndis0: init handler failed
device_probe_and_attach: ndis0 attach returned 6

#5 Updated by dillon over 8 years ago

:
:Matthew Dillon wrote:
:> if_ndis alone will not create an interface. You have to follow the
:> instructions in the README to associate a windows device driver
:> with it. Then it comes down to it probing the device properly.
:
: I did follow the instructions and at step four where it states, "you
:should something similar to the following system console messages:", I
:get one blank line of output when using Xorg. ifconfig shows no ndis0
:interface.
:
: When I'm only using the console and I do the last kldload, I see this
:error:
:
:Function Extension: ...
:..
:CIS reading done
:ndis0: <Belkin Wireless ... Adapter> mem ... irq 11 at device 0.0 on
:cardbus1
:can't re-use a leaf (FrameBursting)!
:ndis0: NDIS API version 5.0
:ndis0: NDIS ERROR: c000138d (unknown error)
:ndis0: NDIS NUMERRORS: 1
:ndis0: argptr: 0x103
:ndis0: init handler failed
:device_probe_and_attach: ndis0 attach returned 6

It looks like an issue that a lot of people have had with that
device. Do a google search for "belkin wireless ndis c000138d".
I'm not sure if there is a fix anywhere. It could be a firmware
issue.

-Matt
Matthew Dillon
<>

#6 Updated by esmith over 8 years ago

Matthew Dillon wrote:
> It looks like an issue that a lot of people have had with that
> device. Do a google search for "belkin wireless ndis c000138d".
> I'm not sure if there is a fix anywhere. It could be a firmware
> issue.

A new Netgear card doesn't work, either, however, now kldstat states
if_ndis.ko is loading.

output is
..
CIS reading done
ndis0: <NETGEAR ... > mem ... irq 11 at device 0.0 on cardbus1
no match for toupper
ndis0: NDIS API version: 5.0
ndis0: init handler failed
device_probe_and_attach: ndis0 attach returned 6
cardbus1: release_all_resource: Resource still owned by child, oops. (
type=3, rid=20, addr=88000000)

#7 Updated by corecode over 8 years ago

panics fixed by dillon

Also available in: Atom PDF