Re: Project Evil: The Evil Continues

Works a treat!! (Dell Latitude D600, 5.2-CURRENT - buildworld 24/1/04,
25/1/04, 26/1/04)

Comes up on boot/resume with no problems. Had to try a few windows
drivers - the one that worked was the latest driver for XP from Dell.
Win2k drivers don't seem to work at all. I can pull up to about
660Kbyte/s across it. No signs of instability. Not tried WEP and only in
adhoc mode (I understand that they are not supported yet?). 

$ dmesg | grep ndis
Preloaded elf module "/boot/kernel/ndis.ko" at 0xc0b97418.
Preloaded elf module "/boot/kernel/if_ndis.ko" at 0xc0b974c4.
ndis0: <Intel(R) PRO/Wireless LAN 2100 3A Mini PCI Adapter> mem
0xfafef000-0xfafeffff irq 11 at device 3.0 on pci2
ndis0: NDIS API version: 5.1
ndis0: 802.11 address: 00:04:23:a0:85:c3
ndis0: 11b rates: 11Mbps 2Mbps 1Mbps
ndis0: set auth failed: 19
ndis0: set auth failed: 19
ndis0: link up

Keep up the good/evil work!

Thanks,
James

On Mon, 2004-01-26 at 00:53, Bill Paul wrote:
> > On Sat, Jan 24, 2004 at 07:49:00PM -0800, Bill Paul wrote:
> > <snip>
> > > If you have a system with one of these chipsets, please give the
> > > NDISulator a try. Note: you do NOT have to recompile your kernel to
> > > test it. Find the .sys and .inf files from your Windows driver media
> > > and do the following:
> > > 
> > > # cp foo.sys foo.inf /sys/modules/if_ndis
> > > # cd /sys/modules/ndis
> > > # make; make load
> > > # cd /sys/modules/if_ndis
> > > # ndiscvt -i foo.inf -s foo.sys -o ndis_driver_data.h
> > > # make; make load
> > > 
> > > You don't even have to reboot. Well, not unless the driver causes
> > > a panic. :/
> > > 
> > <snip>
> > 
> > Please correct me if i'm wrong but does this mean you can only use one single 
> > instance of the ndis driver? If this stuff is really working i think we should 
> > see more instances of the ndis, true?  example a wireless card and a onboard 
> > ethernet? Maybe more. How can you work around that problem?
> 
> Yes you're wrong: you can use more than one NDIS driver. Say you want
> "bwe" (broadcom wireless) and "iwe" (Intel wireless) devices on the same
> machine:
> 
> # mkdir /sys/modules/if_bwe
> # mkdir /sys/modules/if_iwe
> # cp /sys/modules/if_ndis/Makefile /sys/modules/if_bwe
> # cp /sys/modules/if_ndis/Makefile /sys/modules/if_iwe
> # cp bwe.sys bwe.inf /sys/modules/if_bwe
> # cp iwe.sys iwe.inf /sys/modules/if_iwe
> # cd /sys/modules/if_bwe
> # ndiscvt -n bwe -i bwe.inf -s bwe.sys ndis_driver_data.h
> # make
> # cp if_ndis.ko if_bwe.ko
> # cd /sys/modules/if_iwe.ko
> # ndiscvt -n iwe -i iwe.inf -s iwe.sys ndis_driver_data.h
> # make
> # cp if_ndis.ko if_iwe.ko
> 
> You now have both if_bwe.ko and if_iwe.ko drivers.
> 
> > It's just a thought, nothing more, i really like this thing because it helps
> > using strange hardware buildin laptops for example. Really cool stuff.
> 
> You should have read the ndiscvt(8) man page before asking.
> 
> Now, is anyone going to actually test Project Evil with their
> cards like I asked, or is everyone just going to use this as an excuse
> to ask me questions?
> 
> -Bill
> 
> --
> =============================================================================
> -Bill Paul            (510) 749-2329 | Senior Engineer, Master of Unix-Fu
>                  wpaul_at_windriver.com | Wind River Systems
> =============================================================================
>               <adamw> you're just BEGGING to face the moose
> =============================================================================
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"