0

I installed 12.10 on my 11-inch mid-'11 Air without a hitch. I removed Unity and installed Cinnamon in its place. I purged every Unity-related package from the system. Today, the kernel updated and broke my machine. I can't get to the GRUB menu and I am told that the computer is running in low-graphics mode, even though I can't do anything with the options presented by the dialogues. nmcli refuses to connect to my network. I need a way to get the system working again, preferably without using a reinstall or install disk.

lspci -nn | grep VGA produces:

00:02.0 VGA compatible controller [0300]: Intel Corp. 2nd Gen. Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09)

X Log

A Happy Update!

Turns out my problem was I never ran update-grub. So right now, I'm rebooting with Unity installed again to see if it makes a difference.

A Happier Update

The problem now seems to lie with the new kernel. It won't recognize my wireless card. But this problem can be considered closed, methinks.

Eliah Kagan
  • 119,640
jaccarmac
  • 11

2 Answers2

2

jaacarmac solved the problem in his post:

A Happy Update!

Turns out my problem was I never ran update-grub. So right now, I'm rebooting with Unity installed again to see if it makes a difference.

A Happier Update

The problem now seems to lie with the new kernel. It won't recognize my wireless card. But this problem can be considered closed, methinks.

Community
  • 1
Seth
  • 59,332
0

When something like this happens to me, I usually boot from an older kernel image - which I choose in the GRUB menu as @gertvdijk already suggested.

Since you don't see the GRUB menu, I recommend you take a look at your conf file:

sudo vim /etc/default/grub

(or substitute with an editor you're comfortable with - nano, emacs...) Check what your values for GRUB_HIDDEN_TIMEOUT_QUIET and GRUB_HIDDEN_TIMEPUT are. If you're ending up with a shell, you must have passed through GRUB. If nothing else works, try setting your GRUB_DEFAULT value to something other than 0 - probably 1 (try experimenting until you pin-point the correct kernel image).

Once you're done editing the file, run

sudo update-grub

to apply the changes.

If this works, a fix will probably be out by the next kernel version, but you can help the process by checking to see if you can report this bug.

metakermit
  • 2,650