Comment 4 for bug 26266

Making the assumption that the 6.06.1 LiveCD actually runs Dapper as its kernel, (*) this bug is still present. I booted from that CD, shut down, and verified that sending WOL packets to the machine does not wake it up. (I did not do the entire boot-to-BIOS-and-shut-down stuff I did when first reporting this, but the machine configuration hasn't changed; if someone would like me to be extra-paranoid about the control case, I can do that, but not until several days from now. I -did- verify that sending WOL packets to a known-working machine did work, so I think this bug is still here.)

[This is unfortunately becoming a critical issue for me, because the machine of mine where WOL worked (a VIA chipset) is being retired because that very chipset has proven to be unreliable when doing heavy multidisk I/O, and will be replaced by one of the machines in my report above for which WOL has never worked for me in Breezy.]

(*) (I just tested it this afternoon, but stupidly didn't actually type uname at a shell while I was running from the LiveCD, and none of my machines will be in a state where I can reboot to verify that for several days---but I'd be really surprised if the LiveCD ran a significantly different kernel than what the LiveCD installs. If it -does-, and you need me to actually install Dapper to retest this bug, let me know and I'll scrounge up a spare disk to do the installation---I'm not quite ready to install Dapper for real on any of the affected machines yet.)

Also---I'm not sure what "add a linux-source-2.6.15 target to this bug" means. Exactly where in the bugtracker UI am I supposed to do this? By clicking on "Edit Description/Tags" in the upper left and adding it as a tag? Somewhere else?