12.04 boot failure after update manager ran

What video chip does it use?

you could try 2 things

1. It might not work, but it shouldn’t do any harm, so when you get to the GRUB boot loader, choose the Recovery Mode option below the default entry. When you get to a command-line login prompt, simply type your username, hit Enter, then enter your password, and hit Enter.

You will get to the Recovery Menu, on which you choose the dpkg option “Repair broken packages“. Note that you will need to be connected to the internet for it to retrieve the packages it needs.

You’ll see a lot of text fly by as it fetches packages and installs them. When prompted to reboot your computer, do so, and hopefully you end up at your login screen or desktop!

and 2. if this is the right model http://support.gateway.com/s/Mobile/Gateway/M210/5385nv.shtml

then downloading VGA driver says it is for:

one of the following Intel
    Chipsets:

   Intel(R) 830M Chipset
   Intel(R) 845G Chipset
   Intel(R) 855GM Chipset
   Intel(R) 865G Chipset
   Intel(R) 852GM Chipset
   Intel(R) 855GME Chipset
   Intel(R) 852GME Chipset
   Intel(R) 910GL Express Chipset
   Intel(R) 915GV Express Chipset

So in that case the problem would be with Intel video driver. To solve this, it would be best to add this in your grub line:

nomodeset nokms xdriver=vesa

This should bring you to the desktop so you can try to fix things. Also you could try to add Intel`s repo for their newest driver. To setup their packages, please read about it here: https://01.org/linuxgraphics/documentation/intelr-linux-graphics-installer

TO actionparsnip:

Intel(R)82852/82855 GM/GME Graphics Controller

This is the built-in controller.

It worked fine for a couple months on 12.04 until the update manager ran a couple days ago.

I am using XP IE as I have not been successful in getting Ubuntu to boot after several tries.

To Freedomrun:

Selecting "Recovery Mode: brings up the Recovery Menu without a logon.
selecting DPKG Repair broken packages - Gets messages:
                           FSCK from util-linux-2.20.1
                           /dev/sda5 has been mounted 30 times without being checked - check forced
                          /dev/sda5 400922/2883584 files (0.2% non- contiguous, 1942689/11517952 blocks
then goes to blank screen with blinking cursor - no login screen.
cntl-alt-del only way out of it and eventually goes back to GRUB.

I did eventually get a logon screen - don't know how I got there but 2 problems:
    I don't know how to connect to my wifi
    I don't know what commands to enter for dpkg.

Other problem I wouldn't have a clue as to how to add a line to the grub menu.

I am using XP IE as unable to boot ubuntu now.

The most simple would be to connect laptop and router with network cable untill apt checks repos and packages.

See : https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1188131
Andrew Duncan (andrew-duncan) wrote on 2013-06-06: Re: [Bug 1188131] Re: lightdm does not start on boot

"As a fairly acceptable workaround for this problem, enable /etc/rc.local and add the following lines to it:

/sbin/start lightdm
exit $?
It solved the issue for me.

hooked the t10/100 cable directly to the modem as suggested in #5.
got same results as in msg #4.

As for #6 - I can't get to a terminal and if I could I wouldn't know what the commands are to do #6.

I am using XP IE as unable to boot ubuntu now.

gksudo gedit /etc/rc.local

Add the commands above the 'exit 0' line

when you start up the machine and the GRUB (boot manager) shows on the screen pres "e" (e=edit) then at the end of second last line you can add : nomodeset nokms xdriver=vesa

you can see how it looks on this picture:
https://help.ubuntu.com/community/Grub2/Troubleshooting?action=AttachFile&do=get&target=g2_grub_edit_menu.png from the page: https://help.ubuntu.com/community/Grub2/Troubleshooting

..and at the end it should look something like on this attached picture: http://ubuntuone.com/1165nzey8INF13TqjDiKAR

Answer to #9

Was able to add the nonodeset nkms xdriver=vesa using e (edit) on the GRUB screen.

Answer to #6

after making change to rc.local next boot went into continous loop. error message said start lightdm already running.
removed code from rc.local and was able to reboot in recovery mode.

12.04 appears to boot up OK after latest updates installed by update program.