On Tue, 27 Jan 2004 20:39:22 -0800 Mark Knecht <[EMAIL PROTECTED]> wrote:
> Hi, > The instructions below give no specific info on whether to to create > the linux link in /usr/src. Is this still required for 2.6 kernels? I > assume so since some folks will likely use genkernel? > > If so, does the link need a specific name? > > Again, thanks in advance. > > Cheers, > Mark > > On Tue, 2004-01-27 at 14:06, Collins Richey wrote: > > On Tue, 27 Jan 2004 12:22:23 -0800 > > Mark Knecht <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > Can someone suggest what is likely to be the best option for a user > > > who would like to try a 2.6 kernel and needs to be able to use the > > > newest versions of Alsa? > > > > Apparently, if you require a non-english keyboard, you're SOL, but otherwise 2.6 > > works great. I've been running 2.5/2.6 for 6 months on ext3 with shorewall > > firewall. No differences noted with any desktop stuff. > > > > If you're using a CD writer, you can continue to use SCSI emulation (deprecated) > > or not. cdrecord based apps works without; cdrdao probably not. > > > > 1 Get current on gentoo updates; be sure you have latest mod-utils. > > 2. emerge development-sources-2.6.2_rc2.ebuild. I'm une level behind this, but I > > doubt that it's much different. > > 3. (Optional) 'make mrproper' in the new kernel tree. > > 4. copy your old .config to the new source tree > > 5. 'make oldconfig' then 'make menuconfig'. > > 6. Check all results with a fine tooth comb. Make your alsa choices (see below). > > You must specifically turn on the following !!! Read that sentence again, or you > > will regret it (unable to login). > > > > CONFIG_VT=y > > CONFIG_VT_CONSOLE=y > > CONFIG_VGA_CONSOLE=y > > > > 5. 'make bzImage modules modules_install' (or separate 'make modules_install' as > > root, if you prefer doing the rest as normal user.) Note that 'make dep' is no > > longer required. > > 6. Copy your System.map and bzImage as usual (be sure /boot is mounted, if you > > have the standard gentoo setup) > > 7. If you are using nvidia-kernel, set your /usr/src/linux simlink to point to the > > 2.6 source tree and emerge an nvidia-kernel and glx that supports 2.6 (4496 or > > later? I'm not on my nvidia machine at present). > > 8. update grub/lilo stanzas; run lilo if using lilo. > > 9, Reboot and enjoy. > > > > > Specifically, please provide whatever emerge instructions you can > > > lend as well as any specific make.conf options (or other things) that > > > are important and that I should watch out for. > > > > No need to change any make.conf options > > > > > > > > Also, does the Alsa emerge work correctly for 2.6 kernels? I know > > > that Alsa is now built into the kernel, so I assume that configuration > > > is going to be slightly different, but I'm hoping that the emerge of > > > Alsa puts everything in the right place. > > > > > > > The 2.6 contains the equivalent of the latest alsa for 2.4. You define alsa > > settings in the kernel build. You don't emerge alsa any more, but you still need > > alsa-utils and alsa-lib (I'm on 0.9.8 release). Setting up the alsa aliases, > > etc., has not changed; see the gentoo alsa guide. > > The symlink isn't used for much, but it's critical if you are emerging something that has to build a kernel module (nvidia, etc.). Do the following as root: 1. ls -l /usr 2. verify that /usr/src/linux is only a link (see below) 3. rm /usr/src/linux (if exists as a link) 4. ln -s /usr/src/<your linux source directory name> /usr/src/linux If linux is not a link, then you have something setup strangely. I would suggest 'mv /usr/src/linux /usr/src/linux-old', then do 4 above. Investigate why you have a real directory or file instead of a symlink. Enjoy, -- Collins - Denver Area - Gentoo stable kernel 2.6.2-rc1 -- [EMAIL PROTECTED] mailing list
