Error firmware kernel ethernet broadcom

[David Belgini]

Hello,

I found a problem in an JeOS OpenSuse 12.2 generated from KIWI and I found the solution.

I don't know if this is the right place to post that, but I would like to share that…

After install the ISO in an HP DL380G Server, I got the message related to Ethernet interfaces…

 bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw"

The last kernel-default version 86_64 cannot load this file…

To solve the problem I did a copy from bnx2-mips-09-6.2.1a.fw to bnx2-mips-09-6.2.1b.fw.

Thank you.

[Marcus Schäfer]

Hi,

> I found a problem in an JeOS OpenSuse 12.2 generated from KIWI and I
> found the solution.

Thanks much for your feedback

> I don't know if this is the right place to post that, but I would like
> to share that

It helps our users to workaround a problem with the bnx2 firmware
so it's definitly a valuable information. On the other hand it's
out of our scope to fix the 1b version of the bnx2 firmware which
seems to have a problem. If your time permits you can also create
a bugzilla entry for the suse kernel at bugzilla.novell.com
describing the problem so that it will be fixed with the next
kernel update for 12.2

> After install the ISO in an HP DL380G Server, I got the message related
> to Ethernet interfaces
>
> bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw"

there is no additional information why it can't load the firmware
in dmesg or /var/log/messages ?

> The last kernel-default version 86_64 cannot load this file
> To solve the problem I did a copy from bnx2-mips-09-6.2.1a.fw to
> bnx2-mips-09-6.2.1b.fw.

nice cheating :-)
for a production system I would more tend to a real fix though

Thanks

Regards,
Marcus
--
Public Key available
gpg --keyserver pgp.mit.edu --recv-keys 0xCCE3C6A2
-------------------------------------------------------
Marcus Schäfer (Res. & Dev.) SUSE LINUX Products GmbH
Tel: 0911-740 53 0 Maxfeldstrasse 5
FAX: 0911-740 53 479 D-90409 Nürnberg
GF: Jeff Hawn,Jennifer Guild, Felix Imendörffer
HRB: 21284 (AG Nürnberg) Germany
http://www.suse.de
-------------------------------------------------------

[Bahi, David]

Hi

On Feb 21, 2013, at 3:44 AM, Marcus Schäfer <m...@suse.de> wrote:

> Hi,
>
>> I found a problem in an JeOS OpenSuse 12.2 generated from KIWI and I
>> found the solution.
>
> Thanks much for your feedback
>
>> I don't know if this is the right place to post that, but I would like
>> to share that
>
> It helps our users to workaround a problem with the bnx2 firmware
> so it's definitly a valuable information.

indeed - just ran into this with oem preload and PXE install

Can't load firmware file "bnx2/bnx2-mips-06-6.2.1.fs"

> On the other hand it's
> out of our scope to fix the 1b version of the bnx2 firmware which
> seems to have a problem. If your time permits you can also create
> a bugzilla entry for the suse kernel at bugzilla.novell.com

in searching bugzilla it seems that there is a kernel-firmware package avail

/lib/firmware/bnx2/bnx2-mips-06-4.6.16.fw
/lib/firmware/bnx2/bnx2-mips-06-5.0.0.j3.fw
/lib/firmware/bnx2/bnx2-mips-06-5.0.0.j6.fw
/lib/firmware/bnx2/bnx2-mips-06-6.0.15.fw
/lib/firmware/bnx2/bnx2-mips-09-4.6.17.fw
/lib/firmware/bnx2/bnx2-mips-09-5.0.0.j15.fw
/lib/firmware/bnx2/bnx2-mips-09-5.0.0.j3.fw
/lib/firmware/bnx2/bnx2-mips-09-5.0.0.j9.fw
/lib/firmware/bnx2/bnx2-mips-09-6.0.17.fw
/lib/firmware/bnx2/bnx2-mips-09-6.2.1.fw

adding this package to bootinclude config.xml section made no difference to the oem boot env

