* RAMDISK: ran out of compressed data
@ 2008-07-08 0:21 Siva Prasad
2008-07-08 6:58 ` Marco Stornelli
0 siblings, 1 reply; 4+ messages in thread
From: Siva Prasad @ 2008-07-08 0:21 UTC (permalink / raw)
To: linuxppc-dev, linuxppc-embedded
Hi,
I am getting the following error when I tried to boot with ramdisk. Any
specific reason or clue why this is happening?
RAMDISK: Compressed image found at block 0
RAMDISK: ran out of compressed data
invalid compressed format (err=3D1)
I am running into this on 8641D runing 2.6.24-rc6 kernel. My .config
around block area are...
CONFIG_BLK_DEV=3Dy
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=3Dy
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
CONFIG_BLK_DEV_RAM=3Dy
CONFIG_BLK_DEV_RAM_COUNT=3D16
CONFIG_BLK_DEV_RAM_SIZE=3D49152
CONFIG_BLK_DEV_RAM_BLOCKSIZE=3D1024
Thanks
Siva
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: RAMDISK: ran out of compressed data
2008-07-08 0:21 RAMDISK: ran out of compressed data Siva Prasad
@ 2008-07-08 6:58 ` Marco Stornelli
2008-07-08 22:54 ` Siva Prasad
0 siblings, 1 reply; 4+ messages in thread
From: Marco Stornelli @ 2008-07-08 6:58 UTC (permalink / raw)
To: Siva Prasad; +Cc: linuxppc-embedded
Siva Prasad ha scritto:
> Hi,
>
> I am getting the following error when I tried to boot with ramdisk. Any
> specific reason or clue why this is happening?
>
> RAMDISK: Compressed image found at block 0
> RAMDISK: ran out of compressed data
> invalid compressed format (err=1)
>
> I am running into this on 8641D runing 2.6.24-rc6 kernel. My .config
> around block area are...
>
> CONFIG_BLK_DEV=y
> # CONFIG_BLK_DEV_FD is not set
> # CONFIG_BLK_CPQ_DA is not set
> # CONFIG_BLK_CPQ_CISS_DA is not set
> # CONFIG_BLK_DEV_DAC960 is not set
> # CONFIG_BLK_DEV_UMEM is not set
> # CONFIG_BLK_DEV_COW_COMMON is not set
> CONFIG_BLK_DEV_LOOP=y
> # CONFIG_BLK_DEV_CRYPTOLOOP is not set
> # CONFIG_BLK_DEV_NBD is not set
> # CONFIG_BLK_DEV_SX8 is not set
> CONFIG_BLK_DEV_RAM=y
> CONFIG_BLK_DEV_RAM_COUNT=16
> CONFIG_BLK_DEV_RAM_SIZE=49152
> CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
>
> Thanks
> Siva
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
I think it's not a kernel problem but a problem related with the
compression method instead. Check out how you are compressing the ramdisk.
--
Marco Stornelli
Embedded Software Engineer
CoRiTeL - Consorzio di Ricerca sulle Telecomunicazioni
http://www.coritel.it
marco.stornelli@coritel.it
+39 06 72582838
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: RAMDISK: ran out of compressed data
2008-07-08 6:58 ` Marco Stornelli
@ 2008-07-08 22:54 ` Siva Prasad
2008-07-09 7:05 ` Marco Stornelli
0 siblings, 1 reply; 4+ messages in thread
From: Siva Prasad @ 2008-07-08 22:54 UTC (permalink / raw)
To: Marco Stornelli; +Cc: linuxppc-dev, linuxppc-embedded
Hi,
The same ramdisk works fine for 2.6.15 kernel. We are just upgrading to
a new version, and would like to get that ramdisk to work on the new one
as well.
Can you please elaborate on what you mean by compression format. Mine
currently use the standard .gz extension/compression.
Thanks
Siva
Siva Prasad ha scritto:
> Hi,
>=20
> I am getting the following error when I tried to boot with ramdisk.
Any
> specific reason or clue why this is happening?
>=20
> RAMDISK: Compressed image found at block 0
> RAMDISK: ran out of compressed data
> invalid compressed format (err=3D1)
>=20
> I am running into this on 8641D runing 2.6.24-rc6 kernel. My .config
> around block area are...
>=20
> CONFIG_BLK_DEV=3Dy
> # CONFIG_BLK_DEV_FD is not set
> # CONFIG_BLK_CPQ_DA is not set
> # CONFIG_BLK_CPQ_CISS_DA is not set
> # CONFIG_BLK_DEV_DAC960 is not set
> # CONFIG_BLK_DEV_UMEM is not set
> # CONFIG_BLK_DEV_COW_COMMON is not set
> CONFIG_BLK_DEV_LOOP=3Dy
> # CONFIG_BLK_DEV_CRYPTOLOOP is not set
> # CONFIG_BLK_DEV_NBD is not set
> # CONFIG_BLK_DEV_SX8 is not set
> CONFIG_BLK_DEV_RAM=3Dy
> CONFIG_BLK_DEV_RAM_COUNT=3D16
> CONFIG_BLK_DEV_RAM_SIZE=3D49152
> CONFIG_BLK_DEV_RAM_BLOCKSIZE=3D1024
>=20
> Thanks
> Siva
>=20
I think it's not a kernel problem but a problem related with the=20
compression method instead. Check out how you are compressing the
ramdisk.
--=20
Marco Stornelli
Embedded Software Engineer
CoRiTeL - Consorzio di Ricerca sulle Telecomunicazioni
http://www.coritel.it
marco.stornelli@coritel.it
+39 06 72582838
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: RAMDISK: ran out of compressed data
2008-07-08 22:54 ` Siva Prasad
@ 2008-07-09 7:05 ` Marco Stornelli
0 siblings, 0 replies; 4+ messages in thread
From: Marco Stornelli @ 2008-07-09 7:05 UTC (permalink / raw)
To: Siva Prasad; +Cc: linuxppc-embedded
Siva Prasad ha scritto:
> Hi,
>
> The same ramdisk works fine for 2.6.15 kernel. We are just upgrading to
> a new version, and would like to get that ramdisk to work on the new one
> as well.
>
> Can you please elaborate on what you mean by compression format. Mine
> currently use the standard .gz extension/compression.
>
> Thanks
> Siva
>
>
> Siva Prasad ha scritto:
>> Hi,
>>
>> I am getting the following error when I tried to boot with ramdisk.
> Any
>> specific reason or clue why this is happening?
>>
>> RAMDISK: Compressed image found at block 0
>> RAMDISK: ran out of compressed data
>> invalid compressed format (err=1)
>>
>> I am running into this on 8641D runing 2.6.24-rc6 kernel. My .config
>> around block area are...
>>
>> CONFIG_BLK_DEV=y
>> # CONFIG_BLK_DEV_FD is not set
>> # CONFIG_BLK_CPQ_DA is not set
>> # CONFIG_BLK_CPQ_CISS_DA is not set
>> # CONFIG_BLK_DEV_DAC960 is not set
>> # CONFIG_BLK_DEV_UMEM is not set
>> # CONFIG_BLK_DEV_COW_COMMON is not set
>> CONFIG_BLK_DEV_LOOP=y
>> # CONFIG_BLK_DEV_CRYPTOLOOP is not set
>> # CONFIG_BLK_DEV_NBD is not set
>> # CONFIG_BLK_DEV_SX8 is not set
>> CONFIG_BLK_DEV_RAM=y
>> CONFIG_BLK_DEV_RAM_COUNT=16
>> CONFIG_BLK_DEV_RAM_SIZE=49152
>> CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
>>
>> Thanks
>> Siva
>>
>
>
> I think it's not a kernel problem but a problem related with the
> compression method instead. Check out how you are compressing the
> ramdisk.
>
Yes, I meant a problem about gzip or bzip2, but if it works with
2.6.15....I don't what is the problem.
--
Marco Stornelli
Embedded Software Engineer
CoRiTeL - Consorzio di Ricerca sulle Telecomunicazioni
http://www.coritel.it
marco.stornelli@coritel.it
+39 06 72582838
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-07-09 7:03 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-08 0:21 RAMDISK: ran out of compressed data Siva Prasad
2008-07-08 6:58 ` Marco Stornelli
2008-07-08 22:54 ` Siva Prasad
2008-07-09 7:05 ` Marco Stornelli
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.