I think I should get this out in the open before Kernel 2.6.42 gets out. The text was written already half a year ago and never really got a finishing touch but some parts of it might be useful out there in solving some problems and hickups during bootup.
After having some trouble with Kernel 2.6.36 and video playback I turned to examine the bootup messages more closely. The problem, frequent crashes during video playback in X, went away as soon as I was using Kernel 2.6.37 but I thought it can’t hurt to examine the error messages during bootup a little closer. So I checked the messages from the init scripts and the output of X a little bit closer.
vga=791 is deprecated
This tells the kernel parameter for switching to graphics mode using the frambuffer device as specified by VESA. This enables bootspash and console with lots of columns and lines.
As I’m using grub2 this is not the prefered way of
activating this anymore. So I removed that command from /etc/default/grub
console is now „ugly“ until kms kicks in.
gfxpayload=1024x768x16,1024×768 before linux command is now the way for setting the resolution of the console. But for now I can live with the few seconds of bulky text.
I just removed the startup and shutdown links. This article has some details on how this is managed in Debian.
update-rc.d -f lvm2 remove disabled the LVM.
error: „net.ipv6.bindv6only“ is an unknown key
This seems to be a problem of the liquorix kernel that I use. The solution is in /usr/share/doc/procps/README.Debian
Not really needed on a laptop, I guess. So I disabled it with
update-rc.d -f acct remove
Things that are also
- virtuoso-opensource-6.1 I know, this is used for indexing services by KDE, but it also means it’s the third database engine that is started
- PostgreSQL 8.4 + 9.0
- portmap daemon Does NFS still depend on this?
- NFS common utilities
One PostgreSQL should really be enough. I wonder how they got both installed in parallel
Not sure about those.
started in S and in 5:
Now we get to the point where X is started. Here it really was worth digging into the problems. While I thought that the free radeon driver couldn’t handle composite effects it was simply the kernel mode switching that kicked in too late as mentioned in http://www.x.org/wiki/radeonBuildHowTo#Troubleshooting.
Loading the kernel mode switching module in advance made the problem simply disaprear.
unexplained are the following error messages
(EE) SynPS/2 Synaptics TouchPad Unable to query/initialize Synaptics hardware.
(EE) PreInit failed for input device „SynPS/2 Synaptics TouchPad“
since the touchpad seems to work fine.