From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6a)
Description of problem:
I can not find a driver to work with my netgear 802.11b pcmcia card
even though it works fine with core 1. It is automatically identified
in core 1 but test1 core 2 doesn't see it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
3.try to select a driver
Actual Results: can not get it to work
Expected Results: it would be automatically recognized.
It would also be nice if core 2 could include the prism54 stuff so my
new netgear wg511 would work. I have it working with core 1 after
installing some software from prism54.org.
OK, finally got the 802.11b card to work. Had to put the card in the
second pcmcia slot then it kudzu configures the first slot as 3comxxx
and the second slot as orinico_cs which works with my card. Since my
laptop has builtin ether as well I wonder if it is confusing that port
with the pcmcia.
Now that it works the problem is that upon booting the boot process
hangs until I unplug the 802.11b card then completes booting--then i
plug the card in and it works fine.
this is more a kudzu issue
What does kudzu -p -b pcmcia say when it's inserted?
[root@localhost root]# kudzu -p -b pcmcia
desc: "Intersil PRISM2 11 Mbps Wireless Adapter"
The way I boot now is to leave the card out until the machine is
booted and then insert the card and it works instantly. If I have the
card in while booting, the boot process hangs at some point and
remains hung until I remove the card and then the boot process
completes. Then I can reinsert the card and it works fine.
Should I try my netgear wg511 card? Don't know if the new kernel
automatically works with 802.11g or not?
Hm, this seems to imply that it's getting probed OK.
I have a similar problem with a real orinoco card, the boot process will
hang if the card is inserted during boot and also sometimes at shutdown.
when the hangs happen the keyboard is unresponsive. removing the card
causes an driver error message which I will post when I can grab a
copy of it. I suspect this is actually a kernel driver problem, not
system-config-network, can this be moved to kernel component?
Created new bug just in case this is another problem bug 116503, log
moved to kernel component