![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Things that are annoying me right now:
1) Wireless in Linux. Aaarrrrrgh.
The madwifi driver is supposed to work peachily with my hardware, but in recent months has regressed from 'have to unload and reload module to change ESSIDs' (really!) to 'won't associate to an AP at all'. *plonk*
Okay, so native driver is out. Try ndiswrapper! The actual IBM driver (I have a Thinkpad T40) gets stuck in 802.11a mode frequently and also fails to see wireless networks it's nowhere near.
Try another AR5211 driver? Sure! The Proxim ntpr11ab driver almost (ALMOST!) works...it only gets stuck in 802.11a mode after suspend and resume. Such an improvement! *plonk*
So now I'm restarting NetworkManager and D-BUS and HAL and removing and reloading ndiswrapper every time I come back from suspend. Aaararrgh. Worthless.
2) ACPI suspend and resume on linux
My computer only draws marginally less power in ACPI suspend than it does when it's actively on (and yes, I have the acpi patch). It's a "known issue". "Yay".
Worse, since going to 2.6.10, my clock runs away into the future like an enraged wild horse. Oh, it's okay, it's just another command to add to the list of things I have to manually do after coming back from suspend. I know, I'll just set up software suspend, once I figure out which of the THREE different implementations out there actually comes within some margin of error of working. I'm already applying I forget how many third-party patches to my kernel to make things slightly happier, what harm can another do? *plonk*
Or I could repartition my laptop and set up BIOS S5. Sure sounds like fun.
I want a PowerBook.
1) Wireless in Linux. Aaarrrrrgh.
The madwifi driver is supposed to work peachily with my hardware, but in recent months has regressed from 'have to unload and reload module to change ESSIDs' (really!) to 'won't associate to an AP at all'. *plonk*
Okay, so native driver is out. Try ndiswrapper! The actual IBM driver (I have a Thinkpad T40) gets stuck in 802.11a mode frequently and also fails to see wireless networks it's nowhere near.
Try another AR5211 driver? Sure! The Proxim ntpr11ab driver almost (ALMOST!) works...it only gets stuck in 802.11a mode after suspend and resume. Such an improvement! *plonk*
So now I'm restarting NetworkManager and D-BUS and HAL and removing and reloading ndiswrapper every time I come back from suspend. Aaararrgh. Worthless.
2) ACPI suspend and resume on linux
My computer only draws marginally less power in ACPI suspend than it does when it's actively on (and yes, I have the acpi patch). It's a "known issue". "Yay".
Worse, since going to 2.6.10, my clock runs away into the future like an enraged wild horse. Oh, it's okay, it's just another command to add to the list of things I have to manually do after coming back from suspend. I know, I'll just set up software suspend, once I figure out which of the THREE different implementations out there actually comes within some margin of error of working. I'm already applying I forget how many third-party patches to my kernel to make things slightly happier, what harm can another do? *plonk*
Or I could repartition my laptop and set up BIOS S5. Sure sounds like fun.
I want a PowerBook.
