Re: driver not attached

From: Huub (v.niekerk_at_freeler.nl)
Date: 02/21/05 

Date: Mon, 21 Feb 2005 19:22:12 +0100

Andrew Gabriel wrote:
> In article <42196e1f$0$154$3a628fcd@reader2.nntp.hccnet.nl>,
> Huub <v.niekerk@freeler.nl> writes:
>
>>Andrew Gabriel wrote:
>>
>>>In article <4218e8d7$0$769$3a628fcd@reader10.nntp.hccnet.nl>,
>>> Huub <v.niekerk@freeler.nl> writes:
>>>
>>>
>>>>Hi,
>>>>
>>>>Just installed Sol9, x86. Now I have to find the instance number to get
>>>>my NIC working (BCM5702). I installed the driver (pkgadd), but using
>>>>prtconf, it says the driver is not attached. I've installed the correct
>>>>driver from Broadcom. What should I do next?
>>>>Any help appreciated.
>>>
>>>
>>>Check it has added some 'bcme' entries to /etc/driver_aliases.
>>>Run: devfsadm -v -i bcme
>>>If you still don't have /dev/bcme* then, it the driver doesn't
>>>support your hardware. You could look in the prtconf -pv output
>>>to find the pci ID and explicitly add it:
>>>update_drv -a -i '"pciXXXX,YYYY"' bcme
>>>and it might then work.
>>>
>>>If it still doesn't, try using Sun's broadcom driver. You will
>>>need to delete the pci id: update_drv -d -i '"pciXXXX,YYYY"' bcme
>>>and add id to the bge driver: update_drv -a -i '"pciXXXX,YYYY"' bge
>>>and you should get should get /dev/bge* instead. I'm not sure if
>>>Sun's driver supports 5702 though.
>>>
>>
>>/etc/driver_aliases shows many entrances of bcme. How do I know which
>>one to use with plumb?
>
>
> Um, that question doesn't make sense. /etc/driver_aliases is the
> file which tells the kernel to attach the bcme driver to any PCI
> device it finds with matching PCI ID. The driver will then create
> /dev/bcme (via devfsadm). If you haven't got a /dev/bcme, then
> the driver you installed is not designed to drive your BCM5702.
> You could try forcing it to, using the method I described above.
> That may or may not work, depending how similar your BCM5702 is to
> the ones the driver was designed for.
>
I found out I do have a /dev/bcme. But according to the .txt for the
driver, I have to use an instance-number. So how can I figure out what
number to use so I can create the hostname.bcme?

Relevant Pages

  • Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"
    ... 2.6.23-rc1 I have trouble with my network connection. ... # Bus options (PCI, PCMCIA, EISA, MCA, ISA) ... # PCCARD support ... # Generic Driver Options ...
    (Linux-Kernel)
  • IDE:PORTS ALREADY IN USE | USB: irq 11: nobody cared! | loop pcmcia_core.ko which needs pcmcia_core.
    ... VP_IDE: IDE controller at PCI slot 0000:00:11.1 ... USB no longer working. ... irq 11: nobody cared! ... 15 nodes reported by PnP BIOS; 15 recorded by driver ...
    (Linux-Kernel)
  • only a single core (out of 8) initialized
    ... this is 2.6.30-rc7 with a patch added to debug a nv sata driver incompatibility with the Intel SSDs on a tyan motherboard ... kernel direct mapping tables up to d7fd0000 @ 10000-16000 ... Allocating PCI resources starting at f1000000 ... CPU: L2 Cache: 1024K ...
    (Linux-Kernel)
  • 2.6.15-rc5-mm2 does not boot on AMD64 with sata_sil
    ... Using ACPI for IRQ routing ... Uniform CD-ROM driver Revision: 3.20 ... Using ACPI for SMP configuration information Allocating PCI resources starting at e2000000 Checking aperture... ... Real Time Clock Driver v1.12 hw_random: AMD768 system management I/O registers at 0x8000. ...
    (Linux-Kernel)
  • Re: Enumerable I2C busses
    ... :> that will translate the OF provided properties into FreeBSD driver ... additional glue to allow the ofw_iicbus driver to attach. ... The third option is to do what we do for pci, ... If ofw_iicbus is simply an OF-aware version of iicbus (i.e. same ...
    (freebsd-arch)