$ gzip -cd initrd-oemboot-suse-SLES11.x86_64-2.7.1.splash.gz| cpio -it | grep bnx
lib/modules/3.0.74-0.6.6-default/kernel/drivers/net/bnx2.ko
lib/modules/3.0.74-0.6.6-default/kernel/drivers/net/bnx2x
lib/modules/3.0.74-0.6.6-default/kernel/drivers/net/bnx2x/bnx2x.ko
lib/modules/3.0.74-0.6.6-default/kernel/drivers/scsi/bnx2fc
lib/modules/3.0.74-0.6.6-default/kernel/drivers/scsi/bnx2fc/bnx2fc.ko
lib/modules/3.0.74-0.6.6-default/kernel/drivers/scsi/bnx2i
lib/modules/3.0.74-0.6.6-default/kernel/drivers/scsi/bnx2i/bnx2i.ko
198831 blocks


David

[Marcus Schäfer]

Hi,

> in searching bugzilla it seems that there is a kernel-firmware package avail
>
> /lib/firmware/bnx2/bnx2-mips-06-4.6.16.fw
> /lib/firmware/bnx2/bnx2-mips-06-5.0.0.j3.fw
> /lib/firmware/bnx2/bnx2-mips-06-5.0.0.j6.fw
> /lib/firmware/bnx2/bnx2-mips-06-6.0.15.fw
> /lib/firmware/bnx2/bnx2-mips-09-4.6.17.fw
> /lib/firmware/bnx2/bnx2-mips-09-5.0.0.j15.fw
> /lib/firmware/bnx2/bnx2-mips-09-5.0.0.j3.fw
> /lib/firmware/bnx2/bnx2-mips-09-5.0.0.j9.fw
> /lib/firmware/bnx2/bnx2-mips-09-6.0.17.fw
> /lib/firmware/bnx2/bnx2-mips-09-6.2.1.fw
>
> adding this package to bootinclude config.xml section made no difference to the oem boot env
>
> $ gzip -cd initrd-oemboot-suse-SLES11.x86_64-2.7.1.splash.gz| cpio -it | grep bnx
> lib/modules/3.0.74-0.6.6-default/kernel/drivers/net/bnx2.ko
> lib/modules/3.0.74-0.6.6-default/kernel/drivers/net/bnx2x
> lib/modules/3.0.74-0.6.6-default/kernel/drivers/net/bnx2x/bnx2x.ko
> lib/modules/3.0.74-0.6.6-default/kernel/drivers/scsi/bnx2fc
> lib/modules/3.0.74-0.6.6-default/kernel/drivers/scsi/bnx2fc/bnx2fc.ko
> lib/modules/3.0.74-0.6.6-default/kernel/drivers/scsi/bnx2i
> lib/modules/3.0.74-0.6.6-default/kernel/drivers/scsi/bnx2i/bnx2i.ko
> 198831 blocks

Hmm, I can't reproduce this. I got a lot more data in the initrd
concerning "bnx" and also some firmware:

gzip -cd /tmp/mytest/initrd-oemboot-suse-12.3.x86_64-2.7.1.gz| cpio -it | grep bnx
lib/firmware/bnx2
lib/firmware/bnx2/bnx2-mips-06-6.2.3.fw
lib/firmware/bnx2/bnx2-mips-09-6.2.1b.fw
lib/firmware/bnx2x
lib/firmware/bnx2x/bnx2x-e1h-7.8.2.0.fw
lib/firmware/bnx2x/bnx2x-e2-7.8.2.0.fw
lib/firmware/bnx2x/bnx2x-e1-7.8.2.0.fw
lib/firmware/3.7.10-1.1-default/bnx2
lib/firmware/3.7.10-1.1-default/bnx2/bnx2-rv2p-09-6.0.17.fw
lib/firmware/3.7.10-1.1-default/bnx2/bnx2-rv2p-09ax-6.0.17.fw
lib/firmware/3.7.10-1.1-default/bnx2/bnx2-rv2p-06-6.0.15.fw
lib/modules/3.7.10-1.1-default/kernel/drivers/net/ethernet/broadcom/bnx2x
lib/modules/3.7.10-1.1-default/kernel/drivers/net/ethernet/broadcom/bnx2x/bnx2x.ko
lib/modules/3.7.10-1.1-default/kernel/drivers/net/ethernet/broadcom/bnx2.ko
lib/modules/3.7.10-1.1-default/kernel/drivers/scsi/bnx2i
lib/modules/3.7.10-1.1-default/kernel/drivers/scsi/bnx2i/bnx2i.ko
lib/modules/3.7.10-1.1-default/kernel/drivers/scsi/bnx2fc
lib/modules/3.7.10-1.1-default/kernel/drivers/scsi/bnx2fc/bnx2fc.ko

This is with 12.3 and latest kiwi so some questions:

a) which SLES SP is this ?
b) which kiwi version was used to build it ?

Thanks

Regards,
Marcus
--
Public Key available

gpg --keyserver gpg-keyserver.de --recv-keys 0xCCE3C6A2

[Bahi, David]

Hi again,

right. kernel-packages is missing from the 'bootstrap' portion of the images/oemboot... for suse-SLES11

> a) which SLES SP is this ?

SLES 11 SP2 (haven't played with SP3 yet)

> b) which kiwi version was used to build it ?

latest - i think:

> rpm -qa kiwi\* | sort
kiwi-5.05.11-590.1
kiwi-desc-isoboot-5.05.11-590.1
kiwi-desc-oemboot-5.05.11-590.1
kiwi-desc-vmxboot-5.05.11-590.1
kiwi-doc-5.05.11-590.1
kiwi-templates-5.05.11-590.1
kiwi-tools-5.05.11-590.1

[Marcus Schäfer]

Hi,

> right. kernel-packages is missing from the 'bootstrap' portion of the images/oemboot... for suse-SLES11

Problem is that the package "kernel-firmware" does not exist as extra
package for all versions of SLES. That's why one needs to add it for
the SP which has it. So talking about SP2 I tested it some minutes ago
and added:

<package name="kernel-firmware" bootinclude="true"/>

and build an oem image. The oemboot/suse-SLES boot image description
contains the network driver which has a reference to the firmware
So I have: <file name="drivers/net/*"/> in there. At the end my
oemboot initrd contains:

gzip -cd initrd-oemboot-suse-SLES11.x86_64-2.7.1.gz| cpio -it | grep bnx

lib/firmware/bnx2x
lib/firmware/bnx2x/bnx2x-e2-7.0.29.0.fw
lib/firmware/bnx2x/bnx2x-e1h-7.0.29.0.fw
lib/firmware/bnx2x/bnx2x-e1-7.0.29.0.fw
lib/firmware/3.0.13-0.27-default/bnx2
lib/firmware/3.0.13-0.27-default/bnx2/bnx2-rv2p-09-6.0.17.fw
lib/firmware/3.0.13-0.27-default/bnx2/bnx2-rv2p-09ax-6.0.17.fw
lib/firmware/3.0.13-0.27-default/bnx2/bnx2-rv2p-06-6.0.15.fw
lib/firmware/3.0.13-0.27-default/bnx2/bnx2-mips-06-6.2.1.fw
lib/firmware/3.0.13-0.27-default/bnx2/bnx2-mips-09-6.2.1a.fw
lib/modules/3.0.13-0.27-default/kernel/drivers/net/bnx2x
lib/modules/3.0.13-0.27-default/kernel/drivers/net/bnx2x/bnx2x.ko
lib/modules/3.0.13-0.27-default/kernel/drivers/net/bnx2.ko
lib/modules/3.0.13-0.27-default/kernel/drivers/scsi/bnx2i
lib/modules/3.0.13-0.27-default/kernel/drivers/scsi/bnx2i/bnx2i.ko
lib/modules/3.0.13-0.27-default/kernel/drivers/scsi/bnx2fc
lib/modules/3.0.13-0.27-default/kernel/drivers/scsi/bnx2fc/bnx2fc.ko

which looks ok to me. That's plain SLES-SP2

Please note I wrote a function in kiwi called:

suseStripFirmware

this one checks all drivers in the initrd for a reference to some
firmware. Only those firmware drivers stay inside the initrd which
has a driver reference. For the bnx stuff I think it's required
to have the bnx2....ko network drivers as part of the kiwi initrd
which is the case for the standard oemboot initrd.

When I look at your initial output I only saw scsi drivers
which makes me think there is a difference between your oemboot
boot image description and mine :-)

Regards,
Marcus
--
Public Key available

gpg --keyserver pgp.mit.edu --recv-keys 0xCCE3C6A2

[Bahi, David]

oh boy

On May 14, 2013, at 10:53 AM, Marcus Schäfer <m...@suse.de> wrote:

> Hi,
>
>> right. kernel-packages is missing from the 'bootstrap' portion of the images/oemboot... for suse-SLES11
>
> Problem is that the package "kernel-firmware" does not exist as extra
> package for all versions of SLES. That's why one needs to add it for
> the SP which has it. So talking about SP2 I tested it some minutes ago
> and added:
>
> <package name="kernel-firmware" bootinclude="true"/>
>

me too

<package bootinclude="true" name="kernel-firmware"/>

well, been burnt by strip before so, in a separate create try, I added

<strip type="libs">
<file name="/lib/firmware/bnx2/bnx2-rv2p-09ax-5.0.0.j3.fw"/>
<file name="/lib/firmware/bnx2/bnx2-rv2p-09ax-5.0.0.j10.fw"/>
<file name="/lib/firmware/bnx2/bnx2-rv2p-09-5.0.0.j3.fw"/>
<file name="/lib/firmware/bnx2/bnx2-rv2p-09-5.0.0.j10.fw"/>
<file name="/lib/firmware/bnx2/bnx2-rv2p-09-4.6.15.fw"/>
<file name="/lib/firmware/bnx2/bnx2-rv2p-06-5.0.0.j3.fw"/>
<file name="/lib/firmware/bnx2/bnx2-rv2p-06-4.6.16.fw"/>
<file name="/lib/firmware/bnx2/bnx2-mips-09-6.2.1.fw"/>
<file name="/lib/firmware/bnx2/bnx2-mips-09-6.0.17.fw"/>
<file name="/lib/firmware/bnx2/bnx2-mips-09-5.0.0.j9.fw"/>
<file name="/lib/firmware/bnx2/bnx2-mips-09-5.0.0.j3.fw"/>
<file name="/lib/firmware/bnx2/bnx2-mips-09-5.0.0.j15.fw"/>
<file name="/lib/firmware/bnx2/bnx2-mips-09-4.6.17.fw"/>
<file name="/lib/firmware/bnx2/bnx2-mips-06-6.0.15.fw"/>
<file name="/lib/firmware/bnx2/bnx2-mips-06-5.0.0.j6.fw"/>
<file name="/lib/firmware/bnx2/bnx2-mips-06-5.0.0.j3.fw"/>
<file name="/lib/firmware/bnx2/bnx2-mips-06-4.6.16.fw"/>
</strip>

>
> When I look at your initial output I only saw scsi drivers

maybe i trimmed off the wrong bits of output before. here's what my oem initrd has again:

> gzip -cd out/preload/create/initrd-oemboot-suse-SLES11.x86_64-2.7.1.splash.gz| cpio -it | grep bnx

lib/modules/3.0.74-0.6.6-default/kernel/drivers/net/bnx2.ko
lib/modules/3.0.74-0.6.6-default/kernel/drivers/net/bnx2x
lib/modules/3.0.74-0.6.6-default/kernel/drivers/net/bnx2x/bnx2x.ko
lib/modules/3.0.74-0.6.6-default/kernel/drivers/scsi/bnx2fc
lib/modules/3.0.74-0.6.6-default/kernel/drivers/scsi/bnx2fc/bnx2fc.ko
lib/modules/3.0.74-0.6.6-default/kernel/drivers/scsi/bnx2i
lib/modules/3.0.74-0.6.6-default/kernel/drivers/scsi/bnx2i/bnx2i.ko

198836 blocks

and this is even with the 'strip' section mentioned above (no diff)

here is the only evidence that kernel-firmware was installed:

> gzip -cd out/preload/create/initrd-oemboot-suse-SLES11.x86_64-2.7.1.gz| cpio -it | grep "lib/firmware"
lib/firmware
198836 blocks

> which makes me think there is a difference between your oemboot
> boot image description and mine :-)

i'm using the unadulterated images/oemboot area as provided by latest kiwi update



the kiwi build host i'm using is also sles11 sp2 - though i don't know how that would make a diff.

David

[Bahi, David]

Hello Marcus,

On May 14, 2013, at 12:33 PM, "Bahi, David" <David...@emc.com> wrote:

>> the SP which has it. So talking about SP2 I tested it some minutes ago
>> and added:
>>
>> <package name="kernel-firmware" bootinclude="true"/>
>>
>
> me too
>
> <package bootinclude="true" name="kernel-firmware"/>
>
>> and build an oem image.

my <packages element has patternType="onlyRequired" attribute - how about you ?

( Robert: is there a reason all <packages sections in the config.xml have to have the same patternType ? )

also, can you recommend better usage of <strip type="libs"> rather than listing full path and each file - cause that didn't seem to work.

