It's been one year since I published a compiled kernel for our devices. Now I decided to build a new one and share it!
Some facts about it:
- As all of my other kernels this one uses heartbeat during boot.
- It supports the dockstar, goflex net and home.
- Some of you asked for I2C support, it's now working on the dockstar and goflex net. i2cdetect -l has the desired output!
If you encounter any missing modules for certain devices, try to compile them yourself with the given headers and give me a hint so I can include them in feature releases.
In order to install the kernel properly, you need to have initramfs-tools installed. Otherwise your device won't be able to boot! Thanks to chessplayer for sharing this info!
apt-get install initramfs-tools
Make sure you have the latest uboot installed. See 1. in Dockstar: new Kernel 3.3.3 ready to use.
As you may have noticed, we were discussing things about newer kernels and drivers in the comments of Dockstar/Goflex: new Kernel 3.1.10 ready to use. With that in mind I started up my VM and looked at what I've got there in /usr/src - there was a compiled 3.2.1 that initially wouldn't boot. But following davy's guide to upgrade U-Boot makes that one boot.
Taking a look at kernel.org made me jealous... Here it is - a fully working 3.3.3:
It's now been a while since I installed the 3.1.0-1 kernel from sid and made some testing. But I don't like the LED beeing solid green during boot, I want to see whats going on. Thats why I decided to compile 3.1.10 with heartbeat from this erlier article: Dockstar: new Kernel 2.6.38 ready to use. The config is based on sid's 3.1.0-1, if you want to take a look at it, you will find it here: config-3.1.10-dockstar-shyd_1.2
It supports several devices like wifi, webcam, audio or dvb.
Some of you might ask why I didn't build 3.2.1. I did, but it wouldn't boot.
When I was trying to find proper kernel configs for the dockstar, I had to try several builds. Everytime my kernel didn't boot I had to revert the arcNumber and install a working kernel again.
There are two ways to test a kernel:
- Grab another USB stick, make a backup and try the kernel on this backup. If you always do a new backup before testing another build, it will take a long time.
- Test the kernel on the running system (or a backup-stick) and reinstall another kernel in case yours wont boot. In difference to 1. you do this in a chrooted jail.
I want to explain how you do the chroot thing with some lines.
During the last days I was playing around with several kernel-configs and different release versions. Today a new version came out and I built it with the last config I used. In my build I additionally enabled XFS filesystem support and USB sound. If you install my kernel, you don't have to change anything except the device ID concerning the LED if you come from gorgone's heavykernel.
If anybody knows how to build a kernel with gspca drivers for webcam support I would appreciate a short mail!
Some days ago I wanted to test the performance of a partition with XFS as its filesystem. But I wasn't able to mount it. After a look into the kernelconfig of gorgone's heavykernel I noticed that he obviously didn't build it with XFS-support.
I do want to make the test and take a look at kernelbuilding things anyway. Well, I don't want to keep it back, so I decided to verbalize the steps I took.
In this guide you will learn how to set up the crosscompile toolchain to let a more powerful CPU do the job. If you prefer doing the whole thing on the dockstar it will take you several hours.
Further more we will go through the build process until we have a deb-file with the built kernel.