FC6T3 x86-64 booting issue

[Tomas Lanik]

hi,
I am unable to boot FC6T3 x86-64... on (AMD64X2, 4GB DDR2, SATA II, Asus 
M2N-E)
The initrd image is missing in  /boot directory.
I have tried to fix the issue by creating initrd image as suggested by 
alan <alan clueserver org>:
---------------------------------------------------------------------------- 


On Tue, 19 Sep 2006, sean wrote:


   I've been unsuccessful in installing t3 from dvd on a standard intel
   x86-64 chipset box. I think the problem is that I have one partition
   ( not root ) that's lvm. I asssume this will all be fixed for t4.
   Has anybody figured out how to install before then?
Yep.  I posted it earlier.


After you do the install, boot with the "rescue option" on the install dvd.

When you get a prompt:

chroot /mnt/sysmount
cd /boot
mkinitrd --image-version --nocompress initrd `uname -r`

Then add this line to the /etc/grub.conf entry:
 initrd /initrd-<kernelversion>

save, sync and reboot.

---------------------------------------------------------------


with following result:

---------------------------------------------------------------------------- 

root(hd0,0)
FileSystem Type is ext2fs, partition type 0x83
kernel /vmlinuz-2.6.17-1.2630.fc6 ro root=/dev/basevg/rootlv rhgb quiet
  [Linux-bzImage, setup=0x1e00, size=0x20865b]
initrd /initrd-2.6.17-1.2630.fc6
  [Linux-initrd @ 0xdf916000, 0x5b9800 bytes]

Error 28: Selected item cannot fit into memory
Press any key to continue...

---------------------------------------------------------------------------

Any ideas how to make FC6T3 boot?

Cheers

tomas

[Alan]

On Wed, 20 Sep 2006, Tomas Lanik wrote:

>  hi,
>  I am unable to boot FC6T3 x86-64... on (AMD64X2, 4GB DDR2, SATA II, Asus 
>  M2N-E)
>  The initrd image is missing in  /boot directory.
>  I have tried to fix the issue by creating initrd image as suggested by alan 
>  <alan clueserver org>:
>  ---------------------------------------------------------------------------- 
>
>  On Tue, 19 Sep 2006, sean wrote:
>
>
>   I've been unsuccessful in installing t3 from dvd on a standard intel
>   x86-64 chipset box. I think the problem is that I have one partition
>   ( not root ) that's lvm. I asssume this will all be fixed for t4.
>   Has anybody figured out how to install before then?
>  Yep.  I posted it earlier.
>
>
>  After you do the install, boot with the "rescue option" on the install dvd.
>
>  When you get a prompt:
>
>  chroot /mnt/sysmount
>  cd /boot
>  mkinitrd --image-version --nocompress initrd `uname -r`
>
>  Then add this line to the /etc/grub.conf entry:
>  initrd /initrd-<kernelversion>
>
>  save, sync and reboot.
>
>  ---------------------------------------------------------------
>
>
>  with following result:
>
>  ---------------------------------------------------------------------------- 
>  root(hd0,0)
>  FileSystem Type is ext2fs, partition type 0x83
>  kernel /vmlinuz-2.6.17-1.2630.fc6 ro root=/dev/basevg/rootlv rhgb quiet
>  [Linux-bzImage, setup=0x1e00, size=0x20865b]
>  initrd /initrd-2.6.17-1.2630.fc6
>  [Linux-initrd @ 0xdf916000, 0x5b9800 bytes]
>
>  Error 28: Selected item cannot fit into memory
>  Press any key to continue...
>
>  ---------------------------------------------------------------------------
>
>  Any ideas how to make FC6T3 boot? 
Have you tried without the "--nocompress" option?

-- 
"Oh, Joel Miller, you've just found the marble in the oatmeal. You're a
lucky, lucky, lucky little boy. 'Cause you know why? You get to drink
from... the FIRE HOOOOOSE!"
         - The Stanley Spudoski guide to mailing list administration

[Tomas Lanik]

