Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About w3c.org

  • Rank
    InsanelyMac Protégé
  1. Sorry, that's the dumbest thing I've heard. You're using a hacked OSX, with a still under development driver, and you're doing a software update, just like that! Well, NO, you should have waited a little before updating, at least a few days or one or two weeks, so that people with a little more knowledge (say, those who develop the driver) would have tried with the update. So for now, you're stuck, and that's all.
  2. Hi aztec_knight Everything you're asking, as a detailed guide get the wifi working on your computer and everything, is explained through the nine pages of this topic. Please read them carefully, we can't be more helpful than to tell you to read them. About the Aspire One, I think there is also a huge lot of other topics on other forum which could tell you how to do it. Just hit google.
  3. The only problem I see is if the application you download & install doesn't have the required libraries to run on Leopard... But it'll be indicated on the website or wherever you're getting the application. If the application is made to run on panther or tiger specifically, then it won't even launch in Leopard, throwing an error message. So, no, it won't affect the system itself.
  4. myi4u > No I don't use Shade, and I've got no problem installing new programs. In fact I never did a 'repair disk permissions', as everything is working great now. Sometimes I've got to reboot once before getting the wifi to work, but it's ok.
  5. jinnggoff > I think your method works with your laptop, maybe not for every laptop. On my Acer 2920z, everything is working fine, I've just followed the first post of the topic and done a little testing. FYI, I'm running iATKOS v4i with a Vanilla kernel 9.5.0, and I haven't done the DSDT thing. RT91 > to remove every installed thing, just delete the IO80211Family.kext. And may I remind you that you're hacking to install OSX on a non-Apple machine, so don't expect everything to be doable easily! Learn Terminal.app, it's a powerful macintosh application. If you don't want to have to deal with the repair commands, google 'kexthelper'. induscreep > I haven't tried iATKOS v5, nor iDeneb so I can't really help you about that. May I repeat that you don't have to install again the Airport Extreme Update on every reboot? Just delete the .mkext and reboot again before starting Kismac.
  6. joerg84 > once you have the .kext installed, you don't have to reinstall it again. As explained earlier, all you have to do is delete /System/Library/Extensions.mkext and reboot.
  7. Yeah I've got this problem too, it takes me nearly every time two reboots to get the wifi working. About the .mkext, no you can't delete it completely! OSX uses it as a library to know which extensions are loaded at any time, but also to reduce boot time (I'm speaking of legal Apple computers), it's a feature. About KisMAC, well I don't have the slightest idea. In fact I don't even know if it's important, I only launched the application once, on the first install of the .kext, and then it was ok.
  8. Comaco > I don't have a NC10, so I can't really help you... Mine (an Acer 2920z) had the ethernet controller detected since the installation (as en0), so I just had to put the good drivers in and it was ok. Then with the new kext for wireless, airport was detected as en1, so everything was ok.
  9. I'm just trying to share an ethernet connection from the hackintosh computer to another computer, via wifi. It works well on OSX, but not on the hackintosh unfortunately, due to the driver. I've tried different channels, everything, but so far it only works every ten reboots or so, which is quite unusable. So far nothing was proven efficient (removing the mkext, repairing the kext, etc.), but I'm always trying. Well just found out what the problem was... It's *really* weird, but anyway. So, in order to have a working internet connection sharing, you have to let the Airport TCP/IP thingy in automatic (DHCP), then activate the connection sharing. You can verify with the other computer that the hackintosh is effectively broadcasting the wifi network ESSID. Then, and that's the weird thing, you have to manually give an Airport IP to the server and to the client; DHCP seems not to be working at all. I suggest, as OSX 10.4 does, giving the ip to the server, Subnet mask, and router Then on the client, do the same but replace by or what you want. As the Airport IP will stay the same over a reboot, you'll have to configure it again as Automatic before re-activating internet connection sharing.
  10. OK, I don't know if some of you have tried that, but anyway. Sometimes when I boot, everything works fine, I can create an ad-hoc network, connect to it and everything, BUT internet connection sharing doesn't work, which seems a bit strange. Does someone have an idea about that?
  11. First, are you sure you need to edit this? If you already have an ethernet card recognized by OSX, it's ok (because ethernet will be en0, and wifi en1) Else, fire up Terminal.app and type then replace by and by Hit ctrl+x, nano will ask you to save the file, answer Yes, and you're done.
  12. To Comaco, no, there isn't more than one Extensions.mkext. There could be an Extensions.mkext.something, but just do a rm -r /System/Library/Extensions.* and that will be ok. Yes, it is still the same .kext we're all using, and to repair it, do as you want, by kexthelper, by OSX86Tools or by hand. To TI3GIB, you can choose between the same three things: using kexthelper, using OSX86Tools, or by hand. The commands, by hand, are, in a normal user Terminal.app window: Don't forget to delete the Extensions.mkext*, and you'll be done.
  13. Exactly what I thought yesterday Good luck experimenting, but now you've seen it working, that should be ok
  14. That's interesting, but I think it'll work better as a shutdown script (remove the Extension.mkext upon shutdown). By the way, you don't have to repair again the IO80211Family.kext (at least on my computer I don't have to). Take a look here for a way to implement a shutdown script: http://forums.macosxhints.com/archive/index.php/t-3972.html The script would look like (quoting the post on macosxhints): #!/bin/sh . /etc/rc.common StartService () { } StopService () { rm -R /System/Library/Extensions.mkext* } RunService "$1" This file has to be executable, i.e. chmod a+x filename. Then create a file by the name StartupParameters.plist with the following contents: { Description = "Name of your service goes here"; Provides = "Whatever your service provides goes here"; Uses = "Disks"; } But I haven't tested, so try it at your own risk! Edit: I also found this post http://egopoly.com/2008/03/26/add-your-own...pt-to-mac-os-x/ which should give you interesting examples. Edit2: I put a * after the Extensions.mkext because sometimes osx create a temporary library of loaded extensions, named Extensions.mkext.XXXX (with four letters), so the * tells the script to delete both if they are present.
  15. Hi It's working for me on the first recognition of the IO80211Family.kext, but as soon as I reboot or shutdown the computer, I can't connect to a wifi network nor create one that could be recognized by another computer. By deleting not the extension but the extension library (/System/Library/Extensions.mkext, note the 'm' before kext ) I force OSX to reload the IO80211Family.kext on reboot, and it works. To miy4u: i always repair extensions by hand (sudo chown -R root:wheel extension.kext && sudo chmod -R 755 extension.kext) and then delete the Extensions.mkext as explained earlier