Re: ndis on 6.1-PRERELEASE

"Dan Langille" <[email protected]>
Newsgroups gmane.os.freebsd.devel.mobile
Message-ID <[email protected]>
resending, with additionl information after building a new module 
this morning.

On 7 Feb 2006 at 21:28, Bill Paul 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.
> 
> Even though there's nothing I can do about it personally and you don't
> happen to perceive it as being your primary problem, it would have been
> nice if you'd bothered to elaborate further on this.

That's in another thread.  I''ve had the same problem for about 6 or 
8 months with ipw.  It works, for a while, but then freezes the 
system up totally.

> > 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.
> 
> No, wrong. You didn't read what ndisgen said about the nature of firmware
> files. There are _extra_ files, in addition to the .inf and .sys files.
> The Intel driver doesn't have any: they compiled the firmware for the
> chip directly into the driver (which is why w70n51.sys is several megabytes
> in size -- not only did the compile it in, they did it in S-record format).
>  
> > The result was w70n51_sys.ko and w70n51.sys.ko
> 
> Go back and do it again, this time skipping the firmware by just
> hitting enter at the prompt. You should only have w70n51_sys.ko.

Will do.  That's a job for tomorrow morning.  I think we tried that, 
but I'll try it again.

> > 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
> 
> Looks fine so far.
> 
> > 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:
> 
> It doesn't "lose" the SSID. It's not able to associate in the first
> place. Setting the SSID when the interface is down doesn't have any
> effect on the chip. When it's up, ifconfig will report exactly what
> the NDIS driver's current state is. (If it's not associated, it'll
> report as much.)

Ahh, thanks. That explains something I didn't know.  Cheers.

> Unfortunately, you provided very little additional information. In
> particular, you failed to report the output of "ifconfig ndis0 scan"
> to us. If the card doesn't see an AP named "foo" when you do a scan,
> it won't be able to associate.

I tried that. It finds the same APs that Windows XP finds.  And if 
finds the AP I'm interested in: DoNotUseThis

> You also failed to tell us what kind of AP you're trying to associate
> with and what security options, if any, may be set on it. You also
> didn't mention if your laptop has an RF kill switch and whether or not
> you turned it on.

It's a Linksys WAP54G.  No WEP.  I can't recall if there's any MAC 
filtering, but if there any MAC filteringt, it permits this NIC (it 
works with Windows XP and with the ipw driver).

> You should be able to just do "ifconfig ndis0 ssid <myssid> up" and have
> it associate when it starts up.

Here is what happened this morning:

# kldstat
Id Refs Address    Size     Name
 1    3 0xc0400000 6b7b30   kernel
 2    1 0xc0ab8000 58554    acpi.ko
# kldload ndis
# kldstat
Id Refs Address    Size     Name
 1   10 0xc0400000 6b7b30   kernel
 2    1 0xc0ab8000 58554    acpi.ko
 3    1 0xc28bd000 b000     if_ndis.ko
 4    1 0xc28c9000 13000    ndis.ko
# kldload ./W70N51_SYS.ko
# dmesg | tail -5
Trying to mount root from ufs:/dev/ad0s2a
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
# ifconfig ndis0
ndis0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::20c:f1ff:fe27:67f5%ndis0 prefixlen 64 scopeid 0x4
        ether 00:0c:f1:27:67:f5
        media: IEEE 802.11 Wireless Ethernet autoselect
        status: no carrier
        ssid "" channel 1
        authmode OPEN privacy OFF txpowmax 100
# ifconfig ndis0 scan
SSID            BSSID              CHAN RATE  S:N   INT CAPS
DoNotUseThis    00:06:25:3b:e7:77   11   54M 165:0   100 E    ??? ??? 
??? ??? ??? ??? ??? VEN
paqueeney       00:11:95:55:13:ab   11   36M 165:0   100 EP   ??? ??? 
??? ???
# ifconfig ndis0 ssid DoNotUseThis up
# ifconfig ndis0
ndis0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::20c:f1ff:fe27:67f5%ndis0 prefixlen 64 scopeid 0x4
        ether 00:0c:f1:27:67:f5
        media: IEEE 802.11 Wireless Ethernet autoselect
        status: no carrier
        ssid "" channel 1
        authmode OPEN privacy OFF txpowmax 100
#

-- 
Dan Langille : Software Developer looking for work
my resume: http://www.freebsddiary.org/dan_langille.php


_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "[email protected]"
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.