From: Dmitri Seletski <drjoms@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
gaurav.jauhar@atheros.com,
Senthil Balasubramanian <senthilkumar@atheros.com>
Subject: Re: [ath9k-devel] Pending ath9k bugs June, 2009
Date: Mon, 22 Jun 2009 23:46:30 +0100 [thread overview]
Message-ID: <4A4009C6.8020208@gmail.com> (raw)
In-Reply-To: <43e72e890906221358m4a32d747ge67a5af2f74841e0@mail.gmail.com>
Luis R. Rodriguez wrote:
> On Mon, Jun 22, 2009 at 12:25 PM, Dmitri Seletski<drjoms@gmail.com> wrote:
>
>> Luis R. Rodriguez wrote:
>>
>>> We're down to 2 kernel.org bug reports for ath9k:
>>>
>>> http://bugzilla.kernel.org/show_bug.cgi?id=13581
>>> "ath9k doesn't work with newer kernels"
>>> This is a regression between 2.6.29 and 2.6.30, someone needs to look at this.
>>>
>>> http://bugzilla.kernel.org/show_bug.cgi?id=13141
>>> "AR5008/DWA-552 - Very slow"
>>> Patches have been supplied, needs user feedback.
>>>
>>> If you are aware of any other issues please do report.
>>>
>>> Luis
>>> _______________________________________________
>>> ath9k-devel mailing list
>>> ath9k-devel@lists.ath9k.org
>>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>>
>>>
>> Hello Luis,
>> Was that problem i was bothering you with being solved?
>>
>
> Oh no, thanks for the reminder, that is another outstanding issue. Can
> you provide the pcap output.
>
>
>
>> I have attempted to install fresh drivers, but i get:
>>
>> make
>> /bin/sh: line 0: test: -ge: unary operator expected
>> /bin/sh: line 0: test: -le: unary operator expected
>>
>
> Hm, some script may not be using /bin/bash appropriately, but you may
> just want to rm -f /bin/sh && ln -s /bin/bash /bin/sh for now.
>
> Luis
>
rm -f /bin/sh && ln -s /bin/bash /bin/sh
make
/bin/sh: line 0: test: -ge: unary operator expected
/bin/sh: line 0: test: -le: unary operator expected
make -C /lib/modules/2.6.30-rc8/build
M=/home/dimko/compat-wireless-2009-06-20 modules
make[1]: Entering directory `/usr/src/linux-2.6.30-rc8'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory `/usr/src/linux-2.6.30-rc8'
make: *** [modules] Error 2
Make still fails.
About pcap, you probably din't get my last email. I have included log
files of tcpdump...
I have had no packets going through wireless at all, during n only test.
unfortunately i cant compile anything currently
solution with rm -f /bin/sh && ln -s /bin/bash /bin/sh didnt help
compat-wireless-2009-06-20 # make
/bin/sh: line 0: test: -ge: unary operator expected
/bin/sh: line 0: test: -le: unary operator expected
make -C /lib/modules/2.6.30-rc8/build
M=/home/dimko/compat-wireless-2009-06-20 modules
make[1]: Entering directory `/usr/src/linux-2.6.30-rc8'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory `/usr/src/linux-2.6.30-rc8'
make: *** [modules] Error 2
If you want i can of course can resubmit tcpdump test, but i cant
install no ath9k drivers, as such test is pointless, as i only have
built in drivers left...
Sorry for replying to private email.
just to clarify, by all i mean, i cant compile ath9k drivers.
i could compile kernel for example
Regards
Dmitri
next prev parent reply other threads:[~2009-06-22 22:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 15:47 Pending ath9k bugs June, 2009 Luis R. Rodriguez
2009-06-22 18:50 ` [ath9k-devel] " Joseph Cheek
2009-06-22 23:30 ` Joseph Cheek
2009-06-23 2:38 ` Joseph Cheek
2009-06-23 4:19 ` Senthil Balasubramanian
[not found] ` <4A3FDAC2.7020209@gmail.com>
2009-06-22 20:58 ` Luis R. Rodriguez
2009-06-22 22:46 ` Dmitri Seletski [this message]
2009-06-23 5:28 ` Luis R. Rodriguez
[not found] ` <f3ebadea0906230653m4c95b4a1m8cd52f1336e045ba@mail.gmail.com>
2009-06-23 15:15 ` Luis R. Rodriguez
2009-06-23 20:33 ` Dmitri Seletski
2009-06-23 20:40 ` Luis R. Rodriguez
2009-06-23 20:48 ` Dmitri Seletski
2009-06-23 20:55 ` Luis R. Rodriguez
-- strict thread matches above, loose matches on Subject: below --
2009-06-23 4:20 X Xiao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A4009C6.8020208@gmail.com \
--to=drjoms@gmail.com \
--cc=gaurav.jauhar@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=senthilkumar@atheros.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).