LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Other *NIX Forums > Solaris / OpenSolaris
User Name
Password
Solaris / OpenSolaris This forum is for the discussion of Solaris and OpenSolaris.
General Sun, SunOS and Sparc related questions also go here.

Notices

Reply
 
Search this Thread
Old 07-24-2007, 12:29 PM   #1
slionelharris
LQ Newbie
 
Registered: Mar 2007
Posts: 13

Rep: Reputation: 0
Post Can't plumb NIC


When I do:
ifconfig -a I get the following...

lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000

I have 2 internal NIC's and 2 PCI NIC's.
The following is the dev file and kernel driver.

/dev/e1000g and /kernel/drv/e1000g

When I do:

ifconfig /dev/e1000g plumb ...The response is...

ifconfig: plumb: /dev/e1000g: No such file or directory

The NIC's appear to be of the right flavor ... Intel Pro 1000.
I would appreciate any help with this.
 
Old 07-24-2007, 01:54 PM   #2
jlliagre
Moderator
 
Registered: Feb 2004
Location: Outside Paris
Distribution: Solaris10, Solaris 11, Mint, OL
Posts: 9,499

Rep: Reputation: 355Reputation: 355Reputation: 355Reputation: 355
The command should be:
Code:
ifconfig e1000g0 plumb
 
Old 07-24-2007, 04:07 PM   #3
slionelharris
LQ Newbie
 
Registered: Mar 2007
Posts: 13

Original Poster
Rep: Reputation: 0
Can't plumb NIC.

Thanks for your reply. Here are the results:

ifconfig e1000g0 plumb
ifconfig: plumb: e1000g0: No such file or directory

BTW: Here are some machine/OS particulars:

# uname -X
System = SunOS
Node = hwz-v60
Release = 5.9
KernelID = Generic_112234-07
Machine = i86pc
BusType = <unknown>
Serial = <unknown>
Users = <unknown>
OEM# = 0
Origin# = 1
NumCPU = 4

Last edited by slionelharris; 07-24-2007 at 04:51 PM.
 
Old 07-24-2007, 04:22 PM   #4
Necronomicom
Member
 
Registered: Jun 2004
Distribution: Slackware, Solaris
Posts: 127

Rep: Reputation: 15
do a grep e1000g /etc/path_to_inst, see what it shows
 
Old 07-25-2007, 02:08 AM   #5
jlliagre
Moderator
 
Registered: Feb 2004
Location: Outside Paris
Distribution: Solaris10, Solaris 11, Mint, OL
Posts: 9,499

Rep: Reputation: 355Reputation: 355Reputation: 355Reputation: 355
Your NIC isn't recognized.

In addition to what Necronomicom suggests, try
Code:
ifconfig -a plumb
If nothing shows up, run
Code:
/usr/X11/bin/scanpci
and post the output.
 
Old 07-25-2007, 10:59 AM   #6
slionelharris
LQ Newbie
 
Registered: Mar 2007
Posts: 13

Original Poster
Rep: Reputation: 0
Necronomicom: Thank you for your reply. Here are the results:

# grep e1000g /etc/path_to_inst
"/pci@0,0/pci8086,2545@3/pci8086,1460@1f/pci8086,341a@7" 0 "e1000g"
"/pci@0,0/pci8086,2545@3/pci8086,1460@1f/pci8086,341a@7,1" 1 "e1000g"


How does one read this HW path?


jlliagre: Thank you for your reply. As per your suggestions:

ifconfig -a plumb Yielded nothing. The 2nd suggestion:

/usr/X11/bin/scanpci

No such file or directory scanpci doesn't live on this system, even under
/usr/openwin/bin.
 
Old 07-25-2007, 11:51 AM   #7
jlliagre
Moderator
 
Registered: Feb 2004
Location: Outside Paris
Distribution: Solaris10, Solaris 11, Mint, OL
Posts: 9,499

Rep: Reputation: 355Reputation: 355Reputation: 355Reputation: 355
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:
Code:
prtconf -vp | grep pci

Last edited by jlliagre; 07-25-2007 at 11:54 AM.
 
Old 07-25-2007, 01:05 PM   #8
slionelharris
LQ Newbie
 
Registered: Mar 2007
Posts: 13

Original Poster
Rep: Reputation: 0
Can't plumb NIC.

