https://wiki.archlinux.org/api.php?action=feedcontributions&user=Chills&feedformat=atomArchWiki - User contributions [en]2024-03-28T11:22:52ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Bluetooth_mouse&diff=19249Bluetooth mouse2006-12-24T23:52:33Z<p>Chills: /* Connecting the mouse */</p>
<hr />
<div>[[Category:Input devices (English)]]<br />
This article describes how to set up a bluetooth mouse with Archlinux. I used a Logitech v270 with a Trendnet TBW-101UB USB Bluetooth dongle, but the general process should be the same for any model.<br />
<br />
<br />
<br />
== Required software ==<br />
<br />
You need the '''bluez-utils''' and '''bluez-libs''' packages from the community repository. <br />
<br />
== Configuration ==<br />
The pertinent options in /etc/conf.d/bluetooth are <br />
HCID_ENABLE=true<br />
HIDD_ENABLE=true<br />
after that, start bluetooth services with<br />
/etc/rc.d/bluetooth start<br />
<br />
== Finding out your mouse's bdaddr ==<br />
<br />
It is of the form ''12:34:56:78:9A:BC''. Either find it in the documentation of your mouse, on the mouse itself or with the '''hcitool scan''' command.<br />
<br />
== kernel modules ==<br />
<br />
The command<br />
# modprobe -v hci_usb bluetooth hidp l2cap<br />
loads the kernel modules you need, if they weren't loaded automatically. <br />
<br />
== Connecting the mouse ==<br />
hidd --search<br />
hcitool inq<br />
are good for device scanning.<br />
hidd --connect <bdaddr><br />
to actually connect.<br />
hidd --show<br />
will show your currently connected devices. The mouse should show up in this list. If it doesn't, press the reset button to make it discoverable.<br />
<br />
Note: If you have the ipw3945 module loaded (wifi on HP computer) the bluetooth wont work.</div>Chillshttps://wiki.archlinux.org/index.php?title=Network_configuration/Wireless&diff=19248Network configuration/Wireless2006-12-24T22:37:31Z<p>Chills: /* ipw3945 */</p>
<hr />
<div>[[Category:Communication and network (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 />
{{stub}}<br />
<br />
==First steps==<br />
#Check to see if Linux supports your hardware. You can find out what your card is with lshwd.<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] for Ralink's rt2400, rt2500, and rt2570 chipsets.<br />
#*[http://www.ralinktech.com/drivers/Linux/RT73_Linux_STA_Drv1.0.3.6.tar.gz RT73] for Ralink's RT73 USB chipsets<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 />
#*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 only supported under Windows<br />
#*[http://ndiswrapper.sourceforge.net/wiki/index.php/List ndiswrapper] for hardware only supported under Windows (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 />
See the [[Using_the_new_rt2x00_beta_driver|rt2x00 wiki page]]<br />
pacman -S rt2500<br />
also works. Load the module and you are away<br />
<br />
====RT73====<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 apply during boot, add the following to <tt>/etc/modprobe.conf</tt>:<br />
<br />
options ath_pci countrycode=528<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 />
====ipw3945====<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 in 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<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 wont connect unless you unload the ipw3945 module.<br />
<br />
====orinoco====<br />
This should be part of the kernel package and 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 usefull 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:'' AchrCK and Beyond kernels need the packages ndiswrapper-archck and 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, eg http://www2.cddc.vt.edu/linux/distributions/archlinux/extra/os/i686/ .<br />
You need the ndiswrapper (or ndiswrapper-archck or ndiswrapper-beyond as it says above) and ndiswrapper-utils packages. You may also have to download the latest kernel26 (or archck or beyond), as the version provided on the CD is not always the lastest 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 that's the ndiswrapper install almost finished, just got 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. 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 nonexistend create a 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 which are 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 which comes with the driver is actually easier to follow.<br />
<br />
# Download the latest version of the driver. <br />
# Extract the archive in 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 your Driver CD which 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! Finally! In kernel version 2.6.17, the bcm43xx driver was introduced, and it's easy as can beasy to set up!<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 to extract the firmware from.<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://drinus.net/airport/wl_apsta.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 />
==Setup and Boot==<br />
Archlinux provides two methods for enabling wireless connections. The first method is based on the existing network script and is to be used for non-roaming wireless access. If you're only on 1 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 Archlinux Wireless Network settings===<br />
* Typical Archlinux Wireless configuration is rather straight forward. 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 />
* 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 simply, non encrypted setup for the above would look like:<br />
# /etc/conf.d/wireless<br />
wlan_wlan0="wlan0 essid MyEssid"<br />
* ''phrakture's trick''<br />
** My personal trick isn't much of a trick at all, it just simplifies alot 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 />
If your wireless card is eth0 so you change wlan_wlan0 in wlan_eth0="eth0 essid ...."<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 chose! 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 which 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.<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 />
'''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 />
'''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 informtion 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 networkprofile from Gnome (or another windowmanager) can be found in [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/sbin/wifi-radar<br />
then 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 change your network profile after boot, you can run 'netcfg' as root.<br />
# oh, and you might need to edit /etc/conf.d/wifi-radar to set the particular network interface that you want to use<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 selcting 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 />
===Using phrakture's old scripts (very outdated)===<br />
* In order to use these scripts, place them where indicated. The main script is in /etc/rc.d and the profiles are in /etc/conf.d/wireless-profiles. Making a new profile involves copying the sample and renaming it. The script can be used in two ways. It can be added to the DAEMONS array, with an added WIRELESS_PROFILES collection in rc.conf that lists the profiles to start on boot. In addition, the script can be called manually: /etc/rc.d/wireless start/stop/restart will use the listed profiles in rc.conf, and /etc/rc.d/wireless profile sample up/down will use a named profile and bring it up or down.<br />
*[[Wireless Bootup Script]] - /etc/rc.d/wireless <br />
*[[Sample Wireless Profile]] - /etc/conf.d/wireless-profiles/sample/*<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>Chills