[gentoo-user] Laptop resurrection...

2009-12-02 Thread BRM
I'm still working to get my laptop back up; I have one more thing to try.

Presently, I am having a problem with the compiling a 2.6.30-gentoo-r8 kernel 
that actually works. It might be a processor issue - linux reports it as a 
Pentium M which is what I have selected during 'make menuconfig', but the the 
grub keeps reporting that it is not a recognized format or something to that 
effect, so it won't load it.

Questions:

1) I am using the Gentoo 2007.0 LiveCD to boot with, then chroot'ing into my 
installation to build the kernel. I shouldn't need a newer LiveCD, correct?
2) Grub doesn't need to be re-run (e.g. running the grub prompt and going 
through the install procedure) after changes to the menu file, correct?

TIA,

Ben



Re: [gentoo-user] Laptop resurrection...

2009-12-02 Thread Mick
2009/12/2 BRM bm_witn...@yahoo.com:
 I'm still working to get my laptop back up; I have one more thing to try.

 Presently, I am having a problem with the compiling a 2.6.30-gentoo-r8 kernel 
 that actually works. It might be a processor issue - linux reports it as a 
 Pentium M which is what I have selected during 'make menuconfig', but the the 
 grub keeps reporting that it is not a recognized format or something to that 
 effect, so it won't load it.

 Questions:

 1) I am using the Gentoo 2007.0 LiveCD to boot with, then chroot'ing into my 
 installation to build the kernel. I shouldn't need a newer LiveCD, correct?

Correct as long as it recognise your hardware.

 2) Grub doesn't need to be re-run (e.g. running the grub prompt and going 
 through the install procedure) after changes to the menu file, correct?

Correct, assuming you have installed GRUB correctly in the first
instance - which makes me ask:

What is your exact error message?

-- 
Regards,
Mick



Re: [gentoo-user] Laptop resurrection...

2009-12-02 Thread Marcus Wanner

On 12/2/2009 11:26 AM, Mick wrote:

2009/12/2 BRM bm_witn...@yahoo.com:
  

I'm still working to get my laptop back up; I have one more thing to try.

Presently, I am having a problem with the compiling a 2.6.30-gentoo-r8 kernel 
that actually works. It might be a processor issue - linux reports it as a 
Pentium M which is what I have selected during 'make menuconfig', but the the 
grub keeps reporting that it is not a recognized format or something to that 
effect, so it won't load it.

Questions:

1) I am using the Gentoo 2007.0 LiveCD to boot with, then chroot'ing into my 
installation to build the kernel. I shouldn't need a newer LiveCD, correct?



Correct as long as it recognise your hardware.

  

2) Grub doesn't need to be re-run (e.g. running the grub prompt and going 
through the install procedure) after changes to the menu file, correct?



Correct, assuming you have installed GRUB correctly in the first
instance - which makes me ask:

What is your exact error message?
  
I got that error when I copied the wrong kernel image to /boot, make 
sure you are copying the one detailed in the gentoo handbook (chapter 7, 
I think).


Marcus



Re: [gentoo-user] Laptop resurrection...

2009-12-02 Thread Albert Hopkins
On Wed, 2009-12-02 at 06:13 -0800, BRM wrote:
 the the grub keeps reporting that it is not a recognized format or
 something to that effect, so it won't load it.

Please post the exact error message (write it down if need be). Simply
saying or something to that effect tends to lead to errors in
responses (or something to that effect ;).

-a





Re: [gentoo-user] Laptop resurrection...

2009-12-02 Thread BRM
- Original Message 

From: Mick michaelkintz...@gmail.com
 2009/12/2 BRM bm_witn...@yahoo.com:
  I'm still working to get my laptop back up; I have one more thing to try.
  Presently, I am having a problem with the compiling a 2.6.30-gentoo-r8 
  kernel that actually works. It might be a processor issue - linux reports 
  it as a
  Pentium M which is what I have selected during 'make menuconfig', but the 
  the grub keeps reporting that it is not a recognized format or something to 
  that effect, so it won't load it.
  Questions:
  1) I am using the Gentoo 2007.0 LiveCD to boot with, then chroot'ing into 
  my installation to build the kernel. I shouldn't need a newer LiveCD, 
  correct?
 Correct as long as it recognise your hardware.

