Hello, now I tried it with kernel-image-2.6.8-1-686 (version 2.6.8-4) and this one seems to work okay! I tried booting it 4-5 times and in all cases it was successful. So it seems that this bug was fixed with version 2.6.8-4. Regards, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de