Hide Forgot
Please update the iwlagn driver with the following patch: http://git.kernel.org/?p=linux/kernel/git/linville/wireless-2.6.git;a=commit;h=1144181c1bc054dc5e001a6f10b4820167e6c883 This patch fixed the issue of incorrect PCI subsystem id for 6150(Kelsey Peak) devices which may cause some devices not recognized. Device affected: Kelsey Peak HMC 1x2 BG WiFi + 1x2 WiMAX for HP and Lenovo with device id (0886:1317) (0885:1327) (0885:1307) thanks
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
There are some more patches needed on RHEL6 kernel, except fix from comment 0, in order to support these devices. Xiao does this fix is needed also in 6.1z or is enough to have it in 6.2 ? I mean do we have these devices in production now?
Hi Stanislaw, We got customer report that they are using the affected device card but not recognized. Currently I don't know which production they are using but I think the affected cards might already in production or at least will be soon in production. So could you also add it in 6.1z for better support? Thanks, -Hui
Hello Hui, (In reply to comment #3) > There are some more patches needed on RHEL6 kernel, except fix from comment 0, > in order to support these devices. I looked a bit more, should be enough to comment 0 patch to RHEL6 to fix that bug. (In reply to comment #4) > production. So could you also add it in 6.1z for better support? I will propose that bug for z-stream.
Created attachment 503844 [details] iwlagn_fix_6050g2_bg_pci_id.patch RHEL6 backport of commit 1144181c1bc054dc5e001a6f10b4820167e6c883 Author: Wey-Yi Guy <wey-yi.w.guy> Date: Mon May 30 09:32:52 2011 -0700 iwlagn: fix incorrect PCI subsystem id for 6150 devices Can Intel test (and review if possible :-) this patch?
Hi Stanislaw, Since we don't have the right device to perform the test, only sanity check is done. Thanks, -Hui
Hi Xiao, we have no HW either, we have only 6100, which is the same wireless without WiMax I guess. So we should be able to test on 6100 if possible. Any clue if you (Intel) will ever have this device? Thanks Tom
I have an individual card in Westford labeled as: Intel Centrino Advanced-N + WiMAX 6150 [8086:0885]. It loads iwlwifi-6050 ucode and connects to wireless networks. Would this be sufficient for testing?
Hi all, This patch affects only the cards with PCI subsystem id (0886:1317) (0885:1327) and (0885:1307). You can use lspci -nv to check whether you have such cards. From the information I got such cards are Kelsey Peak HMC 1x2 BG WiFi + 1x2 WiMAX for HP and Lenovo. I've tried to find but unfortunately we don't have such specific cards on site and lack of further production/marketing information. So we will not likely to have them specially. Thanks, -Hui
(In reply to comment #11) > Hi all, > > This patch affects only the cards with PCI subsystem id (0886:1317) (0885:1327) > and (0885:1307). You can use lspci -nv to check whether you have such cards. > > From the information I got such cards are Kelsey Peak HMC 1x2 BG WiFi + 1x2 > WiMAX for HP and Lenovo. I've tried to find but unfortunately we don't have > such specific cards on site and lack of further production/marketing > information. So we will not likely to have them specially. > > Thanks, > -Hui Hi Hui, any update here? Thanks Tom
Tomas, What I understand from comment 11, Intel does not have and will not have devices with these specific PCI IDs. They are only available on some Lenovo and HP laptops. If you look at patch, you will see that it is independent for any iwlwifi device except 3 devices which have bad PCI ID. So it does not change functionality of other devices and possibly fix 3 PCI IDs. If (what is quite improbable) it does not fix these 3 devices, it does not make anything worse, since they do not work now for sure.
*** This bug has been marked as a duplicate of bug 766952 ***