Intel Wireless driver

[J.Picard]

Hi Jalavoui,

here comes the new logs from rev 481.

And thanx for adding the revision numbers on the download page!

 

Status:

My LED is blinking and i have no switch to turn on or off.

So it is new, that i can edit the network settings without a kernel panic. But there's no way to change everything. With networkselector it's the same. No ethernet adress is forund for device en2.

 

When i start the system with verbose mode, the iwi2100 driver shows several lines. How can i get this lines?

In my console-program, i can only get the lines to callisto, not before!

system.txt

ioreg.txt

dmesg.txt

[spu]

Hi Mark1970,

 

my problem is just opposed to that you told me.

My 2200bg can be always detected by mac os and I can find some wlan with it and perhaps also connect to someone if there would be someone unsecured. The driver works well in mac os. The switcher and the LED don't work.

 

My problem is:

I cannot use the 2200bg card any more after rebooting into the multibooted windows or linux.

Jalavoui said, the driver manipulates the card to accept the fake values 0x50001 (instead of 0x50000) to be turned on although the switcher is off. He said that it can make the switcher fail to work. It did it and now I cannot make the switcher work again because the way, which Jalavoui told me to change the values, didn't work for me. My card doesn't react on the switcher in mac os.

 

The driver iwi2200 in mac os shuts my 2200bg card off after logging out and my card doens't react on the switcher. So windows and linux cannot use it or activate it. "The switcher is off."

 

What could I do now? I'm sorry that I write so many posts to my problem because since this week I have only one way to get the internet without other's computer, via an encrypted wlan. So I hope someone could help me.

 

Thanks a lot.

spu

[jalavoui]

Hi Jalavoui,here comes the new logs from rev 481.

you have in your log:iwi2100: disable 1 mode 0delete the extensions cache files and post the logs again. also try to use option (1) of networkselector.

the way, which Jalavoui told me to change the values, didn't work for me. My card doesn't react on the switcher in mac os.

this could be because of a hardware problem with your card. can you post the last logs you get in mac os?

[wanahakaluggie]

rev. 488

dmesg.txt

ioreg.txt

system.txt

[Contego Lupus]

Hi Guys

I've got OSx86 Jas 10.4.8 installed successfully on my Dell XPS M1710

I'm trying to get my intel proset wireless 3945abg card to work on iwi3945.kext rev 482

is there anything I can do to help test this driver?

 

[install]

-mounted the dmg file

-copied network selector to applications/utilities/

-ran network selector to configure the card, returned the message - could not recieve id from kernel 2

-installed the package anyways

-ran the network selector

 

i get the following:

 

"

Welcome to insanelyMac Spaceport 0.1

Adaptor en0 (00:18:de:69:0b:f9) [mode: 0 led: on]

...

"

 

the led doesn't function

none of the options appear to function

Network List displays

 

"

Hello World: send network list

"

 

but that's about it

would love to get this working so anything i can do to help you guys let me know

[R4ME]

anyone know how to fully make the 3945ABG card work????

 

like a step by step procedure?

i'm new to mac...

but not to learning

[J.Picard]

you have in your log:iwi2100: disable 1 mode 0delete the extensions cache files and post the logs again. also try to use option (1) of networkselector.this could be because of a hardware problem with your card. can you post the last logs you get in mac os?

 

And here comes the new logs after deleting the kextcache. I've tried all options, but i think the problem is, that in networkselector is no ethernet adresse.

I have no switch on the device, so i cannot turn the card on or off. The software has to make it.

 

The log file contains the last booting logs...

I hope that can help you.

dmesg.txt

ioreg.txt

system.txt

logs.rtf

[Tanob]

Hello guys,

 

my OSX was installed with the version 10.4.9 of uphuck, and my wireless card is the 3945ABG.

 

