Hi jalavoui,

I looked on the tutorial here: http://forum.insanelymac.com/index.php?sho...rt=#entry925693
However when i'm trying to compile the kext it says that it depends on itself and xcode stops compile.
The svn sources were donwloaded as explected , xcode is installed corectly . One difference . When i open the project i don't have to build button up ( i had to add it from customize toolbar )
And the OS version differs ( i think from what you used ).

I will have another look at it today and i will post some screenshots. Maybe will help .

Some of you may or may not love me very soon I'am trying to pick up where the other guy left off on the 3945 driver, just read the whole driver tutorial on apple's site. good new is its partially working I can pick up my bssid see the screenshot below. I'm going to work on it this weekend expect to hear something good or bad by then end of this weekend.

http://screencast.com/t/NCDMGDlFvR

This is very good news



If you are talking about the Voodoo team, then no, that would be wrong. They are starting on the 2200bg, then 3945.

Great!

But regarding your screenshot: the bssid was always recognized in the current svn afaik, while the stabssid has been all zeros. Check for example this bug report http://code.google.com/p/iwidarwin/issues/detail?id=81 from September.

Could you provide the link for the tutorial, I am also reading the code.

I can build it, and start testing around. But without document it's like hitting a snake in the dark, the system log is quite messy.

Some helpful webpages for those just starting out messing with the driver:

http://developer.apple.com/documentation/D..._section_1.html

http://episteme.arstechnica.com/6/ubb.x?a=...mp;m=7480952764

https://daw.apple.com/cgi-bin/WebObjects/DS...eIntel8255x-19/ (sample ethernet driver, needs ADC account)

http://developer.apple.com/documentation/D..._section_1.html

That should be enough documentation to get anyone started.

Yea your right, but I dont understand why they start with 2200bg , from iwidarwin website it say driver is stable for 10.4 and 10.5 , no ?

Because I don't have a 3945. Anyone want to send me one is welcome to do so. Otherwise I don't want to code it blind right now, though after 2200 is done I will probably have to do exactly that...

And because it has NOTHING to do with iwidarwin. That project is officially dead and the code base is unmaintainable. IF the 2200bg driver were "stable" I would never pick up this project in the first place, much less start from scratch.

In other news, after 3 days of full time hacking I have the adapter reset working. Next up: set up firmware and rx/tx queues.

I suggest to close this thread and to open a new one about the new driver.
I also suggest javaloui to give back the money we donated... as i said before it's a shame. at first he asked money for the wi-fi card, then when he had enough money, he asked for a brand new notebook.

thanx mercurysquad.

Just to be clear about it: There is no new driver yet! No promises until it's made. No donations now! People should read this thread for more background.

And re: jalavoui and donations - everyone should realize that donations are not purchase transactions. If you 'donated' but didn't receive any working driver, there is no legal obligation on the person to return the money, specially when he can argue that the donations went into paying for his time and you get the source code in return. There is a moral obligation, maybe. But we cannot decide for him. I can decide about myself, and I am NOT accepting any contribution until the thing actually works.

donations are not payment, you are right.. and we all know that. but if someone is asking for donations to go ahead with the work is supposed to work on that and not keep asking for money rising the target everytime one is reached.

Correct. And that is why my plan says no donations until the driver is ready. Afterwards a target amount is preset based on number of hours the programmer spent, and the driver sourcecode is put online once target is reached. Can't be more transparent than this. I am already working 8-10 hours/day on this project and have clocked around 60 hours so far. There are timesheets and SCM logs to corroborate this (trust me I've done professional work this way )

Anyway we are not at that stage to discuss this yet.

damn, you are a pro!

anyway, if you need donations or testing you can count on my support.
i am a linux admin so i have some skills.

mercurysquad,

if you need help coding, iwidarwin is still up
if you start a new project and need help discussing code i'm here to help

i haven't got he hardware for start working on 3945/4965 - hope to get it soon

do you plan to write new code from scratch?

there's some problems on porting existing code for io80211 family - is this your plan?

in my opinion the best driver to start coding is 3945/4965

2100/2200 are old drivers - can't do much about it

i'd like to ask forum administrators to remove non-development posts
this doesn't help making the drivers work

in iwidarwin svn tree there is code for ioethernet and apple80211
the idea was to make a stable ioethernet version and them port the code to apple80211 (airport version)

for developers:
intel as new firmware versions for 3945/4965. download from
http://intellinuxwireless.org/?n=Downloads
use hex2strng to convert the files and test it
build it and post new .dmg here for testing

a shortuct for making 3945/4965 is to fix the rx/tx packet code
i can't do it whitout the hardware

As mrroboto, if you need donations or testing count on my help .... there are my email in profile, or contact me via pm ..... I will be happy to help ..... and thank you again for everything that do work for the community .....
THANKS FOR ALL!!!!!!!!!!!!!

That laptop is sold also with 'dell wireless 1390/1490' cards whic are known to be airport compatible. Better verify you actually have an intel 3495.. e.g. with ioreg or lspci, check the vendor and device IDs. Intel cards have VID 8086. An airport compatible driver is NOT available for intel 3495, and kext hacking is going to get no one nowhere. (this is not applehda)

Cool, thanks I will contact you if I get stuck at any point.

Me neither. I have 2200bg, so started from that. Once it's working I'll have the required knowledge to get 3945/4965 working, as it doesn't seem very different.

Yes. I looked at your iwidarwin source and I won't lie, it's huge and I can't fathom it. I am starting from scratch, using BSD driver for reference (but it's not a port). The linux driver and consequently iwidarwin are 18k lines, while the bsd driver is less than 4k, so it's much easier to follow.

As I said I'm not porting, but rewriting. Yeah I inherit from io80211family, not sure what problems I'll encounter later on, but that's the plan right now.

Yes but as I said I don't have the hardware and it's not a good idea to code blind something which is already difficult...

I see. But I will not take that approach because I don't want to re-implement ieee80211 stack (as you seem to have done?), it's too much work right now and I think starting from io80211 directly is possible given that the headers are available, so we have to reverse engineer some parts.

I chose v3.0 firmware for 2200, it's the newest. Don't know about 3945/4965.
Also, you can use xxd -i filename to generate the header file from a binary image. xxd is included with OS X and most unix OS's.

Cheers.

The 2200bg drivers aren't stable, that would be why he is working on them, also because that is the card he possess. And like he said he won't request donations until the final product is out. Just because you want something, doesn't mean it has to go before what other people want. You should be happy that after over a year, we have somebody who is capable and willing to create some working drivers for us. If you want wireless now, go buy a USB stick or something, don't complain, it is just going to make things harder for everyone.

