From: mike d. <fl...@po...> - 2008-07-31 22:51:05
|
Justin Mattock said: > Depending on the O.S. version you have, some don't have the kernel > tree in them(only initrd.img). look in /usr/src/ if nothing then, I > would suggest > compiling you're own fresh vanilla kernel. Yes, that's what I've always done, in order to include the mactel patchset. > (this is what I usually do<below>) > make > make modules > make modules_install > make install Since I use Debian, I prefer to make a .deb using 'kernel-package': cd /usr/src/linux/ make-kpkg --revision=$(date +'%Y%m%d') \ --rootcmd fakeroot --initrd kernel_image > if you've already compiled you own kernel then ignore the above: > the MMCONFIG option like I said up top, is in the main menu of > make menuconfig. I think it says "PCI options" or soemthing like that. Right. In "Bus Options (PCI etc.)", there's "Support mmconfig PCI config space access" (CONFIG_PCI_MMCONFIG) indeed. I always had it activated, as far as I know, but it doesn't do the trick. The LKML thread seemed to point out the issue could be firmware-related. Any more information on that? Any other mac users out there facing such problems? Has anyone successfully booted a 2.6.26 and/or 2.6.27 kernel on a MacBook2,1? Cheers, -- mike dentifrice <fl...@po...> |