Search:

What was supposed to be two weeks became five. I hope I am not completley forgotten, because as soon as is possible I would like to continue on with this where I left off. I am going to take the time...

Unfortunately I am at a temporary stopping point. My employer requires me to go off for two weeks to a place where I can not take any of my machines with me. I must leave early morning, so I must...

I tried booting ubuntu without edits, i was given the sp5100_tco again. Replaced quiet splash and was given this after the scrolling information:

[ 1.174720] microcode: Microcode Update...

I shall do that, and then post the results.

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...

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...

came up after both.

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

...

I hit q to quit and am now back at

root@ubuntu:/#

So I tried going back from the beginning with:

fdisk /dev/sda
this gave me

Command (m for help)
So I hit m to see what it gave me:
[code]Command action
a toggle a bootable flag
...

Going to go back over your post, check to see if i missed something again. Just to be certain. And then try again.

corrected the issue with the typo and put it back in terminal, checked it over three times to be certain. No issues. Hit enter, and it gave me the prompt again:

root@ubuntu:/#
So no change, so...

I am trying to force myself beyond the point of typos. My typing has made major improvements just through these past 14 pages. That, and again, i can only have one machine logged in at a time and my...

For some reason, some of the spacing is off in that, not sure why. But I think in this case the spacing is not important. its the wording I am concerned with.

I posted that up as much to get suggestions on how to dig through as to have a copy in a place other than the terminal so I can read through it.

sudo su
root@ubuntu:/home/ubuntu# TARGET=/media/sda1
root@ubuntu:/home/ubuntu# mkdir -p $TARGET
root@ubuntu:/home/ubuntu# mount /dev/sda1 $TARGET
root@ubuntu:/home/ubuntu# mount -bind /dev...

Yes, you are correct, some how the "still in the same terminal" managed to escape me as I moved through this. I apologize.
I decided to put them in individualy:

sudo su TARGET=/media/sda1
this...

I shall try that now.

I am not seeing any issues in what I put into terminal in comparison to what you gave me. So maybe I am doing something wrong?


TARGET=/media/sda1
mkdir -p $TARGET
mount /dev/sda1 $TARGET...

The fdisk listed it as being in /dev/sda1

Now the second set of code you gave me I ran, and it gave me:

chroot: cannot change root directory to /media/sda1: No such file or directory
I am...

I am back to the point where the only way I can get to a desktop is by using the "try Ubuntu" on the disk. But at least that works. I was partialy afraid that not even the disk would get me back to...

And the same for the 17. I am beginning to think I may need to go back to the disk and start over. Whatever I damaged by accident must have been important.

the 3.5.0-26-generic gave me the same. acpi=off did not make a difference.

Yes, recovery mode. Will try the older two next.

I was past the need for nomodeset, but then i managed to mess something up when I was in as root. Already tried going back to using that but it did nothing for me now.