Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

Yesterday I got my new laptop and switched from Mac OS X to Ubuntu. The graphics chip is an intel 3000 chipset of the new sandy bridge processors. Now, I am having trouble with my external monitor, a dell ultrasharp connected via VGA. (at the moment)

The situation I want to have:

  • Monitor disconnected, laptop lid open: laptop screen
  • Monitor disconnected, laptop lid closed: suspend/hibernate
  • Monitor connected, laptop lid open: two screens side by side, of course with max. solution. The external monitor should be the main screen.
  • Monitor connected, laptop lid closed: external monitor as main monitor, laptop screen switched off.

That used to work on my mac quite well; When I closed the lid it hibernated, but I could wake it up by typing on the keyboard while the laptop was closed and the external monitor showed the picture.

Now, I have several problems with Ubuntu.

  • Connecting the monitor while the laptop is running produces bad pictures, the monitor is flashing and I have to pull the cable. When the monitor is connected while booting, it works side-by-side
  • Unity: when I close the laptop, everything becomes black and doesn't react anymore, even though in the system power settings I set the behaviour to "blank screen". Opening the laptop again, results in a black picture on both monitors, only the mouse arrow is visible. But still nothing reacts and I have to reboot the laptop manually.
  • Ubuntu classic: Here, when I close the laptop, the external monitor shows the desktop, but in bad resolution. In the monitor settings, I recognize that the system thinks it is the laptop monitor. (detect monitors) After opening the laptop again, it becomes black just like when unity is running and I have to reboot.

After some googeling, I feel like some other people have the same problems using natty. What could I do about it?

share|improve this question

1 Answer 1

up vote 1 down vote accepted

I solved it using an old kernel 2.6.37. Apparently, the new 2.6.38 branch has problems with the Arrandale chips.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.