Re: Network failures with ACPI enabled (kernel 2.4, 2.6) PROBLEM FOUND!!!!!!

[Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>]

On Tue, 2003-12-30 at 18:46, Michael Guntsche wrote:
> On Wed, 31 Dec 2003 00:17:16 +0100
> Michael Guntsche <mike-Z92qn3yYq0hWk0Htik3J/w@public.gmane.org> wrote:
> 
> > Is there a way to see what the change in the CMOS does to ACPI?
> > What puzzles me is that with the parport disabled outgoing traffic
> > still works. It would make more sense if the network didn't work at all.
> > 
> One more piece of information.
> The parport must be set to ECP, else you still get the same errors.

The fact that transmit works and receive fails is a clue.
Probably the broadcom uses interrupts for receive, but doesn't
use interrupts for transmit.  So if it were not getting interrupts,
transmit could still send frames.

So if you enable the parallel port in ECP mode, broadcom works --
but if the port is disabled, or enabled but not in ECP mode, it fails?

This is curious.  Indeed, the AML for this box shows three devices,
ECP, EPP, and LPTB.  Unfortunately, the _PRS for them disassembles
as a Buffer that one has to hand-disassemble to see what resources
are actually possible...

To answer your question about observing what the ECP enable/disable
does to the AML, the DSDT could be extracted, modified
and used to over-ride the DSDT in the BIOS.  This isn't rocket science,
but isn't trivial either.

As curious as the failure is, the system works both ways when
running XP, so I would encourage you to put the info into a
bug report.  The observation about TX working and RX failing
raises the prospect that this really is an IRQ issue, and
with the /proc/interrupts for the different cases at hand
the solution to this puzzle may become more clear.

thanks,
-Len





-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click