Ubuntu
linux package

Installation CD or USB drive won't boot in Everex

Bug #571366 reported by Sam Williams
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Last week I took aone of my laptops, An Everex Cloudbook, and upgraded from Karmic to Lucid. There were a few python issues that I couldn't correct. I decided I would do a fresh install of Lucid release and hoped that cleared up the problems. I downloaded ubuntu-10.04-rc-desktop-i386.iso (md5sum 9b88dce8d215a3c2839105ab8e3139be), verified its md5 hash, then burned to a cd. The cd wouldn't boot in the laptop. Thinking it could be the media, I burned it on other blank CD-ROM's I had. Still no luck.

Finally I used the startup disk creator tool to create a bootable usb drive. It wouldn't boot either even though I had made sure that booting from usb-device was first when looking for bootable media. I also tried using UNetBootin to prepare a bootable usb drive and still no luck.

This has led me to believe there is something in the boot.img or initrd.img that doesn't work with this particular laptop. I fixed my problem by performing a fresh install with a karmic cd ( 9.10). Once that was up and configured I went through and performed a distr-upgrade to lucid. This time the python worked properly.

The solution to the problem is a ridiculous way to go because it literally took 3.5 hours and that was upgrading from a pristine Karmic install.

Please take a look at this problem.

Thanks for the help!

Revision history for this message
Leo Arias (elopio) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
kernel-janitor (kernel-janitor) wrote :

Hi Sam,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 571366

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

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

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Leo Arias (elopio) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Leo Arias (elopio) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.