public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Andrew Morton <akpm@digeo.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3c59x gives HWaddr FF:FF:...
Date: 29 Mar 2003 01:29:26 +0100	[thread overview]
Message-ID: <1048897765.601.5.camel@teapot> (raw)
In-Reply-To: <20030328230510.GA5124@werewolf.able.es>

On Sat, 2003-03-29 at 00:05, J.A. Magallon wrote:
> > > What happens ? Any solution available ?
> > 
> > The eeprom wasn't powered up.
> > 
> > Please take the 2.4.20 3c59x.c and place that into the 2.5 tree and confirm
> > that it does the same thing (it will).> 
> 
> Hum, I suppose you want to say take the _2.5_ one and put into my _2.4_ tree ?
> Some previous answer also talked about a more recent version in -ac.
> (btw, can 2.5 be useful for something ? does not the driver depend on a new
> arch of, for example, the PCI layer ? )
> 
> > Then try disabling APCI and/or otherwise fiddling with your power management
> > options (maybe in BIOS too).> 
> 
> I don't build ACPI, just APM power-off (SMP box).
> Will take a look at 2.4-ac (it looks like the most similar thing to what I have)
> and to 2.5.

I had exactly the same issue as you, but this time it was on my laptop
when using a 3CCFE575CT CardBus 10/100 NIC. The only solution I found
was to use SourceForge's PCMCIA-CS instead of the built-in PCMCIA
support.

I tracked down the problem to PCI resource allocation, although never
knew what was causing it: the CardBus bridge was using the PCI subsystem
to allocate resources for my CardBus NIC, but it failed and tried to
assign an invalid I/O range (the starting I/O address was higher than
the ending I/O address). I wasn't able to fix it, but in newer kernel
releases, the problem was fixed.

Now, I've got other problems: the card works correctly and I get full
throughput when sending data using FTP/NFS/SCP (~12MBps) but no more
than 4MBps when receiving files.

________________________________________________________________________
        Felipe Alfaro Solana
   Linux Registered User #287198
http://counter.li.org


  parent reply	other threads:[~2003-03-29  0:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-28 14:51 3c59x gives HWaddr FF:FF: J.A. Magallon
2003-03-28 15:57 ` Eric Weigle
2003-03-28 20:48 ` Andrew Morton
2003-03-28 23:05   ` J.A. Magallon
2003-03-28 23:16     ` Andrew Morton
2003-03-29  0:46       ` J.A. Magallon
2003-03-29 17:12         ` Thomas Backlund
2003-03-29 19:45           ` Felipe Alfaro Solana
2003-03-30  2:21           ` Juan Quintela
2003-03-30 10:19             ` Felipe Alfaro Solana
2003-03-30 10:53               ` Thomas Backlund
2003-03-30 11:16                 ` Felipe Alfaro Solana
2003-03-31 19:09             ` Bas Vermeulen
2003-03-29  0:29     ` Felipe Alfaro Solana [this message]
2003-03-29  0:44       ` Andrew Morton
2003-03-29  1:23         ` Felipe Alfaro Solana
  -- strict thread matches above, loose matches on Subject: below --
2003-03-28 16:13 Alex Davis

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=1048897765.601.5.camel@teapot \
    --to=felipe_alfaro@linuxmail.org \
    --cc=akpm@digeo.com \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.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