Home > News > Ubuntu on a Macbook

Ubuntu on a Macbook

I am now the owner of an Apple Macbook and I have spent the course of the day getting Ubuntu installed on it (under Bootcamp).  I will have some tutorials ready by the weekend for any of you that have wanted to try or are tempted to get a Macbook.  So far I am still having trouble with one thing though, and if any of you current owners can offer me some tips I sure would appreciate it.

My problem so far is that wireless doesn’t work for me.  I have tried three sources for a driver over ndiswrapper and none of them seem to work yet.  Two of them will show driver present, hardware present and one of them gives me the best result with a kernel panic (yes, that is sarcasm).

Has anyone been able to get wireless working on a macbook, core 2 duo with the 168c:0024 PCI-ID?

Other than that things are coming along well.  Again, look for a tutorial on getting Ubuntu Feisty running on a MacBook via bootcamp within a few days… assuming I can get this wireless going.

If this article has been helpful, please consider linking to it.

Categories: News Tags:

Related Posts

  1. Abbas Khan
    March 15th, 2007 at 17:51 | #1

    Good Luck, if you get it working, e-mail me the instructions, i haven’t been able to get my newly purchased black macbook (core2duo) working with wifi in either feisty or edgy. Some users report that a d-link driver is working, but it didn’t work for me.

  2. Ord
    March 15th, 2007 at 19:43 | #2

    Why would you buy a Macbook and try and run Linux on it when you know it’s not supported by that operating system?

    Ahah, you’re running Ubuntu under bootcamp, clear evidence of a shy switcher.

    I went the other way. Welcome to the world of a leased operating system with an iron-fisted EULA.

  3. March 15th, 2007 at 19:52 | #3

    i’d be interested in hearing if you have any success.
    I’ve used ubuntu on my macbook but also found that wireless wasn’t supported, so gave up pretty quickly.

  4. kyle
    March 15th, 2007 at 20:47 | #4

    wireless you can use a usb dongle, or ndiswrapper. there should be forums posting pointing you at the driver to use. worth mentioning that if you install the 802.11n upgrade in os x, that some people claim ndiswrapper fails. ymmv, guarantee void in tennessee, etc.

  5. March 15th, 2007 at 22:13 | #5

    I have a first gen Macbook under Feisty, and wireless works perfectly for me. I don’t remember what I did, though :) . Apparently, I’m running a restricted Atheros driver. Also, I remember that Network Manager was smarter about utilizing (or configuring) my wireless.

  6. March 15th, 2007 at 22:45 | #6

    Maybe you can see information about Macbook on Gentoo Wiki.

  7. Stephan Michels
    March 16th, 2007 at 00:05 | #7
  8. March 16th, 2007 at 00:45 | #8

    I got a 2.Gen MacBook as well and i share your experience. There is a corresponding ticket in launchpad: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/83224

  9. March 16th, 2007 at 02:29 | #9

    I’m on Fedora Core 6, with a Intel Mac Mini. As I understand it my 168c:001c is fairly close to what you have. The core issue is that windows NDIS drivers tend to use a lot of stack. By default FC6 has 4K stacks enabled in the kernel, I don’t know about Ubuntu. But even without 4K stacks, the default 8K stacks often aren’t sufficient, and the driver will die. There are patches available that will give a 16K stack.

  10. March 16th, 2007 at 03:13 | #10

    There is a good tutorial on running Ubuntu on MacBook on Ubuntu Wiki.

    Also, try http://www.ubuntuforums.org for the best advice in the Net!

  11. Movi
    March 16th, 2007 at 06:12 | #11

    The Wifi works well in my gen2 MacBook. Im runnin feisty and there’s a catch. The version on ndiswrapper in feisty is outdated – THAT’S why the windows drivers dont work. You need version 1.38 – which means manualling getting them from the site and compiling them. Except that, everything works out-of-the box (or almost like the iSight or microphone or the touchpad)

  12. Colin Watson
    March 16th, 2007 at 07:08 | #12

    No information about wireless, but if you find installer glitches, let me know; current builds of Feisty are intended to install cleanly on Intel Macs.

  13. oskarloko
    March 16th, 2007 at 08:05 | #13

    C2D MacBooks – I’ve a white one – use a new atheros chip. Kernel doesn’t support it yet, so you’ll need

    ndiswrapper
    ndsiwrapper utils 1.8

    DLINK driver 1.01

    http://www.ubuntuforums.org/showthread.php?t=385217

    https://help.ubuntu.com/community/MacBook

    Tell us on forums !!

  14. March 16th, 2007 at 11:58 | #14

    I’ve got a MacBook gen 1 and the wireless works fine BUT it is a different wireless card than the gen 2. A friend has the gen 2 and he has not been able to get it working unfortunately.

    Also, just yesterday I tried to resize the Mac OS X partition with gparted after I’ve had Linux and Mac OS X playing nicely. It worked except I cannot boot Linux anymore (Mac OS X still works). Gparted now complains that the OS X partition’s magic journaling number is wrong or something like that. Any tips?

  15. Stoffe
    March 16th, 2007 at 15:32 | #15

    Joiiin the daaaark siiiiideee…. we have DRM, vendor lock-in, closed source and high prices. But we have oh so shiny buttons.

    – Darth Jobs

  16. March 19th, 2007 at 04:47 | #16

    Why under Bootcamp? EFI should be supported in Ubuntu for a year: http://times.usefulinc.com/2006/03/09-macbook

  17. April 22nd, 2007 at 11:02 | #17

    Wireless works perfectly on my MacBook now, here’s how:

    go to
    http://snapshots.madwifi.org/madwifi-hal-0.9.30.10/

    make
    make install
    (answer ‘r’)

    reboot and configure wireless

  18. Lexion
    October 2nd, 2007 at 04:20 | #18

    try this. It got ndiswrapper working for me.
    btw if it doesn’t work check the ndiswrapper FAQ under ‘essid’

    http://ubuntu-tutorials.com/2007/03/18/how-to-configure-wireless-on-a-macbook-using-ndiswrapper/

  19. October 16th, 2009 at 06:59 | #19

    Well,I am really sorry to know that you could not work with it properly.I believe using the proper operating system would have solved the problem much more effectively.

  1. No trackbacks yet.