Red Hat Bugzilla – Bug 120207
IBM T23 Wireless network card (PRISM2) does not work.
Last modified: 2015-01-04 17:05:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6)
Description of problem:
I have an IBM T23 Laptop.
I have not been able to get the integrated wireless network card
working in fedora core 2.
I have had it working in the past in gentoo linux.
It will not get an ip address when you bring up the card.
After bringing up the card and having the card fail to get an ip
address the card will no longer respond to ifconfig down or ifdown etc.
I'm not sure where the bug is, but I know it worked in gentoo so I
think it has something to do with the configuration utilities and
possibly the default configuration rather than the kernel.
I have tried using iwconfig to configure the wireless card and it
still doesn't work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.bring up the wireless adapter
2.it fails to get an ip address
3.try to bring the adapter down
Actual Results: the adapter stops responding until I reboot.
Expected Results: the adapter is brought down so i can try another
will post logs later.
Mass update of -test bugs to update version to fc4.
(Please retest on final release, and report results if you have not already done
Mass update to all FC4 bugs:
An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (184.108.40.206). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.
Please retest with this update, and update this bug if necessary.
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.
This bug has been mass-closed along with other bugs that have been in NEEDINFO
state for several months.
Due to the large volume of inactive bugs in bugzilla, this is the only method we
have of cleaning out stale bug reports where the reporter has disappeared.
If you can reproduce this bug after installing all the current updates, please
reopen this bug.
If you are not the reporter, you can add a comment requesting it be reopened,
and someone will get to it asap.