Help - Search - Members - Calendar
Full Version: Intel Wireless 2100, 2200bg, 2915bg, 3945abg, 4965agn
InsanelyMac Forum > OSx86 Project > Hardware and Drivers > LAN and Wireless
Pages: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61
TNW
Hi ,
I corrected the iwi3945 for leopard but there is lot of error ...

I will work on but I'm not a good driver writer :/ ( and not a good English writer )
Egoist
QUOTE(TNW @ Feb 5 2008, 03:52 PM) *
Hi ,
I corrected the iwi3945 for leopard but there is lot of error ...

I will work on but I'm not a good driver writer :/ ( and not a good English writer )


There are no new devices shown in the system preferences sad.gif It seems your driver not works...
TNW

Yes , I know , I'm searching why the driver can't read the EPROM ...
But as you can see I never debuged a driver ....

You said there is no new device in the preferences ? that's strange ... I have got one ...

My IONEtworking's kext is 1.6.0
Joeandmat
on my hack, when i reboot, shows MAC is a deep sleep! very very fastly!
PS: don't works for me...
TNW
Hello ,

I modified the driver again , but it's not fonctional...(I disabled the interuptions) but it ataches the interface .. give the mac addresse ...
now i will start to make it working ... but I'm not a chef.. ^^

It's works with an IONetworking (1.6.0)

bye
streilu
TNW now i get the MAC shown in the system-profiler. So up to this it seems to work.
jalavoui
QUOTE(TNW @ Feb 6 2008, 12:01 PM) *
I modified the driver again


looks like TNW and symuc will make this work smile.gif
are you using the same version of iwl3945 as symuc? you should work on the same version
send me a gmail account so i can add you to iwidarwin.

if you need help looking at source code let me know

if you have time can you post a build version of last iwi2200 source? i'm trying to make it work in 10.5 but i only have a imac to make the code

iwi3945
you can help testing the driver by posting logs
this will allow developers to understand what the driver is doing

Joeandmat
hi! i've tested the last kext of iwi3945...
it recognize the card, but like an ethernet card, not an airport...
this is what my console give out of iwi3945:

CODE
Feb  6 15:17:11 provas-mac-pro kernel[0]: darwin_iwi3945 iomemory length: 0x1000 @ 0xf4000000
Feb  6 15:17:11 provas-mac-pro kernel[0]: darwin_iwi3945 virt: 0x2e1f9000 physical: 0xf4000000
Feb  6 15:17:11 provas-mac-pro kernel[0]: darwin_iwi3945 IRQ: 16, Vendor ID: 8086, Product ID: 4222
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_pci_probe *** LOAD DRIVER ***
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_pci_probe iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_set_rxon_channel Staging channel set to 6 [3]
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_read_ucode f/w package hdr ucode version = 0x20e0004
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_read_ucode f/w package hdr runtime inst size = 80524
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_read_ucode f/w package hdr runtime data size = 32768
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_read_ucode f/w package hdr init inst size = 2668
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_read_ucode f/w package hdr init data size = 32768
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_read_ucode f/w package hdr boot inst size = 900
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_read_ucode Copying (but not loading) uCode instr len 80524
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_read_ucode uCode instr buf vaddr = 0x0x34925000, paddr = 0x0361e000
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_read_ucode Copying (but not loading) uCode data len 32768
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_read_ucode Copying (but not loading) init instr len 2668
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_read_ucode Copying (but not loading) init data len 32768
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_read_ucode Copying (but not loading) boot instr len 900
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_pci_probe Queing UP work.
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_hw_nic_init DEBUG
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_hw_nic_init HW Revision ID = 0x2
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_hw_nic_init ALM-MM type
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_hw_nic_init SKU OP mode is basic
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_hw_nic_init 3945ABG revision is 0xF1
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_hw_nic_init Card M type B version is 0x2
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_hw_nic_init SW RF KILL supported in EEPROM.
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: iwl_hw_nic_init HW RF KILL supported in EEPROM.
Feb  6 15:17:11 provas-mac-pro kernel[0]: iwi3945: power state (1)iwi3945: configureInterface

