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
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
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
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.
** Changed in: linux (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of
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
** Changed
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
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
@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!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@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!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@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.
** Changed in: linux (Ubuntu)
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
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
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.
** Package changed: pm-utils (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
Since this is related to the alx driver, there is probably no need to
test the latest up stream kernel, requested in comment #19.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157435
Title:
Unable
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:)
--
You received
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
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
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
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.
--
You received this bug notification because you are a member of
** Summary changed:
- Unable to enter suspend/hibernation in Ubuntu 13.04 on an Asus X201E a.k.a.
F201E [SOLVED]
+ Unable to enter suspend/hibernation in Ubuntu 13.04 on an Asus X201E a.k.a.
F201E
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
22 matches
Mail list logo
