Weird error message with root disk - and crash

Weird error message with root disk - and crash

Post by Joachim Pauli » Tue, 07 Nov 1995 04:00:00



Installing Slackware 3.0 I get the following error message after
inserting the root disk with color.gz (or text.gz) on it:

CRAMDISK: compressed image too long
.
.
( a full screen of this and no more action )

This is after succesfull run of the bootdisk (scsinet2), detecting
correctly the network card and the scsi disk. My Hardware:
a P5 100MHz with 32MB RAM, NCR-SCSI adapter, SMC-Ultra network card
and ELSA Winner 1000 Trio64 PCI Graphics Adapter. Any idea whats going
on?

--
Joachim Paulini                  | Institut fuer Theoretische Physik

 
 
 

Weird error message with root disk - and crash

Post by Brian Smy » Fri, 17 Nov 1995 04:00:00



Quote:

>Installing Slackware 3.0 I get the following error message after
>inserting the root disk with color.gz (or text.gz) on it:

>CRAMDISK: compressed image too long
>.
>.
>( a full screen of this and no more action )

>This is after succesfull run of the bootdisk (scsinet2), detecting
>correctly the network card and the scsi disk. My Hardware:
>a P5 100MHz with 32MB RAM, NCR-SCSI adapter, SMC-Ultra network card
>and ELSA Winner 1000 Trio64 PCI Graphics Adapter. Any idea whats going
>on?

Try installing with the turbo switch off (non-turbo).  If that fixes your
problem, then replace your RAM.  Dont ask me why, but some ram works
sometimes, and other times it wont.  Maybe someone out there can tell us
why.

-Brian

 
 
 

1. Kernel error message booting root disk

I have now run into *two* people having the *same* problem booting Linux
up on a system that may be identical to the one I had no trouble at all
getting Linux to run on.  The system is an AcerPower 9000T 60 MHz Pentium
system.

I had no trouble getting Linux to boot using the Slackware Pro 2.0 CDROM
distribution.  The boot and root disks worked, and Linux started just fine.

However, both of the other two people are having trouble because their
systems choke when reading the root diskette.

One of them has indicated that he has done the following, after ftping
the boot and root images from standard sources on the net (as opposed to
using a CDROM as I did):

got a copy of "sbpcd.gz" with BINARY ON
got a copy of "color144.gz" with BINARY ON
gzip -d sbpcd.gz and color144.gz to get "sbpcd" and "color144"
used Rawrite 2.0 to xfer the image to two newly formatted disks
Tried them and got the same results, although it did detect my CD (yea!)
When it says to put the ROOT floppy in and I do, and hit enter, the Disk
Drive makes a weird read sound...hard to describe, but someone else had
the same symptom and it just comes up read error, only 1024 blocks
implemented (512) whatever that means...

I have traced this message down to the kernel module ll_rw_block.c, although
that module may not necessarily be where the malfunction is occurring.

This does not seem to be a problem with getting Linux to work on a
Pentium, nor does it seem to be a problem specific to the AcerPower 9000T
(since Linux works quite well on mine).  But it does seem to be a problem
with recognizing the size of blocks on the floppy (I think), which could
indicate a problem with the boot or root images, or the sources or
options used to compile them.  (I believe these were Slackware kernels,
and thus may be 1.0.9, if memory serves me correctly.)

Can anyone help the people having these problems?

2. Xwindows

3. Weird messages followed by crash...

4. packet from unknown router

5. Weird Message to root tty...

6. Umax Astra 2200 USB/SCSI Scanner

7. root disk file system and nfs server from boot/root disks.

8. hackers invading

9. root disk file system type and nfs server from boot/root disks.

10. Linux crashes when Root edits /var/adm/messages via Telnet - Why???

11. weird error messages in error_Log

12. weird error message in log...

13. Weird Error Message: What does it mean and how can it be corrected?