hopefully your email readers are good with threads - else i've probably trimmed too much of this to make sense.

Thanks

David

[Robert Schweikert]

On 05/20/2013 03:41 PM, Bahi, David wrote:
> Hello Marcus,
>
> On May 14, 2013, at 12:33 PM, "Bahi, David" <David...@emc.com> wrote:
>
>>> the SP which has it. So talking about SP2 I tested it some minutes ago
>>> and added:
>>>
>>> <package name="kernel-firmware" bootinclude="true"/>
>>>
>>
>> me too
>>
>> <package bootinclude="true" name="kernel-firmware"/>
>>
>>> and build an oem image.
>
> my <packages element has patternType="onlyRequired" attribute - how about you ?
>
> ( Robert: is there a reason all <packages sections in the config.xml have to have the same patternType ? )

Yes, packages are pulled together into one zypper command thus if we do
not force the attributes to be the same in the XML the user would not
know what would be used onlyRequired or plusRecommended. It's basically
a stop gap to avoid ambiguity. Otherwise you'd get one behavior for one
config.xml file and another for another config.xml file depending on the
order of processing or profile settings etc. That would be very bad.

In principal we can manage this better and once XML restructuring is
complete we can entertain this as a feature. However, at the moment this
is a limitation, sorry.

On that note, I will be swamped with other stuff for the near
foreseeable future, thus the restructure effort will continue to be
stuck, sorry, unfortunately there are only 24 hours in a day.

Later,
Robert


--
Robert Schweikert MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center LINUX
Tech Lead
rjsc...@suse.com
rsch...@ca.ibm.com
781-464-8147

[Bahi, David]

indeed

On May 14, 2013, at 12:33 PM, "Bahi, David" <David...@emc.com> wrote:

> oh boy
>
> On May 14, 2013, at 10:53 AM, Marcus Schäfer <m...@suse.de> wrote:
>
>>
>> <package name="kernel-firmware" bootinclude="true"/>

behaves differently on 12.3 than kiwi sles11sp2 host

> here is the only evidence that kernel-firmware was installed:
>
>> gzip -cd out/preload/create/initrd-oemboot-suse-SLES11.x86_64-2.7.1.gz| cpio -it | grep "lib/firmware"
> lib/firmware
> 198836 blocks

nuts.

bahid@bahid-linux01:~/svn/mauitools/branches/QA/grinder-perf-camb/kiwi> gzip -cd out/preload/create/oem-preload/initrd-oemboot-suse-SLES11.x86_64-2.7.1.splash.gz | cpio -it | grep "lib/firmware"

lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-mips-09-6.2.1a.fw
lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-rv2p-06-6.0.15.fw
lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-mips-06-6.2.1.fw
lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-rv2p-09-6.0.17.fw
lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-rv2p-09ax-6.0.17.fw
...
lib/firmware/phanfw.bin
219753 blocks

David

[Marcus Schäfer]

Hi,

> >> <package name="kernel-firmware" bootinclude="true"/>
>
> behaves differently on 12.3 than kiwi sles11sp2 host
>
> > here is the only evidence that kernel-firmware was installed:
> >
> >> gzip -cd out/preload/create/initrd-oemboot-suse-SLES11.x86_64-2.7.1.gz| cpio -it | grep "lib/firmware"
> > lib/firmware
> > 198836 blocks
>
> nuts.
>
> bahid@bahid-linux01:~/svn/mauitools/branches/QA/grinder-perf-camb/kiwi> gzip -cd out/preload/create/oem-preload/initrd-oemboot-suse-SLES11.x86_64-2.7.1.splash.gz | cpio -it | grep "lib/firmware"
>
> lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-mips-09-6.2.1a.fw
> lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-rv2p-06-6.0.15.fw
> lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-mips-06-6.2.1.fw
> lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-rv2p-09-6.0.17.fw
> lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-rv2p-09ax-6.0.17.fw
> ...
> lib/firmware/phanfw.bin
> 219753 blocks
>
> David

Thanks for narrowing this down. Do I have a chance to test this
on your sles11sp2 build host machine ? maybe ssh ? I assume the
kernel-firmware package is installed in both cases thus I guess
the problem must be in the suseStripFirmware function from
/usr/share/kiwi/modules/KIWIConfig.sh

But on a first look I can't tell why it should behave differently
when it runs on sp2 host vs. a 12.3 host

Thanks

[Bahi, David]

