Dear V A K, Thanks . What you said solved the problem. For initrd I did a make install in the end and it did it. Best Ashok --- "V. Ananda Krishnan" <mansarov@xxxxxxxxxx> wrote: > Ashok Sharma wrote: > > Am using Fedora 4 kernel 2.6.16.13 and kernel > panics > > when I try to boot from rebuilt kernel > > > > The error msg is device-mapper missing from > kernel? > > > > How do I fix this problem > During the kernel build phase, did you switch on the > support for Device > Mapper Support which is under the Multi-device > Support (RAID and LVM) ---> > > Besides that you might have to generate a new initrd > depending on the > distro you use. > > Regards, > V. Ananda Krishnan > > > > > --- Ashok Sharma <aks6d@xxxxxxxxxxx> wrote: > > > >> I am getting the Msg device mapper missing from > >> kernel > >> > >> How do I fix this problem > >> > >> Ashok > >> > >> > >> > >> > >> > >> --- rohit hooda <rohit13hooda@xxxxxxxxxxxxxx> > >> wrote: > >> > >>> > >>> > >>> > >>> On Tue, 09 May 2006 Jesper Juhl wrote : > >>>> On 5/8/06, Arjan van de Ven > <arjan@xxxxxxxxxxxxx> > >>> wrote: > >>>>> On Mon, 2006-05-08 at 08:25 -0300, Jeronimo > >> Zucco > >>> wrote: > >>>>>> Arjan van de Ven wrote: > >>>>>>>> May be this is caused by UDEV support. > >>>>>>> > >>>>>>> usually when this happens you forgot to use > >>> an initrd. > >>>>>>> The easiest way to do that is to just do > >>> "make install" as last step in > >>>>>>> building the kernel, that makes an initrd > >> for > >>> you and also adds the > >>>>>>> kernel and initrd correctly to grub.conf > >>>>>> And if you not want use initrd ? > >>>>> why don't you? Can you explain what you have > >>> against using an initrd? > >>>> I don't know what Jeronimo has against > initrd's, > >>> but I can tell you > >>>> what I have against them. > >>>> > >>>> An initrd complicates things. > >>>> It's one more thing to remember to build. > >>>> It's one more thing that can potentially break. > >>>> > >>>> If you just build into the kernel whatever you > >> need > >>> to get to the > >>>> point of mounting the root fs (or want to have > >>> available early) and > >>>> then anything else you need as modules, then an > >>> initrd is pretty > >>>> pointless, and it's a much more simple setup > IMO. > >>>> > >>>>> Fedora requires an initrd for several parts; > >> udev > >>> is one of them, > >>>>> mount-by-label another, selinux a third. > >>>>> > >>>> I'm not a Fedora user, so I don't know what > >> initrd > >>> assumptions are > >>>> build into it, but I've never had a need for an > >>> initrd with Slackware > >>>> - I can build an use one if I want, sure, but > it > >>> has never been a > >>>> requirement in any way. > >>>> > >>>> > >>>>> It's not like using an initrd has drawbacks > that > >> I > >>> know of, nor is it > >>>>> hard; if you use "make install" it's automatic > >> as > >>> I said, and that's a > >>>>> convenient thing to use anyway (because it > does > >>> the bootloader stuff for > >>>>> you) > >>>> Personally I consider "make install" dangerous. > >>>> > >>>> First of all it assumes that I want my kernel > to > >> be > >>> named > >>>> /boot/vmlinuz and happily overwrites any > previous > >>> kernel image that > >>>> may exist by that name. So if my new kernel > >> doesn't > >>> boot, and I only > >>>> have that one entry in my lilo.conf, then I'm > in > >>> trouble and have to > >>>> go find a CD to boot from to recover. > >>>> > >>> my friend this is not the case. In Fedora, the > >>> vmlinuz get appended with the version number of > >> the > >>> kernel as well to let you distinguish from the > >> other > >>> kernel images in /boot directory. You can > specify > >>> this version in the Makefile in the > >>> /usr/src/linux-2.6.xx path. > >>> " > >>> VERSION = 2 > >>> PATCHLEVEL = 6 > >>> SUBLEVEL = 12 > >>> EXTRAVERSION = > >>> " ... a snippet from > >> /usr/src/linux-2.6.12/Makefile > >>> this lets you specify the version numbers for ur > >>> compilation. And also you System.map and the > >> initrd > >>> and get appended with this version number as > well. > >>> > >>>> It's not like it's hard to manually copy > >> System.map > >>> & bzImage to /boot > >>>> under a unique name and add that new file to > your > >>> bootloader - I'd say > >>>> doing it by hand and keeping your old working > >>> kernel in place as a > >>>> secondary option is a hell of a lot safer than > >> just > >>> using "make > >>>> install". > >>>> > >>>> > >>>> -- > >>>> Jesper Juhl <jesper.juhl@xxxxxxxxx> > >>>> Don't top-post > >> > http://www.catb.org/~esr/jargon/html/T/top-post.html > >>>> Plain text mails only, please > >>> http://www.expita.com/nomime.html > >>>> -- > >>>> Kernelnewbies: Help each other learn about the > >>> Linux kernel. > >>>> Archive: > >>> http://mail.nl.linux.org/kernelnewbies/ > >>>> FAQ: http://kernelnewbies.org/faq/ > >>>> > >>> Regards > >>> Rohit Hooda > >>> > >> > >> Send instant messages to your online friends > >> http://uk.messenger.yahoo.com > >> > >> -- > >> Kernelnewbies: Help each other learn about the > Linux > >> kernel. > >> Archive: > >> http://mail.nl.linux.org/kernelnewbies/ > >> FAQ: http://kernelnewbies.org/faq/ > >> > >> > > > > > > > > > > > ___________________________________________________________ > > > Switch an email account to Yahoo! Mail, you could > win FIFA World Cup tickets. http://uk.mail.yahoo.com > > > === message truncated === ___________________________________________________________ Switch an email account to Yahoo! Mail, you could win FIFA World Cup tickets. http://uk.mail.yahoo.com -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
