actually, correct me if i'm wrong, but are you saying you need both of the drivers installed? Because if that's what you're saying that, then you should know that there's more than one wireless card option so they give you both drivers in case you have the broadcom card or if you have the intel card. I'm not sure if that's what you're saying, but that's the reason why there are two wireless card options.

Can i join your ewar ?

Hi, back from winter break. Im not gunna read through like 162 pages so i remember aguy said he would work on the 3945abg adaptor after the holidays, has he started yet?

-shahir29

no, or we dont have news about him. but theres 2 other guy the work on it , Release date : february 2010

Don't you mean 2009?

It looks like my laptop only supports MiniPCI
Although this page on Intel's site about my motherboard (Intel 915GM) seems to imply that it has a minipci-express slot, the BIOS only says "MiniPCI". It has a 2200BG card in it which is also MiniPCI.

It's a Dell Latitude D510. Pentium M 1.73 GHz (this was an upgrade), 533 MHz RAM [not 400 as stated on some spec pages] and Intel 915 motherboard (ICH6-M).

If anyone with a similar laptop has any concrete info on whether I can plug in a 3945 in this thing, it'll be much appreciated.

Well, we're screwed.

I think you guys should buy Dell 1390 b/g WLAN Mini-PCI Express Card. it only costs $15 and works out of the box.

I know, but some laptops require extensive disassembly to get to the wireless card, like mine. Therefore, making it not a possible alternative. (Although I am really considering it, I already have 2 Broadcom cards ready for a transplant )

Well if 2200 works out I can still try coding for 3495 and have some testers test it out. Will be difficult but not impossible. That's how Voodoo kernel was coded.

Lol you HAVE TO get out and buy a laptop with 3945! That's my request!

Just kidding. Of course it's not now but in the future, can you work via VNC? My LAN works well Jalavoui said that he didn't want remote desktop.

Well guys I'm out, I ended up replacing my wireless card (turns out I only had to remove the keyboard). I wish you all luck!

EDIT: BTW, I forgot to tell you, it is a Broadcom 4311 card.

That sucks, sorry about that

how hard would that be to change my 4965 out of my acer laptop ?

mercurysquad if/when you get the 2200 done I believe I can do the changes for the 4965 and if I can get ahold of a 3495 that one as well. I'm under the impression the all three cards are similar in how the drivers access the hardware.

that would be really nice of you to make the 4965

do not stop your work mercury it will help other dev later

BIG... Huuuuuge! THANKS
& Merry CliZmas huaa ha haaa

mercurysquad: Is there any place where you can follow the development? a blog or something? or is this thread the only place to find updates abaout the development?

Right now I'm only posting updates on this thread.

Progress: not much as I got busy with family stuff, only clocked ~7 hours in the past few days. New since last update: command ring setup is finished and some minor additions. Next up: rx/tx rings. I guess you can say about 25% of the work is done so far, but this is also the slowest 25%.

Is there a lot of interest in following the progress? If yes, I'll setup a quick blog.
NOTE: There IS a blog now but this forum's mods don't think the link is fit to be posted here. I'm not going to bother asking for reasons or anything so just find the blog yourself from my profile page. Bye.

Here's a changelog:

-Cleanup

Great progress!

Can't wait till a functioning driver is out for 3945ABG!!!

I am very interested in the development of these drivers, and would greatly appreciate a blog on this!

It's here http://projectcamphor.mercurysquad.com/

got a laptop to work on the drivers:

it's a hp dv6700

thanks everyone for wainting

it comes with a broadcom card

i have test it with a 3945 and 4965 card

4965 gives 104 error - no boot

3945 boots into vista but doesn't get recognized

i remember some of you having this problem with older iwi3945 driver versions

i think this is caused by the onboard bluetooth module

in teory intel wireless drivers are expected to have integradet bluetooth

i haven't install mac os x (nvidia ata problem to fix first)

some of you have patched the bios

maybe someone can help me on this - anyone?

this hp as a amd turion 64 x2

i'll try do find why the card isn't recognized (in linux, winxp, mac os)

mercurysquad,
you're doing a great job
hope others follow this example

we'll talk about the code when you finish

I think it's not because of integrated bluetooth (you sure it has that?), but because bluetooth and WiFi both operate in the 2.4 GHz range causing interference sometimes. In general it shouldn't be a problem as long as the driver enables "bluetooth co-existence" in the firmware. This is what I understood from looking at the BSD drivers..

Jalavoui you have to hack the bios. tell me if you need help on this .

I suppose he does need help, rwmanos.

And it's funny, two big developers working on the drivers jut now! After I replaced my 4965 with Broadcom 4311 card. I waited a year, where have you guys been?

Good to see someone is working on this "unsupported drivers" but is someone will working on the 4965?
If i understand good the making of driver of 4965 will take the same time as the making of 3945?

So mercurysquad do you think you will do it?

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?

Ok People..

1) Jalavoui said tha hpdv6*** bios is locked so you can't change minipci wireless adaptor.(that's why he needs a bios hack)without a bios hack intel3945 or 4965 won't work at all (either on vista,mac,linux,etc.)

2)Jalavoui don't work on the drivers yet because he don't have the ability to test them without working hardware Voodoo labs works on the driver (I think not yet on 3945 and 4965)

just read the topic. And don't ask when are they going to be released or if they work.They are not stable yet

lol he got the new computer but its not compatible with our cards lmao

it's not his fault that the guys at hp are such bastards and lock the bios to a certain card...

AMAZING!!!! How didnt we find this before? Mine works now too (unsecured only but still...)!!!!

wtf? Those drivers are those from jalavoui, didn't you know?

could some admin plz lock this topic until jalavoui has any news?

yes but they didnt work.It needed the procedure mentioned above by JesterDev.

learn to read...

Well maybe it's time to lock this thread yet again, but as Jalavoui appears to be active again we'll leave it open for now. Please keep this topic for discussion of development of the iwidarwin driver and nothing else. Hijacking the topic with other projects only serves to increase confusion.

tried the iwidarwin again with iDeneb and 4965 to no avail. Other user reported trouble too.

already patched my dv6700 bios
the whitelist is in the attached file

the whitelist trick (f9 eb -» f8 eb) doesn't work
i don't find any reference in the list for 8680 devices BUT i can attach a 3945 card and start the pc without the 104 error - after that the card fails to get detected

really need help on this one...

jalavoui have you seen this link: http://forum.insanelymac.com/index.php?showtopic=120190 I am assuming so since you mentioned the whitelist trick.

So at the moment the 3945ABG only works with unsecured networks??

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!

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

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...

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.

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.

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.

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.



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

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.

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¢.