Hi,
On Tue, 2003-02-25 at 00:07, Daxbert wrote:
> Quoting Stacey Roberts <[EMAIL PROTECTED]>:
>
> > On Mon, 2003-02-24 at 23:35, Daxbert wrote:
> > > Quoting Stacey Roberts <[EMAIL PROTECTED]>:
> > >
> > > > Intel Pro100S
> > > > 3COM OfficeConnect (3CSOHO100B)
> > > >
> > > > At installation, I had the Intel (fxp0) connected to the switch, and it
> > > > was configured during the sysinstall stage. However, the 3COM nic never
> > > > showed up after installation in dmesg (as far as I can tell, that is):
> > > >
> > > > But the 3COM *is* picked up from scanpci:
> > > >
> > > > pci bus 0x0000 cardnum 0x0a function 0x00: vendor 0x10b7 device 0x9300
> > > > 3COM Device unknown
> > > > CardVendor 0x10b7 card 0x9300 (3COM, Card unknown)
> > > >
> > > > Am I missing something?
> > > >
> > >
> > > It would appear that from /usr/src/sys/pci/if_xlreg.h that the device id
> > 0x9300
> > > is not present. Because a reference for 0x9300 doesn't exist, you will
> > have an
> > > unknown 'card', and it won't use the driver.
> > >
> >
> > I was just doing a search around FreeBSD tech sites and actually, this
> > *specific* nic - 3CSOHO100B-TX isn't actually listed. What *is* listed
> > in the Handbook is:
> >
> > 3cSOHO100-TX OfficeConnect adapter <-- WHERE I WENT WRONG>>>>>>>>>>>>>>
> >
> > In looking man xl(4) though, 3cSOHO100-TX OfficeConnect isn't even
> > mentioned, far less for 3CSOHO100B-TX. So it appears that I've not done
> > my homework on this one :-(
> >
> > > I've never done this... but one option would be to edit if_xlreg.h and
> > *add*
> > > support for your card and recompile and install the new kernel.
> >
> > Man.., I'd like to get this working.., but I'm not sure about editing
> > those files - not a programmer, you see. Is the HURRICANE_SOHOTX
> > actually the one to edit, for instance?
> >
>
> In a previous email I mentioned my logic behind picking the HURRICANE SOHO,
> because it was the only one which mentioned SOHO in the name.
>
> I did some further research (google: 0x9300 SOHO) and found that this card isn't
> based on the HURRICANE chipset at all:
>
> http://www.tux.org/hypermail/linux-vortex/2002-Dec/0054.html
>
> the author mentions that it's a 'tulip' based card. Tulip is a DEC
> ASIC. First make sure the de driver is enabled, and disable your existing xl
> driver. And hope for the best.
>
> If it's still undetected... you'd need to hack into the tulip files... I'd
> recommend this if you are comfortable with booting alternate kernels. That way,
> if you break the kernel it's not a big deal.
>
Tried replacing the xl driver with the de one, but the 3COM is still not
getting picked up:
# uname -a
FreeBSD crom.vickiandstacey.com 4.7-STABLE FreeBSD 4.7-STABLE #0: Tue
Feb 25 00:36:08 GMT 2003
[EMAIL PROTECTED]:/usr/src/sys/compile/TYAN i386
~ #
# dmesg | grep -i intel
CPU: Intel(R) Pentium(R) III CPU family 1133MHz (1132.96-MHz
686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1
fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0xdc00-0xdc3f mem
0xfb000000-0xfb0fffff,0xfb100000-0xfb100fff irq 5 at device 9.0 on pci0
~ # dmesg | grep -i 3com
~ #
Its still there in pciconf, though:
[EMAIL PROTECTED]:10:0: class=0x020000 card=0x930010b7 chip=0x930010b7 rev=0x31
hdr=0x00
vendor = '3COM Corp, Networking Division'
class = network
subclass = ethernet
and scanpci sees it as well:
pci bus 0x0000 cardnum 0x0a function 0x00: vendor 0x10b7 device 0x9300
3COM Device unknown
CardVendor 0x10b7 card 0x9300 (3COM, Card unknown)
STATUS 0x0290 COMMAND 0x0007
CLASS 0x02 0x00 0x00 REVISION 0x31
BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x08
BASE0 0x0000e001 addr 0x0000e000 I/O
BASE1 0xfb101000 addr 0xfb101000 MEM
MAX_LAT 0x80 MIN_GNT 0x40 INT_PIN 0x01 INT_LINE 0x0a
Not sure about hacking the tulip driver on my own though. If anyone is
willing to guide me through this, I'll gladly give this a go.
Thanks Daxbert, for all the pointers..,
Regards,
Stacey
> if_de.c and if_devar.h (both in /usr/src/sys/pci) are the files in question.
>
> good luck
>
> --daxbert
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message
--
Stacey Roberts
B.Sc (HONS) Computer Science
Web: www.vickiandstacey.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
