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

[jalavoui]

iwi3945
this can fix the starttup bug
looks like some cards just fail to load the ucode
i forgot this file - this does the scan work and can give a kp

Attached File(s)

 iwl3945_base.c.zip ( 65.31K ) Number of downloads: 18
 iwi3945.cpp.zip ( 11.92K ) Number of downloads: 17

 

[pere]

Ok, here is the way i do, if its wrong, please correct me.
Downloaded Xcode from apple (last version)
http://developer.apple.com/tools/download/
Downloaded the repair permissions tools (attached) ,copy it to applications.
Then download the iwi files with the attached .command (everytime there is a new version i erase the whole folder it creates under my user folder before download)
Manually execute iwi3945.xcodeproj
Go to the build folder created by the builder program under iwi3945 in my user folder, go to debug into this folder and take a look to see whether the iwi3945.kext has been created.
Go to system preferences network and check there is an network connection en0 and its not active (
check its id to see its not iwi ones and dettach the cable).
Then restart to make the system loads without any network connection.

Now after rebooting:

1.Open again the iwi3945 folder under my user>build>debug, keep open.
2.Open too system/library/extensions keep open.
3.Then open the console and select show all messages, click on clean screen and watch there is no new messages and keep it open to see new messages.
4.Drag the kext from the debug folder to the extensions folder (previously erase any other iwi3945.kext may be inside and reboot to be sure the system starts clean).
5.Quickly execute repair and set permissions, once the program finish, the kext is loaded auto and the console begins to give output messages, copy them, save into a file.
6.Clean the console, go to system preferences>network, maybe you have a new adapter, click apply, check the console, get the new log.
7.If the new adapter dont appear, add manually (with the + symbol), maybe is the last network adaptor, you have to check the hardware id, go to applications>utilities and open system profiler>network, the new iwi adaptor must be en1 and there you can see its hardware id, compare with the one you have add to network..
8 if it is not en1, then you have to hardcode it to make osx always set it as en1, go to library>preferences>system configuration>networkinterfaces.plist and change the iwi hardware adress from any enX it is to en1 (and currently en1 to the one iwi was using), restart.
9.After some clean reboots with the kext loaded, go to console,system.log and copy it,post here.

Sorry if has been a soooo long explanation, but with the normal log commands i always get blank logs, so i have to do it like this.

Hope it helps.

Attached File(s)

 Repair___Set_Permissions_1.0.zip ( 58.69K ) Number of downloads: 94
 Download_Iwi_svn.command.zip ( 741bytes ) Number of downloads: 75

 

[mlazy]

Built the latest from your attachments.

 iwi3945r806.kext.zip ( 239.01K ) Number of downloads: 108


mine gets stuck in a scan loop of sorts, no matter how I test. (-s, -x, full boot) You can see what's happening within the first 10 lines of the iwl entries. no KP in any boot mode either.



 806syslog.txt ( 609.75K ) Number of downloads: 20

[jalavoui]

mlazy,
there's no usefull data in your logs
can you try after boot to load it with kextload?
i need inital driver starttup log lines
the scan is called after the driver calls enable()
maybe if you delete iwi3945.kext,en1,reboot,kextload,apply en1 will give this logs


iwi3945 rel 805
manage to upload the files
it's the same code as mlazy build

ok, here's a good and simple way to test this:
1) delete any iwi3945 interface from system preferences -> network
2) delete iwi3945.kext and reboot
3) build in xcode and use kextload to load it
open console->system.log. you'll see the msg "check first up bla bla bla)
4) open sys prefs -> networks and press apply
the drive will start working

[mlazy]

mlazy,
there's no usefull data in your logs
can you try after boot to load it with kextload?
i need inital driver starttup log lines
the scan is called after the driver calls enable()

gimme 5 mins. going down now..

[jalavoui]

last version as code to fix the en1 bug
the driver is expected to detect witch enx you're using
some msgs in log still show en1 - ignore it

[mlazy]

Jalavoui,

I'm stuck here. Cold boot, and the first lines I get about the driver are at line 327:

Apr 23 13:51:24 Sony kernel[0]: os Channel 187 [5.2GHz] is restricted -- skipping.
Apr 23 13:51:24 Sony kernel[0]: iwl3945: U iwl3945_init_geos Channel 188 [5.2GHz] is restricted -- skipping.
Apr 23 13:51:24 Sony kernel[0]: iwl3945: U iwl3945_init_geos Channel 189 [5.2GHz] is restricted -- skipping.
Apr 23 13:51:24 Sony kernel[0]: iwl3945: U iwl3945_init_geos Channel 192 [5.2GHz] is restricted -- skipping.
Apr 23 13:51:24 Sony kernel[0]: iwl3945: U iwl3945_init_geos Channel 196 [5.2GHz] is restricted -- skipping.
Apr 23 13:51:24 Sony kernel[0]: e 0x14


No mesages at all about startup. Attached is a log from the power button to the desktop and then some. I guess someone else needs to test this build.....

 805.txt ( 1.18MB ) Number of downloads: 12



Gonna go try your last suggestion now.

[jalavoui]

you seem to be letting the driver autoload
if using kextload do you get inital drive log lines?

im think the problem is:
Apr 23 13:52:04 Sony kernel[0]: goto system preferences -> networks and press apply if you keep seeing this
maybe you forgot to follow it
this msg is show ever 2 seconds - the driver won't start if enx isn't add to sys prefs - nets
but if you get inital errors on driver load this will also fail

anyone else to post logs?

[Miguel Madrid]

