[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Some 2.6.6 kernel questions



On Tue, 2004-07-13 at 07:15, Sven Luther wrote:
> On Mon, Jul 12, 2004 at 10:29:25PM -0400, Albert Cahalan wrote:

> > Just yesterday I grabbed a plain 2.6.8-rc1 kernel
> > from www.kernel.org/pub/linux/ and it works great
> > on my Mac Cube. Perhaps you should try that.
> 
> And what about kernel-image-2.6.7-powerpc ? Does it work fine also ? And
> if not did you fill a bug report. If yes, what motivated you to build
> your own kernel over using the debian provided one ?

I never trust distribution-provided kernels. They are
often full of questionable patches, obsolete, and way
too generic for my taste. They might not even use the
larger 12x22 console font.

The 2.6.7 kernel is certainly obsolete now that
2.6.8-rc1 is out. :-)  I'm only half kidding; the
newer kernel has lots of nice fixes and isn't
generating lots of bug reports.

I built a kernel that supports my hardware and little
else, without modules. The hardest part is identifying
weird Mac hardware. For example, I might not need any
of these for my Mac Cube:

CONFIG_ADB_PMU            Support for PMU  based PowerMacs
CONFIG_PMAC_PBOOK         Power management support for PowerBooks
CONFIG_PMAC_BACKLIGHT     Backlight control for LCD screens
CONFIG_SND_SEQ_DUMMY      Sequencer dummy client
CONFIG_USB_HIDDEV         /dev/hiddev raw HID device support
CONFIG_BLK_DEV_IDEDMA_PCI Generic PCI bus-master DMA support
CONFIG_LLC2               ANSI/IEEE 802.2 LLC type 2 Support
CONFIG_SERIO              Serial i/o support

(tell me if you know)

I also don't know if I2C would be useful to me. I enabled
just enough to see that I have 2 buses.

I know exactly where my kernel is, and exactly where it
came from:

make menuconfig
make vmlinux
mv System.map-2.6.8-rc1 /boot
mv vmlinux-2.6.8-rc1 /boot
cp config-2.6.8-rc1 /boot
joe /etc/yaboot.conf
ybin

See also "make oldconfig" if you have an old kernel config
you'd like to use. I did that before "make menuconfig" because
I had an old config file that I could copy to .config to get
me started.




Reply to: