Gutsy LiveCD won't start on Vaio SRX51 & SRX41

This is related to bug #143958 "Gutsy Alternate fails: cannot detect and mount CD-ROM" since between the two bugs Gutsy cannot be started or installed on these notebooks.

I would like to add my voice to this. I have a SRX51P/B and the downloaded Gutsy install CD-ROM (the standard one) refuses to boot sensibly -- it appears to boot fine but as soon as anything associated with the display and Xorg is supposed to happen I just get a black screen. I forced a boot in safe mode (which gave me 640x480 screen) and did an installation but this led to only being able to use the machine in 800x600 mode which is just not acceptable.

I have given up on Gutsy completely, and reinstalled Feisty from my original install CD-ROM plus updating in the usual way. This works fine.

I'm afraid my report would be Feisty 9/10, Gutsy 0/10 -- Gutsy just is not up to scratch :-(

PS I think my Bug #157077 may effectively be a replica of this bug report.

Same error on Fujitsu Lifebook S-4510, although this doesn't use external CDROM like some of the other laptops mentioned in bug #141646. It's an internal 24x IDE drive.

The Hardy Heron Alpha2 release will be coming out soon (around Dec 20). It would be great if you could test with this new release and verify if this issue still exists. I'll be sure to update this report when Alpha2 is available. Thanks!

Hardy Heron Alpha2 was recently released. It contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks!

I downloaded and burned a CD of Hardy Heron as at 2007-12-30 12:00 then tried booting from it on the Sony PCG-SRX51P/B. The boot appeared to go fine, but X failed to start:

/etc/gdm/failsafeXServer : line 47: [: too many arguments
Warning: Could not retrieve EDID because get-edid is not installed (1)
open_sock (): Permission denied
: error: this program does not know how to configure the "10
shared/default-x-server deosn't exist" X server
Warning: Could not generate /etc/X11/xorg.conf.failsafe for vesa
driver.

I tried the CD on my AJP M3000N and it won't boot at all on that machine, it just hangs immediately and after 30s or so the processor fan starts and that is it :-(

I will try it on my workstation but that is this machine so I will commit the message first!

The CD boots perfectly on my workstation so there are still problems with booting on a Sony PCG-SRX51P/B and there are new very severe problems on AJP M3000N (on which the Gutsy CD boots fine. I guess I need to start a new separate issue?

Thanks for testing Russel. If you could open separate bug reports for the new issues you are witnessing that would be much appreciated. Thanks.

A 'linux' task has been opened against the actively developed kernel. However, against linux-source-2.6.22 the task will be closed until we can find an appropriate fix. At that point we will re-evaluate it's candidacy for an SRU. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!

OK, let's close this one, I will open new reports for each of the machines that the Hardy Heron alpha 3 does the wrong thing on.

Thanks.

I just thought I would report that although the Feisty -> Gusty upgrade failed on my PCG-SRX51P/B last November, I tried it again yesterday and it worked fine. I have no idea what change has made the difference, but it did. So I am now happily running Gutsy on this machine. Hopefully the upgrade to Hardy will be possible -- the machine can only take 384MB memory!

I upgraded to Hardy and there seems to be no trouble at all (well apart from not removing various packages but that seems to be a general problem). I just tried the Hardy Live CD and it booted fine -- except that it came up ion 800x600 mode and not 1024x768. So it seems as though time might have passed this bug by.