https://wiki.archlinux.org/api.php?action=feedcontributions&user=Blazeix&feedformat=atomArchWiki - User contributions [en]2024-03-28T17:30:21ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=MacBookPro10,x&diff=221022MacBookPro10,x2012-09-01T20:52:22Z<p>Blazeix: Removing Thunderbolt to Ethernet option, as afaict there is no thunderbolt support in current mainline. Verified that USB to Ethernet does work.</p>
<hr />
<div>[[Category:Apple]]<br />
{{Article summary start}}<br />
{{Article summary text|This wiki page should help you in getting your MacBook Pro with Retina Display to work with ArchLinux}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Official Arch Linux Install Guide}}<br />
{{Article summary wiki|Beginners Guide}}<br />
{{Article summary wiki|General Recommendations}}<br />
{{Article summary wiki|MacBook}}<br />
{{Article summary end}}<br />
<br />
== Overview ==<br />
This page should help you setting up ArchLinux on a MacBook Pro 10,1 with Retina display. Most of the steps are the same or very similar to the regular ArchLinux installation. However, because this is very new hardware, the setup requires a few different steps. <br />
The general installation guidelines are descibed in [[MacBook]].<br />
<br />
== Preparing for the Installation ==<br />
=== Preparing the Hard drive ===<br />
Assuming you want to have a dual boot with Mac OS X, boot into Mac OS and shrink it's partition with the Disk Utility. You can either create your Linux partition directly here, or do that later in Linux during the installation (using parted and mkfs).<br />
<br />
=== Getting wireless firmware ===<br />
In order for the WiFi chip to work, you need to get the firmware for it. There are various ways to do so. You can juts copy it from another b43 enabled archlinux box, extract it from Broadcoms driver using b43-fwcutter or get them through the b43-firmware package[https://aur.archlinux.org/packages.php?ID=21690] in AUR. In the end you should have a folder "b43" with lots of .fw files in it.<br />
<br />
== Installation ==<br />
<br />
=== Booting the live image ===<br />
Now, download the latest [[Archboot]] iso, write it to USB and boot from it by selecting it in the Apple boot loader. When it comes to the syslinux boot loader, press [tab] to edit the entry and append "noapic" or "nointremap" to the end to prevent a kernel panic during bootup. Currently (august 4, 2012), you also have to add "nomodeset".<br />
<br />
=== Connecting WiFi ===<br />
{{Note| You can skip this if you use the USB to ethernet adapter for the installation.}}<br />
After it has finished booting, enter a command line. Copy the entire folder with the firmware for your wireless card to /lib/firmware/. Now you should be able to use wpa_supplicant to connect to your WiFi network.<br />
<br />
=== The installation ===<br />
Run the installation wizard. When asked to partition your hard drive, create a small HFS partition. This is where you put the standalone grub package after the installation.<br />
{{Note| There are also other ways of booting the kernel. Refer to the [[MacBook]] page if you don't want to have a separate partition for grub but rather prefer to use refit/refind}}<br />
The rest of the installation is pretty much the same as usual. When choosing the bootloader, select grub2 and install it. Don't worry about any errors, we will create the bootable efi image on our own afterwards.<br />
<br />
After the installation has completed, directly copy the WiFi firmware to the installed system to /tmp/install/usr/lib/firmware.<br />
<br />
=== update the kernel ===<br />
Best results are obtained with the 3.5 kernel. To date, you can install it from [testing] or from the AUR linux-mainline. To get keyboard backlight and Bluetooth working, apply [http://follefuder.org/mbp10-3.5.patch this patch].<br />
<br />
=== Bootloader ===<br />
<br />
==== Direct EFI booting ====<br />
<br />
You can directly boot from the kernel, in which case there is no bootloader per se (the kernel is its own bootloader). This is described elsewhere in [[UEFI_Bootloaders]] section EFISTUB. In a nutshell, you have to put kernel and initramfs in a linux directory of your EFI partition (sda1), together with a file containing the kernel boot parameters.<br />
<br />
==== Grub2 ====<br />
<br />
Another solution is to install GRUB2. Edit /tmp/install/boot/grub/grub.cfg and edit the boot entry to load linux-mainline instead of the normal one. Also append "noapic" to the kernel line again.<br />
<br />
Now cd into /tmp/install and create the grub image by calling:<br />
grub-mkstandalone -o grub-standalone-x86_64.efi -d usr/lib/grub/x86_64-efi -O x86_64-efi -C xz boot/grub/grub.cfg<br />
This will create file called grub-standalone-x86_64.efi which contains grub and the config file. It is important to do cd into the right directory to make it pick up the config file and put it into the right place within the image.<br />
Copy this file to the HFS partition you have created earlier. Downside of this method is that you need to repeat this step whenever you want to change the grub config.<br />
<br />
Reboot the machine and boot into Mac OS. The HFS partition should be mounted and the grub standalone image in there. Follow the steps on this page to create the files needed to make the Apple boot loader pick up grub: http://mjg59.dreamwidth.org/7468.html.<br />
After creating the files, use "bless" on the grub image on the partition, if you want to boot automatically to Arch, append --setBoot.<br />
<br />
After another reboot, you should be able to select your installed Arch Linux by keeping the alt button pressed while booting in case you haven't used --setBoot while blessing.<br />
<br />
== Post installation ==<br />
=== Graphics ===<br />
The Laptop comes with an nVidia and a Intel chip. To date (august 4, 2012), the nouveau and intel drivers result in corrupted graphics. The nvidia proprietary driver works though (>=302-17). You can install it from [testing] (recommended) or from the AUR nvidia-beta-all, or download the nVidia installer from their website (not recommended, always install things through pacman to avoid file conflicts).<br />
<br />
=== Touchpad ===<br />
Because of the integrated button, the synaptics touchpad driver caused issues for me. Installing xf86-input-mtrack and adjusting its config produced way better results.<br />
<br />
=== Suspend ===<br />
Suspend should work fine with the nvidia drivers. In case you encounter problems with resuming, try the --quirk-dpms-on quirk. You can add a "99local" file in /etc/pm/config.d/ with the following content:<br />
<nowiki>DISPLAY_QUIRK_DPMS_ON="true"<br />
QUIRKOPTS="true"</nowiki><br />
<br />
== What doesn't work (early August 2012) ==<br />
<br />
* Nouveau driver (screen corruption; mode is correct) < solved ~ august 12, 2012.<br />
* i915 driver (screen corruption; mode is correct) < Solved august 13, 2012 (http://lists.freedesktop.org/archives/intel-gfx/2012-August/019522.html)<br />
* Backlight with nouveau and nvidia drivers<br />
* GMUX (not recognized by GMUX driver) < Solved august 13, 2012. Also makes suspend/resume w/ intel driver work (http://luna.vmars.tuwien.ac.at/~froe...p/apple-gmux.c)<br />
* Microphone (white noise at all times)<br />
* Suspend mode on lid close with nouveau and i915 (does not come out of suspend; blank screen). Solved on i915, see above.<br />
<br />
== Discussions ==<br />
<br />
Here are a couple of interesting threads:<br />
* http://ubuntuforums.org/showthread.php?t=2006475 page 8 and beyond<br />
* https://bbs.archlinux.org/viewtopic.php?id=144255&p=1</div>Blazeixhttps://wiki.archlinux.org/index.php?title=Frequently_asked_questions&diff=57466Frequently asked questions2009-01-08T19:19:03Z<p>Blazeix: added ivman option</p>
<hr />
<div>[[Category:About Arch (English)]]<br />
[[Category:FAQs (English)]]<br />
{{FAQ i18n Links}}<br />
<br />
Besides the questions covered below, you may find [[The Arch Way]], [[Arch Linux]], and [[Devland]] helpful. All three contain a good deal of information about Arch Linux.<br />
<br />
= General =<br />
<br />
==Q) I am a complete GNU/Linux beginner. Should I use Arch?==<br />
'''A)''' This question has had much debate. Arch is targeted at more-advanced GNU/Linux users, but some people feel "Arch is a good place to start". If you are a beginner and want to use Arch, just be warned that you must be willing to learn as well as accept the fact that Arch is largely a do-it-yourself distribution. It is the user who assembles the system, and controls what it will be. Before asking any question, do your own independent research by googling, searching the Wiki, and searching the forum (and reading past FAQs). If you do that, you should be fine. Also know that many people do not want to answer the same basic questions over and over, so you are exposing yourself to that environment. ''There is a reason these resources were created/made available to you in the first place.'' Many thousands of ''volunteered'' hours have been spent compiling this excellent information. Recommended reading: The Arch Linux [[Beginners Guide|Beginners' Guide]].<br />
<br />
==Q) I really like Arch, except the development team needs to implement ''feature X''.==<br />
'''A)''' Before going further, did you read [[The Arch Way]]? Have you provided the feature/solution? Does it conform to the Arch philosophy of ''minimalism'' and ''code-correctness over convenience''? Get involved, contribute your code/solution to the community. If it is well regarded by the community and development team, perhaps it will be merged. The Arch community thrives on contribution and sharing of code and tools.<br />
<br />
==Q) When will the new release be made?==<br />
'''A)''' Arch Linux releases are merely a snapshot of the /core repository, combined with various features or modifications to the installer script itself. The rolling release model keeps every Arch Linux system current and on the bleeding edge by issuing one command.<br />
<br />
For this reason, releases are not terribly important in Arch, because the rolling-release system makes new releases out of date as soon as a package has been updated. If you are looking to obtain the latest Arch Linux release, you do not need to reinstall. You simply run the ''pacman -Syu'' command and your system will be identical to what you would get with a brand-new install.<br />
<br />
For this same reason, new Arch Linux releases are not typically full of new and exciting features. New and exciting features are released as needed with the packages that are updated, and can be obtained immediately via ''pacman -Syu''.<br />
<br />
==Q) Is Arch Linux a stable distro? Will I get frequent breakage? ==<br />
'''A)''' The long and short answer is: It is largely as stable as ''you'' make it. <br />
<br />
You assemble your own Arch system, atop the simple base environment, and you control system upgrades. Obviously, a larger, more bloated system incorporating multitudes of packages, multiple toolkits and desktop environments would be more likely to experience configuration issues due to upstream changes than a slimmer, more simple system would. General UNIX competence, good system maintenance and upgrade practices also play a large role in system stability. Also recall that Arch packages are predominantly unpatched, so most issues are inherently upstream.<br />
Therefore, it is ''the user'' who is ultimately responsible for the stability of his own rolling release system. The user decides when to upgrade, and merges necessary changes when required. If the the user reaches out to the community for help, it is often provided in a timely manner. The difference between Arch and other distributions in this regard is that Arch is truly a 'do-it-yourself' distro; complaints of breakage are misguided and unproductive, since upstream changes are not the responsibility of Arch devs.<br />
<br />
==Q) What exactly ''is'' this 'BSD-style' init framework I keep hearing about? ==<br />
<br />
Part of BSD's 30+ year heritage is the simple init framework that it has incorporated and which has remained largely unchanged. (The SysV init implemented on GNU/Linux systems came much later.) The main difference is that Arch's BSD-style init uses a single file (/etc/rc.conf) to point to scripts within a single directory (etc/rc.d/) for all system services, regardless of runlevel. A sysV init on the other hand would use a directory for each runlevel:/etc/rc.0,1,2,3,4,5,6, with a convoluted array of symlinks within the directory; one for each service, and each symlink pointing to a corresponding script in the /etc/init.d/ directory. Needless to say, the SysV method is much more complex; it could easily contain dozens of symlinks in each /etc/rc. directory. Keeping in line with its simple philosophy, Arch uses the BSD-style init.<br />
<br />
==Q) Arch needs more press (i.e. advertisement)==<br />
'''A)''' Arch gets plenty of press as it is. The goal of Arch Linux is not to be large. The goal is to provide an elegant, minimalist and bleeding edge distribution focused on simplicity and code-correctness. Growth occurs naturally amongst the target user base. Trying to force growth will just cause problems.<br />
<br />
Similarly, the development model does not restrict natural growth. More users might mean more devs to work on Arch Linux. This may cause some organizational issues at the "top", but those will be dealt with when they arrive.<br />
<br />
<br />
<br />
==Q) Arch needs more devs==<br />
'''A)''' Possibly so. Feel free to volunteer your time! Visit the forums, IRC channel, and mailing lists, and see what needs to be done.<br />
There is always a need for documentation; contribute to the wiki.<br />
<br />
==Q) Why is Arch so slow? I thought it's supposed to be fast!==<br />
'''A)''' Make sure that your hostname is correctly set in /etc/hosts (i.e., that it matches the hostname in /etc/rc.conf. Have a look at "Configure the System" in The [[Beginners_Guide]]). If the hostnames do not match, applications may start up very slowly.<br />
<br />
==Q) Why is my internet so slow compared to other operating systems?==<br />
'''A)''' Is your network configured correctly? Have you double checked your /etc/rc.conf /etc/hosts and /etc/resolv.conf? Have a look at "Configure the System" in The [[Beginners_Guide]].<br />
<br />
=Package Management=<br />
<br />
==Q) I've found an error with Package X. What should I do?==<br />
'''A)''' First, you need to figure out if this error is something the Arch team can fix. Sometimes it's not (that Firefox crash may be the fault of the Mozilla team) - this is called an ''upstream error''. If it is an Arch problem, there is a series of steps you can take:<br />
#Search the forums for information. See if anyone else has noticed it.<br />
#Notify the package maintainer. Try a "pacman -Qi <package name>" for this info.<br />
#Post a bug report with detailed information at http://bugs.archlinux.org.<br />
#If you'd like, write a forum post detailing the problem and the fact that you have reported it already. This will help prevent a lot of people from reporting the same error.<br />
<br />
==Q) Will Arch have a database for pacman?==<br />
'''A)''' Possibly. There is discussion over the issue. <br><br />
http://bbs.archlinux.org/viewtopic.php?id=11193 <br><br />
http://bbs.archlinux.org/viewtopic.php?id=10898 <br><br />
Look at http://bugs.archlinux.org/task/5328, too.<br />
<br />
==Q) Arch packages need to use a unique naming convention. .pkg.tar.gz is too long and/or confusing==<br />
'''A)''' This has been discussed on the Arch mailing list. Some proposed a .pac file extension. As far as is currently known, there is no plan to change the package extension.<br />
As Tobias Kieslich, one of the Arch devs, put it, "A package '''is''' a gzipped tarball! And it can be opened, investigated and manipulated by any tar-capable application. Moreover, the mime-type is automatically detected correctly by most applications."<br />
<br />
==Q) Pacman needs a library so other applications can easily access package information==<br />
'''A)''' Since version 3.0.0, pacman has been the front-end to libalpm, the "Arch Linux Package Management" library. This library allows alternative front-ends to be written (for instance, a GUI front-end).<br />
<br />
==Q) Why doesn't Pacman have an official GUI front-end?==<br />
'''A)''' Did you read [[The Arch Way]] and [[Arch Linux]] and [[Devland]]?<br />
The answer is basically that the Arch dev team will not be providing one. Feel free to use one of those developed by users. There is a nice list of them on the [[UserContributionsPage]] in the links section, and a selective list on [[Pacman GUI Frontends]].<br />
<br />
==Q) Pacman needs Feature X!==<br />
'''A)''' Did you read [[The Arch Way]] and [[Arch Linux]] and [[Devland]]?<br />
The Arch philosophy is "Keep It Simple". If you think the idea has merit, and does not violate this simple litany, then by all means, discuss it on the forum [http://bbs.archlinux.org/ here]. You might also like to check [http://bugs.archlinux.org here]; it's a place for feature requests if you find it is important.<br />
<br />
However, the best way to get a feature added to Pacman or Arch Linux is to implement it yourself. There's no telling whether the patch will be officially accepted, but others will appreciate and test your effort.<br />
<br />
==Q) Arch needs a stable package branch==<br />
'''A)'''<br />
Never say never.<br />
Some of the many discussions on the topic: <br><br />
http://bbs.archlinux.org/viewtopic.php?id=11288<br />
<br><br />
http://archlinux.org/pipermail/arch/2007-November/016048.html<br />
<br />
==Q) What's the difference between all these repositories?==<br />
'''A)''' See [[The Arch Linux Repositories]].<br />
<br />
<br />
<br />
==Q) I just installed Package X. How do I start it?==<br />
'''A)''' If you're using a desktop environment like KDE or GNOME, the program should automatically show up in your menu. If you're trying to run the program from a terminal and don't know the binary name, try executing "pacman -Ql packagename | grep bin". A common problem for packages like Firefox or OpenOffice is that they are installed to /opt, which is not in your $PATH - you can "source /etc/profile" or logout/login to fix this.<br />
<br />
=Installation=<br />
<br />
==Q) Arch needs a better installer. Maybe a GUI installer.==<br />
'''A)''' The discussion of a "better" installer is a subjective opinion. The best way to cope with these issues it to fit the installer to "the Arch way". If this opinion on a better installer is backed with more-concrete arguments, it might be taken into account for further development of the installer. Since installation doesn't occur often (see the question above on rolling release), it is not a high priority for developers or users.<br />
However, two unofficial methods exist: [http://archie.dotsrc.org/ Archie Live CD] for XFCE (other desktops in development) and [http://user-contributions.org/wikis/userwiki/index.php?title=Arch_Linux_Office_Install_CD Arch Linux Office Install CD] for KDE.<br />
<br />
==Q) I installed Arch, and now I am at a bash login! What now?==<br />
'''A)''' Have a look at the Arch Linux [[Beginners_Guide]]<br />
<br />
==Q) Arch is touted as a distribution which is built up from a minimal base system, installing only what is required by the user. Isn't this possible with virtually any distribution? What makes Arch unique in this regard?==<br />
<br />
'''A)''' A few distributions may provide minimal installation methods similar in design to the Arch installation process. However, a few points must be noted:<br />
# Arch has been fundamentally designed as a lightweight, minimal environment upon which to build. <br />
# Whether the FTP or Core images are used, the only way to install Arch is by building up from this minimal base.<br />
# The installation, as well as the entire distribution is inherently a K.I.S.S. design approach, which makes it uniquely suitable for its target base of users.<br />
# The simple Arch installer is designed for a high level of transparency and the base system is manually configured by the user to their needed specifications.<br />
# Arch provides thoroughly complete documentation to guide one through this process of system assembly.<br />
<br />
=Other=<br />
<br />
==Q) I get an error every time I use pacman saying 'warning: current locale is invalid; using default "C" locale'. What do I do?==<br />
'''A)''' As the error message says, your locale isn't correctly configured. Have a look at the [[Configuring locales|locale configuration wiki page]].<br />
<br />
==Q) How do I automount/mount something? ==<br />
'''A)''' If you use GNOME, install gnome-volume-manager:<br />
pacman -Sy gnome-volume-manager<br />
<br />
Now add yourself to the storage group:<br />
gpasswd -a ''your_user'' storage<br />
<br />
If you don't want to use gnome-volume-manager, check out [[Ivman]] or [[AutoFS_HowTo|AutoFS]].<br />
<br />
==Q) How do I connect to my wireless network?==<br />
'''A)''' See [[Wireless Setup]].<br />
<br />
==Q) How do I connect to my wired network?==<br />
'''A)''' See [[Configuring network]].<br />
<br />
==Q) What is this AUR thing I keep hearing about?==<br />
'''A)''' See [[AUR Q & A]].<br />
<br />
==Q) Why do I get a green screen whenever I try to watch a video?==<br />
'''A)''' Your colour depth is set wrong. It may need to be 24 instead of 16, for example.<br />
<br />
==Q) Spellcheck is marking all of my text as incorrect!==<br />
'''A)''' Have you installed an aspell dictionary? Use <tt>pacman -Ss aspell</tt> to see the available dictionaries.</div>Blazeixhttps://wiki.archlinux.org/index.php?title=VirtualBox&diff=55101VirtualBox2008-12-08T04:59:35Z<p>Blazeix: Deleted note. Virtualbox is in the main 32bit repos</p>
<hr />
<div>[[Category:Emulators (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|:VirtualBox}}<br />
{{i18n_entry|Italiano|:VirtualBox (Italiano)}}<br />
{{i18n_entry|简体中文|:VirtualBox (简体中文)}}<br />
{{i18n_entry|Русский|VirtualBox (Русский)}}<br />
{{i18n_entry|Español|VirtualBox (Español)}}<br />
{{i18n_links_end}}<br />
<br />
<br />
<br />
== What is VirtualBox ==<br />
[http://www.virtualbox.org VirtualBox] is a virtual pc emulator like vmware. It has many of the features vmware has, as well as some of its own.<br />
<br />
=== Editions ===<br />
VirtualBox is available in two editions: VirtualBox (OSE) and VirtualBox (Personal Use and Evaluation License (PUEL))<br />
<br />
==== VirtualBox (OSE) ====<br />
VirtualBox (OSE) is the open source version of VirtualBox, which can be found in the community repository. It lacks some features such as USB device support and the built-in RDP server.<br />
<br />
==== VirtualBox (PUEL) ====<br />
VirtualBox PUEL is a binary-only version (free for personal use) which is available from the [http://aur.archlinux.org/packages.php?ID=9753 AUR] or directly from the <br />
[http://www.virtualbox.org/wiki/Downloads VirtualBox] website. The PUEL edition offers the following advantages:<br />
<br />
*'''Remote Display Protocol (RDP) Server''' - a complete RDP server on top of the virtual hardware, allowing users to connect to a virtual machine remotely using any RDP compatible client<br />
<br />
*'''USB support''' - a virtual USB controller which allows USB 1.1 and USB 2.0 devices to be passed through to virtual machines<br />
<br />
*'''USB over RDP''' - a combination of the RDP server and USB support, allowing users to make USB devices available to virtual machines running remotely<br />
<br />
*'''iSCSI initiator''' - a builtin iSCSI initiator making it possible to use iSCSI targets as virtual disks without the guest requiring support for iSCSI<br />
<br />
== Installation ==<br />
<br />
=== Install VirtualBox (OSE) ===<br />
<br />
VirtualBox (OSE) is available from the standard repositories:<br />
<br />
# pacman -S virtualbox-ose<br />
<br />
'''Note:''' This package seems not to be in x84_64 Repositories.<br />
<br />
This will select by default <tt>virtualbox-ose</tt> and <tt>virtualbox-modules</tt> packages. Once installed, a desktop entry can be located in ''Applications > System Tools > VirtualBox OSE''<br />
<br />
Now, add the desired username to the '''vboxusers''' group:<br />
<br />
# gpasswd -a USERNAME vboxusers<br />
<br />
''('''Note:''' You must logout/login in order for this change to take effect)''<br />
<br />
Lastly, edit <tt>/etc/rc.conf</tt> as root and add '''vboxdrv''' to the MODULES array in order to load the VirtualBox drivers at startup. For example:<br />
<br />
MODULES=(loop '''vboxdrv''' fuse ...)<br />
<br />
To load the module manually, run the following in a terminal as root: <br />
<br />
# modprobe vboxdrv<br />
<br />
'''HowTo:'''<br><br />
[[VirtualBox-HowTo]]<br />
<br />
=== Install VirtualBox PUEL (virtualbox_bin) ===<br />
VirtualBox PUEL is available from the [http://aur.archlinux.org/packages.php?ID=9753 AUR: virtualbox_bin].<br />
<br />
Download the tarball from the [http://aur.archlinux.org/packages.php?ID=9753 AUR: virtualbox_bin] page, unpack, run <tt>makepkg</tt>, and then as root:<br />
<br />
# pacman -U PACKAGE-NAME.pkg.tar.gz<br />
<br />
'''However, there's an alternative way to install the virtualbox_bin package:'''<br />
<br />
Firstly, add as root the followings into /etc/pacman.conf:<br />
[archlinuxfr]<br />
Server = <nowiki>http://repo.archlinux.fr/i686</nowiki><br />
or<br />
[archlinuxfr]<br />
Server = <nowiki>http://repo.archlinux.fr/x86_64</nowiki><br />
depending on your CPU's architecture.<br />
<br />
Then you can install it successfully via:<br />
# pacman -Sy virtualbox_bin<br />
<br />
After installation, a desktop entry can be located in ''Applications > System Tools > Innotek VirtualBox''<br />
<br />
Now, add the desired username to the '''vboxusers''' group:<br />
# gpasswd -a USERNAME vboxusers<br />
<br />
''('''Note:''' You must logout/login in order for this change to take effect)''<br />
<br />
Lastly, edit <tt>/etc/rc.conf</tt> as root and add '''vboxdrv''' to the MODULES array in order to load the VirtualBox drivers at startup. For example:<br />
MODULES=(loop '''vboxdrv''' fuse ...)<br />
<br />
To load the module manually, run the following in a terminal as root: <br />
# modprobe vboxdrv<br />
<br />
==== Module Rebuilds ====<br />
Note that any time your kernel version changes (due to upgrade, recompile, etc.) you must also rebuild the VirtualBox kernel module by running '''vbox_build_module''' as root. This binary will be located in one of the following locations: <tt>/sbin</tt>, <tt>/bin</tt>, or <tt>/usr/bin</tt>. After rebuilding the module, don't forget to load it with: '''<code>modprobe vboxdrv</code>'''<br />
<br />
=== Install required QT libraries ===<br />
Currently, VirtualBox relies on qt4 for its graphical interface. If you require a GUI, ensure you have qt4 installed:<br />
# pacman -S qt<br />
<br />
=== Start VirtualBox ===<br />
To start Virtualbox, run the following command in a terminal:<br />
$ VirtualBox<br />
<br />
== Configuration ==<br />
After we have installed VirtualBox on our system and added ourselves in the vboxusers group we can start configuring our system in order to make all the features of VirtualBox available to us.Create a new virtual machine using the wizard provided by the GUI and then click settings in order to edit the virtual machine settings.<br />
<br />
=== Keyboard and mouse between the host and the guest ===<br />
To capture the keyboard and mouse, click the mouse inside the Virtual Machine display.<br><br />
To uncapture, "Ctrl-Alt Delete".<br />
<br />
=== Getting network in the guest machine to work ===<br />
First let's get network working in the guest machine. Click the network tab. The not attached option means you'll have "Network cable unplugged" or similar error in the guest computer.<br />
<br />
==== Using NAT network ====<br />
This is the simplest way to get network. Select NAT network and it should be ready to use. Then, the guest operating system can be automatically configured by using DHCP.<br />
<br />
The NAT IP address on the first card is 10.0.2.0, 10.0.3.0 on the second and so on.<br />
<br />
==== Using host interface networking (the Arch way) ====<br />
You are going to just edit these files and reboot:<br />
<br />
* /etc/conf.d/bridges<br />
* /etc/rc.conf<br />
* /etc/vbox/interfaces<br />
<br />
Ready? Let's go!<br />
<br />
'''/etc/conf.d/bridges:'''<br />
bridge_br0="eth0" # Put any interfaces you need.<br />
BRIDGE_INTERFACES=(br0)<br />
<br />
'''/etc/rc.conf:'''<br />
<br />
First add the bridge module to your MODULES line<br />
MODULES=( <your other modules> '''bridge''')<br />
<br />
Then, in your NETWORKING section, make the following changes:<br />
lo="lo 127.0.0.1"<br />
eth0="eth0 up" # If you have more interfaces in the previous file, more lines like "if_number="if_number up" here.<br />
br0="dhcp" # Maybe you have some static configuration... I use DHCP.<br />
INTERFACES=(lo eth0 br0)<br />
<br />
'''/etc/vbox/interfaces'''<br />
<br />
(You can set up more interfaces if you want. Sky is the limit!):<br />
vbox0 your_user br0 # Be sure that your user is in the vboxusers group.<br />
<br />
Reboot and enjoy!<br />
<br />
'''''Note:''' Remember to set up your virtual machine with proper network configuration.''<br />
<br />
'''''Note:''' If you have any issue, make sure that you have the bridge-utils package installed and vboxnet daemon loaded''<br />
<br />
==== Using host interface networking (generic) ====<br />
This way is a bit harder, but it allows you to see the VirtualMachine as a "real" computer on your local network. You need to get bridge-utils <br />
<br />
# pacman -S bridge-utils uml_utilities<br />
<br />
'''Note''' by Sp1d3rmxn:<br />
:You also need to have the TUN module loaded...in [[rc.conf]] add "tun" (without the :quotes) to your MODULES section. For testing this out right now without rebooting :you can load the module from the command line by "modprobe tun".<br />
:<br />
:Then you MUST set these permissions otherwise you'll never get VBox to init the :interface. The command is "<code>chmod 666 /dev/net/tun</code>" (without the quotes).<br />
<br />
:Now proceed with the rest as it's written below.<br />
<br />
'''Note''' by Dharivs<br />
:As said by Sp1d3rmxn, we must set these permissions, but, instead of using the <br />
:command, we can set them in /etc/udev/rules.d/60-vboxdrv.rules, which will set them <br />
:on boot:<br />
KERNEL=="vboxdrv", NAME="vboxdrv", OWNER="root", GROUP="vboxusers", MODE="0660"<br />
KERNEL=="tun", OWNER="root", GROUP="vboxusers", MODE="0660"<br />
<br />
<br />
<b>1.</b> Create a new bridge with this command:<br />
# brctl addbr br0<br />
<br />
<b>2.</b> If you are not using DHCP, run ifconfig and note down the network configuration of your existing network interface (e.g. eth0), which we will need to copy to the bridge in a minute.<br />
<br />
''('''Note: You will need this settings so make sure you don't lose them!!!''')''<br />
<br />
<b>3.</b> Switch your physical network adapter to "promiscuous" mode so that it will accept Ethernet frames for MAC addresses other than its own (replace eth0 with your network interface):<br />
# ifconfig eth0 0.0.0.0 promisc <br />
<br />
''('''Note:''' You will lose network connectivity on eth0 at this point.)''<br />
<br />
<b>4.</b> Add your network adapter to the bridge:<br />
# brctl addif br0 eth0<br />
<br />
<b>5.</b> Transfer the network configuration previously used with your physical ethernet adapter to the new bridge. If you are using DHCP, this should work:<br />
# dhclient br0<br />
<br />
'''Note''' by Sp1d3rmxn:<br />
:Use "dhcpcd -t 30 -h yourhostname br0 &" instead of the above<br />
<br />
Otherwise, run <code>ifconfig br0 x.x.x.x netmask x.x.x.x</code> and use the values that you noted down previously.<br />
<br />
<b>6.</b> To create a permanent host interface called vbox0 (all host interfaces created in this way must be called vbox followed by a number) and add it to the network bridge created above, use the following command:<br />
VBoxAddIF vbox0 vboxuser br0<br />
<br />
Replace vboxuser with the name of the user who is supposed to be able to use the new interface.<br />
<br />
('''Note:''' VboxAddIF is located in /opt/VirtualBox-VERSION OF VIRTUALBOX/VBoxAddIF)<br />
<br />
Alternatively, you can [http://mychael.gotdns.com/blog/2007/05/31/virtualbox-bridging/ setup VirtualBox networking] through your /etc/rc.conf to enable a bridged connection.<br />
<br />
==== Using host interface networking with a wireless device ====<br />
Bridging as described above won't work with a wireless device. Using [http://aur.archlinux.org/packages.php?ID=16356 parprouted] however it can be accomplished.<br />
<br />
# Install parprouted and iproute<br />
# <code># ln -s /usr/sbin/ip /sbin/ip</code><br />
# Make sure IP fowarding is enabled: <code># sysctl net.ipv4.ip_forward=1</code>, and/or edit /etc/sysctl.conf<br />
# <code># VBoxTunctl -b -u <user></code>, to create the tap device<br />
# <code># ip link set tap0 up; ip addr add 192.168.0.X/24 dev tap0</code>, needs to be a manually set IP on the same network your wireless device is.<br />
# <code># parprouted wlan0 tap0</code><br />
<br />
=== Getting USB to work in the guest machine ===<br />
(Only available in the PUEL edition)<br />
<br />
First in order to make usb available for use to the virtual machine you must add this line to your /etc/fstab<br />
none /proc/bus/usb usbfs auto,busgid=108,busmode=0775,devgid=108,devmode=0664 0 0<br />
<br />
108 is is the id of the group which should be allowed to access USB-devices. Change it to the id of your vboxusers group. You can get the id by running:<br />
$ grep vboxusers /etc/group<br />
<br />
If you don't mind a security hole change devmode from 664 to 666.<br />
<br />
Remount /proc/bus/usb:<br />
# mount -o remount /proc/bus/usb/<br />
<br />
'''Note''' by slipper:<br />
:I had to do ''mount -a'' after the above command to get this to work for me.<br />
<br />
Restart Virtualbox and click the USB tab in the settings of the virtual machine and select which devices are available to your pc on boot. If you wish your virtual machine to use device that you have just plugged in (assuming the virtual machine has booted already), go to the VirtualMachine screen go to devices -> USB Devices -> and select the device you wish to plug in the virtual pc.<br />
<br />
=== Installing Guest Additions ===<br />
For VirtualBox (OSE) version 1.6.2 =>, read:<br><br />
[[VirtualBox-HowTo]]<br />
<br />
The Guest Additions make the shared folders feature available, as well as better video (not 3D) and mouse drivers. You will have mouse integration, thus no need to release the mouse after using it in the guest and one can also enable a bidirectional clipboard.<br />
<br />
After you booted the virtual machine, go to menu Devices->Install Guest Additions... Once you've clicked it, VirtualBox loads an ISO into the current CD-ROM, so you won't see anything happen yet ;)<br />
<br />
Then do the following as root:<br />
# mount /media/cdrom<br />
# sh /media/cdrom/VBoxLinuxAdditions.run<br />
<br />
It will build and install the kernel modules, install the Xorg drivers and create init scripts. It will most probably print out errors about init scripts and run levels and what not. Ignore them. You will find rc.vboxadd and rc.vboxvfs in /etc/rc.d (it also creates /etc/rc.d/rc.local which you can delete). To have the Guest Additions loaded at boot time, just add those to the DAEMONS array in /etc/rc.conf eg.<br />
<br />
DAEMONS=(syslog-ng network netfs crond alsa '''rc.vboxadd rc.vboxvfs''')<br />
<br />
=== Sharing folders between the host and the guest ===<br />
For VirtualBox (OSE) version 1.6.2 =>, read:<br><br />
[[VirtualBox-HowTo]]<br />
<br />
In the settings of the virtual machine go to shared folders tab and add the folders you want to share.<br />
<br />
*NOTE: You need to install Guest Additions in order to use this feature.<br />
In a Linux host, "Devices" --> "Install Guest Additions"<br />
Yes (when asked to download the CD image)<br />
Mount (when asked to register and mount)<br />
<br />
In a Linux host, creat one folder for sharing files.<br />
<br />
In a Windows guest, starting with VirtualBox 1.5.0, shared folders are browseable and are therefore visible in Windows Explorer. Open Windows Explorer and look for it under:<br />
<br />
My Networking Places --> Entire Network --> VirtualBox Shared Folders<br />
<br />
Alternatively, on the Windows command line, you can also use the following:<br />
<br />
net use x: \\vboxsvr\sharename<br />
<br />
While vboxsvr is a fixed name, replace "x:" with the drive letter that you want to use for the share, and sharename with the share name specified with VBoxManage.<br />
<br />
In a Linux guest, use the following command:<br />
# mount -t vboxsf [-o OPTIONS] sharename mountpoint<br />
<br />
Replace sharename with the share name specified with VBoxManage, and mountpoint with the path where you want the share to be mounted (e.g. /mnt/share). The usual mount rules apply, that is, create this directory first if it does not exist yet.<br />
<br />
Beyond the standard options supplied by the mount command, the following are available:<br />
iocharset=CHARSET<br />
to set the character set used for I/O operations (utf8 by default) and<br />
convertcp=CHARSET<br />
to specify the character set used for the shared folder name (utf8 by default).<br />
<br />
=== Getting audio to work in the guest machine ===<br />
<br />
In the machine settings, go to the audio tab and select the correct driver according to your sound system (ALSA, OSS or PulseAudio).<br />
<br />
=== Setting up the RAM and Video Memory for the virtual PC ===<br />
<br />
You can change the default values by going to settings -> general.<br />
<br />
=== Setting up CDROM for the Virtual PC ===<br />
<br />
You can change the default values by going to settings -> CD/DVD-ROM.<br />
<br />
Check mount cd/dvd drive and select one of the following options.<br />
<br />
'''Note:''' If no CDROM drive is detected, make sure the HAL daemon is running. To start it, run the following command as root:<br />
<br />
# /etc/rc.d/hal start<br />
<br />
=== Rebuilding vboxdrv module ===<br />
For Virtualbox >= 1.6.0 use [[ABS]] for rebuild vboxdrv module or you can wait the maintainer update it :)<br />
<br />
=== Converting from VMware images ===<br />
Do <br />
# pacman -S qemu<br />
$ qemu-img convert image.vmdk image.bin<br />
$ VBoxManage convertdd image.bin image.vdi<br />
<br />
This may not be needed anymore with recent virtualbox versions (to be confirmed)<br />
<br />
== External Resources ==<br />
* [http://download.virtualbox.org/virtualbox/2.0.6/UserManual.pdf VirtualBox 2.0.6 User Manual]</div>Blazeixhttps://wiki.archlinux.org/index.php?title=Network_configuration/Wireless&diff=32232Network configuration/Wireless2007-11-10T19:33:38Z<p>Blazeix: Replaced broken link</p>
<hr />
<div>[[Category:Communication and network (English)]]<br />
[[Category:Networking (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Wireless_Setup}}<br />
{{i18n_entry|Nederlands|Draadloze_Configuratie}}<br />
{{i18n_entry|German|Drahtlos_Installation}}<br />
{{i18n_links_end}}<br />
<br />
==First steps==<br />
#Check to see if Linux supports your hardware. You can find out what your card is with lshwd.<br />
#*zd1201-based card like ZyXEL B-220<br />
#*[http://www.linux-wlan.org/docs/wlan_adapters.html.gz wlan-ng] supports quite a lot of chipsets; check here first.<br />
#*[http://madwifi.org madwifi] for Atheros chipsets (AR5210, AR5211, AR5212 and AR5213)<br />
#*[http://rt2x00.serialmonkey.com/wiki/index.php/Main_Page rt2x00 project] for a unified driver for Ralink's rt2400, rt2500, and rt2570 chipsets (beta).<br />
#*[http://www.ralinktech.com/ralink/Home/Support/Linux.html Ralink Linux Support] for drivers for Ralink chipsets direct from the manufacturer.<br />
#*[http://rt2x00.serialmonkey.com/wiki/index.php/Downloads rt2x00 project] for better-maintained versions of Ralink's own drivers ("legacy drivers" on the site).<br />
#*[http://ipw2100.sourceforge.net/ ipw2100] for Intel Pro/Wireless 2100 Mini PCI<br />
#*[http://ipw2200.sourceforge.net/ ipw2200] for Intel Pro/Wireless 2200 Mini PCI<br />
#*[http://ipw3945.sourceforge.net/ ipw3945] for Intel Pro/Wireless 3945 AB/G Mini PCI-E<br />
#*[http://www.nongnu.org/orinoco/devices/ orinoco] for some Prism 2-based cards<br />
#*[http://prism54.org/ prism54] for Prism 54-based cards<br />
#*[http://bcm43xx.berlios.de/ bcm43xx] for Broadcom 43xx-based cards<br />
#*Check the [http://linux-wless.passys.nl/ Linux Wireless Support] page for your hardware or in The Linux Questions [http://www.linuxquestions.org/hcl/index.php?cat=10 hardware compatibility list] (HCL), which also has a good list of Linux-friendly hardware <br />
#If the hardware is supported only under Windows<br />
#*[http://ndiswrapper.sourceforge.net/wiki/index.php/List ndiswrapper] for hardware supported only under Windows (some Broadcom, 3com, etc)<br />
#*You will need the .inf and .sys files from your Windows driver - [http://ndiswrapper.sourceforge.net/mediawiki/index.php/List check here]<br />
#If your hardware is not listed anywhere<br />
#*I think you may be screwed....<br />
#*Try a web search for the exact model name of your hardware with the word "linux" - and feel free to ask for help on [http://bbs.archlinux.org the forums]<br />
<br />
==Installation==<br />
First off, make sure you grab '''wireless-tools''' from pacman<br />
<pre>pacman -S wireless_tools</pre><br />
You cannot initialize wireless hardware without these tools.<br />
===Drivers===<br />
Here are the details of how to get the drivers for your card. You may find that there are several options open to you, so remember you can check the [http://www.linuxquestions.org/hcl/index.php?cat=10|LQ HCL] for help on selecting the best driver.<br />
====wlan-ng====<br />
<pre>pacman -S wlan-ng24</pre> or <pre>pacman -S wlan-ng26</pre><br />
====rt2x00====<br />
Unified driver for Ralink chipsets (will ultimately replace rt2500,rt61,rt73 etc). Compatible with stable wpa_supplicant using the wext driver interface. This driver is currently in heavy development but is likely to be in the mainline kernel as of 2.6.24.<br />
<pre>pacman -S rt2x00-cvs</pre> (from unstable repository)<br />
See the [[Using_the_new_rt2x00_beta_driver|rt2x00 wiki page]].<br />
<br />
====RT2500====<br />
For Ralink's PCI/PCMCIA based rt2500 series chipsets (the first generation of Ralink chips to support 802.11g).<br />
<pre>pacman -S rt2500</pre><br />
Supports standard iwconfig tools for unencrypted and WEP connections, although it can be quite sensitive to the order of commands.<br />
wpa_supplicant is not supported using the standard wext interface. The driver does support WPA (using hardware encryption), but in a non-standard way. The trunk version of wpa_supplicant (0.6.x) appears to include special support for this driver, and it is also possible to negotiate a WPA connection manually using iwpriv commands.<br />
See [http://rt2400.cvs.sourceforge.net/*checkout*/rt2400/source/rt2500/Module/iwpriv_usage.txt these instructions] for details.<br />
The same applies for RT61 and RT73 below.<br />
<br />
====RT61====<br />
For PCI/PCMCIA cards based on Ralink's later generation of 802.11g chipsets (including those supporting proprietary MIMO modes).<br />
See the [[RT61_Wireless|RT61 wiki page]].<br />
<br />
====RT73====<br />
For USB devices based on Ralink's later generation of 802.11g chipsets (including those supporting proprietary MIMO modes).<br />
See the [[RT73_Wireless|RT73 wiki page]].<br />
<br />
====madwifi====<br />
<br />
pacman -S madwifi<br />
<br />
The module is called <tt>ath_pci</tt>. '''You may need to use the countrycode option when loading the MadWifi driver in order to use channels and transmit power settings that are legal in your country/region.''' In the Netherlands, for example, you would load the module like this:<br />
<br />
modprobe ath_pci countrycode=528<br />
<br />
You can verify the settings with the <tt>iwlist</tt> command. See <tt>man iwlist</tt> and the [http://madwifi.org/wiki/UserDocs/CountryCode CountryCode page on the MadWifi wiki]. To have this setting automatically applied during boot, add the following to <tt>/etc/modprobe.conf</tt>:<br />
<br />
options ath_pci countrycode=528<br />
<br />
ATTENTION: I had to remove the countrycode option completely or the ath0 device wasn't created (andyrtr, kernel 2.6.21)!<br />
<br />
====ipw2100 and ipw2200====<br />
Depending on which of the chips you have, use either:<br />
<br />
pacman -S ipw2100-fw<br />
<br />
or:<br />
<br />
pacman -S ipw2200-fw<br />
<br />
You will probably need to reboot for the firmware to be loaded.<br />
<br />
====ipw3945 and ipw4965====<br />
Intel's new [http://intellinuxwireless.org/?p=iwlwifi iwlwifi project] drivers will work for both chipsets, simply choose the microcode that corresponds to yours:<br />
<br />
pacman -S iwlwifi iwlwifi-3945-ucode<br />
<br />
or:<br />
<br />
pacman -S iwlwifi iwlwifi-4965-ucode<br />
<br />
Add the kernel driver to your startup:<br />
<br />
nano /etc/rc.conf<br />
<br />
in the modules=() array, add '''iwl3945''' or '''iwl4965''' to the list, depending on your chipset<br />
<br />
CTRL + X, Y to close and save.<br />
<br />
The drivers should now load after a reboot, and running 'ifconfig' from a terminal should report '''wlan0''' as a new network interface.<br />
<br />
Note: if the iwlwifi drivers, being "experimental", do not work, know that the windows NETw4x32 driver works with ndiswrapper just fine.<br />
<br />
====ipw3945 (Alternate Method)====<br />
'''''Note:''' This ipw3945 driver will be phased out as Intel's iwlwifi project drivers reach maturity.''<br />
<br />
<pre>pacman -S ipw3945</pre><br />
<br />
This should install ipw3945-ucode, ipw3945, and ipw3945d (daemon).<br />
<br />
To properly initialize the driver on startup...<br />
<br />
<pre>nano /etc/rc.conf</pre><br />
<br />
in the modules=() array, add ipw3945 to the list<br />
<br />
in the daemons=() array, add ipw3945d to the list (its order must come BEFORE network and dhcdbd/networkmanager in the array)<br />
<br />
CTRL + X, Y to close and save.<br />
<br />
The ipw3945 module should load during "Loading Modules.." and "Starting IPW3945d" should appear during daemon initialization, and ethX should be present.<br />
<br />
Update: <br />
On my HP nc6320 the Bluetooth won't connect unless you unload the ipw3945 module.<br />
<br />
====orinoco====<br />
This should be part of the kernel package and be installed already.<br />
====ndiswrapper====<br />
Ndiswrapper is not a real driver, but you can use it when there are no native Linux drivers for your wireless chips. So it is very useful in some situations. To use it you need the *.inf file from your Windows driver. To install ndiswrapper use the steps below:<br />
<br />
To install the ndiswrapper use pacman:<br />
<pre>pacman -Sy ndiswrapper ndiswrapper-utils</pre><br />
''Note:'' Beyond kernel needs the packages ndiswrapper-beyond instead of the ndiswrapper package!<br />
<br />
''Note:'' If you do not have internet access on the machine running Arch, you can also download the packages to a disk from one of the mirrors, e.g. http://www2.cddc.vt.edu/linux/distributions/archlinux/extra/os/i686/ .<br />
You need the ndiswrapper (or ndiswrapper-beyond as it says above) and ndiswrapper-utils packages. You may also have to download the latest kernel26 (or beyond), as the version provided on the CD is not always the latest one.<br />
<br />
Once the installation has completed, follow the steps to configure ndiswrapper.<br />
<pre>ndiswrapper -i filename.inf<br />
ndiswrapper -l<br />
ndiswrapper -m<br />
depmod -a</pre><br />
<br />
Now the ndiswrapper install is almost finished; you just have to update /etc/rc.conf to load the module at boot (below is a sample of my config; yours might look slightly different):<br />
<br />
<pre>MODULES=(ndiswrapper snd-intel8x0 !usbserial)</pre><br />
<br />
The important part is making sure that ndiswrapper exists on this line, so just add it alongside the other modules. It would be best to test that ndiswrapper will load now, so:<br />
<br />
<pre>modprobe ndiswrapper<br />
iwconfig</pre><br />
<br />
and wlan0 should exist. Check this page if you're having problems:<br />
[http://ndiswrapper.sourceforge.net/mediawiki/index.php/Installation Ndiswrapper installation wiki].<br />
<br />
====prism54====<br />
Download the firmware driver for your appropriate card from [http://www.prism54.org/ this site]. Rename the firmware file to 'isl3890'.<br />
If nonexistent, create the directory /lib/firmware and place the file 'isl3890' in it. This should do the trick. ([http://bbs.archlinux.org/viewtopic.php?t=16569&start=0&postdays=0&postorder=asc&highlight=siocsifflags+such+file++directory forum source])<br />
<br />
====ACX100/111====<br />
The ACX100/111 driver can be found at [http://acx100.sourceforge.net/]. This can be used for cards based on the Texas Instruments ACX100/111 chipset.<br />
<br />
Contrary to what people think, this is relatively easy to setup. There is a huge guide written by Craig [http://www.houseofcraig.net/acx100_howto.php here]. However, the README that comes with the driver is actually easier to follow.<br />
<br />
# Download the latest version of the driver. <br />
# Extract the archive to a directory of your choice. Beware: The archive does not have a directory inside, so if you don't extract within a directory, a lot of files will spill out everywhere.<br />
# Change to the directory containing the extracted files.<br />
# Execute <pre>make -C /lib/modules/`uname -r`/build M=`pwd`</pre><br />
# Change to root user.<br />
# Execute <pre>make -C /lib/modules/`uname -r`/build M=`pwd` modules_install</pre><br />
# Execute <pre>depmod -ae</pre> so the kernel detects the new module.<br />
# Insert the driver CD that came with the card into the CD/DVD drive on your computer.<br />
# Mount the drive with <pre>mount &lt;device&gt;</pre><br />
# Copy the firmware from the CD to /lib/firmware.<br />
# Rename the firmware to 'tiacxNNNcMM' (NNN=100/111, MM=radio module ID (in uppercase hex)) for the PCI driver or tiacxNNNusbcMM for the USB driver. <br />
# Load the acx module with <pre>modprobe acx</pre><br />
# Add the acx module to the MODULES array in /etc/rc.conf so it gets loaded on startup.<br />
# Follow the instructions for connecting to your network with iwconfig.<br />
<br />
<br />
Note: It is also possible to compile the driver inside the kernel tree. This is documented in the README file with the driver.<br />
<br />
====BCM43XX====<br />
Broadcom users that have 43xx series chipsets have a new alternative to ndiswrapper. In kernel version 2.6.17, the bcm43xx driver was introduced.<br />
<br />
#Run <pre>iwconfig</pre> or <pre>hwd -s</pre> to determine that you have an appropriate card. My output of hwd -s looked like this: <pre>Network : Broadcom Corp.|BCM94306 802.11g NIC module: unknown</pre><br />
#Run <pre>pacman -Sy bcm43xx-fwcutter</pre> to install the firmware cutter application.<br />
#Download the Windows driver file for your card from which to extract the firmware.<br />
#*I initially downloaded the driver from Dell's support site. When that didn't work I found a link on the Ubuntu Wiki and used that file instead: [http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o]. I just saved this file to my desktop; you won't need it after the next step.<br />
#Run <pre>bcm43xx-fwcutter -w /lib/firmware /home/&lt;user&gt;/Desktop/wl_apsta.o</pre> You may have to create /lib/firmware first.<br />
#Restart, and configure your device as normal. You may want to add bcm43xx into the modules section of your rc.conf file. Good luck!<br />
<br />
====rtl8187====<br />
See the [[Rtl8187_wireless|rtl8187 wiki page]].<br />
<br />
==Setup and Boot==<br />
Arch Linux provides two methods for enabling wireless connections. The first method is based on the existing network script and should be used for non-roaming wireless access. If you're on only one wireless network, this is the best setup to use. However, if you continually roam from network to network, the Network Profiles setup would be best, though slightly more complicated.<br />
<br />
===Using the Arch Linux Wireless Network settings===<br />
* Typical Arch Linux Wireless configuration is rather straightforward. The network itself is configured in the exact same way a non-wireless network is in /etc/rc.conf. For example:<br />
# /etc/rc.conf<br />
wlan0="dhcp"<br />
INTERFACES=(lo eth0 wlan0)<br />
where wlan0 is the wireless interface name<br />
* Beyond this, the networking scripts need some way to determine that wlan0 is a wireless interface (as not all wireless interfaces are wlan*). This is done in the /etc/conf.d/wireless file. The setup here is very simple. For each wireless interface, you simply declare a setting called wlan_<interface name>. If your wireless interface is "wlan0", it uses wlan_wlan0. If your wireless interface is "eth1", wlan_eth1 is what you need. The value for this setting is simply the parameters to iwconfig (see man iwconfig for details) ''including the interface name''.<br />
* A simple, non-encrypted setup for the above would look like:<br />
# /etc/conf.d/wireless<br />
wlan_wlan0="wlan0 essid MyEssid"<br />
WLAN_INTERFACES=(wlan0)<br />
* While a WEP Encrypted setup would look like:<br />
# /etc/conf.d/wireless<br />
wlan_wlan0="wlan0 essid MyEssid key 12345678"<br />
WLAN_INTERFACES=(wlan0)<br />
* ''phrakture's trick''<br />
** My personal trick isn't much of a trick at all; it just simplifies a lot of the process. While /etc/conf.d/wireless is sourced (included) in the network script, it is not a requirement for having a wireless interface. Therefore, the actual settings for the wireless interface can exist in anything sourced by the network script. For that reason, I put all my settings in /etc/rc.conf:<br />
# /etc/rc.conf<br />
eth0="dhcp"<br />
wlan0="dhcp"<br />
wlan_wlan0="wlan0 essid MyEssid"<br />
#wlan_wlan0="wlan0 essid MyEssid key 12345678"<br />
#wlan_wlan0="wlan0 essid MyEssid key s:wirelesspassword"<br />
WLAN_INTERFACES=(wlan0)<br />
INTERFACES=(lo eth0 wlan0)<br />
<br />
All of these settings assume your wireless card is wlan0, if it is something else (such as eth0) then simply replace wlan0 with eth0 every time it appears. For example, if your wireless card is eth0 so you change wlan_wlan0 to be wlan_eth0="eth0 essid ...." , wlan0="dhcp" to eth0="dhcp" and WLAN_INTERFACES=(wlan0) to WLAN_INTERFACES=(eth0). The same applies for cards named eth1 and so forth.<br />
<br />
===Using the Archlinux Roaming Network Profiles===<br />
<br />
====Quick Setup====<br />
# Create new profile<br />
## Create a new network profile in <tt>/etc/network-profiles/</tt> based on the <tt>template</tt> file. Let's call it <tt>home</tt>. Remember the filename you choose! We'll use it to refer to our new profile later.<br />
## Adjust the settings in the new profile to your needs.<br />
# Remove outdated settings from <tt>rc.conf</tt><br />
## Remove all interfaces that should be managed by the Network Profiles in the future from INTERFACES.<br />
## Remove any relevant routes from ROUTES.<br />
## Leave the "lo" interface in place.<br />
# Add Network Profile settings to <tt>rc.conf</tt><br />
## Add the name of your new network profile to <tt>NET_PROFILES=()</tt> <pre>NET_PROFILES=(home)</pre>.<br />
<br />
So much for the quick setup... You can also set <tt>NET_PROFILES</tt> to "menu" and it will present a dialog/ncurses menu (which requires the [http://www.archlinux.org/packages/4278/ dialog package] installed) at bootup where you can pick the profile you want. This doesn't work if you use @network (starting network in the background).<br />
<br />
Alternatively, you can pass a <tt>NET=</tt> value on the kernel boot line, telling netcfg which profile you wish to start with.<br />
vmlinuz root=/dev/hda3 vga=773 ro NET=home<br />
<br />
Picked from [http://www.archlinux.org/pipermail/arch/2005-June/004855.html Judd's explanation].<br />
<br />
If you want to change your network profile after boot, you can run 'netcfg' as root.<br />
<br />
'''Simple Wireless Autodetection'''<br />
iphitus created an autodetection patch for the official initscripts which has now been imported as standard. Please see [http://www.archlinux.org/pipermail/arch/2005-July/005251.html here] for an explanation of how it works.<br />
<br />
There is a workaround for another [[wireless autodetection]] that scans the air for known APs and starts the associated profile.<br />
<br />
'''WPA support'''<br />
phydeaux created a great patch for WPA support which has been adopted straight into the main tree and will be in the next release (after 0.7.1). For information about how to use WPA with the Network Profiles see also [[Ndiswrapper and wpa supplicant]].<br />
<br />
'''Netcfg GUI''' A simple GUI script to switch network profiles from GNOME (or another window manager) can be found in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=4197 AUR]. ([http://mac-cain13.livejournal.com/tag/netswitch Screenshots])<br />
<br />
===Wifi-radar===<br />
'''Wifi-radar''' This is a nifty little GUI program that lets you switch wireless networks with ease. Simply do the following:<br />
<br />
# # pacman -S wifi-radar<br />
# # visudo<br />
<br />
Here, add the following line: <br />
yourusername ALL=(ALL) NOPASSWD: /usr/bin/wifi-radar<br />
Press ESC, then colon (:), then x, then ENTER to save and exit.<br />
<br />
# Now, just add wifi-radar to your daemons list in /etc/rc.conf and run wifi-radar from your internet menu, and you're all set. :) If you want to view the available networks or to configure your setup, simply run sudo wifi-radar. <br />
# You might need to edit /etc/conf.d/wifi-radar to set the particular network interface that you want to use.<br />
<br />
NB!: I had to set 'Ifup required' to ON to be able to get it to work with my line. Before this, the internet would not connect.<br />
<br />
===NetworkManager===<br />
'''NetworkManager''' A more advanced network management system for Linux. This is included in various Linux distributions and now can be used in Arch Linux. It is very painless for roaming users, and includes an easy-to-use GUI program for selecting your desired network. One caveat however is that you are prompted for your keyring password every time you log into gnome and the program starts. This most likely won't be fixed until later versions, and can be quite annoying. More information on NetworkManager can be found at: [[Networkmanager]].<br />
<br />
==Misc Links==<br />
*[http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Wireless.html An overly wordy howto that rarely helps]<br />
*[http://madwifi.org/wiki/UserDocs/FirstTimeHowTo The madwifi project's method of installing, good if you're having trouble doing it the Arch way]</div>Blazeixhttps://wiki.archlinux.org/index.php?title=Gcin_(%E6%AD%A3%E9%AB%94%E4%B8%AD%E6%96%87)&diff=16078Gcin (正體中文)2006-10-28T19:14:07Z<p>Blazeix: Added basic information about the project.</p>
<hr />
<div>[[Category:Internationalisation (繁體中文)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|GCIN}}<br />
{{i18n_entry|繁體中文|GCIN (繁體中文)}}<br />
{{i18n_links_end}}<br />
<br />
{{stub}}<br />
<br />
= About GCIN =<br />
The following was taken from the freshmeat.net project page:<br />
<br />
gcin (Gtk Chinese INput application in X) is a Chinese input method server for Big5 Traditional Chinese character sets. It features a GTK user interface. It is a very popular Chinese input method (IM) server in Taiwan, which focuses mainly on Traditional Chinese. Its IM table format is almost the same as xcin, and comes with a conversion program to help xcin users transfer their settings. A GUI interface is used for gcin settings such as your favorite Chinese input table and keyboard layout. It is often straightforward for users to append other input tables not originally included in the release package, or tables used by other IMs such as scim.<br />
<br />
= Installing GCIN =<br />
pacman -S gcin<br />
<br />
== Installing Other Input Tables ==<br />
MISSING<br />
<br />
= Configure GCIN =<br />
MISSING<br />
<br />
[http://www.csie.nctu.edu.tw/~cp76/gcin/ Project Homepage]</div>Blazeix