Hi,
Thank for the answer.
I have just tried make the initrd compressed but the result is the same...
I didnt have problems booting with FC6T2 on the same machine. I have 
switched to FC6T2 because I could not apply any updates for some strange 
dependencies with nautilus package after t3 was released.

cheers

tomas


alan wrote:
>  On Wed, 20 Sep 2006, Tomas Lanik wrote:
>
> > hi,
> > I am unable to boot FC6T3 x86-64... on (AMD64X2, 4GB DDR2, SATA II, 
> > Asus M2N-E)
> > The initrd image is missing in  /boot directory.
> > I have tried to fix the issue by creating initrd image as suggested 
> > by alan <alan clueserver org>:
> > ---------------------------------------------------------------------------- 
> >
> > On Tue, 19 Sep 2006, sean wrote:
> >
> >
> >  I've been unsuccessful in installing t3 from dvd on a standard intel
> >  x86-64 chipset box. I think the problem is that I have one partition
> >  ( not root ) that's lvm. I asssume this will all be fixed for t4.
> >  Has anybody figured out how to install before then?
> > Yep.  I posted it earlier.
> >
> >
> > After you do the install, boot with the "rescue option" on the 
> > install dvd.
> >
> > When you get a prompt:
> >
> > chroot /mnt/sysmount
> > cd /boot
> > mkinitrd --image-version --nocompress initrd `uname -r`
> >
> > Then add this line to the /etc/grub.conf entry:
> > initrd /initrd-<kernelversion>
> >
> > save, sync and reboot.
> >
> > ---------------------------------------------------------------
> >
> >
> > with following result:
> >
> > ---------------------------------------------------------------------------- 
> > root(hd0,0)
> > FileSystem Type is ext2fs, partition type 0x83
> > kernel /vmlinuz-2.6.17-1.2630.fc6 ro root=/dev/basevg/rootlv rhgb quiet
> > [Linux-bzImage, setup=0x1e00, size=0x20865b]
> > initrd /initrd-2.6.17-1.2630.fc6
> > [Linux-initrd @ 0xdf916000, 0x5b9800 bytes]
> >
> > Error 28: Selected item cannot fit into memory
> > Press any key to continue...
> >
> > --------------------------------------------------------------------------- 
> >
> >
> > Any ideas how to make FC6T3 boot?
>
>  Have you tried without the "--nocompress" option?
>

[Ronald Warsow]

Tomas Lanik wrote:
>  hi,
>  I am unable to boot FC6T3 x86-64... on (AMD64X2, 4GB DDR2, SATA II, Asus 
>  M2N-E)
>  The initrd image is missing in  /boot directory.
>  
>  Any ideas how to make FC6T3 boot?
>   
what's about a rescue boot and

yum update kernel ???


if it's a *t3* only
then
	there is a new kernel in rawhide
else
	a manual download of an other [newer|elder] kernel
	and an rpm -ivh kernel-xxx [--oldpackage]
fi

means: i would the install routine let do the work.

maybe a check what's *in* the initrd then agains what has the rescue 
environment loaded (lsmod) related to sata, dm,... .
esp. look at entries with dm ...

rescue mode seems -iirc- to work !
network ?
why dealing with complicated stuff ?

maybe i check an i86_64 install later ...

-- 
	
    ronald

[Tomas Lanik]

Hi,
Yum update sounds great!
will give it a try...

tomas


ronald wrote:
>  Tomas Lanik wrote:
> > hi,
> > I am unable to boot FC6T3 x86-64... on (AMD64X2, 4GB DDR2, SATA II, 
> > Asus M2N-E)
> > The initrd image is missing in  /boot directory.
> >
> > Any ideas how to make FC6T3 boot?
> >
>  what's about a rescue boot and
>
>  yum update kernel ???
>
>
>  if it's a *t3* only
>  then
>      there is a new kernel in rawhide
>  else
>      a manual download of an other [newer|elder] kernel
>      and an rpm -ivh kernel-xxx [--oldpackage]
>  fi
>
>  means: i would the install routine let do the work.
>
>  maybe a check what's *in* the initrd then agains what has the rescue 
>  environment loaded (lsmod) related to sata, dm,... .
>  esp. look at entries with dm ...
>
>  rescue mode seems -iirc- to work !
>  network ?
>  why dealing with complicated stuff ?
>
>  maybe i check an i86_64 install later ...
>

