Date: Wed, 31 Jul 1996 20:05:56 -0700 (PDT) From: Doug White <dwhite@riley-net170-164.uoregon.edu> To: DANIEL B REID <cs932304@red.ariel.cs.yorku.ca> Cc: questions@freebsd.org Subject: Re: 3com not detected Message-ID: <Pine.BSI.3.94.960731200114.264C-100000@gdi.uoregon.edu> In-Reply-To: <Pine.SOL.3.95.960731135754.13362A-100000@red>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 31 Jul 1996, DANIEL B REID wrote: > at startup: eth0 eth1 do not detect my 3com card. eth0 is not a FreeBSD device, it's a Linux device. :-/ You say below you have a 3c503. That is device ed0; Look for 'ed0' during the boot sequence. How about mailing us your dmesg output? (dmesg outputs the kernel messages, including the boot messages) > I have it jumperd to 0x300, and have probed at irq 10 and 5 > The card should be working fine but I've not ruled out a damaged > card yet. this card is not pci. I had a pci card but my adaptec > scsi adapter/ 2gb hard drive would not respond to bsd so I switched. Interrupt conflict, I'd bet. > Q: what else can I try in order to get my card recognised 3c503 ? 50_3_? Urk. Old hardware. :( Double check the ed0 settings? > Q: must I configure / compile my own kernel? That is a good idea anyway -- GENERIC has a bit of fluff in it and compiling your own kernel can make it smaller and faster. > Q: are there any known hardware conflicts between adaptec and 3com? Not known, AFAIK. > Q: any other suggestions? Post dmesg, kernel config, and 3c503 configuration. You _must_ know the settings of the 3c503 or you won't be successful. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.94.960731200114.264C-100000>