Arch Linux

Gerenuk81

Member

Registered: 2007-09-15

Posts: 14

Connect knetworkmanager manually twice before rt61connection works?

With quite a recent ArchLinux I'm using the rt61 module to work with the wireless card. I do that with the knetworkmanager, however I have to start the initialization manually twice before it finally works. Thus, I click connect (thought I should do automatically on startup?!) and I have a connection for a few seconds. Only after connecting the second time, the connection is stable.

My setup is:

rc.conf:

MODULES=(forcedeth nvidia rt61pci)
...
wlan0="dhcp"
INTERFACES=(lo)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
...
#NET_PROFILES=(main)
...
DAEMONS=(syslog-ng !network netfs crond gpm dbus hal dhcdbd networkmanager)

wpa_supplicant.conf

...
network={
 ssid="SSID"
 psk="PASSWORD"
 priority=2
}

network-profiles/main

DESCRIPTION="Default Network Profile"

INTERFACE=eth0
HOSTNAME=NAME
IFOPTS="192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255"
ESSID=SSID
IWOPTS="mode managed essid $ESSID channel 11"
WIFI_INTERFACE=wlan0
USEWPA="yes"

Is there anything wrong? Is that the best way to have wireless with rt61?

Anton

Dirhael

Member

From: /cold/north

Registered: 2008-03-12

Posts: 46

Re: Connect knetworkmanager manually twice before rt61connection works?

I had to give up on using the rt61pci module as it simply was to unreliable with my card. It would work, but drop the connection frequently (as soon as you put any stress on it, it breaks down). Ndiswrapper on the other hand have been rock stable on both i686 (using the XP driver) and x86_64 (using the Vista 64 driver).

carlocci

Member

From: Padova - Italy

Registered: 2008-02-12

Posts: 368

Re: Connect knetworkmanager manually twice before rt61connection works?

I had to give up on using the rt61pci module as it simply was to unreliable with my card. It would work, but drop the connection frequently (as soon as you put any stress on it, it breaks down). Ndiswrapper on the other hand have been rock stable on both i686 (using the XP driver) and x86_64 (using the Vista 64 driver).

yeah, the same for me: the steps to make it work everytime I change/upgrade something require too much "magic".
I will try compiling the CVS driver before trying Ndiswrapper though.

edit:
The hourly CVS tarball you can find here, http://rt2x00.serialmonkey.com/rt61-cvs-daily.tar.gz, seems to work well.

Last edited by carlocci (2008-03-24 13:47:50)