Re: Sun x2100 M2 DMESG weirdenn and remote access. OpenBSD 4.0
On Tue, Oct 31, 2006 at 08:35:06PM -0600, Damian Wiest wrote: On Tue, Oct 31, 2006 at 04:22:52PM -1000, [EMAIL PROTECTED] wrote: On 31-Oct-06, at 3:59 PM, Damian Wiest wrote: On Sat, Oct 28, 2006 at 09:17:11AM -0700, Pawel S. Veselov wrote: stan wrote: On Tue, Oct 24, 2006 at 11:11:43PM -0700, Pawel S. Veselov wrote: I'll have to talk to one of my co-workers about this. I seem to recall there being a driver available, but that it didn't work properly. Getting OT, but are you using the SUNWintgige package? Are you talking about the Nvidia RAID controller? That is correct. -- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: Sun x2100 M2 DMESG weirdenn and remote access. OpenBSD 4.0
On Tue, Oct 31, 2006 at 07:59:34PM -0600, Damian Wiest wrote: On Sat, Oct 28, 2006 at 09:17:11AM -0700, Pawel S. Veselov wrote: stan wrote: On Tue, Oct 24, 2006 at 11:11:43PM -0700, Pawel S. Veselov wrote: Daniel Ouellet wrote: stan wrote: That's actually not a given IFIRK Sun says the RAID on the 2100's is Windows only. Why Sun picks that kinda hardware for it's servers, is another kinda question But the controller manufacturers play evil here... Might be beacuse these machines are about $750US each list. What about v65x then ? :) I don't know if I mentioned this already, but the Intel Gigabit Ethernet chip on Sun's AMD64 systems isn't even supported under Solaris. Windows drivers only. I have heard rumors that a recent build of OpenSolaris includes driver support though. OK, _that one_ shocks me. -- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: Sun x2100 M2 DMESG weirdenn and remote access. OpenBSD 4.0
On Sat, Oct 28, 2006 at 09:17:11AM -0700, Pawel S. Veselov wrote: stan wrote: On Tue, Oct 24, 2006 at 11:11:43PM -0700, Pawel S. Veselov wrote: Daniel Ouellet wrote: stan wrote: That's actually not a given IFIRK Sun says the RAID on the 2100's is Windows only. Why Sun picks that kinda hardware for it's servers, is another kinda question But the controller manufacturers play evil here... Might be beacuse these machines are about $750US each list. What about v65x then ? :) I don't know if I mentioned this already, but the Intel Gigabit Ethernet chip on Sun's AMD64 systems isn't even supported under Solaris. Windows drivers only. I have heard rumors that a recent build of OpenSolaris includes driver support though. -Damian
Re: Sun x2100 M2 DMESG weirdenn and remote access. OpenBSD 4.0
On 31-Oct-06, at 3:59 PM, Damian Wiest wrote: On Sat, Oct 28, 2006 at 09:17:11AM -0700, Pawel S. Veselov wrote: stan wrote: On Tue, Oct 24, 2006 at 11:11:43PM -0700, Pawel S. Veselov wrote: Daniel Ouellet wrote: stan wrote: That's actually not a given IFIRK Sun says the RAID on the 2100's is Windows only. Why Sun picks that kinda hardware for it's servers, is another kinda question But the controller manufacturers play evil here... Might be beacuse these machines are about $750US each list. What about v65x then ? :) I don't know if I mentioned this already, but the Intel Gigabit Ethernet chip on Sun's AMD64 systems isn't even supported under Solaris. Windows drivers only. I have heard rumors that a recent build of OpenSolaris includes driver support though. -Damian That is incorrect. The Intel chipset on the Sun AMD64 servers is supported under Solaris with the Sun e1000g driver (and the older ipge driver on SPARC systems that have that same chipset, anyway). The e1000g adds jumbo frames and a few other features over the ipge driver. Also, the RAID controller configuration is available via the BIOS and in Solaris as raidctl(1M) -Mike
Re: Sun x2100 M2 DMESG weirdenn and remote access. OpenBSD 4.0
On Tue, Oct 31, 2006 at 04:22:52PM -1000, [EMAIL PROTECTED] wrote: On 31-Oct-06, at 3:59 PM, Damian Wiest wrote: On Sat, Oct 28, 2006 at 09:17:11AM -0700, Pawel S. Veselov wrote: stan wrote: On Tue, Oct 24, 2006 at 11:11:43PM -0700, Pawel S. Veselov wrote: Daniel Ouellet wrote: stan wrote: That's actually not a given IFIRK Sun says the RAID on the 2100's is Windows only. Why Sun picks that kinda hardware for it's servers, is another kinda question But the controller manufacturers play evil here... Might be beacuse these machines are about $750US each list. What about v65x then ? :) I don't know if I mentioned this already, but the Intel Gigabit Ethernet chip on Sun's AMD64 systems isn't even supported under Solaris. Windows drivers only. I have heard rumors that a recent build of OpenSolaris includes driver support though. -Damian That is incorrect. The Intel chipset on the Sun AMD64 servers is supported under Solaris with the Sun e1000g driver (and the older ipge driver on SPARC systems that have that same chipset, anyway). The e1000g adds jumbo frames and a few other features over the ipge driver. Also, the RAID controller configuration is available via the BIOS and in Solaris as raidctl(1M) -Mike I'll have to talk to one of my co-workers about this. I seem to recall there being a driver available, but that it didn't work properly. Getting OT, but are you using the SUNWintgige package? Are you talking about the Nvidia RAID controller? -Damian
Re: Sun x2100 M2 DMESG weirdenn and remote access. OpenBSD 4.0
On 31-Oct-06, at 4:35 PM, Damian Wiest wrote: On Tue, Oct 31, 2006 at 04:22:52PM -1000, [EMAIL PROTECTED] wrote: On 31-Oct-06, at 3:59 PM, Damian Wiest wrote: On Sat, Oct 28, 2006 at 09:17:11AM -0700, Pawel S. Veselov wrote: stan wrote: On Tue, Oct 24, 2006 at 11:11:43PM -0700, Pawel S. Veselov wrote: Daniel Ouellet wrote: stan wrote: That's actually not a given IFIRK Sun says the RAID on the 2100's is Windows only. Why Sun picks that kinda hardware for it's servers, is another kinda question But the controller manufacturers play evil here... Might be beacuse these machines are about $750US each list. What about v65x then ? :) I don't know if I mentioned this already, but the Intel Gigabit Ethernet chip on Sun's AMD64 systems isn't even supported under Solaris. Windows drivers only. I have heard rumors that a recent build of OpenSolaris includes driver support though. -Damian That is incorrect. The Intel chipset on the Sun AMD64 servers is supported under Solaris with the Sun e1000g driver (and the older ipge driver on SPARC systems that have that same chipset, anyway). The e1000g adds jumbo frames and a few other features over the ipge driver. Also, the RAID controller configuration is available via the BIOS and in Solaris as raidctl(1M) -Mike I'll have to talk to one of my co-workers about this. I seem to recall there being a driver available, but that it didn't work properly. Getting OT, but are you using the SUNWintgige package? Are you talking about the Nvidia RAID controller? -Damian I don't know the package, really, as the manpage doesn't list it as it should in ATTRIBUTES. Unfortunately, our Sun AMD64 boxes were slated for Windows installations, so they only ran Solaris (pre- installed) for a short while. I had little time to play with them before our Windows admin setup the LSI RAID controllers via BIOS and wiped the disks. If it helps, the e1000g driver was released in Solaris Update 2 (U2) 06/06 I believe and is documented here: http://docs.sun.com/app/docs/doc/816-5177/6mbbc4g54?a=view and the following page lists Solaris 32-bit and 64-bit support: http://www.sun.com/servers/entry/x2100/os.jsp -Mike
Re: Sun x2100 M2 DMESG weirdenn and remote access. OpenBSD 4.0
On Tue, Oct 24, 2006 at 11:11:43PM -0700, Pawel S. Veselov wrote: Daniel Ouellet wrote: stan wrote: That's actually not a given IFIRK Sun says the RAID on the 2100's is Windows only. Why Sun picks that kinda hardware for it's servers, is another kinda question But the controller manufacturers play evil here... Might be beacuse these machines are about $750US each list. -- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: Sun x2100 M2 DMESG weirdenn and remote access. OpenBSD 4.0
stan wrote: On Tue, Oct 24, 2006 at 11:11:43PM -0700, Pawel S. Veselov wrote: Daniel Ouellet wrote: stan wrote: That's actually not a given IFIRK Sun says the RAID on the 2100's is Windows only. Why Sun picks that kinda hardware for it's servers, is another kinda question But the controller manufacturers play evil here... Might be beacuse these machines are about $750US each list. What about v65x then ? :)
Re: Sun x2100 M2 DMESG weirdenn and remote access. OpenBSD 4.0
Daniel Ouellet wrote: stan wrote: That's actually not a given IFIRK Sun says the RAID on the 2100's is Windows only. Interesting! I didn't read that. Must have skip my reading then somehow. The choice are in the BIOS to enable it. I didn't buy two drives as it was for testing only, so I can't say if it would work or not for sure, or if it would be supported in OpenBSD or not. No clue. If there is feedback as to it should be supported, not only in Windows, and some are interested to know if it does or not, I could buy an other drive and try it. Not that I will need two drives for what this baby will be use in. So, what's the controller in x2100 ? In v65x it was a u320 aic79xx, Adaptec only provides Windows drivers for it, and is not so willing to share with the microcode needed to support built-in RAID. Someone also mentioned that enabling these kind of RAIDs is of little use, since they put almost the same strain on the CPU, making it run controller's microcode. Why Sun picks that kinda hardware for it's servers, is another kinda question But the controller manufacturers play evil here... Thanks, Pawel.
Re: Sun x2100 M2 DMESG weirdenn and remote access. OpenBSD 4.0
On Tue, Oct 24, 2006 at 11:11:43PM -0700, Pawel S. Veselov wrote: Daniel Ouellet wrote: stan wrote: That's actually not a given IFIRK Sun says the RAID on the 2100's is Windows only. Interesting! I didn't read that. Must have skip my reading then somehow. The choice are in the BIOS to enable it. I didn't buy two drives as it was for testing only, so I can't say if it would work or not for sure, or if it would be supported in OpenBSD or not. No clue. If there is feedback as to it should be supported, not only in Windows, and some are interested to know if it does or not, I could buy an other drive and try it. Not that I will need two drives for what this baby will be use in. So, what's the controller in x2100 ? In v65x it was a u320 aic79xx, Adaptec only provides Windows drivers for it, and is not so willing to share with the microcode needed to support built-in RAID. Someone also mentioned that enabling these kind of RAIDs is of little use, since they put almost the same strain on the CPU, making it run controller's microcode. Why Sun picks that kinda hardware for it's servers, is another kinda question But the controller manufacturers play evil here... Thanks, Pawel. Well, I just found about a half-dozen of these machines in the back room... It's not easy to get to, but the RAID controller is an NVidia nf4-ultra-n-a3; I didn't see any sort of EEPROM or SRAM chip to hold metadata. From what I've heard, there are only Windows drivers available. -Damian
Re: Sun x2100 M2 DMESG weirdenn and remote access. OpenBSD 4.0
On Mon, Oct 23, 2006 at 01:24:11PM -0400, Daniel Ouellet wrote: Stuart Henderson wrote: On 2006/10/22 17:29, Daniel Ouellet wrote: It work,s but as soon as the setup for OpenBSD start to boot the bsd.rd, the access to both the ethernet management port as well as the serial console is lost and the only way is to use local keyboard and monitor. Usually BIOS serial redirection stops after the bootloader, so you have to 'set tty com0' (either typed or, if you're booting from PXE you can place it in $TFTPROOT/etc/boot.conf) But you can't do that if you boot from CD for example to do a fresh install. I was trying to see if I could do that for future needs before installing it in the field. But no success. (: As for regular operation, I will try this and see if that does any difference. The ethernet management is probably asf/ipmi and I guess it would be on one of the broadcom nics, bge(4) doesn't support this at present (was added for a short while but removed again, if_bge.c 1.104-1.106) It is the bge1 interface actually on this box. 4 ethernet, 2 card slots, LOM improvements... sounds like it's a lot more useful machine. So far looks like a very nice server. Front loaded SAS drives, could do RAID as well, (don't know if that works well or not, didn't try yet), dual core CPU and a bunch more of nice features. I wasn't sure OpenBSD was going to work, so I took a chance, got one for testing and see. So, far, pretty nice! A few things don't look right in DMESG, but nothing that is a show stopper yet anyway. Just this management interface, either serial, or Ethernet that doesn't work. Would be nice, but I can live without. It's not to much of a drive, about 40 minutes at worst. But I have to say that I much prefer that box to my IBM 326e or HP 145 G2 or G1 so far. I have nothing bad to say about it yet anyway. Minor things, that's all. Besides the Broadcom, what other nic is on the system board? ISTR newer x2100's shipping with Nvidia ck8-04 Gigabit Ethernet for the primary interface which may not be supported. I believe all of our x2100's are running Solaris 10; I can check to see if we have one available for testing with OpenBSD. I know for a fact that we have the BIOS and console writing to serial port A under Solaris 10. -Damian
Re: Sun x2100 M2 DMESG weirdenn and remote access. OpenBSD 4.0
Damian Wiest wrote: Besides the Broadcom, what other nic is on the system board? ISTR newer x2100's shipping with Nvidia ck8-04 Gigabit Ethernet for the primary interface which may not be supported. It's in the dmesg in archive: Two Broadcom bge Broadcom BCM5715 and two NVIDIA nfe NVIDIA MCP55 LAN I believe all of our x2100's are running Solaris 10; I can check to see if we have one available for testing with OpenBSD. I know for a fact that we have the BIOS and console writing to serial port A under Solaris 10. It must be as Sun needs to support it's own stuff right? (: But so far it's not in OpenBSD. (:
Re: Sun x2100 M2 DMESG weirdenn and remote access. OpenBSD 4.0
On Tue, Oct 24, 2006 at 05:24:43PM -0400, Daniel Ouellet wrote: Damian Wiest wrote: Besides the Broadcom, what other nic is on the system board? ISTR newer x2100's shipping with Nvidia ck8-04 Gigabit Ethernet for the primary interface which may not be supported. It's in the dmesg in archive: Two Broadcom bge Broadcom BCM5715 and two NVIDIA nfe NVIDIA MCP55 LAN I believe all of our x2100's are running Solaris 10; I can check to see if we have one available for testing with OpenBSD. I know for a fact that we have the BIOS and console writing to serial port A under Solaris 10. It must be as Sun needs to support it's own stuff right? (: That's actually not a given IFIRK Sun says the RAID on the 2100's is Windows only. -- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: Sun x2100 M2 DMESG weirdenn and remote access. OpenBSD 4.0
stan wrote: That's actually not a given IFIRK Sun says the RAID on the 2100's is Windows only. Interesting! I didn't read that. Must have skip my reading then somehow. The choice are in the BIOS to enable it. I didn't buy two drives as it was for testing only, so I can't say if it would work or not for sure, or if it would be supported in OpenBSD or not. No clue. If there is feedback as to it should be supported, not only in Windows, and some are interested to know if it does or not, I could buy an other drive and try it. Not that I will need two drives for what this baby will be use in. Best, Daniel
Re: Sun x2100 M2 DMESG weirdenn and remote access. OpenBSD 4.0
On 2006/10/22 17:29, Daniel Ouellet wrote: It work,s but as soon as the setup for OpenBSD start to boot the bsd.rd, the access to both the ethernet management port as well as the serial console is lost and the only way is to use local keyboard and monitor. Usually BIOS serial redirection stops after the bootloader, so you have to 'set tty com0' (either typed or, if you're booting from PXE you can place it in $TFTPROOT/etc/boot.conf) The ethernet management is probably asf/ipmi and I guess it would be on one of the broadcom nics, bge(4) doesn't support this at present (was added for a short while but removed again, if_bge.c 1.104-1.106) 4 ethernet, 2 card slots, LOM improvements... sounds like it's a lot more useful machine.
Re: Sun x2100 M2 DMESG weirdenn and remote access. OpenBSD 4.0
Stuart Henderson wrote: On 2006/10/22 17:29, Daniel Ouellet wrote: It work,s but as soon as the setup for OpenBSD start to boot the bsd.rd, the access to both the ethernet management port as well as the serial console is lost and the only way is to use local keyboard and monitor. Usually BIOS serial redirection stops after the bootloader, so you have to 'set tty com0' (either typed or, if you're booting from PXE you can place it in $TFTPROOT/etc/boot.conf) But you can't do that if you boot from CD for example to do a fresh install. I was trying to see if I could do that for future needs before installing it in the field. But no success. (: As for regular operation, I will try this and see if that does any difference. The ethernet management is probably asf/ipmi and I guess it would be on one of the broadcom nics, bge(4) doesn't support this at present (was added for a short while but removed again, if_bge.c 1.104-1.106) It is the bge1 interface actually on this box. 4 ethernet, 2 card slots, LOM improvements... sounds like it's a lot more useful machine. So far looks like a very nice server. Front loaded SAS drives, could do RAID as well, (don't know if that works well or not, didn't try yet), dual core CPU and a bunch more of nice features. I wasn't sure OpenBSD was going to work, so I took a chance, got one for testing and see. So, far, pretty nice! A few things don't look right in DMESG, but nothing that is a show stopper yet anyway. Just this management interface, either serial, or Ethernet that doesn't work. Would be nice, but I can live without. It's not to much of a drive, about 40 minutes at worst. But I have to say that I much prefer that box to my IBM 326e or HP 145 G2 or G1 so far. I have nothing bad to say about it yet anyway. Minor things, that's all.
Sun x2100 M2 DMESG weirdenn and remote access. OpenBSD 4.0
Hi, I loaded 4.0 into a nice new Sun x2100 M2 and looks like it's working pretty well so far anyway. But I see a few weird things in the dmesg, like the dual core cpu display one core at 1.8GHz and the other at 2.4 sometime? Some device show not configure, but looks like they work. Compare both dmesg below for the cpu speed for example. Rebooting it looks like give different result. Different in setip was in one instance a MAC USB keyboard was connected to the USB port to do the setup and local access. Also, is there a way or trick to get the remote management port, or even the local serial port to continue working as usual to manage the box remotely. It work,s but as soon as the setup for OpenBSD start to boot the bsd.rd, the access to both the ethernet management port as well as the serial console is lost and the only way is to use local keyboard and monitor. Is there a trick, or is that normal? Also, after the system is fully working, would, is there anyway to actually have this working, so some setup that I can't figure out, or is that just normal? That's a pretty nice box so far. I am testing it good as I need a good amount of them and I was wondering to either get the x2100, or the x2100 M2. The M2 does have dual core, so that's very nice and the difference is price is not that bad and support serial ATA as well and the full management port, that may not be working in the end anyway, but not the end of the world. Look like the M2 is a much beter choice. Idea feedback on this, or am I wrong thinking that way? Thanks for the feedback. OpenBSD 4.0 (GENERIC.MP) #967: Sat Sep 16 20:38:15 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 536408064 (523836K) avail mem = 447447040 (436960K) using 13147 buffers containing 53850112 bytes (52588K) of memory mainbus0 (root) bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xfbdc0 (36 entries) bios0: Sun Microsystems X2100 M2 ipmi0 at mainbus0: version 1.5 interface KCS iobase 0xca2/2 spacing 1 mainbus0: Intel MP Specification (Version 1.4) (nVidia MCP55 ) cpu0 at mainbus0: apid 0 (boot processor) cpu0: Dual-Core AMD Opteron(tm) Processor 1210, 1809.51 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: apic clock running at 201MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Dual-Core AMD Opteron(tm) Processor 1210, 1809.27 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative mpbios: bus 0 is type PCI mpbios: bus 1 is type PCI mpbios: bus 2 is type PCI mpbios: bus 3 is type PCI mpbios: bus 4 is type PCI mpbios: bus 5 is type PCI mpbios: bus 6 is type PCI mpbios: bus 7 is type PCI mpbios: bus 8 is type PCI mpbios: bus 9 is type ISA ioapic0 at mainbus0 apid 2 pa 0xfec0, version 11, 24 pins pci0 at mainbus0 bus 0: configuration mode 1 NVIDIA MCP55 Memory rev 0xa2 at pci0 dev 0 function 0 not configured pcib0 at pci0 dev 1 function 0 vendor NVIDIA, unknown product 0x0364 rev 0xa3 nviic0 at pci0 dev 1 function 1 NVIDIA MCP55 SMBus rev 0xa3 iic0 at nviic0: disabled to avoid ipmi0 interactions iic1 at nviic0: disabled to avoid ipmi0 interactions ohci0 at pci0 dev 2 function 0 NVIDIA MCP55 USB rev 0xa1: apic 2 int 15 (irq 15), version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: NVIDIA OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 8 ports with 8 removable, self powered ehci0 at pci0 dev 2 function 1 NVIDIA MCP55 USB rev 0xa2: apic 2 int 7 (irq 7) usb1 at ehci0: USB revision 2.0 uhub1 at usb1 uhub1: NVIDIA EHCI root hub, rev 2.00/1.00, addr 1 uhub1: 8 ports with 8 removable, self powered pciide0 at pci0 dev 4 function 0 NVIDIA MCP55 IDE rev 0xa1: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility atapiscsi0 at pciide0 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: MATSHITA, DVD-ROM SR-8178, PZ16 SCSI0 5/cdrom removable cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4 pciide0: channel 1 ignored (disabled) pciide1 at pci0 dev 5 function 0 NVIDIA MCP55 SATA rev 0xa3: DMA pciide1: using apic 2 int 10 (irq 10) for native-PCI interrupt wd0 at pciide1 channel 0 drive 0: HITACHI HDS7225SBSUN250G 0634NRTRTJ wd0: 16-sector PIO, LBA48,
