https://wiki.archlinux.org/api.php?action=feedcontributions&user=Bladesonfire&feedformat=atomArchWiki - User contributions [en]2024-03-29T02:06:01ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=PulseAudio/Examples&diff=555437PulseAudio/Examples2018-11-17T02:49:16Z<p>Bladesonfire: /* HDMI output configuration */ Update link to use https</p>
<hr />
<div>[[Category:Sound]]<br />
[[it:PulseAudio/Examples]]<br />
[[ja:PulseAudio/サンプル]]<br />
[[ru:PulseAudio/Examples]]<br />
{{Related articles start}}<br />
{{Related|PulseAudio}}<br />
{{Related|PulseAudio/Troubleshooting}}<br />
{{Related articles end}}<br />
== Set default input source ==<br />
<br />
List available input sources<br />
{{hc|$ pacmd list-sources {{!}} grep -e 'index:' -e device.string -e 'name:'|2=<br />
'' ''index: 0<br />
name: <input><br />
device.string = "hw:2"<br />
* index: 1<br />
name: <oss_input.dsp><br />
device.string = "/dev/dsp"<br />
index: 2<br />
name: <alsa_output.pci-0000_04_01.0.analog-stereo.monitor><br />
}}<br />
<br />
The {{ic|*}} in front of the index indicates the current default input.<br />
<br />
To set a system wide default, add the source name in the {{ic|default.pa}} file:<br />
{{hc|/etc/pulse/default.pa|...<br />
set-default-source ''alsa_output.pci-0000_04_01.0.analog-stereo.monitor''<br />
...}}<br />
<br />
For temporary use<br />
$ pacmd "set-default-source alsa_output.pci-0000_04_01.0.analog-stereo.monitor"<br />
<br />
{{Tip|The default source can be referred as {{ic|@DEFAULT_SOURCE@}} in commands, for example: {{ic|$ pactl set-source-mute @DEFAULT_SOURCE@ toggle}}.}}<br />
<br />
== Set the default output source ==<br />
<br />
To list the output sources available, type the following command:<br />
{{hc|$ pacmd list-sinks {{!}} grep -e 'name:' -e 'index:'|<br />
* index: 0<br />
name: <alsa_output.pci-0000_04_01.0.analog-stereo><br />
index: 1<br />
name: <combined>}}<br />
<br />
The {{ic|*}} in front of the index indicates the current default output.<br />
<br />
To set a system wide default, add the source name in the {{ic|default.pa}} file:<br />
{{hc|/etc/pulse/default.pa|...<br />
set-default-sink ''alsa_output.pci-0000_04_01.0.analog-stereo''<br />
...}}<br />
<br />
When done then you can logout/login or restart PulseAudio manually for these changes to take effect.<br />
<br />
{{Note|1=<nowiki></nowiki><br />
* The numbering of sinks is not guaranteed to be persistent, so all sinks in the {{ic|default.pa}} file should be identified by the name.<br />
* For quick identification at runtime (e.g. to manage sound volume), you can use the sink index instead of the sink name: {{bc|<nowiki><br />
$ pactl set-sink-volume 0 +3%<br />
$ pactl set-sink-volume 0 -3%<br />
$ pactl set-sink-mute 0 toggle<br />
</nowiki>}}<br />
* To avoid unnecessary overriding of 100% normal volume it is better to use alternative utilities for managing of sound. See the [https://bbs.archlinux.org/viewtopic.php?id=124513 forum thread] for more information.}}<br />
<br />
{{Tip|The default sink can be referred as {{ic|@DEFAULT_SINK@}} in commands, for example: {{ic|$ pactl set-sink-volume @DEFAULT_SINK@ +5%}}.}}<br />
<br />
== Simultaneous HDMI and analog output ==<br />
PulseAudio allows for simultaneous output to multiple sources. In this example, some applications are configured to use HDMI while others are configured to use analog. Multiple applications are able to receive audio at the same time.<br />
{{bc|$ aplay -l<br />
**** List of PLAYBACK Hardware Devices ****<br />
card 0: Intel [HDA Intel], device 0: ALC889A Analog [ALC889A Analog]<br />
Subdevices: 0/1<br />
Subdevice #0: subdevice #0<br />
card 0: Intel [HDA Intel], device 1: ALC889A Digital [ALC889A Digital]<br />
Subdevices: 1/1<br />
Subdevice #0: subdevice #0<br />
card 0: Intel [HDA Intel], device 3: HDMI 0 [HDMI 0]<br />
Subdevices: 0/1<br />
Subdevice #0: subdevice #0}}<br />
<br />
Or by using the the {{ic|pacmd}} command: <br />
<br />
{{hc|<nowiki>$ pacmd list-sinks | grep -e 'name:' -e 'alsa.device ' -e 'alsa.subdevice '</nowiki>|<nowiki><br />
name: <alsa_output.pci-0000_00_1b.0.analog-stereo><br />
alsa.subdevice = "0"<br />
alsa.device = "0"</nowiki>}}<br />
<br />
The key to a configuration like this is to understand that whatever is selected in pavucontrol under ''Configuration > Internal Audio'' is the default device. Load ''pavucontrol > Configuration'' and select HDMI as the profile. <br />
<br />
To setup the analog device as a secondary source, add the following to the {{ic|/etc/pulse/default.pa}} configuration at the beginning, before any other modules are loaded: <br />
<br />
### Load analog device<br />
load-module module-alsa-sink device=hw:0,0<br />
load-module module-combine-sink sink_name=combined<br />
set-default-sink combined<br />
<br />
Restart PulseAudio, run ''pavucontrol'' and select the "Output Devices" tab. Three settings should be displayed:<br />
# Internal Audio Digital Stereo (HDMI)<br />
# Internal Audio<br />
# Simultaneous output to Internal Audio Digital Stereo (HDMI), Internal Audio<br />
<br />
Now start a program that will use PulseAudio such as MPlayer, VLC, mpd, etc. and switch to the "Playback" tab. A drop-down list should be available for the running program to select one of the three sources.<br />
<br />
Also see [https://bbs.archlinux.org/viewtopic.php?id=118026 this thread] for a variation on this theme and [http://www.freedesktop.org/wiki/Software/PulseAudio/FAQ#Can_I_use_PulseAudio_to_playback_music_on_two_sound_cards_simultaneously.3F PulseAudio FAQ].<br />
<br />
==HDMI output configuration==<br />
As outlined in https://download.nvidia.com/XFree86/gpu-hdmi-audio-document/index.html#_issues_in_pulseaudio unless the HDMI port is the first<br />
output, PulseAudio will not be able to have any audio when using certain graphics cards with HDMI audio support. This is because of a bug in PulseAudio where it will only select the first HDMI output on a device. A work around posted further down is to first find which HDMI output is working by using the aplay utility from ALSA.<br />
<br />
The original title for this section indicated the problem is specific to nVidia cards. As seen in [https://bbs.archlinux.org/viewtopic.php?id=133222 this forum thread] other cards are affected as well. The rest of the section will use an nVidia card as a case-study but the solution should carry over for people using other affected cards.<br />
<br />
===Finding HDMI output===<br />
Then find the working output by listing the available cards<br />
# aplay -l<br />
<br />
sample output:<br />
**** List of PLAYBACK Hardware Devices ****<br />
card 0: NVidia [HDA NVidia], device 0: ALC1200 Analog [ALC1200 Analog]<br />
Subdevices: 1/1<br />
Subdevice #0: subdevice #0<br />
card 0: NVidia [HDA NVidia], device 3: ALC1200 Digital [ALC1200 Digital]<br />
Subdevices: 1/1<br />
Subdevice #0: subdevice #0<br />
card 1: NVidia_1 [HDA NVidia], device 3: HDMI 0 [HDMI 0]<br />
Subdevices: 1/1<br />
Subdevice #0: subdevice #0<br />
card 1: NVidia_1 [HDA NVidia], device 7: HDMI 0 [HDMI 0]<br />
Subdevices: 0/1<br />
Subdevice #0: subdevice #0<br />
card 1: NVidia_1 [HDA NVidia], device 8: HDMI 0 [HDMI 0]<br />
Subdevices: 1/1<br />
Subdevice #0: subdevice #0<br />
card 1: NVidia_1 [HDA NVidia], device 9: HDMI 0 [HDMI 0]<br />
Subdevices: 1/1<br />
Subdevice #0: subdevice #0<br />
<br />
In case your HDMI port is wired to the NVIDIA card, but aplay does not detect an NVIDIA audio card, follow [[NVIDIA/Troubleshooting#No audio over HDMI]].<br />
<br />
===Testing for the correct card===<br />
Now a list of the detected cards is known, users will need to test for which one is outputting to the TV/monitor<br />
# aplay -D plughw:1,3 /usr/share/sounds/alsa/Front_Right.wav<br />
<br />
where 1 is the card and 3 is the device substitute in the values listed from the previous section. If there is no audio, then try substituting a different device (on my card I had to use card 1 device 7)<br />
<br />
===Manually configuring PulseAudio to detect the Nvidia HDMI===<br />
Having identified which HDMI device is working, PulseAudio can be forced to use it via an edit to {{ic|/etc/pulse/default.pa}}:<br />
# load-module module-alsa-sink device=hw:1,7<br />
<br />
where the 1 is the card and the 7 is the device found to work in the previous section<br />
<br />
restart pulse audio<br />
$ pulseaudio -k<br />
$ pulseaudio --start<br />
<br />
open the sound settings manager, make sure that under the hardware tab the graphics cards HDMI audio is set to "Digital Stereo (HDMI) Output" (My graphics card audio is called "GF100 High Definition Audio Controller").<br />
<br />
Then, open the output tab. There should now be two HDMI outputs for the graphics card. Test which one works by selecting one of them, and then using a program to play audio. For example, use VLC to play a movie, and if it does not work, then select the other.<br />
<br />
=== Automatically switch audio to HDMI ===<br />
<br />
{{Accuracy|Can't udev rule directly run a script?|Talk:PulseAudio/Examples#Can't udev rule directly run a script?}}<br />
Create a script to switch to the desired audio profile if an HDMI cable is plugged in:<br />
<br />
{{hc|/usr/local/bin/hdmi_sound_toggle.sh|2=<nowiki><br />
#!/bin/bash<br />
<br />
USER_NAME=$(who | awk -v vt=tty$(fgconsole) '$0 ~ vt {print $1}')<br />
USER_ID=$(id -u "$USER_NAME")<br />
CARD_PATH="/sys/class/drm/card0/"<br />
AUDIO_OUTPUT="analog-surround-40"<br />
PULSE_SERVER="unix:/run/user/"$USER_ID"/pulse/native"<br />
<br />
for OUTPUT in $(cd "$CARD_PATH" && echo card*); do<br />
OUT_STATUS=$(<"$CARD_PATH"/"$OUTPUT"/status)<br />
if [[ $OUT_STATUS == connected ]]<br />
then<br />
echo $OUTPUT connected<br />
case "$OUTPUT" in<br />
"card0-HDMI-A-1")<br />
AUDIO_OUTPUT="hdmi-stereo" # Digital Stereo (HDMI 1)<br />
;;<br />
"card0-HDMI-A-2")<br />
AUDIO_OUTPUT="hdmi-stereo-extra1" # Digital Stereo (HDMI 2)<br />
;;<br />
esac<br />
fi<br />
done<br />
echo selecting output $AUDIO_OUTPUT<br />
sudo -u "$USER_NAME" pactl --server "$PULSE_SERVER" set-card-profile 0 output:$AUDIO_OUTPUT+input:analog-stereo<br />
</nowiki>}}<br />
<br />
Make the script executable:<br />
<br />
chmod +x /usr/local/bin/hdmi_sound_toggle.sh<br />
<br />
Create a [[udev]] rule to run this script when the status of the HDMI change:<br />
{{Note|udev rule can't directly run a script, a workaround is to use a .service to run this script}}<br />
<br />
{{hc|/etc/udev/rules.d/99-hdmi_sound.rules|2=<br />
KERNEL=="card0", SUBSYSTEM=="drm", ACTION=="change", RUN+="/usr/bin/systemctl start hdmi_sound_toggle.service"<br />
}}<br />
<br />
Finally, create the .service file required by the udev rule above:<br />
{{hc|/etc/systemd/system/hdmi_sound_toggle.service|2=<br />
[Unit]<br />
Description=hdmi sound hotplug<br />
<br />
[Service]<br />
Type=simple<br />
RemainAfterExit=no<br />
ExecStart=/usr/local/bin/hdmi_sound_toggle.sh<br />
<br />
[Install]<br />
WantedBy=multi-user.target<br />
}}<br />
<br />
To make the change effective don't forget to reload the udev rules:<br />
udevadm control --reload-rules<br />
<br />
You'll also need to reload the systemd units.<br />
systemctl daemon-reload<br />
<br />
A reboot might be required.<br />
<br />
==Surround sound systems==<br />
Many people have a surround sound card, but have speakers for just two channels, so PulseAudio cannot really default to a surround sound setup. To enable all of the channels, edit {{ic|/etc/pulse/daemon.conf}}: uncomment the default-sample-channels line (i.e. remove the semicolon from the beginning of the line) and set the value to '''6'''. For a ''5.1'' setup, or '''8''' for a ''7.1'' setup etc.<br />
# Default<br />
default-sample-channels=2<br />
# For 5.1<br />
default-sample-channels=6<br />
# For 7.1<br />
default-sample-channels=8<br />
<br />
If your channels are not correclty mapped or the volume controls for the individual channels do not work as expected in pavucontrol, and you have a HDMI and an analog soundcard, then try to add the following line to {{ic|/etc/pulse/default.pa}}<br />
<br />
load-module module-combine channels=6 channel_map=front-left,front-right,rear-left,rear-right,front-center,lfe<br />
<br />
Note that this example is for a 5.1 setup.<br />
<br />
After doing the edit, restart PulseAudio.<br />
<br />
=== Splitting front/rear ===<br />
<br />
Connect speakers to front analog output and headphones to rear output. It would be useful to split front/rear to separate sinks. Add to {{ic|/etc/pulse/default.pa}}:<br />
<br />
load-module module-remap-sink sink_name=speakers sink_properties="device.description='Speakers'" remix=no master=alsa_output.pci-0000_05_00.0.analog-surround-40 channels=2 master_channel_map=front-left,front-right channel_map=front-left,front-right<br />
load-module module-remap-sink sink_name=headphones sink_properties="device.description='Headphones'" remix=no master=alsa_output.pci-0000_05_00.0.analog-surround-40 channels=2 master_channel_map=rear-left,rear-right channel_map=front-left,front-right<br />
Make sure to replace alsa_output.pci-0000_05_00.0.analog-surround-40 with the sound card name shown in 'pacmd list-sinks'.<br />
Now you have 2 additional sinks which can be used separately. You can choose 'sink_name' freely, as long as there is no sink with that name already. The 'remix' parameter controls whether the audio should be down-/upmixed to match the channels in the sink.<br />
<br />
{{Tip|If pulseaudio fails with {{ic|master sink not found}}, comment out the remapping lines, start PulseAudio and verify your card output is set to the one you specified (e.g. analog surround 4.0). Alternatively, try using a [[#Set the default output source|sink index]] instead of a sink name.}}<br />
<br />
===Splitting 7.1 into 5.1+2.0===<br />
<br />
Similar to the example above, you can also split a 7.1 configuration into 5.1 surround and stereo output devices.<br />
Set your card to 7.1 mode, then add the following lines to {{ic|/etc/pulse/default.pa}}:<br />
load-module module-remap-sink sink_name=Surround sink_properties="device.description='Surround'" remix=no master=alsa_output.pci-0000_00_14.2.analog-surround-71 channels=6 master_channel_map=front-left,front-right,rear-left,rear-right,front-center,lfe channel_map=front-left,front-right,rear-left,rear-right,front-center,lfe<br />
load-module module-remap-sink sink_name=Stereo sink_properties="device.description='Stereo'" remix=no master=alsa_output.pci-0000_00_14.2.analog-surround-71 channels=2 master_channel_map=side-left,side-right channel_map=front-left,front-right<br />
<br />
Make sure to replace alsa_output.pci-0000_00_14.2 with your sound card name, get it by running 'pacmd list-sinks'.<br />
This configuration will use the front/rear/center+lfe (green/black/orange) jacks for the 5.1 sink and the side (grey) jack for the stereo sink.<br />
It will also downmix any audio to stereo for the stereo sink, but will not touch the 5.1 output.<br />
<br />
{{Tip|If pulseaudio fails with {{ic|master sink not found}}, comment out the remapping lines, start PulseAudio and verify your card output is set to analog surround 7.1. Alternatively, try using a [[#Set the default output source|sink index]] instead of a sink name.}}<br />
<br />
===Disabling LFE remixing===<br />
By default, PulseAudio remixes the number of channels to the default-sample-channels and since version 7 it also remixes the LFE channel. If you wish to disable LFE remixing, uncomment the line:<br />
<br />
; enable-lfe-remixing = yes<br />
<br />
and replace yes with no:<br />
<br />
enable-lfe-remixing = no<br />
<br />
then restart Pulseaudio.<br />
<br />
===Binaural Headphones===<br />
{{AUR|ladspa-bs2b}} provides a plugin to simulate surround sound on stereo headphones. To use it, find your headphones with:<br />
{{hc|<nowiki>$ pacmd list-sinks | grep -e 'name:'</nowiki>|<br />
name: <alsa_output.pci-0000_00_1b.0.iec958-ac3-surround-51><br />
name: <alsa_output.pci-0000_00_1b.0.iec958-ac3-surround-51.equalizer><br />
name: <bluez_sink.00_1F_82_28_93_51><br />
}}<br />
Load the plugin (''new'' sink_name is up to you, master=''headphone's sink name''):<br />
pacmd load-module module-ladspa-sink sink_name=binaural master=bluez_sink.00_1F_82_28_93_51 plugin=bs2b label=bs2b control=700,4.5<br />
Use {{Pkg|pavucontrol}} to transfer streams to the new sink, or:<br />
pactl move-sink-input $INPUTID $BINAURALSINKNAME<br />
<br />
==PulseAudio over network==<br />
One of PulseAudio's unique features is its ability to stream audio from clients over TCP to a server running the PulseAudio daemon reliably within a LAN. Ensure that client and server systems agree on the time (e.g. use NTP), or audio streams may be choppy or may not work at all.<br />
<br />
===TCP support (networked sound)===<br />
You need to enable the TCP module, on the server edit {{ic|/etc/pulse/default.pa}} to add or uncomment:<br />
load-module module-native-protocol-tcp<br />
<br />
For this to work, it is a requirement that both the client and server share the same cookie. Ensure that the clients and server share the same cookie file found under {{ic|~/.config/pulse/cookie}}. It does not matter whose cookie file you use (the server or a client's), just that the server and client(s) share the same one.<br />
<br />
Note: If experiencing trouble connecting, use (on server)<br />
pacmd list-modules<br />
<br />
===TCP support with anonymous clients===<br />
If it is undesirable to copy the cookie file from clients, anonymous clients can access the server by giving these parameters to module-native-protocol-tcp on the server (again in {{ic|/etc/pulse/default.pa}}):<br />
<br />
load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1;192.168.0.0/24 auth-anonymous=1<br />
<br />
Change the LAN IP subnet to match that of those clients you wish to have access to the server.<br />
<br />
===Zeroconf (Avahi) publishing===<br />
For the remote PulseAudio server to appear in the PulseAudio Device Chooser ({{ic|pasystray}}), load the appropriate zeroconf modules, and enable the [[Avahi]] [[daemon]]. On both machines, the client and server, [[install]] {{Pkg|pulseaudio-zeroconf}} then [[start]] and [[enable]] {{ic|avahi-daemon.service}}.<br />
<br />
On the server, add {{ic|load-module module-zeroconf-publish}} to {{ic|/etc/pulse/default.pa}}. <br />
On the client, add {{ic|load-module module-zeroconf-discover}} to {{ic|/etc/pulse/default.pa}}. Now redirect any stream or complete audio output to the remote PulseAudio server by selecting the appropriate sink.<br />
<br />
If you have issues with the remote syncs appearing on the client, try restarting the Avahi daemon on the server to rebroadcast the available interfaces.<br />
<br />
===Selecting the Server===<br />
Run the graphical PulseAudio Volume Control {{ic|pavucontrol}}. Under the '''Output Devices''' tab, you should see the local and remote output devices. Under the '''Playback''' tab, to the left of the "X" Mute Audio button, you should see a box containing the name of an output device. That box is ''actually a button'', which will display a drop-down radio-button list of the available output devices, with one output device selected. Selecting an output device from the list will allow the audio stream to be switched to the PulseAudio server associated with that output device. This control is not at all obvious until you have used it, and is especially useful with a remote Headless sound server.<br />
<br />
Similarly, under the '''Input Devices''' tab, local and remote input devices will be seen. And under the '''Recording''' tab, there will be a box, to the left of the "X" Mute Audio button, with the name of an input device which is actually a button which will display a drop-down radio-button list of available input devices.<br />
<br />
Run {{ic|pavucontrol}} on the local or remote host associated with the audio stream to be directed. For instance, run {{ic|pavucontrol}} on the remote host to direct the remote audio output to the local host. Run {{ic|pavucontrol}} on the local host to direct the local audio output to some remote host.<br />
<br />
Setting up simultaneous inputs or outputs is a different thing. Search about "monitor" and "module-combine-sink" for that.<br />
===Switching the PulseAudio server used by local X clients===<br />
To switch between servers on the client from within X, the {{ic|pax11publish}} command can be used. For example, to switch from the default server to the server at hostname foo:<br />
$ pax11publish -e -S foo<br />
<br />
Or to switch back to the default:<br />
$ pax11publish -e -r<br />
<br />
Instead of telling the PulseAudio server to stream audio (as described above), this will edit PulseAudio variables on the X11 root window, which will instruct the PulseAudio client libraries to connect to a PulseAudio server other than {{ic|localhost}}. As such, the programs will no longer interact with the local {{ic|pulseaudio}} process, which can then be [[stop]]ped. Programs such as {{ic|pactl}}, {{ic|pacmd}} or {{ic|pavucontrol}} will need to also run with the appropriate {{ic|PULSE_SERVER}} environment/X variable to control the remote PulseAudio server.<br />
<br />
Note that for the switch to become apparent, the programs using Pulse must be restarted, or their PulseAudio client library otherwise reinitialized (completely stopping and restarting playback may be enough). To make this setting permanent, edit {{ic|default-server}} in {{ic|~/.config/pulse/client.conf}} or {{ic|/etc/pulse/client.conf}}.<br />
<br />
===When everything else seems to fail===<br />
The following is a quick fix and NOT a permanent solution<br />
<br />
On the server:<br />
$ paprefs <br />
Go to Network Access -> Enable access to local sound devices (Also check both 'Allow discover' and 'Don't require authentication').<br />
<br />
On the client:<br />
$ export PULSE_SERVER=server.ip && mplayer test.mp3<br />
<br />
==ALSA monitor source==<br />
To be able to record from a monitor source (a.k.a. "What-U-Hear", "Stereo Mix"), use {{ic|pactl list}} to find out the name of the source in PulseAudio (e.g. {{ic|alsa_output.pci-0000_00_1b.0.analog-stereo.monitor}}). Then add lines like the following to {{ic|/etc/asound.conf}} or {{ic|~/.asoundrc}}:<br />
pcm.pulse_monitor {<br />
type pulse<br />
device alsa_output.pci-0000_00_1b.0.analog-stereo.monitor<br />
}<br />
<br />
ctl.pulse_monitor {<br />
type pulse<br />
device alsa_output.pci-0000_00_1b.0.analog-stereo.monitor<br />
}<br />
<br />
Now you can select {{ic|pulse_monitor}} as a recording source.<br />
<br />
Alternatively, you can use pavucontrol to do this: make sure you have set up the display to "All input devices", then select "Monitor of [your sound card]" as the recording source.<br />
<br />
== Monitor specific output ==<br />
<br />
It is possible to monitor a specific output, for example to stream audio from a music player into a VOIP application.<br />
Simply create a null output device:<br />
<br />
pactl load-module module-null-sink sink_name=<name><br />
<br />
In Pulseaudio Volume Control (pavucontrol), under the "Playback" tab, change the output of an application to <name>, and in the recording tab change the input of an application to "Monitor of <name>". Audio will now be outputted from one application into the other.<br />
<br />
==PulseAudio through JACK==<br />
The [[JACK Audio Connection Kit]] is popular for audio work, and is widely supported by Linux audio applications. It fills a similar niche as PulseAudio, but with more of an emphasis on professional audio work. It can offer lower latency audio monitoring along with greater control of input and output of multi-i/o sound devices.<br />
<br />
===The KXStudio method===<br />
This is the recommended method as it is [https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_PulseOnJack officially endorsed by the JACK developers].<br />
<br />
This configuration works with both {{Pkg|jack2-dbus}} and {{Pkg|jack2}} packages.<br />
<br />
JACK now has native features for bridging between ALSA, PulseAudio, and JACK. This will allow you to simultaneously have JACK and PulseAudio running with both outputting at the same time, with no config editing or terminal commands requried.<br />
<br />
If you are using {{Pkg|qjackctl}}, it is recommended to uninstall it before beginning this.<br />
<br />
Begin by installing {{Pkg|cadence}}, as well as {{Pkg|pulseaudio-jack}}. Once installed and started, JACK bridge configuration is found in the bottom right of the window. The ALSA audio bridge should be set to ALSA -> PulseAudio -> JACK, and the PulseAudio bridge should be enabled. Make sure in {{ic|pavucontrol}} that all output devices besides Jack sink are muted, and all input devices besides Jack input are muted. Start JACK using the Force Restart button, and if it starts successfully PulseAudio programs should begin outputting to JACK.<br />
<br />
===The manual sink configuration method===<br />
This configuration provides a method of allowing JACK and PulseAudio to run at the same time and output to each other. It uses manual configuration of the systems that bridge between JACK and PulseAudio. This configuration has no reliance on scripts or commands and is entirely based in configuration.<br />
<br />
This configuration only works with jackdbus (JACK2 compiled with D-Bus support). It also requires the {{Pkg|pulseaudio-jack}} package. Make sure that {{ic|/etc/pulse/default.pa}} contains a line:<br />
load-module module-jackdbus-detect ''options''<br />
Where {{ic|''options''}} can be any options supported by this module, usually {{ic|1=channels=2}}.<br />
<br />
As described on the [https://github.com/jackaudio/jackaudio.github.com/wiki/JackDbusPackaging Jack-DBUS Packaging] page:<br />
<br />
''Server auto-launching is implemented as D-Bus call that auto-activates JACK D-Bus service, in case it is not already started, and starts the JACK server. Correct interaction with PulseAudio is done using a D-Bus based audio card "acquire/release" mechanism. When JACK server starts, it asks this D-Bus service to acquire the audio card and PulseAudio will unconditionally release it. When JACK server stops, it releases the audio card that can be grabbed again by PulseAudio.''<br />
<br />
{{ic|module-jackdbus-detect.so}} dynamically loads and unloads module-jack-sink and module-jack-source when jackdbus is started and stopped.<br />
<br />
If PulseAudio sound does not work, check with {{ic|pavucontrol}} to see if the relevant programs appear in the playback tab. If not, add the following to {{ic|~/.asoundrc}} or {{ic|/etc/asound.conf}} to redirect ALSA to PulseAudio:<br />
<br />
pcm.pulse {<br />
type pulse<br />
}<br />
<br />
ctl.pulse {<br />
type pulse<br />
}<br />
<br />
pcm.!default {<br />
type pulse<br />
}<br />
ctl.!default {<br />
type pulse<br />
}<br />
<br />
If it still does not work, check with {{ic|pavucontrol}} in the playback tab and make sure the relevant programs are outputting to PulseAudio JACK Sink instead of your audio card (which JACK has control of, so it will not work). Also ensure that in the JACK graph the PulseAudio JACK Source is connected to the system audio output.<br />
<br />
===The shell script method===<br />
This method allows JACK and PulseAudio to output at the same time. It mostly relies on shell scripts that are automatically run by QJackCTL to manage aspects of how the JACK sinks and PulseAudio behave.<br />
<br />
The basic idea is that killing PulseAudio is a bad idea because it may crash any apps using PulseAudio and disrupt any audio playing.<br />
<br />
The flow of how this setup works:<br />
<br />
# PulseAudio releases the sound card<br />
# JACK grabs sound card and starts up<br />
# script redirects PulseAudio to JACK<br />
# manually send PulseAudio apps to JACK output (pavucontrol may come in helpful for this)<br />
# use JACK programs etc<br />
# via script, stop redirecting PulseAudio to JACK<br />
# stop JACK and release sound card<br />
# PulseAudio grabs sound card and reroutes audio to it directly<br />
<br />
With QJackCTL, set up these scripts:<br />
<br />
{{ic|pulse-jack-pre-start.sh}} set it up as the execute script on startup script<br />
#!/bin/bash<br />
pacmd suspend true<br />
<br />
{{ic|pulse-jack-post-start.sh}} set this one up as execute script after startup<br />
#!/bin/bash<br />
pactl load-module module-jack-sink channels=2<br />
pactl load-module module-jack-source channels=2<br />
pacmd set-default-sink jack_out<br />
pacmd set-default-source jack_in<br />
<br />
{{ic|pulse-jack-pre-stop.sh}} "execute script on shutdown"<br />
#!/bin/bash<br />
SINKID=$(pactl list | grep -B 1 "Name: module-jack-sink" | grep Module | sed 's/[^0-9]//g')<br />
SOURCEID=$(pactl list | grep -B 1 "Name: module-jack-source" | grep Module | sed 's/[^0-9]//g')<br />
pactl unload-module $SINKID<br />
pactl unload-module $SOURCEID<br />
sleep 5<br />
<br />
{{ic|pulse-jack-post-stop.sh}} "execute script after shutdown"<br />
#!/bin/bash<br />
pacmd suspend false<br />
<br />
===The PulseAudio kill method=== <br />
This method relies on shell scripts to automatically kill PulseAudio when JACK is started, and automatically restart it when JACK is stopped. This will result in lower CPU usage than having both running, but can cause errors in already running PulseAudio application and does not allow simultaneous output of both.<br />
<br />
Using the settings listed above, use QjackCtl to execute a script upon startup and shutdown to load/unload PulseAudio. Part of the reason users may wish to do this is that the above changes disable PulseAudio's automatic hardware detection modules. This particular setup is for using PulseAudio in an exclusive fashion with JACK, though the scripts could be modified to unload and load an alternate non-JACK setup, but killing and starting PulseAudio while programs might be using it would become problematic.<br />
<br />
{{Note|padevchooser in the following example is deprecated. It is replaced by pasystray}}<br />
<br />
The following example could be used and modified as necessary as a startup script that daemonizes PulseAudio and loads the ''padevchooser'' program (optional, needs to be built from AUR) called {{ic|jack_startup}}: <br />
#!/bin/bash <br />
#Load PulseAudio and PulseAudio Device Chooser<br />
pulseaudio -D<br />
padevchooser&<br />
<br />
as well as a shutdown script to kill PulseAudio and the Pulse Audio Device Chooser, as another example called {{ic|jack_shutdown}} also in the home directory: <br />
#!/bin/bash <br />
#Kill PulseAudio and PulseAudio Device Chooser <br />
pulseaudio --kill <br />
killall padevchooser <br />
<br />
Both scripts need to be made executable: <br />
chmod +x jack_startup jack_shutdown<br />
<br />
then with QjackCtl loaded, click on the ''Setup'' button and then the ''Options'' tab and tick both "Execute Script after Startup:" And "Execute Script on Shutdown:" and put either use the ... button or type the path to the scripts (assuming the scripts are in the home directory) {{ic|~/jack_startup}} and {{ic|~/jack_shutdown}} making sure to save the changes.<br />
<br />
==PulseAudio through OSS==<br />
Add the following to {{ic|/etc/pulse/default.pa}}:<br />
load-module module-oss<br />
<br />
Then start PulseAudio as usual, making sure that sinks and sources are defined for OSS devices.<br />
<br />
==PulseAudio from within a chroot ==<br />
Since a chroot sets up an alternative root for the running/jailing of applications, PulseAudio must be installed within the chroot itself ({{ic|pacman -S pulseaudio}} within the chroot environment).<br />
<br />
PulseAudio, if not set up to connect to any specific server (this can be done in {{ic|/etc/pulse/client.conf}}, through the PULSE_SERVER environment variable, or through publishing to the local X11 properties using module-x11-publish), will attempt to connect to the local pulse server, failing which it will spawn a new pulse server. Each pulse server has a unique ID based on the machine-id value in {{ic|/var/lib/dbus}}. To allow for chrooted apps to access the pulse server, the following directories must be mounted within the chroot:-<br />
/run<br />
/var/lib/dbus<br />
/tmp<br />
~/config/.pulse<br />
<br />
{{ic|/dev/shm}} should also be mounted for efficiency and good performance. Note that mounting /home would normally also allow sharing of the {{ic|~/.pulse}} folder.<br />
<br />
PulseAudio selects the path to the socket via XDG_RUNTIME_DIR, so be sure to drag it along when you chroot as a normal user using [[sudo]] (see [[Sudo#Environment variables]]).<br />
<br />
==Disabling automatic spawning of PulseAudio server==<br />
Some users may prefer to manually start the PulseAudio server before running certain programs and then stop the PulseAudio server when they are finished. A simple way to accomplish this is to edit {{ic|~/.config/pulse/client.conf}} or {{ic|/etc/pulse/client.conf}} and change {{ic|1=autospawn = yes}} to {{ic|1=autospawn=no}}. Make sure the line is uncommented as well.<br />
{{hc|~/.config/pulse/client.conf #or /etc/pulse/client.conf|<nowiki><br />
autospawn=no<br />
</nowiki>}}<br />
Now you can manually start the pulseaudio server with<br />
$ pulseaudio --start<br />
and stop it with<br />
$ pulseaudio --kill<br />
<br />
This setting is also respected by the default pulseaudio dektop session startup script {{ic|start-pulseaudio-x11}} which is executed from {{ic|/etc/xdg/autostart/pulseaudio.desktop}}.<br />
<br />
==Disabling pulseaudio daemon altogether==<br />
To disable the pulseaudio daemon completely, and thereby preventing it from starting, one can add {{ic|1=daemon-binary=/bin/true}} to the configuration file.<br />
{{hc|~/.config/pulse/client.conf #or /etc/pulse/client.conf|2=daemon-binary=/bin/true}}<br />
<br />
==Remap stereo to mono==<br />
Remap a stereo input-sink to a mono sink by creating a virtual sink. It would be useful if you only have one speaker. Add to {{ic|/etc/pulse/default.pa}}:<br />
<br />
load-module module-remap-sink master=alsa_output.pci-0000_00_1f.5.analog-stereo sink_name=mono sink_properties="device.description='Mono'" channels=2 channel_map=mono,mono<br />
# Optional: Select new remap as default<br />
set-default-sink mono<br />
<br />
(replace alsa_output.pci-0000_00_1f.5.analog-stereo in the sound card name shown from {{ic|pacmd list-sinks}})<br />
<br />
Switch player between virtual mono sink and real stereo sink.<br />
<br />
==Swap left/right channels==<br />
This is the same as "reverse stereo", where the left and right channels are to be swapped.<br />
<br />
First, identify the card you want its channels swapped:<br />
$ cat /proc/asound/cards<br />
and use the name string for the device you wish to use (the one in square brackets, e.g. [Intel]).<br />
<br />
Edit {{ic|/etc/pulse/default.pa}} and comment out module-hal-detect and module-detect lines.<br />
<br />
Search for the commented-out line that starts "#load-module module-alsa-sink", uncomment it and change it to<br />
<br />
load-module module-alsa-sink device=hw:[device name] channel_map=right,left<br />
Restart the pulseaudio deamon by running<br />
pulseaudio -k; pulseaudio -D<br />
<br />
[https://www.freedesktop.org/wiki/Software/PulseAudio/FAQ/#index34h3 Pulseaudio FAQ: How can I reverse my left and right speaker channels?]<br />
<br />
===Using default.pa===<br />
Another approach to swapping channels is suggested in [https://superuser.com/a/144252/161008]:<br />
<br />
{{hc|~/.config/pulse/default.pa|2=<br />
#!/usr/bin/pulseaudio -nF<br />
<br />
.include /etc/pulse/default.pa<br />
<br />
load-module module-remap-sink sink_name=reverse-stereo master=0 channels=2 master_channel_map=front-right,front-left channel_map=front-left,front-right<br />
set-default-sink reverse-stereo<br />
}}<br />
<br />
== PulseAudio as a minimal unintrusive dumb pipe to ALSA ==<br />
Some people do not want to run PulseAudio all the time for various reasons. This example will turn the full fledged audio server into an unobstrusive dumb pipe to ALSA devices that automatically starts '''and''' stops itself when done, allowing applications that requires PulseAudio to fully function while not touching any ALSA setting nor setting itself as the default ALSA device.<br />
<br />
This configuration tells native PA clients to autospawn the daemon when they need it, then the daemon is configured to autoexit as soon as all clients have disconnected. The daemon itself uses a plain simple static configuration that uses your configured {{ic|pcm.!default}} ALSA devices and nothing more. No replacement of ALSA's default, no playing with mixer levels, nothing but record/playback. Also make sure {{Pkg|pulseaudio-alsa}} is '''not''' installed so standard ALSA clients don't default to pulse. Since {{Pkg|pulseaudio-alsa}} contains only a configuration file {{ic|/etc/asound.conf}}, if it's installed as dependency, one could simply comment all contents in {{ic|/etc/asound.conf}}. {{ic|alsamixer}} functions properly as well as any other ALSA clients. Also make sure common frameworks like Xine, Gstreamer and Phonon are configured to use ALSA: by default if they detect PulseAudio is installed they will try to use it before ALSA.<br />
<br />
{{hc|/etc/pulse/daemon.conf|<nowiki><br />
# Replace these with the proper values<br />
exit-idle-time = 0 # Exit as soon as unneeded<br />
flat-volumes = yes # Prevent messing with the master volume<br />
</nowiki>}}<br />
<br />
{{hc|/etc/pulse/client.conf|<nowiki><br />
# Replace these with the proper values<br />
<br />
# Applications that uses PulseAudio *directly* will spawn it,<br />
# use it, and pulse will exit itself when done because of the<br />
# exit-idle-time setting in daemon.conf<br />
autospawn = yes<br />
</nowiki>}}<br />
<br />
{{hc|/etc/pulse/default.pa|<nowiki><br />
# Replace the *entire* content of this file with these few lines and<br />
# read the comments<br />
<br />
.fail<br />
# Set tsched=0 here if you experience glitchy playback. This will<br />
# revert back to interrupt-based scheduling and should fix it.<br />
#<br />
# Replace the device= part if you want pulse to use a specific device<br />
# such as "dmix" and "dsnoop" so it doesn't lock an hw: device.<br />
<br />
# INPUT/RECORD<br />
load-module module-alsa-source device="default" tsched=1<br />
<br />
# OUTPUT/PLAYBACK<br />
load-module module-alsa-sink device="default" tsched=1 <br />
<br />
# Accept clients -- very important<br />
load-module module-native-protocol-unix<br />
<br />
.nofail<br />
.ifexists module-x11-publish.so<br />
# Publish to X11 so the clients know how to connect to Pulse. Will<br />
# clear itself on unload.<br />
load-module module-x11-publish<br />
.endif<br />
</nowiki>}}<br />
<br />
== Having both speakers and headphones plugged in and switching in software on-the-fly ==<br />
<br />
By design, Pulseaudio automatically turns off Line Out when headphones are plugged in and uses Headphone slider instead. You can observe this behavior in {{ic|alsamixer}}. What we want is to have Headphone and Line Out sliders working separately and at the same time. This is extremely useful if you want to remap Realtek's jacks to have, say, Rear Green for headphones and Blue for speakers (with the help of {{ic|hdajackretask}} from {{Pkg|alsa-tools}}).<br />
<br />
To achieve this, you should directly edit Pulseaudio mixer's configuration.<br />
<br />
1. We tell pulseaudio that headphones are always plugged in. Edit:<br />
<br />
{{ic|/usr/share/pulseaudio/alsa-mixer/paths/analog-output-lineout.conf}}<br />
<br />
Find:<br />
{{bc|<nowiki><br />
[Jack Headphone]<br />
state.plugged = no<br />
state.unplugged = unknown<br />
</nowiki>}}<br />
<br />
Change {{ic|no}} to {{ic|yes}}<br />
<br />
2. By default, Line Out's volume controlled only by Master, and not by Line Out slider itself. We want to merge Line Out with Master.<br />
<br />
Add this snippet to the end of the file:<br />
<br />
{{bc|<nowiki><br />
[Element Line Out]<br />
switch = mute<br />
volume = merge<br />
</nowiki>}}<br />
<br />
3. We need to completely cut off Line Out when we use headphones. Edit:<br />
<br />
{{ic|/usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf}}<br />
<br />
Add this snippet to the end of the file:<br />
<br />
{{bc|<nowiki><br />
[Element Line Out]<br />
switch = off<br />
volume = off<br />
</nowiki>}}<br />
<br />
4. Like Pulseaudio, Alsa itself cuts off speakers when headphones are plugged in. Open {{ic|alsamixer}} (in case of Realtek HDA {{ic|alsamixer -c0}}) and change {{ic|Auto-Mute mode}} to {{ic|disabled}}. <br />
<br />
5. Restart Pulseaudio<br />
<br />
{{bc|<nowiki><br />
$ pulseaudio -k<br />
$ pulseaudio --start<br />
</nowiki>}}<br />
<br />
Now you have two separate ports on the same sink in pulseaudio. They mute each other, so you can switch to headphones and this will mute Line Out, and vice versa.<br />
To switch between ports you can use Gnome or Plasma sound mixer, or install appropriate desktop extension.<br />
<br />
== Allowing multiple users to use PulseAudio at the same time ==<br />
<br />
It is sometimes desirable to run some programs as another user on the same desktop of the primary user in order to isolate the software. However, PulseAudio will not accept by default connections by the secondary users, since a PulseAudio daemon is already running for the primary user. However, a PulseAudio UNIX socket can be created in order to accept connections from other users to the main PulseAudio daemon run by the primary user.<br />
<br />
First, edit {{ic|/etc/pulse/default.pa}} or {{ic|~/.config/pulse/default.pa}} and add a directive for the unix socket to be created:<br />
<br />
{{hc|1=~/.config/pulse/default.pa|2=load-module module-native-protocol-unix auth-anonymous=1 socket=/tmp/pulse-socket}}<br />
<br />
Afterwards, set PulseAudio as a client to the UNIX socket just created in the secondary user:<br />
<br />
{{hc|/home/''secondaryuser''/.config/pulse/client.conf|2=default-server = unix:/tmp/pulse-socket}}<br />
<br />
Now, after restarting the PulseAudio daemon, applications running as the secondary user should be able to play sound through the main PulseAudio daemon running as the primary user without problems.</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Touchpad_Synaptics&diff=318562Touchpad Synaptics2014-06-08T09:51:47Z<p>Bladesonfire: /* Elantech touchpads */</p>
<hr />
<div>[[de:Synaptics Touchpad Treiber]]<br />
[[es:Touchpad Synaptics]]<br />
[[fr:Touchpad Synaptics]]<br />
[[it:Touchpad Synaptics]]<br />
[[ja:Touchpad Synaptics]]<br />
[[ru:Touchpad Synaptics]]<br />
[[zh-CN:Touchpad Synaptics]]<br />
[[Category:Input devices]]<br />
{{Related articles start}}<br />
{{Related|Xorg}}<br />
{{Related|Touchpad Synaptics/10-synaptics.conf example}}<br />
{{Related articles end}}<br />
This article details the installation and configuration process of the '''''Synaptics input driver''''' for Synaptics (and ALPS) touchpads found on most notebooks.<br />
<br />
== Installation ==<br />
<br />
The Synaptics driver can be [[pacman|installed]] with the package {{Pkg|xf86-input-synaptics}}, available in the [[official repositories]].<br />
<br />
== Configuration ==<br />
<br />
The primary method of configuration for the touchpad is through an [[Xorg]] server configuration file. After installation of {{ic|xf86-input-synaptics}}, a default configuration file is located at {{ic|/etc/X11/xorg.conf.d/50-synaptics.conf}}.<br />
<br />
Users can edit this file to configure the various driver options available, for a complete list of all available options users should refer to the synaptics manual page:<br />
<br />
$ man synaptics<br />
<br />
=== Frequently used options ===<br />
<br />
The following lists options that many users may wish to configure. Note that all these options can simply be added to the main configuration file in {{ic|/etc/X11/xorg.conf.d/50-synaptics.conf}}, as shown in this example configuration file where we have enabled vertical, horizontal and circular scrolling:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/50-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "touchpad"<br />
Driver "synaptics"<br />
MatchIsTouchpad "on"<br />
Option "TapButton1" "1"<br />
Option "TapButton2" "2"<br />
Option "TapButton3" "3"<br />
Option "VertEdgeScroll" "on"<br />
Option "VertTwoFingerScroll" "on"<br />
Option "HorizEdgeScroll" "on"<br />
Option "HorizTwoFingerScroll" "on"<br />
Option "CircularScrolling" "on"<br />
Option "CircScrollTrigger" "2"<br />
Option "EmulateTwoFingerMinZ" "40"<br />
Option "EmulateTwoFingerMinW" "8"<br />
Option "CoastingSpeed" "0"<br />
Option "FingerLow" "35"<br />
Option "FingerHigh" "40"<br />
...<br />
EndSection<br />
</nowiki>}}<br />
<br />
; '''TapButton1''': (integer) configures which mouse-button is reported on a non-corner, one finger tap.<br />
; '''TapButton2''': (integer) configures which mouse-button is reported on a non-corner, two finger tap<br />
; '''TapButton3''': (integer) configures which mouse-button is reported on a non-corner, three finger tap<br />
; '''RBCornerButton''': (integer) configures which mouse-button is reported on a right bottom corner, one finger tap (use {{ic|Option "RBCornerButton" "3"}} to achieve Ubuntu style tap behaviour for right mouse button in lower right corner)<br />
; '''RTCornerButton''': (integer) as above, but for top right corner, one finger tap.<br />
; '''VertEdgeScroll''': (boolean) enables vertical scrolling while dragging across the right edge of the touch pad.<br />
; '''HorizEdgeScroll''': (boolean) enables horizontal scrolling while dragging across the bottom edge of the touch pad.<br />
; '''VertTwoFingerScroll''': (boolean) enables vertical scrolling using two fingers.<br />
; '''HorizTwoFingerScroll''': (boolean) enables horizontal scrolling using two fingers.<br />
; '''EmulateTwoFingerMinZ/W''': (integer) play with this value to set the precision of two finger scroll.<br />
; '''FingerLow''': (integer) when finger pressure drops below this value, the driver counts it as a release.<br />
; '''FingerHigh''': (integer) when finger pressure goes above this value, the driver counts it as a touch.<br />
<br />
[[Touchpad Synaptics/10-synaptics.conf example|An example]] with a brief description of all options. As usual settings will vary between machines. It is recommended that you discover your own options using [[Touchpad_Synaptics#Synclient|synclient]].<br />
<br />
{{Note|<br />
* If you find that your hand frequently brushes your touchpad, causing the TapButton2 option to be triggered (which will more than likely paste from your clipboard), and you do not mind losing two-finger-tap functionality, set {{ic|TapButton2}} to -1.<br />
* Recent versions include a "Coasting" feature, enabled by default, which may have the undesired effect of continuing almost any scrolling until the next tap or click, even if you are no longer touching the touchpad. This means that to scroll just a bit, you need to scroll (by using the edge, or a multitouch option) and then almost immediately tap the touchpad, otherwise scrolling will continue forever. If wish to avoid this, set {{ic|CoastingSpeed}} to 0.<br />
* If your touchpad is too sensitive, use higher values for {{ic|FingerLow}} and {{ic|FingerHigh}} and vice versa. Remember that {{ic|FingerLow}} should be smaller than {{ic|FingerHigh}}<br />
}}<br />
<br />
=== Other options ===<br />
<br />
; '''VertScrollDelta''' and '''HorizScrollDelta''': (integer) configures the speed of scrolling, it's a bit counter-intuitive because higher values produce greater precision and thus slower scrolling. Negative values cause natural scrolling like in OS X.<br />
<br />
=== GNOME/Cinnamon ===<br />
<br />
Users of [[GNOME]] may have to edit its configuration as well, because in default it is set to disable tapping to click, horizontal scrolling and not to allow touchpad disabling while typing.<br />
<br />
To change these settings in '''Gnome 2''':<br />
# Run {{ic|gconf-editor}}<br />
# Edit the keys in the {{ic|/desktop/gnome/peripherals/touchpad/}} folder.<br />
<br />
To change these settings in '''Gnome 3''':<br />
# Open ''System Settings''.<br />
# Click ''Mouse and Touchpad''.<br />
# Change the settings on the ''Touchpad'' tab.<br />
<br />
To change these settings in '''Cinnamon''':<br />
# Open ''Cinnamon System Settings''.<br />
# Click ''Mouse and Touchpad''.<br />
# Change the settings on the ''Touchpad'' tab.<br />
<br />
Gnome settings daemon may override existing settings (for example ones set in {{ic|xorg.conf.d}}) for which there is no equivalent in any of the graphical configuration utilities. It is possible to stop gnome from touching mouse settings at all:<br />
# Run {{ic|dconf-editor}}<br />
# Edit {{ic|/org/gnome/settings-daemon/plugins/mouse/}} (or {{ic|/org/cinnamon/settings-daemon/plugins/mouse/}} for cinnamon)<br />
# Uncheck the '''active''' setting<br />
It will now respect your system's existing synaptics configuration.<br />
<br />
'''Remember''': Since Gnome works on a user by user basis, when you run dconf-editor or gconf-editor, this should be done in your current user session. Repeat this procedure for each and every user you have for this computer.<br />
<br />
=== MATE ===<br />
<br />
As with [[GNOME]], it is possible configure the way MATE handles the touchpad:<br />
<br />
# Run {{ic|dconf-editor}}<br />
# Edit the keys in the {{ic|org.mate.peripherals-touchpad}} folder.<br />
<br />
To prevent Mate settings daemon from overriding existing settings, do as follows:<br />
# Run {{ic|dconf-editor}}<br />
# Edit {{ic|org.mate.SettingsDaemon.plugins.mouse}}<br />
# Uncheck the '''active''' setting.<br />
<br />
=== Configuration on the fly ===<br />
<br />
Next to the traditional method of configuration, the Synaptics driver also supports on the fly configuration. This means that users can set certain options through a software application, these options are applied immediately without needing a restart of Xorg. This is useful to test configuration options before you include them in the configuration file.<br />
<br />
{{Warning|On-the-fly configuration is non-permanent and will not remain active through a reboot, suspend/resume, or restart of Xorg. This should only be used to test, fine-tune or script configuration features.}}<br />
<br />
==== Console tools ====<br />
<br />
* {{App|[[Touchpad_Synaptics#Synclient|Synclient]] (Recommended)|command line utility to configure and query Synaptics driver settings on a live system, the tool is developed by the synaptics driver maintainers and is provided with the synaptics driver|http://xorg.freedesktop.org/|{{Pkg|xf86-input-synaptics}}}}<br />
* {{App|[[Touchpad_Synaptics#xinput|xinput]]|small general-purpose CLI tool to configure devices|http://xorg.freedesktop.org/|{{Pkg|xorg-xinput}}}}<br />
<br />
==== Graphical tools ====<br />
<br />
{{Warning|Some of the tools below still require the obsolete {{ic|SHMConfig}} mode, and will not work with current {{Pkg|xf86-input-synaptics}} driver. Please remove outdated tools from the list.}}<br />
<br />
* {{App|GPointing Device Settings|provides graphical on the fly configuration for several pointing devices connected to the system, including your synaptics touch pad. This application replaces GSynaptics as the preferred tool for graphical touchpad configuration through the synaptics driver|http://live.gnome.org/GPointingDeviceSettings|{{Pkg|gpointing-device-settings}}}}<br />
:{{Note|For GPointingDeviceSettings to work with Synaptics touchpads both {{Pkg|xf86-input-synaptics}} and {{Pkg|libsynaptics}} have to be installed.}}<br />
<br />
* {{App|Synaptiks (unmaintained)|touchpad configuration and management tool for [[KDE]]. It provides a System Settings module to configure basic and advanced features of the touchpad. Additionally it comes with a little system tray application, which can switch the touchpad automatically off, while an external mouse is plugged or while you are typing. This utility is currently unmaintained; moreover it seems to crash under KDE 4.11.|https://github.com/synaptiks/synaptiks|{{AUR|synaptiks}}}}<br />
<br />
* {{App|kcm_touchpad|touchpad configuration tool for [[KDE]]. It provides a System Settings module to configure basic and advanced features of the touchpad. Additionally it comes with a little system tray application (plasmoid), which can switch the touchpad manual or automatically off, while an external mouse is plugged or while you are typing. Received a major update in February 2014, works under KDE SC 4.12+|https://projects.kde.org/projects/playground/utils/kcm-touchpad/repository|{{AUR|kcm_touchpad}}}}<br />
<br />
== Advanced configuration ==<br />
<br />
=== Using xinput to determine touchpad capabilities ===<br />
<br />
Depending on your model, synaptic touchpads may have or lack capabilities. We can determine which capabilities your hardware supports by using {{ic|xinput}}.<br />
* left, middle and right hardware buttons<br />
* two finger detection<br />
* three finger detection<br />
* configurable resolution<br />
<br />
First, find the name of your touchpad:<br />
<br />
$ xinput -list<br />
<br />
You can now use {{ic|xinput}} to find your touchpad's capabilities:<br />
<br />
$ xinput list-props "SynPS/2 Synaptics TouchPad" | grep Capabilities<br />
<br />
Synaptics Capabilities (309): 1, 0, 1, 0, 0, 1, 1<br />
<br />
From left to right, this shows:<br />
* (1) device has a physical left button<br />
* (0) device does not have a physical middle button<br />
* (1) device has a physical right button<br />
* (0) device does not support two-finger detection<br />
* (0) device does not support three-finger detection<br />
* (1) device can configure vertical resolution<br />
* (1) device can configure horizontal resolution<br />
<br />
Use {{ic|xinput list-props "SynPS/2 Synaptics TouchPad"}} to list all device properties.<br />
<br />
=== Synclient ===<br />
<br />
Synclient can configure every option available to the user as documented in {{ic|$ man synaptics}}. A full list of the current user settings can be brought up:<br />
<br />
$ synclient -l<br />
<br />
Every listed configuration option can be controlled through synclient, for example:<br />
<br />
$ synclient PalmDetect=1 (to enable palm detection)<br />
$ synclient TapButton1=1 (configure button events)<br />
$ synclient TouchpadOff=1 (disable the touchpad)<br />
<br />
After you have successfully tried and tested your options through synclient, you can make these changes permanent by adding them to {{ic|/etc/X11/xorg.conf.d/50-synaptics.conf}}.<br />
<br />
=== evtest ===<br />
<br />
The tool {{AUR|evtest}} can display pressure and placement on the touchpad in real-time, allowing further refinement of the default Synaptics settings. The evtest monitoring can be started with:<br />
<br />
$ evtest /dev/input/event''X''<br />
<br />
''X'' denotes the touchpad's ID. It can be found by looking at the output of {{ic|cat /proc/bus/input/devices}}.<br />
<br />
evtest needs exclusive access to the device which means it cannot be run together with an X server instance. You can either kill the X server or run evtest from a different virtual terminal (e.g., by pressing {{ic|Ctrl+Alt+2}}).<br />
<br />
=== Circular Scrolling ===<br />
<br />
Circular scrolling is a feature that Synaptics offers which closely resembles the behaviour of iPods. Instead of (or additional to) scrolling horizontally or vertically, you can scroll circularly. Some users find this faster and more precise.<br />
To enable circular scrolling, add the following options to the touchpad device section of {{ic|/etc/X11/xorg.conf.d/50-synaptics.conf}}:<br />
{{hc|/etc/X11/xorg.conf.d/50-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
...<br />
Option "CircularScrolling" "on"<br />
Option "CircScrollTrigger" "0"<br />
...<br />
EndSection<br />
</nowiki>}}<br />
<br />
The option '''CircScrollTrigger''' may be one of the following values, determining which edge circular scrolling should start:<br />
<br />
0 All Edges<br />
1 Top Edge<br />
2 Top Right Corner<br />
3 Right Edge<br />
4 Bottom Right Corner<br />
5 Bottom Edge<br />
6 Bottom Left Corner<br />
7 Left Edge<br />
8 Top Left Corner<br />
<br />
Specifying something different from zero may be useful if you want to use circular scrolling in conjunction with horizontal and/or vertical scrolling. If you do so, the type of scrolling is determined by the edge you start from.<br />
<br />
To scroll fast, draw small circles in the center of your touchpad. To scroll slowly and more precise, draw large circles.<br />
<br />
=== Natural scrolling ===<br />
<br />
It is possible to enable natural scrolling through synaptics. Simply use negative values for {{ic|VertScrollDelta}} and {{ic|HorizScrollDelta}} like so:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/50-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
...<br />
Option "VertScrollDelta" "-111"<br />
Option "HorizScrollDelta" "-111"<br />
...<br />
EndSection<br />
</nowiki>}}<br />
<br />
=== Software toggle ===<br />
<br />
You may find it useful to have a software toggle that will turn on or off your touchpad, especially if it is extremely sensitive and you are doing a lot of typing. Please also see [[#Disable touchpad upon external mouse detection]] as that may be better solution, a matter of choice. The advantage here is you have the control, while the other solution has a daemon determine when to turn off the trackpad.<br />
<br />
You will want to grab [[xbindkeys]] if you do not already have key binding software.<br />
<br />
Then save this script to something such as {{ic|/usr/bin/trackpad-toggle.sh}}:<br />
<br />
{{hc|/usr/bin/trackpad-toggle.sh|<nowiki><br />
#!/bin/bash<br />
<br />
synclient TouchpadOff=$(synclient -l | grep -c 'TouchpadOff.*=.*0')<br />
</nowiki>}}<br />
<br />
Then finally add a key binding to use the script. It is best to call with xbindkeys like so (file {{ic|~/.xbindkeysrc}}):<br />
<br />
{{hc|~/.xbindkeysrc|<nowiki><br />
"/usr/bin/trackpad-toggle.sh"<br />
m:0x5 + c:65<br />
Control+Shift + space<br />
</nowiki>}}<br />
<br />
Copy ''either one of the last two lines'', do not copy both. Now just (re)start {{ic|xbindkeys}} and {{ic|Ctrl+Shift+Space}} will now toggle your trackpad.<br />
<br />
Of course you could easily use any other keybinding software, such as the ones provided by Xfce4 and GNOME.<br />
<br />
=== Disable trackpad while typing ===<br />
<br />
==== Using automatic palm detection ====<br />
<br />
First of all you should test if it works properly for your trackpad and if the settings are accurate:<br />
<br />
$ synclient PalmDetect=1<br />
<br />
Then test the typing. You can tweak the detection with:<br />
<br />
$ synclient PalmMinWidth=<br />
<br />
which is the width of the area your hand touches, and<br />
<br />
$ synclient PalmMinZ=<br />
<br />
which is the minimum Z distance at which the detection is performed.<br />
<br />
Once you have found the correct settings, save them into {{ic|/etc/X11/xorg.conf.d/50-synaptics.conf}} like this:<br />
<br />
{{bc|<nowiki><br />
#synclient PalmDetect=1<br />
Option "PalmDetect" "1"<br />
#synclient PalmMinWidth=10<br />
Option "PalmMinWidth" "10"<br />
#synclient PalmMinZ=200<br />
Option "PalmMinZ" "200"<br />
</nowiki>}}<br />
<br />
{{Warning|1=For some touchpads, an [https://bugzilla.kernel.org/show_bug.cgi?id=77161 issue] with the kernel can cause the palm width to always be reported as 0. This breaks palm detection in a majority of cases. Pending an actual fix, you can [https://gist.github.com/silverhammermba/a231c8156ecaa63c86f1 patch] the synaptics package to use only Z for palm detection.}}<br />
<br />
==== Using .xinitrc ====<br />
<br />
To have the touchpad disabled automatically when you begin typing, add the following line to your {{ic|~/.xinitrc}} (before any line starting with {{ic|exec}}, otherwise the command will not be executed):<br />
<br />
$ syndaemon -t -k -i 2 &<br />
<br />
; '''-i 2''': sets the idle time to 2 seconds. The idle time specifies how many seconds to wait after the last key-press before enabling the touchpad again.<br />
; '''-t''': tells the daemon not to disable mouse movement when typing and only disable tapping and scrolling.<br />
; '''-k''': tells the daemon to ignore modifier keys when monitoring keyboard activity (e.g.: allows Ctrl+Left Click).<br />
<br />
More details are available in the man page:<br />
<br />
$ man syndaemon<br />
<br />
If you are using a login manager, you will need to specify the command where your DE allows you to do so.<br />
<br />
==== Using a login manager ====<br />
<br />
The {{ic|-d}} option is necessary to start syndaemon as a background process for post Login instructions.<br />
<br />
'''For GNOME: (GDM)'''<br />
<br />
To start syndaemon you need to use Gnome's Startup Applications Preferences program. Login to Gnome and go to '''System > Preferences > Startup Applications'''. In the Startup Programs tab click the '''Add''' button. Name the Startup Program whatever you like and input any comments you like (or leave this field blank). In the command field add:<br />
<br />
In Gnome 3 run gnome-session-properties to access startup applications.<br />
<br />
$ syndaemon -t -k -i 2 -d &<br />
<br />
When you are done, click the '''Add''' button in the '''Add Startup Program''' dialogue. Make sure the check box next to the startup program you have created is checked, in the list of additional startup programs. Close the '''Startup Applications Preferences''' window and you are done.<br />
<br />
'''For KDE: (KDM)'''<br />
<br />
Goto '''System Settings > Startup and Shutdown > Autostart''', then click '''Add Program''', enter:<br />
<br />
$ syndaemon -t -k -i 2 -d &<br />
<br />
Then check '''Run in terminal'''.<br />
<br />
=== Disable touchpad upon external mouse detection ===<br />
<br />
With the assistance of [[udev]], it is possible to automatically disable the touchpad if an external mouse has been plugged in. To achieve this, add the following udev rules:<br />
<br />
{{hc|/etc/udev/rules.d/01-touchpad.rules|2=<br />
SUBSYSTEM=="input", KERNEL=="mouse[0-9]*", ACTION=="add", ENV{DISPLAY}=":0", ENV{XAUTHORITY}="/home/''username''/.Xauthority", RUN+="/usr/bin/synclient TouchpadOff=1"<br />
SUBSYSTEM=="input", KERNEL=="mouse[0-9]*", ACTION=="remove", ENV{DISPLAY}=":0", ENV{XAUTHORITY}="/home/''username''/.Xauthority", RUN+="/usr/bin/synclient TouchpadOff=0"<br />
}}<br />
<br />
GDM stores Xauthority files in {{ic|/var/run/gdm}} in a randomly-named directory. For some reason also multiple authority files may appear for a user. So you need udev rules like these:<br />
<br />
{{hc|/etc/udev/rules.d/01-touchpad.rules|2=<br />
SUBSYSTEM=="input", KERNEL=="mouse[0-9]", ACTION=="add", PROGRAM="/usr/bin/find /var/run/gdm -name ''username'' -print -quit", ENV{DISPLAY}=":0", ENV{XAUTHORITY}="$result/database", RUN+="/usr/bin/synclient TouchpadOff=1"<br />
SUBSYSTEM=="input", KERNEL=="mouse[0-9]", ACTION=="remove", PROGRAM="/usr/bin/find /var/run/gdm -name ''username'' -print -quit", ENV{DISPLAY}=":0", ENV{XAUTHORITY}="$result/database", RUN+="/usr/bin/synclient TouchpadOff=0"<br />
}}<br />
<br />
However, these udev rules conflict with [[#Using .xinitrc|syndaemon]]. To disable touchpad and simultaneously kill ''syndaemon'', you can use a rule like this:<br />
<br />
{{hc|/etc/udev/rules.d/01-touchpad.rules|2=<br />
SUBSYSTEM=="input", KERNEL=="mouse[0-9]", ACTION=="add", PROGRAM="/usr/bin/find /var/run/gdm -name ''username'' -print -quit", ENV{DISPLAY}=":0", ENV{XAUTHORITY}="$result/database", RUN+="/bin/sh -c '/usr/bin/synclient TouchpadOff=1 ; sleep 1; /bin/killall syndaemon; '"<br />
}}<br />
<br />
If ''syndaemon'' starts automatically with mouse removal, then you can combine this with the remove rule above. If you need to start ''syndaemon'' yourself, then alter the command accordingly with your favourite ''syndaemon'' options.<br />
<br />
==== System with multiple X sessions ====<br />
<br />
For an environment where multiple users are present, a slightly different approach is needed to detect the current users X environment. This script will help achieving this:<br />
<br />
{{hc|/usr/bin/mouse-pnp-event-handler.sh|<nowiki><br />
#!/bin/sh<br />
## $1 = "add" / "remove"<br />
## $2 = %k from udev <br />
<br />
## Set TRACKPAD_NAME according to your configuration. <br />
## Check your trackpad name with: <br />
## find /sys/class/input/ -name mouse* -exec udevadm info -a {} \; | grep 'ATTRS{name}'<br />
TRACKPAD_NAME="SynPS/2 Synaptics TouchPad"<br />
<br />
<br />
USERLIST=$(w -h | cut -d' ' -f1 | sort | uniq)<br />
MOUSELIST=$(find /sys/class/input/ -name mouse*)<br />
<br />
for CUR_USER in ${USERLIST}; do<br />
CUR_USER_XAUTH="$(sudo -Hiu ${CUR_USER} env | grep -e "^HOME=" | cut -d'=' -f2)/.Xauthority"<br />
<br />
<br />
## Can't find a way to get another users DISPLAY variable from an isolated root environment. Have to set it manually.<br />
#CUR_USER_DISPL="$(sudo -Hiu ${CUR_USER} env | grep -e "^DISPLAY=" | cut -d'=' -f2)"<br />
CUR_USER_DISPL=":0"<br />
<br />
export XAUTHORITY="${CUR_USER_XAUTH}"<br />
export DISPLAY="${CUR_USER_DISPL}"<br />
<br />
if [ -f "${CUR_USER_XAUTH}" ]; then<br />
case "$1" in<br />
"add")<br />
/usr/bin/synclient TouchpadOff=1<br />
/usr/bin/logger "USB mouse plugged. Disabling touchpad for $CUR_USER. ($XAUTHORITY - $DISPLAY)"<br />
;;<br />
"remove")<br />
## Only execute synclient if there are no external USB mice connected to the system.<br />
EXT_MOUSE_FOUND="0"<br />
for CUR_MOUSE in ${MOUSELIST}; do<br />
if [ "$(cat ${CUR_MOUSE}/device/name)" != "${TRACKPAD_NAME}" ]; then<br />
EXT_MOUSE_FOUND="1"<br />
fi<br />
done<br />
if [ "${EXT_MOUSE_FOUND}" == "0" ]; then<br />
/usr/bin/synclient TouchpadOff=0<br />
/usr/bin/logger "No additional external mice found. Enabling touchpad for $CUR_USER."<br />
else<br />
logger "Additional external mice found. Won't enable touchpad yet for $CUR_USER."<br />
fi<br />
;;<br />
esac<br />
fi<br />
done<br />
</nowiki>}}<br />
<br />
Update the {{ic|TRACKPAD_NAME}} variable for your system configuration.<br />
Run {{ic|<nowiki>find /sys/class/input/ -name mouse* -exec udevadm info -a {} \; | grep 'ATTRS{name}'</nowiki>}} to get a list of useful mice-names. Choose the one for your trackpad.<br />
<br />
Then have udev run this script when USB mices are plugged in or out, with these udev rules:<br />
<br />
{{hc|/etc/udev/rules.d/01-touchpad.rules|2=<br />
SUBSYSTEM=="input", KERNEL=="mouse[0-9]*", ACTION=="add", RUN+="/usr/bin/mouse-pnp-event-handler.sh add %k"<br />
SUBSYSTEM=="input", KERNEL=="mouse[0-9]*", ACTION=="remove", RUN+="/usr/bin/mouse-pnp-event-handler.sh remove %k"<br />
}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== Touchpad does not work after resuming from hibernate/suspend ===<br />
Occasionally touchpads will fail to work when the computer resumes from sleep or hibernation. This can often be corrected without rebooting by<br />
* Switching to a console and back again,<br />
* entering sleep mode again, and resuming again, or<br />
* locating the correct kernel module, then removing it and inserting it again. <br />
{{Note|You can use Ctrl-Alt-F1 through F8 to switch to a console without using the mouse.}}<br />
modprobe -r psmouse #psmouse happens to be the kernel module for my touchpad (Alps DualPoint)<br />
modprobe psmouse<br />
Now switch back to the tty that X is running on. If you chose the right module, your touchpad should be working again.<br />
<br />
=== Emulate middle (3rd) mouse button ===<br />
Add this:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/10-evdev.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "Emulate Middle Butten"<br />
MatchIsPointer "on"<br />
Option "Emulate3Buttons" "on"<br />
EndSection<br />
</nowiki>}}<br />
<br />
to your /etc/X11/xorg.conf.d/10-evdev.conf (or any Xorg conf you want) and you will have middle click emulation.<br />
<br />
[https://bbs.archlinux.org/viewtopic.php?pid=847309#p847309 Thx to augegr]<br />
=== xorg.conf.d/50-synaptics.conf doesn't seem to apply under GNOME and MATE ===<br />
<br />
[[GNOME]] and [[MATE]], by default, will overwrite various options for your touch-pad. This includes configurable features for which there is no graphical configuration within GNOME's system control panel. This may cause it to appear that {{ic|/etc/X11/xorg.conf.d/50-synaptics.conf}} isn't applied. Please refer to the GNOME section in this article to prevent this behavior.<br />
<br />
* [[Touchpad_Synaptics#GNOME.2FCinnamon]]<br />
<br />
=== ALPS Touchpads ===<br />
<br />
{{Expansion}}<br />
{{Out of date|needs to be rewritten for udev}}<br />
<br />
For ALPS Touchpads, if the above configuration does not provide the desired results, try the following configuration instead:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/50-synaptics.conf|<br />
Section "ServerLayout"<br />
...<br />
InputDevice "USB Mouse" "CorePointer"<br />
InputDevice "Touchpad" "SendCoreEvents"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Touchpad"<br />
Driver "synaptics"<br />
Option "Device" "/dev/input/mouse0"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "130"<br />
Option "RightEdge" "840"<br />
Option "TopEdge" "130"<br />
Option "BottomEdge" "640"<br />
Option "FingerLow" "7"<br />
Option "FingerHigh" "8"<br />
Option "MaxTapTime" "180"<br />
Option "MaxTapMove" "110"<br />
Option "EmulateMidButtonTime" "75"<br />
Option "VertScrollDelta" "20"<br />
Option "HorizScrollDelta" "20"<br />
Option "MinSpeed" "0.25"<br />
Option "MaxSpeed" "0.50"<br />
Option "AccelFactor" "0.010"<br />
Option "EdgeMotionMinSpeed" "200"<br />
Option "EdgeMotionMaxSpeed" "200"<br />
Option "UpDownScrolling" "1"<br />
Option "CircularScrolling" "1"<br />
Option "CircScrollDelta" "0.1"<br />
Option "CircScrollTrigger" "2"<br />
Option "Emulate3Buttons" "on"<br />
EndSection<br />
}}<br />
<br />
=== The touchpad is not working, Xorg.0.log shows "Query no Synaptics: 6003C8" ===<br />
<br />
Due to the way synaptics is currently set-up, 2 instances of the synaptics module are loaded. We can recognize this situation by opening the xorg log file ({{ic|/var/log/Xorg.0.log}}) and noticing this:<br />
<br />
{{hc|/var/log/Xorg.0.log|<nowiki><br />
[ 9304.803] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"<br />
[ 9304.803] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"<br />
</nowiki>}}<br />
<br />
Notice how 2 differently named instances of the module are being loaded. In some cases, this causes the touchpad to become nonfunctional.<br />
<br />
We can prevent this double loading by adding {{ic|MatchDevicePath "/dev/input/event*"}} to our {{ic|/etc/X11/xorg.conf.d/50-synaptics.conf}} file:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/50-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "touchpad catchall"<br />
Driver "synaptics"<br />
MatchIsTouchpad "on"<br />
MatchDevicePath "/dev/input/event*"<br />
Option "TapButton1" "1"<br />
Option "TapButton2" "2"<br />
Option "TapButton3" "3"<br />
EndSection <br />
</nowiki>}}<br />
<br />
Restart X and check xorg logs again, the error should be gone and the touchpad should be functional.<br />
<br />
related bugreport: {{Bug|20830}}<br />
<br />
related forum topics:<br />
* https://bbs.archlinux.org/viewtopic.php?id=104769<br />
* https://bbs.archlinux.org/viewtopic.php?pid=825690<br />
<br />
=== Touchpad detected as "PS/2 Generic Mouse" or "Logitech PS/2 mouse" ===<br />
<br />
This can be caused by a number of issues;<br />
<br />
==== ALPS touchpads ====<br />
This is caused by a [https://bugzilla.kernel.org/show_bug.cgi?id=27442 kernel bug] which was fixed in kernel version 3.3. Wrongly detected touchpads cannot be configured with the Synaptic input driver. To fix this, simply install the [[AUR]] package {{AUR|psmouse-alps-driver}}.<br />
<br />
Among the affected notebooks are the following models:<br />
<br />
* Acer Aspire 7750G<br />
* Dell Latitude E6230, E6520, E6430 and E6530 (ALPS DualPoint TouchPad), Inspiron N5110 (ALPS GlidePoint), Inspiron 14R 5420/Turbo SE7420/SE7520 (ALPS GlidePoint)<br />
* Samsung NC110/NF210/QX310/QX410/QX510/SF310/SF410/SF510/RF410/RF510/RF710/RV515<br />
<br />
More information can be found in [https://bbs.archlinux.org/viewtopic.php?id=117109 this thread].<br />
<br />
==== Elantech touchpads ====<br />
This can happen with some laptops with an Elantech touchpad, for example the ASUS x53s. In this situation you need {{AUR|psmouse-alps-driver}} package from [[AUR]].<br />
<br />
==== Laptops with touchscreen & touchpad ====<br />
There also seems to be a problem with laptops which have both a touchscreen & a touchpad, such as the Dell XPS 12 or Dell XPS 13. To fix this, you can [[blacklisting|blacklist]] the '''i2c_usbhib''' driver, this does have the side-effect of disabeling the touchscreen though.<br />
<br />
This [http://www.spinics.net/lists/linux-input/msg27768.html seems to be a known problem]. Also see [https://bbs.archlinux.org/viewtopic.php?pid=1419078 this thread].<br />
<br />
=== Non-functional Synaptics special abilities (multi-tap, scrolling, etc.) ===<br />
<br />
In some cases Synaptics touchpads only work partially. Features like two-finger scrolling or two-finger middle-click do not work even if properly enabled. This is probably related to the [[#The_touchpad_is_not_working.2C_Xorg.0.log_shows_.22Query_no_Synaptics:_6003C8.22|The touchpad is not working]] problem mentioned above. Fix is the same, prevent double module loading.<br />
<br />
If preventing the module from loading twice does not solve your issue, try commenting out the toggle "MatchIsTouchpad" (which is now included by default in the synaptics config).<br />
<br />
If clicking with either 2 or 3 fingers is interpreted as a right-click, so you cannot get a middle click either way regardless of configuration, this bug is probably the culprit: https://bugs.freedesktop.org/show_bug.cgi?id=55365<br />
<br />
=== Cursor jump ===<br />
<br />
Some users have their cursor inexplicably ''jump'' around the screen. There currently no patch for this, but the developers are aware of the problem and are working on it.<br />
<br />
Another posibility is that you're experiencing ''IRQ losses'' related to the i8042 controller (this device handles the keyboard and the touchpad of many laptops), so you have two posibilities here:<br />
<br />
1. rmmod && insmod the psmouse module.<br />
2. append i8042.nomux=1 to the boot line and reboot your machine.<br />
<br />
=== Touchpad device is not located at {{ic|/dev/input/*}} ===<br />
<br />
If that is the case, you can use this command to display information about your input devices:<br />
<br />
$ cat /proc/bus/input/devices<br />
<br />
Search for an input device which has the name "SynPS/2 Synaptics TouchPad". The "Handlers" section of the output specifies what device you need to specify.<br />
<br />
'''Example output:'''<br />
<br />
{{hc|$ cat /proc/bus/input/devices|<nowiki><br />
I: Bus=0011 Vendor=0002 Product=0007 Version=0000<br />
N: Name="SynPS/2 Synaptics TouchPad"<br />
P: Phys=isa0060/serio4/input0<br />
S: Sysfs=/class/input/input1<br />
H: Handlers=mouse0 event1<br />
B: EV=b<br />
B: KEY=6420 0 7000f 0<br />
</nowiki>}}<br />
<br />
In this case, the {{ic|Handlers}} are {{ic|mouse0}} and {{ic|event1}}, so {{ic|/dev/input/mouse0}} would be used.<br />
<br />
{{Expansion|TODO: explain how to apply this in {{ic|/etc/X11/xorg.conf.d/50-synaptics.conf}}}}<br />
<br />
=== Firefox and special touchpad events ===<br />
<br />
You can enable/disable some special events that Firefox handles upon tapping or scrolling certain parts of your touchpad by editing the settings of those actions.<br />
Type '''about:config''' in your Firefox address bar.<br />
To alter options, double-click on the line in question.<br />
<br />
==== Firefox 16.0 and earlier ====<br />
<br />
To prevent Firefox from scrolling (backward/forward) through browser history and instead scroll through pages, edit these settings as shown:<br />
<br />
mousewheel.horizscroll.withnokey.action = 1<br />
mousewheel.horizscroll.withnokey.sysnumlines = true<br />
<br />
To prevent Firefox from redirecting you to URLs formed from your clipboard content upon tapping the upper-right corner of your touchpad (or middle mouse button), set the following option to "false":<br />
middlemouse.contentLoadURL = false<br />
<br />
==== Firefox 17.0 and later ====<br />
<br />
Horizontal scrolling will now by default scroll through pages and not through your history. To reenable Mac-style forward/backward with two-finger swiping, edit:<br />
<br />
mousewheel.default.action.override_x = 2<br />
<br />
You may encounter accidental forwards/backwards while scrolling vertically. To change Firefox's sensitivity to horizontal swipes, edit:<br />
<br />
mousewheel.default.delta_multiplier_x<br />
<br />
The optimum value will depend on your touchpad and how you use it, try starting with <code>10</code>. A negative value will reverse the swipe directions.<br />
<br />
=== Opera: horizontal scrolling issues ===<br />
<br />
Same as above.<br />
To fix it, go to ''Tools > Preferences > Advanced > Shortcuts''. Select "Opera Standard" mouse setup and click "Edit". In "Application" section:<br />
{{Accuracy|Description here is not so clear and i don't use Opera,Please make it clear :)}}<br />
* assign key "Button 6" to command "Scroll left"<br />
* assign key "Button 7" to command "Scroll right"<br />
<br />
=== Scrolling and multiple actions with Synaptics on LG laptops ===<br />
<br />
These problems seem to be occurring on several models of LG laptops.<br />
Symptoms include: when pressing Mouse Button 1, Synaptics interprets it as ScrollUP and a regular button 1 click; same goes for button 2.<br />
<br />
The scrolling issue can be resolved by entering in {{ic|xorg.conf}}:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/xorg.conf|Option "UpDownScrolling" "0"}}<br />
<br />
{{Note|This will make Synaptics interpret one button push as three. There is a patch written by Oskar Sandberg[http://www.math.chalmers.se/~ossa/linux/lg_tx_express.html] that removes these clicks.}}<br />
<br />
Apparently, when trying to compile this against the latest version of Synaptics it fails. The solution to this is using the GIT repository for Synaptics[http://web.telia.com/~u89404340/touchpad/synaptics/.git].<br />
<br />
There is also a package build file in the AUR to automate this: {{AUR|xf86-input-synaptics-lg}}.<br />
<br />
To build the package after downloading the tarball and unpacking it, execute:<br />
<br />
$ cd synaptics-git<br />
$ makepkg<br />
<br />
=== Other external mouse issues ===<br />
<br />
First, make sure your section describing the external mouse contains this line (or that the line looks like this):<br />
<br />
{{hc|/etc/X11/xorg.conf.d/xorg.conf|Option "Device" "/dev/input/mice"}}<br />
<br />
If the "Device" line is different, change it to the above and try to restart X. If this does not solve your problem, make your '''touchpad''' is the CorePointer in the "Server Layout" section:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/xorg.conf|InputDevice "Touchpad" "CorePointer"}}<br />
<br />
and make your external device "SendCoreEvents":<br />
<br />
{{hc|/etc/X11/xorg.conf.d/xorg.conf|InputDevice "USB Mouse" "SendCoreEvents"}}<br />
<br />
finally add this to your external device's section:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/xorg.conf|Option "SendCoreEvents" "true"}}<br />
<br />
If all of the above does not work for you, please check relevant bug trackers for possible bugs, or go through the forums to see if anyone has found a better solution.<br />
<br />
=== Touchpad synchronization issues ===<br />
<br />
Sometimes the cursor may freeze for several seconds or start acting on its own for no apparent reason. This behavior is accompanied by records in {{ic|/var/log/messages.log}}<br />
<br />
{{hc|/var/log/messages.log|psmouse.c: TouchPad at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away}}<br />
<br />
This problem has no general solution, but there are several possible workarounds.<br />
* If you use CPU frequency scaling, avoid using the "ondemand" governor and use the "performance" governor when possible, as the touchpad may lose sync when the CPU frequency changes.<br />
* Avoid using an ACPI battery monitor.<br />
* Attempt to load psmouse with "proto=imps" option. To do that, add this line to your {{ic|/etc/modprobe.d/modprobe.conf}}:<br />
<br />
{{hc|/etc/modprobe.d/modprobe.conf|2=options psmouse proto=imps}}<br />
<br />
* Try another desktop environment. Some users report that this problem only occurs when using XFCE or GNOME, for whatever reason<br />
<br />
=== Delay between a button tap and the actual click ===<br />
<br />
{{Out of date|On Synaptics Driver 1.7.1, the {{ic|FastTaps}} option has been removed.}}<br />
<br />
If you experience a delay between the tap on the touchpad and the actual click that is registered you need to enable FastTaps:<br />
<br />
To do so, you should add '''Option "FastTaps" "1"''' to {{ic|/etc/X11/xorg.conf.d/50-synaptics.conf}} so that you have:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/50-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "Synaptics Touchpad"<br />
Driver "synaptics"<br />
...<br />
Option "FastTaps" "1"<br />
...<br />
EndSection<br />
</nowiki>}}<br />
<br />
===Xorg.log.0 shows SynPS/2 Synaptics touchpad can not grab event device, errno=16 ===<br />
<br />
If you are using Xorg 7.4, you may get a warning like this from {{ic|/var/log/Xorg.0.log}}, thais is because the driver will grab the event device for exclusive use when using the Linux 2.6 event protocol. When it fails, X will return this error message.<br />
<br />
Grabbing the event device means that no other user space or kernel space program sees the touchpad events. This is desirable if the X config file includes {{ic|/dev/input/mice}} as an input device, but is undesirable if you want to monitor the device from user space.<br />
<br />
If you want to control it, add or modify the "GrabEventDevice" option in you touchpad section in {{ic|/etc/X11/xorg.conf.d/50-synaptics.conf}}:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/50-synaptics.conf|2=<br />
...<br />
Option "GrabEventDevice" "''boolean''"<br />
...<br />
}}<br />
<br />
This will come into effect when X is restarted, though you can also change it by using synclient. When changing this parameter with the synclient program, the change will not take effect until the Synaptics driver is disabled and re-enabled. This can be achieved by switching to a text console and then switching back to X.<br />
<br />
=== Synaptics loses multitouch detection after rebooting from Windows ===<br />
<br />
Many drivers include a firmware that is loaded into flash memory when the computer boots. This firmware is not necessarily cleared upon shutdown, and is not always compatible with Linux drivers. The only way to clear the flash memory is to shutdown completely rather than using reboot. It is generally considered best practice to never use reboot when switching between operating systems.<br />
<br />
=== Buttonless touchpads (aka ClickPads) ===<br />
<br />
Some laptops have a special kind of touchpad which has the mouse buttons as part of the tracking plate, instead of being external buttons. For example HP series 4500 ProBooks, ThinkPad X220 and X1 ThinkPad series have this kind of a touchpad. By default whole button area is detected as a left button resulting in the second mouse button being unusable and click + drag will not work. Previously support for such devices was achieved by using third party patches, but from version 1.6.0 the synaptics driver has native multitouch support (using the ''mtdev'' library). Note that although the driver registers multiple touches, it does not track individual fingers (as of version 1.7.1) which results in confusing behavior when using physical buttons of a clickpad for drag-and-drop and other gestures. You can look into the {{AUR|xf86-input-mtrack}} driver for better multitouch support.<br />
<br />
To enable other buttons modify the touchpad section in {{ic|/etc/X11/xorg.conf.d/50-synaptics.conf}} (or better, of your custom synaptics configuration file prefixed with a higher number):<br />
<br />
{{hc|/etc/X11/xorg.conf.d/50-synaptics.conf|<nowiki><br />
...<br />
Option "ClickPad" "true"<br />
Option "EmulateMidButtonTime" "0"<br />
Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"<br />
...<br />
</nowiki>}}<br />
<br />
These three options are the key, first one will enable multitouch support, second will disable middle button emulation (not supported for ClickPads), and third will define the button areas. <br />
<br />
Format for the SoftButtonAreas option is (from {{ic|man 4 synaptics}}):<br />
{{bc|RightButtonAreaLeft RightButtonAreaRight RightButtonAreaTop RightButtonAreaBottom MiddleButtonAreaLeft MiddleButtonAreaRight MiddleButtonAreaTop MiddleButtonAreaBottom}}<br />
<br />
The above example is commonly found in documentation or synaptics packages, and it translates to right half of the bottom 18% of the touchpad to be a right button. There is '''no middle button''' defined. If you want to define a middle button remember one key piece of information from the manual; '''edge set to 0 extends to infinity in that direction.'''<br />
<br />
In the following example right button will occupy 40% of the rightmost part of the button area. We then proceed to setup the middle button to occupy 20% of the touchpad in a small area in the center.<br />
<br />
...<br />
Option "SoftButtonAreas" "60% 0 82% 0 40% 59% 82% 0"<br />
...<br />
<br />
You can use {{ic|<nowiki>synclient</nowiki>}} to check the new soft button areas: <br />
<br />
{{hc|<nowiki>$ synclient -l | grep -i ButtonArea</nowiki>|<nowiki><br />
RightButtonAreaLeft = 3914<br />
RightButtonAreaRight = 0<br />
RightButtonAreaTop = 3918<br />
RightButtonAreaBottom = 0<br />
MiddleButtonAreaLeft = 3100<br />
MiddleButtonAreaRight = 3873<br />
MiddleButtonAreaTop = 3918<br />
MiddleButtonAreaBottom = 0<br />
</nowiki>}}<br />
<br />
If your buttons aren't working, soft button areas are not changing, ensure you do not have a synaptics configuration file distributed by a package which is overriding your custom settings (ie. some AUR packages distribute configurations prefixed with very high numbers).<br />
<br />
These settings cannot be modified on the fly with {{ic|<nowiki>synclient</nowiki>}}, however, {{ic|<nowiki>xinput</nowiki>}} works:<br />
<br />
xinput set-prop "SynPS/2 Synaptics TouchPad" "Synaptics Soft Button Areas" 4000 0 4063 0 3000 4000 4063 0<br />
<br />
You cannot use percentages with this command, so look at {{ic|/var/log/Xorg.0.log}} to figure out the touchpad x and y-axis ranges.<br />
<br />
<br />
== See also ==<br />
<br />
* [http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics/ Synaptics touchpad driver]<br />
* [http://www.x.org/archive/X11R7.5/doc/man/man4/synaptics.4.html Synaptics manual on x.org ]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=99348Acer Aspire 14102010-03-08T05:50:10Z<p>Bladesonfire: /* Fan Issues */ Suggests installing the AUR package to fix fan issues.</p>
<hr />
<div>[[Category:Acer (English)]]<br />
{{Stub}}<br />
This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Details<br />
! Driver/Status<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Install xf86-video-intel<br />
|-<br />
| Wireless<br />
| ['''8804'''] Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br><br />
['''233g16n''']<br />
| Install iwlwifi-5000-ucode<br><br />
Install iwlwifi-1000-ucode<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Works out-of-box<br />
|-<br />
| Audio<br />
| Built-in speakers<br><br />
Headphone Jack<br><br />
Integrated Microphone<br><br />
Microphone Jack<br />
| Untested<br><br />
Manual Setup (see below)<br><br />
Untested<br><br />
Untested<br><br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader:<br />
MultiMediaCard™<br><br />
Secure Digital<br><br />
Memory Stick®<br><br />
Memory Stick PRO™<br><br />
xD-Picture Card™<br />
|<br />
Untested<br><br />
Works<br><br />
Untested<br><br />
Works<br><br />
Untested<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Works out-of-box<br />
|-<br />
| Touchpad<br />
| <br />
| Install xf86-input-evdev, xf86-input-synaptics<br />
|-<br />
| HDMI Out<br />
| <br />
| Works OOTB<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
<br />
If you are receiving errors booting or during the install, try setting the SATA mode to "IDE" in the BIOS. This is not necessary for all users.<br />
<br />
=== During the Installation ===<br />
Be sure to install the necessary wireless driver (see above), "wireless_tools", and optionally "netcfg" if you would like wireless to work post-install.<br />
<br />
=== Post-Install ===<br />
<br />
==== Setup the Touchpad ====<br />
<br />
Make sure to install xf86-input-synaptics. If you use HAL for Xorg hotplugging it will be autoloaded. Don't forget to enable the touchpad with <Fn>-F7. The following threads might also be interesting: [http://bbs.archlinux.org/viewtopic.php?id=77400] [http://bbs.archlinux.org/viewtopic.php?id=77190]<br />
<br />
==== Fan Issues ====<br />
<br />
If the noise is running too often or making too much noise, try installing the latest version of [http://aur.archlinux.org/packages.php?ID=23686 acerhdf].<br />
<br />
== Additional Links ==<br />
* [http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official US site]<br />
* [http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]<br />
* [http://forum.notebookreview.com/showthread.php?t=424213 Thread post containing specs of different models]<br />
* [http://forum.notebookreview.com/showthread.php?t=419117 Thread of tips, tricks, & tweaks]<br />
* [http://ubuntuforums.org/showthread.php?p=8409272 Power saving tips and tricks from Ubuntu forum]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=99347Acer Aspire 14102010-03-08T05:24:14Z<p>Bladesonfire: Added Ubuntu link and Fan Issues section.</p>
<hr />
<div>[[Category:Acer (English)]]<br />
{{Stub}}<br />
This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Details<br />
! Driver/Status<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Install xf86-video-intel<br />
|-<br />
| Wireless<br />
| ['''8804'''] Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br><br />
['''233g16n''']<br />
| Install iwlwifi-5000-ucode<br><br />
Install iwlwifi-1000-ucode<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Works out-of-box<br />
|-<br />
| Audio<br />
| Built-in speakers<br><br />
Headphone Jack<br><br />
Integrated Microphone<br><br />
Microphone Jack<br />
| Untested<br><br />
Manual Setup (see below)<br><br />
Untested<br><br />
Untested<br><br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader:<br />
MultiMediaCard™<br><br />
Secure Digital<br><br />
Memory Stick®<br><br />
Memory Stick PRO™<br><br />
xD-Picture Card™<br />
|<br />
Untested<br><br />
Works<br><br />
Untested<br><br />
Works<br><br />
Untested<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Works out-of-box<br />
|-<br />
| Touchpad<br />
| <br />
| Install xf86-input-evdev, xf86-input-synaptics<br />
|-<br />
| HDMI Out<br />
| <br />
| Works OOTB<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
<br />
If you are receiving errors booting or during the install, try setting the SATA mode to "IDE" in the BIOS. This is not necessary for all users.<br />
<br />
=== During the Installation ===<br />
Be sure to install the necessary wireless driver (see above), "wireless_tools", and optionally "netcfg" if you would like wireless to work post-install.<br />
<br />
=== Post-Install ===<br />
<br />
==== Setup the Touchpad ====<br />
<br />
Make sure to install xf86-input-synaptics. If you use HAL for Xorg hotplugging it will be autoloaded. Don't forget to enable the touchpad with <Fn>-F7. The following threads might also be interesting: [http://bbs.archlinux.org/viewtopic.php?id=77400] [http://bbs.archlinux.org/viewtopic.php?id=77190]<br />
<br />
==== Fan Issues ====<br />
<br />
If the noise is running too often or making too much noise, reading [http://ubuntuforums.org/showthread.php?p=8409272 this Ubuntu thread] may help.<br />
<br />
== Additional Links ==<br />
* [http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official US site]<br />
* [http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]<br />
* [http://forum.notebookreview.com/showthread.php?t=424213 Thread post containing specs of different models]<br />
* [http://forum.notebookreview.com/showthread.php?t=419117 Thread of tips, tricks, & tweaks]<br />
* [http://ubuntuforums.org/showthread.php?p=8409272 Power saving tips and tricks from Ubuntu forum]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=98742Acer Aspire 14102010-03-03T04:28:05Z<p>Bladesonfire: /* Specifications */</p>
<hr />
<div>[[Category:Acer (English)]]<br />
{{Stub}}<br />
This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Details<br />
! Driver/Status<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Install xf86-video-intel<br />
|-<br />
| Wireless<br />
| ['''8804'''] Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br><br />
['''233g16n''']<br />
| Install iwlwifi-5000-ucode<br><br />
Install iwlwifi-1000-ucode<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Works out-of-box<br />
|-<br />
| Audio<br />
| Built-in speakers<br><br />
Headphone Jack<br><br />
Integrated Microphone<br><br />
Microphone Jack<br />
| Untested<br><br />
Manual Setup (see below)<br><br />
Untested<br><br />
Untested<br><br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader:<br />
MultiMediaCard™<br><br />
Secure Digital<br><br />
Memory Stick®<br><br />
Memory Stick PRO™<br><br />
xD-Picture Card™<br />
|<br />
Untested<br><br />
Works<br><br />
Untested<br><br />
Works<br><br />
Untested<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Works out-of-box<br />
|-<br />
| Touchpad<br />
| <br />
| Install xf86-input-evdev, xf86-input-synaptics<br />
|-<br />
| HDMI Out<br />
| <br />
| Untested<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
<br />
If you are receiving errors booting or during the install, try setting the SATA mode to "IDE" in the BIOS. This is not necessary for all users.<br />
<br />
=== During the Installation ===<br />
Be sure to install the necessary wireless driver (see above), "wireless_tools", and optionally "netcfg" if you would like wireless to work post-install.<br />
<br />
=== Post-Install ===<br />
<br />
==== Setup the Touchpad ====<br />
<br />
Make sure to install xf86-input-synaptics. If you use HAL for Xorg hotplugging it will be autoloaded. Don't forget to enable the touchpad with <Fn>-F7. The following threads might also be interesting: [http://bbs.archlinux.org/viewtopic.php?id=77400] [http://bbs.archlinux.org/viewtopic.php?id=77190]<br />
<br />
== Additional Links ==<br />
* [http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official US site]<br />
* [http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]<br />
* [http://forum.notebookreview.com/showthread.php?t=424213 Thread post containing specs of different models]<br />
* [http://forum.notebookreview.com/showthread.php?t=419117 Thread of tips, tricks, & tweaks]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=98741Acer Aspire 14102010-03-03T04:27:28Z<p>Bladesonfire: /* Specifications */</p>
<hr />
<div>[[Category:Acer (English)]]<br />
{{Stub}}<br />
This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Details<br />
! Driver/Status<br />
|-<br />
| HDD<br />
| TOSHIBA MK2555GS 250GB<br />
| Works<br />
|-<br />
| Screen<br />
| Acer® CineCrystal 11.6" WXGA (1366 x 768) high-brightness (200-nit) TFT display with 16:9 aspect ratio and LED backlight <br />
| Works<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Install xf86-video-intel<br />
|-<br />
| Wireless<br />
| ['''8804'''] Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br><br />
['''233g16n''']<br />
| Install iwlwifi-5000-ucode<br><br />
Install iwlwifi-1000-ucode<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Works out-of-box<br />
|-<br />
| Audio<br />
| Built-in speakers<br><br />
Headphone Jack<br><br />
Integrated Microphone<br><br />
Microphone Jack<br />
| Untested<br><br />
Manual Setup (see below)<br><br />
Untested<br><br />
Untested<br><br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader:<br />
MultiMediaCard™<br><br />
Secure Digital<br><br />
Memory Stick®<br><br />
Memory Stick PRO™<br><br />
xD-Picture Card™<br />
|<br />
Untested<br><br />
Works<br><br />
Untested<br><br />
Works<br><br />
Untested<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Works out-of-box<br />
|-<br />
| Touchpad<br />
| <br />
| Install xf86-input-evdev, xf86-input-synaptics<br />
|-<br />
| HDMI Out<br />
| <br />
| Untested<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
<br />
If you are receiving errors booting or during the install, try setting the SATA mode to "IDE" in the BIOS. This is not necessary for all users.<br />
<br />
=== During the Installation ===<br />
Be sure to install the necessary wireless driver (see above), "wireless_tools", and optionally "netcfg" if you would like wireless to work post-install.<br />
<br />
=== Post-Install ===<br />
<br />
==== Setup the Touchpad ====<br />
<br />
Make sure to install xf86-input-synaptics. If you use HAL for Xorg hotplugging it will be autoloaded. Don't forget to enable the touchpad with <Fn>-F7. The following threads might also be interesting: [http://bbs.archlinux.org/viewtopic.php?id=77400] [http://bbs.archlinux.org/viewtopic.php?id=77190]<br />
<br />
== Additional Links ==<br />
* [http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official US site]<br />
* [http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]<br />
* [http://forum.notebookreview.com/showthread.php?t=424213 Thread post containing specs of different models]<br />
* [http://forum.notebookreview.com/showthread.php?t=419117 Thread of tips, tricks, & tweaks]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=98740Acer Aspire 14102010-03-03T03:58:26Z<p>Bladesonfire: /* Additional Links */ Added links</p>
<hr />
<div>[[Category:Acer (English)]]<br />
{{Stub}}<br />
This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Details<br />
! Driver/Status<br />
|-<br />
| HDD<br />
| TOSHIBA MK2555GS 250GB<br />
| Works<br />
|-<br />
| Screen<br />
| Acer® CineCrystal 11.6" WXGA (1366 x 768) high-brightness (200-nit) TFT display with 16:9 aspect ratio and LED backlight <br />
| Works<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Install xf86-video-intel<br />
|-<br />
| Wireless<br />
| ['''8804'''] Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br><br />
['''233g16n''']<br />
| Install iwlwifi-5000-ucode<br><br />
Install iwlwifi-1000-ucode<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Broken in latest kernel (see below)<br />
|-<br />
| Audio<br />
| Built-in speakers<br><br />
Headphone Jack<br><br />
Integrated Microphone<br><br />
Microphone Jack<br />
| Untested<br><br />
Manual Setup (see below)<br><br />
Untested<br><br />
Untested<br><br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader:<br />
MultiMediaCard™<br><br />
Secure Digital<br><br />
Memory Stick®<br><br />
Memory Stick PRO™<br><br />
xD-Picture Card™<br />
|<br />
Untested<br><br />
Works<br><br />
Untested<br><br />
Works<br><br />
Untested<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Works<br />
|-<br />
| Touchpad<br />
| <br />
| Install xf86-input-evdev, xf86-input-synaptics<br />
|-<br />
| HDMI Out<br />
| <br />
| Untested<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
<br />
If you are receiving errors booting or during the install, try setting the SATA mode to "IDE" in the BIOS. This is not necessary for all users.<br />
<br />
=== During the Installation ===<br />
Be sure to install the necessary wireless driver (see above), "wireless_tools", and optionally "netcfg" if you would like wireless to work post-install.<br />
<br />
=== Post-Install ===<br />
<br />
==== Setup the Touchpad ====<br />
<br />
Make sure to install xf86-input-synaptics. If you use HAL for Xorg hotplugging it will be autoloaded. Don't forget to enable the touchpad with <Fn>-F7. The following threads might also be interesting: [http://bbs.archlinux.org/viewtopic.php?id=77400] [http://bbs.archlinux.org/viewtopic.php?id=77190]<br />
<br />
== Additional Links ==<br />
* [http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official US site]<br />
* [http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]<br />
* [http://forum.notebookreview.com/showthread.php?t=424213 Thread post containing specs of different models]<br />
* [http://forum.notebookreview.com/showthread.php?t=419117 Thread of tips, tricks, & tweaks]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=98734Acer Aspire 14102010-03-03T02:28:25Z<p>Bladesonfire: /* Post-Install */ No longer necessary to build from source: alsa in extra is now version 1.0.22.1</p>
<hr />
<div>[[Category:Acer (English)]]<br />
{{Stub}}<br />
This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Details<br />
! Driver/Status<br />
|-<br />
| HDD<br />
| TOSHIBA MK2555GS 250GB<br />
| Works<br />
|-<br />
| Screen<br />
| Acer® CineCrystal 11.6" WXGA (1366 x 768) high-brightness (200-nit) TFT display with 16:9 aspect ratio and LED backlight <br />
| Works<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Install xf86-video-intel<br />
|-<br />
| Wireless<br />
| ['''8804'''] Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br><br />
['''233g16n''']<br />
| Install iwlwifi-5000-ucode<br><br />
Install iwlwifi-1000-ucode<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Broken in latest kernel (see below)<br />
|-<br />
| Audio<br />
| Built-in speakers<br><br />
Headphone Jack<br><br />
Integrated Microphone<br><br />
Microphone Jack<br />
| Untested<br><br />
Manual Setup (see below)<br><br />
Untested<br><br />
Untested<br><br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader:<br />
MultiMediaCard™<br><br />
Secure Digital<br><br />
Memory Stick®<br><br />
Memory Stick PRO™<br><br />
xD-Picture Card™<br />
|<br />
Untested<br><br />
Works<br><br />
Untested<br><br />
Works<br><br />
Untested<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Works<br />
|-<br />
| Touchpad<br />
| <br />
| Install xf86-input-evdev, xf86-input-synaptics<br />
|-<br />
| HDMI Out<br />
| <br />
| Untested<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
<br />
If you are receiving errors booting or during the install, try setting the SATA mode to "IDE" in the BIOS. This is not necessary for all users.<br />
<br />
=== During the Installation ===<br />
Be sure to install the necessary wireless driver (see above), "wireless_tools", and optionally "netcfg" if you would like wireless to work post-install.<br />
<br />
=== Post-Install ===<br />
<br />
==== Setup the Touchpad ====<br />
<br />
Make sure to install xf86-input-synaptics. If you use HAL for Xorg hotplugging it will be autoloaded. Don't forget to enable the touchpad with <Fn>-F7. The following threads might also be interesting: [http://bbs.archlinux.org/viewtopic.php?id=77400] [http://bbs.archlinux.org/viewtopic.php?id=77190]<br />
<br />
== Additional Links ==<br />
* [http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official Site]<br />
* [http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=98733Acer Aspire 14102010-03-03T02:14:11Z<p>Bladesonfire: </p>
<hr />
<div>[[Category:Acer (English)]]<br />
{{Stub}}<br />
This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Details<br />
! Driver/Status<br />
|-<br />
| HDD<br />
| TOSHIBA MK2555GS 250GB<br />
| Works<br />
|-<br />
| Screen<br />
| Acer® CineCrystal 11.6" WXGA (1366 x 768) high-brightness (200-nit) TFT display with 16:9 aspect ratio and LED backlight <br />
| Works<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Install xf86-video-intel<br />
|-<br />
| Wireless<br />
| ['''8804'''] Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br><br />
['''233g16n''']<br />
| Install iwlwifi-5000-ucode<br><br />
Install iwlwifi-1000-ucode<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Broken in latest kernel (see below)<br />
|-<br />
| Audio<br />
| Built-in speakers<br><br />
Headphone Jack<br><br />
Integrated Microphone<br><br />
Microphone Jack<br />
| Untested<br><br />
Manual Setup (see below)<br><br />
Untested<br><br />
Untested<br><br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader:<br />
MultiMediaCard™<br><br />
Secure Digital<br><br />
Memory Stick®<br><br />
Memory Stick PRO™<br><br />
xD-Picture Card™<br />
|<br />
Untested<br><br />
Works<br><br />
Untested<br><br />
Works<br><br />
Untested<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Works<br />
|-<br />
| Touchpad<br />
| <br />
| Install xf86-input-evdev, xf86-input-synaptics<br />
|-<br />
| HDMI Out<br />
| <br />
| Untested<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
<br />
If you are receiving errors booting or during the install, try setting the SATA mode to "IDE" in the BIOS. This is not necessary for all users.<br />
<br />
=== During the Installation ===<br />
Be sure to install the necessary wireless driver (see above), "wireless_tools", and optionally "netcfg" if you would like wireless to work post-install.<br />
<br />
=== Post-Install ===<br />
<br />
==== Setup the Internal Microphone ====<br />
Download the latest alsa driver from [http://www.alsa-project.org/main/index.php/Download Alsa Project Download Page].<br />
Untar the file<br />
tar -xjvf alsa-driver-1.0.22.1.tar.bz2<br />
Change directories<br />
cd alsa-driver-1.0.22<br />
Configure<br />
sh configure --prefix=/usr --with-cards=hda-intel<br />
Compile<br />
make<br />
Install<br />
sudo make install<br />
<br />
Reboot/reload your modules, run alsaconf and your mic should be good to go!<br />
<br />
==== Setup the touchpad ====<br />
Make sure to install xf86-input-synaptics. If you use HAL for Xorg hotplugging it will be autoloaded. Don't forget to enable the touchpad with <Fn>-F7. The following threads might also be interesting: [http://bbs.archlinux.org/viewtopic.php?id=77400] [http://bbs.archlinux.org/viewtopic.php?id=77190]<br />
<br />
== Additional Links ==<br />
* [http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official Site]<br />
* [http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=98732Acer Aspire 14102010-03-03T02:12:43Z<p>Bladesonfire: /* Package Installation */</p>
<hr />
<div>[[Category:Acer (English)]]<br />
{{Stub}}<br />
This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Details<br />
! Driver/Status<br />
|-<br />
| HDD<br />
| TOSHIBA MK2555GS 250GB<br />
| Works<br />
|-<br />
| Screen<br />
| Acer® CineCrystal 11.6" WXGA (1366 x 768) high-brightness (200-nit) TFT display with 16:9 aspect ratio and LED backlight <br />
| Works<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Install xf86-video-intel<br />
|-<br />
| Wireless<br />
| ['''8804'''] Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br><br />
['''233g16n''']<br />
| Install iwlwifi-5000-ucode<br><br />
Install iwlwifi-1000-ucode<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Broken in latest kernel (see below)<br />
|-<br />
| Audio<br />
| Built-in speakers<br><br />
Headphone Jack<br><br />
Integrated Microphone<br><br />
Microphone Jack<br />
| Untested<br><br />
Manual Setup (see below)<br><br />
Untested<br><br />
Untested<br><br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader:<br />
MultiMediaCard™<br><br />
Secure Digital<br><br />
Memory Stick®<br><br />
Memory Stick PRO™<br><br />
xD-Picture Card™<br />
|<br />
Untested<br><br />
Works<br><br />
Untested<br><br />
Works<br><br />
Untested<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Works<br />
|-<br />
| Touchpad<br />
| <br />
| Install xf86-input-evdev, xf86-input-synaptics<br />
|-<br />
| HDMI Out<br />
| <br />
| Untested<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
<br />
If you are receiving errors booting or during the install, try setting the SATA mode to "IDE" in the BIOS. This is not necessary for all users.<br />
<br />
=== During the Installation ===<br />
Be sure to install the necessary wireless driver (see above), "wireless_tools", and optionally "netcfg" if you would like wireless to work post-install.<br />
<br />
=== Setup the Internal Microphone ===<br />
Download the latest alsa driver from [http://www.alsa-project.org/main/index.php/Download Alsa Project Download Page].<br />
Untar the file<br />
tar -xjvf alsa-driver-1.0.22.1.tar.bz2<br />
Change directories<br />
cd alsa-driver-1.0.22<br />
Configure<br />
sh configure --prefix=/usr --with-cards=hda-intel<br />
Compile<br />
make<br />
Install<br />
sudo make install<br />
<br />
Reboot/reload your modules, run alsaconf and your mic should be good to go!<br />
<br />
=== Setup the touchpad ===<br />
Make sure to install xf86-input-synaptics. If you use HAL for Xorg hotplugging it will be autoloaded. Don't forget to enable the touchpad with <Fn>-F7. The following threads might also be interesting: [http://bbs.archlinux.org/viewtopic.php?id=77400] [http://bbs.archlinux.org/viewtopic.php?id=77190]<br />
<br />
== Additional Links ==<br />
* [http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official Site]<br />
* [http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=98731Acer Aspire 14102010-03-03T02:11:33Z<p>Bladesonfire: /* Pre-Install */</p>
<hr />
<div>[[Category:Acer (English)]]<br />
{{Stub}}<br />
This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Details<br />
! Driver/Status<br />
|-<br />
| HDD<br />
| TOSHIBA MK2555GS 250GB<br />
| Works<br />
|-<br />
| Screen<br />
| Acer® CineCrystal 11.6" WXGA (1366 x 768) high-brightness (200-nit) TFT display with 16:9 aspect ratio and LED backlight <br />
| Works<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Install xf86-video-intel<br />
|-<br />
| Wireless<br />
| ['''8804'''] Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br><br />
['''233g16n''']<br />
| Install iwlwifi-5000-ucode<br><br />
Install iwlwifi-1000-ucode<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Broken in latest kernel (see below)<br />
|-<br />
| Audio<br />
| Built-in speakers<br><br />
Headphone Jack<br><br />
Integrated Microphone<br><br />
Microphone Jack<br />
| Untested<br><br />
Manual Setup (see below)<br><br />
Untested<br><br />
Untested<br><br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader:<br />
MultiMediaCard™<br><br />
Secure Digital<br><br />
Memory Stick®<br><br />
Memory Stick PRO™<br><br />
xD-Picture Card™<br />
|<br />
Untested<br><br />
Works<br><br />
Untested<br><br />
Works<br><br />
Untested<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Works<br />
|-<br />
| Touchpad<br />
| <br />
| Install xf86-input-evdev, xf86-input-synaptics<br />
|-<br />
| HDMI Out<br />
| <br />
| Untested<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
<br />
If you are receiving errors booting or during the install, try setting the SATA mode to "IDE" in the BIOS. This is not necessary for all users.<br />
<br />
=== Package Installation ===<br />
Be sure to install "iwlwifi-5000-ucode" and "wireless_tools" (I also installed "netcfg") if you would like wireless to work post-install.<br />
<br />
=== Setup the Internal Microphone ===<br />
Download the latest alsa driver from [http://www.alsa-project.org/main/index.php/Download Alsa Project Download Page].<br />
Untar the file<br />
tar -xjvf alsa-driver-1.0.22.1.tar.bz2<br />
Change directories<br />
cd alsa-driver-1.0.22<br />
Configure<br />
sh configure --prefix=/usr --with-cards=hda-intel<br />
Compile<br />
make<br />
Install<br />
sudo make install<br />
<br />
Reboot/reload your modules, run alsaconf and your mic should be good to go!<br />
<br />
=== Setup the touchpad ===<br />
Make sure to install xf86-input-synaptics. If you use HAL for Xorg hotplugging it will be autoloaded. Don't forget to enable the touchpad with <Fn>-F7. The following threads might also be interesting: [http://bbs.archlinux.org/viewtopic.php?id=77400] [http://bbs.archlinux.org/viewtopic.php?id=77190]<br />
<br />
== Additional Links ==<br />
* [http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official Site]<br />
* [http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=98730Acer Aspire 14102010-03-03T02:06:50Z<p>Bladesonfire: /* Specifications */</p>
<hr />
<div>[[Category:Acer (English)]]<br />
{{Stub}}<br />
This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Details<br />
! Driver/Status<br />
|-<br />
| HDD<br />
| TOSHIBA MK2555GS 250GB<br />
| Works<br />
|-<br />
| Screen<br />
| Acer® CineCrystal 11.6" WXGA (1366 x 768) high-brightness (200-nit) TFT display with 16:9 aspect ratio and LED backlight <br />
| Works<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Install xf86-video-intel<br />
|-<br />
| Wireless<br />
| ['''8804'''] Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br><br />
['''233g16n''']<br />
| Install iwlwifi-5000-ucode<br><br />
Install iwlwifi-1000-ucode<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Broken in latest kernel (see below)<br />
|-<br />
| Audio<br />
| Built-in speakers<br><br />
Headphone Jack<br><br />
Integrated Microphone<br><br />
Microphone Jack<br />
| Untested<br><br />
Manual Setup (see below)<br><br />
Untested<br><br />
Untested<br><br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader:<br />
MultiMediaCard™<br><br />
Secure Digital<br><br />
Memory Stick®<br><br />
Memory Stick PRO™<br><br />
xD-Picture Card™<br />
|<br />
Untested<br><br />
Works<br><br />
Untested<br><br />
Works<br><br />
Untested<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Works<br />
|-<br />
| Touchpad<br />
| <br />
| Install xf86-input-evdev, xf86-input-synaptics<br />
|-<br />
| HDMI Out<br />
| <br />
| Untested<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
Before you install Arch, ensure that the SATA mode is set to "IDE" in the BIOS. This will resolve the hard drive error messages.<br />
<br />
----<br />
This wasn't necessary for my Aspire 1410.<br />
<br />
=== Package Installation ===<br />
Be sure to install "iwlwifi-5000-ucode" and "wireless_tools" (I also installed "netcfg") if you would like wireless to work post-install.<br />
<br />
=== Setup the Internal Microphone ===<br />
Download the latest alsa driver from [http://www.alsa-project.org/main/index.php/Download Alsa Project Download Page].<br />
Untar the file<br />
tar -xjvf alsa-driver-1.0.22.1.tar.bz2<br />
Change directories<br />
cd alsa-driver-1.0.22<br />
Configure<br />
sh configure --prefix=/usr --with-cards=hda-intel<br />
Compile<br />
make<br />
Install<br />
sudo make install<br />
<br />
Reboot/reload your modules, run alsaconf and your mic should be good to go!<br />
<br />
=== Setup the touchpad ===<br />
Make sure to install xf86-input-synaptics. If you use HAL for Xorg hotplugging it will be autoloaded. Don't forget to enable the touchpad with <Fn>-F7. The following threads might also be interesting: [http://bbs.archlinux.org/viewtopic.php?id=77400] [http://bbs.archlinux.org/viewtopic.php?id=77190]<br />
<br />
== Additional Links ==<br />
* [http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official Site]<br />
* [http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=76718Acer Aspire 14102009-09-28T06:33:44Z<p>Bladesonfire: /* Specifications */</p>
<hr />
<div>This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Details<br />
! Status<br />
|-<br />
| HDD<br />
| TOSHIBA MK2555GS 250GB<br />
| Works<br />
|-<br />
| Screen<br />
| Acer® CineCrystal 11.6" WXGA (1366 x 768) high-brightness (200-nit) TFT display with 16:9 aspect ratio and LED backlight <br />
| Works<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Works<br />
|-<br />
| Wireless<br />
| Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br />
| Works (install driver)<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Does not work<br />
|-<br />
| Audio<br />
| Headphones/speaker/line-out with SPDIF support and microphone ports <br />
Integrated microphone <br />
| Untested<br />
Untested<br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader supports optional MultiMediaCard™, Secure Digital card, Memory Stick®, Memory Stick PRO™ or xD-Picture Card™<br />
| Works (SD/MS Pro tested)<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Works<br />
|-<br />
| Touchpad<br />
| <br />
| Works (modify Xorg.conf)<br />
|-<br />
| HDMI Out<br />
| <br />
| Untested<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
Before you install Arch, ensure that the SATA mode is set to "IDE" in the BIOS. This will resolve the hard drive error messages.<br />
<br />
=== Package Installation ===<br />
Be sure to install "iwlwifi-5000-ucode" and "wireless_tools" (I also installed "netcfg") if you would like wireless to work post-install.<br />
<br />
<br />
== Additional Links ==<br />
* [http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official Site]<br />
* [http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=76717Acer Aspire 14102009-09-28T06:32:10Z<p>Bladesonfire: </p>
<hr />
<div>This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Manufacturer<br />
! Status<br />
|-<br />
| HDD<br />
| TOSHIBA MK2555GS 250GB<br />
| Works<br />
|-<br />
| Screen<br />
| Acer® CineCrystal 11.6" WXGA (1366 x 768) high-brightness (200-nit) TFT display with 16:9 aspect ratio and LED backlight <br />
| Works<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Works<br />
|-<br />
| Wireless<br />
| Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br />
| Works (install driver)<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Does not work<br />
|-<br />
| Audio<br />
| Headphones/speaker/line-out with SPDIF support and microphone ports <br />
Integrated microphone <br />
| Untested<br />
Untested<br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader supports optional MultiMediaCard™, Secure Digital card, Memory Stick®, Memory Stick PRO™ or xD-Picture Card™<br />
| Works (SD/MS Pro tested)<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Works<br />
|-<br />
| Touchpad<br />
| <br />
| Works (modify Xorg.conf)<br />
|-<br />
| HDMI Out<br />
| <br />
| Untested<br />
|}<br />
<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
Before you install Arch, ensure that the SATA mode is set to "IDE" in the BIOS. This will resolve the hard drive error messages.<br />
<br />
=== Package Installation ===<br />
Be sure to install "iwlwifi-5000-ucode" and "wireless_tools" (I also installed "netcfg") if you would like wireless to work post-install.<br />
<br />
<br />
== Additional Links ==<br />
* [http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official Site]<br />
* [http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=76716Acer Aspire 14102009-09-28T06:29:43Z<p>Bladesonfire: /* Additional Links */</p>
<hr />
<div>This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Manufacturer<br />
! Status<br />
|-<br />
| HDD<br />
| TOSHIBA MK2555GS 250GB<br />
| Works<br />
|-<br />
| Screen<br />
| Acer® CineCrystal 11.6" WXGA (1366 x 768) high-brightness (200-nit) TFT display with 16:9 aspect ratio and LED backlight <br />
| Works<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Works<br />
|-<br />
| Wireless<br />
| Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br />
| Works (install driver)<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Does not work<br />
|-<br />
| Audio<br />
| Headphones/speaker/line-out with SPDIF support and microphone ports <br />
Integrated microphone <br />
| Untested<br />
Untested<br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader supports optional MultiMediaCard™, Secure Digital card, Memory Stick®, Memory Stick PRO™ or xD-Picture Card™<br />
| Works (SD/MS Pro tested)<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Works<br />
|-<br />
| Touchpad<br />
| <br />
| Works (modify Xorg.conf)<br />
|-<br />
| HDMI Out<br />
| <br />
| Untested<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
Before you install Arch, ensure that the SATA mode is set to "IDE" in the BIOS. This will resolve the hard drive error messages.<br />
<br />
=== Package Installation ===<br />
Be sure to install "iwlwifi-5000-ucode" and "wireless_tools" (I also installed "netcfg") if you would like wireless to work post-install.<br />
<br />
<br />
<br />
== Additional Links ==<br />
* [http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official Site]<br />
* [http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=76714Acer Aspire 14102009-09-28T06:25:20Z<p>Bladesonfire: /* Specifications */</p>
<hr />
<div>This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Manufacturer<br />
! Status<br />
|-<br />
| HDD<br />
| TOSHIBA MK2555GS 250GB<br />
| Works<br />
|-<br />
| Screen<br />
| Acer® CineCrystal 11.6" WXGA (1366 x 768) high-brightness (200-nit) TFT display with 16:9 aspect ratio and LED backlight <br />
| Works<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Works<br />
|-<br />
| Wireless<br />
| Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br />
| Works (install driver)<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Does not work<br />
|-<br />
| Audio<br />
| Headphones/speaker/line-out with SPDIF support and microphone ports <br />
Integrated microphone <br />
| Untested<br />
Untested<br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader supports optional MultiMediaCard™, Secure Digital card, Memory Stick®, Memory Stick PRO™ or xD-Picture Card™<br />
| Works (SD/MS Pro tested)<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Works<br />
|-<br />
| Touchpad<br />
| <br />
| Works (modify Xorg.conf)<br />
|-<br />
| HDMI Out<br />
| <br />
| Untested<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
Before you install Arch, ensure that the SATA mode is set to "IDE" in the BIOS. This will resolve the hard drive error messages.<br />
<br />
=== Package Installation ===<br />
Be sure to install "iwlwifi-5000-ucode" and "wireless_tools" (I also installed "netcfg") if you would like wireless to work post-install.<br />
<br />
<br />
<br />
== Additional Links ==<br />
[http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official Site]<br />
[http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=76713Acer Aspire 14102009-09-28T06:22:17Z<p>Bladesonfire: /* Specifications */</p>
<hr />
<div>This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Manufacturer<br />
! Status<br />
|-<br />
| HDD<br />
| TOSHIBA MK2555GS 250GB<br />
| Works<br />
|-<br />
| Screen<br />
| Acer® CineCrystal 11.6" WXGA (1366 x 768) high-brightness (200-nit) TFT display with 16:9 aspect ratio and LED backlight <br />
| Works<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Works<br />
|-<br />
| Wireless<br />
| Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br />
| Works (install driver)<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Does not work<br />
|-<br />
| Audio<br />
| Headphones/speaker/line-out with SPDIF support and microphone ports <br />
Integrated microphone <br />
| Untested<br />
Untested<br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader supports optional MultiMediaCard™, Secure Digital card, Memory Stick®, Memory Stick PRO™ or xD-Picture Card™<br />
| Works (SD tested)<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Works<br />
|-<br />
| Touchpad<br />
| <br />
| Works (modify Xorg.conf)<br />
|-<br />
| HDMI Out<br />
| <br />
| Untested<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
Before you install Arch, ensure that the SATA mode is set to "IDE" in the BIOS. This will resolve the hard drive error messages.<br />
<br />
=== Package Installation ===<br />
Be sure to install "iwlwifi-5000-ucode" and "wireless_tools" (I also installed "netcfg") if you would like wireless to work post-install.<br />
<br />
<br />
<br />
== Additional Links ==<br />
[http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official Site]<br />
[http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=76711Acer Aspire 14102009-09-28T06:20:07Z<p>Bladesonfire: /* Specifications */</p>
<hr />
<div>This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Manufacturer<br />
! Status<br />
|-<br />
| HDD<br />
| TOSHIBA MK2555GS 250GB<br />
| Works<br />
|-<br />
| Screen<br />
| Acer® CineCrystal 11.6" WXGA (1366 x 768) high-brightness (200-nit) TFT display with 16:9 aspect ratio and LED backlight <br />
| Works<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Works<br />
|-<br />
| Wireless<br />
| Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br />
| Works (install driver)<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Does not work<br />
|-<br />
| Audio<br />
| Headphones/speaker/line-out with SPDIF support and microphone ports <br />
Integrated microphone <br />
| Untested<br />
Untested<br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader supports optional MultiMediaCard™, Secure Digital card, Memory Stick®, Memory Stick PRO™ or xD-Picture Card™<br />
| Untested<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Works<br />
|-<br />
| Touchpad<br />
| <br />
| Works (modify Xorg.conf)<br />
|-<br />
| HDMI Out<br />
| <br />
| Untested<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
Before you install Arch, ensure that the SATA mode is set to "IDE" in the BIOS. This will resolve the hard drive error messages.<br />
<br />
=== Package Installation ===<br />
Be sure to install "iwlwifi-5000-ucode" and "wireless_tools" (I also installed "netcfg") if you would like wireless to work post-install.<br />
<br />
<br />
<br />
== Additional Links ==<br />
[http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official Site]<br />
[http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=76709Acer Aspire 14102009-09-28T06:19:43Z<p>Bladesonfire: /* Specifications */</p>
<hr />
<div>This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Manufacturer<br />
! Status<br />
|-<br />
| HDD<br />
| TOSHIBA MK2555GS 250GB<br />
| Works<br />
|-<br />
| Screen<br />
| Acer® CineCrystal 11.6" WXGA (1366 x 768) high-brightness (200-nit) TFT display with 16:9 aspect ratio and LED backlight <br />
| Works<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Works<br />
|-<br />
| Wireless<br />
| Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br />
| Works (install driver)<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Does not work<br />
|-<br />
| Audio<br />
| Headphones/speaker/line-out with SPDIF support and microphone ports <br />
Integrated microphone <br />
| Untested<br />
Untested<br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader supports optional MultiMediaCard™, Secure Digital card, Memory Stick®, Memory Stick PRO™ or xD-Picture Card™<br />
| Untested<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Works<br />
|-<br />
| Touchpad<br />
| <br />
| Untested<br />
|-<br />
| HDMI Out<br />
| <br />
| Untested<br />
|}<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
Before you install Arch, ensure that the SATA mode is set to "IDE" in the BIOS. This will resolve the hard drive error messages.<br />
<br />
=== Package Installation ===<br />
Be sure to install "iwlwifi-5000-ucode" and "wireless_tools" (I also installed "netcfg") if you would like wireless to work post-install.<br />
<br />
<br />
<br />
== Additional Links ==<br />
[http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official Site]<br />
[http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=76705Acer Aspire 14102009-09-27T23:50:49Z<p>Bladesonfire: </p>
<hr />
<div>This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. Here is the (albeit empty) forum post for discussion: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
== Summary ==<br />
<br />
=== Specifications ===<br />
<br />
{| border="1"<br />
|-<br />
! Hardware<br />
! Manufacturer<br />
! Status<br />
|-<br />
| HDD<br />
| TOSHIBA MK2555GS 250GB<br />
| Works<br />
|-<br />
| Screen<br />
| Acer® CineCrystal 11.6" WXGA (1366 x 768) high-brightness (200-nit) TFT display with 16:9 aspect ratio and LED backlight <br />
| Works<br />
|-<br />
| Graphics<br />
| Integrated Intel® Graphics Media Accelerator 4500MHD<br />
| Works<br />
|-<br />
| Wireless<br />
| Intel WiFi Link 5100 802.11a/b/g/Draft-N Wireless<br />
| Works<br />
|-<br />
| Ethernet<br />
| Attansic Technology Gigabit Ethernet<br />
| Does not work<br />
|-<br />
| Audio<br />
| Headphones/speaker/line-out with SPDIF support and microphone ports <br />
Integrated microphone <br />
| Untested<br />
Untested<br />
|-<br />
| Card Reader<br />
| 5-in-1 card reader supports optional MultiMediaCard™, Secure Digital card, Memory Stick®, Memory Stick PRO™ or xD-Picture Card™<br />
| Untested<br />
|-<br />
| Webcam<br />
| Chicony Electronics Co. Ltd<br />
| Untested<br />
|-<br />
| Touchpad<br />
| <br />
| Untested<br />
|-<br />
| HDMI Out<br />
| <br />
| Untested<br />
|}<br />
<br />
<br />
== Installing Arch ==<br />
<br />
=== Pre-Install ===<br />
Before you install Arch, ensure that the SATA mode is set to "IDE" in the BIOS. This will resolve the hard drive error messages.<br />
<br />
=== Package Installation ===<br />
Be sure to install "iwlwifi-5000-ucode" and "wireless_tools" (I also installed "netcfg") if you would like wireless to work post-install.<br />
<br />
<br />
<br />
== Additional Links ==<br />
[http://us.acer.com/acer/productv.do?LanguageISOCtxParam=en&kcond61e.c2att101=63750&sp=page16e&ctx2.c2att1=25&link=ln438e&CountryISOCtxParam=US&ctx1g.c2att92=447&ctx1.att21k=1&CRC=1346651341 Official Site]<br />
[http://www.linlap.com/wiki/acer+aspire+1410 Linux Laptop]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=76704Acer Aspire 14102009-09-27T22:05:35Z<p>Bladesonfire: /* Pre-Install */</p>
<hr />
<div>This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. For now, please visit the forum post for information: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
= Installing Arch =<br />
<br />
== Pre-Install ==<br />
<br />
Before you install Arch, ensure that the SATA mode is set to "IDE" in the BIOS. This will resolve the hard drive error messages.<br />
<br />
== Package Installation ==<br />
<br />
Be sure to install "iwlwifi-5000-ucode" and "wireless_tools" (I also installed "netcfg") if you would like wireless to work post-install.</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=76703Acer Aspire 14102009-09-27T22:05:15Z<p>Bladesonfire: </p>
<hr />
<div>This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. For now, please visit the forum post for information: http://bbs.archlinux.org/viewtopic.php?pid=626296<br />
<br />
= Installing Arch =<br />
<br />
== Pre-Install ==<br />
<br />
Before you install, ensure that the SATA mode is set to "IDE" in the BIOS. This will resolve the hard drive error messages.<br />
<br />
== Package Installation ==<br />
<br />
Be sure to install "iwlwifi-5000-ucode" and "wireless_tools" (I also installed "netcfg") if you would like wireless to work post-install.</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=76617Acer Aspire 14102009-09-26T18:10:53Z<p>Bladesonfire: </p>
<hr />
<div>This page will eventually hold information to install Arch Linux on the Acer Aspire 1410. For now, please visit the forum post for information: http://bbs.archlinux.org/viewtopic.php?pid=626296</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Acer_Aspire_1410&diff=76616Acer Aspire 14102009-09-26T18:09:43Z<p>Bladesonfire: Created page with 'This page will eventually hold information to install Arch Linux on the Acer Aspire 1410.'</p>
<hr />
<div>This page will eventually hold information to install Arch Linux on the Acer Aspire 1410.</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_701&diff=43583ASUS Eee PC 7012008-06-23T19:42:19Z<p>Bladesonfire: /* Choosing Your Installation Media */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
'''WARNING: THIS ARTICLE IS INCOMPLETE!''' Visit the Arch forum thread link below to get information on installing Arch Linux on the Asus EEE PC. <br />
<br />
Most of this information is from the [http://bbs.archlinux.org/viewtopic.php?pid=297632 Arch Forum]. You can also find a lot of helpful information from the [http://forum.eeeuser.com/ EEEUser Forum]. There is also a nice Arch Linux installation guide on the [http://wiki.eeeuser.com/installingarchlinux EeeUser Wiki].<br />
<br />
==Before You Begin==<br />
<br />
===Avoiding Pitfalls===<br />
<br />
The install is pretty normal, except that you'll need to [http://forum.eeeuser.com/viewtopic.php?id=890 avoid the pitfalls] of our alternative Linux install:<br />
<br />
# Never choose to use a journaling file system on the SSD partitions<br />
# Never use a swap partition on the SSD<br />
# Edit your new installation fstab to mount the SSD partitions "noatime"<br />
# Never log messages or error log to the SSD<br />
<br />
The rules ensure that we won't reach the maximum limit of writes on our SSD faster than we should.<br />
<br />
===Choosing Your Installation Media===<br />
<br />
The EEE PC does not have an optical drive installed on the machine. This means you will need to install Arch Linux through one of the alternative methods:<br />
<br />
# External USB CD-ROM drive<br />
# [[Install_from_USB_stick|USB pen drive]] (Recommended)<br />
<br />
==Installing Arch Linux==<br />
<br />
Note: if you're using the USB pen drive as your media, then [[Install_from_USB_stick#After_booting_from_the_USB_stick:|follow these instructions]] to create the installation USB stick.<br />
<br />
===Download the necessary drivers/modules/patches===<br />
<br />
Since the stock kernel doesn't supports either the Eee ethernet or wireless network cards, you might want to download the ethernet or wireless drivers/modules that you need and copy them to the installation USB stick.<br />
<br />
*You can download ethernet driver source from [http://people.redhat.com/csnook/atl2/ here].<br />
*Wireless driver can be downloaded from [http://snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2756-20071018.tar.gz here]. <br />
**The wireless driver requires a patch to make it work with the Eee PC. The patch can be download from [http://madwifi.org/attachment/ticket/1679/madwifi-ng-0933.ar2425.20071130.i386.patch?format=raw here]<br />
<br />
*If you want to use dkite's eeemodules package, you should download the package from his [http://members.shaw.ca/dkite website] and put it on USB for ease of installing. Especially important is the '''eeemodules-2.6.22.9-1-i686.pkg.tar.gz''', because we will need to install this package after installation for wireless and ethernet to work.<br />
<br />
*for anyone who read this wiki previously and wondered where the patched kernel download went; the latest arch kernel contains the patch that fixes the intel graphics vsync hardlock error, so no additional configuration need be done<br />
<br />
===Booting Arch the installation CD/USB===<br />
<br />
Please refer to The [[Beginners_Guide]] for detailed instructions, if needed. Ideally, your CD/USB should boot up just fine on Eee PC without any need for additional options.<br />
<br />
===Start the Installation===<br />
<br />
If you are installing from the USB, then issue<br />
<br />
mount /dev/sd[x] /src<br />
<br />
To mount the usb.<br />
<br />
Then just run<br />
<br />
/arch/setup<br />
<br />
To start the installation just like normal.<br />
<br />
===Prepare Hard Drive===<br />
<br />
The default Eee PC drive is split up into four partitions (here is [http://forum.eeeuser.com/viewtopic.php?id=1805 some information] about the partitioning): <br />
<br />
* It is easiest to wipe the existing partitions and use one or two partitions for your install. One partition would be just '/', and two partitions would be '/boot' and '/'.<br />
* Choose "NONE" for swap (see #2 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
* Select "ext2" as your filesystem (see #1 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
<br />
===Select Packages===<br />
<br />
If you are installing from USB, then choose SRC as your source.<br />
<br />
In addition to the '''BASE''' category, we also need all the packages in the '''DEVEL''' category for compiling our ethernet/wireless drivers.<br />
<br />
If you intended to use wireless, then you'll also need the ''wireless_tools'' package from '''SUPPORT''' category.<br />
<br />
===Configure System===<br />
<br />
Edit /etc/rc.conf and add asus_acpi to the MODULES array:<br />
<br />
MODULES = (... asus_acpi ...) <br />
<br />
Arch will complain about this, pay no attention to the error message because once we install the patched version of asus_acpi module using dkite's package, the error message will disappear.<br />
<br />
Make these edits to "/etc/fstab":<br />
<br />
* Add "noatime" to the options of your mounts (see #3 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
* '''(OPTIONAL)''' Add a new line: "tmpfs /var/log tmpfs size=1M 0 0" (WARNING: this will delete all your logs! See #4 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
** To save your startup/shutdown logs, look at the pitfalls link above.<br />
<br />
===Install Network Adapter Drivers===<br />
<br />
===== Build from sources =====<br />
Update: the atl2 ethernet is support by Arch Linux's stock kernel as of 2008.03<br />
<br />
After the installation, The first thing you will noticed after booting into your newly installed Arch Linux is that the network adapters (both ethernet and wireless) are not working. To install the drivers, mount the USB stick that contains the drivers by issues the following commands:<br />
<br />
mkdir /mnt/usb<br />
mount /dev/sd[x] /mnt/usb<br />
<br />
Then follow the following instructions to install your network driver.<br />
<br />
======Atl2 ethernet driver======<br />
<br />
You can download ethernet driver source from [http://people.redhat.com/csnook/atl2/ here].<br />
<br />
Extract the sources. You may need to modify the kernel version listed in the Makefile.<br />
<br />
make clean<br />
make<br />
cp atl2.ko /lib/modules/2.6.24-ARCH/kernel/drivers/net # Change 2.6.24 as needed<br />
depmod<br />
<br />
======Atheros wireless ethernet driver======<br />
<br />
Instructions from http://wiki.eeeuser.com/ubuntu#wireless_internet_using_native_madwifi_drivers to patch madwifi. This replaces the Arch madwifi packages.<br />
<br />
wget 'http://madwifi.org/attachment/ticket/1679/madwifi-ng-0933.ar2425.20071130.i386.patch?format=raw'<br />
wget http://snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2756-20071018.tar.gz<br />
tar zxvf madwifi-ng-r2756-20071018.tar.gz<br />
cd madwifi-ng-r2756-20071018<br />
patch -p0 < ../madwifi-ng-0933.ar2425.20071130.i386.patch<br />
make clean<br />
make<br />
sudo make install<br />
<br />
If you have already downloaded both the driver source & the patch and have moved them into the USB, then both move the driver source & the patch into the same directory and issues the following command:<br />
<br />
tar zxvf madwifi-ng-r2756-20071018.tar.gz<br />
cd madwifi-ng-r2756-20071018<br />
patch -p0 < ../madwifi-ng-0933.ar2425.20071130.i386.patch<br />
make clean<br />
make<br />
sudo make install<br />
<br />
Working against stock kernel.<br />
<br />
=====Install wireless and ethernet drivers using dkite's eeemodules Package=====<br />
<br />
Another way to install both wireless and ethernet drivers/modules, instate of having to build and install the drivers/modules yourself, is to use dkite's eeemodules Package, which included both wireless and ethernet drivers/modules, among other things.<br />
<br />
Since Don't Panic installation CD comes with kernel version 2.6.22.9, we will need to use '''eeemodules-2.6.22.9-1-i686.pkg.tar.gz''' package, which you can get from [http://members.shaw.ca/dkite his website], if you haven't got it already.<br />
<br />
Mount the USB that contains the package and install it with this command:<br />
<br />
pacman -Uf eeemodules-2.6.22.9-1-i686.pkg.tar.gz<br />
<br />
Then load the modules with<br />
<br />
depmod<br />
<br />
Restart and now you should have a working wireless/ethernet connection.<br />
<br />
====Install All the Necessary Modules====<br />
<br />
After you have installed and configured the driver, proceed to upgrade the system with pacman -Syu command. After the upgrade is complete, it is the time to decide which methods you would like to use to install the modules:<br />
<br />
'''ATTENTION:''' Do ''NOT'' restart after upgrade the system and before you install the modules using one of the following methods, or your hardware (wifi, ethernet, etc.) ''WILL'' stop functioning.<br />
<br />
'''dkite''' have created a package that contains all the necessary modules for wifi, ethernet connection, acpi and video camera hardware that comes with the Eee PC. His package is to be use with the stock kernel. <br />
<br />
The following is the list of hardware/functions that are known to work with dkite's eeemodules Package:<br />
<br />
*Wireless <br />
*Ethernet <br />
*Webcam <br />
*Suspend/Resume<br />
<br />
You can get the package [http://members.shaw.ca/dkite from his website]. <br />
<br />
Currently there are three pre-complied package:<br />
<br />
#'''eeemodules-2.6.22.9-1-i686.pkg.tar.gz''' for use with Don't Panic kernel.<br />
#'''eeemodules-0.0.3-2.6.24.1.2-i686.pkg.tar.gz''' for the 2.6.24.14-2 kernel.<br />
<br />
If you have newer or other version of kernel26, then you will need to download '''eeemodules.tar.gz''', which contains PKGBUILD and all the necessary files, and build the package yourself. <br />
<br />
*'''ATTENTION:''' You will also need to rebuild the package, using eeemodules.tar.gz, every time you upgrade your kernel, or else your hardware (wifi, ethernet, etc.) will stop functioning.<br />
<br />
=====Installation Instructions=====<br />
<br />
Install the package with the following command:<br />
<br />
pacman -Uf eeemodules-<pkgver>.tar.gz<br />
<br />
Then run a depmod command:<br />
<br />
depmod<br />
<br />
'''Attention:''' Do ''not'' forget to run the depmod command after installing the package, otherwise your hardware won't function! <br />
<br />
If you want to use the webcam then you might also need to load the asus_acpi module. Edit the /etc/rc.conf file and insert asus_acpi into MODULES array:<br />
<br />
MODULES = (... asus_acpi ...)<br />
<br />
====Eee repository from toofishes====<br />
toofishes created a repository for the eee. You can find some basic packages like Pentium-M-optimized kernel and needed modules. Add<br />
[eee]<br />
Server = http://code.toofishes.net/packages/eee<br />
to your /etc/pacman.conf to use the repository.<br />
<br />
=====Package List=====<br />
<br />
Currently, toofishes' repository contains the following packages:<br />
<br />
*'''kernel-eee''' <br />
customized kernel for Eee<br />
*'''linux-uvc-eee-svn''' <br />
webcam driver for Eee<br />
*'''luvcview''' <br />
webcam program for testing webcam driver<br />
*'''madwifi-eee-svn''' <br />
wifi driver for Eee<br />
*'''eeepc-linux''' <br />
kernel module to change Eee's FSB speed and fan control<br />
<br />
=====Installation Instruction=====<br />
<br />
Simply use pacman to install the package that you need. For a working system, you'll need at least 3 packages: kernel-eee (the kernel), linux-uvc-eee-svn (webcam driver) and madwifi-eee-svn (the wifi driver).<br />
<br />
Install the packages with this command:<br />
<br />
pacman -Sy kernel-eee linux-uvc-eee-svn madwifi-eee-svn<br />
<br />
'''ATTENTION:''' dkite's eeemodules package conflicts with the madwifi-eee-svn package. You need to remove dkite's eeemodules package before you can install toofishes madfwifi-eee-svn package.<br />
<br />
Then, add the following to /boot/grub/menu.lst; note that no initrd is needed:<br />
# (2) Arch Linux<br />
title Arch Linux EEE kernel<br />
root (hd0,0)<br />
kernel /boot/vmlinuzeee root=/dev/sda1 ro<br />
<br />
Restart and select Arch Linux EEE kernel from the grub boot menu.<br />
<br />
==Getting Everything Working==<br />
<br />
By now, you should have Arch installed. The following is the guide on how to get the rest of your system working.<br />
<br />
===Xorg===<br />
<br />
You have two choices for video on the Eee- the newer <b>xf86-video-intel</b> driver, or the older <b>xf86-video-i810</b> driver paired with 915resolution. Unless there is a compelling reason to use the i810 driver, the intel driver is the focus upstream and is being actively developed so it is your best choice.<br />
<br />
You need these packages in addition to the Xorg's packages:<br />
<br />
pacman -Sy synaptics xf86-video-intel<br />
<br />
If you choose to use the older i180 video, you will have to install xf86-video-i810 and 915resolution as well. Note that the i180 driver and the intel driver cannot both be installed at the same time.<br />
<br />
Then, just drop in the following xorg.conf into your /etc/X11/ directory:<br />
<br />
<pre>Section "ServerLayout"<br />
Identifier "ArchLinux"<br />
Screen 0 "Screen0"<br />
InputDevice "keyboard"<br />
InputDevice "mouse"<br />
InputDevice "synaptics"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/usr/share/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/100dpi:unscaled"<br />
FontPath "/usr/share/fonts/75dpi:unscaled"<br />
FontPath "/usr/share/fonts/TTF"<br />
FontPath "/usr/share/fonts/Type1"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "glx"<br />
Load "dri"<br />
Load "extmod"<br />
Load "synaptics"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AllowMouseOpenFail"<br />
Option "BlankTime" "5"<br />
Option "AIGLX" "false"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "keyboard"<br />
Driver "kbd"<br />
Option "CoreKeyboard"<br />
Option "XkbRules" "xorg"<br />
Option "XkbLayout" "us"<br />
Option "XkbVariant" ""<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "mouse"<br />
Driver "mouse"<br />
Option "Device" "/dev/input/mice"<br />
Option "Protocol" "IMPS/2"<br />
Option "Emulate3Buttons" "yes"<br />
Option "ZAxisMapping" "4 5"<br />
Option "CorePointer"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "synaptics"<br />
Driver "synaptics"<br />
Option "Device" "/dev/psaux"<br />
Option "Protocol" "auto-dev"<br />
Option "LeftEdge" "1000"<br />
Option "RightEdge" "5400"<br />
Option "TopEdge" "1000"<br />
Option "BottomEdge" "4900"<br />
Option "PalmDetect" "0"<br />
Option "SHMConfig" "true"<br />
Option "SendCoreEvents" "yes" <br />
Option "HorizScrollDelta" "0" <br />
Option "RBCornerButton" "0"<br />
Option "RTCornerButtom" "0"<br />
Option "MaxSpeed" "0.1"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "ASUS"<br />
ModelName "eeePC P701"<br />
Modeline "800x480" 29.58 800 816 896 992 480 481 484 497 -HSync +Vsync # 60 Hz<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
Driver "intel"<br />
VendorName "Intel Corporation"<br />
BoardName "Mobile 915GM/GMS/910GML Express Graphics Controller"<br />
BusID "PCI:0:2:0"<br />
Option "AccelMethod" "EXA"<br />
Option "MigrationHeuristic" "greedy"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
</pre><br />
<br />
If you want to set up the i810 driver instead, you will also have to configure 915resolution and add it to your daemons line. This is not needed for the intel driver. Edit the /etc/conf.d/915resolution to look like this:<br />
<br />
<pre># Enter the VBIOS mode to patch<br />
MODE="41"<br />
<br />
# Enter the desired resolution<br />
RESOLUTION="800 480"<br />
</pre><br />
<br />
Now put the 915resolution daemon into your /etc/rc.conf file:<br />
<br />
<pre>DAEMONS=(... 915resolution ...)</pre><br />
<br />
===Sound, Webcam & Microphone===<br />
<br />
====Sound====<br />
<br />
Some people have reported sound working right out of the box with no troubles. However, others might need to add the following line to /etc/modprobe.conf.<br />
<br />
<pre>options snd-hda-intel model=3stack-dig</pre><br />
<br />
If your internal microphone doesn't work, you probably have to turn the capture feature on. Simply fire up alsamixer, find your Capture control, and press spacebar to enable it.<br />
<br />
====Webcam====<br />
<br />
If you installed dkite eeemodules package or toofishes's linux-uvc-eee-svn package, then you should already have webcam driver installed and don't need to install Linux UVC device driver. Just add: <br />
<br />
echo 1 > /proc/acpi/asus/camera<br />
<br />
to your /etc/rc.local file should be suffice to get your webcam working.<br />
<br />
If somehow you don't want to use either dkite eeemodules package or toofishes's linux-uvc-eee-svn package, or prefers to install the driver yourself, then follows the following instructions.<br />
<br />
First, install the Linux UVC device driver. Make sure you have the community repository enabled, and run:<br />
<pre>pacman -S linux-uvc-svn</pre><br />
Then just turn on the webcam (This requires the asus_acpi module):<br />
<pre>echo 1 > /proc/acpi/asus/camera</pre><br />
If you want a simple application application to test it out with, install [http://aur.archlinux.org/packages.php?do_Details=1&ID=7763 luvcview from the AUR], and run it with:<br />
<pre>luvcview -f yuv</pre><br />
<br />
Alternatively, if you want the webcam application that the default Xandos installation uses, install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14469 ucview from the AUR].<br />
<br />
The webcam also works fine with the latest version of Skype.<br />
<br />
If you already have mplayer installed you can launch :<br />
mplayer -fps 15 tv://<br />
<br />
I have yet to get it working with vlc or any other software such as xawtv. If you know how, please update this.<br />
<br />
*'''NOTE:''' For anyone who has accidentally disabled Auto Exposure for their webcam in luvcview (making the image dark), and can't enable it again, do the following:<br />
<br />
Install [http://aur.archlinux.org/packages.php?do_Details=1&ID=14468 libwebcam from the AUR].<br />
<br />
Issue the following command:<br />
<pre>uvcdynctrl --set "Exposure, Auto" 4</pre><br />
<br />
*'''NOTE:''' Be sure the "OS Installation" option is set to "finished" in the BIOS' "Advanced" tab or your camera may not work in some applications (like Skype).<br />
<br />
====Microphone====<br />
<br />
Solution for problems with the internal microphone.<br />
<br />
1. First of all set in alsamixer "Input Source" to "i-Mic"<br />
<br />
2. Increase "Capture" and "i-Mic Boost" to your needs<br />
<br />
3. Edit /etc/asound.state the following, change the 2 "false" to "true" like showing:<br />
<pre><br />
....snap.....<br />
control.11 {<br />
comment.access 'read write'<br />
comment.type BOOLEAN<br />
comment.count 2<br />
iface MIXER<br />
name 'Capture Switch'<br />
value.0 true<br />
value.1 true<br />
}<br />
....snap....</pre><br />
<br />
4. After editing run following as root<br />
<pre>alsactl restore</pre><br />
<br />
5. Now your internal microphone should be working.<br />
<br />
===Getting Hot Keys, Graphic Indicators and Shutdown with the Power Button Working===<br />
<br />
If you want to have working hot keys for changing brightness and volumes, graphic indicators working as well as shutdown when press the power button (just like in the stock Eee PC), then you should install ''''ighea's acpi-eee'''' or ''''dkite's acpid_eee'''' package.<br />
<br />
<br />
==== ighea's acpi-eee ====<br />
<br />
Get the latest package from [http://kapsi.fi/ighea/eee/acpi-eee/ here].<br />
<br />
The package can be easily installed with<br />
pacman -U acpi-eee-8-1-i686.pkg.tar.gz<br />
<br />
See messages during installation for more details and don't forget to edit /etc/acpi/eee.conf to suit your tastes.<br />
<br />
<br />
==== dkite's acpid_eee ====<br />
<br />
Package can also be download form his [http://members.shaw.ca/dkite/ website]<br />
<br />
The package itself can be install with<br />
<br />
pacman -Uf acpid_eee-0.0.3-1-i686.pkg.tar.gz.tar<br />
<br />
<br />
With '''both''' packages don't forget to start asusosd if you want to have the Graphic Indicators from Xandros.<br />
<br />
===Shutdown problem===<br />
<br />
If your Eee won't shutdown properly (i.e. the power indicator led is on but the LCD screen is off), then by adding the following line<br />
<br />
echo -n "0000:00:1b.0" > /sys/bus/pci/drivers/HDA\ Intel/unbind<br />
<br />
To your /etc/rc.local.shutdown should fix the problem.<br />
<br />
If this does not work, the module may not be able to be unloaded until after all services have finished. Do the above, then in /etc/rc.shutdown move <br />
<br />
if [ -x /etc/rc.local.shutdown ]; then<br />
/etc/rc.local.shutdown<br />
fi<br />
<br />
from where it was to directly above the line <br />
<br />
# Terminate all processes<br />
<br />
this will cause the rc.local.shutdown script to run after services have been exited. This fixed all issues for the person editing this note.<br />
<br />
==Additional Tips & Tweaks==<br />
<br />
===kernel26eee tweaks===<br />
<br />
* Toofishes's kernel, also known as kernel26eee, can be tweaked to include custom features. Simple insert a make menuconfig line into the PKGBUILD before the kernel's compilation.<br />
<br />
===Power down with the power button===<br />
<br />
*''If you use dkite's acpid_eee package then you should already be able to shutdown by pressing the power button and should not need to do this.''<br />
<br />
The two alternatives here are described in [[Allow_users_to_shutdown]].<br />
<br />
If you don't already or don't plan to use sudo, it may be simpler to use the setuid /sbin/halt method, otherwise using sudo is preferred.<br />
<br />
Below are all the steps required for the sudo method. If you want to use the setuid method, read the article linked above and perform the 'power' file step here, while omitting the 'sudo' in it.<br />
<br />
<pre>pacman -S sudo</pre><br />
<br />
As root, do the following:<br />
<br />
<pre>visudo</pre><br />
<br />
Add the following line to the file:<br />
<br />
<pre>USER HOST = NOPASSWD: /sbin/poweroff</pre><br />
<br />
Where USER = the user you want to be able to power down with and HOST = your hostname (from /etc/rc.conf).<br />
<br />
Now, create a file called /etc/acpi/events/power, containing:<br />
<br />
<pre># /etc/acpi/events/power<br />
# This is called when the user presses the power button<br />
<br />
event=button/power (PWR.||PBTN)<br />
action=sudo /sbin/poweroff</pre><br />
<br />
Make sure that you execute<br />
<br />
<pre>/etc/rc.d/acpid start</pre><br />
<br />
And/or add acpid to the daemons list in /etc/rc.conf:<br />
<br />
<pre>DAEMONS=(hal, acpid ...</pre><br />
<br />
===Compile the 'everything' Kernel===<br />
<br />
The 'everything' kernel has ath5k, which supports the Atheros chipset found on the EEE PC. Here are the [http://linuxwireless.org/en/users/Drivers/ath5k#Hackingath5k instructions on compiling the 'everthing' kernel] (thanks raymano!).<br />
<br />
===Use cpufreq for power saving===<br />
For scaling down the processor you have to load the p4_clockmod. Insert it into your /etc/rc.conf MODULES array for loading it at startup. <br />
MODULES=(... p4_clockmod ...)<br />
Then proceed like [http://wiki.archlinux.org/index.php/SpeedStep#Alternative_Methods here]. <br />
Add the following into /etc/conf.d/cpufreq<br />
governor="ondemand"<br />
min_freq="113MHz"<br />
max_freq="900MHz"<br />
With enabled cpufreq it scales the processor between 113MHz up to max. frequency. That should save a lot on battery power. The stated 900MHz will be never reached by the eeePC, the p4_clockmod reports a wrong frequency here. But scaling works, you can feel it in the performance of eeePC that he slow down the processor.<br />
<br />
===More responsive system with ondemand governor===<br />
The default up_threshold (where it will bump to a faster speed) for the CPU governor is 80, which means it will increase the CPU speed when utilization is above 80%. This can make X applications have a bit of lag. <br />
Try changing this value:<br />
sudo bash -c "echo 40 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold"<br />
With 40 it still leaves the majority of CPU cycles at the lowest available clock speed but increases responsiveness. You can add this line to one of your startup scripts if you wish to keep it, for example in /etc/rc.local.<br />
<br />
===Speeding up udev for faster boot===<br />
* [[Speedup udev]]<br />
*http://dev.laptop.org/ticket/4349<br />
*[http://www.eeesale.com/Asus-Eee-PC-overclock-Benchmarks.htm Speed up the Eee PC]<br />
<br />
===Update your BIOS without Xandros===<br />
'''Warning : you can break your system, do not update if you are not sure of what you are doing !'''<br />
<br />
First, you need to download the ''.rom'' file.<br />
*[http://update.eeepc.asus.com/bios/ Asus official's BIOS]<br />
*[http://forum.eeeuser.com/viewtopic.php?id=3485 EeeUser's topic]<br />
<br />
You also need an USBStick formated in fat32.<br />
To format an USBStick, use cfdisk tool :<br />
cfdisk /dev/sdc #could be something else than "c"<br />
Choose [delete], [type] : "fat32" (code 0B), [write] and then exit with [quit].<br />
<br />
<br />
Now just copy the ''.rom'' on the USBStick :<br />
cp /somewhere/blabla/.../thecurrentnameofthefile.rom /dev/sdc1/701.rom<br />
The name of the copy '''must''' be 701.rom<br />
<br />
Next step, reboot the eeepc with the USBStick pluged-in, and press<br />
Alt + F2<br />
It will launch the built-in tool. Everything should be Ok, you can make a coffee during the update. When it asks you to push the power-button it has finished.<br />
<br />
<br />
At the next boot, you'll be invited to configure the BIOS. Check if the everything is enable (my webcam and wireless were disable after the update) and if it displays the good version in the main screen. It's done !<br />
<br />
===More usuable font sizes===<br />
<br />
On a default installation with XFCE 4 my font sizes were too big, here is what I did to sort them out.<br />
<br />
First, I set the DPI by adding the following to ~/.Xdefaults:<br />
Xft*dpi: 134<br />
<br />
This then caused the fonts to be even bigger, so I set them all to be font-size 6 by adding the following into ~/.gtkrc-2.0 (note this will be overwritten if you use any tools to change GTK settings):<br />
style "user-font"<br />
{<br />
font_name="Bitstream Vera Sans 6"<br />
}<br />
widget_class "*" style "user-font"<br />
<br />
To do the same with KDE fonts (without KDE installed) you have to add the following to ~/.kde/share/config/kdeglobals:<br />
[General]<br />
StandardFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
activeFont=Bitstream Vera Sans,6,-1,5,75,0,0,0,0,0<br />
fixed=Bitstream Vera Sans Mono,6,-1,5,50,0,0,0,0,0<br />
font=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
menuFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
taskbarFont=Bitstream Vera Sans,6,-1,5,50,1,0,0,0,0<br />
toolBarFont=Bitstream Vera Sans,6,-1,5,50,0,0,0,0,0<br />
<br />
To make your fonts even prettier enable the [[Fonts#Fonts_with_LCD_filter_enabled|LCD Fonts]].<br />
<br />
==Known problems and their solutions==<br />
<br />
===Booting from card without initrd===<br />
<br />
Let's say you decided to install Arch Linux on a card and compiled your own kernel (or used the kernel26eee kernel) without initrd. Card reader on EeePC is connected as an USB device. Unfortunately, USB storage devices are detected with a delay, so we must tell the kernel to wait until this device becomes available. You do this with "rootwait" option passed to kernel at boot time.<br />
<br />
===Sleeping and waking system on a card===<br />
<br />
If you have Arch Linux on a card, waking up from sleeping state will most likely fail. The only solution is to enable the CONFIG_USB_PERSIST option in kernel. The kernel26eee package should have this option enabled.<br />
<br />
===Display doesn't wake up properly===<br />
<br />
If you encounter black display (but apparently working system) after suspend/resume, consider using the "uswsusp" package (available in AUR) and correcting suspend2ram script in /etc/acpi, where you use this line to make the machine go to sleep:<br />
<br />
<pre>/usr/sbin/s2ram --force --vbe_post --vbe_mode</pre></div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=USB_flash_installation_medium&diff=43580USB flash installation medium2008-06-23T17:22:52Z<p>Bladesonfire: /* The New and Improved Way */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{stub}}<br />
<br />
== The New and Improved Way ==<br />
<br />
As of 2008.04, [http://bbs.archlinux.org/viewtopic.php?pid=356073 USB images are provided]. Download them from your [http://archlinux.org/download/ local mirror] (they are the .img files). To install, use the following command:<br />
<br />
dd if=image.img of=/dev/sd[x]<br />
<br />
where ''if='' is the path to the img file and ''of='' is your USB device. Make sure to use /dev/sdx and not /dev/sdx1.<br />
<br />
'''Note:''' This will destroy your USB stick, so make sure you don't have any important files on the stick before doing this.<br />
<br />
'''Note:''' 2008.04-rc arch-core img files are broken. Use the ftp img file for a successful install.<br />
<br />
== Preparing the USB stick ==<br />
<br />
The arch-ftp.iso is only about 26 MB, so it should fit on a 64 MB USB stick. The arch-core.iso should fit on a 512 MB stick.<br />
<br />
1. Partition the USB stick.<br />
Create one partition with FAT16 type, make it bootable. Remember its name, such as /dev/sd[x]1.<br />
<br />
cfdisk /dev/sd[x]<br />
<br />
2. Make a FAT16 filesystem (you need dosfstools)<br />
<br />
mkdosfs /dev/sd[x]1<br />
<br />
3. Get the arch-base install ISO from www.archlinux.org<br />
<br />
4. Mount the iso to an temporary directory<br />
<br />
mkdir -p /mnt/archcd<br />
mount -o loop /Path/to/iso /mnt/archcd<br />
<br />
5. Mount the USB Stick<br />
<br />
mkdir -p /mnt/usb/<br />
mount /dev/sd[x]1 /mnt/usb/<br />
<br />
6. Copy the .iso to the USB Stick<br />
<br />
cp -ra /mnt/archcd/* /mnt/usb/<br />
<br />
<br />
7. Copy the boot data<br />
<br />
cd /mnt/usb/isolinux/<br />
cp vmlinuz /mnt/usb/<br />
cp initrd.img /mnt/usb/<br />
cp boot.* /mnt/usb/<br />
cp isolinux.cfg /mnt/usb/syslinux.cfg<br />
<br />
8. Install MBR and syslinux<br />
<br />
lilo -M /dev/sd[x] mbr<sup>(1</sup><br />
syslinux -s /dev/sd[x]1<br />
<br />
===After booting from the USB stick:===<br />
<br />
Mount the source media on the stick to the /src directory.<br />
<br />
mount /dev/sd[x] /src<br />
<br />
===Troubleshooting:===<br />
<br />
If you happen to run into "Cluster sizes larger than 16K not supported" error when running syslinux - don't panic, that just means you need to install more recent version of syslinux.<br />
<br />
<sup>1)</sup> Using lilo is not really needed because syslinux does the "floppy" loading stuff. But if you get some error like "Can't load operating system" you have to perform the lilo command.</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=USB_flash_installation_medium&diff=43579USB flash installation medium2008-06-23T17:20:18Z<p>Bladesonfire: /* The New and Improved Way */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{stub}}<br />
<br />
== The New and Improved Way ==<br />
<br />
As of 2008.04, [http://bbs.archlinux.org/viewtopic.php?pid=356073 USB images are provided]. Download them from your [http://archlinux.org/download/ local mirror] (they are the .img files). To install, use the following command:<br />
<br />
dd if=image.img of=/dev/sd[x]<br />
<br />
where ''if='' is the path to the img file and ''of='' is your USB device. Make sure to use /dev/sdx and not /dev/sdx1.<br />
<br />
'''Note:''' This will destroy your USB stick, so make sure you don't have any important files on the stick before doing this.<br />
<br />
== Preparing the USB stick ==<br />
<br />
The arch-ftp.iso is only about 26 MB, so it should fit on a 64 MB USB stick. The arch-core.iso should fit on a 512 MB stick.<br />
<br />
1. Partition the USB stick.<br />
Create one partition with FAT16 type, make it bootable. Remember its name, such as /dev/sd[x]1.<br />
<br />
cfdisk /dev/sd[x]<br />
<br />
2. Make a FAT16 filesystem (you need dosfstools)<br />
<br />
mkdosfs /dev/sd[x]1<br />
<br />
3. Get the arch-base install ISO from www.archlinux.org<br />
<br />
4. Mount the iso to an temporary directory<br />
<br />
mkdir -p /mnt/archcd<br />
mount -o loop /Path/to/iso /mnt/archcd<br />
<br />
5. Mount the USB Stick<br />
<br />
mkdir -p /mnt/usb/<br />
mount /dev/sd[x]1 /mnt/usb/<br />
<br />
6. Copy the .iso to the USB Stick<br />
<br />
cp -ra /mnt/archcd/* /mnt/usb/<br />
<br />
<br />
7. Copy the boot data<br />
<br />
cd /mnt/usb/isolinux/<br />
cp vmlinuz /mnt/usb/<br />
cp initrd.img /mnt/usb/<br />
cp boot.* /mnt/usb/<br />
cp isolinux.cfg /mnt/usb/syslinux.cfg<br />
<br />
8. Install MBR and syslinux<br />
<br />
lilo -M /dev/sd[x] mbr<sup>(1</sup><br />
syslinux -s /dev/sd[x]1<br />
<br />
===After booting from the USB stick:===<br />
<br />
Mount the source media on the stick to the /src directory.<br />
<br />
mount /dev/sd[x] /src<br />
<br />
===Troubleshooting:===<br />
<br />
If you happen to run into "Cluster sizes larger than 16K not supported" error when running syslinux - don't panic, that just means you need to install more recent version of syslinux.<br />
<br />
<sup>1)</sup> Using lilo is not really needed because syslinux does the "floppy" loading stuff. But if you get some error like "Can't load operating system" you have to perform the lilo command.</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=USB_flash_installation_medium&diff=43578USB flash installation medium2008-06-23T17:19:55Z<p>Bladesonfire: </p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{stub}}<br />
<br />
== The New and Improved Way ==<br />
<br />
As of 2008.04, [http://bbs.archlinux.org/viewtopic.php?pid=356073 USB images are provided]. Download them from your [http://archlinux.org/download/ local mirror] (they are the .img files). To install, use the following command:<br />
<br />
dd if=image.img of=/dev/sd[x]<br />
<br />
where ''if='' is the path to the img file and ''of='' is your USB device. Make sure to use /dev/sdx and not /dev/sdx1.<br />
<br />
'''Note:''' This will destroy your USB stick, so make sure you don't have any important files on the stick before doing this.<br />
<br />
=== Preparing the USB stick ===<br />
<br />
The arch-ftp.iso is only about 26 MB, so it should fit on a 64 MB USB stick. The arch-core.iso should fit on a 512 MB stick.<br />
<br />
1. Partition the USB stick.<br />
Create one partition with FAT16 type, make it bootable. Remember its name, such as /dev/sd[x]1.<br />
<br />
cfdisk /dev/sd[x]<br />
<br />
2. Make a FAT16 filesystem (you need dosfstools)<br />
<br />
mkdosfs /dev/sd[x]1<br />
<br />
3. Get the arch-base install ISO from www.archlinux.org<br />
<br />
4. Mount the iso to an temporary directory<br />
<br />
mkdir -p /mnt/archcd<br />
mount -o loop /Path/to/iso /mnt/archcd<br />
<br />
5. Mount the USB Stick<br />
<br />
mkdir -p /mnt/usb/<br />
mount /dev/sd[x]1 /mnt/usb/<br />
<br />
6. Copy the .iso to the USB Stick<br />
<br />
cp -ra /mnt/archcd/* /mnt/usb/<br />
<br />
<br />
7. Copy the boot data<br />
<br />
cd /mnt/usb/isolinux/<br />
cp vmlinuz /mnt/usb/<br />
cp initrd.img /mnt/usb/<br />
cp boot.* /mnt/usb/<br />
cp isolinux.cfg /mnt/usb/syslinux.cfg<br />
<br />
8. Install MBR and syslinux<br />
<br />
lilo -M /dev/sd[x] mbr<sup>(1</sup><br />
syslinux -s /dev/sd[x]1<br />
<br />
===After booting from the USB stick:===<br />
<br />
Mount the source media on the stick to the /src directory.<br />
<br />
mount /dev/sd[x] /src<br />
<br />
===Troubleshooting:===<br />
<br />
If you happen to run into "Cluster sizes larger than 16K not supported" error when running syslinux - don't panic, that just means you need to install more recent version of syslinux.<br />
<br />
<sup>1)</sup> Using lilo is not really needed because syslinux does the "floppy" loading stuff. But if you get some error like "Can't load operating system" you have to perform the lilo command.</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Webcam_setup&diff=39362Webcam setup2008-03-29T20:16:53Z<p>Bladesonfire: /* spca5xx */</p>
<hr />
<div>[[Category:Other hardware (English)]] <br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Webcam Setup}}<br />
{{i18n_entry|简体中文|安装网络摄像机}}<br />
{{i18n_links_end}}<br />
<br />
Here's a guide to setting up your webcam in Arch Linux.<br />
<br />
= Identify your webcam =<br />
Identify the name of your webcam and find a proper driver. Below is a list of webcams, and what drivers they work with. Click on the link to the right of the device name for information on compiling modules and other information. If you get your webcam to work, add the name of the webcam and the driver you used to the list!<br />
<br />
== pwc ==<br />
* Creative Labs Webcam Pro Ex<br />
* Logitech QuickCam Notebook Pro (only the "Pro" models)<br />
* Logitech Quickcam Pro 4000<br />
* Philips ToUCams (not confirmed at the moment, but it's using the pwc driver if I remember correctly)<br />
<br />
== [[Retrieving Qc-usb drivers HOWTO|qc-usb]] ==<br />
* Dexxa Webcam<br />
* Labtec Webcam (old model) <br />
* LegoCam<br />
* Logitech Quickcam Express (old model)<br />
* Logitech QuickCam Notebook (not the "Pro" models)<br />
* Logitech Quickcam Web<br />
<br />
== qc-usb-messenger ==<br />
* Logitech Quickcam Messenger<br />
You can find a PKGBUILD for this driver on the [http://aur.archlinux.org/ AUR].<br />
<br />
== zr364xx ==<br />
This driver can be used for many webcams like:<br />
* Aiptek PocketDV 3300<br />
* Creative PC-CAM 880<br />
* Konica Revio 2<br />
* Genius Digital Camera<br />
* Maxell Maxcam PRO DV3<br />
You can find the full list of supported devices [http://royale.zerezo.com/zr364xx/ here]. You can find a PKGBUILD for this driver on the [http://aur.archlinux.org/ AUR].<br />
<br />
== sn9c102 ==<br />
* Trust Spacecam series<br />
* Maxell Smartcam (for notebooks): 352x288 max. resolution @ 3fps<br />
<br />
== spca5xx ==<br />
An extensive list of supported webcams is available [http://mxhaard.free.fr/spca5xx.html here].<br />
* Logitech QuickCam IM<br />
* Logitech QuickCam for Notebooks Deluxe<br />
* Labtec Webcam Pro<br />
* Trust Mini Webcam WB-1200p<br />
<br />
Kernels >= 2.6.11 would now use the gspca module, by installing the gspcav1 package.<br />
<br />
== stv680 ==<br />
Many cheap no-name cameras that came out Asia in the last couple of years use the stv680 chipset. Most of these cameras were novelty items (i.e. Pencam, SpyC@m and LegoCam). <br />
* Aiptek PenCam series<br />
* Digitaldream series<br />
* Dolphin Peripherals series<br />
* Lego LegoCam<br />
* Trust SpyC@m series<br />
* Welback Coolcam<br />
<br />
A more-complete list of webcams that use the stv680 chipset is available [http://webcam-osx.sourceforge.net/cameras/index.php?orderBy=controller here].<br />
<br />
== linux-uvc ==<br />
* Logitech Quickcam Pro 5000<br />
* Logitech Quickcam Orbit MP<br />
<br />
You can find a full list of supported UVC devices [http://linux-uvc.berlios.de/ here]. The package linux-uvc-svn is available in the [community] repository.<br />
<br />
Note: This driver does not have V4L1 support.<br />
<br />
== ov51x-jpeg ==<br />
* Sony EyeToy<br />
* Chicony DC-2120 <br />
* Chicony DC-2120 pro<br />
* Trust Spacecam 320<br />
* Hercules Webcam Deluxe <br />
* Hercules Webcam Classic <br />
* Creative Live! Cam Notebook Pro VF0400 <br />
* Creative Live! Cam Vista IM <br />
* Creative Live! Cam Vista IM VF0420 <br />
* Creative Vista Webcam VF0330 <br />
* ASUS webcam Model? <br />
* Philips PCVC820K/00 <br />
* NGS showtime plus <br />
* HP VGA Webcam with Integrated Microphone<br />
<br />
This is a kernel module found in the AUR with some additions to the original driver that provide jpeg decompression.<br />
See the [http://www.rastageeks.org/ov51x-jpeg/index.php/Main_Page webpage]<br />
<br />
<br />
For me to get my "Creative Live! Cam Vista IM" working with Skype I had to add this line to /etc/modprobe.conf<br />
options ov51x-jpeg forceblock=1<br />
<br />
= Make sure to load the needed module for your webcam =<br />
The easiest way is to let rc.conf load the needed module at boot.<br />
Edit rc.conf. In the modules=() array, add the module of your webcam. This will load your webcam module into the kernel at bootup.<br />
<br />
<b>Note:</b> If your webcam is USB the kernel ''should'' automatically load the proper driver. In that case, after you plug your webcam in, see what dmesg says. You should see something like that:<br />
<br />
<pre>$ dmesg|tail<br />
sn9c102: V4L2 driver for SN9C10x PC Camera Controllers v1:1.24a<br />
usb 1-1: SN9C10[12] PC Camera Controller detected (vid/pid 0x0C45/0x600D)<br />
usb 1-1: PAS106B image sensor detected<br />
usb 1-1: Initialization succeeded<br />
usb 1-1: V4L2 device registered as /dev/video0<br />
usb 1-1: Optional device control through 'sysfs' interface ready<br />
usbcore: registered new driver sn9c102</pre><br />
<br />
= Permissions =<br />
In order to use your webcam you need to have permission to use <code>/dev/video0</code>.<br />
== udev ==<br />
If you use udev (which is default as of kernel 2.6.13) you only need to be in the group <b>video</b>. You can check it with:<br />
$ groups<br />
To add a user to the group run under root:<br />
# gpasswd -a <username> video<br />
== devfs ==<br />
Add the following to your <code>/etc/devfsd.conf</code>. This will give normal users permission to use <code>/dev/video0</code> (your webcam).<br />
# Give normal users access to webcam<br />
REGISTER video0 PERMISSIONS root.users 0660<br />
<br />
= Get software to use your webcam =<br />
== Cheese ==<br />
Cheese is a photo/video taking client similar to Photo Booth in Mac OS X. It is currently available in the AUR.<br />
== Kopete ==<br />
Kopete is the [[KDE]] instant messaging (IM) client. As of KDE 3.5, it has support for MSN and Yahoo! webcams, but not every cam works yet. It is included in the kdenetwork package.<br />
== xawtv ==<br />
This is a basic v4l device viewer, and although it is intended for use with TV tuner cards, it works well with webcams. It will display what your webcam sees in a window. Install it using <br />
pacman -S xawtv<br />
Run it with <br />
xawtv -c /dev/video0<br />
If you're using a nVidia graphic card, and you get an error like<br />
X Error of failed request: XF86DGANoDirectVideoMode<br />
Major opcode of failed request: 139 (XFree86-DGA)<br />
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)<br />
Serial number of failed request: 69<br />
Current serial number in output stream: 69<br />
you should instead run it as:<br />
xawtv -nodga<br />
<br />
== ekiga ==<br />
This is very similar to Microsoft NetMeeting. <br />
Get it with <br />
pacman -S ekiga<br />
The configuration druid will set everything up for you.<br />
<br />
== Sonic-snap ==<br />
Sonic-snap [http://www.stolk.org/sonic-snap/] is a viewer/grabber for sn9c102-based webcams '''only'''.<br />
Available in AUR</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=Network_configuration/Wireless&diff=32280Network configuration/Wireless2007-11-11T12:24:39Z<p>Bladesonfire: /* ndiswrapper */ Updated link to Ndiswrapper installation wiki</p>
<hr />
<div>[[Category:Communication and network (English)]]<br />
[[Category:Networking (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Wireless_Setup}}<br />
{{i18n_entry|Nederlands|Draadloze_Configuratie}}<br />
{{i18n_entry|German|Drahtlos_Installation}}<br />
{{i18n_links_end}}<br />
<br />
==First steps==<br />
#Check to see if Linux supports your hardware. You can find out what your card is with lshwd.<br />
#*zd1201-based card like ZyXEL B-220<br />
#*[http://www.linux-wlan.org/docs/wlan_adapters.html.gz wlan-ng] supports quite a lot of chipsets; check here first.<br />
#*[http://madwifi.org madwifi] for Atheros chipsets (AR5210, AR5211, AR5212 and AR5213)<br />
#*[http://rt2x00.serialmonkey.com/wiki/index.php/Main_Page rt2x00 project] for a unified driver for Ralink's rt2400, rt2500, and rt2570 chipsets (beta).<br />
#*[http://www.ralinktech.com/ralink/Home/Support/Linux.html Ralink Linux Support] for drivers for Ralink chipsets direct from the manufacturer.<br />
#*[http://rt2x00.serialmonkey.com/wiki/index.php/Downloads rt2x00 project] for better-maintained versions of Ralink's own drivers ("legacy drivers" on the site).<br />
#*[http://ipw2100.sourceforge.net/ ipw2100] for Intel Pro/Wireless 2100 Mini PCI<br />
#*[http://ipw2200.sourceforge.net/ ipw2200] for Intel Pro/Wireless 2200 Mini PCI<br />
#*[http://ipw3945.sourceforge.net/ ipw3945] for Intel Pro/Wireless 3945 AB/G Mini PCI-E<br />
#*[http://www.nongnu.org/orinoco/devices/ orinoco] for some Prism 2-based cards<br />
#*[http://prism54.org/ prism54] for Prism 54-based cards<br />
#*[http://bcm43xx.berlios.de/ bcm43xx] for Broadcom 43xx-based cards<br />
#*Check the [http://linux-wless.passys.nl/ Linux Wireless Support] page for your hardware or in The Linux Questions [http://www.linuxquestions.org/hcl/index.php?cat=10 hardware compatibility list] (HCL), which also has a good list of Linux-friendly hardware <br />
#If the hardware is supported only under Windows<br />
#*[http://ndiswrapper.sourceforge.net/wiki/index.php/List ndiswrapper] for hardware supported only under Windows (some Broadcom, 3com, etc)<br />
#*You will need the .inf and .sys files from your Windows driver - [http://ndiswrapper.sourceforge.net/mediawiki/index.php/List check here]<br />
#If your hardware is not listed anywhere<br />
#*I think you may be screwed....<br />
#*Try a web search for the exact model name of your hardware with the word "linux" - and feel free to ask for help on [http://bbs.archlinux.org the forums]<br />
<br />
==Installation==<br />
First off, make sure you grab '''wireless-tools''' from pacman<br />
<pre>pacman -S wireless_tools</pre><br />
You cannot initialize wireless hardware without these tools.<br />
===Drivers===<br />
Here are the details of how to get the drivers for your card. You may find that there are several options open to you, so remember you can check the [http://www.linuxquestions.org/hcl/index.php?cat=10|LQ HCL] for help on selecting the best driver.<br />
====wlan-ng====<br />
<pre>pacman -S wlan-ng24</pre> or <pre>pacman -S wlan-ng26</pre><br />
====rt2x00====<br />
Unified driver for Ralink chipsets (will ultimately replace rt2500,rt61,rt73 etc). Compatible with stable wpa_supplicant using the wext driver interface. This driver is currently in heavy development but is likely to be in the mainline kernel as of 2.6.24.<br />
<pre>pacman -S rt2x00-cvs</pre> (from unstable repository)<br />
See the [[Using_the_new_rt2x00_beta_driver|rt2x00 wiki page]].<br />
<br />
====RT2500====<br />
For Ralink's PCI/PCMCIA based rt2500 series chipsets (the first generation of Ralink chips to support 802.11g).<br />
<pre>pacman -S rt2500</pre><br />
Supports standard iwconfig tools for unencrypted and WEP connections, although it can be quite sensitive to the order of commands.<br />
wpa_supplicant is not supported using the standard wext interface. The driver does support WPA (using hardware encryption), but in a non-standard way. The trunk version of wpa_supplicant (0.6.x) appears to include special support for this driver, and it is also possible to negotiate a WPA connection manually using iwpriv commands.<br />
See [http://rt2400.cvs.sourceforge.net/*checkout*/rt2400/source/rt2500/Module/iwpriv_usage.txt these instructions] for details.<br />
The same applies for RT61 and RT73 below.<br />
<br />
====RT61====<br />
For PCI/PCMCIA cards based on Ralink's later generation of 802.11g chipsets (including those supporting proprietary MIMO modes).<br />
See the [[RT61_Wireless|RT61 wiki page]].<br />
<br />
====RT73====<br />
For USB devices based on Ralink's later generation of 802.11g chipsets (including those supporting proprietary MIMO modes).<br />
See the [[RT73_Wireless|RT73 wiki page]].<br />
<br />
====madwifi====<br />
<br />
pacman -S madwifi<br />
<br />
The module is called <tt>ath_pci</tt>. '''You may need to use the countrycode option when loading the MadWifi driver in order to use channels and transmit power settings that are legal in your country/region.''' In the Netherlands, for example, you would load the module like this:<br />
<br />
modprobe ath_pci countrycode=528<br />
<br />
You can verify the settings with the <tt>iwlist</tt> command. See <tt>man iwlist</tt> and the [http://madwifi.org/wiki/UserDocs/CountryCode CountryCode page on the MadWifi wiki]. To have this setting automatically applied during boot, add the following to <tt>/etc/modprobe.conf</tt>:<br />
<br />
options ath_pci countrycode=528<br />
<br />
ATTENTION: I had to remove the countrycode option completely or the ath0 device wasn't created (andyrtr, kernel 2.6.21)!<br />
<br />
====ipw2100 and ipw2200====<br />
Depending on which of the chips you have, use either:<br />
<br />
pacman -S ipw2100-fw<br />
<br />
or:<br />
<br />
pacman -S ipw2200-fw<br />
<br />
You will probably need to reboot for the firmware to be loaded.<br />
<br />
====ipw3945 and ipw4965====<br />
Intel's new [http://intellinuxwireless.org/?p=iwlwifi iwlwifi project] drivers will work for both chipsets, simply choose the microcode that corresponds to yours:<br />
<br />
pacman -S iwlwifi iwlwifi-3945-ucode<br />
<br />
or:<br />
<br />
pacman -S iwlwifi iwlwifi-4965-ucode<br />
<br />
Add the kernel driver to your startup:<br />
<br />
nano /etc/rc.conf<br />
<br />
in the modules=() array, add '''iwl3945''' or '''iwl4965''' to the list, depending on your chipset<br />
<br />
CTRL + X, Y to close and save.<br />
<br />
The drivers should now load after a reboot, and running 'ifconfig' from a terminal should report '''wlan0''' as a new network interface.<br />
<br />
Note: if the iwlwifi drivers, being "experimental", do not work, know that the windows NETw4x32 driver works with ndiswrapper just fine.<br />
<br />
====ipw3945 (Alternate Method)====<br />
'''''Note:''' This ipw3945 driver will be phased out as Intel's iwlwifi project drivers reach maturity.''<br />
<br />
<pre>pacman -S ipw3945</pre><br />
<br />
This should install ipw3945-ucode, ipw3945, and ipw3945d (daemon).<br />
<br />
To properly initialize the driver on startup...<br />
<br />
<pre>nano /etc/rc.conf</pre><br />
<br />
in the modules=() array, add ipw3945 to the list<br />
<br />
in the daemons=() array, add ipw3945d to the list (its order must come BEFORE network and dhcdbd/networkmanager in the array)<br />
<br />
CTRL + X, Y to close and save.<br />
<br />
The ipw3945 module should load during "Loading Modules.." and "Starting IPW3945d" should appear during daemon initialization, and ethX should be present.<br />
<br />
Update: <br />
On my HP nc6320 the Bluetooth won't connect unless you unload the ipw3945 module.<br />
<br />
====orinoco====<br />
This should be part of the kernel package and be installed already.<br />
====ndiswrapper====<br />
Ndiswrapper is not a real driver, but you can use it when there are no native Linux drivers for your wireless chips. So it is very useful in some situations. To use it you need the *.inf file from your Windows driver. To install ndiswrapper use the steps below:<br />
<br />
To install the ndiswrapper use pacman:<br />
<pre>pacman -Sy ndiswrapper ndiswrapper-utils</pre><br />
''Note:'' Beyond kernel needs the packages ndiswrapper-beyond instead of the ndiswrapper package!<br />
<br />
''Note:'' If you do not have internet access on the machine running Arch, you can also download the packages to a disk from one of the mirrors, e.g. http://www2.cddc.vt.edu/linux/distributions/archlinux/extra/os/i686/ .<br />
You need the ndiswrapper (or ndiswrapper-beyond as it says above) and ndiswrapper-utils packages. You may also have to download the latest kernel26 (or beyond), as the version provided on the CD is not always the latest one.<br />
<br />
Once the installation has completed, follow the steps to configure ndiswrapper.<br />
<pre>ndiswrapper -i filename.inf<br />
ndiswrapper -l<br />
ndiswrapper -m<br />
depmod -a</pre><br />
<br />
Now the ndiswrapper install is almost finished; you just have to update /etc/rc.conf to load the module at boot (below is a sample of my config; yours might look slightly different):<br />
<br />
<pre>MODULES=(ndiswrapper snd-intel8x0 !usbserial)</pre><br />
<br />
The important part is making sure that ndiswrapper exists on this line, so just add it alongside the other modules. It would be best to test that ndiswrapper will load now, so:<br />
<br />
<pre>modprobe ndiswrapper<br />
iwconfig</pre><br />
<br />
and wlan0 should exist. Check this page if you're having problems:<br />
[http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,installation/ Ndiswrapper installation wiki].<br />
<br />
====prism54====<br />
Download the firmware driver for your appropriate card from [http://www.prism54.org/ this site]. Rename the firmware file to 'isl3890'.<br />
If nonexistent, create the directory /lib/firmware and place the file 'isl3890' in it. This should do the trick. ([http://bbs.archlinux.org/viewtopic.php?t=16569&start=0&postdays=0&postorder=asc&highlight=siocsifflags+such+file++directory forum source])<br />
<br />
====ACX100/111====<br />
The ACX100/111 driver can be found at [http://acx100.sourceforge.net/]. This can be used for cards based on the Texas Instruments ACX100/111 chipset.<br />
<br />
Contrary to what people think, this is relatively easy to setup. There is a huge guide written by Craig [http://www.houseofcraig.net/acx100_howto.php here]. However, the README that comes with the driver is actually easier to follow.<br />
<br />
# Download the latest version of the driver. <br />
# Extract the archive to a directory of your choice. Beware: The archive does not have a directory inside, so if you don't extract within a directory, a lot of files will spill out everywhere.<br />
# Change to the directory containing the extracted files.<br />
# Execute <pre>make -C /lib/modules/`uname -r`/build M=`pwd`</pre><br />
# Change to root user.<br />
# Execute <pre>make -C /lib/modules/`uname -r`/build M=`pwd` modules_install</pre><br />
# Execute <pre>depmod -ae</pre> so the kernel detects the new module.<br />
# Insert the driver CD that came with the card into the CD/DVD drive on your computer.<br />
# Mount the drive with <pre>mount &lt;device&gt;</pre><br />
# Copy the firmware from the CD to /lib/firmware.<br />
# Rename the firmware to 'tiacxNNNcMM' (NNN=100/111, MM=radio module ID (in uppercase hex)) for the PCI driver or tiacxNNNusbcMM for the USB driver. <br />
# Load the acx module with <pre>modprobe acx</pre><br />
# Add the acx module to the MODULES array in /etc/rc.conf so it gets loaded on startup.<br />
# Follow the instructions for connecting to your network with iwconfig.<br />
<br />
<br />
Note: It is also possible to compile the driver inside the kernel tree. This is documented in the README file with the driver.<br />
<br />
====BCM43XX====<br />
Broadcom users that have 43xx series chipsets have a new alternative to ndiswrapper. In kernel version 2.6.17, the bcm43xx driver was introduced.<br />
<br />
#Run <pre>iwconfig</pre> or <pre>hwd -s</pre> to determine that you have an appropriate card. My output of hwd -s looked like this: <pre>Network : Broadcom Corp.|BCM94306 802.11g NIC module: unknown</pre><br />
#Run <pre>pacman -Sy bcm43xx-fwcutter</pre> to install the firmware cutter application.<br />
#Download the Windows driver file for your card from which to extract the firmware.<br />
#*I initially downloaded the driver from Dell's support site. When that didn't work I found a link on the Ubuntu Wiki and used that file instead: [http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o]. I just saved this file to my desktop; you won't need it after the next step.<br />
#Run <pre>bcm43xx-fwcutter -w /lib/firmware /home/&lt;user&gt;/Desktop/wl_apsta.o</pre> You may have to create /lib/firmware first.<br />
#Restart, and configure your device as normal. You may want to add bcm43xx into the modules section of your rc.conf file. Good luck!<br />
<br />
====rtl8187====<br />
See the [[Rtl8187_wireless|rtl8187 wiki page]].<br />
<br />
==Setup and Boot==<br />
Arch Linux provides two methods for enabling wireless connections. The first method is based on the existing network script and should be used for non-roaming wireless access. If you're on only one wireless network, this is the best setup to use. However, if you continually roam from network to network, the Network Profiles setup would be best, though slightly more complicated.<br />
<br />
===Using the Arch Linux Wireless Network settings===<br />
* Typical Arch Linux Wireless configuration is rather straightforward. The network itself is configured in the exact same way a non-wireless network is in /etc/rc.conf. For example:<br />
# /etc/rc.conf<br />
wlan0="dhcp"<br />
INTERFACES=(lo eth0 wlan0)<br />
where wlan0 is the wireless interface name<br />
* Beyond this, the networking scripts need some way to determine that wlan0 is a wireless interface (as not all wireless interfaces are wlan*). This is done in the /etc/conf.d/wireless file. The setup here is very simple. For each wireless interface, you simply declare a setting called wlan_<interface name>. If your wireless interface is "wlan0", it uses wlan_wlan0. If your wireless interface is "eth1", wlan_eth1 is what you need. The value for this setting is simply the parameters to iwconfig (see man iwconfig for details) ''including the interface name''.<br />
* A simple, non-encrypted setup for the above would look like:<br />
# /etc/conf.d/wireless<br />
wlan_wlan0="wlan0 essid MyEssid"<br />
WLAN_INTERFACES=(wlan0)<br />
* While a WEP Encrypted setup would look like:<br />
# /etc/conf.d/wireless<br />
wlan_wlan0="wlan0 essid MyEssid key 12345678"<br />
WLAN_INTERFACES=(wlan0)<br />
* ''phrakture's trick''<br />
** My personal trick isn't much of a trick at all; it just simplifies a lot of the process. While /etc/conf.d/wireless is sourced (included) in the network script, it is not a requirement for having a wireless interface. Therefore, the actual settings for the wireless interface can exist in anything sourced by the network script. For that reason, I put all my settings in /etc/rc.conf:<br />
# /etc/rc.conf<br />
eth0="dhcp"<br />
wlan0="dhcp"<br />
wlan_wlan0="wlan0 essid MyEssid"<br />
#wlan_wlan0="wlan0 essid MyEssid key 12345678"<br />
#wlan_wlan0="wlan0 essid MyEssid key s:wirelesspassword"<br />
WLAN_INTERFACES=(wlan0)<br />
INTERFACES=(lo eth0 wlan0)<br />
<br />
All of these settings assume your wireless card is wlan0, if it is something else (such as eth0) then simply replace wlan0 with eth0 every time it appears. For example, if your wireless card is eth0 so you change wlan_wlan0 to be wlan_eth0="eth0 essid ...." , wlan0="dhcp" to eth0="dhcp" and WLAN_INTERFACES=(wlan0) to WLAN_INTERFACES=(eth0). The same applies for cards named eth1 and so forth.<br />
<br />
===Using the Archlinux Roaming Network Profiles===<br />
<br />
====Quick Setup====<br />
# Create new profile<br />
## Create a new network profile in <tt>/etc/network-profiles/</tt> based on the <tt>template</tt> file. Let's call it <tt>home</tt>. Remember the filename you choose! We'll use it to refer to our new profile later.<br />
## Adjust the settings in the new profile to your needs.<br />
# Remove outdated settings from <tt>rc.conf</tt><br />
## Remove all interfaces that should be managed by the Network Profiles in the future from INTERFACES.<br />
## Remove any relevant routes from ROUTES.<br />
## Leave the "lo" interface in place.<br />
# Add Network Profile settings to <tt>rc.conf</tt><br />
## Add the name of your new network profile to <tt>NET_PROFILES=()</tt> <pre>NET_PROFILES=(home)</pre>.<br />
<br />
So much for the quick setup... You can also set <tt>NET_PROFILES</tt> to "menu" and it will present a dialog/ncurses menu (which requires the [http://www.archlinux.org/packages/4278/ dialog package] installed) at bootup where you can pick the profile you want. This doesn't work if you use @network (starting network in the background).<br />
<br />
Alternatively, you can pass a <tt>NET=</tt> value on the kernel boot line, telling netcfg which profile you wish to start with.<br />
vmlinuz root=/dev/hda3 vga=773 ro NET=home<br />
<br />
Picked from [http://www.archlinux.org/pipermail/arch/2005-June/004855.html Judd's explanation].<br />
<br />
If you want to change your network profile after boot, you can run 'netcfg' as root.<br />
<br />
'''Simple Wireless Autodetection'''<br />
iphitus created an autodetection patch for the official initscripts which has now been imported as standard. Please see [http://www.archlinux.org/pipermail/arch/2005-July/005251.html here] for an explanation of how it works.<br />
<br />
There is a workaround for another [[wireless autodetection]] that scans the air for known APs and starts the associated profile.<br />
<br />
'''WPA support'''<br />
phydeaux created a great patch for WPA support which has been adopted straight into the main tree and will be in the next release (after 0.7.1). For information about how to use WPA with the Network Profiles see also [[Ndiswrapper and wpa supplicant]].<br />
<br />
'''Netcfg GUI''' A simple GUI script to switch network profiles from GNOME (or another window manager) can be found in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=4197 AUR]. ([http://mac-cain13.livejournal.com/tag/netswitch Screenshots])<br />
<br />
===Wifi-radar===<br />
'''Wifi-radar''' This is a nifty little GUI program that lets you switch wireless networks with ease. Simply do the following:<br />
<br />
# # pacman -S wifi-radar<br />
# # visudo<br />
<br />
Here, add the following line: <br />
yourusername ALL=(ALL) NOPASSWD: /usr/bin/wifi-radar<br />
Press ESC, then colon (:), then x, then ENTER to save and exit.<br />
<br />
# Now, just add wifi-radar to your daemons list in /etc/rc.conf and run wifi-radar from your internet menu, and you're all set. :) If you want to view the available networks or to configure your setup, simply run sudo wifi-radar. <br />
# You might need to edit /etc/conf.d/wifi-radar to set the particular network interface that you want to use.<br />
<br />
NB!: I had to set 'Ifup required' to ON to be able to get it to work with my line. Before this, the internet would not connect.<br />
<br />
===NetworkManager===<br />
'''NetworkManager''' A more advanced network management system for Linux. This is included in various Linux distributions and now can be used in Arch Linux. It is very painless for roaming users, and includes an easy-to-use GUI program for selecting your desired network. One caveat however is that you are prompted for your keyring password every time you log into gnome and the program starts. This most likely won't be fixed until later versions, and can be quite annoying. More information on NetworkManager can be found at: [[Networkmanager]].<br />
<br />
==Misc Links==<br />
*[http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Wireless.html An overly wordy howto that rarely helps]<br />
*[http://madwifi.org/wiki/UserDocs/FirstTimeHowTo The madwifi project's method of installing, good if you're having trouble doing it the Arch way]</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_701&diff=32236ASUS Eee PC 7012007-11-10T22:21:04Z<p>Bladesonfire: </p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
WARNING: THIS ARTICLE IS INCOMPLETE! Visit the Arch forum thread link below to get information on installing Arch Linux on the Asus EEE PC. <br />
<br />
Most of this information is from the [http://bbs.archlinux.org/viewtopic.php?pid=297632 Arch Forum]. You can also find a lot of helpful information from the [http://forum.eeeuser.com/ EEEUser Forum].<br />
<br />
==Before You Begin==<br />
<br />
===Avoiding Pitfalls===<br />
<br />
The install is pretty normal, except that you'll need to [http://forum.eeeuser.com/viewtopic.php?id=890 avoid the pitfalls] of our alternative Linux install:<br />
<br />
# Never choose to use a journaling file system on the SSD partitions<br />
# Never use a swap partition on the SSD<br />
# Always edit your new installation fstab to mount the SSD partitions "noatime"<br />
# Never log messages or error log to the SSD<br />
<br />
Thee rules ensure that we won't reach the maximum limit of writes on our SSD faster than we should.<br />
<br />
===Choosing Your Kernel===<br />
<br />
Because the hardware is not supported by the default Arch kernel, you'll need to get the hardware up and running through one of the following methods:<br />
<br />
====Arch Kernel and Ndiswrapper====<br />
<br />
Probably the easiest to implement. Install Arch as normal (with the minor kinks found in this article), then install the Windows XP wireless driver found on Asus' website and use Ndiswrapper to get wireless working:<br />
<br />
# Go to Asus' website and download the driver ([http://dlsvr03.asus.com/pub/ASUS/EeePC/EeePC4G(701)/Wireless_XP_071011.zip direct link]).<br />
# Unzip the file and save the contents of the 'ndis5x' folder for use after you install Arch Linux.<br />
<br />
====Compile the 'everything' Kernel====<br />
<br />
The 'everything' kernel has ath5k, which supports the Atheros chipset found on the EEE PC. Here are the [http://linuxwireless.org/en/users/Drivers/ath5k#Hackingath5k instructions on compiling the 'everthing' kernel] (thanks raymano!).<br />
<br />
====Using the EEE PC's Kernel====<br />
<br />
The EEE PC's kernel has all the hardware working through its modules, so why not use it? Grab a few debs from the [http://update.eeepc.asus.com/p701/pool/ EEE PC package source mirror] to your Arch install to make your life easier. They include:<br />
<br />
* The Kernel (linux-image-2.6.21.4-eeepc_3_i386.deb)<br />
* Wireless driver (atheros-swan-modules-2.6.21.4-eeepc_20070713-2_i386.deb)<br />
* LAN driver (atl2-modules-2.6.21.4-eeepc_1.0.40.4-2_i386.deb)<br />
* Webcam driver (uvcvideo-modules-2.6.21.4-eeepc_20070706-2_i386.deb)<br />
* Modem driver (hsfmodem-modules-2.6.21.4-eeepc_7.60.00.04oem-4_i386.deb)<br />
* ACPI (asus-acpi_1.38-1xandros5_i386.deb)<br />
<br />
Now just extract the deb files and save the data.tar.gz files. I also grabbed the xorg.conf, since it has all the Synaptic touchpad info in it.<br />
<br />
===Choosing Your Installation Media===<br />
<br />
The EEE PC does not have an optical drive installed on the machine. This means you will need to install Arch Linux through one of the alternative methods:<br />
<br />
# External USB CD-ROM drive<br />
# [[Install_from_USB_stick|USB pen drive]]<br />
<br />
Unfortunately, the kernel does not include drivers for a LAN or Wireless install. If anyone knows how to do this, they're more than welcome to add this information in =D<br />
<br />
===And Always Remember...===<br />
<br />
And I shouldn't have to tell you this: always back up your data ;)<br />
<br />
It's now time to install Arch Linux (hooray!).<br />
<br />
==Installing Arch Linux==<br />
<br />
Note: if you're using the USB pen drive as your media, don't forget to [[Install_from_USB_stick#After_booting_from_the_USB_stick:|follow these instructions]].<br />
<br />
===Prepare Hard Drive===<br />
<br />
The drive is split up into four partitions (here's [http://forum.eeeuser.com/viewtopic.php?id=1805 some information] about the partitioning): <br />
<br />
* I don't know how other people did it, but I ended up wiping the entire disk and using one partition for the install.<br />
* Choose "NONE" for swap (see #2 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
* Select "ext2" as your filesystem (see #1 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
<br />
===Select Packages===<br />
<br />
The only thing here is if you're using a USB pen drive as your media, select "SRC".<br />
<br />
===Install Packages===<br />
<br />
Nothing to see here.<br />
<br />
===Configure System===<br />
<br />
Make these edits to "/etc/fstab":<br />
<br />
* Add "noatime" to the options of your mounts (see #3 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
* Add a new line: "tmpfs /var/log tmpfs defaults 0 0" (WARNING: this will delete all your logs! See #4 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
** To save your startup/shutdown logs, look at the pitfalls link above.<br />
<br />
===Install Bootloader===<br />
<br />
To decrease boot time, I set "timeout" to 0. It's all about boot up time ;)<br />
<br />
===Reboot===<br />
<br />
Hooray ;)<br />
<br />
==Getting Everything Working==<br />
<br />
By now, you should have Arch installed. When I get back, I'll show you how to make it usable.<br />
<br />
====Arch Kernel and Ndiswrapper====<br />
<br />
<br />
<br />
====Compile the 'everything' Kernel====<br />
<br />
<br />
<br />
====Using the EEE PC's Kernel====</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_701&diff=32234ASUS Eee PC 7012007-11-10T21:53:11Z<p>Bladesonfire: Mostly formatting changes, added section for compiling from 'everything' kernel</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
WARNING: THIS ARTICLE IS INCOMPLETE! Visit the Arch forum thread link below to get information on installing Arch Linux on the Asus EEE PC. <br />
<br />
Most of this information is from the [http://bbs.archlinux.org/viewtopic.php?pid=297632 Arch Forum]. You can also find a lot of helpful information from the [http://forum.eeeuser.com/ EEEUser Forum].<br />
<br />
==Before You Begin==<br />
<br />
===Avoiding Pitfalls===<br />
<br />
The install is pretty normal, except that you'll need to [http://forum.eeeuser.com/viewtopic.php?id=890 avoid the pitfalls] of our alternative Linux install:<br />
<br />
# Never choose to use a journaling file system on the SSD partitions<br />
# Never use a swap partition on the SSD<br />
# Always edit your new installation fstab to mount the SSD partitions "noatime"<br />
# Never log messages or error log to the SSD<br />
<br />
Thee rules ensure that we won't reach the maximum limit of writes on our SSD faster than we should.<br />
<br />
===Choosing Your Kernel===<br />
<br />
Because the hardware is not supported by the default Arch kernel, you'll need to get the hardware up and running through one of the following methods:<br />
<br />
====Arch Kernel and Ndiswrapper====<br />
<br />
Probably the easiest to implement. Install Arch as normal (with the minor kinks found in this article), then install the Windows XP wireless driver found on Asus' website and use Ndiswrapper to get wireless working:<br />
<br />
# Go to Asus' website and download the driver ([http://dlsvr03.asus.com/pub/ASUS/EeePC/EeePC4G(701)/Wireless_XP_071011.zip direct link]).<br />
# Unzip the file and save the contents of the 'ndis5x' folder for use after you install Arch Linux.<br />
<br />
====Compile the 'everything' Kernel====<br />
<br />
The 'everything' kernel has ath5k, which supports the Atheros chipset found on the EEE PC. Here are the [http://linuxwireless.org/en/users/Drivers/ath5k#Hackingath5k instructions on compiling the 'everthing' kernel] (thanks raymano!).<br />
<br />
====Using the EEE PC's Kernel====<br />
<br />
The EEE PC's kernel has all the hardware working through its modules, so why not use it? Grab a few debs from the Xandros install to your Arch install to make your life easier. They include:<br />
<br />
* The Kernel (linux-image-2.6.21.4-eeepc_3_i386.deb)<br />
* Wireless driver (atheros-swan-modules-2.6.21.4-eeepc_20070713-2_i386.deb)<br />
* LAN driver (atl2-modules-2.6.21.4-eeepc_1.0.40.4-2_i386.deb)<br />
* Webcam driver (uvcvideo-modules-2.6.21.4-eeepc_20070706-2_i386.deb)<br />
* Modem driver (hsfmodem-modules-2.6.21.4-eeepc_7.60.00.04oem-4_i386.deb)<br />
<br />
Now just extract the deb files and save the data.tar.gz files in them. I also grabbed the xorg.conf, since it has all the Synaptic touchpad info in it.<br />
<br />
===Choosing Your Installation Media===<br />
<br />
The EEE PC does not have an optical drive installed on the machine. This means you will need to install Arch Linux through one of the alternative methods:<br />
<br />
# External USB CD-ROM drive<br />
# [[Install_from_USB_stick|USB pen drive]]<br />
<br />
Unfortunately, the kernel does not include drivers for a LAN or Wireless install. If anyone knows how to do this, they're more than welcome to add this information in =D<br />
<br />
===And Always Remember...===<br />
<br />
And I shouldn't have to tell you this: always back up your data ;)<br />
<br />
It's now time to install Arch Linux (hooray!).<br />
<br />
==Installing Arch Linux==<br />
<br />
Note: if you're using the USB pen drive as your media, don't forget to [[Install_from_USB_stick#After_booting_from_the_USB_stick:|follow these instructions]].<br />
<br />
===Prepare Hard Drive===<br />
<br />
The drive is split up into four partitions (here's [http://forum.eeeuser.com/viewtopic.php?id=1805 some information] about the partitioning): <br />
<br />
* I don't know how other people did it, but I ended up wiping the entire disk and using one partition for the install.<br />
* Choose "NONE" for swap (see #2 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
* Select "ext2" as your filesystem (see #1 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]]).<br />
<br />
===Select Packages===<br />
<br />
The only thing here is if you're using a USB pen drive as your media, select "SRC".<br />
<br />
===Install Packages===<br />
<br />
Nothing to see here.<br />
<br />
===Configure System===<br />
<br />
Make these edits to "/etc/fstab":<br />
<br />
* Add "noatime" to the options of your mounts (see #3 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
* Add a new line: "tmpfs /var/log tmpfs defaults 0 0" (WARNING: this will delete all your logs! See #4 in [[Installing_Arch_Linux_on_the_Asus_EEE_PC#Avoiding_Pitfalls|Avoiding Pitfalls]])<br />
** To save your startup/shutdown logs, look at the pitfalls link above.<br />
<br />
===Install Bootloader===<br />
<br />
To decrease boot time, I set "timeout" to 0. It's all about boot up time ;)<br />
<br />
===Reboot===<br />
<br />
Hooray ;)<br />
<br />
==Getting Everything Working==<br />
<br />
By now, you should have Arch installed. When I get back, I'll show you how to make it usable.<br />
<br />
====Arch Kernel and Ndiswrapper====<br />
<br />
<br />
<br />
====Compile the 'everything' Kernel====<br />
<br />
<br />
<br />
====Using the EEE PC's Kernel====</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_701&diff=32205ASUS Eee PC 7012007-11-10T11:25:07Z<p>Bladesonfire: /* Configure System */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
Most of this information is from the Arch Forum (http://bbs.archlinux.org/viewtopic.php?pid=297632). You can also find a lot of helpful information from the EEEUser Forum (http://forum.eeeuser.com/).<br />
<br />
The install is pretty normal, except that you'll need to avoid the pitfalls of our alternative Linux install (http://forum.eeeuser.com/viewtopic.php?id=890):<br />
<br />
# Never choose to use a journaling file system on the SSD partitions<br />
# Never use a swap partition on the SSD<br />
# Always edit your new installation fstab to mount the SSD partitions "noatime"<br />
# Never log messages or error log to the SSD<br />
<br />
Thee rules ensure that we won't reach the maximum limit of writes on our SSD faster than we should.<br />
<br />
==Before You Begin==<br />
<br />
Before you begin, you'll want to grab a few debs from the Xandros install to your Arch install to make your life easier. They include:<br />
<br />
* The Kernel (linux-image-2.6.21.4-eeepc_3_i386.deb)<br />
* Wireless driver (atheros-swan-modules-2.6.21.4-eeepc_20070713-2_i386.deb)<br />
* LAN driver (atl2-modules-2.6.21.4-eeepc_1.0.40.4-2_i386.deb)<br />
* Webcam driver (uvcvideo-modules-2.6.21.4-eeepc_20070706-2_i386.deb)<br />
* Modem driver (hsfmodem-modules-2.6.21.4-eeepc_7.60.00.04oem-4_i386.deb)<br />
<br />
I also grabbed the xorg.conf, since it has all the Synaptic touchpad info in it.<br />
<br />
And I shouldn't have to tell you this: always back up your data ;)<br />
<br />
==Choosing Your Installation Media==<br />
<br />
The EEE PC does not have an optical drive installed on the machine. This means you will need to install Arch Linux through one of the alternative methods:<br />
<br />
# External USB CD-ROM drive<br />
# [[Install_from_USB_stick|USB pen drive]]<br />
<br />
Unfortunately, the kernel does not include drivers for a LAN or Wireless install. If anyone knows how to do this, they're more than welcome to add this information in =D<br />
<br />
After choosing your installation media, it's now time to install Arch Linux (hooray!).<br />
<br />
==Installing Arch Linux==<br />
<br />
Note: if you're using the USB pen drive as your media, don't forget to [[Install_from_USB_stick#After_booting_from_the_USB_stick:|follow these instructions]]<br />
<br />
===Prepare Hard Drive===<br />
<br />
The drive is split up into four partitions, and information about them can be found here: http://forum.eeeuser.com/viewtopic.php?id=1805<br />
<br />
* I don't know how other people did it, but I ended up combining the first two partitions.<br />
* Choose "NONE" for swap (see #2 in pitfalls).<br />
* Select "ext2" as your filesystem (see #1 in pitfalls).<br />
<br />
===Select Packages===<br />
<br />
The only thing here is if you're using a USB pen drive as your media, select "SRC".<br />
<br />
===Install Packages===<br />
<br />
Nothing to see here.<br />
<br />
===Configure System===<br />
<br />
Make these edits to "/etc/fstab":<br />
<br />
* Add "noatime" to the options of your mounts (see #3 in pitfalls)<br />
* Add a new line: "tmpfs /var/log tmpfs defaults 0 0" (WARNING: this will delete all your logs! See #4 in pitfalls)<br />
** To save your startup/shutdown logs, look at the pitfalls link above. I haven't done it and can't add any advice to what's on that thread.<br />
<br />
===Install Bootloader===<br />
<br />
To decrease boot time, I set "timeout" to 0. It's all about boot up time ;)<br />
<br />
===Reboot===<br />
<br />
Hooray ;)<br />
<br />
==Getting Everything Working==<br />
<br />
By now, you should have Arch installed. When I get back, I'll show you how to make it usable.</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_701&diff=32193ASUS Eee PC 7012007-11-10T09:38:17Z<p>Bladesonfire: /* Configure System */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
Most of this information is from the Arch Forum (http://bbs.archlinux.org/viewtopic.php?pid=297632). You can also find a lot of helpful information from the EEEUser Forum (http://forum.eeeuser.com/).<br />
<br />
The install is pretty normal, except that you'll need to avoid the pitfalls of our alternative Linux install (http://forum.eeeuser.com/viewtopic.php?id=890):<br />
<br />
# Never choose to use a journaling file system on the SSD partitions<br />
# Never use a swap partition on the SSD<br />
# Always edit your new installation fstab to mount the SSD partitions "noatime"<br />
# Never log messages or error log to the SSD<br />
<br />
Thee rules ensure that we won't reach the maximum limit of writes on our SSD faster than we should.<br />
<br />
==Before You Begin==<br />
<br />
Before you begin, you'll want to grab a few debs from the Xandros install to your Arch install to make your life easier. They include:<br />
<br />
* The Kernel (linux-image-2.6.21.4-eeepc_3_i386.deb)<br />
* Wireless driver (atheros-swan-modules-2.6.21.4-eeepc_20070713-2_i386.deb)<br />
* LAN driver (atl2-modules-2.6.21.4-eeepc_1.0.40.4-2_i386.deb)<br />
* Webcam driver (uvcvideo-modules-2.6.21.4-eeepc_20070706-2_i386.deb)<br />
* Modem driver (hsfmodem-modules-2.6.21.4-eeepc_7.60.00.04oem-4_i386.deb)<br />
<br />
I also grabbed the xorg.conf, since it has all the Synaptic touchpad info in it.<br />
<br />
And I shouldn't have to tell you this: always back up your data ;)<br />
<br />
==Choosing Your Installation Media==<br />
<br />
The EEE PC does not have an optical drive installed on the machine. This means you will need to install Arch Linux through one of the alternative methods:<br />
<br />
# External USB CD-ROM drive<br />
# [[Install_from_USB_stick|USB pen drive]]<br />
<br />
Unfortunately, the kernel does not include drivers for a LAN or Wireless install. If anyone knows how to do this, they're more than welcome to add this information in =D<br />
<br />
After choosing your installation media, it's now time to install Arch Linux (hooray!).<br />
<br />
==Installing Arch Linux==<br />
<br />
Note: if you're using the USB pen drive as your media, don't forget to [[Install_from_USB_stick#After_booting_from_the_USB_stick:|follow these instructions]]<br />
<br />
===Prepare Hard Drive===<br />
<br />
The drive is split up into four partitions, and information about them can be found here: http://forum.eeeuser.com/viewtopic.php?id=1805<br />
<br />
* I don't know how other people did it, but I ended up combining the first two partitions.<br />
* Choose "NONE" for swap (see #2 in pitfalls).<br />
* Select "ext2" as your filesystem (see #1 in pitfalls).<br />
<br />
===Select Packages===<br />
<br />
The only thing here is if you're using a USB pen drive as your media, select "SRC".<br />
<br />
===Install Packages===<br />
<br />
Nothing to see here.<br />
<br />
===Configure System===<br />
<br />
Make these edits to "/etc/fstab":<br />
<br />
* Add "noatime" to the options of your mounts (see #3 in pitfalls)<br />
* Add a new line: "tmpfs /var/log tmpfs defaults 0 0" (see #4 in pitfalls)<br />
** To save your startup/shutdown logs, look at the pitfalls link above. I haven't done it and can't add any advice to what's on that thread.<br />
<br />
===Install Bootloader===<br />
<br />
To decrease boot time, I set "timeout" to 0. It's all about boot up time ;)<br />
<br />
===Reboot===<br />
<br />
Hooray ;)<br />
<br />
==Getting Everything Working==<br />
<br />
By now, you should have Arch installed. When I get back, I'll show you how to make it usable.</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_701&diff=32192ASUS Eee PC 7012007-11-10T07:58:19Z<p>Bladesonfire: New page: Category:Getting and installing Arch (English) Category:HOWTOs (English) Most of this information is from the Arch Forum (http://bbs.archlinux.org/viewtopic.php?pid=297632). You c...</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
Most of this information is from the Arch Forum (http://bbs.archlinux.org/viewtopic.php?pid=297632). You can also find a lot of helpful information from the EEEUser Forum (http://forum.eeeuser.com/).<br />
<br />
The install is pretty normal, except that you'll need to avoid the pitfalls of our alternative Linux install (http://forum.eeeuser.com/viewtopic.php?id=890):<br />
<br />
# Never choose to use a journaling file system on the SSD partitions<br />
# Never use a swap partition on the SSD<br />
# Always edit your new installation fstab to mount the SSD partitions "noatime"<br />
# Never log messages or error log to the SSD<br />
<br />
Thee rules ensure that we won't reach the maximum limit of writes on our SSD faster than we should.<br />
<br />
==Before You Begin==<br />
<br />
Before you begin, you'll want to grab a few debs from the Xandros install to your Arch install to make your life easier. They include:<br />
<br />
* The Kernel (linux-image-2.6.21.4-eeepc_3_i386.deb)<br />
* Wireless driver (atheros-swan-modules-2.6.21.4-eeepc_20070713-2_i386.deb)<br />
* LAN driver (atl2-modules-2.6.21.4-eeepc_1.0.40.4-2_i386.deb)<br />
* Webcam driver (uvcvideo-modules-2.6.21.4-eeepc_20070706-2_i386.deb)<br />
* Modem driver (hsfmodem-modules-2.6.21.4-eeepc_7.60.00.04oem-4_i386.deb)<br />
<br />
I also grabbed the xorg.conf, since it has all the Synaptic touchpad info in it.<br />
<br />
And I shouldn't have to tell you this: always back up your data ;)<br />
<br />
==Choosing Your Installation Media==<br />
<br />
The EEE PC does not have an optical drive installed on the machine. This means you will need to install Arch Linux through one of the alternative methods:<br />
<br />
# External USB CD-ROM drive<br />
# [[Install_from_USB_stick|USB pen drive]]<br />
<br />
Unfortunately, the kernel does not include drivers for a LAN or Wireless install. If anyone knows how to do this, they're more than welcome to add this information in =D<br />
<br />
After choosing your installation media, it's now time to install Arch Linux (hooray!).<br />
<br />
==Installing Arch Linux==<br />
<br />
Note: if you're using the USB pen drive as your media, don't forget to [[Install_from_USB_stick#After_booting_from_the_USB_stick:|follow these instructions]]<br />
<br />
===Prepare Hard Drive===<br />
<br />
The drive is split up into four partitions, and information about them can be found here: http://forum.eeeuser.com/viewtopic.php?id=1805<br />
<br />
* I don't know how other people did it, but I ended up combining the first two partitions.<br />
* Choose "NONE" for swap (see #2 in pitfalls).<br />
* Select "ext2" as your filesystem (see #1 in pitfalls).<br />
<br />
===Select Packages===<br />
<br />
The only thing here is if you're using a USB pen drive as your media, select "SRC".<br />
<br />
===Install Packages===<br />
<br />
Nothing to see here.<br />
<br />
===Configure System===<br />
<br />
Make sure to edit /etc/fstab and add "noatime" to the options (see #3 in pitfalls)<br />
<br />
===Install Bootloader===<br />
<br />
To decrease boot time, I set "timeout" to 0. It's all about boot up time ;)<br />
<br />
===Reboot===<br />
<br />
Hooray ;)<br />
<br />
==Getting Everything Working==<br />
<br />
By now, you should have Arch installed. When I get back, I'll show you how to make it usable.</div>Bladesonfirehttps://wiki.archlinux.org/index.php?title=The_Arch_Way&diff=24664The Arch Way2007-05-23T22:31:48Z<p>Bladesonfire: /* Comments */</p>
<hr />
<div>[[Category:About Arch (English)]]<br />
[[Category:General (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|The Arch Way}}<br />
{{i18n_entry|Polski|The Arch Way (Polski)}}<br />
{{i18n_entry|Português de Portugal|À Maneira do Arch}}<br />
{{i18n_entry|Русский|Путь_Arch}}<br />
{{i18n_entry|Česky|Principy a filozofie Arch Linuxu (Česky)}}<br />
{{i18n_entry|Italiano|The Arch Way (Italiano)}}<br />
{{i18n_entry|Français|The Arch Way (Français)}}<br />
{{i18n_links_end}}<br />
<br />
English<br />
= Arch Principles & Philosophy =<br />
This page attempts to describe the principles and philosophy of [[ArchLinux|Arch Linux]]. There once was no written document about the Arch Way; most likely that will never happen again. In short, the Arch Way stands for "<b>freedom of choice, keep it simple, learning, and user-control</b>".<br />
<br />
== Principles ==<br />
I, Judd Vinet, started building Arch for two reasons:<br />
<br />
# I didn't find any other distributions that met my ideals. Some came very close to what I wanted but there were annoying quirks or needless complexity that seemed to hurt more than help;<br />
# For fun - to give a little something back to the free software community, from which I've taken so much.<br />
<br />
<br />
By its basic nature, Arch is:<br />
<br />
* Lightweight and simple. Note that doesn't mean it's for everyone....<br />
<br />
* NOT designed as a newbie distro; it's intended for more experienced users. The aim is to develop Arch into as nearly a perfect base as is humanly possible. A base doesn't include fancy tools and auto configuration mechanisms, but rather contains manual configuration tools and few functions, for the users to further develop and/or learn on their own.<br />
<br />
* A free gift, again, "...to give a little something back to the free software community, from which I've taken so much." When you receive a gift from someone, it's usually expected to give something in return. As such, users are welcome to contribute their ideas, tools and suggestions.<br />
<br />
* Aware there are two sides which contribute to Arch Linux: Developers and Users. Don't expect the two sides to merge, but to have a mutual relationship whereby anyone can pick up what they want to add to their machine; our GOALs are to:<br />
<br />
* NOT let configure tools / GUIs control the system, but that they be controlled by the user. There is nothing wrong with GUIs as long as they follow this principle.<br />
<br />
* NOT be controlled by or dependent on what tools offer. When developing or selecting a utility tool, it should be written in a hackable/readable programming language (KISS) to enable users to modify it if they so choose.<br />
<br />
* The core development of Arch Linux will NOT be providing any "newbie-friendly" GUIs/utilities at any time in the near future.<br />
<br />
* We humble developers will continue to provide Arch as a solid base for everyone and anyone. If you guys want to make it pretty, give 'er a rip. Free speech, free beer, and all that.<br />
<br />
== Philosophy ==<br />
<br />
The System of values by which Arch develops:<br />
<br />
* KISS (Keep It Simple, ...) is the basis of Arch development.<br />
<br />
* In Arch, 'simple' doesn't always mean what it does in other distros. It's our philosophy that the learning is more important than getting something easily done.<br />
<br />
* Relying on GUIs to build and use your system is just going to hurt a user in the end. At some point in time a user will need to know all that some GUIs hide.<br />
<br />
* If you try to hide the complexity of the system, you'll end up with a more complex system. Instead, try to make the system simpler and more logical from the inside.<br />
<br />
* Sooner or later, you'll have to find the information on the web and usenet (if man is not enough). Learning how and where to find it on the net should be the first thing a newbie has to learn.<br />
<br />
* Where some users say "...such and such distro isn't like so and so distro," Arch allows the user to make all the contributions they want as long as it doesn't go against the ideals of the design or philosophy.<br />
<br />
* Arch Linux is different from the others: at Arch, the user isn't the only concern. Minimizing development of new tools and docs while maximizing understanding of Linux' inner workings, while keeping a watchful eye always on the "KISS" aim and philosophy of Arch Linux in general...is what makes the "Arch Way" truly different.<br />
<br />
* The great thing about contributions is that you don't need anyone's permission to make them. (See?) No one can physically stop you from writing something that you (personally) find useful, even if the "powers that be" don't see it as a blessing. Write it and put it up in the User Contributions forum. If other people like it, you'll receive feedback. If virtually everyone out there hates it but you, you'll receive feedback, for sure - but who cares? It took you 20 minutes to write, and you learned something along the way. It's a winning situation no matter what.<br />
<br />
* It is what you make it.<br />
<br />
== Comments ==<br />
<br />
What users have said about Arch:<br />
<br />
* "I did a distro taste test with zenwalk(slack based), debian, Redhat fedora, redhat Enterprise, T2, freebsd, netbsd, gobolinux, and SUSE. Arch won in a close one over FreeBSD. Why? It was simple to get up n running with X, packages were VERY current and simple to install, and I didn't have to wait all day for something to compile, but my apps are compiled i686 so they are fast. Updates of whole box did not squash apps as Redhat seemed to. To me as a linux admin I am looking to bring up box, and for home use X, and then be able to add apps and libraries as I see fit. Once the box is up, hand it off to developers, or develop on it myself. Other distros had a lame package system, out of date packages, and simply had no docs to config thier systems without a GUI. Arch provides the shortest step from A to B. To read more of why I stick with Arch read the section: Arch v other distros."<br />
<br />
<br />
* "After spending a lot of time with other distributions (debian, gentoo, mandrake, redhat, fedora, slackware) and even FreeBSD. I think that I finally found the distribution I was looking for."<br />
<br />
* Same thing with (k)ubuntu, Mandriva, and several others. Well, openSUSE is nice and easy (that's the one I would advice for my sister); but Arch is the One which really *rocks*.<br />
<br />
* "I have tried several distro's and even took (tired?) RHCE (took it BACK?), but there was always something I disliked about each."<br />
<br />
* "My dream distro was always the simplicity of Slackware with real dependency support like Debian's, and guess what - that's Arch."<br />
<br />
* "I also found Arch my final distro."<br />
<br />
* "After trying out almost all the available distributions, I have to agree that Arch is the best."<br />
<br />
* "Hi all. I just registered here so I could report all the problems I'm having, and ask for help. Funny thing is, I HAVE NO PROBLEMS!!! I really can't believe this, but everything is just working! I installed Arch today, had a little trouble with xorg and sound setup, but found all the answers I needed in the documentation and the forums!"<br />
<br />
* "I tried Mandrake, Yoper, FC3/4, Mepis and Ubuntu. I was looking for the perfect distro. I am glad that I found Arch."<br />
<br />
* "I've always been looking for an easy-to-use distribution that didn't bloat the system and was customizable without breaking the system. After trying so many distributions, I found Arch Linux the way to go. And best of all, it's like using my very first distro (Slackware), but with benefits like Pacman and KDEmod."<br />
<br />
----<br />
<br />
= PROS and CONS =<br />
<br />
== PROS ==<br />
<br />
* i686-optimized<br />
* [[pacman]]: 'System Upgrade' is ONE command: "pacman -Suy"<br />
* [[pacman]]: Dependency-control, no X/GUI needed<br />
* [[ABS]]: the package-building function need only be done once - building another version of a package is extremely easy<br />
* [[ABS]]: you can build all the packages on your machine with one command<br />
* fully up-to-date packages at your request, and fully customizable<br />
* the people behind the scenes are gentle, motivated and able<br />
* less than 20 minutes to create a fully functional system<br />
* the perfect environment to learn Linux in<br />
* not really popular, because not known (still relevant?)<br />
<br />
== CONS ==<br />
<br />
* [[pacman]]: needs a fast internet connection to stay always up-to-date easily (less of a problem as time marches forward)<br />
* some conflicts from using the newest libs ("bleeding edge")<br />
* lack of newbie-friendly features<br />
* very little hardware detection (relevant?)<br />
* info files are almost always way more detailed than man-pages (gcc.info e.g.)<br />
* not really popular, because not known</div>Bladesonfire