TCLUG Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [TCLUG:18004] 3C905C-TX-M with Linux



Jeez -- dyslexia strikes again.  I have a bunch of 3c509, not '905.  509's
are definitely ISA.  Well, shoot.  I guess what I said about loading
modules first has to be relegated back to "voodoo" status - it might work,
but it's shooting blind.

Phil M


On Tue, 23 May 2000 Nick.T.Reinking@supervalu.com wrote:

> Since the 3c905 cards are PCI, they should definitely *not*
> be using the 0x300 I/O range.  If they are, you've got some
> more serious issues. (I/O 0x300 is a ISA I/O range)
> 
> Nick Reinking
> 
> 
> 
> 
> 
> mend0070@tc.umn.edu, on 05/22/2000 09:18:45 PM
> To: tclug-list@mn-linux.org @ PMDF
> cc:  
> Subject: Re: [TCLUG:18004] 3C905C-TX-M with Linux
> 
> I'd have to open a box that's not handy to find out if they were -M, but I
> have a few 3C905s that were difficult to load the modules for.  I finally
> found that they needed to be loaded first -- either reboot, or turn all
> the other modules off first.
> 
>   I bet that this could be gotten around if you knew more about the
> addresses involved than I did.  Something else (hardware *or* software)
> may be using the 0x300 space -- apparently if you have multiple
> programmable I/O addresses, something may fall into the wrong slot.
> 
> That's all I know -- you probably know what's wrong with what I said.  But
> I've gotten similar cards to behave themselves.
> 
> Cheers,
> Phil M
> 
> On Mon, 22 May 2000, Christopher Reid Palmer wrote:
> 
> > Hello,
> > 
> > You'd think this card would work with the usual Vortex/Boomerang driver,
> > 3c59x.o, but nope. When I try to insert it with either insmod(8) or
> > modprobe(8), I get the evil `Device or resource busy' error. I also tried
> > compiling the driver into the kernel and not as a module. I have never had
> > trouble with other 905s (non-`-M') using this driver (I'm using one right
> > now). I've also tried inserting the module with many of the options
> > described in /usr/src/linux/Documentation/networking/vortex.txt, all to no
> > avail.
> > 
> > I think it's the `-M' in the name. Windows sees the card as an `EtherLink
> > ... for Total PC Management ...' (or similar; I'm not in front of the
> > system now). Does anyone know either a) what the error means or b) if the
> > -M cards are known bad under Linux (seems unlikely)?
> > 
> > I have had success with pulling the card out and replacing it with an
> > Intel EtherExpress Pro (eepro.o), so I think the kernel and the other
> > hardware are all fine.
> > 
> > 
> > Desperate,
> > --
> > Christopher Reid Palmer : innerfireworks.com
> > 
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> > For additional commands, e-mail: tclug-list-help@mn-linux.org
> > 
> > 
> 
> 

-- 
Lottery:    a tax on people who are bad at math