headers
Joseph M Dupre (AVAB Inc. | 1 Jul 2005 01:43

Using LVM partitions

I'm trying to boot up to my new LFS 6.0 partition which is a LVM 
logical volume, but I am getting this:

...(snipped)
device-mapper: 4.1.0-ioctl (2003-12-10 initialised: dm <at> uk.sistina.com
...(snipped)
VFS: Cannot open root device "VolGroup00/LFS" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) 

Grub and the lfskernel are currently running from the host's non-LVM 
ext3 boot partition, *not* LFS's /boot directory.  You can see that 
the LVM support (device-mapper) is compiled into the kernel.  

My (snipped) entry in grub is:

target Fedora Core 3
root (hd0,0)
kernel /vmlinuz-2.6.9-1.667smp ro root=/dev/VolGroup00/LogVol00 rhgb 
quiet
initrd /initrd-2.6.9-1.667smp.img

target LFS 6.0
root (hd0,0)
kernel /lfskernel-2.6.8.1 root=/dev/VolGroup00/LFS  

Does anyone know more about LVM that could tell me why the host 
fedora boot up can find the logical volumes but the LFS boot can't?

- Joe
(Continue reading)

Permalink | Reply | 1 comment |
headers
Dan McGhee | 1 Jul 2005 03:01
Favicon

HotPlug and Udev Questions

Although most of my questions concern post_LFS issues, I'm posting here 
because the discussion of modules and devices is in LFS-6.0.  If my 
questions are not appropriate for this list, I'll transfer them to BLFS.

My printer, which prints "randomly" and my desire to have my new digital 
camera work with GIMP caused me to start researching hotplug.  (BEGIN 
OFF TOPIC  The ghoto2 Users' Manual has a great discussion of 
permissions and configurations for usb.  END OFF TOPIC)  My research 
ultimately lead to Section 7.4 of the LFS Manual.  In particular, 
Section 7.4.3, "Handling Hotpluggable/Dynamic Devices, p. 244, says:

If the driver of the just plugged in device is available as a module but 
currently unloaded, then attaching the device to the system will only 
cause the kernel's bus driver to generate a hotplug event that notifies 
userspace of the new device connection and it not being attached to a 
driver.  In effect, nothing happens and the device itself is not usable yet.

My first question is this.  If I have udev set up as a result of the 
bootscripts, do I also need to install hotplug to get my printer to 
work--its drivers are completely modular?  Will this also apply to my 
digital camera whose drivers are supplied by gphoto2?  And ultimately 
also apply to my scanner whose drivers are in SANE?  (Yes, Declan, 
there's a pun in there :) )

In looking at the documentation at http://linux-hotplug.sourceforge.net 
and the LFS/BLFS hints for modules and hotplugging, I used some of the 
commands to see if the software was properly installed.  Instead of

</sbin/hotplug>
(Continue reading)

Permalink | Reply | 11 comments |
headers
Ken Moffat | 1 Jul 2005 03:13

Re: Using LVM partitions

On Thu, 30 Jun 2005, Joseph M Dupre (AVAB Inc.) wrote:

> I'm trying to boot up to my new LFS 6.0 partition which is a LVM
> logical volume, but I am getting this:
>
> ...(snipped)
> device-mapper: 4.1.0-ioctl (2003-12-10 initialised: dm <at> uk.sistina.com
> ...(snipped)
> VFS: Cannot open root device "VolGroup00/LFS" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
>
> Grub and the lfskernel are currently running from the host's non-LVM
> ext3 boot partition, *not* LFS's /boot directory.  You can see that
> the LVM support (device-mapper) is compiled into the kernel.
>
> My (snipped) entry in grub is:
>
> target Fedora Core 3
> root (hd0,0)
> kernel /vmlinuz-2.6.9-1.667smp ro root=/dev/VolGroup00/LogVol00 rhgb
> quiet
> initrd /initrd-2.6.9-1.667smp.img
>
> target LFS 6.0
> root (hd0,0)
> kernel /lfskernel-2.6.8.1 root=/dev/VolGroup00/LFS
>
> Does anyone know more about LVM that could tell me why the host
> fedora boot up can find the logical volumes but the LFS boot can't?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mike Robinson | 1 Jul 2005 04:28

Trying to move from Red Hat 8.0 (kernel 1.4) to 1.6

Please excuse what may seem to be an "RTFM" question.  I promise, promise that 
I -have- looked.

I'm trying to move from Red Hat 8.0 to LFS 1.6.  Obviously this means that I 
am trying to compile the toolchain (specifically at this point glibc) under 
the 1.4 kernel.  I am now confronting the "the chicken or the egg problem" 
that the stated "system requirements" for building an LFS 1.6 kernel say that 
you must already have one.  I do not have the option of shutting this system 
down, booting from CD-ROM and trying to replace the kernel that way.  I need 
to be able to compile the toolchain, and thence the kernel and so-on, doing 
all of the compiles and setup under 1.4.  Then I need to be able to 
successfully boot into 1.6 and move the files into their final locations.

What I do not find is a concise technical explanation of how to perform this.  
In reading the various postings I am keenly aware that the people who are 
talking among themselves have already experienced the "ah hah! moment" 
whereas I have not.  Would one of you therefore kindly point me in the right 
direction?  I'm now stuck at step 5.8 facing "fatal: kernel too old," with a 
thick pile of previous postings that I have read closely, and yet no clear 
idea how to proceed.

Many thanks.

--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Permalink | Reply | 1 comment |
headers
Menon Girish | 1 Jul 2005 16:09
Picon

Re[5]: Корпоративные, Групповые и Частные занятия у Вас дома и в офисе Shang

Доброе время суток!

Весь английский для Вас! Приходите и узучайте
разговорный английский. 

Сегодня со скидками!!!

Мы жд_м Вашего звонка в Москве:
один-ноль-пять пять-один-восемь-шесть
156-0000

Brennan Kenney Decker
Poisson Shaminov Narius Poludennyi
Ambre Morishita Waddell Egor

--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Permalink | Reply | 0 comments |
headers
Stephen Liu | 1 Jul 2005 15:07
Picon
Favicon

A question on 5.36. Stripping

Hi folks,

I skipped following section

5.36. Stripping 
http://www.sg.linuxfromscratch.org/lfs/view/6.0/chapter05/stripping.html

Because there is sufficient space on /mnt/lfs.  In
case of need on which directory will following
commands be executed;

strip --strip-debug /tools/lib/*
strip --strip-unneeded /tools/{,s}bin/*

rm -rf /tools/{doc,info,man}

TIA

B.R.
Stephen Liu
--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Permalink | Reply | 0 comments |
headers
Andrew Benton | 1 Jul 2005 17:38
Picon
Picon

Re: Trying to move from Red Hat 8.0 (kernel 1.4) to 1.6

Mike Robinson wrote:
> Please excuse what may seem to be an "RTFM" question.  I promise, promise that 
> I -have- looked.
> 
> I'm trying to move from Red Hat 8.0 to LFS 1.6.  Obviously this means that I 
> am trying to compile the toolchain (specifically at this point glibc) under 
> the 1.4 kernel.  I am now confronting the "the chicken or the egg problem" 
> that the stated "system requirements" for building an LFS 1.6 kernel say that 
> you must already have one.  I do not have the option of shutting this system 
> down, booting from CD-ROM and trying to replace the kernel that way.  I need 
> to be able to compile the toolchain, and thence the kernel and so-on, doing 
> all of the compiles and setup under 1.4.  Then I need to be able to 
> successfully boot into 1.6 and move the files into their final locations.
> 
> What I do not find is a concise technical explanation of how to perform this.  
> In reading the various postings I am keenly aware that the people who are 
> talking among themselves have already experienced the "ah hah! moment" 
> whereas I have not.  Would one of you therefore kindly point me in the right 
> direction?  I'm now stuck at step 5.8 facing "fatal: kernel too old," with a 
> thick pile of previous postings that I have read closely, and yet no clear 
> idea how to proceed.
> 
> Many thanks.
> 
Why don't you download a recent distro like Fedora Core 4 or Ubuntu? Some people use a live CD. Personally I
found Ubuntu a good host to build from last time I started from scratch, when we got my daughter a few months ago
--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
(Continue reading)

Permalink | Reply | 0 comments |
headers
Stephen Liu | 1 Jul 2005 15:24
Picon
Favicon

What is 'user root'

Hi folks,

I'm now prepared to proceed on following section

6. Installing Basic System Software
http://www.sg.linuxfromscratch.org/lfs/view/6.0/chapter06/chapter06.html

On following "Note"
>>
The remainder of this book is to be performed while
logged in as user root and no longer as user lfs
<<

I'm not very clear of the instruction.  I proceeded
previous Sections while login as LFS Root with
following command

[satimis <at> localhost ~]$ su - lfs
Password: (enter 'LFS Root' password)

Whether the above refers to 'user root'

What is 'user lfs'?  Please advise.  TIA

B.R.
Stephen

--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
(Continue reading)

Permalink | Reply | 1 comment |
headers
Andrew Benton | 1 Jul 2005 14:07
Picon
Picon

Re: HotPlug and Udev Questions

Dan McGhee wrote:
> My printer, which prints "randomly" and my desire to have my new digital 
> camera work with GIMP caused me to start researching hotplug.  (BEGIN 
> OFF TOPIC  The ghoto2 Users' Manual has a great discussion of 
> permissions and configurations for usb.  END OFF TOPIC)  My research 
> ultimately lead to Section 7.4 of the LFS Manual.  In particular, 
> Section 7.4.3, "Handling Hotpluggable/Dynamic Devices, p. 244, says:
> 
> If the driver of the just plugged in device is available as a module but 
> currently unloaded, then attaching the device to the system will only 
> cause the kernel's bus driver to generate a hotplug event that notifies 
> userspace of the new device connection and it not being attached to a 
> driver.  In effect, nothing happens and the device itself is not usable 
> yet.
> 
What I do is build the kernel modules for the things I need (parallel printer, usb printer, digital camera)
into the kernel. That way the drivers are always available  and I avoid a few module loading issues. I can't
see the point of modules if you compile your own kernel. The printers are always connected so I don't think
hotplug is relevant at all. CUPS handles them. (I won't start talking about cups or I'll be here all day ;) 
As far as the kernel is concerned my digital camera is fat 32 usb flash memory just like an mp3 player, flash
memory stick, usb portable hard disk, whatever. They all end up as /dev/sda1 and I mount them with this line
in /etc/fstab

/dev/sda1 /mnt/mp3 auto defaults,user,noauto 0 0

gphoto has never done anything useful for me but YMMV
--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
(Continue reading)

Permalink | Reply | 10 comments |
headers
Joseph M Dupre (AVAB Inc. | 1 Jul 2005 20:49

Re: Using LVM partitions

On 1 Jul 2005 at 0:00, lfs-support-request <at> linuxfromscratch.org wrote:

> kernel events.  I think this might be a chicken-and-egg situation -
> there are no new real devices to create events, all the kernel can see
> are the /dev/hdXn devices.
The initrd use with the fedora setup may be the difference.  The grub 
menu is looking for a device called /dev/VolGroup00/LFS, so that must 
have been defined in the initrd.

> Maybe lvm is
> somewhat similar, and you need to set up a config file for it ?
LVM reads some sort of "signature" written to the drive itself.  
There is no conf file.  Obviously the kernel must have LVM support 
compiled in to do this.

>  A quick google for lvm and udev suggests that /sbin/lvm2 might need
>  to be
> run from an init script, which I guess would mean you _do_ need the
> lvm tools.

That can't be, as the the drive must be mounted first before you 
could have access to any userspace files.  I will take a look at the 
fedora's init scripts to see what it is doing.

- Joe

--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
(Continue reading)

Permalink | Reply | 0 comments |

Gmane