Do you get an error from modprobe?
cubie@Cubian:~$ modprobe --first-time sunxi_cedar_mod
ERROR: could not insert 'sunxi_cedar_mod': Module already in kernel
What does "uname -a" say?
cubie@Cubian:~$ uname -a
Linux Cubian 3.4.67+ #4 SMP PREEMPT Wed Nov 6 08:31:09 CST 2013 armv7l GNU/Linux
What does "find /lib/modules | grep cedar" say?
cubie@Cubian:~$ find /lib/modules | grep cedar
What does "dmesg | grep cedar" say (after the modprobe)?Nothing. It appears the cedar module is already compiled in the kernel. I am using the updated Cubian distro.
cubie@Cubian:~$ ls /dev/disp /dev/cedar_dev
ls: cannot access /dev/cedar_dev: No such file or directory
libvdpau seems to be installed correctly:
cubie@Cubian:~$ find /usr/lib/arm-linux-gnueabihf/vdpau/
Okay, first, if there's a .ko file, that means the module probably isn't baked into the kernel; it could be loaded at startup via /etc/modules. Also, if the module is built in, you will get something from "grep cedar /lib/modules/*/modules.builtin"; if it's not, you'll see entries in modules.order.
Second, even if the module's built-in, you should see something like this from dmesg:
[ 2.430857] [cedar dev]: install start!!!
[ 2.438009] [cedar dev]: install end!!!
So the question is why isn't it initializing. If the module is listed in /etc/modules, comment that out and try modprobe again from a command line. If you have a serial port, see if any errors pop up there.
Oh, and what's your kernel command line look like (cat /proc/cmdline)? You're not setting sunxi_ve_mem_reserve=0 to save memory, are you?