Just upgraded from Hardy to Jaunty and my wake on lan stopped working.
I'm using a realtek 8168 on board NIC, although I notice the driver is
8169. Have tried editing halt script, using ethtool and disabling
ifdown commands in /etc/init.d/networking all to no avail.
Does anyone have a fix?
For anyone who is having the above problem, the fix for me was to
replace the 8169 driver with realteks latest 8168 driver from their
website. This in combination with NETWORKDOWN=no in the
/etc/init.d/halt script worked for me - WOL is now working nicely again.
I guess there is a small problem
Hi my problem is a little different. I was using Kubuntu 8.10 till the
update to 9.04 with Wake On Lan.
Just 3 things needed to be done in my case additional to enabling wol.
- Deinstallation des Networkmanagers
I guess because it messes with the settings
- Editieren der /etc/init.de/halt
** Changed in: linux (Ubuntu)
Importance: Medium = Low
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
Wake on LAN (WOL) not working with r8169 driver on Gutsy
https://bugs.launchpad.net/bugs/160413
You received this bug notification because you are a member of Ubuntu
** Tags added: ct-rev
--
Wake on LAN (WOL) not working with r8169 driver on Gutsy
https://bugs.launchpad.net/bugs/160413
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
A quick test with jaunty does not show any improvement on my machine
(still the same as in my first post.
--
Wake on LAN (WOL) not working with r8169 driver on Gutsy
https://bugs.launchpad.net/bugs/160413
You received this bug notification because you are a member of Ubuntu
Bugs, which is
For me WOL magically started working - I tried a couple of times during the
last few days. The weird thing is that I am still running Intrepid on the
machine, i.e.:
Linux andromeda 2.6.27-11-generic #1 SMP Wed Apr 1 20:53:41 UTC 2009 x86_64
GNU/Linux
The only thing I changed kernel-wise
This bug was reported a while ago but there hasn't been any recent
comments or updates. Is this still an issue with the latest pre-release
of Jaunty 9.04? Refer to http://www.ubuntu.com/testing/jaunty/beta .
Please let us know.
** Changed in: linux (Ubuntu)
Status: Triaged = Incomplete
Pierre-Yves, this bug disappeared during Hardy development, since august
with first Network Manager 0.7 upload on Intrepid, WOL stopped working.
NM 0.7 seems to ignore network system settings.
--
Wake on LAN (WOL) not working with r8169 driver on Gutsy
https://bugs.launchpad.net/bugs/160413
You
I have quickly tested the Kubuntu Intrepid Alpha, and the problem still exist.
As mentioned in the kernel bug report (
http://bugzilla.kernel.org/show_bug.cgi?id=9512 ) the issue is related to
Network Manager that stops the interface before shutdown (it shouldn't be a
problem normally). The
Just tested the r8168-8.008.00 module from Realtek and WOL doesn't work as long
as NetworkManager is used (I tested that if NM is removed WOL just works
normally).
So, the issue still remains.
--
Wake on LAN (WOL) not working with r8169 driver on Gutsy
https://bugs.launchpad.net/bugs/160413
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
http://www.linuxquestions.org/questions/linux-
networking-3/realtek-813981688169-on-2.6.21.3-or-newer-593495/
speaks of a setting in Windows XP which prevents same from leaving the
NIC in a state from which the linux drivers cannot recover.
That all said I am suspicious of network-manager given
kernel bug for this: http://bugzilla.kernel.org/show_bug.cgi?id=9512
--
Wake on LAN (WOL) not working with r8169 driver on Gutsy
https://bugs.launchpad.net/bugs/160413
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
On 09/03/08 at 11:27 -, John Cass wrote:
(note: my system uses a PCI 8139 type ethernet card)
I think that 8139 is a different NIC, and you might use a different
driver. Are you sure that you are using r8169?
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
|
Lucas
I am indeed using a 8139 type nic, not a 8169 - sorry for any confusion.
John
--
Wake on LAN (WOL) not working with r8169 driver on Gutsy
https://bugs.launchpad.net/bugs/160413
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Confusingly, my system now DOES work with WOL - using Ubuntu Gutsy standard
kernel 2.6.22-14
I dont know what has changed...
The system does turn off the light on the ethernet card but it does respond to
magic packets.
If I find out what changed I will add a comment.
Regards
John
(note: my
Hi,
I tried both the new kernel revision and the network init script hack
and ... no luck for me. Again, I checked right after each attempt that a
shutdown after a Win XP boot re-enables WOL.
Pierre-Yves
--
Wake on LAN (WOL) not working with r8169 driver on Gutsy
It seems that the problem is that shutting down the NIC during shutdown
disables WOL.
If I shutdown using poweroff -f, WOL works fine. (Warning: poweroff -f
doesn't go through the normal shutdown procedure, and might cause data
loss)
Running 2.6.24 from Debian. Can someone double-check using
Another way to double-check that is to edit /etc/init.d/networking, look for:
stop)
if sed -n 's/^[^ ]* \([^ ]*\) \([^ ]*\) .*$/\2/p' /proc/mounts |
grep -qE '^(nfs[1234]?|smbfs|ncp|ncpfs|coda|cifs)$'; then
log_warning_msg not deconfiguring network interfaces:
Hmmm.
Tried booting from the latest (alpha 5) heron xubuntu live cd, got
thrown into ash in initramfs ;-(
Also tried booting from my previous edgy installation - in which wol
worked for over a year - and now wol fails there too..
something in the bios changed by installing gutsy? i dont
Just found this (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/181561),
which could solve my CD boot problem, I'll try again tonight...
John
--
Wake on LAN (WOL) not working with r8169 driver on Gutsy
https://bugs.launchpad.net/bugs/160413
You received this bug notification because you
Hi Richard
Did you update just the kernel from Heron to Gutsy, or did you do a
'full update'? I tried just upgrading just the kernel (using this
procedure: http://ubuntuforums.org/showthread.php?t=646755) and it is
still NOT working for me. Could you let us know exactly what you have
done so I
Hello,
I used Hardy, I didn't try Hardy kernel on Gutsy. This bug don't seem
depend on kernel.
Regards.
Richard
--
Wake on LAN (WOL) not working with r8169 driver on Gutsy
https://bugs.launchpad.net/bugs/160413
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hello,
I'm currently on vacation, I hope to test the latetst kernel release
this week end.
Regards
Pierre-Yves
--
Wake on LAN (WOL) not working with r8169 driver on Gutsy
https://bugs.launchpad.net/bugs/160413
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hello,
Works fine on Hardy with kernel-image-2.6.24-11-generic. Tested with wakeonlan
and wol binaries from openwrt on gateway and from mac os x.
I didn't change anything, just follow Hardy updates.
Pierre-yves could you try with Hardy on host ?
Regards.
Richard
--
Wake on LAN (WOL) not
Hello
I wonder if there has been any progress on this?
I would like to report that since upgrading to Gutsy (from Edgy) - without
changing the hardware at all - WOL has stopped working : it used to work
perfectly.
My card is an 8139 type ethernet card. I set it correctly with ethtool but
** Changed in: linux
Status: Unknown = In Progress
--
Wake on LAN (WOL) not working with r8169 driver on Gutsy
https://bugs.launchpad.net/bugs/160413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=9512
Importance: Unknown
Status: Unknown
--
Wake on LAN (WOL) not working with r8169 driver on Gutsy
https://bugs.launchpad.net/bugs/160413
You received this bug notification because you are a member of Ubuntu
I'm not sure it's a kernel bug. I tried latest vanilla kernel and Ubuntu Hardy,
I got the same issue with wake on lan.
If I stopped computer with halt command (no call to init 6 or 0), then wol from
another computer works fine.
--
Wake on LAN (WOL) not working with r8169 driver on Gutsy
hello Richard,
I just tried to shutdown my box using the halt command under Ubuntu
Hardy : WOL is still not working on my box (I also verified that after a
boot/shutdown with Win XP WOL is always OK). Did you use special options
?
Regards
PY
--
Wake on LAN (WOL) not working with r8169 driver
hi Pierre-Yves,
I have tried halt command few weeks ago, i forgot something, i can't get wol
working now.
Perhaps I've started a Windows before booting Ubuntu.
Thanks for the bug report
http://bugzilla.kernel.org/show_bug.cgi?id=9512, I just subscribed to
it.
--
Wake on LAN (WOL) not working
Hello Richard,
On my side, booting linux after windows does not change anything :
- Shutting down from windows : works whatever the OS I ran before
- Shutting down from linux : does not work whatever the OS I ran before
Anyway, I feel less alone !
--
Wake on LAN (WOL) not working with r8169
The Hardy Heron kernel was recently uploaded for testing. We'd really
appreciate it if you could try testing with this newer kernel and verify
if this issue still exists. Unfortunately, the Hardy Heron Alpha1
LiveCD was released with the older 2.6.22 kernel. You'll have to
manually install the
Hi,
I have just tested the 2.6.24-1-generic kernel and there is no
difference with 2.6.22 (I have also checked that it is still working
after a windows XP shutdown). With this new kernel boot process is not
complete since I guess my nvidia modules does not match the new kernel
but I could check
Well there are maybe a few options you could do to get this noticed by
upstream:
1) Open a bug report at bugzilla.kernel.org regarding this issue. Afterwards,
we can then easily link this launchpad bug report to the upstream kernel
bugzilla bug report you created.
2) You could attempt to
36 matches
Mail list logo
