Re: [osol-discuss] Network adapters

2008-04-18 Thread Emmanuel De Paepe
Just an update about the network card issue. After upgrading to Solaris 10 5/08 It seems that the upgrade added the 'IPv6' now. Could anybody comment which of the two (or both) are working? The on-board network adapter (like anticipated) is still down. bash-3.00$ ifconfig -a lo0:

Re: [osol-discuss] Network adapters

2008-04-18 Thread andrew
The output of the ifconfig -a command you posted shows that there are 4 logical interfaces active on your system - two IPv6 and 2 IPv4. You have the local loopback adapter (lo0) and your Realtek-based NIC (rtls0) configured. The Solaris installer should ask you whether you want to enable LPv6

Re: [osol-discuss] Network adapters

2008-04-15 Thread Lurie
That's Attansic L1, it's not supported, see http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6580058 http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6677682 (I guess a dup of the previous bug) This message posted from opensolaris.org

Re: [osol-discuss] Network adapters

2008-04-15 Thread Emmanuel De Paepe
This makes it all clear. I hope to find some time to extract a new driver from the Windows driver. In the meantime I took the easiest solution, which costed me an extra 10 euro. Lucky it's just a network card and not a graphic adapter. This message posted from opensolaris.org

Re: [osol-discuss] Network adapters

2008-04-14 Thread andrew
Your onboard network chip seems to be an Attansic L1 gigabit ethernet adaptor. Unfortunately there doesn't seem to be a Solaris driver available for this. Your best bet is probably to use the NDIS wrapper along with the Windows drivers for this NIC. You can find the NDIS wrapper toolkit for

Re: [osol-discuss] Network adapters

2008-04-14 Thread Emmanuel De Paepe
Thanks a lot for the feedback. I will give this a try. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Network adapters

2008-04-13 Thread andrew
No - lo0 is the local loopback adapter. There are two interfaces for lo0 - one for IPv4 (the top one) and one for IPv6 (the bottom one). The only other interface is rtls0 - which will be the card which you added. This shows that Solaris hasn't attached a driver to your onboard network

Re: [osol-discuss] Network adapters

2008-04-13 Thread Emmanuel De Paepe
I tried to post two times the complete readout of 'prtconf -v', but it disappeared after a while. Is there perhaps a post length limit on this board? This message posted from opensolaris.org ___ opensolaris-discuss mailing list

Re: [osol-discuss] Network adapters

2008-04-13 Thread andrew
Copy the output into a text editor, then trawl through it and find any references to devices with a description similar to Ethernet Adaptor. Post the contents of the file around the lines that contain the description - about 10 lines either side. Cheers Andrew. This message posted from

Re: [osol-discuss] Network adapters

2008-04-13 Thread Emmanuel De Paepe
I found back the string 'ethernet controller' on two occasions: I think the first one is the on-board 1) pci1043,8226 (driver not attached) Hardware properties: name='assigned-addresses' type=int items=5

[osol-discuss] Network adapters

2008-04-12 Thread Emmanuel De Paepe
I'm currently using a simple Sweex network adapter for internet connection. The reason was that the on-board network adapter did not work in Solaris 10. How can I still see what is missing for the on-board network adapter. This brings me to the following question, how are two network adapters in

Re: [osol-discuss] Network adapters

2008-04-12 Thread andrew
Can you run the following command as root: prtconf -v then post the output here? Also, can yo utell us what network chip your motherboard has on it? Thanks Andrew. This message posted from opensolaris.org ___ opensolaris-discuss mailing list

Re: [osol-discuss] Network adapters

2008-04-12 Thread Emmanuel De Paepe
I tried the in verbose mode but the read out is quite long do you really need this? I'll try to figure out the chip set of the on board network adapter. This is the motherboard: ASUS P5KR By the way, I only plugged in another network adapter after Solaris 10 internet connection failed. So, I

Re: [osol-discuss] Network adapters

2008-04-12 Thread Emmanuel De Paepe
If I'm correct at least SXDE seems to recognize there is an on board network adapter. I will check for Solaris 10 too. bash-3.2$ prtdiag System Configuration: System manufacturer P5KR BIOS Configuration: American Megatrends Inc. 020107/31/2007 Processor Sockets

Re: [osol-discuss] Network adapters

2008-04-12 Thread Emmanuel De Paepe
This is what I found about the on-board network adapter: PCIe Gigabit LAN controller featuring AI NET2 I'll check the manual of the motherboard for further details. 'prtconf' in Solaris 10, 'prtdiag' returns the same results as in SXDE. bash-3.00$ prtconf System Configuration: Sun

Re: [osol-discuss] Network adapters

2008-04-12 Thread andrew
Yes - the verbose mode gives the detail required - specifically the PCI ID of the network chip. From looking on the web, it seems that the chip on you motherboard may be an Intel 82556DC, which is supported on Solaris Express since build 58. Can you run the following command on your SXDE

Re: [osol-discuss] Network adapters

2008-04-12 Thread Emmanuel De Paepe
Thanks for the feedback, this is what I got back for SXDE: # ifconfig -a plumb ifconfig: SIOCSLIFNAME for ip: rtls0: already exists # This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Network adapters

2008-04-12 Thread andrew
That message means that the rtls0 interface (which is a Realtek card) was already plumbed - presumably this is the card that you bought? Can you run this command as root: ifconfig -a and post the output here? Thanks Andrew. This message posted from opensolaris.org

Re: [osol-discuss] Network adapters

2008-04-12 Thread Emmanuel De Paepe
That will indeed be the network card I added. Here is the readout: # ifconfig -a lo0: flags=2001000849UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL mtu 8232 index 1 inet 127.0.0.1 netmask ff00 rtls0: flags=201004843UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS mtu 1500 index 2