lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 10 Nov 2008 11:51:09 -0500
From:	"Bob Copeland" <me@...copeland.com>
To:	"Maxim Levitsky" <maximlevitsky@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org,
	ath5k-devel@...ts.ath5k.org, alsa-devel@...a-project.org
Subject: Re: Bugs on aspire one A150

On Fri, Nov 7, 2008 at 10:26 PM, Maxim Levitsky <maximlevitsky@...il.com> wrote:
> ** 2 - wireless: not to mention the fact that ath5k wasn't installed by
> default in ubuntu...
> wireless more or less works, but kernel log is full of backtraces.

As you've seen, these should at least be gone now...

> Was able to connect to my WPA2 access point.
> Sometimes wireless fails completely, especially after suspend to ram.

Did you get noise calibration failures in dmesg at this point?  Felix posted
a patch recently that handles them better.

> Advanced features like monitor/injection work, but when I changed the card's
> mac address it stopped working.
> I also noticed that if I then start airodump, then wireless works with new
> mac.

> ** 4 - wireless led doesn't work.
> ath5k devs, can you fix this?

Currently all the LED code we have in there is for setting a particular gpio
for particular laptops (and they differ between models).  We only have quirks
for IBM and HP, none for Acer.  Also, the legacy-hal seems to have a different
strategy for 2425 chips.  I can try to hack up some code for you to test.

-- 
Bob Copeland %% www.bobcopeland.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