Re: ndis on 6.1-PRERELEASE

Fabian Keil <[email protected]>
Newsgroups gmane.os.freebsd.devel.mobile
Message-ID <20060207124340.56f62d38@localhost>
"Dan Langille" <[email protected]> wrote:

> I'm trying, and failing so far, to get ndis running on 6.1-PRERELEASE 
> (Sat Feb 4).  I was using ipw but it frooze the system.

?
 
> I have an IBM ThinkPad T41.  I grabbed the drivers from http://www-
> 307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-59438
> 
> After downloading and extracting the files from 1rwc88ww.exe, 
> I used w70n501.inf and w70n51.sys as inputs to ndisgen.
> 
> When asked for firmware, I supplied w70n51.sys the input.

For me this step was never needed and I just press return to
skip it. I use ndis with an
Intel(R) PRO/Wireless 2200BG Network Connection.
 
> The result was w70n51_sys.ko and w70n51.sys.ko
> 
> I loaded ndis.ko, if_ndis.ko, w70n51.sys.ko, and w70n51_sys.ko (in 
> that order).  dmesg showed:
> 
> ndis0: <Intel(R) PRO/Wireless LAN 2100 3B Mini PCI Adapter> mem 
> 0xc0214000-0xc0214fff irq 11 at device 2.0 on pci2
> ndis0: [GIANT-LOCKED]
> ndis0: NDIS API version: 5.1
> ndis0: Ethernet address: 00:0c:f1:27:67:f5

Don't you get this even without loading w70n51.sys.ko?

> ndis0 is unable to set/retain an SSID while it is UP.  When DOWN, 
> yes, it takes an SSID, but moving the card to UP loses the SSID:

Try setting the ssid together with the bssid, this works for me
on a TP51 running 6.0-Stable.

Without specifying the bssid I get results like you described,
but I can't set the ssid alone, even if ndis0 is down.
More information at:
http://www.mail-archive.com/[email protected]/msg75473.html.

Fabian
-- 
http://www.fabiankeil.de/
signature.asc (application/pgp-signature, 187 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iD8DBQFD6IfzjV8GA4rMKUQRApu8AJ4y3y9a8OWCzMz3JJwcmDJ3MbCKaQCggUf+
CZq42kezvVHOplcHH0S7cIc=
=oYQs
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.