I'll not able to test today as I have a family party (My sister birthday)...


but I think the startup issue could be related to when the kext is load...

As I said before, a reboot is needed, because the first time the kext is loaded don't work in the same way as second time...

I think we should find the correct way to test, or jalavoui will not be able to get info from the logs.

As far as I see it could be:

- Update svn, build with xcode. Repair permision on kext
- load the kext
- Goto system preferences and apply (not sure of this)
- reboot
- load the kext againg

Other important thing is the harware switch... I think it must be on during the computer bios startup... too many options...

I'll read you later.... enjoy the evening...

[jalavoui]

@#$ iwi cards

[Doctadre]

Alright I think jala/mlazy are up to some good here. First off the bat, I think the timer issue is back, I guess its trying to regulate the temp of the card before it can load???. But I did get a few good lines

Apr 23 13:20:14 doctadres-mac-pro kernel[0]: iwl3945: U iwl3945_rx_handle r = 7, i = 6, REPLY_ADD_STA, 0x18
Apr 23 13:20:14 doctadres-mac-pro kernel[0]: iwl3945: U iwl3945_rx_reply_add_sta Received REPLY_ADD_STA: 0x01
Apr 23 13:20:14 doctadres-mac-pro kernel[0]: iwl3945: U iwl3945_send_cmd_sync Wait REPLY_ADD_STA Condition: 49ms left
Apr 23 13:20:14 doctadres-mac-pro kernel[0]: iwl3945: U iwl3945_send_add_station REPLY_ADD_STA PASSED

Then later I get:

Apr 23 13:20:14 doctadres-mac-pro kernel[0]: darwin_iwi3945: Ethernet address 00:19:d2:be:49:86
Apr 23 13:20:14 doctadres-mac-pro kernel[0]: darwin_iwi3945::enable()
Apr 23 13:20:14 doctadres-mac-pro kernel[0]: ifconfig going up
Apr 23 13:20:14 doctadres-mac-pro kernel[0]: outputPacket called by someone
Apr 23 13:20:14 doctadres-mac-pro kernel[0]: outputPaccket2 called

Then it tells me thermal timer is not needed, somewhere we need to comment out the calls to these functions. You have two separate functions that may be in conflict with each other. I need a bigger partition any one else game, or am I just completely off the marker?

Kext below

Attached File(s)

 systemlog805.txt ( 30.4K ) Number of downloads: 9

 

[righteye]

Build the Revision 805
First time it freezes my system:
second boot KP
third boot this are the logs:
[attachment=26363:dmesg.txt][attachment=26364:ioreg.txt][attachment=26365:system
txt]
i'll be back tomorrow with more logs.

[mlazy]

Hey,

Manual kextload goes right to it as well:

Apr 23 14:20:18 Sony sudo[417]: super : TTY=ttys001 ; PWD=/Users/super/Desktop/iwi3945/805/build/Debug ; USER=root ; COMMAND=/sbin/kextload -t iwi3945.kext
Apr 23 14:20:23 Sony kernel[0]: 945/805/compatibility.cpp:6520
Apr 23 14:20:23 Sony kernel[0]: iwl3945: U iwl3945_rx_handle r = 18, i = 17, REPLY_3945_RX, 0x1b
Apr 23 14:20:23 Sony kernel[0]: iwl3945: U iwl3945_rx_reply_rx Rssi -85 noise -127 qual 40 sig_avg 0 noise_diff 0
Apr 23 14:20:23 Sony kernel[0]: ieee80211_rx_irqsafe @ /Users/super/Desktop/iwi3945/805/compatibility.cpp:1841

I've got to figure out what I'm doing wrong here. I have a pretty good record testing with you here over the past 3 weeks.

 manual_kextload.txt ( 314.96K ) Number of downloads: 24

[jalavoui]

at least some conclusion:
- the driver works fine for some cards
- if you don't get a kp them the card fail to start and is doing nothing
- the panic is at ieee80211_scan_completed() this means the driver complets the scan job ok
need to find out why

[Cxddev]

iwi4965-osx5.1 uploaded to svn...

jalavoui - can you check it in case I baulked the repository (again!)

BTW the version is a bit out of date, but it should build ok.

[jalavoui]

ok
we'll share some bugs here

it's ok for building
you can post iwi4965.kext here for testing
first tip:
change ieee_open,checkfirstup

i hope you find a way to start scaning - i'm getting crazy about this


iwi3945 rel 807
this might be the way to scan
only works if you manage to start the driver without errors
if you get a kp - post the picture

[pere]

My log from 805...Always frozen except safe boot, manual load

Attached File(s)

 Safe_boot_manual_load.txt ( 36.73K ) Number of downloads: 15

 

[righteye]

Logs 806
Guys you move fast again ...
after a KP ... a few reboots and 7 minutes waiting for each reboot ... the driver loaded
have a look when the driver loads ... allot better
[attachment=26369:Logs_r806.zip]

[pere]

Logs 807.
No freezes.

Attached File(s)

 reboot_log.txt ( 31.35K ) Number of downloads: 7
 manual_load.txt ( 302.11K ) Number of downloads: 5

 

[mlazy]

807 manual kextload: no KP, sees new enet, starts scan.

I'll reboot into -x mode and manually load again to confirm results.

807 built from Jalavoui's source.

 iwi3945r807.kext.zip ( 238.98K ) Number of downloads: 98


Still getting some errors on my card version. booted -x, manual load. looks interesting, very interesting..

 807syslog.txt ( 17.7K ) Number of downloads: 31