PROBLEM: 3C905/2.2.15pre11 everything but working

David Forrest drf5n@mug.sys.virginia.edu
Mon Mar 6 20:21:07 2000


I found a win98 disk, booted up, and after the threatening warnings
about my non-formatted C: disk, I loaded the 3c90xcfg program and let
it autoconfig and did the diagnostics.  Lights came on, and I saw lichts
flash with each test packet.

However, booting back up in linux, it remains dark and uncommunicative.

Using the kmod / modules.conf thorough a /sbin/ifconfig eth1 up I get:

/var/adm/essages:
Mar  6 19:56:35 mug kernel: 3c59x.c:v0.99H 11/17/98 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
Mar  6 19:56:35 mug kernel: eth1: 3Com 3c905 Boomerang 100baseTx at
0xd800,  00:60:08:9f:d6:5d, IRQ 12
Mar  6 19:56:35 mug kernel:   8K word-wide RAM 3:5 Rx:Tx split,
autoselect/MII interface.
Mar  6 19:56:35 mug kernel:   Media override to transceiver type 0
(10baseT).
Mar  6 19:56:35 mug kernel:   Enabling bus-master transmits and
whole-frame receives.

With vortex-diag I get the following:

root@mug:~#                 /usr/local/sbin/vortex-diag -a
vortex-diag.c:v1.09 7/28/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a 3c905 Boomerang 100baseTx adapter at 0xd800.
The Vortex chip may be active, so FIFO registers will not be read.
To see all register values use the '-f' flag.
Initial window 7, registers values by window:
  Window 0: 0000 0000 0000 0000 0000 00bf ffff 0000.
  Window 1: FIFO FIFO 0000 2000 8000 00ff 13fc 2000.
  Window 2: 6000 9f08 5dd6 0000 0000 0000 06c6 4000.
  Window 3: 02d8 0103 0000 0000 e040 0bff 13ff 6000.
  Window 4: 0000 06d0 0000 05c0 0002 8ad0 0000 8000.
  Window 5: 1ffc fffc 06c6 0600 0005 06de 06c6 a000.
  Window 6: 0000 0000 0000 0000 0000 0000 0000 c000.
  Window 7: 0000 0000 0000 0000 8000 00ff 0000 e000.
Vortex chip registers at 0xd800
  0xD810: **FIFO** 00000000 00008000 *STATUS*
  0xD820: 00000020 00000000 00000000 06000000
  0xD830: 00000000 0000ab68 093b1800 00000000
 Indication enable is 06c6, interrupt enable is 06de.
 No interrupt sources are pending.
 Transceiver/media interfaces available:  MII.
Transceiver type in use:  10baseT.
 MAC settings: half-duplex.
Maximum packet size is 0.
 Station address set to 00:60:08:9f:d6:5d.
 Configuration options 4000.
root@mug:~#             /usr/local/sbin/vortex-diag -m
vortex-diag.c:v1.09 7/28/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a 3c905 Boomerang 100baseTx adapter at 0xd800.
 MII PHY found at address 24, status 7849.
 MII PHY 0 at #24 transceiver registers:
   3100 7849 2000 5c01 01e1 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0001 8060
   8020 0c58 0000 3800 a3b9 0080 8005 001d.
root@mug:~# 

Using a slightly edited insmod line from
http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
I get 

root@mug:~# /sbin/insmod 3c59x.o debug=1 options=0 full_duplex=0
3c59x.o: 3c59x.o: No such file or directory
root@mug:~# /sbin/insmod 3c59x debug=1 options=0 full_duplex=0
root@mug:~#
with messages of:
Mar  6 20:03:39 mug kernel: 3c59x.c:v0.99H 11/17/98 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
Mar  6 20:03:39 mug kernel: eth1: 3Com 3c905 Boomerang 100baseTx at
0xd800,  00:60:08:9f:d6:5d, IRQ 12
Mar  6 20:03:39 mug kernel:   8K word-wide RAM 3:5 Rx:Tx split,
autoselect/MII interface.
Mar  6 20:03:39 mug kernel:   Media override to transceiver type 0
(10baseT).
Mar  6 20:03:39 mug kernel:   Enabling bus-master transmits and
whole-frame receives.

With no options, I get:
root@mug:~# /sbin/insmod 3c59x debug=1                       
root@mug:~# 

And messages of:

Mar  6 20:06:39 mug kernel: 3c59x.c:v0.99H 11/17/98 Donald
Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
Mar  6 20:06:39 mug kernel: eth1: 3Com 3c905 Boomerang 100baseTx at
0xd800,  00:60:08:9f:d6:5d, IRQ 12
Mar  6 20:06:39 mug kernel:   8K word-wide RAM 3:5 Rx:Tx split,
autoselect/MII interface.
Mar  6 20:06:39 mug kernel:   MII transceiver found at address 24, status
7849.
Mar  6 20:06:39 mug kernel:   Enabling bus-master transmits and
whole-frame receives.


As to whether it is properly configured, I would suppose not, since it
doen't seem to to work.  However, I did try the 3com program, and it
seemed to configure/test fine.  


On Sat, 4 Mar 2000, Paul wrote:

> Have you properly configured the card?
> (Using 3com's 3c90xcfg.exe program)
> Try setting it to autoselect.
> 
> Paul
> 
> -----Original Message-----
> From: David Forrest <drf5n@mug.sys.virginia.edu>
> To: linux-vortex-bug@beowulf.gsfc.nasa.gov
> <linux-vortex-bug@beowulf.gsfc.nasa.gov>
> Date: Saturday, March 04, 2000 12:50 AM
> Subject: PROBLEM: 3C905/2.2.15pre11 everything but working
> 
> 
> >Dear Sir or Madam,
> >  I am currently trying to install my 3Com 3C905-TX (FCC DF68C905-TX) into
> >my linux box.  Everything seems to install OK, except that the lights
> >don't light, and the packets don't pack.
> >
> >It recognizes the card, interrupt and memory (IRQ10, 0xd8000), ifconfig
> >works, and my routes were set up, but I can't ping anything and the lights
> >remain dim.
> >
> >I have connected it to a 10BT hub, and a 100TX switch with various cables
> >which work with other cards, but this card does not seem to communicate.
> >
> >I tried the 3c59x.c:v0.99L driver also, and continued to have the same
> >problem.
> >
> >vortex-diag seemed pretty happy, I failed to capture the outputs.
> >
> >I yanked the card and put in an ISA 10BT, but I could re-try the 3C905 if
> >I had a clue about what to try next.
> >
> >Does anyone have any guidance?
> >
> >Dave.
> >--
> > Dave Forrest                                dforrest@virginia.edu
> > (804)296-7283h 924-3954w   http://www.people.virginia.edu/~drf5n/
> >
> >-------------------------------------------------------------------
> >To unsubscribe send a message body containing "unsubscribe"
> >to linux-vortex-bug-request@beowulf.org
> >
> 

-- 
 Dave Forrest                                dforrest@virginia.edu
 (804)296-7283h 924-3954w   http://www.people.virginia.edu/~drf5n/

-------------------------------------------------------------------
To unsubscribe send a message body containing "unsubscribe"
to linux-vortex-bug-request@beowulf.org