On Sun, 2010-05-30 at 18:47 -0500, Steven P. Ulrick wrote:
> OK. The good news is that the RPM was successfully built. The bad news is
> that
> the output of "rpm -ivh kernel-2.6.33noframebuffer-1.x86_64.rpm" is as
> follows:
>
> [r...@localhost x86_64]# rpm -ivh kernel-2.6.33noframebuffer-1.x86_64.rpm
> Preparing... ########################################### [100%]
> package kernel-2.6.33.3-85.fc13.x86_64 (which is newer than
> kernel-2.6.33noframebuffer-1.x86_64) is already installed
> package kernel-2.6.33.4-95.fc13.x86_64 (which is newer than
> kernel-2.6.33noframebuffer-1.x86_64) is already installed
> file /lib/firmware/matrox/g200_warp.fw from install of
> kernel-2.6.33noframebuffer-1.x86_64 conflicts with file from package linux-
> firmware-20100106-4.fc13.noarch
> file /lib/firmware/matrox/g400_warp.fw from install of
> kernel-2.6.33noframebuffer-1.x86_64 conflicts with file from package linux-
> firmware-20100106-4.fc13.noarch
>
> Any ideas?
When I build a kernel I have to rebuild the firmware, even though I
never use it. Here's my Build script:
#!/bin/bash
rpmbuild -bb --with baseonly --with firmware --without debuginfo
\
--target=`uname -m` SPECS/kernel.spec >& LOG/kernel
This web site is extremely useful when building a kernel.
http://fedoraproject.org/wiki/Building_a_custom_kernel
Part of your problem may be your choice of name for the custom kernel.
I suspect that kernel-2.6.33.noframebuffer-1.x86_64 (note the dot after
the "33") will work better. The new kernel must come after the old one
in ASCII sort order.
Good Luck. I have similar problems.
jon
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
