Very Computer

by **Michael Metzle** » Thu, 03 Sep 1998 04:00:00

I am trying to get my 3c905-TX working on my system, and whenever I try
to fire up the network (ifup eth0 or via netcfg), the system stops --
immediately and completely -- no mouse, no keyboard, no nothing. I must
power off and reboot.

I am running Linux 5.1 (dual boot with Nt 4.0) on a Micron Xku 300, 128
Mb RAM, 8 Mb IDE, internal zip, Viper V330 w/4mb, USR 56K modem.
Everything else seems to work O.K. The 3c905 is recognized and the
module is loaded at boot. The 3c905 works just fine under NT.

I know just enough to be dangerous. I suspect (gut feeling) that this
is an interrupt conflict, but have yet to determine how to change the
IRQ for the 3c905 (IRQ 9 is reported). The web page at
http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html seems to suggest
moving the board to a different slot to get a different interrupt. I
tried this, with no apparent change in results.

Any suggestions?

Thanks much,
Mike Metzler

by **Daniel Schil** » Sat, 05 Sep 1998 04:00:00

> I am trying to get my 3c905-TX working on my system, and whenever I try
> to fire up the network (ifup eth0 or via netcfg), the system stops --
> immediately and completely -- no mouse, no keyboard, no nothing. I must
> power off and reboot.

> I am running Linux 5.1 (dual boot with Nt 4.0) on a Micron Xku 300, 128
> Mb RAM, 8 Mb IDE, internal zip, Viper V330 w/4mb, USR 56K modem.
> Everything else seems to work O.K. The 3c905 is recognized and the
> module is loaded at boot. The 3c905 works just fine under NT.

> I know just enough to be dangerous. I suspect (gut feeling) that this
> is an interrupt conflict, but have yet to determine how to change the
> IRQ for the 3c905 (IRQ 9 is reported). The web page at
> http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html seems to suggest
> moving the board to a different slot to get a different interrupt. I
> tried this, with no apparent change in results.

> Any suggestions?

Get the 3c90xx tools from 3Com and run the configuration program -
auto-detect should find the right settings for you system. I allways do
this as a 1st step of my installation procedure. 2nd thing is that you
should try to compile the driver into the kernel.

--
Daniel Schild
Dienst- und Applikationsentwicklung
Teleport Sachsen-Anhalt GmbH | RegioCom GmbH
Tel: ++49 39203 8 2030 | ++49 39203 8 3300
Fax: ++49 39203 8 2031 | ++49 39203 8 3399

S-Mail: Steinfeldstr. 3, 39179 Barleben, Germany

by **Michael Metzle** » Sat, 05 Sep 1998 04:00:00

> Get the 3c90xx tools from 3Com and run the configuration program -
> auto-detect should find the right settings for you system. I allways do
> this as a 1st step of my installation procedure. 2nd thing is that you
> should try to compile the driver into the kernel.

> --
> Daniel Schild
> Dienst- und Applikationsentwicklung
> Teleport Sachsen-Anhalt GmbH | RegioCom GmbH
> Tel: ++49 39203 8 2030 | ++49 39203 8 3300
> Fax: ++49 39203 8 2031 | ++49 39203 8 3399

> S-Mail: Steinfeldstr. 3, 39179 Barleben, Germany

Thanks for the suggestions. At first, this did not work -- even though the
3c905 worked great under NT, the 3Com tools could not find it!! Moving it to
a different slot resulted in a changed IRQ (10 vs previous 9) and now the
tools found the card. Strange, makes me think even more of an interrupt
conflict. In any case, the card now works w/RH 5.1 as well as NT (after
uninstalling and reinstalling).

Appreciate the help!

___________________
Michael D. Metzler
ISCIENCES, L.L.C.
220 E. Huron, Suite 270
Ann Arbor, MI 48104
(734) 214-9810 (phone)
(734) 214-9813 (FAX)

Very Computer

3c905 startup brings system down

3c905 startup brings system down

3c905 startup brings system down

3c905 startup brings system down