https://wiki.archlinux.org/api.php?action=feedcontributions&user=StANTo&feedformat=atomArchWiki - User contributions [en]2024-03-29T14:23:06ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Rt2x00_beta_driver&diff=28013Rt2x00 beta driver2007-08-25T12:47:51Z<p>StANTo: Adjustments on situation with rt2570/2500 adapter and rt2x00 package in unstable.</p>
<hr />
<div>[[Category:Communication and network (English)]]<br />
[[Category:HOWTOs (English)]]<br />
This page describes how you can make the new '''rt2x00''' Beta drivers work. This page '''does not''' describe the legacy '''rt2500''', '''rt2400''' and '''rt2570''' drivers derived from the original Ralink drivers.<br />
<br />
At the time of this writing, only the '''rt2560''' PCI and PcCard chipsets ('''rt2500pci''' driver) are known to work in Open, WEP or WPA (PSK and EAP) mode. So far, there are no success stories with '''rt2400pci''', '''rt2500usb''' and '''rt61pci''' drivers. If you succeed in using these drivers, please add a comment here.<br />
<br />
// Currently the rt2500/2570usb adapter component is still in development. It should work and associate with an AP, then gain an IP from DHCP but the connection works intermittantly. NDiswrapper is recommended until fixed.<br />
<br />
The '''rt2x00''' drivers are supposed to work with SMP kernels, but I did not test this myself. Please add comments here if you were able to use the driver with an SMP kernel.<br />
<br />
There are still many issues with this driver. Many people experienced crappy speed. To help solve these issues, everyone who is willing to test the new driver should look at the [http://rt2x00.serialmonkey.com/phpBB2/viewforum.php?f=5 rt2x00 BETA Testing] section of the rt2x00 forums.<br />
<br />
<br />
= Installing the driver =<br />
<br />
The '''rt2x00 Beta 3''' (as posted in the AUR) and older version are known to '''NOT WORK'''. In order to have a working driver, you '''MUST''' use the new rewrite based on the DeviceScape stack. This new driver is (at the time of this writing) only available as a [http://rt2x00.serialmonkey.com/rt2x00-cvs-daily.tar.gz CVS snapshot]. To install the driver, unpack the driver, change to the '''rt2x00-cvs-2006XXXXXX''' directory and type<br />
<br />
make<br />
make install<br />
<br />
There is a package for this in [unstable] that currently has no maintainer, it is advised you use the latest snapshot. Grab the pkgbuild from CVS here: http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/modules/rt2x00/?cvsroot=Unstable<br />
<br />
If it is the '''rt61''' driver you need, you'll also have to manually install the '''firmware''' [http://www.ralinktech.com.tw/data/RT61_Firmware_V1.2.zip from RaLink]. To proceed, create a /lib/firmware directory -if you don't have one already- and place the *.bin files inside. (NB: this firmware is likely to be soon included into rt2x00.serialmonkey tree)<br />
<br />
= Using the driver =<br />
<br />
== Setting the interface up ==<br />
<br />
If you have module autoloading enabled, the drivers should be loaded automatically when you boot your machine or insert the device. If this doesn't work or autoloading is disabled, load the modules manually:<br />
<br />
modprobe 80211<br />
modprobe rc80211_simple<br />
modprobe $driver<br />
<br />
where $driver is one of the following: '''rt2500pci''', '''rt2400pci''', '''rt2500usb''' or '''rt61pci'''.<br />
<br />
When the driver is loaded, you will have two interfaces, wmaster0 and wlan0.<br />
<br />
== Using the driver ==<br />
<br />
In the case of these drivers, the order in which you configure them is important.<br />
<br />
ifconfig wlan0 up<br />
iwlist wlan0 scan<br />
iwconfig wlan0 essid myessid<br />
iwconfig wlan0 ap mybssid <br />
<br />
Is the preferred, and most likely to work order of configuring the device. From there you can use '''ifconfig''' or '''dhcpcd''' to get an IP, and wep or wpa if needed.<br />
<br />
= Extra utils for wep/wpa =<br />
<br />
== wpa_supplicant ==<br />
<br />
rt2x00 should work fine with the wpa_supplicant '''wext''' driver. It is not necessary to patch it any more.<br />
<br />
== Using wpa_supplicant ==<br />
<br />
For example, to use wpa_supplicant, try<br />
<br />
/usr/sbin/wpa_supplicant -wB -Dwext -iwlan0 -c/etc/wpa_supplicant.conf<br />
<br />
Note that wpa_supplicant didn't work with hidden essid in my tests.<br />
<br />
// TODO: someone please confirm that wpa_supplicant also successfully associates to open or wep-encrypted networks, I only tried WPA-PSK and read success reports about WPA-EAP<br />
<br />
== Using WEP ==<br />
<br />
WEP should work with the Wireless Extensions used by iwconfig.<br />
<br />
// TODO: Some please confirm that this works<br />
<br />
= Configuring the driver for automatic startup on booting =<br />
<br />
== RT2400 (rt2400pci) ==<br />
The following is known to work for the cvs snapshot available [http://rt2x00.serialmonkey.com/wiki/index.php?title=Downloads here] with the date 23-Dec-2006.<br />
<br />
To set the driver up for automatically connecting while the computer is booting, type the following in /etc/rc.conf<br />
<br />
wlan0="wlan0 192.168.1.102 netmast 255.255.255.0 broadcast 192.168.1.255"<br />
INTERFACES=(lo !eth0 wlan0)<br />
<br />
And the following in /etc/rc.local<br />
<br />
iwconfig wlan0 channel 10<br />
iwconfig wlan0 essid linksys<br />
iwconfig wlan0 ap 00:0c:41:a8:87:8e <-- Put your access point's bssid here</div>StANTohttps://wiki.archlinux.org/index.php?title=Concurrent_Versions_System&diff=28012Concurrent Versions System2007-08-25T12:41:44Z<p>StANTo: Section 06 had cvs initialise command arranged incorrectly.</p>
<hr />
<div>[[Category:Networking (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
01) Open up a shell<br />
<br />
<br />
02) su to root<br />
<br />
<br />
03) Make sure you have the latest version of CVS<br />
pacman -Sy cvs<br />
<br />
<br />
04) Make sure you have the latest version of xinetd<br />
pacman -S xinetd<br />
<br />
<br />
05) Now create the directory that will become your CVS repository.<br />
mkdir /home/cvsroot<br />
<br />
<br />
06) Initialize your CVS repository<br />
cvs -d /home/cvsroot init<br />
<br />
<br />
07) Create a group called cvs - members of this group will have write access to the repository<br />
groupadd cvs<br />
<br />
<br />
08) Create a user named cvs<br />
useradd -d /home -g cvs -p password cvs<br />
<br />
<br />
09) Set the owner and group of the repository<br />
chown -R cvs:cvs /home/cvsroot<br />
<br />
<br />
10) Set the proper permissions for the repository(set group ID, owner: read write execute, group: read write execute, others: read execute)<br />
chmod 2775 /home/cvsroot<br />
<br />
<br />
Add any users that you want to have local access to the repository to the group cvs by using the following two steps.<br />
<br />
<br />
11) Get a list of the groups for a user.<br />
groups someuser<br />
<br />
<br />
12) Set the groups for the user. The group1 group2 etc. are the groups you got from the previous step. '''NOTE: make sure not to use spaces when listing the additional groups'''<br />
usermod -g users -G group1,group2,group3,cvs someuser<br />
<br />
<br />
13) Make a file in /etc/xinetd.d/ called cvspserver with these contents:<br />
<br />
service cvspserver<br />
{<br />
port = 2401<br />
socket_type = stream<br />
protocol = tcp<br />
wait = no<br />
user = root<br />
passenv = /home/cvsroot<br />
server = /usr/bin/cvs<br />
server_args = -f --allow-root=/home/cvsroot pserver<br />
}<br />
<br />
14) Edit /etc/services and add cvspserver service if does not exist:<br />
cvspserver 2401/tcp #CVS PServer<br />
<br />
<br />
15) Create some files in CVSROOT<br />
/home/cvsroot/CVSROOT/passwd # user and passwd, refer to the following<br />
<br />
anonymous::<br />
lnzju:YKy0EJBP5vDpY:cvs<br />
<br />
<br />
/home/cvsroot/CVSROOT/writers # users that have write permission of the repository,every user take a newline<br />
lnzju<br />
/home/cvsroot/CVSROOT/readers # users that have read permission of the repository,every user take a newline<br />
anonymous<br />
<br />
16)Allow clients to connect to the Server<br />
edit /etc/hosts.allow ,add a newline ,as the following<br />
<br />
cvs:ALL<br />
<br />
<br />
17) You must unset the variable HOME before you restart xinetd<br />
unset HOME<br />
<br />
<br />
18) Restart the xinetd server<br />
/etc/rc.d/xinetd restart<br />
<br />
<br />
You can test out the server using the following commands:<br />
<br />
export CVSROOT=:pserver:my_user_name@127.0.0.1:/home/cvsroot<br />
cvs login<br />
mkdir ~/sandbox<br />
mkdir ~/sandbox/myproject<br />
cd ~/sandbox/myproject<br />
echo "this is a sample file" > myfile<br />
cvs import -m "description of myproject" myproject v1 r1<br />
cd ..<br />
rm -R myproject<br />
cvs checkout myproject<br />
cd myproject<br />
echo "some changes to the file" >> myfile<br />
cvs commit -m "Explain changes here" myfile</div>StANTo