[Tomas Lanik]

The rescue mode in FC6T3 is rotten as well!
After trying to set up eth0 interface using DHCP it just spawns some 
"giberish" chars on me!!!!
The special char-art already appears when entering the shell in resue 
mode but this time really freezes the machine.
Awful stuff! after hangs forever so... bye bye yum followed by 
CTRL-ALT-DEL ---> Kernel Panic!!!
Will try setup the networking manually...

tomas

Tomas Lanik wrote:
>  Hi,
>  Yum update sounds great!
>  will give it a try...
>
>  tomas
>
>
>  ronald wrote:
> > Tomas Lanik wrote:
> >> hi,
> >> I am unable to boot FC6T3 x86-64... on (AMD64X2, 4GB DDR2, SATA II, 
> >> Asus M2N-E)
> >> The initrd image is missing in  /boot directory.
> >>
> >> Any ideas how to make FC6T3 boot?
> >>
> > what's about a rescue boot and
> >
> > yum update kernel ???
> >
> >
> > if it's a *t3* only
> > then
> >     there is a new kernel in rawhide
> > else
> >     a manual download of an other [newer|elder] kernel
> >     and an rpm -ivh kernel-xxx [--oldpackage]
> > fi
> >
> > means: i would the install routine let do the work.
> >
> > maybe a check what's *in* the initrd then agains what has the rescue 
> > environment loaded (lsmod) related to sata, dm,... .
> > esp. look at entries with dm ...
> >
> > rescue mode seems -iirc- to work !
> > network ?
> > why dealing with complicated stuff ?
> >
> > maybe i check an i86_64 install later ...
> >
>

[Tomas Lanik]

Neither manually...
Networking started OK but yum crashes on
# yum update kernel
with corruption of rpmdb....

I giving up spending 1/2 day with this

may be FC6T4 will do... but I think t3 should not have been released at all!
>  After trying to set up eth0 interface using DHCP it just spawns some 
>  "giberish" chars on me!!!!
>  The special char-art already appears when entering the shell in resue 
>  mode but this time really freezes the machine.
>  Awful stuff! after hangs forever so... bye bye yum followed by 
>  CTRL-ALT-DEL ---> Kernel Panic!!!
>  Will try setup the networking manually...
>
>  tomas
>
>  Tomas Lanik wrote:
> > Hi,
> > Yum update sounds great!
> > will give it a try...
> >
> > tomas
> >
> >
> > ronald wrote:
> >> Tomas Lanik wrote:
> >>> hi,
> >>> I am unable to boot FC6T3 x86-64... on (AMD64X2, 4GB DDR2, SATA II, 
> >>> Asus M2N-E)
> >>> The initrd image is missing in  /boot directory.
> >>>
> >>> Any ideas how to make FC6T3 boot?
> >>>
> >> what's about a rescue boot and
> >>
> >> yum update kernel ???
> >>
> >>
> >> if it's a *t3* only
> >> then
> >>     there is a new kernel in rawhide
> >> else
> >>     a manual download of an other [newer|elder] kernel
> >>     and an rpm -ivh kernel-xxx [--oldpackage]
> >> fi
> >>
> >> means: i would the install routine let do the work.
> >>
> >> maybe a check what's *in* the initrd then agains what has the rescue 
> >> environment loaded (lsmod) related to sata, dm,... .
> >> esp. look at entries with dm ...
> >>
> >> rescue mode seems -iirc- to work !
> >> network ?
> >> why dealing with complicated stuff ?
> >>
> >> maybe i check an i86_64 install later ...
> >>
> >
>

[Ronald Warsow]

Tomas Lanik wrote:
>  Neither manually...
>  Networking started OK but yum crashes on
>  # yum update kernel
>  with corruption of rpmdb....
>  
>  I giving up spending 1/2 day with this 
WHAT ???

