gmane.linux.lfs.support

Re: lfs7.1 cannot boot

Omar — 2012-05-25T09:07:19

Thank you, Ken and Fernando. I've had a try about your suggestions. The results is below.



Look at the following (1).



Run this cmd with root on Ubuntu:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION="Ubuntu 10.04.4 LTS"


Yes, I backup the entire VM directory of Ubuntu10.04. Just a copy.



I run update-grub with root and check the file /boot/grub/grub.cfg in the end of which it has contained the description of LFS7.1 like below.
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "GNU/Linux, Linux 3.2.6-lfs-7.1 (on /dev/sdb1)" {
insmod ext2
set root='(hd1,1)'
search --no-floppy --fs-uuid --set 63a59ea4-b2dd-4ede-a506-14b8d0a951c5
linux /boot/vmlinuz-3.2.6-lfs-7.1 root=/dev/sdb1 ro
}
### END /etc/grub.d/30_os-prober ###
After rebooting select LFS 7.1 in the boot option(ubuntu can start up and run correctly.) and appear the same errors as before.

...md: ... autorun DONE.
Root-NFS: on NFS server address......
(1)Then I do a test according to what Ken said. 
Copy initrd.img-2.6.32-41-generic from /boot of the ubuntuto /boot of LFS, and change the name toinitrd.img-3.2.6-lfs-7.1, and add it to grub.cfg of ubuntu as follows.
 
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "GNU/Linux, Linux 3.2.6-lfs-7.1 (on /dev/sdb1)" {
insmod ext2
set root='(hd1,1)'
search --no-floppy --fs-uuid --set 63a59ea4-b2dd-4ede-a506-14b8d0a951c5
linux /boot/vmlinuz-3.2.6-lfs-7.1 root=/dev/sdb1 ro
initrd /boot/initrd.img-3.2.6-lfs-7.1
}
### END /etc/grub.d/30_os-prober ###
After the same operation the error prompt changes to :


1039/oom_score_adj instead.
Begin: Loading essential drivers... ...
Done.
Begin: Running /scripts/init-premount ...
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top...
Done.
[2.803565] blkid used greatest stack depth: 6744 bytes left
[2.820658] scsi_id used greatest stack depth: 6304 bytes left
[5.879234] udevd used greatest stack depth: 6268 bytes left
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
  - Check rootdelay= (did the system wait long enough?)
  - Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
FATAL: Could not load /lib/modules/3.2.6/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/3.2.6/modules.dep: No such file or directory
ALERT! /dev/sdb1 does not exist. Dropping to a shell!

BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) cat /proc/cmdline    (It is the command I run from here)

BOOT_IMAGE=/boot/vmlinux-3.2.6-lfs-7.1 root=/dev/sdb1 ro
(initramfs) cat /proc/modules
(nothing)
(initramfs) ls /lib/modules
2.6.32-41-generic 
(because it is the initrd.img of ubuntu)
(initramfs) ls /dev
(a lot of tty* devices but no sdb)
So! If the above all prompt that LFS 7.1 really need its own initrd.img. I don't know how to generate it now because lfs7.1 book doesn't contain the content. I'll search and have some other tries. 


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

回复： lfs7.1 cannot boot

Omar — 2012-05-25T02:48:24

Thank you, Elly.
I've had a try. It failed again with error prompt "no such partition."
I think the reason is in the chapter 8.4.2 of LFS 7.1 book as follow:

...Note that this is different from earlier versions where both numbers started from zero. For example, partition sda1 is (hd0,1) to GRUB and sdb3 is (hd1,3)...


________________________________
 发件人： Eleanore Boyd <cara117< at >cox.net>
收件人： Omar <vicpli< at >yahoo.com.cn>; LFS Support List <lfs-support< at >linuxfromscratch.org> 
发送日期： 2012年5月24日, 星期四, 下午 8:12
主题: Re: [lfs-support] lfs7.1 cannot boot
 

On 5/24/2012 7:11 AM, Eleanore Boyd wrote: 
On 5/24/2012 2:07 AM, Omar wrote: 
            available partitions:
            unknown-block(2.0)
As I recall, (hd*,*) refers to disk and partition, where the numbering starts at 0. It probably can't find the kernel at the second partition, or the second partition doesn't exist. (hd1,1) would actually be (hd1,0) to find the kernel and system.
Oops. Forgot to sign. It's a little early for my head....

Elly

Re: lfs7.1 cannot boot

Fernando de Oliveira — 2012-05-25T02:14:33


You have also overwritten the MBR of sda. Probably Ubuntu's grub version
is different from LFS's.



Please, if you can, provide the output of

    cat /etc/lsb-release

I believe you have first to fix Ubuntu, and doing so, the other part
will be fixed as well.

If you can boot into Ubuntu, run as root:

    grub-install /dev/sda

to get back the original grub in the MBR.

Then, as root, run

    update-grub

This will create a new grub.cfg in /etc/boot/grub which will have also a
menuentry for LFS.

If you cannot boot, the instructions above should be done using chroot.
This will be a little more difficult. Ubuntu's live CD or iso image can
be used, but first you have to be able to change the VM bios boot order
to have CD option before HD option. This is a little tricky, as you have
to the hit Esc key *only once* during the time the VMW bar is
displaying.

Before going on with the explanation of how to chroot in, we need more
feedback from you.

Re: lfs7.1 cannot boot

Ken Moffat — 2012-05-24T14:07:50

[...]
 So, you have overwritten the ubuntu grub.cfg.

 You have booted *a* linux kernel, so I don't think Elly's
suggestions to change where grub is looking or installed will be
needed.  If I've read correctly, you now only have one entry in
grub.cfg and that one doesn't boot.

 I think you might have booted the ubuntu kernel : that needs its
initrd to be able to access anything.  If you can get to the grub
command line, and you know what the initrd is called, you might be
able to edit the commandline (if the initrd is still there).
Otherwise, recover from a backup.  Once you can boot the ubuntu VM,
you will be able to use that to fix problems with your LFS system.

 After that, add the LFS system to ubuntu's grub.cfg by *editing*
that file so that there are entries for both ubuntu and LFS, not by
running programs and NOT by overwriting it.  When you have the LFS
system booting and working correctly, you can think about doing
without the ubuntu VM (hint: until you can download other software
to it, the LFS system is not particularly useful),

 Note that I know very little about Virtual Machines, they just seem
to make it harder for new builders.

ĸen

Re: lfs7.1 cannot boot

Eleanore Boyd — 2012-05-24T12:12:04

Oops. Forgot to sign. It's a little early for my head....

Elly

Re: lfs7.1 cannot boot

Eleanore Boyd — 2012-05-24T12:11:17

As I recall, (hd*,*) refers to disk and partition, where the numbering 
starts at 0. It probably can't find the kernel at the second partition, 
or the second partition doesn't exist. (hd1,1) would actually be (hd1,0) 
to find the kernel and system.

Re: binutils - Pass 2 configuration issue

sandip sitapara — 2012-05-24T10:37:12

Also would you please share your commands for binutils configuration?

On Thu, May 24, 2012 at 4:05 PM, sandip sitapara <s13884neo< at >gmail.com>wrote:

Re: binutils - Pass 2 configuration issue

sandip sitapara — 2012-05-24T10:35:48

configure script couldn't find the specific file ( compiler executable)
under /tools/lib directory so you got the message "fatal error: no input
files". I think, your /tools/lib directory is empty or wrong path for
executable.

The -B option used in gcc to find the executables, libraries, include
files, and data files of the compiler itself. And configure script couldn't
find the executable so unable to compile the conftest.c  so there is no
file like a.out. But confusion is here "configure:4066: $? = 0" why return
0?

Please check your /tools/lib directory

On Thu, May 24, 2012 at 2:38 PM, Void Abh <voidabh< at >gmail.com> wrote:

binutils - Pass 2 configuration issue

Void Abh — 2012-05-24T09:08:08

Hi All,

I have a user level understanding of linux and have done some application
programming using gcc.

I have just started out with LFS7.1 and it has been a smooth ride until 5.8
(Adjusting the toolchain).

The problem i am facing is with 5.9 :

While running the script: "binutils-2.22/configure", it failed with
config.log showing three errors:

*********************************************************************
configure:4009: x86_64-lfs-linux-gnu-gcc -B/tools/lib/ -V >&5
x86_64-lfs-linux-gnu-gcc: error: unrecognized option '-V'
x86_64-lfs-linux-gnu-gcc: fatal error: no input files
compilation terminated.
configure:4020: $? = 1
configure:4009: x86_64-lfs-linux-gnu-gcc -B/tools/lib/ -qversion >&5
x86_64-lfs-linux-gnu-gcc: error: unrecognized option '-qversion'
x86_64-lfs-linux-gnu-gcc: fatal error: no input files
compilation terminated.
configure:4020: $? = 1
configure:4040: checking for C compiler default output file name
configure:4062: x86_64-lfs-linux-gnu-gcc -B/tools/lib/    conftest.c  >&5
configure:4066: $? = 0
configure:4103: result: a.out
configure:4119: checking whether the C compiler works
configure:4128: ./a.out
../binutils-2.22/configure: line 4130: ./a.out: No such file or directory
configure:4132: $? = 127
configure:4139: error: in `/media/lin/sources/binutils-build':
configure:4143: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
***********************************************************************

Since man x86_64-lfs-linux-gnu-gcc didn't have -V  and -qversion options ,
i modified binutils-2.22/configure as follows:

#Original source:
for ac_option in --version -v -V -qversion; do

#Modified source
for ac_option in --version -v; do

With this change , i dont get the first two errors but the last error (not
finding ./a.out) still exists.
*********************************************************************
gcc version 4.6.2 (GCC)
configure:4020: $? = 0
configure:4040: checking for C compiler default output file name
configure:4062: x86_64-lfs-linux-gnu-gcc -B/tools/lib/    conftest.c  >&5
configure:4066: $? = 0
configure:4103: result: a.out
configure:4119: checking whether the C compiler works
configure:4128: ./a.out
../binutils-2.22/configure: line 4130: ./a.out: No such file or directory
configure:4132: $? = 127
configure:4139: error: in `/media/lin/sources/binutils-build':
configure:4143: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
*********************************************************************

My questions:
1) How come invalid options such as -V and -qversion have ended up in the
configure script ? Is there something that i have missed here ?
2) How come the same scripts worked during the first pass ?
3) How do i solve the last problem ? (./a.out)


I would be grateful for any help/ advise.

Regards

lfs7.1 cannot boot

Omar — 2012-05-24T07:07:34

Hi, all:
I finished all work of the LFS 7.1 book except the error when booting my LFS.

Firstly, I states my LFS 7.1.
I use VMware installed Ubuntu 10.04 on a virtual SCSI disk of 20G. Before beginning, I add another 8G virtual SCSI disk to VM and mount it in the Ubuntu manually. So the first disk with Ubuntu displays sda in /dev/ and the second which is mounted newly displays sdb in /dev/. Following the book I install LFS 7.1 on the sdb1 which is formatted with ext3 on the sdb and given only one partition. All pass with no error.
According to my disk in chapter 8.4.3 I run cmd as grub-install /dev/sdb and in chapter 8.4.4 I save grub.cfg as follows.

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

insmod ext2
set root=(hd1,1)

menuentry "GNU/Linux, Linux 3.2.6-lfs-7.1" {
linux /boot/vmlinuz-3.2.6-lfs-7.1 root=/dev/sdb1 ro
}

After a few works such as logout and unmount, I reboot the computer. But it starts up using Ubuntu again only appearing error checking of a moment.

Then I change the cmd in chapter 8.4.3 to grub-install /dev/sda and keep grub.cfg the same and reboot again. The computer gives errors as follows and stop starting up.

md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: Autorun ...
md: ... autorun DONE.
Root-NFS: on NFS server address
VFS: Unable to mount root fs via NFS. trying floppy.
VFS: cannot open root device "sdb1" or unknown-block(2.0)
Please append a correct "root=" boot option; here are the available partitions:
0b00 1048575 sr0 driver: sr
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2.0)
Pid: 1. comm: swapper/0 Not tained 3.2.6 #1
Call trace:
...mount_block_root+0x141/0x1c9...mount_root...kernel_init...

I search this problem from lfs mail list and google, which says that compiling kernel needs some SCSI driver or changing hda to sda in the grub.cfg and etc. .I compile the kernel again with more drivers like SCSI. When I reboot again, it is the same.

Could anybody help me? Thanks in advance.

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

Re: Bug in udev LFS 7.0

Ken Moffat — 2012-05-22T14:36:17

 I think you might be missing some firmware.  Does it eventually
boot if you wait for up to 5 minutes (the delay varies according to
your hardware and processor speed) ?  If it does, look in dmesg.

 If it doesn't continue, and you have KMS (kernel modesetting - for
xorg) configured, try turning that off until you are able to boot.
You might also have to review other configure options.

 There is an intention to remove all firmware from the kernel - at
the moment, firmware for older hardware is still in the kernel tree
but no new firmware is being added.  If you do need firmware, google
for 'linux firmware'.

 Alternatively, you might have made a similar error to what I did
last year : took a working config for the same kernel on a very old
installation, and forgot to update the sysfs options.  In that case,
adding devtmpfs papered over the problem.  For current LFS devtmpfs
is needed, but I think we only changed to that for 7.1.

ĸen

Re: Bug in udev LFS 7.0

Eleanore Boyd — 2012-05-22T11:50:50

Any problems with the board are up to you. However, I would suggest that 
you reconfigure the kernel, and if it still won't work, talk to the udev 
team, not us. We support LFS, not the packages that go into it except 
when there are configuration issues instead of code issues. So, have fun!

Elly

Bug in udev LFS 7.0

satit pherm — 2012-05-22T08:53:59

hi,
I think i found a bug of  udev  in LFS 7.0.
because of everytime after boot , it will stop and wait at ...

Populating /dev with device node

i used kernel 3.2 and asus main board P8Z77-V Pro.

please helps, Thank you in advance.

Satit P.

Re: handle power button in LFS

xinglp — 2012-05-18T19:10:15

2012/5/18 Bruce Dubbs <bruce.dubbs< at >gmail.com>:

I've written a script to handle power button, so my box can suspend to
disk(hibernate).
On one of my boxes, when I press the power button for one time,
the /proc/acpi/event create many event.
So when my hibernated box restored, it go hibernate again, and again.
Perhaps I need to replace the power button switch.

Re: handle power button in LFS

Fernando de Oliveira — 2012-05-18T15:54:56

With window managers, I used a script to open xterm and ask me to
{shutdown, reboot, close session}. Then, noticed several Live CDs, such
as pmagic (and systemrescuecd, if I recall correctly), which used small
scripts in xdialog. I know other distribution Live CDs with the same,
but do not remember now. That what I am using now, but with mouse click.
It would be possible possible for a initial script to test for X and
then execute for console or X, I believe.

Re: handle power button in LFS

Bruce Dubbs — 2012-05-18T15:18:55

Just a suggestion.  You could write a short script to run at C-A-D and ask if 
you want to shut down or reboot.  I don't know if this would run in a window 
manager or not.

   -- Bruce

Re: handle power button in LFS

Andrew Benton — 2012-05-18T14:00:42

On Fri, 18 May 2012 14:44:00 +0100
xinglp <xinglp< at >gmail.com> wrote:


I don't know of any other way of handling the power button event at
init 3. I used to install acpid, like you, for this reason but I
stopped as I hardly spend any time at the command prompt nowadays. So
what I do now is alter /etc/inittab so that it handles ctrl alt del by
shutting down instead of rebooting:

ca:12345:ctrlaltdel:/sbin/halt

When X is running I have my window manager (Openbox) handle pressing
the power button (xev says it is XF86PowerOff) by running a script
which (after it's tidied up a few things) calls /sbin/halt.

Andy

handle power button in LFS

xinglp — 2012-05-18T13:39:33

In order to use "power button" to shutdown or suspend my lfs.
I enabled the depreciate  /proc/acpi/event in kernel,
and install acpid to handle the button event.
It works well.

But is there any clear way to do that, such as by inittab or udev
or kernel callout userspace script ( /proc/sys/kernel/poweroff_cmd has
somethings )

I've looked into blfs, there's a lot more packages need to be
installed to enable this.(I'm not a X user,for now.)

Thanks.

Re: LFS-7.1: 6.37. Automake-1.11.3 (TEST FAILURE)!

Yasser Zamani — 2012-05-16T15:03:41

From: bl8r1ner< at >tut.by
Date: Wed, 16 May 2012 14:33:12 +0300
To: lfs-support< at >linuxfromscratch.org
Subject: Re: [lfs-support] LFS-7.1: 6.37. Automake-1.11.3 (TEST FAILURE)!

In my machine, LFS-7.1 compiled good with -j2 switch except automake in section 6. however, so far!
-Yasser

On 16 May 2012 13:29, Simon Geard <delgarde< at >ihug.co.nz> wrote:

On Tue, 2012-05-15 at 19:43 +0300, Эмиль Кранц wrote:

That surprises me. Runnning tests in parallel may be flaky, but the

actual compilation step should be fine. Every package in the book built

fine with -j6, last time I tried (on hardware capable of it).

Simon.

--

http://linuxfromscratch.org/mailman/listinfo/lfs-support

FAQ: http://www.linuxfromscratch.org/lfs/faq.html

Unsubscribe: See the above information page

Re: glibc-2.15 make error undefined reference to `__rela_iplt_start' & undefined reference to `__rela_iplt_end'

Eleanore Boyd — 2012-05-16T11:41:20

This will sound very mean, but: Learn CentOS inside and out first. Find 
all the different ways it works. /Then/ try building LFS again.

Or, try a copy+paste method, and keep an eye out for <replace_me>, which 
need the appropriate value for the system in the line (pointy brackets 
not required).

Either way, trying to customize LFS from the start doesn't seem to be 
working on your system. It usually ends in failure if you're new to the 
book (and if you're new to Linux).

Elly

Re: LFS-7.1: 6.37. Automake-1.11.3 (TEST FAILURE)!

Эмиль Кранц — 2012-05-16T11:33:12

I expect every chip has its peculiarities, and my CPUs are not an exception.
I failed to build LFS-6.8 (if I remember correctly, it was before 7.0 for
sure) with -j2, however all worked fine with -j1.
I haven't tried building in parallel on my later builds though, so maybe I
should.
On the other hand, almost all software after binutils-gcc-glibc builds in a
matter of minutes anyway, mostly under one minute, not counting the test
suites. And tests as we see from reports are better run with j1. Good time
for brushing up on man pages while waiting, I think.

In BLFS all packages except glib and mplayer were built with -j2, no problem

EK

On 16 May 2012 13:29, Simon Geard <delgarde< at >ihug.co.nz> wrote: