Date: Tue, 24 Nov 1998 20:19:16 -0500 From: "Stephen Comoletti" <stevec@delanet.com> To: "root" <root@jtrevick.student.simons-rock.edu>, "Kaleb S. KEITHLEY" <kaleb@ics.com> Cc: <questions@FreeBSD.ORG>, <hackers@FreeBSD.ORG> Subject: Re: Linksys NIC, was: Re: de ethernet driver -- another puzzle Message-ID: <003901be1811$a2777140$118809d0@oemcomputer>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
------=_NextPart_000_0031_01BE17E7.B5A31280
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Which model? I have a Lynksys 10bt in a 3.0 box running fine. I had to use a
win95/98 boot disk with the lynksys setup util on it..but other than that it
runs fine. BSD recognizes it as a KTI card however. I've noticed win95 and 98
both see it as a KTI as well.
>
>Out of curiosity, If I have a Linksys NIC and want to do a FTP install of
>FreeBSD, how would I go about it since support isnt config'ed into the
>kernel
>
>On Tue, 24 Nov 1998, Kaleb S. KEITHLEY wrote:
>
>> Joel Ray Holveck wrote:
>> >
>> > >>> I also now know why the de probe doesn't print out a message when the
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> > >>> probe fails. Which is not to say that I think that's good. On the
>> > >>> contrary, I think it's bad. C'est la vie.
>> > >> Printing out an error message when a PCI match fails would be stupid;
>>
>> Yup; but then I said as much.
>>
>> > >> every PCI device is (currently) presented to every PCI driver until one
>> > >> claims it. Printing a message when the match failed ("no, not for me")
>> > >> would produce a useless spew of garbage.
>> > > You need a pseudo-device at the end of the inquiry chain to catch
>> > > id's that haven't been caught by the real drivers, and to print
>> > > out a message ("PCI: no driver: id xxx ...").
>> >
>> > That's catching the wrong set.
>>
>> Yes and no.
>>
>> > Kaleb wanted the to know the drivers without cards.
>>
>> Not really. I wanted to know why the de driver wasn't recognizing my
>> NIC. According to the FAQ and the Handbook it is supposed to be the
>> driver for my card. Turns out it's not, but there ought to be a better
>> way to discover this than by sprinkling the kernel with printfs, or
>> try-each-one-until-one-succeeds, or
>> turn-everything-on-to-discover-which-it-is.
>>
>> > You're giving us the set of cards without drivers.
>> > (This is also possibly a useful set, but not what kaleb wanted.)
>>
>> Seems to me -- from the cursory look-see that I took while figuring out
>> my card -- that the PCI ethernet stuff could be unified into something
>> like a single pci (pseudo?) ethernet device. That could be fun to hack
>> on.
>>
>>
>> --
>> Kaleb
>>
>> To Unsubscribe: send mail to majordomo@FreeBSD.org
>> with "unsubscribe freebsd-questions" in the body of the message
>>
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-questions" in the body of the message
>
------=_NextPart_000_0031_01BE17E7.B5A31280
Content-Type: text/x-vcard;
name="Stephen C. Comoletti.vcf"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="Stephen C. Comoletti.vcf"
BEGIN:VCARD
VERSION:2.1
N:Comoletti;Stephen;C.
FN:Stephen C. Comoletti
ORG:DelaNET, Inc.
TITLE:Asst. Systems Administrator
TEL;WORK;VOICE:(302) 326-5800 / (888) DELANET
TEL;WORK;FAX:(302) 326-5802
ADR;WORK:;;262 Quigley Boulevard;New Castle;DE;19720;USA
LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:262 Quigley =
Boulevard=3D0D=3D0ANew Castle, DE 19720=3D0D=3D0AUSA
URL:
URL:http://www.delanet.com/
EMAIL;PREF;INTERNET:stevec@delanet.com
REV:19981125T011915Z
END:VCARD
------=_NextPart_000_0031_01BE17E7.B5A31280--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003901be1811$a2777140$118809d0>