14e4:4727 [Samsung NP-RF511-S03SE] wifi stops working when laptop lid is closed

[unksi]

In Ubuntu 12.10, when I close the laptop lid, the wlan connection is closed. Wired (ethernet) connections keep working normally.

This prevents using only external monitor in places where wired connections are not accessible and forces the user to keep the laptop display on even if it is not needed.

Changing the power manager settings to "Do nothing" does not affect this. It also does not matter if the laptop is plugged in or not.

Apparently, at some point, disabling the screen saver would fix this issue. However, there is no such setting on Ubuntu 12.10.

---
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: unksi 2255 F.... pulseaudio
 /dev/snd/pcmC0D0p: unksi 2255 F...m pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
DistroRelease: Ubuntu 12.10
InstallationDate: Installed on 2013-03-01 (16 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
MarkForUpload: True
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic root=UUID=a7bbcbf4-2e43-442d-a6e9-c22e2a1016c0 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-25-generic N/A
 linux-backports-modules-3.5.0-25-generic N/A
 linux-firmware 1.95
Tags: quantal running-unity
Uname: Linux 3.5.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
dmi.bios.date: 11/27/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 17HX.M045.20121127.SSH
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: RF511/RF411/RF711
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: 17HX
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr17HX.M045.20121127.SSH:bd11/27/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr17HX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF511/RF411/RF711:rvr17HX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: RF511/RF411/RF711
dmi.product.version: 17HX
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1153252/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[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 1153252

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.

[unksi (unksi)]

apport information

[unksi (unksi)]

apport information

[unksi (unksi)]

apport information

[unksi (unksi)]

apport information

[unksi (unksi)]

apport information

[unksi (unksi)]

apport information

[unksi (unksi)]

apport information

[unksi (unksi)]

apport information

[unksi (unksi)]

apport information

[unksi (unksi)]

apport information

[unksi (unksi)]

apport information

[unksi (unksi)]

apport information

[unksi (unksi)]

apport information

[unksi (unksi)]

apport information

[unksi (unksi)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

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.9-rc3-raring/

[unksi (unksi)]

I cannot test it because dkms cannot build the wireless driver modules for this kernel. I have attached a log of the installation.

The kernel itself boots fine - it is just missing the wlan drivers needed to complete the test.

I did use --force-all with dpkg to get it installed, as the linux-headers package required itself as its dependency and thus would not install normally. However, I do not know how to fix this issue with dkms. If you can tell me how to get it installed, I will be happy to try again.

[unksi (unksi)]

Here is the log for the wlan driver dkms module install. It says the header Makefile does not exist.

I checked and the file does exist - it is empty, though.

[unksi (unksi)]

Update: the makefile does not really exist, but it is a symlink that loops back to itself instead.

[penalvch (penalvch)]

Tero Ratilainen, could you please provide the full computer model as noted on the sticker?

[unksi (unksi)]

The model is Samsung NP-RF511-S03SE (afaik only sold in Nordic countries and has different specs from the regular S03 counterpart).

[penalvch (penalvch)]

Tero Ratilainen, because Samsung does not easily reveal what the latest BIOS is for a given model, could you please download the latest firmware as per http://www.samsung.com/uk/support/model/NP-RF511-S03SE-downloads#, and advise if a BIOS update is available? If so, when you update to this, does it change anything? If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

[unksi (unksi)]

# dmidecode -s bios-version
17HX.M045.20121127.SSH
# dmidecode -s bios-release-date
11/27/2012

I updated it last time around March, before switching the laptop from Windows to Ubuntu. I will check the update utility if they have any updates for it when I can boot to Windows (they don't show BIOS updates on their website, only utility versions).

This bug happens with Raring as well. I will check tomorrow if it happens on Saucy.

[unksi (unksi)]

I checked BIOS and I have the newest version (17HX).

It also happens with saucy. Here is a log from ping:

$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=47 time=35.9 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=47 time=33.1 ms
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
(message above was repeated quite a many times)
From 10.0.1.125 icmp_seq=57 Destination Host Unreachable
From 10.0.1.125 icmp_seq=58 Destination Host Unreachable
From 10.0.1.125 icmp_seq=59 Destination Host Unreachable
From 10.0.1.125 icmp_seq=60 Destination Host Unreachable
From 10.0.1.125 icmp_seq=61 Destination Host Unreachable
From 10.0.1.125 icmp_seq=62 Destination Host Unreachable
From 10.0.1.125 icmp_seq=63 Destination Host Unreachable
From 10.0.1.125 icmp_seq=64 Destination Host Unreachable
From 10.0.1.125 icmp_seq=65 Destination Host Unreachable
From 10.0.1.125 icmp_seq=66 Destination Host Unreachable
From 10.0.1.125 icmp_seq=67 Destination Host Unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
64 bytes from 8.8.8.8: icmp_seq=81 ttl=47 time=35.8 ms
64 bytes from 8.8.8.8: icmp_seq=82 ttl=47 time=34.7 ms
64 bytes from 8.8.8.8: icmp_seq=83 ttl=47 time=32.1 ms
64 bytes from 8.8.8.8: icmp_seq=84 ttl=47 time=31.6 ms
64 bytes from 8.8.8.8: icmp_seq=85 ttl=47 time=28.6 ms
^C
--- 8.8.8.8 ping statistics ---
85 packets transmitted, 7 received, +11 errors, 91% packet loss, time 124409ms
rtt min/avg/max/mdev = 28.689/33.180/35.996/2.423 ms

[penalvch (penalvch)]

Tero Ratilainen, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[unksi (unksi)]

I tested with 3.11.0-031100rc4-generic. The ping output changed, though it still does get disconnected:

$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=47 time=25.6 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=47 time=27.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=47 time=29.7 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=47 time=31.4 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=47 time=88.8 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=47 time=2682 ms
From 10.0.1.130 icmp_seq=56 Destination Host Unreachable
From 10.0.1.130 icmp_seq=57 Destination Host Unreachable
From 10.0.1.130 icmp_seq=58 Destination Host Unreachable
64 bytes from 8.8.8.8: icmp_seq=10 ttl=47 time=49571 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=47 time=48592 ms
64 bytes from 8.8.8.8: icmp_seq=20 ttl=47 time=39698 ms
64 bytes from 8.8.8.8: icmp_seq=21 ttl=47 time=38700 ms
64 bytes from 8.8.8.8: icmp_seq=22 ttl=47 time=37696 ms
64 bytes from 8.8.8.8: icmp_seq=60 ttl=47 time=10981 ms
64 bytes from 8.8.8.8: icmp_seq=61 ttl=47 time=9981 ms
64 bytes from 8.8.8.8: icmp_seq=62 ttl=47 time=8985 ms
64 bytes from 8.8.8.8: icmp_seq=63 ttl=47 time=7981 ms
64 bytes from 8.8.8.8: icmp_seq=64 ttl=47 time=6976 ms
64 bytes from 8.8.8.8: icmp_seq=65 ttl=47 time=5978 ms
64 bytes from 8.8.8.8: icmp_seq=66 ttl=47 time=4982 ms
64 bytes from 8.8.8.8: icmp_seq=67 ttl=47 time=3981 ms
64 bytes from 8.8.8.8: icmp_seq=68 ttl=47 time=2984 ms
64 bytes from 8.8.8.8: icmp_seq=69 ttl=47 time=1983 ms
64 bytes from 8.8.8.8: icmp_seq=70 ttl=47 time=977 ms
64 bytes from 8.8.8.8: icmp_seq=71 ttl=47 time=62.8 ms
64 bytes from 8.8.8.8: icmp_seq=72 ttl=47 time=24.9 ms
64 bytes from 8.8.8.8: icmp_seq=73 ttl=47 time=25.1 ms

[penalvch (penalvch)]

Tero Ratilainen, for regression testing purposes, could you please test for this in Precise via http://releases.ubuntu.com/precise/ ?

[unksi (unksi)]

I tested it with Ubuntu 12.04.2 amd64 livecd. It happened again, however this time ping would freeze when the lid was closed (it stopped from pinging and would recover with ^C and restarting the process).

[penalvch (penalvch)]

Tero Ratilainen, could you please test for this in Lucid via http://old-releases.ubuntu.com/releases/lucid/ ?

[unksi (unksi)]

Tested out with 10.04.4, the behaviour is similar to saucy (gives out ping: sendmsg: No buffer space available, recovers after that).

[Joseph Salisbury (jsalisbury)]

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.

We are approaching release and would like to confirm if this bug is still present. Please test again with the latest development 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.

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

[unksi (unksi)]

Still exists with 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

Tero Ratilainen, just to clarify, when you go into System Setting, are all the power management settings regarding lid state set to do nothing/disabled? If so, you may have to WORKAROUND a gnome-power-manager issue that doesn't inhibit systemd in order for this set state to engage.

[Launchpad Janitor (janitor)]

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