Intel Wireless 2100, 2200bg, 2915bg, 3945abg, 4965agn, IWIDarwin drivers for mac os x 10.4 and 10.5 *under development* Options

[Beto2k7]

No, you're wrong! You're linking the virtual machine to the physical pci bus so that the host machine knows nothing about it.

That way you can get almost all drivers to work on mac so we should give it a try.

for that u need a type 1 Hypervisor... You're wrong... Kthx

[DPyro]

Apr 9 17:27:14 macbook kernel[0]: IOPCCard info: iwl3945: Intel® PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.23d
Apr 9 17:27:14 macbook kernel[0]: IOPCCard info: iwl3945: Copyright© 2003-2007 Intel Corporation
Apr 9 17:27:14 macbook kernel[0]: ieee80211_alloc_hw [OK]
Apr 9 17:27:14 macbook kernel[0]: PCI device enabled [OK]
Apr 9 17:27:14 macbook kernel[0]: IOPCCard info: iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
Apr 9 17:27:14 macbook kernel[0]: init_waitqueue_head stubbed out!
Apr 9 17:27:14 macbook kernel[0]: error iwl3945: Time out reading EEPROM[0]error iwl3945: Unable to init EEPROM
Apr 9 17:27:14 macbook kernel[0]: Error drv->probe
Apr 9 17:27:14 macbook kernel[0]: error iwl3945: Unable to initialize PCI module

[Donk]

for that u need a type 1 Hypervisor... You're wrong... Kthx

You don't necessarily need a type-1 hypervisor but you do require VT-d and VT-c enabled chipsets. See Parallels Workstation Extreme for an example. Also ESX is getting this capability for network cards.

[jalavoui]

anyone whith a 3945 card please dowload last .dmg and post system.log
http://iwidarwin.googlecode.com/svn/trunk/...0.5/iwi3945.dmg
don't use networkselector

[drumthrasher109]

What would you use?

[eBrY]

Hi, I have Intel 3945. Still does not work. After installing, how do I test if it works? It still doesn't detect wireless.

anyone whith a 3945 card please dowload last .dmg and post system.log
http://iwidarwin.googlecode.com/svn/trunk/...0.5/iwi3945.dmg
don't use networkselector

[jr0en]

I installed javaloui's latest 3945 driver (from the post above).
I'd like to help the project by posting my system.log, but where can i find it on my harddrive?

[lebidou]

I installed javaloui's latest 3945 driver (from the post above).
I'd like to help the project by posting my system.log, but where can i find it on my harddrive?

You can open the console in /Applications/Utilities/
Or make a copy of /var/log/system.log

It's recommend to clear it before loading the kext in order to have it easier to read.

[dewtea]

anyone whith a 3945 card please dowload last .dmg and post system.log
http://iwidarwin.googlecode.com/svn/trunk/...0.5/iwi3945.dmg
don't use networkselector

I tried the networkselector as well, but it wasn't of any use either. Anyways, the experts can analyze systemlog and dmesg. Any pointers and i can help in further testing. Many thanks to jalavoui for bringing us this far.

______________________________________________________________________
My configuration: Dell Inspiron E1505 (6400) 2GHz Core2Duo, Intel GMA950 (working with QE/CI), SigmaTel 9200 (Working), Broadcom 440x integrated LAN Controller (Working), Intel 3945ABG (not working)

Attached File(s)

 dmesg.txt ( 4K ) Number of downloads: 17
 systemlog.txt ( 262.29K ) Number of downloads: 28

 

[Beto2k7]

You don't necessarily need a type-1 hypervisor but you do require VT-d and VT-c enabled chipsets. See Parallels Workstation Extreme for an example. Also ESX is getting this capability for network cards.

which are ... yup .. u r right... type 1 hypervisors thx

[stmkjp]

anyone whith a 3945 card please dowload last .dmg and post system.log
http://iwidarwin.googlecode.com/svn/trunk/...0.5/iwi3945.dmg
don't use networkselector

Here's system.log output after I kextloaded the iwi3945. Hope this helps.

