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

[jalavoui]

pere,
at least a good log
run more tests and teach others how you get this log
you seem to have a bluetooth controler interfering with iwi3945 - try to disable it
we need to have a scan_complete in logs
maybe this code is stable enought for iwi4965 to start working
the iwi3945 is not so easy - looks like it need some reboots to work
other things can interfere with it - bad enx setup, rfkill,etc
i think you'll get a kp when the driver tries to associate to a network - just test it

so there's no point in making new releases - the code need to be checked
maybe Cxddev can find a solution

[Wayfarer247]

maybe this code is stable enought for iwi4965 to start working

Ruud, you may be right. I'll wait to be told what to do. I am a little out of my league, but would love to help test anything at this point. Perhaps a Different thread?

Whatever you want!

[pere]

pere,
at least a good log
run more tests and teach others how you get this log
you seem to have a bluetooth controler interfering with iwi3945 - try to disable it
we need to have a scan_complete in logs

This time i did:
Went to safe mode, loaded the kext, make a log, shutted down the laptop.
Quitted the power supply and battery to my laptop and waited 20 loooooong seconds.
Started and grabbed the system.log from console.

Javalui, i have to erase the kexts for bluetooth, anyone knows wich are they?
My hardware switch controls both, bluetooth and wifi ON/OFF.


Before i posted the method i use, here is the link.
http://forum.insanelymac.com/index.php?s=&...st&p=721057
Its for newbies, like me
Erased the bluetooth kexts, the same logs.

[Wayfarer247]

I believe this is the link for the 4965 trunk, in case anyone but me cares:

http://iwidarwin.googlecode.com/svn/trunk/iwi4965-osx10.5

[Doctadre]

Damn, pere gets no errors. Im getting this error from the get go:

Apr 23 17:12:45 doctadres-mac-pro kernel[0]: error iwl3945: U iwl3945_pci_probe pci_resource_len = 0x00000008
Apr 23 17:12:45 doctadres-mac-pro kernel[0]: error iwl3945: U iwl3945_pci_probe pci_resource_base = 0x350fe000

but then right after that, I get this, it sees the card!!!

Apr 23 17:12:45 doctadres-mac-pro kernel[0]: IOPCCard info: iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
Apr 23 17:12:45 doctadres-mac-pro kernel[0]: error iwl3945: U iwl3945_set_rxon_channel Staging channel set to 6 [3]
Apr 23 17:12:45 doctadres-mac-pro kernel[0]: init_waitqueue_head stubbed out!
Apr 23 17:12:45 doctadres-mac-pro kernel[0]: error iwl3945: U iwl3945_pci_probe MAC address: 00:19:d2:be:49:86

Then it seems to be scanning in which these errors come up:

Apr 23 17:13:30 doctadres-mac-pro kernel[0]: error iwl3945: U iwl3945_rx_handle r = 176, i = 175, REPLY_3945_RX, 0x1b
Apr 23 17:13:30 doctadres-mac-pro kernel[0]: error iwl3945: U iwl3945_rx_reply_rx Rssi -66 noise -127 qual 67 sig_avg 0 noise_diff 0
Apr 23 17:13:30 doctadres-mac-pro kernel[0]: error iwl3945: U iwl3945_report_frame Beacon: 0x0080, dst=0xff, src=0x72, rssi=29, tim=43211679 usec, phy=0x23, chnl=1

Maybe something to do with this:
Apr 23 17:12:45 doctadres-mac-pro kernel[0]: warning en1: Failed to add default virtual iface

the numbers change all the time with each time there is an error. Pere what are the initial log lines for you?

Attached File(s)

 systemlog810.txt ( 105.32K ) Number of downloads: 5

 

[righteye]

810
Hmm
have no idea why cannot get it proper. there are no IOPCCard debug in my logs
the only thing that has some importance is:

CODE

Apr 24 01:43:29 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_rx_handle r = 79, i = 78, SCAN_RESULTS_NOTIFICATION, 0x83
Apr 24 01:43:29 right-eyes-mac-pro kernel[0]: iwl3945_rx_handle r = 93, i = 91, STATISTICS_NOTIFICATION, 0x9d
Apr 24 01:43:29 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_hw_rx_statistics Statistics notification received (240 vs 244).
Apr 24 01:43:29 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_rx_handle r = 93, i = 92, SCAN_START_NOTIFICATION, 0x82
Apr 24 01:43:29 right-eyes-mac-pro kernel[0]: art: 34 [802.11a] (TSF: 0x00000000:00050BCB) - 1 (beacon timer 50410549)
Apr 24 01:43:29 right-eyes-mac-pro kernel[0]: queue_te @ /Users/righteye/4WirelessProjects/new/iwi3945_new-osx10.5/compatibility.cpp:6531
Apr 24 01:43:29 right-eyes-mac-pro kernel[0]: test_function @ /Users/righteye/4WirelessProjects/new/iwi3945_new-osx10.5/compatibility.cpp:6520
Apr 24 01:43:29 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_rx_handle r = 99, i = 98, SCAN_RESULTS_NOTIFICATION, 0x83
Apr 24 01:43:29 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_rx_scan_results_notif Scan ch.res: 34 [802.11a] (TSF: 0x00000000:0006C3E7) - 0 elapsed=112668 usec (120ms since last)
Apr 24 01:43:29 right-eyes-mac-pro kernel[0]: queue_te @ /Users/righteye/4WirelessProjects/new/iwi3945_new-osx10.5/compatibility.cpp:6531
Apr 24 01:43:29 right-eyes-mac-pro kernel[0]: 2, SCAN_START_NOTIFICATION, 0x82
Apr 24 01:43:29 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:000A6E80) - 1 (beacon timer 100696448)
Apr 24 01:43:29 right-eyes-mac-pro kernel[0]: queue_te @ /Users/righteye/4WirelessProjects/new/iwi3945_new-osx10.5/compatibility.cpp:6531
Apr 24 01:43:29 right-eyes-mac-pro kernel[0]: test_function @ /Users/righteye/4WirelessProjects/new/iwi3945_new-osx10.5/compatibility.cpp:6520
Apr 24 01:43:29 right-eyes-mac-pro kernel[0]: ssProjects/new/iwi3945_new-osx10.5/compatibility.cpp:6520
Apr 24 01:43:29 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_rx_handle r 123 i 122 No handler needed for REPLY_TX_PWR_TABLE_CMD, 0x97
Apr 24 01:43:29 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_send_cmd_sync Wait REPLY_TX_PWR_TABLE_CMD Condition: 49ms left
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: 945_new-osx10.5/compatibility.cpp:6520
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_rx_handle r 134 i 133 No handler needed for REPLY_RATE_SCALE, 0x47
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_send_cmd_sync Wait REPLY_RATE_SCALE Condition: 49ms left
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_mac_config_interface leave
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_hw_reg_send_txpower ch 1:1 rf 147 dsp 119 rate code 0x0d
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_hw_reg_send_txpower ch 1:1 rf 147 dsp 119 rate code 0x0f
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_hw_reg_send_txpower ch 1:1 rf 147 dsp 119 rate code 0x05
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_hw_reg_send_txpower ch 1:1 rf 147 dsp 119 rate code 0x07
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_hw_reg_send_txpower ch 1:1 rf 147 dsp 119 rate code 0x09
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_hw_reg_send_txpower ch 1:1 rf 147 dsp 119 rate code 0x0b
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_hw_reg_send_txpower ch 1:1 rf 147 dsp 119 rate code 0x01
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_hw_reg_send_txpower ch 1:1 rf 147 dsp 106 rate code 0x03
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_hw_reg_send_txpower ch 1:1 rf 203 dsp 127 rate code 0x0a
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_hw_reg_send_txpower ch 1:1 rf 203 dsp 127 rate code 0x14
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_hw_reg_send_txpower ch 1:1 rf 203 dsp 127 rate code 0x37
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_hw_reg_send_txpower ch 1:1 rf 203 dsp 127 rate code 0x6e
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_enqueue_hcmd Sending command REPLY_TX_PWR_TABLE_CMD (#97), seq: 0x0419, 56 bytes at 25[25]:4
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: queue_te @ /Users/righteye/4WirelessProjects/new/iwi3945_new-osx10.5/compatibility.cpp:6531
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: test_function @ /Users/righteye/4WirelessProjects/new/iwi3945_new-osx10.5/compatibility.cpp:6520
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_rx_handle r 135 i 134 No handler needed for REPLY_TX_PWR_TABLE_CMD, 0x97
Apr 24 01:43:30 right-eyes-mac-pro kernel[0]: iwl3945: U iwl3945_send_cmd_sync Wait REPLY_TX_PWR_TABLE_CMD Condition: 49ms left

Here is the [attachment=26399:system.txt]

[rulli]

Hello these are my first logs. Please tell me what I could do to improve them. En1 was applied only shortly before restart. It's build 810.
 system.txt ( 239.4K ) Number of downloads: 11

[pere]

I believe this is the link for the 4965 trunk, in case anyone but me cares:

http://iwidarwin.googlecode.com/svn/trunk/iwi4965-osx10.5

Wayfarer, the command for you...test if it points to the right place for download. (Attached).

For the iwi 3945 testers....

I have install a driver from Chun-nan, is supposed to get the correct bios data for cardbus/pcmcia, but this kexts give to osx the overall irq information in a better way... i give you the link, maybe this is one difference. USE REV 8 from Chun-nan driver.
http://forum.insanelymac.com/index.php?showtopic=81036
The other thing maybe i do different is just i turn off my laptop completely (I quit the battery and unplug power supply too) and wait 20 seconds, i have find the card goes buggy after trying the driver and need a full reset/shutdown to startup correctly.

Hope it helps.

If you continue having en1 errors, tell me and i will help you to hardcode the card into networkpreferences.plist
My kext build 810 is attached too.

Attached File(s)

 Iwi_4965_svn_download.command.zip ( 791bytes ) Number of downloads: 27
 iwi3945.kext.zip ( 237.88K ) Number of downloads: 55

 

[joe momma]

the r810 kext seems to work well for me via eathernet, however I can't use wireless. I seem to remember older revisions (though I don't remember exactly which ones) showing up under airport, but the last few have not for me.

I'm loading them by
cd /
sudo unzip iwi3945r810.kext.zip
sudo kextload iwi3945.kext

Am I doing dsomething wrong?

Thanks
All the work is definitely appreciated.

[Lofn]

Attached are my iwl4965 log results.

For those who don't know about it, Kext Helper could save you a lot of work in the terminal when loading kexts.

Attached File(s)

 system.log.txt ( 750.47K ) Number of downloads: 14

 

[f41qu3]

iwi4965
it's almost ready to work -> just need a few hacks like iwi3945

iwi3945 rel 810
last version for today
try to hack the function check_firstup()
maybe you can find a way to make the driver load without errors

Hi,

I'm test 810 here and have this bits:

Mine IOREG output:

CODE

    | |   |   +-o pci8086,4222@0  <class IOPCIDevice, registered, matched, active, busy 0, retain 57>
    | |   |       {
    | |   |         "IOPCIResourced" = Yes
    | |   |         "IOInterruptControllers" = ("io-apic-0","IOPCIMessagedInterruptController")
    | |   |         "IOName" = "pci8086,4222"
    | |   |         "subsystem-id" = <00100000>
    | |   |         "IOPCIExpressLinkCapabilities" = 465937
    | |   |         "IODeviceMemory" = (({"address"=18446744073679138816,"length"=4096}))
    | |   |         "class-code" = <00800200>
    | |   |         "IOPowerManagement" = {"CurrentPowerState"=2}
    | |   |         "revision-id" = <02000000>
    | |   |         "IOInterruptSpecifiers" = (<1200000007000000>,<0500000000000100>)
    | |   |         "IOChildIndex" = 1
    | |   |         "assigned-addresses" = <100003820000000000f02ffe0000000000100000>
    | |   |         "device-id" = <22420000>
    | |   |         "vendor-id" = <86800000>
    | |   |         "name" = "pci8086,4222"
    | |   |         "subsystem-vendor-id" = <86800000>
    | |   |         "IOPCIExpressLinkStatus" = 4113
    | |   |         "reg" = <0000030000000000000000000000000000000000100003020000000000000000000000000010
000>
    | |   |         "compatible" = <"pci8086,1000","pci8086,4222","pciclass,028000">
    | |   |       }

Have this IDs on Darwin's lspci:

CODE

03:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG Network Connection [8086:4222] (rev 02)
03:00.0 0280: 8086:4222 (rev 02)

HexDump:
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

CODE

00: 86 80 22 42 06 00 10 00 02 00 80 02 08 00 00 00
10: 00 f0 2f fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 00 10
30: 00 00 00 00 c8 00 00 00 00 00 00 00 12 01 00 00

Bootlog: (as long, lot lines, I post up in pastebin.ca to easy view)
http://pastebin.ca/995321

Last line after system freeze:

CODE

Apr 23 21:46:53 MacBook SystemUIServer[116]: Error: ACInterfaceGetPower() called with invalid interface

Intel 3945 as knowed at Wired Interface (2).

When system stared, running fine for some 20 or 30 seconds, before, freeze.

I'm portuguese brazillian, and working to try solve something too.

Sorry long post.

Cheerz,

[jalavoui]

just compare your logs with pere's logs
some of you are testing the wrong versions of iwi3945.kext...
anyone as tryed to hack the code?

iwi3945 rel 811
this as the scan call that gives scan_complete but i guess also give a kp

[f41qu3]

[To add]

When I use ./networkSelector nothing happened.

-

Yes, I tried make some hacks;

Edited: Link: http://iwidarwin.googlecode.com/svn/trunk/...45_new-osx10.5/


Cheerz,

[Miguel Madrid]

I have been making test during the morning trying the find why or where some of us are getting errors...

Having a look line by line to my log against pere's one.... all seems to be ok

Apr 24 13:28:22 kernel[0]: iwl3945: U iwl3945_pci__nic_init SW RF KILL supported in EEPROM.
Apr 24 13:28:22 kernel[0]: iwl3945: U iwl3945_hw_nic_init HW RF KILL supported in EEPROM.
Apr 24 13:28:22 kernel[0]: iwl3945: U iwl3945_load_bsm Begin load bsm
Apr 24 13:28:22 kernel[0]: iwl3945: U iwl3945_verify_bsm Begin verify bsm
Apr 24 13:28:22 kernel[0]: iwl3945: U iwl3945_verify_bsm BSM bootstrap uCode image OK
Apr 24 13:28:22 kernel[0]: iwl3945: U iwl3945_load_bsm BSM write complete, poll 1 iterations
Apr 24 13:28:22 kernel[0]: iwl3945: U __iwl3945_up iwl3945 is coming up
Apr 24 13:28:22 kernel[0]: iwl3945: U iwl3945_mac_open Start UP work.

but... then it goes to:

Apr 24 13:28:23 kernel[0]: s: 0x00000004
Apr 24 13:28:23 kernel[0]: iwl3945: U iwl3945_print_rx_config_cmd u8 dev_type: 0x3
Apr 24 13:28:23 kernel[0]: iwl3945: U iwl3945_print_rx_config_cmd u8 ofdm_basic_rates: 0xff
Apr 24 13:28:23 kernel[0]: iwl3945: U iwl3945_print_rx_config_cmd u8 cck_basic_rates: 0x0f
Apr 24 13:28:23 kernel[0]: iwl3945: U iwl3945_print_rx_config_cmd u8[6] node_addr: 00:1c:bf:02:15:16
Apr 24 13:28:23 kernel[0]: iwl3945: U iwl3945_print_rx_config_cmd u8[6] bssid_addr: 00:00:00:00:00:00
Apr 24 13:28:23 kernel[0]: iwl3945: U iwl3945_print_rx_config_cmd u16 assoc_id: 0x0
Apr 24 13:28:23 kernel[0]: iwl3945: U iwl3945_irq_handle_error Restarting adapter due to uCode error.

and in pere's one is

Apr 23 23:20:50 Pere kernel[0]: iwl3945: U iwl3945_mac_open Start UP work.\
Apr 23 23:20:50 Pere kernel[0]: queue_te
Apr 23 23:20:50 Pere kernel[0]: wi3945/compatibility.cpp:6520\
Apr 23 23:20:50 Pere kernel[0]: ieee80211_tx_pending
Apr 23 23:20:50 Pere kernel[0]: test_function @
Apr 23 23:20:50 Pere kernel[0]: ieee80211_tasklet_handler @
Apr 23 23:20:50 Pere kernel[0]: test_function @
Apr 23 23:20:50 Pere kernel[0]: iwl3945: U iwl3945_rx_handle r = 1, i = 0, REPLY_ALIVE, 0x01\
Apr 23 23:20:50 Pere kernel[0]: iwl3945: U iwl3945_rx_reply_alive Alive ucode status 0x00000001 revision 0x1 0x9\
Apr 23 23:20:50 Pere kernel[0]: iwl3945: U iwl3945_rx_reply_alive Initialization Alive received.\

