can you reproduce the bug with linux-image-2.6.18-5-686 ? also this sounds more like an lilo failure? -- maks