I have as of yet to see my desktop

[Mecharius]

I hit q to quit and am now back at

root@ubuntu:/#

[r.stiltskin]

So you will better understand what we're trying to do: chroot in and of itself doesn't solve anything. All chroot does is change what the system views as its root file system.

You can't boot to your Ubuntu partition, so you're booting with a CD. Therefore, your system regards the files on the CD as its root file system. If you try to install or uninstall anything, you're trying to modify the files on the CD, which is pointless. You need to modify the files on your hard disk. Therefore, you "chroot" into the file system which you installed on /dev/sda1 -- the first partition on your hard disk. Now the system regards that partition as its root file system, and any changes you make will be reflected in the files on your hard disk.

Then when you "exit" from the chroot environment, you're back in the CD's file system.

Hope that helps.

[Mecharius]

x out the terminal and started back over. sudo su took me back to being:

root@ubuntu:/#

put everything in again, checked twice for mistakes, none. Hit enter:

root@ubuntu;/#

put in

apt-get remove amd64-microcode
apt-get autoremove

This gave me:

E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

[r.stiltskin]

x out the terminal and started back over. sudo su took me back to being:

root@ubuntu:/#

put everything in again, checked twice for mistakes, none. Hit enter:

root@ubuntu;/#

put in

apt-get remove amd64-microcode
apt-get autoremove

This gave me:

E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

Exactly when did you get that message? After "apt-get remove amd64-microcode" or after "apt-get autoremove"? Were there any other messages (and when?)

[Mecharius]

came up after both.

[r.stiltskin]

And there were no other messages before that one? (Immediately after "apt-get remove amd64-microcode"?)

[Mecharius]

root@ubuntu:/# apt-get remove amd64-microcode
E: dpkg was interrupted, you must manually run 'sudo-dpkg --configure -a' to correct the problem.
root@ubuntu:/# apt-get autoremove
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
root@ubuntu:/#

[r.stiltskin]

As things stand, I can't tell whether you actually have uninstalled the amd64-microcode package or not. (I think not.) It appears that dpkg is simply refusing to do anything, including that removal, until "configure" is completed. It sounds like something went wrong when you installed something (who knows what) in a previous session. I just don't have enough information.

If you have nothing else to report, you should simply run that one single command, and then post back with as much information as you can glean from the output it gives you. It's probably going to be too much to post here in full, so you'll have to make your best effort to try and distinguish which parts are important. So just run this single command:

dpkg --configure -a

By the way, dpkg is the "back-end" program that apt-get calls to install, uninstall, and update packages. That error message is just telling you that there is a package (or packages) that was not successfully configured some previous time that dpkg ran. Running this command will (hopefully) complete that process.

Then tell us what the output was & we can try to figure out what to do next.

[Mecharius]

ran the dpkg, this is what I was given.

Setting up amd64-microcode (1.20120910-1) ...
Using per-core interface to update microcode on online processors...
update-inttramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.5.0-27-generic
root@ubuntu:/#

So my next guess would be to go on with the apt-get remove, but due to recent events, i wish to wait and see what suggestions are made?

[r.stiltskin]

And in fact, it may not even be necessary or appropriate to remove amd64-microcode because the actual problem may be related to whatever was not properly configured in that previous session a week ago. Furthermore, for all we know, you may not even have installed amd64-microcode yet.