Comment 10 for bug 876147
Revision history for this message
| TonyLudwick (tonyludwick) wrote Re: [Bug 876147] Re: Intel Corporation Centrino Wireless-N + WiMAX 6150 (rev 67) not working after upgrade to 11.10 | #10 |
Tried it had no effect.
On Tue, Nov 15, 2011 at 10:56 AM, Chris J Arges
<email address hidden>wrote:
> Noticed these threads regarding issues with the 6150 on 11.04. Would this
> affect 11.10 as well?
>
> http://
> https:/
>
> Would it be possible to try this workaround and see if it has any affect
> on this bug?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Intel Corporation Centrino Wireless-N + WiMAX 6150 (rev 67) not
> working after upgrade to 11.10
>
> Status in Ubuntu:
> Confirmed
> Status in “linux” package in Ubuntu:
> Triaged
>
> Bug description:
> I had a pretty stable Natty install, but then I went and upgraded to
> 11.10. It went downhill from there. Most of my problems I am about to
> describe are covered in various threads but none of the solutions have
> worked for me.
>
> I have a Asus laptop model no: U56E-BBL5 with 6gb RAM, Intel core i5
>
> 1. Wireless/wifi stopped working. Outputs from various commands
> suggested in other threads are pasted here
>
> [CODE]me@
> 0: asus-wlan: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> 1: asus-wimax: WiMAX
> Soft blocked: yes
> Hard blocked: no
> 2: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
>
> me@me-ubuntu:~$ iwconfig
> lo no wireless extensions.
>
> eth0 no wireless extensions.
>
> wlan0 IEEE 802.11bgn ESSID:off/any
> Mode:Managed Access Point: Not-Associated Tx-Power=15 dBm
> Retry long limit:7 RTS thr:off Fragment thr:off
> Power Management:on
>
> me@me-ubuntu:~$ dmesg | grep -i firm
> [ 0.811564] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
> [ 15.539802] iwlagn 0000:02:00.0: loaded firmware version 41.28.5.1
> build 33926
> [ 15.667238] elantech: assuming hardware version 3, firmware version
> 69.15.1
>
> me@me-ubuntu:~$ lspci | grep -i network
> 02:00.0 Network controller: Intel Corporation Centrino Wireless-N + WiMAX
> 6150 (rev 67)
>
> me@me-ubuntu:~$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 11.10
> Release: 11.10
> Codename: oneiric
>
> me@me-ubuntu:~$ sudo lshw -C network
> [sudo] password for me:
> *-network
> description: Wireless interface
> product: Centrino Wireless-N + WiMAX 6150
> vendor: Intel Corporation
> physical id: 0
> bus info: pci@0000:02:00.0
> logical name: wlan0
> version: 67
> serial: 40:25:c2:34:fe:d4
> width: 64 bits
> clock: 33MHz
> capabilities: pm msi pciexpress bus_master cap_list ethernet
> physical wireless
> configuration: broadcast=yes driver=iwlagn
> driverversion=
> link=no multicast=yes wireless=IEEE 802.11bgn
> resources: irq:50 memory:
> *-network
> description: Ethernet interface
> product: AR8151 v2.0 Gigabit Ethernet
> vendor: Atheros Communications
> physical id: 0
> bus info: pci@0000:04:00.0
> logical name: eth0
> version: c0
> serial: 14:da:e9:2a:1e:bc
> size: 100Mbit/s
> capacity: 1Gbit/s
> width: 64 bits
> clock: 33MHz
> capabilities: pm msi pciexpress vpd bus_master cap_list ethernet
> physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
> configuration: autonegotiation=on broadcast=yes driver=atl1c
> driverversion=
> latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s
> resources: irq:53 memory:
> [/CODE]So, wireless is completely not working now and I have to sit near
> by shoe closet on the floor to get a wired connection to post this.
>
> 2. Suspend hangs the system.
>
> Whenever I suspend or system goes to suspend due to inactivity, the
> system completely freezes. Only a hard reset is possible at this time.
>
> 3. System is generally slow and unreliable. Only saving grace has been
> Gnome3.2 which looks rather neat.
>
> Any help is greatly appreciated and any one else having same problems
> please give a shout. I would feel a little better knowing that I am
> not alone having these problems.
>
> To manage notifications about this bug go to:
> https:/
>