From owner-freebsd-questions@FreeBSD.ORG Tue Aug 29 13:35:35 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00D2F16A4DD for ; Tue, 29 Aug 2006 13:35:34 +0000 (UTC) (envelope-from freebsd@dfwlp.com) Received: from zeus.dfwlp.com (zeus.dfwlp.com [208.11.134.127]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82FCD43D45 for ; Tue, 29 Aug 2006 13:35:34 +0000 (GMT) (envelope-from freebsd@dfwlp.com) Received: from webmail.dfwlp.org (localhost.dfwlp.com [127.0.0.1]) by zeus.dfwlp.com (8.13.6/8.13.6) with ESMTP id k7TDZTlb022695 for ; Tue, 29 Aug 2006 08:35:29 -0500 (CDT) (envelope-from freebsd@dfwlp.com) Received: from 167.246.36.14 (SquirrelMail authenticated user jhorne) by webmail.dfwlp.org with HTTP; Tue, 29 Aug 2006 08:35:29 -0500 (CDT) Message-ID: <16819.167.246.36.14.1156858529.squirrel@webmail.dfwlp.org> In-Reply-To: <1fd935cc0608290240y5fc46020l28b6bd531d025e5a@mail.gmail.com> References: <1fd935cc0608290240y5fc46020l28b6bd531d025e5a@mail.gmail.com> Date: Tue, 29 Aug 2006 08:35:29 -0500 (CDT) From: "Jonathan Horne" To: freebsd-questions@freebsd.org User-Agent: SquirrelMail/1.4.8 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.4 X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on zeus.dfwlp.com Subject: Re: Wake on Lan stopped working soon after system upgrade X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2006 13:35:35 -0000 > Hi there > > I recently upgraded my system from > FreeBSD 6.1-STABLE #1: Sun Jul 30 15:12:34 NZST 2006 > to > FreeBSD 6.1-STABLE #2: Mon Aug 7 19:20:35 NZST 2006 > Somewhere along the way my Wake on Lan stopped working. I've tested my > Wakeup system[1] - it is still wakes up my WinXP laptop but won't wake > up my FreeBSD[2] box. > > After checking a few logs it seems I did manage to wake the system up > remotely once once after 'make installkernel' and 'make installworld'. > The only thing I've changed since then is an upgrade of ports[3]. > > I have noticed that when my FreeBSD box is shut down, the Ethernet > lights are off. I have a feeling that previously the lights may have > stayed on when the system was down(?) I've checked the bios[4] > settings, it is still set to wake on lan. The LAN port[5] is built > into the motherboard. > > I've had a bit of a look at the ACPI[6] settings in the kernel[7], but > nothing's standing out, even after reading the acpi man page. I've > tried booting with and without acpi, and always shutdown with > "shutdown -p". > > Hope someone can help, > Dan > > > [1] "Linksys WRT54Sv1.1 GDD-WRT v23 SP1 Final (05/16/06) voip" > > [2] FreeBSD schooner.harbour 6.1-STABLE FreeBSD 6.1-STABLE #2: Mon Aug > 7 19:20:35 NZST 2006 > > root@schooner.harbour:/usr/obj/usr/src/sys/SCHOONER i386 > > [3] Here's what "portmanager -u" updated after the last time I got WoL to > work. > 00029 have:portupgrade-2.1.3.2_2,2 /sysutils/portupgrade > OLD available: portupgrade-2.1.3.2_3,2 > 00045 have:php5-5.1.4 /lang/php5 > built with OLD dependency: apache-1.3.37_1 > 00047 have:apache-1.3.37 /www/apache13 > OLD available: apache-1.3.37_1 > 00065 have:postgresql-libpqxx-2.6.6 > /databases/postgresql-libpqxx OLD available: > postgresql-libpqxx-2.6.7 > 00080 have:koffice-1.5.1,2 /editors/koffice-kde3 > built with OLD dependency: > > postgresql-libpqxx-2.6.7 > 00087 have:kdelibs-3.5.3 /x11/kdelibs3 > built with OLD dependency: > > mDNSResponder-107.5 > 00093 have:libltdl-1.5.22 /devel/libltdl15 > > > [4] BIOS upgraded before I set WoL up. Gigabyte GA-7VKMLS motherboard > VIA KM266/KL266 chipset > > [5] > rl0: port 0xe000-0xe0ff mem > 0xdefdff00-0xdefdffff irq 18 at device 19.0 on pci0 > miibus0: on rl0 > rlphy0: on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > rl0: Ethernet address: 00:20:ed:6f:dd:4d > acpi_button1: on acpi0 > > > [6] > $ dmesg | grep acpi > acpi0: on motherboard > acpi0: Power Button (fixed) > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > cpu0: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > acpi_button1: on acpi0 > fdc0: port 0x3f2-0x3f3,0x3f4-0x3f5,0x3f7 irq > 6 drq 2 on acpi0 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > ppc0: port 0x378-0x37f,0x778-0x77b irq 7 > drq 3 on acpi0 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > acpi0: on motherboard > acpi0: Power Button (fixed) > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > cpu0: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > acpi_button1: on acpi0 > fdc0: port 0x3f2-0x3f3,0x3f4-0x3f5,0x3f7 irq > 6 drq 2 on acpi0 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > ppc0: port 0x378-0x37f,0x778-0x77b irq 7 > drq 3 on acpi0 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > $ > > [7] > $ sysctl -a | grep acpi > acpidev 48 2K - 48 32 > acpisem 19 2K - 19 64 > acpitask 0 0K - 1 32 > acpica 1566 85K - 20527 16,32,64,128,256,512,1024 > acpipwr 1 1K - 1 32 > debug.acpi.do_powerstate: 1 > debug.acpi.acpi_ca_version: 0x20041119 > debug.acpi.semaphore_debug: 0 > hw.acpi.supported_sleep_state: S1 S4 S5 > hw.acpi.power_button_state: S5 > hw.acpi.sleep_button_state: S1 > hw.acpi.lid_switch_state: NONE > hw.acpi.standby_state: S1 > hw.acpi.suspend_state: S3 > hw.acpi.sleep_delay: 1 > hw.acpi.s4bios: 0 > hw.acpi.verbose: 0 > hw.acpi.disable_on_reboot: 0 > hw.acpi.handle_reboot: 0 > hw.acpi.reset_video: 1 > hw.acpi.cpu.cx_supported: C1/0 > hw.acpi.cpu.cx_lowest: C1 > hw.acpi.cpu.cx_usage: 100.00% > machdep.acpi_timer_freq: 3579545 > machdep.acpi_root: 1025552 > dev.acpi.0.%desc: AMIINT AMIINI09 > dev.acpi.0.%driver: acpi > dev.acpi.0.%parent: nexus0 > dev.acpi_sysresource.0.%desc: System Resource > dev.acpi_sysresource.0.%driver: acpi_sysresource > dev.acpi_sysresource.0.%location: handle=\_SB_.PCI0.SBRG.SYSR > dev.acpi_sysresource.0.%pnpinfo: _HID=PNP0C02 _UID=0 > dev.acpi_sysresource.0.%parent: acpi0 > dev.acpi_timer.0.%desc: 24-bit timer at 3.579545MHz > dev.acpi_timer.0.%driver: acpi_timer > dev.acpi_timer.0.%location: unknown > dev.acpi_timer.0.%pnpinfo: unknown > dev.acpi_timer.0.%parent: acpi0 > dev.pci_link.0.%parent: acpi0 > dev.pci_link.1.%parent: acpi0 > dev.pci_link.2.%parent: acpi0 > dev.pci_link.3.%parent: acpi0 > dev.cpu.0.%parent: acpi0 > dev.acpi_button.0.%desc: Power Button > dev.acpi_button.0.%driver: acpi_button > dev.acpi_button.0.%location: handle=\_SB_.PWRB > dev.acpi_button.0.%pnpinfo: _HID=PNP0C0C _UID=0 > dev.acpi_button.0.%parent: acpi0 > dev.acpi_button.1.%desc: Sleep Button > dev.acpi_button.1.%driver: acpi_button > dev.acpi_button.1.%location: handle=\_SB_.SLPB > dev.acpi_button.1.%pnpinfo: _HID=PNP0C0E _UID=0 > dev.acpi_button.1.%parent: acpi0 > dev.pcib.0.%parent: acpi0 > dev.fdc.0.%parent: acpi0 > dev.sio.0.%parent: acpi0 > dev.sio.1.%parent: acpi0 > dev.ppc.0.%parent: acpi0 > dev.atdma.0.%parent: acpi0 > dev.attimer.0.%parent: acpi0 > dev.attimer.1.%parent: acpi0 > dev.npxisa.0.%parent: acpi0 > dev.psmcpnp.0.%parent: acpi0 > dev.atkbdc.0.%parent: acpi0 > $ the act of the actual "waking up of" is operating system independant. however, i think acpi might the right place to be looking, as it might be shutting your system down differently than before. if your ethernet lights are not bliking even when your system is powered down, then youll be dead in the water until those start working again. first thing to check, is to make sure your bios didnt get reset somehow, and turned of the WOL support. second, did you compile your kernel differently this time around? try switching to the old kernel, giving a 'shutdown -p now' and see if the ethernet lights remain on and blinking. hth, jonathan