Hi,
I log out (and shutdown the computer also) between the two chapters 5 and 6.
When I logged in as root I noted that the environment wasn't the correct one
(e.g. LFS wasn't defined), so I hit the command
su - lfs
and returned back to root.
This way the environment was correct (for me) but the
On Wed, Feb 17, 2010 at 3:40 AM, Louis Davies wrote:
> Hi,
>
> I log out (and shutdown the computer also) between the two chapters 5 and 6.
>
> When I logged in as root I noted that the environment wasn't the correct one
> (e.g. LFS wasn't defined), so I hit the command
> su - lfs
> and returned b
On Tue, 2010-02-16 at 23:10 +, aztec...@comcast.net wrote:
> Based on this setup, is it possible to have /root and /boot on two
> separate drives (in my case '/root' was in #2, and '/boot' was on
> #1)?
Hang on, do you really mean '/root', i.e the root user's home directory?
Or do you mean th
On 16/02/10 23:10, aztec...@comcast.net wrote:
> Based on this setup, is it possible to have /root and /boot on two separate
> drives (in my case '/root' was in #2, and '/boot' was on #1)? The reason I
> ask is because I attempted to do an install using this scheme but it gave me
> error 17 or 15
Here we are, though I'm not a fat hard driver as many of you are.
/dev/hda 80gb
/dev/hdc 40gb
hda:
/dev/hda1 16mb /boot
/dev/hda2 20gb /
/dev/hda3 20gb /
/dev/hda4 + /dev/hdc1 = /dev/md0 80gb /home
/dev/hda5 + /dev/hdc2 = remaining swap for roughly 1.5gb
hda2 and hda3 are used as current root
> On 02/16/2010 06:46 PM, Timothy Legg wrote:
>> Hello,
>>
>> Thanks for the wonderful advice last time.
>>
>> I have moved along. On chapter 5.12.1 where I 'make test', I get back 7
>> failures, output is at end of this message.
>>
>> Tis is similar to two occurances in previous threads, but I am
The system is a AMD phenom II 820 X4 Quad core with 8 GB ram
Host is Slackware 12.2 - only sees 4 GB Ram non pae kernel
Is this ok?
gcc tst-cpuclock2.c -c -std=gnu99 -fgnu89-inline -O2 -O3 -Wall -Winline
-Wwrite-strings -fmerge-all-constants -g -march=i486 -mtune=native -pipe
-Wstrict-prototype
Baho Utot wrote:
> The system is a AMD phenom II 820 X4 Quad core with 8 GB ram
> Host is Slackware 12.2 - only sees 4 GB Ram non pae kernel
>
> Is this ok?
>
> /Build/glibc-build/rt/tst-cpuclock2 >
> /Build/glibc-build/rt/tst-cpuclock2.out
> make[4]: *** [/Build/glibc-build/rt/tst-cpuclock2.out
Bruce Dubbs wrote:
> Baho Utot wrote:
>
>> The system is a AMD phenom II 820 X4 Quad core with 8 GB ram
>> Host is Slackware 12.2 - only sees 4 GB Ram non pae kernel
>>
>> Is this ok?
>>
>> /Build/glibc-build/rt/tst-cpuclock2 >
>> /Build/glibc-build/rt/tst-cpuclock2.out
>> make[4]: *** [/Build
On 2/17/10, Randy McMurchy wrote:
> If the community's expectations are that we have the most current
> release of every package in the most recent BLFS book, then the
> expectations are too high and are unreasonable.
I agree.
I think the most important thing is that following step by step
in th
On Wed, Feb 17, 2010 at 9:16 AM, Baho Utot wrote:
> The system is a AMD phenom II 820 X4 Quad core with 8 GB ram
This seems to be a common Phenom II problem, as Trac user ringlis got
the same error, albeit with LFS 6.6-rc1 and Glibc-2.11.1. Of cource,
it could be heavy system load or for other rea
William Immendorf wrote:
> On Wed, Feb 17, 2010 at 9:16 AM, Baho Utot wrote:
>
>> The system is a AMD phenom II 820 X4 Quad core with 8 GB ram
>>
> This seems to be a common Phenom II problem, as Trac user ringlis got
> the same error, albeit with LFS 6.6-rc1 and Glibc-2.11.1. Of cource,
>
Baho Utot wrote:
> cat /mnt/lfs/Build/glibc-build/rt/tst-cpuclock2.out
> live thread clock fffdd58e resolution 0.1
> live thread before sleep => 0.53078
> self thread before sleep => 0.000169320
> live thread after sleep => 0.501525776
> self thread after sleep => 0.000186263
> proce
Baho Utot wrote:
> I don't understand how a quad core would be "under heavy system load",
You're right. I've done a bit of research and testing today and I'm
rewriting the error sections.
"The nptl/tst-clock2, nptl/tst-attr3, and rt/tst-cpuclock2
tests have been known to fail. The reason is
Bruce Dubbs wrote:
> Baho Utot wrote:
>
>
>> cat /mnt/lfs/Build/glibc-build/rt/tst-cpuclock2.out
>> live thread clock fffdd58e resolution 0.1
>>
>
>
>> live thread before sleep => 0.53078
>> self thread before sleep => 0.000169320
>> live thread after sleep => 0.501525776
>>
Bruce Dubbs wrote:
> Baho Utot wrote:
>
>
>> I don't understand how a quad core would be "under heavy system load",
>>
>
> You're right. I've done a bit of research and testing today and I'm
> rewriting the error sections.
>
> "The nptl/tst-clock2, nptl/tst-attr3, and rt/tst-cpuclock2
>
I have still not managed to log into my new LFS system. I believe the system is
up, it gets all the way to the login prompt. I can see in sys.log that the root
filesystem gets mounted and I created a swap partition that gets added. So I am
still stuck with the USB not working. My question is, is
brown wrap wrote:
> I have still not managed to log into my new LFS system. I believe the
> system is up, it gets all the way to the login prompt. I can see in
> sys.log that the root filesystem gets mounted and I created a swap
> partition that gets added. So I am still stuck with the USB not
> wo
>
> dhcp is not a part of LFS. There is no reason you
> can't use a static IP
> instead. However, you can build dhcp from
> BLFS if you want.
>
> You will need ot build openssl and openssh and start sshd
> from a boot
> script to log in remotely.
>
> Are you by any chance building this in
I posted my config file yesterday, but didn't know how to get the reference #.
Here it is:
pastebin.com/m4994360d
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
brown wrap wrote:
>
>
> I posted my config file yesterday, but didn't know how to get the reference
> #. Here it is:
> pastebin.com/m4994360d
Nothing jumps out as missing, but can you give us the results of
lspci | grep USB
That may give us a clue.
-- Bruce
--
http://linuxfromscrat
> Nothing jumps out as missing, but can you give us the
> results of
>
> lspci | grep USB
>
> That may give us a clue.
>
> -- Bruce
Here you go:
[r...@localhost boot]# /sbin/lspci |grep USB
00:04.0 USB Controller: nVidia Corporation GeForce 7100/nForce 630i USB (rev a1)
00:04.1 US
On 18/02/10 00:20, brown wrap wrote:
>
>
>
> I posted my config file yesterday, but didn't know how to get the reference
> #. Here it is:
>
>
> pastebin.com/m4994360d
>
In your config you've enabled both OHCI and UHCI. Try just using just UHCI like
so
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB
On Wednesday 17 February 2010 18:13:14 brown wrap wrote:
> > Nothing jumps out as missing, but can you give us the
> > results of
> >
> > lspci | grep USB
> >
> > That may give us a clue.
> >
> >-- Bruce
>
> Here you go:
>
> [r...@localhost boot]# /sbin/lspci |grep USB
> 00:04.0 USB Contr
> > >
> > > lspci | grep USB
> > >
> > > That may give us a clue.
> > >
> > > -- Bruce
> >
> > Here you go:
> I seem to recall a bunch of trial and error to get my first
> kernel built.
>
> --
> Regards,
> Trent.
That lspci output is from a working system.
--
http://linuxf
I posted the last boot. I see a warning regarding the order of loading modules,
but its the errors at the end that is worrisome.
http://pastebin.com/m7950b00b
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See
On Wednesday 17 February 2010 20:11:54 brown wrap wrote:
> I posted the last boot. I see a warning regarding the order of loading
> modules, but its the errors at the end that is worrisome.
>
Have you tried as Andrew suggested?
>From the descriptions while configuring the kernel it sounds like
Yes, the sys.log I attached is a result of leaving one out. It changed the
symptoms slightly, but it still didn't work. I will try leaving the other out
tomorrow. But I have a working Centos system and the kernel that is working has
a config file and I think both were enabled.
I just thought so
brown wrap wrote:
> Yes, the sys.log I attached is a result of leaving one out. It
> changed the symptoms slightly, but it still didn't work. I will try
> leaving the other out tomorrow. But I have a working Centos system
> and the kernel that is working has a config file and I think both
> were en
> Did you compare the CentOS dmesg with the one from LFS?
>
> -- Bruce
Well, dmesg from CentOS doesn't have any errors or warnings.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information
I grepped "USB" from the dmesg file.
http://pastebin.com/d7fba
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
brown wrap wrote:
> I grepped "USB" from the dmesg file.
> http://pastebin.com/d7fba
It looks like an older kernel. What I have is:
[2.362992] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
...
[2.379291] usb usb1: default language 0x0409
[2.379295] usb usb1: New USB
32 matches
Mail list logo