Feb  6 15:17:11 provas-mac-pro kernel[0]: darwin_iwi3945: Ethernet address 00:1b:77:c0:65:d6
Feb  6 15:17:13 provas-mac-pro kernel[0]: iwi3945: ifnet_t en1 = 45e3004
Feb  6 15:17:13 provas-mac-pro kernel[0]: iwi3945: ifconfig down
Feb  6 15:17:13 provas-mac-pro kernel[0]: iwi3945: ifconfig already down
Feb  6 15:17:13 provas-mac-pro kernel[0]: : Grabbing access while already held at line 892.
Feb  6 15:17:13 provas-mac-pro kernel[0]: iwi3945: iwl_hw_nic_init DEBUG
Feb  6 15:17:13 provas-mac-pro kernel[0]: iwi3945: iwl_hw_nic_init HW Revision ID = 0x2
Feb  6 15:17:13 provas-mac-pro kernel[0]: iwi3945: iwl_hw_nic_init ALM-MM type
Feb  6 15:17:13 provas-mac-pro kernel[0]: iwi3945: iwl_hw_nic_init SKU OP mode is basic
Feb  6 15:17:13 provas-mac-pro kernel[0]: iwi3945: iwl_hw_nic_init 3945ABG revision is 0xF1
Feb  6 15:17:13 provas-mac-pro kernel[0]: iwi3945: iwl_hw_nic_init Card M type B version is 0x2
Feb  6 15:17:13 provas-mac-pro kernel[0]: iwi3945: iwl_hw_nic_init SW RF KILL supported in EEPROM.
Feb  6 15:17:13 provas-mac-pro kernel[0]: iwi3945: iwl_hw_nic_init HW RF KILL supported in EEPROM.
Feb  6 15:17:13 provas-mac-pro kernel[0]: iwi3945: iwl_load_bsm Begin load bsm
Feb  6 15:17:13 provas-mac-pro kernel[0]: iwi3945: iwl_verify_bsm Begin verify bsm
Feb  6 15:17:14 provas-mac-pro kernel[0]: iwi3945: iwl_verify_bsm BSM bootstrap uCode image OK
Feb  6 15:17:14 provas-mac-pro kernel[0]: iwi3945: iwl_load_bsm BSM write complete, poll 1 iterations
Feb  6 15:17:14 provas-mac-pro kernel[0]: iwi3945: iwl_up MAC address: 00:1b:77:c0:65:d6

the mac address is correct, but no airport card found and no connection...
i've taked also a photo of my system profiler... it's attached down...
i hope that this can help you! and thaks for your hard works!
jalavoui
TNW,

