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

RE: Built 2.6.14!

Why use initrd at all (as long as you are not using a RAID ROOT volume)

Try installing with ik, http://installkernel.tripod.com/

Configure your kernel and LILO/GRUB then run:

./ik -i

Then reboot.

-----Original Message-----
From: David Baron [mailto:d_baron@012.net.il] 
Sent: Wednesday, December 14, 2005 9:58 AM
To: debian-user@lists.debian.org, 
Subject: Built 2.6.14!

Yes, I succeded for the first time in building a kernel. Since the Sid
came up with "Kernel modules not enabled" and loads of undefined
symbols, no 
alsa, etc., I based the build on the working 2.6.11 config. Answered a
of questions for new items, taking mostly the defaults except for
preemption and a couple of other interesting-looking goodies. Ran
and viole. Painless.

I installed the .deb. Yaird is broken but never worked for me anyway so
the initrd the old fashioned way. Ran lilo and rebooted.

The kernel booted and came up ... exactly like the Sid version with all
same errors! So ...

1. I am not using udev. Apparently not using devfs either because I
that into the kernel with no change. Since I am based on an older
install, what exactly am I using? Devpts is what? How do I get modules
and alsa working?

2. While I cam compiling, I might as well dispense with the initrd. The
filesystems are all ext3 so I must compile in ext3, ext3, jbd and what
(I use mkinitrd with "dep" and explicitely call for ext3.)

Nice satisfaction on making my own kernel for the first time but still
use it :-(

To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact

Reply to: