I went through the lfs 6.5 book and copied and pasted all the commands
in the book to a series of shell scripts. I only made changes where it
was necessary like with stuff like hda1 and hda5 other than that I
left the commands in the book in tact. I used two partitions hda1 and
hda5. The lfs build
Hi, I had a similar problem and the solution was to recompile the kernel
with the correct driver for the hard disk. In my case the hard disk was a
vmware partition. In your case seems that the kernel can't read the hda1. If
you can, try to do an lspci and look for what HD you have than check you
Also for the record the book LFS 6.5 does not tell you that the
entries in menu.lst and fstab need to be sd now and not hd.
LFS 6.5 chapter 8.4.2 the last entry before EOF should be sdxx and not hdxx
cat boot/grub/menu.lst EOF
# Begin /boot/grub/menu.lst
# By default boot the first menu
On Monday 23 November 2009 21:27:37 su.sinnes wrote:
Hi im stuck with grub, as soon as i restart i get into the grub shell
and when i type boot it says no loaded kernel.
but if i do:
1) made a file under /boot/grub/device.map as Bruce
(hd0) /dev/sda
2) grub-install --root-directory=/boot/
On Monday November 23 2009 05:19:32 am stosss wrote:
Also for the record the book LFS 6.5 does not tell you that the
entries in menu.lst and fstab need to be sd now and not hd.
It really depends on how you build your kernel; hd* is still valid, as
far as I'm aware.
--
Trent.
--
On Sunday November 22 2009 11:58:26 pm Simon Geard wrote:
I'm afraid I can't
be more specific, but it may be that your X libraries are too old for
KDE (or less likely, too new).
I can confirm the 4.3 branch built against Xorg-7.5 for me.
--
Trent.
--
I solved that problem by doing this:
grub-install --root-directory=/boot/ /dev/sda
grub-mkconfig -o /boot/boot/grub/grub.cfg
but now i got a new problem.
kernel panic , not syncing:VFS:unable to mount root
fs on unknown-block(2,0)
I read that i might need to install SATA drivers for it to
On 11/23/2009 07:06 AM, stosss wrote:
Just for the record.
The grub configuration commands won't work in chroot. They do work
when you get out of chroot. There is nothing in the chapter to tell
you to do that.
Yes they do. If they didn't work for you, my guess is that /dev probably
wasn't
stosss wrote:
All Right! I did what you suggested and now I have a command prompt!
Congratulations on being a new LFS user!
Three cheers!
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made
Segmentation fault occurs right after stripping in chapter05.
I am building lfs trunk using jhalfs trunk.
The stripping step succeeds, but the next step which is to
restore-luser-env errors. The restore-luser-env step only has to copy
the saved $(LUSER_HOME)/.bashrc.XXX back to .bashrc, but that
On Mon, 23 Nov 2009 16:02:12 -0500
linux fan linuxscra...@gmail.com wrote:
Segmentation fault occurs right after stripping in chapter05.
I am building lfs trunk using jhalfs trunk.
The stripping step succeeds, but the next step which is to
restore-luser-env errors. The restore-luser-env
On 11/23/09, Aleksandar Kuktin wrote:
As I have not tried jhalfs, a question, just to be clear: you are
running the make command via automated means, after stripping, in a
single slurp (from the same script)?
jhalfs automates from start to finish.
I have used it to build LFS 6.2.0, 6.3, and
linux fan wrote:
Last night, I tried restarting make after it came back to the shell
prompt and all kinds of system problems occurred :
It barfed badly when trying to umount the build dir
System choked on attempt to shutdown
It just got the situation to be unstable
The sys.log
On 11/23/09, Bruce Dubbs bruce.du...@gmail.com wrote:
Is there any possibility
that there could be a memory or disk problem? Are you sure you have
enough disk space?
Good thinking, but doesn't seem to be space issue:
top - 19:43:27 up 11:00, 1 user, load average: 1.06, 1.03, 1.04
Tasks:
Alex:
In the past, I was able to avoid creation
of unnecessary fd nodes.
Mike McCarty:
In what sense unnecessary?
Do your floppy drives not support those modes?
There are tools which use the name of the device
to select their mode of operation, and
if you don't have a /dev node for that
I went through the menuconfig 4 times. Compiling/not compiling scsi made no
difference when it came to error I was getting.
I am not at the computer now and won't be for several more hours.
Where is the setting and why did changing the two files and three entries
from hd to sd work? I don't have
I must clarify my confusion.
I am supposing that you would like for me to roll back to the point
where it is to be stripped.
Then strip.
Then run /tools/command on /tools/file
Correct?
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
On 11/23/09, Bruce Dubbs wrote:
To check things out a little more, you can try
Note: I had built up thru gmp-ch6 which is in the chroot
Intending to umount and roll back, I get:
df -ha
FilesystemSize Used Avail Use% Mounted on
/dev/sda11 11G 7.6G 2.7G 74% /
/proc
linux fan wrote:
On 11/23/09, Bruce Dubbs wrote:
To check things out a little more, you can try
Note: I had built up thru gmp-ch6 which is in the chroot
Intending to umount and roll back, I get:
df -ha
FilesystemSize Used Avail Use% Mounted on
/dev/sda11 11G
On 11/24/09, Bruce Dubbs wrote:
Have you tried booting int memtest86+
and checking your memory?
I don't know whereis or howto memtest86+.
I guess this will be a multi-day adventure.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
20 matches
Mail list logo
