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

[ckybam69]

finally installed mac os x
the computer as a switch for turning bluetooth AND wireless card on/off
tested both ways with 3945 card and it doesn't get detect

if anyone can help on patching the bios - here's the link
http://h10025.www1.hp.com/ewfrf/wc/softwar...product=3667489

this is a hp dv6730ep with a amd turion

the bios defaults to allow 3945 and broadcom cards
3945 also doesn't work on vista
i'll test this in xp and linux

if anyone as a dv67000 - please post other drivers links. i'm looking for video,sound,etc

after some reading i found out hp6700 support 3 cards: broadcom, intel and atheros
looks like intel cards only work in intel processor
i have a amd processor...
can someone confirm that intel 3945/4965 works with a amd processor?

i have a hp dv5t and came with intel 5100. after doing much research i found that with hp laptops/desktops the bios whitelists certain cards, which u already know. u can hack the bios to allow any card but if u have amd the intel wireless wont work with hp. i believe this cuz i have an intel core2 and my atheros card wouldnt work for me so i had to get a broadcom card and i think it is vice versa. maybe u can get it to work but i couldnt. good luck!

[mac_cute]

@All
The driver is under development.So please,stay on topic.Any further question/comment must be related with the project.
-Thanks

[jalavoui]

can someone check if iwi3945 is working on 10.5.5?
maybe it's a fake post (read back some pages)
i'd like to see the system.log if that's true

good to have admins/moderators following this thread
feel free to delete non-development posts

ckybam69,
i'll check if i can make intel cards work on my amd
i must find a way to make this cards work...

[leo71]

Hi

If it could be useful.
I installed the iwi3945.kext. It is recognized as ethernet. With network selector I can scan the networks but i cannot connect to anyone of them.





Laptop Toshiba Satellite A100-833 15" with Intel 945PM Express chipset, Core Duo T5200 & 120 GB ATA HD Ideneb 10.5.5 GUID chameleon EFI: Darwin Kernel Version 9.5.0
working: shutdown, restart, Graphics Adapter intel GMA 950 | FireWire 400, USB, DVD DL RW & TouchPad, USB 2.0 mass storage with orByte's Generic USB2.0 (EHCI) Driver | LAN Intel PRO/100 VE ,
not working: PCMCIA TIxx12 and intel 3945abg WiFi, laptop doesn't go to sleep or hibernate.

[lebidou]

Hello,

I installed the iwi3945.kext too and though it adds an Ethernet interface, it is tells me it is unwired and cannot get the Hardware Adress, I only get ff:ff:ff… Network Selector doesn't catch any network.

I attached a system.log if it can help.

Attached File(s)

 lebidou_system.log.txt ( 29.66K ) Number of downloads: 43

 

[syberkowboy]

I've tried iwi4965 with 10.5.5 with absolutely no luck. When I had a bluetooth module in it did recognize that as a network interface but not the WiFi card.

[peach-os]

I've tried iwi4965 with 10.5.5 with absolutely no luck. When I had a bluetooth module in it did recognize that as a network interface but not the WiFi card.

[JesterDev]

can someone check if iwi3945 is working on 10.5.5?
maybe it's a fake post (read back some pages)
i'd like to see the system.log if that's true

good to have admins/moderators following this thread
feel free to delete non-development posts

ckybam69,
i'll check if i can make intel cards work on my amd
i must find a way to make this cards work...

On my Dell 1720 it never gets detected by OSX, however, I am able to scan for networks with the terminal app that comes with the drivers. I can also turn the card on, but never off once it's on, and I cannot connect to any networks-unsecured or not. I never get an error, or a reason why it wont connect, just never does. Or maybe it is, but it's not tied into OSX... In anycase I am running on iAtkos 5i with a vanilla kernal. Tried on both 10.5.5 and 10.6.5. On the later there was a major crash that may or may not have been related to the driver install. At the time I was still working on getting various things working, however, the boot errors repeated something about the 3945 card in an infinate loop. I have not tried them since.

Hi

If it could be useful.
I installed the iwi3945.kext. It is recognized as ethernet. With network selector I can scan the networks but i cannot connect to anyone of them.

Same thing happens with mine. It's recognized as an ethernet card (cable unplugged).

[JesterDev]

Now that ive read about 50 or so pages and done a few hours of searching.. before asking...now that these intel devices are supported under linux distros like ubuntu for example and port them over to osx... I understand that osx is unix based and ive read that there is now kernel support in linux for these devices. could we not create a seperate wrapper such as NdisWrapper for Linux or Project Evil for FreeBSD. I do also understand that there must be some rewriting since OSX uses IOKit but googling around i see that porting is not the hardest thing around. and since its been WAY over a year writing a NEW driver wouldent attacking an enemy from more than one side make a battle easir? that being said could we not have instead of a driver, a program that could reach out to the hardware to use the device such as audieee? is having a kext the only way were going to access the hardware?
http://developer.apple.com/documentation/P...tingDrivers.pdf
and since there was some talk a while back on the same subject here i thought maybe we could recreate the porting proect again instead of working on creating a NEW driver or Kext??
http://forum.insanelymac.com/lofiversion/i....php/t1022.html

just my 2 cents feel free to delete this should it be off topic.

I've used ndiswrapper before, and while I don't know much of anything about osx development I think this approach would have been ideal in the beginning. Now, however, things are so far along I don't know if it would be worth it for all of those who have waited a year or more to get this far. Then again, it might be easier then I think. The foundation already exists, and I personally think that it's a great idea as more and more unsopperted hardware begins to appear on the market. Would certainly be easier then writing new drivers for every new card that comes out, because it's only a matter of time until the next unsopported card becomes an option when getting a new box built.

[mercurysquad]

Now that ive read about 50 or so pages and done a few hours of searching.. before asking...now that these intel devices are supported under linux distros like ubuntu for example and port them over to osx... I understand that osx is unix based and ive read that there is now kernel support in linux for these devices. could we not create a seperate wrapper such as NdisWrapper for Linux or Project Evil for FreeBSD. I do also understand that there must be some rewriting since OSX uses IOKit but googling around i see that porting is not the hardest thing around. and since its been WAY over a year writing a NEW driver wouldent attacking an enemy from more than one side make a battle easir? that being said could we not have instead of a driver, a program that could reach out to the hardware to use the device such as audieee? is having a kext the only way were going to access the hardware?
http://developer.apple.com/documentation/P...tingDrivers.pdf
and since there was some talk a while back on the same subject here i thought maybe we could recreate the porting proect again instead of working on creating a NEW driver or Kext??
http://forum.insanelymac.com/lofiversion/i....php/t1022.html

just my 2 cents feel free to delete this should it be off topic.

Not offtopic, actually those are some very good points you raised.

Porting anything from Linux is going to be a mess - I guarantee it. FreeBSD or other BSDs are what I recommend.

Now, Project Evil can actually be ported. But it is about 15-20k of C source-code dealing with the hardcore internals of the operating system, including re-implementing a big portion of the Windows kernel. By design it is always going to be a race where we are chasing. Porting it to OS X and IOKit is not going to be as trivial as you think. It'll be a huge project.

I weighed the pros and cons and decided that the easiest and fastest method was to rewrite Intel drivers. Why? Because it's 4k lines of relatively easy to understand code. Project Evil or Ndiswrapper were built to support the vaaast number of wifi adapters for which good opensource drivers didn't exist. These were mostly Broadcom cards. OS X has support for Broadcom and Atheros. Ralink has official OS X drivers. That leaves just Intel cards. So my question was - Are there many wireless chipsets other than Intel which are not supported in OS X? The answer was a no. If you add the Intel range (all of which work in about the same way), then you don't need ndiswrapper at all as we will have covered 90%+ of all laptops and a lot of desktops.

About accessing devices from userspace - no for PCI-adapters you don't have the choice as with printers, USB or scanner devices. It has got to live in the kernel.

And porting vs. rewriting -- IOKit is C++ based and all other unix systems are C based. Just because OS X is Unix doesn't mean drivers are automatically compatible or similar. The Unix-basis is mostly visible to USERSPACE apps, which can make POSIX calls. Not drivers. Each kernel has its own driver API. So porting is not really that simple, though it's not necessarily impossible either. But again when decided whether to rewrite or to port, I asked myself - What benefit will rewriting give us in terms of code manageability? And the answer was clear - if it is rewritten to take FULL advantage of C++ and IOKit architecture rather than squaring a circle, it'll benefit us in the long run when writing other similar drivers. This is also discounted doing anything to improve the massive iwidarwin project - jalavoui is the only person who has the superpower to fathom it

That's my 2¢.

[hypnotic]

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.

[sha_doh]

"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

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

[IsmailBhai]

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.

[mercurysquad]

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.

[DMJC]

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.

[mercurysquad]

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.

[Peter_Z.]

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

[realityiswhere]

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

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.

[Chris-Cross]

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.

Attached File(s)

 ioreg.txt ( 35.25K ) Number of downloads: 44
 dmesg.txt ( 4K ) Number of downloads: 40

 

[realityiswhere]

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.