/lib/firmware conflicts with custom kernel

jlimon · 2009-05-23 21:57:52

Hi, I followed the Wiki's guide to ABS building of a custom kernel. Normally I wouldn't care too much if it was maintained by pacman or not, but sadly it HAS to be for the nvidia driver to properly work (and probably my wireless driver's firmware package too..)

It built fine and made the package, but when I go to install it I get file conflicts from kernel26-firmare in /lib/firmware

Do I just disable all kernel firmware in menuconfig and let the kernel26-firmware package handle that?

graysky · 2009-09-07 10:41:36

I too have this problem using a custom kernel I build via makepkg. I had to add the force flag when installing to overwrite the stock arch firmware items. Probably not the right thing to do. Maybe others will reply with the right answer.

Last edited by graysky (2009-09-07 10:42:08)

D-Locked · 2009-09-07 10:59:01

You can check out how some other custom kernels handle this situation.
http://aur.archlinux.org/packages/kerne … 1/PKGBUILD

In this particular example,

rm -fr ${pkgdir}/lib/firmware

combuster · 2009-09-07 11:02:33

Yes, they remove /lib/firmware, but what if I'm using 2.6.31-rc all the time and while upgrading to 2.6.30-5-ARCH wich I don't boot at all messes up with my /lib/firmware. My solution was to back up /lib/firmware, update then replace /lib/firmware with the custome one I've backed up...

.:B:. · 2009-09-07 11:53:19

If you build your own kernels, you need either to remove the firmware dir in the package (like the official PKGBUILD does) or uninstall the kernel26-firmware package (I do the latter).

Combuster: there's nothing 'custom' about the firmware in your own kernel build, if you don't remove it in the PKGBUILD. Of course they might be differences between kernel versions but in general I don't think that's such a big deal it will break anything...

combuster · 2009-09-07 12:00:55

Isn't kernel26-firmware required by kernel26, if I pacman -Rd it could it potentialy make trouble with future kernel upgrades?

I feared that because I almost always run and test the rc kernels (I compile it in the oldfashioned style from kernel source tarball, no abs, aur etc) it could brake something but I think u'r right, possibilities are minimal...

Last edited by combuster (2009-09-07 12:03:35)

.:B:. · 2009-09-07 13:05:44

I just build one package including the kernel, modules and firmware. But then again, I haven't got the official kernel26 on my system at all. If you keep kernel26 alongside your own builds with different versions, then conflicts might arise (you might get firmware mismatches (newer kernels requiring newer versions of e.g. wireless firmware) but those can be easily discovered by checking dmesg - and they're few and far in between.

combuster · 2009-09-07 13:22:41

Please B, because I never boot with arch kernel26, is it safe to just pacman -R kernel26 ???

I'll try it now

:: glibc: requires kernel-headers>=2.6.30.5

I can't remove kernel-headers, I could Rd it but... Please advise

Last edited by combuster (2009-09-07 13:25:31)

.:B:. · 2009-09-07 13:38:19

kernel-headers isn't related to the kernel26 and kernel26-firmware packages (although the name would make you think otherwise). A lot of packages need kernel headers to build on so that's one of the reasons why it's a split out package. You need to keep it.

combuster · 2009-09-07 13:41:06

Ty B...

xduugu · 2009-09-07 14:18:41

You could also replace kernel26-firmware with kernel26-firmware-git. Usually firmware files aren't removed in newer snapshots, they only add new ones. Thus it is quite save to replace it with a newer snapshot.

Arch Linux

#1 2009-05-23 21:57:52

/lib/firmware conflicts with custom kernel

#2 2009-09-07 10:41:36

Re: /lib/firmware conflicts with custom kernel

#3 2009-09-07 10:59:01

Re: /lib/firmware conflicts with custom kernel

#4 2009-09-07 11:02:33

Re: /lib/firmware conflicts with custom kernel

#5 2009-09-07 11:53:19

Re: /lib/firmware conflicts with custom kernel

#6 2009-09-07 12:00:55

Re: /lib/firmware conflicts with custom kernel

#7 2009-09-07 13:05:44

Re: /lib/firmware conflicts with custom kernel

#8 2009-09-07 13:22:41

Re: /lib/firmware conflicts with custom kernel

#9 2009-09-07 13:38:19

Re: /lib/firmware conflicts with custom kernel

#10 2009-09-07 13:41:06

Re: /lib/firmware conflicts with custom kernel

#11 2009-09-07 14:18:41

Re: /lib/firmware conflicts with custom kernel

Board footer