Hi,

On May 29, 2013, at 3:54 AM, Marcus Schäfer <m...@suse.de> wrote:

>> bahid@bahid-linux01:~/svn/mauitools/branches/QA/grinder-perf-camb/kiwi> gzip -cd out/preload/create/oem-preload/initrd-oemboot-suse-SLES11.x86_64-2.7.1.splash.gz | cpio -it | grep "lib/firmware"
>>
>> lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-mips-09-6.2.1a.fw
>> lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-rv2p-06-6.0.15.fw
>> lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-mips-06-6.2.1.fw
>> lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-rv2p-09-6.0.17.fw
>> lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-rv2p-09ax-6.0.17.fw
>> ...
>> lib/firmware/phanfw.bin
>> 219753 blocks
>>
>> David
>
> Thanks for narrowing this down. Do I have a chance to test this
> on your sles11sp2 build host machine ? maybe ssh ?

unfortunately not.

> I assume the
> kernel-firmware package is installed in both cases

same kiwi config.xml and .sh and supporting env (root hooks etc)

> thus I guess
> the problem must be in the suseStripFirmware function from
> /usr/share/kiwi/modules/KIWIConfig.sh

cool - looking into how this differs.

>
> But on a first look I can't tell why it should behave differently
> when it runs on sp2 host vs. a 12.3 host

but first note - this curiosity - chroot into the SLES 11 SP2 host prepare'd root


bang-magenta:/> find /lib/modules -name "*.ko" | xargs modinfo | grep ^firmware | sort
firmware: 3com/3C359.bin
firmware: 3com/typhoon.bin
firmware: 6fire/dmx6fireap.ihx
firmware: 6fire/dmx6firecf.bin
firmware: 6fire/dmx6firel2.ihx
firmware: acenic/tg1.bin
firmware: acenic/tg2.bin
firmware: adaptec/starfire_rx.bin
firmware: adaptec/starfire_tx.bin
firmware: agere_ap_fw.bin
firmware: agere_sta_fw.bin
firmware: aic94xx-seq.fw
firmware: asihpi/dsp5000.bin
firmware: asihpi/dsp6200.bin
firmware: asihpi/dsp6205.bin
firmware: asihpi/dsp6400.bin
firmware: asihpi/dsp6600.bin
firmware: asihpi/dsp8700.bin
firmware: asihpi/dsp8900.bin
firmware: atmel_at76c502_3com.bin
firmware: atmel_at76c502_3com-wpa.bin
firmware: atmel_at76c502.bin
firmware: atmel_at76c502d.bin
firmware: atmel_at76c502d-wpa.bin
firmware: atmel_at76c502e.bin
firmware: atmel_at76c502e-wpa.bin
firmware: atmel_at76c502-wpa.bin
firmware: atmel_at76c504_2958.bin
firmware: atmel_at76c504_2958-wpa.bin
firmware: atmel_at76c504a_2958.bin
firmware: atmel_at76c504a_2958-wpa.bin
firmware: atmel_at76c504.bin
firmware: atmel_at76c504-wpa.bin
firmware: atmel_at76c506.bin
firmware: atmel_at76c506-wpa.bin
firmware: BCM2033-FW.bin
firmware: BCM2033-MD.hex
firmware: bfubase.frm
firmware: bnx2/bnx2-mips-06-6.2.1.fw
firmware: bnx2/bnx2-mips-09-6.2.1a.fw
firmware: bnx2/bnx2-rv2p-06-6.0.15.fw
firmware: bnx2/bnx2-rv2p-09-6.0.17.fw
firmware: bnx2/bnx2-rv2p-09ax-6.0.17.fw
firmware: bnx2x/bnx2x-e1-7.0.29.0.fw
firmware: bnx2x/bnx2x-e1h-7.0.29.0.fw
firmware: bnx2x/bnx2x-e2-7.0.29.0.fw
firmware: BT3CPCC.bin
firmware: cbfw.bin
...

notice that the created /lib/firmware-required area has bnx2x but not bnx2

