ubuntu-11.10-alternate-amd64.iso fails to boot

[Hadmut Danisch]

Hi,

I was just trying to install Ubuntu on a Foxconn NT-A3500 barebone, with ubuntu-11.10-alternate-amd64.iso. The machine does not have a regular CDROM drive.

* my usual way to use usb-creator-gtk does not work since usb-creator-gtk currently crashes with segmentation fault somewhere in the process

* I read somewhere that the 11.10 iso images can be copied to USB sticks directly. Boots into syslinux but then complains

  vesamenu.c32: not a COM32R images

* I have an external USB bluray drive. Burning the image onto an old fashioned CDROM brings indeed the installation process up. But after identifying the keyboard type the installation process aborts when the system wants to mount the CD somewhere, because the CD drive does not appear as a block device and such is not mountable.

Currently I do not see a clean and regular way to install ubuntu on that machine...

[Hadmut Danisch (hadmut)]

Correction: The method of directly copying the iso image to the stick works. The COM32R error message must have come from and older 10.04 LTS image I had copied onto the same USB stick to test the bugs in usb-creator-gtk.

However, the problem with booting from CD still exists.

Interestingly, booting from CD works when the USB stick is present at the same time, because the system then starts from CD and when it tries to mount itself instead uses the USB stick and successfully goes on.

[Hadmut Danisch (hadmut)]

...what, by the way, raises the question why the ubuntu installer was able to mount the USB stick, but not the USB bluray drive.

I guess this was because I had connected the USB stick to a USB 2.0 port, while the USB bluray drive needs two USB ports because of it's power consumption and therefore I had connected it to the front ports, which are USB 3.0 ports.

So maybe the reason is that the installer does not support USB 3.0 ports even when the device connected is a USB 2.0 device?

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/908601/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]