solved. thanx!
LINT added an explanation of the miibus driver requirement.
I did the basic configuration from the 17 Apr LINT file and
missed the change when I updated, even though I diff LINT
when it updates. see diff below.
As they say: RTFS... carefully.
attila out!
--
No, I don't suffer from insanity; I enjoy every minute of it!
< is LINT prior to 18 Apr
> is LINT after 18 Apr which tells you WHY you need 'miibus'
168d1823
< device miibus # MII bus support
179,218c1834,2227
> # MII bus support is required for some PCI 10/100 ethernet NICs,
> # namely those which use MII-compliant transceivers or implement
> # tranceiver control interfaces that operate like an MII. Adding
> # "device miibus0" to the kernel config pulls in support for
> # the generic miibus API and all of the PHY drivers, including a
> # generic one for PHYs that aren't specifically handled by an
> # individual driver.
> device miibus
on Wed, 19 Apr 2000 23:18:08 -0700 (PDT), Jaye Mathisen:
You need the device mii or miibus in your kernel config file, and I think
it generates it.
Look at a GENERIC near the dc driver in the later releases, and you'll see
it added, or grep for mii in LINT/GENERIC.
On Thu, 20 Apr 2000, attila! wrote:
>
> > ../../pci/if_dc.c:151: miibus_if.h: No such file or directory
> > mkdep: compile failed
>
> 'find' on entire sys subsystem fails to show it, and I
> pulled cvsups on 19th and 20th to see if it was in the
> stream --nope. pulled a 'glimpse' of 'current' list but
> found no reference.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