jlliagre:
In answer to your question:
The 1st time I tried it, the system responded with nothing.
I tried it the 2nd time and this is the result:
Code:
# ifconfig -a plumb 
ifconfig: plumb: llc2: no such interface
Then:
Code:
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
I then tried: prtconf -vp | grep pci with the following results:
Code:
prtconf -vp | grep pci
 screen:  '/pci@0,0/pci8086,244e@1e/display@c'
        bios-primary:  '/pci@0,0/pci8086,2545@3/pci8086,1460@1d/pci8086,341a@7,1/sd@1,0'
        boot-path:  '/pci@0,0/pci8086,2545@3/pci8086,1460@1d/pci8086,341a@7,1/sd@1,0:a'
        bootpath:  '/pci@0,0/pci8086,2545@3/pci8086,1460@1d/pci8086,341a@7,1/sd@1,0:a'
        boot-device:  '/pci@0,0/pci8086,2545@3/pci8086,1460@1d/pci8086,341a@7,1/sd@1,0'
        boot-path:  '/pci@0,0/pci8086,2545@3/pci8086,1460@1d/pci8086,341a@7,1/sd@1,0:a'
        bootpath:  '/pci@0,0/pci8086,2545@3/pci8086,1460@1d/pci8086,341a@7,1/sd@1,0:a'
        pciide:  'true'
        device_type:  'pci'
        name:  'pci'
            compatible: 'pci8086,341a' + 'pci8086,341a' + 'pci8086,254c' + 'pciclass,060000'
            name:  'pci8086,341a'
            compatible: 'pci8086,341a' + 'pci8086,341a' + 'pci8086,2541' + 'pciclass,ff0000'
            model:  'PCI: 8086,341a - class: Unknown class of pci/pnpbios device'
            name:  'pci8086,341a'
            compatible: 'pci8086,2545' + 'pci8086,2545' + 'pciclass,060400'
            device_type:  'pci'
            name:  'pci8086,2545'
                compatible: 'pci8086,341a' + 'pci8086,341a' + 'pci8086,1461' + 'pciclass,080020'
                model:  'PCI: 8086,341a - class: Unknown class of pci/pnpbios device'
                name:  'pci8086,341a'
                compatible: 'pci8086,1460' + 'pci8086,1460' + 'pciclass,060400'
                device_type:  'pci'
                name:  'pci8086,1460'
                    compatible: 'pci8086,341a' + 'pci8086,341a' + 'pci9005,801f' + 'pciclass,010000'
                    name:  'pci8086,341a'
                    compatible: 'pci8086,341a' + 'pci8086,341a' + 'pci9005,801f' + 'pciclass,010000'
                    name:  'pci8086,341a'
                    compatible: 'pci8086,1012' + 'pci8086,1012' + 'pci8086,1012' + 'pciclass,020000'
                    name:  'pci8086,1012'
                    compatible: 'pci8086,1012' + 'pci8086,1012' + 'pci8086,1012' + 'pciclass,020000'
                    name:  'pci8086,1012'
                compatible: 'pci8086,341a' + 'pci8086,341a' + 'pci8086,1461' + 'pciclass,080020'
                model:  'PCI: 8086,341a - class: Unknown class of pci/pnpbios device'
                name:  'pci8086,341a'
                compatible: 'pci8086,1460' + 'pci8086,1460' + 'pciclass,060400'
                device_type:  'pci'
                name:  'pci8086,1460'
                    compatible: 'pci8086,341a' + 'pci8086,341a' + 'pci8086,1010' + 'pciclass,020000'
                    name:  'pci8086,341a'
                    compatible: 'pci8086,341a' + 'pci8086,341a' + 'pci8086,1010' + 'pciclass,020000'
                    name:  'pci8086,341a'
                    compatible: 'pci8086,1001' + 'pci8086,1001' + 'pci8086,1026' + 'pciclass,020000'
                    name:  'pci8086,1001'
            compatible: 'pci8086,341a' + 'pci8086,341a' + 'pci8086,2546' + 'pciclass,ff0000'
            model:  'PCI: 8086,341a - class: Unknown class of pci/pnpbios device'
            name:  'pci8086,341a'
            compatible: 'pci8086,341a' + 'pci8086,341a' + 'pci8086,2482' + 'pciclass,0c0300'
            name:  'pci8086,341a'
            compatible: 'pci8086,341a' + 'pci8086,341a' + 'pci8086,2484' + 'pciclass,0c0300'
            name:  'pci8086,341a'
            compatible: 'pci8086,244e' + 'pci8086,244e' + 'pciclass,060400'
            device_type:  'pci'
            name:  'pci8086,244e'
                compatible: 'display' + 'pci8086,341a' + 'pci1002,4752' + 'pciclass,030000'
            compatible: 'pci8086,2480' + 'pci8086,2480' + 'pciclass,060100'
            name:  'pci8086,2480'
            compatible: 'pci-ide' + 'pci8086,341a' + 'pci8086,248b' + 'pciclass,01018a'
            device_type:  'pci-ide'
            name:  'pci-ide'
            compatible: 'pci8086,341a' + 'pci8086,341a' + 'pci8086,2483' + 'pciclass,0c0500'
            model:  'PCI: 8086,341a - class: Unknown class of pci/pnpbios device'
            name:  'pci8086,341a'
 
