1369 kernel won't boot.

Steve Holdoway steve at greengecko.co.nz
Tue Jun 7 06:17:45 UTC 2005


Dave Jones wrote:

>On Tue, Jun 07, 2005 at 06:00:29PM +1200, Steve Holdoway wrote:
> > Hi folks,
> > 
> > I can boot fine off a 1366 kernel with no problems, but I get the 
> > following errors from 1369
> > 
> > RAMDISK: compressed image found at block 0
> > RAMDISK: ran out of compressed data
> > invalid compressed format (err=1)
> > 
> > I'm booting into a reiser root partition...
> > 
> > md5sums for the installed files...
> > b04bc854d21e0d6ed811ca721984b90f  config-2.6.11-1.1369_FC4
> > dd119b324f849d41593f2843a1c69640  initrd-2.6.11-1.1369_FC4.img
> > 70a0d393db5703555459514c2bd65050  System.map-2.6.11-1.1369_FC4
> > a71e7abce43fb3a62066007d7ad2c0e6  vmlinuz-2.6.11-1.1369_FC4
> > 
> > a cpio -itv of the gunzipped initrd archive shows...
> > 
> > -rw-r--r--   1 root     root        12384 Jun  6 17:17 lib/sata_nv.ko
> > -rw-r--r--   1 root     root       296800 Jun  6 17:17 lib/reiserfs.ko
> > -rw-r--r--   1 root     root       187272 Jun  6 17:17 lib/scsi_mod.ko
> > -rw-r--r--   1 root     root        25492 Jun  6 17:17 lib/sd_mod.ko
> > -rw-r--r--   1 root     root        55912 Jun  6 17:17 lib/libata.ko
> > 
> > and the archive is 5196 blocks in size.
> > 
> > 
> > Any ideas what could be causing the problems?
>
>Did it run out of disk space in /boot when it installed ?
>It looks like an installation problem. Try removing it, and
>installing it again.
>
>		Dave
>
>  
>
No diskspace issues...

Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/hda1              4008000   3059788    948212  77% /
none                    517732         0    517732   0% /dev/shm
/dev/hda6              4008000    112828   3895172   3% /tmp
/dev/hda3             10008136   8819668   1188468  89% /usr
/dev/hda5              6008068   4348340   1659728  73% /var
/dev/hda7             52137284  43903720   8233564  85% /share

Removed, downloaded the rpm again, and reinstalled. had exactly the same 
problem, although interestingly the md5sum for the initrd has changed... ?

9d7e317bafafdf6d106d5ef10da2e27e  initrd-2.6.11-1.1369_FC4.img

Can anyone confirm the correct value?? Any other suggestions? I can't 
seem to roll my own kernel and get it to boot either.

Cheers,

Steve











More information about the fedora-test-list mailing list