Some days ago, I was brave to do a "do-release-upgrade" call on my fit-pc2. Before it was 11.04 and now I am running Ubuntu 11.10.
But of course this only works with my own linux kernel. I had som 3.2.0-rc2 running from november. This kernel won't be replaced by Ubuntu. That's of course, what I wanted.
My first problem after upgrade was the music playback. It run too fast (!) and alsa threw error messages about buffer underrun.
So, I assumed some problems with my "old" kernel and the updated alsa userland libs/tools. And decided to upgrade the kernel by a fresh "git pull".
After this, the music is working again - but where is my gma500 driver gone? It moved from staging to mainline drivers/gpu/drm/gma500/ ?!
Alan Cox started last november the move. And now it will be finished with coming kernel release 3.3. The driver is called gma500_gfx now.
I'm really happy about this!
The only thing I had to change, is my kernel config.
There is still one issue open: On bootup, the X-server output is only shown in the top half of the monitor.
I found a simple workaround. I just stop and start the lightdm. This "fixes" the issue for me now. I hope this will be fixed in coming versions of the driver.
I place my fix in /etc/rc.local:
??stop lightdm
start lightdm
![]() |
I just realized that kernel 3.0.0 is available since friday. So I just compiled it with my config from 2.6.39 and... trara: it's working! Here you can find my new config-3.0.0 for the fit-pc2.
Compared to the last kernel upgrade, this one was quite easy. The psb_gfx driver comes still from the psb-dkms package.
What's new in kernel 3.0.0? First: the version numbering. After 2.6.39 follows now 3.0.0. Ok, if Linus like so, why not. We are working to long with 2.6. But I hope, the linux kernel is not following now the version numbering inflation like chrome and firefox...
There is a quite good site where the changes are explaned: http://kernelnewbies.org/LinuxChanges
Recently, I spent a couple of hours to update and upgrade my fit-pc2.
I started with the kernel which was running 2.6.37.1 with the psb driver for the Intel GMA500 (Poulsbo) graphics engine. Unfortunately this driver isn't maintained anymore and does not compile with 2.6.38 or even 2.6.39 kernels.
But in the meantime, a new driver entered the staging tree of the kernel and is already part of 2.6.39. This driver-directory is called gma500 but the module is named psb_gfx and the driver is named psbfb. This driver supports Kernel Mode Setting (KMS) and uses the fbdev driver from xorg.
It took me some hours to get this running. Of course because I even compile the kernel on the fit-pc2 which is not that fast. But the biggest problem was to find a working kernel config and the setting for the right display resolution. In my case the monitor is connected to DVI (on the HDMI plug) and has a native resolution of 1440x900.
Here is my kernel config for 2.6.39.2 and I had to change the grub default settings in /etc/default/grub for my monitor:
?GRUB_CMDLINE_LINUX="acpi_osi=Linux acpi_backlight=vendor acpi_skip_timer \
nomodeset video=DVI-D-1:1440x900 pci=nocrs mem=896mb"
Please note: the current driver doesn't support reading your monitor EDID data by itsself. It will start with 1024x768 by default. To get information about the connector (in my case DVI-D-1), I added the parameter "drm.debug=7" to the kernel command line.
I don't know why, but I still need a xorg.conf file. Without it, the USB keyboard and mouse won't work.
After the kernel, I upgraded Ubuntu from 10.10 to 11.04 without any problems.
With the new kernel, it was'n possible to use the sound as normal user. So I was checking the drivers and the permissions. After killing pulseaudio, it was possible for the root user to playback sound.
When reloading the alsa drivers there was always a strange warning I've never seen:
sudo alsa force-reload
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/ab/.gvfs
This was the solution: there were some permission issues for this userfilesystem. My solution was the following in the /home/ab/ directory:
sudo umount .gvfs
chmod 755 .gvfs
sudo /usr/lib/gvfs/gvfs-fuse-daemon .gvfs
I have a simple flatbed scanner connected via USB and this scanner didn't work with the new 2.6.39 kernel anymore. But why?
This was another permission issue because root was able to scan. In my kernel config I disabled CONFIG_USB_DEVICE_CLASS because it is marked as DEPRECATED. The current Ubuntu udev rules seems to prefer the old fashioned way. I had to change the permissions for the new style in /lib/udev/rules.d/50-udev-default.rules:
# libusb device nodes
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666"
This is of course a dirty workaround and no solution. But anyway. Let's wait for Ubuntu 11.10!
The scanner is found now and working as usual:
ab@ab-fit:~$ scanimage -L
device `plustek:libusb:004:009' is a Canon CanoScan N670U/N676U/LiDE20 flatbed scanner
On 20th October 2010 the linux kernel 2.6.36 was released. Yesterday I compiled it for my fit-PC2. This works without problems. When I install a custom kernel with
?dpkg -i linux-image-2.6.36_ab.1_i386.deb
the /etc/kernel/postinst.d/* scritps will be executed. One of these scripts (dkms) is building the psb (poulsbo) driver for this stupid GMA500 Intel graphics chipset.
But for 2.6.36 this fails with ?psb-kernel-source-4.42 :-(
The reason is explained in the make.log which is located in
/var/lib/dkms/psb-kernel-source/4.42.0/2.6.36/i686/log/:
psb_drv.c:988: error: unknown field ‘ioctl’ specified in initializer
So, something changed in the kernel API from 2.6.35 to 2.6.36 and the psb-driver is not up-to-date. After a quick search, I found a patch which repaired it for me. And I hope this patch is getting soon in the psb-kernel-source package.
Thank you for the patch!

Last Sunday, Linus Torvald released Linux kernel 2.6.35. Because I've just upgraded my "fit-PC2" to Ubuntu 10.04, I was ???courageous to compile the new kernel on this tiny Atom driven computer.
This took several hours because I was to lazy to deselect most of the features in the kernel.
I was a little surprised that the initrd wasn't build during installation of my build linux-image debian package. I had to copy manually the postinst script for the initramfs:
??cp /usr/share/kernel-package/examples/etc/kernel/postinst.d/initramfs \
/etc/kernel/postinst.d/
The kernel is working. But there is one strange message during booting the kernel. It seems not to hurt the system but anyway:
pci_root PNP0A08:00: address space collision: host bridge window
[mem 0x000c0000-0x000dffff] conflicts with reserved [mem 0x000d0000-0x000fffff]