Bug 186135

Description of problem:
NetworkManager does not do anything with a recently inserted Netgear WG511. This
worked on another machine which had been installed with rawhide (pre-release
FC5) from a week and a half ago, and disabling selinux on the FC5 Gold machine
did not help.

I am currently checking to see if upgrading the pre-release FC5 box to FC5 Gold
causes it to no longer be able to do anything with the Netgear card in question. 

Version-Release number of selected component (if applicable):
NetworkManager-0.6.0-3
(the version on the pre-release box was apparently 0.6.0-2)

How reproducible:
Always.

Steps to Reproduce:
1. Obtain a laptop with FC5 Gold on it (this is a Sony Vaio)
2. Insert the Netgear WG511 into the PCMCIA slot
3. See the card get detected in /var/log/messages, but see nothing else happen;
no messages from the kernel saying that it figured out what kind of card it was
(and loaded the firmware and prism driver appropriately), none at all from
NetworkManager (this may belong as a kernel bug, since there were no kernel
messages; not sure)
  
Actual results:
No card being used in NetworkManager

Expected results:
Should be able to see wireless now listed as an option in NetworkManager

Additional info:
/var/log/messages says the following when the card is inserted (note no messages
from kernel specifying that the card type was recognized, and nothing at all
from NetworkManager):

Mar 21 15:18:23 dhcp83-71 kernel: pccard: CardBus card inserted into slot 0
Mar 21 15:18:23 dhcp83-71 kernel: PCI: Enabling device 0000:07:00.0 (0000 ->
0002)
Mar 21 15:18:23 dhcp83-71 kernel: ACPI: PCI Interrupt 0000:07:00.0[A] -> GSI
16 (level, low) -> IRQ 16

Since I'm suspecting kernel, although not strongly enough to put this as kernel
instead of NetworkManager, I note that it looks like the pre-release machine had
kernel-2.6.15-1.2032_FC5, and GOLD has kernel-2.6.15-1.2054_FC5.

Will attach the results of a successful recognition of this card to this bug report.

Also, upgrading did not break it, at least on the one machine I tried it on.
This could either be a result of upgrading really not breaking things, or
because it's a different laptop, unfortunately... (the laptop on which things
worked both before and after upgrade is an Acer Aspire)