On Sat, 4 Jun 2011 14:56:10 -0400 Camilo Mesias <[email protected]> wrote:
> I have the same hardware and the same fault, I don't think it's faulty > hardware. My tale of woe is reported here too. Ah well, I suppose it's good to know I'm not the only one. More incentive for the bug to be fixed perhaps. I wonder if it's something specific to the UK or Europe. > Currently I'm trying to shoehorn an Intel based wifi card into the > machine but there is a BIOS whitelist in the way. There is a tweaked > BIOS where the whitelist is disabled, but reflashing the BIOS from > Linux is difficult / impossible, it seems. I didn't know they'd crippled the BIOS like that. I won't be buying HP again. > I'm doing this because a > git bisect of the driver since when it worked isn't an attractive > option. No, but I've done it! If you're interested I can look back through my old emails and find the git SHA code. I can't be 100% sure I found the right commit, but I tested the "good" one fairly thoroughly. The commit message said that the changeset introduced support for AR9285. > This is a reproducible problem though, maybe not reported by many > people but very real. Even a simple rmmod will lock up the machine. > Commands like ifconfig X down / iwconfig X tx off / rmmod don't help > either. Same here. At one point I found that I could safely suspend and resume by disconnecting the PSU before rmmod ath9k but that seemed to stop working after a while. It might help to also be on battery power when booting or loading the module though. _______________________________________________ ath9k-devel mailing list [email protected] https://lists.ath9k.org/mailman/listinfo/ath9k-devel
