cosmix, this bug report is being closed due to your last comment
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can
This seems to be fixed as of Precise (12.04) Beta 2. If there isn't
anyone else still affected by this issue, feel free to close this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/464305
Title:
This is 100% kernel issue. I've changed to 2.6.32-22-preempt and
everything is working fine. Without editing halt script.
--
Sky2 GbE NIC left at a bad state after shutdown.
https://bugs.launchpad.net/bugs/464305
You received this bug notification because you are a member of Ubuntu
Bugs, which
Well I'm back to the beginning. 2.6.32-22 amd64 and halt script edited
and still my network interface is up after shutdown.
--
Sky2 GbE NIC left at a bad state after shutdown.
https://bugs.launchpad.net/bugs/464305
You received this bug notification because you are a member of Ubuntu
Bugs, which
Do you upgraded to lucid or did a clean install?
--
Sky2 GbE NIC left at a bad state after shutdown.
https://bugs.launchpad.net/bugs/464305
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Clean install.
--
Sky2 GbE NIC left at a bad state after shutdown.
https://bugs.launchpad.net/bugs/464305
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Now on Lucid with 2.6.32-22 amd64 the /etc/init.d/halt script is exactly
the same as before, but problem is solved - NIC is powered down as it
should.
--
Sky2 GbE NIC left at a bad state after shutdown.
https://bugs.launchpad.net/bugs/464305
You received this bug notification because you are a
I had this problem on amd64 karmic and it still occurs on amd64 lucid.
--
Sky2 GbE NIC left at a bad state after shutdown.
https://bugs.launchpad.net/bugs/464305
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
When commenting the WOL part in halt script everything wokrs fine since
I don't use that feature.
--
Sky2 GbE NIC left at a bad state after shutdown.
https://bugs.launchpad.net/bugs/464305
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
These are drivers, not firmware.
Now I found out something else - /etc/init.d/halt script has the part,
that should make possible to not shut down the network interfaces to
enable using the WOL.
When I commented out that part -
# Make it possible to not shut down network interfaces,
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
Sky2 GbE NIC left at a bad state after shutdown.
https://bugs.launchpad.net/bugs/464305
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Unfortunately firmware update did not solve the problem completely -
longer uptime causes this behaviour to be back again.
--
Sky2 GbE NIC left at a bad state after shutdown.
https://bugs.launchpad.net/bugs/464305
You received this bug notification because you are a member of Ubuntu
Bugs, which
12 matches
Mail list logo
