Re: [lfs-support] Preparing Virtual Kernel File Systems always kills Chromium.
I had the same problem. Try starting chrome from bash by typing 'google-chrome' and a solution will be suggested. I believe by remaking /dev/shm, the permissions have been changed. Correct me if I'm wrong, but the permission change shouldn't have any effect on the LFS build (it didn't for me). Alex On Thu, Dec 20, 2012 at 3:17 AM, JIA Pei jp4w...@gmail.com wrote: Hi, all: Sorry for bugging all of you again. I'm now preparing Virtual Kernel File systems, please refer to page http://www.linuxfromscratch.org/lfs/view/development/chapter06/kernfs.html However, whenever I tried to run the last command on this page if [ -h /dev/shm ]; then rm -f $LFS/dev/shm mkdir $LFS/dev/shm fi mount -vt tmpfs shm $LFS/dev/shm It always kill the Chromium web browser directly, and Chrome will never come back to life. 1) Chrome is not able to be found in running processes. 2) I can never restart Chrome again. Can anybody help to explain why it is so? cheers Pei -- Pei JIA Email: jp4w...@gmail.com cell:+1 604-362-5816 Welcome to Vision Open http://www.visionopen.com -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] LFS Issues with Windows 8
Hello all, I have been transferring an LFS system on a USB drive around various computers and it works for all except a new laptop running Windows 8. In that case, the BIOS (or is it UEFI?) does not read (or reads and discards) the grub loader on the USB. There is no way to select the USB drive as a booting option. I have plugged in other USBs with Ubuntu and Fedora on this same laptop and they are recognized. I think this has something to do with the new secure boot mandate by Microsoft. The interesting thing is that in my bios settings it is displayed as disabled. What is different about the LFS system that the BIOS thinks can be malicious? Is it the kernel that needs to be officially signed or the loader (GRUB)? If this is not a secure boot issue (it does say it's disabled in bios) what else can be the problem? It probably is irrelevant but the bios on the Windows 8 laptop is Aptio 2.16. On another laptop (windows 7) I have an earlier version of Aptio (I think 2.06) and the USB is listed as boot option. Any insight will be much appreciated, Thanks -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Booting LFS Error Kernel Panic
Hello all,
I am having a hard time booting my LFS system, which is on a USB drive. I
installed grub on /dev/sdc (the usb relative to the host) and the bios
successfully finds GRUB. After around 2.3 seconds, the boot process hangs
after printing what I believe to be a trace call. Interestingly, one time
when I booted the trace call was short enough for me to write down the
error which I can't normally see due to the length of the trace prints.
Here is the error:
Kernel panic-not syncing: VFS: Unable to mount root fs on unknown block(0,0)
What exactly does unknown block(0,0) mean?
The problem appears to be that the kernel can't find the root file system.
How can that be a problem, if the kernel, which is ON the root file system,
was found and ran?
Here is the grub.cfg file:
# Begin /boot/grub/grub.cfg
set default=0
set timeout=5
insmod ext2
set root=(hd0,1)
menuentry GNU/Linux, Linux 3.7-lfs-SVN-20121212 {
linux /boot/vmlinuz-3.7-lfs-SVN-20121212 root=/dev/sda1 ro
}
I believe the USB is always sda because to boot I do a manual boot override
and select USB from the BIOS menu. The grub command line also confirms this.
Searching online, there were some suggestions that the kernel was compiled
without support for necessary file systems and hardware. I check my config
file for the kernel and found all the important options to be set to yes
(USB_mass_storage, ext3 filesystem, USB UHCI, USB OHCI, and several scsi
ones). There are however many USB options that are not set. Are there any
specific ones that should be set for the kernel to load the root filesystem?
Also, I've tried unsuccessfully to read more of the boot output by two
methods: increasing the resolution and scrolling back. The scroll back
buffer is set to yes in the kernel config yet shift page down and shift
page up do nothing. Also, vga=791 is deprecated and I haven't been able to
get any effect by using set vgxpayload=1024x728.
How can I read the boot print outputs without a high speed camera?
Thanks,
Alex
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Booting LFS Error Kernel Panic
I got it to work! Turns out that the root file system changes to /dev/sdc1
after all the harddisks are found so changing the line root=/dev/sda1 to
root=/dev/sdc1 and adding a rootdelay successfully booted the system!
Now it would be nice for it to work using UUIDs so the booting can
be independent of host system.
Also, the scrollback buffer does work just not when the kernel has crashed.
I am sorry for the long kind of useless post but if anyone has anything to
add please feel free.
On Mon, Dec 17, 2012 at 5:24 PM, Alexander Spitzer aes...@cornell.eduwrote:
Hello all,
I am having a hard time booting my LFS system, which is on a USB drive. I
installed grub on /dev/sdc (the usb relative to the host) and the bios
successfully finds GRUB. After around 2.3 seconds, the boot process hangs
after printing what I believe to be a trace call. Interestingly, one time
when I booted the trace call was short enough for me to write down the
error which I can't normally see due to the length of the trace prints.
Here is the error:
Kernel panic-not syncing: VFS: Unable to mount root fs on unknown
block(0,0)
What exactly does unknown block(0,0) mean?
The problem appears to be that the kernel can't find the root file system.
How can that be a problem, if the kernel, which is ON the root file system,
was found and ran?
Here is the grub.cfg file:
# Begin /boot/grub/grub.cfg
set default=0
set timeout=5
insmod ext2
set root=(hd0,1)
menuentry GNU/Linux, Linux 3.7-lfs-SVN-20121212 {
linux /boot/vmlinuz-3.7-lfs-SVN-20121212 root=/dev/sda1 ro
}
I believe the USB is always sda because to boot I do a manual boot
override and select USB from the BIOS menu. The grub command line also
confirms this.
Searching online, there were some suggestions that the kernel was compiled
without support for necessary file systems and hardware. I check my config
file for the kernel and found all the important options to be set to yes
(USB_mass_storage, ext3 filesystem, USB UHCI, USB OHCI, and several scsi
ones). There are however many USB options that are not set. Are there any
specific ones that should be set for the kernel to load the root filesystem?
Also, I've tried unsuccessfully to read more of the boot output by two
methods: increasing the resolution and scrolling back. The scroll back
buffer is set to yes in the kernel config yet shift page down and shift
page up do nothing. Also, vga=791 is deprecated and I haven't been able to
get any effect by using set vgxpayload=1024x728.
How can I read the boot print outputs without a high speed camera?
Thanks,
Alex
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
[lfs-support] Installation of Bash 5.15 Error on make
Hello all, I am on section 5.15.1 (installing bash) on LFS version 7.2 and I am receiving an error after running make: $ make -j yacc -d ./parse.y make: execvp: yacc: Permission denied make: *** [y.tab.c] Error 127 I have encountered this before and I attempted to get around by sudo, but that turned out to be a bad idea as the bash binaries were linked to libraries on the host system. After doing a fresh start I am once again confronted by this error. I suspect this has something to do with the yacc link. readlink -f /usr/bin/yacc - /usr/bin/yacc And here is /usr/bin/yacc: #! /bin/sh exec '/usr/bin/bison' -y $@ Is this not a script executing bison as specified in the host requirements? If not, how should /usr/bin/yacc look? Is there anything else that may be causing the permission denied error? Thanks, Alex -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Installation of Bash 5.15 Error on make
Hi Chris, Thanks for your reply. ls -l /usr/bin/yacc gives: -rw-r--r-- 1 root root 41 Dec 13 19:13 /usr/bin/yacc -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Installation of Bash 5.15 Error on make
On Sat, Dec 15, 2012 at 3:10 AM, Chris Staub ch...@beaker67.com wrote: On 12/15/2012 03:03 AM, Alexander Spitzer wrote: An additional piece of information that might be important: The patch asked for in the book is bash-4.2-fixes-8.patch while the one I have from the website and that one that I applied is bash-4.2-fixes-10.patch Could that be the cause of the problem? That is extremely unlikely, though since you are saying you are doing something differently than what's in the book, I need to ask how else (no matter how trivial it might seem) you are deviating from the book's instructions. Also, you're saying the book mentions a fixes-8 patch as stated in the 7.2 book - that specific patch is in fact available - it's even linked right in the book. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page I used the sources in wget-list and the list had the fixes-10.patch. I hope that doesn't turn out to be the issue. Other than that, the only thing I can think of is during the make of the check package, I received a undefined reference to pthread. error in the directory tests, which I fixed by: cd tests open the makefile and add -lpthread to the variable CFLAGS after that it built properly. The book mentions the swap partition but I only made 1 ext3 3GB sized partition on a 4GB USB stick. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Installation of Bash 5.15 Error on make
It worked! Thank you so much! For reference I also had to edit /usr/bin/yacc to exec '/usr/local/bin/bison' -y $@ since there was no bison at all in /usr/bin On Sat, Dec 15, 2012 at 3:15 AM, Chris Staub ch...@beaker67.com wrote: On 12/15/2012 03:11 AM, Alexander Spitzer wrote: Hi Chris, Thanks for your reply. ls -l /usr/bin/yacc gives: -rw-r--r-- 1 root root 41 Dec 13 19:13 /usr/bin/yacc That explains it, that script is not executable. chmod a+x /usr/bin/yacc and it should work. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Installation of Bash 5.15 Error on make
I am definitely using the development source while reading 7.2 :X This might be why check didn't build smoothly. I'll carry on for now but if I encounter any weird problems I'll know why. On Sat, Dec 15, 2012 at 3:27 AM, Chris Staub ch...@beaker67.com wrote: On 12/15/2012 03:18 AM, Alexander Spitzer wrote: I used the sources in wget-list and the list had the fixes-10.patch. I hope that doesn't turn out to be the issue. Other than that, the only thing I can think of is during the make of the check package, I received a undefined reference to pthread. error in the directory tests, which I fixed by: cd tests open the makefile and add -lpthread to the variable CFLAGS after that it built properly. The book mentions the swap partition but I only made 1 ext3 3GB sized partition on a 4GB USB stick. The wget-list in LFS 7.2 does in fact also have the fixes-8 patch, so it looks like you are doing something weird with mixing 7.2 and the development book. I don't know if this is the specific cause of any of your issues, but first thing I'd suggest would be to go back to the beginning and only use 7.2. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Freeing space for installation of gcc in chapter 6
Hello all, The gcc installation in chapter 6 is listed as requiring 2.0 GB of free space. However, I only have 1.4 GB available :( Are there any files or libraries that are not needed and can SAFELY be deleted (maybe in /tools)? I am hesitant to touch anything. The make runs fine. It is during the check that the messages No space left on device start appearing. Perhaps there is something that can be deleted after the make command to save space? Also, is it possible to expand the partition without altering any data? I have about 1 GB left to go (I made a 3 GB partition on a 4 GB USB drive). Thanks, Alex -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Chroot failure: bash not found
Hello all, I am on section 6.4, entering the chroot environment, in LFS Book 7.2 and when i attempt to chroot I get the following error: /tools/bin/env: /tools/bin/bash: No such file or directory This seems to be not too rarely encountered problem but all the diagnostic checks that I've found seem to be okay: The sanity check gives the following: [Requesting program interpreter: /tools/lib64/ld-linux-x86-64.so.2] Running readelf -e /tools/bin/env | grep interpreter gives the following: [Requesting program interpreter: /tools/lib64/ld-linux-x86-64.so.2] I read about a specs patch for gcc that is related to this problem, but I could not find it in this version of the book. I could not find a specs file in the host directory either. This problem is very bizarre to me because there is definitely a bash binary in /tools/bin. If anyone can point me in the right direction or try to help me understand what is going on, that would be great. Thanks, Alex -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Chroot failure: bash not found
Hello Michael, Thanks for your reply. Here is the output: -rwxr-xr-x 1 root root 930472 Dec 13 22:58 /tools/bin/bash and: GNU bash, version 4.2.39(1)-release (x86_64-unknown-linux-gnu) Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software; you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. I am running it as root but I am not sure if I entered root the correct way. From my daily user I typed sudo -i and entered my root password. The command su - didn't work for me because I do not know the root user password (which should be different from MY root/sudo password). In addition, if it may pertain in any way, the LFS partition is on a 4GB USB flash drive. On Fri, Dec 14, 2012 at 7:46 PM, Michael E. Maher mich...@maheronline.co.uk wrote: Hello Alex, Could you send the output of: $ ls -l /tools/bin/bash $ /tools/bin/bash --version Might be a permissions problem. Also are you running the 'chroot' command as the root user? Thanks, Michael On Fri, 2012-12-14 at 19:22 -0500, Alexander Spitzer wrote: Hello all, I am on section 6.4, entering the chroot environment, in LFS Book 7.2 and when i attempt to chroot I get the following error: /tools/bin/env: /tools/bin/bash: No such file or directory This seems to be not too rarely encountered problem but all the diagnostic checks that I've found seem to be okay: The sanity check gives the following: [Requesting program interpreter: /tools/lib64/ld-linux-x86-64.so.2] Running readelf -e /tools/bin/env | grep interpreter gives the following: [Requesting program interpreter: /tools/lib64/ld-linux-x86-64.so.2] I read about a specs patch for gcc that is related to this problem, but I could not find it in this version of the book. I could not find a specs file in the host directory either. This problem is very bizarre to me because there is definitely a bash binary in /tools/bin. If anyone can point me in the right direction or try to help me understand what is going on, that would be great. Thanks, Alex -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Chroot failure: bash not found
Hi Ken, Running ldd /tools/bin/bash gives: linux-vdso.so.1 = (0x7fff3d955000) libtinfo.so.5 = /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f39676b7000) libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f39674b3000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f39670f3000) /lib64/ld-linux-x86-64.so.2 (0x7f39678ff000) which is bad because /tools/lib is nowhere to be found. However, checking a later package such as grep gives: linux-vdso.so.1 = (0x7fffe7bff000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f7eb0a62000) /tools/lib64/ld-linux-x86-64.so.2 = /lib64/ld-linux-x86-64.so.2 (0x7f7eb0e42000) which I'm assuming is good. The result for the other packages is similar to the one for grep. Is bash the only package with a problem? Or should the ONLY libraries listed from a ldd check be in /tools/bin (this would mean that EVERY package is improperly installed) On Fri, Dec 14, 2012 at 8:09 PM, Michael E. Maher mich...@maheronline.co.uk wrote: That should be fine, as long as it's not FAT formatted. The partition is ext3. I'm almost positive I only took a break after finishing chapter 5. Thought it seems that bash is the problem, is it possible that I didn't resume the environment properly for chapter 6? Thanks for the help. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Chroot failure: bash not found
Hi Simon, I think that's exactly the problem. On Fri, Dec 14, 2012 at 8:45 PM, Simon Geard delga...@ihug.co.nz wrote: No such file or directory doesn't always refer to the actual program you ran (/tools/bin/bash) - it sometimes means the interpreter for the program can't be found. If you use the same readelf command on /tools/bin/bash, what does it tell you the interpreter is for that program? And does it exist? readelf -l /tools/bin/bash | grep interpreter gives: [Requesting program interpreter: /lib64/ld-linux-x86-64.so.2] which is NOT what we want (/tools/lib64/...) Other binaries give the correct: [Requesting program interpreter: /tools/lib64/ld-linux-x86-64.so.2] Also, what happens if you try running /tools/bin/bash from outside the chroot, instead of inside it? Does it work there? It works from the outside because there IS a /lib64/ld-linux-x86-64.so.2. I'm assuming it doesn't work from the inside (i.e. chroot command gives an error) because it can't get to the interpreter requested: /lib64/ld-linux-x86-64.so.2 Now I have to try and figure out how to fix the bash binary to look for the correct interpreter. If there's anything wrong with my reasoning please don't hesitate to correct me. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Chroot failure: bash not found
On Fri, Dec 14, 2012 at 9:45 PM, Ken Moffat zarniwh...@ntlworld.com wrote: At the moment, I don't recognize your results. Usually, people who get the correct results from the sanity checks get a good build. Perhaps there is something different about _how_ you built this. What host distro are you using ? Did you check all the host system requirements ? But, in the absence of any other information (your loader in /tools/lib64 apparently using a loader in /lib64 really perplexes me!), I don't think I know what is wrong. Maybe someone else will recognize the symptoms. Did you run the sanity check after gcc in chapter 5 ? ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page I ran the ldd command from my user, rather than the lfs user. My apologies! Sorry if this caused confusion. ldd /tools/bin/grep now gives: linux-vdso.so.1 (0x7fff3658a000) libc.so.6 = /tools/lib/libc.so.6 (0x7fbd657d4000) /tools/lib64/ld-linux-x86-64.so.2 (0x7fbd65b79000) and for bash (same thing as before): linux-vdso.so.1 = (0x7fff3148) libtinfo.so.5 = /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f48f0234000) libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f48f003) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f48efc71000) /lib64/ld-linux-x86-64.so.2 (0x7f48f045b000) I did find another clue: when running make for the bash package I ran into a Permission denied error for yacc and I somehow sudoed my way around it. Perhaps this resulted in the wrong libraries being linked because I was not the lfs user. Will try again and reply back. Thanks for your help and sorry again for wasting your time with my silly mistakes. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Chroot failure: bash not found
On Fri, Dec 14, 2012 at 11:14 PM, Simon Geard delga...@ihug.co.nz wrote: Does it work if you simply rebuild bash, according to the instructions in the book? No need to actually install it - just run the steps up to make, and run readelf on the resulting binary in order to see if it's valid. Also, someone else asked you to run ls -l /tools/bin/bash, but I don't see the output of that command in any of your emails. Might be important? Simon. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page Make is the step that fails for me. Initially it gave an error like yacc: Permission denied but now it gives the following error: /bin/sh: bashbug: Permission denied make: *** [bashbug] Error 1 ls -l /tools/bin/bash gives (run as user lfs): -rwxr-xr-x 1 root root 3184266 Dec 15 03:52 /tools/bin/bash I am suspicious about the links. readlink -f /usr/bin/yacc gives /usr/bin/yacc BUT /usr/bin/yacc contains: #! /bin/sh exec '/usr/bin/bison' -y $@ which LOOKS like a script executing bison. Is it executing the correct bison? readlink -f /bin/sh gave: /bin/dash until I changed it moments ago with sudo rm /bin/sh and sudo ln -s /bin/bash /bin/sh now readlink -f /bin/sh correctly gives: /bin/bash Does the fact that it pointed to dash mean big trouble for all packages built during chapter 5? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
