Jilliagre, I would appreciate much if you could wave your magic wand and tell me the solution to the rge driver! Intel Quad 9450. Build 91. rge driver is the included on Solaris - it is no 3rd party driver. I think the rge driver is v1.9. It feels like I am close to get this working? Or?



My progress this far with dual NIC on intel P45 chipset, GA-EP45-DS3P mobo:

scanpci
pci bus 0x0003 cardnum 0x00 function 0x00: vendor 0x10ec device 0x8168
Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller

pci bus 0x0004 cardnum 0x00 function 0x00: vendor 0x10ec device 0x8168
Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller






bash-3.2# prtconf
System Configuration: Sun Microsystems i86pc
Memory size: 4095 Megabytes
System Peripherals (Software Nodes):

i86pc
scsi_vhci, instance #0
isa, instance #0
asy, instance #0
i8042, instance #0
keyboard, instance #0
motherboard (driver not attached)
pit_beep, instance #0
pci, instance #0
pci1458,5000 (driver not attached)
pci8086,2e21, instance #0
display, instance #0
pci1002,aa30 (driver not attached)
pci1458,5004, instance #0
mouse, instance #3
pci1458,5004, instance #1
pci1458,5004, instance #2
pci1458,5006, instance #0
pci1458,a102, instance #0
pci8086,3a40, instance #1
pci8086,3a48, instance #2
pci1458,e000, instance #0
pci8086,3a4a, instance #3
pci1458,e000, instance #1
pci1458,5004, instance #3
pci1458,5004, instance #4
pci1458,5004, instance #5
pci1458,5006, instance #1
pci8086,244e, instance #0
pci11ab,11ab, instance #0
disk, instance #1
disk, instance #2
disk, instance #3
disk, instance #4
pci1458,1000, instance #0
pci-ide, instance #2
ide, instance #4
cmdk, instance #0
ide (driver not attached)
pci1458,5001 (driver not attached)
pci-ide, instance #0
ide (driver not attached)
ide, instance #1
sd, instance #0
pci1458,5001 (driver not attached)
pci-ide, instance #1
ide (driver not attached)
ide (driver not attached)
iscsi, instance #0
stmf, instance #0
sbd, instance #0
fct, instance #0
pseudo, instance #0
options, instance #0
agpgart, instance #0
xsvc, instance #0
used-resources (driver not attached)
cpus, instance #0
cpu, instance #0
cpu, instance #1
cpu, instance #2
cpu, instance #3






prtconf -pv
Node 0x00001e
assigned-addresses: 81030010.00000000.0000b000.00000000.00000100.c3030018.00
000000.ea110000.000 00000.00001000.c3030020.00000000.ea100000.00000000.00010000
reg: 00030000.00000000.00000000.00000000.00000000.01030010.00000000.00000000
.000 00000.00000100.43030018.00000000.00000000.00000000.00001000.43030020.00000000.00 000000.00
000000.00010000
compatible: 'pciex10ec,8168.1458.e000.2' + 'pciex10ec,8168.1458.e000' + 'pcie
x10ec,8168.2' + 'pciex10ec,8168' + 'pciexclass,020000' + 'pciexclass,0200' + 'pci10ec,8168.14
58.e000.2' + 'pci10ec,8168.1458.e000' + 'pci1458,e000' + 'pci10ec,8168.2' + 'pci10ec,8168' +
'pciclass,020000' + 'pciclass,0200'
model: 'Ethernet controller'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
subsystem-vendor-id: 00001458
subsystem-id: 0000e000
unit-address: '0'
class-code: 00020000
revision-id: 00000002
vendor-id: 000010ec
device-id: 00008168
pcie-capid-pointer: 00000070
pcie-capid-reg: 00000201
name: 'pci1458,e000'

Node 0x00001f
assigned-addresses: 81040010.00000000.0000c000.00000000.00000100.c3040018.00
000000.ea010000.000 00000.00001000.c3040020.00000000.ea000000.00000000.00010000
reg: 00040000.00000000.00000000.00000000.00000000.01040010.00000000.00000000
.000 00000.00000100.43040018.00000000.00000000.00000000.00001000.43040020.00000000.00 000000.00
000000.00010000
compatible: 'pciex10ec,8168.1458.e000.2' + 'pciex10ec,8168.1458.e000' + 'pcie
x10ec,8168.2' + 'pciex10ec,8168' + 'pciexclass,020000' + 'pciexclass,0200' + 'pci10ec,8168.14
58.e000.2' + 'pci10ec,8168.1458.e000' + 'pci1458,e000' + 'pci10ec,8168.2' + 'pci10ec,8168' +
'pciclass,020000' + 'pciclass,0200'
model: 'Ethernet controller'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
subsystem-vendor-id: 00001458
subsystem-id: 0000e000
unit-address: '0'
class-code: 00020000
revision-id: 00000002
vendor-id: 000010ec
device-id: 00008168
pcie-capid-pointer: 00000070
pcie-capid-reg: 00000201
name: 'pci1458,e000'





less driver_aliases:
rge "pci10ec,8169"
rge "pci10ec,8168"
rge "pci10ec,8167"
rge "pci16ec,116"
rge "pci10ec,8136"
rge "pciex10ec,8136"





bash-3.2# ifconfig -a
lo0: flags=2001000849 mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
rge0: flags=201004843 mtu 1500 index 2
inet 192.168.0.100 netmask ffffff00 broadcast 192.168.0.255
ether 0:1f:d0:20:c0:6a
lo0: flags=2002000849 mtu 8252 index 1
inet6 ::1/128
bash-3.2# ping 192.168.0.100
192.168.0.100 is alive
bash-3.2# ping www.google.com
ping: unknown host www.google.com

What says:
?

My Solaris halts boot before starting the desktop, so I did this in console (before desktop login). I am experimenting with Ati4850 graphic card right now...




netstat -rn

Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
----------- ------- ----- --- --- ----------
192.168.0.0 192.168.0.100 U 1 0 rge0
127.0.0.1 127.0.0.1 UH 1 0 lo0

Routing Table: IPv6
Destination/Mask Gateway Flags Ref Use If
---------------- ------- ----- --- --- ---

::1 ::1 UH 1 0 lo0







ping 75.126.162.205
ICMP Host Unreachable from gateway frasse (192.168.0.100)
for icmp from frasse (192.168.0.100) to 75.126.162.205
...
...

FYI:

This tells you very little; ping an external host, not your own interface.

This tells you either DNS is not working, There can be several causes. Use an IP address instead.


This tells you there is no route in your route table, to reach the remote IP.

This confirms that there is no route. You are missing a default route. This would be a route that delivers packets to your broadband router or Internet connection.device. Your IP looks like it might be a DHCP-assigned IP. Is that correct ? Is your gateway IP address configured on the router?

You NIC may works but you didn't configure routing (and possibly DNS).

If you do not tell your machine how to reach the Internet and how to resolve names, there is no chance it can ping google or whatever.

Put your router IP in the /etc/defaultrouter file, put your DNS server in the /etc/resolv.conf file, add dns to the host entry in /etc/nsswitch.conf file.

Eg (adjust to your own and possibly ISP settings for the DNS entry):

I have a D-link 604 firewall/hub. On it I have opened ports for IP 192.168.0.183 (because I played computer games earlier on my old computer). The D-link has IP-adress 192.168.0.1




I did a sys-unconfig again. Here are my choices this time (I dont know what I am doing, I just try different answers). Can you spot an error here?



Networked? - Yes
Configure which interfaces? rge0? rge1? - only rge0
Use dhcp for rge0? - Yes
Enable IPv6 for rge0? - No
"Now configuring... Just a moment..." (5-10 minutes paus) "System identification error. Could not contact to dhcp server on the nic rge0. Press F2 to dismiss this message"
Networked? - Yes
Configure which interfaces? rge0? rge1? - only rge0
Use dhcp for rge0? - No
Hostname for rge0? - frasse
Ip address for rge0? 192.168.0.183
System part of a subnet? - No
Enable IPv6 for rge0? - No
Default Route for rge0? - Detect one upon reboot
Configure Kerberos? - No
Name service (NIS+, NIS, DNS, LDAP, None)? - None
NFSv4 Domain Configuration? - Use the NFSv4 domain derived by the system
System part of a subnet? - No

choose country, time, root passwd, etc...

So the box cannot obtain a DHCP addess. Your going to have to get your router/firewall configured correctly.

I'm going to leave this thread - it seems hijacked from the original poster's intent to ask about Building a new box; this has become a debug session for enabling a network.

How about opening your own thread with a good title.

Instead a restarting from scratch, feel free to report this thread to be splitted by a moderator.

Ok, ive tried your suggestions and executed the commands about /etc/defaulrouter, etc. These files didnt exist on my Solaris. Now I get this:

#netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
----------- ------- ----- --- --- ----------
default 192.168.0.1 UG 1 0
192.168.0.0 192.168.0.183 U 1 72 rge0
127.0.0.1 127.0.0.1 UH 1 293 lo0

Routing Table: IPv6
Destination/Mask Gateway Flags Ref Use If
---------------- ------- ----- --- --- ---
::1 ::1 UH 1 21 lo0


#ping 75.126.162.205
no answer from 75.126.162.205




From my other Windows computer:
Ethernet-kort Anslutning till lokalt nätverk (I am translating from Swedish)

Connection dependent DNS-suffix . : bredbandsbolaget.se
Description . . . . . . . . . . . : Broadcom 570x Gigabit Integrated C
Physical adress . . . . . . . . . : 00-0B-DB-A4-B7-CC
DHCP active . . . . . . . . .... : Yes
Autokonfiguration active .... . . : Yes
IP-adress . . . . . . . . . . . . : 192.168.0.179
Netmask . . . . . . . . . . . . . : 255.255.255.0
Standard-gateway . . . . . . . . : 192.168.0.1
DHCP-server . . . . . . . . . . . : 192.168.0.1
DNS-servrar . . . . . . . . . . . : 195.54.122.200
195.54.122.199
Lånet erhölls . . . . . . . . . . : den 7 juli 2008 09:22:47
Lånet upphör . . . . . . . . . . : den 14 juli 2008 09:22:47

Hey, I am sorry for hijacking this thread. But the starter of this thread, was looking for a mobo with this LAN nic chip that I am trying to get working. I think he would like to know if the mobo he is considering will work under Solaris too? He wants to know if the mobo he is considering will work under Solaris. This is a hardware question.

I will post here my complete setup soon, for the thread starter. If we can get this nic to work, we know that Solaris works under bleading edge new mother board P45 chipset. I am also dabbling with getting the ati 4850 to work. I have got a new Solaris driver for that, I will soon try. The thread starter would like to know if Ati 4850 works under Solaris too? I will report everything here. But to do that, I must get it working first. Otherwise I can not report success / failuer of Solaris in mobo that is a few days old. Bear with me. I will report success / failure soon.

Could it help if I tried the gani driver? I dont see why gani driver would help the nic get contact to dhcp?

The gani driver might work better. It worth trying.

Did you change something in the driver_aliases file for the rge driver to load or was it set in the first time ?

Any system message about the driver when you boot and/or when you plug the cable ? (dmesg | grep rge)

Did you try snooping the network to see if incoming packets are seen ? (snoop -d rge0)

Yea, well what can you do. I think I'll be waiting to better define my needs for a system. I appreciate everyone's input relating to my questions.

-AM

This really should have been in your own thread. Instead of debugging your issue and making it look like it might help me, all you need to have said was that it is troublesome to get it working and point to another thread for the workaround.

Putting your problem here is not only rude to me but doesn't contribute to my original post. Now you are attempting to mask the fact that this problem solving will help me in some way by telling me you'll post success or not. You're trying to make yourself feel better by associating your hardware problems with my questions about compatibility; this does not fly with me.

Unless my eyes deceive me, it says you are one.

Student04,

No it is not like that. Seriously. I thought you would like to know how this hardware (intel P45 chipset + Intel Quad9450 + Ati4850) worked with Solaris? You said you considered a motherboard with this NIC for your new solaris, didnt you? If you have read my other threads, you would have known that I try different things out, and at the last post always report and summarize how I did, and how the workarounds were. I think it helps others, if we all report the problem and the solution. So, I have a history of doing that, and Im not writing that, just to make me look better in your eyes. Thats not my style, nor personality to do so. Would you rather prefer I came to a conclusion about this nic, and didnt tell you? If it works, or if you should look for another mobo?

I admit that I hijacked this thread, and I admit I shouldve started another thread. And for that, I apologize and hope you accept my apologies. And lastly, I should have posted my conclusions here, and the summary. You are correct there. But I do NOT write things to make me look better in other peoples eyes. When I have done something wrong, I do not try to make up bad excuses. Like other people maybe do. I am not that kind of person. Instead, I admit that I have done wrong and apologize. I am leaving this thread now. Do you still want to know how my bleading edge hardware works with Solaris? Should I report it here, for you?