public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter.Zeipelt-zqRNUXuvxA0b1SvskN2V4Q@public.gmane.org
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: No network after S3
Date: Sat, 14 Feb 2004 15:39:49 +0100 (CET)	[thread overview]
Message-ID: <1076768932.402e30a460d2e@webmail.t-online.de> (raw)

Hello list

I hope this is the right place for my question.
Using an ABIT KT7-RAID with SuSE 8.2prof and the kernel 2.6.1 or 2.6.2
STR seems to work fine.
But trying to use network nothing really happens.
I tried out several NICs (3c905c, 100PRO/S and one with a 8139b).
When i try to ping another  host in the local net, all get is an
Destination Host unreachable.
The 8139b says "no buffer space available" .
A dmesg with the 3c905 says "IRQ blocked by another device?"
But there isn't any other device on this IRQ.
Un- and reloading the module doesn't help.
Trying the STR on an ASUS A7N8X with driver for the nforce NIC in the
kernel brings the same result.
Another strange thing to me is, that S3 and S4 are working better on
the old ABIT  board with Via KT133
chipset then on my newer nforce boards.
The ASUS didn't fall in S4 mode, cause it seems that the disks are
powered down before writing the RAM
on it.
An Enmic 8RDA+ doesn't boot after S3.
But for now my main problem is to bring the network to work after the
S3.
Any hints?

Thanks
Peter


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

             reply	other threads:[~2004-02-14 14:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-14 14:39 Peter.Zeipelt-zqRNUXuvxA0b1SvskN2V4Q [this message]
     [not found] ` <1076768932.402e30a460d2e-2RFepEojUI3OpE1Re6/EDRvVK+yQ3ZXh@public.gmane.org>
2004-02-15  5:36   ` No network after S3 Len Brown
     [not found]     ` <1076823407.25351.73.camel-D2Zvc0uNKG8@public.gmane.org>
2004-02-15  8:12       ` Len Brown
     [not found]         ` <1076832762.25353.132.camel-D2Zvc0uNKG8@public.gmane.org>
2004-02-15  9:34           ` Peter.Zeipelt-zqRNUXuvxA0b1SvskN2V4Q
  -- strict thread matches above, loose matches on Subject: below --
2004-02-16  6:10 Brown, Len
     [not found] ` <BF1FE1855350A0479097B3A0D2A80EE0025A6344-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2004-02-16 11:02   ` Peter.Zeipelt-zqRNUXuvxA0b1SvskN2V4Q
2004-02-16 13:17   ` Thorsten Zachmann
     [not found]     ` <200402161417.42755.t.zachmann-c61pB8mzqkY@public.gmane.org>
2004-02-17  6:53       ` Len Brown
     [not found]         ` <1077000806.2515.46.camel-D2Zvc0uNKG8@public.gmane.org>
2004-02-17  7:56           ` Thorsten Zachmann
     [not found]             ` <200402170856.42059.t.zachmann-c61pB8mzqkY@public.gmane.org>
2004-02-24  6:41               ` Thorsten Zachmann
     [not found]                 ` <200402240741.30530.t.zachmann-c61pB8mzqkY@public.gmane.org>
2004-02-24 16:41                   ` Peter Meier
2004-02-17 21:49           ` Peter.Zeipelt-zqRNUXuvxA0b1SvskN2V4Q

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1076768932.402e30a460d2e@webmail.t-online.de \
    --to=peter.zeipelt-zqrnuxuvxa0b1svskn2v4q@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox