[vortex] Wont wake up after suspend with 2.4.7 (vortex_suspend?)

[Martin Vonwald]

Am Sonntag, 4. November 2001 05:08 schrieben Sie:
> Martin Vonwald wrote:
> > Hi all!
> >
> > I have _one_ machine with two setups:
> > * the old setup is running kernel 2.2.14 (Suse 6.3)
> > * the new setup is running kernel 2.4.7 (Suse 7.2)
> >
> > This machine runs pretty all the time and suspends itself via "apm -s" if
> > no other machine is connected (smb+nfs). When some other machine accesses
> > the network it should wake up on its own - and it does exactly that
> > running 2.2.14 and it completely fails running 2.4.7 (both using the
> > driver 3c90x from the kernel of the distro)
> >
> > When the the machine (2.4.7) goes into suspend and after that resumes
> > (manually!) I see the following messages in /var/log/messages:
> > ---------
> > Oct 30 07:56:12 Heraklith apmd[564]: Version 3.0final (APM BIOS 1.2,
> > Linux driver 1.14)
> > Oct 30 07:56:13 Heraklith apmd[564]: Charge: * * * (-1% unknown)
> > Oct 30 07:56:14 Heraklith kernel: vortex_suspend(eth0)
> > Oct 30 07:56:15 Heraklith apmd[564]: User Suspend
> > Oct 30 07:56:27 Heraklith kernel: vortex_resume(eth0)
> > Oct 30 07:56:27 Heraklith kernel: eth0: using NWAY device table, not 8
> > Oct 30 07:56:28 Heraklith apmd[564]: Normal Resume after 00:00:13 (-1%
> > unknown) AC power
> > ---------
>
> Please add
>
> 	options 3c59x enable_wol=1
>
> to /etc/modules.conf.  Despite the name, this option enables the
> use of the new power management APIs in the kernel.  It'll save
> and restore the device's power state and may well fix the problem.

Hi again!

I have now successfully upgraded to 2.4.13. The nic now works with 
enable_wol=1, but still the machine doesnt wake up on network activity.
With this option set now I dont get those messages vortex_suspend and 
vortex_resume anymore.

For now it seems to me that 2.4 completely breaks the ability to wake up my 
machine. As I didnt mention it clearly in my first mail, please read:
-----
This machine is NOT a laptop - it is a desktop machine running as 
file/web/ftp server and is providing my internet connection. IIt puts itself 
into suspend mode via apm -s, i.e. everything (all applications, drivers, 
etc.) is still "running" - only the cpu is on halt (not precisely, but you 
get the point).
So I think WOL doesnt make any difference for me because as far as I 
understand WOL, this should power on a powered-off machine; but my machine is 
never powered off.
Using 2.2.x this machines wakes up if someone on the network tries to reach 
the machine, i.e. a simple ping on its ip address(!!) is enough.
Using 2.4.x this machine does NOT wake up.
-----

Any further ideas? Right now I can stand up every day early in the morning 
and press the suspend button myself - pretty suboptimal ;-)

Thanks for your help,
Martin

> _______________________________________________
> vortex mailing list
> vortex@scyld.com
> http://www.scyld.com/mailman/listinfo/vortex