Bug 511036
| Summary: | ipw3945 and iwl3945 driver conflict | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Prarit Bhargava <prarit> |
| Component: | ipw3945-kmod | Assignee: | Jon Masters <jcm> |
| Status: | CLOSED NOTABUG | QA Contact: | desktop-bugs <desktop-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.4 | CC: | huzaifas, jmontleo, linville, lsmid, prarit, qcai, sghosh, syeghiay, tburke, zcerza |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Red Hat is no longer able to responsibly support the ipw3945 wireless laptop network driver to the full levels of service, as the upstream company responsible for that driver has suspended maintenance efforts on the driver.
Red Hat, following the guidance of the company responsible for the driver has migrated over to the iwl3945 driver (first introduced in Red Hat Enterprise Linux 5.3). Ongoing maintenance of driver issues associated with the 3945 hardware will be provided on the iwl3945 driver. All fresh/full installations of Red Hat Enterprise Linux 5.4 on systems with 3945 hardware will install the iwl3945 driver.
Red Hat continues to provide the ipw3945 driver in Red Hat Enterprise Linux 5.4 as a migration convenience. It is recommended that customers transition to the iwl3945 driver. Refer to the Red Hat Knowledgebase for details on how to transition if you are doing an update install from a system that had its full installation prior to Red Hat Enterprise Linux 5.4.
Customers who report issues with the ipw3945 driver may be referred to migrate to the iwl3945 driver for resolution. For example, there are known issues connecting to VPN concentrators present in the ipw3945 driver which are resolved in the iwl3945 driver.
Note
the use of the iwl3945 driver requires installing the iwl3945-firmware package from the supplementary RHN channel. Package version 15.28.2.8-2 or later is required. (ie iwl3945-firmware-15.28.2.8-2 or later)
Additionally, the device name, for example as it appears in the output of the `ifconfig` command appears as eth0 (or eth1) when using the ipw3945 driver, when using the iwl3945 driver it is identified as wlan0.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-08-24 04:27:19 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 468301, 518583 | ||
|
Description
Prarit Bhargava
2009-07-13 12:07:38 UTC
Sorry, wrong component. P. Adding Jason Montleon from helpdesk ... P. Note: we would rather do a rpm -e kmod-ipw3945, unless there are other implications. When we added iwl3945 in 5.3, the decision was made to keep existing kmod-ipw3945 users on that driver due to upgrade path issues. I think if we found a way to cleanly migrate users to iwl3945, nobody would argue against it as the iwl driver is generally seen to be superior (and who wants two drivers for one device anyway). I haven't seen the hanging issue, but I'm not entirely surprised that someone ran into one. Hopefully this gives us the motivation to figure out a better upgrade path. Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: - RH is no longer able to responsibly support the ipw3945 to our normal full levels of service as the upstream company responsible for that driver has suspended maintenance efforts on this particular driver. - RH, following the guidance of the company responsible for the driver has migrated over to the iwl3945 driver (first introduced in RHEL5.3) - Ongoing maintenance of driver issues associated with the 3945 hardware will be provided on the iwl3945 driver. - All fresh/full installations of RHEL5.4 on systems with 3945 hardware will install the iwl3945 driver. - RH continues to provide the ipw3945 driver in RHEL5.4 as a migration convenience. We do recommend that customers transition to the iwl3945 driver. Refer here to (kbase) for details on how to transition if you are doing an update install from a system that had its full installation prior to RHEL5.4. - Customers who report issues with the ipw3945 driver may be referred to migrate to the iwl3945 driver for resolution. - Note that use of the iwl3945 driver requires installing the iwl3945-firmware package from the supplementary RHN channel. Package version 15.28.2.8-2 or later is required. (ie iwl3945-firmware-15.28.2.8-2 or later) Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,7 +1,9 @@ +editorial comment: this is an important migration issue. therefore it warrants the prominence of mention in the relnotes; rather than being obscured in the tech notes. - RH is no longer able to responsibly support the ipw3945 to our normal full levels of service as the upstream company responsible for that driver has suspended maintenance efforts on this particular driver. - RH, following the guidance of the company responsible for the driver has migrated over to the iwl3945 driver (first introduced in RHEL5.3) - Ongoing maintenance of driver issues associated with the 3945 hardware will be provided on the iwl3945 driver. - All fresh/full installations of RHEL5.4 on systems with 3945 hardware will install the iwl3945 driver. - RH continues to provide the ipw3945 driver in RHEL5.4 as a migration convenience. We do recommend that customers transition to the iwl3945 driver. Refer here to (kbase) for details on how to transition if you are doing an update install from a system that had its full installation prior to RHEL5.4. -- Customers who report issues with the ipw3945 driver may be referred to migrate to the iwl3945 driver for resolution. +- Customers who report issues with the ipw3945 driver may be referred to migrate to the iwl3945 driver for resolution. For example, there are known issues connecting to VPN concentrators present in the ipw3945 driver which are resolved in the iwl3945 driver. -- Note that use of the iwl3945 driver requires installing the iwl3945-firmware package from the supplementary RHN channel. Package version 15.28.2.8-2 or later is required. (ie iwl3945-firmware-15.28.2.8-2 or later)+- Note that use of the iwl3945 driver requires installing the iwl3945-firmware package from the supplementary RHN channel. Package version 15.28.2.8-2 or later is required. (ie iwl3945-firmware-15.28.2.8-2 or later) +- Also note that the device name, for example as it appears in the output of the `ifconfig` command appears as eth0 (or eth1) when using the ipw3945 driver, when using the iwl3945 driver it is identified as wlan0. Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,9 +1,10 @@ -editorial comment: this is an important migration issue. therefore it warrants the prominence of mention in the relnotes; rather than being obscured in the tech notes. +editorial comment: this is an important migration issue. therefore it warrants the prominence of mention in the relnotes; rather than being obscured in the tech notes.) + - RH is no longer able to responsibly support the ipw3945 to our normal full levels of service as the upstream company responsible for that driver has suspended maintenance efforts on this particular driver. - RH, following the guidance of the company responsible for the driver has migrated over to the iwl3945 driver (first introduced in RHEL5.3) - Ongoing maintenance of driver issues associated with the 3945 hardware will be provided on the iwl3945 driver. - All fresh/full installations of RHEL5.4 on systems with 3945 hardware will install the iwl3945 driver. -- RH continues to provide the ipw3945 driver in RHEL5.4 as a migration convenience. We do recommend that customers transition to the iwl3945 driver. Refer here to (kbase) for details on how to transition if you are doing an update install from a system that had its full installation prior to RHEL5.4. +- RH continues to provide the ipw3945 driver in RHEL5.4 as a migration convenience. We do recommend that customers transition to the iwl3945 driver. Refer here to (kbase - that Jeremy West agreed to do) for details on how to transition if you are doing an update install from a system that had its full installation prior to RHEL5.4. - Customers who report issues with the ipw3945 driver may be referred to migrate to the iwl3945 driver for resolution. For example, there are known issues connecting to VPN concentrators present in the ipw3945 driver which are resolved in the iwl3945 driver. - Note that use of the iwl3945 driver requires installing the iwl3945-firmware package from the supplementary RHN channel. Package version 15.28.2.8-2 or later is required. (ie iwl3945-firmware-15.28.2.8-2 or later) - Also note that the device name, for example as it appears in the output of the `ifconfig` command appears as eth0 (or eth1) when using the ipw3945 driver, when using the iwl3945 driver it is identified as wlan0. Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,6 +1,6 @@ editorial comment: this is an important migration issue. therefore it warrants the prominence of mention in the relnotes; rather than being obscured in the tech notes.) -- RH is no longer able to responsibly support the ipw3945 to our normal full levels of service as the upstream company responsible for that driver has suspended maintenance efforts on this particular driver. +- RH is no longer able to responsibly support the ipw3945 wireless laptop network driver to our normal full levels of service as the upstream company responsible for that driver has suspended maintenance efforts on this particular driver. - RH, following the guidance of the company responsible for the driver has migrated over to the iwl3945 driver (first introduced in RHEL5.3) - Ongoing maintenance of driver issues associated with the 3945 hardware will be provided on the iwl3945 driver. - All fresh/full installations of RHEL5.4 on systems with 3945 hardware will install the iwl3945 driver. Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,10 +1,10 @@ editorial comment: this is an important migration issue. therefore it warrants the prominence of mention in the relnotes; rather than being obscured in the tech notes.) -- RH is no longer able to responsibly support the ipw3945 wireless laptop network driver to our normal full levels of service as the upstream company responsible for that driver has suspended maintenance efforts on this particular driver. -- RH, following the guidance of the company responsible for the driver has migrated over to the iwl3945 driver (first introduced in RHEL5.3) +- Red Hat is no longer able to responsibly support the ipw3945 wireless laptop network driver to our normal full levels of service as the upstream company responsible for that driver has suspended maintenance efforts on this particular driver. +- Red Hat, following the guidance of the company responsible for the driver has migrated over to the iwl3945 driver (first introduced in Red Hat Enterprise Linux 5.3) - Ongoing maintenance of driver issues associated with the 3945 hardware will be provided on the iwl3945 driver. -- All fresh/full installations of RHEL5.4 on systems with 3945 hardware will install the iwl3945 driver. -- RH continues to provide the ipw3945 driver in RHEL5.4 as a migration convenience. We do recommend that customers transition to the iwl3945 driver. Refer here to (kbase - that Jeremy West agreed to do) for details on how to transition if you are doing an update install from a system that had its full installation prior to RHEL5.4. +- All fresh/full installations of Red Hat Enterprise Linux 5.4 on systems with 3945 hardware will install the iwl3945 driver. +- Red Hat continues to provide the ipw3945 driver in Red Hat Enterprise Linux 5.4 as a migration convenience. We do recommend that customers transition to the iwl3945 driver. Refer here to (kbase - that Jeremy West agreed to do) for details on how to transition if you are doing an update install from a system that had its full installation prior to Red Hat Enterprise Linux 5.4. - Customers who report issues with the ipw3945 driver may be referred to migrate to the iwl3945 driver for resolution. For example, there are known issues connecting to VPN concentrators present in the ipw3945 driver which are resolved in the iwl3945 driver. - Note that use of the iwl3945 driver requires installing the iwl3945-firmware package from the supplementary RHN channel. Package version 15.28.2.8-2 or later is required. (ie iwl3945-firmware-15.28.2.8-2 or later) - Also note that the device name, for example as it appears in the output of the `ifconfig` command appears as eth0 (or eth1) when using the ipw3945 driver, when using the iwl3945 driver it is identified as wlan0. FWIW, looks fine to me... *** Bug 515621 has been marked as a duplicate of this bug. *** Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,10 +1,8 @@ -editorial comment: this is an important migration issue. therefore it warrants the prominence of mention in the relnotes; rather than being obscured in the tech notes.) +Red Hat is no longer able to responsibly support the ipw3945 wireless laptop network driver to the full levels of service, as the upstream company responsible for that driver has suspended maintenance efforts on the driver. +Red Hat, following the guidance of the company responsible for the driver has migrated over to the iwl3945 driver (first introduced in Red Hat Enterprise Linux 5.3). Ongoing maintenance of driver issues associated with the 3945 hardware will be provided on the iwl3945 driver. All fresh/full installations of Red Hat Enterprise Linux 5.4 on systems with 3945 hardware will install the iwl3945 driver. +Red Hat continues to provide the ipw3945 driver in Red Hat Enterprise Linux 5.4 as a migration convenience. It is recommended that customers transition to the iwl3945 driver. Refer to the Red Hat Knowledgebase for details on how to transition if you are doing an update install from a system that had its full installation prior to Red Hat Enterprise Linux 5.4. +Customers who report issues with the ipw3945 driver may be referred to migrate to the iwl3945 driver for resolution. For example, there are known issues connecting to VPN concentrators present in the ipw3945 driver which are resolved in the iwl3945 driver. -- Red Hat is no longer able to responsibly support the ipw3945 wireless laptop network driver to our normal full levels of service as the upstream company responsible for that driver has suspended maintenance efforts on this particular driver. +Note -- Red Hat, following the guidance of the company responsible for the driver has migrated over to the iwl3945 driver (first introduced in Red Hat Enterprise Linux 5.3) +the use of the iwl3945 driver requires installing the iwl3945-firmware package from the supplementary RHN channel. Package version 15.28.2.8-2 or later is required. (ie iwl3945-firmware-15.28.2.8-2 or later) -- Ongoing maintenance of driver issues associated with the 3945 hardware will be provided on the iwl3945 driver. +Additionally, the device name, for example as it appears in the output of the `ifconfig` command appears as eth0 (or eth1) when using the ipw3945 driver, when using the iwl3945 driver it is identified as wlan0.-- All fresh/full installations of Red Hat Enterprise Linux 5.4 on systems with 3945 hardware will install the iwl3945 driver. -- Red Hat continues to provide the ipw3945 driver in Red Hat Enterprise Linux 5.4 as a migration convenience. We do recommend that customers transition to the iwl3945 driver. Refer here to (kbase - that Jeremy West agreed to do) for details on how to transition if you are doing an update install from a system that had its full installation prior to Red Hat Enterprise Linux 5.4. -- Customers who report issues with the ipw3945 driver may be referred to migrate to the iwl3945 driver for resolution. For example, there are known issues connecting to VPN concentrators present in the ipw3945 driver which are resolved in the iwl3945 driver. -- Note that use of the iwl3945 driver requires installing the iwl3945-firmware package from the supplementary RHN channel. Package version 15.28.2.8-2 or later is required. (ie iwl3945-firmware-15.28.2.8-2 or later) -- Also note that the device name, for example as it appears in the output of the `ifconfig` command appears as eth0 (or eth1) when using the ipw3945 driver, when using the iwl3945 driver it is identified as wlan0. This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?". This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. Red Hat has deprecated this driver, which has long since been replaced by another driver. A note was made to this effect. |