3Com 3c501 parameters?

"Network Configuration > Network Adapters Configuration" wants the
following information about the 3Com 3c501 adapter:

IRQ:

MEM:

IO:

IO1:

IO2:

DMA0:

DMA1:





The page:

http://linux.iol.unh.edu/linux/alpha...ll/doc117.html

lists

3c501=io_port,IRQ

opposite 3Com 3c501 , but I don't know how to translate that into the
fields that "Network Configuration > Network Adapters Configuration"
wants.

Thanks.

A.Melon <(E-Mail Removed)> wrote in
news:0eb2aa28966867ab60a6f0ccfc305e6e@melontraffic kers.com:

> "Network Configuration > Network Adapters Configuration" wants the
> following information about the 3Com 3c501 adapter:
>

No it does not. That is what stupid "Network Configua,daskljeqwklejk >
Network Adaptkjqhe wj COnfiguajksdhb" thinks you or it needs to know.

I bet if you knew the io mem's address and maybe the irq card is using with
a single command you could get it working.

If card has jumpers, set them, if not and card has eprom (electronicaly
programmable rom) get an utility and set the io/irq settings for the card.

Then read up some manuals, then load the modules w/ appropriate
arguments. (modprobe <module> io=0xM irq=N)


P.Krumins

A.Melon wrote:
> "Network Configuration > Network Adapters Configuration" wants the
> following information about the 3Com 3c501 adapter:
>
> IRQ:
>
> MEM:
>
> IO:
>
> IO1:
>
> IO2:
>
> DMA0:
>
> DMA1:
>
>
>
>
>
> The page:
>
> http://linux.iol.unh.edu/linux/alpha...ll/doc117.html
>
> lists
>
> 3c501=io_port,IRQ
>
> opposite 3Com 3c501 , but I don't know how to translate that into the
> fields that "Network Configuration > Network Adapters Configuration"
> wants.
>
> Thanks.
>


why dont you search this very newsgroup for '3c509B', their was a
discussion within the last week of a guy getting his 3c509B going which
was an ISA card and that thread would hold great info, and certainly you
can contact the original poster. I believe it used the same driver as
your card.

you may also be able to type

locate 3c501
or
locate 3c509

and find the documentation for your chip.

Mine is here /usr/src/linux-2.4.20-28.9/Documentation/networking/3c509.txt







cl

A.Melon <(E-Mail Removed)> wrote:
> "Network Configuration > Network Adapters Configuration" wants the
> following information about the 3Com 3c501 adapter:

If you're unsure of the parameters a module can give, use the modinfo
program.

(I don't have the 3c501 module compiled, so here's another.)


$ /sbin/modinfo cs46xx
filename: /lib/modules/2.4.22/kernel/drivers/sound/cs46xx.o
description: "Crystal SoundFusion Audio Support"
author: "Alan Cox <(E-Mail Removed)>,
Jaroslav Kysela, <(E-Mail Removed)>"
license: "GPL"
parm: cs_debuglevel int
parm: cs_debugmask int
parm: hercules_egpio_disable int
parm: initdelay int
parm: powerdown int
parm: defaultorder int
parm: external_amp int
parm: thinkpad int

> http://linux.iol.unh.edu/linux/alpha...ll/doc117.html
>
> lists
>
> 3c501=io_port,IRQ

That's saying what parameters it _can_ take.

> opposite 3Com 3c501 , but I don't know how to translate that into the
> fields that "Network Configuration > Network Adapters Configuration"
> wants.

Most of the time, you can leave them empty. With ISA network cards you
may need to specify an IO port and IRQ, which are configured via
jumpers, or via a DOS program that came with the card.

--
Cameron Kerr
(E-Mail Removed) : http://nzgeeks.org/cameron/
Empowered by Perl!

A.Melon <(E-Mail Removed)> said:
>"Network Configuration > Network Adapters Configuration" wants the
>following information about the 3Com 3c501 adapter:

Please, do everything you can to find a more sensible adapter.

Some comments from the start of Linux 3c501 driver source code:
....
This is a device driver for the 3Com Etherlink 3c501.
Do not purchase this card, even as a joke. It's performance is horrible,
and it breaks in many ways.
....
Removed calls to init_etherdev since they are no longer needed, and
cleaned up modularization just a bit. The driver still allows only
the default address for cards when loaded as a module, but that's
really less braindead than anyone using a 3c501 board.
19950208 ((E-Mail Removed))
....
* There are a wide variety of undocumented error returns from the card
* and you basically have to kick the board and pray if they turn up. Most
* only occur under extreme load or if you do something the board doesn't
* like (eg touching a register at the wrong time).
*
* The driver is less efficient than it could be. It switches through
* receive mode even if more transmits are queued. If this worries you buy
* a real Ethernet card.
*
* The combination of slow receive restart and no real multicast
* filter makes the board unusable with a kernel compiled for IP
* multicasting in a real multicast environment. That's down to the board,
* but even with no multicast programs running a multicast IP kernel is
* in group 224.0.0.1 and you will therefore be listening to all multicasts.
* One nv conference running over that Ethernet and you can give up.
....

.... and I recall someone offering a (monetary, but small) reward on each
3C501 MAC-address ROM sent to him as a proof of a 3C501 card having been
decommissioned. This might've been around 1995, or so.
--
Wolf a.k.a. Juha Laiho Espoo, Finland
(GC 3.0) GIT d- s+: a C++ ULSH++++$ P++@ L+++ E- W+$@ N++ !K w !O !M V
PS(+) PE Y+ PGP(+) t- 5 !X R !tv b+ !DI D G e+ h---- r+++ y++++
"...cancel my subscription to the resurrection!" (Jim Morrison)