dude, do not attempt hacking your bios.
i remember very well, some people mentioned about hp compatible intel cards in this thread.
why not getting one of them ?
i am really worried that u will screw your new laptop again.
otherwise it is fine.
Full Version: Intel Wireless 2100, 2200bg, 2915bg, 3945abg, 4965agn
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, 62, 63, 64, 65, 66, 67, 68, 69
"Mercurysquad"
Thanks for the insight, while were on the topic, What about using "classic" method as it allows direct access to the hardware layer without all the messy security layers of OSX10. Knowing that all classic applications run as "emulated" and arent given direct access to the hardware but what if we were to use the device as a "dial-up" device which has historically used direct hardware access because of the nature of the device, we make the os "think" were using a legacy device then develop an ap to negotiate the "legacy" device. once you have direct hardware access you wouldn't necessarily need to run the device through the kernel rather bootstrap it to something else? as we all know osx isnt very backwards compatible but if we rebranded to device as another device that would allow an application to control the hardware "messy". remember the days of the Generic driver? well if we rebranded the device or created a different firmware we could meet the development goal halfway. have the device itself be more compatible.
I would happily donate my intel 5100 wireless if it would help the cause!...kinda useless right now
just thinking outside the ∆
Intel5100 working in linux
Thanks for the insight, while were on the topic, What about using "classic" method as it allows direct access to the hardware layer without all the messy security layers of OSX10. Knowing that all classic applications run as "emulated" and arent given direct access to the hardware but what if we were to use the device as a "dial-up" device which has historically used direct hardware access because of the nature of the device, we make the os "think" were using a legacy device then develop an ap to negotiate the "legacy" device. once you have direct hardware access you wouldn't necessarily need to run the device through the kernel rather bootstrap it to something else? as we all know osx isnt very backwards compatible but if we rebranded to device as another device that would allow an application to control the hardware "messy". remember the days of the Generic driver? well if we rebranded the device or created a different firmware we could meet the development goal halfway. have the device itself be more compatible.
I would happily donate my intel 5100 wireless if it would help the cause!...kinda useless right now
just thinking outside the ∆
Intel5100 working in linux
CODE
http://ubuntuforums.org/showthread.php?t=879134&page=2
CODE
lshw -C network
*-network DISABLED
description: Wireless interface
product: Intel Corporation
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0e:00.0
logical name: wmaster0
version: 00
serial: 00:16:ea:73:64:e0
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl4965 latency=0 module=iwl4965 multicast=yes wireless=IEEE 802.11abgn
*-network
description: Ethernet interface
product: RTL8111/8168B PCI Express Gigabit Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:14:00.0
logical name: eth0
version: 02
serial: 00:1e:ec:55:88:02
size: 100MB/s
capacity: 1GB/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.2LK duplex=full ip=192.168.1.8 latency=0 link=yes module=r8169 multicast=yes port=twisted pair speed=100MB/s
*-network DISABLED
description: Wireless interface
product: Intel Corporation
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0e:00.0
logical name: wmaster0
version: 00
serial: 00:16:ea:73:64:e0
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl4965 latency=0 module=iwl4965 multicast=yes wireless=IEEE 802.11abgn
*-network
description: Ethernet interface
product: RTL8111/8168B PCI Express Gigabit Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:14:00.0
logical name: eth0
version: 02
serial: 00:1e:ec:55:88:02
size: 100MB/s
capacity: 1GB/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.2LK duplex=full ip=192.168.1.8 latency=0 link=yes module=r8169 multicast=yes port=twisted pair speed=100MB/s
I have a Lenovo X60 with 3945 and my Wireless works. I am using Leopard with VMware. It does not detect it as airport though.
QUOTE (IsmailBhai @ Jan 25 2009, 12:00 PM) 
I have a Lenovo X60 with 3945 and my Wireless works. I am using Leopard with VMware. It does not detect it as airport though.
In VMware your real hardware is not used directly.
That's not entirely true. I've done firmware upgrades on my bluray burner from within vmware that did rewrite the hardware code. I've also got a programmable usb joystick I can upload compiled code to in vmware and when I detatch the stick from vmware and reconnect it to linux the profile settings remain. Vmware does interact with real hardware. As far as I know however you are correct with regards to network devices. AFAIK vmware leaves the host system in control of networking.
QUOTE (DMJC @ Jan 27 2009, 10:11 AM)
That's not entirely true. I've done firmware upgrades on my bluray burner from within vmware that did rewrite the hardware code. I've also got a programmable usb joystick I can upload compiled code to in vmware and when I detatch the stick from vmware and reconnect it to linux the profile settings remain. Vmware does interact with real hardware. As far as I know however you are correct with regards to network devices. AFAIK vmware leaves the host system in control of networking.
Yes USB devices can be used directly from VMware. In general devices that need kernel-resident drivers are virtualized, devices which can work with userspace drivers can be used directly.
Are there new drivers für 4965?
Any suggestions to get intel wifi 4965 to work with unsecured networkes?
I tried out the experimental driver, but i get the same bug as the other here.
Pleease release a freakin build to get it working
Happy Coding!
peter
Any suggestions to get intel wifi 4965 to work with unsecured networkes?
I tried out the experimental driver, but i get the same bug as the other here.
Pleease release a freakin build to get it working
Happy Coding!
peter
QUOTE (Peter_Z. @ Jan 27 2009, 11:11 AM)
Are there new drivers für 4965?
Any suggestions to get intel wifi 4965 to work with unsecured networkes?
I tried out the experimental driver, but i get the same bug as the other here.
Pleease release a freakin build to get it working
Happy Coding!
peter
Any suggestions to get intel wifi 4965 to work with unsecured networkes?
I tried out the experimental driver, but i get the same bug as the other here.
Pleease release a freakin build to get it working
Happy Coding!
peter
This user has had their account suspended for two weeks as an example to those who do not read.
No there is no working driver yet, when it's done someone will post, stop asking.
Attached you'll find my log files. I have Kalyway 10.5.6 with an Intel Wireless WiFi Link 4965AGN.
Sincerely yours
*chris
PS: The system.txt file was empty, therefore it is missing here.
Sincerely yours
*chris
PS: The system.txt file was empty, therefore it is missing here.
In response to all of the pointless posts I just had to clean up I will summarize:
1. There is NO DRIVER for 3945, 4965, or 5100 that works yet, PERIOD, END OF STORY.
2. Graphics driver questions are to be kept in the GRAPHICS subsection.
3. Buying thoughts, reviews, and recommendations for replacement wireless cards for the as-yet-unworking cards are to be kept in the section conveniently named exactly that.
1. There is NO DRIVER for 3945, 4965, or 5100 that works yet, PERIOD, END OF STORY.
2. Graphics driver questions are to be kept in the GRAPHICS subsection.
3. Buying thoughts, reviews, and recommendations for replacement wireless cards for the as-yet-unworking cards are to be kept in the section conveniently named exactly that.
From Mercurysquad's blog, the information about IO80211ScanManager class is of interest. By a little reverse engineering, I picked the parts of IO80211Scanner and IO80211ScanManager out from IO80211Family binary file and attached it here. Click to view attachment
I'll be glad if this helps.
I'll be glad if this helps.
AWESOME! I was gonna pass the disassembly through c++filt and get just the class definition but you disassembled down to the implementation. There are some issues though, like :
You want to disassemble IO80211Controller and IO80211Interface also please?
CODE
if (node->358) return kAirPortReturnNoScanAvailable;
but it's still heavily useful.You want to disassemble IO80211Controller and IO80211Interface also please?
QUOTE (mercurysquad @ Feb 5 2009, 02:18 PM)
There are some issues though, like :
Actually all the variable name are guessed since I don't have the source file from Apple either. For those that no good candidate names can be jumped from my brain, I just use its offset in the structure as its name, thus node->358 is the variable located at offset 0x358 of the apple80211_scan_req_node structure. And for all the dissembled structures, the offset of each variable is labeled as an comment.CODE
if (node->358) return kAirPortReturnNoScanAvailable;
QUOTE
You want to disassemble IO80211Controller and IO80211Interface also please?
I will give it a try. 
QUOTE (realityiswhere @ Feb 5 2009, 06:50 AM)
1. There is NO DRIVER for 3945, 4965, or 5100 that works yet, PERIOD, END OF STORY.
Thanks, you just saved me a ton of reading!
I didnt read back far enough to see people criticizing me however I dont really care. I have work to do, I check on here and "play" with hackin tosh for fun and mental excercise. It would be nice if I could recreate the working intel card again but, I dont have time to take every one of the 6 or so OS86x version I burnt when I first undertook this SIDE project.
I DONT suggest those who are doubtful, those with little time, or those that just dont feel like it, to keep trying with old OS86x installers to get the intel card to work, I just wanted to let those that cared know, that a wormhole must have opened up during my 1st install of osx on M1210 and the wireless worked for a few hours. I didnt have sound, I didnt have proper resolution and I thought, AT THE TIME, that I would need to install a different VERSION of osx86 to fix that. Obviously I SHOULD HAVE left that 1st install on and patched all the other KEXTs but I was toying around still and didnt give a ....
anyhoo. Good luck finding the right kext or developing your own.
Adios.
I DONT suggest those who are doubtful, those with little time, or those that just dont feel like it, to keep trying with old OS86x installers to get the intel card to work, I just wanted to let those that cared know, that a wormhole must have opened up during my 1st install of osx on M1210 and the wireless worked for a few hours. I didnt have sound, I didnt have proper resolution and I thought, AT THE TIME, that I would need to install a different VERSION of osx86 to fix that. Obviously I SHOULD HAVE left that 1st install on and patched all the other KEXTs but I was toying around still and didnt give a ....
anyhoo. Good luck finding the right kext or developing your own.
Adios.
@vjkevlar:
Can you please stop posting your misleading info on this thread?
Let's review the facts you have stated --
1) You have a wireless card in your laptop
2) It needs Broadcom drivers to work under Windows
3) Intel drivers are listed on your laptop manufacturer's website next to Broadcom drivers
4) Because of point 3 you claim you have Intel wifi card
5) But your wifi card doesnt work with Intel drivers only, on Windows
6) It worked out of the box on OS X which supports Broadcom and Atheros only
7) It doesn't work with iwidarwin driver
Those 7 points prove conclusively that you have a Broadcom card.
Further, you were asked to post lspci output, or the PCI dev/vendor ID of your wireless card so we know which card you actually have. You didn't do this. All you have done is insist on something you cannot and have not proven through any evidence which MIGHT ACTUALLY HELP ANYONE.
Therefore, you have no business misleading people trying to actually do some real work. Please stay out of this thread.
Can you please stop posting your misleading info on this thread?
Let's review the facts you have stated --
1) You have a wireless card in your laptop
2) It needs Broadcom drivers to work under Windows
3) Intel drivers are listed on your laptop manufacturer's website next to Broadcom drivers
4) Because of point 3 you claim you have Intel wifi card
5) But your wifi card doesnt work with Intel drivers only, on Windows
6) It worked out of the box on OS X which supports Broadcom and Atheros only
7) It doesn't work with iwidarwin driver
Those 7 points prove conclusively that you have a Broadcom card.
Further, you were asked to post lspci output, or the PCI dev/vendor ID of your wireless card so we know which card you actually have. You didn't do this. All you have done is insist on something you cannot and have not proven through any evidence which MIGHT ACTUALLY HELP ANYONE.
Therefore, you have no business misleading people trying to actually do some real work. Please stay out of this thread.
I have an Intel PRO/Wireless 3945abg mini-PCI-e card in my laptop that I'm willing to donate if it will help getting a stable driver developed. If there's interest, PM me.
Hello. Hacintosh is a new toy of mine, and i'm new to it and new to the forum. I recently got an older macbook pro and fell in love with the OS. This led me to try hacintosh on my older laptop, which is a Toshiba Satellite A200-AH9 notebook.
It does have the 3945abg intel wireless card.
Please let me know if i can provide any information that will help with he progress of this kext.
The system is running leo 10.5.5 with the stock kernel using iATKOS and it is the only OS on the unit.
It does have the 3945abg intel wireless card.
Please let me know if i can provide any information that will help with he progress of this kext.
The system is running leo 10.5.5 with the stock kernel using iATKOS and it is the only OS on the unit.
Hello jalavoui!
I hope you can help me with the following issue. After installing the latest stable iwi2200 driver the Airport sign and also the sign of iwi GUI appeared on the menu bar. But when attempting to open Network preference pane it's window stops responding and subsequently the app quits with an error.
Also while i can select wireless network from GUI i can't connect to any.
The installing of tweaked IPPCIFamily.kext from iPC 10.5.6 distributive didn't help.
What do you suggest me to do?
I hope you can help me with the following issue. After installing the latest stable iwi2200 driver the Airport sign and also the sign of iwi GUI appeared on the menu bar. But when attempting to open Network preference pane it's window stops responding and subsequently the app quits with an error.
Also while i can select wireless network from GUI i can't connect to any.
The installing of tweaked IPPCIFamily.kext from iPC 10.5.6 distributive didn't help.
What do you suggest me to do?
finally got a laptop to work on iwi3945 code
this is the latest source code
looks like there's no code in linux for associating to a network (except for wireless event)
this means that iwi3945/4965 only scan for networks
i hope someone else can help making this work - i can't find a way to do this for now
this is very important and if it can be fixed i believe the remaining code can be done quiet easily
the ucode is very unstable in 3945 (works better in 4965). a few reboots fix it...
this release is for developers only
there's only a "simple" thing this code needs:
find a way to send a associate event to a network
in iwi2100/2200 this was done by sending a command to the card
i'm a bit frustrated but this code will need more than 2 days of work to make the driver associate to a network
this is the latest source code
looks like there's no code in linux for associating to a network (except for wireless event)
this means that iwi3945/4965 only scan for networks
i hope someone else can help making this work - i can't find a way to do this for now
this is very important and if it can be fixed i believe the remaining code can be done quiet easily
the ucode is very unstable in 3945 (works better in 4965). a few reboots fix it...
this release is for developers only
there's only a "simple" thing this code needs:
find a way to send a associate event to a network
in iwi2100/2200 this was done by sending a command to the card
i'm a bit frustrated but this code will need more than 2 days of work to make the driver associate to a network
Thanks for the developers' continuous work!
Here comes my newly dissembled code for IO80211Controller and IO80211Interface. All the class functions are done except one, i.e. IO80211Interface::setLinkstatus, I have part of it not clear yet. Most of the static non-class functions (not defined in .h file) are not dissembled due to a lack of information. Previous dissembled code for IO80211Scanner and IO80211ScanManager contain some errors because I treated "test" instruction as "cmp" instruction. The corrected version is put in new tar file as well.
I did not notice that jalavoui is not using the IOKit system. Sorry for put stuff on wrong place. Feel free to remove them.
Here comes my newly dissembled code for IO80211Controller and IO80211Interface. All the class functions are done except one, i.e. IO80211Interface::setLinkstatus, I have part of it not clear yet. Most of the static non-class functions (not defined in .h file) are not dissembled due to a lack of information. Previous dissembled code for IO80211Scanner and IO80211ScanManager contain some errors because I treated "test" instruction as "cmp" instruction. The corrected version is put in new tar file as well.
I did not notice that jalavoui is not using the IOKit system. Sorry for put stuff on wrong place. Feel free to remove them.
QUOTE (jalavoui @ Feb 10 2009, 10:03 PM)
finally got a laptop to work on iwi3945 code
this is the latest source code
looks like there's no code in linux for associating to a network (except for wireless event)
this means that iwi3945/4965 only scan for networks
i hope someone else can help making this work - i can't find a way to do this for now
this is very important and if it can be fixed i believe the remaining code can be done quiet easily
the ucode is very unstable in 3945 (works better in 4965). a few reboots fix it...
this release is for developers only
there's only a "simple" thing this code needs:
find a way to send a associate event to a network
in iwi2100/2200 this was done by sending a command to the card
i'm a bit frustrated but this code will need more than 2 days of work to make the driver associate to a network
this is the latest source code
looks like there's no code in linux for associating to a network (except for wireless event)
this means that iwi3945/4965 only scan for networks
i hope someone else can help making this work - i can't find a way to do this for now
this is very important and if it can be fixed i believe the remaining code can be done quiet easily
the ucode is very unstable in 3945 (works better in 4965). a few reboots fix it...
this release is for developers only
there's only a "simple" thing this code needs:
find a way to send a associate event to a network
in iwi2100/2200 this was done by sending a command to the card
i'm a bit frustrated but this code will need more than 2 days of work to make the driver associate to a network
Thanks Jalavoui....i wil test it.....
Hi to all
I Have a HP 530 Notebook (the celeron M version)
This is my WLAN Card
Intel PRO Wireless 802.11 a/b/g Wireless
i searched in google and in the forum but i dont found anything if (i will install the last version of ideneb)
Thanks so much and sorry for my crappy english (i'm from italy)
I Have a HP 530 Notebook (the celeron M version)
This is my WLAN Card
Intel PRO Wireless 802.11 a/b/g Wireless
i searched in google and in the forum but i dont found anything if (i will install the last version of ideneb)
Thanks so much and sorry for my crappy english (i'm from italy)
Hello,
I've just tested the last iwi3945, and even after several reboots, the card isn't initialized properly.
Here is what I had in system.log at first try :
After 4 reboots Ethernet address still ff:ff:ff:ff:ff:ff, the 'Unable to int nic' appears at each boot and the 'HARDWARE GONE??' message comes repeatedly.
I don't understand what makes the hardware initialization function fail.
I've just tested the last iwi3945, and even after several reboots, the card isn't initialized properly.
Here is what I had in system.log at first try :
CODE
Feb 11 19:41:28 Le-Bidou sudo[886]: lebidou : TTY=ttys001; PWD=/; USER=root; COMMAND=/usr/bin/su
Feb 11 19:41:42 Le-Bidou kernel[0]: Resetting IOCatalogue.
Feb 11 19:41:42 Le-Bidou kextd[10]: 0 cached, 436 uncached personalities to catalog
Feb 11 19:41:43 Le-Bidou kernel[0]: iwi3945: Starting
Feb 11 19:41:43 Le-Bidou kernel[0]: Someone called createOutputQueue()
Feb 11 19:41:43 Le-Bidou kernel[0]: settCurController [OK]
Feb 11 19:41:43 Le-Bidou kernel[0]: IOPCCard info: iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.23d
Feb 11 19:41:43 Le-Bidou kernel[0]: IOPCCard info: iwl3945: Copyright(c) 2003-2007 Intel Corporation
Feb 11 19:41:43 Le-Bidou kernel[0]: ieee80211_alloc_hw [OK]
Feb 11 19:41:43 Le-Bidou kernel[0]: IOPCCard info: iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
Feb 11 19:41:43 Le-Bidou kernel[0]: init_waitqueue_head stubbed out!
Feb 11 19:41:43 Le-Bidou kernel[0]: IOPCCard debug: wmaster1: Selected rate control algorithm 'iwl-3945-rs'
Feb 11 19:41:43 Le-Bidou kernel[0]: error iwl3945: Unable to int nic
Feb 11 19:41:45 Le-Bidou kernel[0]: no netif_running
Feb 11 19:41:45 Le-Bidou kernel[0]: Someone called createOutputQueue()
Feb 11 19:41:45 Le-Bidou kernel[0]: darwin_iwi3945::configureInterface()
Feb 11 19:41:45 Le-Bidou kernel[0]: power state (1)
Feb 11 19:41:45 Le-Bidou kernel[0]: darwin_iwi3945: Ethernet address ff:ff:ff:ff:ff:ff
Feb 11 19:41:54 Le-Bidou kernel[0]: warning iwl3945: HARDWARE GONE?? INTA == 0x000000000000000000000000000000000000000000000000000000000000000000000000ffffff
f
Feb 11 19:41:42 Le-Bidou kernel[0]: Resetting IOCatalogue.
Feb 11 19:41:42 Le-Bidou kextd[10]: 0 cached, 436 uncached personalities to catalog
Feb 11 19:41:43 Le-Bidou kernel[0]: iwi3945: Starting
Feb 11 19:41:43 Le-Bidou kernel[0]: Someone called createOutputQueue()
Feb 11 19:41:43 Le-Bidou kernel[0]: settCurController [OK]
Feb 11 19:41:43 Le-Bidou kernel[0]: IOPCCard info: iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.23d
Feb 11 19:41:43 Le-Bidou kernel[0]: IOPCCard info: iwl3945: Copyright(c) 2003-2007 Intel Corporation
Feb 11 19:41:43 Le-Bidou kernel[0]: ieee80211_alloc_hw [OK]
Feb 11 19:41:43 Le-Bidou kernel[0]: IOPCCard info: iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
Feb 11 19:41:43 Le-Bidou kernel[0]: init_waitqueue_head stubbed out!
Feb 11 19:41:43 Le-Bidou kernel[0]: IOPCCard debug: wmaster1: Selected rate control algorithm 'iwl-3945-rs'
Feb 11 19:41:43 Le-Bidou kernel[0]: error iwl3945: Unable to int nic
Feb 11 19:41:45 Le-Bidou kernel[0]: no netif_running
Feb 11 19:41:45 Le-Bidou kernel[0]: Someone called createOutputQueue()
Feb 11 19:41:45 Le-Bidou kernel[0]: darwin_iwi3945::configureInterface()
Feb 11 19:41:45 Le-Bidou kernel[0]: power state (1)
Feb 11 19:41:45 Le-Bidou kernel[0]: darwin_iwi3945: Ethernet address ff:ff:ff:ff:ff:ff
Feb 11 19:41:54 Le-Bidou kernel[0]: warning iwl3945: HARDWARE GONE?? INTA == 0x000000000000000000000000000000000000000000000000000000000000000000000000ffffff
f
After 4 reboots Ethernet address still ff:ff:ff:ff:ff:ff, the 'Unable to int nic' appears at each boot and the 'HARDWARE GONE??' message comes repeatedly.
I don't understand what makes the hardware initialization function fail.
QUOTE (jalavoui @ Feb 11 2009, 02:33 AM)
looks like there's no code in linux for associating to a network (except for wireless event)
Hey jalavoui, is your driver based on the new "iwlwifi" driver, or the linux driver that intel supplies (called ipw3945 i think)?
If it's the intel-supplied driver, then there is a daemon which needs to run, with which the driver interacts. Maybe you are missing that?
If it's based on the iwlwifi driver, then I don't know, the procedure to associate with a network seems to be roughly the same as 2200 (ie. send a command).
hope that helps.
QUOTE (dong @ Feb 11 2009, 05:36 AM)
Here comes my newly dissembled code for IO80211Controller and IO80211Interface.
Great, thanks a lot again!
But since your work is mostly related to the project:camphor drivers (not iwidarwin), could you in the future please use the blog (link in my sig) instead of this thread?
The forum admins have requested that we use this thread only for jalavoui's iwidarwin related discussion, to avoid confusion.
Thanks for all your efforts.
I believe u can do it.Just do it
I believe u can do it.Just do it
QUOTE (ElJobso @ Feb 11 2009, 08:31 PM)
Hi to all
I Have a HP 530 Notebook (the celeron M version)
This is my WLAN Card
Intel PRO Wireless 802.11 a/b/g Wireless
i searched in google and in the forum but i dont found anything if (i will install the last version of ideneb)
Thanks so much and sorry for my crappy english (i'm from italy)
I Have a HP 530 Notebook (the celeron M version)
This is my WLAN Card
Intel PRO Wireless 802.11 a/b/g Wireless
i searched in google and in the forum but i dont found anything if (i will install the last version of ideneb)
Thanks so much and sorry for my crappy english (i'm from italy)
Ok you´ve got a 530 from hp and you want to know wich wirless card it have ?
Ok i have the same Laptop but with a core2duo (
)and it have Intel 3945abg wich does not work at this time.With kalyway the rest works fine for me.
Hope I can help. If there any questions pm me
the ff:ff:ff:ff:ff:ff address is a old bug - search in this thread (i think it's related with iopcifamlily.kext)
in iwi2100/2200 you can send a command to associate to a network
in iwi3945... well...
i guess a hack can be made by taking some data from scan results (probe responses?)
best way to check this is to use svn latest source and the one i just posted
this is developer only work - i don't need test results
this can also be tested with iwi4965 (copy code from 3945). the 4965 firmware is much more stable
thanks to dong we have some code for io80211 family
ipw_scan() and IO80211Scanner
mercurysquad, do you plan to convert the linux code or just ignore some os x code in io80211?
i think you can use old iwi2200 code, pass the scan results to IO80211Scanner and ignore io80211 code (country, etc)
making the driver show the scan results in airport menu and allowing the user to select a network is 1rst goal
you also can rewrite the mbuf code (rx/tx). maybe this can make the driver work faster
iwi2200 as lot of unnecessary code - use just what you need
in iwi2100/2200 you can send a command to associate to a network
in iwi3945... well...
i guess a hack can be made by taking some data from scan results (probe responses?)
best way to check this is to use svn latest source and the one i just posted
this is developer only work - i don't need test results
this can also be tested with iwi4965 (copy code from 3945). the 4965 firmware is much more stable
thanks to dong we have some code for io80211 family
ipw_scan() and IO80211Scanner
mercurysquad, do you plan to convert the linux code or just ignore some os x code in io80211?
i think you can use old iwi2200 code, pass the scan results to IO80211Scanner and ignore io80211 code (country, etc)
making the driver show the scan results in airport menu and allowing the user to select a network is 1rst goal
you also can rewrite the mbuf code (rx/tx). maybe this can make the driver work faster
iwi2200 as lot of unnecessary code - use just what you need
I found this in the FreeBSD wpi driver(here) source (firmware v. 2.14.3), I thought it could be useful :
In if_wpireg.h line 243 :
Nevertheless, this command is never used in the driver.
It seems that the wpi driver uses the WPI_CMD_CONFIGURE command to listen to a particular channel. Plus, the struct it uses is more complete and looks more like the ipw_associate struct used in iwi2200.
This is the definition for it :
I hope it helps, and that I haven't polluted the thread one more time.
In if_wpireg.h line 243 :
CODE
struct wpi_tx_cmd {
uint8_t code;
#define WPI_CMD_CONFIGURE 16
#define WPI_CMD_ASSOCIATE 17
...
/* structure for command WPI_CMD_ASSOCIATE */
struct wpi_assoc {
uint32_t flags;
uint32_t filter;
uint8_t ofdm_mask;
uint8_t cck_mask;
uint16_t reserved;
} __packed;
uint8_t code;
#define WPI_CMD_CONFIGURE 16
#define WPI_CMD_ASSOCIATE 17
...
/* structure for command WPI_CMD_ASSOCIATE */
struct wpi_assoc {
uint32_t flags;
uint32_t filter;
uint8_t ofdm_mask;
uint8_t cck_mask;
uint16_t reserved;
} __packed;
Nevertheless, this command is never used in the driver.
It seems that the wpi driver uses the WPI_CMD_CONFIGURE command to listen to a particular channel. Plus, the struct it uses is more complete and looks more like the ipw_associate struct used in iwi2200.
This is the definition for it :
CODE
/* structure for WPI_CMD_CONFIGURE */
struct wpi_config {
uint8_t myaddr[IEEE80211_ADDR_LEN];
uint16_t reserved1;
uint8_t bssid[IEEE80211_ADDR_LEN];
uint16_t reserved2;
uint8_t wlap_bssid_addr[6];
uint16_t reserved3;
uint8_t mode;
#define WPI_MODE_HOSTAP 1
#define WPI_MODE_STA 3
#define WPI_MODE_IBSS 4
#define WPI_MODE_MONITOR 6
uint8_t air_propogation;
uint16_t reserved4;
uint8_t ofdm_mask;
uint8_t cck_mask;
uint16_t associd;
uint32_t flags;
#define WPI_CONFIG_24GHZ (1 << 0)
#define WPI_CONFIG_CCK (1 << 1)
#define WPI_CONFIG_AUTO (1 << 2)
#define WPI_CONFIG_SHSLOT (1 << 4)
#define WPI_CONFIG_SHPREAMBLE (1 << 5)
#define WPI_CONFIG_NODIVERSITY (1 << 7)
#define WPI_CONFIG_ANTENNA_A (1 << 8)
#define WPI_CONFIG_ANTENNA_B (1 << 9)
#define WPI_CONFIG_TSF (1 << 15)
uint32_t filter;
#define WPI_FILTER_PROMISC (1 << 0)
#define WPI_FILTER_CTL (1 << 1)
#define WPI_FILTER_MULTICAST (1 << 2)
#define WPI_FILTER_NODECRYPT (1 << 3)
#define WPI_FILTER_BSS (1 << 5)
#define WPI_FILTER_BEACON (1 << 6)
uint8_t chan;
uint16_t reserved6;
} __packed;
struct wpi_config {
uint8_t myaddr[IEEE80211_ADDR_LEN];
uint16_t reserved1;
uint8_t bssid[IEEE80211_ADDR_LEN];
uint16_t reserved2;
uint8_t wlap_bssid_addr[6];
uint16_t reserved3;
uint8_t mode;
#define WPI_MODE_HOSTAP 1
#define WPI_MODE_STA 3
#define WPI_MODE_IBSS 4
#define WPI_MODE_MONITOR 6
uint8_t air_propogation;
uint16_t reserved4;
uint8_t ofdm_mask;
uint8_t cck_mask;
uint16_t associd;
uint32_t flags;
#define WPI_CONFIG_24GHZ (1 << 0)
#define WPI_CONFIG_CCK (1 << 1)
#define WPI_CONFIG_AUTO (1 << 2)
#define WPI_CONFIG_SHSLOT (1 << 4)
#define WPI_CONFIG_SHPREAMBLE (1 << 5)
#define WPI_CONFIG_NODIVERSITY (1 << 7)
#define WPI_CONFIG_ANTENNA_A (1 << 8)
#define WPI_CONFIG_ANTENNA_B (1 << 9)
#define WPI_CONFIG_TSF (1 << 15)
uint32_t filter;
#define WPI_FILTER_PROMISC (1 << 0)
#define WPI_FILTER_CTL (1 << 1)
#define WPI_FILTER_MULTICAST (1 << 2)
#define WPI_FILTER_NODECRYPT (1 << 3)
#define WPI_FILTER_BSS (1 << 5)
#define WPI_FILTER_BEACON (1 << 6)
uint8_t chan;
uint16_t reserved6;
} __packed;
I hope it helps, and that I haven't polluted the thread one more time.
Hi guys. I followed all the instructions and I would like to say. Fantastic walkthrough on installation of the driver. Really covered everything. Did I get it first time, hell no.
But got to a stage where I could scan through the network selector i put on the desktop. Picked up more networks than the same card running windows 7 which is interesting.
So as I understand it , we can all now scan for networks. No more at this stage. So peeps with the audacity to ask for a working driver, its not fully complete but these guys are really close to getting it working. But it could take a long time. So dont bug)(lol) them.
I learnt a lot from this and really do appreciate the work going into not just testing, but making tutorials for noobs and sharing what has been many hours of trials and stress. djar
But got to a stage where I could scan through the network selector i put on the desktop. Picked up more networks than the same card running windows 7 which is interesting.
So as I understand it , we can all now scan for networks. No more at this stage. So peeps with the audacity to ask for a working driver, its not fully complete but these guys are really close to getting it working. But it could take a long time. So dont bug)(lol) them.
I learnt a lot from this and really do appreciate the work going into not just testing, but making tutorials for noobs and sharing what has been many hours of trials and stress. djar
...
this thread is for development only
if you like to complain about driver development open a new thread
i need a moderator do erase all this posts back to the one i post the latest source code for development
iwi3945/4965 status
need help on fixing the association code
this thread is for development only
if you like to complain about driver development open a new thread
i need a moderator do erase all this posts back to the one i post the latest source code for development
iwi3945/4965 status
need help on fixing the association code
I'm not looking for any contributors. iwidarwin source is open and is at a MUCH advanced stage. If people want to help, they should start with jalavoui's code. The guy ran a one-man-show for 3 effing years and no one really contributed anything significant. It's not respectful to recommend HIM to work with someone when it should be the other way round. Talk is cheap; show us the code.
QUOTE (mercurysquad @ Mar 19 2009, 02:41 PM)
I'm not looking for any contributors. iwidarwin source is open and is at a MUCH advanced stage. If people want to help, they should start with jalavoui's code. The guy ran a one-man-show for 3 effing years and no one really contributed anything significant. It's not respectful to recommend HIM to work with someone when it should be the other way round. Talk is cheap; show us the code.
This post was genius right here. Mercurysquad is 100% right with this.
Got the dreaded: "Could not get Id for kernel control" I've done the following:
-Checked and the iwi2200.kext is installed
-Rebooted
-Am not in safe mode
-Have removed and reinstalled iwi2200 three times
-Have reinstalled 10.5.2 twice
-Have been working on this for a week (Grrrrr)
-Have noted random (and perhaps unrelated) messages in the boot log (attached) like:
1. -pci card interrupt, pci status change
2. -dumpPanic[29] error getting reference to device tree (or something like this)
3. -com.apple driver has dependencies on both com.apple.kernel and com.apple.kpi components, use only one style
Any thoughts?
x40 Thinkpad
10.5.2
Intel Pro Wireless Card
(UPDATE 3-26) After more diddling with the iwi2200 kext, I'm beginning the think the fault is with the IOPCCardbridge. The log tels me that it has failed to start. Should I be in a different topic?
Hello? Anyone? Is this thing on?
-andy
Click to view attachment
Click to view attachment
Click to view attachment
-Checked and the iwi2200.kext is installed
-Rebooted
-Am not in safe mode
-Have removed and reinstalled iwi2200 three times
-Have reinstalled 10.5.2 twice
-Have been working on this for a week (Grrrrr)
-Have noted random (and perhaps unrelated) messages in the boot log (attached) like:
1. -pci card interrupt, pci status change
2. -dumpPanic[29] error getting reference to device tree (or something like this)
3. -com.apple driver has dependencies on both com.apple.kernel and com.apple.kpi components, use only one style
Any thoughts?
x40 Thinkpad
10.5.2
Intel Pro Wireless Card
(UPDATE 3-26) After more diddling with the iwi2200 kext, I'm beginning the think the fault is with the IOPCCardbridge. The log tels me that it has failed to start. Should I be in a different topic?
Hello? Anyone? Is this thing on?
-andy
Click to view attachment
Click to view attachment
Click to view attachment
QUOTE (squeezebag @ Mar 25 2009, 01:52 PM)
Got the dreaded: "Could not get Id for kernel control" I've done the following:
-Checked and the iwi2200.kext is installed
-Rebooted
-Am not in safe mode
-Have removed and reinstalled iwi2200 three times
-Have reinstalled 10.5.2 twice
-Have been working on this for a week (Grrrrr)
-Have noted random (and perhaps unrelated) messages in the boot log (attached) like:
1. -pci card interrupt, pci status change
2. -dumpPanic[29] error getting reference to device tree (or something like this)
3. -com.apple driver has dependencies on both com.apple.kernel and com.apple.kpi components, use only one style
Any thoughts?
x40 Thinkpad
10.5.2
Intel Pro Wireless Card
(UPDATE 3-26) After more diddling with the iwi2200 kext, I'm beginning the think the fault is with the IOPCCardbridge. The log tels me that it has failed to start. Should I be in a different topic?
Hello? Anyone? Is this thing on?
-andy
Click to view attachment
Click to view attachment
Click to view attachment
-Checked and the iwi2200.kext is installed
-Rebooted
-Am not in safe mode
-Have removed and reinstalled iwi2200 three times
-Have reinstalled 10.5.2 twice
-Have been working on this for a week (Grrrrr)
-Have noted random (and perhaps unrelated) messages in the boot log (attached) like:
1. -pci card interrupt, pci status change
2. -dumpPanic[29] error getting reference to device tree (or something like this)
3. -com.apple driver has dependencies on both com.apple.kernel and com.apple.kpi components, use only one style
Any thoughts?
x40 Thinkpad
10.5.2
Intel Pro Wireless Card
(UPDATE 3-26) After more diddling with the iwi2200 kext, I'm beginning the think the fault is with the IOPCCardbridge. The log tels me that it has failed to start. Should I be in a different topic?
Hello? Anyone? Is this thing on?
-andy
Click to view attachment
Click to view attachment
Click to view attachment
Have you tried installing the IOPCCard drivers from this post? http://forum.insanelymac.com/index.php?sho...036&st=500#
QUOTE (asstastic @ Mar 26 2009, 10:53 PM)
Have you tried installing the IOPCCard drivers from this post? http://forum.insanelymac.com/index.php?sho...036&st=500#
I did install these drivers - PCCard.10.5.2.Beta2.pkg.zip ( 222.24K ) Number of downloads: 6404. I just went through the install and took the defaults. No help.
QUOTE (squeezebag @ Mar 28 2009, 06:35 AM)
I did install these drivers - PCCard.10.5.2.Beta2.pkg.zip ( 222.24K ) Number of downloads: 6404. I just went through the install and took the defaults. No help.
It didn't solve my problem either. Stuck with ff:ff:ff… MAC Address…
iwi3945 release 1213
ethernet version - no airport driver here
the driver tries to associate to the first open network available...
if association fails or if you get a kernel panic shutdown and reboot
download from svn tree
http://code.google.com/p/iwidarwin/
don't use networkselector
post system.log
what's missing:
send authentication - this will allow the driver to call associate and post-associate
feel free to hack the code and make it work
ethernet version - no airport driver here
the driver tries to associate to the first open network available...
if association fails or if you get a kernel panic shutdown and reboot
download from svn tree
http://code.google.com/p/iwidarwin/
don't use networkselector
post system.log
what's missing:
send authentication - this will allow the driver to call associate and post-associate
feel free to hack the code and make it work
crash after associated with first open network, but gd job
regards
martin
regards
martin
here is my system log
4965agn on 10.5.5
Although the results don't mention anything I am assuming this because the firmware for 4965agn is not included.
4965agn on 10.5.5
Although the results don't mention anything I am assuming this because the firmware for 4965agn is not included.
QUOTE (jalavoui @ Mar 31 2009, 10:27 AM)
iwi3945 release 1213
ethernet version - no airport driver here
the driver tries to associate to the first open network available...
if association fails or if you get a kernel panic shutdown and reboot
download from svn tree
http://code.google.com/p/iwidarwin/
don't use networkselector
post system.log
what's missing:
send authentication - this will allow the driver to call associate and post-associate
feel free to hack the code and make it work
ethernet version - no airport driver here
the driver tries to associate to the first open network available...
if association fails or if you get a kernel panic shutdown and reboot
download from svn tree
http://code.google.com/p/iwidarwin/
don't use networkselector
post system.log
what's missing:
send authentication - this will allow the driver to call associate and post-associate
feel free to hack the code and make it work
CODE
Apr 1 13:31:18 macbook kernel[0]: error iwl3945: Unable to initialize PCI module
Apr 1 13:31:18 macbook kernel[0]: iwi3945: Starting
Apr 1 13:31:18 macbook kernel[0]: IOPCCard info: iwl3945:
Intel® PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.23d
Apr 1 13:31:18 macbook kernel[0]: IOPCCard info: iwl3945: Copyright© 2003-2007
Intel Corporation
Apr 1 13:31:18 macbook kernel[0]: IOPCCard info: iwl3945:
Detected Intel PRO/Wireless 3945ABG Network Connection
Apr 1 13:31:18 macbook kernel[0]: iwi3945: Starting
Apr 1 13:31:18 macbook kernel[0]: IOPCCard info: iwl3945:
Intel® PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.23d
Apr 1 13:31:18 macbook kernel[0]: IOPCCard info: iwl3945: Copyright© 2003-2007
Intel Corporation
Apr 1 13:31:18 macbook kernel[0]: IOPCCard info: iwl3945:
Detected Intel PRO/Wireless 3945ABG Network Connection
No connection, no kernel panic
Someone needs to lock this thread.
People, stop trying to get it working. Instead, just wait for these guys (http://projectcamphor.mercurysquad.com/) to get it working.
People, stop trying to get it working. Instead, just wait for these guys (http://projectcamphor.mercurysquad.com/) to get it working.
I've been looking forward both projects for some months and i've been wondering if there's any way to pass directly the pci device interaction to a virtual machine and let it recognize the device using the built-in drivers (ie. Linux) and then get it back to mac via a virtual ethernet device.
What i mean is that running a virtual operating system (with parallels, for example) you can pass directly to the emulated system the physical pci address and let that system interact with it, only having to use a virtual driver to get the network back to the mac so that you can connect to internet via the virtual machine.
I believe that'd be simplier than getting around all encryption systems of the card (up to wpa2 on 3945, which i'm using) and using an small amount of resources (you can boot gentoo with minimal ram and cpu usage), plus drivers for these platforms are open-source so that you can get it easily.
In fact you'd be able to do so if you get the way to pass directly the pci adress to the vm, any ideas?
Edit: Well going on that idea i've found that this is possible on fedora virtual machines: http://fedoraproject.org/wiki/Features/KVM...vice_Assignment
I'm going to try to get those libraries working on mac via fink, and maybe if i get the vm working i'd be able to assign the physicall bus of the card to the vm.
What i mean is that running a virtual operating system (with parallels, for example) you can pass directly to the emulated system the physical pci address and let that system interact with it, only having to use a virtual driver to get the network back to the mac so that you can connect to internet via the virtual machine.
I believe that'd be simplier than getting around all encryption systems of the card (up to wpa2 on 3945, which i'm using) and using an small amount of resources (you can boot gentoo with minimal ram and cpu usage), plus drivers for these platforms are open-source so that you can get it easily.
In fact you'd be able to do so if you get the way to pass directly the pci adress to the vm, any ideas?
Edit: Well going on that idea i've found that this is possible on fedora virtual machines: http://fedoraproject.org/wiki/Features/KVM...vice_Assignment
I'm going to try to get those libraries working on mac via fink, and maybe if i get the vm working i'd be able to assign the physicall bus of the card to the vm.
QUOTE (yushir @ Apr 4 2009, 01:43 PM)
I've been looking forward both projects for some months and i've been wondering if there's any way to pass directly the pci device interaction to a virtual machine and let it recognize the device using the built-in drivers (ie. Linux) and then get it back to mac via a virtual ethernet device.
What i mean is that running a virtual operating system (with parallels, for example) you can pass directly to the emulated system the physical pci address and let that system interact with it, only having to use a virtual driver to get the network back to the mac so that you can connect to internet via the virtual machine.
I believe that'd be simplier than getting around all encryption systems of the card (up to wpa2 on 3945, which i'm using) and using an small amount of resources (you can boot gentoo with minimal ram and cpu usage), plus drivers for these platforms are open-source so that you can get it easily.
In fact you'd be able to do so if you get the way to pass directly the pci adress to the vm, any ideas?
Edit: Well going on that idea i've found that this is possible on fedora virtual machines: http://fedoraproject.org/wiki/Features/KVM...vice_Assignment
I'm going to try to get those libraries working on mac via fink, and maybe if i get the vm working i'd be able to assign the physicall bus of the card to the vm.
What i mean is that running a virtual operating system (with parallels, for example) you can pass directly to the emulated system the physical pci address and let that system interact with it, only having to use a virtual driver to get the network back to the mac so that you can connect to internet via the virtual machine.
I believe that'd be simplier than getting around all encryption systems of the card (up to wpa2 on 3945, which i'm using) and using an small amount of resources (you can boot gentoo with minimal ram and cpu usage), plus drivers for these platforms are open-source so that you can get it easily.
In fact you'd be able to do so if you get the way to pass directly the pci adress to the vm, any ideas?
Edit: Well going on that idea i've found that this is possible on fedora virtual machines: http://fedoraproject.org/wiki/Features/KVM...vice_Assignment
I'm going to try to get those libraries working on mac via fink, and maybe if i get the vm working i'd be able to assign the physicall bus of the card to the vm.
hardware not detected on host OS wont ever work on Virtualized OS. kthx
QUOTE (Beto2k7 @ Apr 5 2009, 04:23 AM)
hardware not detected on host OS wont ever work on Virtualized OS. kthx
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.
Yes, it might work, but if your running a VM anyway, you might as well just run a Windows VM or Linux VM and use it as your web browser whenever you need it .
Though I've never used VM's so I might be an idiot here.
-Daniel
.Though I've never used VM's so I might be an idiot here
.-Daniel
Well i've got to give you some bad news, here's how's all:
The only emulators that can pass directly physicall pci interfaces to the guest machines are Qemu and Kvm (and Xen*) both of them using Libvirt which does all the job.
VMware guys are so lazy they don't want to make it ever possible (you can look on google there's a post saying it from VMware).
Now: Kvm guys are most likely to not to help us, and they say that porting their software from linux to mac is likely to get more time than developing the driver (i asked them on the irc and that was what they said) and told me to look after Xen.
Xen is currently not supporting Mac Os X as a host machine (there was a project named xenU which was given away some years ago), so it isn't an option.
*Xen uses linux kernel and it WON'T WORK unless a full port based on the XNU (Mac) Kernel is done.
Qemu can also use that lib, can be installed on mac via Macports and has a nice gui called Q which actually runs Virtual Machines.
Now the trick is getting the libvirt compiled on Mac OS X and making Qemu load it.
As u might notice the hard thing is to get the libvirt compiled, there are lots of dependencies missing and it's most likely to send us to hell before getting it to work.
I'm not specialized in porting apps to mac and it's not likely i will get anywhere (at least now by now, i've work to do) so may anyone get interested on this?
Well at least i got the info,
See ya!
PD: For those interested, look at http://qemu-forum.ipi.fi/viewtopic.php?f=6&t=4961
The only emulators that can pass directly physicall pci interfaces to the guest machines are Qemu and Kvm (and Xen*) both of them using Libvirt which does all the job.
VMware guys are so lazy they don't want to make it ever possible (you can look on google there's a post saying it from VMware).
Now: Kvm guys are most likely to not to help us, and they say that porting their software from linux to mac is likely to get more time than developing the driver (i asked them on the irc and that was what they said) and told me to look after Xen.
Xen is currently not supporting Mac Os X as a host machine (there was a project named xenU which was given away some years ago), so it isn't an option.
*Xen uses linux kernel and it WON'T WORK unless a full port based on the XNU (Mac) Kernel is done.
Qemu can also use that lib, can be installed on mac via Macports and has a nice gui called Q which actually runs Virtual Machines.
Now the trick is getting the libvirt compiled on Mac OS X and making Qemu load it.
As u might notice the hard thing is to get the libvirt compiled, there are lots of dependencies missing and it's most likely to send us to hell before getting it to work.
I'm not specialized in porting apps to mac and it's not likely i will get anywhere (at least now by now, i've work to do) so may anyone get interested on this?
Well at least i got the info
,See ya!
PD: For those interested, look at http://qemu-forum.ipi.fi/viewtopic.php?f=6&t=4961
Hello.
I instal iwi3945.kext. I see the wireless network, but i can't connect.
See my system log fnd help me pleas.
My system log iwi3945
1)
Apr 8 13:01:58 localhost kernel[0]: iwi3945: Starting
Apr 8 13:01:58 localhost kernel[0]: Someone called createOutputQueue()
Apr 8 13:01:58 localhost kernel[0]: settCurController [OK]
Apr 8 13:01:58 localhost kernel[0]: IOPCCard info: iwl3945: Intel® PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.23d
Apr 8 13:01:58 localhost kernel[0]: IOPCCard info: iwl3945: Copyright© 2003-2007 Intel Corporation
Apr 8 13:01:58 localhost kernel[0]: ieee80211_alloc_hw [OK]
Apr 8 13:01:58 localhost kernel[0]: PCI device enabled [OK]
Apr 8 13:01:58 localhost kernel[0]: IOPCCard info: iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
Apr 8 13:01:58 localhost kernel[0]: init_waitqueue_head stubbed out!
Apr 8 13:01:58 localhost kernel[0]: IOPCCard debug: wmaster1: Selected rate control algorithm 'iwl-3945-rs'
Apr 8 13:01:58 localhost kernel[0]: PCI device enabled [OK]
Apr 8 13:01:58 localhost kernel[0]: NVDANV50HAL loaded and registered.
Apr 8 13:01:58 localhost kernel[0]: __ IN iwl3945_alive_start __
Apr 8 13:01:58 localhost kernel[0]: NVID: family specific matching fails
Apr 8 13:01:58 localhost kernel[0]: IOPCCard info: iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels
Apr 8 13:01:58 localhost kernel[0]: error iwl3945: Microcode SW error detected. Restarting 0x82000008.
Apr 8 13:01:58 localhost kernel[0]: error iwl3945: Error Reply type 0x00000000 cmd UNKNOWN (0x00) seq 0x0000 ser 0x00000000
Apr 8 13:01:58 localhost kernel[0]: error iwl3945: No space for Tx
Apr 8 13:01:58 localhost kernel[0]: error iwl3945: Error sending REPLY_BT_CONFIG: iwl3945_enqueue_hcmd failed: -28
Apr 8 13:01:58 localhost kernel[0]: __ OUT iwl3945_alive_start __
Apr 8 13:01:58 localhost kernel[0]: IOPCCard debug: HW CONFIG: channel=1 freq=2412 phymode=3
Apr 8 13:01:59 localhost kernel[0]: no netif_running
Apr 8 13:01:59 localhost kernel[0]: Someone called createOutputQueue()
Apr 8 13:01:59 localhost kernel[0]: power state (1)
Apr 8 13:01:59 localhost kernel[0]: darwin_iwi3945::configureInterface()
Apr 8 13:01:59 localhost kernel[0]: error iwl3945: Can't stop Rx DMA.
Apr 8 13:01:59 localhost kernel[0]: __ IN iwl3945_alive_start __
Apr 8 13:01:59 localhost diskarbitrationd[31]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Apr 8 13:01:59 localhost kernel[0]: Sending RXON
Apr 8 13:01:59 localhost kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:01:59 localhost DirectoryService[32]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Apr 8 13:01:59 localhost kernel[0]: * channel = 1
Apr 8 13:01:59 localhost mds[21]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Apr 8 13:01:59 localhost kernel[0]: * bssid = 00:00:00:00:00:00
Apr 8 13:01:59 localhost configd[34]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Apr 8 13:01:59 localhost kernel[0]: __ OUT iwl3945_alive_start __
2)
Apr 8 13:05:25 kirill-s-marinins-macpro31 kernel[0]: darwin_iwi3945::enable()
Apr 8 13:05:25 kirill-s-marinins-macpro31 kernel[0]: ifconfig going up
Apr 8 13:05:25 kirill-s-marinins-macpro31 kernel[0]: IOPCCard debug: en1: dropped data frame to not associated station
Apr 8 13:05:25 kirill-s-marinins-macpro31 kernel[0]: TXRX_DROP fail
Apr 8 13:05:27 kirill-s-marinins-macpro31 kernel[0]: bss_add= 02:13:d4:ff:c1:eb ('')
Apr 8 13:05:27 kirill-s-marinins-macpro31 kernel[0]: q6
Apr 8 13:05:29: --- last message repeated 7 times ---
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: IOPCCard debug: HW CONFIG: channel=1 freq=2412 phymode=3
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: Sending RXON
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * channel = 1
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * bssid = 00:00:00:00:00:00
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: Sending RXON
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * channel = 1
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * bssid = 00:00:00:00:00:00
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: searching for networks...
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: 1) 02:13:d4:ff:c1:eb ('Wireless') cap 411 hw 3 ch 1
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: trying to associate
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: IOPCCard debug: HW CONFIG: channel=1 freq=2412 phymode=3
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: Sending RXON
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * channel = 1
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * bssid = 02:13:d4:ff:c1:eb
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: Sending RXON
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * channel = 1
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * bssid = 02:13:d4:ff:c1:eb
Apr 8 13:05:25 kirill-s-marinins-macpro31 kernel[0]: darwin_iwi3945::enable()
Apr 8 13:05:25 kirill-s-marinins-macpro31 kernel[0]: ifconfig going up
Apr 8 13:05:25 kirill-s-marinins-macpro31 kernel[0]: IOPCCard debug: en1: dropped data frame to not associated station
Apr 8 13:05:25 kirill-s-marinins-macpro31 kernel[0]: TXRX_DROP fail
Apr 8 13:05:27 kirill-s-marinins-macpro31 kernel[0]: bss_add= 02:13:d4:ff:c1:eb ('')
Apr 8 13:05:27 kirill-s-marinins-macpro31 kernel[0]: q6
Apr 8 13:05:29: --- last message repeated 7 times ---
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: IOPCCard debug: HW CONFIG: channel=1 freq=2412 phymode=3
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: Sending RXON
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * channel = 1
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * bssid = 00:00:00:00:00:00
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: Sending RXON
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * channel = 1
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * bssid = 00:00:00:00:00:00
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: searching for networks...
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: 1) 02:13:d4:ff:c1:eb ('Wireless') cap 411 hw 3 ch 1
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: trying to associate
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: IOPCCard debug: HW CONFIG: channel=1 freq=2412 phymode=3
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: Sending RXON
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * channel = 1
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * bssid = 02:13:d4:ff:c1:eb
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: Sending RXON
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * channel = 1
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * bssid = 02:13:d4:ff:c1:eb
3)
Apr 8 14:01:11 bb-92-43-6-146 kernel[0]: IOPCCard debug: en1: associcated
Apr 8 14:01:11 bb-92-43-6-146 kernel[0]: IOPCCard debug: en1: No STA entry for own AP 00:00:00:00:00:00
Apr 8 14:01:12 bb-92-43-6-146 kernel[0]: IOPCCard debug: en1: dropped data frame to not associated station
Apr 8 14:01:12 bb-92-43-6-146 kernel[0]: TXRX_DROP fail
I instal iwi3945.kext. I see the wireless network, but i can't connect.
See my system log fnd help me pleas.
My system log iwi3945
1)
Apr 8 13:01:58 localhost kernel[0]: iwi3945: Starting
Apr 8 13:01:58 localhost kernel[0]: Someone called createOutputQueue()
Apr 8 13:01:58 localhost kernel[0]: settCurController [OK]
Apr 8 13:01:58 localhost kernel[0]: IOPCCard info: iwl3945: Intel® PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.23d
Apr 8 13:01:58 localhost kernel[0]: IOPCCard info: iwl3945: Copyright© 2003-2007 Intel Corporation
Apr 8 13:01:58 localhost kernel[0]: ieee80211_alloc_hw [OK]
Apr 8 13:01:58 localhost kernel[0]: PCI device enabled [OK]
Apr 8 13:01:58 localhost kernel[0]: IOPCCard info: iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
Apr 8 13:01:58 localhost kernel[0]: init_waitqueue_head stubbed out!
Apr 8 13:01:58 localhost kernel[0]: IOPCCard debug: wmaster1: Selected rate control algorithm 'iwl-3945-rs'
Apr 8 13:01:58 localhost kernel[0]: PCI device enabled [OK]
Apr 8 13:01:58 localhost kernel[0]: NVDANV50HAL loaded and registered.
Apr 8 13:01:58 localhost kernel[0]: __ IN iwl3945_alive_start __
Apr 8 13:01:58 localhost kernel[0]: NVID: family specific matching fails
Apr 8 13:01:58 localhost kernel[0]: IOPCCard info: iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels
Apr 8 13:01:58 localhost kernel[0]: error iwl3945: Microcode SW error detected. Restarting 0x82000008.
Apr 8 13:01:58 localhost kernel[0]: error iwl3945: Error Reply type 0x00000000 cmd UNKNOWN (0x00) seq 0x0000 ser 0x00000000
Apr 8 13:01:58 localhost kernel[0]: error iwl3945: No space for Tx
Apr 8 13:01:58 localhost kernel[0]: error iwl3945: Error sending REPLY_BT_CONFIG: iwl3945_enqueue_hcmd failed: -28
Apr 8 13:01:58 localhost kernel[0]: __ OUT iwl3945_alive_start __
Apr 8 13:01:58 localhost kernel[0]: IOPCCard debug: HW CONFIG: channel=1 freq=2412 phymode=3
Apr 8 13:01:59 localhost kernel[0]: no netif_running
Apr 8 13:01:59 localhost kernel[0]: Someone called createOutputQueue()
Apr 8 13:01:59 localhost kernel[0]: power state (1)
Apr 8 13:01:59 localhost kernel[0]: darwin_iwi3945::configureInterface()
Apr 8 13:01:59 localhost kernel[0]: error iwl3945: Can't stop Rx DMA.
Apr 8 13:01:59 localhost kernel[0]: __ IN iwl3945_alive_start __
Apr 8 13:01:59 localhost diskarbitrationd[31]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Apr 8 13:01:59 localhost kernel[0]: Sending RXON
Apr 8 13:01:59 localhost kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:01:59 localhost DirectoryService[32]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Apr 8 13:01:59 localhost kernel[0]: * channel = 1
Apr 8 13:01:59 localhost mds[21]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Apr 8 13:01:59 localhost kernel[0]: * bssid = 00:00:00:00:00:00
Apr 8 13:01:59 localhost configd[34]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Apr 8 13:01:59 localhost kernel[0]: __ OUT iwl3945_alive_start __
2)
Apr 8 13:05:25 kirill-s-marinins-macpro31 kernel[0]: darwin_iwi3945::enable()
Apr 8 13:05:25 kirill-s-marinins-macpro31 kernel[0]: ifconfig going up
Apr 8 13:05:25 kirill-s-marinins-macpro31 kernel[0]: IOPCCard debug: en1: dropped data frame to not associated station
Apr 8 13:05:25 kirill-s-marinins-macpro31 kernel[0]: TXRX_DROP fail
Apr 8 13:05:27 kirill-s-marinins-macpro31 kernel[0]: bss_add= 02:13:d4:ff:c1:eb ('')
Apr 8 13:05:27 kirill-s-marinins-macpro31 kernel[0]: q6
Apr 8 13:05:29: --- last message repeated 7 times ---
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: IOPCCard debug: HW CONFIG: channel=1 freq=2412 phymode=3
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: Sending RXON
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * channel = 1
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * bssid = 00:00:00:00:00:00
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: Sending RXON
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * channel = 1
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * bssid = 00:00:00:00:00:00
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: searching for networks...
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: 1) 02:13:d4:ff:c1:eb ('Wireless') cap 411 hw 3 ch 1
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: trying to associate
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: IOPCCard debug: HW CONFIG: channel=1 freq=2412 phymode=3
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: Sending RXON
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * channel = 1
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * bssid = 02:13:d4:ff:c1:eb
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: Sending RXON
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * channel = 1
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * bssid = 02:13:d4:ff:c1:eb
Apr 8 13:05:25 kirill-s-marinins-macpro31 kernel[0]: darwin_iwi3945::enable()
Apr 8 13:05:25 kirill-s-marinins-macpro31 kernel[0]: ifconfig going up
Apr 8 13:05:25 kirill-s-marinins-macpro31 kernel[0]: IOPCCard debug: en1: dropped data frame to not associated station
Apr 8 13:05:25 kirill-s-marinins-macpro31 kernel[0]: TXRX_DROP fail
Apr 8 13:05:27 kirill-s-marinins-macpro31 kernel[0]: bss_add= 02:13:d4:ff:c1:eb ('')
Apr 8 13:05:27 kirill-s-marinins-macpro31 kernel[0]: q6
Apr 8 13:05:29: --- last message repeated 7 times ---
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: IOPCCard debug: HW CONFIG: channel=1 freq=2412 phymode=3
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: Sending RXON
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * channel = 1
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * bssid = 00:00:00:00:00:00
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: Sending RXON
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * channel = 1
Apr 8 13:05:29 kirill-s-marinins-macpro31 kernel[0]: * bssid = 00:00:00:00:00:00
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: searching for networks...
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: 1) 02:13:d4:ff:c1:eb ('Wireless') cap 411 hw 3 ch 1
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: trying to associate
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: IOPCCard debug: HW CONFIG: channel=1 freq=2412 phymode=3
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: Sending RXON
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * channel = 1
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * bssid = 02:13:d4:ff:c1:eb
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: Sending RXON
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * without RXON_FILTER_ASSOC_MSK
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * channel = 1
Apr 8 13:05:31 kirill-s-marinins-macpro31 kernel[0]: * bssid = 02:13:d4:ff:c1:eb
3)
Apr 8 14:01:11 bb-92-43-6-146 kernel[0]: IOPCCard debug: en1: associcated
Apr 8 14:01:11 bb-92-43-6-146 kernel[0]: IOPCCard debug: en1: No STA entry for own AP 00:00:00:00:00:00
Apr 8 14:01:12 bb-92-43-6-146 kernel[0]: IOPCCard debug: en1: dropped data frame to not associated station
Apr 8 14:01:12 bb-92-43-6-146 kernel[0]: TXRX_DROP fail
QUOTE (Gipnotizer @ Apr 8 2009, 11:11 AM)
Hello.
I instal iwi3945.kext. I see the wireless network, but i can't connect.
See my system log fnd help me pleas.
My system log iwi3945
I instal iwi3945.kext. I see the wireless network, but i can't connect.
See my system log fnd help me pleas.
My system log iwi3945
U're lucky you don't get a panic when you install it. You can forget about connecting to a network, it only connects to unprotected networks (without https login!) and almost nobody will have their network configured that way.
Get a wireless usb or change ur intel.
iwi3945 rel 1214
add tx authentication packed (code from aircrack-ng)
to test:
the driver tries to authenticate to the 1st open network available
if this fails you'll get a kernel panic - shutdown and try again
i can't test this code because i need to ask for a friend laptop...
thanks for helping
add tx authentication packed (code from aircrack-ng)
to test:
the driver tries to authenticate to the 1st open network available
if this fails you'll get a kernel panic - shutdown and try again
i can't test this code because i need to ask for a friend laptop...
thanks for helping
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.