On Tue, Jun 30, 2009 at 6:50 PM, Jasin Colegrove<j.wholesalesupply@xxxxxxxxx> wrote: > I AM NOT A SUBSCRIBER. Please reply to me directly at this e-mail > address j.wholesalesupply@xxxxxxxxx No need to shout -- also common etiquette on Linux kernel lists is to "reply-all" anyway :) > Then I decided to see if it the card was working, So I tried to iwlist > wlan0 scan, it returned the expected results. > I would be glad to offer up as much > information as I can, but I don't have the slightest on how to debug > this issue? So to summarize: 2.6.29 works, 2.6.30 doesn't, ath9k works, ath5k doesn't, userspace setup is unchanged. ath5k can get scan results (which means RX is working at least some of the time) but dhcp does not. You said you are comfortable with the command line, in that case the easiest way to debug the change is to just bisect the ath5k changes using git. There were only 50 or so patches since 2.6.29 so you will likely only need to compile the kernel 5 or 6 times. You can do something like: $ git bisect start v2.6.30 v2.6.29 -- drivers/net/wireless/ath5k > Any help on that issue is much appreciated. Where can I > file the appropriate bug and what information do I need to post from a > technical standpoint. http://bugzilla.kernel.org/ is where you would file it, the information you've already given here is a good start. -- Bob Copeland %% www.bobcopeland.com -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