Thanks.

  2) Grub doesn't need to be re-run (e.g. running the grub prompt and going 
  through the install procedure) after changes to the menu file, correct?
 Correct, assuming you have installed GRUB correctly in the first instance

Thanks

  - which makes me ask:
 What is your exact error message?

I'll post that tonight.

- Original Message 
From: Marcus Wanner marc...@cox.net
 I got that error when I copied the wrong kernel image to /boot, make 
 sure you are copying the one detailed in the gentoo handbook (chapter 7, I 
 think).

The last kernel I copied in I copied the file specified by the kernel's README: 
arch/arch/boot/bzImage - arch being x86.

Though according to http://www.gentoo.org/doc/en/kernel-config.xml it should be 
arch/i386/boot/bzImage...not sure which is right off hand.
Will check into it tonight.

Ben




Re: [gentoo-user] Laptop resurrection...

2009-12-02 Thread Dale

BRM wrote:

- Original Message 

From: Mick michaelkintz...@gmail.com
  

2009/12/2 BRM bm_witn...@yahoo.com:


I'm still working to get my laptop back up; I have one more thing to try.
Presently, I am having a problem with the compiling a 2.6.30-gentoo-r8 kernel 
that actually works. It might be a processor issue - linux reports it as a
Pentium M which is what I have selected during 'make menuconfig', but the the 
grub keeps reporting that it is not a recognized format or something to that 
effect, so it won't load it.
Questions:
1) I am using the Gentoo 2007.0 LiveCD to boot with, then chroot'ing into my 
installation to build the kernel. I shouldn't need a newer LiveCD, correct?
  

Correct as long as it recognise your hardware.



Thanks.

  

2) Grub doesn't need to be re-run (e.g. running the grub prompt and going 
through the install procedure) after changes to the menu file, correct?
  

Correct, assuming you have installed GRUB correctly in the first instance



Thanks

  

 - which makes me ask:
What is your exact error message?



I'll post that tonight.

- Original Message 
From: Marcus Wanner marc...@cox.net
  
I got that error when I copied the wrong kernel image to /boot, make 
sure you are copying the one detailed in the gentoo handbook (chapter 7, I think).



The last kernel I copied in I copied the file specified by the kernel's README: 
arch/arch/boot/bzImage - arch being x86.

Though according to http://www.gentoo.org/doc/en/kernel-config.xml it should be 
arch/i386/boot/bzImage...not sure which is right off hand.
Will check into it tonight.

Ben
  


This may not be the problem but I ran into this a while back.  Some 
times when I build a kernel, the bzImage in */i386/boot is actually a 
link, not the bzImage itself.  Naturally copying a link will not boot, 
especially if it breaks the link or /usr is on a separate partition and 
not mounted yet.


I ran into this twice with two different kernels.  I can't recall the 
version tho.  You may want to check that before you copy the bzImage 
over, just to make sure it is a file and not a link.


Oh, don't forget to mount /boot too.  Very common thing to forget.

Dale

:-)  :-) 



Re: [gentoo-user] Laptop resurrection... (solved)

2009-12-02 Thread BRM




- Original Message 
From: Mick michaelkintz...@gmail.com
 On Wednesday 02 December 2009 20:52:35 BRM wrote:
  - Original Message 
  From: Mick michaelkintz...@gmail.com
   2009/12/2 BRM bm_witn...@yahoo.com:
- which makes me ask:
   What is your exact error message?
  I'll post that tonight.

Exact error message was:

ERROR 13: Invalid or unsupported executable format

Well, I mounted the drive again - and didn't go into the chroot shell.
I had been doing all the copying from within the chroot before.
I found the arch/i386/boot/bzImage, which does just point to 
arch/x86/boot/bzImage.

I had copied arch/x86/boot/bzImage but for whatever reason the md5 hashes of 
the image
and what I had copied didn't match. So I copied it, rebooted, and viola it 
worked.
Odd...not sure what was up with it; but it's working. Now to update the 
environment.

- Original Message 
From: Dale rdalek1...@gmail.com
 Oh, don't forget to mount /boot too.  Very common thing to for

True; however I don't setup /boot that way unless I absolutely have to - namely 
for older systems that couldn't access the whole hard drive until after the 
kernel was loaded, or some other explicit reason. I haven't had a system like 
that in a long time. And it wasn't needed on this system.

Thanks!

Ben