So I think some of us will need to find why or where there is differences in the HW.. later I can see on my log:

Apr 24 13:28:24 kernel[0]: iwl3945: U iwl3945_alive_start Runtime Alive received.
Apr 24 13:28:24 kernel[0]: iwl3945: U iwl3945_verify_inst_sparse ucode inst image size is 900
Apr 24 13:28:24 kernel[0]: iwl3945: U iwl3945_verify_inst_sparse ucode inst image size is 2668
Apr 24 13:28:24 kernel[0]: iwl3945: U iwl3945_verify_inst_sparse ucode inst image size is 80524
Apr 24 13:28:24 kernel[0]: iwl3945: U iwl3945_verify_ucode Runtime uCode is good in inst SRAM
Apr 24 13:28:24 kernel[0]: iwl3945: U iwl3945_alive_start RFKILL status: 0x1
Apr 24 13:28:24 kernel[0]: iwl3945: U iwl3945_init_channel_map Channel map already initialized.
Apr 24 13:28:24 kernel[0]: iwl3945: U iwl3945_init_geos Geography modes already initialized.
Apr 24 13:28:24 kernel[0]: ieee80211_start_queues
Apr 24 13:28:24 kernel[0]: iwl3945: U iwl3945_update_power_cmd Flags value = 0x00000008
Apr 24 13:28:24 kernel[0]: iwl3945: U iwl3945_update_power_cmd Tx timeout = 0
Apr 24 13:28:24 kernel[0]: iwl3945: U iwl3945_update_power_cmd Rx timeout = 0
Apr 24 13:28:24 kernel[0]: iwl3945: U iwl3945_update_power_cmd Sleep interval vector = { 0 , 0 , 0 , 0 , 0 }
Apr 24 13:28:24 kernel[0]: iwl3945: U iwl3945_enqueue_hcmd Sending command POWER_TABLE_CMD (#77), seq: 0x0400, 36 bytes at 0[0]:4
Apr 24 13:28:24 kernel[0]: queue_te
Apr 24 13:28:24 kernel[0]: test_function
Apr 24 13:28:24 kernel[0]: error iwl3945: Microcode HW error detected. Restarting.
Apr 24 13:28:24 kernel[0]: error iwl3945: Desc Time asrtPC blink2 ilink1 nmiPC Line
Apr 24 13:28:24 kernel[0]: error iwl3945: Start IWL Event Log Dump: display count 6, wraps 0
Apr 24 13:28:24 kernel[0]: error iwl3945: 0000000000 0x000000d5 0117
Apr 24 13:28:24 kernel[0]: error iwl3945: 0000000000 0x000000be 0118
Apr 24 13:28:24 kernel[0]: error iwl3945: 0000000130 0x00000000 0651
Apr 24 13:28:24 kernel[0]: error iwl3945: 0000000151 0xffffff2e 0454
Apr 24 13:28:24 kernel[0]: error iwl3945: 0000000152 0x00000000 0472
Apr 24 13:28:24 kernel[0]: error iwl3945: 0000000173 0x000000iwc5 l39401045:
Apr 24 13:28:24 kernel[0]: U iwl3945_send_cmd_sync Wait POWER_TABLE_CMD Condition: 20ms left

IT seems to be related to "power" so the next things I'll be testing the the power settings in both BIOS and Systempreferences...

Jalavoui... may we know from where the @#~# the Apr 24 13:28:23 kernel[0]: s: 0x00000004 comes from. It's the first difference between the logs...

Regards..... let's keep moving

[jalavoui]

this bug is related to Microcode - some cards have it
do you get it after a few reboots?

when you get this errror the driver calls iwl3945_bg_restart() - this tryes to load the ucode again
need to make it work better
the card is restarted if you see this msg "Restarting adapter due to uCode error.\n"

i thing i get it:
the pci_disable_device, etc code is wrong - i'll fix it

iwi3945 rel 812
pci hacks
the driver setup is done after enable() gets called

[kazzi]

Rev 811.

I got KP right when I click apply in Network Preferences.

This is the log.

http://pastebin.ca/995691

[mlazy]

Wayfarer, the command for you...test if it points to the right place for download. (Attached).

For the iwi 3945 testers....

I have install a driver from Chun-nan, is supposed to get the correct bios data for cardbus/pcmcia, but this kexts give to osx the overall irq information in a better way... i give you the link, maybe this is one difference. USE REV 8 from Chun-nan driver.
http://forum.insanelymac.com/index.php?showtopic=81036
The other thing maybe i do different is just i turn off my laptop completely (I quit the battery and unplug power supply too) and wait 20 seconds, i have find the card goes buggy after trying the driver and need a full reset/shutdown to startup correctly.

Hope it helps.

If you continue having en1 errors, tell me and i will help you to hardcode the card into networkpreferences.plist
My kext build 810 is attached too.

Pere is dead on here. I HAD to have the Chun-nan kexts loaded for any of this to work...

[pere]

Hello all!.
Log for 811...

Javalui is correct for this one, if the card is correclty initialized, then it get frozen.
I have been trying for 1 our all the ways to make this 811 work, the only way for my card to initialize correctly is still TURN OFF the laptop and unplug battery and power cord for at least 30 seconds, plug again and start as spected, loaded correctly and get frozen.

EDIT: I know the card is correctly initialized if i find this on the begining of the log:

iwi3945: Starting\
Someone called createOutputQueue()\
settCurController [OK]\
IOPCCard info: iwl3945: Intel® PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.23d\
IOPCCard info: iwl3945: Copyright© 2003-2007 Intel Corporation\
ieee80211_alloc_hw @ /Users/PERE/iwi3945/compatibility.cpp:5592\
sta_info_init @ /Users/PERE/iwi3945/compatibility.cpp:5424\
init_timer @ /Users/PERE/iwi3945/compatibility.cpp:886\
ieee80211_if_sdata_init @ /Users/PERE/iwi3945/compatibility.cpp:2088\
ieee80211_alloc_hw [OK]\

Attached File(s)

 reboot_log.txt ( 14.85K ) Number of downloads: 14
 iwi3945.kext.zip ( 237.95K ) Number of downloads: 26

 

[panto91]

news for 3945a/b/g??? ... please, i need driver for it ...

thanks..

Panto91

[jalavoui]

here's the bug:

Apr 24 14:44:44 Pere kernel[0]: iwl3945: U iwl3945_verify_inst_sparse ucode inst image size is 2668\
Apr 24 14:44:44 Pere kernel[0]: iwl3945: U iwl3945_verify_inst_sparse ucode inst image size is 80524\
Apr 24 14:44:44 Pere kernel[0]: iwl3945: U iwl3945_mac_open Wait START_ALIVE Condition: 0ms left\
Apr 24 14:44:44 Pere kernel[0]: iwl3945: U iwl3945_mac_open Wait for START_ALIVE timeout after 2000ms.\
Apr 24 14:44:44 Pere kernel[0]: iwl3945: U iwl3945_mac_open leave - failed\
Apr 24 14:44:44 Pere kernel[0]: Someone called createOutputQueue()\
Apr 24 14:44:44 Pere kernel[0]: darwin_iwi3945::configureInterface()\
Apr 24 14:44:44 Pere kernel[0]: iwl3945: U iwl3945_verify_ucode Runtime uCode is good in inst SRAM\
Apr 24 14:44:44 Pere kernel[0]: iwl3945: U iwl3945_alive_start RFKILL status: 0x1\

this line Apr 24 14:44:44 Pere kernel[0]: iwl3945: U iwl3945_mac_open Wait for START_ALIVE timeout after 2000ms.\
show that the ucode failed to start, etc
but after this
Apr 24 14:44:44 Pere kernel[0]: iwl3945: U iwl3945_mac_open leave - failed\
the ucode starts to work
weird...

my guess goes to
queue_delayed_work(priv->workqueue, pwork, msecs_to_jiffies(5));
if this takes to long to get called the driver startup fails

need logs for new release

iwi3945 rel 813
add more time for ucode to load - this remind me old iwi2200 bugs...
check if it starts ok this time - only need first log lines
need to test this using kextload