Follow attached the logs (not dmesg.txt 'cause it is empty) testing with the rev 482.

ioreg.txt

system.txt

[jalavoui]

iwi2100/3945/4965

 

for developers:

 

the mac address is wrong in the latest releases. this can be fixed in the start() function.

old releases report a valid mac address but lead to other errors.

 

i'd like to use iwi2200 code to fix this but it need some changes...

 

can someone try to fix this?

[spu]

Hi Jalavoui,

 

here are my last system logs. I hope you can help me to find out why the wlan card doesn't react on the switcher and perhaps how I could get the card run again in windows.

 

Thanks a lot.

spu

System_20070803.txt

System_20070813.txt

dmesg_20070813.txt

[m!Ka]

hi, I a complete noob in mac, I just installed it 2 days ago and I've never seen a mac desktop b4.

Anyway the only thing thats not working is the wireless card intel 2100b. so i thought I'd post my logs 2 help.

 

Version of iwi: Intel PROset/Wireless 2100 rev 481

iwi message logs: attached

Mac OS X version: 10.4.9

What you were doing when the bug occured:

nothing it just never gets a mac address, doesnt find networks, only action that works is turn off led, it turns off but the network selector still says its on

Kernel version: ????

IO80211Family version:???

 

 

thanxs.

dmesg.txt

ioreg.txt

system.txt

[JustJoe]

Version of iwi: Intel PROset/Wireless 2100 rev 481

iwi message logs: attached

Mac OS X version: 10.4.9

What you were doing when the bug occured:

nothing it just never gets a mac address, doesnt find networks, only action that works is turn off led, it turns off but the network selector still says its on

Kernel version: ????

IO80211Family version:???

Now if we could just get everyone to read the FAQs znd post decent log details like m!Ka here, we could be getting a lot farther with development.

Thanks m!Ka.

 

[R4ME]

iwi3945 ^{rev 482}

Freshly Installed - Uphuck 10.4.9 v1.4i

 

Doesn't work, all I get is this...

 

Could not get ID for kernel control. 2

 

 

ioreg.txt

system.txt

dmesg.txt

 

 

Any developer know what's wrong with my system?

[JustJoe]

ioreg.txt

system.txt

dmesg.txt

 

Any developer know what's wrong with my system?

please go to our google code site and download the getlogs3.command.zip tool.

logs are hard enough to go through without a bunch of extraneous information.

 

Thanks

[themessenger500]

Hi

 

I'm having trouble with the recent builds for 2200/2915 even though one of the original 2200 builds worked fine (since deleted for the upgrade). My card is the 2915 and it is claimed to be supported. It will turn on, scan and list available networks; however, when I select an unsecured network (several attempted) to connect to, seconds later the card will be off and I cannot get any further than that.

 

I do not have a log. But if this is a common problem, please let me know what the fix is. I've uninstalled cleanly and reinstalled multiple times to the same effect.

[tprins228]

logs from latest., MAC is no longer ffffff... its now all just zeros.

dmesg.txt

ioreg.txt

system.txt

[Evil_Cartman]

Here's logs of rev.482 for 3945a/b/g on Benq Joybook R55, Uphuck 10.4.9

 

As I said before, NetworkSelector utility does just nothing except turning card On and Off.

It provides no networks lists.

 

H/W switch for theese logs definitely was turned On just before boot.

dmesg.txt

ioreg.txt

system.txt

[auqs10]

Hi to all of you, after installing the 482 version for iwi3945, the card was associated as en2 in the NetworkInterfaces.plist even though was supposed to upgrade the previous version that remained as en1 in the interfaces list. Another observation is that the new 482 has losed the MAC address, as all the previous versions at least associated something. Now, the MAC address was full of pears of zeros, and the ERROR #0 was reported. The notebook became slower and I had to remove all the lines in the NetworkInterfaces.plist, also the iwi3945.kext and finally from the Network Preferences items listed. So, still no success for this wireless card Intel 3945. I am sorry that I can not help because I have no knowledge on programing, I am able just to test the versions released. Thank you for all your persistence on helping us.

[AkshayGenius]

Hi guyz, Im planning to install os x x86 on my laptop, and obviously without internet, there is probably no point for me installing it. As there are 131 pages and I have just come here now, I would like to ask what is the status of the 2200 bg wireless card? does it work, still in progress or no development, in os x86 wiki, the 2200bg should work, but I just wanted to confirm...

 

Thanx,

Ak

[youngi]

yes it works, look through the topic, there is a working driver for the 2200

[zipper]

I wish to contribute however i am not technically inclined. However here is what i tested with my IBM TP60 which has an Intel 3945 wireless.

 

As all here know that with the OSX86 installed, the 3945 is still not working. But when i installed Ubuntu 7.04, the 3945 works right away.

 

I was wondering if the driver from the Ubuntu can be used in OSX86? I am a PC user so don't know if this idea is stupid enough but i see there is some similarity between the 2 OSes... just wondering..

[Jaap-Jan van der Veen]

I wish to contribute however i am not technically inclined. However here is what i tested with my IBM TP60 which has an Intel 3945 wireless.

 

As all here know that with the OSX86 installed, the 3945 is still not working. But when i installed Ubuntu 7.04, the 3945 works right away.

 

I was wondering if the driver from the Ubuntu can be used in OSX86? I am a PC user so don't know if this idea is stupid enough but i see there is some similarity between the 2 OSes... just wondering..

 

As a matter of fact, the ipw3945 driver from Linux (and thus from Ubuntu too) is used as the starting point for the driver being developed here. But no, a driver written for Linux cannot be used directly. Because of the radically different driver models between OS'es.

 

At first you have the programming language. Linux drivers are written in plain C, while drivers written for Mac OS X are implemented in some subset of C++. Now, that isn't a big problem, because C++ is 'as close backwards compatible to C as possible, but no more'.

 

But then you have API's which are incompatible between OS'es. A lot of effort goes into trying to adapt this Linux driver (with Linux API) to a driver using the IOKit API.

 

And (in this special case), you have another problem: the IOKit API which allows for wireless communication (com.apple.iokit.IO80211Family) isn't public, so developing a driver with this framework is difficult. That's why they are developing an ethernet driver and a separate tool to configure the network. Of course, a wired network doesn't know anything about ESSID's, WEP/ WPA/ WPA2- keys and so on, so instead of configuring wireless via the official way (a driver based on the IO80211Family, which is difficult to implement), they are developing their own set of tools to be able to configure the wireless card.

 

I hope I've made this complicated matter a little clearer for you .

[Mr-Mur]

Installed current release of Intel PROset/Wireless 3945a/b/g rev 482 from site, noo BSODs at strartup. but have no AP near to check driver.

Here are some logs:

dmesg.txt ioreg.txt system.txt

 

Hope 945 to be working

[zipper]

As a matter of fact, the ipw3945 driver from Linux (and thus from Ubuntu too) is used as the starting point for the driver being developed here. But no, a driver written for Linux cannot be used directly. Because of the radically different driver models between OS'es.

 

At first you have the programming language. Linux drivers are written in plain C, while drivers written for Mac OS X are implemented in some subset of C++. Now, that isn't a big problem, because C++ is 'as close backwards compatible to C as possible, but no more'.

 

But then you have API's which are incompatible between OS'es. A lot of effort goes into trying to adapt this Linux driver (with Linux API) to a driver using the IOKit API.

 

And (in this special case), you have another problem: the IOKit API which allows for wireless communication (com.apple.iokit.IO80211Family) isn't public, so developing a driver with this framework is difficult. That's why they are developing an ethernet driver and a separate tool to configure the network. Of course, a wired network doesn't know anything about ESSID's, WEP/ WPA/ WPA2- keys and so on, so instead of configuring wireless via the official way (a driver based on the IO80211Family, which is difficult to implement), they are developing their own set of tools to be able to configure the wireless card.

 

I hope I've made this complicated matter a little clearer for you .

 

Thanks Jaap-Jan van der Veen for taking the time & efforts in giving the explanation. Really appreciate it, even though i may not understand it fully, i see the picture!

 

Ok, now i understand it better!

 

Thanks to all who dedicated their works in developing the drivers and wish you luck!

 

[reeiit]

hope this helps

http://www.intel.com/support/notebook/sb/cs-006006.htm

 

"Note: The Intel® PRO/Wireless 3945ABG Network Connection uses a PCIe Mini Card connector, which is a different physical connector and electrical interface compared to older adapters, which use a miniPCI connector. Therefore, the Intel PRO/Wireless 3945ABG Network Connection cannot be used as a replacement for your Intel PRO/Wireless 2100/2100A/2200BG/2915ABG Network Connection because it will not fit or connect."