Re: [lfs-support] help

[Kevin Liu]

Tim, thanks for your suggestion. I made a new build for make 4.3, copied it 
over to /usr/bin, then problem resolved. Many thanks again. Kevin

Sent from my iPad

> On Nov 29, 2020, at 11:04 PM, Tim Tassonis  wrote:
> 
> 
> 
>> On 11/30/20 6:02 AM, Kevin Liu wrote:
>> Dear Sir/Madam,
>> 1. compiling LFS version 10.0, chapter 5.5, glibc-2.32
>> 2. too old : make error running ../configure, see below
>> checking for python3... python3
>> checking version of python3... 3.6.8, ok
>> configure: error:
>> *** These critical programs are missing or too old: make
>> *** Check the INSTALL file for required versions.
>> 3. make:
>> lfs:/mnt/lfs/sources/glibc-2.32/build$ which make
>> /usr/bin/make
>> lfs:/mnt/lfs/sources/glibc-2.32/build$ make -v
>> GNU Make 3.82
>> Built for x86_64-redhat-linux-gnu
>> Copyright (C) 2010  Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later 
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>> 4. PATH
>> lfs:/mnt/lfs/sources/glibc-2.32/build$ env | grep PATH
>> PATH=/mnt/lfs/tools/bin:/usr/bin
>> 5. Linux
>> lfs:/mnt/lfs/sources/glibc-2.32/build$ uname -a
>> Linux starbuck 3.10.0-957.10.1.el7.x86_64 #1 SMP Mon Mar 18 15:06:45 UTC 
>> 2019 x86_64 x86_64 x86_64 GNU/Linux
>> Please help, thanks in advance. Kevin
> 
> 
> "Chapter 2. Preparing the Host System"
> 
> clearly states that you need at least make 4.0, but you only have GNU Make 
> 3.82.
> 
> You might try to build
> 
> "6.12. Make-4.3"
> 
> before chapter 5.5, and then re-try, but I'm not sure if that works.
> 
> 
> Bye
> Tim
> -- 
> http://lists.linuxfromscratch.org/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
> 
> Do not top post on this list.
> 
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> 
> http://en.wikipedia.org/wiki/Posting_style

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] help

[Tim Tassonis]

On 11/30/20 6:02 AM, Kevin Liu wrote:

Dear Sir/Madam,

1. compiling LFS version 10.0, chapter 5.5, glibc-2.32
2. too old : make error running ../configure, see below
checking for python3... python3
checking version of python3... 3.6.8, ok
configure: error:
*** These critical programs are missing or too old: make
*** Check the INSTALL file for required versions.
3. make:
lfs:/mnt/lfs/sources/glibc-2.32/build$ which make
/usr/bin/make
lfs:/mnt/lfs/sources/glibc-2.32/build$ make -v
GNU Make 3.82
Built for x86_64-redhat-linux-gnu
Copyright (C) 2010  Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
4. PATH
lfs:/mnt/lfs/sources/glibc-2.32/build$ env | grep PATH
PATH=/mnt/lfs/tools/bin:/usr/bin
5. Linux
lfs:/mnt/lfs/sources/glibc-2.32/build$ uname -a
Linux starbuck 3.10.0-957.10.1.el7.x86_64 #1 SMP Mon Mar 18 15:06:45 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux


Please help, thanks in advance. Kevin



"Chapter 2. Preparing the Host System"

clearly states that you need at least make 4.0, but you only have GNU 
Make 3.82.


You might try to build

"6.12. Make-4.3"

before chapter 5.5, and then re-try, but I'm not sure if that works.


Bye
Tim
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help with Booting LFS

[Xi Ruoyao]

On 2020-01-14 16:08 -0700，Alan Feuerbacher wrote:
> On 1/14/2020 7:39 AM, Xi Ruoyao wrote:
> > On 2020-01-13 13:41 -0700, Alan Feuerbacher wrote:
> > > I'm building the LFS systemd development version, and having some
> > > difficulty deciding how to configure some UEFI things.
> > > 
> > > I'm using GPT partitions and LVM (Logical Volume Management).
> > Using LVM for root FS would require an initramfs:
> > 
> > http://svn.linuxfromscratch.org/hints/trunk/Root_FS_on_RAID+encryption+LVM.txt
> > 
> > /* snip */
> 
> Building an initramfs was the key: I can now boot up using rEFInd.
> 
> I still can't boot with grub, though, even though I used some concepts 
> from the rEFInd configure file to modify grub.cfg.

/* snip */

> The grub.cfg is now:
> 
> 
>   # Begin /boot/grub/grub.cfg
>  set default=0
>  set timeout=5
> 
>  insmod gzio
>  insmod part_gpt
>  insmod ext2
> #set root=(hd1, gpt1)
> #set root=(hd1, gpt3)
>  set root=UUID="08122b74-5c84-4aa5-947e-0d2952db1ecd"

/* snip */

> When I try to boot with grub, the grub command interpreter puts out this error
> message:
> 
> error: disk '08122b74-5c84...' not found.

"set root=(some uuid)" is wrong.  Grub doesn't support this thing.  It should be
something like

search --no-floppy --fs-uuid --set=root 08122b74-5c84...

> error: you need to load the kernel first.
> 
> I get a similar error no matter what "set root=..." line I use. For 
> example, when I use:
> 
> set root=(hd1, gpt3)
> 
> I get:
> 
> error: disk '(hd1, ' not found.
> 
> I have no clue what " '(hd1, ' " represents.

I don't think LVM devices are "hard drive" in Grub.  You can get into the grub
command line interface and try to find the correct partition.  From "info grub":

