On 12/3/09, Simon Geard wrote:
> Wow... if you *do* get a new LFS build running on that, I'd be curious
> to know how long it took...
My first guess is 11 days or so.
Calculating from:
http://www.linuxfromscratch.org/~sbu
MHz=100
one_sbu=5848
lfs_6_5_sbus=153
seconds=899422
time=10,9:50:22
--
ht
On 11/29/09, linux fan wrote:
> The "VFS can't find ..." suggests that the boot loader (grub/lilo)
> done its job and the kernel was loading until it choked on the
> filesystem fstab told it,
If the message is exactly:
Kernel panic -not syncing VFS: unable to mount root
On 11/29/09, Alberto Hernando wrote:
> ... The error is the same, VFS
> can't find a valid root system, "please add a valid root option". I
> .. and /etc/fstab is as the book says.
If /etc/fstab is as the book says (verbatim), it won't work.
You must interpolate
/dev/ / defaults
On 11/28/09, Baho Utot wrote:
> make test | tee $CURRDIR/06.58.Check.log
> make install | tee $CURRDIR/06.58.Install.log
Logging helps so much when things go wrong.
As already mentioned
> Scripting an LFS build is *hard*
> 1. Use jhalfs. That is the most consistent way to do things
> and it k
On 11/28/09, stosss wrote:
> I am only using the lfs 6.3 LiveCD (this is the newest and last lfs
> LiveCD released) so I will have a working environment to build lfs
Unless I am mistaken, everything in ch6-8 is done within chroot.
Then it is imperative to be certain that
6.2. Preparing Virtual Ke
On 11/23/09, su.sinnes wrote:
> Hi im stuck with grub, as soon as i restart i get into the grub shell
I reserve the right to be wrong, but ...
While you can't compile the old grub under 64bit, you could still use
the old grub ... can't you?
--
http://linuxfromscratch.org/mailman/listinfo/lfs-sup
On 11/25/09, su.sinnes wrote:
> it did not work i think it's because im on a laptop and i need to hold
> down the fn key to use prt sc and sysrq, and it is not supported.
> neither did ctrl + s
OOPS, I might have typed before I had my coffee ...
I might have meant the "Pause Break" key ... let m
On 11/25/09, su.sinnes wrote:
> is there anything i can do?
We've all been down this road before ... whatever we do, grub doesn't
seem to work ...
You have gotten grub to load a kernel ... that is getting close.
The key marked "PrtScr SysRq" can stop the display from scrolling
while booting --
On 11/24/09, Bruce Dubbs wrote:
> linux fan wrote:
>> Intending to umount and roll back, I get:
>>
>> df -ha
>> FilesystemSize Used Avail Use% Mounted on
>> /dev/sda11 11G 7.6G 2.7G 74% /
>> /proc0 0 0
On 11/24/09, Bruce Dubbs wrote:
> I don't know where you live, but I've seen them given away as
> promotions. Otherwise they are very common at $10 or less.
Some day, I might get one.
I don't care what udev does as long as it doesn't cause problems.
I've got the 16 fd things in dev and was never
On 11/24/09, Bruce Dubbs wrote:
> If you are getting a kernel panic, it's not grub. Grub did it's job and
> loaded the kernel, then the kernel had a problem.
Agree.
But, there are 2 places that cause kernel panic:
1) grub's kernel/linux line, the root=/dev/[is_incorrect] parameter
2) fstab's: [
On 11/24/09, Ken Moffat wrote:
> The names of the devices in grub and within linux are two separate
> things. For an explanation of why /dev/hdX becomes /dev/sdX
> see Simon's response to another thread.
>
> /dev/hdX (from the old IDE drivers) is now regarded as legacy, except
> for old ppc maci
On 11/24/09, Bruce Dubbs wrote:
> That works for you, but for most people, it's far easier to use a usb
> thumb drive with capacities in GB to do the same thing.
>
I know that it is impossible to believe, but I have yet to purchase my
first usb thumb drive.
--
http://linuxfromscratch.org/mailman/
On 11/24/09, Bruce Dubbs wrote:
> I'd start over. Having a suspect base is not a good idea. Try jhalfs
> to automate the build.
Yes jhalfs has been working for me.
Starting over from mke2fs.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/f
On 11/24/09, Simon Geard wrote:
> On Mon, 2009-11-23 at 18:29 -0600, al...@verizon.net wrote:
>> The last thing is to start a flame here; I still see a
>> need for floppies on Linux
Agree there is a need for floppies.
I just used a floppy to boot memtest86+ which found a bad memory bank
was bugg
On 11/24/09, Jeremy Henty wrote:
> On Mon, Nov 23, 2009 at 08:24:53AM -0700, Trent Shea wrote:
>
>> It really depends on how you build your kernel; hd* is still valid,
>> as far as I'm aware.
>
> That's not my experience. My /dev/hd* devices disappeared when I
> upgraded 2.6.27 to 2.6.28
On 11/24/09, Bruce Dubbs wrote:
> linux fan wrote:
>> On 11/24/09, Bruce Dubbs wrote:
>>> Have you tried booting into memtest86+
>>> and checking your memory?
Thanks for that!
Eliminated one memory bank at a time until it didn't fail before test #5.
Rolled back
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.ht
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
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
Uns
On 11/23/09, Bruce Dubbs wrote:
> To check things out a little more, you can try
Er, uh, excuse my dumbness, but ...
did you mean like:
ldd /usr/bin/make
or like:
ldd /tools/bin/make
or like:
/tools/bin/ldd /tools/bin/make
... By the way, this is without the stripping ...
/tools/bin/ldd /too
On 11/23/09, Bruce Dubbs 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: 77 total, 2 runnin
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
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
Building development book in chapter06
Tar keeps saying:
tar: Record size = 8 blocks
tools/bin/tar --version
tar (GNU tar) 1.22
Did I miss something?
Is there a fix?
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See th
On 11/21/09, Kyle Brennan wrote:
> make[2]: *** [/tools/include/linux/errno.h] Error 1
> make[2]: Leaving directory `/mnt/lfs/tools/glibc-2.5.1/iconv'
> make[1]: *** [iconv/subdir_lib] Error 2
> make[1]: Leaving directory `/mnt/lfs/tools/glibc-2.5.1'
> make: *** [all] Error 2
Don't forget that it
On 11/20/09, su.sin...@mail.com wrote:
>
> What should i do now?
>
> menuentry "GNU/Linux, Linux 2.6.30.2" {
> insmod ext2
> set root=(hd0,1)
> search --no-floppy --fs-uuid --set e4adbac2-a338-4305-bafe-73f2adb307da
> linux/boot/vmlinux-2.6.30.2 root=/dev/sda1 ro
> }
What is
On 11/19/09, Bruce Dubbs wrote:
> We changed the cp command for the kernel to:
>cp -v arch/x86/boot/bzImage /boot/vmlinux-2.6.31.6-lfs-SVN-20091117
It worked for me to just make a symlink in boot instread ot remaking
kernel just to get a new name.
ln -s lfskernel-2.6.31.6 vmlinux-2.6.31.6
--
On 11/19/09, Daniel Jäderberg wrote:
> so then i tried to install grub2 as suggested. and i followed the hint.
> 3) grub-mkconfig -o /boot/grub/grub.cfg
>
> and i still get nothing when i do the grub-mkconfig -o /boot/grub/grub.cfg
grub2 wants the kernel name to begin with vmlinux or vmlinuz inst
On 11/12/09, Bruce Dubbs wrote:
> The problem with GRUB Legacy is that it didn't support 64-bit systems --
> at least it have to be built from a 32-bit system. This is a major
> drawback in that virtually every new Intel/AMD system is 64-bit capable.
Ok, maybe I just keep this in my back pocket
On 11/11/09, Bruce Dubbs wrote:
>
>> # grub-install --grub-setup=/bin/true /dev/sda11
>
> This should be /dev/sda, but I see you tried that too.
Now I really _want_ to install grub on individual partitions so that I
can chainloader to different installations like grub-legacy has let me
do for ye
On 11/12/09, Bruce Dubbs wrote:
> Bruce Dubbs wrote:
>
>> I just had an aha!
>>
>> Try rebuilding grub without the --disable-largefile switch.
That worked!
Now some more things.
.. I needed to suppress probing the ancient mobo ide drive that is not
connected to avoid a 2 minute wait for it not t
On 11/12/09, Bruce Dubbs wrote:
> Bruce Dubbs wrote:
>
>> I just had an aha!
>>
>> Try rebuilding grub without the --disable-largefile switch. Your
>> partition is 11G and that probably is causing it to fail. I don't know
>> what the threshold is. I'll investigate.
>
> man 2 open
>
>O_LARGE
On 11/11/09, Bruce Dubbs wrote:
>
> OK, I assume you are still within the chroot environment.
No, this system has been running regularly with grub1 since January 2009.
> What is the result of:
>
> ls -l /dev/sd*
r...@lfs:~# ls -l /dev/sd*
brw-rw 1 root disk 8, 0 2009-11-11 18:13 /dev/sda
br
Since lfs dev has switched to grub2,.I want to try it.
I don't know why grub2 fails to work properly on my system.
It seems to choke on partitions/filesystems on my sata hard drives.
I built grub-1.97 exactly from the instructions in lfs dev.
Searching google proved fruitless in solving the bizarr
101 - 135 of 135 matches
Mail list logo
