** Tags removed: kernel-request-3.11.0-7.14
** Tags added: bot-stop-nagging
** Tags added: latest-bios-202 needs-upstream-testing regression-
potential
** Tags added: raring
** Description changed:
The following is being reproduced every-time:
- When coming back from suspend, the alx driver w
** Also affects: linux (Arch Linux)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1213009
Title:
alx driver is not working after system resum
after few days I can say that above not working correctly.
With pm-utils installed my laptop won't suspend,
without pm-utils onboard scripts won't be executing. I'm investigating it
further more
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
I've achieved script to work now.
1. sudo apt-get install pm-utils
2. sudo touch /usr/lib/pm-utils/sleep.d/01alxdriver
3. sudo chmod +x /usr/lib/pm-utils/sleep.d/01alxdriver
4. sudo vim / nano or your favourite text editor and paste:
#!/bin/sh
case "$1" in
hibernate|suspend)
That's true.
Bug appears only with kernel 3.11.
about script in /etc/pm/sleep.d
I tried to do that, but I can't achieve my script to be executed...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
I tried using 3.10 ( 3.10.0-6-generic #17-Ubuntu SMP Fri Jul 26 18:29:23 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux),
and it seems to be working fine. please tell if you need more info.
about the workaround: note that you can automate it by putting in
/etc/pm/sleep.d
(see
http://askubuntu.com/ques
Linux TBH117 3.11.0-999-generic #201309110406 SMP Wed Sep 11 08:07:10
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Unfrtunately bug still exists.
Workaround:
before suspend type:
sudo rmmod alx
after wake up:
sudo modprobe alx
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1213009
Title:
alx driver is not working after system resume
Status i
from kernel 3.11.0-7 this bug also affects me.
how can I help to resolve this bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1213009
Title:
alx driver is not working after system re
Right, sorry, with 3.2 and 3.5 you would need the backports kernel. Can
you also test the v3.10 kernel:
https://launchpad.net/ubuntu/+source/linux/3.10.0-6.17/+build/4828465
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
Tried both kernels. couldn't load 3.2 (I think due to graphic card driver error
- the display keeps blinking).
and it 3.5 I get
:~$ modprobe alx
FATAL: Module alx not found.
:~$ modinfo alx
ERROR: Module alx not found.
:~$ uname -r
3.5.0-030500-generic
So I'm not sure how to procceed (should I ge
Can you also test the 3.2 and 3.5 kernels to see if this is a regression
or not:
v3.2 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-precise/
v3.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-quantal/
--
You received this bug notification because you are a member of Kerne
I didn't upgrad - it is a new computer and I installed 13.10 from the
beginning.
However I installed ubuntu 13.04 on a different partition.
the device is still not working after resuming from suspend, but there is no
constant error message (the same error does appear if I try to go back second
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of the
introduction of a regression, and when this regression was introduced.
If this is a regre
15 matches
Mail list logo
