10ec:8171 Wifi card not working

[Emanuel Negromonte]

After installing Ubuntu 14.04 Beta 2 to NIC Realtek Wlan does not enable, and some commands are needed to make the card work. It shows as "disabled via hardware" and when buttons are pressed on the notebook enables and disables the card quickly.

See:

$ sudo rfkill unblock all
---
ApportVersion: 2.14.1-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: emanuel 1704 F.... pulseaudio
CurrentDmesg:
 [ 25.846086] init: plymouth-upstart-bridge main process ended, respawning
 [ 2018.395021] perf samples too long (2509 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=af9bc449-809f-46eb-bb79-42481ac2ac47
InstallationDate: Installed on 2014-04-06 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta i386 (20140326)
MachineType: Intel Corporation HuronRiver Platform
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=d9fbe1b7-5840-4ec2-858e-85fe8bb2e156 ro locale=pt_BR quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-23-generic N/A
 linux-backports-modules-3.13.0-23-generic N/A
 linux-firmware 1.127
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: trusty
Uname: Linux 3.13.0-23-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 03/05/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 1.05_
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Emerald Lake
dmi.board.vendor: Intel Corp.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr1.05_:bd03/05/2011:svnIntelCorporation:pnHuronRiverPlatform:pvr0.1:rvnIntelCorp.:rnEmeraldLake:rvrFAB1:cvnIntelCorporation:ct9:cvr0.1:
dmi.product.name: HuronRiver Platform
dmi.product.version: 0.1
dmi.sys.vendor: Intel Corporation

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1304528

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Emanuel Negromonte (emanuelnegromonte)]

apport information

[Emanuel Negromonte (emanuelnegromonte)]

apport information

[Emanuel Negromonte (emanuelnegromonte)]

apport information

[Emanuel Negromonte (emanuelnegromonte)]

apport information

[Emanuel Negromonte (emanuelnegromonte)]

apport information

[Emanuel Negromonte (emanuelnegromonte)]

apport information

[Emanuel Negromonte (emanuelnegromonte)]

apport information

[Emanuel Negromonte (emanuelnegromonte)]

apport information

[Emanuel Negromonte (emanuelnegromonte)]

apport information

[Emanuel Negromonte (emanuelnegromonte)]

apport information

[Emanuel Negromonte (emanuelnegromonte)]

apport information

[Emanuel Negromonte (emanuelnegromonte)]

apport information

[Emanuel Negromonte (emanuelnegromonte)]

apport information

[Joseph Salisbury (jsalisbury)]

Do you have to run the rfkill command after each reboot?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/

[Emanuel Negromonte (emanuelnegromonte)]

Yes, the problem persists, you must run the command I talked to unlock the card, no it does not work.

[Joseph Salisbury (jsalisbury)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

  With the recent release of this Ubuntu release, would like to confirm if this bug is still present. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Launchpad Janitor (janitor)]

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