how to use ipw3945?

iggy · 2006-05-06 14:27:22

hello!

i want to know, how to use the new ipw3945 drivers. i know, that i have to start the regulatory deamon to use the adapter. any ideas? can i do it like that?

3. AUTOMATIC DAEMON LOADING VIA MODPROBE
-----------------------------------------------

There are some typical steps that are fairly generic in order
to automate the launching of the daemon you can use your
distribution's modprobe configuraiton. To do this, you need to copy
ipw3945.ko into your depmod path. This is typically done via:

# cp ipw3945.ko /lib/modules/$(uname -r)
# depmod -a

Now, when you run modprobe it will load the module (and any depdencies,
such as ieee80211.ko) and modprobe -r will remove the module. The next
step is to automate the launching and unloading of the regulatory
daemon. To do this, you typically place the following two lines into
your /etc/modprobe.conf or into a new file /etc/modules.d/ipw3945:

# echo install ipw3945 /sbin/modprobe --ignore-install ipw3945 ; 
sleep 0.5 ; /sbin/ipw3945d --quiet >> /etc/modules.d/ipw3945

# echo remove ipw3945 /sbin/ipw3945d --kill ; 
/sbin/modprobe -r --ignore-remove ipw3945 >> /etc/modules.d/ipw3945

NOTE: The  above is to continue the entered line to the next line (the
lines added to the file are wider than 80 columns and so would wrap)

On some distributions you then may need to run the 'modules-update'
script.

To verify if the above is working, you can type:

# modprobe ipw3945
# ps -C ipw3945d

If you see a running 'ipw3945d' then it launched the daemon for you.

thanks for help.
mfg iggy

iphitus · 2006-05-06 14:40:27

um... read those instructions.

marteus · 2006-05-26 21:47:50

The daemon script would be nice to have in the package. It works a whole lot better (for me) than the modprobe version.

iphitus · 2006-05-27 00:08:20

Thanks. I'll add that to the package. it's much nicer than what I had, and admittedly, I just ran with it because I was in a hurry to get it into the repos.

James

marteus · 2006-06-21 09:07:26

The daemon script has gotten the path to the binary daemon wrong (or the reverse?), ipw3945d is located in /sbin, not in /usr/sbin.

And is there any reason why the script is called ipw3945d.rc?

iphitus · 2006-06-21 11:32:01

fixed both bugs.

marteus · 2006-06-21 19:19:13

This is kinda weird:

The updated daemon wont work, or rather the network daemon fails at boot. When running the network daemon a second time it works (after login)

But I do have a solution: Add a sleep 0.5 after the /sbin/ipw3945d is called.

The weird part is that I have several daemon loading (not in loading background) between ipw3945d and network in the DAEMONS array.

phrakture · 2006-06-22 15:51:09

tolkan wrote:

Those instructions are not very helpful for those that use Archlinux. The syntax for the suggested commands is even incorrect.

Archlinux uses the exact same modprobe command as every other linux distro. It works the same.

phrakture · 2006-07-10 19:28:54

Yeah, on a personal level, I would highly recommend everyone opt out of this hardware on Linux, if you can (my thinkpad let me select an Atheros chipset instead).

The reason being that this crappy daemon is actually used as a way to get around GPL licensing, so that Intel doesn't need to open up their driver technology. Well they can bite me. It's moves like that that make me refuse to buy any IPW hardware for a long time.

fk · 2006-07-10 20:31:33

Yeah, on a personal level, I would highly recommend everyone opt out of this hardware on Linux, if you can (my thinkpad let me select an Atheros chipset instead).
The reason being that this crappy daemon is actually used as a way to get around GPL licensing, so that Intel doesn't need to open up their driver technology. Well they can bite me. It's moves like that that make me refuse to buy any IPW hardware for a long time.

The problem, I can't change the wireless card, i have had only these, and now I have these card.

marteus · 2006-07-21 12:39:29

marteus wrote:

This is kinda weird:
The updated daemon wont work, or rather the network daemon fails at boot. When running the network daemon a second time it works (after login)
But I do have a solution: Add a sleep 0.5 after the /sbin/ipw3945d is called.
The weird part is that I have several daemon loading (not in loading background) between ipw3945d and network in the DAEMONS array.

This issue has reappeared with 1.7.22.
In the source package two scripts were added (start/stop daemon) so perhaps they are must be merged into the ipw3945d.rc daemon script?

Arch Linux

#1 2006-05-06 14:27:22

how to use ipw3945?

#2 2006-05-06 14:40:27

Re: how to use ipw3945?

#3 2006-05-26 21:47:50

Re: how to use ipw3945?

#4 2006-05-27 00:08:20

Re: how to use ipw3945?

#5 2006-06-21 09:07:26

Re: how to use ipw3945?

#6 2006-06-21 11:32:01

Re: how to use ipw3945?

#7 2006-06-21 19:19:13

Re: how to use ipw3945?

#8 2006-06-22 15:51:09

Re: how to use ipw3945?

#9 2006-07-10 19:28:54

Re: how to use ipw3945?

#10 2006-07-10 20:31:33

Re: how to use ipw3945?

#11 2006-07-21 12:39:29

Re: how to use ipw3945?

Board footer