[Click] Is there a good "dumb-moron" guide to kernel mode?

Nicholas Weaver nweaver at ICSI.Berkeley.EDU
Thu Jan 18 16:54:30 EST 2007


On Thu, Jan 11, 2007 at 10:57:46PM +0200, Beyers Cronje composed:
> Hi Nicholas,
> 
> I also use Fedora, FC 4 was the latest I've installed. I start with the
> default config at:
> 
> /usr/src/kernels/2.6.11-1.1369_FC4-smp-i686/.config   , apply the click
> kernel patch, and compile and install the vanilla kernel using this config.
> The only thing that does not work is 'make install' adds a new entry in
> /boot/grub/grub.conf for the vanilla kernel, but the root=LABEL=/ kernel
> option tag does not work. I just manually change this tag to my root drive
> i.e. root=/dev/sda1 and everything works fine from there on.

Thanks.  I think this is my problem, but I don't know what the right
incantation for root= should be..

For the default in grub 
kernel /vmlinuz-2.6.16.22 ro root=/dev/VolGroup00/LogVol00 rhgb quiet

doesn't work (of course), bailing out with the "Unable to find device
mapper" "No Volume groups found" "Volume Group ''VolGroup00'' not
found" and related errors.

But when I do it manually to be root=/dev/sda1 (or sda, sda2 etc, its
two disks sda and sdb I belive, but df doesn't help me as it shows me
it as /dev/VolGroup/LogVol00 as /)


(The starting point is a Fedora Core 6 install fully updated, using
the 2.6.16.22 kernel from kernel.org with the click patches.  Without
the click patches, that kernel boots fine with the default root=
arguments)


Suggestions?  

Thanks for everybody's help.

(HW is a PowerEdge 850, base linux is FC6 fully updated, kernel being
modified is 2.6.16.22 with the click patches)


> One last thing, I do a full FC install, so all programming tools etc are
> installed by default through the FC install.
> 
> Hope that helps.
> 
> Beyers
> 
> 
> On 1/11/07, Eddie Kohler <kohler at cs.ucla.edu> wrote:
> >
> >The easiest thing to do is to take the working .config and copy it.
> >
> >Compiling linux with that config generally takes forever and a day
> >because of the number of modules compiled.
> >
> >How to find the config?  /lib/modules/VERSION/build/........  Poke
> >around there.  Also you can install kernel source RPMs.  Perhaps someone
> >else has more detailed advice, my memory is faulty.
> >
> >Eddie
> >
> >
> >Nicholas Weaver wrote:
> >> n Thu, Jan 11, 2007 at 09:02:06AM -0800, Eddie Kohler composed:
> >>> In my experience the hard part is finding the config that works.  After
> >>> that you're home free.  Before that I generally want to cry.  What type
> >>> of wedge are you seeing?  I generally use Red Hat/Fedora based distros.
> >>
> >> Question: would the broadcom on-board NIC cause things to screw up as
> >> well?  EG, should I just disable it and only have the Intel NICs?
> >>
> >> Was Fedora Core latest, but using a vanilla kernel.  2.6.16.13 built
> >with
> >> click.
> >>
> >> I think I may have screwed up something very low level early, because
> >> its failing by "unable to fine device-mapper major/minor"
> >>
> >>
> >> (I haven't done much kernel building etc).
> >>
> >> What configuration etc have you used succesfully?  I can nuke and
> >> reinstall this machine however I want.
> >>
> >_______________________________________________
> >click mailing list
> >click at amsterdam.lcs.mit.edu
> >https://amsterdam.lcs.mit.edu/mailman/listinfo/click
> >

-- 
Nicholas C. Weaver                               nweaver at icsi.berkeley.edu
     This message has been ROT-13 encrypted twice for higher security.


More information about the click mailing list