https://wiki.archlinux.org/api.php?action=feedcontributions&user=Shastry&feedformat=atomArchWiki - User contributions [en]2024-03-29T11:07:29ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=GNOME/Document_viewer&diff=592055GNOME/Document viewer2019-12-17T05:59:28Z<p>Shastry: WebP comic book support</p>
<hr />
<div>[[Category:Office]]<br />
[[es:GNOME (Español)/Document viewer]]<br />
[[ja:Evince]]<br />
[[w:Evince|Document viewer]] is specifically designed to support the following file formats: [[PDF, PS and DjVu|PDF, PostScript, DjVu]], tiff, dvi, XPS, SyncTex support with gedit, comics books (cbr,cbz,cb7 and cbt). For a comprehensive list of formats supported, see [https://wiki.gnome.org/Apps/Evince/SupportedDocumentFormats Supported Document Formats].<br />
<br />
Document viewer uses the poppler library as a backend.<br />
<br />
{{Note|Document viewer was previously known as [https://wiki.gnome.org/Apps/Evince Evince] until the application was given new descriptive names, one for each supported language. The name ''Evince'' is still used in numerous places such as the executable name, some package names, some desktop entries, and some GSettings schemas.}} <br />
<br />
== Installation ==<br />
<br />
[[Install]] the {{Pkg|evince}} package, or {{AUR|evince-git}} for the development version.<br />
Evince installs the {{Pkg|gnome-desktop}} as a dependency.<br />
<br />
For a standalone version install {{AUR|evince-no-gnome}} or the light version {{AUR|evince-light}} for PDF support only.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Printer does not show up ===<br />
<br />
Upgrade {{Pkg|gtk3}} to version {{ic|3.22.26+47+g3a1a7135a2-1}} or higher. In previous GTK 3 versions, the GTK printer backends were included in a separate package. [https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/gtk3&id=54e7af64837e18355122e62ff565970620db3537]<br />
<br />
=== Zoom-in is limited ===<br />
<br />
Increasing Evince's page cache size allows you to zoom in further, which is handy for large documents. By default the setting is set to 50MiB. Increasing the page cache size obviously increases Evince's memory consumption when zoomed-in.<br />
<br />
The following command increases the page cache size to one gigabyte:<br />
<br />
$ gsettings set org.gnome.Evince page-cache-size 'uint32 1000'<br />
<br />
=== PDF texts is not show correctly ===<br />
<br />
Try setting {{ic|override-restrictions}} parameter to false:<br />
<br />
$ gsettings set org.gnome.Evince override-restrictions false<br />
<br />
=== Inverse search with SyncTeX doesn't work ===<br />
<br />
Check that {{Pkg|python-dbus}} is [[install]]ed. After that {{ic|Ctrl+click}} should work.<br />
<br />
=== WebP comic book support ===<br />
<br />
Some comic books files (cbr, cbz etc.) use WebP images. Install {{AUR|webp-pixbuf-loader}} for WebP comic book support.<br />
<br />
== Tips and Tricks ==<br />
<br />
=== Annotation handling ===<br />
<br />
[https://gitlab.gnome.org/GNOME/evince/blob/d203432a5e6dd530574e3fe403576f9b0cc2d3a3/shell/ev-application.c#L1048 Evince v3.31.0] adds keyboard hotkeys "s" for adding note text annotations and "Ctrl+H" for adding a highlight text annotation. <br />
<br />
The default author for note text animations is equal to the [[Users_and_groups#User_database|GECOS comment]] for the current user, to change this:<br />
<br />
usermod -c “Your full new Real Name” yourusername<br />
<br />
=== Use as default PDF viewer ===<br />
<br />
To set the default association for [[Default_applications#xdg-open|xdg-open]],<br />
<br />
xdg-mime default org.gnome.Evince.desktop application/pdf<br />
<br />
[[Default_applications|Other resource openers]] can be configured similarly.<br />
<br />
== See also ==<br />
<br />
* [https://wiki.gnome.org/Apps/Evince Evince website] <br />
* [http://poppler.freedesktop.org/ Poppler website] <br />
* [http://www.adobe.com/devnet/pdf/pdf_reference.html Page "PDF reference" from Adobe]</div>Shastryhttps://wiki.archlinux.org/index.php?title=Firefox/Privacy&diff=271616Firefox/Privacy2013-08-18T19:23:38Z<p>Shastry: more typo fixes</p>
<hr />
<div>[[Category:Web Browser]]<br />
{{Article summary start}}<br />
{{Article summary text|Configuration and installation of recommended add-ons to the Firefox browser to improve privacy}}<br />
{{Article summary heading|Required}}<br />
{{Article summary wiki|Firefox}}: Installing and troubleshooting the Firefox browser and plugins<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Tor}}: Anonymous proxy network<br />
{{Article summary wiki|Browser Plugins}}: Acquiring and installing plugins such as [[Flash]]<br />
{{Article summary wiki|Firefox Tweaks}}: Configuration and modifications<br />
{{Article summary wiki|Speed-up Firefox using tmpfs}}: Caching the profile in RAM<br />
{{Article summary end}}<br />
<br />
This article overviews some useful extensions which enhance security and privacy while using the Firefox web browser.<br />
<br />
==HTTPS Everywhere==<br />
<br />
[https://www.eff.org/https-everywhere HTTPS Everywhere] is an extension which encrypts your communication with a website. It forces a connection over HTTPS instead of HTTP wherever possible.<br />
<br />
HTTPS Everywhere will be automatically configured and enabled upon restarting Firefox. For information on how to set up your own rules for different websites please visit [https://www.eff.org/https-everywhere/rulesets the official website].<br />
<br />
{{Note|HTTPS Everywhere does not magically enable HTTPS for every site on the internet. The site needs to support HTTPS and HTTPS Everywhere should have a ruleset configured for that site.}}<br />
<br />
==Adblock Plus==<br />
<br />
[https://adblockplus.org/en/ Adblock Plus] can be used to stop intrusive advertisments but it can also be configured to block websites from tracking you.<br />
<br />
Once installed visit the [https://easylist.adblockplus.org/en/ Easy List website] and add the EasyList and EasyPrivacy lists to your Adblock Plus filter subscriptions. This is done by simply clicking any of the "Add [filter] to Adblock Plus" on the webpage. This will bring up the add filter prompt. Review the details and click "Add Subscription".<br />
<br />
EasyList is the primary subscription that removes adverts from English webpages, including unwanted frames, images and objects.<br />
<br />
EasyPrivacy is a supplementary subscription for EasyList which removes all forms of tracking from the internet, including web bugs, tracking scripts and information collectors.<br />
<br />
==Disconnect==<br />
<br />
Disconnect is a open source project aimed at stopping 2,000 third-party sites from tracking a user. It encrypts data sent to popular sites and claims to loads web pages 27 percent faster. Disconnect shows its users, in real time, how many tracking attempts from Google, Twitter, Facebook, and more are stopped. It categorizes tracking attempts into advertising, analytical, social, and content, which makes it easy to monitor how one is being tracked.<br />
<br />
Disconnect can also stop side-jacking, which utilizes stolen cookies to steal personal data. It's easy to use and well supported. It can be added to Firefox at the [https://disconnect.me/ official website].<br />
<br />
==Ghostery==<br />
<br />
[https://www.ghostery.com/ Ghostery] is similar to Disconnect, but is a proprietary project to track businesses which employ the use of website trackers. From the website:<br />
<br />
''Ghostery tracks over 1,000 trackers and gives you a roll-call of the ad networks, behavioural data providers, web publishers, and other companies interested in your activity.<br />
<br />
Ghostery can be installed from the [https://www.ghostery.com/download official website]. Once installed Ghostery can be configured from:<br />
chrome://ghostery/content/options.html<br />
<br />
Or by selecting preferences from the Add-ons Manager in Firefox which will bring you to the configuration page. <br />
<br />
Alternatively you can configure Ghostery through the included wizard:<br />
chrome://ghostery/content/wizard.html<br />
<br />
From the configuration page you can configure what 3rd party elements(3pes) Ghostery should block. When navigating the categories you can click on the individual profiles for more information about that specific company. You can also choose to clear Flash and Silverlight cookies on exit. Also, you can enable the cookie protection feature which prevents selected websites from setting cookies in your browser.<br />
<br />
==NoScript==<br />
<br />
[http://noscript.net/ NoScript] is an extension which disables JavaScript, Java, Flash and other plugins on any website not specifically whitelisted by the user. This extension will protect you from exploitation of security vulnerabilities by not letting anything but trusted sites (e.g: your bank, webmail) serve you executable content.<br />
<br />
Once installed you can configure settings for NoScript by either clicking its icon on the toolbar or right clicking a page and navigating to NoScript. You will then have the option to enable/disable scripts for the current page, as well as any third party scripts that the page is linking to. Alternatively you can choose to enable scripts temporarily for that session only.<br />
<br />
For more detailed configuration see the [http://noscript.net/faq NoScript FAQ].<br />
<br />
==Cookie Monster==<br />
<br />
[https://addons.mozilla.org/en-US/firefox/addon/cookie-monster/ Cookie Monster] is a similar extension to NoScript but will the goal of managing cookies.<br />
<br />
From the preferences for Cookie Monster select "Block All Cookies". Once this is done, just as with NoScript, you can enable the use of cookies for specific pages from either the Cookie Monster icon on the toolbar or by right clicking the page and navigating to Cookie Monster. You have the option to accept cookies from the website in question or alternatively to only temporarily allow cookies for the current session.<br />
<br />
==RefControl==<br />
<br />
[http://www.stardrifter.org/refcontrol/ RefControl] is an extension to control what gets sent as the HTTP Referer. Once installed RefControl can be configured so that no referer gets sent when navigating to a new webpage. This prevents the server from knowing which website you originated from.<br />
<br />
To do this open RefControl's preferences and change the setting for "Default for sites not listed:" to <Block>.<br />
<br />
== RequestPolicy ==<br />
<br />
[https://www.requestpolicy.com/ RequestPolicy] is an extension for Mozilla browsers which lets you have control over cross-site requests. The latest development version lets you blacklist or whitelist requests by default. Disabling unnecessary cross-site requests leads to better privacy, safety and faster browsing.<br />
<br />
For more information on cross-site requests and RequestPolicy visit [https://www.requestpolicy.com/faq.html here].</div>Shastryhttps://wiki.archlinux.org/index.php?title=Firefox/Privacy&diff=271615Firefox/Privacy2013-08-18T19:21:05Z<p>Shastry: typo fix</p>
<hr />
<div>[[Category:Web Browser]]<br />
{{Article summary start}}<br />
{{Article summary text|Configuration and installation of recommended add-ons to the Firefox browser to improve privacy}}<br />
{{Article summary heading|Required}}<br />
{{Article summary wiki|Firefox}}: Installing and troubleshooting the Firefox browser and plugins<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Tor}}: Anonymous proxy network<br />
{{Article summary wiki|Browser Plugins}}: Acquiring and installing plugins such as [[Flash]]<br />
{{Article summary wiki|Firefox Tweaks}}: Configuration and modifications<br />
{{Article summary wiki|Speed-up Firefox using tmpfs}}: Caching the profile in RAM<br />
{{Article summary end}}<br />
<br />
This article overviews some useful extensions which enhance security and privacy while using the Firefox web browser.<br />
<br />
==HTTPS Everywhere==<br />
<br />
[https://www.eff.org/https-everywhere HTTPS Everywhere] is an extension which encrypts your communication with a website. It forces a connection over HTTPS instead of HTTP wherever possible.<br />
<br />
HTTPS Everywhere will be automatically configured and enabled upon restarting Firefox. For information on how to set up your own rules for different websites please visit [https://www.eff.org/https-everywhere/rulesets the official website].<br />
<br />
{{Note|HTTPS Everywhere does not magically enable HTTPS for every site on the internet. The site needs to support HTTPS and HTTPS Everywhere should have a ruleset configured for that site.}}<br />
<br />
==Adblock Plus==<br />
<br />
[https://adblockplus.org/en/ Adblock Plus] can be used to stop intrusive advertisments but it can also be configured to block websites from tracking you.<br />
<br />
Once installed visit the [https://easylist.adblockplus.org/en/ Easy List website] and add the EasyList and EasyPrivacy lists to your Adblock Plus filter subscriptions. This is done by simply clicking any of the "Add [filter] to Adblock Plus" on the webpage. This will bring up the add filter prompt. Review the details and click "Add Subscription".<br />
<br />
EasyList is the primary subscription that removes adverts from English webpages, including unwanted frames, images and objects.<br />
<br />
EasyPrivacy is a supplementary subscription for EasyList which removes all forms of tracking from the internet, including web bugs, tracking scripts and information collectors.<br />
<br />
==Disconnect==<br />
<br />
Disconnect is a open source project aimed at stopping 2,000 third-party sites from tracking a user. It encrypts data sent to popular sites and claims to loads web pages 27 percent faster. Disconnect shows its users, in real time, how many tracking attempts from Google, Twitter, Facebook, and more are stopped. It categorizes tracking attempts into advertizing, analytical, social, and content, which makes it easy to monitor how one is being tracked.<br />
<br />
Disconnect can also stop side-jacking, which utilizes stolen cookies to steal personal data. It's easy to use and well supported. It can be added to firefox at the [https://disconnect.me/ official website].<br />
<br />
==Ghostery==<br />
<br />
[https://www.ghostery.com/ Ghostery] is similiar to Disconnect, but is a proprietary project to track businesses which employ the use of website trackers. From the website:<br />
<br />
''Ghostery tracks over 1,000 trackers and gives you a roll-call of the ad networks, behavioral data providers, web publishers, and other companies interested in your activity.<br />
<br />
Ghostery can be installed from the [https://www.ghostery.com/download official website]. Once installed Ghostery can be configured from:<br />
chrome://ghostery/content/options.html<br />
<br />
Or by selecting preferences from the Add-ons Manager in Firefox which will bring you to the configuration page. <br />
<br />
Alternatively you can configure Ghostery through the included wizard:<br />
chrome://ghostery/content/wizard.html<br />
<br />
From the configuration page you can configure what 3rd party elements(3pes) Ghostery should block. When navigating the categories you can click on the individual profiles for more information about that specific company. You can also choose to clear Flash and Silverlight cookies on exit. Also, you can enable the cookie protection feature which prevents selected websites from setting cookies in your browser.<br />
<br />
==NoScript==<br />
<br />
[http://noscript.net/ NoScript] is an extension which disables JavaScript, Java, Flash and other plugins on any website not specifically whitelisted by the user. This extension will protect you from exploitation of security vulnerabilities by not letting anything but trusted sites (e.g: your bank, webmail) serve you executable content.<br />
<br />
Once installed you can configure settings for NoScript by either clicking its icon on the toolbar or right clicking a page and navigating to NoScript. You will then have the option to enable/disable scripts for the current page, as well as any third party scripts that the page is linking to. Alternatively you can choose to enable scripts temporarily for that session only.<br />
<br />
For more detailed configuration see the [http://noscript.net/faq NoScript FAQ].<br />
<br />
==Cookie Monster==<br />
<br />
[https://addons.mozilla.org/en-US/firefox/addon/cookie-monster/ Cookie Monster] is a similar extension to NoScript but will the goal of managing cookies.<br />
<br />
From the preferences for Cookie Monster select "Block All Cookies". Once this is done, just as with NoScript, you can enable the use of cookies for specific pages from either the Cookie Monster icon on the toolbar or by right clicking the page and navigating to Cookie Monster. You have the option to accept cookies from the website in question or alternatively to only temporarily allow cookies for the current session.<br />
<br />
==RefControl==<br />
<br />
[http://www.stardrifter.org/refcontrol/ RefControl] is an extension to control what gets sent as the HTTP Referer. Once installed RefControl can be configured so that no referer gets sent when navigating to a new webpage. This prevents the server from knowing which website you originated from.<br />
<br />
To do this open RefControl's preferences and change the setting for "Default for sites not listed:" to <Block>.<br />
<br />
== RequestPolicy ==<br />
<br />
[https://www.requestpolicy.com/ RequestPolicy] is an extension for Mozilla browsers which lets you have control over cross-site requests. The latest development version lets you blacklist or whitelist requests by default. Disabling unnecessary cross-site requests leads to better privacy, safety and faster browsing.<br />
<br />
For more information on cross-site requests and RequestPolicy visit [https://www.requestpolicy.com/faq.html here].</div>Shastryhttps://wiki.archlinux.org/index.php?title=NetworkManager&diff=252602NetworkManager2013-04-01T16:02:23Z<p>Shastry: use nmcli to get UUID. /etc/NetworkManager/system-connections/ doesn't contain info unless a network is modified.</p>
<hr />
<div>[[Category:Networking]]<br />
[[cs:NetworkManager]]<br />
[[de:Networkmanager]]<br />
[[es:NetworkManager]]<br />
[[fr:NetworkManager]]<br />
[[it:NetworkManager]]<br />
[[ja:NetworkManager]]<br />
[[pt:NetworkManager]]<br />
[[ru:NetworkManager]]<br />
[[tr:NetworkManager]]<br />
[[zh-CN:NetworkManager]]<br />
{{Article summary start}}<br />
{{Article summary text|Covers installation and configuration of NetworkManager &ndash; a set of co-operative tools that make networking simple and straightforward.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Networking overview}}}}<br />
{{Article summary end}}<br />
<br />
[http://projects.gnome.org/NetworkManager/ NetworkManager] is a program for providing detection and configuration for systems to automatically connect to network. NetworkManager's functionality can be useful for both wireless and wired networks. For wireless networks, NetworkManager prefers known wireless networks and has the ability to switch to the most reliable network. NetworkManager-aware applications can switch from online and offline mode. NetworkManager also prefers wired connections over wireless ones, has support for modem connections and certain types of VPN. NetworkManager was originally developed by Red Hat and now is hosted by the [[GNOME]] project.<br />
<br />
== Base install ==<br />
<br />
NetworkManager can be installed with the package {{Pkg|networkmanager}}, available in the [[official repositories]].<br />
<br />
=== VPN support ===<br />
<br />
Network Manager VPN support is based on a plug-in system. If you need VPN support via network manager you have to install one of the following packages from the [[official repositories]]:<br />
<br />
* {{Pkg|networkmanager-openvpn}}<br />
* {{Pkg|networkmanager-pptp}}<br />
* {{Pkg|networkmanager-vpnc}}<br />
<br />
== Graphical front-ends ==<br />
<br />
To configure and have easy access to NetworkManager most people will want to install an applet. This GUI front-end usually resides in the system tray (or notification area) and allows network selection and configuration of NetworkManager. Various applets exist for different types of desktops.<br />
<br />
=== GNOME ===<br />
<br />
GNOME's {{Pkg|network-manager-applet}} is lightweight enough and works across all environments.<br />
<br />
If you want to store authentication details (Wireless/DSL) and enable global connection settings, i.e "available to all users" install and configure [[GNOME Keyring]].<br />
<br />
=== KDE ===<br />
<br />
The KNetworkManager front-end is a Plasma widget available in the official repositories as package {{Pkg|kdeplasma-applets-networkmanagement}}.<br />
<br />
{{Note|If you are changing from another network managing tool like [[Wicd]], do not forget to set the default 'Network Management Backend' in <br />
System Settings -> Hardware -> Information Sources}}<br />
<br />
If you have both the Plasma widget and {{ic|nm-applet}} installed and do not want to start {{ic|nm-applet}} when using KDE, add the following line to {{ic|/etc/xdg/autostart/nm-applet.desktop}}:<br />
NotShowIn=KDE<br />
<br />
See [http://userbase.kde.org/NetworkManagement Userbase page] for more info.<br />
<br />
=== XFCE ===<br />
{{Pkg|network-manager-applet}} will work fine in XFCE, but in order to see notifications, ''including error messages'', {{ic|nm-applet}} needs an implementation of the Freedesktop desktop notifications specification (see the [http://www.galago-project.org/specs/notification/0.9/index.html Galapago Project]) to display them. To enable notifications install {{Pkg|xfce4-notifyd}}, a package that provides an implementation for the specification.<br />
<br />
Without such a notification daemon, {{ic|nm-applet}} outputs the following errors to stdout/stderr:<br />
<br />
(nm-applet:24209): libnotify-WARNING **: Failed to connect to proxy<br />
** (nm-applet:24209): WARNING **: get_all_cb: couldn't retrieve<br />
system settings properties: (25) Launch helper exited with unknown<br />
return code 1.<br />
** (nm-applet:24209): WARNING **: fetch_connections_done: error<br />
fetching connections: (25) Launch helper exited with unknown return<br />
code 1.<br />
** (nm-applet:24209): WARNING **: Failed to register as an agent:<br />
(25) Launch helper exited with unknown return code 1<br />
<br />
{{ic|nm-applet}} will still work fine, though, but without notifications.<br />
<br />
=== Openbox ===<br />
<br />
To function properly in Openbox, the GNOME applet requires the {{Pkg|xfce4-notifyd}} notification daemon for the same reason as in XFCE and the {{Pkg|gnome-icon-theme}} package to be able to display the applet in the systray.<br />
<br />
If you want to store authentication details (Wireless/DSL) install and configure [[gnome-keyring]].<br />
<br />
{{Note|If the ''networkmanager'' daemon is in {{ic|rc.conf}}, the following settings are obsolete or the applet will be started twice.}}<br />
<br />
To have Openbox's autostart start {{ic|nm-applet}} properly, you may need to delete the file {{ic|/etc/xdg/autostart/nm-applet.desktop}} (You may need to delete this file again after every update to {{Pkg|network-manager-applet}}).<br />
<br />
Then in {{ic|autostart}}, start {{ic|nm-applet}} with this line:<br />
<br />
(sleep 3 && /usr/bin/nm-applet --sm-disable) &<br />
<br />
If you experience errors connecting, make sure you have your [[D-Bus]] user session started.<br />
<br />
=== Other desktops and window managers ===<br />
<br />
In all other scenarios it is recommended to use the GNOME applet. You will also need to be sure that the {{Pkg|gnome-icon-theme}} package is installed to be able to display the applet.<br />
<br />
To store connection secrets install and configure [[gnome-keyring]].<br />
<br />
In order to run {{ic|nm-applet}} without a systray, you can use {{Pkg|trayer}} or {{Pkg|stalonetray}}. For example, you can add a script like this one in your path:<br />
{{hc|nmgui|<nowiki><br />
#!/bin/sh<br />
nm-applet > /dev/null 2>/dev/null &<br />
stalonetray > /dev/null 2>/dev/null<br />
killall nm-applet<br />
</nowiki>}}<br />
<br />
When you close the stalonetray window, it closes {{ic|nm-applet}} too, so no extra memory is used once you are done with network settings.<br />
<br />
=== Command line ===<br />
<br />
The {{Pkg|networkmanager}} package contains [http://manpages.ubuntu.com/manpages/maverick/man1/nmcli.1.html nmcli] since version 0.8.1.<br />
<br />
== Configuration ==<br />
<br />
NetworkManager will require some additional steps to be able run properly.<br />
<br />
Verify that your {{ic|/etc/hosts}} is correct before continuing. If you previously tried to connect before doing this step, NetworkManager may have altered it. An example hostname line in {{ic|/etc/hosts}}:<br />
<br />
{{hc|/etc/hosts|<br />
127.0.0.1 localhost<br />
::1 localhost<br />
}}<br />
<br />
In case you have nss-myhostname turned off, the line would look like:<br />
<br />
{{hc|/etc/hosts|<br />
127.0.0.1 my-laptop localhost<br />
::1 my-laptop localhost<br />
}}<br />
<br />
=== Disable current network setup ===<br />
You will want to disable your current network setup to be able to properly test NetworkManager<br />
<br />
First, [[Daemon|stop]] the network daemon:<br />
<br />
# systemctl stop net-auto-wireless.service<br />
<br />
Then, disable currently running network daemons.<br />
<br />
# systemctl disable net-auto-wireless.service<br />
<br />
Finally, bring down your NIC's (Network Interface Controllers, i.e. network cards). For example (using the {{Pkg|iproute2}} package):<br />
<br />
# ip link set eth0 down<br />
# ip link set wlan0 down<br />
<br />
=== Enable NetworkManager ===<br />
<br />
Once the NetworkManager daemon is started, it will automatically connect to any available "system connections" that have already been configured. Any "user connections" or unconfigured connections will need {{ic|nmcli}} or an applet to configure and connect.<br />
<br />
You can enable NetworkManager at startup with the following command:<br />
<br />
{{bc|# systemctl enable NetworkManager}}<br />
<br />
You can start the NetworkManager daemon immediately with the following command:<br />
<br />
{{bc|# systemctl start NetworkManager}}<br />
<br />
=== Enable NetworkManager Wait Online ===<br />
If you have services which fail if they are started before the network is up, you have to use {{ic|NetworkManager-wait-online.service}} in addition to the NetworkManager service. This is however hardly ever necessary since most network daemons start up fine, even if the network has not been configured yet.<br />
<br />
You can enable NetworkManager Wait Online at startup with the following command:<br />
<br />
{{bc|# systemctl enable NetworkManager-wait-online}}<br />
<br />
In some cases the service will still fail to start sucessfully on boot:<br />
<br />
NetworkManager-wait-online.service: main process exited, code=exited, status=1/FAILURE<br />
Failed to start Network Manager Wait Online<br />
Unit NetworkManger-wait-online.service entered failed state<br />
Starting Network.<br />
Reached target Network.<br />
<br />
This is due to the timeout setting in {{ic|/usr/lib/systemd/system/NetworkManager-wait-online.service}} being to short. Change the default timeout from 30 to a higher value.<br />
<br />
=== Set up PolicyKit permissions ===<br />
<br />
See [[General Troubleshooting#Session permissions]] for setting up a working session.<br />
<br />
With a working session, you have several options for granting the necessary privileges to NetworkManager:<br />
<br />
''Option 1.'' Run a [[PolicyKit]] authentication agent when you log in, such as {{ic|/usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1}} (part of {{Pkg|polkit-gnome}}). You will be prompted for your password whenever you add or remove a network connection.<br />
<br />
''Option 2.'' Add yourself to the {{ic|wheel}} group. You will not have to enter your password, but your user account may be granted other permissions as well, such as the ability to use [[sudo]] without entering the root password.<br />
<br />
''Option 3.'' Add yourself to the {{ic|network}} group and create the following file:<br />
{{hc|/etc/polkit-1/rules.d/50-org.freedesktop.NetworkManager.rules|<nowiki><br />
polkit.addRule(function(action, subject) {<br />
if (action.id.indexOf("org.freedesktop.NetworkManager.") == 0 && subject.isInGroup("network")) {<br />
return polkit.Result.YES;<br />
}<br />
});</nowiki>}}<br />
All users in the {{ic|network}} group will be able to add and remove networks without a password. This will not work under systemd if you do not have an active session with [[Systemd#Using_systemd-logind|systemd-logind]].<br />
<br />
=== Network services with NetworkManager dispatcher===<br />
<br />
There are quite a few network services that you will not want running until NetworkManager brings up an interface. Good examples are [[OpenNTPD]] and network filesystem mounts of various types (e.g. '''netfs'''). NetworkManager has the ability to start these services when you connect to a network and stop them when you disconnect.<br />
<br />
To use this feature, scripts can be added to the {{ic|/etc/NetworkManager/dispatcher.d}} directory. These scripts will need to have executable, user permissions. For security, it is good practice to make them owned by '''root:root''' and writable only by the owner.<br />
<br />
The scripts will be run in alphabetical order at connection time, and in reverse alphabetical order at disconnect time. They receive two arguments: the name of the interface (e.g. ''eth0'') and the status (''up'' or ''down''). To ensure what order they come up in, it is common to use numerical characters prior to the name of the script (e.g. {{ic|10_portmap}} or {{ic|30_netfs}} (which ensures that the portmapper is up before NFS mounts are attempted).<br />
<br />
{{Warning|For security reason. You should disable write access for group and other. For example use 755 mask.<br />
In other case it can refuse to execute script, with error message "nm-dispatcher.action: Script could not be executed: writable by group or other, or set-UID." in {{ic|/var/log/messages.log}} }}<br />
{{Warning|if you connect to foreign or public networks, be aware of what services you are starting and what servers you expect to be available for them to connect to. You could make a security hole by starting the wrong services while connected to a public network.}}<br />
<br />
==== Start OpenNTPD ====<br />
<br />
The following example starts the OpenNTPD daemon when an interface is brought up. Save the file as {{ic|/etc/NetworkManager/dispatcher.d/20_openntpd}} and make it executable.<br />
<br />
{{bc|<nowiki><br />
#!/bin/sh<br />
interface=$1 status=$2<br />
case $status in<br />
up)<br />
systemctl start openntpd<br />
;;<br />
down)<br />
if ! nm-tool | awk '/State:/{print $2}' | grep -qs connected; then<br />
systemctl stop openntpd<br />
fi<br />
;;<br />
esac<br />
</nowiki>}}<br />
<br />
==== Mount remote folder with sshfs ====<br />
<br />
As the script is run in a very restrictive environment, you have to export {{ic|SSH_AUTH_SOCK}} in order to connect to your SSH agent. There are different ways to accomplish this, see [https://bbs.archlinux.org/viewtopic.php?pid=1042030#p1042030 this link] for more information. The example below works with [[gnome-keyring]], and will ask you for the password if not unlocked already. In case NetworkManager connects automatically on login, it is likely gnome-keyring has not yet started and the export will fail (hence the sleep). The {{ic|UUID}} to match can be found with the command {{ic|nmcli con status}} or {{ic|nmcli con list}}. <br />
<br />
{{bc|<nowiki><br />
#!/bin/sh<br />
USER='username'<br />
REMOTE='user@host:/remote/path'<br />
LOCAL='/local/path'<br />
<br />
interface=$1 status=$2<br />
if [ "$CONNECTION_UUID" = "<uuid>" ]; then<br />
case $status in<br />
up)<br />
export SSH_AUTH_SOCK=$(find /tmp -maxdepth 1 -type s -user "$USER" -name 'ssh')<br />
su "$USER" -c "sshfs $LOCAL $REMOTE"<br />
;;<br />
down)<br />
fusermount -u "$LOCAL"<br />
;;<br />
esac<br />
fi<br />
</nowiki>}}<br />
<br />
==== Use dispatcher to connect to a VPN after a network-connection is established ====<br />
<br />
In this example we want to connect automatically to a previously defined VPN connection after connecting to a specific WiFi network. First thing to do is to create the dispatcher script that defines what to do after we are connected to the network. <br />
<br />
:1. Create the dispatcher script:<br />
{{hc|/etc/NetworkManager/dispatcher.d/vpn-up|<nowiki><br />
#!/bin/sh<br />
VPN_NAME="name of VPN connection defined in NetworkManager"<br />
ESSID="wifi network ESSID (not connection name)"<br />
<br />
interface=$1 status=$2<br />
case $status in<br />
up|vpn-down)<br />
if iwgetid | grep -qs ":\"$ESSID\""; then<br />
nmcli con up id "$VPN_NAME"<br />
fi<br />
;;<br />
down)<br />
if iwgetid | grep -qs ":\"$ESSID\""; then<br />
if nmcli con status id "$VPN_NAME" | grep -qs activated; then<br />
nmcli con down id "$VPN_NAME"<br />
fi<br />
fi<br />
;;<br />
esac<br />
</nowiki>}}<br />
Remember to make it executable with {{ic|chmod +x}} and to make the VPN connection available to all users. <br />
<br />
Trying to connect using this setup will fail and NetworkManager will complain about 'no valid VPN secrets', because of [http://projects.gnome.org/NetworkManager/developers/migrating-to-09/secrets-flags.html the way VPN secrets are stored] which brings us to step 2:<br />
<br />
:2. Edit your VPN connection configuration file to make NetworkManager store the secrets by itself rather than inside a keyring [https://bugzilla.redhat.com/show_bug.cgi?id=710552 that will be inaccessible for root]: open up {{ic|/etc/NetworkManager/system-connections/<name of your VPN connection>}} and change the {{ic|password-flags}} and {{ic|secret-flags}} form {{ic|1}} to {{ic|0}}.<br />
<br />
{{Note|It may now be necessary to re-open the NetworkManager connection editor and re-enter the VPN passwords/secrets.}}<br />
<br />
=== Proxy settings ===<br />
<br />
NetworkManager does not directly handle proxy settings, but if you are using GNOME, you could use [http://marin.jb.free.fr/proxydriver/ proxydriver] wich handles proxy settings using NetworkManager's informations. You can find the package for {{AUR|proxydriver}} in the [[AUR]].<br />
<br />
In order for proxydriver to be able to change the proxy settings, you would need to execute this command, as part of the GNOME startup process (System -> Preferences -> Startup Applications):<br />
<br />
xhost +si:localuser:your_username<br />
<br />
See: [[Proxy settings]]<br />
<br />
== Testing ==<br />
<br />
NetworkManager applets are designed to load upon login so no further configuration should be necessary for most users. If you have already disabled your previous network settings and disconnected from your network, you can now test if NetworkManager will work. The first step is to [[Daemon|start]] the ''networkmanager'' daemon.<br />
<br />
Some applets will provide you with a {{ic|.desktop}} file so that the NetworkManager applet can be loaded through the application menu. If it does not, you are going to either have to discover the command to use or logout and login again to start the applet. Once the applet is started, it will likely begin polling network connections with for auto-configuration with a DHCP server.<br />
<br />
To start the GNOME applet in non-xdg-compliant window managers like [[Awesome]]:<br />
<br />
nm-applet --sm-disable &<br />
<br />
For static IPs you will have to configure NetworkManager to understand them. The process usually involves right-clicking the applet and selecting something like 'Edit Connections'.<br />
<br />
== Troubleshooting ==<br />
<br />
Some fixes to common problems.<br />
<br />
=== No traffic via PPTP tunnel ===<br />
<br />
PPTP connection logins successfully, you see ppp0 interface with correct VPN IP, but you cannot even ping remote IP. It is due to lack of MPPE (Microsoft Point-to-Point Encryption) support in stock Arch pppd. It is recommended to first try with the stock Arch {{Pkg|ppp}} as it may work as intended.<br />
<br />
To solve the problem it should be sufficient to install {{AUR|ppp-mppe}} from the [[AUR]].<br />
<br />
=== Network management disabled ===<br />
<br />
Sometimes when NetworkManager shuts down but the pid (state) file does not get removed and you will get a 'Network management disabled' message. If this happens, you'll have to remove it manually:<br />
<br />
# rm /var/lib/NetworkManager/NetworkManager.state<br />
<br />
If this happens upon reboot, you can add an action to your {{ic|/etc/rc.local}} to have it removed upon bootup:<br />
<br />
{{bc|<nowiki>nmpid=/var/lib/NetworkManager/NetworkManager.state<br />
[ -f $nmpid ] && rm $nmpid</nowiki>}}<br />
<br />
=== NetworkManager prevents DHCPCD from using resolv.conf.head and resolv.conf.tail ===<br />
<br />
Sometimes it is problematic to add static items to {{ic|resolv.conf}} when it is constantly rewritten by NetworkManager and {{ic|dhcpcd}}. A simple solution is using the following script:<br />
{{bc|<nowiki><br />
#!/bin/bash<br />
# <br />
# /etc/NetworkManager/dispatcher.d/99-resolv.conf-head_and_tail<br />
# Include /etc/resolv.conf.head and /etc/resolv.conf.tail to /etc/resolv.conf<br />
#<br />
# scripts in the /etc/NetworkManager/dispatcher.d/ directory<br />
# are called alphabetically and are passed two parameters:<br />
# $1 is the interface name, and $2 is “up” or “down” as the<br />
# case may be.<br />
<br />
resolvconf='/etc/resolv.conf';<br />
cat "$resolvconf"{.head,,.tail} 2>/dev/null > "$resolvconf".tmp<br />
mv -f "$resolvconf".tmp "$resolvconf"<br />
</nowiki>}}<br />
<br />
This script is also available in the [https://aur.archlinux.org/packages/networkmanager-dispatch-resolv AUR] for convenience<br />
<br />
=== Preserving changes to resolv.conf ===<br />
<br />
NetworkManager will attempt to write DNS information from DHCP into {{ic|/etc/resolv.conf}}, overwriting the existing contents. To prevent this, you can set the immutable bit on the file:<br />
# chattr +i /etc/resolv.conf<br />
<br />
To modify the file in the future, first remove the immutable bit:<br />
# chattr -i /etc/resolv.conf<br />
<br />
=== DHCP problems ===<br />
<br />
If you have problems with getting an IP via DHCP, try to add the following to your {{ic|/etc/dhclient.conf}}:<br />
interface "eth0" {<br />
send dhcp-client-identifier 01:aa:bb:cc:dd:ee:ff;<br />
}<br />
Where {{ic|aa:bb:cc:dd:ee:ff}} is the MAC address of this NIC. The MAC address can be found using the {{ic|ip link show eth0}} command from the {{Pkg|iproute2}} package.<br />
<br />
For some (incompliant) routers, you will not be able to connect properly unless you comment the line<br />
require dhcp_server_identifier<br />
in {{ic|/etc/dhcpcd.conf}} (note that this file is distinct from {{ic|dhcpd.conf}}). This should not cause issues unless you have multiple DHCP servers on your network (not typical); see [http://technet.microsoft.com/en-us/library/cc977442.aspx this page] for more information.<br />
<br />
=== Hostname problems ===<br />
Add the following line to /etc/NetworkManager/NetworkManager.conf:<br />
dhcp=dhcpcd<br />
then restart.<br />
systemctl restart NetworkManager<br />
source https://bbs.archlinux.org/viewtopic.php?id=152376<br />
=== Missing default route ===<br />
<br />
On at least one KDE4 system, no default route was created when establishing wireless connections with NetworkManager. Changing the route settings of the wireless connection to remove the default selection "Use only for resources on this connection" solved the issue.<br />
<br />
=== 3G modem not detected ===<br />
<br />
If NetworkManager (from v0.7.999) does not detect your 3G modem, but you still can connect using [[wvdial]], try installing <br />
{{Pkg|modemmanager}} and restart NetworkManager daemon with {{ic|rc.d restart networkmanager}}. It may also be necessary to replug or restart your modem. This utility provides support for hardware not in NetworkManager's default database.<br />
<br />
=== Switching off WLAN on laptops ===<br />
<br />
Sometimes NetworkManager will not work when you disable your WiFi adapter with a switch on your laptop and try to enable it again afterwards. This is often a problem with {{ic|rfkill}}. Install {{Pkg|rfkill}} from the [[official repositories]] and use <br />
<br />
$ watch -n1 rfkill list all<br />
<br />
to check if the driver notifies {{ic|rfkill}} about the wireless adapter's status.<br />
If one identifier stays blocked after you switch on the adapter you could try to manually unblock it with (where X is the number of the identifier provided by the above output):<br />
<br />
# rfkill event unblock X<br />
<br />
=== Static IP settings revert to DHCP ===<br />
<br />
Due to an unresolved bug, when changing default connections to static IP, {{ic|nm-applet}} may not properly store the configuration change, and will revert to automatic DHCP.<br />
<br />
To work around this issue you have to edit the default connection (e.g. "Auto eth0") in {{ic|nm-applet}}, change the connection name (e.g. "my eth0"), uncheck the "Available to all users" checkbox, change your static IP settings as desired, and click '''Apply'''. This will save a new connection with the given name.<br />
<br />
Next, you will want to make the default connection not connect automatically. To do so, run {{ic|nm-connection-editor}} (''not'' as root). In the connection editor, edit the default connection (eg "Auto eth0") and uncheck "Connect automatically". Click '''Apply''' and close the connection editor.<br />
<br />
=== Cannot edit connections as normal user ===<br />
<br />
See [[#Set_up_PolicyKit_permissions]].<br />
<br />
=== Forget hidden wireless network ===<br />
<br />
Since hidden network are not displayed in the selection list of the Wireless view, they cannot be forgotten (removed) with the GUI. You can delete one with the following command:<br />
<br />
# rm /etc/NetworkManager/system-connections/[SSID]<br />
<br />
This works for any other connection.<br />
<br />
=== VPN not working in Gnome ===<br />
<br />
When setting up openconnect or vpnc connections in NetworkManager while using Gnome, you'll sometimes never see the dialog box pop up and the following error appears in /var/log/errors.log:<br />
<br />
localhost NetworkManager[399]: <error> [1361719690.10506] [nm-vpn-connection.c:1405] get_secrets_cb(): Failed to request VPN secrets #3: (6) No agents were available for this request.<br />
<br />
This is caused by the Gnome NM Applet expecting dialog scripts to be at /usr/lib/gnome-shell, when NetworkManager's packages put them in /usr/lib/networkmanager.<br />
As a "temporary" fix (this bug has been around for a while now), make the following symlink(s):<br />
<br />
# For OpenConnect<br />
ln -s /usr/lib/networkmanager/nm-openconnect-auth-dialog /usr/lib/gnome-shell/ <br />
<br />
# For VPNC (i.e. Cisco VPN)<br />
ln -s /usr/lib/networkmanager/nm-vpnc-auth-dialog /usr/lib/gnome-shell/<br />
<br />
This may need to be done for any other NM VPN plugins as well, but these are the two most common.<br />
<br />
== Tips and tricks ==<br />
<br />
=== Sharing internet connection over wifi ===<br />
<br />
You can share your internet connection (eg.: 3G or wired) by few clicks using nm. You will need supported wifi card (Cards based on Atheros AR9xx or at least AR5xx are probably best choice)<br />
<br />
==== Ad-hoc ====<br />
<br />
* pacman -S dnsmasq<br />
* custom dnsmasq.conf may interfere with nm (not sure about this, but i think so)<br />
* Click on nm-applet -> Create new wireless network<br />
* Follow wizard (if using WEP be sure to use 5 or 13 charactes long password, different lengths will fail)<br />
* Settings will remain stored for next time you'll need it<br />
<br />
==== Real AP ====<br />
<br />
Support of infrastructure mode (which is needed by Andoid phones as they don't intentionally support ad-hoc) is not currently supported by NetworkManager, but is in active development...<br />
<br />
See: http://fedoraproject.org/wiki/Features/RealHotspot<br />
<br />
=== Checking if networking is up inside a cron job or script ===<br />
<br />
Some cron jobs require networking to be up to succeed. You may wish to avoid running these jobs when the network is down. To accomplish this, add an '''if''' test for networking that queries NetworkManager's {{ic|nm-tool}} and checks the state of networking. The test shown here succeeds if any interface is up, and fails if they are all down. This is convenient for laptops that might be hardwired, might be on wireless, or might be off the network. <br />
if [ `nm-tool|grep State|cut -f2 -d' '` == "connected" ]; then<br />
#Whatever you want to do if the network is online<br />
else<br />
#Whatever you want to do if the network is offline - note, this and the else above are optional<br />
fi<br />
<br />
This useful for a {{ic|cron.hourly}} script that runs {{ic|fpupdate}} for the F-Prot virus scanner signature update, as an example. Another way it might be useful, with a little modification, is to differentiate between networks using various parts of the output from {{ic|nm-tool}}; for example, since the active wireless network is denoted with an asterisk, you could grep for the network name and then grep for a literal asterisk.<br />
<br />
=== Automatically unlock keyring after login ===<br />
<br />
==== GNOME ====<br />
<br />
# Right click on the {{ic|nm-applet}} icon in your panel and select Edit Connections and open the Wireless tab<br />
# Select the connection you want to work with and click the Edit button<br />
# Check the boxes “Connect Automatically” and “Available to all users”<br />
Log out and log back in to complete.<br />
<br />
{{Note|The following method is dated and known not to work on at least one machine!}}<br />
* In {{ic|/etc/pam.d/gdm}} (or your corresponding daemon in {{ic|/etc/pam.d}}), add these lines at the end of the "auth" and "session" blocks if they do not exist already: <br />
auth optional pam_gnome_keyring.so<br />
session optional pam_gnome_keyring.so auto_start<br />
<br />
* In {{ic|/etc/pam.d/passwd}}, use this line for the 'password' block:<br />
password optional pam_gnome_keyring.so<br />
<br />
:Next time you log in, you should be asked if you want the password to be unlocked automatically on login.<br />
<br />
==== KDE ====<br />
{{Note|See http://live.gnome.org/GnomeKeyring/Pam for reference, and if you are using KDE with KDM, you can use {{AUR|pam-keyring-tool}} from the [[AUR]].}}<br />
<br />
Put a script like the following in {{ic|~/.kde4/Autostart}}:<br />
#!/bin/sh<br />
echo PASSWORD | /usr/bin/pam-keyring-tool --unlock --keyring=default -s<br />
Similar should work with Openbox, LXDE, etc.<br />
<br />
==== SLiM login manager ====<br />
See [[Slim#SLiM and Gnome Keyring]].<br />
<br />
=== Ignore specific devices ===<br />
<br />
Sometimes it may be desired that NetworkManager ignores specific devices and does not try to configure addresses and routes for them.You can quickly and easily ignore devices by MAC by using the following in {{ic|/etc/NetworkManager/NetworkManager.conf}} :<br />
[keyfile]<br />
unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C4<br />
After you have put this in, [[Daemon|restart]] NetworkManager, and you should be able to configure interfaces without NetworkManager altering what you have set.<br />
<br />
=== Connect faster ===<br />
<br />
==== Disabling IPv6 ====<br />
<br />
Slow connection or reconnection to the network may be due to superfluous IPv6 queries in NetworkManager. If there is no IPv6 support on the local network, connecting to a network may take longer than normal while NetworkManager tries to establish an IPv6 connection that eventually times out. The solution is to disable IPv6 within NetworkManager which will make network connection faster. This has to be done once for every network you connect to.<br />
<br />
* Right-click on the network status icon.<br />
* Click on "Edit Connections".<br />
* Go to the "Wired" or "Wireless" tab, as appropriate.<br />
* Select the name of the network.<br />
* Click on "Edit".<br />
* Go to the "IPv6 Settings" tab.<br />
* In the "Method" dropdown, choose "Ignore/Disabled".<br />
* Click on "Save".<br />
<br />
==== Speed up DHCP by disabling ARP probing in DHCPCD ====<br />
<br />
{{ic|dhcpcd}} contains an implementation of a recommendation of the DHCP standard ([http://www.ietf.org/rfc/rfc2131.txt RFC2131] section 2.2) to check via ARP if the assigned IP address is really not taken. This seems mostly useless in home networks, so you can save about 5 seconds on every connect by adding the following line to {{ic|/etc/dhcpcd.conf}}:<br />
<br />
noarp<br />
<br />
This is equivalent to passing {{ic|--noarp}} to {{ic|dhcpcd}}, and disables the described ARP probing, speeding up connections to networks with DHCP.<br />
<br />
==== Use OpenDNS servers ====<br />
<br />
Create {{ic|/etc/resolv.conf.opendns}} with the nameservers:<br />
<br />
nameserver 208.67.222.222<br />
nameserver 208.67.220.220<br />
<br />
or use Google DNS servers, because people have been getting ads via the OpenDNS servers lately <br />
<br />
nameserver 8.8.8.8<br />
nameserver 8.8.4.4<br />
<br />
And have the dispatcher replace the discovered DHCP servers with the OpenDNS ones:<br />
<br />
{{hc|/etc/NetworkManager/dispatcher.d/dns-servers-opendns|<nowiki><br />
#!/bin/bash<br />
# Use OpenDNS servers over DHCP discovered servers<br />
<br />
cp -f /etc/resolv.conf.opendns /etc/resolv.conf</nowiki>}}<br />
<br />
Make the script executable:<br />
<br />
# chmod +x /etc/NetworkManager/dispatcher.d/dns-servers-opendns</div>Shastryhttps://wiki.archlinux.org/index.php?title=AUR_Cleanup_Day/2010&diff=40842AUR Cleanup Day/20102008-05-07T07:55:28Z<p>Shastry: /* Package List */</p>
<hr />
<div>The AUR has a large number of obsolete packages which could use cleaning up. Examples of packages that may be cleaned up are:<br />
*packages that have been renamed or replaced<br />
*old and unmaintained developmental (cvs/svn/etc) packages<br />
<br />
Post suggestions of packages on this pages. Trusted Users will get together and go though the list in a couple of weeks and confirm which packages should be removed. '''Please DO NOT REMOVE suggestions from the wiki page but add a comment on why it should be kept instead.''' TUs will not delete any useful package.<br />
<br />
==Package List==<br />
* [http://aur.archlinux.org/packages.php?ID=2787 9base-devel] - Hasn't been update since 25/12/2005. I think its not needed.<br />
* [http://aur.archlinux.org/packages.php?ID=12840 abraca-hg] - Replaced by abraca-git<br />
* [http://aur.archlinux.org/packages.php?ID=7086 alienarena2007] - Replaced by alienarena<br />
* [http://aur.archlinux.org/packages.php?ID=573 amavisd-new] - old version, won't compile, maintainer don't answare for e-mails (I have made new package [http://aur.archlinux.org/packages.php?ID=14650 amavisdnew])<br />
* [http://aur.archlinux.org/packages.php?ID=3194 azrael] - dead project, does not compile<br />
* [http://aur.archlinux.org/packages.php?ID=1404 cdrtools-dvd] - Outdated, replaced by [http://aur.archlinux.org/packages.php?ID=323 cdrtools] or [http://www.archlinux.org/packages/search/?q=cdrkit cdrkit], maintainer's e-mail address is not valid<br />
* [http://aur.archlinux.org/packages.php?ID=1727 creapkg] - web site no longer exists<br />
* [http://aur.archlinux.org/packages.php?ID=1308 dx9wine] - contains a patch not needed anymore<br />
* [http://aur.archlinux.org/packages.php?ID=4493 eclipse-kde] - Dead<br />
* [http://aur.archlinux.org/packages.php?ID=13227 ethereal] - Renamed to wireshark, available in extra<br />
* [http://aur.archlinux.org/packages.php?ID=7259 firefox2-ca] - firefox2 is depreciated.<br />
* [http://aur.archlinux.org/packages.php?ID=10229 flumotion] - removed from community a year ago, orphan and 1 year out of date without any complain.<br />
* [http://aur.archlinux.org/packages.php?ID=1790 fusesmb] or [http://aur.archlinux.org/packages.php?ID=14475 fusesmb2] - duplicate (and both outdated, version 8.7 is available)<br />
* [http://aur.archlinux.org/packages.php?ID=13063 fftw2single] - part of fftw2 from [extra]<br />
* [http://aur.archlinux.org/packages.php?ID=13589 gimp-freetype] - This plugin was developed for gimp 2.0 and is not needed according to the notes [http://ftp.gwdg.de/pub/misc/grafik/gimp/gimp/plug-ins/v2.0/freetype/ here.]<br />
* [http://aur.archlinux.org/packages.php?ID=6823 gimp-resynth] or [http://aur.archlinux.org/packages.php?ID=12273 gimp-plugin-resynthesizer] - duplicate (best to keep latter)<br />
* [http://aur.archlinux.org/packages.php?ID=3754 gnash-cvs] - Hasn't been update since 18/11/2006. gnash is in extra now too.<br />
* gmpc*-svn - replaced by git<br />
* [http://aur.archlinux.org/packages.php?ID=3689 ii-hg] - outdated, probably discontinued as the project website isn't available anymore (moved maybe?)<br />
* [http://aur.archlinux.org/packages.php?ID=7488 ionice] - part of util-linux-ng<br />
* [http://aur.archlinux.org/packages.php?ID=7037 kanola] - probably dead project, didn't went past the 0.0.1 release since 2006<br />
* [http://aur.archlinux.org/packages.php?ID=8231 kdelibs-noarts] - out-of-date, modified official package<br />
* [http://aur.archlinux.org/packages.php?ID=12581 kdenlive 0.5_1-1] - out-of-date, doesn't compile<br />
** Latest stable version is 0.5, last updated in AUR on Sun, 09 Mar 2008 --[[User:Doc Angelo|Doc Angelo]]<br />
** It's not even out of date, nor duplicate of another package – 6xx<br />
* [http://aur.archlinux.org/packages.php?ID=6296 kernel26thinkpad] - obsolete, out of date since 2006<br />
* [http://aur.archlinux.org/packages.php?ID=10305 linux-uvc-isight] and [http://aur.archlinux.org/packages.php?ID=13687 linux-uvc-isight-svn] - Outdated, [http://aur.archlinux.org/packages.php?ID=6906 linux-uvc-svn] does the same thing<br />
* [http://aur.archlinux.org/packages.php?ID=5408 mlame] - just a small bash script, no project page, could be moved to the wiki maybe<br />
* [http://aur.archlinux.org/packages.php?ID=10526 moaceyahoo] - Dead project. Will post new one, someday.<br />
* [http://aur.archlinux.org/packages.php?ID=2700 mutt-cvs] - mutt switched to mercurial a while back; way outdated anyway.<br />
* [http://aur.archlinux.org/packages.php?ID=12051 netscape-navigator] - Not supported upstream anymore making it vulnerable to security issues.<br />
** Can be used for web development – 6xx<br />
* [http://aur.archlinux.org/packages.php?ID=15312 openssh-snapshot] - Not needed anymore<br />
* [http://aur.archlinux.org/packages.php?ID=12193 pidgin-xfire] - Broke; Replaced by [http://aur.archlinux.org/packages.php?ID=16776 pidgin-gfire].<br />
* [http://aur.archlinux.org/packages.php?ID=10514 rt61-cvs] - This driver is included in linus's tree and is therefore obsolete<br />
* [http://aur.archlinux.org/packages.php?ID=494 sonic-rainbow] - dead project, does not compile<br />
* [http://aur.archlinux.org/packages.php?ID=2612 stepmania-bin] - orphan, replaced by [http://aur.archlinux.org/packages.php?ID=5453 stepmania]<br />
* [http://aur.archlinux.org/packages.php?ID=15910 tar-fixed] - This bug is verified fixed in tar 1.20<br />
* [http://aur.archlinux.org/packages.php?ID=13622 wicd-svn] - Outdated, wicd on repository extra is newer.<br />
* [http://aur.archlinux.org/packages.php?ID=647 ximian-openoffice] - Ximian port of OpenOffice 1.x. Users should use the more secure OpenOffice 2.x. Also Ximian openoffice is what is now known as ooo-build.<br />
<br />
==Remove from Filesystem==<br />
<br />
This is a list of files on the AUR filesystem that have been created when poorly formed packages were uploaded. This is a secondary consideration.<br />
<br />
<pre><br />
/packages/0verkill-0.16.tar.gz/<br />
/packages/2007.02.17-2/<br />
/packages/abakus-0.91-1/<br />
/packages/abakus-0.91.tar.gz/<br />
/packages/abakus-0.91/<br />
/packages/akgregator/<br />
/packages/akregator/<br />
/packages/akregator1.0.2/<br />
/packages/akregator_1.0.2/<br />
/packages/amsn-0.97ec1/<br />
/packages/amsn-0.97rc1/<br />
/packages/amsn-097rc1-1/<br />
/packages/amsn-097rc1/<br />
/packages/amsn-cvs/<br />
/packages/amsn-svn_update/<br />
/packages/amsn096/<br />
/packages/amsn096rc1/<br />
/packages/bashstyle-5.0<br />
/packages/bashstyle-5.0rc1.tar.gz/<br />
/packages/bashstyle-5.0rc1.tar.gz1/<br />
/packages/bashstyle-5.0rc1/<br />
/packages/bashstyle.tar.gz/<br />
/packages/bashstyle-ng/<br />
/packages/bashstyle1/<br />
/packages/braero-svn<br />
/packages/braser-cvs/<br />
/packages/brasero-cvs/<br />
/packages/brasero.svn/<br />
/packages/brlcad-cvs/<br />
/packages/ccd2iso-0.3/<br />
/packages/cdcollect-0.6.0/<br />
/packages/centerim-4.22.2/<br />
/packages/centerim/<br />
/packages/ploticus-test/<br />
/packages/test-louipc/<br />
/packages/test/<br />
/packages/test_pkg/<br />
/packages/yacas-1.1.17-2/<br />
/packages/yacas-1.2.2/<br />
/packages/yacas-1.17-2/<br />
/packages/yacas-new/<br />
/packages/yacasnew/<br />
/packages/zzztest/<br />
/packages/zzzztest/<br />
</pre></div>Shastryhttps://wiki.archlinux.org/index.php?title=Dell_Inspiron_6400&diff=29672Dell Inspiron 64002007-09-21T20:59:27Z<p>Shastry: /* Conexant HDA D110 MDC V.92 modem (winmodem) */</p>
<hr />
<div>[[Category:Laptops (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
=Introduction=<br />
==Summary==<br />
The goal of this wiki is to provide a comprehensive guide for Dell Inspiron 6400 owners seeking to install Arch Linux. It will attempt to cover all facets of hardware management, including wireless networking and hotkey support. Although this guide has been written specifically for the Inspiron 6400, many of the sub-sections can be applied to other Dell Inspiron models, including: <br />
* Dell Inspiron e1405<br />
* Dell Inspiron 640m<br />
* Dell Inspiron e1705<br />
<br />
==From the original contributor==<br />
I will attempt to cover as much as possible, however please feel free to contribute to this guide as you feel necessary. I will be happy to answer any questions, but I am by no means a Linux expert so there's a good chance I won't know the answer either! ~Thayer ([[User:Thayer.w|thayer.w]]) (thayerw(at)gmail(dot)com)<br />
<br />
=Hardware Specifications=<br />
The 6400 series laptop is currently available in a number of configurations and this guide will attempt to cover them all. Refer to the list below to determine whether your configuration has been documented.<br />
<br />
*<span style="color:green;">Green items are confirmed to work</span><br />
*<span style="color:red;">Red items have yet to be confirmed and require a Wiki entry</span><br />
<br />
===Base Components===<br />
<br />
* Intel Core Duo and Core 2 Duo processors<br />
** T2500 (2GHz/667MHz FSB/2MB Cache)<br />
** T5600 (1.83GHz/667MHz FSB/2MB Cache)<br />
** T2050 (1.66GHz/667MHz FSB/2MB Cache)<br />
** T1350 (1.66GHz/667MHz FSB/2MB Cache)<br />
** T5200 (1.60GHz/667MHz FSB/2MB Cache)<br />
* 512MB/1GB/2GB 533MHz/667MHz DDR2 SDRAM Memory<br />
* 15.4" Widescreen Display<br />
** WXGA (1280 x 800)<br />
** <span style="color:green;">WSXGA 1280x800 with TrueLife™</span><br />
** <span style="color:green;">WSXGA+ 1680x1050 with TrueLife™</span><br />
* 80GB/100GB/120GB/160GB 5400/7200 RPM SATA Hard Drive<br />
* <span style="color:green;">8x CD/DVD+/-RW/DL+R</span><br />
* <span style="color:green;">Broadcom 440x 10/100 Ethernet</span><br />
* <span style="color:green;">Conexant HDA D110 MDC V.92 modem (winmodem)</span><br />
* <span style="color:green;">Sigmatel STAC 92xx Audio</span><br />
* <span style="color:green;">Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Card Reader</span><br />
* <span style="color:green;">4 USB 2.0 Ports</span><br />
* <span style="color:red;">Firewire port (IEEE 1394)</span><br />
* <span style="color:red;">1 ExpressCard Slot</span><br />
* <span style="color:green;">Synaptics touchpad with scroll zones</span><br />
<br />
===Video Options===<br />
<br />
* <span style="color:green;">128MB ATI Mobility Radeon X1300 with HyperMemory</span><br />
* <span style="color:green;">256MB ATI Mobility Radeon X1400 with Hypermemory</span><br />
* <span style="color:green;">256MB nVidia GeForce Go 7300 with TurboCache</span><br />
* <span style="color:green;">128MB Intel Graphics Media Accelerator 950</span><br />
<br />
===Wireless Options===<br />
<br />
* <span style="color:green;">Intel Pro/Wireless 3945ABG (802.11a/b/g)</span><br />
* <span style="color:green;">Dell Wireless 1390</span><br />
* <span style="color:green;">Dell Wireless 1500 Draft 802.11n Wireless (Intel 4965AGN)</span><br />
* <span style="color:green;">Dell Wireless 350 Bluetooth Module</span><br />
* <span style="color:green;">Dell Wireless 355 Bluetooth Module</span><br />
<br />
=Arch Installation=<br />
There are plenty of resources available to help new users install and configure a basic Arch Linux installation, including the [[Official_Arch_Linux_Install_Guide|Official Installation Guide]] and the [[Beginners_Guide|Beginners Guide]].<br />
<br />
That being said, the following tips are specific to the Dell Inspiron 6400 and may be of some help during installation.<br />
<br />
If an Ethernet (wired land-line) broadband internet connection is available it is highly recommended that Arch be installed with the smaller FTP ISO. If you plan to have a desktop environment (KDE, GNOME, etc) then the majority of the packages you require will come from the internet repositories and <em>not</em> the Arch CD itself. This method will get you up and running in the shortest amount of time. Simply download the FTP ISO, burn it to a CD and restart your computer.<br />
<br />
The following steps assume you are connected to the Internet with a wired Ethernet connection, as opposed to a wireless connection.<br />
<br />
==Boot the Arch Setup CD==<br />
If the laptop does not boot from the CD, reboot and press F12 at the DELL BIOS splash screen to access the boot menu. From there you can choose to boot from the CD/DVD drive.<br />
<br />
==Setup==<br />
For the most part, the default settings should be fine, however the following notes may be of assistance.<br />
<br />
===0 - Configure===<br />
Just follow the prompts, choosing the defaults when asked. Make sure you allow the setup to detect your basic hardware automatically when asked.<br />
<br />
===1 - Prepare Hard Disks===<br />
The following is an example partition table. The example hard drive is 100GB and is configured to run only Arch Linux. Your settings will vary depending on the size of your hard drive and the number of operating systems you plan to run.<br />
<br />
'''sda''' (100GB)<br />
'''sda1''' ext2 100MB /boot ''(the boot loader files and kernel images will be installed here)''<br />
'''sda2''' swap 2.1GB swap ''(this example notebook has 2GB of RAM and we want to leave room for suspend2disk (hibernation) functions)''<br />
'''sda3''' ext3 6GB / ''(root--everything else will go here except for the files in /home and /boot)''<br />
'''sda4''' ext3 90GB /home ''(it's actually less than 90GB because ext3 filesystems reserve space to avoid capacity problems, but you get the point)''<br />
<br />
===2 - Select Packages===<br />
*Choose a mirror ('''''ftp.nethat.com''''' works very well from Vancouver, BC @ 160kb/s)<br />
*Choose ''only'' the base packages<br />
*Select ''all'' packages by default<br />
<br />
===3 - Install Packages===<br />
*Answer ''yes'' to cache packages (default)<br />
*Grab a coffee, it's going to take a while to fetch 100MB of packages<br />
<br />
===4 - Configure System===<br />
Choose your preferred editor; either vim or nano. <br />
<br />
A few files can be left alone, but there are some changes worth mentioning:<br />
<br />
====rc.conf====<br />
*Change your locale if necessary, for example Canadians will want to use ''en_CA'':<br />
LOCALE="en_CA.utf8"<br />
*Change the timezone if necessary, for example:<br />
TIMEZONE="Canada/Pacific"<br />
*To get rid of that ever-so-annoying system beep, blacklist the PC speaker module:<br />
MOD_BLACKLIST=(pcspkr)<br />
*Change the hostname if you desire a unique name, for example:<br />
HOSTNAME="dublin"<br />
*If your Internet Service Provider assigns your IP address automatically (and most do), make sure ''eth0'' is set to ''dhcp'':<br />
lo="lo 127.0.0.1"<br />
'''eth0="dhcp"'''<br />
<br />
====hosts====<br />
Add a second line under localhost with your unique hostname (the same hostname you chose in rc.conf) in place of localhost, for example:<br />
127.0.0.1 localhost.localdomain localhost<br />
'''127.0.0.1 dublin.localdomain dublin'''<br />
<br />
====fstab====<br />
No changes should be necessary.<br />
<br />
====mkinitcpio.conf====<br />
No changes should be necessary.<br />
<br />
====modprobe.conf====<br />
No changes should be necessary.<br />
<br />
====resolv.conf====<br />
No changes should be necessary.<br />
<br />
====locale.gen====<br />
Uncomment the languages files you wish to use, including the one you configured under LOCALE in the rc.conf:<br />
#en_BW.UTF-8 UTF-8<br />
#en_BW ISO-8859-1<br />
'''en_CA.UTF-8 UTF-8'''<br />
'''en_CA ISO-8859-1'''<br />
#en_DK.UTF-8 UTF-8<br />
#en_DK ISO-8859-1<br />
<br />
Canadians should probably uncomment ''en_US, en_CA and en_GB''.<br />
<br />
====root password====<br />
Set a root password.<br />
<br />
====pacman mirrors====<br />
You can either use the same mirror you used to install the base packages, or you can choose a different one at this time. The mirror you select at this stage will be your default repository after installation is complete.<br />
<br />
===5 - Install Kernel===<br />
The default choices should be fine.<br />
<br />
===6 - Install Boot Loader===<br />
If you are installing Arch as the sole operating system on the notebook, just go with the default settings. If you are dual-booting with another OS, choose the options carefully to avoid problems with your existing settings.<br />
<br />
* When installing GRUB, you can also append '''vga=791''' to the kernel option to set your terminal (framebuffer) resolution to 1024x768, for example:<br />
kernel /vmlinuz26 root=/dev/sda3 ro '''vga=791'''<br />
<br />
===7 - Exit===<br />
Reboot, eject the CD and log into your new Arch Linux installation.<br />
<br />
==Synchronize Repositories and Update==<br />
When logging into Arch for the first time, it is a good idea to make sure the local package database is synchronized with the Arch software repositories and that all of your software is up to date. From the console, type:<br />
# pacman -Syu<br />
<br />
=Add Users=<br />
At this point you can add a local user account by typing:<br />
# useradd -m johndoe<br />
# passwd johndoe<br />
<br />
''The '''-m''' flag creates the user's /home directory and copies the default configuration files to it (from /etc/skel)''<br />
<br />
Note, you will not be able to use the '''sudo''' command with this account until you [[Sudo|install and configure sudo]].<br />
<br />
=Xorg=<br />
If you plan to install a desktop environment (e.g. GNOME, KDE, etc.) you must install and configure Xorg.<br />
<br />
===Installation===<br />
Install the necessary packages:<br />
# pacman -S xorg xterm hwd<br />
<br />
===Configuration===<br />
The <tt>hwd</tt> program (''Hardware Detect'') will examine your hardware and create a default configuration file for Xorg (''/etc/X11/xorg.conf''):<br />
# hwd -xa<br />
You should now have a working X setup, however the default configuration uses the generic VESA graphics driver. If you want to run your desktop at its native resolution (e.g. 1680x1050) and enable 3D acceleration, you'll need to install the appropriate driver for your video card. See the [[Dell_Inspiron_6400#Video|Video]] section below for detailed instructions.<br />
<br />
=Desktop Environments=<br />
Arch Linux supports a variety of desktop environments and window managers, all of which must be installed manually. Refer to the following list for more information:<br />
<br />
'''Openbox:''' [[Openbox|Openbox Wiki]]<br />
<br />
'''GNOME:''' [[GNOME|GNOME Wiki]]<br />
<br />
'''Xfce:''' [[Xfce|Xfce Wiki]]<br />
<br />
'''KDE:''' [[KDE|KDE Wiki]]<br />
<br />
'''KDEmod:''' Visit the KDEmod website at http://kdemod.ath.cx/ or see the [[KDEmod|KDEmod Wiki]] for more information.<br />
<br />
'''E17:''' [[E17|E17 Wiki]]<br />
<br />
'''Fluxbox:''' [[Fluxbox|Fluxbox Wiki]]<br />
<br />
=Hardware=<br />
<br />
==Audio==<br />
===Sigmatel/Intel Chipset===<br />
The Sigmatel audio chipset should be detected automatically during installation, requiring no input from the user. For example, the following kernel modules are configured in ''/etc/rc.conf'' by default:<br />
snd-mixer-oss snd-pcm-oss snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore<br />
<br />
====ALSA Audio Drivers====<br />
Refer to the [[ALSA]] wiki for general assistance with volume settings, group permissions, etc.<br />
<br />
====OSS Audio Drivers====<br />
See the [[OSS]] wiki for more information.<br />
<br />
==Video==<br />
===ATI X1300/X1400 Radeon Mobility===<br />
====Proprietary Driver (fglrx)====<br />
<br />
The fglrx ATI proprietary driver is available from the standard Arch repositories and is the simplest way to get full 3D acceleration and native resolutions on your notebook:<br />
# pacman -S fglrx<br />
Run the '''aticonfig''' tool to automatically add the appropriate settings to ''/etc/X11/xorg.conf'':<br />
# aticonfig --initial<br />
Lastly, we need to modify ''/etc/rc.conf'' and add the '''fglrx''' kernel driver to the MODULES section, for example:<br />
MODULES=('''fglrx''' b44 mii snd-mixer-oss ...)<br />
Reboot and confirm that the ATI driver is working by typing '''fglrxinfo''' in a terminal. The results should look something like this:<br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Mobility Radeon X1400<br />
OpenGL version string: 2.0.6473 (8.37.6)<br />
<br />
Further information can be found at the [[ATI]] wiki.<br />
<br />
====Open Source ATI Driver====<br />
<br />
Please refer to the [[ATI]] wiki for more information.<br />
<br />
===Intel Graphics Media Accelerator 950===<br />
====Open Source Intel Driver====<br />
<br />
Install the driver:<br />
# pacman -S xf86-video-intel<br />
<br />
Use '''''gft''''' to generate the Xorg ''Modeline'' values and then edit ''/etc/X11/xorg.conf'' and add these values to the ''Monitor'' section, for example:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "unknown"<br />
'''Modeline "800x600" 40.12 800 848 968 1056 600 601 605 628 #60Hz'''<br />
EndSection<br />
<br />
Lastly, add the following to the "Device" section, replacing the existing ''Driver'' value if present:<br />
<br />
VideoRam 229376<br />
Option "CacheLines" "1980"<br />
Driver "intel"<br />
<br />
===nVidia GeForce Go 7300===<br />
The [[NVIDIA|NVIDIA Driver Wiki]] works fine. A side note: When running Beryl/Compiz-Fusion, while opening multiple instances of FireFox, the entire window went black. Forcing AIGLX solved this.<br />
<br />
==Networking==<br />
<br />
===Broadcom 440x 10/100 Ethernet===<br />
The Broadcom Ethernet card should have out-of-the-box support. No configuration necessary.<br />
<br />
===Dell Wireless 1390===<br />
<br />
Dell does not offer native Linux drivers for the 1390 wireless card. Fortunately, '''ndiswrapper''' can be used to install the Windows driver:<br />
# pacman -S ndiswrapper<br />
<br />
Download the 1390 driver from the Dell website:<br />
wget http://ftp.us.dell.com/network/R140747.EXE<br />
<br />
Create a temp folder and extract the driver:<br />
mkdir ~/Dell1390<br />
mv R14070747.EXE ~/Dell1390 <br />
cd ~/Dell1390 <br />
unzip -a R14070747.EXE<br />
cd DRIVERS<br />
<br />
As root, configure ndiswrapper to use the Windows driver:<br />
# ndiswrapper -i bcmwl5.inf<br />
# ndiswrapper -l<br />
# ndiswrapper -m<br />
# modprobe ndiswrapper<br />
<br />
Test the new driver by typing '''iwlist scanning''' in a terminal.<br />
<br />
To load the driver automatically at each boot, add '''ndiswrapper''' to the MODULES array in ''/etc/rc.conf'', for example:<br />
MODULES=(fglrx '''ndiswrapper''' b44 mii ...)<br />
<br />
Finally, remove the temp folder used during installation:<br />
rm -rf ~/Dell1390<br />
<br />
===Dell Wireless 1500 Draft 802.11n Wireless (Intel 4965AGN)===<br />
Grab the driver packages:<br />
# pacman -S iwlwifi iwlwifi-4965-ucode<br />
Edit ''/etc/rc.conf'' as root and add '''iwl4965''' to the MODULES list:<br />
MODULES=(fglrx '''''iwl4965''''' b44 mii ...)<br />
Add '''wlan0="dchp"''' to the NETWORKING section:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''wlan0="dhcp"'''''<br />
If '''wlan0''' is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!wlan0''''')<br />
<br />
===Dell Wireless 350 Bluetooth Module===<br />
Install the bluetooth libraries and basic utilties:<br />
# pacman -S bluez-libs bluez-utils<br />
Add '''bluetooth''' to the DAEMONS list in ''/etc/rc.conf'', for example:<br />
DAEMONS=(syslog-ng powersaved '''bluetooth''' ipw3945d ...)<br />
Now, depending on your desktop environment, install the appropriate tools:<br />
<br />
For GNOME: <br />
# pacman -S gnome-bluetooth bluez-gnome<br />
For KDE:<br />
# pacman -S kdebluetooth<br />
<br />
===Dell Wireless 355 Bluetooth Module===<br />
The steps described above for Dell Wireless 350 Bluetooth Module work with Dell Wireless 355 Bluetooth Module too.<br />
<br />
===Intel PRO/Wireless 3945ABG===<br />
With the release of Intel's open source [http://intellinuxwireless.org/ iwlwifi driver], 3945 owners now have two choices for wireless drivers. As the iwlwifi project matures, the ipw3945 driver will become obsolete, however until that time it will remain below as a second alternative.<br />
<br />
Install and configure NetworkManager before attempting to install the Intel 3945 wireless drivers. Refer to the [[Networkmanager| Networkmanager Wiki]] for more information.<br />
<br />
====Method 1: iwlwifi driver====<br />
Grab the driver packages:<br />
# pacman -S iwlwifi iwlwifi-3945-ucode<br />
Edit ''/etc/rc.conf'' as root and add '''iwl3945''' to the MODULES list:<br />
MODULES=(fglrx '''''iwl3945''''' b44 mii ...)<br />
Add '''wlan0="dchp"''' to the NETWORKING section:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''wlan0="dhcp"'''''<br />
If '''wlan0''' is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!wlan0''''')<br />
<br />
====Method 2: ipw3945 driver====<br />
Grab the Intel 3945 driver packages:<br />
# pacman -S ipw3945<br />
Edit ''/etc/rc.conf'' as root and add '''ipw3945''' to the MODULES list:<br />
MODULES=(fglrx '''''ipw3945''''' b44 mii ...)<br />
Add '''eth1="dchp"''' to the NETWORKING section ''(Note: It is sometimes detected as eth2 instead of eth1, use '''ifconfig''' to verify yours and, if necessary add eth2="dhcp" instead)'':<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''eth1="dhcp"'''''<br />
If '''eth1''' (or '''eth2''') is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!eth1''''')<br />
Add '''ipw3945d''' to the DAEMONS list ''before'' the dhcdbd and networkmanager daemons:<br />
DAEMONS=(syslog-ng '''''ipw3945d''''' dhcdbd networkmanager alsa ...)<br />
<br />
==Conexant HDA D110 MDC V.92 modem (winmodem)==<br />
The Conexant modem requires the proprietary '''hsfmodem''' driver.<br />
Dell offers a debian package [http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R155004&SystemID=INSPIRONI6400/E1505&servicetag=&os=UBLN&osl=en&deviceid=8593&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=1&libid=20&fileid=206745 hsfmodem_7.60.00.06oem_i386.deb] at their [http://support.dell.com/ support site] that works at '''full speed''' unlike the trial version from [http://www.linuxant.com/ Linuxant] which works at 14.4kbps.<br />
<br />
The following '''PKGBUILD''' can be used to create an archlinux '''hsfmodem''' package from the debian package:<br />
pkgname=hsfmodem<br />
pkgver=7.60.00.06oem<br />
pkgrel=1<br />
pkgdesc="Conexant modem driver by Dell"<br />
url="http://support.dell.com/"<br />
license=("unknown")<br />
arch=('i686')<br />
source=(${pkgname}_${pkgver}_i386.deb)<br />
md5sums=('80d38fccab347638fa7a2237b458b428')<br />
<br />
build() {<br />
cd $startdir/src/<br />
ar x ${pkgname}_${pkgver}_i386.deb<br />
tar xzf data.tar.gz<br />
cp -a usr etc $startdir/pkg/<br />
}<br />
<br />
#Download and place '''hsfmodem_7.60.00.06oem_i386.deb''' and the '''PKGBUILD''' in a new folder, and run <code>makepkg</code> to create the package. See [[ABS]] for details on building packages.<br />
#Run <code>hsfconfig</code> as root to build the module and initialise the modem. A reboot is required before the modem can be initialised. Run <code>hsfconfig</code> again after reboot.<br />
#The modules are automatically loaded and a <code>/dev/modem</code> symlink is setup for use with the modem. Now use wvdial or other dialer programs to connect to the internet.<br />
<br />
==Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Card Reader==<br />
The Ricoh card reader should work out of the box, as long as '''MOD_AUTOLOAD''' is set to '''yes''' in ''/etc/rc.conf''. Assuming you use a HAL-aware desktop (GNOME, KDE, etc.), when a memory card is inserted, the kernel should automatically load the '''mmc_core/mmc_block''' modules and mount the new filesystem according to your desktop's automount settings. <br />
<br />
This has been confirmed with the following card types:<br />
* SD Card<br />
<br />
==Synaptics Touchpad==<br />
The Synaptics touchpad should provide basic functions out-of-the-box, however if you would like to use the scroll zones and enable other advanced features, please refer to the [[Touchpad_Synaptics | Synaptics Touchpad]] wiki.<br />
<br />
=Power Management=<br />
<br />
==ACPI Hibernation/Suspend with pm-utils==<br />
The powersave scripts have been officially replaced by [http://www.archlinux.org/packages/search/?q=pm-utils pm-utils]. Refer to the [[Pm-utils]] wiki for detailed instructions.<br />
<br />
'''''Note:''''' ATI video card owners must also add '''vga=0''' to the kernel options in <tt>/boot/grub/menu.lst</tt> in order to resume from suspend2ram. For exmaple:<br />
<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda3 resume=/dev/sda2 ro '''''vga=0'''''<br />
initrd /kernel26.img<br />
<br />
==CPU Frequency Scaling with cpufrequtils==<br />
<br />
Refer to the [[Cpufrequtils]] wiki for step-by-step instructions.<br />
<br />
= Multimedia Buttons & Fn Hotkeys =<br />
Unfortunately, configuring multimedia buttons and function keys on your laptop can be complicated process. Factors that must be taken into consideration include your choice of Desktop Environment (or lack thereof) and the actions you wish to bind to the special buttons or keys. For a detailed explanation of what is required, please refer to the [[Hotkeys]] wiki.<br />
<br />
The following tips may offer some assistance in getting started.<br />
<br />
== Multimedia Buttons ==<br />
For the most part, the Volume and Playback buttons should be recognized as an unassigned key by the Linux kernel. In which case, all that is necessary is to bind the button to an action. <br />
<br />
It is also worth noting that the multimedia buttons and equivalent Fn key shortcut (e.g. Fn+PgUp = Vol Up) will produce the same keycode, so if you configure the button, the Fn hotkey combo will execute the same action.<br />
<br />
=== GNOME ===<br />
The GNOME desktop provides an easy method for binding multimedia keys to their appropriate action. <br />
<br />
# Browse to '''System -> Preferences -> Keyboard Shortcuts''' and scroll down to the '''Sound''' section.<br />
# Click on an item (e.g. Mute) and then press the corresponding multimedia button<br />
# Repeat this process for all of the multimedia buttons<br />
<br />
The volume buttons should now work system-wide, and the playback buttons will now work in media players such as Rhythmbox and Exaile.<br />
<br />
=== Openbox and other Window Managers ===<br />
The <tt>xbindkeys</tt> utility is highly recommended for lightweight desktops such as Openbox--refer to the [[Hotkeys]] wiki for information. <br />
<br />
The following is an example ''~/.xbindkeysrc'' config file, making use of the multimedia buttons:<br />
<pre><br />
# vol up<br />
"amixer set Master 2dB+ unmute"<br />
m:0x10 + c:176<br />
# vol dn<br />
"amixer set Master 2dB- unmute"<br />
m:0x10 + c:174<br />
# vol mute<br />
"amixer set Master mute"<br />
m:0x10 + c:160<br />
# play/pause<br />
"audacious -t"<br />
m:0x10 + c:162<br />
# back<br />
"audacious -r"<br />
m:0x10 + c:144<br />
# forward<br />
"audacious -f"<br />
m:0x10 + c:153<br />
# stop<br />
"audacious -s"<br />
m:0x10 + c:164<br />
</pre><br />
<br />
== Function (Fn) Hotkeys ==<br />
Function keys seem to be less standardized than the Volume/Playback buttons, and therefore it can be difficult to get all of them working properly. For example, the Standby shortcut (Fn+ESC) may be recognized while at the same time the Hibernate shortcut (Fn+F1) is not. To make matters more confusing, it appears that some Fn keys such as those that adjust the LCD brightness are controlled by the BIOS, independent of the Operating System. Again, the [[Hotkeys]] wiki is highly recommended reading.<br />
<br />
The following example shows how one can configure the Dell Media Direct button, Eject (Fn+F10) and Hibernate (Fn+F1) hotkeys to execute specific commands:<br />
<br />
First, assign kernel keycodes to the Media Direct button and Fn hotkeys, using the ''/etc/rc.local'' script (which is executed before X loads):<br />
#!/bin/bash<br />
#<br />
# /etc/rc.local: Local multi-user startup script.<br />
#<br />
setkeycodes e009 122 # e009 eject fn<br />
setkeycodes e012 130 # e012 mediadirect<br />
setkeycodes e00a 123 # e00a hibernate fn<br />
<br />
Then use the <tt>xbindkeys</tt> utility to bind the newly recognized keys to a custom action. Here's an ''~/.xbindkeysrc'' config file:<br />
<br />
# media direct button<br />
"streamtuner"<br />
m:0x10 + c:134<br />
# eject function hotkey<br />
"eject"<br />
m:0x10 + c:210 <br />
# hibernate function hotkey<br />
"sudo /usr/sbin/pm-hibernate"<br />
m:0x10 + c:209<br />
<br />
Finally, execute <tt>xbindkeys</tt> at startup by placing it in your .xinitrc (or appropriate startup file for your environment):<br />
xscreensaver -no-splash &<br />
eval `cat $HOME/.fehbg` &<br />
'''''xbindkeys &'''''<br />
#sleep 3<br />
pypanel &<br />
exec openbox<br />
<br />
As stated previously, it can be a complicated process involving lots of trial & error troubleshooting, but hopefully this will help you get started.<br />
<br />
=Resources=<br />
TuxMobil: [http://tuxmobil.org/mylaptops.html Linux Laptop & Notebook Installation Guides]<br />
<br />
TuxMobil: [http://tuxmobil.org/dell.html DELL Notebooks]<br />
<br />
Gentoo Wiki: [http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_6400 HARDWARE Dell Inspiron 6400]<br />
<br />
Gentoo Wiki: [http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_6400_Fixes_for_common_problems HARDWARE Dell Inspiron 6400 Fixes for common problems]<br />
<br />
<br />
<br />
=Comments=</div>Shastryhttps://wiki.archlinux.org/index.php?title=Dell_Inspiron_6400&diff=29671Dell Inspiron 64002007-09-21T20:58:18Z<p>Shastry: /* Conexant HDA D110 MDC V.92 modem (winmodem) */</p>
<hr />
<div>[[Category:Laptops (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
=Introduction=<br />
==Summary==<br />
The goal of this wiki is to provide a comprehensive guide for Dell Inspiron 6400 owners seeking to install Arch Linux. It will attempt to cover all facets of hardware management, including wireless networking and hotkey support. Although this guide has been written specifically for the Inspiron 6400, many of the sub-sections can be applied to other Dell Inspiron models, including: <br />
* Dell Inspiron e1405<br />
* Dell Inspiron 640m<br />
* Dell Inspiron e1705<br />
<br />
==From the original contributor==<br />
I will attempt to cover as much as possible, however please feel free to contribute to this guide as you feel necessary. I will be happy to answer any questions, but I am by no means a Linux expert so there's a good chance I won't know the answer either! ~Thayer ([[User:Thayer.w|thayer.w]]) (thayerw(at)gmail(dot)com)<br />
<br />
=Hardware Specifications=<br />
The 6400 series laptop is currently available in a number of configurations and this guide will attempt to cover them all. Refer to the list below to determine whether your configuration has been documented.<br />
<br />
*<span style="color:green;">Green items are confirmed to work</span><br />
*<span style="color:red;">Red items have yet to be confirmed and require a Wiki entry</span><br />
<br />
===Base Components===<br />
<br />
* Intel Core Duo and Core 2 Duo processors<br />
** T2500 (2GHz/667MHz FSB/2MB Cache)<br />
** T5600 (1.83GHz/667MHz FSB/2MB Cache)<br />
** T2050 (1.66GHz/667MHz FSB/2MB Cache)<br />
** T1350 (1.66GHz/667MHz FSB/2MB Cache)<br />
** T5200 (1.60GHz/667MHz FSB/2MB Cache)<br />
* 512MB/1GB/2GB 533MHz/667MHz DDR2 SDRAM Memory<br />
* 15.4" Widescreen Display<br />
** WXGA (1280 x 800)<br />
** <span style="color:green;">WSXGA 1280x800 with TrueLife™</span><br />
** <span style="color:green;">WSXGA+ 1680x1050 with TrueLife™</span><br />
* 80GB/100GB/120GB/160GB 5400/7200 RPM SATA Hard Drive<br />
* <span style="color:green;">8x CD/DVD+/-RW/DL+R</span><br />
* <span style="color:green;">Broadcom 440x 10/100 Ethernet</span><br />
* <span style="color:green;">Conexant HDA D110 MDC V.92 modem (winmodem)</span><br />
* <span style="color:green;">Sigmatel STAC 92xx Audio</span><br />
* <span style="color:green;">Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Card Reader</span><br />
* <span style="color:green;">4 USB 2.0 Ports</span><br />
* <span style="color:red;">Firewire port (IEEE 1394)</span><br />
* <span style="color:red;">1 ExpressCard Slot</span><br />
* <span style="color:green;">Synaptics touchpad with scroll zones</span><br />
<br />
===Video Options===<br />
<br />
* <span style="color:green;">128MB ATI Mobility Radeon X1300 with HyperMemory</span><br />
* <span style="color:green;">256MB ATI Mobility Radeon X1400 with Hypermemory</span><br />
* <span style="color:green;">256MB nVidia GeForce Go 7300 with TurboCache</span><br />
* <span style="color:green;">128MB Intel Graphics Media Accelerator 950</span><br />
<br />
===Wireless Options===<br />
<br />
* <span style="color:green;">Intel Pro/Wireless 3945ABG (802.11a/b/g)</span><br />
* <span style="color:green;">Dell Wireless 1390</span><br />
* <span style="color:green;">Dell Wireless 1500 Draft 802.11n Wireless (Intel 4965AGN)</span><br />
* <span style="color:green;">Dell Wireless 350 Bluetooth Module</span><br />
* <span style="color:green;">Dell Wireless 355 Bluetooth Module</span><br />
<br />
=Arch Installation=<br />
There are plenty of resources available to help new users install and configure a basic Arch Linux installation, including the [[Official_Arch_Linux_Install_Guide|Official Installation Guide]] and the [[Beginners_Guide|Beginners Guide]].<br />
<br />
That being said, the following tips are specific to the Dell Inspiron 6400 and may be of some help during installation.<br />
<br />
If an Ethernet (wired land-line) broadband internet connection is available it is highly recommended that Arch be installed with the smaller FTP ISO. If you plan to have a desktop environment (KDE, GNOME, etc) then the majority of the packages you require will come from the internet repositories and <em>not</em> the Arch CD itself. This method will get you up and running in the shortest amount of time. Simply download the FTP ISO, burn it to a CD and restart your computer.<br />
<br />
The following steps assume you are connected to the Internet with a wired Ethernet connection, as opposed to a wireless connection.<br />
<br />
==Boot the Arch Setup CD==<br />
If the laptop does not boot from the CD, reboot and press F12 at the DELL BIOS splash screen to access the boot menu. From there you can choose to boot from the CD/DVD drive.<br />
<br />
==Setup==<br />
For the most part, the default settings should be fine, however the following notes may be of assistance.<br />
<br />
===0 - Configure===<br />
Just follow the prompts, choosing the defaults when asked. Make sure you allow the setup to detect your basic hardware automatically when asked.<br />
<br />
===1 - Prepare Hard Disks===<br />
The following is an example partition table. The example hard drive is 100GB and is configured to run only Arch Linux. Your settings will vary depending on the size of your hard drive and the number of operating systems you plan to run.<br />
<br />
'''sda''' (100GB)<br />
'''sda1''' ext2 100MB /boot ''(the boot loader files and kernel images will be installed here)''<br />
'''sda2''' swap 2.1GB swap ''(this example notebook has 2GB of RAM and we want to leave room for suspend2disk (hibernation) functions)''<br />
'''sda3''' ext3 6GB / ''(root--everything else will go here except for the files in /home and /boot)''<br />
'''sda4''' ext3 90GB /home ''(it's actually less than 90GB because ext3 filesystems reserve space to avoid capacity problems, but you get the point)''<br />
<br />
===2 - Select Packages===<br />
*Choose a mirror ('''''ftp.nethat.com''''' works very well from Vancouver, BC @ 160kb/s)<br />
*Choose ''only'' the base packages<br />
*Select ''all'' packages by default<br />
<br />
===3 - Install Packages===<br />
*Answer ''yes'' to cache packages (default)<br />
*Grab a coffee, it's going to take a while to fetch 100MB of packages<br />
<br />
===4 - Configure System===<br />
Choose your preferred editor; either vim or nano. <br />
<br />
A few files can be left alone, but there are some changes worth mentioning:<br />
<br />
====rc.conf====<br />
*Change your locale if necessary, for example Canadians will want to use ''en_CA'':<br />
LOCALE="en_CA.utf8"<br />
*Change the timezone if necessary, for example:<br />
TIMEZONE="Canada/Pacific"<br />
*To get rid of that ever-so-annoying system beep, blacklist the PC speaker module:<br />
MOD_BLACKLIST=(pcspkr)<br />
*Change the hostname if you desire a unique name, for example:<br />
HOSTNAME="dublin"<br />
*If your Internet Service Provider assigns your IP address automatically (and most do), make sure ''eth0'' is set to ''dhcp'':<br />
lo="lo 127.0.0.1"<br />
'''eth0="dhcp"'''<br />
<br />
====hosts====<br />
Add a second line under localhost with your unique hostname (the same hostname you chose in rc.conf) in place of localhost, for example:<br />
127.0.0.1 localhost.localdomain localhost<br />
'''127.0.0.1 dublin.localdomain dublin'''<br />
<br />
====fstab====<br />
No changes should be necessary.<br />
<br />
====mkinitcpio.conf====<br />
No changes should be necessary.<br />
<br />
====modprobe.conf====<br />
No changes should be necessary.<br />
<br />
====resolv.conf====<br />
No changes should be necessary.<br />
<br />
====locale.gen====<br />
Uncomment the languages files you wish to use, including the one you configured under LOCALE in the rc.conf:<br />
#en_BW.UTF-8 UTF-8<br />
#en_BW ISO-8859-1<br />
'''en_CA.UTF-8 UTF-8'''<br />
'''en_CA ISO-8859-1'''<br />
#en_DK.UTF-8 UTF-8<br />
#en_DK ISO-8859-1<br />
<br />
Canadians should probably uncomment ''en_US, en_CA and en_GB''.<br />
<br />
====root password====<br />
Set a root password.<br />
<br />
====pacman mirrors====<br />
You can either use the same mirror you used to install the base packages, or you can choose a different one at this time. The mirror you select at this stage will be your default repository after installation is complete.<br />
<br />
===5 - Install Kernel===<br />
The default choices should be fine.<br />
<br />
===6 - Install Boot Loader===<br />
If you are installing Arch as the sole operating system on the notebook, just go with the default settings. If you are dual-booting with another OS, choose the options carefully to avoid problems with your existing settings.<br />
<br />
* When installing GRUB, you can also append '''vga=791''' to the kernel option to set your terminal (framebuffer) resolution to 1024x768, for example:<br />
kernel /vmlinuz26 root=/dev/sda3 ro '''vga=791'''<br />
<br />
===7 - Exit===<br />
Reboot, eject the CD and log into your new Arch Linux installation.<br />
<br />
==Synchronize Repositories and Update==<br />
When logging into Arch for the first time, it is a good idea to make sure the local package database is synchronized with the Arch software repositories and that all of your software is up to date. From the console, type:<br />
# pacman -Syu<br />
<br />
=Add Users=<br />
At this point you can add a local user account by typing:<br />
# useradd -m johndoe<br />
# passwd johndoe<br />
<br />
''The '''-m''' flag creates the user's /home directory and copies the default configuration files to it (from /etc/skel)''<br />
<br />
Note, you will not be able to use the '''sudo''' command with this account until you [[Sudo|install and configure sudo]].<br />
<br />
=Xorg=<br />
If you plan to install a desktop environment (e.g. GNOME, KDE, etc.) you must install and configure Xorg.<br />
<br />
===Installation===<br />
Install the necessary packages:<br />
# pacman -S xorg xterm hwd<br />
<br />
===Configuration===<br />
The <tt>hwd</tt> program (''Hardware Detect'') will examine your hardware and create a default configuration file for Xorg (''/etc/X11/xorg.conf''):<br />
# hwd -xa<br />
You should now have a working X setup, however the default configuration uses the generic VESA graphics driver. If you want to run your desktop at its native resolution (e.g. 1680x1050) and enable 3D acceleration, you'll need to install the appropriate driver for your video card. See the [[Dell_Inspiron_6400#Video|Video]] section below for detailed instructions.<br />
<br />
=Desktop Environments=<br />
Arch Linux supports a variety of desktop environments and window managers, all of which must be installed manually. Refer to the following list for more information:<br />
<br />
'''Openbox:''' [[Openbox|Openbox Wiki]]<br />
<br />
'''GNOME:''' [[GNOME|GNOME Wiki]]<br />
<br />
'''Xfce:''' [[Xfce|Xfce Wiki]]<br />
<br />
'''KDE:''' [[KDE|KDE Wiki]]<br />
<br />
'''KDEmod:''' Visit the KDEmod website at http://kdemod.ath.cx/ or see the [[KDEmod|KDEmod Wiki]] for more information.<br />
<br />
'''E17:''' [[E17|E17 Wiki]]<br />
<br />
'''Fluxbox:''' [[Fluxbox|Fluxbox Wiki]]<br />
<br />
=Hardware=<br />
<br />
==Audio==<br />
===Sigmatel/Intel Chipset===<br />
The Sigmatel audio chipset should be detected automatically during installation, requiring no input from the user. For example, the following kernel modules are configured in ''/etc/rc.conf'' by default:<br />
snd-mixer-oss snd-pcm-oss snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore<br />
<br />
====ALSA Audio Drivers====<br />
Refer to the [[ALSA]] wiki for general assistance with volume settings, group permissions, etc.<br />
<br />
====OSS Audio Drivers====<br />
See the [[OSS]] wiki for more information.<br />
<br />
==Video==<br />
===ATI X1300/X1400 Radeon Mobility===<br />
====Proprietary Driver (fglrx)====<br />
<br />
The fglrx ATI proprietary driver is available from the standard Arch repositories and is the simplest way to get full 3D acceleration and native resolutions on your notebook:<br />
# pacman -S fglrx<br />
Run the '''aticonfig''' tool to automatically add the appropriate settings to ''/etc/X11/xorg.conf'':<br />
# aticonfig --initial<br />
Lastly, we need to modify ''/etc/rc.conf'' and add the '''fglrx''' kernel driver to the MODULES section, for example:<br />
MODULES=('''fglrx''' b44 mii snd-mixer-oss ...)<br />
Reboot and confirm that the ATI driver is working by typing '''fglrxinfo''' in a terminal. The results should look something like this:<br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Mobility Radeon X1400<br />
OpenGL version string: 2.0.6473 (8.37.6)<br />
<br />
Further information can be found at the [[ATI]] wiki.<br />
<br />
====Open Source ATI Driver====<br />
<br />
Please refer to the [[ATI]] wiki for more information.<br />
<br />
===Intel Graphics Media Accelerator 950===<br />
====Open Source Intel Driver====<br />
<br />
Install the driver:<br />
# pacman -S xf86-video-intel<br />
<br />
Use '''''gft''''' to generate the Xorg ''Modeline'' values and then edit ''/etc/X11/xorg.conf'' and add these values to the ''Monitor'' section, for example:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "unknown"<br />
'''Modeline "800x600" 40.12 800 848 968 1056 600 601 605 628 #60Hz'''<br />
EndSection<br />
<br />
Lastly, add the following to the "Device" section, replacing the existing ''Driver'' value if present:<br />
<br />
VideoRam 229376<br />
Option "CacheLines" "1980"<br />
Driver "intel"<br />
<br />
===nVidia GeForce Go 7300===<br />
The [[NVIDIA|NVIDIA Driver Wiki]] works fine. A side note: When running Beryl/Compiz-Fusion, while opening multiple instances of FireFox, the entire window went black. Forcing AIGLX solved this.<br />
<br />
==Networking==<br />
<br />
===Broadcom 440x 10/100 Ethernet===<br />
The Broadcom Ethernet card should have out-of-the-box support. No configuration necessary.<br />
<br />
===Dell Wireless 1390===<br />
<br />
Dell does not offer native Linux drivers for the 1390 wireless card. Fortunately, '''ndiswrapper''' can be used to install the Windows driver:<br />
# pacman -S ndiswrapper<br />
<br />
Download the 1390 driver from the Dell website:<br />
wget http://ftp.us.dell.com/network/R140747.EXE<br />
<br />
Create a temp folder and extract the driver:<br />
mkdir ~/Dell1390<br />
mv R14070747.EXE ~/Dell1390 <br />
cd ~/Dell1390 <br />
unzip -a R14070747.EXE<br />
cd DRIVERS<br />
<br />
As root, configure ndiswrapper to use the Windows driver:<br />
# ndiswrapper -i bcmwl5.inf<br />
# ndiswrapper -l<br />
# ndiswrapper -m<br />
# modprobe ndiswrapper<br />
<br />
Test the new driver by typing '''iwlist scanning''' in a terminal.<br />
<br />
To load the driver automatically at each boot, add '''ndiswrapper''' to the MODULES array in ''/etc/rc.conf'', for example:<br />
MODULES=(fglrx '''ndiswrapper''' b44 mii ...)<br />
<br />
Finally, remove the temp folder used during installation:<br />
rm -rf ~/Dell1390<br />
<br />
===Dell Wireless 1500 Draft 802.11n Wireless (Intel 4965AGN)===<br />
Grab the driver packages:<br />
# pacman -S iwlwifi iwlwifi-4965-ucode<br />
Edit ''/etc/rc.conf'' as root and add '''iwl4965''' to the MODULES list:<br />
MODULES=(fglrx '''''iwl4965''''' b44 mii ...)<br />
Add '''wlan0="dchp"''' to the NETWORKING section:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''wlan0="dhcp"'''''<br />
If '''wlan0''' is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!wlan0''''')<br />
<br />
===Dell Wireless 350 Bluetooth Module===<br />
Install the bluetooth libraries and basic utilties:<br />
# pacman -S bluez-libs bluez-utils<br />
Add '''bluetooth''' to the DAEMONS list in ''/etc/rc.conf'', for example:<br />
DAEMONS=(syslog-ng powersaved '''bluetooth''' ipw3945d ...)<br />
Now, depending on your desktop environment, install the appropriate tools:<br />
<br />
For GNOME: <br />
# pacman -S gnome-bluetooth bluez-gnome<br />
For KDE:<br />
# pacman -S kdebluetooth<br />
<br />
===Dell Wireless 355 Bluetooth Module===<br />
The steps described above for Dell Wireless 350 Bluetooth Module work with Dell Wireless 355 Bluetooth Module too.<br />
<br />
===Intel PRO/Wireless 3945ABG===<br />
With the release of Intel's open source [http://intellinuxwireless.org/ iwlwifi driver], 3945 owners now have two choices for wireless drivers. As the iwlwifi project matures, the ipw3945 driver will become obsolete, however until that time it will remain below as a second alternative.<br />
<br />
Install and configure NetworkManager before attempting to install the Intel 3945 wireless drivers. Refer to the [[Networkmanager| Networkmanager Wiki]] for more information.<br />
<br />
====Method 1: iwlwifi driver====<br />
Grab the driver packages:<br />
# pacman -S iwlwifi iwlwifi-3945-ucode<br />
Edit ''/etc/rc.conf'' as root and add '''iwl3945''' to the MODULES list:<br />
MODULES=(fglrx '''''iwl3945''''' b44 mii ...)<br />
Add '''wlan0="dchp"''' to the NETWORKING section:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''wlan0="dhcp"'''''<br />
If '''wlan0''' is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!wlan0''''')<br />
<br />
====Method 2: ipw3945 driver====<br />
Grab the Intel 3945 driver packages:<br />
# pacman -S ipw3945<br />
Edit ''/etc/rc.conf'' as root and add '''ipw3945''' to the MODULES list:<br />
MODULES=(fglrx '''''ipw3945''''' b44 mii ...)<br />
Add '''eth1="dchp"''' to the NETWORKING section ''(Note: It is sometimes detected as eth2 instead of eth1, use '''ifconfig''' to verify yours and, if necessary add eth2="dhcp" instead)'':<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''eth1="dhcp"'''''<br />
If '''eth1''' (or '''eth2''') is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!eth1''''')<br />
Add '''ipw3945d''' to the DAEMONS list ''before'' the dhcdbd and networkmanager daemons:<br />
DAEMONS=(syslog-ng '''''ipw3945d''''' dhcdbd networkmanager alsa ...)<br />
<br />
==Conexant HDA D110 MDC V.92 modem (winmodem)==<br />
The Conexant modem requires the proprietary '''hsfmodem''' driver.<br />
Dell offers a debian package [http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R155004&SystemID=INSPIRONI6400/E1505&servicetag=&os=UBLN&osl=en&deviceid=8593&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=1&libid=20&fileid=206745 hsfmodem_7.60.00.06oem_i386.deb] at their [http://support.dell.com/ support site] that works at '''full speed''' unlike the trial version from [http://www.linuxant.com/ Linuxant] which works at 14.4kbps.<br />
<br />
The following '''PKGBUILD''' can be used to create an archlinux '''hsfmodem''' package from the debian package:<br />
pkgname=hsfmodem<br />
pkgver=7.60.00.06oem<br />
pkgrel=1<br />
pkgdesc="Conexant dialup modem driver by dell"<br />
url="http://support.dell.com/"<br />
license=("unknown")<br />
arch=('i686')<br />
source=(${pkgname}_${pkgver}_i386.deb)<br />
md5sums=('80d38fccab347638fa7a2237b458b428')<br />
<br />
build() {<br />
cd $startdir/src/<br />
ar x ${pkgname}_${pkgver}_i386.deb<br />
tar xzf data.tar.gz<br />
cp -a usr etc $startdir/pkg/<br />
}<br />
<br />
#Download and place '''hsfmodem_7.60.00.06oem_i386.deb''' and the '''PKGBUILD''' in a new folder, and run <code>makepkg</code> to create the package. See [[ABS]] for details on building packages.<br />
#Run <code>hsfconfig</code> as root to build the module and initialise the modem. A reboot is required before the modem can be initialised. Run <code>hsfconfig</code> again after reboot.<br />
#The modules are automatically loaded and a <code>/dev/modem</code> symlink is setup for use with the modem. Now use wvdial or other dialer programs to connect to the internet.<br />
<br />
==Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Card Reader==<br />
The Ricoh card reader should work out of the box, as long as '''MOD_AUTOLOAD''' is set to '''yes''' in ''/etc/rc.conf''. Assuming you use a HAL-aware desktop (GNOME, KDE, etc.), when a memory card is inserted, the kernel should automatically load the '''mmc_core/mmc_block''' modules and mount the new filesystem according to your desktop's automount settings. <br />
<br />
This has been confirmed with the following card types:<br />
* SD Card<br />
<br />
==Synaptics Touchpad==<br />
The Synaptics touchpad should provide basic functions out-of-the-box, however if you would like to use the scroll zones and enable other advanced features, please refer to the [[Touchpad_Synaptics | Synaptics Touchpad]] wiki.<br />
<br />
=Power Management=<br />
<br />
==ACPI Hibernation/Suspend with pm-utils==<br />
The powersave scripts have been officially replaced by [http://www.archlinux.org/packages/search/?q=pm-utils pm-utils]. Refer to the [[Pm-utils]] wiki for detailed instructions.<br />
<br />
'''''Note:''''' ATI video card owners must also add '''vga=0''' to the kernel options in <tt>/boot/grub/menu.lst</tt> in order to resume from suspend2ram. For exmaple:<br />
<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda3 resume=/dev/sda2 ro '''''vga=0'''''<br />
initrd /kernel26.img<br />
<br />
==CPU Frequency Scaling with cpufrequtils==<br />
<br />
Refer to the [[Cpufrequtils]] wiki for step-by-step instructions.<br />
<br />
= Multimedia Buttons & Fn Hotkeys =<br />
Unfortunately, configuring multimedia buttons and function keys on your laptop can be complicated process. Factors that must be taken into consideration include your choice of Desktop Environment (or lack thereof) and the actions you wish to bind to the special buttons or keys. For a detailed explanation of what is required, please refer to the [[Hotkeys]] wiki.<br />
<br />
The following tips may offer some assistance in getting started.<br />
<br />
== Multimedia Buttons ==<br />
For the most part, the Volume and Playback buttons should be recognized as an unassigned key by the Linux kernel. In which case, all that is necessary is to bind the button to an action. <br />
<br />
It is also worth noting that the multimedia buttons and equivalent Fn key shortcut (e.g. Fn+PgUp = Vol Up) will produce the same keycode, so if you configure the button, the Fn hotkey combo will execute the same action.<br />
<br />
=== GNOME ===<br />
The GNOME desktop provides an easy method for binding multimedia keys to their appropriate action. <br />
<br />
# Browse to '''System -> Preferences -> Keyboard Shortcuts''' and scroll down to the '''Sound''' section.<br />
# Click on an item (e.g. Mute) and then press the corresponding multimedia button<br />
# Repeat this process for all of the multimedia buttons<br />
<br />
The volume buttons should now work system-wide, and the playback buttons will now work in media players such as Rhythmbox and Exaile.<br />
<br />
=== Openbox and other Window Managers ===<br />
The <tt>xbindkeys</tt> utility is highly recommended for lightweight desktops such as Openbox--refer to the [[Hotkeys]] wiki for information. <br />
<br />
The following is an example ''~/.xbindkeysrc'' config file, making use of the multimedia buttons:<br />
<pre><br />
# vol up<br />
"amixer set Master 2dB+ unmute"<br />
m:0x10 + c:176<br />
# vol dn<br />
"amixer set Master 2dB- unmute"<br />
m:0x10 + c:174<br />
# vol mute<br />
"amixer set Master mute"<br />
m:0x10 + c:160<br />
# play/pause<br />
"audacious -t"<br />
m:0x10 + c:162<br />
# back<br />
"audacious -r"<br />
m:0x10 + c:144<br />
# forward<br />
"audacious -f"<br />
m:0x10 + c:153<br />
# stop<br />
"audacious -s"<br />
m:0x10 + c:164<br />
</pre><br />
<br />
== Function (Fn) Hotkeys ==<br />
Function keys seem to be less standardized than the Volume/Playback buttons, and therefore it can be difficult to get all of them working properly. For example, the Standby shortcut (Fn+ESC) may be recognized while at the same time the Hibernate shortcut (Fn+F1) is not. To make matters more confusing, it appears that some Fn keys such as those that adjust the LCD brightness are controlled by the BIOS, independent of the Operating System. Again, the [[Hotkeys]] wiki is highly recommended reading.<br />
<br />
The following example shows how one can configure the Dell Media Direct button, Eject (Fn+F10) and Hibernate (Fn+F1) hotkeys to execute specific commands:<br />
<br />
First, assign kernel keycodes to the Media Direct button and Fn hotkeys, using the ''/etc/rc.local'' script (which is executed before X loads):<br />
#!/bin/bash<br />
#<br />
# /etc/rc.local: Local multi-user startup script.<br />
#<br />
setkeycodes e009 122 # e009 eject fn<br />
setkeycodes e012 130 # e012 mediadirect<br />
setkeycodes e00a 123 # e00a hibernate fn<br />
<br />
Then use the <tt>xbindkeys</tt> utility to bind the newly recognized keys to a custom action. Here's an ''~/.xbindkeysrc'' config file:<br />
<br />
# media direct button<br />
"streamtuner"<br />
m:0x10 + c:134<br />
# eject function hotkey<br />
"eject"<br />
m:0x10 + c:210 <br />
# hibernate function hotkey<br />
"sudo /usr/sbin/pm-hibernate"<br />
m:0x10 + c:209<br />
<br />
Finally, execute <tt>xbindkeys</tt> at startup by placing it in your .xinitrc (or appropriate startup file for your environment):<br />
xscreensaver -no-splash &<br />
eval `cat $HOME/.fehbg` &<br />
'''''xbindkeys &'''''<br />
#sleep 3<br />
pypanel &<br />
exec openbox<br />
<br />
As stated previously, it can be a complicated process involving lots of trial & error troubleshooting, but hopefully this will help you get started.<br />
<br />
=Resources=<br />
TuxMobil: [http://tuxmobil.org/mylaptops.html Linux Laptop & Notebook Installation Guides]<br />
<br />
TuxMobil: [http://tuxmobil.org/dell.html DELL Notebooks]<br />
<br />
Gentoo Wiki: [http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_6400 HARDWARE Dell Inspiron 6400]<br />
<br />
Gentoo Wiki: [http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_6400_Fixes_for_common_problems HARDWARE Dell Inspiron 6400 Fixes for common problems]<br />
<br />
<br />
<br />
=Comments=</div>Shastryhttps://wiki.archlinux.org/index.php?title=Dell_Inspiron_6400&diff=29670Dell Inspiron 64002007-09-21T20:57:41Z<p>Shastry: /* Conexant HDA D110 MDC V.92 modem (winmodem) */</p>
<hr />
<div>[[Category:Laptops (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
=Introduction=<br />
==Summary==<br />
The goal of this wiki is to provide a comprehensive guide for Dell Inspiron 6400 owners seeking to install Arch Linux. It will attempt to cover all facets of hardware management, including wireless networking and hotkey support. Although this guide has been written specifically for the Inspiron 6400, many of the sub-sections can be applied to other Dell Inspiron models, including: <br />
* Dell Inspiron e1405<br />
* Dell Inspiron 640m<br />
* Dell Inspiron e1705<br />
<br />
==From the original contributor==<br />
I will attempt to cover as much as possible, however please feel free to contribute to this guide as you feel necessary. I will be happy to answer any questions, but I am by no means a Linux expert so there's a good chance I won't know the answer either! ~Thayer ([[User:Thayer.w|thayer.w]]) (thayerw(at)gmail(dot)com)<br />
<br />
=Hardware Specifications=<br />
The 6400 series laptop is currently available in a number of configurations and this guide will attempt to cover them all. Refer to the list below to determine whether your configuration has been documented.<br />
<br />
*<span style="color:green;">Green items are confirmed to work</span><br />
*<span style="color:red;">Red items have yet to be confirmed and require a Wiki entry</span><br />
<br />
===Base Components===<br />
<br />
* Intel Core Duo and Core 2 Duo processors<br />
** T2500 (2GHz/667MHz FSB/2MB Cache)<br />
** T5600 (1.83GHz/667MHz FSB/2MB Cache)<br />
** T2050 (1.66GHz/667MHz FSB/2MB Cache)<br />
** T1350 (1.66GHz/667MHz FSB/2MB Cache)<br />
** T5200 (1.60GHz/667MHz FSB/2MB Cache)<br />
* 512MB/1GB/2GB 533MHz/667MHz DDR2 SDRAM Memory<br />
* 15.4" Widescreen Display<br />
** WXGA (1280 x 800)<br />
** <span style="color:green;">WSXGA 1280x800 with TrueLife™</span><br />
** <span style="color:green;">WSXGA+ 1680x1050 with TrueLife™</span><br />
* 80GB/100GB/120GB/160GB 5400/7200 RPM SATA Hard Drive<br />
* <span style="color:green;">8x CD/DVD+/-RW/DL+R</span><br />
* <span style="color:green;">Broadcom 440x 10/100 Ethernet</span><br />
* <span style="color:green;">Conexant HDA D110 MDC V.92 modem (winmodem)</span><br />
* <span style="color:green;">Sigmatel STAC 92xx Audio</span><br />
* <span style="color:green;">Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Card Reader</span><br />
* <span style="color:green;">4 USB 2.0 Ports</span><br />
* <span style="color:red;">Firewire port (IEEE 1394)</span><br />
* <span style="color:red;">1 ExpressCard Slot</span><br />
* <span style="color:green;">Synaptics touchpad with scroll zones</span><br />
<br />
===Video Options===<br />
<br />
* <span style="color:green;">128MB ATI Mobility Radeon X1300 with HyperMemory</span><br />
* <span style="color:green;">256MB ATI Mobility Radeon X1400 with Hypermemory</span><br />
* <span style="color:green;">256MB nVidia GeForce Go 7300 with TurboCache</span><br />
* <span style="color:green;">128MB Intel Graphics Media Accelerator 950</span><br />
<br />
===Wireless Options===<br />
<br />
* <span style="color:green;">Intel Pro/Wireless 3945ABG (802.11a/b/g)</span><br />
* <span style="color:green;">Dell Wireless 1390</span><br />
* <span style="color:green;">Dell Wireless 1500 Draft 802.11n Wireless (Intel 4965AGN)</span><br />
* <span style="color:green;">Dell Wireless 350 Bluetooth Module</span><br />
* <span style="color:green;">Dell Wireless 355 Bluetooth Module</span><br />
<br />
=Arch Installation=<br />
There are plenty of resources available to help new users install and configure a basic Arch Linux installation, including the [[Official_Arch_Linux_Install_Guide|Official Installation Guide]] and the [[Beginners_Guide|Beginners Guide]].<br />
<br />
That being said, the following tips are specific to the Dell Inspiron 6400 and may be of some help during installation.<br />
<br />
If an Ethernet (wired land-line) broadband internet connection is available it is highly recommended that Arch be installed with the smaller FTP ISO. If you plan to have a desktop environment (KDE, GNOME, etc) then the majority of the packages you require will come from the internet repositories and <em>not</em> the Arch CD itself. This method will get you up and running in the shortest amount of time. Simply download the FTP ISO, burn it to a CD and restart your computer.<br />
<br />
The following steps assume you are connected to the Internet with a wired Ethernet connection, as opposed to a wireless connection.<br />
<br />
==Boot the Arch Setup CD==<br />
If the laptop does not boot from the CD, reboot and press F12 at the DELL BIOS splash screen to access the boot menu. From there you can choose to boot from the CD/DVD drive.<br />
<br />
==Setup==<br />
For the most part, the default settings should be fine, however the following notes may be of assistance.<br />
<br />
===0 - Configure===<br />
Just follow the prompts, choosing the defaults when asked. Make sure you allow the setup to detect your basic hardware automatically when asked.<br />
<br />
===1 - Prepare Hard Disks===<br />
The following is an example partition table. The example hard drive is 100GB and is configured to run only Arch Linux. Your settings will vary depending on the size of your hard drive and the number of operating systems you plan to run.<br />
<br />
'''sda''' (100GB)<br />
'''sda1''' ext2 100MB /boot ''(the boot loader files and kernel images will be installed here)''<br />
'''sda2''' swap 2.1GB swap ''(this example notebook has 2GB of RAM and we want to leave room for suspend2disk (hibernation) functions)''<br />
'''sda3''' ext3 6GB / ''(root--everything else will go here except for the files in /home and /boot)''<br />
'''sda4''' ext3 90GB /home ''(it's actually less than 90GB because ext3 filesystems reserve space to avoid capacity problems, but you get the point)''<br />
<br />
===2 - Select Packages===<br />
*Choose a mirror ('''''ftp.nethat.com''''' works very well from Vancouver, BC @ 160kb/s)<br />
*Choose ''only'' the base packages<br />
*Select ''all'' packages by default<br />
<br />
===3 - Install Packages===<br />
*Answer ''yes'' to cache packages (default)<br />
*Grab a coffee, it's going to take a while to fetch 100MB of packages<br />
<br />
===4 - Configure System===<br />
Choose your preferred editor; either vim or nano. <br />
<br />
A few files can be left alone, but there are some changes worth mentioning:<br />
<br />
====rc.conf====<br />
*Change your locale if necessary, for example Canadians will want to use ''en_CA'':<br />
LOCALE="en_CA.utf8"<br />
*Change the timezone if necessary, for example:<br />
TIMEZONE="Canada/Pacific"<br />
*To get rid of that ever-so-annoying system beep, blacklist the PC speaker module:<br />
MOD_BLACKLIST=(pcspkr)<br />
*Change the hostname if you desire a unique name, for example:<br />
HOSTNAME="dublin"<br />
*If your Internet Service Provider assigns your IP address automatically (and most do), make sure ''eth0'' is set to ''dhcp'':<br />
lo="lo 127.0.0.1"<br />
'''eth0="dhcp"'''<br />
<br />
====hosts====<br />
Add a second line under localhost with your unique hostname (the same hostname you chose in rc.conf) in place of localhost, for example:<br />
127.0.0.1 localhost.localdomain localhost<br />
'''127.0.0.1 dublin.localdomain dublin'''<br />
<br />
====fstab====<br />
No changes should be necessary.<br />
<br />
====mkinitcpio.conf====<br />
No changes should be necessary.<br />
<br />
====modprobe.conf====<br />
No changes should be necessary.<br />
<br />
====resolv.conf====<br />
No changes should be necessary.<br />
<br />
====locale.gen====<br />
Uncomment the languages files you wish to use, including the one you configured under LOCALE in the rc.conf:<br />
#en_BW.UTF-8 UTF-8<br />
#en_BW ISO-8859-1<br />
'''en_CA.UTF-8 UTF-8'''<br />
'''en_CA ISO-8859-1'''<br />
#en_DK.UTF-8 UTF-8<br />
#en_DK ISO-8859-1<br />
<br />
Canadians should probably uncomment ''en_US, en_CA and en_GB''.<br />
<br />
====root password====<br />
Set a root password.<br />
<br />
====pacman mirrors====<br />
You can either use the same mirror you used to install the base packages, or you can choose a different one at this time. The mirror you select at this stage will be your default repository after installation is complete.<br />
<br />
===5 - Install Kernel===<br />
The default choices should be fine.<br />
<br />
===6 - Install Boot Loader===<br />
If you are installing Arch as the sole operating system on the notebook, just go with the default settings. If you are dual-booting with another OS, choose the options carefully to avoid problems with your existing settings.<br />
<br />
* When installing GRUB, you can also append '''vga=791''' to the kernel option to set your terminal (framebuffer) resolution to 1024x768, for example:<br />
kernel /vmlinuz26 root=/dev/sda3 ro '''vga=791'''<br />
<br />
===7 - Exit===<br />
Reboot, eject the CD and log into your new Arch Linux installation.<br />
<br />
==Synchronize Repositories and Update==<br />
When logging into Arch for the first time, it is a good idea to make sure the local package database is synchronized with the Arch software repositories and that all of your software is up to date. From the console, type:<br />
# pacman -Syu<br />
<br />
=Add Users=<br />
At this point you can add a local user account by typing:<br />
# useradd -m johndoe<br />
# passwd johndoe<br />
<br />
''The '''-m''' flag creates the user's /home directory and copies the default configuration files to it (from /etc/skel)''<br />
<br />
Note, you will not be able to use the '''sudo''' command with this account until you [[Sudo|install and configure sudo]].<br />
<br />
=Xorg=<br />
If you plan to install a desktop environment (e.g. GNOME, KDE, etc.) you must install and configure Xorg.<br />
<br />
===Installation===<br />
Install the necessary packages:<br />
# pacman -S xorg xterm hwd<br />
<br />
===Configuration===<br />
The <tt>hwd</tt> program (''Hardware Detect'') will examine your hardware and create a default configuration file for Xorg (''/etc/X11/xorg.conf''):<br />
# hwd -xa<br />
You should now have a working X setup, however the default configuration uses the generic VESA graphics driver. If you want to run your desktop at its native resolution (e.g. 1680x1050) and enable 3D acceleration, you'll need to install the appropriate driver for your video card. See the [[Dell_Inspiron_6400#Video|Video]] section below for detailed instructions.<br />
<br />
=Desktop Environments=<br />
Arch Linux supports a variety of desktop environments and window managers, all of which must be installed manually. Refer to the following list for more information:<br />
<br />
'''Openbox:''' [[Openbox|Openbox Wiki]]<br />
<br />
'''GNOME:''' [[GNOME|GNOME Wiki]]<br />
<br />
'''Xfce:''' [[Xfce|Xfce Wiki]]<br />
<br />
'''KDE:''' [[KDE|KDE Wiki]]<br />
<br />
'''KDEmod:''' Visit the KDEmod website at http://kdemod.ath.cx/ or see the [[KDEmod|KDEmod Wiki]] for more information.<br />
<br />
'''E17:''' [[E17|E17 Wiki]]<br />
<br />
'''Fluxbox:''' [[Fluxbox|Fluxbox Wiki]]<br />
<br />
=Hardware=<br />
<br />
==Audio==<br />
===Sigmatel/Intel Chipset===<br />
The Sigmatel audio chipset should be detected automatically during installation, requiring no input from the user. For example, the following kernel modules are configured in ''/etc/rc.conf'' by default:<br />
snd-mixer-oss snd-pcm-oss snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore<br />
<br />
====ALSA Audio Drivers====<br />
Refer to the [[ALSA]] wiki for general assistance with volume settings, group permissions, etc.<br />
<br />
====OSS Audio Drivers====<br />
See the [[OSS]] wiki for more information.<br />
<br />
==Video==<br />
===ATI X1300/X1400 Radeon Mobility===<br />
====Proprietary Driver (fglrx)====<br />
<br />
The fglrx ATI proprietary driver is available from the standard Arch repositories and is the simplest way to get full 3D acceleration and native resolutions on your notebook:<br />
# pacman -S fglrx<br />
Run the '''aticonfig''' tool to automatically add the appropriate settings to ''/etc/X11/xorg.conf'':<br />
# aticonfig --initial<br />
Lastly, we need to modify ''/etc/rc.conf'' and add the '''fglrx''' kernel driver to the MODULES section, for example:<br />
MODULES=('''fglrx''' b44 mii snd-mixer-oss ...)<br />
Reboot and confirm that the ATI driver is working by typing '''fglrxinfo''' in a terminal. The results should look something like this:<br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Mobility Radeon X1400<br />
OpenGL version string: 2.0.6473 (8.37.6)<br />
<br />
Further information can be found at the [[ATI]] wiki.<br />
<br />
====Open Source ATI Driver====<br />
<br />
Please refer to the [[ATI]] wiki for more information.<br />
<br />
===Intel Graphics Media Accelerator 950===<br />
====Open Source Intel Driver====<br />
<br />
Install the driver:<br />
# pacman -S xf86-video-intel<br />
<br />
Use '''''gft''''' to generate the Xorg ''Modeline'' values and then edit ''/etc/X11/xorg.conf'' and add these values to the ''Monitor'' section, for example:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "unknown"<br />
'''Modeline "800x600" 40.12 800 848 968 1056 600 601 605 628 #60Hz'''<br />
EndSection<br />
<br />
Lastly, add the following to the "Device" section, replacing the existing ''Driver'' value if present:<br />
<br />
VideoRam 229376<br />
Option "CacheLines" "1980"<br />
Driver "intel"<br />
<br />
===nVidia GeForce Go 7300===<br />
The [[NVIDIA|NVIDIA Driver Wiki]] works fine. A side note: When running Beryl/Compiz-Fusion, while opening multiple instances of FireFox, the entire window went black. Forcing AIGLX solved this.<br />
<br />
==Networking==<br />
<br />
===Broadcom 440x 10/100 Ethernet===<br />
The Broadcom Ethernet card should have out-of-the-box support. No configuration necessary.<br />
<br />
===Dell Wireless 1390===<br />
<br />
Dell does not offer native Linux drivers for the 1390 wireless card. Fortunately, '''ndiswrapper''' can be used to install the Windows driver:<br />
# pacman -S ndiswrapper<br />
<br />
Download the 1390 driver from the Dell website:<br />
wget http://ftp.us.dell.com/network/R140747.EXE<br />
<br />
Create a temp folder and extract the driver:<br />
mkdir ~/Dell1390<br />
mv R14070747.EXE ~/Dell1390 <br />
cd ~/Dell1390 <br />
unzip -a R14070747.EXE<br />
cd DRIVERS<br />
<br />
As root, configure ndiswrapper to use the Windows driver:<br />
# ndiswrapper -i bcmwl5.inf<br />
# ndiswrapper -l<br />
# ndiswrapper -m<br />
# modprobe ndiswrapper<br />
<br />
Test the new driver by typing '''iwlist scanning''' in a terminal.<br />
<br />
To load the driver automatically at each boot, add '''ndiswrapper''' to the MODULES array in ''/etc/rc.conf'', for example:<br />
MODULES=(fglrx '''ndiswrapper''' b44 mii ...)<br />
<br />
Finally, remove the temp folder used during installation:<br />
rm -rf ~/Dell1390<br />
<br />
===Dell Wireless 1500 Draft 802.11n Wireless (Intel 4965AGN)===<br />
Grab the driver packages:<br />
# pacman -S iwlwifi iwlwifi-4965-ucode<br />
Edit ''/etc/rc.conf'' as root and add '''iwl4965''' to the MODULES list:<br />
MODULES=(fglrx '''''iwl4965''''' b44 mii ...)<br />
Add '''wlan0="dchp"''' to the NETWORKING section:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''wlan0="dhcp"'''''<br />
If '''wlan0''' is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!wlan0''''')<br />
<br />
===Dell Wireless 350 Bluetooth Module===<br />
Install the bluetooth libraries and basic utilties:<br />
# pacman -S bluez-libs bluez-utils<br />
Add '''bluetooth''' to the DAEMONS list in ''/etc/rc.conf'', for example:<br />
DAEMONS=(syslog-ng powersaved '''bluetooth''' ipw3945d ...)<br />
Now, depending on your desktop environment, install the appropriate tools:<br />
<br />
For GNOME: <br />
# pacman -S gnome-bluetooth bluez-gnome<br />
For KDE:<br />
# pacman -S kdebluetooth<br />
<br />
===Dell Wireless 355 Bluetooth Module===<br />
The steps described above for Dell Wireless 350 Bluetooth Module work with Dell Wireless 355 Bluetooth Module too.<br />
<br />
===Intel PRO/Wireless 3945ABG===<br />
With the release of Intel's open source [http://intellinuxwireless.org/ iwlwifi driver], 3945 owners now have two choices for wireless drivers. As the iwlwifi project matures, the ipw3945 driver will become obsolete, however until that time it will remain below as a second alternative.<br />
<br />
Install and configure NetworkManager before attempting to install the Intel 3945 wireless drivers. Refer to the [[Networkmanager| Networkmanager Wiki]] for more information.<br />
<br />
====Method 1: iwlwifi driver====<br />
Grab the driver packages:<br />
# pacman -S iwlwifi iwlwifi-3945-ucode<br />
Edit ''/etc/rc.conf'' as root and add '''iwl3945''' to the MODULES list:<br />
MODULES=(fglrx '''''iwl3945''''' b44 mii ...)<br />
Add '''wlan0="dchp"''' to the NETWORKING section:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''wlan0="dhcp"'''''<br />
If '''wlan0''' is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!wlan0''''')<br />
<br />
====Method 2: ipw3945 driver====<br />
Grab the Intel 3945 driver packages:<br />
# pacman -S ipw3945<br />
Edit ''/etc/rc.conf'' as root and add '''ipw3945''' to the MODULES list:<br />
MODULES=(fglrx '''''ipw3945''''' b44 mii ...)<br />
Add '''eth1="dchp"''' to the NETWORKING section ''(Note: It is sometimes detected as eth2 instead of eth1, use '''ifconfig''' to verify yours and, if necessary add eth2="dhcp" instead)'':<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''eth1="dhcp"'''''<br />
If '''eth1''' (or '''eth2''') is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!eth1''''')<br />
Add '''ipw3945d''' to the DAEMONS list ''before'' the dhcdbd and networkmanager daemons:<br />
DAEMONS=(syslog-ng '''''ipw3945d''''' dhcdbd networkmanager alsa ...)<br />
<br />
==Conexant HDA D110 MDC V.92 modem (winmodem)==<br />
The Conexant modem requires the proprietary '''hsfmodem''' driver.<br />
Dell offers a debian package [http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R155004&SystemID=INSPIRONI6400/E1505&servicetag=&os=UBLN&osl=en&deviceid=8593&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=1&libid=20&fileid=206745 hsfmodem_7.60.00.06oem_i386.deb] at their [http://support.dell.com/ support site] that works at '''full speed''' unlike the trial version from [http://www.linuxant.com/ Linuxant] which works at 14.4kbps.<br />
<br />
The following '''PKGBUILD''' can be used to create an archlinux '''hsfmodem''' package from the debian package:<br />
pkgname=hsfmodem<br />
pkgver=7.60.00.06oem<br />
pkgrel=1<br />
pkgdesc="Conexant dialup modem driver by dell"<br />
url="http://support.dell.com/"<br />
license=("unknown")<br />
arch=('i686')<br />
source=(${pkgname}_${pkgver}_i386.deb)<br />
md5sums=('80d38fccab347638fa7a2237b458b428')<br />
<br />
build() {<br />
cd $startdir/src/<br />
ar x ${pkgname}_${pkgver}_i386.deb<br />
tar xzf data.tar.gz<br />
cp -a usr etc $startdir/pkg/<br />
}<br />
<br />
#Download and place """hsfmodem_7.60.00.06oem_i386.deb""" and the """PKGBUILD""" in a new folder, and run <code>makepkg</code> to create the package. See [[ABS]] for details on building packages.<br />
#Run <code>hsfconfig</code> as root to build the module and initialise the modem. A reboot is required before the modem can be initialised. Run <code>hsfconfig</code> again after reboot.<br />
#The modules are automatically loaded and a <code>/dev/modem</code> symlink is setup for use with the modem. Now use wvdial or other dialer programs to connect to the internet.<br />
<br />
==Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Card Reader==<br />
The Ricoh card reader should work out of the box, as long as '''MOD_AUTOLOAD''' is set to '''yes''' in ''/etc/rc.conf''. Assuming you use a HAL-aware desktop (GNOME, KDE, etc.), when a memory card is inserted, the kernel should automatically load the '''mmc_core/mmc_block''' modules and mount the new filesystem according to your desktop's automount settings. <br />
<br />
This has been confirmed with the following card types:<br />
* SD Card<br />
<br />
==Synaptics Touchpad==<br />
The Synaptics touchpad should provide basic functions out-of-the-box, however if you would like to use the scroll zones and enable other advanced features, please refer to the [[Touchpad_Synaptics | Synaptics Touchpad]] wiki.<br />
<br />
=Power Management=<br />
<br />
==ACPI Hibernation/Suspend with pm-utils==<br />
The powersave scripts have been officially replaced by [http://www.archlinux.org/packages/search/?q=pm-utils pm-utils]. Refer to the [[Pm-utils]] wiki for detailed instructions.<br />
<br />
'''''Note:''''' ATI video card owners must also add '''vga=0''' to the kernel options in <tt>/boot/grub/menu.lst</tt> in order to resume from suspend2ram. For exmaple:<br />
<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda3 resume=/dev/sda2 ro '''''vga=0'''''<br />
initrd /kernel26.img<br />
<br />
==CPU Frequency Scaling with cpufrequtils==<br />
<br />
Refer to the [[Cpufrequtils]] wiki for step-by-step instructions.<br />
<br />
= Multimedia Buttons & Fn Hotkeys =<br />
Unfortunately, configuring multimedia buttons and function keys on your laptop can be complicated process. Factors that must be taken into consideration include your choice of Desktop Environment (or lack thereof) and the actions you wish to bind to the special buttons or keys. For a detailed explanation of what is required, please refer to the [[Hotkeys]] wiki.<br />
<br />
The following tips may offer some assistance in getting started.<br />
<br />
== Multimedia Buttons ==<br />
For the most part, the Volume and Playback buttons should be recognized as an unassigned key by the Linux kernel. In which case, all that is necessary is to bind the button to an action. <br />
<br />
It is also worth noting that the multimedia buttons and equivalent Fn key shortcut (e.g. Fn+PgUp = Vol Up) will produce the same keycode, so if you configure the button, the Fn hotkey combo will execute the same action.<br />
<br />
=== GNOME ===<br />
The GNOME desktop provides an easy method for binding multimedia keys to their appropriate action. <br />
<br />
# Browse to '''System -> Preferences -> Keyboard Shortcuts''' and scroll down to the '''Sound''' section.<br />
# Click on an item (e.g. Mute) and then press the corresponding multimedia button<br />
# Repeat this process for all of the multimedia buttons<br />
<br />
The volume buttons should now work system-wide, and the playback buttons will now work in media players such as Rhythmbox and Exaile.<br />
<br />
=== Openbox and other Window Managers ===<br />
The <tt>xbindkeys</tt> utility is highly recommended for lightweight desktops such as Openbox--refer to the [[Hotkeys]] wiki for information. <br />
<br />
The following is an example ''~/.xbindkeysrc'' config file, making use of the multimedia buttons:<br />
<pre><br />
# vol up<br />
"amixer set Master 2dB+ unmute"<br />
m:0x10 + c:176<br />
# vol dn<br />
"amixer set Master 2dB- unmute"<br />
m:0x10 + c:174<br />
# vol mute<br />
"amixer set Master mute"<br />
m:0x10 + c:160<br />
# play/pause<br />
"audacious -t"<br />
m:0x10 + c:162<br />
# back<br />
"audacious -r"<br />
m:0x10 + c:144<br />
# forward<br />
"audacious -f"<br />
m:0x10 + c:153<br />
# stop<br />
"audacious -s"<br />
m:0x10 + c:164<br />
</pre><br />
<br />
== Function (Fn) Hotkeys ==<br />
Function keys seem to be less standardized than the Volume/Playback buttons, and therefore it can be difficult to get all of them working properly. For example, the Standby shortcut (Fn+ESC) may be recognized while at the same time the Hibernate shortcut (Fn+F1) is not. To make matters more confusing, it appears that some Fn keys such as those that adjust the LCD brightness are controlled by the BIOS, independent of the Operating System. Again, the [[Hotkeys]] wiki is highly recommended reading.<br />
<br />
The following example shows how one can configure the Dell Media Direct button, Eject (Fn+F10) and Hibernate (Fn+F1) hotkeys to execute specific commands:<br />
<br />
First, assign kernel keycodes to the Media Direct button and Fn hotkeys, using the ''/etc/rc.local'' script (which is executed before X loads):<br />
#!/bin/bash<br />
#<br />
# /etc/rc.local: Local multi-user startup script.<br />
#<br />
setkeycodes e009 122 # e009 eject fn<br />
setkeycodes e012 130 # e012 mediadirect<br />
setkeycodes e00a 123 # e00a hibernate fn<br />
<br />
Then use the <tt>xbindkeys</tt> utility to bind the newly recognized keys to a custom action. Here's an ''~/.xbindkeysrc'' config file:<br />
<br />
# media direct button<br />
"streamtuner"<br />
m:0x10 + c:134<br />
# eject function hotkey<br />
"eject"<br />
m:0x10 + c:210 <br />
# hibernate function hotkey<br />
"sudo /usr/sbin/pm-hibernate"<br />
m:0x10 + c:209<br />
<br />
Finally, execute <tt>xbindkeys</tt> at startup by placing it in your .xinitrc (or appropriate startup file for your environment):<br />
xscreensaver -no-splash &<br />
eval `cat $HOME/.fehbg` &<br />
'''''xbindkeys &'''''<br />
#sleep 3<br />
pypanel &<br />
exec openbox<br />
<br />
As stated previously, it can be a complicated process involving lots of trial & error troubleshooting, but hopefully this will help you get started.<br />
<br />
=Resources=<br />
TuxMobil: [http://tuxmobil.org/mylaptops.html Linux Laptop & Notebook Installation Guides]<br />
<br />
TuxMobil: [http://tuxmobil.org/dell.html DELL Notebooks]<br />
<br />
Gentoo Wiki: [http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_6400 HARDWARE Dell Inspiron 6400]<br />
<br />
Gentoo Wiki: [http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_6400_Fixes_for_common_problems HARDWARE Dell Inspiron 6400 Fixes for common problems]<br />
<br />
<br />
<br />
=Comments=</div>Shastryhttps://wiki.archlinux.org/index.php?title=Dell_Inspiron_6400&diff=29669Dell Inspiron 64002007-09-21T20:56:18Z<p>Shastry: /* Conexant HDA D110 MDC V.92 modem (winmodem) */</p>
<hr />
<div>[[Category:Laptops (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
=Introduction=<br />
==Summary==<br />
The goal of this wiki is to provide a comprehensive guide for Dell Inspiron 6400 owners seeking to install Arch Linux. It will attempt to cover all facets of hardware management, including wireless networking and hotkey support. Although this guide has been written specifically for the Inspiron 6400, many of the sub-sections can be applied to other Dell Inspiron models, including: <br />
* Dell Inspiron e1405<br />
* Dell Inspiron 640m<br />
* Dell Inspiron e1705<br />
<br />
==From the original contributor==<br />
I will attempt to cover as much as possible, however please feel free to contribute to this guide as you feel necessary. I will be happy to answer any questions, but I am by no means a Linux expert so there's a good chance I won't know the answer either! ~Thayer ([[User:Thayer.w|thayer.w]]) (thayerw(at)gmail(dot)com)<br />
<br />
=Hardware Specifications=<br />
The 6400 series laptop is currently available in a number of configurations and this guide will attempt to cover them all. Refer to the list below to determine whether your configuration has been documented.<br />
<br />
*<span style="color:green;">Green items are confirmed to work</span><br />
*<span style="color:red;">Red items have yet to be confirmed and require a Wiki entry</span><br />
<br />
===Base Components===<br />
<br />
* Intel Core Duo and Core 2 Duo processors<br />
** T2500 (2GHz/667MHz FSB/2MB Cache)<br />
** T5600 (1.83GHz/667MHz FSB/2MB Cache)<br />
** T2050 (1.66GHz/667MHz FSB/2MB Cache)<br />
** T1350 (1.66GHz/667MHz FSB/2MB Cache)<br />
** T5200 (1.60GHz/667MHz FSB/2MB Cache)<br />
* 512MB/1GB/2GB 533MHz/667MHz DDR2 SDRAM Memory<br />
* 15.4" Widescreen Display<br />
** WXGA (1280 x 800)<br />
** <span style="color:green;">WSXGA 1280x800 with TrueLife™</span><br />
** <span style="color:green;">WSXGA+ 1680x1050 with TrueLife™</span><br />
* 80GB/100GB/120GB/160GB 5400/7200 RPM SATA Hard Drive<br />
* <span style="color:green;">8x CD/DVD+/-RW/DL+R</span><br />
* <span style="color:green;">Broadcom 440x 10/100 Ethernet</span><br />
* <span style="color:green;">Conexant HDA D110 MDC V.92 modem (winmodem)</span><br />
* <span style="color:green;">Sigmatel STAC 92xx Audio</span><br />
* <span style="color:green;">Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Card Reader</span><br />
* <span style="color:green;">4 USB 2.0 Ports</span><br />
* <span style="color:red;">Firewire port (IEEE 1394)</span><br />
* <span style="color:red;">1 ExpressCard Slot</span><br />
* <span style="color:green;">Synaptics touchpad with scroll zones</span><br />
<br />
===Video Options===<br />
<br />
* <span style="color:green;">128MB ATI Mobility Radeon X1300 with HyperMemory</span><br />
* <span style="color:green;">256MB ATI Mobility Radeon X1400 with Hypermemory</span><br />
* <span style="color:green;">256MB nVidia GeForce Go 7300 with TurboCache</span><br />
* <span style="color:green;">128MB Intel Graphics Media Accelerator 950</span><br />
<br />
===Wireless Options===<br />
<br />
* <span style="color:green;">Intel Pro/Wireless 3945ABG (802.11a/b/g)</span><br />
* <span style="color:green;">Dell Wireless 1390</span><br />
* <span style="color:green;">Dell Wireless 1500 Draft 802.11n Wireless (Intel 4965AGN)</span><br />
* <span style="color:green;">Dell Wireless 350 Bluetooth Module</span><br />
* <span style="color:green;">Dell Wireless 355 Bluetooth Module</span><br />
<br />
=Arch Installation=<br />
There are plenty of resources available to help new users install and configure a basic Arch Linux installation, including the [[Official_Arch_Linux_Install_Guide|Official Installation Guide]] and the [[Beginners_Guide|Beginners Guide]].<br />
<br />
That being said, the following tips are specific to the Dell Inspiron 6400 and may be of some help during installation.<br />
<br />
If an Ethernet (wired land-line) broadband internet connection is available it is highly recommended that Arch be installed with the smaller FTP ISO. If you plan to have a desktop environment (KDE, GNOME, etc) then the majority of the packages you require will come from the internet repositories and <em>not</em> the Arch CD itself. This method will get you up and running in the shortest amount of time. Simply download the FTP ISO, burn it to a CD and restart your computer.<br />
<br />
The following steps assume you are connected to the Internet with a wired Ethernet connection, as opposed to a wireless connection.<br />
<br />
==Boot the Arch Setup CD==<br />
If the laptop does not boot from the CD, reboot and press F12 at the DELL BIOS splash screen to access the boot menu. From there you can choose to boot from the CD/DVD drive.<br />
<br />
==Setup==<br />
For the most part, the default settings should be fine, however the following notes may be of assistance.<br />
<br />
===0 - Configure===<br />
Just follow the prompts, choosing the defaults when asked. Make sure you allow the setup to detect your basic hardware automatically when asked.<br />
<br />
===1 - Prepare Hard Disks===<br />
The following is an example partition table. The example hard drive is 100GB and is configured to run only Arch Linux. Your settings will vary depending on the size of your hard drive and the number of operating systems you plan to run.<br />
<br />
'''sda''' (100GB)<br />
'''sda1''' ext2 100MB /boot ''(the boot loader files and kernel images will be installed here)''<br />
'''sda2''' swap 2.1GB swap ''(this example notebook has 2GB of RAM and we want to leave room for suspend2disk (hibernation) functions)''<br />
'''sda3''' ext3 6GB / ''(root--everything else will go here except for the files in /home and /boot)''<br />
'''sda4''' ext3 90GB /home ''(it's actually less than 90GB because ext3 filesystems reserve space to avoid capacity problems, but you get the point)''<br />
<br />
===2 - Select Packages===<br />
*Choose a mirror ('''''ftp.nethat.com''''' works very well from Vancouver, BC @ 160kb/s)<br />
*Choose ''only'' the base packages<br />
*Select ''all'' packages by default<br />
<br />
===3 - Install Packages===<br />
*Answer ''yes'' to cache packages (default)<br />
*Grab a coffee, it's going to take a while to fetch 100MB of packages<br />
<br />
===4 - Configure System===<br />
Choose your preferred editor; either vim or nano. <br />
<br />
A few files can be left alone, but there are some changes worth mentioning:<br />
<br />
====rc.conf====<br />
*Change your locale if necessary, for example Canadians will want to use ''en_CA'':<br />
LOCALE="en_CA.utf8"<br />
*Change the timezone if necessary, for example:<br />
TIMEZONE="Canada/Pacific"<br />
*To get rid of that ever-so-annoying system beep, blacklist the PC speaker module:<br />
MOD_BLACKLIST=(pcspkr)<br />
*Change the hostname if you desire a unique name, for example:<br />
HOSTNAME="dublin"<br />
*If your Internet Service Provider assigns your IP address automatically (and most do), make sure ''eth0'' is set to ''dhcp'':<br />
lo="lo 127.0.0.1"<br />
'''eth0="dhcp"'''<br />
<br />
====hosts====<br />
Add a second line under localhost with your unique hostname (the same hostname you chose in rc.conf) in place of localhost, for example:<br />
127.0.0.1 localhost.localdomain localhost<br />
'''127.0.0.1 dublin.localdomain dublin'''<br />
<br />
====fstab====<br />
No changes should be necessary.<br />
<br />
====mkinitcpio.conf====<br />
No changes should be necessary.<br />
<br />
====modprobe.conf====<br />
No changes should be necessary.<br />
<br />
====resolv.conf====<br />
No changes should be necessary.<br />
<br />
====locale.gen====<br />
Uncomment the languages files you wish to use, including the one you configured under LOCALE in the rc.conf:<br />
#en_BW.UTF-8 UTF-8<br />
#en_BW ISO-8859-1<br />
'''en_CA.UTF-8 UTF-8'''<br />
'''en_CA ISO-8859-1'''<br />
#en_DK.UTF-8 UTF-8<br />
#en_DK ISO-8859-1<br />
<br />
Canadians should probably uncomment ''en_US, en_CA and en_GB''.<br />
<br />
====root password====<br />
Set a root password.<br />
<br />
====pacman mirrors====<br />
You can either use the same mirror you used to install the base packages, or you can choose a different one at this time. The mirror you select at this stage will be your default repository after installation is complete.<br />
<br />
===5 - Install Kernel===<br />
The default choices should be fine.<br />
<br />
===6 - Install Boot Loader===<br />
If you are installing Arch as the sole operating system on the notebook, just go with the default settings. If you are dual-booting with another OS, choose the options carefully to avoid problems with your existing settings.<br />
<br />
* When installing GRUB, you can also append '''vga=791''' to the kernel option to set your terminal (framebuffer) resolution to 1024x768, for example:<br />
kernel /vmlinuz26 root=/dev/sda3 ro '''vga=791'''<br />
<br />
===7 - Exit===<br />
Reboot, eject the CD and log into your new Arch Linux installation.<br />
<br />
==Synchronize Repositories and Update==<br />
When logging into Arch for the first time, it is a good idea to make sure the local package database is synchronized with the Arch software repositories and that all of your software is up to date. From the console, type:<br />
# pacman -Syu<br />
<br />
=Add Users=<br />
At this point you can add a local user account by typing:<br />
# useradd -m johndoe<br />
# passwd johndoe<br />
<br />
''The '''-m''' flag creates the user's /home directory and copies the default configuration files to it (from /etc/skel)''<br />
<br />
Note, you will not be able to use the '''sudo''' command with this account until you [[Sudo|install and configure sudo]].<br />
<br />
=Xorg=<br />
If you plan to install a desktop environment (e.g. GNOME, KDE, etc.) you must install and configure Xorg.<br />
<br />
===Installation===<br />
Install the necessary packages:<br />
# pacman -S xorg xterm hwd<br />
<br />
===Configuration===<br />
The <tt>hwd</tt> program (''Hardware Detect'') will examine your hardware and create a default configuration file for Xorg (''/etc/X11/xorg.conf''):<br />
# hwd -xa<br />
You should now have a working X setup, however the default configuration uses the generic VESA graphics driver. If you want to run your desktop at its native resolution (e.g. 1680x1050) and enable 3D acceleration, you'll need to install the appropriate driver for your video card. See the [[Dell_Inspiron_6400#Video|Video]] section below for detailed instructions.<br />
<br />
=Desktop Environments=<br />
Arch Linux supports a variety of desktop environments and window managers, all of which must be installed manually. Refer to the following list for more information:<br />
<br />
'''Openbox:''' [[Openbox|Openbox Wiki]]<br />
<br />
'''GNOME:''' [[GNOME|GNOME Wiki]]<br />
<br />
'''Xfce:''' [[Xfce|Xfce Wiki]]<br />
<br />
'''KDE:''' [[KDE|KDE Wiki]]<br />
<br />
'''KDEmod:''' Visit the KDEmod website at http://kdemod.ath.cx/ or see the [[KDEmod|KDEmod Wiki]] for more information.<br />
<br />
'''E17:''' [[E17|E17 Wiki]]<br />
<br />
'''Fluxbox:''' [[Fluxbox|Fluxbox Wiki]]<br />
<br />
=Hardware=<br />
<br />
==Audio==<br />
===Sigmatel/Intel Chipset===<br />
The Sigmatel audio chipset should be detected automatically during installation, requiring no input from the user. For example, the following kernel modules are configured in ''/etc/rc.conf'' by default:<br />
snd-mixer-oss snd-pcm-oss snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore<br />
<br />
====ALSA Audio Drivers====<br />
Refer to the [[ALSA]] wiki for general assistance with volume settings, group permissions, etc.<br />
<br />
====OSS Audio Drivers====<br />
See the [[OSS]] wiki for more information.<br />
<br />
==Video==<br />
===ATI X1300/X1400 Radeon Mobility===<br />
====Proprietary Driver (fglrx)====<br />
<br />
The fglrx ATI proprietary driver is available from the standard Arch repositories and is the simplest way to get full 3D acceleration and native resolutions on your notebook:<br />
# pacman -S fglrx<br />
Run the '''aticonfig''' tool to automatically add the appropriate settings to ''/etc/X11/xorg.conf'':<br />
# aticonfig --initial<br />
Lastly, we need to modify ''/etc/rc.conf'' and add the '''fglrx''' kernel driver to the MODULES section, for example:<br />
MODULES=('''fglrx''' b44 mii snd-mixer-oss ...)<br />
Reboot and confirm that the ATI driver is working by typing '''fglrxinfo''' in a terminal. The results should look something like this:<br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Mobility Radeon X1400<br />
OpenGL version string: 2.0.6473 (8.37.6)<br />
<br />
Further information can be found at the [[ATI]] wiki.<br />
<br />
====Open Source ATI Driver====<br />
<br />
Please refer to the [[ATI]] wiki for more information.<br />
<br />
===Intel Graphics Media Accelerator 950===<br />
====Open Source Intel Driver====<br />
<br />
Install the driver:<br />
# pacman -S xf86-video-intel<br />
<br />
Use '''''gft''''' to generate the Xorg ''Modeline'' values and then edit ''/etc/X11/xorg.conf'' and add these values to the ''Monitor'' section, for example:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "unknown"<br />
'''Modeline "800x600" 40.12 800 848 968 1056 600 601 605 628 #60Hz'''<br />
EndSection<br />
<br />
Lastly, add the following to the "Device" section, replacing the existing ''Driver'' value if present:<br />
<br />
VideoRam 229376<br />
Option "CacheLines" "1980"<br />
Driver "intel"<br />
<br />
===nVidia GeForce Go 7300===<br />
The [[NVIDIA|NVIDIA Driver Wiki]] works fine. A side note: When running Beryl/Compiz-Fusion, while opening multiple instances of FireFox, the entire window went black. Forcing AIGLX solved this.<br />
<br />
==Networking==<br />
<br />
===Broadcom 440x 10/100 Ethernet===<br />
The Broadcom Ethernet card should have out-of-the-box support. No configuration necessary.<br />
<br />
===Dell Wireless 1390===<br />
<br />
Dell does not offer native Linux drivers for the 1390 wireless card. Fortunately, '''ndiswrapper''' can be used to install the Windows driver:<br />
# pacman -S ndiswrapper<br />
<br />
Download the 1390 driver from the Dell website:<br />
wget http://ftp.us.dell.com/network/R140747.EXE<br />
<br />
Create a temp folder and extract the driver:<br />
mkdir ~/Dell1390<br />
mv R14070747.EXE ~/Dell1390 <br />
cd ~/Dell1390 <br />
unzip -a R14070747.EXE<br />
cd DRIVERS<br />
<br />
As root, configure ndiswrapper to use the Windows driver:<br />
# ndiswrapper -i bcmwl5.inf<br />
# ndiswrapper -l<br />
# ndiswrapper -m<br />
# modprobe ndiswrapper<br />
<br />
Test the new driver by typing '''iwlist scanning''' in a terminal.<br />
<br />
To load the driver automatically at each boot, add '''ndiswrapper''' to the MODULES array in ''/etc/rc.conf'', for example:<br />
MODULES=(fglrx '''ndiswrapper''' b44 mii ...)<br />
<br />
Finally, remove the temp folder used during installation:<br />
rm -rf ~/Dell1390<br />
<br />
===Dell Wireless 1500 Draft 802.11n Wireless (Intel 4965AGN)===<br />
Grab the driver packages:<br />
# pacman -S iwlwifi iwlwifi-4965-ucode<br />
Edit ''/etc/rc.conf'' as root and add '''iwl4965''' to the MODULES list:<br />
MODULES=(fglrx '''''iwl4965''''' b44 mii ...)<br />
Add '''wlan0="dchp"''' to the NETWORKING section:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''wlan0="dhcp"'''''<br />
If '''wlan0''' is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!wlan0''''')<br />
<br />
===Dell Wireless 350 Bluetooth Module===<br />
Install the bluetooth libraries and basic utilties:<br />
# pacman -S bluez-libs bluez-utils<br />
Add '''bluetooth''' to the DAEMONS list in ''/etc/rc.conf'', for example:<br />
DAEMONS=(syslog-ng powersaved '''bluetooth''' ipw3945d ...)<br />
Now, depending on your desktop environment, install the appropriate tools:<br />
<br />
For GNOME: <br />
# pacman -S gnome-bluetooth bluez-gnome<br />
For KDE:<br />
# pacman -S kdebluetooth<br />
<br />
===Dell Wireless 355 Bluetooth Module===<br />
The steps described above for Dell Wireless 350 Bluetooth Module work with Dell Wireless 355 Bluetooth Module too.<br />
<br />
===Intel PRO/Wireless 3945ABG===<br />
With the release of Intel's open source [http://intellinuxwireless.org/ iwlwifi driver], 3945 owners now have two choices for wireless drivers. As the iwlwifi project matures, the ipw3945 driver will become obsolete, however until that time it will remain below as a second alternative.<br />
<br />
Install and configure NetworkManager before attempting to install the Intel 3945 wireless drivers. Refer to the [[Networkmanager| Networkmanager Wiki]] for more information.<br />
<br />
====Method 1: iwlwifi driver====<br />
Grab the driver packages:<br />
# pacman -S iwlwifi iwlwifi-3945-ucode<br />
Edit ''/etc/rc.conf'' as root and add '''iwl3945''' to the MODULES list:<br />
MODULES=(fglrx '''''iwl3945''''' b44 mii ...)<br />
Add '''wlan0="dchp"''' to the NETWORKING section:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''wlan0="dhcp"'''''<br />
If '''wlan0''' is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!wlan0''''')<br />
<br />
====Method 2: ipw3945 driver====<br />
Grab the Intel 3945 driver packages:<br />
# pacman -S ipw3945<br />
Edit ''/etc/rc.conf'' as root and add '''ipw3945''' to the MODULES list:<br />
MODULES=(fglrx '''''ipw3945''''' b44 mii ...)<br />
Add '''eth1="dchp"''' to the NETWORKING section ''(Note: It is sometimes detected as eth2 instead of eth1, use '''ifconfig''' to verify yours and, if necessary add eth2="dhcp" instead)'':<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''eth1="dhcp"'''''<br />
If '''eth1''' (or '''eth2''') is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!eth1''''')<br />
Add '''ipw3945d''' to the DAEMONS list ''before'' the dhcdbd and networkmanager daemons:<br />
DAEMONS=(syslog-ng '''''ipw3945d''''' dhcdbd networkmanager alsa ...)<br />
<br />
==Conexant HDA D110 MDC V.92 modem (winmodem)==<br />
The Conexant modem requires the proprietary '''hsfmodem''' driver.<br />
Dell offers a debian package [http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R155004&SystemID=INSPIRONI6400/E1505&servicetag=&os=UBLN&osl=en&deviceid=8593&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=1&libid=20&fileid=206745 hsfmodem_7.60.00.06oem_i386.deb] at their [http://support.dell.com/ support site] that works at '''full speed''' unlike the trial version from [http://www.linuxant.com/ Linuxant] which works at 14.4kbps.<br />
<br />
The following '''PKGBUILD''' can be used to create an archlinux '''hsfmodem''' package from the debian package:<br />
pkgname=hsfmodem<br />
pkgver=7.60.00.06oem<br />
pkgrel=1<br />
pkgdesc="Conexant dialup modem driver by dell"<br />
url="http://support.dell.com/"<br />
license=("unknown")<br />
arch=('i686')<br />
source=(${pkgname}_${pkgver}_i386.deb)<br />
md5sums=('80d38fccab347638fa7a2237b458b428')<br />
<br />
build() {<br />
cd $startdir/src/<br />
ar x ${pkgname}_${pkgver}_i386.deb<br />
tar xzf data.tar.gz<br />
cp -a usr etc $startdir/pkg/<br />
}<br />
<br />
#Download and place <code>hsfmodem_7.60.00.06oem_i386.deb</code> and the <code>PKGBUILD</code> in a new folder, and run makepkg to create the package. See [[ABS]] for details on building packages.<br />
#Run <code>hsfconfig</code> as root to build the module and initialise the modem. A reboot is required before the modem can be initialised. Run <code>hsfconfig</code> again after reboot.<br />
#The modules are automatically loaded and a <code>/dev/modem</code> symlink is setup for use with the modem. Now use <code>wvdial</code> or other dialer programs to connect to the internet.<br />
<br />
==Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Card Reader==<br />
The Ricoh card reader should work out of the box, as long as '''MOD_AUTOLOAD''' is set to '''yes''' in ''/etc/rc.conf''. Assuming you use a HAL-aware desktop (GNOME, KDE, etc.), when a memory card is inserted, the kernel should automatically load the '''mmc_core/mmc_block''' modules and mount the new filesystem according to your desktop's automount settings. <br />
<br />
This has been confirmed with the following card types:<br />
* SD Card<br />
<br />
==Synaptics Touchpad==<br />
The Synaptics touchpad should provide basic functions out-of-the-box, however if you would like to use the scroll zones and enable other advanced features, please refer to the [[Touchpad_Synaptics | Synaptics Touchpad]] wiki.<br />
<br />
=Power Management=<br />
<br />
==ACPI Hibernation/Suspend with pm-utils==<br />
The powersave scripts have been officially replaced by [http://www.archlinux.org/packages/search/?q=pm-utils pm-utils]. Refer to the [[Pm-utils]] wiki for detailed instructions.<br />
<br />
'''''Note:''''' ATI video card owners must also add '''vga=0''' to the kernel options in <tt>/boot/grub/menu.lst</tt> in order to resume from suspend2ram. For exmaple:<br />
<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda3 resume=/dev/sda2 ro '''''vga=0'''''<br />
initrd /kernel26.img<br />
<br />
==CPU Frequency Scaling with cpufrequtils==<br />
<br />
Refer to the [[Cpufrequtils]] wiki for step-by-step instructions.<br />
<br />
= Multimedia Buttons & Fn Hotkeys =<br />
Unfortunately, configuring multimedia buttons and function keys on your laptop can be complicated process. Factors that must be taken into consideration include your choice of Desktop Environment (or lack thereof) and the actions you wish to bind to the special buttons or keys. For a detailed explanation of what is required, please refer to the [[Hotkeys]] wiki.<br />
<br />
The following tips may offer some assistance in getting started.<br />
<br />
== Multimedia Buttons ==<br />
For the most part, the Volume and Playback buttons should be recognized as an unassigned key by the Linux kernel. In which case, all that is necessary is to bind the button to an action. <br />
<br />
It is also worth noting that the multimedia buttons and equivalent Fn key shortcut (e.g. Fn+PgUp = Vol Up) will produce the same keycode, so if you configure the button, the Fn hotkey combo will execute the same action.<br />
<br />
=== GNOME ===<br />
The GNOME desktop provides an easy method for binding multimedia keys to their appropriate action. <br />
<br />
# Browse to '''System -> Preferences -> Keyboard Shortcuts''' and scroll down to the '''Sound''' section.<br />
# Click on an item (e.g. Mute) and then press the corresponding multimedia button<br />
# Repeat this process for all of the multimedia buttons<br />
<br />
The volume buttons should now work system-wide, and the playback buttons will now work in media players such as Rhythmbox and Exaile.<br />
<br />
=== Openbox and other Window Managers ===<br />
The <tt>xbindkeys</tt> utility is highly recommended for lightweight desktops such as Openbox--refer to the [[Hotkeys]] wiki for information. <br />
<br />
The following is an example ''~/.xbindkeysrc'' config file, making use of the multimedia buttons:<br />
<pre><br />
# vol up<br />
"amixer set Master 2dB+ unmute"<br />
m:0x10 + c:176<br />
# vol dn<br />
"amixer set Master 2dB- unmute"<br />
m:0x10 + c:174<br />
# vol mute<br />
"amixer set Master mute"<br />
m:0x10 + c:160<br />
# play/pause<br />
"audacious -t"<br />
m:0x10 + c:162<br />
# back<br />
"audacious -r"<br />
m:0x10 + c:144<br />
# forward<br />
"audacious -f"<br />
m:0x10 + c:153<br />
# stop<br />
"audacious -s"<br />
m:0x10 + c:164<br />
</pre><br />
<br />
== Function (Fn) Hotkeys ==<br />
Function keys seem to be less standardized than the Volume/Playback buttons, and therefore it can be difficult to get all of them working properly. For example, the Standby shortcut (Fn+ESC) may be recognized while at the same time the Hibernate shortcut (Fn+F1) is not. To make matters more confusing, it appears that some Fn keys such as those that adjust the LCD brightness are controlled by the BIOS, independent of the Operating System. Again, the [[Hotkeys]] wiki is highly recommended reading.<br />
<br />
The following example shows how one can configure the Dell Media Direct button, Eject (Fn+F10) and Hibernate (Fn+F1) hotkeys to execute specific commands:<br />
<br />
First, assign kernel keycodes to the Media Direct button and Fn hotkeys, using the ''/etc/rc.local'' script (which is executed before X loads):<br />
#!/bin/bash<br />
#<br />
# /etc/rc.local: Local multi-user startup script.<br />
#<br />
setkeycodes e009 122 # e009 eject fn<br />
setkeycodes e012 130 # e012 mediadirect<br />
setkeycodes e00a 123 # e00a hibernate fn<br />
<br />
Then use the <tt>xbindkeys</tt> utility to bind the newly recognized keys to a custom action. Here's an ''~/.xbindkeysrc'' config file:<br />
<br />
# media direct button<br />
"streamtuner"<br />
m:0x10 + c:134<br />
# eject function hotkey<br />
"eject"<br />
m:0x10 + c:210 <br />
# hibernate function hotkey<br />
"sudo /usr/sbin/pm-hibernate"<br />
m:0x10 + c:209<br />
<br />
Finally, execute <tt>xbindkeys</tt> at startup by placing it in your .xinitrc (or appropriate startup file for your environment):<br />
xscreensaver -no-splash &<br />
eval `cat $HOME/.fehbg` &<br />
'''''xbindkeys &'''''<br />
#sleep 3<br />
pypanel &<br />
exec openbox<br />
<br />
As stated previously, it can be a complicated process involving lots of trial & error troubleshooting, but hopefully this will help you get started.<br />
<br />
=Resources=<br />
TuxMobil: [http://tuxmobil.org/mylaptops.html Linux Laptop & Notebook Installation Guides]<br />
<br />
TuxMobil: [http://tuxmobil.org/dell.html DELL Notebooks]<br />
<br />
Gentoo Wiki: [http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_6400 HARDWARE Dell Inspiron 6400]<br />
<br />
Gentoo Wiki: [http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_6400_Fixes_for_common_problems HARDWARE Dell Inspiron 6400 Fixes for common problems]<br />
<br />
<br />
<br />
=Comments=</div>Shastryhttps://wiki.archlinux.org/index.php?title=Dell_Inspiron_6400&diff=29667Dell Inspiron 64002007-09-21T20:52:38Z<p>Shastry: /* Conexant HDA D110 MDC V.92 modem (winmodem) */</p>
<hr />
<div>[[Category:Laptops (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
=Introduction=<br />
==Summary==<br />
The goal of this wiki is to provide a comprehensive guide for Dell Inspiron 6400 owners seeking to install Arch Linux. It will attempt to cover all facets of hardware management, including wireless networking and hotkey support. Although this guide has been written specifically for the Inspiron 6400, many of the sub-sections can be applied to other Dell Inspiron models, including: <br />
* Dell Inspiron e1405<br />
* Dell Inspiron 640m<br />
* Dell Inspiron e1705<br />
<br />
==From the original contributor==<br />
I will attempt to cover as much as possible, however please feel free to contribute to this guide as you feel necessary. I will be happy to answer any questions, but I am by no means a Linux expert so there's a good chance I won't know the answer either! ~Thayer ([[User:Thayer.w|thayer.w]]) (thayerw(at)gmail(dot)com)<br />
<br />
=Hardware Specifications=<br />
The 6400 series laptop is currently available in a number of configurations and this guide will attempt to cover them all. Refer to the list below to determine whether your configuration has been documented.<br />
<br />
*<span style="color:green;">Green items are confirmed to work</span><br />
*<span style="color:red;">Red items have yet to be confirmed and require a Wiki entry</span><br />
<br />
===Base Components===<br />
<br />
* Intel Core Duo and Core 2 Duo processors<br />
** T2500 (2GHz/667MHz FSB/2MB Cache)<br />
** T5600 (1.83GHz/667MHz FSB/2MB Cache)<br />
** T2050 (1.66GHz/667MHz FSB/2MB Cache)<br />
** T1350 (1.66GHz/667MHz FSB/2MB Cache)<br />
** T5200 (1.60GHz/667MHz FSB/2MB Cache)<br />
* 512MB/1GB/2GB 533MHz/667MHz DDR2 SDRAM Memory<br />
* 15.4" Widescreen Display<br />
** WXGA (1280 x 800)<br />
** <span style="color:green;">WSXGA 1280x800 with TrueLife™</span><br />
** <span style="color:green;">WSXGA+ 1680x1050 with TrueLife™</span><br />
* 80GB/100GB/120GB/160GB 5400/7200 RPM SATA Hard Drive<br />
* <span style="color:green;">8x CD/DVD+/-RW/DL+R</span><br />
* <span style="color:green;">Broadcom 440x 10/100 Ethernet</span><br />
* <span style="color:green;">Conexant HDA D110 MDC V.92 modem (winmodem)</span><br />
* <span style="color:green;">Sigmatel STAC 92xx Audio</span><br />
* <span style="color:green;">Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Card Reader</span><br />
* <span style="color:green;">4 USB 2.0 Ports</span><br />
* <span style="color:red;">Firewire port (IEEE 1394)</span><br />
* <span style="color:red;">1 ExpressCard Slot</span><br />
* <span style="color:green;">Synaptics touchpad with scroll zones</span><br />
<br />
===Video Options===<br />
<br />
* <span style="color:green;">128MB ATI Mobility Radeon X1300 with HyperMemory</span><br />
* <span style="color:green;">256MB ATI Mobility Radeon X1400 with Hypermemory</span><br />
* <span style="color:green;">256MB nVidia GeForce Go 7300 with TurboCache</span><br />
* <span style="color:green;">128MB Intel Graphics Media Accelerator 950</span><br />
<br />
===Wireless Options===<br />
<br />
* <span style="color:green;">Intel Pro/Wireless 3945ABG (802.11a/b/g)</span><br />
* <span style="color:green;">Dell Wireless 1390</span><br />
* <span style="color:green;">Dell Wireless 1500 Draft 802.11n Wireless (Intel 4965AGN)</span><br />
* <span style="color:green;">Dell Wireless 350 Bluetooth Module</span><br />
* <span style="color:green;">Dell Wireless 355 Bluetooth Module</span><br />
<br />
=Arch Installation=<br />
There are plenty of resources available to help new users install and configure a basic Arch Linux installation, including the [[Official_Arch_Linux_Install_Guide|Official Installation Guide]] and the [[Beginners_Guide|Beginners Guide]].<br />
<br />
That being said, the following tips are specific to the Dell Inspiron 6400 and may be of some help during installation.<br />
<br />
If an Ethernet (wired land-line) broadband internet connection is available it is highly recommended that Arch be installed with the smaller FTP ISO. If you plan to have a desktop environment (KDE, GNOME, etc) then the majority of the packages you require will come from the internet repositories and <em>not</em> the Arch CD itself. This method will get you up and running in the shortest amount of time. Simply download the FTP ISO, burn it to a CD and restart your computer.<br />
<br />
The following steps assume you are connected to the Internet with a wired Ethernet connection, as opposed to a wireless connection.<br />
<br />
==Boot the Arch Setup CD==<br />
If the laptop does not boot from the CD, reboot and press F12 at the DELL BIOS splash screen to access the boot menu. From there you can choose to boot from the CD/DVD drive.<br />
<br />
==Setup==<br />
For the most part, the default settings should be fine, however the following notes may be of assistance.<br />
<br />
===0 - Configure===<br />
Just follow the prompts, choosing the defaults when asked. Make sure you allow the setup to detect your basic hardware automatically when asked.<br />
<br />
===1 - Prepare Hard Disks===<br />
The following is an example partition table. The example hard drive is 100GB and is configured to run only Arch Linux. Your settings will vary depending on the size of your hard drive and the number of operating systems you plan to run.<br />
<br />
'''sda''' (100GB)<br />
'''sda1''' ext2 100MB /boot ''(the boot loader files and kernel images will be installed here)''<br />
'''sda2''' swap 2.1GB swap ''(this example notebook has 2GB of RAM and we want to leave room for suspend2disk (hibernation) functions)''<br />
'''sda3''' ext3 6GB / ''(root--everything else will go here except for the files in /home and /boot)''<br />
'''sda4''' ext3 90GB /home ''(it's actually less than 90GB because ext3 filesystems reserve space to avoid capacity problems, but you get the point)''<br />
<br />
===2 - Select Packages===<br />
*Choose a mirror ('''''ftp.nethat.com''''' works very well from Vancouver, BC @ 160kb/s)<br />
*Choose ''only'' the base packages<br />
*Select ''all'' packages by default<br />
<br />
===3 - Install Packages===<br />
*Answer ''yes'' to cache packages (default)<br />
*Grab a coffee, it's going to take a while to fetch 100MB of packages<br />
<br />
===4 - Configure System===<br />
Choose your preferred editor; either vim or nano. <br />
<br />
A few files can be left alone, but there are some changes worth mentioning:<br />
<br />
====rc.conf====<br />
*Change your locale if necessary, for example Canadians will want to use ''en_CA'':<br />
LOCALE="en_CA.utf8"<br />
*Change the timezone if necessary, for example:<br />
TIMEZONE="Canada/Pacific"<br />
*To get rid of that ever-so-annoying system beep, blacklist the PC speaker module:<br />
MOD_BLACKLIST=(pcspkr)<br />
*Change the hostname if you desire a unique name, for example:<br />
HOSTNAME="dublin"<br />
*If your Internet Service Provider assigns your IP address automatically (and most do), make sure ''eth0'' is set to ''dhcp'':<br />
lo="lo 127.0.0.1"<br />
'''eth0="dhcp"'''<br />
<br />
====hosts====<br />
Add a second line under localhost with your unique hostname (the same hostname you chose in rc.conf) in place of localhost, for example:<br />
127.0.0.1 localhost.localdomain localhost<br />
'''127.0.0.1 dublin.localdomain dublin'''<br />
<br />
====fstab====<br />
No changes should be necessary.<br />
<br />
====mkinitcpio.conf====<br />
No changes should be necessary.<br />
<br />
====modprobe.conf====<br />
No changes should be necessary.<br />
<br />
====resolv.conf====<br />
No changes should be necessary.<br />
<br />
====locale.gen====<br />
Uncomment the languages files you wish to use, including the one you configured under LOCALE in the rc.conf:<br />
#en_BW.UTF-8 UTF-8<br />
#en_BW ISO-8859-1<br />
'''en_CA.UTF-8 UTF-8'''<br />
'''en_CA ISO-8859-1'''<br />
#en_DK.UTF-8 UTF-8<br />
#en_DK ISO-8859-1<br />
<br />
Canadians should probably uncomment ''en_US, en_CA and en_GB''.<br />
<br />
====root password====<br />
Set a root password.<br />
<br />
====pacman mirrors====<br />
You can either use the same mirror you used to install the base packages, or you can choose a different one at this time. The mirror you select at this stage will be your default repository after installation is complete.<br />
<br />
===5 - Install Kernel===<br />
The default choices should be fine.<br />
<br />
===6 - Install Boot Loader===<br />
If you are installing Arch as the sole operating system on the notebook, just go with the default settings. If you are dual-booting with another OS, choose the options carefully to avoid problems with your existing settings.<br />
<br />
* When installing GRUB, you can also append '''vga=791''' to the kernel option to set your terminal (framebuffer) resolution to 1024x768, for example:<br />
kernel /vmlinuz26 root=/dev/sda3 ro '''vga=791'''<br />
<br />
===7 - Exit===<br />
Reboot, eject the CD and log into your new Arch Linux installation.<br />
<br />
==Synchronize Repositories and Update==<br />
When logging into Arch for the first time, it is a good idea to make sure the local package database is synchronized with the Arch software repositories and that all of your software is up to date. From the console, type:<br />
# pacman -Syu<br />
<br />
=Add Users=<br />
At this point you can add a local user account by typing:<br />
# useradd -m johndoe<br />
# passwd johndoe<br />
<br />
''The '''-m''' flag creates the user's /home directory and copies the default configuration files to it (from /etc/skel)''<br />
<br />
Note, you will not be able to use the '''sudo''' command with this account until you [[Sudo|install and configure sudo]].<br />
<br />
=Xorg=<br />
If you plan to install a desktop environment (e.g. GNOME, KDE, etc.) you must install and configure Xorg.<br />
<br />
===Installation===<br />
Install the necessary packages:<br />
# pacman -S xorg xterm hwd<br />
<br />
===Configuration===<br />
The <tt>hwd</tt> program (''Hardware Detect'') will examine your hardware and create a default configuration file for Xorg (''/etc/X11/xorg.conf''):<br />
# hwd -xa<br />
You should now have a working X setup, however the default configuration uses the generic VESA graphics driver. If you want to run your desktop at its native resolution (e.g. 1680x1050) and enable 3D acceleration, you'll need to install the appropriate driver for your video card. See the [[Dell_Inspiron_6400#Video|Video]] section below for detailed instructions.<br />
<br />
=Desktop Environments=<br />
Arch Linux supports a variety of desktop environments and window managers, all of which must be installed manually. Refer to the following list for more information:<br />
<br />
'''Openbox:''' [[Openbox|Openbox Wiki]]<br />
<br />
'''GNOME:''' [[GNOME|GNOME Wiki]]<br />
<br />
'''Xfce:''' [[Xfce|Xfce Wiki]]<br />
<br />
'''KDE:''' [[KDE|KDE Wiki]]<br />
<br />
'''KDEmod:''' Visit the KDEmod website at http://kdemod.ath.cx/ or see the [[KDEmod|KDEmod Wiki]] for more information.<br />
<br />
'''E17:''' [[E17|E17 Wiki]]<br />
<br />
'''Fluxbox:''' [[Fluxbox|Fluxbox Wiki]]<br />
<br />
=Hardware=<br />
<br />
==Audio==<br />
===Sigmatel/Intel Chipset===<br />
The Sigmatel audio chipset should be detected automatically during installation, requiring no input from the user. For example, the following kernel modules are configured in ''/etc/rc.conf'' by default:<br />
snd-mixer-oss snd-pcm-oss snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore<br />
<br />
====ALSA Audio Drivers====<br />
Refer to the [[ALSA]] wiki for general assistance with volume settings, group permissions, etc.<br />
<br />
====OSS Audio Drivers====<br />
See the [[OSS]] wiki for more information.<br />
<br />
==Video==<br />
===ATI X1300/X1400 Radeon Mobility===<br />
====Proprietary Driver (fglrx)====<br />
<br />
The fglrx ATI proprietary driver is available from the standard Arch repositories and is the simplest way to get full 3D acceleration and native resolutions on your notebook:<br />
# pacman -S fglrx<br />
Run the '''aticonfig''' tool to automatically add the appropriate settings to ''/etc/X11/xorg.conf'':<br />
# aticonfig --initial<br />
Lastly, we need to modify ''/etc/rc.conf'' and add the '''fglrx''' kernel driver to the MODULES section, for example:<br />
MODULES=('''fglrx''' b44 mii snd-mixer-oss ...)<br />
Reboot and confirm that the ATI driver is working by typing '''fglrxinfo''' in a terminal. The results should look something like this:<br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Mobility Radeon X1400<br />
OpenGL version string: 2.0.6473 (8.37.6)<br />
<br />
Further information can be found at the [[ATI]] wiki.<br />
<br />
====Open Source ATI Driver====<br />
<br />
Please refer to the [[ATI]] wiki for more information.<br />
<br />
===Intel Graphics Media Accelerator 950===<br />
====Open Source Intel Driver====<br />
<br />
Install the driver:<br />
# pacman -S xf86-video-intel<br />
<br />
Use '''''gft''''' to generate the Xorg ''Modeline'' values and then edit ''/etc/X11/xorg.conf'' and add these values to the ''Monitor'' section, for example:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "unknown"<br />
'''Modeline "800x600" 40.12 800 848 968 1056 600 601 605 628 #60Hz'''<br />
EndSection<br />
<br />
Lastly, add the following to the "Device" section, replacing the existing ''Driver'' value if present:<br />
<br />
VideoRam 229376<br />
Option "CacheLines" "1980"<br />
Driver "intel"<br />
<br />
===nVidia GeForce Go 7300===<br />
The [[NVIDIA|NVIDIA Driver Wiki]] works fine. A side note: When running Beryl/Compiz-Fusion, while opening multiple instances of FireFox, the entire window went black. Forcing AIGLX solved this.<br />
<br />
==Networking==<br />
<br />
===Broadcom 440x 10/100 Ethernet===<br />
The Broadcom Ethernet card should have out-of-the-box support. No configuration necessary.<br />
<br />
===Dell Wireless 1390===<br />
<br />
Dell does not offer native Linux drivers for the 1390 wireless card. Fortunately, '''ndiswrapper''' can be used to install the Windows driver:<br />
# pacman -S ndiswrapper<br />
<br />
Download the 1390 driver from the Dell website:<br />
wget http://ftp.us.dell.com/network/R140747.EXE<br />
<br />
Create a temp folder and extract the driver:<br />
mkdir ~/Dell1390<br />
mv R14070747.EXE ~/Dell1390 <br />
cd ~/Dell1390 <br />
unzip -a R14070747.EXE<br />
cd DRIVERS<br />
<br />
As root, configure ndiswrapper to use the Windows driver:<br />
# ndiswrapper -i bcmwl5.inf<br />
# ndiswrapper -l<br />
# ndiswrapper -m<br />
# modprobe ndiswrapper<br />
<br />
Test the new driver by typing '''iwlist scanning''' in a terminal.<br />
<br />
To load the driver automatically at each boot, add '''ndiswrapper''' to the MODULES array in ''/etc/rc.conf'', for example:<br />
MODULES=(fglrx '''ndiswrapper''' b44 mii ...)<br />
<br />
Finally, remove the temp folder used during installation:<br />
rm -rf ~/Dell1390<br />
<br />
===Dell Wireless 1500 Draft 802.11n Wireless (Intel 4965AGN)===<br />
Grab the driver packages:<br />
# pacman -S iwlwifi iwlwifi-4965-ucode<br />
Edit ''/etc/rc.conf'' as root and add '''iwl4965''' to the MODULES list:<br />
MODULES=(fglrx '''''iwl4965''''' b44 mii ...)<br />
Add '''wlan0="dchp"''' to the NETWORKING section:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''wlan0="dhcp"'''''<br />
If '''wlan0''' is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!wlan0''''')<br />
<br />
===Dell Wireless 350 Bluetooth Module===<br />
Install the bluetooth libraries and basic utilties:<br />
# pacman -S bluez-libs bluez-utils<br />
Add '''bluetooth''' to the DAEMONS list in ''/etc/rc.conf'', for example:<br />
DAEMONS=(syslog-ng powersaved '''bluetooth''' ipw3945d ...)<br />
Now, depending on your desktop environment, install the appropriate tools:<br />
<br />
For GNOME: <br />
# pacman -S gnome-bluetooth bluez-gnome<br />
For KDE:<br />
# pacman -S kdebluetooth<br />
<br />
===Dell Wireless 355 Bluetooth Module===<br />
The steps described above for Dell Wireless 350 Bluetooth Module work with Dell Wireless 355 Bluetooth Module too.<br />
<br />
===Intel PRO/Wireless 3945ABG===<br />
With the release of Intel's open source [http://intellinuxwireless.org/ iwlwifi driver], 3945 owners now have two choices for wireless drivers. As the iwlwifi project matures, the ipw3945 driver will become obsolete, however until that time it will remain below as a second alternative.<br />
<br />
Install and configure NetworkManager before attempting to install the Intel 3945 wireless drivers. Refer to the [[Networkmanager| Networkmanager Wiki]] for more information.<br />
<br />
====Method 1: iwlwifi driver====<br />
Grab the driver packages:<br />
# pacman -S iwlwifi iwlwifi-3945-ucode<br />
Edit ''/etc/rc.conf'' as root and add '''iwl3945''' to the MODULES list:<br />
MODULES=(fglrx '''''iwl3945''''' b44 mii ...)<br />
Add '''wlan0="dchp"''' to the NETWORKING section:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''wlan0="dhcp"'''''<br />
If '''wlan0''' is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!wlan0''''')<br />
<br />
====Method 2: ipw3945 driver====<br />
Grab the Intel 3945 driver packages:<br />
# pacman -S ipw3945<br />
Edit ''/etc/rc.conf'' as root and add '''ipw3945''' to the MODULES list:<br />
MODULES=(fglrx '''''ipw3945''''' b44 mii ...)<br />
Add '''eth1="dchp"''' to the NETWORKING section ''(Note: It is sometimes detected as eth2 instead of eth1, use '''ifconfig''' to verify yours and, if necessary add eth2="dhcp" instead)'':<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''eth1="dhcp"'''''<br />
If '''eth1''' (or '''eth2''') is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!eth1''''')<br />
Add '''ipw3945d''' to the DAEMONS list ''before'' the dhcdbd and networkmanager daemons:<br />
DAEMONS=(syslog-ng '''''ipw3945d''''' dhcdbd networkmanager alsa ...)<br />
<br />
==Conexant HDA D110 MDC V.92 modem (winmodem)==<br />
The Conexant modem requires the proprietary '''hsfmodem''' driver.<br />
Dell offers a debian package [http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R155004&SystemID=INSPIRONI6400/E1505&servicetag=&os=UBLN&osl=en&deviceid=8593&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=1&libid=20&fileid=206745 hsfmodem_7.60.00.06oem_i386.deb] at their [http://support.dell.com/ support site] that works at '''full speed''' unlike the trial version from [http://www.linuxant.com/ Linuxant] which works at 14.4kbps.<br />
<br />
The following '''PKGBUILD''' can be used to create an archlinux '''hsfmodem''' package from the debian package:<br />
pkgname=hsfmodem<br />
pkgver=7.60.00.06oem<br />
pkgrel=1<br />
pkgdesc="Conexant dialup modem driver by dell"<br />
url="http://support.dell.com/"<br />
license=("unknown")<br />
arch=('i686')<br />
source=(${pkgname}_${pkgver}_i386.deb)<br />
md5sums=('80d38fccab347638fa7a2237b458b428')<br />
<br />
build() {<br />
cd $startdir/src/<br />
ar x ${pkgname}_${pkgver}_i386.deb<br />
tar xzf data.tar.gz<br />
cp -a usr etc $startdir/pkg/<br />
}<br />
<br />
#Download and place <code>hsfmodem_7.60.00.06oem_i386.deb</code> and the <code>PKGBUILD</code> in a new folder, and run makepkg to create the package. See [[Arch Build System]] for details on building packages.<br />
#Run <code>hsfconfig</code> as root to build the module and initialise the modem. A reboot is required before the modem can be initialised. Run <code>hsfconfig</code> again after reboot.<br />
#The modules are automatically loaded and a <code>/dev/modem</code> symlink is setup for use with the modem. Now use <code>wvdial</code> or other dialer programs to connect to the internet.<br />
<br />
==Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Card Reader==<br />
The Ricoh card reader should work out of the box, as long as '''MOD_AUTOLOAD''' is set to '''yes''' in ''/etc/rc.conf''. Assuming you use a HAL-aware desktop (GNOME, KDE, etc.), when a memory card is inserted, the kernel should automatically load the '''mmc_core/mmc_block''' modules and mount the new filesystem according to your desktop's automount settings. <br />
<br />
This has been confirmed with the following card types:<br />
* SD Card<br />
<br />
==Synaptics Touchpad==<br />
The Synaptics touchpad should provide basic functions out-of-the-box, however if you would like to use the scroll zones and enable other advanced features, please refer to the [[Touchpad_Synaptics | Synaptics Touchpad]] wiki.<br />
<br />
=Power Management=<br />
<br />
==ACPI Hibernation/Suspend with pm-utils==<br />
The powersave scripts have been officially replaced by [http://www.archlinux.org/packages/search/?q=pm-utils pm-utils]. Refer to the [[Pm-utils]] wiki for detailed instructions.<br />
<br />
'''''Note:''''' ATI video card owners must also add '''vga=0''' to the kernel options in <tt>/boot/grub/menu.lst</tt> in order to resume from suspend2ram. For exmaple:<br />
<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda3 resume=/dev/sda2 ro '''''vga=0'''''<br />
initrd /kernel26.img<br />
<br />
==CPU Frequency Scaling with cpufrequtils==<br />
<br />
Refer to the [[Cpufrequtils]] wiki for step-by-step instructions.<br />
<br />
= Multimedia Buttons & Fn Hotkeys =<br />
Unfortunately, configuring multimedia buttons and function keys on your laptop can be complicated process. Factors that must be taken into consideration include your choice of Desktop Environment (or lack thereof) and the actions you wish to bind to the special buttons or keys. For a detailed explanation of what is required, please refer to the [[Hotkeys]] wiki.<br />
<br />
The following tips may offer some assistance in getting started.<br />
<br />
== Multimedia Buttons ==<br />
For the most part, the Volume and Playback buttons should be recognized as an unassigned key by the Linux kernel. In which case, all that is necessary is to bind the button to an action. <br />
<br />
It is also worth noting that the multimedia buttons and equivalent Fn key shortcut (e.g. Fn+PgUp = Vol Up) will produce the same keycode, so if you configure the button, the Fn hotkey combo will execute the same action.<br />
<br />
=== GNOME ===<br />
The GNOME desktop provides an easy method for binding multimedia keys to their appropriate action. <br />
<br />
# Browse to '''System -> Preferences -> Keyboard Shortcuts''' and scroll down to the '''Sound''' section.<br />
# Click on an item (e.g. Mute) and then press the corresponding multimedia button<br />
# Repeat this process for all of the multimedia buttons<br />
<br />
The volume buttons should now work system-wide, and the playback buttons will now work in media players such as Rhythmbox and Exaile.<br />
<br />
=== Openbox and other Window Managers ===<br />
The <tt>xbindkeys</tt> utility is highly recommended for lightweight desktops such as Openbox--refer to the [[Hotkeys]] wiki for information. <br />
<br />
The following is an example ''~/.xbindkeysrc'' config file, making use of the multimedia buttons:<br />
<pre><br />
# vol up<br />
"amixer set Master 2dB+ unmute"<br />
m:0x10 + c:176<br />
# vol dn<br />
"amixer set Master 2dB- unmute"<br />
m:0x10 + c:174<br />
# vol mute<br />
"amixer set Master mute"<br />
m:0x10 + c:160<br />
# play/pause<br />
"audacious -t"<br />
m:0x10 + c:162<br />
# back<br />
"audacious -r"<br />
m:0x10 + c:144<br />
# forward<br />
"audacious -f"<br />
m:0x10 + c:153<br />
# stop<br />
"audacious -s"<br />
m:0x10 + c:164<br />
</pre><br />
<br />
== Function (Fn) Hotkeys ==<br />
Function keys seem to be less standardized than the Volume/Playback buttons, and therefore it can be difficult to get all of them working properly. For example, the Standby shortcut (Fn+ESC) may be recognized while at the same time the Hibernate shortcut (Fn+F1) is not. To make matters more confusing, it appears that some Fn keys such as those that adjust the LCD brightness are controlled by the BIOS, independent of the Operating System. Again, the [[Hotkeys]] wiki is highly recommended reading.<br />
<br />
The following example shows how one can configure the Dell Media Direct button, Eject (Fn+F10) and Hibernate (Fn+F1) hotkeys to execute specific commands:<br />
<br />
First, assign kernel keycodes to the Media Direct button and Fn hotkeys, using the ''/etc/rc.local'' script (which is executed before X loads):<br />
#!/bin/bash<br />
#<br />
# /etc/rc.local: Local multi-user startup script.<br />
#<br />
setkeycodes e009 122 # e009 eject fn<br />
setkeycodes e012 130 # e012 mediadirect<br />
setkeycodes e00a 123 # e00a hibernate fn<br />
<br />
Then use the <tt>xbindkeys</tt> utility to bind the newly recognized keys to a custom action. Here's an ''~/.xbindkeysrc'' config file:<br />
<br />
# media direct button<br />
"streamtuner"<br />
m:0x10 + c:134<br />
# eject function hotkey<br />
"eject"<br />
m:0x10 + c:210 <br />
# hibernate function hotkey<br />
"sudo /usr/sbin/pm-hibernate"<br />
m:0x10 + c:209<br />
<br />
Finally, execute <tt>xbindkeys</tt> at startup by placing it in your .xinitrc (or appropriate startup file for your environment):<br />
xscreensaver -no-splash &<br />
eval `cat $HOME/.fehbg` &<br />
'''''xbindkeys &'''''<br />
#sleep 3<br />
pypanel &<br />
exec openbox<br />
<br />
As stated previously, it can be a complicated process involving lots of trial & error troubleshooting, but hopefully this will help you get started.<br />
<br />
=Resources=<br />
TuxMobil: [http://tuxmobil.org/mylaptops.html Linux Laptop & Notebook Installation Guides]<br />
<br />
TuxMobil: [http://tuxmobil.org/dell.html DELL Notebooks]<br />
<br />
Gentoo Wiki: [http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_6400 HARDWARE Dell Inspiron 6400]<br />
<br />
Gentoo Wiki: [http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_6400_Fixes_for_common_problems HARDWARE Dell Inspiron 6400 Fixes for common problems]<br />
<br />
<br />
<br />
=Comments=</div>Shastryhttps://wiki.archlinux.org/index.php?title=Dell_Inspiron_6400&diff=29666Dell Inspiron 64002007-09-21T20:51:58Z<p>Shastry: /* Conexant HDA D110 MDC V.92 modem (winmodem) */</p>
<hr />
<div>[[Category:Laptops (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
=Introduction=<br />
==Summary==<br />
The goal of this wiki is to provide a comprehensive guide for Dell Inspiron 6400 owners seeking to install Arch Linux. It will attempt to cover all facets of hardware management, including wireless networking and hotkey support. Although this guide has been written specifically for the Inspiron 6400, many of the sub-sections can be applied to other Dell Inspiron models, including: <br />
* Dell Inspiron e1405<br />
* Dell Inspiron 640m<br />
* Dell Inspiron e1705<br />
<br />
==From the original contributor==<br />
I will attempt to cover as much as possible, however please feel free to contribute to this guide as you feel necessary. I will be happy to answer any questions, but I am by no means a Linux expert so there's a good chance I won't know the answer either! ~Thayer ([[User:Thayer.w|thayer.w]]) (thayerw(at)gmail(dot)com)<br />
<br />
=Hardware Specifications=<br />
The 6400 series laptop is currently available in a number of configurations and this guide will attempt to cover them all. Refer to the list below to determine whether your configuration has been documented.<br />
<br />
*<span style="color:green;">Green items are confirmed to work</span><br />
*<span style="color:red;">Red items have yet to be confirmed and require a Wiki entry</span><br />
<br />
===Base Components===<br />
<br />
* Intel Core Duo and Core 2 Duo processors<br />
** T2500 (2GHz/667MHz FSB/2MB Cache)<br />
** T5600 (1.83GHz/667MHz FSB/2MB Cache)<br />
** T2050 (1.66GHz/667MHz FSB/2MB Cache)<br />
** T1350 (1.66GHz/667MHz FSB/2MB Cache)<br />
** T5200 (1.60GHz/667MHz FSB/2MB Cache)<br />
* 512MB/1GB/2GB 533MHz/667MHz DDR2 SDRAM Memory<br />
* 15.4" Widescreen Display<br />
** WXGA (1280 x 800)<br />
** <span style="color:green;">WSXGA 1280x800 with TrueLife™</span><br />
** <span style="color:green;">WSXGA+ 1680x1050 with TrueLife™</span><br />
* 80GB/100GB/120GB/160GB 5400/7200 RPM SATA Hard Drive<br />
* <span style="color:green;">8x CD/DVD+/-RW/DL+R</span><br />
* <span style="color:green;">Broadcom 440x 10/100 Ethernet</span><br />
* <span style="color:green;">Conexant HDA D110 MDC V.92 modem (winmodem)</span><br />
* <span style="color:green;">Sigmatel STAC 92xx Audio</span><br />
* <span style="color:green;">Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Card Reader</span><br />
* <span style="color:green;">4 USB 2.0 Ports</span><br />
* <span style="color:red;">Firewire port (IEEE 1394)</span><br />
* <span style="color:red;">1 ExpressCard Slot</span><br />
* <span style="color:green;">Synaptics touchpad with scroll zones</span><br />
<br />
===Video Options===<br />
<br />
* <span style="color:green;">128MB ATI Mobility Radeon X1300 with HyperMemory</span><br />
* <span style="color:green;">256MB ATI Mobility Radeon X1400 with Hypermemory</span><br />
* <span style="color:green;">256MB nVidia GeForce Go 7300 with TurboCache</span><br />
* <span style="color:green;">128MB Intel Graphics Media Accelerator 950</span><br />
<br />
===Wireless Options===<br />
<br />
* <span style="color:green;">Intel Pro/Wireless 3945ABG (802.11a/b/g)</span><br />
* <span style="color:green;">Dell Wireless 1390</span><br />
* <span style="color:green;">Dell Wireless 1500 Draft 802.11n Wireless (Intel 4965AGN)</span><br />
* <span style="color:green;">Dell Wireless 350 Bluetooth Module</span><br />
* <span style="color:green;">Dell Wireless 355 Bluetooth Module</span><br />
<br />
=Arch Installation=<br />
There are plenty of resources available to help new users install and configure a basic Arch Linux installation, including the [[Official_Arch_Linux_Install_Guide|Official Installation Guide]] and the [[Beginners_Guide|Beginners Guide]].<br />
<br />
That being said, the following tips are specific to the Dell Inspiron 6400 and may be of some help during installation.<br />
<br />
If an Ethernet (wired land-line) broadband internet connection is available it is highly recommended that Arch be installed with the smaller FTP ISO. If you plan to have a desktop environment (KDE, GNOME, etc) then the majority of the packages you require will come from the internet repositories and <em>not</em> the Arch CD itself. This method will get you up and running in the shortest amount of time. Simply download the FTP ISO, burn it to a CD and restart your computer.<br />
<br />
The following steps assume you are connected to the Internet with a wired Ethernet connection, as opposed to a wireless connection.<br />
<br />
==Boot the Arch Setup CD==<br />
If the laptop does not boot from the CD, reboot and press F12 at the DELL BIOS splash screen to access the boot menu. From there you can choose to boot from the CD/DVD drive.<br />
<br />
==Setup==<br />
For the most part, the default settings should be fine, however the following notes may be of assistance.<br />
<br />
===0 - Configure===<br />
Just follow the prompts, choosing the defaults when asked. Make sure you allow the setup to detect your basic hardware automatically when asked.<br />
<br />
===1 - Prepare Hard Disks===<br />
The following is an example partition table. The example hard drive is 100GB and is configured to run only Arch Linux. Your settings will vary depending on the size of your hard drive and the number of operating systems you plan to run.<br />
<br />
'''sda''' (100GB)<br />
'''sda1''' ext2 100MB /boot ''(the boot loader files and kernel images will be installed here)''<br />
'''sda2''' swap 2.1GB swap ''(this example notebook has 2GB of RAM and we want to leave room for suspend2disk (hibernation) functions)''<br />
'''sda3''' ext3 6GB / ''(root--everything else will go here except for the files in /home and /boot)''<br />
'''sda4''' ext3 90GB /home ''(it's actually less than 90GB because ext3 filesystems reserve space to avoid capacity problems, but you get the point)''<br />
<br />
===2 - Select Packages===<br />
*Choose a mirror ('''''ftp.nethat.com''''' works very well from Vancouver, BC @ 160kb/s)<br />
*Choose ''only'' the base packages<br />
*Select ''all'' packages by default<br />
<br />
===3 - Install Packages===<br />
*Answer ''yes'' to cache packages (default)<br />
*Grab a coffee, it's going to take a while to fetch 100MB of packages<br />
<br />
===4 - Configure System===<br />
Choose your preferred editor; either vim or nano. <br />
<br />
A few files can be left alone, but there are some changes worth mentioning:<br />
<br />
====rc.conf====<br />
*Change your locale if necessary, for example Canadians will want to use ''en_CA'':<br />
LOCALE="en_CA.utf8"<br />
*Change the timezone if necessary, for example:<br />
TIMEZONE="Canada/Pacific"<br />
*To get rid of that ever-so-annoying system beep, blacklist the PC speaker module:<br />
MOD_BLACKLIST=(pcspkr)<br />
*Change the hostname if you desire a unique name, for example:<br />
HOSTNAME="dublin"<br />
*If your Internet Service Provider assigns your IP address automatically (and most do), make sure ''eth0'' is set to ''dhcp'':<br />
lo="lo 127.0.0.1"<br />
'''eth0="dhcp"'''<br />
<br />
====hosts====<br />
Add a second line under localhost with your unique hostname (the same hostname you chose in rc.conf) in place of localhost, for example:<br />
127.0.0.1 localhost.localdomain localhost<br />
'''127.0.0.1 dublin.localdomain dublin'''<br />
<br />
====fstab====<br />
No changes should be necessary.<br />
<br />
====mkinitcpio.conf====<br />
No changes should be necessary.<br />
<br />
====modprobe.conf====<br />
No changes should be necessary.<br />
<br />
====resolv.conf====<br />
No changes should be necessary.<br />
<br />
====locale.gen====<br />
Uncomment the languages files you wish to use, including the one you configured under LOCALE in the rc.conf:<br />
#en_BW.UTF-8 UTF-8<br />
#en_BW ISO-8859-1<br />
'''en_CA.UTF-8 UTF-8'''<br />
'''en_CA ISO-8859-1'''<br />
#en_DK.UTF-8 UTF-8<br />
#en_DK ISO-8859-1<br />
<br />
Canadians should probably uncomment ''en_US, en_CA and en_GB''.<br />
<br />
====root password====<br />
Set a root password.<br />
<br />
====pacman mirrors====<br />
You can either use the same mirror you used to install the base packages, or you can choose a different one at this time. The mirror you select at this stage will be your default repository after installation is complete.<br />
<br />
===5 - Install Kernel===<br />
The default choices should be fine.<br />
<br />
===6 - Install Boot Loader===<br />
If you are installing Arch as the sole operating system on the notebook, just go with the default settings. If you are dual-booting with another OS, choose the options carefully to avoid problems with your existing settings.<br />
<br />
* When installing GRUB, you can also append '''vga=791''' to the kernel option to set your terminal (framebuffer) resolution to 1024x768, for example:<br />
kernel /vmlinuz26 root=/dev/sda3 ro '''vga=791'''<br />
<br />
===7 - Exit===<br />
Reboot, eject the CD and log into your new Arch Linux installation.<br />
<br />
==Synchronize Repositories and Update==<br />
When logging into Arch for the first time, it is a good idea to make sure the local package database is synchronized with the Arch software repositories and that all of your software is up to date. From the console, type:<br />
# pacman -Syu<br />
<br />
=Add Users=<br />
At this point you can add a local user account by typing:<br />
# useradd -m johndoe<br />
# passwd johndoe<br />
<br />
''The '''-m''' flag creates the user's /home directory and copies the default configuration files to it (from /etc/skel)''<br />
<br />
Note, you will not be able to use the '''sudo''' command with this account until you [[Sudo|install and configure sudo]].<br />
<br />
=Xorg=<br />
If you plan to install a desktop environment (e.g. GNOME, KDE, etc.) you must install and configure Xorg.<br />
<br />
===Installation===<br />
Install the necessary packages:<br />
# pacman -S xorg xterm hwd<br />
<br />
===Configuration===<br />
The <tt>hwd</tt> program (''Hardware Detect'') will examine your hardware and create a default configuration file for Xorg (''/etc/X11/xorg.conf''):<br />
# hwd -xa<br />
You should now have a working X setup, however the default configuration uses the generic VESA graphics driver. If you want to run your desktop at its native resolution (e.g. 1680x1050) and enable 3D acceleration, you'll need to install the appropriate driver for your video card. See the [[Dell_Inspiron_6400#Video|Video]] section below for detailed instructions.<br />
<br />
=Desktop Environments=<br />
Arch Linux supports a variety of desktop environments and window managers, all of which must be installed manually. Refer to the following list for more information:<br />
<br />
'''Openbox:''' [[Openbox|Openbox Wiki]]<br />
<br />
'''GNOME:''' [[GNOME|GNOME Wiki]]<br />
<br />
'''Xfce:''' [[Xfce|Xfce Wiki]]<br />
<br />
'''KDE:''' [[KDE|KDE Wiki]]<br />
<br />
'''KDEmod:''' Visit the KDEmod website at http://kdemod.ath.cx/ or see the [[KDEmod|KDEmod Wiki]] for more information.<br />
<br />
'''E17:''' [[E17|E17 Wiki]]<br />
<br />
'''Fluxbox:''' [[Fluxbox|Fluxbox Wiki]]<br />
<br />
=Hardware=<br />
<br />
==Audio==<br />
===Sigmatel/Intel Chipset===<br />
The Sigmatel audio chipset should be detected automatically during installation, requiring no input from the user. For example, the following kernel modules are configured in ''/etc/rc.conf'' by default:<br />
snd-mixer-oss snd-pcm-oss snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore<br />
<br />
====ALSA Audio Drivers====<br />
Refer to the [[ALSA]] wiki for general assistance with volume settings, group permissions, etc.<br />
<br />
====OSS Audio Drivers====<br />
See the [[OSS]] wiki for more information.<br />
<br />
==Video==<br />
===ATI X1300/X1400 Radeon Mobility===<br />
====Proprietary Driver (fglrx)====<br />
<br />
The fglrx ATI proprietary driver is available from the standard Arch repositories and is the simplest way to get full 3D acceleration and native resolutions on your notebook:<br />
# pacman -S fglrx<br />
Run the '''aticonfig''' tool to automatically add the appropriate settings to ''/etc/X11/xorg.conf'':<br />
# aticonfig --initial<br />
Lastly, we need to modify ''/etc/rc.conf'' and add the '''fglrx''' kernel driver to the MODULES section, for example:<br />
MODULES=('''fglrx''' b44 mii snd-mixer-oss ...)<br />
Reboot and confirm that the ATI driver is working by typing '''fglrxinfo''' in a terminal. The results should look something like this:<br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Mobility Radeon X1400<br />
OpenGL version string: 2.0.6473 (8.37.6)<br />
<br />
Further information can be found at the [[ATI]] wiki.<br />
<br />
====Open Source ATI Driver====<br />
<br />
Please refer to the [[ATI]] wiki for more information.<br />
<br />
===Intel Graphics Media Accelerator 950===<br />
====Open Source Intel Driver====<br />
<br />
Install the driver:<br />
# pacman -S xf86-video-intel<br />
<br />
Use '''''gft''''' to generate the Xorg ''Modeline'' values and then edit ''/etc/X11/xorg.conf'' and add these values to the ''Monitor'' section, for example:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "unknown"<br />
'''Modeline "800x600" 40.12 800 848 968 1056 600 601 605 628 #60Hz'''<br />
EndSection<br />
<br />
Lastly, add the following to the "Device" section, replacing the existing ''Driver'' value if present:<br />
<br />
VideoRam 229376<br />
Option "CacheLines" "1980"<br />
Driver "intel"<br />
<br />
===nVidia GeForce Go 7300===<br />
The [[NVIDIA|NVIDIA Driver Wiki]] works fine. A side note: When running Beryl/Compiz-Fusion, while opening multiple instances of FireFox, the entire window went black. Forcing AIGLX solved this.<br />
<br />
==Networking==<br />
<br />
===Broadcom 440x 10/100 Ethernet===<br />
The Broadcom Ethernet card should have out-of-the-box support. No configuration necessary.<br />
<br />
===Dell Wireless 1390===<br />
<br />
Dell does not offer native Linux drivers for the 1390 wireless card. Fortunately, '''ndiswrapper''' can be used to install the Windows driver:<br />
# pacman -S ndiswrapper<br />
<br />
Download the 1390 driver from the Dell website:<br />
wget http://ftp.us.dell.com/network/R140747.EXE<br />
<br />
Create a temp folder and extract the driver:<br />
mkdir ~/Dell1390<br />
mv R14070747.EXE ~/Dell1390 <br />
cd ~/Dell1390 <br />
unzip -a R14070747.EXE<br />
cd DRIVERS<br />
<br />
As root, configure ndiswrapper to use the Windows driver:<br />
# ndiswrapper -i bcmwl5.inf<br />
# ndiswrapper -l<br />
# ndiswrapper -m<br />
# modprobe ndiswrapper<br />
<br />
Test the new driver by typing '''iwlist scanning''' in a terminal.<br />
<br />
To load the driver automatically at each boot, add '''ndiswrapper''' to the MODULES array in ''/etc/rc.conf'', for example:<br />
MODULES=(fglrx '''ndiswrapper''' b44 mii ...)<br />
<br />
Finally, remove the temp folder used during installation:<br />
rm -rf ~/Dell1390<br />
<br />
===Dell Wireless 1500 Draft 802.11n Wireless (Intel 4965AGN)===<br />
Grab the driver packages:<br />
# pacman -S iwlwifi iwlwifi-4965-ucode<br />
Edit ''/etc/rc.conf'' as root and add '''iwl4965''' to the MODULES list:<br />
MODULES=(fglrx '''''iwl4965''''' b44 mii ...)<br />
Add '''wlan0="dchp"''' to the NETWORKING section:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''wlan0="dhcp"'''''<br />
If '''wlan0''' is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!wlan0''''')<br />
<br />
===Dell Wireless 350 Bluetooth Module===<br />
Install the bluetooth libraries and basic utilties:<br />
# pacman -S bluez-libs bluez-utils<br />
Add '''bluetooth''' to the DAEMONS list in ''/etc/rc.conf'', for example:<br />
DAEMONS=(syslog-ng powersaved '''bluetooth''' ipw3945d ...)<br />
Now, depending on your desktop environment, install the appropriate tools:<br />
<br />
For GNOME: <br />
# pacman -S gnome-bluetooth bluez-gnome<br />
For KDE:<br />
# pacman -S kdebluetooth<br />
<br />
===Dell Wireless 355 Bluetooth Module===<br />
The steps described above for Dell Wireless 350 Bluetooth Module work with Dell Wireless 355 Bluetooth Module too.<br />
<br />
===Intel PRO/Wireless 3945ABG===<br />
With the release of Intel's open source [http://intellinuxwireless.org/ iwlwifi driver], 3945 owners now have two choices for wireless drivers. As the iwlwifi project matures, the ipw3945 driver will become obsolete, however until that time it will remain below as a second alternative.<br />
<br />
Install and configure NetworkManager before attempting to install the Intel 3945 wireless drivers. Refer to the [[Networkmanager| Networkmanager Wiki]] for more information.<br />
<br />
====Method 1: iwlwifi driver====<br />
Grab the driver packages:<br />
# pacman -S iwlwifi iwlwifi-3945-ucode<br />
Edit ''/etc/rc.conf'' as root and add '''iwl3945''' to the MODULES list:<br />
MODULES=(fglrx '''''iwl3945''''' b44 mii ...)<br />
Add '''wlan0="dchp"''' to the NETWORKING section:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''wlan0="dhcp"'''''<br />
If '''wlan0''' is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!wlan0''''')<br />
<br />
====Method 2: ipw3945 driver====<br />
Grab the Intel 3945 driver packages:<br />
# pacman -S ipw3945<br />
Edit ''/etc/rc.conf'' as root and add '''ipw3945''' to the MODULES list:<br />
MODULES=(fglrx '''''ipw3945''''' b44 mii ...)<br />
Add '''eth1="dchp"''' to the NETWORKING section ''(Note: It is sometimes detected as eth2 instead of eth1, use '''ifconfig''' to verify yours and, if necessary add eth2="dhcp" instead)'':<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''eth1="dhcp"'''''<br />
If '''eth1''' (or '''eth2''') is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!eth1''''')<br />
Add '''ipw3945d''' to the DAEMONS list ''before'' the dhcdbd and networkmanager daemons:<br />
DAEMONS=(syslog-ng '''''ipw3945d''''' dhcdbd networkmanager alsa ...)<br />
<br />
==Conexant HDA D110 MDC V.92 modem (winmodem)==<br />
The Conexant modem requires the proprietary '''hsfmodem''' driver.<br />
Dell offers a debian package [http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R155004&SystemID=INSPIRONI6400/E1505&servicetag=&os=UBLN&osl=en&deviceid=8593&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=1&libid=20&fileid=206745 hsfmodem_7.60.00.06oem_i386.deb] at their [http://support.dell.com/ support site] that works at '''full speed''' unlike the trial version from [http://www.linuxant.com/ Linuxant] which works at 14.4kbps.<br />
<br />
The following '''PKGBUILD''' can be used to create a '''hsfmodem''' package from the debian package:<br />
pkgname=hsfmodem<br />
pkgver=7.60.00.06oem<br />
pkgrel=1<br />
pkgdesc="Conexant dialup modem driver by dell"<br />
url="http://support.dell.com/"<br />
license=("unknown")<br />
arch=('i686')<br />
source=(${pkgname}_${pkgver}_i386.deb)<br />
md5sums=('80d38fccab347638fa7a2237b458b428')<br />
<br />
build() {<br />
cd $startdir/src/<br />
ar x ${pkgname}_${pkgver}_i386.deb<br />
tar xzf data.tar.gz<br />
cp -a usr etc $startdir/pkg/<br />
}<br />
<br />
#Download and place <code>hsfmodem_7.60.00.06oem_i386.deb</code> and the <code>PKGBUILD</code> in a new folder, and run makepkg to create the package. See [[Arch Build System]] for details on building packages.<br />
#Run <code>hsfconfig</code> as root to build the module and initialise the modem. A reboot is required before the modem can be initialised. Run <code>hsfconfig</code> again after reboot.<br />
#The modules are automatically loaded and a <code>/dev/modem</code> symlink is setup for use with the modem. Now use <code>wvdial</code> or other dialer programs to connect to the internet.<br />
<br />
==Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Card Reader==<br />
The Ricoh card reader should work out of the box, as long as '''MOD_AUTOLOAD''' is set to '''yes''' in ''/etc/rc.conf''. Assuming you use a HAL-aware desktop (GNOME, KDE, etc.), when a memory card is inserted, the kernel should automatically load the '''mmc_core/mmc_block''' modules and mount the new filesystem according to your desktop's automount settings. <br />
<br />
This has been confirmed with the following card types:<br />
* SD Card<br />
<br />
==Synaptics Touchpad==<br />
The Synaptics touchpad should provide basic functions out-of-the-box, however if you would like to use the scroll zones and enable other advanced features, please refer to the [[Touchpad_Synaptics | Synaptics Touchpad]] wiki.<br />
<br />
=Power Management=<br />
<br />
==ACPI Hibernation/Suspend with pm-utils==<br />
The powersave scripts have been officially replaced by [http://www.archlinux.org/packages/search/?q=pm-utils pm-utils]. Refer to the [[Pm-utils]] wiki for detailed instructions.<br />
<br />
'''''Note:''''' ATI video card owners must also add '''vga=0''' to the kernel options in <tt>/boot/grub/menu.lst</tt> in order to resume from suspend2ram. For exmaple:<br />
<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda3 resume=/dev/sda2 ro '''''vga=0'''''<br />
initrd /kernel26.img<br />
<br />
==CPU Frequency Scaling with cpufrequtils==<br />
<br />
Refer to the [[Cpufrequtils]] wiki for step-by-step instructions.<br />
<br />
= Multimedia Buttons & Fn Hotkeys =<br />
Unfortunately, configuring multimedia buttons and function keys on your laptop can be complicated process. Factors that must be taken into consideration include your choice of Desktop Environment (or lack thereof) and the actions you wish to bind to the special buttons or keys. For a detailed explanation of what is required, please refer to the [[Hotkeys]] wiki.<br />
<br />
The following tips may offer some assistance in getting started.<br />
<br />
== Multimedia Buttons ==<br />
For the most part, the Volume and Playback buttons should be recognized as an unassigned key by the Linux kernel. In which case, all that is necessary is to bind the button to an action. <br />
<br />
It is also worth noting that the multimedia buttons and equivalent Fn key shortcut (e.g. Fn+PgUp = Vol Up) will produce the same keycode, so if you configure the button, the Fn hotkey combo will execute the same action.<br />
<br />
=== GNOME ===<br />
The GNOME desktop provides an easy method for binding multimedia keys to their appropriate action. <br />
<br />
# Browse to '''System -> Preferences -> Keyboard Shortcuts''' and scroll down to the '''Sound''' section.<br />
# Click on an item (e.g. Mute) and then press the corresponding multimedia button<br />
# Repeat this process for all of the multimedia buttons<br />
<br />
The volume buttons should now work system-wide, and the playback buttons will now work in media players such as Rhythmbox and Exaile.<br />
<br />
=== Openbox and other Window Managers ===<br />
The <tt>xbindkeys</tt> utility is highly recommended for lightweight desktops such as Openbox--refer to the [[Hotkeys]] wiki for information. <br />
<br />
The following is an example ''~/.xbindkeysrc'' config file, making use of the multimedia buttons:<br />
<pre><br />
# vol up<br />
"amixer set Master 2dB+ unmute"<br />
m:0x10 + c:176<br />
# vol dn<br />
"amixer set Master 2dB- unmute"<br />
m:0x10 + c:174<br />
# vol mute<br />
"amixer set Master mute"<br />
m:0x10 + c:160<br />
# play/pause<br />
"audacious -t"<br />
m:0x10 + c:162<br />
# back<br />
"audacious -r"<br />
m:0x10 + c:144<br />
# forward<br />
"audacious -f"<br />
m:0x10 + c:153<br />
# stop<br />
"audacious -s"<br />
m:0x10 + c:164<br />
</pre><br />
<br />
== Function (Fn) Hotkeys ==<br />
Function keys seem to be less standardized than the Volume/Playback buttons, and therefore it can be difficult to get all of them working properly. For example, the Standby shortcut (Fn+ESC) may be recognized while at the same time the Hibernate shortcut (Fn+F1) is not. To make matters more confusing, it appears that some Fn keys such as those that adjust the LCD brightness are controlled by the BIOS, independent of the Operating System. Again, the [[Hotkeys]] wiki is highly recommended reading.<br />
<br />
The following example shows how one can configure the Dell Media Direct button, Eject (Fn+F10) and Hibernate (Fn+F1) hotkeys to execute specific commands:<br />
<br />
First, assign kernel keycodes to the Media Direct button and Fn hotkeys, using the ''/etc/rc.local'' script (which is executed before X loads):<br />
#!/bin/bash<br />
#<br />
# /etc/rc.local: Local multi-user startup script.<br />
#<br />
setkeycodes e009 122 # e009 eject fn<br />
setkeycodes e012 130 # e012 mediadirect<br />
setkeycodes e00a 123 # e00a hibernate fn<br />
<br />
Then use the <tt>xbindkeys</tt> utility to bind the newly recognized keys to a custom action. Here's an ''~/.xbindkeysrc'' config file:<br />
<br />
# media direct button<br />
"streamtuner"<br />
m:0x10 + c:134<br />
# eject function hotkey<br />
"eject"<br />
m:0x10 + c:210 <br />
# hibernate function hotkey<br />
"sudo /usr/sbin/pm-hibernate"<br />
m:0x10 + c:209<br />
<br />
Finally, execute <tt>xbindkeys</tt> at startup by placing it in your .xinitrc (or appropriate startup file for your environment):<br />
xscreensaver -no-splash &<br />
eval `cat $HOME/.fehbg` &<br />
'''''xbindkeys &'''''<br />
#sleep 3<br />
pypanel &<br />
exec openbox<br />
<br />
As stated previously, it can be a complicated process involving lots of trial & error troubleshooting, but hopefully this will help you get started.<br />
<br />
=Resources=<br />
TuxMobil: [http://tuxmobil.org/mylaptops.html Linux Laptop & Notebook Installation Guides]<br />
<br />
TuxMobil: [http://tuxmobil.org/dell.html DELL Notebooks]<br />
<br />
Gentoo Wiki: [http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_6400 HARDWARE Dell Inspiron 6400]<br />
<br />
Gentoo Wiki: [http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_6400_Fixes_for_common_problems HARDWARE Dell Inspiron 6400 Fixes for common problems]<br />
<br />
<br />
<br />
=Comments=</div>Shastryhttps://wiki.archlinux.org/index.php?title=Dell_Inspiron_6400&diff=29665Dell Inspiron 64002007-09-21T20:49:14Z<p>Shastry: /* Conexant HDA D110 MDC V.92 modem (winmodem) */</p>
<hr />
<div>[[Category:Laptops (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
=Introduction=<br />
==Summary==<br />
The goal of this wiki is to provide a comprehensive guide for Dell Inspiron 6400 owners seeking to install Arch Linux. It will attempt to cover all facets of hardware management, including wireless networking and hotkey support. Although this guide has been written specifically for the Inspiron 6400, many of the sub-sections can be applied to other Dell Inspiron models, including: <br />
* Dell Inspiron e1405<br />
* Dell Inspiron 640m<br />
* Dell Inspiron e1705<br />
<br />
==From the original contributor==<br />
I will attempt to cover as much as possible, however please feel free to contribute to this guide as you feel necessary. I will be happy to answer any questions, but I am by no means a Linux expert so there's a good chance I won't know the answer either! ~Thayer ([[User:Thayer.w|thayer.w]]) (thayerw(at)gmail(dot)com)<br />
<br />
=Hardware Specifications=<br />
The 6400 series laptop is currently available in a number of configurations and this guide will attempt to cover them all. Refer to the list below to determine whether your configuration has been documented.<br />
<br />
*<span style="color:green;">Green items are confirmed to work</span><br />
*<span style="color:red;">Red items have yet to be confirmed and require a Wiki entry</span><br />
<br />
===Base Components===<br />
<br />
* Intel Core Duo and Core 2 Duo processors<br />
** T2500 (2GHz/667MHz FSB/2MB Cache)<br />
** T5600 (1.83GHz/667MHz FSB/2MB Cache)<br />
** T2050 (1.66GHz/667MHz FSB/2MB Cache)<br />
** T1350 (1.66GHz/667MHz FSB/2MB Cache)<br />
** T5200 (1.60GHz/667MHz FSB/2MB Cache)<br />
* 512MB/1GB/2GB 533MHz/667MHz DDR2 SDRAM Memory<br />
* 15.4" Widescreen Display<br />
** WXGA (1280 x 800)<br />
** <span style="color:green;">WSXGA 1280x800 with TrueLife™</span><br />
** <span style="color:green;">WSXGA+ 1680x1050 with TrueLife™</span><br />
* 80GB/100GB/120GB/160GB 5400/7200 RPM SATA Hard Drive<br />
* <span style="color:green;">8x CD/DVD+/-RW/DL+R</span><br />
* <span style="color:green;">Broadcom 440x 10/100 Ethernet</span><br />
* <span style="color:green;">Conexant HDA D110 MDC V.92 modem (winmodem)</span><br />
* <span style="color:green;">Sigmatel STAC 92xx Audio</span><br />
* <span style="color:green;">Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Card Reader</span><br />
* <span style="color:green;">4 USB 2.0 Ports</span><br />
* <span style="color:red;">Firewire port (IEEE 1394)</span><br />
* <span style="color:red;">1 ExpressCard Slot</span><br />
* <span style="color:green;">Synaptics touchpad with scroll zones</span><br />
<br />
===Video Options===<br />
<br />
* <span style="color:green;">128MB ATI Mobility Radeon X1300 with HyperMemory</span><br />
* <span style="color:green;">256MB ATI Mobility Radeon X1400 with Hypermemory</span><br />
* <span style="color:green;">256MB nVidia GeForce Go 7300 with TurboCache</span><br />
* <span style="color:green;">128MB Intel Graphics Media Accelerator 950</span><br />
<br />
===Wireless Options===<br />
<br />
* <span style="color:green;">Intel Pro/Wireless 3945ABG (802.11a/b/g)</span><br />
* <span style="color:green;">Dell Wireless 1390</span><br />
* <span style="color:green;">Dell Wireless 1500 Draft 802.11n Wireless (Intel 4965AGN)</span><br />
* <span style="color:green;">Dell Wireless 350 Bluetooth Module</span><br />
* <span style="color:green;">Dell Wireless 355 Bluetooth Module</span><br />
<br />
=Arch Installation=<br />
There are plenty of resources available to help new users install and configure a basic Arch Linux installation, including the [[Official_Arch_Linux_Install_Guide|Official Installation Guide]] and the [[Beginners_Guide|Beginners Guide]].<br />
<br />
That being said, the following tips are specific to the Dell Inspiron 6400 and may be of some help during installation.<br />
<br />
If an Ethernet (wired land-line) broadband internet connection is available it is highly recommended that Arch be installed with the smaller FTP ISO. If you plan to have a desktop environment (KDE, GNOME, etc) then the majority of the packages you require will come from the internet repositories and <em>not</em> the Arch CD itself. This method will get you up and running in the shortest amount of time. Simply download the FTP ISO, burn it to a CD and restart your computer.<br />
<br />
The following steps assume you are connected to the Internet with a wired Ethernet connection, as opposed to a wireless connection.<br />
<br />
==Boot the Arch Setup CD==<br />
If the laptop does not boot from the CD, reboot and press F12 at the DELL BIOS splash screen to access the boot menu. From there you can choose to boot from the CD/DVD drive.<br />
<br />
==Setup==<br />
For the most part, the default settings should be fine, however the following notes may be of assistance.<br />
<br />
===0 - Configure===<br />
Just follow the prompts, choosing the defaults when asked. Make sure you allow the setup to detect your basic hardware automatically when asked.<br />
<br />
===1 - Prepare Hard Disks===<br />
The following is an example partition table. The example hard drive is 100GB and is configured to run only Arch Linux. Your settings will vary depending on the size of your hard drive and the number of operating systems you plan to run.<br />
<br />
'''sda''' (100GB)<br />
'''sda1''' ext2 100MB /boot ''(the boot loader files and kernel images will be installed here)''<br />
'''sda2''' swap 2.1GB swap ''(this example notebook has 2GB of RAM and we want to leave room for suspend2disk (hibernation) functions)''<br />
'''sda3''' ext3 6GB / ''(root--everything else will go here except for the files in /home and /boot)''<br />
'''sda4''' ext3 90GB /home ''(it's actually less than 90GB because ext3 filesystems reserve space to avoid capacity problems, but you get the point)''<br />
<br />
===2 - Select Packages===<br />
*Choose a mirror ('''''ftp.nethat.com''''' works very well from Vancouver, BC @ 160kb/s)<br />
*Choose ''only'' the base packages<br />
*Select ''all'' packages by default<br />
<br />
===3 - Install Packages===<br />
*Answer ''yes'' to cache packages (default)<br />
*Grab a coffee, it's going to take a while to fetch 100MB of packages<br />
<br />
===4 - Configure System===<br />
Choose your preferred editor; either vim or nano. <br />
<br />
A few files can be left alone, but there are some changes worth mentioning:<br />
<br />
====rc.conf====<br />
*Change your locale if necessary, for example Canadians will want to use ''en_CA'':<br />
LOCALE="en_CA.utf8"<br />
*Change the timezone if necessary, for example:<br />
TIMEZONE="Canada/Pacific"<br />
*To get rid of that ever-so-annoying system beep, blacklist the PC speaker module:<br />
MOD_BLACKLIST=(pcspkr)<br />
*Change the hostname if you desire a unique name, for example:<br />
HOSTNAME="dublin"<br />
*If your Internet Service Provider assigns your IP address automatically (and most do), make sure ''eth0'' is set to ''dhcp'':<br />
lo="lo 127.0.0.1"<br />
'''eth0="dhcp"'''<br />
<br />
====hosts====<br />
Add a second line under localhost with your unique hostname (the same hostname you chose in rc.conf) in place of localhost, for example:<br />
127.0.0.1 localhost.localdomain localhost<br />
'''127.0.0.1 dublin.localdomain dublin'''<br />
<br />
====fstab====<br />
No changes should be necessary.<br />
<br />
====mkinitcpio.conf====<br />
No changes should be necessary.<br />
<br />
====modprobe.conf====<br />
No changes should be necessary.<br />
<br />
====resolv.conf====<br />
No changes should be necessary.<br />
<br />
====locale.gen====<br />
Uncomment the languages files you wish to use, including the one you configured under LOCALE in the rc.conf:<br />
#en_BW.UTF-8 UTF-8<br />
#en_BW ISO-8859-1<br />
'''en_CA.UTF-8 UTF-8'''<br />
'''en_CA ISO-8859-1'''<br />
#en_DK.UTF-8 UTF-8<br />
#en_DK ISO-8859-1<br />
<br />
Canadians should probably uncomment ''en_US, en_CA and en_GB''.<br />
<br />
====root password====<br />
Set a root password.<br />
<br />
====pacman mirrors====<br />
You can either use the same mirror you used to install the base packages, or you can choose a different one at this time. The mirror you select at this stage will be your default repository after installation is complete.<br />
<br />
===5 - Install Kernel===<br />
The default choices should be fine.<br />
<br />
===6 - Install Boot Loader===<br />
If you are installing Arch as the sole operating system on the notebook, just go with the default settings. If you are dual-booting with another OS, choose the options carefully to avoid problems with your existing settings.<br />
<br />
* When installing GRUB, you can also append '''vga=791''' to the kernel option to set your terminal (framebuffer) resolution to 1024x768, for example:<br />
kernel /vmlinuz26 root=/dev/sda3 ro '''vga=791'''<br />
<br />
===7 - Exit===<br />
Reboot, eject the CD and log into your new Arch Linux installation.<br />
<br />
==Synchronize Repositories and Update==<br />
When logging into Arch for the first time, it is a good idea to make sure the local package database is synchronized with the Arch software repositories and that all of your software is up to date. From the console, type:<br />
# pacman -Syu<br />
<br />
=Add Users=<br />
At this point you can add a local user account by typing:<br />
# useradd -m johndoe<br />
# passwd johndoe<br />
<br />
''The '''-m''' flag creates the user's /home directory and copies the default configuration files to it (from /etc/skel)''<br />
<br />
Note, you will not be able to use the '''sudo''' command with this account until you [[Sudo|install and configure sudo]].<br />
<br />
=Xorg=<br />
If you plan to install a desktop environment (e.g. GNOME, KDE, etc.) you must install and configure Xorg.<br />
<br />
===Installation===<br />
Install the necessary packages:<br />
# pacman -S xorg xterm hwd<br />
<br />
===Configuration===<br />
The <tt>hwd</tt> program (''Hardware Detect'') will examine your hardware and create a default configuration file for Xorg (''/etc/X11/xorg.conf''):<br />
# hwd -xa<br />
You should now have a working X setup, however the default configuration uses the generic VESA graphics driver. If you want to run your desktop at its native resolution (e.g. 1680x1050) and enable 3D acceleration, you'll need to install the appropriate driver for your video card. See the [[Dell_Inspiron_6400#Video|Video]] section below for detailed instructions.<br />
<br />
=Desktop Environments=<br />
Arch Linux supports a variety of desktop environments and window managers, all of which must be installed manually. Refer to the following list for more information:<br />
<br />
'''Openbox:''' [[Openbox|Openbox Wiki]]<br />
<br />
'''GNOME:''' [[GNOME|GNOME Wiki]]<br />
<br />
'''Xfce:''' [[Xfce|Xfce Wiki]]<br />
<br />
'''KDE:''' [[KDE|KDE Wiki]]<br />
<br />
'''KDEmod:''' Visit the KDEmod website at http://kdemod.ath.cx/ or see the [[KDEmod|KDEmod Wiki]] for more information.<br />
<br />
'''E17:''' [[E17|E17 Wiki]]<br />
<br />
'''Fluxbox:''' [[Fluxbox|Fluxbox Wiki]]<br />
<br />
=Hardware=<br />
<br />
==Audio==<br />
===Sigmatel/Intel Chipset===<br />
The Sigmatel audio chipset should be detected automatically during installation, requiring no input from the user. For example, the following kernel modules are configured in ''/etc/rc.conf'' by default:<br />
snd-mixer-oss snd-pcm-oss snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore<br />
<br />
====ALSA Audio Drivers====<br />
Refer to the [[ALSA]] wiki for general assistance with volume settings, group permissions, etc.<br />
<br />
====OSS Audio Drivers====<br />
See the [[OSS]] wiki for more information.<br />
<br />
==Video==<br />
===ATI X1300/X1400 Radeon Mobility===<br />
====Proprietary Driver (fglrx)====<br />
<br />
The fglrx ATI proprietary driver is available from the standard Arch repositories and is the simplest way to get full 3D acceleration and native resolutions on your notebook:<br />
# pacman -S fglrx<br />
Run the '''aticonfig''' tool to automatically add the appropriate settings to ''/etc/X11/xorg.conf'':<br />
# aticonfig --initial<br />
Lastly, we need to modify ''/etc/rc.conf'' and add the '''fglrx''' kernel driver to the MODULES section, for example:<br />
MODULES=('''fglrx''' b44 mii snd-mixer-oss ...)<br />
Reboot and confirm that the ATI driver is working by typing '''fglrxinfo''' in a terminal. The results should look something like this:<br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Mobility Radeon X1400<br />
OpenGL version string: 2.0.6473 (8.37.6)<br />
<br />
Further information can be found at the [[ATI]] wiki.<br />
<br />
====Open Source ATI Driver====<br />
<br />
Please refer to the [[ATI]] wiki for more information.<br />
<br />
===Intel Graphics Media Accelerator 950===<br />
====Open Source Intel Driver====<br />
<br />
Install the driver:<br />
# pacman -S xf86-video-intel<br />
<br />
Use '''''gft''''' to generate the Xorg ''Modeline'' values and then edit ''/etc/X11/xorg.conf'' and add these values to the ''Monitor'' section, for example:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "unknown"<br />
'''Modeline "800x600" 40.12 800 848 968 1056 600 601 605 628 #60Hz'''<br />
EndSection<br />
<br />
Lastly, add the following to the "Device" section, replacing the existing ''Driver'' value if present:<br />
<br />
VideoRam 229376<br />
Option "CacheLines" "1980"<br />
Driver "intel"<br />
<br />
===nVidia GeForce Go 7300===<br />
The [[NVIDIA|NVIDIA Driver Wiki]] works fine. A side note: When running Beryl/Compiz-Fusion, while opening multiple instances of FireFox, the entire window went black. Forcing AIGLX solved this.<br />
<br />
==Networking==<br />
<br />
===Broadcom 440x 10/100 Ethernet===<br />
The Broadcom Ethernet card should have out-of-the-box support. No configuration necessary.<br />
<br />
===Dell Wireless 1390===<br />
<br />
Dell does not offer native Linux drivers for the 1390 wireless card. Fortunately, '''ndiswrapper''' can be used to install the Windows driver:<br />
# pacman -S ndiswrapper<br />
<br />
Download the 1390 driver from the Dell website:<br />
wget http://ftp.us.dell.com/network/R140747.EXE<br />
<br />
Create a temp folder and extract the driver:<br />
mkdir ~/Dell1390<br />
mv R14070747.EXE ~/Dell1390 <br />
cd ~/Dell1390 <br />
unzip -a R14070747.EXE<br />
cd DRIVERS<br />
<br />
As root, configure ndiswrapper to use the Windows driver:<br />
# ndiswrapper -i bcmwl5.inf<br />
# ndiswrapper -l<br />
# ndiswrapper -m<br />
# modprobe ndiswrapper<br />
<br />
Test the new driver by typing '''iwlist scanning''' in a terminal.<br />
<br />
To load the driver automatically at each boot, add '''ndiswrapper''' to the MODULES array in ''/etc/rc.conf'', for example:<br />
MODULES=(fglrx '''ndiswrapper''' b44 mii ...)<br />
<br />
Finally, remove the temp folder used during installation:<br />
rm -rf ~/Dell1390<br />
<br />
===Dell Wireless 1500 Draft 802.11n Wireless (Intel 4965AGN)===<br />
Grab the driver packages:<br />
# pacman -S iwlwifi iwlwifi-4965-ucode<br />
Edit ''/etc/rc.conf'' as root and add '''iwl4965''' to the MODULES list:<br />
MODULES=(fglrx '''''iwl4965''''' b44 mii ...)<br />
Add '''wlan0="dchp"''' to the NETWORKING section:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''wlan0="dhcp"'''''<br />
If '''wlan0''' is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!wlan0''''')<br />
<br />
===Dell Wireless 350 Bluetooth Module===<br />
Install the bluetooth libraries and basic utilties:<br />
# pacman -S bluez-libs bluez-utils<br />
Add '''bluetooth''' to the DAEMONS list in ''/etc/rc.conf'', for example:<br />
DAEMONS=(syslog-ng powersaved '''bluetooth''' ipw3945d ...)<br />
Now, depending on your desktop environment, install the appropriate tools:<br />
<br />
For GNOME: <br />
# pacman -S gnome-bluetooth bluez-gnome<br />
For KDE:<br />
# pacman -S kdebluetooth<br />
<br />
===Dell Wireless 355 Bluetooth Module===<br />
The steps described above for Dell Wireless 350 Bluetooth Module work with Dell Wireless 355 Bluetooth Module too.<br />
<br />
===Intel PRO/Wireless 3945ABG===<br />
With the release of Intel's open source [http://intellinuxwireless.org/ iwlwifi driver], 3945 owners now have two choices for wireless drivers. As the iwlwifi project matures, the ipw3945 driver will become obsolete, however until that time it will remain below as a second alternative.<br />
<br />
Install and configure NetworkManager before attempting to install the Intel 3945 wireless drivers. Refer to the [[Networkmanager| Networkmanager Wiki]] for more information.<br />
<br />
====Method 1: iwlwifi driver====<br />
Grab the driver packages:<br />
# pacman -S iwlwifi iwlwifi-3945-ucode<br />
Edit ''/etc/rc.conf'' as root and add '''iwl3945''' to the MODULES list:<br />
MODULES=(fglrx '''''iwl3945''''' b44 mii ...)<br />
Add '''wlan0="dchp"''' to the NETWORKING section:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''wlan0="dhcp"'''''<br />
If '''wlan0''' is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!wlan0''''')<br />
<br />
====Method 2: ipw3945 driver====<br />
Grab the Intel 3945 driver packages:<br />
# pacman -S ipw3945<br />
Edit ''/etc/rc.conf'' as root and add '''ipw3945''' to the MODULES list:<br />
MODULES=(fglrx '''''ipw3945''''' b44 mii ...)<br />
Add '''eth1="dchp"''' to the NETWORKING section ''(Note: It is sometimes detected as eth2 instead of eth1, use '''ifconfig''' to verify yours and, if necessary add eth2="dhcp" instead)'':<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''eth1="dhcp"'''''<br />
If '''eth1''' (or '''eth2''') is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!eth1''''')<br />
Add '''ipw3945d''' to the DAEMONS list ''before'' the dhcdbd and networkmanager daemons:<br />
DAEMONS=(syslog-ng '''''ipw3945d''''' dhcdbd networkmanager alsa ...)<br />
<br />
==Conexant HDA D110 MDC V.92 modem (winmodem)==<br />
The Conexant modem requires the proprietary '''hsfmodem''' driver.<br />
Dell offers a debian package [http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R155004&SystemID=INSPIRONI6400/E1505&servicetag=&os=UBLN&osl=en&deviceid=8593&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=1&libid=20&fileid=206745 hsfmodem_7.60.00.06oem_i386.deb] at their [http://support.dell.com/ support site] that works at '''full speed''', unlike the trial version from Linuxant which works at 14.4kbps.<br />
<br />
The following '''PKGBUILD''' can be used to create a '''hsfmodem''' package from the debian package:<br />
pkgname=hsfmodem<br />
pkgver=7.60.00.06oem<br />
pkgrel=1<br />
pkgdesc="Conexant dialup modem driver by dell"<br />
url="http://support.dell.com/"<br />
license=("unknown")<br />
arch=('i686')<br />
source=(${pkgname}_${pkgver}_i386.deb)<br />
md5sums=('80d38fccab347638fa7a2237b458b428')<br />
<br />
build() {<br />
cd $startdir/src/<br />
ar x ${pkgname}_${pkgver}_i386.deb<br />
tar xzf data.tar.gz<br />
cp -a usr etc $startdir/pkg/<br />
}<br />
<br />
#Download and place <code>hsfmodem_7.60.00.06oem_i386.deb</code> and the <code>PKGBUILD</code> in a new folder, and run makepkg to create the package. See [[Arch Build System]] for details on building packages.<br />
#Run <code>hsfconfig</code> as root to build the module and initialise the modem. A reboot is required before the modem can be initialised. Run <code>hsfconfig</code> again after reboot.<br />
#The modules are automatically loaded and a <code>/dev/modem</code> symlink is setup for use with the modem. Now use <code>wvdial</code> or other dialer programs to connect to the internet.<br />
<br />
==Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Card Reader==<br />
The Ricoh card reader should work out of the box, as long as '''MOD_AUTOLOAD''' is set to '''yes''' in ''/etc/rc.conf''. Assuming you use a HAL-aware desktop (GNOME, KDE, etc.), when a memory card is inserted, the kernel should automatically load the '''mmc_core/mmc_block''' modules and mount the new filesystem according to your desktop's automount settings. <br />
<br />
This has been confirmed with the following card types:<br />
* SD Card<br />
<br />
==Synaptics Touchpad==<br />
The Synaptics touchpad should provide basic functions out-of-the-box, however if you would like to use the scroll zones and enable other advanced features, please refer to the [[Touchpad_Synaptics | Synaptics Touchpad]] wiki.<br />
<br />
=Power Management=<br />
<br />
==ACPI Hibernation/Suspend with pm-utils==<br />
The powersave scripts have been officially replaced by [http://www.archlinux.org/packages/search/?q=pm-utils pm-utils]. Refer to the [[Pm-utils]] wiki for detailed instructions.<br />
<br />
'''''Note:''''' ATI video card owners must also add '''vga=0''' to the kernel options in <tt>/boot/grub/menu.lst</tt> in order to resume from suspend2ram. For exmaple:<br />
<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda3 resume=/dev/sda2 ro '''''vga=0'''''<br />
initrd /kernel26.img<br />
<br />
==CPU Frequency Scaling with cpufrequtils==<br />
<br />
Refer to the [[Cpufrequtils]] wiki for step-by-step instructions.<br />
<br />
= Multimedia Buttons & Fn Hotkeys =<br />
Unfortunately, configuring multimedia buttons and function keys on your laptop can be complicated process. Factors that must be taken into consideration include your choice of Desktop Environment (or lack thereof) and the actions you wish to bind to the special buttons or keys. For a detailed explanation of what is required, please refer to the [[Hotkeys]] wiki.<br />
<br />
The following tips may offer some assistance in getting started.<br />
<br />
== Multimedia Buttons ==<br />
For the most part, the Volume and Playback buttons should be recognized as an unassigned key by the Linux kernel. In which case, all that is necessary is to bind the button to an action. <br />
<br />
It is also worth noting that the multimedia buttons and equivalent Fn key shortcut (e.g. Fn+PgUp = Vol Up) will produce the same keycode, so if you configure the button, the Fn hotkey combo will execute the same action.<br />
<br />
=== GNOME ===<br />
The GNOME desktop provides an easy method for binding multimedia keys to their appropriate action. <br />
<br />
# Browse to '''System -> Preferences -> Keyboard Shortcuts''' and scroll down to the '''Sound''' section.<br />
# Click on an item (e.g. Mute) and then press the corresponding multimedia button<br />
# Repeat this process for all of the multimedia buttons<br />
<br />
The volume buttons should now work system-wide, and the playback buttons will now work in media players such as Rhythmbox and Exaile.<br />
<br />
=== Openbox and other Window Managers ===<br />
The <tt>xbindkeys</tt> utility is highly recommended for lightweight desktops such as Openbox--refer to the [[Hotkeys]] wiki for information. <br />
<br />
The following is an example ''~/.xbindkeysrc'' config file, making use of the multimedia buttons:<br />
<pre><br />
# vol up<br />
"amixer set Master 2dB+ unmute"<br />
m:0x10 + c:176<br />
# vol dn<br />
"amixer set Master 2dB- unmute"<br />
m:0x10 + c:174<br />
# vol mute<br />
"amixer set Master mute"<br />
m:0x10 + c:160<br />
# play/pause<br />
"audacious -t"<br />
m:0x10 + c:162<br />
# back<br />
"audacious -r"<br />
m:0x10 + c:144<br />
# forward<br />
"audacious -f"<br />
m:0x10 + c:153<br />
# stop<br />
"audacious -s"<br />
m:0x10 + c:164<br />
</pre><br />
<br />
== Function (Fn) Hotkeys ==<br />
Function keys seem to be less standardized than the Volume/Playback buttons, and therefore it can be difficult to get all of them working properly. For example, the Standby shortcut (Fn+ESC) may be recognized while at the same time the Hibernate shortcut (Fn+F1) is not. To make matters more confusing, it appears that some Fn keys such as those that adjust the LCD brightness are controlled by the BIOS, independent of the Operating System. Again, the [[Hotkeys]] wiki is highly recommended reading.<br />
<br />
The following example shows how one can configure the Dell Media Direct button, Eject (Fn+F10) and Hibernate (Fn+F1) hotkeys to execute specific commands:<br />
<br />
First, assign kernel keycodes to the Media Direct button and Fn hotkeys, using the ''/etc/rc.local'' script (which is executed before X loads):<br />
#!/bin/bash<br />
#<br />
# /etc/rc.local: Local multi-user startup script.<br />
#<br />
setkeycodes e009 122 # e009 eject fn<br />
setkeycodes e012 130 # e012 mediadirect<br />
setkeycodes e00a 123 # e00a hibernate fn<br />
<br />
Then use the <tt>xbindkeys</tt> utility to bind the newly recognized keys to a custom action. Here's an ''~/.xbindkeysrc'' config file:<br />
<br />
# media direct button<br />
"streamtuner"<br />
m:0x10 + c:134<br />
# eject function hotkey<br />
"eject"<br />
m:0x10 + c:210 <br />
# hibernate function hotkey<br />
"sudo /usr/sbin/pm-hibernate"<br />
m:0x10 + c:209<br />
<br />
Finally, execute <tt>xbindkeys</tt> at startup by placing it in your .xinitrc (or appropriate startup file for your environment):<br />
xscreensaver -no-splash &<br />
eval `cat $HOME/.fehbg` &<br />
'''''xbindkeys &'''''<br />
#sleep 3<br />
pypanel &<br />
exec openbox<br />
<br />
As stated previously, it can be a complicated process involving lots of trial & error troubleshooting, but hopefully this will help you get started.<br />
<br />
=Resources=<br />
TuxMobil: [http://tuxmobil.org/mylaptops.html Linux Laptop & Notebook Installation Guides]<br />
<br />
TuxMobil: [http://tuxmobil.org/dell.html DELL Notebooks]<br />
<br />
Gentoo Wiki: [http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_6400 HARDWARE Dell Inspiron 6400]<br />
<br />
Gentoo Wiki: [http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_6400_Fixes_for_common_problems HARDWARE Dell Inspiron 6400 Fixes for common problems]<br />
<br />
<br />
<br />
=Comments=</div>Shastryhttps://wiki.archlinux.org/index.php?title=Dell_Inspiron_6400&diff=29663Dell Inspiron 64002007-09-21T20:43:37Z<p>Shastry: /* Conexant HDA D110 MDC V.92 modem (winmodem) */</p>
<hr />
<div>[[Category:Laptops (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
=Introduction=<br />
==Summary==<br />
The goal of this wiki is to provide a comprehensive guide for Dell Inspiron 6400 owners seeking to install Arch Linux. It will attempt to cover all facets of hardware management, including wireless networking and hotkey support. Although this guide has been written specifically for the Inspiron 6400, many of the sub-sections can be applied to other Dell Inspiron models, including: <br />
* Dell Inspiron e1405<br />
* Dell Inspiron 640m<br />
* Dell Inspiron e1705<br />
<br />
==From the original contributor==<br />
I will attempt to cover as much as possible, however please feel free to contribute to this guide as you feel necessary. I will be happy to answer any questions, but I am by no means a Linux expert so there's a good chance I won't know the answer either! ~Thayer ([[User:Thayer.w|thayer.w]]) (thayerw(at)gmail(dot)com)<br />
<br />
=Hardware Specifications=<br />
The 6400 series laptop is currently available in a number of configurations and this guide will attempt to cover them all. Refer to the list below to determine whether your configuration has been documented.<br />
<br />
*<span style="color:green;">Green items are confirmed to work</span><br />
*<span style="color:red;">Red items have yet to be confirmed and require a Wiki entry</span><br />
<br />
===Base Components===<br />
<br />
* Intel Core Duo and Core 2 Duo processors<br />
** T2500 (2GHz/667MHz FSB/2MB Cache)<br />
** T5600 (1.83GHz/667MHz FSB/2MB Cache)<br />
** T2050 (1.66GHz/667MHz FSB/2MB Cache)<br />
** T1350 (1.66GHz/667MHz FSB/2MB Cache)<br />
** T5200 (1.60GHz/667MHz FSB/2MB Cache)<br />
* 512MB/1GB/2GB 533MHz/667MHz DDR2 SDRAM Memory<br />
* 15.4" Widescreen Display<br />
** WXGA (1280 x 800)<br />
** <span style="color:green;">WSXGA 1280x800 with TrueLife™</span><br />
** <span style="color:green;">WSXGA+ 1680x1050 with TrueLife™</span><br />
* 80GB/100GB/120GB/160GB 5400/7200 RPM SATA Hard Drive<br />
* <span style="color:green;">8x CD/DVD+/-RW/DL+R</span><br />
* <span style="color:green;">Broadcom 440x 10/100 Ethernet</span><br />
* <span style="color:green;">Conexant HDA D110 MDC V.92 modem (winmodem)</span><br />
* <span style="color:green;">Sigmatel STAC 92xx Audio</span><br />
* <span style="color:green;">Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Card Reader</span><br />
* <span style="color:green;">4 USB 2.0 Ports</span><br />
* <span style="color:red;">Firewire port (IEEE 1394)</span><br />
* <span style="color:red;">1 ExpressCard Slot</span><br />
* <span style="color:green;">Synaptics touchpad with scroll zones</span><br />
<br />
===Video Options===<br />
<br />
* <span style="color:green;">128MB ATI Mobility Radeon X1300 with HyperMemory</span><br />
* <span style="color:green;">256MB ATI Mobility Radeon X1400 with Hypermemory</span><br />
* <span style="color:green;">256MB nVidia GeForce Go 7300 with TurboCache</span><br />
* <span style="color:green;">128MB Intel Graphics Media Accelerator 950</span><br />
<br />
===Wireless Options===<br />
<br />
* <span style="color:green;">Intel Pro/Wireless 3945ABG (802.11a/b/g)</span><br />
* <span style="color:green;">Dell Wireless 1390</span><br />
* <span style="color:green;">Dell Wireless 1500 Draft 802.11n Wireless (Intel 4965AGN)</span><br />
* <span style="color:green;">Dell Wireless 350 Bluetooth Module</span><br />
* <span style="color:green;">Dell Wireless 355 Bluetooth Module</span><br />
<br />
=Arch Installation=<br />
There are plenty of resources available to help new users install and configure a basic Arch Linux installation, including the [[Official_Arch_Linux_Install_Guide|Official Installation Guide]] and the [[Beginners_Guide|Beginners Guide]].<br />
<br />
That being said, the following tips are specific to the Dell Inspiron 6400 and may be of some help during installation.<br />
<br />
If an Ethernet (wired land-line) broadband internet connection is available it is highly recommended that Arch be installed with the smaller FTP ISO. If you plan to have a desktop environment (KDE, GNOME, etc) then the majority of the packages you require will come from the internet repositories and <em>not</em> the Arch CD itself. This method will get you up and running in the shortest amount of time. Simply download the FTP ISO, burn it to a CD and restart your computer.<br />
<br />
The following steps assume you are connected to the Internet with a wired Ethernet connection, as opposed to a wireless connection.<br />
<br />
==Boot the Arch Setup CD==<br />
If the laptop does not boot from the CD, reboot and press F12 at the DELL BIOS splash screen to access the boot menu. From there you can choose to boot from the CD/DVD drive.<br />
<br />
==Setup==<br />
For the most part, the default settings should be fine, however the following notes may be of assistance.<br />
<br />
===0 - Configure===<br />
Just follow the prompts, choosing the defaults when asked. Make sure you allow the setup to detect your basic hardware automatically when asked.<br />
<br />
===1 - Prepare Hard Disks===<br />
The following is an example partition table. The example hard drive is 100GB and is configured to run only Arch Linux. Your settings will vary depending on the size of your hard drive and the number of operating systems you plan to run.<br />
<br />
'''sda''' (100GB)<br />
'''sda1''' ext2 100MB /boot ''(the boot loader files and kernel images will be installed here)''<br />
'''sda2''' swap 2.1GB swap ''(this example notebook has 2GB of RAM and we want to leave room for suspend2disk (hibernation) functions)''<br />
'''sda3''' ext3 6GB / ''(root--everything else will go here except for the files in /home and /boot)''<br />
'''sda4''' ext3 90GB /home ''(it's actually less than 90GB because ext3 filesystems reserve space to avoid capacity problems, but you get the point)''<br />
<br />
===2 - Select Packages===<br />
*Choose a mirror ('''''ftp.nethat.com''''' works very well from Vancouver, BC @ 160kb/s)<br />
*Choose ''only'' the base packages<br />
*Select ''all'' packages by default<br />
<br />
===3 - Install Packages===<br />
*Answer ''yes'' to cache packages (default)<br />
*Grab a coffee, it's going to take a while to fetch 100MB of packages<br />
<br />
===4 - Configure System===<br />
Choose your preferred editor; either vim or nano. <br />
<br />
A few files can be left alone, but there are some changes worth mentioning:<br />
<br />
====rc.conf====<br />
*Change your locale if necessary, for example Canadians will want to use ''en_CA'':<br />
LOCALE="en_CA.utf8"<br />
*Change the timezone if necessary, for example:<br />
TIMEZONE="Canada/Pacific"<br />
*To get rid of that ever-so-annoying system beep, blacklist the PC speaker module:<br />
MOD_BLACKLIST=(pcspkr)<br />
*Change the hostname if you desire a unique name, for example:<br />
HOSTNAME="dublin"<br />
*If your Internet Service Provider assigns your IP address automatically (and most do), make sure ''eth0'' is set to ''dhcp'':<br />
lo="lo 127.0.0.1"<br />
'''eth0="dhcp"'''<br />
<br />
====hosts====<br />
Add a second line under localhost with your unique hostname (the same hostname you chose in rc.conf) in place of localhost, for example:<br />
127.0.0.1 localhost.localdomain localhost<br />
'''127.0.0.1 dublin.localdomain dublin'''<br />
<br />
====fstab====<br />
No changes should be necessary.<br />
<br />
====mkinitcpio.conf====<br />
No changes should be necessary.<br />
<br />
====modprobe.conf====<br />
No changes should be necessary.<br />
<br />
====resolv.conf====<br />
No changes should be necessary.<br />
<br />
====locale.gen====<br />
Uncomment the languages files you wish to use, including the one you configured under LOCALE in the rc.conf:<br />
#en_BW.UTF-8 UTF-8<br />
#en_BW ISO-8859-1<br />
'''en_CA.UTF-8 UTF-8'''<br />
'''en_CA ISO-8859-1'''<br />
#en_DK.UTF-8 UTF-8<br />
#en_DK ISO-8859-1<br />
<br />
Canadians should probably uncomment ''en_US, en_CA and en_GB''.<br />
<br />
====root password====<br />
Set a root password.<br />
<br />
====pacman mirrors====<br />
You can either use the same mirror you used to install the base packages, or you can choose a different one at this time. The mirror you select at this stage will be your default repository after installation is complete.<br />
<br />
===5 - Install Kernel===<br />
The default choices should be fine.<br />
<br />
===6 - Install Boot Loader===<br />
If you are installing Arch as the sole operating system on the notebook, just go with the default settings. If you are dual-booting with another OS, choose the options carefully to avoid problems with your existing settings.<br />
<br />
* When installing GRUB, you can also append '''vga=791''' to the kernel option to set your terminal (framebuffer) resolution to 1024x768, for example:<br />
kernel /vmlinuz26 root=/dev/sda3 ro '''vga=791'''<br />
<br />
===7 - Exit===<br />
Reboot, eject the CD and log into your new Arch Linux installation.<br />
<br />
==Synchronize Repositories and Update==<br />
When logging into Arch for the first time, it is a good idea to make sure the local package database is synchronized with the Arch software repositories and that all of your software is up to date. From the console, type:<br />
# pacman -Syu<br />
<br />
=Add Users=<br />
At this point you can add a local user account by typing:<br />
# useradd -m johndoe<br />
# passwd johndoe<br />
<br />
''The '''-m''' flag creates the user's /home directory and copies the default configuration files to it (from /etc/skel)''<br />
<br />
Note, you will not be able to use the '''sudo''' command with this account until you [[Sudo|install and configure sudo]].<br />
<br />
=Xorg=<br />
If you plan to install a desktop environment (e.g. GNOME, KDE, etc.) you must install and configure Xorg.<br />
<br />
===Installation===<br />
Install the necessary packages:<br />
# pacman -S xorg xterm hwd<br />
<br />
===Configuration===<br />
The <tt>hwd</tt> program (''Hardware Detect'') will examine your hardware and create a default configuration file for Xorg (''/etc/X11/xorg.conf''):<br />
# hwd -xa<br />
You should now have a working X setup, however the default configuration uses the generic VESA graphics driver. If you want to run your desktop at its native resolution (e.g. 1680x1050) and enable 3D acceleration, you'll need to install the appropriate driver for your video card. See the [[Dell_Inspiron_6400#Video|Video]] section below for detailed instructions.<br />
<br />
=Desktop Environments=<br />
Arch Linux supports a variety of desktop environments and window managers, all of which must be installed manually. Refer to the following list for more information:<br />
<br />
'''Openbox:''' [[Openbox|Openbox Wiki]]<br />
<br />
'''GNOME:''' [[GNOME|GNOME Wiki]]<br />
<br />
'''Xfce:''' [[Xfce|Xfce Wiki]]<br />
<br />
'''KDE:''' [[KDE|KDE Wiki]]<br />
<br />
'''KDEmod:''' Visit the KDEmod website at http://kdemod.ath.cx/ or see the [[KDEmod|KDEmod Wiki]] for more information.<br />
<br />
'''E17:''' [[E17|E17 Wiki]]<br />
<br />
'''Fluxbox:''' [[Fluxbox|Fluxbox Wiki]]<br />
<br />
=Hardware=<br />
<br />
==Audio==<br />
===Sigmatel/Intel Chipset===<br />
The Sigmatel audio chipset should be detected automatically during installation, requiring no input from the user. For example, the following kernel modules are configured in ''/etc/rc.conf'' by default:<br />
snd-mixer-oss snd-pcm-oss snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore<br />
<br />
====ALSA Audio Drivers====<br />
Refer to the [[ALSA]] wiki for general assistance with volume settings, group permissions, etc.<br />
<br />
====OSS Audio Drivers====<br />
See the [[OSS]] wiki for more information.<br />
<br />
==Video==<br />
===ATI X1300/X1400 Radeon Mobility===<br />
====Proprietary Driver (fglrx)====<br />
<br />
The fglrx ATI proprietary driver is available from the standard Arch repositories and is the simplest way to get full 3D acceleration and native resolutions on your notebook:<br />
# pacman -S fglrx<br />
Run the '''aticonfig''' tool to automatically add the appropriate settings to ''/etc/X11/xorg.conf'':<br />
# aticonfig --initial<br />
Lastly, we need to modify ''/etc/rc.conf'' and add the '''fglrx''' kernel driver to the MODULES section, for example:<br />
MODULES=('''fglrx''' b44 mii snd-mixer-oss ...)<br />
Reboot and confirm that the ATI driver is working by typing '''fglrxinfo''' in a terminal. The results should look something like this:<br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Mobility Radeon X1400<br />
OpenGL version string: 2.0.6473 (8.37.6)<br />
<br />
Further information can be found at the [[ATI]] wiki.<br />
<br />
====Open Source ATI Driver====<br />
<br />
Please refer to the [[ATI]] wiki for more information.<br />
<br />
===Intel Graphics Media Accelerator 950===<br />
====Open Source Intel Driver====<br />
<br />
Install the driver:<br />
# pacman -S xf86-video-intel<br />
<br />
Use '''''gft''''' to generate the Xorg ''Modeline'' values and then edit ''/etc/X11/xorg.conf'' and add these values to the ''Monitor'' section, for example:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "unknown"<br />
'''Modeline "800x600" 40.12 800 848 968 1056 600 601 605 628 #60Hz'''<br />
EndSection<br />
<br />
Lastly, add the following to the "Device" section, replacing the existing ''Driver'' value if present:<br />
<br />
VideoRam 229376<br />
Option "CacheLines" "1980"<br />
Driver "intel"<br />
<br />
===nVidia GeForce Go 7300===<br />
The [[NVIDIA|NVIDIA Driver Wiki]] works fine. A side note: When running Beryl/Compiz-Fusion, while opening multiple instances of FireFox, the entire window went black. Forcing AIGLX solved this.<br />
<br />
==Networking==<br />
<br />
===Broadcom 440x 10/100 Ethernet===<br />
The Broadcom Ethernet card should have out-of-the-box support. No configuration necessary.<br />
<br />
===Dell Wireless 1390===<br />
<br />
Dell does not offer native Linux drivers for the 1390 wireless card. Fortunately, '''ndiswrapper''' can be used to install the Windows driver:<br />
# pacman -S ndiswrapper<br />
<br />
Download the 1390 driver from the Dell website:<br />
wget http://ftp.us.dell.com/network/R140747.EXE<br />
<br />
Create a temp folder and extract the driver:<br />
mkdir ~/Dell1390<br />
mv R14070747.EXE ~/Dell1390 <br />
cd ~/Dell1390 <br />
unzip -a R14070747.EXE<br />
cd DRIVERS<br />
<br />
As root, configure ndiswrapper to use the Windows driver:<br />
# ndiswrapper -i bcmwl5.inf<br />
# ndiswrapper -l<br />
# ndiswrapper -m<br />
# modprobe ndiswrapper<br />
<br />
Test the new driver by typing '''iwlist scanning''' in a terminal.<br />
<br />
To load the driver automatically at each boot, add '''ndiswrapper''' to the MODULES array in ''/etc/rc.conf'', for example:<br />
MODULES=(fglrx '''ndiswrapper''' b44 mii ...)<br />
<br />
Finally, remove the temp folder used during installation:<br />
rm -rf ~/Dell1390<br />
<br />
===Dell Wireless 1500 Draft 802.11n Wireless (Intel 4965AGN)===<br />
Grab the driver packages:<br />
# pacman -S iwlwifi iwlwifi-4965-ucode<br />
Edit ''/etc/rc.conf'' as root and add '''iwl4965''' to the MODULES list:<br />
MODULES=(fglrx '''''iwl4965''''' b44 mii ...)<br />
Add '''wlan0="dchp"''' to the NETWORKING section:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''wlan0="dhcp"'''''<br />
If '''wlan0''' is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!wlan0''''')<br />
<br />
===Dell Wireless 350 Bluetooth Module===<br />
Install the bluetooth libraries and basic utilties:<br />
# pacman -S bluez-libs bluez-utils<br />
Add '''bluetooth''' to the DAEMONS list in ''/etc/rc.conf'', for example:<br />
DAEMONS=(syslog-ng powersaved '''bluetooth''' ipw3945d ...)<br />
Now, depending on your desktop environment, install the appropriate tools:<br />
<br />
For GNOME: <br />
# pacman -S gnome-bluetooth bluez-gnome<br />
For KDE:<br />
# pacman -S kdebluetooth<br />
<br />
===Dell Wireless 355 Bluetooth Module===<br />
The steps described above for Dell Wireless 350 Bluetooth Module work with Dell Wireless 355 Bluetooth Module too.<br />
<br />
===Intel PRO/Wireless 3945ABG===<br />
With the release of Intel's open source [http://intellinuxwireless.org/ iwlwifi driver], 3945 owners now have two choices for wireless drivers. As the iwlwifi project matures, the ipw3945 driver will become obsolete, however until that time it will remain below as a second alternative.<br />
<br />
Install and configure NetworkManager before attempting to install the Intel 3945 wireless drivers. Refer to the [[Networkmanager| Networkmanager Wiki]] for more information.<br />
<br />
====Method 1: iwlwifi driver====<br />
Grab the driver packages:<br />
# pacman -S iwlwifi iwlwifi-3945-ucode<br />
Edit ''/etc/rc.conf'' as root and add '''iwl3945''' to the MODULES list:<br />
MODULES=(fglrx '''''iwl3945''''' b44 mii ...)<br />
Add '''wlan0="dchp"''' to the NETWORKING section:<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''wlan0="dhcp"'''''<br />
If '''wlan0''' is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!wlan0''''')<br />
<br />
====Method 2: ipw3945 driver====<br />
Grab the Intel 3945 driver packages:<br />
# pacman -S ipw3945<br />
Edit ''/etc/rc.conf'' as root and add '''ipw3945''' to the MODULES list:<br />
MODULES=(fglrx '''''ipw3945''''' b44 mii ...)<br />
Add '''eth1="dchp"''' to the NETWORKING section ''(Note: It is sometimes detected as eth2 instead of eth1, use '''ifconfig''' to verify yours and, if necessary add eth2="dhcp" instead)'':<br />
lo="lo 127.0.0.1"<br />
eth0="dhcp"<br />
'''''eth1="dhcp"'''''<br />
If '''eth1''' (or '''eth2''') is listed in the INTERFACES section, make sure it is disabled:<br />
INTERFACES=(lo !eth0 '''''!eth1''''')<br />
Add '''ipw3945d''' to the DAEMONS list ''before'' the dhcdbd and networkmanager daemons:<br />
DAEMONS=(syslog-ng '''''ipw3945d''''' dhcdbd networkmanager alsa ...)<br />
<br />
==Conexant HDA D110 MDC V.92 modem (winmodem)==<br />
The Conexant modem requires the proprietary '''hsfmodem''' driver.<br />
Dell offers a debian package [http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R155004&SystemID=INSPIRONI6400/E1505&servicetag=&os=UBLN&osl=en&deviceid=8593&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=1&libid=20&fileid=206745 hsfmodem_7.60.00.06oem_i386.deb] at their [http://support.dell.com/ support site] that works at '''full speed''', unlike the trial version from Linuxant which works at 14.4kbps.<br />
<br />
The following '''PKGBUILD''' can be used to create a '''hsfmodem''' package:<br />
pkgname=hsfmodem<br />
pkgver=7.60.00.06oem<br />
pkgrel=1<br />
pkgdesc="Conexant dialup modem driver by dell"<br />
url="http://support.dell.com/"<br />
license=("unknown")<br />
arch=('i686')<br />
source=(${pkgname}_${pkgver}_i386.deb)<br />
md5sums=('80d38fccab347638fa7a2237b458b428')<br />
<br />
build() {<br />
cd $startdir/src/<br />
ar x ${pkgname}_${pkgver}_i386.deb<br />
tar xzf data.tar.gz<br />
cp -a usr etc $startdir/pkg/<br />
}<br />
<br />
# Place PKGBUILD and hsfmodem_7.60.00.06oem_i386.deb in a new folder, and run makepkg to create the package. See ([[Arch Build System]]) for details on building packages.<br />
<br />
# run <code>hsfconfig</code> as root to build the module and initialise the modem. A reboot is required before the modem can be initialised. Run <code>hsfconfig</code> again after reboot.<br />
<br />
==Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Card Reader==<br />
The Ricoh card reader should work out of the box, as long as '''MOD_AUTOLOAD''' is set to '''yes''' in ''/etc/rc.conf''. Assuming you use a HAL-aware desktop (GNOME, KDE, etc.), when a memory card is inserted, the kernel should automatically load the '''mmc_core/mmc_block''' modules and mount the new filesystem according to your desktop's automount settings. <br />
<br />
This has been confirmed with the following card types:<br />
* SD Card<br />
<br />
==Synaptics Touchpad==<br />
The Synaptics touchpad should provide basic functions out-of-the-box, however if you would like to use the scroll zones and enable other advanced features, please refer to the [[Touchpad_Synaptics | Synaptics Touchpad]] wiki.<br />
<br />
=Power Management=<br />
<br />
==ACPI Hibernation/Suspend with pm-utils==<br />
The powersave scripts have been officially replaced by [http://www.archlinux.org/packages/search/?q=pm-utils pm-utils]. Refer to the [[Pm-utils]] wiki for detailed instructions.<br />
<br />
'''''Note:''''' ATI video card owners must also add '''vga=0''' to the kernel options in <tt>/boot/grub/menu.lst</tt> in order to resume from suspend2ram. For exmaple:<br />
<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda3 resume=/dev/sda2 ro '''''vga=0'''''<br />
initrd /kernel26.img<br />
<br />
==CPU Frequency Scaling with cpufrequtils==<br />
<br />
Refer to the [[Cpufrequtils]] wiki for step-by-step instructions.<br />
<br />
= Multimedia Buttons & Fn Hotkeys =<br />
Unfortunately, configuring multimedia buttons and function keys on your laptop can be complicated process. Factors that must be taken into consideration include your choice of Desktop Environment (or lack thereof) and the actions you wish to bind to the special buttons or keys. For a detailed explanation of what is required, please refer to the [[Hotkeys]] wiki.<br />
<br />
The following tips may offer some assistance in getting started.<br />
<br />
== Multimedia Buttons ==<br />
For the most part, the Volume and Playback buttons should be recognized as an unassigned key by the Linux kernel. In which case, all that is necessary is to bind the button to an action. <br />
<br />
It is also worth noting that the multimedia buttons and equivalent Fn key shortcut (e.g. Fn+PgUp = Vol Up) will produce the same keycode, so if you configure the button, the Fn hotkey combo will execute the same action.<br />
<br />
=== GNOME ===<br />
The GNOME desktop provides an easy method for binding multimedia keys to their appropriate action. <br />
<br />
# Browse to '''System -> Preferences -> Keyboard Shortcuts''' and scroll down to the '''Sound''' section.<br />
# Click on an item (e.g. Mute) and then press the corresponding multimedia button<br />
# Repeat this process for all of the multimedia buttons<br />
<br />
The volume buttons should now work system-wide, and the playback buttons will now work in media players such as Rhythmbox and Exaile.<br />
<br />
=== Openbox and other Window Managers ===<br />
The <tt>xbindkeys</tt> utility is highly recommended for lightweight desktops such as Openbox--refer to the [[Hotkeys]] wiki for information. <br />
<br />
The following is an example ''~/.xbindkeysrc'' config file, making use of the multimedia buttons:<br />
<pre><br />
# vol up<br />
"amixer set Master 2dB+ unmute"<br />
m:0x10 + c:176<br />
# vol dn<br />
"amixer set Master 2dB- unmute"<br />
m:0x10 + c:174<br />
# vol mute<br />
"amixer set Master mute"<br />
m:0x10 + c:160<br />
# play/pause<br />
"audacious -t"<br />
m:0x10 + c:162<br />
# back<br />
"audacious -r"<br />
m:0x10 + c:144<br />
# forward<br />
"audacious -f"<br />
m:0x10 + c:153<br />
# stop<br />
"audacious -s"<br />
m:0x10 + c:164<br />
</pre><br />
<br />
== Function (Fn) Hotkeys ==<br />
Function keys seem to be less standardized than the Volume/Playback buttons, and therefore it can be difficult to get all of them working properly. For example, the Standby shortcut (Fn+ESC) may be recognized while at the same time the Hibernate shortcut (Fn+F1) is not. To make matters more confusing, it appears that some Fn keys such as those that adjust the LCD brightness are controlled by the BIOS, independent of the Operating System. Again, the [[Hotkeys]] wiki is highly recommended reading.<br />
<br />
The following example shows how one can configure the Dell Media Direct button, Eject (Fn+F10) and Hibernate (Fn+F1) hotkeys to execute specific commands:<br />
<br />
First, assign kernel keycodes to the Media Direct button and Fn hotkeys, using the ''/etc/rc.local'' script (which is executed before X loads):<br />
#!/bin/bash<br />
#<br />
# /etc/rc.local: Local multi-user startup script.<br />
#<br />
setkeycodes e009 122 # e009 eject fn<br />
setkeycodes e012 130 # e012 mediadirect<br />
setkeycodes e00a 123 # e00a hibernate fn<br />
<br />
Then use the <tt>xbindkeys</tt> utility to bind the newly recognized keys to a custom action. Here's an ''~/.xbindkeysrc'' config file:<br />
<br />
# media direct button<br />
"streamtuner"<br />
m:0x10 + c:134<br />
# eject function hotkey<br />
"eject"<br />
m:0x10 + c:210 <br />
# hibernate function hotkey<br />
"sudo /usr/sbin/pm-hibernate"<br />
m:0x10 + c:209<br />
<br />
Finally, execute <tt>xbindkeys</tt> at startup by placing it in your .xinitrc (or appropriate startup file for your environment):<br />
xscreensaver -no-splash &<br />
eval `cat $HOME/.fehbg` &<br />
'''''xbindkeys &'''''<br />
#sleep 3<br />
pypanel &<br />
exec openbox<br />
<br />
As stated previously, it can be a complicated process involving lots of trial & error troubleshooting, but hopefully this will help you get started.<br />
<br />
=Resources=<br />
TuxMobil: [http://tuxmobil.org/mylaptops.html Linux Laptop & Notebook Installation Guides]<br />
<br />
TuxMobil: [http://tuxmobil.org/dell.html DELL Notebooks]<br />
<br />
Gentoo Wiki: [http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_6400 HARDWARE Dell Inspiron 6400]<br />
<br />
Gentoo Wiki: [http://gentoo-wiki.com/HARDWARE_Dell_Inspiron_6400_Fixes_for_common_problems HARDWARE Dell Inspiron 6400 Fixes for common problems]<br />
<br />
<br />
<br />
=Comments=</div>Shastryhttps://wiki.archlinux.org/index.php?title=Package_Maintainers&diff=23988Package Maintainers2007-05-11T04:15:08Z<p>Shastry: /* shastry */</p>
<hr />
<div>==brain0==<br />
==bjorn==<br />
{|border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border-style:solid; border-width:1px; border-collapse:collapse; empty-cells:show"<br />
|-<br />
! Real name || Email || Jabber || IRC || Forum || AUR || Arch<br />
|-<br />
| Bjørn Lindeijer || bjorn lindeijer nl || b lindeijer gmail com || b_lindeijer || [http://bbs.archlinux.org/profile.php?id=1086 Bjørn] || [http://aur.archlinux.org/packages.php?K=bjorn&SeB=m bjorn] || i686<br />
|}<br />
<br />
==codemac==<br />
===Contact Info===<br />
{|border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border-style:solid; border-width:1px; border-collapse:collapse; empty-cells:show"<br />
|-<br />
! Email || Jabber || IRC || Forum || AUR<br />
|-<br />
| [mailto:jeff@archlinux.org jeff@archlinux.org] || j@xmpp.us || [irc://irc.freenode.net/archlinux codemac@freenode#archlinux] || [http://bbs.archlinux.org/profile.php?id=3725 codemac] || [http://aur.archlinux.org/packages.php?K=codemac&SeB=m codemac]<br />
|}<br />
<br />
==DaNiMoTh==<br />
{|<br />
|style="padding-right:20px;"|Name<br />
| JJ. DaNiMoTh<br />
|-<br />
|E-Mail<br />
|jjdanimoth@gmail.com<br />
|-<br />
|GPG <br />
|[http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD8444743 Public Key]<br />
|-<br />
|Skype<br />
|DaNiMoTh<br />
|-<br />
|IRC<br />
|DaNiMoTh<br />
|-<br />
|Forum<br />
|[http://bbs.archlinux.org/profile.php?id=6339 DaNiMoTh]<br />
|-<br />
|AUR<br />
|[http://aur.archlinux.org/account.php?Action=DisplayAccount&ID=1464 DaNiMoTh]<br />
|-<br />
|Arch<br />
|i686<br />
|}<br />
<br />
==dejari==<br />
<br />
==dsa==<br />
<br />
{|border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border-style:solid; border-width:1px; border-collapse:collapse; empty-cells:show"<br />
|-<br />
! Real name || Email || Jabber || MSN || IRC || AUR || Arch<br />
|-<br />
| Douglas Soares de Andrade || dsandrade at gmail dot com || dsandrade at jabber.org || douglas at tuxfamily.org || [irc://irc.freenode.net/archlinux dsa@freenode#archlinux] || [http://aur.archlinux.org/packages.php?K=dsa&SeB=m dsa] || i686<br />
|}<br />
<br />
==dtw==<br />
<br />
==elasticdog==<br />
{|border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border-style:solid; border-width:1px; border-collapse:collapse; empty-cells:show"<br />
|-<br />
! Email || IRC || Forum || AUR<br />
|-<br />
| aaron [at] elasticdog dot com || [irc://irc.freenode.net/archlinux elasticdog@freenode#archlinux] || [http://bbs.archlinux.org/profile.php?id=3667 elasticdog] || [http://aur.archlinux.org/packages.php?K=elasticdog&SeB=m elasticdog]<br />
|}<br />
<br />
==ganja_guru==<br />
{|<br />
|style="padding-right:20px;"|Name<br />
|Varun Acharya<br />
|-<br />
|E-Mail<br />
|varun at archlinux dot org<br />
|-<br />
|Forum<br />
|[http://bbs.archlinux.org/profile.php?id=3040 ganja_guru]<br />
|-<br />
|IRC<br />
|ganja_guru<br />
|-<br />
|MSN<br />
|varun_acharya at hotmail dot com<br />
|-<br />
|Arch <br />
|x86_64<br />
|}<br />
<br />
==encelo==<br />
==filoktetes==<br />
==iphitus==<br />
==mOLOk==<br />
{|<br />
|style="padding-right:20px;"|Name<br />
| Alessio Bolognino<br />
|-<br />
|E-Mail<br />
|themolok@gmail.com<br />
|-<br />
|GPG <br />
|[http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xFE0270FB Public Key]<br />
|-<br />
|Jabber<br />
|themolok@gmail.com<br />
|-<br />
|IRC<br />
|mOLOk<br />
|-<br />
|Forum<br />
|[http://bbs.archlinux.org/profile.php?id=4253 mOLOk]<br />
|-<br />
|AUR<br />
|[http://aur.archlinux.org/packages.php?K=mOLOk&SeB=m mOLOk]<br />
|-<br />
|Arch<br />
| i686<br />
|}<br />
<br />
==Neverth==<br />
{|<br />
|style="padding-right:20px;"|Name<br />
|Mikko Seppälä<br />
|-<br />
|E-Mail<br />
|t-r-a-y@mbnet.fi<br />
|-<br />
|IRC<br />
|Neverther<br />
|-<br />
|Forum<br />
|[http://bbs.archlinux.org/profile.php?id=6101 Neverth]<br />
|-<br />
|AUR<br />
|[http://aur.archlinux.org/account.php?Action=AccountInfo&ID=2239 Neverth]<br />
|-<br />
|Arch<br />
|x86_64 (i686 if really needed)<br />
|}<br />
<br />
==Pierre==<br />
{|<br />
|style="padding-right:20px;"|Name<br />
|Pierre Schmitz<br />
|-<br />
|E-Mail<br />
|pierre@archlinux.de<br />
|-<br />
|Jabber<br />
|pierre@jabber.archlinux.de<br />
|-<br />
|Forum<br />
|[http://bbs.archlinux.org/profile.php?id=1760 Pierre]<br />
|-<br />
|AUR<br />
|[http://aur.archlinux.org/account.php?Action=AccountInfo&ID=16 Pierre]<br />
|-<br />
|Arch<br />
|x86_64, i686<br />
|}<br />
==pizzapunk==<br />
==phrakture==<br />
==pjmattal==<br />
==Romashka==<br />
{|<br />
|style="padding-right:20px;"|Name<br />
|Roman Kyrylych<br />
|-<br />
|E-Mail<br />
|Roman.Kyrylych@gmail.com<br />
|-<br />
|Jabber<br />
|Romashka@amessage.info<br>Roman.Kyrylych@gmail.com<br />
|-<br />
|ICQ<br />
|Romashka<br>295208414<br />
|-<br />
|IRC<br />
|Romashka<br />
|-<br />
|Forum<br />
|[http://bbs.archlinux.org/profile.php?id=4852 Romashka]<br />
|-<br />
|AUR<br />
|[http://aur.archlinux.org/packages.php?K=Romashka&SeB=m Romashka]<br />
|-<br />
|Arch<br />
|i686, soon x86_64<br />
|}<br />
<br />
==sergej==<br />
{|<br />
|Name<br />
|Sergej Pupykin<br />
|-<br />
|E-Mail<br />
|sergej@aur.archlinux.org<br>pupykins@gmail.com<br />
|-<br />
|Jabber<br />
|pupykins@gmail.com<br />
|-<br />
|IRC<br />
|sergej5<br />
|-<br />
|Forum<br />
|[http://bbs.archlinux.org/profile.php?id=5706 sergej]<br />
|-<br />
|AUR<br />
|[http://aur.archlinux.org/packages.php?K=sergej&PP=100&SeB=m sergej]<br />
|-<br />
|Arch<br />
|i686<br />
|-<br />
|}<br />
<br />
==shastry==<br />
{|<br />
|style="padding-right:20px;"|Name<br />
|Vinay S Shastry<br />
|-<br />
|E-Mail<br />
|vinayshastry@gmail.com<br>shastry@aur.archlinux.org<br />
|-<br />
|Jabber<br />
|shastry@jabber.org<br>vinayshastry@gmail.com<br />
|-<br />
|IRC<br />
|shastry<br />
|-<br />
|Forum<br />
|[http://bbs.archlinux.org/profile.php?id=1954 shastry]<br />
|-<br />
|AUR<br />
|[http://aur.archlinux.org/account.php?Action=AccountInfo&ID=67 shastry]<br />
|-<br />
|Arch<br />
|i686<br />
|}<br />
<br />
==Snowman==<br />
<br />
===Status: Active===<br />
<br />
===Supported Architecture: i686, x86_64===<br />
<br />
===Contact Info===<br />
{|border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border-style:solid; border-width:1px; border-collapse:collapse; empty-cells:show"<br />
|-<br />
! Name || Email || AUR || Forum ||IRC<br />
|-<br />
| Eric Bélanger||[mailto:belanger@ASTRO.UMontreal.CA belanger at astro dot umontreal dot ca] || [http://aur.archlinux.org/packages.php?K=Snowman&SeB=m Snowman]||[http://bbs.archlinux.org/profile.php?id=1940 Snowman] || [irc://irc.freenode.net/archlinux _Snowman_@freenode#archlinux]<br />
|}<br />
<br />
==swiergot==<br />
{|<br />
|style="padding-right:20px;"|Name<br />
|Jaroslaw Swierczynski<br />
|-<br />
|E-Mail<br />
|swiergot@gmail.com<br />
|-<br />
|Jabber<br />
|swiergot@gmail.com<br />
|-<br />
|IRC<br />
|swiergot<br />
|-<br />
|Forum<br />
|[http://bbs.archlinux.org/profile.php?id=2736 swiergot]<br />
|-<br />
|AUR<br />
|[http://aur.archlinux.org/account.php?Action=AccountInfo&ID=19 swiergot]<br />
|}<br />
<br />
==vegai==<br />
==voidnull==<br />
{|<br />
|style="padding-right:20px;"|Name<br />
|Giovanni Scafora<br />
|-<br />
|E-Mail<br />
|linuxmania@gmail.com<br>voidnull@aur.archlinux.org<br />
|-<br />
|Jabber<br />
|linuxmania@gmail.com<br />
|-<br />
|ICQ<br />
|voidnull<br>410599156<br />
|-<br />
|IRC<br />
|voidnull<br />
|-<br />
|Forum<br />
|[http://bbs.archlinux.org/profile.php?id=3497 voidnull]<br />
|-<br />
|AUR<br />
|[http://aur.archlinux.org/account.php?Action=AccountInfo&ID=61 voidnull]<br />
|-<br />
|Arch<br />
|i686<br />
|}<br />
<br />
==wizzomafizzo==<br />
==xterminus==</div>Shastryhttps://wiki.archlinux.org/index.php?title=Intel_GMA_945&diff=21635Intel GMA 9452007-03-05T08:59:49Z<p>Shastry: typo fix</p>
<hr />
<div>I did not find a Wiki file for the Graphics Chipset 945GM.<br />
So I decided to write down a brief description here how it works for me in Voodoo 0.8 <br />
<br />
<br />
How to get native 1400x1050 resolution ?<br />
<br />
- pacman the driver for i810 <br />
pacman -S xf86-video-i810<br />
<br />
- edit your /etc/X11/xorg.conf file<br />
<br />
Section "Device"<br />
Driver "i810"<br />
<br />
- Section "Screen"<br />
SubSection "Display"<br />
Depth 16<br />
Modes "1400x1050" "1280x1024" "800x600"<br />
<br />
- dowload the 915resolution Intel hack tool from here:<br />
http://www.geocities.com/stomljen/download.html<br />
untar, compile and install ( make, make install)<br />
<br />
- logout from startx<br />
<br />
- run <br />
915resolution -l<br />
select modes that you want to overwrite, like 49 and 45 in this case.<br />
<br />
915resolution 45 1280 1024 16<br />
915resolution 49 1400 1050 16<br />
( or something similar like you need ) <br />
- check what you have changed<br />
915resolution -l<br />
<br />
More detail: http://www.geocities.com/stomljen<br />
Startx again a you will get 1400x1050 and 1280x1024 in KDE.<br />
<br />
- Of course you want to load 915resolution at startup. <br />
Just add in /etc/rc.local these lines:<br />
<br />
/usr/sbin/915resolution 45 1280 1024 16<br />
/usr/sbin/915resolution 49 1400 1050 16</div>Shastryhttps://wiki.archlinux.org/index.php?title=Intel_GMA_945&diff=21634Intel GMA 9452007-03-05T08:58:47Z<p>Shastry: fix xorg.conf locatation</p>
<hr />
<div>I did not find a Wiki file for the Graphics Chipset 945GM.<br />
So I decided to write down a brief description here how it works for me in Voodoo 0.8 <br />
<br />
<br />
How to get native 1400x1050 resolution ?<br />
<br />
- pacman the driver for i810 <br />
pacman -S xf86-video-i810<br />
<br />
- edit your /etc/X11/xorg.conf file<br />
<br />
Section "Device"<br />
Driver "i810"<br />
<br />
- Section "Screen"<br />
SubSection "Display"<br />
Depth 16<br />
Modes "1400x1050" "1280x1024" "800x600"<br />
<br />
- dowload the 915resolution Intel hack tool from here:<br />
http://www.geocities.com/stomljen/download.html<br />
untar, compile and install ( make, make install)<br />
<br />
- logout from startx<br />
<br />
- run <br />
915resolution -l<br />
select modes that you want to overwrite, like 49 and 45 in this case.<br />
<br />
915resolution 45 1280 1024 16<br />
915resolution 49 1400 1050 16<br />
( or something similar like you need ) <br />
- check what you have changed<br />
914resolution -l<br />
<br />
More detail: http://www.geocities.com/stomljen<br />
Startx again a you will get 1400x1050 and 1280x1024 in KDE.<br />
<br />
- Of course you want to load 915resolution at startup. <br />
Just add in /etc/rc.local these lines:<br />
<br />
/usr/sbin/915resolution 45 1280 1024 16<br />
/usr/sbin/915resolution 49 1400 1050 16</div>Shastryhttps://wiki.archlinux.org/index.php?title=Advanced_Linux_Sound_Architecture&diff=21201Advanced Linux Sound Architecture2007-02-18T10:32:21Z<p>Shastry: added a common remedy for poor sound quality</p>
<hr />
<div>[[Category:Sound (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|ALSA Setup}}<br />
{{i18n_entry|Deutsch|ALSA Einrichten}}<br />
{{i18n_entry|Nederlands|ALSA instellen}}<br />
{{i18n_entry|Русский|ALSA Setup (Русский)}}<br />
{{i18n_entry|Slovensky|Nastavenie ALSA}}<br />
{{i18n_entry|Czech|ALSA (Česky)}}<br />
{{i18n_entry|中文(简体)|设置ALSA}}<br />
{{i18n_entry|עברית|הגדרת ALSA}}<br />
{{i18n_entry|Рolski|ALSA Setup (Polski)}}<br />
{{i18n_entry|Português do Brasil|Instalação ALSA}}<br />
{{i18n_entry|ไทย|ALSA Setup (ไทย)}}<br />
{{i18n_links_end}}<br />
<br />
This document tells how to get Alsa working with 2.6 kernels. Also see how to <br />
[[Allow_multiple_programs_to_play_sound_at_once|allow multiple programs to play sound at once]].<br />
<br />
==Installation==<br />
<br />
===Kernel drivers===<br />
<br />
Alsa has been included in the 2.6 kernels and is included in all arch '''kernel26*''' packages. If you build a custom kernel, do not forget to enable the correct alsa driver.<br />
<br />
All necessary modules should be detected and loaded automatically by udev. No special configuration has to be done unless you use ISA cards. '''NEVER''' use alsaconf if you have a PCI or ISAPNP sound card, the entries alsaconf adds to the modprobe.conf file might break udev's autodetection.<br />
<br />
===Userspace utilities===<br />
<br />
* Required for native alsa programs and administration<br />
# pacman -Sy alsa-lib alsa-utils<br />
* Recommended if you want to use applications with OSS sound support in combination with dmix:<br />
# pacman -S alsa-oss<br />
<br />
All alsa programs will most likely have alsa-lib as a dependency.<br />
<br />
==Configuration==<br />
<br />
===Making sure the sound modules are loaded===<br />
<br />
You can assume that udev will autodetect your sound properly, including the OSS compatibility modules. You can check this with the command<br />
<br />
$ lsmod|grep '^snd'<br />
snd_usb_audio 69696 0 <br />
snd_usb_lib 13504 1 snd_usb_audio<br />
snd_rawmidi 20064 1 snd_usb_lib<br />
snd_hwdep 7044 1 snd_usb_audio<br />
snd_seq_oss 29412 0 <br />
snd_seq_midi_event 6080 1 snd_seq_oss<br />
snd_seq 46220 4 snd_seq_oss,snd_seq_midi_event<br />
snd_seq_device 6796 3 snd_rawmidi,snd_seq_oss,snd_seq<br />
snd_pcm_oss 45216 0 <br />
snd_mixer_oss 15232 1 snd_pcm_oss<br />
snd_intel8x0 27932 0 <br />
snd_ac97_codec 87648 1 snd_intel8x0<br />
snd_ac97_bus 1792 1 snd_ac97_codec<br />
snd_pcm 76296 4 snd_usb_audio,snd_pcm_oss,snd_intel8x0,snd_ac97_codec<br />
snd_timer 19780 2 snd_seq,snd_pcm<br />
snd 43776 12 snd_usb_audio,snd_rawmidi,snd_hwdep,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer<br />
snd_page_alloc 7944 2 snd_intel8x0,snd_pcm<br />
<br />
If the output looks similar, your sound drivers have been successfully autodetected (note that in this case, snd_intel8x0 and snd_usb_audio are the drivers for the hardware devices). You might also want to check the directory '''/dev/snd''' for the right device files:<br />
<br />
$ ls -l /dev/snd/<br />
total 0<br />
crw-rw---- 1 root audio 116, 0 Apr 8 14:17 controlC0<br />
crw-rw---- 1 root audio 116, 32 Apr 8 14:17 controlC1<br />
crw-rw---- 1 root audio 116, 24 Apr 8 14:17 pcmC0D0c<br />
crw-rw---- 1 root audio 116, 16 Apr 8 14:17 pcmC0D0p<br />
crw-rw---- 1 root audio 116, 25 Apr 8 14:17 pcmC0D1c<br />
crw-rw---- 1 root audio 116, 56 Apr 8 14:17 pcmC1D0c<br />
crw-rw---- 1 root audio 116, 48 Apr 8 14:17 pcmC1D0p<br />
crw-rw---- 1 root audio 116, 1 Apr 8 14:17 seq<br />
crw-rw---- 1 root audio 116, 33 Apr 8 14:17 timer<br />
<br />
If you have at least the devices '''controlC0''' and '''pcmC0D0p''' or similar, then your sound modules have been detected and loaded properly.<br />
<br />
<br />
If this is not the case, your sound modules have not been detected properly. '''If you want any help on IRC or the forums, please post the output of the above commands.''' To solve this, you can try loading the modules manually:<br />
<br />
* Locate the module for your soundcard: http://www.alsa-project.org/alsa-doc/ The module will be prefixed with 'snd-' (for example: 'snd-via82xx').<br />
* Load modules:<br />
# modprobe snd-NAME-OF-MODULE<br />
# modprobe snd-pcm-oss<br />
* Check for the device files in '''/dev/snd''' (see above) and/or try if '''alsamixer''' or '''amixer''' have resonable output.<br />
* Add '''snd-pcm-oss''' and '''snd-NAME-OF-MODULE''' to the list of MODULES in '''/etc/rc.conf''' to ensure they are loaded next time.<br />
<br />
===Unmuting the channels and testing the sound card===<br />
<br />
In this section, we assume that you are logged in as root. If you want to perform these steps as an unprivileged user, you have to skip to the next section ''Setup Permissions'' first.<br />
<br />
* Unmute Soundcard<br />
<br />
It is recommended to use 'alsamixer' to configure your mixer and unmute the channels.<br><br><br />
'''NOTE:''' When using '''alsamixer''', be sure to '''unmute''' (push M) as well as bring volumes up by a specific percent amount i.e you need to use that % sign. '''alsamixer''' understands the percentage sign (%) not numbers. if you use a number (say 90)then '''alsamixer''' will take it as 100%.<br />
<br />
You can also use the 'amixer', but it is much less comfortable<br />
# amixer set Master 90% unmute<br />
# amixer set PCM 85% unmute<br />
<br />
* Try to play a wave file<br />
<br />
# aplay mywav.wav<br />
<br />
* [[Allow multiple programs to play sound at once]]<br />
<br />
===Setup Permissions===<br />
<br />
To be able to use the sound card as a user, follow these steps:<br />
<br />
* Add your user to the audio group:<br />
# gpasswd -a USERNAME audio<br />
<br />
* Log your user out and back in to ensure the audio group is loaded.<br />
<br />
===Restore Alsa Mixer settings at Startup===<br />
<br />
* Run 'alsactl' once to create '/etc/asound.state'<br />
<br />
alsactl store<br />
<br />
* Edit '/etc/rc.conf' and add 'alsa' to the list of daemons to start on bootup. This will store the mixer settings on every shutdown and restore them when you boot.<br />
<br />
===Getting SPDIF output===<br />
<br />
(from gralves from the gentoo forums)<br />
* In Gnome Volume Control, under the Options tab, change the IEC958 to PCM. This option can be enabled in the preferences.<br />
* If you don't have Gnome Volume Control installed, <br />
** Edit /etc/asound.state. This file is where alsasound store your mixer settings.<br />
** Find a line that says : 'IEC958 Playback Switch'. Near it you will find a line saying value:false. Change it to value:true <br />
** Now find this line: 'IEC958 Playback AC97-SPSA' and change value to 0. <br />
** Restart alsa.<br />
<br />
Alternative way to enable SPDIF output automatically on login (tested on SoundBlaster Audigy):<br />
* add following lines to /etc/rc.local:<br />
<br />
# Use COAX-digital output<br />
amixer set 'IEC958 Optical' 100 unmute<br />
amixer set 'Audigy Analog/Digital Output Jack' on<br />
<br />
You can see the name of your cards digital output name with:<br />
<br />
amixer scontrols<br />
<br />
==Still Getting No Sound?==<br />
<br />
Even though your drivers are installed correctly, and your volume is right, and nothing is muted, you might not hear anything! Adding the following line to <code>/etc/modprobe.conf</code> fixes this problem (with the <code>via82xx</code> driver, at least).<br />
<br />
options snd-NAME-OF-MODULE ac97_quirk=0<br />
<br />
==Poor Sound Quality?==<br />
<br />
If you experience poor sound quality, try setting the PCM volume (in alsamixer) to a level such that gain is 0.<br />
<br />
==KDE settings==<br />
* Start up KDE:<br />
# startx<br />
<br />
* Setup the volumes as you want them for this user (each user has their own settings):<br />
# alsamixer<br />
<br />
* <b>KDE 3.3</b> Go to the K Menu > Multimedia > KMix<br />
** Choose Settings > Configure KMix...<br />
** Un-check the option "Restore volumes on logon"<br />
** Press OK, and you should be all set. Now your volumes will be the same from the command line or within KDE.</div>Shastryhttps://wiki.archlinux.org/index.php?title=Advanced_Linux_Sound_Architecture&diff=14198Advanced Linux Sound Architecture2006-07-10T18:26:41Z<p>Shastry: /* Making sure the sound modules are loaded */</p>
<hr />
<div>[[Category:Audio/Video]][[Category:Installation]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|ALSA Setup}}<br />
{{i18n_entry|Deutsch|ALSA Einrichten}}<br />
{{i18n_entry|Nederlands|ALSA instellen}}<br />
{{i18n_entry|Русский|ALSA Setup (Русский)}}<br />
{{i18n_entry|Slovensky|Nastavenie ALSA}}<br />
{{i18n_entry|中文(简体)|设置ALSA}}<br />
{{i18n_entry|עברית|הגדרת ALSA}}<br />
{{i18n_entry|Рolski|ALSA Setup (Polski)}}<br />
{{i18n_entry|Português do Brasil|Instalação ALSA}}<br />
{{i18n_links_end}}<br />
<br />
This document tells how to get Alsa working with 2.6 kernels. Also see how to <br />
[[Allow_multiple_programs_to_play_sound_at_once|allow multiple programs to play sound at once]].<br />
<br />
==Installation==<br />
<br />
===Kernel drivers===<br />
<br />
Alsa has been included in the 2.6 kernels and is included in all arch '''kernel26*''' packages. If you build a custom kernel, do not forget to enable the correct alsa driver.<br />
<br />
All necessary modules should be detected and loaded automatically by udev. No special configuration has to be done unless you use ISA cards. '''NEVER''' use alsaconf if you have a PCI or ISAPNP sound card, the entries alsaconf adds to the modprobe.conf file might break udev's autodetection.<br />
<br />
===Userspace utilities===<br />
<br />
* Required for native alsa programs and administration<br />
# pacman -Sy alsa-lib alsa-utils<br />
* Recommended if you want to use applications with OSS sound support in combination with dmix:<br />
# pacman -S alsa-oss<br />
<br />
All alsa programs will most likely have alsa-lib as a dependency.<br />
<br />
==Configuration==<br />
<br />
===Making sure the sound modules are loaded===<br />
<br />
You can assume that udev will autodetect your sound properly, including the OSS compatibility modules. You can check this with the command<br />
<br />
$ lsmod|grep '^snd'<br />
snd_usb_audio 69696 0 <br />
snd_usb_lib 13504 1 snd_usb_audio<br />
snd_rawmidi 20064 1 snd_usb_lib<br />
snd_hwdep 7044 1 snd_usb_audio<br />
snd_seq_oss 29412 0 <br />
snd_seq_midi_event 6080 1 snd_seq_oss<br />
snd_seq 46220 4 snd_seq_oss,snd_seq_midi_event<br />
snd_seq_device 6796 3 snd_rawmidi,snd_seq_oss,snd_seq<br />
snd_pcm_oss 45216 0 <br />
snd_mixer_oss 15232 1 snd_pcm_oss<br />
snd_intel8x0 27932 0 <br />
snd_ac97_codec 87648 1 snd_intel8x0<br />
snd_ac97_bus 1792 1 snd_ac97_codec<br />
snd_pcm 76296 4 snd_usb_audio,snd_pcm_oss,snd_intel8x0,snd_ac97_codec<br />
snd_timer 19780 2 snd_seq,snd_pcm<br />
snd 43776 12 snd_usb_audio,snd_rawmidi,snd_hwdep,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer<br />
snd_page_alloc 7944 2 snd_intel8x0,snd_pcm<br />
<br />
If the output looks similar, your sound drivers have been successfully autodetected (note that in this case, snd_intel8x0 and snd_usb_audio are the drivers for the hardware devices). You might also want to check the directory '''/dev/snd''' for the right device files:<br />
<br />
$ ls -l /dev/snd/<br />
total 0<br />
crw-rw---- 1 root audio 116, 0 Apr 8 14:17 controlC0<br />
crw-rw---- 1 root audio 116, 32 Apr 8 14:17 controlC1<br />
crw-rw---- 1 root audio 116, 24 Apr 8 14:17 pcmC0D0c<br />
crw-rw---- 1 root audio 116, 16 Apr 8 14:17 pcmC0D0p<br />
crw-rw---- 1 root audio 116, 25 Apr 8 14:17 pcmC0D1c<br />
crw-rw---- 1 root audio 116, 56 Apr 8 14:17 pcmC1D0c<br />
crw-rw---- 1 root audio 116, 48 Apr 8 14:17 pcmC1D0p<br />
crw-rw---- 1 root audio 116, 1 Apr 8 14:17 seq<br />
crw-rw---- 1 root audio 116, 33 Apr 8 14:17 timer<br />
<br />
If you have at least the devices '''controlC0''' and '''pcmC0D0p''' or similar, then your sound modules have been detected and loaded properly.<br />
<br />
<br />
If this is not the case, your sound modules have not been detected properly. '''If you want any help on IRC or the forums, please post the output of the above commands.''' To solve this, you can try loading the modules manually:<br />
<br />
* Locate the module for your soundcard: http://www.alsa-project.org/alsa-doc/ The module will be prefixed with 'snd-' (for example: 'snd-via82xx').<br />
* Load modules:<br />
# modprobe snd-NAME-OF-MODULE<br />
# modprobe snd-pcm-oss<br />
* Check for the device files in '''/dev/snd''' (see above) and/or try if '''alsamixer''' or '''amixer''' have resonable output.<br />
* Add '''snd-pcm-oss''' and '''snd-NAME-OF-MODULE''' to the list of MODULES in '''/etc/rc.conf''' to ensure they are loaded next time.<br />
<br />
===Unmuting the channels and testing the sound card===<br />
<br />
In this section, we assume that you are logged in as root. If you want to perform these steps as an unprivileged user, you have to skip to the next section ''Setup Permissions'' first.<br />
<br />
* Unmute Soundcard<br />
<br />
It is recommended to use 'alsamixer' to configure your mixer and unmute the channels.<br><br />
'''NOTE:''' When using '''alsamixer''', be sure to '''unmute''' (push M) as well as bring volumes up.<br />
<br />
You can also use the 'amixer', but it is much less comfortable<br />
# amixer set Master 75 unmute<br />
# amixer set PCM 75 unmute<br />
<br />
* Try to play a wave file<br />
<br />
# aplay mywav.wav<br />
<br />
* [[Allow multiple programs to play sound at once]]<br />
<br />
===Setup Permissions===<br />
<br />
To be able to use the sound card as a user, follow these steps:<br />
<br />
* Add your user to the audio group:<br />
# gpasswd -a USERNAME audio<br />
<br />
* Log your user out and back in to ensure the audio group is loaded.<br />
<br />
===Restore Alsa Mixer settings at Startup===<br />
<br />
* Run 'alsactl' once to create '/etc/asound.state'<br />
<br />
alsactl store<br />
<br />
* Edit '/etc/rc.conf' and add 'alsa' to the list of daemons to start on bootup. This will store the mixer settings on every shutdown and restore them when you boot.<br />
<br />
===Getting SPDIF output===<br />
<br />
(from gralves from the gentoo forums)<br />
* In Gnome Volume Control, under the Options tab, change the IEC958 to PCM. This option can be enabled in the preferences.<br />
* If you don't have Gnome Volume Control installed, <br />
** Edit /etc/asound.state. This file is where alsasound store your mixer settings.<br />
** Find a line that says : 'IEC958 Playback Switch'. Near it you will find a line saying value:false. Change it to value:true <br />
** Now find this line: 'IEC958 Playback AC97-SPSA' and change value to 0. <br />
** Restart alsa.<br />
<br />
Alternative way to enable SPDIF output automatically on login (tested on SoundBlaster Audigy):<br />
* add following lines to /etc/rc.local:<br />
<br />
# Use COAX-digital output<br />
amixer set 'IEC958 Optical' 100 unmute<br />
amixer set 'Audigy Analog/Digital Output Jack' on<br />
<br />
You can see the name of your cards digital output name with:<br />
<br />
amixer scontrols<br />
<br />
==Still Getting No Sound?==<br />
<br />
Even though your drivers are installed correctly, and your volume is right, and nothing is muted, you might not hear anything! Adding the following line to <code>/etc/modprobe.conf</code> fixes this problem (with the <code>via82xx</code> driver, at least).<br />
<br />
options snd-NAME-OF-MODULE ac97_quirk=0<br />
<br />
<br />
<br />
==KDE settings==<br />
* Start up KDE:<br />
# startx<br />
<br />
* Setup the volumes as you want them for this user (each user has their own settings):<br />
# alsamixer<br />
<br />
* <b>KDE 3.3</b> Go to the K Menu > Multimedia > KMix<br />
** Choose Settings > Configure KMix...<br />
** Un-check the option "Restore volumes on logon"<br />
** Press OK, and you should be all set. Now your volumes will be the same from the command line or within KDE.</div>Shastryhttps://wiki.archlinux.org/index.php?title=Package_Maintainer_guidelines&diff=13093Package Maintainer guidelines2006-05-16T08:00:19Z<p>Shastry: </p>
<hr />
<div>[[Category:Package Management]]<br />
[[Category:AUR]]<br />
=The Trusted User (TU)=<br />
The '''Trusted User (TU)''' is a member of the community charged with<br />
keeping the AUR in working order. He/she maintains popular packages, and<br />
votes in administrative matters. A TU is elected from active community<br />
members by current TUs in a democratic process. TUs are the only<br />
members who have a final say in the direction of the AUR.<br />
<br />
The TUs are governed using the [http://archlinux.org/~simo/TUbylaws.html TUbylaws]<br />
<br />
=TU Duties=<br />
==The TU and UNSUPPORTED==<br />
<br />
The TUs should also make an effort to check package submissions in UNSUPPORTED for malicious code and good PKGBUILDing standards. In around 80% of cases the PKGBUILDs in the UNSUPPORTED are very simple and can be quickly checked for sanity and malicious code by the TU team.<br />
<br />
TUs should also check PKGBUILDs for minor mistakes, suggest corrections and improvements. The TU should endeavour to confirm that all pkgs follow the Arch Packging Guidelines/Standards and in doing so share their skills with other package builders in an effort to raise the standard of package building across the distro.<br />
<br />
TUs are also in an excellent position to document recommended practices.<br />
<br />
==="Flag Safe" guidelines===<br />
There is new functionality in the AUR that will allow TUs to mark pkgs as checked. However, users are still responsible for checking the PKGBUILDs themselves.<br />
<br />
==The TU and [community], Guidelines for Package Maintenance==<br />
<br />
=== Accessing the Repo ===<br />
<br />
Follow these instructions for uploading/modifying packages once you have become a TU:<br />
<ol><br />
<br />
<li>Install the "aurtools" package. Make sure you read the [[AURtools Tutorial]]</li><br />
<li>You will need to email your the output of "htpasswd -n" to whoever is in charge of the AUR CVS repo ( Paul Mattal = paul@mattal.com ). It comes with Apache.</li><br />
htpasswd -n <userid><br />
<li>Run the following commands to checkout the AUR CVS:<br><br />
<pre><br />
export CVSROOT=":pserver:<userid>@cvs.archlinux.org:/home/cvs-community"<br />
cvs login<br />
cvs co community</pre></li><br />
<br />
<li> To add a new package:</li><br />
<pre><br />
cvs add &lt;directory&gt;<br />
cd &lt;directory&gt;<br />
cvs add PKGBUILD<br />
</pre><br />
<li>Make a commit:</li><br />
cvs commit<br />
<li> To upload a binary package:</li><br />
Please note that AUR password is to be used with tupkg (NOT the CVS password)<br />
tupkg --user &lt;userid&gt; --password &lt;aur-password&gt; &lt;packagefile.pkg.tar.gz&gt;<br />
<br />
<li> After uploading a package and committing the build files, tag the files with this command:</li><br />
cvs tag -cFR CURRENT &lt;newpackagebuilddir&gt;<br />
Package changes should be available within 10 minutes. Verify everything was uploaded properly, then select the newly added or updated package in the web interface and set yourself as the maintainer.<br />
</ol><br />
<i>'''Note:''' Steps 5-7 can be run with communitypkg in one command as mentioned below in the AURtools tutorial.</i><br />
<br />
=== Adopting Packages ===<br />
A TU may adopt any package at any time. But because the TU's time is<br />
limited, he should try to only adopt popular packages. The voting<br />
mechanism in the AUR allows a TU to quickly gage which packages users<br />
want.<br />
<br />
If a package receives 25 votes, it may be adopted by a TU. A maintainer<br />
should adopt it via the web interface. That maintainer is then<br />
responsible for bug fixes and new version updates. Packages must be<br />
properly cleaned and fixed after adoption.<br />
<br />
=== Disowning packages ===<br />
You can disown packages by choosing "Disown Packages" in the AUR webinterface.<br />
If a TU can't or doesn't want to maintain a package any longer, a<br />
notice should be posted to the AUR Mailing List, so another TU can<br />
maintain it. A package can still be disowned even if no other TU wants<br />
to maintain it, but the TUs should try not to drop many packages (they<br />
shouldn't take on more than they have time for). If a package has<br />
become obsolete or isn't used any longer, it can be removed completely<br />
as well.<br />
<br />
If a package has been removed completely, it can be uploaded once again<br />
(fresh) to UNSUPPORTED, where a regular user can maintain the package<br />
instead of the TU.<br />
<br />
=== Deleting packages from [community] ===<br />
<br />
Removing a package from [community] is easy but not straightforward.<br />
After you've removed it from community, you could re-add it to <br />
unsupported (make sure to keep a copy!) and orphan it, for adoption by <br />
some other user in unsupported.<br />
<br />
To remove a package, all you really need to do is remove the CURRENT tag <br />
from the PKGBUILD. You do this by doing:<br />
<br />
cvs tag -d CURRENT PKGBUILD<br />
<br />
If you wish to remove the package materials from CVS for future <br />
revisions (because you don't want the old stuff lying around), you can <br />
do the following '''FROM THE PACKAGE'S DIRECTORY''' in your checked out <br />
version of the community repo (this is very important!):<br />
<br />
cd /path/to/<packagedirname><br />
cvs tag -dl CURRENT<br />
cvs rm -fl<br />
cvs commit<br />
<br />
'''BE VERY CAREFUL''' with CVS delete commands! By untagging current on the <br />
whole repo you risk removing '''EVERYTHING''' in [community]. I've suggested<br />
commands that hope to minimize that possibility, but there's <br />
still danger where delete is involved. Especially note that the tag <br />
delete takes '''IMMEDIATELY''' before committing, so be very careful.<br />
<br />
Also, due to weirdness of CVS, actually removing the package directory <br />
is impossible. It will still show up in a checked out version. This is <br />
CVS and we have to live with it, at least for now.<br />
<br />
Any TU can remove any package in [community] so keep this in mind and be <br />
extra super careful with this ability, lest you accidentally wipe out <br />
someone else's package.<br />
<br />
== AURtools ==<br />
To help the Trusted Users with their duties, the AURtools were written based on the '''tupkg''' tool. If you are Trusted User, it is highly recomended that you use the AURtools. The [[AURtools Tutorial]] was written to help you to get used to them.</div>Shastryhttps://wiki.archlinux.org/index.php?title=Package_Maintainer_guidelines&diff=13092Package Maintainer guidelines2006-05-16T07:57:29Z<p>Shastry: </p>
<hr />
<div>[[Category:Package Management]]<br />
[[Category:AUR]]<br />
=The Trusted User (TU)=<br />
The '''Trusted User (TU)''' is a member of the community charged with<br />
keeping the AUR in working order. He/she maintains popular packages, and<br />
votes in administrative matters. A TU is elected from active community<br />
members by current TUs in a democratic process. TUs are the only<br />
members who have a final say in the direction of the AUR.<br />
<br />
The TUs are governed using the [http://archlinux.org/~simo/TUbylaws.html TUbylaws]<br />
<br />
=TU Duties=<br />
==The TU and UNSUPPORTED==<br />
<br />
The TUs should also make an effort to check package submissions in UNSUPPORTED for malicious code and good PKGBUILDing standards. In around 80% of cases the PKGBUILDs in the UNSUPPORTED are very simple and can be quickly checked for sanity and malicious code by the TU team.<br />
<br />
TUs should also check PKGBUILDs for minor mistakes, suggest corrections and improvements. The TU should endeavour to confirm that all pkgs follow the Arch Packging Guidelines/Standards and in doing so share their skills with other package builders in an effort to raise the standard of package building across the distro.<br />
<br />
TUs are also in an excellent position to document recommended practices.<br />
<br />
==="Flag Safe" guidelines===<br />
There is new functionality in the AUR that will allow TUs to mark pkgs as checked. However, users are still responsible for checking the PKGBUILDs themselves.<br />
<br />
==The TU and [community], Guidelines for Package Maintenance==<br />
<br />
=== Accessing the Repo ===<br />
<br />
Follow these instructions for uploading/modifying packages once you have become a TU:<br />
<ol><br />
<br />
<li>Install the "aurtools" package. Make sure you read the [[AURtools Tutorial]]</li><br />
<li>You will need to email your the output of "htpasswd -n" to whoever is in charge of the AUR CVS repo ( Paul Mattal = paul@mattal.com ). It comes with Apache.</li><br />
htpasswd -n <userid><br />
<li>Run the following commands to checkout the AUR CVS:<br><br />
<pre><br />
export CVSROOT=":pserver:<userid>@cvs.archlinux.org:/home/cvs-community"<br />
cvs login<br />
cvs co community</pre></li><br />
<br />
<li> To add a new package:</li><br />
<pre><br />
cvs add &lt;directory&gt;<br />
cd &lt;directory&gt;<br />
cvs add PKGBUILD<br />
</pre><br />
<li>Make a commit:</li><br />
cvs commit<br />
<li> To upload a binary package:</li><br />
tupkg --user &lt;userid&gt; --password &lt;aur-password&gt; &lt;packagefile.pkg.tar.gz&gt;<br />
<br />
<li> After uploading a package and committing the build files, tag the files with this command:</li><br />
cvs tag -cFR CURRENT &lt;newpackagebuilddir&gt;<br />
Package changes should be available within 10 minutes. Verify everything was uploaded properly, then select the newly added or updated package in the web interface and set yourself as the maintainer.<br />
</ol><br />
<i>'''Note:''' Steps 5-7 can be run with communitypkg in one command as mentioned below in the AURtools tutorial.</i><br />
<br />
=== Adopting Packages ===<br />
A TU may adopt any package at any time. But because the TU's time is<br />
limited, he should try to only adopt popular packages. The voting<br />
mechanism in the AUR allows a TU to quickly gage which packages users<br />
want.<br />
<br />
If a package receives 25 votes, it may be adopted by a TU. A maintainer<br />
should adopt it via the web interface. That maintainer is then<br />
responsible for bug fixes and new version updates. Packages must be<br />
properly cleaned and fixed after adoption.<br />
<br />
=== Disowning packages ===<br />
You can disown packages by choosing "Disown Packages" in the AUR webinterface.<br />
If a TU can't or doesn't want to maintain a package any longer, a<br />
notice should be posted to the AUR Mailing List, so another TU can<br />
maintain it. A package can still be disowned even if no other TU wants<br />
to maintain it, but the TUs should try not to drop many packages (they<br />
shouldn't take on more than they have time for). If a package has<br />
become obsolete or isn't used any longer, it can be removed completely<br />
as well.<br />
<br />
If a package has been removed completely, it can be uploaded once again<br />
(fresh) to UNSUPPORTED, where a regular user can maintain the package<br />
instead of the TU.<br />
<br />
=== Deleting packages from [community] ===<br />
<br />
Removing a package from [community] is easy but not straightforward.<br />
After you've removed it from community, you could re-add it to <br />
unsupported (make sure to keep a copy!) and orphan it, for adoption by <br />
some other user in unsupported.<br />
<br />
To remove a package, all you really need to do is remove the CURRENT tag <br />
from the PKGBUILD. You do this by doing:<br />
<br />
cvs tag -d CURRENT PKGBUILD<br />
<br />
If you wish to remove the package materials from CVS for future <br />
revisions (because you don't want the old stuff lying around), you can <br />
do the following '''FROM THE PACKAGE'S DIRECTORY''' in your checked out <br />
version of the community repo (this is very important!):<br />
<br />
cd /path/to/<packagedirname><br />
cvs tag -dl CURRENT<br />
cvs rm -fl<br />
cvs commit<br />
<br />
'''BE VERY CAREFUL''' with CVS delete commands! By untagging current on the <br />
whole repo you risk removing '''EVERYTHING''' in [community]. I've suggested<br />
commands that hope to minimize that possibility, but there's <br />
still danger where delete is involved. Especially note that the tag <br />
delete takes '''IMMEDIATELY''' before committing, so be very careful.<br />
<br />
Also, due to weirdness of CVS, actually removing the package directory <br />
is impossible. It will still show up in a checked out version. This is <br />
CVS and we have to live with it, at least for now.<br />
<br />
Any TU can remove any package in [community] so keep this in mind and be <br />
extra super careful with this ability, lest you accidentally wipe out <br />
someone else's package.<br />
<br />
== AURtools ==<br />
To help the Trusted Users with their duties, the AURtools were written based on the '''tupkg''' tool. If you are Trusted User, it is highly recomended that you use the AURtools. The [[AURtools Tutorial]] was written to help you to get used to them.</div>Shastry