Trouble trying to boot from live cd

[Qqmike]

Well, if it is a UEFI computer, then you must be certain you are booting the flash drive or DVD in whatever mode you intend to boot it: either in UEFI mode, or in BIOS mode (this is what you have told us above). My how-to shows an example of setting things up to boot in UEFI mode, section titled "Installing the OS in UEFI mode":
https://www.kubuntuforums.net/showth...l=1#post379977
As you can see, your UEFI firmware ("BIOS") settings must be set right: in your case, for non-UEFI booting. Every UEFI/BIOS firmware setup menus may be differently quirky.
Rod Smith is the expert on this and issues:
http://www.rodsbooks.com/efi-bootloaders/

[Qqmike]

(Deleted--duplicate post to the above; the forum's settings caused this, somehow.)

[mr_raider]

Are your drives set to ahci mode? Are you sure you are not booting in raid mode?

If it's not that try booting a 16.04 distro like kubuntu 16.04 or KDE neon.

Sent from my ONEPLUS A5010 using Tapatalk

[geekusprimus]

Allow me to clarify once again:
My motherboard, although UEFI capable from what I can tell, is booting in legacy mode. Even if that weren't the case, I have booted from my disc drive in both AHCI mode and UEFI mode (which produced even more errors). I will try 16.04 and see if that works and let you guys know.

[mr_raider]

Its clearly not a UEFI error since you are getting kernel error messages. That means grub has loaded.

Trouble shooting these problems can be annoying. One thing you can do is disconnected every drive but the target installation drive. Use the USB to boot.

I only have AMD hardware so I can't help you much on this specific hardware. My mom has a core i7 4770 running Mint KDE so I know it's not a chipset issue.

Sent from my ONEPLUS A5010 using Tapatalk

[geekusprimus]

Awesome! I disconnected my SATA2 drives (my storage drive and the DVD drive) and it worked just fine. Thanks, guys!

EDIT: Minor issue - Kubuntu will only boot properly if my SATA2 drives remain unplugged. If you guys know of a good solution or a patch I can install, that would be great.

[Bings]

Do you have more than one type of SATA socket on your motherboard? When I got my latest motherboard, I plugged in the wrong socket and it caused constant problems booting up Linux (with the odd exception of Trisquel). Moved it to a different socket and fixed. I can't remember the technical difference off the top of my head but I moved it to a different colour one

[jglen490]

And that is what is related to the kernel and modules that the install media is trying to boot for purpose of setting up the install environment, and the resultant errors thrown from the live DVD environment. This may not be the same kernel and module combination that the DVD would eventually install to the PC's environment.

If they are the same, then even if the DVD successfully boots with changes made to how the drives are plugged into the mobo, the installed Linux may then fail if the drives are moved back their original plugged in locations on the mobo.

So, yes, the SATA level may be a continuing problem if the kernel modules don't work with the SATA level associated with a specific mobo's SATA ports. It's a dependency on the implementation within a "BIOS"/firmware configuration burned into the mobo.

[jlittle]

Minor issue - Kubuntu will only boot properly if my SATA2 drives remain unplugged.

That suggests those devices are ahead of the one with Kubuntu in the boot order, and there's one or more boot loaders, possibly fragmentary or borked, on them. I suggest checking the boot order in the firmware (often called the BIOS, sometimes loosely).

Sent from my Vodafone Smart ultra 6 using Tapatalk

[geekusprimus]

I can get to the GRUB screen, similar to booting from a disk or USB, but I still get errors when I boot up. I've checked the boot order, and no matter where I put my Kubuntu drive, it gives me errors when I try to boot up.

As a minor correction from earlier, all my drives are connected via SATA3. There's a sticker on the motherboard over two of them and all of the SATA2 ports, so they looked like they were SATA2. Anyway, the two sets of SATA3 ports (A0, A1 and 0, 1) are slightly different. The ordinary numbered ports are connected to an Intel SATA3 controller, whereas the A ports are connected to an ASMedia ASM1061 SATA3 controller. The motherboard manufacturer recommends placing bootable drives on the Intel controller, so I switched my solid state OS drives over to it and moved my storage drive and my DVD drive to the other one. Although my Windows installation is now booting up faster than ever, I still can't get into Kubuntu unless I remove my other drives.

That suggests those devices are ahead of the one with Kubuntu in the boot order, and there's one or more boot loaders, possibly fragmentary or borked, on them. I suggest checking the boot order in the firmware (often called the BIOS, sometimes loosely).

The only drive other than my Kubuntu drive that could have a boot loader installed on it would be my Windows drive, which has had zero problems with dual-booting.

My best guess at this moment is that Kubuntu is somehow struggling with the fact that I'm using two different SATA controllers.

[mr_raider]

I did a quick search and the internet seems littered with problems on the asmedia 1061 controllers, particularly on asrock boards.

What modes are available in your bios for these ports?

Sent from my ONEPLUS A5010 using Tapatalk

[geekusprimus]

I have an option to switch between disabling the controller, IDE mode, and AHCI mode. I tried disabling the controller just to see if I could boot (since my Kubuntu drive is on the Intel controller now), which was such a disaster that I had to perform a hard reset on my BIOS to gain access to it again. I also have an option to enable or disable the SATA boot ROM, which seemed to affect nothing as far as trying to load Kubuntu is concerned.

I have checked, and my BIOS features the most recent firmware. I was under the impression from doing my own quick search that there might be a patch or updated Ubuntu driver for those controllers, but the post was also nearly seven years old and may no longer apply.