Solaris / OpenSolaris This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. |
|
Tags used in this thread
|
|
Popular LQ Tags
|
code
|
 |
|
02-06-2007, 05:32 AM
|
#16
|
|
Moderator
Registered: Feb 2004
Location: Outside Paris, under a rock ...
Distribution: Solaris & OpenSolaris based distros, Ubuntu
Posts: 7,510
|
[ Log in to get rid of this advertisement]
Add the following lines at the end of the menu.lst file
Code:
#
title Solaris 10 32-bit
root (hd0,0,a)
kernel /platform/i86pc/multiboot kernel/unix
module /platform/i86pc/boot_archive
And replace "default 0" by "default 2" in the fourth line.
Reboot and see if that improves.
|
|
|
|
02-06-2007, 07:21 AM
|
#17
|
|
Member
Registered: Jan 2007
Location: Mumbai
Distribution: Solaris, CentOS
Posts: 42
|
I have configured the Rhine III VIA card, and it has registered the vfe driver.
Code:
Feb 6 16:16:54 machine-p4 vfe: [ID 130221 kern.info] vfe0: VT6105 Rhine-III (vid: 0x1106, did: 0x3106, revid: 0x86)
Feb 6 16:16:54 machine-p4 vfe: [ID 682396 kern.info] vfe0: eeprom dump:
Feb 6 16:16:54 machine-p4 vfe: [ID 951234 kern.info] 0x00: 0x1500 0xb0e9 0x3b36 0x0001
Feb 6 16:16:54 machine-p4 vfe: [ID 951234 kern.info] 0x04: 0x1405 0x1186 0x3106 0x1106
Feb 6 16:16:54 machine-p4 vfe: [ID 951234 kern.info] 0x08: 0x101f 0x0000 0x0000 0x0803
Feb 6 16:16:54 machine-p4 vfe: [ID 951234 kern.info] 0x0c: 0x0e09 0x0003 0x8240 0x2173
Feb 6 16:16:54 machine-p4 vfe: [ID 451511 kern.info] vfe0: MII PHY (0x01018f45) found at 1
Feb 6 16:16:54 machine-p4 vfe: [ID 426109 kern.info] vfe0: PHY control:0, status:7849<100_BASEX_FD,100_BASEX,10_BASE_FD,10_BASE,MFPRMBLSUPR,CANAUTONEG,EXTENDED>, advert:de1<ASM_DIR,PAUSE,100BASE_TX_FD,100BASE_TX,10BASE_T_FD,10BASE_T>, lpar:0
Feb 6 16:16:54 machine-p4 vfe: [ID 716252 kern.info] vfe0: resetting PHY
Feb 6 16:16:54 machine-p4 gld: [ID 944156 kern.info] vfe0: via rhine nic driver v1.1.0: type "ether" mac address 00:15:e9:b0:36:3b
Feb 6 16:16:54 machine-p4 pci: [ID 370704 kern.info] PCI-device: pci1186,1405@a, vfe0
Feb 6 16:16:54 machine-p4 genunix: [ID 936769 kern.info] vfe0 is /pci@0,0/pci1186,1405@a
Feb 6 16:16:54 machine-p4 pcplusmp: [ID 637496 kern.info] pcplusmp: pci1106,3106 (vfe) instance 0 vector 0x12 ioapic 0x2 intin 0x12 is bound to cpu 1
Feb 6 16:16:55 machine-p4 vfe: [ID 831844 kern.info] vfe0: auto-negotiation started
Feb 6 16:17:00 machine-p4 vfe: [ID 503627 kern.warning] WARNING: vfe0: auto-negotiation failed: timeout
However my second NIC card, DLink DFE-520TX 10/100 Mbps Fast Ethernet Adapter is still not showing up in the dmesg output.
Is there any other driver that this particular card would take, or is the vfe driver good enough for it.
|
|
|
|
02-06-2007, 07:30 AM
|
#18
|
|
Moderator
Registered: Feb 2004
Location: Outside Paris, under a rock ...
Distribution: Solaris & OpenSolaris based distros, Ubuntu
Posts: 7,510
|
I can't tell.
Last time you mentioned this card, it was unplugged ...
You need to check what is reported by scanpci with the drivers installed.
|
|
|
|
02-07-2007, 04:20 AM
|
#19
|
|
Member
Registered: Jan 2007
Location: Mumbai
Distribution: Solaris, CentOS
Posts: 42
|
Output of scanpci after plugging in both the NIC's:
Code:
pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x1106 device 0x0314
VIA Technologies, Inc. P4M800CE Host Bridge
pci bus 0x0000 cardnum 0x00 function 0x01: vendor 0x1106 device 0x1314
VIA Technologies, Inc. P4M800CE Host Bridge
pci bus 0x0000 cardnum 0x00 function 0x02: vendor 0x1106 device 0x2314
VIA Technologies, Inc. P4M800CE Host Bridge
pci bus 0x0000 cardnum 0x00 function 0x03: vendor 0x1106 device 0x3208
VIA Technologies, Inc. PT890 Host Bridge
pci bus 0x0000 cardnum 0x00 function 0x04: vendor 0x1106 device 0x4314
VIA Technologies, Inc. P4M800CE Host Bridge
pci bus 0x0000 cardnum 0x00 function 0x07: vendor 0x1106 device 0x7314
VIA Technologies, Inc. P4M800CE Host Bridge
pci bus 0x0000 cardnum 0x01 function 0x00: vendor 0x1106 device 0xb198
VIA Technologies, Inc. VT8237 PCI Bridge
pci bus 0x0000 cardnum 0x0a function 0x00: vendor 0x1106 device 0x3106
VIA Technologies, Inc. VT6105 [Rhine-III]
pci bus 0x0000 cardnum 0x0f function 0x00: vendor 0x1106 device 0x3149
VIA Technologies, Inc. VIA VT6420 SATA RAID Controller
pci bus 0x0000 cardnum 0x0f function 0x01: vendor 0x1106 device 0x0571
VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE
pci bus 0x0000 cardnum 0x10 function 0x00: vendor 0x1106 device 0x3038
VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
pci bus 0x0000 cardnum 0x10 function 0x01: vendor 0x1106 device 0x3038
VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
pci bus 0x0000 cardnum 0x10 function 0x02: vendor 0x1106 device 0x3038
VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
pci bus 0x0000 cardnum 0x10 function 0x03: vendor 0x1106 device 0x3038
VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
pci bus 0x0000 cardnum 0x10 function 0x04: vendor 0x1106 device 0x3104
VIA Technologies, Inc. USB 2.0
pci bus 0x0000 cardnum 0x11 function 0x00: vendor 0x1106 device 0x3227
VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
pci bus 0x0000 cardnum 0x11 function 0x05: vendor 0x1106 device 0x3059
VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller
pci bus 0x0000 cardnum 0x12 function 0x00: vendor 0x1106 device 0x3065
VIA Technologies, Inc. VT6102 [Rhine-II]
pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x1106 device 0x3344
VIA Technologies, Inc. Device unknown
Both the NIC's were detected by Schillix earlier as rh0 and rh1 and I could configure them likewise.
|
|
|
|
02-07-2007, 05:27 AM
|
#20
|
|
Moderator
Registered: Feb 2004
Location: Outside Paris, under a rock ...
Distribution: Solaris & OpenSolaris based distros, Ubuntu
Posts: 7,510
|
Your second NIC doesn't appear on the scanpci output, which is not a good start.
If with schillix they were using the same driver, then vfe should work too.
|
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 03:11 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
LQ Podcast
LQ Radio
|
|