Solaris / OpenSolarisThis forum is for the discussion of Solaris and OpenSolaris.
General Sun, SunOS and Sparc related questions also go here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Distribution: Solaris & OpenSolaris based distros, Ubuntu
Posts: 8,134
Thanked: 86
Sorry, I overlook you were using Solaris 9. scanpci is from Solaris 10 only.
When you write ifconfig -a plumb yeld nothing, do you mean you checked the interface presence with ifconfig -a after and the e1000g still does not show up ?
As an alternative for scanpci, post the result of:
I noticed in another Thread the use of "devfsadm" which
I tried with the following results:
Code:
# devfsadm -v
Jul 25 11:12:34 hwz-v60 re1000: WARNING: couldn't allocate 83886080 bytes. driver will NOT function. please reboot.
Jul 25 11:12:34 hwz-v60 re1000: WARNING: couldn't reserve 81920K for re1000g0!
Jul 25 11:12:35 hwz-v60 re1000: WARNING: couldn't allocate 83886080 bytes. driver will NOT function. please reboot.
Jul 25 11:12:35 hwz-v60 re1000: WARNING: couldn't reserve 81920K for re1000g1!
Jul 25 11:12:35 hwz-v60 re1000: WARNING: couldn't allocate 83886080 bytes. driver will NOT function. please reboot.
Jul 25 11:12:35 hwz-v60 re1000: WARNING: couldn't reserve 81920K for re1000g2!
Jul 25 11:12:35 hwz-v60 re1000: WARNING: couldn't allocate 83886080 bytes. driver will NOT function. please reboot.
Jul 25 11:12:35 hwz-v60 re1000: WARNING: couldn't reserve 81920K for re1000g3!
Jul 25 11:12:36 hwz-v60 re1000: WARNING: couldn't allocate 83886080 bytes. driver will NOT function. please reboot.
Jul 25 11:12:36 hwz-v60 re1000: WARNING: couldn't reserve 81920K for re1000g4!
It appears as though my driver isn't working. I'll reboot the system. If this doesn't do the trick, I'll replace the driver and let you know! Unless there is a better suggestion out there!
Last edited by slionelharris; 07-26-2007 at 12:58 PM..
Reason: Clean up.
So, I rebooted the machine, and re-ran devfsadm -v. This
time, it reported, in effect that 3 of my 5 interfaces
weren't configured and mentioned that I should modify
the /kernel/drv/re1000g.conf file. There I changed the
number of interfaces to 5, and rebooted the machine.
When completed I re-issued the devfsadm -v command. This
time "devfsadm" did it's thing by creating the dev files for
the remaining 3 interfaces. However, I still cannot plumb
any of the interfaces and ifconfig -a reports only the "loopback" interface and
nothing more. Please see below:
Code:
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.