This is my 1st ever wiki and I hope that by writing this it can benefit another user out there to setup archlinux on their laptop like me. I should also like to explain that I am a novice in the World of Linux and so I shall try and pass on as much knowledge as I possibly can. These are the settings that apply to my machine and my network setup so you must remember that what works for me will not necessarily work ok for you. This machine is running 2.6.31-ARCH and all the hardware is ok other than having to load the wireless driver iwl4965 and nvidia everything else just worked from the core install.

This is my 1st ever wiki and I hope that by writing this it can benefit another user out there to setup archlinux on their laptop like me. I should also like to explain that I am a novice in the World of Linux and so I shall try and pass on as much knowledge as I possibly can. These are the settings that apply to my machine and my network setup so you must remember that what works for me will not necessarily work ok for you. This machine is running 2.6.31-ARCH and all the hardware is ok other than having to load the wireless driver iwl4965 and nvidia everything else just worked from the core install.

This contains the commands to connect to my Buffalo NAS drive, which I have added incase it helps someone else with one. I connect to the drive which is on a static IP address and has no security set for the shares, so in your case connecting up to your own network shares would of course differ from mine.

Then you need to edit /etc/rc.conf to load the wicd daemon at startup. If you put a bang(!) in front of a network interface then you are allowing wicd to control the interface. The Interfaces and Routes are optional but you will need to load the Daemon. Then after a reboot in the system notification area you should now be able to use the wicd client to hook up to your network.

I have been using [[Compiz]] for effects and [[Emerald]] as my window decorator (minimize, maximise buttons etc) and I have been having an on-going fault where you login to Gnome and the desktop hangs for a couple of seconds before continuing the loading process. Well I also broke my window decorator Emerald over the weekend (24th Oct 2009) with a system update that stopped Compiz loading up the window decorator Emerald.

+

+

Well having googled around the subject a bit and trying the usual ''emerald --replace'' options which had been working until the update I came across and article that fixed it for me.

+

First I decided that I no longer wished to use Emerald as my window decorator and to replace that with ''gtk-window-decorator'' instead.

+

+

So to "fix" this I set the window decorator that starts when you load Gnome back to metacity for when you login, then using a script to load up compiz and the gtk-window-decorator after, which make Gnome load a few seconds faster in my case!

+

+

====Disable Compiz and set Gnome to use Metacity====

+

I ran these commands from a terminal to reset Gnome to use Metacity as the window decorator

To do this I created an empty file in my home folder called ''compiz.sh''

+

Then using right click on the file and choosing "permissions" tab I set the "Allow executing file as program"

+

Now open the file up for editing, I double-clicked on the file and choose the "Display" option which opened the file in Gedit.

+

In the empty script file I added the following code: -

+

compiz --replace ccp & '''gtk-window-decorator''' --replace &

+

exit

+

Note - Change '''gtk-window-decorator''' to '''emerald''' if that is your preffered window decorator

+

+

I saved the file and then you need to add it to the "Startup programs"

+

Go to "System" then "Preferences" then "Startup Applications" and then click "Add"

+

Under name

+

Compiz startup script

+

Under command, where '''mark''' becomes ''your'' username!

+

/home/'''mark'''/compiz.sh

+

Under Comment

+

This script loads Compiz after Gnome loads

+

+

Now when you next logon you should find that your desktop loads faster and your Compiz effects are back to normal.

==Tips & Tricks==

==Tips & Tricks==

Line 348:

Line 182:

mount -a

mount -a

fi

fi

−

Now exit nano by using "ctrl-x" and press "y" to save your changes. Then logout of the terminal as you are still running as root! When you next login to Gnome it will run the script and mount the drives if the NAS box is online.

Now exit nano by using "ctrl-x" and press "y" to save your changes. Then logout of the terminal as you are still running as root! When you next login to Gnome it will run the script and mount the drives if the NAS box is online.

Line 354:

Line 187:

exit

exit

exit

exit

−

...or if running Gnome like me then use gedit as it is much easier on the eye.

...or if running Gnome like me then use gedit as it is much easier on the eye.

Line 404:

Line 236:

=====Install the components=====

=====Install the components=====

First you need to install "acpid"

First you need to install "acpid"

−

{{Command|name=Type this into a console|output=

+

sudo pacman -S acpid

−

sudo pacman -S acpid

−

}}

Then you need to install "cpufrequtils"

Then you need to install "cpufrequtils"

−

{{Command|name=Type this into a console|output=

+

sudo pacman -S cpufrequtils

−

sudo pacman -S cpufrequtils

−

}}

=====Now setup the modules and daemons=====

=====Now setup the modules and daemons=====

We need to load the Modules and Daemons into /etc/rc.conf

We need to load the Modules and Daemons into /etc/rc.conf

−

{{Command|name=Type this into a console|output=

+

sudo nano /etc/rc.conf

−

sudo nano /etc/rc.conf

+

−

}}

In nano makes these changes to rc.conf

In nano makes these changes to rc.conf

−

{{Command|name=Make these changes to the Modules & Daemons section|output=

Now the "harder" one to do is sort out the power events in acpid as they do not work out of the box. The problem is that the power event for plugging in your power adapter is not defined in the script so you need to add the event to the file.

+

To see what I am talking about bring up a terminal and type in this command

+

sudo tail -f /var/log/messages.log

−

Now the "harder" one to do is sort out the power events in acpid as they don't work out of the box. The problem is that the power event for plugging in your power adapter is not defined in the script so you need to add the event to the file.

−

{{Command|name=To see what I am talking about bring up a terminal and type in this command|output=

−

sudo tail -f /var/log/messages.log

−

}}

Now with this terminal open unplug the power adapter or plug it in and you will see this pop up in the log open on the terminal (use ctrl-c to exit log)

Now with this terminal open unplug the power adapter or plug it in and you will see this pop up in the log open on the terminal (use ctrl-c to exit log)

−

{{Command|name=Here is what should pop up|output=

+

Here is what should pop up

−

Oct 22 12:34:27 8920g kernel: Restarting tasks ... done.

+

Oct 22 12:34:27 8920g kernel: Restarting tasks ... done.

−

Oct 22 12:34:27 8920g logger: ACPI action undefined: '''ADP0'''

+

Oct 22 12:34:27 8920g logger: ACPI action undefined: '''ADP0'''

−

Oct 22 12:34:27 8920g acpid: client connected from 3654[0:0]

+

Oct 22 12:34:27 8920g acpid: client connected from 3654[0:0]

−

Oct 22 12:34:27 8920g acpid: 1 client rule loaded

+

Oct 22 12:34:27 8920g acpid: 1 client rule loaded

−

}}

The bold entry is the one we are concerned with, this is what changes when we plug in and remove the power adapter.

The bold entry is the one we are concerned with, this is what changes when we plug in and remove the power adapter.

Now for the interesting part, changing the acpid events to "catch" this change of power adapter.

Now for the interesting part, changing the acpid events to "catch" this change of power adapter.

−

{{Command|name=To make these changes bring up a terminal and type in this command|output=

+

To make these changes bring up a terminal and type in this command

−

su

+

su

−

cd /etc/acpi/events

+

cd /etc/acpi/events

−

chmod +x anything

+

chmod +x anything

−

cd ..

+

cd ..

−

gedit handler.sh

+

gedit handler.sh

−

}}

−

{{Command|name=Now we need to change the bold entries in this file|output=

+

Now we need to change the bold entries in this file

−

#!/bin/sh

+

#!/bin/sh

−

# Default acpi script that takes an entry for all actions

+

# Default acpi script that takes an entry for all actions

−

+

−

# NOTE: This is a 2.6-centric script. If you use 2.4.x, you'll have to

+

# NOTE: This is a 2.6-centric script. If you use 2.4.x, you'll have to

−

# modify it to not use /sys

+

# modify it to not use /sys

−

+

−

minspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq`

+

minspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq`

−

maxspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`

+

maxspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`

−

setspeed="/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed"

+

setspeed="/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed"

−

+

−

set $*

+

set $*

−

+

−

case "$1" in

+

case "$1" in

button/power)

button/power)

#echo "PowerButton pressed!">/dev/tty5

#echo "PowerButton pressed!">/dev/tty5

Line 502:

Line 323:

00000000)

00000000)

'''# So we now change the CPU scaler to ondemand which is nice and responsive'''

'''# So we now change the CPU scaler to ondemand which is nice and responsive'''

