Why installation of a new kernel package on Red Hat Enterprise Linux 6 install bfa-firmware package as dependency ?
Issue
- Why does the installation of a new kernel package on Red Hat Enterprise Linux 6 install bfa-firmware package as dependency even if the system does not have a Brocade Fibre Channel HBA ?
Eg:
# lspci |grep -i HBA
# grep -i HBA /var/log/dmesg
# yum install kernel
Resolving Dependencies
--> Running transaction check
---> Package kernel.x86_64 0:2.6.32-358.14.1.el6 will be installed
--> Processing Dependency: kernel-firmware >= 2.6.32-358.14.1.el6 for package: kernel-2.6.32-358.14.1.el6.x86_64
--> Running transaction check
---> Package kernel-firmware.noarch 0:2.6.32-279.19.1.el6 will be updated
---> Package kernel-firmware.noarch 0:2.6.32-358.14.1.el6 will be an update
--> Processing Conflict: kernel-2.6.32-358.14.1.el6.x86_64 conflicts bfa-firmware < 3.0.3.1
--> Restarting Dependency Resolution with new changes.
--> Running transaction check
---> Package bfa-firmware.noarch 0:3.0.0.0-1.el6 will be updated
---> Package bfa-firmware.noarch 0:3.0.3.1-1.el6 will be an update
--> Finished Dependency Resolution
--> Running transaction check
---> Package kernel.x86_64 0:2.6.32-220.17.1.el6 will be erased
--> Finished Dependency Resolution
Environment
- Red Hat Enterprise Linux 6
- kernel
- bfa-firmware
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.