Need Help - boot fails
I have completed the LFS-6.8 book to the chapter on rebooting to the new LFS system. The kernel appears to load but fails at the point of: [ 1.433897] Freeing unused kernel memory: 400k freed It stops there and a hard reset is required. What is the next step in the boot process. The new LFS system root file system is all on one partition Here is the partition list /dev/sda1 /boot /dev/sda2 swap /dev/sda3 / /dev/sda4 extended /dev/sda5 root of host build system , arch linux -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Need Help - boot fails
On Sun, 25 Sep 2011 08:52:02 -0400 scrat wrote: > I have completed the LFS-6.8 book to the chapter on rebooting to the new > LFS system. > > The kernel appears to load but fails at the point of: > > [ 1.433897] Freeing unused kernel memory: 400k freed > > It stops there and a hard reset is required. You need to recompile your kernel. You need to work on your kernel .config and develop a working kernel that can boot your computer _without_ modules. Andy -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Need Help - boot fails
On 09/25/2011 10:33 AM, Andrew Benton wrote: > On Sun, 25 Sep 2011 08:52:02 -0400 > scrat wrote: > >> I have completed the LFS-6.8 book to the chapter on rebooting to the new >> LFS system. >> >> The kernel appears to load but fails at the point of: >> >> [ 1.433897] Freeing unused kernel memory: 400k freed >> >> It stops there and a hard reset is required. > You need to recompile your kernel. You need to work on your > kernel .config and develop a working kernel that can boot your computer > _without_ modules. > > Andy Ok I will look at the kernel. I used a config file that had booted before on this machine Thanks -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Need Help - boot fails
scrat wrote: > On 09/25/2011 10:33 AM, Andrew Benton wrote: >> On Sun, 25 Sep 2011 08:52:02 -0400 >> scrat wrote: >> >>> I have completed the LFS-6.8 book to the chapter on rebooting to the new >>> LFS system. >>> >>> The kernel appears to load but fails at the point of: >>> >>> [ 1.433897] Freeing unused kernel memory: 400k freed >>> >>> It stops there and a hard reset is required. >> You need to recompile your kernel. You need to work on your >> kernel .config and develop a working kernel that can boot your computer >> _without_ modules. > Ok I will look at the kernel. > > I used a config file that had booted before on this machine One thing you can probably do is use Shift-PgUp to look at earlier screens to see if there are any error messages that might have scrolled off. One suspicious thing is the [ 1.433897] number. My system is not particularly slow, but it has [3.081309] Freeing unused kernel memory: 612k freed The next things that follow on my system are the initialization of the usb HW. I agree with Andy that the kernel config look suspicious. Remember to not use modules for the first time through. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Need Help - boot fails
On 09/25/2011 12:51 PM, Bruce Dubbs wrote: > scrat wrote: >> On 09/25/2011 10:33 AM, Andrew Benton wrote: >>> On Sun, 25 Sep 2011 08:52:02 -0400 >>> scrat wrote: >>> I have completed the LFS-6.8 book to the chapter on rebooting to the new LFS system. The kernel appears to load but fails at the point of: [ 1.433897] Freeing unused kernel memory: 400k freed It stops there and a hard reset is required. >>> You need to recompile your kernel. You need to work on your >>> kernel .config and develop a working kernel that can boot your computer >>> _without_ modules. >> Ok I will look at the kernel. >> >> I used a config file that had booted before on this machine > One thing you can probably do is use Shift-PgUp to look at earlier > screens to see if there are any error messages that might have scrolled off. > > One suspicious thing is the [ 1.433897] number. My system is not > particularly slow, but it has > [3.081309] Freeing unused kernel memory: 612k freed > > The next things that follow on my system are the initialization of the > usb HW. I agree with Andy that the kernel config look suspicious. > Remember to not use modules for the first time through. > > -- Bruce It is a laptop dual core AMD 1600MHz I tried a kernel without modules and it failed at the same place. What does the [ 1.433897] mean? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Need Help - boot fails
That would be the time since the system(kernel) started. IIRC. Sent from my Verizon Wireless BlackBerry -Original Message- From: scrat Sender: lfs-support-boun...@linuxfromscratch.org Date: Sun, 25 Sep 2011 13:56:28 To: LFS Support List Reply-To: LFS Support List Subject: Re: Need Help - boot fails On 09/25/2011 12:51 PM, Bruce Dubbs wrote: > scrat wrote: >> On 09/25/2011 10:33 AM, Andrew Benton wrote: >>> On Sun, 25 Sep 2011 08:52:02 -0400 >>> scrat wrote: >>> >>>> I have completed the LFS-6.8 book to the chapter on rebooting to the new >>>> LFS system. >>>> >>>> The kernel appears to load but fails at the point of: >>>> >>>> [ 1.433897] Freeing unused kernel memory: 400k freed >>>> >>>> It stops there and a hard reset is required. >>> You need to recompile your kernel. You need to work on your >>> kernel .config and develop a working kernel that can boot your computer >>> _without_ modules. >> Ok I will look at the kernel. >> >> I used a config file that had booted before on this machine > One thing you can probably do is use Shift-PgUp to look at earlier > screens to see if there are any error messages that might have scrolled off. > > One suspicious thing is the [ 1.433897] number. My system is not > particularly slow, but it has > [3.081309] Freeing unused kernel memory: 612k freed > > The next things that follow on my system are the initialization of the > usb HW. I agree with Andy that the kernel config look suspicious. > Remember to not use modules for the first time through. > > -- Bruce It is a laptop dual core AMD 1600MHz I tried a kernel without modules and it failed at the same place. What does the [ 1.433897] mean? -- 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: Need Help - boot fails
Hello, On Sun, Sep 25, 2011 at 01:56:28PM -0400, scrat wrote: > I have completed the LFS-6.8 book to the chapter on rebooting to the new > LFS system. > > The kernel appears to load but fails at the point of: > > [ 1.433897] Freeing unused kernel memory: 400k freed > It stops there and a hard reset is required. > >>> You need to recompile your kernel. You need to work on your > >>> kernel .config and develop a working kernel that can boot your computer > >>> _without_ modules. > >> Ok I will look at the kernel. > >> I used a config file that had booted before on this machine > > One thing you can probably do is use Shift-PgUp to look at earlier > > screens to see if there are any error messages that might have scrolled off. > > One suspicious thing is the [ 1.433897] number. My system is not > > particularly slow, but it has > > [3.081309] Freeing unused kernel memory: 612k freed > > The next things that follow on my system are the initialization of the > > usb HW. I agree with Andy that the kernel config look suspicious. > > Remember to not use modules for the first time through. > > -- Bruce > It is a laptop dual core AMD 1600MHz > I tried a kernel without modules and it failed at the same place. > What does the > [ 1.433897] mean? If you have the framebuffer enabled, try turning it off and see what happens. Device Drivers ---> Graphics support ---> < > Support for frame buffer devices Sometimes if there is a mismatch between the driver and video card, the kernel will boot, but the screen will remain black. Best of luck, ae -- My Blog: http://elian001.wordpress.com -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Need Help - boot fails - This cause?
I think I may have found the error of my ways
I am building for i686
When reviewing my build process logs I found this under Chapter 6.16
GCC-4.5.2...
When doing the compile test ie echo main(){} > dummy.c...etc.
From the book:
Next, verify that the new linker is being used with the correct search
paths:
grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'
If everything is working correctly, there should be no errors, and the
output of the last command (allowing for platform-specific target
triplets) will be:
SEARCH_DIR("/usr/i686-pc-linux-gnu/lib")
SEARCH_DIR("/usr/local/lib")
SEARCH_DIR("/lib")
SEARCH_DIR("/usr/lib");
Here is what I have:
SEARCH_DIR("/tools/i686-pc-linux-gnu/lib")
SEARCH_DIR("/usr/lib");
SEARCH_DIR("/lib")
What would cause the SEARCH_DIR to be wrong?
As far as I can tell the readjust of the tools chain occurred without error.
The ouput in my compile of GCC is the same as from the adjust tool chain
step... Is that correct?
If not could please point me (if you can) to the most likely setp I have
errored on if possible.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: Need Help - boot fails - This cause?
On Sun, Sep 25, 2011 at 07:46:54PM -0400, scrat wrote:
>
> I think I may have found the error of my ways
I'm sorry, I disagree.
>
> I am building for i686
>
> When reviewing my build process logs I found this under Chapter 6.16
> GCC-4.5.2...
>
> When doing the compile test ie echo main(){} > dummy.c...etc.
>
> From the book:
>
> Next, verify that the new linker is being used with the correct search
> paths:
> grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'
> If everything is working correctly, there should be no errors, and the
> output of the last command (allowing for platform-specific target
> triplets) will be:
> SEARCH_DIR("/usr/i686-pc-linux-gnu/lib")
> SEARCH_DIR("/usr/local/lib")
> SEARCH_DIR("/lib")
> SEARCH_DIR("/usr/lib");
>
> Here is what I have:
>
> SEARCH_DIR("/tools/i686-pc-linux-gnu/lib")
> SEARCH_DIR("/usr/lib");
> SEARCH_DIR("/lib")
So, on the face of it, libraries in /usr/local/lib will not be
found. But, your problem is a failure to boot - the kernel does not
link to libraries.
The messages you saw on the screen when trying to boot are only
really helpful if you can boot a working kernel on the same machine,
AND if it runs slowly enough for you to be able to read what
happens. Unfortunately, modern desktop machines are probably too
quick for that. The messages don't usually make it into the logs,
so we can't look at logs and hazard a guess at what should come next.
Somebody implied a video problem - that sounds plausible.
You were also advised to avoid modules - in fact, for some things
such as network adaptors (wired ethernet) modules are usually no
problem. The big issues are booting without an initrd (most distros
use intirds, LFS doesn't), and supporting your hardware - as well as
the obvious "build in ext4 or whatever you use" and "enable the
correct [ SATA ] drivers(s) for your chipset(s)" I suppose we should
add "if in doubt, keep the video simple".
kms is a wonderful thing when it works, but a bit of a beast to set
up in some situations, and occasionally liable to break across
kernel upgrades on some hardware (particularly, intel). So, if you
are using it, I suggest that you build an alternative kernel without
it, and use that to help identify where your problem lies. Equally,
even just using a framebuffer might cause problems (on my new
server, I had to fiddle with grub.conf to get a non-blank screen,
and I eventually switched to, I think, vesdafb from radeonfb - on
earlier kernels with my previosu hardware, the framebuffer had worked
fine without specifying anything odd to grub).
I think you said that you had used this config already on your host
system ? If so, is the host using an initrd [ if it is, the config
is probably not adequate for LFS ], and did you use the same version
of the kernel ? Occasionally, things break in newer kernels [ hmm -
if you are already running a *newer* kernel on the host, use the
same version in the new system, don't go back to an older kernel
just because it is in the book ].
ĸ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
Re: Need Help - boot fails - This cause?
On 09/25/2011 08:51 PM, Ken Moffat wrote:
> On Sun, Sep 25, 2011 at 07:46:54PM -0400, scrat wrote:
>> I think I may have found the error of my ways
> I'm sorry, I disagree.
OK I've been completely wrong before ;)
>> I am building for i686
>>
>> When reviewing my build process logs I found this under Chapter 6.16
>> GCC-4.5.2...
>>
>> When doing the compile test ie echo main(){}> dummy.c...etc.
>>
>> From the book:
>>
>> Next, verify that the new linker is being used with the correct search
>> paths:
>> grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'
>>If everything is working correctly, there should be no errors, and the
>> output of the last command (allowing for platform-specific target
>> triplets) will be:
>> SEARCH_DIR("/usr/i686-pc-linux-gnu/lib")
>> SEARCH_DIR("/usr/local/lib")
>> SEARCH_DIR("/lib")
>> SEARCH_DIR("/usr/lib");
>>
>> Here is what I have:
>>
>> SEARCH_DIR("/tools/i686-pc-linux-gnu/lib")
>> SEARCH_DIR("/usr/lib");
>> SEARCH_DIR("/lib")
> So, on the face of it, libraries in /usr/local/lib will not be
> found. But, your problem is a failure to boot - the kernel does not
> link to libraries.
>
> The messages you saw on the screen when trying to boot are only
> really helpful if you can boot a working kernel on the same machine,
> AND if it runs slowly enough for you to be able to read what
> happens. Unfortunately, modern desktop machines are probably too
> quick for that. The messages don't usually make it into the logs,
> so we can't look at logs and hazard a guess at what should come next.
This is a five year old lapdog machine so it is not to beastky fast ;)
> Somebody implied a video problem - that sounds plausible.
No I don't get a blank/black screen I just get a hard crash, the screen
never clears or blanks
>
> You were also advised to avoid modules - in fact, for some things
> such as network adaptors (wired ethernet) modules are usually no
> problem. The big issues are booting without an initrd (most distros
> use intirds, LFS doesn't), and supporting your hardware - as well as
> the obvious "build in ext4 or whatever you use" and "enable the
> correct [ SATA ] drivers(s) for your chipset(s)" I suppose we should
> add "if in doubt, keep the video simple".
I did use a kernel without modules. I recompiled the kernel without
modules as suggested.
>
> kms is a wonderful thing when it works, but a bit of a beast to set
> up in some situations, and occasionally liable to break across
> kernel upgrades on some hardware (particularly, intel). So, if you
> are using it, I suggest that you build an alternative kernel without
> it, and use that to help identify where your problem lies. Equally,
> even just using a framebuffer might cause problems (on my new
> server, I had to fiddle with grub.conf to get a non-blank screen,
> and I eventually switched to, I think, vesdafb from radeonfb - on
> earlier kernels with my previosu hardware, the framebuffer had worked
> fine without specifying anything odd to grub).
I am not doing anything to advanced as of now. I just want to see the
machine boot.
I'll mess up the kernel by adding sound kms etc later
First get it to boot then on to blfs and add/chqange the kernel params
as needed to get things functional is/was my plan.
>
> I think you said that you had used this config already on your host
> system ? If so, is the host using an initrd [ if it is, the config
> is probably not adequate for LFS ], and did you use the same version
> of the kernel ? Occasionally, things break in newer kernels [ hmm -
> if you are already running a *newer* kernel on the host, use the
> same version in the new system, don't go back to an older kernel
> just because it is in the book ].
No, I did not use a config from a distro, I made the config file from
my own doing.(That's why it didn't work I suppose?)
I did a mrproper
Then make deflaultconfig or something like that
Then make menuconfig and looked over the config and eliminated a bunch
of stuff and added the proper sata drivers etc.
I have no framebuffer or kms configured in the kernel.
I then compiled a kernel that booted.
After which I changed the hard drive in the laptop ( the machine I built
the system on ) and then re-done the LFS as a new build.
When I got the the reboot stage it hung.
I used the same host system and the same partition system on both hard
drives.
I also scripted the first system and copied it to a usb thumb drive to
use again.
After setting up the new drive I used the scripts following the build
sequence to install on the newer/larger drive.
I have to manually do each step following the book. I built the scripts
by cutting and pasting each chapter into a script and adding a section
to untarball the source package and cd to the now source directory
Each script resides into a subdirectory.
The script when run unpacks the tarball cd to the unpacked directoty
and runs the pasted commands.
What I don't know is when does the kernel
Re: Need Help - boot fails - This cause?
On Sun, Sep 25, 2011 at 09:32:04PM -0400, scrat wrote: hmm, I didn't intend to still be awake at this time, really I didn't, but I'm nursing my current dekstop build scripts :-( > > This is a five year old lapdog machine so it is not to beastky fast ;) > That is odd, because the log timestamp you quoted was something like 1.4 seconds after the kernel had started to boot. > > Somebody implied a video problem - that sounds plausible. > > No I don't get a blank/black screen I just get a hard crash, the screen > never clears or blanks > Next time you boot the host system, watch the messages to see what comes next in a successful boot. > > > > You were also advised to avoid modules - in fact, for some things > > such as network adaptors (wired ethernet) modules are usually no > > problem. The big issues are booting without an initrd (most distros > > use intirds, LFS doesn't), and supporting your hardware - as well as > > the obvious "build in ext4 or whatever you use" and "enable the > > correct [ SATA ] drivers(s) for your chipset(s)" I suppose we should > > add "if in doubt, keep the video simple". > > I did use a kernel without modules. I recompiled the kernel without > modules as suggested. > Sounds good > > > > kms is a wonderful thing when it works, but a bit of a beast to set > > up in some situations, and occasionally liable to break across > > kernel upgrades on some hardware (particularly, intel). So, if you > > are using it, I suggest that you build an alternative kernel without > > it, and use that to help identify where your problem lies. Equally, > > even just using a framebuffer might cause problems (on my new > > server, I had to fiddle with grub.conf to get a non-blank screen, > > and I eventually switched to, I think, vesdafb from radeonfb - on > > earlier kernels with my previosu hardware, the framebuffer had worked > > fine without specifying anything odd to grub). > > I am not doing anything to advanced as of now. I just want to see the > machine boot. > I'll mess up the kernel by adding sound kms etc later > First get it to boot then on to blfs and add/chqange the kernel params > as needed to get things functional is/was my plan. > Sounds good. > > > > I think you said that you had used this config already on your host > > system ? If so, is the host using an initrd [ if it is, the config > > is probably not adequate for LFS ], and did you use the same version > > of the kernel ? Occasionally, things break in newer kernels [ hmm - > > if you are already running a *newer* kernel on the host, use the > > same version in the new system, don't go back to an older kernel > > just because it is in the book ]. > > No, I did not use a config from a distro, I made the config file from > my own doing.(That's why it didn't work I suppose?) > > I did a mrproper > Then make deflaultconfig or something like that > Then make menuconfig and looked over the config and eliminated a bunch > of stuff and added the proper sata drivers etc. > I have no framebuffer or kms configured in the kernel. > I then compiled a kernel that booted. > > After which I changed the hard drive in the laptop ( the machine I built > the system on ) and then re-done the LFS as a new build. > When I got the the reboot stage it hung. > I'm lost here (probably because it is late) - you've used the same host to build LFS twice, first on the old disk, and then on the new disk ? > I used the same host system and the same partition system on both hard > drives. > I also scripted the first system and copied it to a usb thumb drive to > use again. > After setting up the new drive I used the scripts following the build > sequence to install on the newer/larger drive. > I have to manually do each step following the book. I built the scripts > by cutting and pasting each chapter into a script and adding a section > to untarball the source package and cd to the now source directory > Each script resides into a subdirectory. > > The script when run unpacks the tarball cd to the unpacked directoty > and runs the pasted commands. The above sounds sensible, but the reality is that scripting makes it very easy to miss errors. OTOH, if you are manually running each step, any errors ought to be apparent to you. > > What I don't know is when does the kernel hand over booting to inittab etc. > > My theory if not flawed is that some/all binaries are linked to the > /tools directory, and since /tools has beened removed it hangs. > Although I could be completely wrong about this. > > It should be simple for you to test this theory - take a program from each package (starting with /sbin/init) and use ldd to see what it links to. If the program you picked turns out to be a shell script, try a different program from the same package (see chapter 6, I think, for what gets installed in each package ? - I don't have a graphical browser on my current desktop). If /sbin/init is linked to /tool
Re: Need Help - boot fails - This cause?
On 09/25/2011 10:44 PM, Ken Moffat wrote: [putolin] > > I'm lost here (probably because it is late) - you've used the same > host to build LFS twice, first on the old disk, and then on the new > disk ? Yes that is correct. The scripts produced a LFS system that booted and worked on the old hard drive so I thought is was good. The only difference is an increase in size of the hard drive 120GB to a 500GB. >> I used the same host system and the same partition system on both hard >> drives. >> I also scripted the first system and copied it to a usb thumb drive to >> use again. >> After setting up the new drive I used the scripts following the build >> sequence to install on the newer/larger drive. >> I have to manually do each step following the book. I built the scripts >> by cutting and pasting each chapter into a script and adding a section >> to untarball the source package and cd to the now source directory >> Each script resides into a subdirectory. >> >>The script when run unpacks the tarball cd to the unpacked directoty >> and runs the pasted commands. > The above sounds sensible, but the reality is that scripting makes > it very easy to miss errors. OTOH, if you are manually running each > step, any errors ought to be apparent to you. Well that is why I scripted it. This old fart has a problem reading off the nook which has the LFS-6.8 pdf and typing the correct thing into the system under build. I use this at the top of the script #!/bin/bash -e set +h shopt -s -o pipefail pkgname=automake pkgver=1.11.1 startdir=$(pwd) then do the cut and paste line with |& tee "$startdir/build.log" at the end so I have a log of what happened so I can then lokk the result over and correct the "hey look dummy errors". >> What I don't know is when does the kernel hand over booting to inittab etc. >> >> My theory if not flawed is that some/all binaries are linked to the >> /tools directory, and since /tools has beened removed it hangs. >> Although I could be completely wrong about this. >> >> > It should be simple for you to test this theory - take a program > from each package (starting with /sbin/init) and use ldd to see what > it links to. If the program you picked turns out to be a shell > script, try a different program from the same package (see chapter > 6, I think, for what gets installed in each package ? - I don't have > a graphical browser on my current desktop). OK I'll do that after I get home from work today > If /sbin/init is linked to /tools, I would expect to see a > meaningful error message, but who knows. If /sbin/init is NOT > linked to /tools, then this appears to be a kernel config problem. > > If /bin/bash is linked correctly, you can also try booting with > init=/bin/bash, although it won't give you a nice environment and > is normally reserved for stepping through the init scripts if things > have broken. > -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