Thanks!

Last edited by slionelharris; 07-26-2007 at 11:57 AM. Reason: Clean up.
 
Old 07-25-2007, 01:22 PM   #9
slionelharris
LQ Newbie
 
Registered: Mar 2007
Posts: 13

Original Poster
Rep: Reputation: 0
Can't plumb NIC.

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 11:58 AM. Reason: Clean up.
 
Old 07-26-2007, 11:32 AM   #10
slionelharris
LQ Newbie
 
Registered: Mar 2007
Posts: 13

Original Poster
Rep: Reputation: 0
Can't plumb NIC, (Progress report)

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 
Any ideas?

Your help is greatly appreciated.
 
Old 07-26-2007, 01:59 PM   #11
jlliagre
Moderator
 
Registered: Feb 2004
Location: Outside Paris
Distribution: Solaris10, Solaris 11, Mint, OL
Posts: 9,499

Rep: Reputation: 355Reputation: 355Reputation: 355Reputation: 355
Is this driver bundled with Solaris 9 or do you get it elsewhere ?

I know about e1000g, but not re1000g.
 
Old 07-26-2007, 02:23 PM   #12
slionelharris
LQ Newbie
 
Registered: Mar 2007
Posts: 13

Original Poster
Rep: Reputation: 0
Yes, this driver came bundled with the OS.
 
Old 07-26-2007, 03:37 PM   #13
jlliagre
Moderator
 
Registered: Feb 2004
Location: Outside Paris
Distribution: Solaris10, Solaris 11, Mint, OL
Posts: 9,499

Rep: Reputation: 355Reputation: 355Reputation: 355Reputation: 355
Okay, what says:
Code:
grep re1000g /etc/path_to_inst /etc/driver_aliases /var/sadm/install/contents
 
Old 07-27-2007, 09:24 AM   #14
slionelharris
LQ Newbie
 
Registered: Mar 2007
Posts: 13

Original Poster
Rep: Reputation: 0
It comes back with nothing.
 
Old 07-27-2007, 11:33 AM   #15
jlliagre
Moderator
 
Registered: Feb 2004
Location: Outside Paris
Distribution: Solaris10, Solaris 11, Mint, OL
Posts: 9,499

Rep: Reputation: 355Reputation: 355Reputation: 355Reputation: 355
This seems to contradict the posting where you wrote this driver comes bundled with Solaris.

Who created the /kernel/drv/re1000g.conf file ?

There is no reference to this "r" prefix for the e1000g driver in its documentation.

Last edited by jlliagre; 07-27-2007 at 11:38 AM.
 
  


Reply

Tags
ifconfig, sun


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
NIC Bonding: Does not failover successfully. Only one NIC is active Akhran Debian 2 02-18-2011 07:26 PM
eth0 NIC Card Not Working! 3com 3c501 NIC. Mustard010 Linux - Networking 16 08-15-2007 02:22 AM
about ifconfig hme1 plumb .... jsnch Solaris / OpenSolaris 3 07-07-2005 02:04 PM
troubles getting Gigabit NIC to work in slack 10 (HGA32T NIC) TheLinuxDuck Slackware 10 03-10-2005 04:37 PM
1st nic regular FTP, 2nd nic SSH Riselong Linux - Distributions 2 02-02-2004 05:13 PM


All times are GMT -5. The time now is 09:29 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration