[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Loading device firmware in kickstart



Thanks, unfortunately I was hoping to stick with a generic kernel because though I know how to build a standard kernel, I'm not sure how to build what used to be known as a "BOOT" kernel.

It looks worse than this though, from what I can see I need "udev" user-space hotplug support to load firmware. That means among other things getting "udevd" to start at boot. I highly doubt any of that is encoded in the standard kickstart image and may be a bear to get in. I can't seem to find any examples of someone using "udevd" in kickstart either...

Fun, fun, fun.

Thanks again,

			- Matt

Caetano, Greg wrote:
Matt:

From the ipw2200 install document:

MAKE SURE THAT THE FOLLOWING CAPABILITIES ARE ENABLED:
~~~~~~~~~~~~~~~~~~~~~~~~~~~
#define CONFIG_FW_LOADER 1
~~~~~~~~~~~~~~~~~~~~~~~~~~~
ipw2200 loads firmware via the Linux firmware hotplug capability (see
later
section on firmware loading).  In 2.6.x, this is enabled via menuconfig:

        Device Drivers ->
                Generic Driver Options ->
Hotplug firmware loading support

Greg Caetano
HP TSG Linux Solutions Alliances Engineering
Chicago, IL
greg caetano hp com
Red Hat Certified Engineer
RHCE#803004972711193

-----Original Message-----
From: kickstart-list-bounces redhat com
[mailto:kickstart-list-bounces redhat com] On Behalf Of Matt Fahrner
Sent: Tuesday, June 26, 2007 9:58 AM
To: kickstart-list redhat com
Subject: Loading device firmware in kickstart

Hi all,

We've built a kickstart image (initrd.img) with custom modules to
support the Intel PRO/Wireless 2200BG wireless card (it uses the
"ipw2200" module). As we've had experience with this before, getting the
module itself to load wasn't too hard, however in order for the card to
work it needs to load a firmware image as well. We believe that part is
failing.

What I've tried to do is put the firmware files in the same spot under
the "initrd" image as on a normal multi-user system, namely
"/lib/firmware". However as best as we can tell this isn't working.

We are going to try "/etc/firmware" as well, however I thought someone
might have had some experience with this before, so I am trying this
list. Does someone have some advice here?

Any help would be appreciated.

Thanks,

			- Matt

--
---------------------------------------------------------------------
Matt Fahrner                                    2 South Park St.
Chief Systems Architect                         Willis House
Burlington Coat Factory Warehouse               Lebanon, N.H.  03766
Tel: (603) 448-4100 x5150                       USA
Fax: (603) 443-6190                             Matt Fahrner COAT COM
---------------------------------------------------------------------

_______________________________________________
Kickstart-list mailing list
Kickstart-list redhat com
https://www.redhat.com/mailman/listinfo/kickstart-list

_______________________________________________
Kickstart-list mailing list
Kickstart-list redhat com
https://www.redhat.com/mailman/listinfo/kickstart-list

--
---------------------------------------------------------------------
Matt Fahrner                                    2 South Park St.
Chief Systems Architect                         Willis House
Burlington Coat Factory Warehouse               Lebanon, N.H.  03766
Tel: (603) 448-4100 x5150                       USA
Fax: (603) 443-6190                             Matt Fahrner COAT COM
---------------------------------------------------------------------


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]