I wonder if there's some laptop-mode thing that's causing issues. Things that come to mind are wlan power-saving mode and rfkill. Speaking of which, what's rfkill say when you're struggling?
Also, could you clarify "works" and "doesn't work"? Do you mean that you can't get even get it to scan for access points, or just that it won't connect (or something else)? If the former, what's "iwlist wlan2 scan" tell you (when it's otherwise not working)?
Cttoi, I'm left wondering why your is adapter wlan2... This might suggest some sort of driver issue, I guess? What's "ifconfig -a | grep wlan" tell you?
--
Jonathan
On 10 August 2014 14:59, Lawrence Bottorff <borgauf@gmail.com> wrote:
Here's the output:*-networkdescription: Ethernet interfaceproduct: 82577LM Gigabit Network Connectionvendor: Intel Corporationphysical id: 19bus info: pci@0000:00:19.0logical name: eth2version: 06serial: f0:de:f1:32:d4:7fcapacity: 1Gbit/swidth: 32 bitsclock: 33MHzcapabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiationconfiguration: autonegotiation=on broadcast=yes driver=e1000e driverversion=2.3.2-k firmware=0.12-1 latency=0 link=no multicast=yes port=twisted pairresources: irq:41 memory:f2500000-f251ffff memory:f2525000-f2525fff ioport:1820(size=32)*-networkdescription: Wireless interfaceproduct: Centrino Advanced-N 6200vendor: Intel Corporationphysical id: 0bus info: pci@0000:02:00.0logical name: wlan2version: 35serial: 58:94:6b:79:8a:68width: 64 bitsclock: 33MHzcapabilities: pm msi pciexpress bus_master cap_list ethernet physical wirelessconfiguration: broadcast=yes driver=iwlwifi driverversion=3.13.0-32-generic firmware=9.221.4.1 build 25532 ip=172.15.255.28 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgnresources: irq:43 memory:f2400000-f2401fffSo just putting it in lock is fine, but suspend or reboot starts the fight to get connected.On Sun, Aug 10, 2014 at 10:58 AM, Kiser, Ryan Lee <rlkiser@iu.edu> wrote:You don't happen to know which wifi adapter your thinkpad has, do you? Some more specific details would help.
I believe putting 'lshw -C network' in a terminal (without quotes) should give you a list of the network bits in your laptop. Don't hold it against me if I'm wrong though, I don't have a linux box with me to try it out on.
Ryan
> _______________________________________________
On Aug 9, 2014, at 5:07 PM, Lawrence Bottorff <borgauf@gmail.com> wrote:
> I'm new to this state (up in Elkhart) and I'm on U14.04 on my Thinkpad X201. I could not get Wifi to work at all initially. Then a Xfinity support person "changed something" and it . . . sort of worked. That means it worked after fiddling with enable, disable, (I'm on Gnome classic). Actually, I don't know what I would do, but eventually it would work. Then I'd put it in suspend, come back . . . and it wouldn't work. Repeat fiddling, rebooting, etc., then it would work. Any ideas what I'm having probs with?
>
> LB
> Elkhart
> BLUG mailing list
> BLUG@bloomingtonlinux.org
> http://lists.bloomingtonlinux.org/mailman/listinfo/blug
_______________________________________________
BLUG mailing list
BLUG@bloomingtonlinux.org
http://lists.bloomingtonlinux.org/mailman/listinfo/blug
_______________________________________________
BLUG mailing list
BLUG@bloomingtonlinux.org
http://lists.bloomingtonlinux.org/mailman/listinfo/blug