Installation Stops on 2.4.1 .ISO (blue screen)

[Guest]

[dmartin]

I am attempting to upgrade from 2.2 to 2.4.1. The efw-upgrade will not work so I am backing up the settings and using the .ISO. I tried this on a test PC work and successfully installed and restored my settings. When I go to try and install on the actual machine, I get the initial linux load and then the screen goes blue before it asks you the install language and just sits there. It doesn't appear to lock up, it just stops. Any ideas? I tried the NOUSB, NOPCMCIA and DMA options and none of them seemed to help.

Thanks!

[lo]

Hey dmartin,

if you type ALT+F3 you should be able to see the output logs of the installation...is there any error message?

Moreover, are you sure thate the image is not corrupted (is the hash right?)?

Thanks

Lo

[dmartin]

I used to the same install CD on a  of other computers and it comes up fine on them.

[lo]

And to you have the same hardware on each PC?
because if the hardware changes, you can have driver problems, dispalyed in the third console (reachable with ALT+F3)

[dmartin]

I hit ALT-F3 when it stopped loading and it's just sitting at the Sh-3.00# prompt...

[lo]

which is the output of

tail -n 30 /var/log/messages

to be fair, I don't remember if it is

/var/log/messages

or

/target/var/log/messages

I am trying to remember, but if you need I will try to make an installation and to say you the right log to check

Bye

Lo

[dmartin]

"No such file or directory" for either one.

[lo]

which is the output of

ls -l /

?

bye

Lo

[dmartin]

Here is the output.

[qzzx1k]

I have the same problem.   I went back to 2.2 RC1 and tried that, and was able to get a bit farther down the road, but still no install.   

------UPDATE-----------
found a "USB CDROM" and used it to install.   Works.  A bit slow for the install, but it works.  I think this problem may have something to do with the "re-detection" of the harddrives and cdroms after the initial boot.

[lo]

so now your system is up and running?

happy to know that, even if my posts were useless!

btw, you are probably right about the source of the problem...

[Quickspace]

Hi All.

I know this a old post but I had exactly the same problem trying to install Endian 2.5.1 on VMware server using a ISO. What fixed it for me was to change the CD IDE address from 1:0 to 0:1 under Virtual Device Modes.

Hope that helps someone.

[monocubo]

Hi to all!
today i was having the same issue with a new installation of 2.5.1, just booted it and I'd got this blue screen. At my BIOS settings I was trying to boot the CD from a secundary slave IDE, I just managed to change it to secundary master, and ... voilá! It just worked! So its seems to my like a trouble looking for the files in a path or something like that.
Thanks you all!