If anybody's running Ubuntu 12.04 here, try out this ppa:
It worked on my HP mini 210-4000
Follow the instructions here http://daily.siebler.eu/2012/06/ubuntu-12-04-driver-for-intel-cedarview-atom-n2000-und-d2000-serie/
I have Linux Mint 13 Mate 64-bit on my netbook with an N2600 CPU(GMA 3600 GPU), and the resolution is perfect, and I can watch video and Flash with no problems. No problems playing 720p and 1080p, but the CPU usage is at about 80% for 1080p. If there was a linux driver for the GPU, then the that would take all the work off the CPU. EDIT: And playing 1080p video files, the CPU is at about 60-65% usage.
Don't know what problems other people are having.
Mine doesn't work at this step:
xabix@HTPC:~/.config$ sudo apt-get install cedarview-drm libva-cedarview-vaapi-driver cedarview-graphics-drivers
Reading package lists… Done
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
cedarview-drm:i386 : Depends: dkms:i386 (>= 1.95) but it is not installable
Depends: linux-headers-generic:i386 (>= 2.6) but it is not going to be installed or
linux-headers-generic-pae:i386 (>= 2.6) but it is not going to be installed
cedarview-graphics-drivers:i386 : Depends: xserver-xorg-core:i386 (>= 2:184.108.40.2061) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
but the depedencies are installed maybe because I run 64 bits precise?
I currently bout a linux based laptop using the cedar trail cpu, but with a different dedicated gpu. Will keep you updated.
Dear Intel, I realize that some linux enthusiasts are quite hot-headed. However, I would greatly appreciate proper support for the cedar trail cpu. In exchange, I promise to let every linux forum that a regularly visit know that proper support has been provided.
I have really enjoyed using your chips in the past, and hope to continue doing so.
thees matherboard people conecting to monitors and speekers, now over hdmi so vy cant use these bords.
Only for small servers.
Unique dn2800mt it is, gpu driver will by in future.
There is an alternative: Download MeeGo, store its file system somewhere as an archive, and copy out the kernel, modules, xorg, and associated powervr libraries into a compatible Linux system like slackware and possibly Ubuntu, which has been known to start up with a foreign kernel without crashing.
Gee whilikers, guys, the latest netbook Meego has a working xorg for the powervr chip. All you need is a Linux that can be installed on your netbook as is, then altered, copying the Meego kernel, modules, xorg and powervr libraries into the netbook Linux. There are several versions of Slackware on which that approach works resoundingly well; and some, but not all, versions of Ubuntu can be subverted into using the pieces from Meego. The meego kernel has built-in alsa sound which is extremely good, it has built-in cpufrequency ladder permanently set to 'ondemand' and it boots up to a gma500 framebuffer (/dev/fb0) text console which you then follow by startx to get the MeeGo xorg directory into action. This probably means you need a rescue flash stick system like RIPLinuX to do all this subverting.
When your Xorg.0.log finally reads:
[ 838.877] PVRPreInit: done
[ 838.877] (--) Depth 24 pixmap format is 32 bpp
[ 838.877] (II) pvr(0): [DRI2] Setup complete
[ 838.877] (II) pvr(0): [DRI2] DRI driver: pvr
[ 838.877] (II) EXA(0): Driver allocated offscreen pixmaps
[ 838.877] (II) EXA(0): Driver registered support for the following operations:
[ 838.877] (II) Solid
[ 838.877] (II) Copy
[ 838.878] (II) Composite (RENDER acceleration)
you'll know you have copied in all the relevant MeeGo powervr libraries. Don't forget /etc/powervr.ini and put 'video=LVDS-1:d' on the kernel command line in grub. And, remember to delete the original /usr/lib/xorg directory that comes with your system before replacing it with the one from MeeGo.
To add on this
These drivers were made for us at Canonical for OEM machines shipping Ubuntu 12.04 because the meego drivers don't support 12.04 userspace.
There is no 64 bit support and there never will be unfortunately, and they also do not work with >=4GB ram in the machine.
There is nothing we can do about that, they don't even make 64 bit windows drivers for the machines. Also, the drivers will only ever work in 12.04 (where they will soon be uploaded to for 12.04.1),
They wont update them for 12.10 and newer. Sorry to bear the bad news but these machines are an absolute nightmare and this was the best we could get
I must not be as hard to please as some of the people on this group. In fact, I get remarkable 3dfx from the full Meego setup on slackware. I don't know what anyone has to be apologetic for, it is a fairly robust, yet interesting graphics chip. And it is for a desktop board with modest ambitions. So what is everyone so critical about? You'd think you were engaging in personal attacks, rather than dispassionate professional evaluation. Especially, if a psychological test of your own eye resolution would yield insensitivity to the claimed effects.
Anyway, this morning as a lark, I installed the kernel-adaptation-pc-3.0.0-10.1.i586.rpm kernel package from the Meego repository on my test slackware system, leaving Xorg intact, and added a 'Modes' line to the xorg.conf file with my monitor resolution (another realistic use of resources based on the Intel minimalist philosophy), and changed from vesa to fbdev. It actually works, rather well, using the gma500 colour framebuffer as basis. It runs the peacekeeper benchmark with a value of 760, right up there with the full Meego installation and previous attempts using 915resolution and uvesafb (URL: http://peacekeeper.futuremark.com/results?key=5dtR&resultId=2507912 ). And everything else I care about, like the fonts being in good focus, and the Mplayer system working, is right there.
vtailor, I don't quite understand why do you need a Meego kernel if you only use fbdev. Recent kernels (> 3.4) support it directly. The problem is that the Meego package (not only kernel, but also vaapi and xorg that provide video acceleration) are i386 and do not support 4 gb ram. Nothing to be happy given that the cpu is capable of EMT64/amd64 and boards do support 4 gb ram.
Mary, if you don't understand the fine points of working with the Cedarview, why are you on this group? With the MeeGo kernel, you get a frame buffer that will let fbdev.so draw the screen in monitor resolution. All you have to do is add a
line to /etc/X11/xorg.conf
With a standard distribution kernel, you get a vesafb frame buffer by requesting it on the command line. And adding, e. g., 'Modes "1366x768"' simply doesn't work with fbdev.
If you have Nothing to be happy about, why don't you keep it to yourself, since it is irrelevant to me.
For those who don't know it, Meego is defunct. Hacking around with a defunct kernel is hardly the optimal solution to the problem of a lack of drivers. As can be seen in this thread and elsewhere, the results are rarely successful.
Intel needs to provide Linux drivers for the Atom Cedar Trail, because right now, these CPUs are crippled where Linux is concerned.