> This means that, for example, you only need to type
> 
>  set root=(
> 
>followed by a , and GRUB will display the list of drives,
> partitions, or file names.  So it should be quite easy to determine the
> name of your target partition, even with minimal knowledge of the
> syntax.

/* snip */

> Yes, as I said above, that worked with rEFInd, but not grub. Any ideas?

They are different softwares, and there is no "ISO/IEC 9:2020 - Information
Technology -- Bootloader" forcing their behavior.

> I noticed something very strange. I have separate partitions for /boot 
> and /boot/efi. In the Fedora 31 host system, /boot is populated as expected:
> 
> (lfs chroot) root:/boot# ll
> total 39092
> -rw-r--r-- 1 root root  5293922 Jan 14 12:16 System.map-5.4.8
> -rw-r--r-- 1 root root   132145 Jan 14 12:17 config-5.4.8
> drwxr-xr-x 3 root root 4096 Dec 31  1969 efi
> drwxr-xr-x 4 root root 4096 Jan 14 14:13 grub
> drwxr-xr-x 2 root root 4096 Jan 14 14:39 grubexp
> -rw-r--r-- 1 root root 22604288 Jan 14 11:29 initrd.img-5.4.8
> drwx-- 2 root root16384 Jan  2 14:26 lost+found
> -rw-r--r-- 1 root root  511 Jan 10 20:38 refind_linux.conf
> -rw-r--r-- 1 root root 11957120 Jan 14 12:16 vmlinuz-5.4.8-lfs-20200109-
> systemd
> 
> But in my newly booted LFS system, nothing but the efi entry is there. What's
> going on?

I don't know.  You can just run "mount" in both systems to see.
-- 
Xi Ruoyao 
School of Aerospace Science and Technology, Xidian University

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help with Booting LFS

[Alan Feuerbacher]

On 1/14/2020 7:39 AM, Xi Ruoyao wrote:

On 2020-01-13 13:41 -0700, Alan Feuerbacher wrote:

I'm building the LFS systemd development version, and having some
difficulty deciding how to configure some UEFI things.

I'm using GPT partitions and LVM (Logical Volume Management).

Using LVM for root FS would require an initramfs:

http://svn.linuxfromscratch.org/hints/trunk/Root_FS_on_RAID+encryption+LVM.txt

/* snip */


Building an initramfs was the key: I can now boot up using rEFInd.

I still can't boot with grub, though, even though I used some concepts 
from the rEFInd configure file to modify grub.cfg.


The rEFInd refind.conf is now:


menuentry Linux-LFS-f {
icon EFI/refind/icons/os_linux.png
volume efi-boot
loader /vmlinuz-5.4.8-lfs-20200109-systemd
initrd /initrd.img-5.4.8
options "ro root=UUID=f7309704-012d-4115-884d-403c6e06a989 
initrd=/initrd.img-5.4.8"
}



The grub.cfg is now:


 # Begin /boot/grub/grub.cfg
set default=0
set timeout=5

insmod gzio
insmod part_gpt
insmod ext2
#set root=(hd1, gpt1)
#set root=(hd1, gpt3)
set root=UUID="08122b74-5c84-4aa5-947e-0d2952db1ecd"
#set root=(lvm/lfslvm-boot)

insmod efi_gop
insmod efi_uga
insmod font
if loadfont /boot/grub/fonts/unicode.pf2; then
  loadfont /boot/grub/fonts/unicode.pf2
  set gfxmode=auto
  insmod gfxterm
  set gfxpayload=keep
  terminal_output gfxterm
fi

menuentry "GNU/Linux, Linux vmlinuz-5.4.8-lfs-20200109-systemd"  {
  linux   /vmlinuz-5.4.8-lfs-20200109-systemd 
root=UUID=f7309704-012d-4115-884d-403c6e06a989 initrd=/initrd.img-5.4.8 ro
  initrd /initrd.img-5.4.8
}


Here are the relevant bits from blkid on the host system:
#
[root@localhost Buildscripts-sysd9]# blkid
/dev/sdb1: LABEL_FATBOOT="efi-boot" LABEL="efi-boot" UUID="000A-CAC9"
TYPE="vfat" PARTLABEL="EFI System" PARTUUID="3ae2214c-3cf6-4324-80cf-
a01741ccbccc"
/dev/sdb3: UUID="VzWWbo-7FXe-LfrH-vMkK-ewze-y0kQ-vFV395"
TYPE="LVM2_member" PARTLABEL="Linux LVM" PARTUUID="b0ce9087-639c-4487-
97dc-5c947aec3603"
/dev/sdb4: UUID="u3BU8P-G1GU-FqWS-sm2q-5xpe-tvUb-68s3zX"
TYPE="LVM2_member" PARTLABEL="Linux LVM" PARTUUID="35e97922-0128-453a-
afbf-3f0dd75d98b2"
/dev/mapper/lfslvm-boot: UUID="08122b74-5c84-4aa5-947e-0d2952db1ecd"
TYPE="ext4"
/dev/mapper/lfslvm-root: UUID="f7309704-012d-4115-884d-403c6e06a989"
TYPE="ext4"
#

When I try to boot with grub, the grub command interpreter puts out this error 
message:

error: disk '08122b74-5c84...' not found.
error: you need to load the kernel first.

I get a similar error no matter what "set root=..." line I use. For 
example, when I use:


set root=(hd1, gpt3)

I get:

error: disk '(hd1, ' not found.

I have no clue what " '(hd1, ' " represents.

See grub.cfg above for my attempts.

I've been unable to find relevant information on the Net.


I've had trouble with the "efivarfs" stuff in builds years ago. In
particular, is the line in /etc/fstab necessary or not? I think it is
necessary in my system, partly because efibootmgr (running in the chroot
environment) gives an error complaining about "efivars not defined"
without it. But when I mount an efi directory like so (the stuff below
is all run from the host system, not in the chroot environment):

mkdir -pv /sys/firmware/efi/efivars
mount -t efivars efivars /sys/firmware/efi/efivars

efibootmgr runs ok and seems to give reasonable output.

Old kernels have /sys/firmware/efi/efivars as a part of sysfs.  In newer kernel
builds firmware/efi/efivars is an empty directory in sysfs and efivarfs should
be mounted here.  The old way is CONFIG_EFI_VARS and the new way is
CONFIG_EFIVAR_FS, in kconfig.  We're using the latter, in the hint:


  ## CONFIG_EFI_VARS is not set
  ## CONFIG_EFI_RUNTIME_MAP=y

Location:
  -> Firmware Drivers
-> EFI (Extensible Firmware Interface) Support
  < > EFI Variable Support via sysfs
  [*] Export efi runtime maps to sysfs


  ## CONFIG_EFIVAR_FS=y/m

 Location:
   -> File systems
 -> Pseudo filesystems
   [*] EFI Variable filesystem
My .config is the same, except for CONFIG_EFI_VARS which is set. It all 
appears to be working, but I'm checking out a lot of stuff.

/* snip */


  menuentry "GNU/Linux, Linux vmlinuz-5.4.8-lfs-20200109-systemd"  {
#  linux   /vmlinuz-5.4.8-lfs-20200109-systemd root=/dev/sdb4 ro
linux   /vmlinuz-5.4.8-lfs-20200109-systemd
root=35e97922-0128-453a-afbf-3f0dd75d98b2 ro
  }

/* snip */


The last Boot entry eventually puts out an error message:

error: disk '3ae2214c-3cf6-4324-80cf-a01741ccbccc' not found

Using UUID as the value of "root" in kernel command line would require an
initramfs.  So in LFS book we just use root=/dev/sd[a-z][1-9].


Yes, as I said above, that worked with rEFInd, but not grub. Any ideas?


I noticed something very strange. I have 

Re: [lfs-support] Help with Booting LFS

[Xi Ruoyao]

On 2020-01-13 13:41 -0700, Alan Feuerbacher wrote:
> I'm building the LFS systemd development version, and having some 
> difficulty deciding how to configure some UEFI things.
> 
> I'm using GPT partitions and LVM (Logical Volume Management).

Using LVM for root FS would require an initramfs:

http://svn.linuxfromscratch.org/hints/trunk/Root_FS_on_RAID+encryption+LVM.txt

/* snip */

> I've had trouble with the "efivarfs" stuff in builds years ago. In 
> particular, is the line in /etc/fstab necessary or not? I think it is 
> necessary in my system, partly because efibootmgr (running in the chroot 
> environment) gives an error complaining about "efivars not defined" 
> without it. But when I mount an efi directory like so (the stuff below 
> is all run from the host system, not in the chroot environment):
> 
> mkdir -pv /sys/firmware/efi/efivars
> mount -t efivars efivars /sys/firmware/efi/efivars
> 
> efibootmgr runs ok and seems to give reasonable output.

Old kernels have /sys/firmware/efi/efivars as a part of sysfs.  In newer kernel
builds firmware/efi/efivars is an empty directory in sysfs and efivarfs should
be mounted here.  The old way is CONFIG_EFI_VARS and the new way is
CONFIG_EFIVAR_FS, in kconfig.  We're using the latter, in the hint:

>  ## CONFIG_EFI_VARS is not set
>  ## CONFIG_EFI_RUNTIME_MAP=y
> 
>Location:
>  -> Firmware Drivers
>-> EFI (Extensible Firmware Interface) Support
>  < > EFI Variable Support via sysfs
>  [*] Export efi runtime maps to sysfs
> 
> 
>  ## CONFIG_EFIVAR_FS=y/m
> 
> Location:
>   -> File systems
> -> Pseudo filesystems
>   [*] EFI Variable filesystem

/* snip */

>  menuentry "GNU/Linux, Linux vmlinuz-5.4.8-lfs-20200109-systemd"  {
> #  linux   /vmlinuz-5.4.8-lfs-20200109-systemd root=/dev/sdb4 ro
>linux   /vmlinuz-5.4.8-lfs-20200109-systemd 
> root=35e97922-0128-453a-afbf-3f0dd75d98b2 ro
>  }

/* snip */

> The last Boot entry eventually puts out an error message:
> 
> error: disk '3ae2214c-3cf6-4324-80cf-a01741ccbccc' not found

Using UUID as the value of "root" in kernel command line would require an
initramfs.  So in LFS book we just use root=/dev/sd[a-z][1-9].
-- 
Xi Ruoyao 
School of Aerospace Science and Technology, Xidian University

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[DOMINIQUE VAYSSAIRAT]

HI,

If you use an external support (i.e USB ) you can try to add on the linux line 
: rootdelay=10 (or more). Some devices are slow during boot.



> Le 28 nov. 2018 à 21:56, thomas  a écrit :
> 
> Am 2018-11-28 19:57, schrieb Jimmy Zhang:
>> Hi,
>> I followed the instruction on LFS-BOOK-8.3.pdf step by step to the
>> end.
>> During the reboot, I got the error message "Kernel panic - not
>> syncing: VFS: Unable to mount root fs on unknown-block(0,0)".
>> I was building LFS with my VMware machine.
>> Need help to see which part I may mess up?
>> Thanks,
>> Jimmy Zhang
> 
> Usually this is caused by missing device drivers in the kernel so that the 
> kernel isn't able to read the root file system. This can be caused by missing 
> filesystem drivers like ext4 or by missing drivers for the disk devices 
> itself like PATA or SATA.
> Check the kernel configuration for that.
> 
> --
> Thomas
> --
> http://lists.linuxfromscratch.org/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
> 
> Do not top post on this list.
> 
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> 
> http://en.wikipedia.org/wiki/Posting_style



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[Thomas Trepl]

Am Samstag, den 01.12.2018, 03:20 + schrieb Jimmy Zhang:
> 
> 
> On Wednesday, November 28, 2018, 8:15:30 PM EST, renodr 
>  wrote:
> 
> 
> On 2018-11-28 14:56, thomas wrote:
> > Am 2018-11-28 19:57, schrieb Jimmy Zhang:
> >> Hi,
> >> I followed the instruction on LFS-BOOK-8.3.pdf step by step to the
> >> end.
> >> During the reboot, I got the error message "Kernel panic - not
> >> syncing: VFS: Unable to mount root fs on unknown-block(0,0)".
> >> I was building LFS with my VMware machine.
> >> Need help to see which part I may mess up?
> >> Thanks,
> >> Jimmy Zhang
> > 
> > Usually this is caused by missing device drivers in the kernel so that
> > the kernel isn't able to read the root file system. This can be caused
> > by missing filesystem drivers like ext4 or by missing drivers for the
> > disk devices itself like PATA or SATA.
> > Check the kernel configuration for that.
> > 
> > --
> > Thomas
> 
> Jimmy,
> 
> Look for Fusion MPT support and build all of that, as well as the VMWare 
> VMCI Driver, SCSI Disk/Device/Generic support, Buslogic SCSI support, 
> and PVSCSI support. You might need the VMXNET3 driver as well.
> 
> 
> 
> Hi guys,
> I added PATA, SATA, VMWaer VMCI Driver, SCSI drivers and my kernel continued 
> and passed the panic spot I reported.
> But still stopped at 
> Looks still missing some drivers. Any suggestions will be appreciated.
> Thanks for all your support.
> Jimmy

Ah, some progress made.

Maybe you zip the kernel config (.config) and post it here together
with the grub.cfg?

--
Thomas


-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[Jimmy Zhang]

 

On Wednesday, November 28, 2018, 8:15:30 PM EST, renodr 
 wrote:  
 
 On 2018-11-28 14:56, thomas wrote:
> Am 2018-11-28 19:57, schrieb Jimmy Zhang:
>> Hi,
>> I followed the instruction on LFS-BOOK-8.3.pdf step by step to the
>> end.
>> During the reboot, I got the error message "Kernel panic - not
>> syncing: VFS: Unable to mount root fs on unknown-block(0,0)".
>> I was building LFS with my VMware machine.
>> Need help to see which part I may mess up?
>> Thanks,
>> Jimmy Zhang
> 
> Usually this is caused by missing device drivers in the kernel so that
> the kernel isn't able to read the root file system. This can be caused
> by missing filesystem drivers like ext4 or by missing drivers for the
> disk devices itself like PATA or SATA.
> Check the kernel configuration for that.
> 
> --
> Thomas

Jimmy,

Look for Fusion MPT support and build all of that, as well as the VMWare 
VMCI Driver, SCSI Disk/Device/Generic support, Buslogic SCSI support, 
and PVSCSI support. You might need the VMXNET3 driver as well.


Hi guys,I added PATA, SATA, VMWaer VMCI Driver, SCSI drivers and my kernel 
continued and passed the panic spot I reported.But still stopped at 
Looks still missing some drivers. Any suggestions will be appreciated.Thanks 
for all your support.Jimmy
  -- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[Baho Utot]

On 11/28/18 10:11 PM, Ken Moffat wrote:

On Wed, Nov 28, 2018 at 07:15:14PM -0600, renodr wrote:

Look for Fusion MPT support and build all of that, as well as the VMWare
VMCI Driver, SCSI Disk/Device/Generic support, Buslogic SCSI support, and
PVSCSI support. You might need the VMXNET3 driver as well.

since so many people seem to build in VMs, and have problems, maybe
we ought to document this somewhere ?  Alternatively, perhaps using
lsmod like on a distro does actually work on VMs ?

ĸen



I build using OverlayFs.  It is much better than to try to build it in a 
VM. I make a container that will have the host build system:


    msg_line "Creating root filesystem container - this may take awhile 
--> "

    dd if=/dev/zero of=host.img bs=4096 count=512000 > /dev/null 2>&1
    mkfs -t ext4 host.img > /dev/null 2>&1

then populate it with a host system ie PClinuxOS or LFS-8.2.

This gives me a host system called host.img

It gets mounted as read only:

OVERLAY=OVERLAY

msg_line "Mounting file systems --> "
mountpoint -q ${OVERLAY}/lower        || mount --read-only host.img 
${OVERLAY}/lower
mountpoint -q ${OVERLAY}/overlay        || mount -t overlay overlay -o 
lowerdir=${OVERLAY}/lower,upperdir=${OVERLAY}/upper,workdir=${OVERLAY}/workdir 
${OVERLAY}/overlay
mountpoint -q ${OVERLAY}/overlay/dev    || mount --bind /dev 
${OVERLAY}/overlay/dev
mountpoint -q ${OVERLAY}/overlay/dev/pts    || mount -t devpts devpts 
${OVERLAY}/overlay/dev/pts -o gid=5,mode=620
mountpoint -q ${OVERLAY}/overlay/proc    || mount -t proc proc 
${OVERLAY}/overlay/proc
mountpoint -q ${OVERLAY}/overlay/sys    || mount -t sysfs sysfs 
${OVERLAY}/overlay/sys
mountpoint -q ${OVERLAY}/overlay/run    || mount -t tmpfs tmpfs 
${OVERLAY}/overlay/run

msg_success

Then:

msg "Chrooting overlay file system --> "
chroot "${OVERLAY}/overlay" \
    env -i \
    HOME=/root \
    TERM="$TERM" \
    PS1='(blfs chroot) \u:\w\$ ' \
    PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
    /bin/bash --login +h

I then build the new system.

The "lower" filesystem never gets changed

the "upper" contains all the newer files and changes to the lower ro 
filesystem


the overlay is the merge filesystem (lower merged with upper) and it is 
where you do your work








--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[Ken Moffat]

On Thu, Nov 29, 2018 at 03:16:41PM -0700, JD wrote:
> I have run fbsd kernels that support Large File System  on multiple PC
> platforms with
> cpus from Intel and AMD, without any problems with missing Hardware
> dependencies.
> 
> So, my response was to BRUCE who brought up missing driver
> issue to the OP.
> I have never run into any missing driver issues on any of the PC I installed
> the Large File System on them.
> 
> So, Bruce has NOT come up with any answer about just exactly which driver
> he assumes is missing.
> 

So, you are now claiming to be talking about the Large File System.
And yet you earlier said 'NO' to the suggestion that is what you
were talkign about.

We have no interest in that (strictly, we expect it to be installed
on the linux machine we use to build linuxfromscratch, and it will
be used in linuxfromscratch as in all other sane modern linuxes -
limiting files to 4GB on modern disks is not a good idea.

We expect people here to build a LINUX kernel (indeed, our methods
are clearly not going to work on FreeBSD), and as part of that you
get the choice, in 'make menuconfig', of which drivers to include.

I'll file your posts under 'troll'.

-- 
I'm saving up 22 shillings and 10 pence (almost a pound!) per week to
buy an ARM-13.
http://www.antipope.org/charlie/blog-static/2018/11/brexit-means-brexit.html
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[JD]

I have run fbsd kernels that support Large File System  on multiple PC
platforms with
cpus from Intel and AMD, without any problems with missing Hardware
dependencies.

So, my response was to BRUCE who brought up missing driver
issue to the OP.
I have never run into any missing driver issues on any of the PC I installed
the Large File System on them.

So, Bruce has NOT come up with any answer about just exactly which driver
he assumes is missing.




On 11/29/18, Ken Moffat  wrote:
> On Thu, Nov 29, 2018 at 02:47:38PM -0700, JD wrote:
>>
>> On 11/29/2018 02:41 PM, Douglas R. Reno wrote:
>> >
>> > On 11/29/18 3:37 PM, JD wrote:
>> > >
>> > > On 11/29/2018 02:18 PM, Bruce Dubbs wrote:
>> > > >
>> > > > 1. LFS got on to the hard drive using the host's drivers.
>> > > >
>> > > > 2. The specific driver needed depends on the HW.  Try rebuilding
>> > > > the kernel with make defconfig; make
>> > > >
>> > > Hey Bruce,
>> > > you are saying that LFS varies and depends on the hardware??
>> > > Exactly which hardware?
>> > > The disk IO layer drivers are dependent on type of disk HW interface
>> > > at the lowest level.
>> > > Above that an abstraction layer is used, and it is possible (if
>> > > necessary) to build yet
>> > > another abstraction layer above that.
>> > > The FS's LFS layer is built on top of the "block io" layer, as the
>> > > file system works
>> > > with BLOCKS.
>> > > So, please explain what type of hardware is  LFS dependent on?
>> > >
>> >
>> > Would you happen to be here for inquiries on Large File Support (LFS),
>> > not Linux From Scratch? The two things are entirely separate, and "Large
>> > File Support" was coined many years after the Linux From Scratch
>> > distribution was started.
>> >
>> NO
>
> So, maybe you are here to troll ?
>
> On the off-chance that you are not trolling: linuxfromscratch (LFS)
> is installed in a chroot by building from a pre-existing linux
> system running on the same machine.
>
> As part of that, some parts of the build may be specific to the
> machine (or what a VM presents as, if building in a VM), e.g. gmp
> goes out of its way to optimise for what is expected to be present
> on that machine (see past issues where a low-end pentium of what was
> then the latest intel family lacked an instruction which whoever had
> updated gmp's configure script thought was present on all of that
> family).
>
> And the kernel configuration, because we expect the builder to build
> for the machine he or she is using, will vary from one machine to
> the next.
>
> ĸen
> --
> I'm saving up 22 shillings and 10 pence (almost a pound!) per week to
> buy an ARM-13.
> http://www.antipope.org/charlie/blog-static/2018/11/brexit-means-brexit.html
> --
> http://lists.linuxfromscratch.org/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
>
> Do not top post on this list.
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> http://en.wikipedia.org/wiki/Posting_style
>
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[Ken Moffat]

On Thu, Nov 29, 2018 at 02:47:38PM -0700, JD wrote:
> 
> On 11/29/2018 02:41 PM, Douglas R. Reno wrote:
> > 
> > On 11/29/18 3:37 PM, JD wrote:
> > > 
> > > On 11/29/2018 02:18 PM, Bruce Dubbs wrote:
> > > > 
> > > > 1. LFS got on to the hard drive using the host's drivers.
> > > > 
> > > > 2. The specific driver needed depends on the HW.  Try rebuilding
> > > > the kernel with make defconfig; make
> > > > 
> > > Hey Bruce,
> > > you are saying that LFS varies and depends on the hardware??
> > > Exactly which hardware?
> > > The disk IO layer drivers are dependent on type of disk HW interface
> > > at the lowest level.
> > > Above that an abstraction layer is used, and it is possible (if
> > > necessary) to build yet
> > > another abstraction layer above that.
> > > The FS's LFS layer is built on top of the "block io" layer, as the
> > > file system works
> > > with BLOCKS.
> > > So, please explain what type of hardware is  LFS dependent on?
> > > 
> > 
> > Would you happen to be here for inquiries on Large File Support (LFS),
> > not Linux From Scratch? The two things are entirely separate, and "Large
> > File Support" was coined many years after the Linux From Scratch
> > distribution was started.
> > 
> NO

So, maybe you are here to troll ?

On the off-chance that you are not trolling: linuxfromscratch (LFS)
is installed in a chroot by building from a pre-existing linux
system running on the same machine.

As part of that, some parts of the build may be specific to the
machine (or what a VM presents as, if building in a VM), e.g. gmp
goes out of its way to optimise for what is expected to be present
on that machine (see past issues where a low-end pentium of what was
then the latest intel family lacked an instruction which whoever had
updated gmp's configure script thought was present on all of that
family).

And the kernel configuration, because we expect the builder to build
for the machine he or she is using, will vary from one machine to
the next.

ĸen
-- 
I'm saving up 22 shillings and 10 pence (almost a pound!) per week to
buy an ARM-13.
http://www.antipope.org/charlie/blog-static/2018/11/brexit-means-brexit.html
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[Ken Moffat]

On Thu, Nov 29, 2018 at 01:49:49PM -0700, JD wrote:

Please do not top-post.

> 1. If the kernel does not have the required driver,
> how did LFS end up on the drive?

As Bruce has already answered.

> 2. Just exactly what driver are you referring to?
> "Driver" is a generic term which is used to to refer to different
> interfaces in the kernel.
> YOU claim that  to say "re-install" is a strange piece of advice.
> I, actually, everyone, would love to hear from you just exactly which
> driver the OP is missing.

People have already made suggestions - I do not use vmware, but
there were suggestions about that.

From a normal distro system which has been used to build LFS, in
chroot 'lsmod' will show which modules are currently loaded.  I
assume that a distro running on vmware will do the same.

So as a first step, all of those need to be available in the kernel.
For things like network devices, modules should be fine in LFS. But
for the disk drivers, and the filesystem used on the LFS partition,
they need to be built-in, not modules, because we do not use an
initrd.

Later, it is often possible to slim-down a kernel config by removing
items which seem unnecessary (but obviously, keep the existing
working kernel when trying to do that, and use a different version
for the experiments).

So, for the filesystem - ext4 (unless the builder used something
else).

For the disk drives - it depends very much on the motherboard and
(on some motherboards) which port is used for the disk.  On the
machine where I'm writing this I have

CONFIG_ATA=y
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_ATA_ACPI=y

CONFIG_SATA_AHCI=y

On some other machines I have added, variously,

CONFIG_SATA_PMP=y
CONFIG_SATA_INIC162X=y
CONFIG_SATA_ACARD_AHCI=y
CONFIG_ATA_SFF=y
CONFIG_ATA_BMDMA=y
CONFIG_ATA_PIIX=y
CONFIG_PATA_AMD=y
CONFIG_PATA_ATIIXP=y

But for a virtual machine I assume that the disk driver is
determined by the VM not by the underlying hardware.

ĸen
-- 
I'm saving up 22 shillings and 10 pence (almost a pound!) per week to
buy an ARM-13.
http://www.antipope.org/charlie/blog-static/2018/11/brexit-means-brexit.html
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[JD]

On 11/29/2018 02:41 PM, Douglas R. Reno wrote:


On 11/29/18 3:37 PM, JD wrote:



On 11/29/2018 02:18 PM, Bruce Dubbs wrote:

On 11/29/2018 02:49 PM, JD wrote:

1. If the kernel does not have the required driver,
how did LFS end up on the drive?
2. Just exactly what driver are you referring to?
 "Driver" is a generic term which is used to to refer to different
interfaces in the kernel.
YOU claim that  to say "re-install" is a strange piece of advice.
I, actually, everyone, would love to hear from you just exactly which
driver the OP is missing.


1. LFS got on to the hard drive using the host's drivers.

2. The specific driver needed depends on the HW.  Try rebuilding the 
kernel with make defconfig; make


  -- Bruce


Hey Bruce,
you are saying that LFS varies and depends on the hardware??
Exactly which hardware?
The disk IO layer drivers are dependent on type of disk HW interface 
at the lowest level.
Above that an abstraction layer is used, and it is possible (if 
necessary) to build yet

another abstraction layer above that.
The FS's LFS layer is built on top of the "block io" layer, as the 
file system works

with BLOCKS.
So, please explain what type of hardware is  LFS dependent on?



Would you happen to be here for inquiries on Large File Support (LFS), 
not Linux From Scratch? The two things are entirely separate, and 
"Large File Support" was coined many years after the Linux From 
Scratch distribution was started.



NO
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[Douglas R. Reno]

On 11/29/18 3:37 PM, JD wrote:



On 11/29/2018 02:18 PM, Bruce Dubbs wrote:

On 11/29/2018 02:49 PM, JD wrote:

1. If the kernel does not have the required driver,
how did LFS end up on the drive?
2. Just exactly what driver are you referring to?
 "Driver" is a generic term which is used to to refer to different
interfaces in the kernel.
YOU claim that  to say "re-install" is a strange piece of advice.
I, actually, everyone, would love to hear from you just exactly which
driver the OP is missing.


1. LFS got on to the hard drive using the host's drivers.

2. The specific driver needed depends on the HW.  Try rebuilding the 
kernel with make defconfig; make


  -- Bruce


Hey Bruce,
you are saying that LFS varies and depends on the hardware??
Exactly which hardware?
The disk IO layer drivers are dependent on type of disk HW interface 
at the lowest level.
Above that an abstraction layer is used, and it is possible (if 
necessary) to build yet

another abstraction layer above that.
The FS's LFS layer is built on top of the "block io" layer, as the 
file system works

with BLOCKS.
So, please explain what type of hardware is  LFS dependent on?



Would you happen to be here for inquiries on Large File Support (LFS), 
not Linux From Scratch? The two things are entirely separate, and "Large 
File Support" was coined many years after the Linux From Scratch 
distribution was started.


--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[JD]

On 11/29/2018 02:18 PM, Bruce Dubbs wrote:

On 11/29/2018 02:49 PM, JD wrote:

1. If the kernel does not have the required driver,
how did LFS end up on the drive?
2. Just exactly what driver are you referring to?
 "Driver" is a generic term which is used to to refer to different
interfaces in the kernel.
YOU claim that  to say "re-install" is a strange piece of advice.
I, actually, everyone, would love to hear from you just exactly which
driver the OP is missing.


1. LFS got on to the hard drive using the host's drivers.

2. The specific driver needed depends on the HW.  Try rebuilding the 
kernel with make defconfig; make


  -- Bruce


Hey Bruce,
you are saying that LFS varies and depends on the hardware??
Exactly which hardware?
The disk IO layer drivers are dependent on type of disk HW interface at 
the lowest level.
Above that an abstraction layer is used, and it is possible (if 
necessary) to build yet

another abstraction layer above that.
The FS's LFS layer is built on top of the "block io" layer, as the file 
system works

with BLOCKS.
So, please explain what type of hardware is  LFS dependent on?

--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[Bruce Dubbs]

On 11/29/2018 02:49 PM, JD wrote:

1. If the kernel does not have the required driver,
how did LFS end up on the drive?
2. Just exactly what driver are you referring to?
 "Driver" is a generic term which is used to to refer to different
interfaces in the kernel.
YOU claim that  to say "re-install" is a strange piece of advice.
I, actually, everyone, would love to hear from you just exactly which
driver the OP is missing.


1. LFS got on to the hard drive using the host's drivers.

2. The specific driver needed depends on the HW.  Try rebuilding the 
kernel with make defconfig; make


  -- Bruce

--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[JD]

1. If the kernel does not have the required driver,
how did LFS end up on the drive?
2. Just exactly what driver are you referring to?
"Driver" is a generic term which is used to to refer to different
interfaces in the kernel.
YOU claim that  to say "re-install" is a strange piece of advice.
I, actually, everyone, would love to hear from you just exactly which
driver the OP is missing.



On 11/29/18, Ken Moffat  wrote:
> On Thu, Nov 29, 2018 at 11:27:11AM -0700, JD wrote:
>>
>>
>> On 11/29/2018 11:00 AM, Xi Ruoyao wrote:
>> > On 2018-11-29 15:17 +, Jimmy Zhang wrote:
>> > > Hi,
>> > > One thing I am confused that the LFS kernel
>> > > (/boot/vmlinuz-4.18.5-lfs-8.3 from my partition(one partition for both
>> > > /boot and /) was loaded and run, which indicated that the system can
>> > > access my partition /dev/sda3 which was going
>> > > to be mounted as root, right? why the kernel will give the error
>> > > messages that unable to mount root fs?
>> > Grub can access your partition and copy the kernel into your RAM.  But
>> > then
>> > the kernel can not access your partition because it doesn't have proper
>> > driver.
>> Jimmy,
>> Might also be that the FS is corrupted?
>> Boot from a live DVD, and
>> fsck -y /dev/sda3
>> andthe remove the live dvd
>> and boot normally.
>> Might work!!
>> If it does not work,
>> you will have to re-install the OS.
>>
> Now that is *very* strange advice to offer on LFS, rather like the
> sort of "drive by" responses sometimes seen on forums by people who
> don't understand how LFS is built.
>
> In particular "re-install the OS" is an odd thing to say here.  The
> error message clearly implies that the kernel does not have a
> required driver.  For that, going back to chroot and fixing the
> kernel config is the normal process.
>
> ĸen
> --
> I'm saving up 22 shillings and 10 pence (almost a pound!) per week to
> buy an ARM-13.
> http://www.antipope.org/charlie/blog-static/2018/11/brexit-means-brexit.html
> --
> http://lists.linuxfromscratch.org/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
>
> Do not top post on this list.
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> http://en.wikipedia.org/wiki/Posting_style
>
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[Ken Moffat]

On Thu, Nov 29, 2018 at 11:27:11AM -0700, JD wrote:
> 
> 
> On 11/29/2018 11:00 AM, Xi Ruoyao wrote:
> > On 2018-11-29 15:17 +, Jimmy Zhang wrote:
> > > Hi,
> > > One thing I am confused that the LFS kernel (/boot/vmlinuz-4.18.5-lfs-8.3 
> > > from my partition(one partition for both
> > > /boot and /) was loaded and run, which indicated that the system can 
> > > access my partition /dev/sda3 which was going
> > > to be mounted as root, right? why the kernel will give the error messages 
> > > that unable to mount root fs?
> > Grub can access your partition and copy the kernel into your RAM.  But then
> > the kernel can not access your partition because it doesn't have proper 
> > driver.
> Jimmy,
> Might also be that the FS is corrupted?
> Boot from a live DVD, and
> fsck -y /dev/sda3
> andthe remove the live dvd
> and boot normally.
> Might work!!
> If it does not work,
> you will have to re-install the OS.
> 
Now that is *very* strange advice to offer on LFS, rather like the
sort of "drive by" responses sometimes seen on forums by people who
don't understand how LFS is built.

In particular "re-install the OS" is an odd thing to say here.  The
error message clearly implies that the kernel does not have a
required driver.  For that, going back to chroot and fixing the
kernel config is the normal process.

ĸen
-- 
I'm saving up 22 shillings and 10 pence (almost a pound!) per week to
buy an ARM-13.
http://www.antipope.org/charlie/blog-static/2018/11/brexit-means-brexit.html
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[JD]

On 11/29/2018 11:00 AM, Xi Ruoyao wrote:

On 2018-11-29 15:17 +, Jimmy Zhang wrote:

Hi,
One thing I am confused that the LFS kernel (/boot/vmlinuz-4.18.5-lfs-8.3 from 
my partition(one partition for both
/boot and /) was loaded and run, which indicated that the system can access my 
partition /dev/sda3 which was going
to be mounted as root, right? why the kernel will give the error messages that 
unable to mount root fs?

Grub can access your partition and copy the kernel into your RAM.  But then
the kernel can not access your partition because it doesn't have proper driver.

Jimmy,
Might also be that the FS is corrupted?
Boot from a live DVD, and
fsck -y /dev/sda3
andthe remove the live dvd
and boot normally.
Might work!!
If it does not work,
you will have to re-install the OS.

--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[Xi Ruoyao]

On 2018-11-29 15:17 +, Jimmy Zhang wrote:
> 
> Hi,
> One thing I am confused that the LFS kernel (/boot/vmlinuz-4.18.5-lfs-8.3 
> from my partition(one partition for both
> /boot and /) was loaded and run, which indicated that the system can access 
> my partition /dev/sda3 which was going
> to be mounted as root, right? why the kernel will give the error messages 
> that unable to mount root fs?

Grub can access your partition and copy the kernel into your RAM.  But then
the kernel can not access your partition because it doesn't have proper driver.
-- 
Xi Ruoyao 
School of Aerospace Science and Technology, Xidian University

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[Jimmy Zhang]

 
Hi,One thing I am confused that the LFS kernel (/boot/vmlinuz-4.18.5-lfs-8.3 
from my partition(one partition for both /boot and /) was loaded and run, which 
indicated that the system can access my partition /dev/sda3 which was going to 
be mounted as root, right? why the kernel will give the error messages that 
unable to mount root fs?ThanksJimmy 
On Wednesday, November 28, 2018, 8:15:30 PM EST, renodr 
 wrote:  
 
 On 2018-11-28 14:56, thomas wrote:
> Am 2018-11-28 19:57, schrieb Jimmy Zhang:
>> Hi,
>> I followed the instruction on LFS-BOOK-8.3.pdf step by step to the
>> end.
>> During the reboot, I got the error message "Kernel panic - not
>> syncing: VFS: Unable to mount root fs on unknown-block(0,0)".
>> I was building LFS with my VMware machine.
>> Need help to see which part I may mess up?
>> Thanks,
>> Jimmy Zhang
> 
> Usually this is caused by missing device drivers in the kernel so that
> the kernel isn't able to read the root file system. This can be caused
> by missing filesystem drivers like ext4 or by missing drivers for the
> disk devices itself like PATA or SATA.
> Check the kernel configuration for that.
> 
> --
> Thomas

Jimmy,

Look for Fusion MPT support and build all of that, as well as the VMWare 
VMCI Driver, SCSI Disk/Device/Generic support, Buslogic SCSI support, 
and PVSCSI support. You might need the VMXNET3 driver as well.
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style
  -- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[Ken Moffat]

On Wed, Nov 28, 2018 at 07:15:14PM -0600, renodr wrote:
> 
> Look for Fusion MPT support and build all of that, as well as the VMWare
> VMCI Driver, SCSI Disk/Device/Generic support, Buslogic SCSI support, and
> PVSCSI support. You might need the VMXNET3 driver as well.

since so many people seem to build in VMs, and have problems, maybe
we ought to document this somewhere ?  Alternatively, perhaps using
lsmod like on a distro does actually work on VMs ?

ĸen
-- 
I'm saving up 22 shillings and 10 pence (almost a pound!) per week to
buy an ARM-13.
http://www.antipope.org/charlie/blog-static/2018/11/brexit-means-brexit.html
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[renodr]

On 2018-11-28 14:56, thomas wrote:

Am 2018-11-28 19:57, schrieb Jimmy Zhang:

Hi,
I followed the instruction on LFS-BOOK-8.3.pdf step by step to the
end.
During the reboot, I got the error message "Kernel panic - not
syncing: VFS: Unable to mount root fs on unknown-block(0,0)".
I was building LFS with my VMware machine.
Need help to see which part I may mess up?
Thanks,
Jimmy Zhang


Usually this is caused by missing device drivers in the kernel so that
the kernel isn't able to read the root file system. This can be caused
by missing filesystem drivers like ext4 or by missing drivers for the
disk devices itself like PATA or SATA.
Check the kernel configuration for that.

--
Thomas


Jimmy,

Look for Fusion MPT support and build all of that, as well as the VMWare 
VMCI Driver, SCSI Disk/Device/Generic support, Buslogic SCSI support, 
and PVSCSI support. You might need the VMXNET3 driver as well.

--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[thomas]

Am 2018-11-28 19:57, schrieb Jimmy Zhang:

Hi,
I followed the instruction on LFS-BOOK-8.3.pdf step by step to the
end.
During the reboot, I got the error message "Kernel panic - not
syncing: VFS: Unable to mount root fs on unknown-block(0,0)".
I was building LFS with my VMware machine.
Need help to see which part I may mess up?
Thanks,
Jimmy Zhang


Usually this is caused by missing device drivers in the kernel so that 
the kernel isn't able to read the root file system. This can be caused 
by missing filesystem drivers like ext4 or by missing drivers for the 
disk devices itself like PATA or SATA.

Check the kernel configuration for that.

--
Thomas
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

[lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[Jimmy Zhang]

Hi,I followed the instruction on LFS-BOOK-8.3.pdf step by step to the 
end.During the reboot, I got the error message "Kernel panic - not syncing: 
VFS: Unable to mount root fs on unknown-block(0,0)".I was building LFS with my 
VMware machine.Need help to see which part I may mess up?Thanks,Jimmy Zhang-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] help

[Aditya Dixit]

Apologies for creating any sort of confusion.

My machine has x86_64 architecture. Earlier I was not sure of, it but now
I'm.

On Oct 29, 2016 11:53 PM, "Ken Moffat"  wrote:

> On Sat, Oct 29, 2016 at 08:07:44PM +0530, Aditya Dixit wrote:
> > Hey William,
> >
> > Thanks for response.
> >
> > After hours of research I could figure out the significance of 139 but I
> > still need to interpret the reason.
> >
> > And, as far as I know, my machine doesn't support x86_64 architecture.
> >
> Excuse me ?  Did you not say earlier that you were running Fedora
> 64-bit ?  What is the output of 'cat /proc/cpuinfo | head' ?
>
> ĸen
> --
> `I shall take my mountains', said Lu-Tze. `The climate will be good
> for them.' -- Small Gods
> --
> http://lists.linuxfromscratch.org/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
>
> Do not top post on this list.
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> http://en.wikipedia.org/wiki/Posting_style
>
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] help

[Ken Moffat]

On Sat, Oct 29, 2016 at 08:07:44PM +0530, Aditya Dixit wrote:
> Hey William,
> 
> Thanks for response.
> 
> After hours of research I could figure out the significance of 139 but I
> still need to interpret the reason.
> 
> And, as far as I know, my machine doesn't support x86_64 architecture.
> 
Excuse me ?  Did you not say earlier that you were running Fedora
64-bit ?  What is the output of 'cat /proc/cpuinfo | head' ?

ĸen
-- 
`I shall take my mountains', said Lu-Tze. `The climate will be good
for them.' -- Small Gods
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] help

[William Harrington]

On Sat, 29 Oct 2016 20:07:44 +0530
Aditya Dixit  wrote:

> So what should I do regarding the architecture (if there is any, if my
> machine doesn't support x86_64 architecture)??

You would want to build for x86 and not x86_64.
Run "uname -m" to be certain of your host machine hardware type.

Sincerely,

William Harrington
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] help

[Aditya Dixit]

Hey William,

Thanks for response.

After hours of research I could figure out the significance of 139 but I
still need to interpret the reason.

And, as far as I know, my machine doesn't support x86_64 architecture.

So what should I do regarding the architecture (if there is any, if my
machine doesn't support x86_64 architecture)??

And I'm not so well versed as to introduce optimizations in the tool chain
as of now.

On Oct 29, 2016 7:16 PM, "William Harrington"  wrote:

On Sat, 29 Oct 2016 08:58:46 +0530
Aditya Dixit  wrote:

> ../binutils-2.27/configure: line 4507:  2249 Segmentation fault
> (core dumped) ./$ac_file
> configure:4509: $? = 139

Hello Aditya,

Unix systems will return 128 when killed by a signal and then + the signal,
in your case it is 11. You get exit status $? = 139 in the log.

Use valgrind to find the issue. If you are not familiar with valgrind then
go to http://cs.ecs.baylor.edu/~donahoo/tools/valgrind/ for a demo.

For your LFS target, is it a generic X86_64 and can your host run binaries
meant for generic x86_64. Are you introducing any optimizations in the
toolchain for which the host cannot run?

SIncerely,

William Harrington
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] help

[Aditya Dixit]

Hey Ken,

Thank you for your timely reply.

I tried compiling the a small hello world program in my lfs
environment with x86...gnu-gcc compiler. It did produce an "a.out" but
when I tried to execute it, it again gave a segmentation fault.

Another observation of mine is that - we usually have a "GCC"
executable binary in /usr/bin to execute our code normally. But in my
$LFS/tools/bin folder, only x86..gnu-gcc compiler is there and not
"GCC". So does that make any difference?

If not, then what should I do to overcome the problem? Apologies for
troubling you but I'm a total newbie to this.

On 10/29/16, Ken Moffat  wrote:
> On Sat, Oct 29, 2016 at 08:58:46AM +0530, Aditya Dixit wrote:
>> Please help me in fixing this issue. I'm following v.7.10 of
>> LinuxFromScratch on Fedora 64-bit device.
>>
>> The problem is:
>>
>> configure:4496: checking whether the C compiler works
>> configure:4505: ./a.out
>> ../binutils-2.27/configure: line 4507:  2249 Segmentation fault
>> (core dumped) ./$ac_file
>> configure:4509: $? = 139
>> configure:4516: error: in `/mnt/lfs/sources/binutils-2.27':
>> configure:4520: error: cannot run C compiled programs.
>
> Bad hardware | bad memory | over-temperature | power-supply problem
> (including irregular mains power).
>
> Does it reliably compile other things ?  One of my machines is an
> AMD Phenom of some sort - it has always had a tendency to segfault,
> possibly a BIOS problem, dropping the caches with
>  echo 3 >/proc/sys/vm_drop_caches
> *mostly* helps - before I added that to my bootscripts, I used to
> find that using make -j3 instead of make -j4 was more reliable
> (somebody else also found that on a phenom).
>
> For memory, memtest86+ : many motherboards will NOT run for more
> than a few minutes with the "all cores" (F2) option - but if it
> locks up within 5 minutes you should reboot, select that again, then
> immediately use the option to configure it and choose round-robin or
> sequential for cores.  Leave it running for a few hours, checking it
> from time to time.
>
> At one time, over-temperature used to be a common problem, with
> gummed-up fans - modern hardware tends to throttle the CPU if the
> temperature goes up.  But if the BIOS lets you see temperatures,
> check them.
>
> Oh, and overclocking can cause this.  And sometimes, it's just one of
> those things (alpha particles ?) and works fine next time.
>
> ĸen
> --
> `I shall take my mountains', said Lu-Tze. `The climate will be good
> for them.' -- Small Gods
> --
> http://lists.linuxfromscratch.org/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
>
> Do not top post on this list.
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> http://en.wikipedia.org/wiki/Posting_style
>


-- 
*Thank You*

*Aditya Dixit*
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Re: [lfs-support] help

[Ken Moffat]

On Sat, Oct 29, 2016 at 08:58:46AM +0530, Aditya Dixit wrote:
> Please help me in fixing this issue. I'm following v.7.10 of
> LinuxFromScratch on Fedora 64-bit device.
> 
> The problem is:
> 
> configure:4496: checking whether the C compiler works
> configure:4505: ./a.out
> ../binutils-2.27/configure: line 4507:  2249 Segmentation fault
> (core dumped) ./$ac_file
> configure:4509: $? = 139
> configure:4516: error: in `/mnt/lfs/sources/binutils-2.27':
> configure:4520: error: cannot run C compiled programs.

Bad hardware | bad memory | over-temperature | power-supply problem
(including irregular mains power).

Does it reliably compile other things ?  One of my machines is an
AMD Phenom of some sort - it has always had a tendency to segfault,
possibly a BIOS problem, dropping the caches with
 echo 3 >/proc/sys/vm_drop_caches
*mostly* helps - before I added that to my bootscripts, I used to
find that using make -j3 instead of make -j4 was more reliable
(somebody else also found that on a phenom).

For memory, memtest86+ : many motherboards will NOT run for more
than a few minutes with the "all cores" (F2) option - but if it
locks up within 5 minutes you should reboot, select that again, then
immediately use the option to configure it and choose round-robin or
sequential for cores.  Leave it running for a few hours, checking it
from time to time.

At one time, over-temperature used to be a common problem, with
gummed-up fans - modern hardware tends to throttle the CPU if the
temperature goes up.  But if the BIOS lets you see temperatures,
check them.

Oh, and overclocking can cause this.  And sometimes, it's just one of
those things (alpha particles ?) and works fine next time.

ĸen
-- 
`I shall take my mountains', said Lu-Tze. `The climate will be good
for them.' -- Small Gods
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

[lfs-support] help

[Aditya Dixit]

Greetings,

I am following the LFS book release version 7.10.

I'm using Fedora-24 on a 64-bit architecture.

I am very new to this kind of development and am strictly following the
instructions given in the book.

But when I am trying to compile my glibc-2.24 version package using MAKE
command as per section 5.7 in the book, I am getting an error. It's screen
shot is attached along with. Please help me with it at the earliest
possible.

Thank you in advance :)

-- 
*Thank You*

*Aditya Dixit*
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style