Why don't you guys just stop whining? You waited a year, wait just a little bit more. There's a guy who came here with his mad coding skills willing to write the drivers from scratch for free (let's be honest - one in a hundred users who download something actually donate to developer) and you wouldn't show any sign of appreciation, just shouting and rushing him - I don't think it's gonna work. Just let him do his thing. It's better than nothing.

edit: my post is quite similar to booger_sniffer5000's one, didn't see him writing

Well said

I spent $70 on a USB Wifi stick that semi-works. It was one of the few wireless N sticks i could think of that you could buy in store (Linksys WUSB600N). I hate buying online, especially eBay. I'm not yelling nor screaming. I'm just stating the fact that when the starter of this thread said it would take 2 days to work once he got the card, we expected it to take far less than what it has taken. Again, I do apologize about misunderstanding about the stability of the card, even though on the site it does say it is stable which is very confusing. I haven't been waiting for a year, though i have been waiting over 2 months (I started looking at the OSX86 project about 2 months ago). Though I'm not looking for a 3945 card, I still feel for those who have waited over a year for the card to work and got there hopes crushed when it has taken this long and the iwidarwin site seems to be inactive. Don't get me wrong, i do appreciate mercurysquad's willingness to be a part of this though there has been almost a 2 month period of no activity. It's just a frustration from my waiting so long and it's gotta be worse for those who have been here since the start of this thread.

You could have done what I did and replaced your Intel card with a card that is known to work (like a Dell card). In any case, I'm not sure if you have looked at the iwidarwin source but it is very hard to figure out what is going on. I checked the source out a few months ago to try and take a stab at cleaning it up some but I eventually came to my own private conclusion that pretty much only jav really understands the code. If you are tired of waiting then I suggest you either go buy a real Mac or buy a card that works natively.

Lastly, in case you've been living under a rock, mercurysquad is one of the guys behind the voodoo kernel and other big developments here. If he's taking a stab at it there's a good chance something will come out of it. Continuing to make this thread longer and longer with further pointless "poor me" posts does nothing for the driver's development.

I meant mercurysquad with his/their great work on the Voodoo kernel.

I don't believe that's what he said. He said he would release the source code once it works and a certain target has been reached.
Even though it's no fun that the iwi stuff failed in a way it's no use to start yelling at someone who gives us new hope. He seems to be doing a pretty decent job so far for "only" 60 hours of work. It's no use either to have him start on a card he doesn't have yet, let him work on the other until he has a 3945/4965 gives him some time to practice with the intel wifi driver coding as well (if he needs it). If he succeeds in making a stable 2200 driver i don't think a stabl 3945/4965 is very far away.

Stop it ...

Mercury decided to work first on 2200bg, and his work is to prepare the 3945 devellopement, its not optionnal, this is the way he chose to work.

any news here ?

If you have the 3954ABG card read this

I spent some time this weekend going through the driver listed on the first page for the 3945 card it appears to be partially working, but still need a good amount of work. So I'am going to give you the best advice go buy an atheros card anything but the 5008 from what I've read should easily work. Unless you are a software developer with many free hours on you hands which I doubt any software developer has much free time I know I don't. Its not worth the time you can easily pick up an atheros car for around $40us shipped. The driver that exists can be finished by its original creator be cause he understands the conventions used and its structure.

First of all mercurysquad owe you (and us all) nothing. He can write code for whatever the heck he want, I'm also want driver for my 4965 card first but that's not my choose it's has own choose to start coding for whatever he want

If you don't like it go and code your own driver...

im in the same position and i agree with you 100 %

Well put, thank you

Hey guys, thanks for the hearty laugh I got this morning reading through the replies. It's ridiculous what sense of entitlement some people have. People even suggested I go out and buy a 3945 card to code drivers for you.. when you won't buy an apple-supported card for your own use. Heh.

Anyway, let the whininess competition continue! Lurkers rate each post 'whiny' or 'not whiny'. Good way to pass time while we're waiting.

Cheers.

Well I am glad that you had good humor about what people said.

I did read it. And that's very interesting, not more. It is a strange situation that you only and no other (so far) have experienced, so we can't start a "ghost chase" for the "misterious lost combination". When you come with something more tangible then the experts can try to study why does it work; until then it is like I say that I saw a flying pig and request others to start chasing it...

Are you sure you could connect to networks? Because It's not a big deal that the card is visible and detected as Airport, but you can't really do anything about it.

Or just install xcode, open the project file in the source, hit Command-B, load the kext...

Plus why would mercurysquad not give out a compiled version of the kext? I mean, I could compile the source and post the compiled kext for people. So either he gives out the kext and doesn't give out the source until he gets enough donations (which is what I believe the plan is) or he gives out the source and makes everyone compile it (which is pointless for the reason I just mentioned).

Its DEF. a Intel PRO wireless 3945ABG card. Just checked device manager in XP to be sure.

Not possible, no drivers have ever been written for these cards, let alone any wireless anything with an Intel chipset.

Its DEF. a Intel PRO wireless 3945ABG card. Just checked device manager in XP to be sure.

Sorry guys, I just realized I was refreshing the page to update my view of this post and it was resubmitting my last post!

As far as the comments doubting I had it working, I would give you more details but this is a side project for fun and not priority one. When I get a moment I will try and submit a full detail of what I did to get it working.

I can tell you right now it WAS a 3945abg, I used a Kalyway 10.5.2 disc, I had both XP and OSX partitions, Dell XPSm1210, I could connect to Secured wireless networks using keys, I could browse available wireless networks, use the internet like an MADE FOR OSX wireless card.

I didnt have sound working (I hadnt done my research on what updated drivers to install, I was testing what OSX86 Natively got me the most compatibility)... and I was doing all of this without reading sites and forums. Basically it was a blind test. If I had read about the card not working, and the Kext updates for sound and graphics, I would have just left that original installation and fixed the other elements.

IT did work BUT perhaps trying to nail down how exactly it worked that time may be "a flying pig". It doesnt hurt to let people know that it did work on my machine on the 1st try.

K

PS: Kudos to whoever gets it working, and thanks for spending your valuable time creating solutions for those who dont have the time and/or skills.

Dude, I dont believe you, many people try to fool people in this thread, so you reinstall the kalyway 10.5.2 on your own and prove us that it work, or we will just ignore you.

Exactly, there would be no point in only releasing the source code of the kext to try and solicit money; it's too easy to compile it, and I mean it's EXTREMELY easy, you need no knowledge of programming whatsoever. Trust me, if you end up needing to compile it, it's not a big deal. I compile code everyday; it takes little to no time.

Im not here to convince you or anyone anything. I thought if someone else had a similar experience or some insight it would expose a potential solution... Ive tried installing Kalyway once again but Im not sure what kexts I selected during that 1st install, like i said I just basically clicked through to see what would happen.

Anyhoo.... when I get a chance ill try reinstalling KALYWAY 10.5.2 again with a few different options. One thing I remember is that without explanation during some of my OSX86 installs, it takes HOURS AND HOURS...other times it only takes 30-40 mins. Really strange and also why im hesitant to install Kalyway 10 times trying to recreate something...

K

DAMN RIGHT Mercury squad shouldn't have to buy the card. I actually have a huge problem with that fact, for some reason it makes me angry. Mercurysquad should literally buy NOTHING. We should be happy as hell to supply him with the card. And if you're not, then you should not be on this page. If you think you have a sense of entitlement that you should simply receive the driver after he has put in so much work, while you have simply waited, and think that they should buy everything themselves and don't deserve a thank you, then GTFO. You don't respect devlopers, you don't respect this thread, and you dont respect anyone who has every tried to code something.

Also, SO WHAT if he starts with whatever card he wants to. Screw it, I say. I say MercurySquad should just start with the most obscure card out there just to show that its their
******* show and they can do as they damn well please. He said he would get to the 3945, so just wait! If you think that your card is more important shut up, because its really not. Even if more people have it that doesn't make it more important. It just means more people want it. And then more people like some certain people in the last couple pages start ******** about the fact that they should get their driver first, and then they just look like jack*****.

And I completely agree with MercurySquad. There should be no donations untill the card is finished. You have no idea if the money is going to the devlopment, or whether or not its actually going to anything related to the code.

MercurySquad is the BEST thing to EVER happen to this squad, and if you cant appreciate that then you dont deserve to use any driver written by him.


P.S. I swear to god. The next person who posts "Is anyone working on XXXX card?" I'm going to track down and punch in the face. They obviously have not read the thread, and don't deserve to post. You could even read the first posts and see that the card isnt working!

You have a PM
I just installed a 1505 BGN card, so my 3495 pcie is up for grabs.

I just replaced my intel 3945abg with an Atheros one, which dev would like to use the hardware for driver development?

It is a mini-PCIe form factor with two connectors for antenna.

vjkevlar

I'm not the kind of guy that uses believe... I use reason!
So make several cups of coffe and start to work on what you claim!! This way you would shut up those who critesize you and help lots of others who are having that problem with Inter Wireless....

Go by attempts... you will find the correct combination of kests that make this wireless work....

One thing i now is that even on Windows this wireless cards need a Broadcom codec... so the solution must be on the right combination between Broadcom and Intel codecs... or kexts...

Less talk and more work

I'll be waiting for news from you soon



Se7eN

Sorry to burst your bubble, but this is not true at all. The Intel wireless cards use a completely different driver set than the Broadcom cards.

well... you are not sharp enough...

In Windows Vista I have installed "Broadcom 802.11 Wireless". And i've tested that if i uninstall that my wireless card stops working... No matter what Intel drivers i install... latest or the provided by HP...

I have a HP Pavilion dv6179ea...

Check this link HP Pavilion dv6179ea in HP Website and tell me why is there a "Broadcom Wireless LAN Driver for Microsoft Windows Vista"....

Who's bubble bursted now?


Se7eN

Then you obviously have a Broadcom card...

just check that link, and you will see just below the Broadcom link the Intel PRO/Wireless Drivers for Vista

now tell me: DO I HAVE 2 WIRELESS CARD ON MY LAPTOP?
Of course not!

Obviously the Intel Wireless cards have components provided by Broadcom, that's why the need some codecs...

This is my last response to this question... You should believe in whatever you want...



Se7eN

Whatever, I am just telling you that there is no combination of kexts that will make this card work. And if the Broadcom drivers make your card work, then you have a Broadcom card. Believe what you want, I don't care, but Broadcom doesn't supply chipsets for Intel's wifi cards.