On Sun, 25 Sep 2005, David Koski wrote:
> On Saturday 24 September 2005 07:52 pm, David R. Litwin wrote: > > > > As a bit of a follow-up, I read the marlow.dk <http://marlow.dk> site: I do > > need to compile my own kernel with that. no.. you compile the madwifi drivers for your kernel or find ones that a precompiled for your kernel: linux-2.6.13-123.4-89.abc get the latest madwifi drivers from cvs at madwifi.sourceforge.net > Don't I? Now, I'd be willing to go with the ndiwrapper, traitor :-0 > but I do not konw where the Windows driver is. look at the cd that came with the hardware .. ms forces all the manufacturers to provide a 600MB cd for their hw > > Furthermore, apparently, it doesn't even work. it works ... ndiswrapper usually works ... i havent seen on that doesn't work, even if it's dead by default due to mswindows - you should be able to install the windoze drivers - you should be able to see the hardware - you may even be able to config it - whether you can ping wirelessly is a different ballgame > > So, it seems my options are compile the kernel, no ... compile madwifi .. NOT the kernel cd /usr/local/src download madwifi drivers cd madwifi make make install ls -la /lib/modules/`uname -r`/net modprobe "madwifi" ifconfig ath0 up ifconfig -v - how you configure the params is a different ballgame > > Please, do tell me what I should do. gp down the local linux/unix/c++ user groups and say you will buy pizza for whomever gets it working madwifi howto http://Madwifi.net c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
