Thread: [Madwifi-users] Re: ath driver in 2.6.10-rc2
Status: Beta
Brought to you by:
otaku
From: Peter R. <pbr...@gm...> - 2004-12-29 04:54:18
|
On Fri, 2004-12-24 at 05:50 +0100, Michael Renzmann wrote: > Hi. > > Stephen Walton wrote: > >>What DHCP client are you using? > > Whatever one comes with FC3. The DHCP server is a Netgear access point. > > Can anyone say what DHCP client is used in FC3? dhclient in the FC3 client used, its part of the dhcp package from the ISC. I'm seeing similar problems with the CVS Version of the code with a DLink DWL-G650 revision C2. The card seems to come up OK and is all there. Using ethereal on the interface you see it request a DHCP address but the responses comes back with bad UDP checksums so they are discarded. The router/dhcp server is a DLink DI-624. The same DHCP Server will assign an address to a wired ethernet interface with no problems on the same laptop, if you manually assign an IP address you don't seem to get any data although I haven't ran any packet captures to see if there's any issues there either. Regards Peter |
From: Michael R. <ma...@no...> - 2004-12-29 09:05:55
|
Hi Peter. Peter Robinson wrote: > I'm seeing similar problems with the CVS Version of the code with > a DLink DWL-G650 revision C2. The card seems to come up OK and is all > there. Using ethereal on the interface you see it request a DHCP > address but the responses comes back with bad UDP checksums so they > are discarded. Aha! Now it would be interesting to know if others, who experience the same problems, also see bad UDP checksums. Thanks for your report. Bye, Mike |
From: Stephen W. <ste...@cs...> - 2004-12-30 16:46:58
|
Michael Renzmann wrote: > Peter Robinson wrote: > >> I'm seeing similar problems with the CVS Version of the code with >> a DLink DWL-G650 revision C2. The card seems to come up OK and is all >> there. Using ethereal on the interface you see it request a DHCP >> address but the responses comes back with bad UDP checksums so they >> are discarded. > > > Aha! Now it would be interesting to know if others, who experience the > same problems, also see bad UDP checksums. I'm afraid that is not my problem. I just rebuilt madwifi from the latest CVS under 2.6.10rc3. Even though 'modprobe ath_pci' succeeds, when I start ethereal, ath0 is not listed as an available interface. Logging with ethereal while I try to start the network ('/etc/sysconfig/network-scripts/ifup ath0') shows no packets at all going out over the wireless link. The same setup works fine on the stock 2.6.9 FC3 kernel; I get a link and ethereal happily logs the packets. This is with FC3 on a Compaq Presario 2100 and a D-Link LWL-G650 Rev B card. Access point is a D-Link DI-624. |
From: Stephen W. <ste...@cs...> - 2005-01-02 02:24:57
|
Peter Robinson wrote: >What does the output from dmesg have to say. With my FC3 with a make, >make install, modprobe ath_pci it all comes up and is fine. > OK, I'm having some other problem. With 2.6.10-rc3, the card is not found. It does not show up in lspci, nor does madwifi find it (of course). Again, this is a Compaq laptop with a D-Link DWL-G650 rev B card. Now what? |
From: Richard D. <ri...@ph...> - 2005-01-02 12:11:45
|
Hello. Stephen Walton wrote: > Peter Robinson wrote: > >> What does the output from dmesg have to say. With my FC3 with a make, >> make install, modprobe ath_pci it all comes up and is fine. >> > OK, I'm having some other problem. With 2.6.10-rc3, the card is not > found. It does not show up in lspci, nor does madwifi find it (of > course). Again, this is a Compaq laptop with a D-Link DWL-G650 rev B card. > > Now what? You need a patch to build and get a working driver with 2.6.10-rc2 or later. People have reported success with my patch: http://sourceforge.net/mailarchive/forum.php?thread_id=6188321&forum_id=33958 A couple of people have also posted similar patches. You can find those in the mail archives too. Good luck! Bye, Rich =] -- Richard Dawe [ http://homepages.nildram.co.uk/~phekda/richdawe/ ] "You can't evaluate a man by logic alone." -- McCoy, "I, Mudd", Star Trek |
From: Michael R. <ma...@no...> - 2005-01-02 12:31:19
|
Hi. Richard Dawe wrote: > You need a patch to build and get a working driver with 2.6.10-rc2 or > later. People have reported success with my patch: No need to apply a patch anymore, simply upgrading to the latest CVS snapshot should do the trick. You're patch (along with other stuff) has been incorporated some days ago. Bye, Mike |
From: Richard D. <ri...@ph...> - 2005-01-02 12:50:32
|
Hello. Michael Renzmann wrote: > > Richard Dawe wrote: > >> You need a patch to build and get a working driver with 2.6.10-rc2 or >> later. People have reported success with my patch: > > > No need to apply a patch anymore, simply upgrading to the latest CVS > snapshot should do the trick. You're patch (along with other stuff) has > been incorporated some days ago. Yes, you're quite right. Time for me to get with the program. ;) Thanks! Bye, Rich =] -- Richard Dawe [ http://homepages.nildram.co.uk/~phekda/richdawe/ ] "You can't evaluate a man by logic alone." -- McCoy, "I, Mudd", Star Trek |