;-)

>  
>  may be FC6T4 will do... but I think t3 should not have been released at 
>  all! 
fc6t4 is named *FC6* scheduled at ...

i'm currently through the half of an t3-x86_64 install.
also asus mb. A8V, amd64, sata.
i'll wait and see and report later in ~1h.

try a new install ! maybe from net. => rawhide
seems that there is more up with your box....

-- 
ronald

[Alan Cox]

On Thu, Sep 21, 2006 at 12:06:28AM +0100, Tomas Lanik wrote:
>  may be FC6T4 will do... but I think t3 should not have been released
> at 
>  all! 
And we are all perfect and hindsight is wonderful

T3 has done an excellent job of finding a problem...

[Alan]

On Wed, 20 Sep 2006, Alan Cox wrote:

>  On Thu, Sep 21, 2006 at 12:06:28AM +0100, Tomas Lanik wrote:
> > may be FC6T4 will do... but I think t3 should not have been released at
> > all!
>
>  And we are all perfect and hindsight is wonderful
>
>  T3 has done an excellent job of finding a problem... 
I think that is "problems".

Upgrading on i386 has proven quite impossible for me with FC6t3.

I have gotten past the initrd problem on x86_64, but I appear to be one of 
the few.

I just hope these get cleaned up before release.  I shudder to think what 
the reaction would have been if FC6t3 had been the actual release.

-- 
"Oh, Joel Miller, you've just found the marble in the oatmeal. You're a
lucky, lucky, lucky little boy. 'Cause you know why? You get to drink
from... the FIRE HOOOOOSE!"
         - The Stanley Spudoski guide to mailing list administration

[Ronald Warsow]

Alan Cox wrote:
>  On Thu, Sep 21, 2006 at 12:06:28AM +0100, Tomas Lanik wrote:
...
>  
>  T3 has done an excellent job of finding a problem...
>   
ok -and i speak for me self here- therefore i do test installations,- too -.
but what is that problem ?

did you read:
https://www.redhat.com/archives/fedora-list/2006-September/msg02311.html ?



-- 
	
    ronald

[Alan Cox]

