Re: Adding a 3Com NIC to Solaris 9 x86 9/04

From: Andrew Gabriel (andrew_at_cucumber.demon.co.uk)
Date: 10/30/04

  • Next message: alan pae: "Re: Small Business Accounting Software" 
    Date: 29 Oct 2004 22:41:35 GMT

    In article <4182A051.1000902@uiowa.edu>,
            R Holdaway <robert-SPAM-holdaway@uiowa.edu> writes:
    > Hi,
    >
    > I am attempting to install a 3Com 3C905C-TX-M NIC in a Dell Optiplex GX280.
    >
    > I install the OS without the NIC okay. (I get 2 warnings about
    > ACPI/non-ACPI devices. The hard disk will boot after acpi is turned off
    > using eeprom.)
    >
    > So far so good.
    >
    > I add the line:
    > pci10b7,1000 pci10b7,1000 net pci elxl.bef "3Com 3C905C-TX-M"
    > to /boot/solaris/devicedb/master.

    Are you sure pci10b7,1000 is a 3C905?
    Doesn't look much like any of the known 3C905 pciids.

    > Then I add the line:
    > elxl "pci10b7,1000"
    > to /etc/driver_aliases.
    >
    > Next I install the NIC and reboot: (b -r).
    > In the DCA the card is recognised showing my label: "3Com 3C905C-TX-M".
    >
    > But the device files are not installed during the reconfiguration boot.
    > So I type "devfsadm -i elxl" and get the failure to attach error message.

    Are there any messages on the console or in /var/adm/messages saying
    why the driver failed to attach?

    Will the module even load into the kernel without errors:
    modload /kernel/drv/elxl

    > I can see the device under 'pci8086,244e' in 'prtconf -D', but this
    > never shows up in the device tree, /devices/pci@0,0.

    pci8086,244e is a PCI bridge -- creating a new PCI bus on
    the other side of it. 

    -- 
Andrew Gabriel
Consultant Software Engineer
  • Next message: alan pae: "Re: Small Business Accounting Software"
    • Quantcast