https://wiki.archlinux.org/api.php?action=feedcontributions&user=Wilco&feedformat=atomArchWiki - User contributions [en]2024-03-29T10:41:26ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=ASUS_Zenbook_UX305&diff=431164ASUS Zenbook UX3052016-04-14T12:33:41Z<p>Wilco: /* Brightness Keys */</p>
<hr />
<div>[[Category:ASUS]]<br />
{{Expansion}}<br />
This page contains instructions, tips, pointers, and links for installing and configuring Arch Linux on the [http://www.asus.com/Notebooks_Ultrabooks/ASUS_ZENBOOK_UX305/Features/ ASUS Zenbook UX305].<br />
<br />
Hardware reference from UX305-FB041H. Model available since '''12 feb 2015'''.<br />
<br />
== Hardware lists ==<br />
<br />
See [https://gist.github.com/anonymous/6363a5462af10ee18c0c] for specific hardware information.<br />
<br />
See [https://gist.github.com/precurse/6dc1990cd000551c8f11] for UX305CA (Skylake) hardware information. Physically labelled with UX305C on laptop, but UX305CA shows in dmesg. See and contribute to discussion tab of this page for fixes.<br />
<br />
== Compatibility ==<br />
<br />
=== Touchpad ===<br />
<br />
See [[Touchpad Synaptics]] for details.<br />
<br />
Multi-touch scrolling works as of kernel 3.16.<br />
<br />
If default Palm Detection doesn't work well, one can manually disable part of the trackpad by setting AreaEdge properties.<br />
<br />
You can do this on the fly or add these parameters in the config file:<br />
<br />
$ synclient AreaLeftEdge=500<br />
$ synclient AreaRightEdge=2500<br />
<br />
'''UX305C:'''<br />
<br />
Touchpad will only work by default with Linux 4.5.0-rc1 or later. Can currently be used by installing {{AUR|linux-mainline}}.<br />
<br />
'''UX305UA'''<br />
<br />
Touchpad works great on Linux-4.4.3 kernel and superior.<br />
<br />
=== Wifi ===<br />
<br />
Intel Dual Band wifi. Should work with recent kernels. 3.10+ with iwlwifi. See [[Wireless network configuration#iwlwifi]] for details.<br />
<br />
=== Graphics ===<br />
<br />
As of {{Pkg|linux}} 3.16, virtual terminals show a blank screen.<br />
<br />
UEFI results with memory changes for the Intel graphic card:<br />
<br />
With 32-256MB memory assignment in bios: Works.<br />
With 512MB memory assignment: '''X11 breaks'''. 1/3th upper-part of screen semi works (swapped and mis-alligned), rest is noise/snow.<br />
<br />
Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1151757<br />
<br />
Kernel 3.16 boots with usable tty/x11 via bootparam: nomodeset<br />
<br />
See also [[Intel graphics#SNA issues]].<br />
<br />
=== QHD monitor ===<br />
<br />
Some models include a 3200x1800 screen, which display very tiny characters.<br />
<br />
For Firefox and Thunderbird, add the below property in the about:config area<br />
<br />
layout.css.devPixelsPerPx=2.<br />
<br />
=== Function Keys ===<br />
<br />
Kernel 3.16 with {{ic|acpi_listen}}, when pressing {{ic|Fn+F12}} (volup), {{ic|Fn+F11}} (voldown), {{ic|Fn+F10}} (mute), {{ic|F9}} (disable mousepad):<br />
<br />
button/volumeup VOLUP 00000080 00000000 K<br />
button/volumedown VOLDN 00000080 00000000 K<br />
button/mute MUTE 00000080 00000000 K<br />
PNP0C14:00 000000ff 00000000<br />
<br />
The light(sensor?) button (fn+a) returns:<br />
<br />
PNP0C14:00 000000ff 00000000<br />
<br />
Tested with:<br />
<br />
# modprobe -D asus-laptop<br />
<br />
And/Or:<br />
<br />
# modprobe -D asus-nb-wmi<br />
<br />
No effect so far. Investigate.<br />
<br />
==== Brightness Keys ====<br />
For whatever reason, {{ic|xev}} does not return any events for the standard brightness keys, but {{ic|F3}} and {{ic|F4}} seem to be detected as {{ic|XF86KbdBrightnessDown}} and {{ic|XF86KbdBrightnessUp}}, respectively.<br />
<br />
You can create your own shortcut on gnome, on keyboard configuration, associating a key with the commands:<br />
xdotool key XF86MonBrightnessUp<br />
xdotool key XF86MonBrightnessDown<br />
<br />
You need to install xdotool first.<br />
<br />
There is also a kernel patch which enables the proper brightness keys. This patch is tested with 4.4 kernels: https://bugzilla.kernel.org/attachment.cgi?id=195071<br />
<br />
== See also ==<br />
<br />
* [[ASUS Zenbook UX303]]<br />
* https://wiki.debian.org/InstallingDebianOn/Asus/UX31a<br />
* https://wiki.debian.org/InstallingDebianOn/Asus/UX301LA</div>Wilcohttps://wiki.archlinux.org/index.php?title=Broadcom_wireless&diff=200366Broadcom wireless2012-05-05T18:11:16Z<p>Wilco: /* Miscellaneous user notes */</p>
<hr />
<div>{{i18n|Broadcom wireless}}<br />
[[Category:Wireless Networking]]<br />
<br />
== Introduction ==<br />
<br />
Broadcom has been notorious in its support for its Wi-Fi cards on GNU/Linux. Until recently, most Broadcom chips were either entirely unsupported or required the user to tinker with firmware. A limited set of wireless chips were supported by various reverse-engineered drivers ({{ic|brcm4xxx}}, {{ic|b43}}, etc.). The reverse-engineered [http://wireless.kernel.org/en/users/Drivers/b43 {{ic|b43}}] drivers have been in the kernel since 2.6.24.<br />
<br />
In August 2008, Broadcom released the [http://www.broadcom.com/support/802.11/linux_sta.php 802.11 Linux STA driver] officially supporting Broadcom wireless hardware on GNU/Linux. These are restrictively licensed drivers, but Broadcom promised to work towards a more open approach in the future. Further, they do not work with hidden ESSIDs.<br />
<br />
In September 2010, Broadcom [http://thread.gmane.org/gmane.linux.kernel.wireless.general/55418 finally released] fully open source drivers for its hardware. This driver, [http://wireless.kernel.org/en/users/Drivers/brcm80211 {{ic|brcm80211}}], has been included into the kernel since 2.6.37. With the release of 2.6.39, these drivers have been renamed to {{ic|brcmsmac}} and {{ic|brcmfmac}}.<br />
<br />
At the time of writing, there are three choices for users with Broadcom Wi-Fi chipsets:<br />
<br />
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"<br />
! Driver !! Description<br />
|-<br />
|brcmsmac/brcmfmac || Open source kernel driver<br />
|-<br />
|b43 || Reversed engineered kernel driver<br />
|-<br />
|broadcom-wl || Proprietary Broadcom STA driver<br />
|}<br />
<br />
== Determine which driver you need/can use ==<br />
<br />
First, determine your card's [http://en.wikipedia.org/wiki/PCI_configuration_space PCI-ID]. Type the following (case-sensitive) command into a console:<br />
$ lspci -vnn | grep 14e4<br />
<br />
If your card is in the following list, you can use the [[#brcmsmac.2Fbrcmfmac|{{ic|brcmsmac}} driver]]:<br />
{| border="1"<br />
! PCI-ID !! Name<br />
|-<br />
| {{ic|[14e4:4727]}} || BCM4313<br />
|-<br />
| {{ic|[14e4:4353]}} || BCM43224 <br />
|-<br />
| {{ic|[14e4:4357]}} || BCM43225<br />
|}<br />
If your card is in the following list, you can use the [[#brcmsmac.2Fbrcmfmac|{{ic|brcmfmac}} SDIO driver]]:<br />
{| border="1"<br />
! Name<br />
|-<br />
| BCM4329<br />
|}<br />
A more up-to-date list may be found [http://linuxwireless.org/en/users/Drivers/brcm80211 here].<br />
<br />
If your card is not in the above lists, you need to use the older {{ic|b43}} or {{ic|b43legacy}} driver, which supports following devices.<br />
{| border="1"<br />
! PCI-ID !! Name !! Notes<br />
|-<br />
| {{ic|[14e4:4301]}} || BCM4301 || legacy-only<br />
|-<br />
| {{ic|[14e4:4306]}} || BCM4306 || ?legacy<br />
|-<br />
| {{ic|[14e4:4307]}} || BCM4306 ||<br />
|-<br />
| {{ic|[14e4:4311]}} || BCM4311 ||<br />
|-<br />
| {{ic|[14e4:4312]}} || BCM4311 ||<br />
|-<br />
| {{ic|[14e4:4313]}} || BCM4311 ||<br />
|-<br />
| {{ic|[14e4:4315]}} || BCM4312 || b43 has problems with this model, try broadcom-wl driver insead. Not in kernel26-lts<br />
|-<br />
| {{ic|[14e4:4318]}} || BCM4318 ||<br />
|-<br />
| {{ic|[14e4:4319]}} || BCM4318 ||<br />
|-<br />
| {{ic|[14e4:4320]}} || BCM4306 || ?legacy<br />
|-<br />
| {{ic|[14e4:4321]}} || BCM4321 || Not in kernel26-lts<br />
|-<br />
| {{ic|[14e4:4324]}} || BCM4306 || legacy-only<br />
|-<br />
| {{ic|[14e4:4325]}} || BCM4306 || legacy-only<br />
|-<br />
| {{ic|[14e4:4328]}} || BCM4321 || Not in kernel26-lts<br />
|-<br />
| {{ic|[14e4:4329]}} || BCM4321 || Not in kernel26-lts<br />
|-<br />
| {{ic|[14e4:432a]}} || BCM4321 ||<br />
|-<br />
| {{ic|[14e4:432b]}} || BCM4322 || Not in kernel26-lts<br />
|-<br />
| {{ic|[14e4:432c]}} || BCM4322 ||<br />
|-<br />
| {{ic|[14e4:432d]}} || BCM4322 ||<br />
|-<br />
| {{ic|[14e4:4358]}} || BCM43227 ||<br />
|-<br />
| {{ic|[14e4:4359]}} || BCM43228 ||<br />
|}<br />
?legacy means that there are devices with same PCI-IDs, but with different hardware available.<br />
Some of these work with the {{ic|b43}} driver, but some might need {{ic|b43legacy}} driver.<br />
legacy-only means that you need to use the {{ic|b43legacy}} driver.<br />
<br />
A more up-to-date list may be found [http://linuxwireless.org/en/users/Drivers/b43 here].<br />
<br />
If your card is in the following list, you can use the [[#broadcom-wl|{{ic|broadcom-wl}} driver]]:<br />
{| border="1"<br />
! PCI-ID !! Name<br />
|-<br />
| {{ic|[14e4:4311]}} || BCM4311<br />
|-<br />
| {{ic|[14e4:4312]}} || BCM4311<br />
|-<br />
| {{ic|[14e4:4313]}} || BCM4311<br />
|-<br />
| {{ic|[14e4:4315]}} || BCM4312<br />
|-<br />
| {{ic|[14e4:4727]}} || BCM4313<br />
|-<br />
| {{ic|[14e4:4328]}} || BCM4321<br />
|-<br />
| {{ic|[14e4:4329]}} || BCM4321<br />
|-<br />
| {{ic|[14e4:432a]}} || BCM4321<br />
|-<br />
| {{ic|[14e4:432b]}} || BCM4322<br />
|-<br />
| {{ic|[14e4:432c]}} || BCM4322<br />
|-<br />
| {{ic|[14e4:432d]}} || BCM4322<br />
|-<br />
| {{ic|[14e4:4353]}} || BCM43224<br />
|-<br />
| {{ic|[14e4:4357]}} || BCM43225<br />
|-<br />
| {{ic|[14e4:4358]}} || BCM43227<br />
|-<br />
| {{ic|[14e4:4359]}} || BCM43228<br />
|}<br />
A more up-to-date list may be found [http://www.broadcom.com/docs/linux_sta/README.txt here].<br />
<br />
== Getting the driver ==<br />
<br />
=== brcmsmac/brcmfmac ===<br />
The {{ic|brcm80211}} drivers have been included in the kernel since 2.6.37. Since the release of 2.6.39, they have been renamed to {{ic|brcmsmac}} (for PCI cards) and {{ic|brcmfmac}} (for SDIO).<br />
<br />
These drivers should be automatically loaded during startup and no further action should be required of the user.<br />
<br />
{{Note|The {{ic|bcma}} module can prevent some cards from showing up and may need to be [[#Wi-Fi_card_does_not_work.2Fshow_up_since_kernel_upgrade_.28brcmsmac.29|blacklisted]].}}<br />
<br />
{{Note|Since linux 3.3.1 the {{ic|brcmsmac}} driver depends on the {{ic|bcma}} module and blacklisting is no longer required.}}<br />
<br />
{{Note|[http://wireless.kernel.org/en/users/Drivers/brcm80211 wireless.kernel.org] states that brcm80211 does not support older PCI/PCI-E chips with ssb backplane.}}<br />
<br />
=== b43/b43legacy ===<br />
The drivers are included in the kernel since 2.6.24.<br />
<br />
==== Loading the b43/b43legacy kernel module ====<br />
Verify which module you need by looking up your device [http://wireless.kernel.org/en/users/Drivers/b43#Known_PCI_devices here]. You can also check by computer model [http://linuxwireless.org/en/users/Drivers/b43/devices here]. Blacklist the other module (either {{ic|b43}} or {{ic|b43legacy}}) to prevent possible problems/confusion. For instructions, see [[Kernel_modules#Blacklisting]].<br />
<br />
Install the appropriate {{AUR|b43-firmware}} or {{AUR|b43-firmware-legacy}} package from the [[AUR]].<br />
<br />
You can now configure your device.<br />
<br />
=== broadcom-wl ===<br />
{{Warning|This driver is more likely to cause problems than to resolve them. Most of the problems reported by users on Broadcom chips are caused by this driver. Using this is HIGHLY NOT recommended. Before you even think of trying out this one, make sure to try the other drivers first.}}<br />
For users of the {{ic|broadcom-wl}} driver, there is a PKGBUILD available in the AUR ({{AUR|broadcom-wl}}). You can also download this driver directly from [http://www.broadcom.com/support/802.11/linux_sta.php Broadcom]. However, the PKGBUILD method is strongly encouraged, as that way will have [[pacman]] track all of the files.<br />
<br />
==== Loading the wl kernel module ====<br />
The {{ic|wl}} module may need to be manually loaded if there are other usable modules present. Before loading the {{ic|wl}} module, remove the {{ic|b43}} or other module that may have been automatically loaded instead:<br />
# rmmod b43<br />
<br />
Also unload {{ic|ssb}}, if loaded:<br />
# rmmod ssb<br />
<br />
{{Note|Failure to unload {{ic|ssb}} may result in the wireless interface not being created.}}<br />
<br />
Load the {{ic|wl}} module<br />
# modprobe wl<br />
<br />
The {{ic|wl}} module should automatically load {{ic|lib80211}} or {{ic|lib80211_crypt_tkip}}. Check with {{ic|lsmod}} to see if this is the case. If not, you may need to add one of those two modules as well.<br />
# modprobe lib80211<br />
<br />
or<br />
# modprobe lib80211_crypt_tkip<br />
<br />
If you installed the driver directly from Broadcom, you may also need to update the dependencies:<br />
# depmod -a<br />
<br />
To make the module load at boot, add {{ic|wl}} (and {{ic|lib80211}}/{{ic|lib80211_crypt_tkip}}, if needed) to your MODULES array in {{ic|/etc/rc.conf}}.<br />
MODULES=(... wl...)<br />
<br />
You can also blacklist other modules (to prevent them from interfering) in {{ic|/etc/modprobe.d/modprobe.conf}}. To blacklist a module just append a new line with the syntax {{ic|blacklist <module name>}}:<br />
blacklist b43<br />
blacklist ssb<br />
<br />
{{Warning|Broadcom Corporation BCM4311 802.11b/g WLAN [14e4:4311] does not work with blacklisting {{ic|b43}} and {{ic|ssb}}.}}<br />
<br />
== Troubleshooting ==<br />
=== Wi-Fi card does not work or show up after kernel upgrade (brcmsmac) ===<br />
<br />
This is caused by the kernel using the {{ic|bcma}} module instead of the {{ic|brcmsmac}} module. The solution is to blacklist the {{ic|bcma}} module. For instructions, see [[Kernel_modules#Blacklisting]].<br />
{{Note|This affects only Linux kernels 3.0, 3.1, and 3.2. Since kernel 3.3, the {{ic|brcmsmac}} module actually uses {{ic|bcma}}, so {{ic|bcma}} needs to be unblacklisted or the Wi-Fi interface will not appear.}}<br />
<br />
=== Wi-Fi card does not work when resuming from suspend (brcm80211) ===<br />
{{Note|This issue only affects Linux kernels 2.6.38 and earlier.}}<br />
The {{ic|brcm80211}} module needs to be unloaded before suspend and reloaded upon resume, otherwise Wi-Fi will not come back up. This is printed by {{ic|dmesg}}:<br />
wlc_coreinit: ucode did not self-suspend!<br />
wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on.<br />
psmdebug 0x000f8773, phydebug 0x00000000, psm_brc 0x0000<br />
<br />
The [[pm-utils]] page explains how to do this. If the file does not already exist, create a file called {{ic|modules}} or {{ic|config}} in {{ic|/etc/pm/config.d/}} and add/modify the following line:<br />
SUSPEND_MODULES="brcm80211"<br />
<br />
Now, the card should resume working correctly.<br />
<br />
An alternative procedure:<br />
<br />
1. Create the new file {{ic|/etc/pm/sleep.d/brcm.sh}}<br />
<br />
2. Insert this code and save:<br />
#!/bin/bash<br />
# Simple Bash script to fix resume from suspend issues...<br />
# Place this script in /etc/pm/sleep.d/<br />
# then chmod +x /etc/pm/sleep.d/brcm.sh<br />
case $1 in<br />
hibernate|suspend)<br />
/sbin/modprobe -r brcm80211<br />
;;<br />
thaw|resume)<br />
/sbin/modprobe brcm80211<br />
;;<br />
esac<br />
<br />
3. Make it executable:<br />
chmod +x /etc/pm/sleep.d/brcm.sh<br />
<br />
=== Wi-Fi card does not work/show up (broadcom-wl) ===<br />
Check if you are loading the correct modules. You may need to blacklist the {{ic|brcm80211}}, {{ic|b43}}, and {{ic|ssb}} kernel modules to prevent them from loading automatically. For instructions, see [[Kernel_modules#Blacklisting]].<br />
<br />
{{Note|You may not have to blacklist the {{ic|brcm80211}} driver; although as of 2011-06-20, it will still default to loading the {{ic|brcm80211}} module before the {{ic|wl}} driver, which prevents {{ic|wl}} from being used.}}<br />
<br />
Check if you updated your module dependencies:<br />
# depmod -a<br />
<br />
* Verify that your wireless interface(s) appear using {{ic|ip addr}}.<br />
* You may need to restart your machine to see the device appear in {{ic|iwconfig}} or {{ic|ip addr}}.<br />
* If you have recently upgraded your kernel, you need to rebuild the {{ic|broadcom-wl}} package with the new kernel installed to update the module.<br />
<br />
=== Interfaces swapped (broadcom-wl) ===<br />
Users of the {{ic|broadcom-wl}} driver may find their Ethernet and Wi-Fi interfaces have been swapped. The [http://wiki.archlinux.org/index.php/Udev#Mixed_Up_Devices.2C_Sound.2FNetwork_Cards_Changing_Order_Each_Boot udev] page explains how to resolve this. Create a file named {{ic|/etc/udev/rules.d/10-network.rules}} and bind the MAC address of each of your cards to a certain interface name:<br />
SUBSYSTEM=="net", ATTR{address}=="aa:bb:cc:dd:ee:ff", NAME="eth0"<br />
SUBSYSTEM=="net", ATTR{address}=="ff:ee:dd:cc:bb:aa", NAME="eth1"<br />
<br />
Ensure that the interface name appears correctly in {{ic|/etc/rc.conf}} and other configuration files that refer to it.<br />
<br />
=== Miscellaneous user notes ===<br />
* In my Dell Inspiron Laptop, I have a Broadcom BCM4401 Ethernet card and a Broadcom BCM4328 wireless card. If I just remove {{ic|b43}}, I can load the {{ic|wl}} driver, but no wireless card shows up. However, if I first remove the {{ic|b44}} (and {{ic|ssb}}) driver for my Ethernet card, and ''then'' load the {{ic|wl}} driver, I get a wireless device using the name ''eth0''. Afterwards, I can load {{ic|b44}} again, to have an Ethernet ''eth1'' device.<br />
<br />
* I could not get the BCM4313 chip on a Lenovo B560 to work before following these steps:<br />
*# "Load defaults" in the BIOS. After that, the wireless was working under MS Windows. There are not many options in there, so I do not know what the reset may have changed, but it did the trick.<br />
*# Blacklist the {{ic|acer_wmi}} module. For testing, you can add the following to the kernel line in GRUB: {{ic|acer_wmi.disable<nowiki>=</nowiki>1}}<br />
<br />
* I have found that to get the {{ic|wl}} drivers working for the Broadcom 4313 chip, you need to blacklist {{ic|brcm80211}} along with {{ic|b43}} and {{ic|ssb}}.<br />
<br />
* If you notice slow wireless speeds when your laptop/netbook is not connected to AC power, you may need to disable Wi-Fi power management by adding the following line (assuming ''wlan0'' is your wireless device) {{ic|iwconfig wlan0 power off}} to {{ic|/etc/rc.local}} and create an empty file {{ic|/etc/pm/power.d/wireless}}. In case you also experience interface swapping (discussed above), you might want to add another line for the second interface name as well. The command will have no effect on the wired interface.<br />
<br />
* In my case on a HP pavilion netbook DM1 with a BCM4313 chip, with the original kernel brcmsmac driver, the LED didn't work, the power was awful, and it kept loosing the signal all the time, unless very close to the wifi hotspot. The last broadcom driver {{ic|wl}} solved everything. So in some cases, it's actually better than the kernel driver. However, I had to install it in the initram image, along with lib80211 and lib80211_crypt_tkip to avoid a recurring kernel panic. (Use mkinitcpio)<br />
<br />
* On a similar HP DM1 netbook I found the brcmsmac driver did not work either. The kernel panic can also be solved by blacklisting the brcmsmac, b43 and wl drivers. In rc.local you can modprobe wl without problems. On a sidenote: I get hard lockups, without any way to debug because there is nothing in kernel.log. Not sure if related to the wl driver though.</div>Wilcohttps://wiki.archlinux.org/index.php?title=PhpMyAdmin&diff=86323PhpMyAdmin2009-12-04T20:44:58Z<p>Wilco: /* Configuration */</p>
<hr />
<div>[[Category:Web Server (English)]]<br />
==Pre-Installation==<br />
Read the [http://wiki.archlinux.org/index.php/LAMP LAMP] wiki entry to setup apache, php and mysql.<br />
<br />
==Installation==<br />
To install [http://www.phpmyadmin.net/ phpMyAdmin] just type this into the console.<br />
<br />
<pre><br />
#pacman -S phpmyadmin php-mcrypt<br />
</pre><br />
<br />
==Configuration==<br />
<br />
Make sure you delete any old version of phpmyadmin.<br />
<br />
<pre><br />
rm -r /srv/httpd/phpMyAdmin<br />
</pre><br />
<br />
Copy the example configuration file to your httpd configuration file directory.<br />
<br />
<pre><br />
cp /etc/webapps/phpmyadmin/apache.example.conf /etc/httpd/conf/extra/httpd-phpmyadmin.conf<br />
</pre><br />
<br />
Add the following line to /etc/httpd/conf/httpd.conf:<br />
<br />
<pre><br />
Include conf/extra/httpd-phpmyadmin.conf<br />
</pre><br />
<br />
You can type this into the console to produce the same effect:<br />
<br />
<pre><br />
echo -e "\nInclude conf/extra/httpd-phpmyadmin.conf" >> /etc/httpd/conf/httpd.conf<br />
</pre><br />
<br />
Comment out (or delete) 'deny form all' in /usr/share/webapps/phpMyAdmin/.htaccess, the line should look like this:<br />
<br />
<pre><br />
#deny from all<br />
</pre><br />
<br />
Otherwise you will get "Error 403 - Access forbidden!" when you try to access your phpmyadmin installation.<br />
<br />
Your '/etc/httpd/conf/extra/httpd-phpmyadmin.conf' should have the following information:<br />
<br />
<pre><br />
Alias /phpmyadmin/ "/usr/share/webapps/phpMyAdmin/"<br />
<Directory "/usr/share/webapps/phpMyAdmin"><br />
AllowOverride All<br />
Options FollowSymlinks<br />
Order allow,deny<br />
Allow from all<br />
</Directory><br />
</pre><br />
<br />
Open your '/etc/php/php.ini' and edit the line containing 'open_basedir' so it has the following:<br />
<br />
<pre><br />
:/usr/share/webapps/:/etc/webapps<br />
</pre><br />
<br />
For example, mine contains the following:<br />
<br />
<pre><br />
open_basedir = /srv/http/:/home/:/tmp/:/usr/share/pear/:/srv/:/usr/share/webapps/:/etc/webapps<br />
</pre><br />
<br />
You need the mcrypt module, so uncomment in {{Filename|/etc/php/php.ini}}:<br />
;extension=mcrypt.so<br />
:to<br />
extension=mcrypt.so<br />
<br />
==Access your phpmyadmin installation==<br />
<br />
You can access your phpmyadmin installation using the following url:<br />
<br />
<pre><br />
http://localhost/phpmyadmin/<br />
or<br />
http://localhost/phpmyadmin/index.php<br />
</pre><br />
<br />
Note: 'localhost' is the hostname in your /etc/rc.conf file.<br />
<br />
If you want to access it using:<br />
<br />
<pre><br />
http://localhost/phpmyadmin<br />
</pre><br />
<br />
in '/etc/httpd/conf/extra/httpd-phpmyadmin.conf' change:<br />
<br />
<pre><br />
Alias /phpmyadmin/ "/usr/share/webapps/phpMyAdmin/"<br />
</pre><br />
<br />
to<br />
<br />
<pre><br />
Alias /phpmyadmin "/usr/share/webapps/phpMyAdmin"<br />
</pre><br />
<br />
You should also read [http://bbs.archlinux.org/viewtopic.php?pid=632500 this thread].<br />
<br />
If you get the error "#2002 - The server is not responding (or the local MySQL server's socket is not correctly configured)" then you might want to change "localhost" in /etc/webapps/phpmyadmin/config.inc.php on this line:<br />
<br />
<pre><br />
$cfg['Servers'][$i]['host'] = 'localhost';<br />
</pre><br />
<br />
to your hostname specified in /etc/hosts and /etc/rc.conf under HOSTNAME.<br />
<br />
If you would like to use phpmyadmin setup script by calling http://localhost/phpmyadmin/setup you will need to create a config directory that's writeable by the httpd in the /usr/share/webapps/phpmyadmin as follows:<br />
<br />
<pre><br />
cd /usr/share/webapps/phpmyadmin<br />
sudo mkdir config<br />
sudo chgrp http config<br />
sudo chmod g+w config<br />
</pre><br />
<br />
==Other (Older) information==<br />
<br />
This page holds a sample 'config.inc.php' file that you can place in the main phpMyAdmin directory so that it immediately starts working<br />
<br />
'''Things you should do first'''<br />
<br />
Create a 'controluser', so that phpmyadmin can read from the main mysql database.<br />
<br />
<pre>mysql -u root -pYOURROOTPASSWORD<br />
mysql> grant usage on mysql.* to controluser@localhost identified by 'CONTROLPASS';<br />
</pre><br />
<br />
'''Where is phpmyadmin'''<br />
<br />
in phpmyadmin 3.2.2-3 the file is missing /srv/http/ create this symlik<br />
<br />
<pre>ln -s /usr/share/webapps/phpMyAdmin/ /srv/http/phpmyadmin<br />
</pre><br />
<br />
'''Things you should change'''<br />
<br />
controluser is set to controluser <br><br />
controlpass is set to password <br><br />
verbose is set to name_of_server<br />
<br />
'''Sample 'config.inc.php' file'''<br />
<pre><br />
<?php<br />
/*<br />
* Generated configuration file<br />
* Generated by: phpMyAdmin 2.11.8.1 setup script by Michal Čihař <michal@cihar.com><br />
* Version: $Id: setup.php 11423 2008-07-24 17:26:05Z lem9 $<br />
* Date: Mon, 01 Sep 2008 20:34:02 GMT<br />
*/<br />
<br />
/* Servers configuration */<br />
$i = 0;<br />
<br />
/* Server ravi-test-mysql (http) [1] */<br />
$i++;<br />
$cfg['Servers'][$i]['host'] = 'localhost';<br />
$cfg['Servers'][$i]['extension'] = 'mysql';<br />
$cfg['Servers'][$i]['port'] = '3306';<br />
$cfg['Servers'][$i]['connect_type'] = 'tcp';<br />
$cfg['Servers'][$i]['compress'] = false;<br />
$cfg['Servers'][$i]['controluser'] = 'controluser';<br />
$cfg['Servers'][$i]['controlpass'] = 'password';<br />
$cfg['Servers'][$i]['auth_type'] = 'http';<br />
$cfg['Servers'][$i]['verbose'] = 'name_of_server';<br />
<br />
/* End of servers configuration */<br />
<br />
$cfg['LeftFrameLight'] = true;<br />
$cfg['LeftFrameDBTree'] = true;<br />
$cfg['LeftFrameDBSeparator'] = '_';<br />
$cfg['LeftFrameTableSeparator'] = '__';<br />
$cfg['LeftFrameTableLevel'] = 1;<br />
$cfg['LeftDisplayLogo'] = true;<br />
$cfg['LeftDisplayServers'] = false;<br />
$cfg['DisplayServersList'] = false;<br />
$cfg['DisplayDatabasesList'] = 'auto';<br />
$cfg['LeftPointerEnable'] = true;<br />
$cfg['DefaultTabServer'] = 'main.php';<br />
$cfg['DefaultTabDatabase'] = 'db_structure.php';<br />
$cfg['DefaultTabTable'] = 'tbl_structure.php';<br />
$cfg['LightTabs'] = false;<br />
$cfg['ErrorIconic'] = true;<br />
$cfg['MainPageIconic'] = true;<br />
$cfg['ReplaceHelpImg'] = true;<br />
$cfg['NavigationBarIconic'] = 'both';<br />
$cfg['PropertiesIconic'] = 'both';<br />
$cfg['BrowsePointerEnable'] = true;<br />
$cfg['BrowseMarkerEnable'] = true;<br />
$cfg['ModifyDeleteAtRight'] = false;<br />
$cfg['ModifyDeleteAtLeft'] = true;<br />
$cfg['RepeatCells'] = 100;<br />
$cfg['DefaultDisplay'] = 'horizontal';<br />
$cfg['TextareaCols'] = 40;<br />
$cfg['TextareaRows'] = 7;<br />
$cfg['LongtextDoubleTextarea'] = true;<br />
$cfg['TextareaAutoSelect'] = false;<br />
$cfg['CharEditing'] = 'input';<br />
$cfg['CharTextareaCols'] = 40;<br />
$cfg['CharTextareaRows'] = 2;<br />
$cfg['CtrlArrowsMoving'] = true;<br />
$cfg['DefaultPropDisplay'] = 'horizontal';<br />
$cfg['InsertRows'] = 2;<br />
$cfg['EditInWindow'] = true;<br />
$cfg['QueryWindowHeight'] = 310;<br />
$cfg['QueryWindowWidth'] = 550;<br />
$cfg['QueryWindowDefTab'] = 'sql';<br />
$cfg['ForceSSL'] = false;<br />
$cfg['ShowPhpInfo'] = false;<br />
$cfg['ShowChgPassword'] = false;<br />
$cfg['AllowArbitraryServer'] = false;<br />
$cfg['LoginCookieRecall'] = 'something';<br />
$cfg['LoginCookieValidity'] = 1800;<br />
?><br />
</pre></div>Wilcohttps://wiki.archlinux.org/index.php?title=KVM&diff=84364KVM2009-11-18T17:28:45Z<p>Wilco: /* How to use KVM */</p>
<hr />
<div>[[Category:Emulators (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|KVM}}<br />
{{i18n_entry|简体中文|KVM (简体中文)}}<br />
{{i18n_links_end}}<br />
<br />
'''KVM''', Kernel-based Virtual Machine, is a hypervisor built right into the 2.6 kernel for kernels later than 2.6.20. It is similar to [[Xen]] in purpose but much simpler to get running. To start using the hypervisor, just load the appropriate kvm modules and the hypervisor is up. As with Xen's full virtualization, in order for KVM to work, you must have a processor that supports Intel's VT extensions or AMD's Pacifica extensions.<br />
<br />
Using KVM, one can run multiple virtual machines running unmodified Linux, Windows or any other system images. (See [http://www.linux-kvm.org/page/Guest_Support_Status Guest Support Status]) Each virtual machine has private virtualized hardware: a network card, disk, graphics adapter, etc. See [http://www.linux-kvm.org/page/HOWTO KVM Howto]<br />
<br />
Differences among KVM, Xen, VMware, and QEMU can be found at [http://www.linux-kvm.org/page/FAQ#General_KVM_information KVM FAQ].<br />
<br />
=== Get the packages ===<br />
<br />
Arch Kernel 2.6.22 or newer now provide appropriate kvm modules. <br />
You could check if your kernel support kvm with the following command :<br />
<pre><br />
modprobe -l 'kvm*'<br />
</pre><br />
KVM also requires a modified QEMU (the kvm package in the EXTRA repository, providing the qemu-kvm) to launch and manage virtual machines. Or, you can choose to install qemu >= 0.9.0, which conflicts with the kvm packge, and now provides a qemu-kvm executable (qemu -enable-kvm) that take advantage of this technology. <br />
pacman -Sy kernel26 kvm<br />
or<br />
pacman -Sy kernel26 qemu<br />
<br />
=== Setup kernel modules ===<br />
<br />
You could check if your computer support hardware acceleration with this command (must return something on screen) :<br />
<pre><br />
egrep '^flags.*(vmx|svm)' /proc/cpuinfo<br />
</pre><br />
<br />
Firstly, you need to add your user into the kvm group to use the /dev/kvm device.<br />
<pre><br />
gpasswd -a <Your_Login_Name> kvm<br />
</pre><br />
<br />
Secondly, modprobe ''kvm'' and ''kvm-intel'' modules if you have Intel extensions.<br />
<pre><br />
modprobe kvm<br />
modprobe kvm-intel<br />
</pre><br />
Or modprobe ''kvm'' and ''kvm-amd'' modules if you have AMD extensions.<br />
<pre><br />
modprobe kvm<br />
modprobe kvm-amd<br />
</pre><br />
If modprobing kvm succedes, but modprobing kvm-intel or kvm-amd fails (but /proc/cpuinfo claims that VT is supported), check your bios settings. Some vendors (especially laptop vendors) disable VT by default.<br />
<br />
If you want these modules to persist, add them to ''rc.conf''<br />
<br />
=== Using KVM as a non-root user ===<br />
By default the /dev/kvm device is owned by root:root and is not accessible by other users. To enable a user to invoke qemu-kvm without root <br />
privileges, add them to the kvm group then add a udev rule to change the permissions of /dev/kvm when it is created. <br />
<pre><br />
groupadd kvm<br />
usermod -aG kvm <the users' username><br />
cat >>/etc/udev/rules.d/65-kvm.rules <<EOF<br />
KERNEL=="kvm", NAME="%k", GROUP="kvm", MODE="0660"<br />
EOF<br />
modprobe -r kvm-intel # or kvm-amd if using that hardware<br />
modprobe kvm-intel<br />
</pre><br />
It is necessary to for the user to log out before any group membership changes will take effect. /dev/kvm will be recreated with read-write<br />
privileges for members of group kvm. <br />
<br />
=== How to use KVM ===<br />
# Create a guest OS image <pre>$ qemu-img create -f qcow2 <Image_Name> <size></pre><br />
# Install the guest OS <br> A CD/DVD image (ISO files) can be used for the installation. <pre>$ qemu-kvm -hda <Image_Name> -m 512 -cdrom </Path/to/the/ISO/Image> -boot d -vga std</pre><br />
# Running the system <pre>$ qemu-kvm -hda <Image_Name> -m 512 -vga std</pre><br />
Note: The default memory of KVM is 128M, if not provide "-m". Also note that recent Windows operating systems (tested with Vista and Windows 7) require the qcow2 filesystem. Other filesystems gave me a 0x80070057 error during the installation.<br />
<br />
See '''[[QEMU]]''' for all informations, and the ''Using the Kernel-based Virtual Machine'' section.<br />
<br />
=== Easy to Use for New User ===<br />
If the qemu package has been installed, you can use an GUI tool, such as qtemu, to manage your virtual machine (you need to change "qemu" in the configure item"QEMU start command" to "qemu-kvm" / "qemu-system-x86_64") or append -enable-kvm to the additional start options.</div>Wilcohttps://wiki.archlinux.org/index.php?title=Wicd&diff=76819Wicd2009-09-30T16:54:10Z<p>Wilco: </p>
<hr />
<div>[[Category: Networking (English)]]<br />
[[Category: HOWTOs (English)]]<br />
[[Category: Internet and Email (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Wicd}}<br />
{{i18n_entry|Italiano|Wicd (Italiano)}}<br />
{{i18n_entry|简体中文|Wicd (简体中文)}}<br />
{{i18n_entry|Türkçe|Wicd (Türkçe)}}<br />
{{i18n_links_end}}<br />
<br />
=Introduction=<br />
<br />
[http://www.wicd.net/ Wicd] is a network connection manager that can manage wireless and wired interfaces, similar and an alternative to [[NetworkManager]]. Wicd is written in [[Python]] and [[GTK+]], requiring fewer dependencies than other network managers.<br />
<br />
=Installation=<br />
<br />
==Standard Installation==<br />
<br />
If you're not using gnome (or its notification-daemon), you might want to install xfce4-notifyd from extra before you install wicd, or you will most likely end up with the standard notification-daemon pulling a lot of unnecessary packages.<br />
<br />
# pacman -S xfce4-notifyd<br />
<br />
Wicd also is available from the standard repositories:<br />
<br />
# pacman -S wicd<br />
<br />
This will install Wicd and all the necessary dependencies, including ''dbus'', ''python'' and ''gtk2''.<br />
<br />
==Other Way==<br />
<br />
The [http://aur.archlinux.org/packages.php?ID=22923 wicd-bzr] buildscript is available from [[AUR]], which should build the latest development branch.<br />
<br />
If you need an alternative version or you just want to roll your own package, you can easily build it using [[ABS]].<br />
<br />
=Getting Started=<br />
<br />
==Initial Setup==<br />
<br />
Wicd provides a daemon that must be started. <br />
<br />
{{Warning | running multiple network managers ''will'' cause problems, so it is important to ''disable all other network management daemons''.}}<br />
<br />
First, stop all previously running network daemons:<br />
<br />
# /etc/rc.d/network stop<br />
# /etc/rc.d/dhcdbd stop<br />
# /etc/rc.d/networkmanager stop<br />
<br />
Now, edit '''/etc/rc.conf''' as root:<br />
<br />
# nano /etc/rc.conf<br />
<br />
Disable (!) any devices in the INTERFACES array that you wish to manage with Wicd. For example:<br />
<br />
INTERFACES=(!eth0 !wlan0)<br />
<br />
Disable (!) any existing network management daemons in the DAEMONS array, including '''network''', '''dhcdbd''', and '''networkmanager'''.<br />
<br />
Now, add '''dbus''' (if not already present) and '''wicd''' to the DAEMONS array, in that order. The DAEMONS array should now look something like this:<br />
<br />
DAEMONS=(syslog-ng '''dbus''' !network !dhcdbd !networkmanager '''wicd''' ...)<br />
<br />
{{Note | if you use '''hal''', replace '''dbus''' with '''hal''' in DAEMONS array,because the Hal daemon will automatically start dbus'' for you.}}<br />
<br />
Save and close. <br />
<br />
Add your account to '''network''' group:<br />
<br />
# gpasswd -a USERNAME network<br />
<br />
{{Note | the Unix group that dbus allows to access '''wicd''' is subject to change, and may be different than ''network''. Check which policy group is specified in '''/etc/dbus-1/system.d/wicd.conf''', and add your user to that group.}}<br />
<br />
Lastly, reboot your PC.<br />
Note: There is no need to reboot your computer after installing and configuring wicd. Arch != Windows so there's no need to reboot after installing some (trivial) stuff like wicd. Start /etc/rc.d/dbus (or hal) and /etc/rc.d/wicd. If you want your new group for a user to be active you can just logout and login. <br />
<br />
==Running Wicd==<br />
<br />
To load Wicd, run:<br />
<br />
$ wicd-client<br />
<br />
Or if your desktop environment does not have a notification area, run:<br />
<br />
$ wicd-client -n<br />
<br />
You can add '''wicd-client''' to your DE/WM startup to have the application start when you log in.<br />
<br />
{{Note | Wicd doesn't prompt you for a passkey. To use encrypted connections (WPA/WEP), expand the network you want to connect to, click '''Advanced''' and enter the needed info.}}<br />
<br />
== Importing pynotify failed, notifications disabled. ==<br />
If that one didn't get installed automatically: The package name is "python-notify" and it's in extra.<br />
# pacman -S python-notify<br />
<br />
<br />
==Note about graphical sudo programs==<br />
If you are receiving an error about wicd failing to find a graphical sudo program, run one of the following commands:<br />
<br />
$ ktsuss wicd-client -n<br />
<br />
$ gksudo wicd-client -n<br />
<br />
$ kdesu wicd-client -n<br />
<br />
These programs require the ktsuss (found in the AUR), gksudo, and kdesu packages, respectively.<br />
<br />
=Related links=<br />
<br />
*[http://bbs.archlinux.org/viewtopic.php?id=40337 Note on the network daemon and interfaces]<br />
*[http://www.wicd.net/download.php Note on interfaces at the official site]</div>Wilcohttps://wiki.archlinux.org/index.php?title=Talk:Wicd&diff=73766Talk:Wicd2009-08-12T09:17:11Z<p>Wilco: /* No need for rebooting */ new section</p>
<hr />
<div>'''Version:''' wicd 1.6.0.<br />
<br />
Recipe "4.3 Connecting as a Normal User" does not working for me, because not enougth privileges to start wicd daemon. It works if I just adding my user to group "users". <br />
<br />
Let me show content of my original /etc/dbus-1/system.d/wicd.conf is (without header and footer):<br />
<br />
<policy user="root"><br />
<allow own="org.wicd.daemon"/><br />
<allow send_destination="org.wicd.daemon"/><br />
<allow send_interface="org.wicd.daemon"/><br />
<allow send_destination="org.wicd.daemon.wireless"/><br />
<allow send_interface="org.wicd.daemon.wireless"/><br />
<allow send_destination="org.wicd.daemon.wired"/><br />
<allow send_interface="org.wicd.daemon.wired"/><br />
<allow send_destination="org.wicd.daemon.config"/><br />
<allow send_interface="org.wicd.daemon.config"/><br />
</policy><br />
<br />
<policy at_console="true"><br />
<allow send_destination="org.wicd.daemon"/><br />
<allow send_interface="org.wicd.daemon"/><br />
<allow send_destination="org.wicd.daemon.wireless"/><br />
<allow send_interface="org.wicd.daemon.wireless"/><br />
<allow send_destination="org.wicd.daemon.wired"/><br />
<allow send_interface="org.wicd.daemon.wired"/><br />
<allow send_destination="org.wicd.daemon.config"/><br />
<allow send_interface="org.wicd.daemon.config"/><br />
<allow send_interface="org.freedesktop.DBus.Introspectable"/><br />
</policy><br />
<br />
<policy context="default"><br />
<deny own="org.wicd.daemon"/><br />
</policy><br />
<br />
&lt;!-- This Unix group will have permission to use Wicd's gui --><br />
<policy group="users"><br />
<allow send_interface="org.freedesktop.DBus.Introspectable"/><br />
<allow send_destination="org.wicd.daemon"/><br />
<allow send_interface="org.wicd.daemon"/><br />
</policy><br />
<br />
Pay your attention to the comment "This Unix group will have permission to use Wicd's gui".<br />
<br />
== No need for rebooting ==<br />
<br />
There is no need to reboot your computer after installing and configuring wicd. Arch != Windows so there's no need to reboot after installing some (trivial) stuff like wicd,<br />
If you want your new group for a user to be active you can just logout and login.</div>Wilcohttps://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_1000HE&diff=66653ASUS Eee PC 1000HE2009-04-11T09:05:28Z<p>Wilco: /* Sample Config */</p>
<hr />
<div>[[Category:HOWTOs (English)]]<br />
{| style="float:right; border: 1px solid #000;" <br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|- <br />
| Intel 945GM || style="color:green" | '''Working''' || xf86-video-intel <br />
|- <br />
| Ethernet || style="color:green" | '''Working''' || atl1e<br />
|-<br />
| Wireless || style="color:green" | '''Working''' || ath9k<br />
|-<br />
| Bluetooth || style="color:green" | '''Working''' || bluetooth<br />
|-<br />
| Audio || style="color:green" | '''Working''' || snd_hda_intel<br />
|-<br />
| Camera || style="color:green" | '''Working''' || uvcvideo <br />
|-<br />
| Card Reader || style="color:green" | '''Working''' || <br />
|-<br />
| Function Keys || style="color:green" | '''Working''' || <br />
|}<br />
<br />
=Introduction=<br />
First, feel free to help out!<br />
<br />
Secondly, this wiki page assumes you are using kernel 2.6.29 or greater.<br />
<br />
The stock 2.6.29 kernel works just fine. There is no need for a customized eeePC kernel. These customized kernels used to contain patches to allow the hotkeys and whatnot to work. All of these features have since been merged into the standard kernel.<br />
<br />
=Installation=<br />
Use the 2009.02 installation USB image (see [[Install_from_USB_stick]]). There is out-of-the-box support for the wired and wireless NICs. There are no special instructions for installation. For an in-depth guide on the installation see the [[Beginners_Guide]].<br />
<br />
=Xorg=<br />
This example uses hotplugging. Make sure that you have hal installed and started. Also, don't forget to add hal to the DAEMONS=() array in rc.conf!<br />
<br />
==Sample Config==<br />
Note: The 1000HE also functions correctly without using a xorg.conf!<br />
<br />
Here is a basic xorg config file. Using xrandr, you can switch between the lcd + external display.<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "DontZap" "false"<br />
EndSection<br />
<br />
Section "Files"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/local"<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 "dri"<br />
Load "glx"<br />
Load "extmod"<br />
Load "record"<br />
Load "dbe"<br />
Load "dri2"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "IntelCard"<br />
Driver "intel"<br />
VendorName "Intel Corporation"<br />
BoardName "Mobile 945GME Express Integrated Graphics Controller"<br />
BusID "PCI:0:2:0"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "ASUS"<br />
ModelName "eeePC 1000he"<br />
Modeline "1024x600" 48.86 1024 1064 1168 1312 600 601 604 622 -Hsync +Vsync<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "IntelCard"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 1<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 4<br />
EndSubSection<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 />
Virtual 1280 1024 #Set to resolution of CRT/External<br />
EndSubSection<br />
EndSection<br />
<br />
==Keyboard==<br />
#Copy /usr/share/hal/fdi/policy/10osvendor/10-keymap.fdi to /etc/hal/fdi/policy<br />
#Edit /etc/hal/fdi/policy/10-keymap.fdi and change '''<merge key="input.xkb.layout" type="string">us</merge>''' accordingly<br />
<br />
==Touchpad==<br />
#Install the xf86-input-synaptics package<br />
#Create /etc/hal/fdi/policy/11-x11-synaptics.fdi with the following contents:<br />
<?xml version="1.0" encoding="ISO-8859-1"?><br />
<deviceinfo version="0.2"><br />
<device><br />
<match key="info.product" contains="ETPS/2 Elantech Touchpad"><br />
<merge key="input.x11_driver" type="string">synaptics</merge><br />
<merge key="input.x11_options.SHMConfig" type="string">on</merge><br />
<merge key="input.x11_options.MaxSpeed" type="string">1.00</merge><br />
<merge key="input.x11_options.MinSpeed" type="string">0.75</merge><br />
<merge key="input.x11_options.Emulate3Buttons" type="string">on</merge><br />
<merge key="input.x11_options.VertTwoFingerScroll" type="string">1</merge><br />
<merge key="input.x11_options.HorizTwoFingerScroll" type="string">1</merge><br />
<merge key="input.x11_options.TapButton1" type="string">1</merge><br />
<merge key="input.x11_options.TapButton2" type="string">2</merge><br />
<merge key="input.x11_options.TapButton3" type="string">3</merge><br />
<merge key="input.x11_options.LockedDrags" type="string">1</merge><br />
</match><br />
</device><br />
</deviceinfo><br />
<br />
==xrandr==<br />
For a nice GUI tool, try '''lxrandr'''; it is very simple to use!<br />
<br />
Switch to External Monitor:<br />
xrandr --output LVDS --off --output VGA --auto<br />
<br />
Switch back to eeepc's LCD: <br />
xrandr --output LVDS --auto --output VGA --off<br />
<br />
=ACPI=<br />
==acpi-eeepc-generic==<br />
Install the [http://aur.archlinux.org/packages.php?ID=23318 acpi-eeepc-generic package] from AUR (see [[AUR User Guidelines]]).<br />
You must install version 0.9 or greater, as previous versions do not have support for the 1000HE.<br />
<br />
==Sleep==<br />
Use '''pm-suspend''' instead of the script in acpi-eeepc-generic.<br />
The acpi-eeepc-generic suspend script will cause the system to re-suspend when being woken up or when exiting X!<br />
<br />
==cpufrequtils==<br />
To scale the CPU and possibly save a bit of power, you will want to set up cpufrequtils.<br />
<br />
#pacman -Sy cpufrequtils<br />
#Edit /etc/conf.d/cpufreq <pre>min_freq="1000MHz" max_freq="1.67GHz"</pre><br />
#modprobe acpi-cpufreq cpufreq_ondemand cpufreq_powersave<br />
#Add these modules listed above to the MODULES=() array in rc.conf<br />
#/etc/rc.d/cpufreq start<br />
#Add cpufreq to the DAEMONS=() array in rc.conf<br />
<br />
=Hardware=<br />
==Bluetooth==<br />
To turn the bluetooth radio on/off:<br />
<br />
# enable<br />
$ echo 1 > /sys/class/rfkill/rfkill1/state<br />
# disable<br />
$ echo 0 > /sys/class/rfkill/rfkill1/state<br />
<br />
Install the '''bluez-utils''' and '''bluez-libs''' packages, then <tt>modprobe btusb</tt>.<br />
<br />
''Note: in the test repository '''bluez-utils''' and '''bluez-libs''' are merged into a single package, '''bluez'''.''<br />
<br />
See the Arch Linux [[Bluetooth]] and [[Bluetooth Mouse]] wiki pages for more information about configuring and using Bluetooth devices.<br />
<br />
{{Box Note |'''''Switching the Bluetooth Radio on and off does not work on kernel 2.6.28 or below. You need to use kernel 2.6.29 or greater.'''''}}<br />
<br />
==Camera==<br />
<br />
To enable/disable the camera:<br />
<br />
# enable<br />
echo 1 > /sys/devices/platform/eeepc/camera<br />
# disable<br />
echo 0 > /sys/devices/platform/eeepc/camera<br />
<br />
Make sure that the module <tt>uvcvideo</tt> is loaded<br />
<br />
To record video and take photos, you may use '''cheese''' or the [http://aur.archlinux.org/packages.php?ID=15272 '''wxcam'''] package.<br />
<br />
To simply test the camera, you may use <tt>mplayer</tt>:<br />
<br />
mplayer -fps 15 tv://<br />
<br />
The webcam is reported to work with Skype.<br />
<br />
=Info=<br />
==lspci==<br />
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)<br />
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)<br />
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)<br />
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)<br />
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)<br />
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)<br />
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)<br />
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)<br />
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)<br />
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)<br />
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)<br />
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)<br />
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)<br />
01:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01)<br />
03:00.0 Ethernet controller: Attansic Technology Corp. L1e Gigabit Ethernet Adapter (rev b0)<br />
<br />
=Issues=<br />
Laptop suspends while "waking up"<br />
*Use pm-suspend instead of acpi script<br />
<br />
If you have any other issues, make sure you are using kernel 2.6.29 or greater.</div>Wilcohttps://wiki.archlinux.org/index.php?title=ASUS_Eee_PC_1000HE&diff=66652ASUS Eee PC 1000HE2009-04-11T09:04:46Z<p>Wilco: /* Sample Config */</p>
<hr />
<div>[[Category:HOWTOs (English)]]<br />
{| style="float:right; border: 1px solid #000;" <br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|- <br />
| Intel 945GM || style="color:green" | '''Working''' || xf86-video-intel <br />
|- <br />
| Ethernet || style="color:green" | '''Working''' || atl1e<br />
|-<br />
| Wireless || style="color:green" | '''Working''' || ath9k<br />
|-<br />
| Bluetooth || style="color:green" | '''Working''' || bluetooth<br />
|-<br />
| Audio || style="color:green" | '''Working''' || snd_hda_intel<br />
|-<br />
| Camera || style="color:green" | '''Working''' || uvcvideo <br />
|-<br />
| Card Reader || style="color:green" | '''Working''' || <br />
|-<br />
| Function Keys || style="color:green" | '''Working''' || <br />
|}<br />
<br />
=Introduction=<br />
First, feel free to help out!<br />
<br />
Secondly, this wiki page assumes you are using kernel 2.6.29 or greater.<br />
<br />
The stock 2.6.29 kernel works just fine. There is no need for a customized eeePC kernel. These customized kernels used to contain patches to allow the hotkeys and whatnot to work. All of these features have since been merged into the standard kernel.<br />
<br />
=Installation=<br />
Use the 2009.02 installation USB image (see [[Install_from_USB_stick]]). There is out-of-the-box support for the wired and wireless NICs. There are no special instructions for installation. For an in-depth guide on the installation see the [[Beginners_Guide]].<br />
<br />
=Xorg=<br />
This example uses hotplugging. Make sure that you have hal installed and started. Also, don't forget to add hal to the DAEMONS=() array in rc.conf!<br />
<br />
==Sample Config==<br />
Note: The 1000HE also functions correctly without using a xorg.conf!<br />
Here is a basic xorg config file. Using xrandr, you can switch between the lcd + external display.<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "DontZap" "false"<br />
EndSection<br />
<br />
Section "Files"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/local"<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 "dri"<br />
Load "glx"<br />
Load "extmod"<br />
Load "record"<br />
Load "dbe"<br />
Load "dri2"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "IntelCard"<br />
Driver "intel"<br />
VendorName "Intel Corporation"<br />
BoardName "Mobile 945GME Express Integrated Graphics Controller"<br />
BusID "PCI:0:2:0"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "ASUS"<br />
ModelName "eeePC 1000he"<br />
Modeline "1024x600" 48.86 1024 1064 1168 1312 600 601 604 622 -Hsync +Vsync<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "IntelCard"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 1<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 4<br />
EndSubSection<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 />
Virtual 1280 1024 #Set to resolution of CRT/External<br />
EndSubSection<br />
EndSection<br />
<br />
==Keyboard==<br />
#Copy /usr/share/hal/fdi/policy/10osvendor/10-keymap.fdi to /etc/hal/fdi/policy<br />
#Edit /etc/hal/fdi/policy/10-keymap.fdi and change '''<merge key="input.xkb.layout" type="string">us</merge>''' accordingly<br />
<br />
==Touchpad==<br />
#Install the xf86-input-synaptics package<br />
#Create /etc/hal/fdi/policy/11-x11-synaptics.fdi with the following contents:<br />
<?xml version="1.0" encoding="ISO-8859-1"?><br />
<deviceinfo version="0.2"><br />
<device><br />
<match key="info.product" contains="ETPS/2 Elantech Touchpad"><br />
<merge key="input.x11_driver" type="string">synaptics</merge><br />
<merge key="input.x11_options.SHMConfig" type="string">on</merge><br />
<merge key="input.x11_options.MaxSpeed" type="string">1.00</merge><br />
<merge key="input.x11_options.MinSpeed" type="string">0.75</merge><br />
<merge key="input.x11_options.Emulate3Buttons" type="string">on</merge><br />
<merge key="input.x11_options.VertTwoFingerScroll" type="string">1</merge><br />
<merge key="input.x11_options.HorizTwoFingerScroll" type="string">1</merge><br />
<merge key="input.x11_options.TapButton1" type="string">1</merge><br />
<merge key="input.x11_options.TapButton2" type="string">2</merge><br />
<merge key="input.x11_options.TapButton3" type="string">3</merge><br />
<merge key="input.x11_options.LockedDrags" type="string">1</merge><br />
</match><br />
</device><br />
</deviceinfo><br />
<br />
==xrandr==<br />
For a nice GUI tool, try '''lxrandr'''; it is very simple to use!<br />
<br />
Switch to External Monitor:<br />
xrandr --output LVDS --off --output VGA --auto<br />
<br />
Switch back to eeepc's LCD: <br />
xrandr --output LVDS --auto --output VGA --off<br />
<br />
=ACPI=<br />
==acpi-eeepc-generic==<br />
Install the [http://aur.archlinux.org/packages.php?ID=23318 acpi-eeepc-generic package] from AUR (see [[AUR User Guidelines]]).<br />
You must install version 0.9 or greater, as previous versions do not have support for the 1000HE.<br />
<br />
==Sleep==<br />
Use '''pm-suspend''' instead of the script in acpi-eeepc-generic.<br />
The acpi-eeepc-generic suspend script will cause the system to re-suspend when being woken up or when exiting X!<br />
<br />
==cpufrequtils==<br />
To scale the CPU and possibly save a bit of power, you will want to set up cpufrequtils.<br />
<br />
#pacman -Sy cpufrequtils<br />
#Edit /etc/conf.d/cpufreq <pre>min_freq="1000MHz" max_freq="1.67GHz"</pre><br />
#modprobe acpi-cpufreq cpufreq_ondemand cpufreq_powersave<br />
#Add these modules listed above to the MODULES=() array in rc.conf<br />
#/etc/rc.d/cpufreq start<br />
#Add cpufreq to the DAEMONS=() array in rc.conf<br />
<br />
=Hardware=<br />
==Bluetooth==<br />
To turn the bluetooth radio on/off:<br />
<br />
# enable<br />
$ echo 1 > /sys/class/rfkill/rfkill1/state<br />
# disable<br />
$ echo 0 > /sys/class/rfkill/rfkill1/state<br />
<br />
Install the '''bluez-utils''' and '''bluez-libs''' packages, then <tt>modprobe btusb</tt>.<br />
<br />
''Note: in the test repository '''bluez-utils''' and '''bluez-libs''' are merged into a single package, '''bluez'''.''<br />
<br />
See the Arch Linux [[Bluetooth]] and [[Bluetooth Mouse]] wiki pages for more information about configuring and using Bluetooth devices.<br />
<br />
{{Box Note |'''''Switching the Bluetooth Radio on and off does not work on kernel 2.6.28 or below. You need to use kernel 2.6.29 or greater.'''''}}<br />
<br />
==Camera==<br />
<br />
To enable/disable the camera:<br />
<br />
# enable<br />
echo 1 > /sys/devices/platform/eeepc/camera<br />
# disable<br />
echo 0 > /sys/devices/platform/eeepc/camera<br />
<br />
Make sure that the module <tt>uvcvideo</tt> is loaded<br />
<br />
To record video and take photos, you may use '''cheese''' or the [http://aur.archlinux.org/packages.php?ID=15272 '''wxcam'''] package.<br />
<br />
To simply test the camera, you may use <tt>mplayer</tt>:<br />
<br />
mplayer -fps 15 tv://<br />
<br />
The webcam is reported to work with Skype.<br />
<br />
=Info=<br />
==lspci==<br />
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)<br />
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)<br />
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)<br />
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)<br />
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)<br />
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)<br />
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)<br />
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)<br />
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)<br />
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)<br />
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)<br />
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)<br />
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)<br />
01:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01)<br />
03:00.0 Ethernet controller: Attansic Technology Corp. L1e Gigabit Ethernet Adapter (rev b0)<br />
<br />
=Issues=<br />
Laptop suspends while "waking up"<br />
*Use pm-suspend instead of acpi script<br />
<br />
If you have any other issues, make sure you are using kernel 2.6.29 or greater.</div>Wilco