On Thu, Sep 21, 2006 at 03:00:41PM +0200, ronald wrote:
>  Alan Cox wrote:
>  >On Thu, Sep 21, 2006 at 12:06:28AM +0100, Tomas Lanik wrote:
>  ...
>  >
>  >T3 has done an excellent job of finding a problem...
>  >
>  ok -and i speak for me self here- therefore i do test installations,- too 
>  -.
>  but what is that problem ? 
Primarily it seems squashfs causing memory corruption (#204638)

>  did you read:
>  https://www.redhat.com/archives/fedora-list/2006-September/msg02311.html ?

[Ronald Warsow]

Alan Cox wrote:
>  On Thu, Sep 21, 2006 at 03:00:41PM +0200, ronald wrote: 
...
> > -.
> > but what is that problem ?
>  
>  Primarily it seems squashfs causing memory corruption (#204638)
>   
thx.

-- 
	
    ronald

[Phillip Lougher]

Alan Cox <alan <at> redhat.com> writes:

>  Primarily it seems squashfs causing memory corruption (#204638)
This proved to be an incorrectly applied patch (by Red Hat) which broke 
Mksquashfs.  A fix should have gone in last weekend.

Phillip

[Tomas Lanik]

Hi everyone,
I have installed the FC6T3 again over the http as suggested by Ronald:
----------------------------------------------------------------------
hi all
to clear some questions related to x86_64 installation i give it a try:

this is a *real T3* not a rawhide installation
components (see attachment)

apart from a -maybe- broken mirror NO PROBLEMS with the installation !

for people who want http-install from the german mirror tu-chemnitz.de:
i tried it twice, but ever with the failure: repodata/primary.xml.gz- 
...[Errno 256]

the file is definitively there, but ... don't know !

with mirror sunsite.icm.edu.pl no problems.
btw: this seems to be a quick one. (~2.1GB in ~1h)
---------------------------------------------------------------------
The install went all OK but the result is the same, even with the 
correct initrd-<version>.img is in /boot:
root(hd0,0)
FileSystem Type is ext2fs, partition type 0x83
kernel /vmlinuz-2.6.17-1.2630.fc6 ro root=/dev/basevg/rootlv rhgb quiet
 [Linux-bzImage, setup=0x1e00, size=0x20865b]
initrd /initrd-2.6.17-1.2630.fc6.img
 [Linux-initrd @ 0xdf916000, 0x5b9800 bytes]

Error 28: Selected item cannot fit into memory
Press any key to continue...

It think it might be related to the raid system and(or) GRUB.. Could the 
GRUB update from linux rescue help?
----------------------------------------------------------------------
GRUB ERROR DESCRIPTION

28 : Selected item cannot fit into memory
    This error is returned if a kernel, module, or raw file load command
    is either trying to load its data
    such that it won't fit into memory or it is simply too big.

---------------------------------------------------------------------
 I am using (nvidia RAID on Asus M2N-E, AthlonXPX2, SATAII
and my LVM setup is:

---  /dev/mapper/nvidia_ieabbfdc (RAID 1, 2xSATA II)
                    /dev/mapper/nvidia_ieabbfdcp1     /boot        ext3
                    /dev/mapper/nvidia_ieabbfdcp2     LVM PV        
basevg (Base Volume Group)
                                    /                                   
rootLV            (Logical Volume)
                                    /var                              
varLV              (Logical Volume)
                                   /usr                               
usrLV               (Logical Volume)
                                   /home                           
homeLV           (Logical Volume)
                                   /chroot                         
chrootLV          (Logical Volume)
                                   swap                            
swapLV            (Logical Volume)
                    /dev/mapper/nvidia_ieabbfdcp3     LVM PV       xenvg 
(Xen Volume Group)
                                  (no Logical Volumes Yet)

FC6T3 clearly fails to boot but after reinstalling FC6 T2 all works fine 
without any problems!

Suggestions?

Tomas





ronald wrote:
>  Alan Cox wrote:
> > On Thu, Sep 21, 2006 at 12:06:28AM +0100, Tomas Lanik wrote:
>  ...
> >
> > T3 has done an excellent job of finding a problem...
> >
>  ok -and i speak for me self here- therefore i do test installations,- 
>  too -.
>  but what is that problem ?
>
>  did you read:
>  https://www.redhat.com/archives/fedora-list/2006-September/msg02311.html 
>  ?
>
>
>

[Dave Jones]

On Thu, Sep 21, 2006 at 05:25:19PM +0100, Tomas Lanik wrote:

>  The install went all OK but the result is the same, even with the 
>  correct initrd-<version>.img is in /boot:
>  root(hd0,0)
>  FileSystem Type is ext2fs, partition type 0x83
>  kernel /vmlinuz-2.6.17-1.2630.fc6 ro root=/dev/basevg/rootlv rhgb quiet
>   [Linux-bzImage, setup=0x1e00, size=0x20865b]
>  initrd /initrd-2.6.17-1.2630.fc6.img
>   [Linux-initrd @ 0xdf916000, 0x5b9800 bytes]
>  
>  Error 28: Selected item cannot fit into memory
>  Press any key to continue...
>  
>  It think it might be related to the raid system and(or) GRUB.. Could the 
>  GRUB update from linux rescue help?
>  ----------------------------------------------------------------------
>  GRUB ERROR DESCRIPTION
>  
>  28 : Selected item cannot fit into memory
>      This error is returned if a kernel, module, or raw file load command
>      is either trying to load its data
>      such that it won't fit into memory or it is simply too big. 
Bizarre. How much RAM do you actually have ?
*thinks*, Peter, I recall something magical about grub and x86-64
a while back (I think it was on one of those 'viper' boxes).
Ring any bells ?

	Dave

[Tomas Lanik]

4GB DDR2 Registered

tomas

Dave Jones wrote:
>  On Thu, Sep 21, 2006 at 05:25:19PM +0100, Tomas Lanik wrote:
>
>   > The install went all OK but the result is the same, even with the 
>   > correct initrd-<version>.img is in /boot:
>   > root(hd0,0)
>   > FileSystem Type is ext2fs, partition type 0x83
>   > kernel /vmlinuz-2.6.17-1.2630.fc6 ro root=/dev/basevg/rootlv rhgb quiet
>   >  [Linux-bzImage, setup=0x1e00, size=0x20865b]
>   > initrd /initrd-2.6.17-1.2630.fc6.img
>   >  [Linux-initrd @ 0xdf916000, 0x5b9800 bytes]
>   > 
>   > Error 28: Selected item cannot fit into memory
>   > Press any key to continue...
>   > 
>   > It think it might be related to the raid system and(or) GRUB.. Could the 
>   > GRUB update from linux rescue help?
>   > ----------------------------------------------------------------------
>   > GRUB ERROR DESCRIPTION
>   > 
>   > 28 : Selected item cannot fit into memory
>   >     This error is returned if a kernel, module, or raw file load command
>   >     is either trying to load its data
>   >     such that it won't fit into memory or it is simply too big.
>
>  Bizarre. How much RAM do you actually have ?
>  *thinks*, Peter, I recall something magical about grub and x86-64
>  a while back (I think it was on one of those 'viper' boxes).
>  Ring any bells ?
>
>  	Dave 
>
>

[Peter Jones]

On Thu, 2006-09-21 at 12:29 -0400, Dave Jones wrote:
>  On Thu, Sep 21, 2006 at 05:25:19PM +0100, Tomas Lanik wrote:
>  
>   > The install went all OK but the result is the same, even with the 
>   > correct initrd-<version>.img is in /boot:
>   > root(hd0,0)
>   > FileSystem Type is ext2fs, partition type 0x83
>   > kernel /vmlinuz-2.6.17-1.2630.fc6 ro root=/dev/basevg/rootlv rhgb quiet
>   >  [Linux-bzImage, setup=0x1e00, size=0x20865b]
>   > initrd /initrd-2.6.17-1.2630.fc6.img
>   >  [Linux-initrd @ 0xdf916000, 0x5b9800 bytes]
>   > 
>   > Error 28: Selected item cannot fit into memory
>   > Press any key to continue...
>   > 
>   > It think it might be related to the raid system and(or) GRUB.. Could the 
>   > GRUB update from linux rescue help?
>   > ----------------------------------------------------------------------
>   > GRUB ERROR DESCRIPTION
>   > 
>   > 28 : Selected item cannot fit into memory
>   >     This error is returned if a kernel, module, or raw file load command
>   >     is either trying to load its data
>   >     such that it won't fit into memory or it is simply too big.
>  
>  Bizarre. How much RAM do you actually have ?
>  *thinks*, Peter, I recall something magical about grub and x86-64
>  a while back (I think it was on one of those 'viper' boxes).
>  Ring any bells ? 
Yeah, this is because of a change that was backed out because it was
limiting vmalloc= on non-hughmem kernels to be ~500M instead of ~700M or
so, and we couldn't find any bug related to it or figure out quite why
it was there.  It's back in in the build I did today, and I'm advising
the customers who care to bite the bullet and run hughmem.  So this
should be fixed in tomorrow's tree.

-- 
  Peter

[Jeremy Katz]

On Thu, 2006-09-21 at 14:27 -0400, Peter Jones wrote:
>  >  > 28 : Selected item cannot fit into memory
>  >  >     This error is returned if a kernel, module, or raw file load command
>  >  >     is either trying to load its data
>  >  >     such that it won't fit into memory or it is simply too big.
>
>  Yeah, this is because of a change that was backed out because it was
>  limiting vmalloc= on non-hughmem kernels to be ~500M instead of ~700M or
>  so, and we couldn't find any bug related to it or figure out quite why
>  it was there.  It's back in in the build I did today, and I'm advising
>  the customers who care to bite the bullet and run hughmem.  So this
>  should be fixed in tomorrow's tree. 
Also, you should be able to workaround and get your machine to boot by
going into the grub "uppermem" command

Jeremy