Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 247546 - Intel Pro/Wireless 2200bg can be compiled statically into the kernel
Summary: Intel Pro/Wireless 2200bg can be compiled statically into the kernel
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-19 06:59 UTC by Marek Kozlowski
Modified: 2008-11-21 03:17 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marek Kozlowski 2008-11-19 06:59:55 UTC
make menuconfig -> Device Drivers -> Network Device Support -> Wireless LAN -> IEEE 802.11 -> Intel Pro/Wireless 2200BG Network Connection. It can be compiled as a module (M) or statically into the kernel (*). This driver requires the firmware (net-wireless/ipw2200-firmware) and it can load it ONLY if compiled as a module. If it is compiled into the kernel then it is unable to load the firmware (Error -2 occures) -- and it's very difficult to guess the problem (it's not well documented).

Reproducible: Always

Actual Results:  
Mysterious and not documented bug -2 occures if compiled statically.

Expected Results:  
This driver should be able to compile ONLY as a module.
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2008-11-20 18:13:27 UTC
Which cat/pkg-version does this apply to?
Comment 2 Thorsten Vollmer 2008-11-20 20:29:07 UTC
This behavior is thoroughly documented in recent kernels: "It is recommended that you compile this driver as a module (M) rather than built-in (Y). This driver requires firmware at device initialization time, and when built-in this typically happens before the filesystem is accessible (hence firmware will be unavailable and initialization will fail). If you do choose to build this driver into your kernel image, you can avoid this problem by including the firmware and a firmware loader in an initramfs."

In kernels >=2.6.27, you can also add the firmware to the kernel image using CONFIG_EXTRA_FIRMWARE.