/lib/firmware:
total 14908
drwxr-xr-x 33 root root 4096 May 29 11:27 3.0.74-0.6.6-default
drwxr-xr-x 2 root root 6 Mar 11 17:15 3com
drwxr-xr-x 2 root root 6 Mar 11 17:15 acenic
drwxr-xr-x 2 root root 6 Mar 11 17:15 adaptec
drwxr-xr-x 2 root root 6 Mar 11 17:15 advansys
drwxr-xr-x 5 root root 4096 May 21 15:44 ar3k
-rw-r--r-- 1 root root 70624 Jul 8 2011 ar7010_1_1.fw
-rw-r--r-- 1 root root 70624 Jul 8 2011 ar7010.fw
-rw-r--r-- 1 root root 83968 Jul 8 2011 ar9170-1.fw
-rw-r--r-- 1 root root 3508 Jul 8 2011 ar9170-2.fw
-rw-r--r-- 1 root root 51312 Jul 8 2011 ar9271.fw
-rw-r--r-- 1 root root 246804 Jul 8 2011 ath3k-1.fw
drwxr-xr-x 4 root root 32 May 21 15:44 ath6k
-rw-r--r-- 1 root root 28164 Feb 21 2009 atmel_at76c503-i3861.bin
-rw-r--r-- 1 root root 28040 Feb 21 2009 atmel_at76c503-i3863.bin
-rw-r--r-- 1 root root 35372 Feb 21 2009 atmel_at76c503-rfmd-0.90.2-140.bin
-rw-r--r-- 1 root root 37804 Feb 21 2009 atmel_at76c503-rfmd-acc.bin
-rw-r--r-- 1 root root 37964 Feb 21 2009 atmel_at76c503-rfmd.bin
-rw-r--r-- 1 root root 35196 Feb 21 2009 atmel_at76c504c-wpa.bin
-rw-r--r-- 1 root root 37009 Feb 21 2009 atmel_at76c505a-rfmd2958.bin
-rw-r--r-- 1 root root 37000 Feb 21 2009 atmel_at76c505-rfmd2958.bin
-rw-r--r-- 1 root root 35532 Feb 21 2009 atmel_at76c505-rfmd.bin
drwxr-xr-x 2 root root 6 Mar 11 17:15 av7110
drwxr-xr-x 2 root root 4096 May 21 15:44 bnx2
drwxr-xr-x 2 root root 4096 May 29 11:27 bnx2x
-rw-r--r-- 1 root root 165768 Jul 8 2011 bnx2x-e1-4.8.53.0.fw
-rw-r--r-- 1 root root 163000 Jul 8 2011 bnx2x-e1-5.2.13.0.fw
-rw-r--r-- 1 root root 162800 Jul 8 2011 bnx2x-e1-5.2.7.0.fw
-rw-r--r-- 1 root root 192400 Jul 8 2011 bnx2x-e1h-4.8.53.0.fw
-rw-r--r-- 1 root root 205512 Jul 8 2011 bnx2x-e1h-5.2.13.0.fw
-rw-r--r-- 1 root root 205488 Jul 8 2011 bnx2x-e1h-5.2.7.0.fw
drwxr-xr-x 2 root root 104 May 21 15:44 brcm
drwxr-xr-x 3 root root 16 May 21 15:44 cis
drwxr-xr-x 2 root root 6 Mar 11 17:15 cpia2
-rw-r--r-- 1 root root 338656 Jan 13 2012 ctfw_cna.bin
drwxr-xr-x 2 root root 69 May 21 15:44 cxgb3
drwxr-xr-x 2 root root 6 May 29 11:27 cxgb4
...


/lib/firmware-required/:
total 10904
drwxr-xr-x 26 root root 4096 May 29 11:27 3.0.74-0.6.6-default
-rw-r--r-- 1 root root 50698 Jul 8 2011 agere_ap_fw.bin
-rw-r--r-- 1 root root 65046 Jul 8 2011 agere_sta_fw.bin
-rw-r--r-- 1 root root 22622 Feb 21 2009 aic94xx-seq.fw
-rw-r--r-- 1 root root 30348 Feb 21 2009 atmel_at76c502_3com.bin
-rw-r--r-- 1 root root 35184 Feb 21 2009 atmel_at76c502_3com-wpa.bin
-rw-r--r-- 1 root root 31764 Feb 21 2009 atmel_at76c502.bin
-rw-r--r-- 1 root root 31764 Feb 21 2009 atmel_at76c502d.bin
-rw-r--r-- 1 root root 35276 Feb 21 2009 atmel_at76c502d-wpa.bin
-rw-r--r-- 1 root root 31776 Feb 21 2009 atmel_at76c502e.bin
-rw-r--r-- 1 root root 35272 Feb 21 2009 atmel_at76c502e-wpa.bin
-rw-r--r-- 1 root root 35276 Feb 21 2009 atmel_at76c502-wpa.bin
-rw-r--r-- 1 root root 35180 Feb 21 2009 atmel_at76c504_2958-wpa.bin
-rw-r--r-- 1 root root 39928 Feb 21 2009 atmel_at76c504a_2958-wpa.bin
-rw-r--r-- 1 root root 31748 Feb 21 2009 atmel_at76c504.bin
-rw-r--r-- 1 root root 31824 Feb 21 2009 atmel_at76c506.bin
-rw-r--r-- 1 root root 35228 Feb 21 2009 atmel_at76c506-wpa.bin
drwxr-xr-x 2 root root 88 May 29 11:27 bnx2x
-rw-r--r-- 1 root root 358080 Jan 13 2012 cbfw.bin
-rw-r--r-- 1 root root 498128 Jan 13 2012 ct2fw.bin
-rw-r--r-- 1 root root 472144 Jan 13 2012 ctfw.bin
drwxr-xr-x 2 root root 21 May 29 11:27 cxgb4
-rw-r--r-- 1 root root 209190 May 5 2010 ipw2100-1.3.fw
-rw-r--r-- 1 root root 201138 May 5 2010 ipw2100-1.3-i.fw
-rw-r--r-- 1 root root 196458 May 5 2010 ipw2100-1.3-p.fw
-rw-r--r-- 1 root root 191154 May 5 2010 ipw2200-bss.fw
-rw-r--r-- 1 root root 185428 May 5 2010 ipw2200-ibss.fw
...

[Bahi, David]

hum....

On May 29, 2013, at 8:13 AM, "Bahi, David" <David...@emc.com> wrote:

> Hi,
>
> On May 29, 2013, at 3:54 AM, Marcus Schäfer <m...@suse.de> wrote:
>
>>> bahid@bahid-linux01:~/svn/mauitools/branches/QA/grinder-perf-camb/kiwi> gzip -cd out/preload/create/oem-preload/initrd-oemboot-suse-SLES11.x86_64-2.7.1.splash.gz | cpio -it | grep "lib/firmware"
>>>
>>> lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-mips-09-6.2.1a.fw
>>> lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-rv2p-06-6.0.15.fw
>>> lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-mips-06-6.2.1.fw
>>> lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-rv2p-09-6.0.17.fw
>>> lib/firmware/3.0.74-0.6.8-default/bnx2/bnx2-rv2p-09ax-6.0.17.fw
>>> ...
>>> lib/firmware/phanfw.bin
>>> 219753 blocks
>>>
>>> David
>>
>> Thanks for narrowing this down. Do I have a chance to test this
>> on your sles11sp2 build host machine ? maybe ssh ?
>
> unfortunately not.
>
>> I assume the
>> kernel-firmware package is installed in both cases
>
> same kiwi config.xml and .sh and supporting env (root hooks etc)
>
>> thus I guess
>> the problem must be in the suseStripFirmware function from
>> /usr/share/kiwi/modules/KIWIConfig.sh
>
> cool - looking into how this differs.

the bnx2 (not 2x) is in the `uname -r` dir

/lib/firmware-required/3.0.74-0.6.8-default/bnx2:
total 220
-rw-r--r-- 1 root root 92792 May 29 12:57 bnx2-mips-06-6.2.1.fw
-rw-r--r-- 1 root root 103868 May 29 12:57 bnx2-mips-09-6.2.1a.fw
-rw-r--r-- 1 root root 5696 May 29 12:57 bnx2-rv2p-06-6.0.15.fw
-rw-r--r-- 1 root root 6104 May 29 12:57 bnx2-rv2p-09-6.0.17.fw
-rw-r--r-- 1 root root 6616 May 29 12:57 bnx2-rv2p-09ax-6.0.17.fw


so it's not this function - cause firmware-required looks good - gets moved for /lib/firmware

if suseStripFirmware runs something must happen afterwards that removes /lib/firmware...

David

[Marcus Schäfer]

Hi,

> hum....

>
> so it's not this function - cause firmware-required looks good - gets moved for /lib/firmware

Hmmm

> if suseStripFirmware runs something must happen afterwards that removes /lib/firmware...

looks like but I'm clueless now what could cause this and I can't
reproduce it... strange