Unable to enter suspend/hibernation in Ubuntu 13.04 on an Asus X201E a.k.a. F201E

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/1157435/+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.]

Status changed to 'Confirmed' because the bug affects multiple users.

FWIW, I had also seen this behaviour on 12.10 on my Asus F201E, but not as often (usually after a day or two it would stop suspending). I upgraded to 13.04 and so far it's happened every time (only just rebooted into 13.04), as Alex described. My log is a bit different, attaching in full.

Hi Nelson,
thank you very much for your comment/support. I just added my complete log above.

Indeed, I experienced the same bug on 12.10, in my case again after the first suspend-operation that worked as in 13.04 like a charm. But from the second time on, no possibility to get into suspend-mode, neither in 12.10, nor in 13.04. I tried each and every terminal-command I could find on the net, without any positive effect. Thus I hope a fix will be incorporated in the final version of 13.04.

The thing is that I buyed the Asus X201e exactly for the reason that Ubuntu [12.04 LTS] was preinstalled on it and that I presumed maximum compatibility. But 12.04 LTS hat the same bug as 12.10, notably that after suspend [no matter if it worked like in 12.04 or not as in 12.10], I was no longer able to reconnect to my WIFI. That's why I made an upgrade to 12.10 and then 13.04 [in both cases full re-installations from USB with the respective the 64bit-versions].

Sadly, I got minimum compatibility, as ASUS seems to have used a special version with their own drivers no one can find on the net. I contacted their technical "support" twice, and they even admitted that they had "no experience" with Ubuntu and could not help me or send me a driver-package or ISO-link!!!

And what ASUS hosts in the following repository [or any other - I tried them all] is no help as well:

deb http://asus.archive.canonical.com/updates precise-annan public

Ergo, my final hope lies in the Ubuntu-community.

Best,
Alex

I'm tagging this with regression-release, but the only last-working version I can give is the precise version.

Info that I have:
 * suspend was working fine with Precise (the OS the machine was purchased with) and there are no updates at http://asus.archive.canonical.com/updates/dists/precise-annan/public/binary-amd64/,
 * suspend would work mostly with Quantal (seemed to stop suspending after 4-5 suspends - it was for this reason I tried upgrading to raring)
 * suspend doesn't work at all (for me) in raring as per above.

This is on a machine purchased with Precise pre-installed.

Indeed, the preinstalled Asus-custom-built 12.04 LTS was working just fine on the X201e, because as it seems, they incorporated special drivers you cannot find on the net, and their "technical support" is no help either. Now where do we go from here?

The only thing I found was a czech forum-entry on how to rebuild the recovery-partition, here the original link:

http://forum.ubuntu.cz/index.php?PHPSESSID=kq8h8pv5fqdo3tjic4rk68jop4&topic=66022.msg472005#msg472005

and the google-translation [reply #14]:

http://translate.google.com/translate?hl=en&ie=UTF8&prev=_t&sl=auto&tl=en&u=http://forum.ubuntu.cz/index.php%3FPHPSESSID%3Dkq8h8pv5fqdo3tjic4rk68jop4%26topic%3D66022.msg472005%23msg472005

It would be elegant to be able to convert backup_ASUS.tgz in a bootable ISO, but I didn't try that for now and I certainly won't reformat the HDD like it was with 109 GB wasted for an omnious backup of an old OS. This is also the reason I'm not interested in 12.04 LTS, but I want to see 13.04 able to enter into regular suspend mode [I think it's a fundamental ability for a computer nowadays] from the second time onwards, not only the first & last time.

Fingers crossed, I hope there is a solution, because if it worked in 12.04 and *sometimes* in 12.10 - it should work in 13.04!

The other thing I learned is to never ever buy a notebook with a pre-installed special-version of Ubuntu, but to look specificly for maximum compatibility with to official distro. I didn't realize that there is a huge difference, now I now better.

Hi,
On my X201E, dmesg indicates alx ethernet driver has a problem going to suspend state on the 2nd time.
As i use only wifi and not ethernet, i desactivated alx driver adding line "blacklist alx" in file /etc/modprobe.d/blacklist.conf (for example you can do it by typing "sudo gedit /etc/modprobe.d/blacklist.conf" in a terminal).
It works for me.
Hope it can help.

