You are not logged in.
For the running netcfg twice thingy...
Use netcfg from testing, and try various combinations of the quirks option. There's bound to be a combination that will work for you.
For the rmmod/modprobe driver, try PRE_UP="rmmod iwl3945; modprobe iwl3945"
Offline
Another thing I'm confused about is how to get the connection to automatically connect on boot. I tried following the instructions in the Network Profiles wiki entry (http://wiki.archlinux.org/index.php/Network_Profiles), but I can't find a NETWORKS=() line in my rc.conf. Is NET_PROFILES=() the line it's talking about, INTERFACES=(), or do I need to make a new line?
In my /etc/rc.conf there is the following section:
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
NETWORKS=(home)
Where "home" is my network profile. So if this section isn`t present in your /etc/rc.conf than try to add at least this line: "NETWORK=(*profile*)" (where *profile* should be edge1 in your case I gess). Now netcfg2 should try to connect to your network during booting.
Top_se
Offline
I do have a similar section in my rc.conf:
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network-profiles
#
NET_PROFILES=(edge1)
And that's what I have. Netcfg2 doesn't start automatically, though. This may be because of the rmmod/modprobe thing. I'll also try iphitus' suggestion.
-Vert
---------
Free webhosting@http://shadowserve.ath.cx - Currently and soon to go through many changes, still alive! - June 29, 2009
Offline
Regarding the modules: please try leaving them both in rc.conf, albeit transposing their order (the second one first).
About the network manager: I strongly suggest using wicd (http://wiki.archlinux.org/index.php/Wicd). If it works, you may even load it when the system boots up, by a simple modification of rc.conf. Follow the wiki.
Offline
Hello vertimyst
I do have a similar section in my rc.conf:
# Enable these network profiles at boot-up. These are only useful # if you happen to need multiple network configurations (ie, laptop users) # - set to 'menu' to present a menu during boot-up (dialog package required) # - prefix an entry with a ! to disable it # # Network profiles are found in /etc/network-profiles # NET_PROFILES=(edge1)
And that's what I have. Netcfg2 doesn't start automatically, though
NET_PROFILES is the line the former netcfg (version 1) used, since you are using netcfg2, this line must be changed into NETWORKS=(...)
And when you can make sure that the deamon net-profiles and the modules for your wifi card are loaded correctly (iphitus` sugestion is very very helpful in this case!) than netcfg2 will start automatically during booting.
good luck!
Offline
Well, I've managed to get netcfg2 to try and connect on boot, but it fails because I still need to rmmod/modprobe iwl3945 after bootup, as well as run netcfg2 edge1 twice. First time I get 'Wireless association failed', second time works. I'm using netcfg 2.1.0_RC-1 from testing, with some quirks options in my network profile (right place?).
Where do I put PRE_UP="rmmod iwl3945; modprobe iwl3945"? In rc.conf, my network profile..?
Last edited by vertimyst (2008-08-09 17:43:59)
-Vert
---------
Free webhosting@http://shadowserve.ath.cx - Currently and soon to go through many changes, still alive! - June 29, 2009
Offline
I'm using netcfg 2.1.0_RC-1 from testing, with some quirks options in my network profile (right place?).
jup, right place, but there is no garantee that it works ... just try around a little bit
Where do I put PRE_UP="rmmod iwl3945; modprobe iwl3945"? In rc.conf, my network profile..?
put this as another line into your network profile.
Offline
Still no luck, during bootup, I get these messages (or similar):
Starting network: [failed]
eth0 not responding
edge1 up [failed]
eth0 is logical because it's mywired connection, which I'm not using at the moment. At least netcfg2 is trying to start my wireless, but it's failing because I have to rmmod/modprobe after I log in. The line I added to my network profile doesn't seem to be making a difference in that regard.
Edit: Oddly, when I booted up today, I was unable to start my network via netcfg2 edge1. I was able to connect by following the Wireless Quickstart directions in the Wireless Setup wiki, though, something I couldn't do before. Weird.
Last edited by vertimyst (2008-08-11 20:26:53)
-Vert
---------
Free webhosting@http://shadowserve.ath.cx - Currently and soon to go through many changes, still alive! - June 29, 2009
Offline
All I did to get my 3945 to work was:
1. Install iwlwifi-3945-ucode via pacman (everything else in kernel)
(not running a custom kernel are you?)
2. Blacklist (!ipw3945) the old 3945 driver module in rc.conf
3. Ensure the new (@iwl3945) driver is loaded via rc.conf
5. Install wicd package (simple software that "just works")
4. Config the wireless card:
http://wiki.archlinux.org/index.php/Wicd
Dont forget to start the wicd daemon via rc.conf after you get it configured.
It really should be that simple; follow the wicd wiki page very closely.
Offline
All I did to get my 3945 to work was:
1. Install iwlwifi-3945-ucode via pacman (everything else in kernel)
(not running a custom kernel are you?)
2. Blacklist (!ipw3945) the old 3945 driver module in rc.conf
3. Ensure the new (@iwl3945) driver is loaded via rc.conf
5. Install wicd package (simple software that "just works")
4. Config the wireless card:
http://wiki.archlinux.org/index.php/Wicd
Dont forget to start the wicd daemon via rc.conf after you get it configured.
Regarding #2, you don't need to blacklist ipw3945. Simply remove it from the MODULES array if present.
Regarding #3, the @ symbol implies it is a daemon service, which it isn't. Add iwl3945 to the MODULES array, not the DAEMONS array.
thayer williams ~ cinderwick.ca
Offline
Thanks for the help, but I still need to run rmmod iwl3945 and modprobe iwl3945 every time I boot. Other than that, though, my wireless is working fine now. wicd is really handy!
-Vert
---------
Free webhosting@http://shadowserve.ath.cx - Currently and soon to go through many changes, still alive! - June 29, 2009
Offline
I would like to chime in on this thread. I have the same problem on my HP 6510b with the iwl3945 wireless card. I've even upgraded to the latest BIOS version. (Should I reinstall Arch after a BIOS upgrade?)
Here's some info:
$ dmesg | grep 3945
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
iwl3945: Copyright(c) 2003-2008 Intel Corporation
iwl3945: Detected Intel Wireless WiFi Link 3945ABG
iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels
phy0: Selected rate control algorithm 'iwl-3945-rs'
iwl3945: Failed to register network device (error -12)
iwl3945: probe of 0000:10:00.0 failed with error -12
To 'fix' the problem I have to do:
$ rmmod iwl3945
$ modprobe iwl3945
Its strange, the drivers actually load during boot, but the interface isn't created. 'lsmod | grep 3945' shows it loaded, but there is no wlan0 interface when I 'ifconfig -a'. I have to unload then reload the drivers for it to create the interface. After that I can connect to my AP with no problem.
As a side note, I also tried it with a patched driver (aircrack-ng fragmentation patch). Aside from the above problem it would give me a kernel panic when I:
$ iwconfig wlan0 essid MyESSID key 1234567890
Even with the kernel panic problem when I tried to connect to my AP, aircrack-ng actually worked great! Cracked APs are useless if I can't connect to them (I know, I know...shame on me) so I uninstalled the patched drivers and went back to the original.
It would be nice if there was a solution to 'error -12' instead of just fix. The solution is far beyond my capabilities. Im a linux n00b.
Thanks for the help, the Arch community, the great wiki, and of course a fantastic distro!
Offline
http://www.intellinuxwireless.org/bugzi … gi?id=1212
Apparently the solution is to compile mac80211 directly into the kernel, rather than a module. I don't get error -12, so I haven't tried it.
Offline
Thanks for the link. Messing with the kernel might be a little beyond me right now...not that thats going to stop me from trying! When I have some time research how to actually go about doing it I'll give it a try. If I have any luck I'll report back here.
Offline
Just wanted to post a quick update on this issue...
I never did get around to compiling the driver into the kernel. Instead I ended up reinstalling. This time I switched to i686 from x86_64 (for different reasons) and now everything works nicely.
Thanks for the help anyways.
Offline
Are you sure arch loads the firmware?
In my case I had to add the firmware hook to /etc/mkinitcpio.conf, and reinstall the kernel to get iwl3945 working and ofc, blacklist ipw3945d and ipw3945.
edit: aww :\ too late
Last edited by Themaister (2008-09-12 05:57:23)
Offline