Hi, i installed kernel-2.6.17-5mdv .src.rpm, removed some patch files, built the .src.rpm again. then built the i586 kernel, and now it works... ( i renamed it to 2.6.17-6mdv and used the patch list above)
so, this means that some patches are not OK... where can i send the .src.rpm and i586.rpm's to? i would like a boot.iso based on it in i586 and x86_64 ... then maybe i'll be able to install x86_64 on it... thanks for all help. Sincerely, Maarten 2006/11/4, Maarten Vanraes <[EMAIL PROTECTED]>:
Thanks for the info, but this means that one of those patches is breaking the ahci driver. i've built a .src.rpm and an i586 kernel rpm with only the patches i had applied, this _should_ work, but i'll have to see how it goes. thanks for the help, Maarten 2006/11/2, Thomas Backlund <[EMAIL PROTECTED]>: > Maarten Vanraes skrev: > > I know how .src.rpm 's work, i installed the .src.rpm to get the > > patches (clean kernel did not work). > > > > in the .src.rpm are 2 tarballs, the 1st is then the basic 2.6.17 > > kernel from kernel.org, and the other contains patches. > > > > i don't really get the significance of the %use_patch 0 macro. does > > this mean that use_patch 0 means NO patches applied? (or is this about > > other patches?), if i rebuild the kernel, does this mean i need to set > > this to 1 ? or comment out that line? > > > > Nope. > > the use_patch is for rc builds, so if you on a 2.6.17 spec file set > use_patch to rc1 it will try to build with linux-2.6.16.tar.bz2 + > patch-2.6.17-rc1.bz2 > > > All patches in the patch tarbarll will _always_ be applied > > > -- > Thomas > -- Alien is my name and head-biting is my game
-- Alien is my name and head-biting is my game
