Quantcast
Channel: Ubuntu Forums - Installation & Upgrades
Viewing all articles
Browse latest Browse all 26379

Dual boot failure of 13.04 Studio and Windows Starter

$
0
0
Dell Inspiron Mini 1012
Intel Atom N450
BIOS A11
2G mem
250G HD
Windows 7 Starter
13.04 Ubuntu Studio 386 32 bit
unetbootin

There was no "Try Ubuntu first"

The install went well, and the guided partitioning was easy, I freed up 100G for the Ubuntu load.

SCSI1 (0,0,0) (sda) - 250 GB ATA Toshiba MK2565GS
#1 Primary 41.1 MB fat16
#2 primary 15.7 GB B ntfs
#3 primary 108 GB ntfs
#4 logical 124 GB ext4
#6 logical 2.1 GB F swap swap


When it came time to "select and install software" (or something like that) that were above and beyond the core, I selected all of the video/music/graphics/photo studio package sets.

It then came up with a "Fail" page, suggesting I retry or otherwise finish the install.

I removed the 1st package and tried again. Failure.

I removed all the studio packages and continued. Failure.

I decided I would load them later, and finished the install (which then went very smoothly). I loaded Grub in the MBR, as it suggested.

I rebooted and the menu came up to the selection of Ubuntu or Windows, I tried Windows.

Screen blanked, and the cursor hung halfway down the left side. After waiting a long time, I hit the power button.

What appeared to be a shutdown script ("acpid exiting")started looking for unattended update scripts, then executed a few more lines then turned off.

I rebooted and tried to start with Ubuntu Studio this time, but the same result occurred.

I retried several times, with and without the USB drive inserted. Same results.

I ran diagnostics, and everything checked out.

I booted from the USB and tried "Help", which took me right back through the Install process.

I tried booting from the USB in Rescue mode and ended up with basically the same result as "Help"

I then tried booting from the menu with the Ubuntu Recovery mode, and it ran through a blitz of instructions, eventually putting my at root at a command line. I haven't run real Unix in 20 years (and even then just barely knew how to find my way around), so didn't know what to do, but thought that it was a sign that *something* wasn't altogether wrong.

Where have I gone wrong and what should I do?

Viewing all articles
Browse latest Browse all 26379

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>