On Monday 03 March 2003 10:29 pm, jokerman64 wrote:
> > When trying to install 9.1 RC1, I get the following error and then the
> > computer just freezes:
>
> I got this exact same error as well
>
> > "Could not uncompress second state ramdisk. This is probably a
> > hardware error while reading the data. (This may be caused by a hardware
> > failure or a Linux Kernel bug)"
>
> Yup
>
> > The log window shows:
> >
> > * trying to load /tmp/image/Mandrake/base/mdinst_state2.bz2 as a ramdisk
> > * reading compressed ramdisk: IO_ERROR
> > * unsetting automatic
> >
> > The kernel messages show:
> >
> > <6> end_request: I/O error, dev 03:40 (hdb), sector 1148956
> > <4> hdb: status timeout: status=0xc0 (Busy)
> > <4> hdb: status timeout: status=0x00
> > <3> hdb: drive not ready for command
> > <4> hdb: ATAPI reset complete
> > <4> hdb: irq timeout: status=0x00 (Busy)
> > <4> hdb: irq timeout: error=0x00
> > <4> hdb: ATAPI reset complete
> > <4> hdb: irq timeout status=0xc0 (Busy)
> > <4> hdb: irq timeout: error=0x00
> > <6> end_request: I/O error, dev 03:40 (hdb), sector 1148960
>
> Even the error message is the same except it complained about dev hdd (my
> dvd-rom)
>
> > This computer has an ASUS A7N8X motherboard with the integrated
> > NVIDIA nForce 2 chipset. It also has an AMD XP 2000 CPU.
> > BTW, I get the same errors when trying to install Mandrake 9.0.
> > I currently have Mandrake 8.1 installed
> > but I installed it on my drive using a different computer.
>
> I have an AMD XP 2000 CPU. Anyway I found a resolution. USE A NEW CD!
> Did wonders really. I was trying to burn an old (read OLD) cdrw disk
> because I didn't want to waste my roomates good ones. The installation
> didn't work and I decided to try with new media installation went perfectly
> (except for me not being able to change lilo settings at install time). I
> suggest you try a new cd-r or burning a new disk. I used k3b and a usb
> phillips 400 series to burn.
>
> > ------- You are receiving this mail because: -------
> > You are on the CC list for the bug, or are watching someone who is.
Ok, now i'm confused. i recently used (couple of hours ago) a cd to try and install
9.1 RC2 on a laptop. I didn't get all the way through because the laptop i
"commandeered" wasn't mine and needed tobe used for other purposes.
Regardless, on the laptop i did get to an installation screen and got as far as the
Update/Install dialog. Fast forward to a couple of minutes ago and i try the same
thing on my computer. I get the same bloody error message.
Now obviuosly the disk working on one computer (ibm laptop) and not working on another
(custom built desktop) isn't a problem of faulty media. this leads me to believe that
the kernel is in fact at fault or maybe ACPI support in the kernel.
I'm going to try this again with ACPI support disabled and then enabled in BIOS to
see what happens.
On a very distressing sidenote the botched installation seemed to have somehow messed
up CMOS or wherever the bios memory is kept. After hitting the restart button (i was
instructed at the console that i could do so) i decided to shut down instead.
A couple minutes later i turned on the computer and i had to reset everything in bios.
It looked just as it did after i put it together and turned it on for the first time.
If i manage to get this to happen again (and i'll try my damndest) i'll file a bug
report.
But for now i suggest reopening this one in case it was closed because of my previuos
reply.
--
I:
The best way to make a silk purse from a sow's ear is to begin
with a silk sow. The same is true of money.
II:
If today were half as good as tomorrow is supposed to be, it would
probably be twice as good as yesterday was.
III:
There are no lazy veteran lion hunters.
IV:
If you can afford to advertise, you don't need to.
V:
One-tenth of the participants produce over one-third of the output.
Increasing the number of participants merely reduces the average
output.
-- Norman Augustine