Apr 21 18:10:49 jukimnote kernel[0]: iwi3945: Starting
Apr 21 18:10:49 jukimnote kernel[0]: Someone called createOutputQueue()
Apr 21 18:10:49 jukimnote kernel[0]: settCurController [OK]
Apr 21 18:10:49 jukimnote kernel[0]: IOPCCard info: iwl3945: Intel® PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.23d
Apr 21 18:10:49 jukimnote kernel[0]: IOPCCard info: iwl3945: Copyright© 2003-2007 Intel Corporation
Apr 21 18:10:49 jukimnote kernel[0]: ieee80211_alloc_hw [OK]
Apr 21 18:10:49 jukimnote kernel[0]: PCI device enabled [OK]
Apr 21 18:10:49 jukimnote kernel[0]: IOPCCard info: iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
Apr 21 18:10:49 jukimnote kernel[0]: init_waitqueue_head stubbed out!
Apr 21 18:10:49 jukimnote kernel[0]: IOPCCard debug: wmaster1: Selected rate control algorithm 'iwl-3945-rs'
Apr 21 18:10:49 jukimnote kernel[0]: PCI device enabled [OK]
Apr 21 18:10:49 jukimnote kernel[0]: __ IN iwl3945_alive_start __
Apr 21 18:10:49 jukimnote kernel[0]: IOPCCard info: iwl3945: Tunable channels: 13 802.11bg, 4 802.11a channels
Apr 21 18:10:49 jukimnote kernel[0]: error iwl3945: Error sending POWER_TABLE_CMD: time out after 500ms.
Apr 21 18:10:50 jukimnote kernel[0]: error iwl3945: Error sending REPLY_BT_CONFIG: time out after 500ms.
Apr 21 18:10:50 jukimnote kernel[0]: Sending RXON
Apr 21 18:10:50 jukimnote kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 21 18:10:50 jukimnote kernel[0]: * channel = 1
Apr 21 18:10:50 jukimnote kernel[0]: * bssid = 00:00:00:00:00:00
Apr 21 18:10:50 jukimnote kernel[0]: error iwl3945: Error sending REPLY_RXON: time out after 500ms.
Apr 21 18:10:50 jukimnote kernel[0]: error iwl3945: Error setting new configuration (-60).
Apr 21 18:10:50 jukimnote kernel[0]: __ OUT iwl3945_alive_start __
Apr 21 18:10:50 jukimnote kernel[0]: IOPCCard debug: HW CONFIG: channel=1 freq=2412 phymode=3
Apr 21 18:10:50 jukimnote kernel[0]: Sending RXON
Apr 21 18:10:50 jukimnote kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 21 18:10:50 jukimnote kernel[0]: * channel = 1
Apr 21 18:10:50 jukimnote kernel[0]: * bssid = 00:00:00:00:00:00
Apr 21 18:10:51 jukimnote kernel[0]: error iwl3945: Error sending REPLY_RXON: time out after 500ms.
Apr 21 18:10:51 jukimnote kernel[0]: error iwl3945: Error setting new configuration (-60).
Apr 21 18:10:51 jukimnote kernel[0]: no netif_running
Apr 21 18:10:51 jukimnote kernel[0]: Someone called createOutputQueue()
Apr 21 18:10:51 jukimnote kernel[0]: power state (1)
Apr 21 18:10:51 jukimnote kernel[0]: darwin_iwi3945::configureInterface()
Apr 21 18:10:51 jukimnote kernel[0]: darwin_iwi3945: Ethernet address xx:xx:xx:xx:xx:08 (sorry, mac address masked)
Apr 21 18:10:51 jukimnote kernel[0]: darwin_iwi3945::enable()
Apr 21 18:10:51 jukimnote kernel[0]: ifconfig going up
Apr 21 18:10:51 jukimnote kernel[0]: IOPCCard debug: en0: dropped data frame to not associated station
Apr 21 18:10:51 jukimnote kernel[0]: TXRX_DROP fail
Apr 21 18:10:53 jukimnote kernel[0]: error iwl3945: Error sending REPLY_SCAN_CMD: time out after 500ms.
Apr 21 18:10:53 jukimnote kernel[0]: IOPCCard debug: HW CONFIG: channel=1 freq=2412 phymode=3
Apr 21 18:10:53 jukimnote kernel[0]: error iwl3945: Failed to get channel info for channel 0 [3]
Apr 21 18:10:57 jukimnote kernel[0]: searching for networks...
Apr 21 18:11:27: --- last message repeated 4 times ---

[stmkjp]

I don't know if this helps, but...

