From: Free Ekanayaka <[EMAIL PROTECTED]> > |--==> Danai SAE-HAN writes: > DS> From: Free Ekanayaka <[EMAIL PROTECTED]> > >>Mmh, I built a 2.6.18 kernel myself and did not have the problem you > >>mention. > >> > >>I suggest you generate a new config, by copying your old config file > >>in the sources root and then run menu-config, which should clean it > >>up. > > DS> That's what I always do: run "make oldconfig" first, and then run > DS> make-kpkg with the options from above. > > DS> I think that the fault might perhaps be on make-kpkg's side. The > DS> newest versions fix some $(ARCH) problems, so I'll keep you updated > DS> when I get a change to install the latest version of kernel-package. > > It might be, I usually build my kernels against bleeding-edge unstable.
Same with me, so that's strange. I'm not using pristine 2.6.18 kernels but kernel sources packaged by Debian. The newest 10.062 version of make-kpkg didn't help. I still get the error when bootsplash is enabled. I rebuilt Linux 2.6.17, and it works flawlessly. Is there a big difference between the 2.6.17 and the 2.6.18 version of the bootsplash kernel patches? I don't think it has anything to do with my .config file. After saving my own .config somewhere safe, I tried the following combo's with the bootsplash patch: - "make allmodconfig" works; - "make allyesconfig" fails; - "make defconfig" works; - "make allnoconfig" works. I tried "make allyesconfig" without the bootsplash patch, and it works. Could you try and see if any of the above mentioned combinations gets you past the initial configuration stage? Thanks Danai SAE-HAN 韓達耐 -- 題目:《書憤》 作者:陸游（１１２５－１２１０） 早歲那知世事艱，中垢北望氣如山。 樓船夜雪瓜洲渡，鐵馬秋風大散關。 塞上長城空自許，鏡中衰鬢已先斑。 出師一表真名世，千載誰堪伯仲間。
