Ubuntu 15.10: WiFi disabled on Thinkpad X230

[viv]

Like there :
https://<email address hidden>/msg4805327.html

My wifi doesn't work anymore. Nothing seems to reactivate it. I tried to use on/off button, to restart iwlwifi, to reboot the compu.

What may i do ?

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-25-generic 4.2.0-25.30
ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
Uname: Linux 4.2.0-25-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: vivien 912 F.... pulseaudio
CurrentDesktop: GNOME
Date: Sat Feb 6 15:37:14 2016
HibernationDevice: RESUME=UUID=0e043f89-5a2f-4bb1-94e8-19cb33703486
InstallationDate: Installed on 2016-01-29 (8 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 3438FE2
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic root=UUID=b09ce02e-80f8-46f7-b943-3ecc7001fd60 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-25-generic N/A
 linux-backports-modules-4.2.0-25-generic N/A
 linux-firmware 1.149.3
SourcePackage: linux
UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/09/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: GCETA2WW (2.62 )
dmi.board.asset.tag: Not Available
dmi.board.name: 3438FE2
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGCETA2WW(2.62):bd04/09/2015:svnLENOVO:pn3438FE2:pvrThinkPadX230Tablet:rvnLENOVO:rn3438FE2:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3438FE2
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[viv (rochevivien)]

Hello,

Sorry for the late. I tried today to update bios from 2.62 to 2.63. It changed nothing.
Here's the output of the command line you asked :

GCETA3WW (2.63 )
09/24/2015

Update to 16.04LTS will may solve this problem ?

[penalvch (penalvch)]

viv, it would be helpful to test http://cdimage.ubuntu.com/daily-live/current/ . Could you please advise?

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[viv (rochevivien)]

I just come from updating, the problem is the same...

cat /etc/lsb-release
*DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"

[penalvch (penalvch)]

viv, could you please:
1) Execute the following terminal command and provide the results:
rfkill list

2) Advise do you have a wireless hard switch or keyboard combination that toggles the WiFi?

[viv (rochevivien)]

Here's the 'rfkill list' results :

0: tpacpi_bluetooth_sw: Bluetooth
 Soft blocked: no
 Hard blocked: no
1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
2: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

It shows that my wifi switch is on.

The LAN connection is also crappy. Each half an hour (sometimes less) I have to connect it again.

[penalvch (penalvch)]

viv, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.