From: <Pet...@t-...> - 2004-02-15 09:37:31
|
Len, thank `s for your advice. I tried pci=noacpi. No diference. If I understand you right, I should wait a little bit before dealing with this powersaving stuff. You mentioned the bugzilla entries. Can you tell me please where I can find them? So I can see, if the problems there are similar to mine. Peter Len Brown schrieb: > dunno why i didn't realize that you were talking about > the NIC failing > after resuming from S3, guess I didn't read the subject > line;-) > > Yes, we've got a number of bugzilla entries that show > that somehow > interrupts are toast after resume. Perhaps this failure > is the same as > those? > > -Len > > On Sun, 2004-02-15 at 00:36, Len Brown wrote: > > Peter, > > Same NIC works with pci=noacpi or acpi=off? > > If yes, then this is an ACPI bug. If no, then the > problem lies > > elsewhere. > > > > I'd defer dealing with the suspend/resume issues until > more basic > > functionality is working properly. > > > > thanks, > > -Len > > > > > > On Sat, 2004-02-14 at 09:39, Pet...@t-... > wrote: > > > 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 > > > _______________________________________________ > > > Acpi-devel mailing list > > > Acp...@li... > > > > https://lists.sourceforge.net/lists/listinfo/acpi-devel > > > > > > > > > ------------------------------------------------------- > > 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 > > _______________________________________________ > > Acpi-devel mailing list > > Acp...@li... > > > https://lists.sourceforge.net/lists/listinfo/acpi-devel > > |