How To: Asus 1201T (1201N also)

[maestrobwh1]

To get most everything working:

To get the volume Fn Keys working of you have had no success otheriwise:

sudo dpkg-reconfigure grub-pc

and on the second prompt for options, add

acpi_osi=Linux

before "quiet splash"

Reboot.

Wifi was fixed by adding the repo mentioned here

https://launchpad.net/~matt-price/+archive/mattprice

and installing the rtl8192-dkms package.

Apparently Fn F2 does disable the wireless BUT the wifi light stays on. NetworkManager disconnects the connection. I am thinking it is not a power saving feature at this point if the light is still on.

The screen blanking Fn key does not work for me (at least in running KDE) - to fix this

Open the terminal and create a file

sudo nano /etc/acpi/events/asus-screenblank

and then paste this

# /etc/acpi/events/asus-screenblank
# This is called when the user presses the screenblank key.
event=hotkey (ATKD|HOTK) 00000016
action=/etc/acpi/screenblank.sh

I had suspend issues from time to time... and seemingly it was related to network-manager that for some reason tries to suspend but does so too late or early in the game and it was never consistent so I was having weird issues with KDE suspending properly along with other odd network issues when the desktop would launch (late connection so my weather plasma widget would not get a connection initially).

EDIT: still had suspend issues. I added this script to /etc/pm/sleep.d called 97quirks

 #!/bin/sh

# let other scripts catch up

case $1 in
  suspend|hibernate) 
    sleep 5 ;;
  resume|thaw)    
    ;;
  *) exit $NA ;;
esac
exit 0

Then reboot or at the command line

sudo /etc/init.d/acpid restart

I still find that the wireless driver is not terribly reliable under wicd either. If you get hung conections with it going down oddly and not finding any wireless signals

sudo rmmod r8192se_pci 
sudo modprobe r8192se_pci

...and then it works well again:-)

Annoying that the native driver does not work and we have to install a ppa to get it working. I suspect that if the kernel driver actually worked, this would not be an issue.