Jump to content
InsanelyMac Forum


  • Content count

  • Joined

  • Last visited

About aroman

  • Rank
    InsanelyMac Protégé
  1. Intel PRO/Wireless 2200 driver

    Well, the other guy has been making good progress. I, sadly, have been overwhelmed with school work even after midterms I still want to work on this, but I just don't have the time right now So, if he gets it done, all good for the project! If not, then when I have time, I will work on it. I have a x86 laptop and I want my wireless card to work, so the motivation is there Again, sorry I haven't been too active lately, but university is really a lot of work
  2. Intel PRO/Wireless 2200 driver

    OK my exams are over, and I think I did pretty well, so I'm happy Meanwhile because I needed a windows program (and my only windows machine was my laptop) I installed xp on my laptop and accidentally wiped os x. whoops! But I have all my source code in the CVS so it's all good. I will just have to re-install OS X. Will do that this weekend. Another guy is working on this driver sorta by himself... Just letting you know. But I'll continue to work on this, no worries. That being said, relax I haven't abandoned the project. Cheers, Alex.
  3. Intel PRO/Wireless 2200 driver

    LOL moseschrist... I don't want power A black macbook would be nice though jks [EDIT] Unfortunately I'll have some exams starting soon throughout june, so I might be a bit inactive in development and posts... But don't worry, I've not abandoned the project. I just need some time to study for these exams... [/EDIT]
  4. Intel PRO/Wireless 2200 driver

    It should work... The driver is the same in Linux/*BSD/etc. so it should work if I follow the linux driver correctly!
  5. Intel PRO/Wireless 2200 driver

    Well, now I need to implement firmware and microcode loading. After that, I'll have to implement a bunch of methods relating to wireless. Then, it's packet flows. And only then there may be real testing (I may release something which just shows the interface as an Airport...). If you really think you need to know exactly what's going on, you can follow the blog I set up at http://osx-ipw2200.blogspot.com/. Cheers, Alex.
  6. You are correct. The discussion has been sorta moved over there. You can also follow the development blog I've set up at http://osx-ipw2200.blogspot.com/ Cheers, Alex.
  7. Intel PRO/Wireless 2200 driver

    Because I do not have such a card, I cannot work on a driver for it. However, once I release any sources (and I will release sources, maybe set up a repository sometime soon), other developers which do have this card can follow the driver's model and see how they can adapt it to the 3945.
  8. Intel PRO/Wireless 2200 driver

    Thank you all for the replies. I'll try to answer some questions... I tried getting in touch with tuxx. I messaged him saying I'd like to help, but his reply was "die". Simply that. I don't know why, but since he hasn't posted any updates about what he's been doing and because I have a little spare time, I've decided to work on this myself. About the interfaces... In the latest version of Xcode came a Kernel.Framework which contains an apple80211 directory with headers for an IO80211Interface and IO80211Controller They subclass IOEthernetInterface and IOEthernetController, respectively. So far 1 person has contacted me to help me, and I've filled him in on the situation and we're working on it. Any more help would be welcome: please PM me. The current step is to get the latest firmware code loaded. Yes, I'm using the ipw2200 drivers as a reference. They have a lot of comments which is always helpful. Cheers Alex.
  9. Intel PRO/Wireless 2200 driver

    Thanks for the replies guys! I've gotten it to work, though. What I forgot to do was have a getHardwareAddress(). However, after I added a dummy one, the system preferences see it as an "airport" card, though it doesn't do anything yet! Next, I'll be working on firmware loading, getting it to work basically Please PM me if you wish to help code on this thing. Testing WILL come on later, though! When I'll need testing, I'll say so. Until then, keep watching this topic and http://osx-ipw2200.blogspot.com/ for updates! Alex.
  10. Hello all, I'm working on a driver for the Intel PRO/Wireless 2200 controller. I've run into a problem. I'm trying to call attachInterface() to create a network interface, but that is failing (returns false). Is there any way to get more detailed information? ie. something like a getLastError()? If anyone wishes to help CODING (not testing) he/she would be welcome. Thanks, Alex.
  11. With a little help from Joey on IRC, we determined that the KEXT loads on 10.4.6, but not 10.4.5. So I assume the Kernel.Framework comes with headers for 10.4.6. This is good news, since now I know that the KEXT I build actually loads and the dependencies are satisfied. This weekend I plan on upgrading to 10.4.6 on my laptop and continue development. Like I said previously, if you wish to help, contact me. I know I will have some difficulties with setting up the Rx and Tx queues, so if anyone with Darwin/OS X network driver experience feels like helping, he/she is more than welcome! Cheers.
  12. OK, with the latest version of XCode, I got a Kernel.Framework which contains a 802.11 IOKit family. I'm attempting to build a driver (based on tuxx's), however I am running into a small (?) problem. I load my kext, but it complains: 15AirPort_IPW2200 is not compatible with its superclass, 17IO80211Controller superclass changed? kextload: a link/load error occured for kernel extension IPW2200.kext kextload: clearing all version/dependency relationships among kernel extensions load failed for extension IPW2200.kext Now, I'd like to ask other people with more Darwin/OS X driver development experience than me... What does this message exactly mean? From what I can tell, the driver should be fairly straight forward. The IO80211Controller subclasses IOEthernetController and adds wireless extensions, such as getSSID, getRSSI, etc. After getting the firmware to load and setting up packet flows, the wireless extensions should be fairly easy to implement. Also, the IO80211 header files seem to be missing some comments (a couple of ??? here and there), so I hope that Apple will release updated headers with more comments with the framework bundled in the next version of XCode. In another note, I got a reply from tuxx (I asked him if I could be of any help in developing these drivers). His reply was simply "die...". I don't know what his reasons were, and I'm not going to start criticizing him, however, I have one piece of advice for him: You said you want help with this, yet when help comes your way, you reject it. Fair enough, however I still want to work on these drivers, for they affect me directly. So, whoever wants to help me and organize some development, please PM me. That is all for now. Sorry if the post seems a bit disorganized, I was a bit in a hurry. Cheers, Alex.
  13. People, As tuxx reported, that driver does nothing but load firmware and ucode onto the 2200bg chipset. It won't work yet as a "real" wireless card. It won't work as a network card whatsoever (except it is reported by ifconfig and the mac address is recognized ). I know C/C++, so I want to start working on this. I got the 802.11, 802.11b and 802.11g standards specifications from IEEE (they provide them for free). I am currently looking at the OpenSolaris implementation (I find it has a bit more comments in sensible areas of the code) and with the specs I think I should be able to make sense of what is involved in creating a wireless driver for that card. I've contacted tuxx telling him about my willingness to help, and I'm waiting on a reply from him. Meanwhile, if you're not a programmer, or you're not willing to help coding, there's unfortunately not much you can do When a major breakthrough is made, you'll hear about it! Of course, if you want to help coding, I think you should contact tuxx. Cheers Alex.
  14. Windows is a piece of shit

    I must agree with that... And, no, it didn't take me this long to realize that about windows, I've been a regular linux user for the past 3-4 years....