iwi3945 was ported from the old iwl3945 version (1.0) taken from intel (they say it's a stable version)
http://downloadcenter.intel.com/Detail_Des...x*&lang=eng

you should try to use other firmware versions to see how they work.
use hex2string with the firmware file to build ipw3945.ucode.h

i remember this version as a problem while sending commands (timeouts) - maybe you can fix it

symuc is working on a recent version of iwl3945 but i think you will find bugs in both versions.
i've asked him to change the source code and use the same file structure that exist in old iwi3945 because it's easier to make changes in code and keep it up with intel source code.

iwi3945
i'll ask again for people to post decent logs for developers
http://forum.insanelymac.com/index.php?showtopic=71779
if you're testing TNW version delete the airport interface in system preferences
if testing symuc version delete the iwi3945 ethernet interface

iwi2200 rel 581
i've added a folder to the svn tree: iwi2200-osx10.5 (same as posted before)
i hope this helps developers build a working version
you need to build it in xcode to test it
TNW
Hi,
new version with interupts and complet load, it panics sometime times

I will (hope) start the scan of networks

next versions will be on iwi3945 svn

bye
nike.stars
any news about driver for 4965? i have a laptop with that chipset, i'll gladly help whatever i could smile.gif
LeoASH
Great work guys. I and I believe many others appreciate your hard work. I hope you will make a fully working driver for 3945 soon.
Do I sound cheeky? anyway thanks guys.

Regards
ASH
A.J
Anyone tested the newest version of 3945 yet ?
lo-fi
Hi

As far as the iwi2200 10.5 is concerned I will post some logs as soon as I can download xcode. I checked the apple site and it is 1000mb. I dont have any download ability for a few days sad.gif
Or has someone else already compiled the source that they can post here? That way us noobs can just test it post the logs? I dont really know what Im talking about but I am keen to help.
Joeandmat
the last iwi3945 doesn't work for me...
i haved booted with -s, i loaded the kext but when i do /networkSelector and i press 1, it says something, i re-press 1 and it says other, i re-re-press 1 and the system show up many many words and the text scrool so fast that i cannot do a photo...
when i boot normally, first the system doesn't want startup, after, it startup normally, but no internet connection... leopard doesn't recognize airport...
i hope this is useful...

PS: sorry for my english! tongue.gif
Hugo91
I have the same problem as Joeandmat, when i try to turn the airport on via networkselector i get some kind of error and it just scrolls really fast saying same thing over and over again.

I can boot normally without problem though.

Keep up the good work!
TNW
Sorry for the bad version ...


We have a "MicroCode SW error" but I don't know why and that create a geant loop like:

-SW error
-restart
-SW eror
-reststart ...

so I post the last code http://zetasam.ath.cx/iwi3945.zip

if you know why tell me or modify the code wink.gif

for me it's time to go to bed wink.gif
[EDIT] CORRECTED
aocch3
I downloaded the latest build so I could upload the log files from it. Unfortunately I must be missing something. I copied the package over to /system/library/extensions and it told me it was improperly installed. when I rebooted in single user mode and tried to run networkselector it didn't work. Is there some step I'm overlooking in installation of this package? I would like to try and help developers by providing my logs and feedback.
craze
after pkg installed it hanged and on restart gave kp.
TNW
it's corrected ... it'a all my fault i changed the ucode =_=
but now I've a KP in iwl_send_cmd ...
x4hu
Woah great to learn that project is alive smile.gif... It's time to install Mac OS !!!
@irBOrNE
Excellent work here! Make sure to work together and share the knowledge as jalavoui has shown, and I'm sure we'll have some great final products here!
jalavoui
TNW,

looks like apple80211 changes in 10.5 (at least in symuc's code)
if your version work i think symuc can use the code

it would be nice to have 2 versions of the same driver smile.gif
TNW
Hi !!!
I've a good new ... and a bad new:

the bad new:
The driver have a HW error(very often)

the good new:
The driver works only scan (sometimes) :/

I give you the log ...
and if you know why we have the HW error , I listen you wink.gif

the last code is herre :
http://zetasam.ath.cx/iwi3945-1.zip
bye

[EDIT] I posted the bad log =_=
sbrungardt
Hey folks. I have an HP dv8000t with the Intel 3945 wireless - I'd love to see this working. What can I do to help that happen?
niceppl
TNW u r the man.... if u can make this happen..... there will be millions people worship you for sure... well at least (I will biggrin.gif) so....i thank you, and good luck~
P.S give urself some rest.
sbrungardt
QUOTE
Feb 7 14:15:53 netwarriors-mac-pro kernel[0]: iwi3945: : BSM uCode verification failed at addr 0x00003800+0 (of 900), is 0xa5a5a5a1, s/b 0xf802020\


This looks to me like the driver's not accessing the hardware properly; that is to say that some of the settings isn't working right. As for the specifics, like what the BSM uCode is, I found the following in Wikipedia:

http://en.wikipedia.org/wiki/OpenBSM

And

http://en.wikipedia.org/wiki/Persistent_Un...esource_Locator

The nutshell of what it looks like to me is that the BSM is the Basic Security Module; probably a part of the device to ensure that the system has the proper rights to access it, and uCode looks to me like an abbreviation for Unicode, based on that second link. So, putting those together, if I had to hazard a guess I'd say that the way the driver is attempting to access the hardware, via Unicode or something similar, isn't passing a security audit on the device itself.

Of course, this is entirely speculation, but I hope it helps!
ayle
Ugh... Installed the 4965iwl... Kp.
TNW
It's me again .
I found why there are errors:
during the ucode and eeprom init we should disable the interupts.
realityiswhere
I got a kernel panic with latest 4965 on kalyway.
Joeandmat
sorry tnw, but why don't you do only onething with the symuc project? it's more beautiful has recognized the intel 3945 like an airport...
jalavoui
TNW,

i checked your code and find some things to fix:

>> in iwl_read_ucode()
you need to replace all IOMallocContiguous() by MemoryDmaAlloc()
if you use IOMallocContiguous() you'll get lots of firmware errors (as i got in iwi2200)
copy source code of MemoryDmaAlloc() from here and replace it in iwi3945
you should also replace it in iwl_tx_queue_alloc(), iwl_tx_queue_init(), iwl_hw_set_hw_setting() and iwl_rx_queue_alloc()

or
you can try this
instead of using
priv->ucode_code.v_addr=IOMallocContiguous( priv->ucode_code.len, sizeof(__le32)
try
priv->ucode_code.v_addr=IOMallocContiguous( priv->ucode_code.len, sizeof(__le32*)

but i'm shure MemoryDmaAlloc() is much better


>> in iwl_send_cmd()
remove this line - if the driver can't send commands we should not force it
if (rc==HOST_COMPLETE_TIMEOUT) priv->status &= ~STATUS_HCMD_ACTIVE;//hack
i have a problem with IODelay(HOST_COMPLETE_TIMEOUT) - be shure you don't get firmware errors because of this

>> in init()
if you like to change the debug messages change the values in here
this need to be fixed later when the driver is ready to show less debug messages

>> this is the function from iwi2200 you should replace in iwi3945
IOBufferMemoryDescriptor*
darwin_iwi2200::MemoryDmaAlloc(UInt32 buf_size, dma_addr_t *phys_add, void *virt_add)
{
IOBufferMemoryDescriptor *memBuffer;
void *virt_address;
dma_addr_t phys_address;
IOMemoryMap *memMap;

memBuffer = IOBufferMemoryDescriptor::inTaskWithOptions(kernel_task,
kIODirectionOutIn | kIOMemoryPhysicallyContiguous |
kIOMapInhibitCache | kIOMemoryAutoPrepare , buf_size,
PAGE_SIZE);



memMap = memBuffer->map();

if (memMap == NULL) {
IWI_DEBUG("mapping failed\n");
memBuffer->release();
memBuffer = NULL;

return NULL;
}

if (phys_add!=NULL)
phys_address = memMap->getPhysicalAddress();

if (virt_add!=NULL)
{
virt_address = (void *)memMap->getVirtualAddress();

if (virt_address == NULL || phys_address == NULL) {
memMap->release();
memBuffer->release();
memBuffer = NULL;

return NULL;
}
}
if (phys_add!=NULL) *phys_add = phys_address;
if (virt_add!=NULL) *(IOVirtualAddress*)virt_add = (IOVirtualAddress)virt_address;
memMap->release();

return memBuffer;
}

>> change the code in networkSelector.xcodeproj to allow the user to turn the card on/off
try to find a way to make it show the scan results

>> copy the code from iwi2200 of nsGUI.xcodeproj
it will not work in iwi3945 but it's the latest version
with some changes you can use it in iwi3945

you should use the iwidarwin tree to commit you changes in code
this will make it easier for developers to check your code
you'll need to install Subversion-1.4.3.pkg for svn acess
and RapidSVN.app to commit your changes
i think you should create a folder called "iwi3945-osx10.5" in "trunk" in the svn tree for your project


iwi3945
please post logs to help developers understand what the driver is doing
saying "it doesn't work" doesn't help at all
nexus665
QUOTE(sbrungardt @ Feb 7 2008, 04:09 PM) *
[...], and uCode looks to me like an abbreviation for Unicode, based on that second link. So, putting those together, if I had to hazard a guess I'd say that the way the driver is attempting to access the hardware, via Unicode or something similar, isn't passing a security audit on the device itself.

Of course, this is entirely speculation, but I hope it helps!

Hiya,
uCode is a common way to abbreviate Microcode, like in uTorrent (microTorrent). Usually it's not really a u but a micro sign (u with the left side elongated below). Nothing to do with Unicode, really smile.gif

µ is the one it represents - HTH.

Now for some working wireless drivers wink.gif Thanks for your work up to now, Jalavoui, symuc and TNW!
TNW
Hi I think the probleme is that we have too many interruptions ...

If I made interupts myself (2 on log) I've this

iwi3945: iwl_pci_probe *** LOAD DRIVER ***
iwi3945: iwl_pci_probe iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
iwi3945: iwl_set_rxon_channel Staging channel set to 6 [3]
iwi3945: iwl_read_ucode f/w package hdr ucode version = 0x20e0004
iwi3945: iwl_read_ucode f/w package hdr runtime inst size = 80524
iwi3945: iwl_read_ucode f/w package hdr runtime data size = 32768
iwi3945: iwl_read_ucode f/w package hdr init inst size = 2668
iwi3945: iwl_read_ucode f/w package hdr init data size = 32768
iwi3945: iwl_read_ucode f/w package hdr boot inst size = 900
iwi3945: iwl_read_ucode Copying (but not loading) uCode instr len 80524
iwi3945: iwl_read_ucode uCode instr buf vaddr = 0x0x1acc8000, paddr = 0x037f1000
iwi3945: iwl_read_ucode Copying (but not loading) uCode data len 32768
iwi3945: iwl_read_ucode Copying (but not loading) init instr len 2668
iwi3945: iwl_read_ucode Copying (but not loading) init data len 32768
iwi3945: iwl_read_ucode Copying (but not loading) boot instr len 900
iwi3945: iwl_pci_probe Queing UP work.
iwi3945: iwl_hw_nic_init DEBUG
iwi3945: iwl_hw_nic_init HW Revision ID = 0x2
iwi3945: iwl_hw_nic_init ALM-MM type
iwi3945: iwl_hw_nic_init SKU OP mode is basic
iwi3945: iwl_hw_nic_init 3945ABG revision is 0xF1
iwi3945: iwl_hw_nic_init Card M type B version is 0x2
iwi3945: iwl_hw_nic_init SW RF KILL supported in EEPROM.
iwi3945: iwl_hw_nic_init HW RF KILL supported in EEPROM.
iwi3945: iwl_hw_nic_init Rx queue [ALOCATED]
iwi3945: power state (1)
iwi3945: configureInterface
darwin_iwi3945: Ethernet address 00:13:02:15:d8:12
iwi3945: ifnet_t en4 = 318f004
iwi3945: ifconfig up
iwi3945: ifconfig going up
iwi3945: ifconfig down
iwi3945: ifconfig going down
: Grabbing access while already held at line 892.
iwi3945: iwl_hw_nic_init DEBUG
iwi3945: iwl_hw_nic_init HW Revision ID = 0x2
iwi3945: iwl_hw_nic_init ALM-MM type
iwi3945: iwl_hw_nic_init SKU OP mode is basic
iwi3945: iwl_hw_nic_init 3945ABG revision is 0xF1
iwi3945: iwl_hw_nic_init Card M type B version is 0x2
iwi3945: iwl_hw_nic_init SW RF KILL supported in EEPROM.
iwi3945: iwl_hw_nic_init HW RF KILL supported in EEPROM.
iwi3945: iwl_hw_nic_init Rx queue [RESETED]
iwi3945: iwl_load_bsm Begin load bsm
iwi3945: iwl_verify_bsm Begin verify bsm
iwi3945: iwl_verify_bsm BSM bootstrap uCode image OK
iwi3945: iwl_load_bsm BSM write complete, poll 1 iterations
iwi3945: iwl_up MAC address: 00:13:02:15:d8:12
iwi3945: connect
2
inta 0x80000009, enabled 0x00000000, fh 0x00010000
iwi3945: iwl_rx_reply_alive Alive ucode status 0x00000001 revision 0x1 0x9
iwi3945: iwl_rx_reply_alive Initialization Alive received.
iwi3945: iwl_rx_handle r = 1, i = 0, rx_handler REPLY_ALIVE
iwi3945: iwl_verify_inst_sparse ucode inst image size is 900
iwi3945: iwl_verify_inst_sparse ucode inst image size is 2668
iwi3945: iwl_verify_ucode Initialize uCode is good in inst SRAM
iwi3945: iwl_init_alive_start Initialization Alive received.
iwi3945: iwl_set_ucode_ptrs Runtime uCode pointers are set.
2
inta 0x80000009, enabled 0x00000000, fh 0x00010000
iwi3945: iwl_rx_reply_alive Alive ucode status 0x00000001 revision 0x1 0x0
iwi3945: iwl_rx_reply_alive Runtime Alive received.
iwi3945: iwl_disable_events Selected uCode log events may be disabled
iwi3945: iwl_disable_events by writing "1"s into disable bitmap
iwi3945: iwl_disable_events in SRAM at 0x8015f4, size 47 u32s
iwi3945: iwl_rx_handle r = 2, i = 1, rx_handler REPLY_ALIVE
iwi3945: iwl_alive_start Runtime Alive received.
iwi3945: iwl_verify_inst_sparse ucode inst image size is 900
iwi3945: iwl_verify_inst_sparse ucode inst image size is 2668
iwi3945: iwl_verify_inst_sparse ucode inst image size is 80524
iwi3945: iwl_verify_ucode Runtime uCode is good in inst SRAM
iwi3945: iwl_alive_start RFKILL status: 0x1
iwi3945: iwl_init_channel_map Initializing regulatory info from EEPROM
iwi3945: iwl_init_channel_map Parsing data for 56 channels.
iwi3945: iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels
iwi3945: : iwl_equeue_hcmd ---------------------
iwi3945: iwl_enqueue_hcmd Sending command REPLY_BT_CONFIG (#9b), seq: 0x0400, 16 bytes at 0[0]:4
iwi3945: iwl_enqueue_hcmd iwl_tx_queue_update_write_ptr()
iwi3945: iwl_commit_rxon Sending RXON
* without RXON_FILTER_ASSOC_MSK
* channel = 1
* bssid = 00:00:00:00:00:00
iwi3945: : iwl_equeue_hcmd ---------------------
iwi3945: iwl_enqueue_hcmd Sending command REPLY_RXON (#10), seq: 0x0401, 48 bytes at 1[1]:4
iwi3945: iwl_enqueue_hcmd iwl_tx_queue_update_write_ptr()
iwi3945: : iwl_equeue_hcmd ---------------------
iwi3945: iwl_enqueue_hcmd Sending command REPLY_TX_PWR_TABLE_CMD (#97), seq: 0x0402, 56 bytes at 2[2]:4
iwi3945: iwl_enqueue_hcmd iwl_tx_queue_update_write_ptr()
iwi3945: iwl_add_station Adding STA ID 24: ff:ff:ff:ff:ff:ff
iwi3945: : iwl_equeue_hcmd ---------------------
iwi3945: iwl_enqueue_hcmd Sending command REPLY_ADD_STA (#18), seq: 0x0403, 68 bytes at 3[3]:4
iwi3945: iwl_enqueue_hcmd iwl_tx_queue_update_write_ptr()
iwi3945: : Error: Response NULL in 'REPLY_ADD_STA'
iwi3945: : iwl_equeue_hcmd ---------------------
iwi3945: iwl_enqueue_hcmd Sending command REPLY_TX_LINK_QUALITY_CMD (#4e), seq: 0x0404, 60 bytes at 4[4]:4
iwi3945: iwl_enqueue_hcmd iwl_tx_queue_update_write_ptr()
iwi3945: iwl3945_init_hw_rate_table Select G mode rate scale
iwi3945: : iwl_equeue_hcmd ---------------------
iwi3945: iwl_enqueue_hcmd Sending command REPLY_RATE_SCALE (#47), seq: 0x0405, 56 bytes at 5[5]:4
iwi3945: iwl_enqueue_hcmd iwl_tx_queue_update_write_ptr()
iwi3945: : iwl_equeue_hcmd ---------------------
iwi3945: iwl_enqueue_hcmd Sending command REPLY_RATE_SCALE (#47), seq: 0x0406, 56 bytes at 6[6]:4
iwi3945: iwl_enqueue_hcmd iwl_tx_queue_update_write_ptr()
iwi3945: iwl_alive_start ALIVE processing complete.

jalavoui
TNW,

check this linux log
http://forum.insanelymac.com/index.php?sho...;p=479426&#

you don't need iwl_update_power_cmd -> but you can try

try to disable checkfirstup()
in older versions i use networkselector to turn the card on/off and call iwl_bg_up()

you might have a bug on the REPLY_ADD_STA handling

i think the linux log will help you to check what the driver should do
TNW
When the driver is activated lot of interuption come :/
is it normal ?
but when the driver is disactivated(with the switch) few interuption ...

I need help
jalavoui
QUOTE(TNW @ Feb 7 2008, 07:54 PM) *
When the driver is activated lot of interuption come :/


yes because in start() you have checkfirstup() wich calls iwl_bg_up()
if this is the problem just remove checkfirstup()
but youl'll need to use networkselector to turn the card on - or - you can try to press the switch button

it's normal to get lots of interrupts -> see the linux log
you can check the IODelay(HOST_COMPLETE_TIMEOUT) if you think the interrupts are coming to fast

i think the driver is going in the right direction smile.gif
BlackCH
Great job guys. I hope you get it working (3945).

In the meantime I attach a few logs. The Zip contains ioreg, dmesg, system log, and a profiler screenshot using the kext from post 64.

the other is a system log using the kext from post 69. This one doesnt let me boot, but I managed to copy the log from the command line as -s user.

keep it up!
TNW
I'm booring =_= by this !#@ driver ...
if someone can help me to dev this ...
I've got problem with the interrupts but I dont't what ...


I compiled the iwi2200 for leo ... but i can't test it...
TNW
I'm fine now ^^
there is a KP on iwl_enqueue_hcmd in base.c


if some have the time for =)

you have just to put a return after a line in iwl_enqueue_hcmd() and test , if it's ok put it after another line ...again and again ... it's crappy ,I know XD
sbandol
Hi guys,

I've just instaled last realease of the driver , and i have the folowing problem
in the network selector i got this text:

Last login: Fri Feb 8 01:00:20 on console
/Users/alexbandol/Desktop/networkSelector ; exit;
alex-bandols-mac-pro:~ alexbandol$ /Users/alexbandol/Desktop/networkSelector ; exit;
Could not get ID for kernel control. 2
logout

[Process completed]


when i normaly boot to mac i got the kernel panic , then i booted with -v -s and its booted fine but stil no network and the same text in network selector.

mayby i didnt install it good, i just used

i'm using a kalyway 10.5.1 on a Thinkpad R61

if other info needed i'm ready to offer them...

Than you ...
TNW
latest version :
no loop ,no kp , no log of 3 billion lines but no work XD
due to the iwl_send_cmd() function
sbandol
Hi TNW and others,

Like i have posted before , i didnt succed to instal this driver (i dont see the network adapter in about this mac) , so i'm asking you if you can write a step-by-step to instal tutoril,


I will be honest , i'm a windows user trying to swith to mac so i dont even know exactly how to use a .kext file .
Thats way im asking that tutorial.

Thank you in advance, i know writing a tutorial is not the most interesting thing.
TNW
open a Terminal
go to the good dir with "cd"
hint this on your keyboard

chown -R root:wheel iwi3945.kext
chmod 755 -R iwi3945.kext
kextload -t iwi3945.kext

that's all
antaholics
jalavoui and TNW,

Thanks for all the work on these drivers! I'm really glad people are working on this!

However, I have a Intel wireless 4965... and there doesn't seem to be any news on that ATM. Is the 3945 driver supposed to be really similar? If the 3645 driver eventually works, will it work for 4965 too?

Thanks!!
Ant
TNW
Normally yes the two drivers are(is) the same but I can't test it ..
blazes816
Just wanted to say thank you and keep up the good work! Can't wait for 3945 support!
Symuc
Wow, it looks as though a lot has happened while I've been away. Good job TNW.

I've got a question for javaloui, now: in working on getting minimally-modified drivers to do something. Anything. Right now they compile, but I'm coming up with compatability routines, for example a function called pci_free_consistent that actually calls IOFreeContiguous. So far, with the exception of replacing all instances like skb->data with a call to skb_data() (then writing a function skb_data()) and stripping the Linux-specific include files, it is working entirely without modification.

Do you think this is a viable, beneficial approach?
@irBOrNE
Wow, I accidentally lost my link to this forum topic and MAN was it hard to find! The search function in this forum is pretty useless at times. Anyway, defaulting back to a good old google search eventually got me here.

jalavoui - you might want to update the forum link to this on your http://code.google.com/p/iwidarwin/ page.

TNW and Symuc - make sure to work together on this, your combined knowledge will get you a much faster and better end product than trying to go separate routes in my opinion.. jalavoui, you're doing a fantastic job keeping it all tied together, thanks.
darval
QUOTE(TNW @ Feb 7 2008, 01:57 PM) *
I'm booring =_= by this !#@ driver ...if someone can help me to dev this ...I've got problem with the interrupts but I dont't what ...I compiled the iwi2200 for leo ... but i can't test it...
I just tried this with a fair amount of success. It loads (no KP at least), sees the network (using nsGUI) and lets me connect. It looks like it has a problem when it tries to get the address setup (dhcp wise). Log files attached.
QUOTE(Symuc @ Feb 7 2008, 04:55 PM) *
Do you think this is a viable, beneficial approach?
If the driver designs are compatible enough to make this work "fairly" easily, this is a fantastic approach. It allows the linux community to maintain the driver and us to gain the advantage if they make changes, improvements, bug fixes, etc..If you want some help with that, let me know. I have done some linux driver work, but am new to it in OSX.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.