Results 1 to 9 of 9

Thread: Live CD Install Dies During Boot

Threaded View

  1. #1
    Join Date
    Aug 2005
    Beans
    117

    Live CD Install Dies During Boot (M2R32-MVP Issue)

    EDIT: For anyone who arrives through Search - I've edited the subject of this thread due to discovering part of the problem was the Asus M2R32-MVP Motherboard I have. This comes in later.

    Hi,

    I'm running Gutsy at the moment, I'm trying to do a fresh install of Hardy. I cannot get the live desktop CD to run (have tried multiple burns and CD passes its verification check).

    I turned on Safe Graphics mode and to get more information I also removed the Splash and Quiet options from the boot line. I don't know how I can get an actual log file from a live CD, so the best I could do was copy down the error messages by hand. I got the following:

    Code:
    end request: I/O error , dev fd0, sector 0
    end request: I/O error , dev fd0, sector 0
    Buffer I/O: I/O error , dev fd0, locical block 0
    ata1.00: qc timeout (cmd 0xec)
    ata1.00: failed to IDENTIFY (I/O error, err_mask 0x4)
    failed to recover some devices retrying in 5 secs
    I then get an endless cycle of repetition of the above with some minor variations for other ata numbers (ata2.00, ata3.00, ata4.00) along with the occasional message that a particular numbered SATA link is UP or DOWN.

    It may be significant that earlier in the message list (though apparently before it errors properly), I see the line:
    Code:
    floppy drive fd0 is 1.44M
    I have no floppy drive. Nor IDE drives. My hardware is as follows:AMD Barcelona Dual Core 5200 CPU, Asus M2R32-MVP motherboard, 4GB DDR800 RAM, Samsung SATA DVD-RW, Radeon 2600HD Pro Graphics card, 2x 160GB HDs with Ext3 filesystems.

    To the best of my knowledge, my hardware is good. I'd really appreciate any help with this as I'd really like to get the new Kubuntu on my machine. Also, as this is a problem right out of the box, I'd imagine that there are other people out there who have the same problem and are getting a very bad first impression of Kubuntu so fixing this might mean solving a bug in the actual Kubuntu install.

    Anybody?

    Thanks a lot,

    Harmony.
    Last edited by H4rm0ny; April 27th, 2008 at 04:27 PM.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •