Re: Wake on lan with RTL8111/8168B
On Monday 11 February 2013 06:27:57 assir...@nonada.if.usp.br wrote: > I have an ASUS P8Z77-M motherboard with an onboard RTL8111/8168B network > card. I want to enable wake on lan for this card. Wake on lan itself is > workg when I call > > wakeonlan > > from another machine, but when I shutdown the computer, the system powers > down and about 5 seconds later it powers up again without any sending of > magic packets. The effective result is therefore a reboot and not the > wished power down. > > I wonder if anyone had the same problem? Is this EFI BIOS? I experience a similar issue on a Gigabyte GA-Z68X-UD3H-B3 (rev 1.0) motherboard which has a RTL8168E network card (lspci reports the wrong name for vendor:device 10ec:8168 rev 06). I contacted Gigabyte using http://ggts.gigabyte.com/, but they have asked me to try to reproduce this on Windows. I do not have such an installation laying around for this machine, so that will be slightly more difficult to test. My request for BIOS source code was also denied due to "the rule of firma". What I have tried: - Clear the PM_Status bit to stop asserting a wake-up: sudo setpci -v -s 06:00.0 CAP_PM+5.B=80 - Disabling wake-on-lan with `sudo ethtool -s eth0 wol d`. On the Ubuntu 3.5.0-34-generic kernel, the flag gets set to "d", but on resume it becomes the default "g" again. IIRC, on Arch Linux with Linux 3.9.6-1, WOL stays disabled, but then enabling it again did not work (MagicPacket did not trigger a wake- up). NOTE: as you experienced, a machine woken with WOL will restart on shutdown. I experience the same behavior with suspend. That is, if a machine was woken with WOL, after suspend it takes a few seconds before it decides to resume again without any interaction. NOTE2: WOL worked fine on older non-EFI AWARD BIOS versions, F12 and older. The EFI BIOSes version U1h and U1l both have this WOL issue. Downgrading to AWARD BIOS resolves the problem (but then I miss certain newer features). Can you reproduce this WOL issue on other non-Linux OSes? (where WOL is functioning of course) Please mention BIOS version as well. Regards, Peter PS. let me know if you need Realtek datasheets. > I am running Wheezy. The problem occours with kernels 3.2, 3.7 (from > experimental) and vanilla 3.8-rc6, both with the native r8169 and Realtek > provided r8168. I also tried to call > > ethtool -s eth0 wol g > > and / or > > > pci-config -B 3 -# 1 -S > (as described in http://lists.debian.org/debian-user/2012/01/msg00241.html) > > before every shutdown. I also tried combinations > > ethtool -s eth0 wol ug > ethtool -s eth0 wol mg > ethtool -s eth0 wol bg > ethtool -s eth0 wol mug etc > > as described in wiki.archlinux.org/index.php/Wake-on-LAN, with no > improvement. > > Any hint will be greatly appreciated! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/10503989.IAAQ7pyvH5@al
Re: wake on lan: power on, no boot
On Apr 18, 2013 21:28, "Soare Catalin" wrote: On Apr 18, 2013 10:14 AM, "Freddie" wrote: Hi Debian users, I asked this question to the debian-laptop list a few weeks ago but there's been no solution found. As I'm not convinced my issues are laptop specific I thought I'd open it up to the wider group. I'm wanting to wake my philips freeline X10 laptop (circa 2004) using wol. I've enabled power on from PCI in the bios, and I've used ethtool and /etc/network/interfaces to ensure that wake on magic packet is enabled for eth0 on every boot. I can confirm this with # ethtool eth0 (the laptop is connect to the router by an ethernet cable). After powering off the laptop if I send a magic packet using # wakeonlan -i The laptop powers on (that is, the power led turns on and the DVD drive spins up a couple of times) but nothing boots. I'm left with a blank screen - there're no POST or BIOS screens. It might also be relevant that a usb peripheral (a sound card, in this case) doesn't power on even though it would normally power on at around the same time as the DVD drive spinning up during a normal (non-wol) boot. Does anyone have any ideas what this might be? I'm stumped. Thanks in advance. Freddie Hi Freddie Sorry for the late reply! I'm not subscribed to debian-user and so didn't see this email until now. I really should remember to check the list after I post. Whoops! I can't say I have done what you are trying to do, I have only done it with desktops. Anyway, to me, how you describe it, your laptop doesn't fully start/boot. I don't want to offend you (in case you have checked already) but I'd check the manufacturer's website for this symptom, and eventually check for (BIOS) firmware upgrades and their changelogs. I think you're correct - the laptop doesn't seem to start properly. You don't offend at all, but I had looked for a newer BIOS than the one I have. Unfortunately I can't seem to find anything for this laptop - it is gettin on a bit now! Thanks for you suggestion. I'll keep looking for a BIOS update. Any other ideas? Good luck! -- Sent from my Brick (TM) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.DEB.2.02.1304270012060.3531@music.f_and_s
Re: wake on lan: power on, no boot
On Apr 18, 2013 10:14 AM, "Freddie" wrote: > > Hi Debian users, > > I asked this question to the debian-laptop list a few weeks ago but there's been no solution found. As I'm not convinced my issues are laptop specific I thought I'd open it up to the wider group. > > I'm wanting to wake my philips freeline X10 laptop (circa 2004) using wol. > > I've enabled power on from PCI in the bios, and I've used ethtool and /etc/network/interfaces to ensure that wake on magic packet is enabled for eth0 on every boot. I can confirm this with > # ethtool eth0 > (the laptop is connect to the router by an ethernet cable). > > After powering off the laptop if I send a magic packet using > # wakeonlan -i > The laptop powers on (that is, the power led turns on and the DVD drive spins up a couple of times) but nothing boots. I'm left with a blank screen - there're no POST or BIOS screens. > > It might also be relevant that a usb peripheral (a sound card, in this case) doesn't power on even though it would normally power on at around the same time as the DVD drive spinning up during a normal (non-wol) boot. > > Does anyone have any ideas what this might be? I'm stumped. > > Thanks in advance. > > Freddie > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/alpine.DEB.2.02.1304180751001.3238@eeepc.Belkin > Hi Freddie I can't say I have done what you are trying to do, I have only done it with desktops. Anyway, to me, how you describe it, your laptop doesn't fully start/boot. I don't want to offend you (in case you have checked already) but I'd check the manufacturer's website for this symptom, and eventually check for (BIOS) firmware upgrades and their changelogs. Good luck! -- Sent from my Brick (TM)
wake on lan: power on, no boot
Hi Debian users, I asked this question to the debian-laptop list a few weeks ago but there's been no solution found. As I'm not convinced my issues are laptop specific I thought I'd open it up to the wider group. I'm wanting to wake my philips freeline X10 laptop (circa 2004) using wol. I've enabled power on from PCI in the bios, and I've used ethtool and /etc/network/interfaces to ensure that wake on magic packet is enabled for eth0 on every boot. I can confirm this with # ethtool eth0 (the laptop is connect to the router by an ethernet cable). After powering off the laptop if I send a magic packet using # wakeonlan -i The laptop powers on (that is, the power led turns on and the DVD drive spins up a couple of times) but nothing boots. I'm left with a blank screen - there're no POST or BIOS screens. It might also be relevant that a usb peripheral (a sound card, in this case) doesn't power on even though it would normally power on at around the same time as the DVD drive spinning up during a normal (non-wol) boot. Does anyone have any ideas what this might be? I'm stumped. Thanks in advance. Freddie -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.DEB.2.02.1304180751001.3238@eeepc.Belkin
Re: Wake on lan with RTL8111/8168B
Did you ever get this to work? I have the same problem. It seems like every second time I start my computer with WOL it reboots when a issue a poweroff. -- View this message in context: http://debian.2.n7.nabble.com/Wake-on-lan-with-RTL8111-8168B-tp2867498p2878147.html Sent from the Debian User mailing list archive at Nabble.com. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1361884883737-2878147.p...@n7.nabble.com
Re: Wake on lan with RTL8111/8168B
> And, how do you connect to that distant computer? SSH, I guess? > If I had the same problem, I would check that the correct profile > (environment variables, rights, such kind of things) related to poweroff > is loaded, since I think ssh does not provide all environment variables to > connected users. All my tests until now were done with local shells. I assure it is not such a problem. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130211162018.ca6cc...@nonada.if.usp.br
Re: Wake on lan with RTL8111/8168B
>> Le Lun 11 février 2013 9:27, assir...@nonada.if.usp.br a écrit : >>> Hello, >>> >>> >>> I have an ASUS P8Z77-M motherboard with an onboard RTL8111/8168B >>> network >>> card. I want to enable wake on lan for this card. Wake on lan itself is >>> workg when I call >>> >>> wakeonlan >>> >>> from another machine, but when I shutdown the computer, the system >>> powers >>> down and about 5 seconds later it powers up again without any sending >>> of >>> magic packets. The effective result is therefore a reboot and not the >>> wished power down. >>> >>> I wonder if anyone had the same problem? >> >> I think your problem is not related to the wake on lan, since you >> correctly start the needed computer with WoL. >> Your problem here is to shutdown, and not reboot. >> >> So, how do you shut it down? >> >> > > Sorry for not including this in the description. I tried the following > ways to shut down. > > shutdown -h now > shutdown -hP now > poweroff > telinit 0 > > both from runlevel 2 and single. All of them gave the same results. Also, the problem must be related to WOL somehow, because it restarts only if it was turned on by WOL. If I turn it on by the power button, it shuts down normally. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/f95ae38bd6bae08301fce900d8e5b7a2.squir...@nonada.if.usp.br
Re: Wake on lan with RTL8111/8168B
Le Lun 11 février 2013 10:29, assir...@nonada.if.usp.br a écrit : >>> Le Lun 11 février 2013 9:27, assir...@nonada.if.usp.br a écrit : >>> >>>> Hello, >>>> >>>> >>>> >>>> I have an ASUS P8Z77-M motherboard with an onboard RTL8111/8168B >>>> network card. I want to enable wake on lan for this card. Wake on lan >>>> itself is workg when I call >>>> >>>> wakeonlan >>>> >>>> from another machine, but when I shutdown the computer, the system >>>> powers down and about 5 seconds later it powers up again without any >>>> sending of magic packets. The effective result is therefore a reboot >>>> and not the wished power down. >>>> >>>> I wonder if anyone had the same problem? >>>> >>> >>> I think your problem is not related to the wake on lan, since you >>> correctly start the needed computer with WoL. Your problem here is to >>> shutdown, and not reboot. >>> >>> So, how do you shut it down? >>> >>> >>> >> >> Sorry for not including this in the description. I tried the following >> ways to shut down. >> >> shutdown -h now shutdown -hP now poweroff telinit 0 >> >> both from runlevel 2 and single. All of them gave the same results. > > Also, the problem must be related to WOL somehow, because it restarts > only if it was turned on by WOL. If I turn it on by the power button, it > shuts down normally. > > And, how do you connect to that distant computer? SSH, I guess? If I had the same problem, I would check that the correct profile (environment variables, rights, such kind of things) related to poweroff is loaded, since I think ssh does not provide all environment variables to connected users. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8be41b751703713d1fb5980f6050ab4b.squir...@www.sud-ouest.org
Re: Wake on lan with RTL8111/8168B
> Le Lun 11 février 2013 9:27, assir...@nonada.if.usp.br a écrit : >> Hello, >> >> >> I have an ASUS P8Z77-M motherboard with an onboard RTL8111/8168B network >> card. I want to enable wake on lan for this card. Wake on lan itself is >> workg when I call >> >> wakeonlan >> >> from another machine, but when I shutdown the computer, the system >> powers >> down and about 5 seconds later it powers up again without any sending >> of >> magic packets. The effective result is therefore a reboot and not the >> wished power down. >> >> I wonder if anyone had the same problem? > > I think your problem is not related to the wake on lan, since you > correctly start the needed computer with WoL. > Your problem here is to shutdown, and not reboot. > > So, how do you shut it down? > > Sorry for not including this in the description. I tried the following ways to shut down. shutdown -h now shutdown -hP now poweroff telinit 0 both from runlevel 2 and single. All of them gave the same results. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/520216b5a4a498671d9c1e973c0898fe.squir...@nonada.if.usp.br
Re: Wake on lan with RTL8111/8168B
Le Lun 11 février 2013 9:27, assir...@nonada.if.usp.br a écrit : > Hello, > > > I have an ASUS P8Z77-M motherboard with an onboard RTL8111/8168B network > card. I want to enable wake on lan for this card. Wake on lan itself is > workg when I call > > wakeonlan > > from another machine, but when I shutdown the computer, the system powers > down and about 5 seconds later it powers up again without any sending of > magic packets. The effective result is therefore a reboot and not the > wished power down. > > I wonder if anyone had the same problem? I think your problem is not related to the wake on lan, since you correctly start the needed computer with WoL. Your problem here is to shutdown, and not reboot. So, how do you shut it down? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/9ba6c431d34ad2075c24d6766ab71eed.squir...@www.sud-ouest.org
Wake on lan with RTL8111/8168B
Hello, I have an ASUS P8Z77-M motherboard with an onboard RTL8111/8168B network card. I want to enable wake on lan for this card. Wake on lan itself is workg when I call wakeonlan from another machine, but when I shutdown the computer, the system powers down and about 5 seconds later it powers up again without any sending of magic packets. The effective result is therefore a reboot and not the wished power down. I wonder if anyone had the same problem? I am running Wheezy. The problem occours with kernels 3.2, 3.7 (from experimental) and vanilla 3.8-rc6, both with the native r8169 and Realtek provided r8168. I also tried to call ethtool -s eth0 wol g and / or pci-config -B 3 -# 1 -S (as described in http://lists.debian.org/debian-user/2012/01/msg00241.html) before every shutdown. I also tried combinations ethtool -s eth0 wol ug ethtool -s eth0 wol mg ethtool -s eth0 wol bg ethtool -s eth0 wol mug etc as described in wiki.archlinux.org/index.php/Wake-on-LAN, with no improvement. Any hint will be greatly appreciated! Regards, Joao Luis. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2d1cb5d39499065c9c62fe205c0d30ee.squir...@nonada.if.usp.br
Re: [SOLVED] RTL8111/8168B wake on lan (WOL) working randomly
2012/1/3 Janek Lapka : > Juan Sierra Pons writes: > >>lspci -v >> >>02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > ^^ The 2 digit at the beginning of the line means the pci bus > > > > More info: > http://www.thinkwiki.org/wiki/WakeOnLAN > or google: pci-config wol > >> The problem is that when I shutdown the computer the NIC is switched >> off too. I can see it as the port in my home ADSL router is switched >> off. BUT randomly I can see that the NIC is not switched off after a >> shutdown and if I send the WOL packet from another computer it works >> like a charm. > > Use pci-config (apt-get install nictools-pci) to put the nic into > sleep mode > > (part of my /etc/network/interfaces) > # pci-config -B 4 -#1 > # gigabyte p35c-ds3r pci bus ^ ^ device number > # The primary network interface > allow-hotplug eth0 > iface eth0 inet static > address 192.168.1.2 > netmask 255.255.255.0 > network 192.168.1.0 > broadcast 192.168.1.255 > gateway 192.168.1.1 > # wol gigabyte p35c-ds3r (on asus p5b I don't need this) > #pre-up pci-config -W -B 4 -#1 # I don't use > #pre-up pci-config -B 4 -#1 # I don't use > pre-down pci-config -S -B 4 -#1 # Put device to sleep (ACPI D3) > pre-down pci-config -B 4 -#1 # Show the current status > > > > Also, if you share the drive with MS-Windows it may change the status of > the driver. > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/87wr99pldc@ibmx60t.lan > Hi all, Finally Janek pointed me in the right direction: nictools-pci package and the pci-config command I tried the pre-down directive in the /etc/network/interfaces and it worked ok but the second or third time I rebooted my PC it got frozen so I started to search the internet and I found a web [1] explaining how to use the pci-config I've make it work using the following procedure: lspci -nn |grep -i Ether 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 01) ^^ The 2 digit at the beginning of the line means the pci bus (As explained by Janek) ^ ^ this is the vendor:model number Then: pci-config -B 2 pci-config.c:v2.05 2/23/2005 Donald Becker (bec...@scyld.com) http://www.scyld.com/diag/index.html Device #1 at bus 2 device/function 0/0, 816810ec. ^-^ this is tne model:vendor number the same as before BUT in different order Now I know the BUS number (2) and device number (#1) So I can use the pci-config to put the NIC in the proper state for WOL: pci-config -B 2 -# 1 -S Instead of using the pre-down directive in the /etc/network/interfaces I choose the /etc/init.d/halt script as written in [1] and added the following lines just before "halt -d -f $netdown $poweroff $hddown" [...] ### http://lists.debian.org/debian-user/2012/01/msg00182.html ### http://ubuntuforums.org/archive/index.php/t-951563.html rmmod r8168 sleep 0.5 modprobe r8168 sleep 0.5 pci-config -B 2 -# 1 -S sleep 0.5 log_action_msg "Will now halt" halt -d -f $netdown $poweroff $hddown [...] I have restarted my PC at least 10 times and it works without problem. [1] http://ubuntuforums.org/archive/index.php/t-951563.html Thank you guys for your time!! Best regards -- Juan Sierra Pons j...@elsotanillo.net Linux User Registered: #257202 http://www.elsotanillo.net GPG key = 0xA110F4FE Key Fingerprint = DF53 7415 0936 244E 9B00 6E66 E934 3406 A110 F4FE -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CABS=y9v=7u21xq6me4asonare7uyaa14t6ukg2fekv7uyj-...@mail.gmail.com
Re: RTL8111/8168B wake on lan (WOL) working randomly
On Sun, 01 Jan 2012 21:01:33 +0100, Juan Sierra Pons wrote: > I have been spending many days trying to make my computer start using > the with wake on lan (WOL) feature. (...) > The problem is that when I shutdown the computer the NIC is switched off > too. I can see it as the port in my home ADSL router is switched off. > BUT randomly I can see that the NIC is not switched off after a shutdown > and if I send the WOL packet from another computer it works like a > charm. (...) Okay, so the fact your system powers off the ethernet adapter "randomly" is the key of the problem. This should not happen. As the network interface comes integrated within the motherboard, I would look for a BIOS update and check if it solves someting related to power management or WOL (hint: most of the manufacturers do not write down the full BIOS release changelogs unless you directly contact them, so it's a good idea to ask the motherboard's manufacturer directly and query about this). A bad PSU, "too smart" UPS unit (or a power surge strip) can be also making noise here... Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2012.01.03.15.59...@gmail.com
Re: RTL8111/8168B wake on lan (WOL) working randomly
Juan Sierra Pons writes: >lspci -v > >02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. ^^ The 2 digit at the beginning of the line means the pci bus More info: http://www.thinkwiki.org/wiki/WakeOnLAN or google: pci-config wol > The problem is that when I shutdown the computer the NIC is switched > off too. I can see it as the port in my home ADSL router is switched > off. BUT randomly I can see that the NIC is not switched off after a > shutdown and if I send the WOL packet from another computer it works > like a charm. Use pci-config (apt-get install nictools-pci) to put the nic into sleep mode (part of my /etc/network/interfaces) # pci-config -B 4 -#1 # gigabyte p35c-ds3r pci bus ^ ^ device number # The primary network interface allow-hotplug eth0 iface eth0 inet static address 192.168.1.2 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.1 # wol gigabyte p35c-ds3r (on asus p5b I don't need this) #pre-up pci-config -W -B 4 -#1 # I don't use #pre-up pci-config -B 4 -#1 # I don't use pre-down pci-config -S -B 4 -#1 # Put device to sleep (ACPI D3) pre-down pci-config -B 4 -#1 # Show the current status Also, if you share the drive with MS-Windows it may change the status of the driver. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87wr99pldc@ibmx60t.lan
Re: RTL8111/8168B wake on lan (WOL) working randomly
On 02/01/12 07:01, Juan Sierra Pons wrote: > Dear all, > > I have been spending many days trying to make my computer start using > the with wake on lan (WOL) feature. > > My PC has a "Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)" > integrated NIC > > lspci -v > > 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01) > Subsystem: ASUSTeK Computer Inc. P5B > Flags: bus master, fast devsel, latency 0, IRQ 41 > I/O ports at dc00 [size=256] > Memory at fdfff000 (64-bit, non-prefetchable) [size=4K] > [virtual] Expansion ROM at fdd0 [disabled] [size=128K] > Capabilities: [40] Power Management version 2 > Capabilities: [48] Vital Product Data > Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+ > Capabilities: [60] Express Endpoint, MSI 00 > Capabilities: [84] Vendor Specific Information: Len=4c > Capabilities: [100] Advanced Error Reporting > Capabilities: [12c] Virtual Channel > Capabilities: [148] Device Serial Number 1a-00-00-00-10-ec-81-68 > Capabilities: [154] Power Budgeting > Kernel driver in use: r8168 > > I have found on many mailing lists, forums that it is necessary the > r8168 module to make it works as by default Debian wheezy uses the > r8169 so I have installed the newest r8168 module from > http://code.google.com/p/r8168/ > > For example: > http://djlab.com/2010/10/fixing-rtl8111-8168b-driver-debian-ubuntu/comment-page-1/ > > The problem is that when I shutdown the computer the NIC is switched > off too. I can see it as the port in my home ADSL router is switched > off. BUT randomly I can see that the NIC is not switched off after a > shutdown and if I send the WOL packet from another computer it works > like a charm. > > I have already checked the following: > > * My computer uses the right module as i have blacklisted the r8169: > > more /etc/modprobe.d/blacklist-network.conf > blacklist r8169 > > * I am using the last module version: > > ethtool -i eth0 > driver: r8168 > version: 8.027.00-NAPI > firmware-version: > bus-info: :02:00.0 > supports-statistics: yes > supports-test: no > supports-eeprom-access: yes > supports-register-dump: yes > > * NIC has the WOL feature enabled (Wake-on: g) > > root@mediacenter:/etc# ethtool eth0 > > Settings for eth0: > Supported ports: [ TP ] > Supported link modes: 10baseT/Half 10baseT/Full > 100baseT/Half 100baseT/Full > 1000baseT/Full > Supported pause frame use: No > Supports auto-negotiation: Yes > Advertised link modes: 10baseT/Half 10baseT/Full > 100baseT/Half 100baseT/Full > 1000baseT/Full > Advertised pause frame use: No > Advertised auto-negotiation: Yes > Speed: 100Mb/s > Duplex: Full > Port: Twisted Pair > PHYAD: 0 > Transceiver: internal > Auto-negotiation: on > MDI-X: Unknown > Supports Wake-on: pumbg > Wake-on: g > Current message level: 0x0033 (51) > drv probe ifdown ifup > Link detected: yes > > * I have already modified the /etc/init.d/halt script with NETDOWN=no > to do not switch off the NIC > [] > NETDOWN=no > [] > # Make it possible to not shut down network interfaces, > # needed to use wake-on-lan > netdown="-i" > if [ "$NETDOWN" = "no" ]; then > netdown="" > fi > [] > > I can not see any pattern as it works around 10-20% of the times I > shutdown the computer locally, remotely or from the poweroff button. > > Thanks a log for your time. > > Best regards > > Juan Sierra Pons > > -- > Juan Sierra Pons j...@elsotanillo.net > Linux User Registered: #257202 http://www.elsotanillo.net > GPG key = 0xA110F4FE > Key Fingerprint = DF53 7415 0936 244E 9B00 6E66 E934 3406 A110 F4FE > -- > > You might try the tip suggested in:- http://lists.debian.org/debian-user/2011/12/msg01704.html Thank you for supplying all that info - I'm only familiar with one WOL tool (wakeonl
RTL8111/8168B wake on lan (WOL) working randomly
Dear all, I have been spending many days trying to make my computer start using the with wake on lan (WOL) feature. My PC has a "Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)" integrated NIC lspci -v 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01) Subsystem: ASUSTeK Computer Inc. P5B Flags: bus master, fast devsel, latency 0, IRQ 41 I/O ports at dc00 [size=256] Memory at fdfff000 (64-bit, non-prefetchable) [size=4K] [virtual] Expansion ROM at fdd0 [disabled] [size=128K] Capabilities: [40] Power Management version 2 Capabilities: [48] Vital Product Data Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+ Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [84] Vendor Specific Information: Len=4c Capabilities: [100] Advanced Error Reporting Capabilities: [12c] Virtual Channel Capabilities: [148] Device Serial Number 1a-00-00-00-10-ec-81-68 Capabilities: [154] Power Budgeting Kernel driver in use: r8168 I have found on many mailing lists, forums that it is necessary the r8168 module to make it works as by default Debian wheezy uses the r8169 so I have installed the newest r8168 module from http://code.google.com/p/r8168/ For example: http://djlab.com/2010/10/fixing-rtl8111-8168b-driver-debian-ubuntu/comment-page-1/ The problem is that when I shutdown the computer the NIC is switched off too. I can see it as the port in my home ADSL router is switched off. BUT randomly I can see that the NIC is not switched off after a shutdown and if I send the WOL packet from another computer it works like a charm. I have already checked the following: * My computer uses the right module as i have blacklisted the r8169: more /etc/modprobe.d/blacklist-network.conf blacklist r8169 * I am using the last module version: ethtool -i eth0 driver: r8168 version: 8.027.00-NAPI firmware-version: bus-info: :02:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: yes supports-register-dump: yes * NIC has the WOL feature enabled (Wake-on: g) root@mediacenter:/etc# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: pumbg Wake-on: g Current message level: 0x0033 (51) drv probe ifdown ifup Link detected: yes * I have already modified the /etc/init.d/halt script with NETDOWN=no to do not switch off the NIC [] NETDOWN=no [] # Make it possible to not shut down network interfaces, # needed to use wake-on-lan netdown="-i" if [ "$NETDOWN" = "no" ]; then netdown="" fi [] I can not see any pattern as it works around 10-20% of the times I shutdown the computer locally, remotely or from the poweroff button. Thanks a log for your time. Best regards Juan Sierra Pons -- Juan Sierra Pons j...@elsotanillo.net Linux User Registered: #257202 http://www.elsotanillo.net GPG key = 0xA110F4FE Key Fingerprint = DF53 7415 0936 244E 9B00 6E66 E934 3406 A110 F4FE -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CABS=y9sagc4mwwtozg+ywj2wzvczyizhsks0oozpjk8opej...@mail.gmail.com
Re: Wake on lan, etc
On 30/12/11 05:41, T o n g wrote: Hi, Does Linux support wake on lan? My friend told me, in windows, you can send some magic packages over internet to wake up box that is even in sleep mode. The same tool can tell the box to reboot as well. Is such beast exist in Linux world as well? As others have said, it is supported as long as your hardware supports WOL. I use it on some of my systems, using wakeonlan. For some hardware, I found that the "Wake On MagicPacket™" flag got cleared when the interface was enabled during booting, so WOL would work the first time a machine is powered on in standby, but wouldn't work after a shutdown. I solved this by putting a post-up line in /etc/network/interfaces to reset the flag after the interface is enabled: iface eth0 inet dhcp post-up /sbin/ethtool -s eth0 wol g (that's assuming you don't use NM) -- Dom -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4efd9bb7.3040...@rpdom.net
Re: Wake on lan, etc
On 30/12/11 16:41, T o n g wrote: > Hi, > > Does Linux support wake on lan? > > My friend told me, in windows, you can send some magic packages over > internet to wake up box that is even in sleep mode. The same tool can > tell the box to reboot as well. Is such beast exist in Linux world as > well? > > Thanks > Yes - in the Debian repositories there's:- etherwake - A little tool to send magic Wake-on-LAN packets gwakeonlan - wakes up your machines using Wake on LAN wakeonlan - Sends 'magic packets' to wake-on-LAN enabled ethernet adapters I've only used the last package - it works very nicely. eg:- wakeonlan -i 192.168.0.255 00:60:b0:a4:22:f6 NOTE: some boxes require the -i broadcast address option eg. Thinkpads, other don't. Most modern laptops/mbs with built-in NICs support it, though it generally requires enabling in the BIOS. Many older mbs support it if you have the 3-wire cable and enable the BIOS setting. If anyone knows the pinouts for the 10-wire WOL cables that come with the AMD-PCNet NICs I'd appreciate knowing the 3 used for WOL (5V+, Gnd, WOL). Cheers -- Iceweasel/Firefox extensions for finding answers to Debian questions:- https://addons.mozilla.org/en-US/firefox/collections/Scott_Ferguson/debian/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4efd62c0.7010...@gmail.com
Re: Wake on lan, etc
On Friday 30 December 2011 06:41:55 T o n g wrote: > Hi, > > Does Linux support wake on lan? > > My friend told me, in windows, you can send some magic packages over > internet to wake up box that is even in sleep mode. The same tool can > tell the box to reboot as well. Is such beast exist in Linux world as > well? > > Thanks Wake on lan is not OS dependant, it is hardware dependant. See: http://en.wikipedia.org/wiki/Wake-on-LAN Thierry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201112300708.56260.tchate...@free.fr
Re: wake-on-lan
Roel Schroeven wrote: > > From the man page, it indeed looks like that should help. Unfortunately > it doesn't seem to work. I'll investigate further tomorrow. > > I do power ON/OFF my PC using this card and remote browser or cell phone if you will: https://ool-43537bf6.dyn.optonline.net/Power%20Web%20Button.htm -- View this message in context: http://www.nabble.com/wake-on-lan-tf1706584.html#a13011777 Sent from the Debian User mailing list archive at Nabble.com. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Getting wake-on-lan to work in Etch
Le Thursday 26 July 2007 14:14:57 Raj Kiran Grandhi, vous avez écrit : > On 7/26/07, Gilles Mocellin <[EMAIL PROTECTED]> wrote: > > Le Wednesday 25 July 2007 01:46:03 Raj Kiran Grandhi, vous avez écrit: > > > Hi, > > > > > > I am trying to get "wake on lan" to work in Etch. I have a motherboard > > > with an onboard NIC which supports wake-on-lan. I have enabled > > > wake-on-lan in the bios. When I poweroff the computer during POST, I am > > > able to remotely wake it, but if I shut it down from Etch, power to the > > > NIC is also being turned off and wake-on-lan does not work. I have > > > edited '/etc/init.d/halt' and removed the '-i' option from the 'halt' > > > command, but the NIC is still being powered down. > > > > Try to add this line in your /etc/network/interfaces : > > post-down ethtool -s eth0 wol g > > > > It tells your nic to prepare to be woken up, so perhaps it will not power > > off. > > > > Install ethtool if you don't have it. > > ethtool did the trick! Thanks a lot. Only, I had to add that line as a > script in the /etc/network/if-up.d directory. It's OK, I just thought it was more suitable to set wol for the card on network stop, not start. But I was perhaps wrong about the post-down, perhaps a bit too late. If it work at start, let's go. Personnaly, I prefer to add a "up" line in my /etc/network/interfaces instead of create a script in /etc/network/if-up.d. That Way I know wich interface is up. signature.asc Description: This is a digitally signed message part.
Re: Getting wake-on-lan to work in Etch
* Raj Kiran Grandhi (2007-07-26): >> > I am trying to get "wake on lan" to work in Etch. I have a motherboard >> > with an onboard NIC which supports wake-on-lan. I have enabled >> > wake-on-lan in the bios. When I poweroff the computer during POST, I am >> > able to remotely wake it, but if I shut it down from Etch, power to the >> > NIC is also being turned off and wake-on-lan does not work. I have >> > edited '/etc/init.d/halt' and removed the '-i' option from the 'halt' >> > command, but the NIC is still being powered down. >> >> Try to add this line in your /etc/network/interfaces : >> post-down ethtool -s eth0 wol g >> >> It tells your nic to prepare to be woken up, so perhaps it will not power >> off. >> >> Install ethtool if you don't have it. >> > ethtool did the trick! Thanks a lot. Only, I had to add that line as a > script in the /etc/network/if-up.d directory. It turned out to be 3d hit in google "linux wake on lan". While it's gentoo wiki, hardware<->kernel thing is the same: there's nothing interesting in bios?kernel?acpi?userspace dance. Anyway beware of acpi reboot/poweroff problems and how they are awkward. <http://mid.gmane.org/[EMAIL PROTECTED]> <http://mid.gmane.org/[EMAIL PROTECTED]> Also some drivers are not wol ready in 2.6.18: <http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=e3173832d7be8f62a181a1888a65f0a3dc58c2e0> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Getting wake-on-lan to work in Etch
On 7/26/07, Gilles Mocellin <[EMAIL PROTECTED]> wrote: > Le Wednesday 25 July 2007 01:46:03 Raj Kiran Grandhi, vous avez écrit: > > Hi, > > > > I am trying to get "wake on lan" to work in Etch. I have a motherboard > > with an onboard NIC which supports wake-on-lan. I have enabled > > wake-on-lan in the bios. When I poweroff the computer during POST, I am > > able to remotely wake it, but if I shut it down from Etch, power to the > > NIC is also being turned off and wake-on-lan does not work. I have > > edited '/etc/init.d/halt' and removed the '-i' option from the 'halt' > > command, but the NIC is still being powered down. > > Try to add this line in your /etc/network/interfaces : > post-down ethtool -s eth0 wol g > > It tells your nic to prepare to be woken up, so perhaps it will not power off. > > Install ethtool if you don't have it. > ethtool did the trick! Thanks a lot. Only, I had to add that line as a script in the /etc/network/if-up.d directory.
Re: Getting wake-on-lan to work in Etch
Le Wednesday 25 July 2007 01:46:03 Raj Kiran Grandhi, vous avez écrit : > Hi, > > I am trying to get "wake on lan" to work in Etch. I have a motherboard > with an onboard NIC which supports wake-on-lan. I have enabled > wake-on-lan in the bios. When I poweroff the computer during POST, I am > able to remotely wake it, but if I shut it down from Etch, power to the > NIC is also being turned off and wake-on-lan does not work. I have > edited '/etc/init.d/halt' and removed the '-i' option from the 'halt' > command, but the NIC is still being powered down. Try to add this line in your /etc/network/interfaces : post-down ethtool -s eth0 wol g It tells your nic to prepare to be woken up, so perhaps it will not power off. Install ethtool if you don't have it. signature.asc Description: This is a digitally signed message part.
Re: Getting wake-on-lan to work in Etch
* 24-07-2007, Raj Kiran Grandhi > I am trying to get "wake on lan" to work in Etch. I have a motherboard > with an onboard NIC which supports wake-on-lan. I have enabled > wake-on-lan in the bios. When I poweroff the computer during POST, I am > able to remotely wake it, but if I shut it down from Etch, power to the > NIC is also being turned off and wake-on-lan does not work. I have > edited '/etc/init.d/halt' and removed the '-i' option from the 'halt' > command, but the NIC is still being powered down. >From the man page it's shutdown interfaces (in networking sense). > If I boot into single user mode (init 1) and call poweroff from there, > the NIC is kept alive after the computer is powered down. Another thing > I have noticed is that when I issue the 'poweroff' from runlevel 2, the > console displays the message "acpi_poweroff called" just before > powerdown and the NIC is also powered off. This message does not appear > when issuing poweroff from runlevel 1. So, ACPI/BIOS whatever thinks that it knows better than somebody else. OTHO, maybe it's another set of bugs in that brain damaged interface, > How can I configure the system to keep the NIC alive after shutting down > from runlevel 2? Try to get rid of acpi: any acpi-related kernel modules (/lib/linux/kernel/drivers/acpi/*) or try kernel parameters (e.g. acpi=off). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Getting wake-on-lan to work in Etch
Hi, I am trying to get "wake on lan" to work in Etch. I have a motherboard with an onboard NIC which supports wake-on-lan. I have enabled wake-on-lan in the bios. When I poweroff the computer during POST, I am able to remotely wake it, but if I shut it down from Etch, power to the NIC is also being turned off and wake-on-lan does not work. I have edited '/etc/init.d/halt' and removed the '-i' option from the 'halt' command, but the NIC is still being powered down. If I boot into single user mode (init 1) and call poweroff from there, the NIC is kept alive after the computer is powered down. Another thing I have noticed is that when I issue the 'poweroff' from runlevel 2, the console displays the message "acpi_poweroff called" just before powerdown and the NIC is also powered off. This message does not appear when issuing poweroff from runlevel 1. How can I configure the system to keep the NIC alive after shutting down from runlevel 2? Thanks, Raj Kiran -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Getting wake-on-lan to work in Etch
Hi, I am trying to get "wake on lan" to work in Etch. I have a motherboard with an onboard NIC which supports wake-on-lan. I have enabled wake-on-lan in the bios. When I poweroff the computer during POST, I am able to remotely wake it, but if I shut it down from Etch, power to the NIC is also being turned off and wake-on-lan does not work. I have edited '/etc/init.d/halt' and removed the '-i' option from the 'halt' command, but the NIC is still being powered down. If I boot into single user mode (init 1) and call poweroff from there, the NIC is kept alive after the computer is powered down. Another thing I have noticed is that when I issue the 'poweroff' from runlevel 2, the console displays the message "acpi_poweroff called" just before powerdown and the NIC is also powered off. This message does not appear when issuing poweroff from runlevel 1. How can I configure the system to keep the NIC alive after shutting down from runlevel 2? Thanks, Raj Kiran -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wake-on-lan
Christian Pernegger schreef: I also checked Documentation/networking/e100.txt (I presume the card's driver is e100 since that's the only network driver related module I see in lsmod) and it says that it should work with ethtool. But it doesn't. It says the same for e1000 and that also only works with Intel's newer driver. Give it a try, chances are it will work. Nope, still no luck. On the bright side: I tried out some older kernels to see if it was a kernel update that triggered the faulty behavior. I tried 2.6.16, 2.6.12 and 2.6.8; 2.6.8 works as it should. So I'm simply going to use that one for the time being. I'll see if I can add anything useful to the bug report, once bugs.debian.org is back up. -- If I have been able to see further, it was only because I stood on the shoulders of giants. -- Isaac Newton Roel Schroeven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wake-on-lan
I also checked Documentation/networking/e100.txt (I presume the card's driver is e100 since that's the only network driver related module I see in lsmod) and it says that it should work with ethtool. But it doesn't. It says the same for e1000 and that also only works with Intel's newer driver. Give it a try, chances are it will work. C. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wake-on-lan
Christian Pernegger schreef: > [...] I can remotely wake the box if I shut it down before it boots > Linux, but it doesn't work if I shut it down when Linux is running. I had the same problem, as do many others according to Google. 1) Check if WoL is on using # ethtool eth0 There should be a 'g' in the Wake-On: line. If there is not you'll have to run It's there: Supports Wake-on: g Wake-on: g 2) The problem in my case was that the driver turned off the NIC completely during shutdown, so it lost its link to the switch (check the LEDs) and the ability to wake up. The LEDs (a green one and an orange one FWIW) are lighted when the box is powered down. I also checked Documentation/networking/e100.txt (I presume the card's driver is e100 since that's the only network driver related module I see in lsmod) and it says that it should work with ethtool. But it doesn't. I must be missing something; I'll search further tonight when I get home; I'm not going to mess around with it right now since I'm not home to power it back up manually. I filed a bug on WoL not working, please add your experience there - maybe someone in the kernel team will look at it if more people complain :) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368399 I'm not sure it is a kernel bug yet, but I will my experience once I have a better view of the problem and hopefully the solution. -- If I have been able to see further, it was only because I stood on the shoulders of giants. -- Isaac Newton Roel Schroeven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wake-on-lan
> [...] I can remotely wake the box if I shut it down before it boots > Linux, but it doesn't work if I shut it down when Linux is running. I had the same problem, as do many others according to Google. 1) Check if WoL is on using # ethtool eth0 There should be a 'g' in the Wake-On: line. If there is not you'll have to run # ethtool -s eth0 wol g every time you reboot the machine. If this does not work ... 2) The problem in my case was that the driver turned off the NIC completely during shutdown, so it lost its link to the switch (check the LEDs) and the ability to wake up. In my case (an Intel Desktop Gigabit NIC with the e1000 driver) compiling the newer GPL driver from the Intel web site out-of-tree worked nicely. (You just need the headers or full source of your kernel accessible as /usr/src/linux) Remember to update the initrd, if you use one, otherwise the old driver will be loaded on boot. (Check dmesg) I filed a bug on WoL not working, please add your experience there - maybe someone in the kernel team will look at it if more people complain :) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368399 Cheers C. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wake-on-lan
Bruno Buys schreef: The way you shut the box down isn´t supposed to have any effect on the ability to wake it up. That's what I thought, but I've tried multiple times so I'm absolutely sure that there is a difference in behaviour before and after booting Linux. To wake up the machine has to be an atx form, and be powered on, as you can figure by the lighting ethernet led, in the box´s rear. I´m guessing you have some issue with acpi. What machine is this? An acpi issue sounds plausible, but it's an area I have no experience in. I certainly can't see any problems in dmesg | grep -i acpi The machine is an MSI Hermes 845GV (http://www.msicomputer.com/product/p_spec.asp?model=Hermes_845GV_Black). $ lspci :00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 03) :00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03) :00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 02) :00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 02) :00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 02) :00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 02) :00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 82) :00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge (rev 02) :00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 02) :00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 02) :00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 02) :01:01.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05) :01:01.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05) :01:07.0 FireWire (IEEE 1394): NEC Corporation uPD72874 IEEE1394 OHCI 1.1 3-port PHY-Link Ctrlr (rev 01) :01:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (LOM) Ethernet Controller (rev 82) -- If I have been able to see further, it was only because I stood on the shoulders of giants. -- Isaac Newton Roel Schroeven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wake-on-lan
Jeronimo Pellegrini schreef: On Tue, May 30, 2006 at 08:56:24PM +0200, Roel Schroeven wrote: Now I did investigate, and this is what I found out: given that the BIOS is configured correctly, I can remotely wake the box if I shut it down before it boots Linux (it works if I shut it down while the Grub menu is visible), but it doesn't work if I shut it down when Linux is running. I tried shutting it down via poweroff, shutdown -h now and pushing the power button, but all with the same effect: no response to wake-up packets. I had a similar problem... Before shutting down, I need to run this command: # ethtool -s eth0 wol g Because after a reboot WOL is disabled. I included that line in my boot scripts. From the man page, it indeed looks like that should help. Unfortunately it doesn't seem to work. I'll investigate further tomorrow. -- If I have been able to see further, it was only because I stood on the shoulders of giants. -- Isaac Newton Roel Schroeven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wake-on-lan
On Tue, May 30, 2006 at 08:56:24PM +0200, Roel Schroeven wrote: > Now I did investigate, and this is what I found out: given that the BIOS > is configured correctly, I can remotely wake the box if I shut it down > before it boots Linux (it works if I shut it down while the Grub menu is > visible), but it doesn't work if I shut it down when Linux is running. I > tried shutting it down via poweroff, shutdown -h now and pushing the > power button, but all with the same effect: no response to wake-up packets. > > So, what can I do to enable the wake-on-lan feature again? I had a similar problem... Before shutting down, I need to run this command: # ethtool -s eth0 wol g Because after a reboot WOL is disabled. I included that line in my boot scripts. J. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wake-on-lan
The way you shut the box down isn´t supposed to have any effect on the ability to wake it up. To wake up the machine has to be an atx form, and be powered on, as you can figure by the lighting ethernet led, in the box´s rear. I´m guessing you have some issue with acpi. What machine is this?On 5/30/06, Roel Schroeven < [EMAIL PROTECTED]> wrote:Hi,I have a box running Debian Unstable that I'd like to power on via wake-on-lan. I had it running some time in the past; at some point intime it stopped working, but I didn't care that much about it so Ididn't investigate it further.Now I did investigate, and this is what I found out: given that the BIOS is configured correctly, I can remotely wake the box if I shut it downbefore it boots Linux (it works if I shut it down while the Grub menu isvisible), but it doesn't work if I shut it down when Linux is running. I tried shutting it down via poweroff, shutdown -h now and pushing thepower button, but all with the same effect: no response to wake-up packets.So, what can I do to enable the wake-on-lan feature again? --If I have been able to see further, it was only because I stoodon the shoulders of giants. -- Isaac NewtonRoel Schroeven--To UNSUBSCRIBE, email to [EMAIL PROTECTED]with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
wake-on-lan
Hi, I have a box running Debian Unstable that I'd like to power on via wake-on-lan. I had it running some time in the past; at some point in time it stopped working, but I didn't care that much about it so I didn't investigate it further. Now I did investigate, and this is what I found out: given that the BIOS is configured correctly, I can remotely wake the box if I shut it down before it boots Linux (it works if I shut it down while the Grub menu is visible), but it doesn't work if I shut it down when Linux is running. I tried shutting it down via poweroff, shutdown -h now and pushing the power button, but all with the same effect: no response to wake-up packets. So, what can I do to enable the wake-on-lan feature again? -- If I have been able to see further, it was only because I stood on the shoulders of giants. -- Isaac Newton Roel Schroeven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wake on lan with onboard amd 97c972 (pcnet32) card
Felipe Leon schreef: Hello all, I have this little server pentium III or smthing. I have debian 3.1 on it and have been struggling to get wol capability without success. The onboard card (email subject) works flawless with the pcnet32 driver but the wol characteristics dont show up when using ethtool so wake on lan doesnt work. I activated wol already in the bios. I bought one of these rtl8139 cards and put it in one of the pci slots. Ethtool shows the wol option, I set it to wake on magic packet, but still it doesnt wake up the computer. I have tested the etherwake program with other systems (same router and so on) and it works fine. Anybody with experience about this? Any help greatly appreciated. Felipe. If you put in another NIC, then you have to connect it to the wol header on your motherboard, with a small plug. I take it you have done so? If so, then perhaps a BIOS upgrade will help (doubtfull). Warren _ Dont just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
wake on lan with onboard amd 97c972 (pcnet32) card
Hello all, I have this little server pentium III or smthing. I have debian 3.1 on it and have been struggling to get wol capability without success. The onboard card (email subject) works flawless with the pcnet32 driver but the wol characteristics dont show up when using ethtool so wake on lan doesnt work. I activated wol already in the bios. I bought one of these rtl8139 cards and put it in one of the pci slots. Ethtool shows the wol option, I set it to wake on magic packet, but still it doesnt wake up the computer. I have tested the etherwake program with other systems (same router and so on) and it works fine. Anybody with experience about this? Any help greatly appreciated. Felipe. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wake on lan
Hi! On Wed Dec 17, 2003 at 08:28:39AM +0100, Lendvai Peter wrote: > My abit kx7 motherboard also has WOL header. I enabled Wake ON lan in > BIOS and I can measure +5V on the WOL header. Somehow the NIC doesin't > recognize magic packets. Does not wake the machine up. I've tried a > lot of wol/magicpacket applications but nothing. > > Did anybody encounter any similar problem? please help :) Maybe the FAQ at [1] can help you. So long Thomas 1. http://ahh.sourceforge.net/wol/faq.html#q1 -- .''`. Obviously we do not want to leave zombies around. - W. R. Stevens : :' : Thomas Krennwallner `. `'` 1024D/67A1DA7B 9484 D99D 2E1E 4E02 5446 DAD9 FF58 4E59 67A1 DA7B `-http://bigfish.ull.at/~djmaecki/ pgp0.pgp Description: PGP signature
wake on lan
hi! I bougth an RTL8139D based NIC and it has WOL ability. My abit kx7 motherboard also has WOL header. I enabled Wake ON lan in BIOS and I can measure +5V on the WOL header. Somehow the NIC doesin't recognize magic packets. Does not wake the machine up. I've tried a lot of wol/magicpacket applications but nothing. Did anybody encounter any similar problem? please help :) thank u in advance Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ether-wake / Wake On Lan setup
On Sun, Oct 07, 2001 at 11:55:51PM +, Darren Wyn Rees wrote: > I am using Donald Becker's ether-wake v.1.03 with some 3COM 905 > NICs, however I am unable to 'wake' any machines. > > I send the magic packet using the correct MAC address : > > debian:~/ether-wake-1.03.orig# ./etherwake -D -b 00:50:DA:34:61:23 > Command line stations address is 00:50:da:34:61:23. > Packet is ff ff ff ff ff ff 00 50 da 34 61 23 08 42 ff ff ff ff ff ff > 00 50 da > 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da > 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da > 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da > 34 61 23 00 50 da 34 61 > 23 00 50 da 34 61 23 00 50 da 34 61 23. > Sendto worked ! 116. > > Looking at the LAN switch I can see activity. Looking at the NIC > on the box to be woken, I can see link activity... but no wakey, wakey. > > I have tried using two different motherboards, and read through the > motherboard manuals to double check everything is configured properly. > > Useful comments and suggestions much appreciated. I'm not sure about yours, but mine (don't remember which driver, but is SMC) won't wakeup from cold ATX plugin, but only after ATX power off. -- Ferret -- Support your government, give Echelon / Carnivore something to parse -- classfield top-secret government restricted data information project CIA KGB GRU DISA DoD atheist defense systems military systems spy steal EMP Microsoft terrorist Allah Natasha Gregori destroy destruct attack will own send Russia bank system compromise World Trade Center international rule the world ATSC RTEM warmod ATMD force Pentagon power enforce Bin Laden Bill Gates sensitive directorate TSP NSTD ORD DD2-N AMTAS STRAP warrior-T presidental elections policital foreign fnord embassy takeover democracy -- pgp6keuab3D52.pgp Description: PGP signature
ether-wake / Wake On Lan setup
I am using Donald Becker's ether-wake v.1.03 with some 3COM 905 NICs, however I am unable to 'wake' any machines. I send the magic packet using the correct MAC address : debian:~/ether-wake-1.03.orig# ./etherwake -D -b 00:50:DA:34:61:23 Command line stations address is 00:50:da:34:61:23. Packet is ff ff ff ff ff ff 00 50 da 34 61 23 08 42 ff ff ff ff ff ff 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23 00 50 da 34 61 23. Sendto worked ! 116. Looking at the LAN switch I can see activity. Looking at the NIC on the box to be woken, I can see link activity... but no wakey, wakey. I have tried using two different motherboards, and read through the motherboard manuals to double check everything is configured properly. Useful comments and suggestions much appreciated. -- Darren Wyn Rees [EMAIL PROTECTED]
Re: wake on lan
Markus, If you open lilo.conf on the box that will not go to sleep you will see a line in there called append="" make it look like this append="apm=on" and then in the terminal type lilo and that will make the change take effect. The wake on lan pc will then shut down after you tell it to. I hope that this is what you rlooking for. Don --- Markus Hansen <[EMAIL PROTECTED]> wrote: > hi guys i have the following problem but it seems to > me that it is a > little OT. > i want to use wake on lan for a pc. > this pc shall be woken up on lan if another pc is > present (this pc sends > automaticly the wake sequence) > my problem is: > i put the pc into the state to be woken up on lan. > one pc wakes it up > the wake-on-lan-pc wakes up and does several > services. > now the other pc shuts down and sends a shut down > signal to the wake on > lan pc (because it shouldnt run all the time) > the wake on lan pc shuts down... > i cant wake it up later... > this is my problem. > how do i have to shut it down to be able to start it > again? > ps what is the difference between shutdown -h and -p > (it seems i cant > use p) > plaese help, my evil brother is sitting at my neck > if i cant give him a > solution and he is really angry. > markus > > > -- > To UNSUBSCRIBE, email to > [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/
Re: wake on lan
allright. shutdown -h waits for you to push the reset button or turn off and back on the power. But very likely you are using an atx board. Well I heard that to use the full functionality of the ATX board, ( turn off autmatically) you must configure lilo ( lilo.conf). I also think you must enable some feature in the kernel to do that. These are only assumptions but I hope it is of some use. regards On Wed, 8 Aug 2001, Markus Hansen wrote: > hi guys i have the following problem but it seems to me that it is a > little OT. > i want to use wake on lan for a pc. > this pc shall be woken up on lan if another pc is present (this pc sends > automaticly the wake sequence) > my problem is: > i put the pc into the state to be woken up on lan. > one pc wakes it up > the wake-on-lan-pc wakes up and does several services. > now the other pc shuts down and sends a shut down signal to the wake on > lan pc (because it shouldnt run all the time) > the wake on lan pc shuts down... > i cant wake it up later... > this is my problem. > how do i have to shut it down to be able to start it again? > ps what is the difference between shutdown -h and -p (it seems i cant > use p) > plaese help, my evil brother is sitting at my neck if i cant give him a > solution and he is really angry. > markus > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
wake on lan
hi guys i have the following problem but it seems to me that it is a little OT. i want to use wake on lan for a pc. this pc shall be woken up on lan if another pc is present (this pc sends automaticly the wake sequence) my problem is: i put the pc into the state to be woken up on lan. one pc wakes it up the wake-on-lan-pc wakes up and does several services. now the other pc shuts down and sends a shut down signal to the wake on lan pc (because it shouldnt run all the time) the wake on lan pc shuts down... i cant wake it up later... this is my problem. how do i have to shut it down to be able to start it again? ps what is the difference between shutdown -h and -p (it seems i cant use p) plaese help, my evil brother is sitting at my neck if i cant give him a solution and he is really angry. markus
Re: Wake on LAN question
>>>>> "Robert" == Robert Kerr <[EMAIL PROTECTED]> writes: Robert> What would be the steps to go about setting linux up for Robert> wake-on-lan access? Disclaimer: I never used wake-on-lan, but I can make a few educated guesses about how it might work. YMMV. To get the machine to suspend, you should only need to install the APM package, and boot the kernel with `apm=on'. The BIOS will alert the machine when something happens on the network. Next step: getting the client machines to awaken the firewall. You probably need to set up an ARP entry for the firewall. (See man arp for more info.) Hopefully, this is enough to get the server out of sleep mode. If you have a dynamically assigned IP address on the external network, you might need to restart the DHCP client (and reinstall firewall rules) on APM resume. -- G. ``Iggy'' Geens - ICQ: #64109250 Home: <[EMAIL PROTECTED]> - Work: <[EMAIL PROTECTED]> WWW: http://users.pandora.be/guy.geens/ `I want quality, not quantity. But I want lots of it!'
Re: Wake on LAN question
On Mon Jul 30 07:24:38 2001, [EMAIL PROTECTED] wrote: > Hi all, > I am setting up a machine to do firewalling/IP masquerading. I'd like to > be able to leave this machine on all the time, but perhaps in a > powered-down mode, so it's not using as much electricity, and not so noisy > at night. I envision it in standby or suspend mode, but waking up > whenever someone on my internal LAN wants to access the internet. > 1) Is this possible? > 2) What would be the steps to go about setting linux up for wake-on-lan > access? 1. Get the right combination of hardware. You need a NIC that can do it, a motherboard/power-supply that can do it, and a wire from a couple of pins on the NIC to a couple of pins on the motherboard. 2. Get a driver that supports it. 3. Enable WoL support in the driver 4. Shut down the machine softly enough 5. Get a program that can send the magic ethernet frames to trigger WoL In my case, the things are 1. 3Com 3c905C Tornado 2. standard 3c59x.o 3. options 3c59x enable_wol=1 4. APM enabled, so 'shutdown -h now' shuts down properly 5. etherwake.c by Donald Becker 'etherwake' needs to be run explicitly, as root - thus, I only answered part of your question. I imagine doing WoL automagically would be difficult. Still, WoL is a nifty thing, even if you have to do it manually. /Jörgen -- // Jörgen Grahn "...idols of gold, and silver, and brass, [...] \X/ <[EMAIL PROTECTED]> which neither can see, nor hear, nor walk." -- Revelation, 9:20
Re: Wake on LAN question
On Monday July 30 2001 09:24, Robert Kerr wrote: > Hi all, > I am setting up a machine to do firewalling/IP masquerading. I'd like to > be able to leave this machine on all the time, but perhaps in a > powered-down mode, so it's not using as much electricity, and not so noisy > at night. I envision it in standby or suspend mode, but waking up > whenever someone on my internal LAN wants to access the internet. > 1) Is this possible? > 2) What would be the steps to go about setting linux up for wake-on-lan > access? > > thanks I haven't done this myself, but you might want to look at the APM support in the Linux kernel. I think there is either a power howto or an APM howto. I remember reading about this when I was researching ways to enable suspend on my laptop. I think it's doable. HTH, Andy
Wake on LAN question
Hi all, I am setting up a machine to do firewalling/IP masquerading. I'd like to be able to leave this machine on all the time, but perhaps in a powered-down mode, so it's not using as much electricity, and not so noisy at night. I envision it in standby or suspend mode, but waking up whenever someone on my internal LAN wants to access the internet. 1) Is this possible? 2) What would be the steps to go about setting linux up for wake-on-lan access? thanks -- -bob Remember the... the... uhh. ** * Robert Kerr, The morphing guy. *MS 0847 Sandia National Labs * * [EMAIL PROTECTED] *Albuquerque NM 87185-0847 * * [EMAIL PROTECTED] * Phone: (505) 844-8606 * * http://www.et.byu.edu/~kerrr* Fax: (505) 844-9297 * **
