Alright, lads and lasses. You may not believe this, but I got the wireless working.Firstly, I gcompiled MADWiFi from the website at marlow.dk. I made sure to use both make-kpkg clean and to delete the linux symlink (which was present).
Then I simply used KWiFiManager to connect (via putting in the
On Sunday 25 September 2005 03:52, David R. Litwin wrote:
Isn't make-kpkg used to make a kernel? Or, does it simply happen to
co-incide.?
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. Don't I? Now, I'd be willing to go
The first use of make-kpkg in the marlow.dk howto simply sets up the
.config file to match the binary installed kernel that you are running.The second use appends the new modules (in this case madwifi) to thethe existing kernel by building a madwifi-modules deb file you can
install.So although you
On Sun, 25 Sep 2005, David R. Litwin wrote:
Which is better: MADWiFi or ndiswrapper; and why?
madwifi is better because... ( in one pc )
- it supports 3 flavors of WEP key sizes
- it supports wpa
- it can be your AP
- it can be firewalled
- it can be a
On Saturday 24 September 2005 07:52 pm, David R. Litwin wrote:
Isn't make-kpkg used to make a kernel? Or, does it simply happen to
co-incide.?
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. Don't I? Now, I'd be willing to
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
no.. you compile the madwifi drivers for your kernelor find ones that a precompiled for your kernel:
linux-2.6.13-123.4-89.abcget the latest madwifi drivers from cvs at madwifi.sourceforge.net
no ... compile madwifi .. NOT the kernelcd /usr/local/srcdownload madwifi driverscd madwifimakemake
I have recently acquired a Toshiba A70. It has a WiFi card: an Atheros 5004X. This is built in to the machine, so I have no need to purchase another one.Now, I do need a driver for this. I have looked, and it seems to me that the NdisWrapper would be the Driver for me. It gives two options: The
NdisWrapper emulates a windows-driver. Maybe you want to consider using
madwifi which would be a native dirver. If you are interested have a
look at the following sites:
http://madwifi.sourceforge.net/
http://www.marlow.dk/site.php/tech/madwifi
Hope, this helps.
Louis
David R. Litwin
On 24/09/05, Louis Woods [EMAIL PROTECTED] wrote:
NdisWrapper emulates a windows-driver. Maybe you want to consider usingmadwifi which would be a native dirver. If you are interested have alook at the following sites:
http://madwifi.sourceforge.net/http://www.marlow.dk/site.php/tech/madwifiHope,
On Saturday 24 September 2005 20:48, David R. Litwin wrote:
On 24/09/05, Louis Woods [EMAIL PROTECTED] wrote:
NdisWrapper emulates a windows-driver. Maybe you want to consider using
madwifi which would be a native dirver. If you are interested have a
look at the following sites:
You do not need to compile your own kernel, just the module.Instructions as to how to do this can be found at:-
http://www.marlow.dk/site.php/tech/madwifiand yes those instructions are Debian specific.There are an error in that page, and some changes needed
if you are using 2.6.12.In the first
Isn't make-kpkg used to make a kernel? Or, does it simply happen to co-incide.?
As a bit of a follow-up, I read the marlow.dk site: I do need to compile my own kernel with that. Don't I? Now, I'd be willing to go with the ndiwrapper, but I do not konw where the Windows driver is. Furthermore,
13 matches
Mail list logo