It won't work just after modifying the file, because the kernel module is still present.
You've got to "sudo rmmod alx" or just reboot, the module won't be loaded at startup (because it's blacklisted)

Hi Thomas,

many thanks for your mail. You know what:

IT WORKED!!!!!!!!!!!!!!!!!!!!!!! BRAVO, HAT TIP & THUMBS UP!

I followed your advice to add the line "blacklist alx" into /etc/modprobe.d/blacklist.conf, rebooted and managed to go 3 times in suspend in a row without any problems a.k.a. the X201e not waking up again.

Thus, I would say problem solved @ 99%. Give me one day to test it again and I will present my findings.

If I get it right, it's not only affecting pm-utils [if at all?], but also the kernel module. Perhaps this should be added as an info above in the header. Do you know the exact "project" to chose, Thomas?

Ha, what Asus' so-called "technical support" was unable to fix because of a "lack of experience with Ubuntu", you can. I'm delighted! This is the bright side of the internet.

Best,
Alex

I'd like to reiterate at this point that the solution Thomas proposed solves the problem of the Asus X201E not being able to go into standby on Ubuntu 13.04. After several reboots & suspends, the bug is not coming back, and I'm delighted about it! So, to recapitulate how to fix it:

1. Open terminal and paste the following:

sudo gedit /etc/modprobe.d/blacklist.conf

2. Add this line to the end of the config-file that opened and save it:

blacklist alx

3. Reboot.

At this point, thumbs up and many thanks again to Thomas - it was indeed the ethernet driver messing up the ability to go into suspend more than once.

Best,
Alex

Thanks.
But it's not a solution, it's a workaround.
When you blacklist ethernet driver, * you can not use ethernet connexion anymore ! *
There is still a suspend/hibernation big problem in alx driver. Nothing is solved.
Thomas.

Granted, it's only *solved* for me as I only use WIFI. I changed the titel of this bug-report back again.

But you are right of course, up to now, it's only an arbitrage between standy & ethernet. Thus the bug remains, but at least there is a workaround!

If I get that straigth, the ethernet-adapter prevents standby, so the bug should be narrowed down in that respect. Having standby AND ethernet would be ideal, indeed.

I hope this gets fixed in the final version of 13.04.

Looking forward.
Alex

I've found a small workaround.
In /etc/pm/config.d i've created a file "config" containing the following line:

SUSPEND_MODULES="alx"

Now suspend works, but NetworkManager fails to resume the last connection profile used on resume (it doesn't remember the active connection on suspend).
I've also created the file "11_alx" into /etc/pm/sleep.d with the following content:

====================================================
#!/bin/sh
PATH=/sbin:/usr/sbin:/bin:/usr/bin

case "${1}" in
    hibernate|suspend)
        CONN=$(nmcli -t --fields name conn status | uniq)
        echo -n $CONN > /var/spool/nmconn.txt ## just a temp file to store the active connection
        nmcli conn down id "$CONN"
        ;;

    resume|thaw)
        CONN=$(cat /var/spool/nmconn.txt)
        sleep 3
        nmcli conn up id "$CONN"
        ;;

esac
====================================================

but while the connection profile gets saved into /var/spool/nmconn.txt, the connection wasn't resumed on resume (but it get resumed if I execute manually those command with sudo in a terminal.

Hi Antonio,

cool, many thx. But is it really better having the NetworkManager failing to resume the last connection-profile used? I would rather opt [like I did] for having a working WIFI and no ETHERNET instead. I'm sure there would also be a way to make the sudo-command to resume the connection automatic - or for desktop-uses of the Asus X201E [perhaps there are some people out there] to switch the adapters and disabling WIFI instead of ETHERNET using Thomas' hack.

Anyway, nice to see that I'm not alone here and that there are several ways to get suspend-mode working. On the other hand, it's really weird that this is not working out-of-the-box with 13.04.

But the greatest irony in all of this is still the failed assistance by ASUS. Why on earth they didn't release their proprietary drivers and give assistance like I asked them for is very telling to say the least.

Best,
Alex

Guys,

i have this problem also, but i fix it using this method.

http://www.webupd8.org/2013/01/fix-wireless-or-wired-network-not.html

this is the step i done, based on tutorial above

1. sudo gedit /etc/pm/config.d/unload_modules
2. insert into the file

 SUSPEND_MODULES="$SUSPEND_MODULES MODULE_NAME_FOUND_UNDER_STEP_1"

3. reboot, done

now i can suspend and wake fine, all still working, hopefully will help your case...

Hi,
I have same problem and many thanks to Arie that Arie's solution works GREAT for me.

Actually I don't have /etc/pm/config.d/unload_modules file
So I created that file with just one line

SUSPEND_MODULES="$SUSPEND_MODULES alx"

and reboot.
Then everything works fine for me:)

Switch package to the kernel as this is a suspend issue which is resolved by removing the alx driver before suspend and reinserting it after resume.

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.10 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.10-rc2-saucy/

Since this is related to the alx driver, there is probably no need to test the latest up stream kernel, requested in comment #19.

Hi -
I have this same bug - I've got a Asus X201EP upgraded to Ubuntu 13.04, and when trying to suspend, the computer just goes straight to the lock screen instead of suspending.

None of the above solutions worked for me (I tried the solutions listed in comments #11, 16, and 17).

However, I did find a solution that worked, from here:
http://askubuntu.com/questions/254457/why-wont-ubuntu-suspend-hibernate

Here's the relevant portion that solved my problem:
===================
It was caused by a script which avoid suspend-bug with usb 3, located in [B]/etc/pm/sleep.d[/B] . I removed this well-known script and my comp went suspended without any trouble.

Sorry for the non-existing issue.

(Note that this script never caused issue before, ie with kernels 3.5 and 3.7.)
===================

I spoke too soon...

Using the solution in the comment above (that is, removing the script titled 11_usb_s3 from /etc/pm/sleep.d/) only allowed me to suspend once. When trying to suspend a second time, the computer started the suspend process, then dropped me back into the logon screen.

In order to to fix this, I needed to use the solution described by comment #17.

So, to summarize, I needed to do two things to fix my suspend problem, both necessary and neither sufficient:

remove /etc/pm/sleep.d/11_usb_s3

add /etc/pm/config.d/unload_modules
Inside unload_modules, include the line
SUSPEND_MODULES="$SUSPEND_MODULES alx"

@jsalisbury

I've tested the 3.10 kernal.
(And change the bug status to confirmed according to #19.)

suspend works on Linux kernel 3.10.

But wired network doesn't work on kernel 3.10.
So I think it's not a good idea to add the 'kernel-bug-fixed-upstream' tag.

@jsalisbury

I updated to saucy (for other reasons), and tried suspend with the v3.10 kernal. It suspended, but didn't resume. Details on bug 1206625. Thanks to the team for looking at these!

@jsalisbury

Sorry - update: After updating the bios to the latest version from Asus, retrying with the v3.10 kernel resumed fine :) Thanks for your help!

Hi,

I have ASUS X201E
I bought it with Ubuntu 12.04 and reinstalled to Ubuntu 13.04 64bit
After i installed alx driver for wired Ethernet exactly by this method:

http://askubuntu.com/questions/284295/how-do-i-enable-the-alx-ethernet-driver-on-ubuntu-13-04

(Answer 1)

I don't have a problems with sleep mode and my wired Ethernet works fine
I work with only Wifi, but in anytime i can connect to wire Ethernet. And i didn't have a problems with sleep mode.
Please try it - i think it will help to you

Perlover

Alex Alibi, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

It seems to be fixed. I did a fresh install of Ubuntu 13.04 [final] on another Asus F201E in the meantime and the suspend-/hibernation-bug was no longer there, and this without any terminal-hacks.

Thus, I suspect that it was an issue related to the beta-version of 13.04.

Best,
Alex

Alex Alibi, closing the linux (Ubuntu) general task. Please feel free to reopen if the issue is found in a release prior to Raring and you would desire a backport.

Hi

I just reset my laptop (Asus x201ep) back to factory settings, then immediately upgraded to Ubuntu 13.10. The bug, at least for me, has not been fixed - I still get sent straight to the login screen when I try to suspend. No settings have been changed from the default settings, and the only new program installed is chromium.

Hi jessepye,

thanks for your message. Ok, this tells us that the problem is still not fixed - at least via an upgrade. But I erased my complete HDD, used gparted to create several partitions [SWAP/OS/DATA] and then installed 13.04 inside my OS-partition. I'll format my OS-partition again in the coming days and install 13.10 on it - but from the ISO, not via an upgrade [I never do updates or upgrades, as they are building upon a mess]. I'll post the results here. But in my eyes, to disable the ethernet-adapter was the best fix the last 6 months, as I only use WIFI anyway. But I understand that this is not the panacea for everybody.

I'll keep you informed.

Best,
Alex

jessepye, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.