ipw3945 wireless drivers

djtreble · Posted: Wed Mar 08, 2006 1:08 pm Post subject:

rmh3093: that inut script works like a charm, thank you.

I added

rmh3093 · Posted: Wed Mar 08, 2006 5:47 pm Post subject:

Ok people here are some new ebuilds for people to play with.... Thanks again VinzC for starting this project.

New

svn to make updates easier
requires in-kernel IEEE80211 subsystem
corrected paths so downloads dont fail
ditched the license
ipw3945d includes rc-script
useflags for QoS and RFmon

Setup

djtreble · Posted: Sat Mar 11, 2006 6:51 am Post subject:

rmh3093 · Posted: Sat Mar 11, 2006 1:37 pm Post subject:

Jobbe · Posted: Sun Mar 12, 2006 8:18 pm Post subject:

I keep on getting this error:

VinzC · Posted: Sun Mar 12, 2006 9:28 pm Post subject:

@Jobbe:

Make sure you disabled built-in support for IEEE80211 in your kernel and have run

Jobbe · Posted: Sun Mar 12, 2006 9:39 pm Post subject:

Oh I thought I had to build it into the kernel because of

VinzC · Posted: Mon Mar 13, 2006 9:47 pm Post subject:

Serph · n00b Joined: 04 Aug 2005 Posts: 24

Hi, I originally removed IEEE80211 from the kernel. How can I add it back in? I'd really like to try rmh3093's ebuilds.

Thanks!

Jobbe · Posted: Tue Mar 14, 2006 8:36 am Post subject:

It's in 'networking'.

VinzC thanks for your reply. I'll tell y'all later how I'm doing ^^

Jobbe · Posted: Tue Mar 14, 2006 10:52 am Post subject:

Allright, this is for rmh3093's ebuilds:

I can't get them to compile. I upgraded to the most recent gentoo-sources in portage I could find (2.6.15-r7), ieee80211 support is enabled (tried both in-kernel and as a module), still, ipw3945 will not compile, failing with the error messages I posted above.

I guess I'll try VinzC's aproach now...

EDIT:

Weehaa, it worked. Thanks for the work & help :]

djtreble · Posted: Tue Mar 14, 2006 1:38 pm Post subject:

Just to add my 2c.

I couldn't get rmh3093's ebuild to work with my built in kernel headers even though vanilla linux-2.6.16-rc6 has version 1.1.17 of ieee80211 I _think_

The first error was an undeclared ieee80211_action structure, if I remember correctly.

I convinced myself that in kernel 1.1.17 wasn't new enough and went back to VinzC .70 ebuild with rmh3093's init script. This is working fine.

rmh3093 · Posted: Tue Mar 14, 2006 3:36 pm Post subject:

i think the error i was getting with IEEE80211 in portage had to do with -mm sources so in the next revision of the ebuild I will check your kernel version.... if you are using -mm sources it will use the inkernel ieee80211 if not it will ask for the version in portage... i bet this would fix your problems...... sorry guys for causing some problems, i cant use a non -mm kernel with out my system crashing
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.

Jobbe · Posted: Tue Mar 14, 2006 6:27 pm Post subject:

No need to be sorry at all

I'd be happy to test your ebuild once it's updated.

VinzC · Posted: Tue Mar 14, 2006 6:54 pm Post subject:

Jobbe · Posted: Thu Mar 16, 2006 9:49 am Post subject:

After a bit of using the driver I'm really happy. It works, although almost every other time I have to do the modprobe/dhcp calls by hand. I have no idea why, possibly the driver is just a little immature. But even if I have to do this, it still works like a charm afterwards. Thanks for the help&work guys!

VinzC · Posted: Thu Mar 16, 2006 6:37 pm Post subject:

Hmmm... strange. It doesn't happen on my system and I must admit I never had to restart the network connection in a week of daily usage.

Have you run the regulatory daemon? Have you also tuned the module configuration file to run the daemon as soon as the module is loaded?
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!

Jobbe · Posted: Fri Mar 17, 2006 11:51 am Post subject:

Yeah that's what I did. It _is_strange especially considering that if I do the worx by hand there never is a problem. I have to unload the daemon (it's obviously started yet the module can't be loaded - weird) and then modprobe ipw3945 again.

VinzC · Posted: Fri Mar 17, 2006 1:04 pm Post subject:

Jobbe · Posted: Fri Mar 17, 2006 3:31 pm Post subject:

Uh no I do the following:
modules.autoload.conf: ipw3945
...
...
...
runlevel default: net.eth1

The daemon is loaded by the module, I set it up the way you showed on the first page of this thread.

VinzC · Posted: Mon Mar 20, 2006 10:34 pm Post subject:

Then I'm afraid I have no idea

.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!

Jobbe · Posted: Tue Mar 21, 2006 12:03 pm Post subject:

Yeah well it's not too annoying...
Kinda weird though, I noticed that sometimes not even eth0 (e1000 intel adapter) is found and sometimes the system seems to confuse the both of them...

I don't know what's wrong, but it does work most of the time, so, I don't really care

Sejam · Tux's lil' helper Joined: 25 Oct 2004 Posts: 80

rmh3093 · Posted: Thu Mar 23, 2006 10:56 pm Post subject:

Sejam · Tux's lil' helper Joined: 25 Oct 2004 Posts: 80

For those of you that previously owned the Inspiron 6000 which had the Intel 2200, have you noticed a decrease in range with the 3945? Didn't realize it last night, but I'm not able to get as good as a signal as I did with the 2200 in my house.