Save and exit this file and after a reboot the system will load by default the "ondemand" profile which changes the CPU speed quite nicely I find. If you then plug in the mains for something intensive like a game with graphics or some compiling then the both processor cores will ramp up to full speed and so will the graphics card as we did that earlier. Then when you need to use the laptop on the battery you will find that the clock will drop down to 800MHz from 2,400MHz and the graphics will slow down and conserve power.

Save and exit this file and after a reboot the system will load by default the "ondemand" profile which changes the CPU speed quite nicely I find. If you then plug in the mains for something intensive like a game with graphics or some compiling then the both processor cores will ramp up to full speed and so will the graphics card as we did that earlier. Then when you need to use the laptop on the battery you will find that the clock will drop down to 800MHz from 2,400MHz and the graphics will slow down and conserve power.

Line 553:

Line 373:

=====Verify that it works=====

=====Verify that it works=====

−

If you have installed bluetooth stack and started the daemon as per the wiki instructions available here [http://wiki.archlinux.org/index.php/Bluetooth Bluetooth]

+

If you have installed bluetooth stack and started the daemon as per the wiki instructions available here [https://wiki.archlinux.org/index.php/Bluetooth Bluetooth]

Send a file to a mobile phone using Gnome-Bluetooth utility in the system tray.

Send a file to a mobile phone using Gnome-Bluetooth utility in the system tray.

If that worked out fine then move onto the next step, if not then troubleshoot bluetooth until you do get it working.

If that worked out fine then move onto the next step, if not then troubleshoot bluetooth until you do get it working.

Line 560:

Line 380:

Basically I figured the best way to do this was to use gdm's PostLogin script that I used earlier and add a line to turn off the power to the device.

Basically I figured the best way to do this was to use gdm's PostLogin script that I used earlier and add a line to turn off the power to the device.

−

{{Command|name=To make these change bring up a terminal and type in this command|output=

+

To make this change bring up a terminal and type in this command

−

sudo nano /etc/gdm/PostLogin/Default

+

sudo nano /etc/gdm/PostLogin/Default

−

}}

−

{{Command|name=Then add this line in bold to nano and save the file|output=

−

#!/bin/sh

−

#

−

# Note: this is a sample and will not be run as is. Change the name of this

−

# file to <gdmconfdir>/PostLogin/Default for this script to be run. This

−

# script will be run before any setup is run on behalf of the user and is

−

# useful if you for example need to do some setup to create a home directory

−

# for the user or something like that. $HOME, $LOGIN and such will all be

−

# set appropriately and this script is run as root.

−

+

Then add this line in bold to nano and save the file

−

'''# Now we shall try and powerdown the bluetooth device until we need it'''

+

#!/bin/sh

−

'''echo "0" > /sys/devices/platform/acer-wmi/rfkill/rfkill1/state'''

+

#

−

+

# Note: this is a sample and will not be run as is. Change the name of this

−

+

# file to <gdmconfdir>/PostLogin/Default for this script to be run. This

−

# This ping's the NAS box to see if it is online, and if it is then mount

+

# script will be run before any setup is run on behalf of the user and is

−

# the shares.

+

# useful if you for example need to do some setup to create a home directory

−

# If not then just exit, or the mount command will hang the system for

+

# for the user or something like that. $HOME, $LOGIN and such will all be

−

# about 20~30 seconds which just plain sucks!

+

# set appropriately and this script is run as root.

−

}}

+

+

+

'''# Now we shall try and powerdown the bluetooth device until we need it'''

+

'''echo "0" > /sys/devices/platform/acer-wmi/rfkill/rfkill1/state'''

+

+

+

# This ping's the NAS box to see if it is online, and if it is then mount

+

# the shares.

+

# If not then just exit, or the mount command will hang the system for

+

# about 20~30 seconds which just plain sucks!

Revision as of 00:41, 6 December 2012

This is my 1st ever wiki and I hope that by writing this it can benefit another user out there to setup archlinux on their laptop like me. I should also like to explain that I am a novice in the World of Linux and so I shall try and pass on as much knowledge as I possibly can. These are the settings that apply to my machine and my network setup so you must remember that what works for me will not necessarily work ok for you. This machine is running 2.6.31-ARCH and all the hardware is ok other than having to load the wireless driver iwl4965 and nvidia everything else just worked from the core install.

Troubleshooting

These are some of the things I needed to download and the configuration files that needed modifying in order to configure the machine to behave as a laptop should... be wireless and consume less power!
I assume by this point that you have already got to the stage of a working desktop and just need to dot the i's and cross the t's to polish things off.

Wireless

Nvidia Graphics

I assume by now that you have a working desktop and just need to "tweak" the system for 3-D apps and power management so this is what I changed in my system.

In the /etc/X11/xorg.conf file I made the following changes to allow compiz eye candy and power management. The PowerMizer options are set to lowest performance on battery, with the option of increasing speed if needed and the system will run at full speed when the mains are plugged in.

Window Decorator & Compiz Error

I have been using Compiz for effects and Emerald as my window decorator (minimize, maximise buttons etc) and I have been having an on-going fault where you login to Gnome and the desktop hangs for a couple of seconds before continuing the loading process. Well I also broke my window decorator Emerald over the weekend (24th Oct 2009) with a system update that stopped Compiz loading up the window decorator Emerald.

Well having googled around the subject a bit and trying the usual emerald --replace options which had been working until the update I came across and article that fixed it for me.
First I decided that I no longer wished to use Emerald as my window decorator and to replace that with gtk-window-decorator instead.

So to "fix" this I set the window decorator that starts when you load Gnome back to metacity for when you login, then using a script to load up compiz and the gtk-window-decorator after, which make Gnome load a few seconds faster in my case!

Disable Compiz and set Gnome to use Metacity

I ran these commands from a terminal to reset Gnome to use Metacity as the window decorator

Loading Compiz with gtk-window-decorator

To do this I created an empty file in my home folder called compiz.sh
Then using right click on the file and choosing "permissions" tab I set the "Allow executing file as program"
Now open the file up for editing, I double-clicked on the file and choose the "Display" option which opened the file in Gedit.
In the empty script file I added the following code: -

compiz --replace ccp & gtk-window-decorator --replace &
exit

Note - Change gtk-window-decorator to emerald if that is your preffered window decorator

I saved the file and then you need to add it to the "Startup programs"
Go to "System" then "Preferences" then "Startup Applications" and then click "Add"
Under name

Compiz startup script

Under command, where mark becomes your username!

/home/mark/compiz.sh

Under Comment

This script loads Compiz after Gnome loads

Now when you next logon you should find that your desktop loads faster and your Compiz effects are back to normal.

Tips & Tricks

Here are some of the hacks that I have made to my system in addition to the above.

fstab mounting and offline drives

I found that despite mounting my network drives is fstab and having the wicd daemon loading that the network shares would not connect at startup. I think that fstab mounts drives at an early stage and the wicd daemon has not even loaded yet so they fail and the boot process carries on. So I found a solution where I run a script just after I logon to check to see if the drive is online and to connect if it is. I found that if I tried to mount -a and the NAS box was offline that the mount command would retry to connect a few times and this would cause the system to hang until it is finished. So as you will see from the script it first "pings" the NAS box to see if it is online and only then does it issue the mount -a command, if it is offline then it just exits.

Since I use gdm to logon to Gnome I discovered that it could run scripts at certain defined events via PostLogin, PreSession & PostSession.
So I added this script that I found on the internet whilst googling and changed it a little to suit my needs.

Type this into a console, using su at the start to become root (nano method)

# This ping's the NAS box to see if it is online, and if it is then mount
# the shares.
# If not then just exit, or the mount command will hang the system for
# about 20~30 seconds which just plain sucks!
if [ "$(ping -c 1 192.168.1.2 | grep '0 received')" ]
then
: ; exit 1
else
mount -a
fi

Now exit nano by using "ctrl-x" and press "y" to save your changes. Then logout of the terminal as you are still running as root! When you next login to Gnome it will run the script and mount the drives if the NAS box is online.
Type this into a console

exit
exit

...or if running Gnome like me then use gedit as it is much easier on the eye.
Type this into a console, using su at the start to become root (gedit method)

# This ping's the NAS box to see if it is online, and if it is then mount
# the shares.
# If not then just exit, or the mount command will hang the system for
# about 20~30 seconds which just plain sucks!
if [ "$(ping -c 1 192.168.1.2 | grep '0 received')" ]
then
: ; exit 1
else
mount -a
fi

Now exit gedit and save your changes. Then logout of the terminal as you are still running as root! When you next login to Gnome it will run the script and mount the drives if the NAS box is online.
Type this into a console

exit
exit

Ok, I've mounted my network shares now my laptop hangs on shutdown!

Sadly there is a bit of a bug with Linux which stretches back to it's unix roots: The concept of connecting to network drives was not around it seems and when the shutdown scripts execute it does things in reverse... so basically one of the consequences is that networking goes down before the drives have been un-mounted. This causes the system to hang as it would like to shutdown the shares properly to check to see if files are open etc but it cannot connect.

So to fix this we need to un-mount the drives at some stage before the shutdown script gets rolling. I could have added a script to /etc/gdm/PostSession/Default like above, but it seems silly to un-mount the drives if I just logged out of Gnome and let someone else login to use my laptop. So I found a suitable location that works well is /etc/rc.local.shutdown and added these commands...
Type this into a console

Exit out of nano saving changes and voila! The system now shutdown clean and fast.

Saving Power

This is an ongoing concern for me... I am working on trying to have the display dimmer when on battery and full brightness when on mains adapter. If I get this fixed then it shall appear here. Meanwhile I have so far been able to save some power with the PowerMizer settings for nvidia in xorg.conf file above, but is there more? Well yes!

Cpufreq is our first port of call

We need to install acpi and cpufreq, then configure the system for AC and battery.

Install the components

First you need to install "acpid"

sudo pacman -S acpid

Then you need to install "cpufrequtils"

sudo pacman -S cpufrequtils

Now setup the modules and daemons

We need to load the Modules and Daemons into /etc/rc.conf

sudo nano /etc/rc.conf

In nano makes these changes to rc.conf
Changes the bold entries in the Modules & Daemons section

Now the "harder" one to do is sort out the power events in acpid as they do not work out of the box. The problem is that the power event for plugging in your power adapter is not defined in the script so you need to add the event to the file.
To see what I am talking about bring up a terminal and type in this command

sudo tail -f /var/log/messages.log

Now with this terminal open unplug the power adapter or plug it in and you will see this pop up in the log open on the terminal (use ctrl-c to exit log)
Here is what should pop up

Save and exit this file and after a reboot the system will load by default the "ondemand" profile which changes the CPU speed quite nicely I find. If you then plug in the mains for something intensive like a game with graphics or some compiling then the both processor cores will ramp up to full speed and so will the graphics card as we did that earlier. Then when you need to use the laptop on the battery you will find that the clock will drop down to 800MHz from 2,400MHz and the graphics will slow down and conserve power.

Bluetooth

As we have a hardware switch for bluetooth then we can turn this on only when we need it and this will save battery power and make the system a bit more secure.
Hopefully I won't need to tell you how to install bluetooth, and on my machine I made no changes to the default configuration files.

Verify that it works

If you have installed bluetooth stack and started the daemon as per the wiki instructions available here Bluetooth
Send a file to a mobile phone using Gnome-Bluetooth utility in the system tray.
If that worked out fine then move onto the next step, if not then troubleshoot bluetooth until you do get it working.

Saving power by turning off bluetooth by default when the system is logged into the Desktop

Basically I figured the best way to do this was to use gdm's PostLogin script that I used earlier and add a line to turn off the power to the device.

To make this change bring up a terminal and type in this command

sudo nano /etc/gdm/PostLogin/Default

Then add this line in bold to nano and save the file

#!/bin/sh
#
# Note: this is a sample and will not be run as is. Change the name of this
# file to <gdmconfdir>/PostLogin/Default for this script to be run. This
# script will be run before any setup is run on behalf of the user and is
# useful if you for example need to do some setup to create a home directory
# for the user or something like that. $HOME, $LOGIN and such will all be
# set appropriately and this script is run as root.
# Now we shall try and powerdown the bluetooth device until we need itecho "0" > /sys/devices/platform/acer-wmi/rfkill/rfkill1/state
# This ping's the NAS box to see if it is online, and if it is then mount
# the shares.
# If not then just exit, or the mount command will hang the system for
# about 20~30 seconds which just plain sucks!