Sun X2100
I'm considering purchasing a Sun X2100 to use a an OpenBSD based firewall. Any hardware issues I should be aware of? What have been peoples experince with these (or similar) machines? -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
Re: Sun X2100
stan wrote: I'm considering purchasing a Sun X2100 to use a an OpenBSD based firewall. Any hardware issues I should be aware of? What have been peoples experince with these (or similar) machines? It worked. Undeadly host their site on it, the only issue at the time was the second Ethernet port wasn't supported. I don't know if that changed or not. Search the archive on it, there is information there including dmesg as well.
Re: Sun X2100
stan wrote: I'm considering purchasing a Sun X2100 to use a an OpenBSD based firewall. Any hardware issues I should be aware of? What have been peoples experince with these (or similar) machines? I have been using a couple of the X2100's in testing environments for a few weeks, they run 3.9 well. In 3.8 the second NIC was not usable.
Re: Sun X2100
On Tue, Apr 18, 2006 at 04:39:44PM -0700, Dag Richards wrote: > stan wrote: > >I'm considering purchasing a Sun X2100 to use a an OpenBSD based > >firewall. > > > >Any hardware issues I should be aware of? > > > >What have been peoples experince with these (or similar) machines? > > > > > I have been using a couple of the X2100's in testing environments for a > few weeks, they run 3.9 well. > In 3.8 the second NIC was not usable. > Thanks, that's important info, as I am planing on useing both. Out of curiosity what was the issue? I would assume they are both the same hardware type, no? -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
Re: Sun X2100
Look at: http://www.armorlogic.com/openbsd_information_server_compatibility_list.html?action=detail&id=x2100 The only *real* issue left is the nvidia network card puking under major load, but that might have been solved by the last commit (past 3.9-STABLE) by [EMAIL PROTECTED] I haven't got my hands on this box again to test though.
Re: Sun X2100
On Tue, Apr 18, 2006 at 07:19:07PM -0400, stan wrote: > I'm considering purchasing a Sun X2100 to use a an OpenBSD based firewall. > > Any hardware issues I should be aware of? > > What have been peoples experince with these (or similar) machines? Although it's not directly OpenBSD related, you'll probably want to flash the BIOS with the latest version, as Sun still seem to be shipping machines with the comically broken first version of the BIOS. Just to give you an idea of how bad it is: USB keyboards don't work reliably (and this is a machine without a PS/2 slot don't forget), and at least one BIOS screen says something like "press Shift-F1" but misses the "f" in "shift". Quality control were probably having an off day. Mercifully the BIOS update you can get from SUN is installable in an OS independent fashion, and after that the machine (and OpenBSD) seem to run fine. Laurie -- http://tratt.net/laurie/ -- Personal http://convergepl.org/ -- The Converge programming language http://sosym.dcs.kcl.ac.uk/ -- Software and Systems Modelling Team http://modelsconference.org/ -- MoDELS/UML 2006 conference
nfe driver and Sun X2100
Has anyone gotten teh nfe port on a Sun 2100 to work on 19M? I have one of these, that I am setting up as a firewall between 2 legacy networks, both of which are 10M, and when I plug that port into the 10M hub, I get continuing kernel error messages. I'm considering locking it down, to se if that works, but have not tried that yet. -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
hardware: Sun x2100 test results
For those interested, here are the preliminary results of my Sun x2100 tests. More hardware tests results available at http://www.armorlogic.com/oscl/ Issues with Sun X2100 running OpenBSD/amd64 (-current from 22/02/2006) 1) possible bsd.mp issues due to misconfigured apic's ioapic0 at mainbus0 apid 2: pa 0x83738f24, version 11, 24 pins ioapic0: misconfigured as apic 0 ioapic0: remapped to apic 2 2) nfe(4) shows a constant 100/interrupts a seconds without having a link; only configured with ifconfig nfe0 127.0.0.1 255.0.0.0; it also has the same interrupt rate when configured normally 3) nfe(4) stops responding during stress-testing with netperf (transmitter box, Dell SC1425, dual em/gigabit) (receiver box, Sun X2100, nfe/gigabit) (both connected to a Dell PowerConnect 2708 gigabit switch) # netperf -H 192.168.0.60 -l 300 -- -s 64K -m 64K -M 64K -S 64K TCP STREAM TEST to 192.168.0.60 Recv SendSend Socket Socket Message Elapsed Size SizeSize Time Throughput bytes bytes bytessecs.10^6bits/sec 65536 65536 65536298.96940.67 (transmitter: 8K/interrupts seconds on em0, 0% system idle) (receiver: 83K/interrupts seconds on nfe0, 0% system idle) All fine. Stress test runs for 300 seconds without a problem. Now, we try the same test, but we increase the remote socket (nfe0) send/recv buffer size to 128K. # netperf -H 192.168.0.60 -l 60 -- -s 128K -m 64K -M 64K -S 128K (transmitter: 8K/interrupts seconds on em9, 0% system idle) (receiver: 100K/interrupts seconds on nfe0, 0% system idle) nfe0 will stop responding after few seconds; tcpdump shows nothing; ifconfig down/up doesn't help; only a reboot does. 4) nviic(4) is probed/found, but provides no values to sensors(4) framework. Details follow: nviic0 at pci0 dev 1 function 1 "NVIDIA nForce4 SMBus" rev 0xa2 iic0 at nviic0 iic0: addr 0x2e 00=00 01=00 02=00 03=00 04=00 05=00 06=00 07=00 08=00 09=00 0a=00 0b=00 0c=00 0d=00 0e=00 0f=00 10=00 11=00 12=00 13=00 14=00 15=00 16=00 17=00 18=00 19=00 1a=00 1b=00 1c=00 1d=00 1e=00 1f=03 20=63 21=75 22=c1 23=c1 24=bc 25=38 26=1c 27=19 28=39 29=02 2a=19 2b=03 2c=f5 2d=02 2e=2e 2f=02 30=81 31=55 32=55 33=00 34=00 35=00 36=00 37=00 38=00 39=00 3a=00 3b=00 3c=00 3d=00 3e=5c 3f=89 40=05 41=00 42=00 43=00 44=00 46=00 48=00 4a=00 4c=00 4e=ec 4f=50 50=ec 51=3c 52=ec 53=3c 54=5e 55=1a 56=5e 57=1a 58=5e 59=1a 5a=5e 5b=1a 5c=02 5d=22 5e=42 5f=4b 60=ab 61=ab 62=e8 63=88 64=80 65=33 66=33 67=38 68=2d 69=2a 6a=3e 6b=3a 6c=37 6d=44 6e=40 6f=00 70=80 71=33 72=33 73=09 74=09 75=09 76=09 77=09 78=09 79=00 7a=10 7b=00 7c=44 7d=00 7e=00 7f=1c 80=0f 81=84 82=05 83=00 84=ec 85=9a 86=73 87=1d 88=26 89=00 8a=4d 8b=4d 8c=0b 8d=0b 8e=0c 8f=00 90=84 91=86 92=86 93=84 94=0c 95=0c 96=0c 97=5a 98=f1 99=be 9a=ac 9b=00 9d=00 9f=00 a0=00 a1=00 a2=0c a3=00 a4=02 a5=00 a6=00 a7=0b a8=0b a9=fe ab=fe b1=00 b2=00 b3=00 b4=00 b5=00 b6=28 b7=28 b8=0e b9=0e ba=2b bb=2b bc=00 bd=00 be=00 bf=00 c0=00 c1=00 c2=00 c3=00 c4=00 c5=00 c6=00 c7=00 c8=00 c9=00 ca=00 cb=00 cc=00 cd=00 ce=00 cf=00 d0=00 d1=00 d2=00 d3=00 d4=00 d5=00 d6=00 d7=00 d8=00 d9=00 da=00 db=00 dc=00 dd=00 de=00 df=00 e0=00 e1=00 e2=00 e3=00 e4=00 e5=00 e6=00 e7=00 e8=00 e9=00 ea=00 eb=00 ec=00 ed=00 ee=00 ef=00 f0=00 f1=00 f2=00 f3=00 f4=00 f5=00 f6=00 f7=00 f8=00 f9=00 fa=00 fb=00 fc=00 fd=00 fe=00 ff=00 iic1 at nviic0 iic1: addr 0x2e 00=00 01=00 02=00 03=00 04=00 05=00 06=00 07=00 08=00 09=00 0a=00 0b=00 0c=00 0d=00 0e=00 0f=00 10=00 11=00 12=00 13=00 14=00 15=00 16=00 17=00 18=00 19=00 1a=00 1b=00 1c=00 1d=00 1e=00 1f=03 20=63 21=75 22=c1 23=c1 24=bc 25=38 26=1c 27=19 28=39 29=02 2a=1a 2b=03 2c=fb 2d=02 2e=2e 2f=02 30=81 31=55 32=55 33=00 34=00 35=00 36=00 37=00 38=00 39=00 3a=00 3b=00 3c=00 3d=00 3e=5c 3f=89 40=05 41=00 42=00 43=00 44=00 46=00 48=00 4a=00 4c=00 4e=ec 4f=50 50=ec 51=3c 52=ec 53=3c 54=5e 55=1a 56=5e 57=1a 58=5e 59=1a 5a=5e 5b=1a 5c=02 5d=22 5e=42 5f=4b 60=ab 61=ab 62=e8 63=88 64=80 65=33 66=33 67=38 68=2d 69=2a 6a=3e 6b=3a 6c=37 6d=44 6e=40 6f=00 70=80 71=33 72=33 73=09 74=09 75=09 76=09 77=09 78=09 79=00 7a=10 7b=00 7c=44 7d=00 7e=00 7f=1c 80=0f 81=84 82=05 83=00 84=bd 85=95 86=63 87=1d 88=46 89=00 8a=4d 8b=4d 8c=0b 8d=0b 8e=0c 8f=00 90=84 91=86 92=86 93=84 94=0c 95=0c 96=0c 97=5a 98=f1 99=be 9a=ac 9b=00 9d=00 9f=00 a0=00 a1=00 a2=0c a3=00 a4=02 a5=00 a6=00 a7=0b a8=0b a9=fe ab=fe b1=00 b2=00 b3=00 b4=00 b5=00 b6=28 b7=28 b8=0e b9=0e ba=2b bb=2b bc=00 bd=00 be=00 bf=00 c0=00 c1=00 c2=00 c3=00 c4=00 c5=00 c6=00 c7=00 c8=00 c9=00 ca=00 cb=00 cc=00 cd=00 ce=00 cf=00 d0=00 d1=00 d2=00 d3=00 d4=00 d5=00 d6=00 d7=00 d8=00 d9=00 da=00 db=00 dc=00 dd=00 de=00 df=00 e0=00 e1=00 e2=00 e3=00 e4=00 e5=00 e6=00 e7=00 e8=00 e9=00 ea=00 eb=00 ec=00 ed=00 ee=00 ef=00 f0=00 f1=00 f2=00 f3=00 f4=00 f5=00 f6=00 f7=00 f8=00 f9=00 fa=00 fb=00 fc=00 fd=00 fe=00 ff=00 dmesg x2100: OpenBSD 3.9-beta (GENERIC.MP) #0: Wed Feb 22 12:04:50 CET 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem =
Re: nfe driver and Sun X2100
On 6/8/06, stan <[EMAIL PROTECTED]> wrote: Has anyone gotten teh nfe port on a Sun 2100 to work on 19M? I have one of these, that I am setting up as a firewall between 2 legacy networks, both of which are 10M, and when I plug that port into the 10M hub, I get continuing kernel error messages. I'm considering locking it down, to se if that works, but have not tried that yet. AFAIK, phy on that nfe *does not* support 10mbit.
Sun X2100 on board RAID support?
I've got a bunch of Sun 2100 machines. Nice machine that i plan on doing a number of things with. I'd prefer to use OpenBSD on them for firewalls, and other network related tasks. I've got 2 x 250G drives in these machines, and want to mirror them. Under FreeBSD the built in RAID controller (OK semi-software RAID) works, but apparently it does not under OpenBSD. Is this correct? or am I missing something? If it's not supported, are there plans to add support for it? BTW, It's the 3.9 64 bit install set I'm trying to install. If I turn off RAID in the firmware, everything works fine. If I enable it the disks are not detected at all. -- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: hardware: Sun x2100 test results
On Wed, Feb 22, 2006 at 02:31:10PM +0100, Srebrenko Sehic wrote: > For those interested, here are the preliminary results of my Sun x2100 > tests. More hardware tests results available at > http://www.armorlogic.com/oscl/ > > Issues with Sun X2100 running OpenBSD/amd64 (-current from 22/02/2006) > > 1) possible bsd.mp issues due to misconfigured apic's > > ioapic0 at mainbus0 apid 2: pa 0x83738f24, version 11, 24 pins > ioapic0: misconfigured as apic 0 > ioapic0: remapped to apic 2 > > 2) nfe(4) shows a constant 100/interrupts a seconds without having > a link; only configured with ifconfig nfe0 127.0.0.1 255.0.0.0; it also has > the same interrupt rate when configured normally This should be fixed in -current by damien. > > 3) nfe(4) stops responding during stress-testing with netperf This also possibly. > > (transmitter box, Dell SC1425, dual em/gigabit) > (receiver box, Sun X2100, nfe/gigabit) > (both connected to a Dell PowerConnect 2708 gigabit switch) > > # netperf -H 192.168.0.60 -l 300 -- -s 64K -m 64K -M 64K -S 64K > TCP STREAM TEST to 192.168.0.60 > Recv SendSend > Socket Socket Message Elapsed > Size SizeSize Time Throughput > bytes bytes bytessecs.10^6bits/sec > > 65536 65536 65536298.96940.67 > > (transmitter: 8K/interrupts seconds on em0, 0% system idle) > (receiver: 83K/interrupts seconds on nfe0, 0% system idle) > > All fine. Stress test runs for 300 seconds without a problem. > > Now, we try the same test, but we increase the remote socket (nfe0) > send/recv buffer size to 128K. > > # netperf -H 192.168.0.60 -l 60 -- -s 128K -m 64K -M 64K -S 128K > > (transmitter: 8K/interrupts seconds on em9, 0% system idle) > (receiver: 100K/interrupts seconds on nfe0, 0% system idle) > > nfe0 will stop responding after few seconds; tcpdump shows nothing; > ifconfig down/up doesn't help; only a reboot does. > > 4) nviic(4) is probed/found, but provides no values to sensors(4) > framework. Details follow: > > nviic0 at pci0 dev 1 function 1 "NVIDIA nForce4 SMBus" rev 0xa2 > iic0 at nviic0 > iic0: addr 0x2e 00=00 01=00 02=00 03=00 04=00 05=00 06=00 07=00 08=00 > 09=00 0a=00 0b=00 0c=00 0d=00 0e=00 0f=00 10=00 11=00 12=00 13=00 > 14=00 15=00 16=00 17=00 18=00 19=00 1a=00 1b=00 1c=00 1d=00 1e=00 > 1f=03 20=63 21=75 22=c1 23=c1 24=bc 25=38 26=1c 27=19 28=39 29=02 > 2a=19 2b=03 2c=f5 2d=02 2e=2e 2f=02 30=81 31=55 32=55 33=00 34=00 > 35=00 36=00 37=00 38=00 39=00 3a=00 3b=00 3c=00 3d=00 3e=5c 3f=89 > 40=05 41=00 42=00 43=00 44=00 46=00 48=00 4a=00 4c=00 4e=ec 4f=50 > 50=ec 51=3c 52=ec 53=3c 54=5e 55=1a 56=5e 57=1a 58=5e 59=1a 5a=5e > 5b=1a 5c=02 5d=22 5e=42 5f=4b 60=ab 61=ab 62=e8 63=88 64=80 65=33 > 66=33 67=38 68=2d 69=2a 6a=3e 6b=3a 6c=37 6d=44 6e=40 6f=00 70=80 > 71=33 72=33 73=09 74=09 75=09 76=09 77=09 78=09 79=00 7a=10 7b=00 > 7c=44 7d=00 7e=00 7f=1c 80=0f 81=84 82=05 83=00 84=ec 85=9a 86=73 > 87=1d 88=26 89=00 8a=4d 8b=4d 8c=0b 8d=0b 8e=0c 8f=00 90=84 91=86 > 92=86 93=84 94=0c 95=0c 96=0c 97=5a 98=f1 99=be 9a=ac 9b=00 9d=00 > 9f=00 a0=00 a1=00 a2=0c a3=00 a4=02 a5=00 a6=00 a7=0b a8=0b a9=fe > ab=fe b1=00 b2=00 b3=00 b4=00 b5=00 b6=28 b7=28 b8=0e b9=0e ba=2b > bb=2b bc=00 bd=00 be=00 bf=00 c0=00 c1=00 c2=00 c3=00 c4=00 c5=00 > c6=00 c7=00 c8=00 c9=00 ca=00 cb=00 cc=00 cd=00 ce=00 cf=00 d0=00 > d1=00 d2=00 d3=00 d4=00 d5=00 d6=00 d7=00 d8=00 d9=00 da=00 db=00 > dc=00 dd=00 de=00 df=00 e0=00 e1=00 e2=00 e3=00 e4=00 e5=00 e6=00 > e7=00 e8=00 e9=00 ea=00 eb=00 ec=00 ed=00 ee=00 ef=00 f0=00 f1=00 > f2=00 f3=00 f4=00 f5=00 f6=00 f7=00 f8=00 f9=00 fa=00 fb=00 fc=00 > fd=00 fe=00 ff=00 > iic1 at nviic0 > iic1: addr 0x2e 00=00 01=00 02=00 03=00 04=00 05=00 06=00 07=00 08=00 > 09=00 0a=00 0b=00 0c=00 0d=00 0e=00 0f=00 10=00 11=00 12=00 13=00 > 14=00 15=00 16=00 17=00 18=00 19=00 1a=00 1b=00 1c=00 1d=00 1e=00 > 1f=03 20=63 21=75 22=c1 23=c1 24=bc 25=38 26=1c 27=19 28=39 29=02 > 2a=1a 2b=03 2c=fb 2d=02 2e=2e 2f=02 30=81 31=55 32=55 33=00 34=00 > 35=00 36=00 37=00 38=00 39=00 3a=00 3b=00 3c=00 3d=00 3e=5c 3f=89 > 40=05 41=00 42=00 43=00 44=00 46=00 48=00 4a=00 4c=00 4e=ec 4f=50 > 50=ec 51=3c 52=ec 53=3c 54=5e 55=1a 56=5e 57=1a 58=5e 59=1a 5a=5e > 5b=1a 5c=02 5d=22 5e=42 5f=4b 60=ab 61=ab 62=e8 63=88 64=80 65=33 > 66=33 67=38 68=2d 69=2a 6a=3e 6b=3a 6c=37 6d=44 6e=40 6f=00 70=80 > 71=33 72=33 73=09 74=09 75=09 76=09 77=09 78=09 79=00 7a=10 7b=00 > 7c=44 7d=00 7e=00 7f=1c 80=0f 81=84 82=05 83=00 84=bd 85=95 86=63 > 87=1d 88=46 89=00 8a=4d 8b=4d 8c=0b 8d=0b 8e=0c 8f=00 90=84 91=86 > 92=86 93=84 94=0c 95=0c 96=0c 97=5a 98=f1 99=be 9a=ac 9b=00 9d=00 > 9f=00 a0=00 a1=00 a2=0c a3=00 a4=02 a5=00 a6=00 a7=0b a8=0b a9=fe > ab=fe b1=00 b2=00 b3=00 b4=00 b5=00 b6=28
Re: hardware: Sun x2100 test results
On 2/22/06, Jonathan Gray <[EMAIL PROTECTED]> wrote: > > 2) nfe(4) shows a constant 100/interrupts a seconds without having > > a link; only configured with ifconfig nfe0 127.0.0.1 255.0.0.0; it also has > > the same interrupt rate when configured normally > > This should be fixed in -current by damien. Indeed. Just tried with if_nfe.c (r1.47). 0 interrupts/seconds without activity. Also, under the stress test, "systat vmstat" shows around 55% system idle (r1.47). Previously, it was 0% (r1.45). > > 3) nfe(4) stops responding during stress-testing with netperf > > This also possibly. Still happens. Settings the receiver (nfe0) socket buffer size to 256K rendered x2100/nfe0 useless. Still, only a reboot helps. This happened before (r.1.45) with socket buffer of 128K; now, it's just pushed a bit further.
Sun X2100 M2 ELOM and OpenBSD?
Has anyone gotten this system set up so you can use three NICs and connect to the Service Processor on the fourth? I got console redirected to the SP easily enough, and have tried disabling and cloning bge* via config(8) so it only binds to one of the bge ports as opposed to both of them. The interface I add (bge0) comes up, can be configured, upped and downed, but it it seems to be hosed: bge0 at pci6 dev 4 function 0 "Broadcom BCM5715" rev 0xa3, BCM5715 A3 (0x9003): apic 2 int 15 (irq 15), address 00:16:36:88:46:6e OUI 0x000818 model 0x0034 rev 0 at bge0 phy 1 not configured bge0: no PHY found! [r...@b-fw-sd]:[~]# ifconfig bge0 bge0: flags=8843 mtu 1500 lladdr 00:16:36:88:46:6e priority: 0 media: Ethernet manual (none) inet6 fe80::216:36ff:fe88:466e%bge0 prefixlen 64 scopeid 0x3 Some googling suggests that this should work, but I can't seem to get there. It's been a while since I've needed to go messing around in the OpenBSD kernel. Any insight would be much appreciated. Commands, dmesg from modified and unmodified systems follow: [r...@b-fw-sd]:[/]# cp bsd bsd.orig [r...@b-fw-sd]:[/]# config -e -o bsd.new bsd.orig OpenBSD 4.5 (GENERIC) #2052: Sat Feb 28 14:55:24 MST 2009 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC Enter 'help' for information ukc> find bge 149 bge* at pci* dev -1 function -1 flags 0x0 ukc> add bge0 Clone Device (DevNo, 'q' or '?') ? 149 Insert before Device (DevNo, 'q' or '?') ? 149 149 bge0 at pci* dev -1 function -1 flags 0x0 ukc> change bge0 149 bge0 at pci* dev -1 function -1 flags 0x0 change [n] y dev [-1] ? 4 function [-1] ? 0 flags [0] ? 149 bge0 changed 149 bge0 at pci* dev 4 function 0 flags 0x0 ukc> disable bge* 150 bge* disabled ukc> find bge 149 bge0 at pci* dev 4 function 0 flags 0x0 150 bge* at pci* disable dev -1 function -1 flags 0x0 ukc> quit Saving modified kernel. [r...@b-fw-sd]:[/]# mv bsd.new bsd [r...@b-fw-sd]:[~]# cat /etc/boot.conf set tty com1 dmesg from the modified system: OpenBSD 4.5 (GENERIC) #2052: Sat Feb 28 14:55:24 MST 2009 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 3756982272 (3582MB) avail mem = 3634565120 (3466MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xfbdc0 (36 entries) bios0: vendor Sun Microsystems version "S40_3A05" date 09/01/2006 bios0: Sun Microsystems X2100 M2 acpi0 at bios0: rev 2 acpi0: tables DSDT FACP APIC SPCR OEMB SSDT acpi0: wakeup devices PS2K(S4) PS2M(S4) NSMB(S4) USB0(S1) USB2(S1) NMAC(S5) NMAD(S5) P0P1(S4) HDAC(S4) BR10(S5) BR11(S5) BR12(S5) BR1E(S5) BCM1(S5) BR13(S5) BR14(S5) BR15(S5) SLPB(S4) PWRB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Dual-Core AMD Opteron(tm) Processor 1210, 1809.50 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,CX16,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 cpu at mainbus0: not configured ioapic0 at mainbus0 apid 2 pa 0xfec0, version 11, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P1) acpiprt2 at acpi0: bus 8 (BR10) acpiprt3 at acpi0: bus 7 (BR11) acpiprt4 at acpi0: bus 5 (BR12) acpiprt5 at acpi0: bus 6 (BR1E) acpiprt6 at acpi0: bus 4 (BR13) acpiprt7 at acpi0: bus 3 (BR14) acpiprt8 at acpi0: bus 2 (BR15) acpicpu0 at acpi0: PSS acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: PWRB ipmi at mainbus0 not configured cpu0: PowerNow! K8 1809 MHz: speeds: 1800 1000 MHz 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 "NVIDIA MCP55 ISA" rev 0xa3 nviic0 at pci0 dev 1 function 1 "NVIDIA MCP55 SMBus" rev 0xa3 iic0 at nviic0 spdmem0 at iic0 addr 0x50: 1GB DDR2 SDRAM ECC PC2-5300CL5 spdmem1 at iic0 addr 0x51: 1GB DDR2 SDRAM ECC PC2-5300CL5 spdmem2 at iic0 addr 0x52: 1GB DDR2 SDRAM ECC PC2-5300CL5 spdmem3 at iic0 addr 0x53: 1GB DDR2 SDRAM ECC PC2-5300CL5 iic1 at nviic0 ohci0 at pci0 dev 2 function 0 "NVIDIA MCP55 USB" rev 0xa1: apic 2 int 15 (irq 15), version 1.0, legacy support ehci0 at pci0 dev 2 function 1 "NVIDIA MCP55 USB" rev 0xa2: apic 2 int 7 (irq 7) usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "NVIDIA EHCI root hub" rev 2.00/1.00 addr 1 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
Re: Sun X2100 on board RAID support?
stan writes: I've got a bunch of Sun 2100 machines. Nice machine that i plan on doing a number of things with. I'd prefer to use OpenBSD on them for firewalls, and other network related tasks. I've got 2 x 250G drives in these machines, and want to mirror them. Under FreeBSD the built in RAID controller (OK semi-software RAID) works, but apparently it does not under OpenBSD. Is this correct? or am I missing something? If it's not supported, are there plans to add support for it? BTW, It's the 3.9 64 bit install set I'm trying to install. If I turn off RAID in the firmware, everything works fine. If I enable it the disks are not detected at all. As an aside to this, I would like to know if there are plans to support the x4[12]00 SAS controller -- this does work in FreeBSD -current. ./matt
Re: Sun X2100 on board RAID support?
Matt Kolb wrote: stan writes: I've got a bunch of Sun 2100 machines. Nice machine that i plan on doing a number of things with. I'd prefer to use OpenBSD on them for firewalls, and other network related tasks. I've got 2 x 250G drives in these machines, and want to mirror them. Under FreeBSD the built in RAID controller (OK semi-software RAID) works, but apparently it does not under OpenBSD. Is this correct? or am I missing something? If it's not supported, are there plans to add support for it? BTW, It's the 3.9 64 bit install set I'm trying to install. If I turn off RAID in the firmware, everything works fine. If I enable it the disks are not detected at all. As an aside to this, I would like to know if there are plans to support the x4[12]00 SAS controller -- this does work in FreeBSD -current. ./matt Using -current as of about a week after the last hack-a-thon, the x4?00 SAS worked. From a dmesg I posted on 6/6/06, here is the relevant part: | mpi0 at pci2 dev 3 function 0 "Symbios Logic SAS1064" rev 0x02: apic 6 int | 0 (irq 11) | scsibus0 at mpi0: 63 targets | sd0 at scsibus0 targ 2 lun 0: SCSI2 | 0/direct fixed | sd0: 69618MB, 69618 cyl, 16 head, 128 sec, 512 bytes/sec, 142577664 sec total It worked using both bsd and bsd.mp. But that was using the AMD64 port. As always, YMMV. Nick
Re: Sun X2100 on board RAID support?
Nick Shank writes: Matt Kolb wrote: As an aside to this, I would like to know if there are plans to support the x4[12]00 SAS controller -- this does work in FreeBSD -current. Using -current as of about a week after the last hack-a-thon, the x4?00 SAS worked. From a dmesg I posted on 6/6/06, here is the relevant part: | mpi0 at pci2 dev 3 function 0 "Symbios Logic SAS1064" rev 0x02: apic 6 int | 0 (irq 11) | scsibus0 at mpi0: 63 targets | sd0 at scsibus0 targ 2 lun 0: SCSI2 | 0/direct fixed | sd0: 69618MB, 69618 cyl, 16 head, 128 sec, 512 bytes/sec, 142577664 sec total It worked using both bsd and bsd.mp. But that was using the AMD64 port. As always, YMMV. Thanks a lot Nick. I guess the next logical question is into which stable release it will be available in. Thanks again! ./matt
Re: Sun X2100 on board RAID support?
On Fri, Aug 25, 2006 at 03:32:12PM -0400, Matt Kolb wrote: > Nick Shank writes: > >Matt Kolb wrote: > >>As an aside to this, I would like to know if there are plans to support > >>the x4[12]00 SAS controller -- this does work in FreeBSD -current. > > > >Using -current as of about a week after the last hack-a-thon, the x4?00 > >SAS worked. From a dmesg I posted on 6/6/06, here is the relevant part: > > > >| mpi0 at pci2 dev 3 function 0 "Symbios Logic SAS1064" rev 0x02: apic 6 > >int > >| 0 (irq 11) > >| scsibus0 at mpi0: 63 targets > >| sd0 at scsibus0 targ 2 lun 0: SCSI2 > >| 0/direct fixed > >| sd0: 69618MB, 69618 cyl, 16 head, 128 sec, 512 bytes/sec, 142577664 sec > >total > > > >It worked using both bsd and bsd.mp. But that was using the AMD64 port. As > >always, YMMV. > > Thanks a lot Nick. I guess the next logical question is into which stable > release it will be available in. 4.0, obviously. Joachim
Re: Sun X2100 on board RAID support?
On 26/08/2006, at 5:05 AM, Matt Kolb wrote: stan writes: I've got a bunch of Sun 2100 machines. Nice machine that i plan on doing a number of things with. I'd prefer to use OpenBSD on them for firewalls, and other network related tasks. I've got 2 x 250G drives in these machines, and want to mirror them. Under FreeBSD the built in RAID controller (OK semi-software RAID) works, but apparently it does not under OpenBSD. Is this correct? or am I missing something? If it's not supported, are there plans to add support for it? BTW, It's the 3.9 64 bit install set I'm trying to install. If I turn off RAID in the firmware, everything works fine. If I enable it the disks are not detected at all. As an aside to this, I would like to know if there are plans to support the x4[12]00 SAS controller -- this does work in FreeBSD - current. are you serious?
Current AMD64 DMESG on Sun X2100 M2
Hi all, Just for the records and for the interested in case you were looking at the new Sun X2100 M2. Here is the DMESG for it as of Sun Oct 22 22:42:18 MDT 2006. A few more devices are present in the current version oppose to the 4.0 release version. Very short differences: -mainbus0: Intel MP Specification (Version 1.4) (nVidia MCP55 ) +mainbus0: Intel MP Specification (Version 1.4) -pcib0 at pci0 dev 1 function 0 vendor "NVIDIA", unknown product 0x0364 rev 0xa3 +pcib0 at pci0 dev 1 function 0 "NVIDIA MCP55 ISA" rev 0xa3 -vga1 at pci1 dev 5 function 0 unknown vendor 0x1a03 product 0x2000 rev 0x00 +vga1 at pci1 dev 5 function 0 "ASPEED Technology AST2000" rev 0x00 -ukphy0 at nfe0 phy 2: Generic IEEE 802.3u media interface, rev. 1: OUI 0x005043, model 0x000b +eephy0 at nfe0 phy 2: Marvell 88E1149 Gigabit PHY, rev. 1 -ukphy1 at nfe1 phy 3: Generic IEEE 802.3u media interface, rev. 1: OUI 0x005043, model 0x000b +eephy1 at nfe1 phy 3: Marvell 88E1149 Gigabit PHY, rev. 1 -bge0 at pci6 dev 4 function 0 "Broadcom BCM5715" rev 0xa3, unknown BCM5714 (0x9003): apic 2 int 15 (irq 15), address 00:16:36:76:0e:25 +bge0 at pci6 dev 4 function 0 "Broadcom BCM5715" rev 0xa3, BCM5715 A3 (0x9003): apic 2 int 15 (irq 15), address 00:16:36:76:0e:25 -bge1 at pci6 dev 4 function 1 "Broadcom BCM5715" rev 0xa3, unknown BCM5714 (0x9003): apic 2 int 10 (irq 10), address 00:16:36:76:0e:26 +bge1 at pci6 dev 4 function 1 "Broadcom BCM5715" rev 0xa3, BCM5715 A3 (0x9003): apic 2 int 10 (irq 10), address 00:16:36:76:0e:26 All else stay the same. Full dmesg below if interested. Best, Daniel OpenBSD 4.0-current (GENERIC.MP) #999: Sun Oct 22 22:42:18 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 536408064 (523836K) avail mem = 447303680 (436820K) 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) cpu0 at mainbus0: apid 0 (boot processor) cpu0: Dual-Core AMD Opteron(tm) Processor 1210, 1809.55 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 "NVIDIA MCP55 ISA" 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: 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 wd
Re: Sun X2100 M2 ELOM and OpenBSD?
On Thu, Nov 19, 2009 at 3:28 PM, Bryan Allen wrote: > Has anyone gotten this system set up so you can use three NICs and connect to > the Service Processor on the fourth? > > I got console redirected to the SP easily enough, and have tried disabling and > cloning bge* via config(8) so it only binds to one of the bge ports as opposed > to both of them. > > The interface I add (bge0) comes up, can be configured, upped and downed, but > it it seems to be hosed: > > bge0 at pci6 dev 4 function 0 "Broadcom BCM5715" rev 0xa3, BCM5715 A3 (0x9003): apic 2 int 15 (irq 15), address 00:16:36:88:46:6e > OUI 0x000818 model 0x0034 rev 0 at bge0 phy 1 not configured > bge0: no PHY found! > > [r...@b-fw-sd]:[~]# ifconfig bge0 > bge0: flags=8843 mtu 1500 > lladdr 00:16:36:88:46:6e > priority: 0 > media: Ethernet manual (none) > inet6 fe80::216:36ff:fe88:466e%bge0 prefixlen 64 scopeid 0x3 > > Some googling suggests that this should work, but I can't seem to get there. > It's been a while since I've needed to go messing around in the OpenBSD kernel. > > Any insight would be much appreciated. > > Commands, dmesg from modified and unmodified systems follow: > > [r...@b-fw-sd]:[/]# cp bsd bsd.orig > [r...@b-fw-sd]:[/]# config -e -o bsd.new bsd.orig > OpenBSD 4.5 (GENERIC) #2052: Sat Feb 28 14:55:24 MST 2009 >dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC > Enter 'help' for information > ukc> find bge > 149 bge* at pci* dev -1 function -1 flags 0x0 > ukc> add bge0 > Clone Device (DevNo, 'q' or '?') ? 149 > Insert before Device (DevNo, 'q' or '?') ? 149 > 149 bge0 at pci* dev -1 function -1 flags 0x0 > ukc> change bge0 > 149 bge0 at pci* dev -1 function -1 flags 0x0 > change [n] y > dev [-1] ? 4 > function [-1] ? 0 > flags [0] ? > 149 bge0 changed > 149 bge0 at pci* dev 4 function 0 flags 0x0 > ukc> disable bge* > 150 bge* disabled > ukc> find bge > 149 bge0 at pci* dev 4 function 0 flags 0x0 > 150 bge* at pci* disable dev -1 function -1 flags 0x0 > ukc> quit > Saving modified kernel. > [r...@b-fw-sd]:[/]# mv bsd.new bsd > [r...@b-fw-sd]:[~]# cat /etc/boot.conf > set tty com1 > > dmesg from the modified system: > > OpenBSD 4.5 (GENERIC) #2052: Sat Feb 28 14:55:24 MST 2009 >dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC > real mem = 3756982272 (3582MB) > avail mem = 3634565120 (3466MB) > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xfbdc0 (36 entries) > bios0: vendor Sun Microsystems version "S40_3A05" date 09/01/2006 > bios0: Sun Microsystems X2100 M2 > acpi0 at bios0: rev 2 > acpi0: tables DSDT FACP APIC SPCR OEMB SSDT > acpi0: wakeup devices PS2K(S4) PS2M(S4) NSMB(S4) USB0(S1) USB2(S1) NMAC(S5) NMAD(S5) P0P1(S4) HDAC(S4) BR10(S5) BR11(S5) BR12(S5) BR1E(S5) BCM1(S5) BR13(S5) BR14(S5) BR15(S5) SLPB(S4) PWRB(S4) > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Dual-Core AMD Opteron(tm) Processor 1210, 1809.50 MHz > cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,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 > cpu at mainbus0: not configured > ioapic0 at mainbus0 apid 2 pa 0xfec0, version 11, 24 pins > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus 1 (P0P1) > acpiprt2 at acpi0: bus 8 (BR10) > acpiprt3 at acpi0: bus 7 (BR11) > acpiprt4 at acpi0: bus 5 (BR12) > acpiprt5 at acpi0: bus 6 (BR1E) > acpiprt6 at acpi0: bus 4 (BR13) > acpiprt7 at acpi0: bus 3 (BR14) > acpiprt8 at acpi0: bus 2 (BR15) > acpicpu0 at acpi0: PSS > acpibtn0 at acpi0: SLPB > acpibtn1 at acpi0: PWRB > ipmi at mainbus0 not configured > cpu0: PowerNow! K8 1809 MHz: speeds: 1800 1000 MHz > 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 "NVIDIA MCP55 ISA" rev 0xa3 > nviic0 at pci0 dev 1 function 1 "NVIDIA MCP55 SMBus" rev 0xa3 > iic0 at nviic0 > spdmem0 at iic0 addr 0x50: 1GB DDR2 SDRAM ECC PC2-5300CL5 > spdmem1 at iic0 addr 0x51: 1GB DDR2 SDRAM ECC PC2-5300CL5 > spdmem2 at iic0 addr 0x52: 1GB DDR2 SDRAM ECC PC2-5300CL5 > spdmem3 at iic0 addr 0x53: 1GB DDR2 SDRAM ECC PC2-5300CL5 > iic1 at nviic0 > ohci0 at pci0 dev 2 function 0 "NVIDIA MCP55 USB" rev 0xa1: apic 2 int 15 (irq 15), version 1.0, legacy support > ehci0 at pci0 dev 2 function 1 "NVIDIA MCP55 USB" rev 0xa2: apic 2 int 7 (irq 7) > usb0 at ehci0: USB revision 2.0 > uhub0 at usb0 "NVIDIA EHCI root hub" rev 2.00/1.00 addr 1 > pciide0 at pci0 dev 4 function 0 "NVIDIA MCP55 IDE" rev 0xa1: DMA, channel 0 configured to compatibility, channel 1 configured to compatibi
Re: Sun X2100 M2 ELOM and OpenBSD?
+-- | On 2009-11-19 16:25:47, Brent Jones wrote: | | On the old ELOM systems, AFAIK you need to define the ELOM port's | behavior inside the system BIOS. | Its hokey, and even Solaris/OpenSolaris have issues with those ELOM | ports. Don't know why Sun doesn't refund customers who got suckered | into getting ELOM systems. Haven't seen this behavior. The serial console is, by default, given to the BMC/service processor. I haven't had any real problems (other than ELOM's interface sucking) with it. It *is* annoying you can't upgrade the 2100s to ILOM, though. The core problem ELOM had initially is it defaulted to stupid port speeds, and was bound to ttyb instead of ttya. ILOM/ELOM speed has been unified for a while now, thankfully. Initial runs were pretty broken, though. The ttya/ttyb divergence between X2100 and X4xxxs is still true, and can't (afaik) be changed on the 2100s. As I said, I do have it redirectly properly: [r...@a-fw-sd]:[~]# ssh b-fw-sd-sp r...@b-fw-sd-sp's password: Sun(TM) Embedded Lights Out Manager Copyright 2004-2006 Sun Microsystems, Inc. All rights reserved. Version 3.24 Hostname: b-fw-sd IP address: 192.168.12.205 MAC address: 00:16:36:88:4A:82 System serial number: /SP -> start /SP/AgentInfo/console console activate successful press ESC ( to terminate session... OpenBSD/amd64 (b-fw-sd) (tty01) login: root Password: Last login: Thu Nov 19 18:01:06 on ttyp0 from OpenBSD 4.5 (GENERIC) #2052: Sat Feb 28 14:55:24 MST 2009 Welcome to OpenBSD: The proactively secure Unix-like operating system. You have new mail. Terminal type? [vt220] [r...@b-fw-sd]:[~]# I'd really just like to get bge0 working. :-) Cheers. -- bda cyberpunk is dead. long live cyberpunk.
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: 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
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.
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
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 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
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 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: High Interrupt for Intel 1000 PT Quad Port on Sun x2100
On 2007/06/22 13:47, Nigel Wohlers wrote: > bios0 at mainbus0: AT/286+ BIOS, date 03/20/06, BIOS32 rev. 0 @ 0xfa780, try a new BIOS and/or enabling ACPI - one-off for testing: boot -c, "enable acpi" - to create a modified kernel on-disk, use the -e flag to config(8).
Re: High Interrupt for Intel 1000 PT Quad Port on Sun x2100
Stuart Henderson wrote: > On 2007/06/22 13:47, Nigel Wohlers wrote: >> bios0 at mainbus0: AT/286+ BIOS, date 03/20/06, BIOS32 rev. 0 @ 0xfa780, > > try a new BIOS and/or enabling ACPI - one-off for testing: boot -c, > "enable acpi" - to create a modified kernel on-disk, use the -e flag > to config(8). > Thanks for your suggestions, Stuart. A bios upgrade has fixed the issue. Regards, N.
Re: High Interrupt for Intel 1000 PT Quad Port on Sun x2100
Nigel Wohlers wrote: > Stuart Henderson wrote: >> On 2007/06/22 13:47, Nigel Wohlers wrote: >>> bios0 at mainbus0: AT/286+ BIOS, date 03/20/06, BIOS32 rev. 0 @ 0xfa780, >> try a new BIOS and/or enabling ACPI - one-off for testing: boot -c, >> "enable acpi" - to create a modified kernel on-disk, use the -e flag >> to config(8). >> > > Thanks for your suggestions, Stuart. A bios upgrade has fixed the issue. > Unfortunately I now receive the emX watchdog timeout errors others are seeing. This occurs on both current and 4.1 even after applying the recent patch by Mark Kettenis. (http://marc.info/?l=openbsd-tech&m=117848134811286&w=2) Thanks, N.