When I kextloaded it from single user mode, output message was slightly different.
( not logged to system.log and cannot redirect the message to file, so I'll hardcopy part of the messages)

between
Apr 21 18:10:49 jukimnote kernel[0]: __ IN iwl3945_alive_start __
and
Apr 21 18:10:50 jukimnote kernel[0]: __ OUT iwl3945_alive_start __

messages shown like below:
error iwl3945: Microcode SW error detected. Restarting 0x82000008/
error iwl3945: Error Reply type 0x00000000 cmd UNKNOWN (0x00) seq 0x0000 ser 0x00000000

thoese messages (including __IN and _OUT alive_start thing) appeared several times.

AND,

whenever I kextunload it, my osx got kernel panic after it said unload the kext succeeded.

kernel panic messages are quite long, but I can take a screenshot or hardcopy it if you want....

[jr0en]

You can open the console in /Applications/Utilities/
Or make a copy of /var/log/system.log

It's recommend to clear it before loading the kext in order to have it easier to read.

Thanks. I wanted to post the log today.. but I can't boot anymore I get kernel panic while booting when osx loads the iwi3945 kext.

Any suggestions what to do now?
Thanks in advance

[lebidou]

Thanks. I wanted to post the log today.. but I can't boot anymore I get kernel panic while booting when osx loads the iwi3945 kext.

Any suggestions what to do now?
Thanks in advance

At boot time, press F8 repeatly to get the boot options, type -x then enter. You'll be in safe boot mode.
Remove iwi3945.kext from /System/Library/Extensions/
In a terminal type sudo touch /System/Library/Extensions
At boot time, press F8 repeatly to get the boot options, type -f then enter. It will ignore boot caches.

[stmkjp]

Thanks. I wanted to post the log today.. but I can't boot anymore I get kernel panic while booting when osx loads the iwi3945 kext.

Any suggestions what to do now?
Thanks in advance

If U still want to test the kext, then don't just remove it. move the kext to the some other directory like /System/Library/Extensions.bkups (u may have to create one).

U can do that on single user terminal mode (boot with -s switch).

CODE

/sbin/mount -uw /
move /System/Library/Extensions/iwi3945.kext /Where/You/Want/To/Move
reboot

after that boot with -f option.

Now U can boot your osx safely and can even test the kext !

How to Test :
after boot, open terminal and console.
select system.log on console menu and clear the console.
after that, on terminal

CODE

sudo kextload -t /Directory/Where/You/Moved/It/iwi3945.kext

That's it. U can just copy the messages shown on console and paste it to
this forum or your favorite editor.

FYI, U can kextunload that kext, but u can see "Please Restart blah blah~" message
if u do it. (don't worry, just reboot and it'll be fine)

[eBrY]

Is there an approximate date of when the development of the 3945 kext will be somewhat useable? I'm debating whether to get an external USB dongle wifi instead of waiting for 3945 to be compatible. Is there a chance the development will never make it? And can anyone suggest the best USB dongle (best bang for the buck) cost also considered of the one that will work out of the box for 10.5.6? Please help me, and one that would be on sale at Fry's. Please tell me about how much it would cost.

If U still want to test the kext, then don't just remove it. move the kext to the some other directory like /System/Library/Extensions.bkups (u may have to create one).

U can do that on single user terminal mode (boot with -s switch).

CODE

/sbin/mount -uw /
move /System/Library/Extensions/iwi3945.kext /Where/You/Want/To/Move
reboot

after that boot with -f option.

Now U can boot your osx safely and can even test the kext !

How to Test :
after boot, open terminal and console.
select system.log on console menu and clear the console.
after that, on terminal

CODE

sudo kextload -t /Directory/Where/You/Moved/It/iwi3945.kext

That's it. U can just copy the messages shown on console and paste it to
this forum or your favorite editor.

FYI, U can kextunload that kext, but u can see "Please Restart blah blah~" message
if u do it. (don't worry, just reboot and it'll be fine)

[ipoco]

This thread is dedicated to the development of the driver. If you wish to talk about USB Wireless devices please create a new topic and discuss the issue there. Any more posts that are not directly related to the development will be considered as spam.

iPoco

[IntelMacGuy]

for that u need a type 1 Hypervisor... You're wrong... Kthx

u sir are an idiot... learn to google stuff before you add your 2 cents. Anything can be detected through a virtual machine.... Even if it's a PCI/PCI-E device or not IT WILL detect it. k.. thnx...

[jalavoui]

howto test latest iwi3945

1) install the driver
2) reboot
3) open console and check system.log
4) the driver as code to associate to the 1st open network found. this is done without using networkselector in the check_firstup() function.
5) if you get firmware errors, timeouts, etc try step 2)

the driver is unstable - so you'll need to run a few tests to get a good system.log without errors

[Beto2k7]

u sir are an idiot... learn to google stuff before you add your 2 cents. Anything can be detected through a virtual machine.... Even if it's a PCI/PCI-E device or not IT WILL detect it. k.. thnx...

but it wont work if it's not working on the host OS. Unless of course you are using BareMetal virtualization (yes Hypervisors type 1). I would like to read your google results though.... kthx.

Virtualization FAQ

Note that even Fusion goes through the host's drivers (again, only one OS controls the hardware, so that means everything funnels through the host drivers) - this means we're subject to any bugs or limitations of the host drivers.

No funtcional mac drivers for 3945 or 4965 (idk the number) = no hardware to virtualize....

im guessing who is the idiot now.