How to use firmware-tools on Dell Inspiron 531S

[R. Steven Rainwater]

On Fri, 2008-02-22 at 12:21 -0800, Chris Evans wrote:
>On Fri, 2008-02-22 at 13:28 -0600, R. Steven Rainwater wrote:
> > I've got a Dell Inspiron 531S desktop box running Redhat Fedora 8.
> > 
> >  yum install $(bootstrap_firmware)
> > 
> > I'm assuming $(bootstrap_firmware) is supposed to be some sort of
> > variable...
>
> bootstrap_firmware is a command that lists the devices on your system
> $(command) is similar to `command` so it gets replaced with the
> devices needed
> so the way to get it up is
> yum install $(bootstrap_firmware) # installs the firmware that is  
> packaged for your system.
> update_firmware # updates the firmware.

So, if I'm understanding you, I should literally type "yum install
$(bootstrap_firmware)" at the command prompt; dollar sign, parenthesis
and all. Might be good to update the wiki with something to that effect.
Since that's different than the way people normally use yum. Others may
expect the $ to indicate a variable or something they're supposed to
replace. At least if they're as dumb as me. :)

Okay, so here's what happens on my box. It looks like something has gone
terribly wrong from the look of it but it's not clear what. Normal usage
of Yum doesn't dump out 20 lines of hex-coded error messages so I'm not
sure what to make of this. Any ideas?

[rsr at ixtl ~]$ yum install $(bootstrap_firmware)
Loading "dellsysidplugin" plugin
livna                     100% |=========================| 2.1 kB
00:00     
dell-software             100% |=========================| 1.9 kB
00:00     
ftp://ftp.applios.net/pub/fedora/linux/releases/8/Everything/i386/os/repodata/repomd.xml: [Errno 4] IOError: [Errno ftp error] 550 Failed to change directory.
Trying other mirror.
fedora                    100% |=========================| 2.1 kB
00:00     
fwupdate                  100% |=========================| 1.9 kB
00:00     
updates                   100% |=========================| 2.3 kB
00:00     
Setting up Install Process
Parsing package install arguments
No package
pci_firmware(ven_0x1002_dev_0x5b72_subven_0x1002_subdev_0x0f03)
available.
No package
pci_firmware(ven_0x1002_dev_0x5b62_subven_0x1002_subdev_0x0f02)
available.
No package
pci_firmware(ven_0x11c1_dev_0x5811_subven_0x1028_subdev_0x8010)
available.
No package pci_firmware(ven_0x1022_dev_0x1103) available.
No package pci_firmware(ven_0x1022_dev_0x1102) available.
No package pci_firmware(ven_0x1022_dev_0x1101) available.
No package pci_firmware(ven_0x1022_dev_0x1100) available.
No package pci_firmware(ven_0x10de_dev_0x03e9) available.
No package pci_firmware(ven_0x10de_dev_0x03e8) available.
No package
pci_firmware(ven_0x10de_dev_0x03f6_subven_0x1028_subdev_0x020e)
available.
No package
pci_firmware(ven_0x10de_dev_0x03ef_subven_0x1028_subdev_0x020e)
available.
No package
pci_firmware(ven_0x10de_dev_0x03ec_subven_0x1028_subdev_0x020e)
available.
No package
pci_firmware(ven_0x10de_dev_0x03f0_subven_0x1028_subdev_0x020e)
available.
No package pci_firmware(ven_0x10de_dev_0x03f3) available.
No package
pci_firmware(ven_0x10de_dev_0x03f2_subven_0x1028_subdev_0x020e)
available.
No package
pci_firmware(ven_0x10de_dev_0x03f1_subven_0x1028_subdev_0x020e)
available.
No package
pci_firmware(ven_0x10de_dev_0x03f5_subven_0x1028_subdev_0x020e)
available.
No package
pci_firmware(ven_0x10de_dev_0x03eb_subven_0x1028_subdev_0x020e)
available.
No package
pci_firmware(ven_0x10de_dev_0x03e0_subven_0x1028_subdev_0x020e)
available.
No package
pci_firmware(ven_0x10de_dev_0x03ea_subven_0x1028_subdev_0x020e)
available.
No package bmc_firmware(ven_0x1028_dev_0x020e) available.
No package system_bios(ven_0x1028_dev_0x020e) available.
No package
pci_firmware(ven_0x1002_dev_0x5b72_subven_0x1002_subdev_0x0f03)/system(ven_0x1028_dev_0x020e) available.
No package
pci_firmware(ven_0x1002_dev_0x5b62_subven_0x1002_subdev_0x0f02)/system(ven_0x1028_dev_0x020e) available.
No package
pci_firmware(ven_0x11c1_dev_0x5811_subven_0x1028_subdev_0x8010)/system(ven_0x1028_dev_0x020e) available.
No package
pci_firmware(ven_0x1022_dev_0x1103)/system(ven_0x1028_dev_0x020e)
available.
No package
pci_firmware(ven_0x1022_dev_0x1102)/system(ven_0x1028_dev_0x020e)
available.
No package
pci_firmware(ven_0x1022_dev_0x1101)/system(ven_0x1028_dev_0x020e)
available.
No package
pci_firmware(ven_0x1022_dev_0x1100)/system(ven_0x1028_dev_0x020e)
available.
No package
pci_firmware(ven_0x10de_dev_0x03e9)/system(ven_0x1028_dev_0x020e)
available.
No package
pci_firmware(ven_0x10de_dev_0x03e8)/system(ven_0x1028_dev_0x020e)
available.
No package
pci_firmware(ven_0x10de_dev_0x03f6_subven_0x1028_subdev_0x020e)/system(ven_0x1028_dev_0x020e) available.
No package
pci_firmware(ven_0x10de_dev_0x03ef_subven_0x1028_subdev_0x020e)/system(ven_0x1028_dev_0x020e) available.
No package
pci_firmware(ven_0x10de_dev_0x03ec_subven_0x1028_subdev_0x020e)/system(ven_0x1028_dev_0x020e) available.
No package
pci_firmware(ven_0x10de_dev_0x03f0_subven_0x1028_subdev_0x020e)/system(ven_0x1028_dev_0x020e) available.
No package
pci_firmware(ven_0x10de_dev_0x03f3)/system(ven_0x1028_dev_0x020e)
available.
No package
pci_firmware(ven_0x10de_dev_0x03f2_subven_0x1028_subdev_0x020e)/system(ven_0x1028_dev_0x020e) available.
No package
pci_firmware(ven_0x10de_dev_0x03f1_subven_0x1028_subdev_0x020e)/system(ven_0x1028_dev_0x020e) available.
No package
pci_firmware(ven_0x10de_dev_0x03f5_subven_0x1028_subdev_0x020e)/system(ven_0x1028_dev_0x020e) available.
No package
pci_firmware(ven_0x10de_dev_0x03eb_subven_0x1028_subdev_0x020e)/system(ven_0x1028_dev_0x020e) available.
No package
pci_firmware(ven_0x10de_dev_0x03e0_subven_0x1028_subdev_0x020e)/system(ven_0x1028_dev_0x020e) available.
No package
pci_firmware(ven_0x10de_dev_0x03ea_subven_0x1028_subdev_0x020e)/system(ven_0x1028_dev_0x020e) available.
Nothing to do