3C905B support
On BeOS my 3C905 Card is not recognized. It works in Linux and Syllable.
I did try to put it into PCI slot 1 and 3 and 4.
instead of ec9xx driver I did try the 3c920 driver. No Use.
Tried Bone. Did not help.
Is there a source code available for this device driver (Ex ec9xx) so that I maybe can see what is the problem.
Yes. It is a 3C905B Card. (OR rather probably a 3C950-Combo) This is the outpot from my messgae log file starting up Linux:
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:00:0f.0:
3Com PCI 3c905B Cyclone 10/100/BNC at 0x1000. Vers LK1.1.19
I run BEOS PE 5
Somewhere I read that the BEOS driver works only if the card is on IRQ 5.
Mine on linux is put to IRQ 10.
Actually I read on the 3COM support that with the PCI card one can only change the IRQ settings by moving it into a different PCI slot. Maybe on my DELL computer I do not hit the right IRQ.
Comments
3C905B support
BeOS or Haiku? I never had a problem with my 3C905b card in BeOS 4 or 5.
3C905B support
Ditto, I've never had problems with my 3C905b... I've also never had problems with my 3c905c card at home - but my one 3c905c-tx card on my previous workstation at work did NOT properly work in R5 or BONE. Apparently they changed something on the chipset that prevents the built-in driver from working any longer with those cards.
3C905B support
Perhaps 3com pulled a stunt like ATI does and change the PCI ID number of a card while keeping the same model number. I remember getting an ATI Rage Fury Pro that was on the R5 hardware list but wasn't recognized. It took a slightly hacked driver to recongize the card. Maybe this is the case here?
3C905B support
yeh I've had exactly the same issue as umccullough has had ...
3C905B support
No, it was even more sinister.
The card was recognized by BeOS, and appeared to be working - but generated absolutely no traffic whatsoever... DHCP failed, ICMP failed, etc.