Re: wol rtl 8139 or APM power off or hardware problem?

From: JK (joze.klepec_at_siol.net)
Date: 11/10/04


Date: Wed, 10 Nov 2004 19:03:29 +0000

David Schrittesser pravi:
> Dear Fellow Subscribers,
>
> I am trying to get my computer to wake on LAN, but it just stays off. I am
> not sure where the problem occurs.
>
> I use a perl module called "Net-Wake". I have checked that the machine to
> be woken (the target machine) receives the wake-packages by logging all
> packets received on that port with ipchains.
> My BIOS (Award Modular v4.51 PG, Motherboard: M6VBE-A) has an option WOL
> and I enabled it. I also enabled the "PM by APM" option. Is that needed?
> I also have a little cable connecting NIC to the proper plug.
> When execute /usr/bin/poweroff (that's how I usually turn of my
> machine) it turns of power, but it doesn't ever wol. Should the NIC light
> be on or something after power of? It's not. Is it clear that I am in ATX
> soft power off mode or +5VSB after I do poweroff?
>
> To people with similar problems, the following advice has been given:
> Recompile the kernel with CONFIG_APM_REAL_MODE_POWER_OFF (this option is
> infact 'n' in my kernel)
> or boot with kernel parameter apm=power-off
> What does this have to do with it? I thought this only helps you if you
> can't do software controlled poweroff?
> By the way, apm -v gives APM BIOS 1.2 (kernel driver 1.13). I don't think
> it works correctly for when I do apm -s (that's standby) the screen
> blanks but the computer never resumes (but I am ignorant with repsect to
> apm).
> I admit I am confused.
> Let me know if you have any helpful information.
>
> (Net_Wake was obtained from
> http://www.perl.com/CPAN/authors/id/CLINTDW/, and listed in the Wake on
> LAN mini HOWTO)
>
> bw, David
>
>
1. You need to know which version of RTL 8139 chipset you have
(8139a/b/c/d).
2. if RTL 8139? adapter is onboard, then most likely this is APM
problem. Try disabling APM in BIOS for a good start. That worked fine
for my Asus VM266SE-LAN.
3. Try further tinkering in BIOS (change default IRQs).
4. If this does not help - the cheapest solution is another RTL8139 PCI
card with another chip version, around 10$ or so (onboard card should be
disabled, but if enabled it can happen that one x PCI RTL 8139 will
raise onboard brand RTL8139 card from the graveyard - voila you can have
them two or more to make something of your network).

cheers, JK



Relevant Pages

  • Re: Problem with remote network connections
    ... problem in installing OpenNETCF 1.4 and 2.1 on the same PC? ... matter of this card not working precisely the same as the other card; ... Summit driver from Unitech, ... and I have a problem connecting to our LAN. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Problem with remote network connections
    ... wanted to as the device manufacturers are telling me that WZC in CE.NET 4.2 ... this card not working precisely the same as the other card; ... I have got the Summit card configured to use WZC. ... WiFi card and connects to the LAN successfully, ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Problem with remote network connections
    ... this card not working precisely the same as the other card; ... I have got the Summit card configured to use WZC. ... You have the latest driver from Summit? ... WiFi card and connects to the LAN successfully, ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: ADSL onload LAN connection
    ... |>> LAN and I want to connect it to my Billion BIPAC-7100 ... |>> allow the onboard LAN port to function because the ... |>> drivers from ASUS for the onboard LAN are not windows ...
    (microsoft.public.windowsxp.general)
  • Re: P4C800-E Deluxe BIOS 1023
    ... I disabled the onboard ... LAN and put in a reliable Intel Nic. ... after a BIOS update I always go into the ... Frustrated I flashed back to 1018 and the onboard LAN connection ...
    (alt.comp.periphs.mainboard.asus)