Re: Recommended laptop
On Tuesday 22 December 2009 04:57:55 STeve Andre' wrote: On Monday 21 December 2009 22:48:45 James Hozier wrote: This will be my first purchase that is focused primarily on having only OpenBSD on it and nothing else to be used as a main workstation. The budget is around $900 or so. I'm looking for something with quality parts and probably have everything supported and compatible with OpenBSD straight out of the box (like the graphics/sound, wireless card, etc.) I've heard that most developers use Thinkpads. Which model would be a good suggestion? A problem is that $900 isn't going to get you a thinkpad and a multi-year warranty. If you stay away from nvidia video, just about all the thinkpads are going to work with the ooccaisonal exception of the wireless card, and I'm not sure that hasn't shrunk a bunch, the ones that don't work. My W500 runs OpenBSD wonderfully. Looking at the Lenovo site I see a T500 with a 15 screen with *led* back light, 160G disk 2.4G core two something, intel wifi and intel graphics for $849. I don't know the status of the Intel graphics card, but you could get that, except it has a 1 year warranty. There are discounts if you can get it through an educational organization, etc. --STeve Andre' If you get a Thinkpad stay clear of the SL300. It's cheap crap.
Re: Supporting OpenBSD
On Wednesday 09 September 2009 08:45:41 you wrote: I have a few questions about the stores in Australia (since we're on the topic here). (http://www.openbsd.org/orders.html#au/lsl) LSL doesn't seem to be doing pre-orders (see http://www.lsl.com.au/advanced_search_result.php?keywords=openbsdx=0y=0); does anybody know about the status of ESI? I cannot find any mention of OpenBSD, let alone any pre-orders on their site (http://www.esi.com.au/). If anybody living in Australia could help out to call the store/s (I dont live there - it's just that this is the nearest store to me) and enquire, that would be great. thanks, -jf Having spoken to some OpenBSD users in Australia it appears as if your best bet is to order directly from https://https.openbsd.org/cgi-bin/order That way you can make a per-order as well. Regards Johan M:son
Re: OT: reliable 4-port switches
On Wednesday 15 August 2007 03:30:48 Jacob Yocom-Piatt wrote: i'm carping a couple machines with public IPs and would appreciate recommendations for reliable 4-port switches for the task. there is a single ethernet cable uplink to the ISP that i will feed into the switch, then to the firewalls. i ask this because i've bought cheapo 4-port switches in the past and had them seize-up on occasion. seize-ups are totally unacceptable to me for this application so suggestions on which brand or model would be appreciated. otherwise my wallet tells me to go with the 25 USD 3-com 4-port switch... cheers, jake There's an obvious problem with this approach - you can't tell the link state of your uplink, so thus it would probably be wise to spend the extra money and get a managed switch of some kind so that you can monitor your ISP connection over time. Regards Johan M:son
Re: Chances of this hardware running OpenBSD?
It is the same scam and con artists behind this scheme as in the other cases of amiga vapoware that we've seen over the course of the last ten years or so. So please, don't start foaming at the mouth before you actually hold one of these units in your hand. IMHO this attitude destroys (not only) their business model; of course one need pre-orders before they really start to create PCBs et al. out of nothing. In my not so humble opinion you should go read this article, I believe saying I told you so is unnecessary at this point. http://www.osnews.com/comment.php?news_id=18018 Regards Johan M:son Lindman
Re: Chances of this hardware running OpenBSD?
On Tuesday 08 May 2007, you wrote: Hi list, during the last days news popped up [0] verifying that the new 'Power System' (aka Amiga) will be based on PA Semi's very nice PowerPC chip. I was disappointed quite often by vaporware in the Amiga universe, especially during the hard, long time of agony of this system. However, as this really might become reality, how are chances to port OpenBSD to this machine? I'd like to be able to replace my x86/amd64 workstation at work by something non-SPARCy [I *like* SPARC] ;) [0] -- http://www.amiga.org/modules/news/article.php?storyid=7310 -- I think sex is better than logic, but I can't prove it. Timo, Please check the URL you provided yourself. It is the same scam and con artists behind this scheme as in the other cases of amiga vapoware that we've seen over the course of the last ten years or so. So please, don't start foaming at the mouth before you actually hold one of these units in your hand. The Pegasos story ought to have taught us all a very valuable lesson about the fraudsters that have been (and I believe still are) dealing with what is left of Amiga. Regards Johan M:son
Re: 4.0 on Dell 2650
On Saturday 10 February 2007 00:09, you wrote: Hi guys Just wanted to ask if any of you have experience putting openbsd 4.0 to a dell 2650? I tried to boot up using both cd40.iso and floppyB40.fs but it always says no disks found. haven't seen any scsi drives loaded. I tried an initial setup using RAID 5 hardware (configured) and see if 4.0 will see it but with no luck I even tried it with mirror and just a regular stripe.. with still no avail, makes me wonder does this mean openbsd doesn't support scsi controllers build into dell boxes? well any comments or suggestions will be very much appreciated. Since you didn't provide a dmesg (boo) I can only guess, but typically Dell 2650s are equipped with aac(4) ROMB. aac(4) is not a supported driver anymore as can be seen in the FAQ here (scroll down to 12.7.7); http://www.openbsd.org/faq/faq12.html Though it should be noted that as of revision 1.25 aac has improved somewhat and is a bit less error prone as experienced by some of us using this driver. But still, using aac with OpenBSD should not be recommended to those faint of heart. Regards Johan M:son
Re: Slow write performance on Compaq Smart Array 64xx (ciss0)
On Sunday 28 January 2007 22:21, you wrote: On Sun, Jan 28, 2007 at 11:28:27AM -0800, Joe wrote: Some more tests: # dd if=/dev/zero of=./testfile count=100 100+0 records in 100+0 records out 51200 bytes transferred in 16.354 secs (31306797 bytes/sec) # dd if=./testfile of=/dev/null count=100 100+0 records in 100+0 records out 51200 bytes transferred in 6.013 secs (85137347 bytes/sec) So is 30MBps acceptable write speed for RAID 5 on a Compaq Smart Array 64xx controller? Could this be a driver issue? I doubt it: clearly it can transfer data at 85MBps, and it's unlikely that the SCSI bus can transfer data faster in one direction than the other. I don't know this controller specifically, but maybe a better controller would give you better RAID5 write performance. Or maybe something isn't quite set up correctly on the card (e.g. if there's NVRAM write-through cache, maybe the battery isn't present or it's disabled for some other reason) You're right. Most probably this guy joe is lacking Battery Backed Write Cache enabler. HP ships their boxes without it as default. This will likely give some performance penalty. I told him to check if he has a BBWC in a previous mail but as most idiots on misc he ignored it and sent another mail asking the same question. :-) Regards Johan M:son
Re: How to use bioctl with ciss0?
On Sunday 28 January 2007 14:19, Vijay Sankar wrote: Good day, What do I have to do to get info about a raid array on a HP DL380 G4 with bioctl? Is this supported? # bioctl -v -h ciss0 bioctl: Can't locate ciss0 device via /dev/bio That's interesting, I can replicate this problem on my HP DL365 machines and current, but not on HP DL385 and current. dmesg, 365 then 385... bioctl -v ciss0 bioctl: Can't locate ciss0 device via /dev/bio OpenBSD 4.0-current (GENERIC.MP) #1: Mon Nov 27 17:16:55 CET 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 1073082368 (1047932K) avail mem = 907214848 (885952K) using 22937 buffers containing 107515904 bytes (104996K) of memory mainbus0 (root) bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xee000 (59 entries) bios0: HP ProLiant DL365 G1 acpi at mainbus0 not configured ipmi0 at mainbus0: version 2.0 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 2210, 1800.37 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 200MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Dual-Core AMD Opteron(tm) Processor 2210, 1800.07 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 4 is type PCI mpbios: bus 8 is type PCI mpbios: bus 9 is type PCI mpbios: bus 10 is type PCI mpbios: bus 11 is type PCI mpbios: bus 12 is type PCI mpbios: bus 13 is type PCI mpbios: bus 16 is type PCI mpbios: bus 19 is type PCI mpbios: bus 21 is type PCI mpbios: bus 241 is type ISA ioapic0 at mainbus0 apid 8 pa 0xfec0, version 11, 16 pins ioapic1 at mainbus0 apid 9 pa 0xfec01000, version 11, 16 pins pci0 at mainbus0 bus 0: configuration mode 1 vga1 at pci0 dev 3 function 0 ATI ES1000 rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) Compaq iLO rev 0x03 at pci0 dev 4 function 0 not configured Compaq iLO rev 0x03 at pci0 dev 4 function 2 not configured uhci0 at pci0 dev 4 function 4 Hewlett-Packard USB rev 0x00: apic 9 int 10 (irq 11) usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Hewlett-Packard UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered Hewlett-Packard IPMI rev 0x00 at pci0 dev 4 function 6 not configured ppb0 at pci0 dev 5 function 0 ServerWorks HT-1000 PCI rev 0x00 pci1 at ppb0 bus 1 ppb1 at pci1 dev 13 function 0 ServerWorks HT-1000 PCIX rev 0xc0 pci2 at ppb1 bus 2 piixpm0 at pci0 dev 6 function 0 ServerWorks HT-1000 rev 0x00: polling iic0 at piixpm0: disabled to avoid ipmi0 interactions pciide0 at pci0 dev 6 function 1 ServerWorks HT-1000 IDE rev 0x00: DMA atapiscsi0 at pciide0 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: TEAC, DW-224E-C, C.8D SCSI0 5/cdrom removable cd0(pciide0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 0 pcib0 at pci0 dev 6 function 2 ServerWorks HT-1000 LPC rev 0x00 ohci0 at pci0 dev 7 function 0 ServerWorks HT-1000 USB rev 0x01: apic 8 int 5 (irq 5), version 1.0, legacy support usb1 at ohci0: USB revision 1.0 uhub1 at usb1 uhub1: ServerWorks OHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ohci1 at pci0 dev 7 function 1 ServerWorks HT-1000 USB rev 0x01: apic 8 int 5 (irq 5), version 1.0, legacy support usb2 at ohci1: USB revision 1.0 uhub2 at usb2 uhub2: ServerWorks OHCI root hub, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0 at pci0 dev 7 function 2 ServerWorks HT-1000 USB rev 0x01: apic 8 int 5 (irq 5) usb3 at ehci0: USB revision 2.0 uhub3 at usb3 uhub3: ServerWorks EHCI root hub, rev 2.00/1.00, addr 1 uhub3: 4 ports with 4 removable, self powered pchb0 at pci0 dev 24 function 0 AMD AMD64 HyperTransport rev 0x00 pci3 at pchb0 bus 8 ppb2 at pci3 dev 15 function 0 ServerWorks HT-2100 PCIE rev 0xa2 pci4 at ppb2 bus 19 ppb3 at pci3 dev 16 function 0 ServerWorks HT-2100 PCIE rev 0xa2 pci5 at ppb3 bus 16 ppb4 at pci3 dev 17 function 0 ServerWorks HT-2100 PCIE rev 0xa2 pci6 at ppb4 bus 9 ppb5 at pci6 dev 0 function 0 ServerWorks PCIE-PCIX rev 0xc2 pci7 at ppb5 bus 10 bnx0 at pci7 dev 0 function 0 Broadcom
Re: Slow IO on Compaq Smart Array 6
On Friday 26 January 2007 22:17, you wrote: I've got a new box with the following hardware: 2x Intel Xeon 3Ghz 4 GB RAM 2x 72GB U320 10K drives I've configured the RAID for RAID-0 (i have reasons for this). During installation, I create a 20GB / and 106?GB/data partition. It took about 20 minutes to run newfs on the drives. Why? I'll post a dmesg once the install is done. Check that you have a BBWC in your box, for some idiotic reason HP ship their machines without BBWC as standard and without that you don't get any write cache, only read cache. That'll inevitably affect performance to some extent. Regards Johan M:son
Re: Ethernet Card
On Wednesday 17 May 2006 10:44, you wrote: I see. Thanks a lot and sorry for the stupid question. By the way, is there any way, how to use the two NICs for load balancing? Karel Yes there is. trunk(4) will tell you how. Regards Johan M:son
Re: AMD64 Experience Report: Pundit-AE3
On Monday 28 November 2005 10.30, you wrote: Hi. Just in case anybody's interested in building an amd64 machine for using with OpenBSD: I wouldn't recommend the asus pundit ae3 barebone. It is based on what seems to be a KS-8-MV motherboard which has an sis chip providing SATA, Network and Video. As of 3.8 (release and latest snapshot) none of the above work: * SVGA Chip works in VESA mode for X11. This is only a small problem as an AGP expansion slot (slow profile form-factor though) is available. * Network interface isn't recognized. * SATA controller shows up as pciide alright, but any access to disk fails. Strictly from the hardware point of view I initially bought a sempron64 2600+ CPU which was reported as unsupported by the motherboard which prevented the system from booting. Changing the CPU to a 3000+ athlon 64 fixed the problem. Too bad it wouldn't work since it's a really slim machine with a nice case, 64bit CPU really fast HDD and ram and costs less than a mac mini. Where's the dmesg? Regards Johan M:son
Re: Marvell 8053 Based NIC
On Wednesday 16 November 2005 08.22, you wrote: I am attempting an install of OpenBSD 3.8 on a machine with an Marvell Yukon 8053 based four port PCIe NIC and am encountering the following error (from syslog) Has anyone had luck with this NIC? 1. Entire dmesg please, snippets of dmesgs are not very helpful. 2. Could you please try -current, that way you will see if this problem has been fixed recently. 3. If in doubt please read http://www.openbsd.org/report.html Regards Johan M:son Lindman
Re: ciss is slow and uses all the CPU
I think this is enough to file a Problem Report, could you please do that? Read sendbug(1) and http://www.openbsd.org/report.html if unsure. I have a DL380 G3 which shows the same ciss0: cmd_stat 2 scsi_stat 0x0 messages so chances are mine's affected as well, I'll try to load it a bit and see what happens. Regards Johan M:son On Tuesday 01 November 2005 18.18, you wrote: I installed a snapshot on an HP Proliant DL360, and everything seems fine except that disk performance is terrible. Just running bonnie++ for a quick test it can only do 8MB/s write because its using 100% of the CPU. Top shows its all being spent in system time. For contrast, my slow laptop ATA drive does 14MB/s at 3% CPU usage. Adam OpenBSD 3.8-current (GENERIC) #169: Sun Oct 2 15:06:50 MDT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Xeon(TM) CPU 3.06GHz (GenuineIntel 686-class) 3.07 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,A CPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT- ID real mem = 2147041280 (2096720K) avail mem = 1953218560 (1907440K) using 4278 buffers containing 107454464 bytes (104936K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 12/31/99, BIOS32 rev. 0 @ 0xf pcibios0 at bios0: rev 2.1 @ 0xf/0x2000 pcibios0: PCI BIOS has 7 Interrupt Routing table entries pcibios0: PCI Interrupt Router at 000:15:0 (ServerWorks CSB5 SouthBridge rev 0x00) pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x4000 0xcc000/0x1800 0xee000/0x2000! cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 ServerWorks CNB20-HE rev 0x31 pchb1 at pci0 dev 0 function 1 ServerWorks CNB20-HE rev 0x00 pchb2 at pci0 dev 0 function 2 ServerWorks CNB20-HE rev 0x00 pci1 at pchb2 bus 1 bge0 at pci1 dev 2 function 0 Broadcom BCM5703X rev 0x02, BCM5703 A2 (0x1002): irq 11 address 00:0b:cd:d1:2a:c7 brgphy0 at bge0 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2 vga1 at pci0 dev 3 function 0 ATI Rage XL rev 0x27 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ciss0 at pci0 dev 4 function 0 Compaq Smart Array 5i/532 rev.2 rev 0x01: irq 3 ciss0: 1 LD HW rev 1 FW 2.38/2.38 lmap 4000:0 scsibus0 at ciss0: 1 targets sd0 at scsibus0 targ 0 lun 0: COMPAQ, LOGICAL VOLUME, 2.38 SCSI0 0/ direct fixed ciss0: cmd_stat 2 scsi_stat 0x0 ciss0: cmd_stat 2 scsi_stat 0x0 sd0: 69459MB, 69459 cyl, 64 head, 32 sec, 512 bytes/sec, 142253280 sec total vendor Compaq, unknown product 0xb203 (class system subclass miscellaneous, rev 0x01) at pci0 dev 5 function 0 not configured vendor Compaq, unknown product 0xb204 (class system subclass miscellaneous, rev 0x01) at pci0 dev 5 function 2 not configured pcib0 at pci0 dev 15 function 0 ServerWorks CSB5 SouthBridge rev 0x93 pciide0 at pci0 dev 15 function 1 ServerWorks CSB5 IDE rev 0x93: DMA atapiscsi0 at pciide0 channel 0 drive 0 scsibus1 at atapiscsi0: 2 targets cd0 at scsibus1 targ 0 lun 0: COMPAQ, CRN-8245B, 2.19 SCSI0 5/cdrom removable cd0(pciide0:0:0): using PIO mode 4, DMA mode 2 pchb3 at pci0 dev 15 function 3 ServerWorks CSB5 PCI rev 0x00 pchb4 at pci0 dev 17 function 0 ServerWorks CIOBX2 rev 0x05 pchb5 at pci0 dev 17 function 2 ServerWorks CIOBX2 rev 0x05 pci2 at pchb5 bus 4 bge1 at pci2 dev 2 function 0 Broadcom BCM5703X rev 0x02, BCM5703 A2 (0x1002): irq 10 address 00:0b:cd:d1:2a:c6 brgphy1 at bge1 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2 isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pmsi0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pmsi0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 sysbeep0 at pcppi0 npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec biomask e3ed netmask efed ttymask ffef pctr: user-level cycle counter enabled ciss0: cmd_stat 2 scsi_stat 0x0 ciss0: cmd_stat 2 scsi_stat 0x0 dkcsum: sd0 matches BIOS drive 0x80 root on sd0a ciss0: cmd_stat 2 scsi_stat 0x0 ciss0: cmd_stat 2 scsi_stat 0x0 ciss0: cmd_stat 2 scsi_stat 0x0 ciss0: cmd_stat 2 scsi_stat 0x0 rootdev=0x400 rrootdev=0xd00 rawdev=0xd02 ciss0: cmd_stat 2 scsi_stat 0x0 ciss0: cmd_stat 2 scsi_stat 0x0 ciss0: cmd_stat 2 scsi_stat 0x0 ciss0: cmd_stat 2 scsi_stat 0x0 !DSPAM:4367aa85188902939917969!
Re: Two Isp Fault Tollerance Help
On Thursday 06 October 2005 10.24, you wrote: Hi to all. One of my clients has got an Internet connection with a no much affidable provider. He reports continual disconnection and so on. I would like to do a second connection with another provider to obtain a sort of redundancy, a fault tollerance. What I have to do to obtain the automatic connection with both of the providers and to shift to the one that is connected when the other is in trouble? ( without problems for the client). Border Gateway Protocol. See bgpd(8). Regards Johan M:son
Re: Two Isp Fault Tollerance Help
On Friday 07 October 2005 15.33, you wrote: On Fri, 7 Oct 2005 14:29:08 +0200 Johan M:son Lindman [EMAIL PROTECTED] wrote: One of my clients has got an Internet connection with a no much affidable provider. He reports continual disconnection and so on. I would like to do a second connection with another provider to obtain a sort of redundancy, a fault tollerance. What I have to do to obtain the automatic connection with both of the providers and to shift to the one that is connected when the other is in trouble? ( without problems for the client). Border Gateway Protocol. Doesn't it imply that said client has its own IP addresses range and not NATing behind one single ISP-provided address ? Well the original post doesn't tell us jack about the type of connections this client of his has, really. It merely state that there's problem with connectivity at customer site. I'm not going to make assumptions either way, but for proper fault tolerant internet connectivity BGP is one (the?) way to go and is very well supported by OBSD. Regards Johan M:son
Re: Need Opteron Motherboard Help - Supermicro?
On Wednesday 28 September 2005 03.31, you wrote: On Tuesday 27 September 2005 18.47, Mike wrote: Hi All, Anyone here using one of the Supermicro AMD 8131-based motherboards on their OBSD system? If these are unsuitable for OpenBSD, then what AMD64 or Opteron motherboards are the current cream of the crop that do work well with OpenBSD? HP DL145 (G1) work well, dmesg below, haven't tried Supermicro. Though you should probably want to avoid the newer Nvidia nForce 4 based Opteron motherboards which seems to be all the rage these days. nForce4 has got several issues with smp (ehci, AC97 and SATA not working with GENERIC.MP) and it's not able to find all ppb(4)s properly. It should be noted that the ppb problem is only known to happen on the HP DL145 G2 server. Regards Johan M:son
Re: Need Opteron Motherboard Help - Supermicro?
On Tuesday 27 September 2005 18.47, Mike wrote: Hi All, Anyone here using one of the Supermicro AMD 8131-based motherboards on their OBSD system? If these are unsuitable for OpenBSD, then what AMD64 or Opteron motherboards are the current cream of the crop that do work well with OpenBSD? HP DL145 (G1) work well, dmesg below, haven't tried Supermicro. Though you should probably want to avoid the newer Nvidia nForce 4 based Opteron motherboards which seems to be all the rage these days. nForce4 has got several issues with smp (ehci, AC97 and SATA not working with GENERIC.MP) and it's not able to find all ppb(4)s properly. Regtards Johan M:son OpenBSD 3.6 (GENERIC) #136: Fri Sep 17 12:28:10 MDT 2004 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 1073278976 (1048124K) avail mem = 909922304 (888596K) using 22937 buffers containing 107536384 bytes (105016K) of memory mainbus0 (root) cpu0 at mainbus0: (uniprocessor) cpu0: AMD Opteron(tm) Processor 242, 1594.41 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,NXE,MMXX,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 pci0 at mainbus0 bus 0: configuration mode 1 ppb0 at pci0 dev 1 function 0 AMD 8131 PCIX rev 0x12 pci1 at ppb0 bus 3 AMD 8131 PCIX IOAPIC rev 0x01 at pci0 dev 1 function 1 not configured ppb1 at pci0 dev 2 function 0 AMD 8131 PCIX rev 0x12 pci2 at ppb1 bus 2 bge0 at pci2 dev 3 function 0 Broadcom BCM5704C rev 0x02: irq 10 address 00:00:1a:19:c0:0e brgphy0 at bge0 phy 1: BCM5704 10/100/1000baseT PHY, rev. 0 bge1 at pci2 dev 3 function 1 Broadcom BCM5704C rev 0x02: irq 11 address 00:00:1a:19:c0:0d brgphy1 at bge1 phy 1: BCM5704 10/100/1000baseT PHY, rev. 0 AMD 8131 PCIX IOAPIC rev 0x01 at pci0 dev 2 function 1 not configured ppb2 at pci0 dev 6 function 0 AMD 8111 PCI-PCI rev 0x07 pci3 at ppb2 bus 1 ohci0 at pci3 dev 0 function 0 AMD 8111 USB rev 0x0b: irq 10, version 1.0, legacy support ohci0: SMM does not respond, resetting usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1 at pci3 dev 0 function 1 AMD 8111 USB rev 0x0b: irq 10, version 1.0, legacy support ohci1: SMM does not respond, resetting usb1 at ohci1: USB revision 1.0 uhub1 at usb1 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered vga1 at pci3 dev 4 function 0 ATI Rage XL rev 0x27 wsdisplay0 at vga1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) AMD AMD8111 LPC rev 0x05 at pci0 dev 7 function 0 not configured pciide0 at pci0 dev 7 function 1 AMD 8111 IDE rev 0x03: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: Maxtor 6E040L0 wd0: 16-sector PIO, LBA, 38166MB, 78165360 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 6 pciide0: channel 1 disabled (no drives) AMD 8111 ACPI rev 0x05 at pci0 dev 7 function 3 not configured pchb0 at pci0 dev 24 function 0 AMD AMD64 HyperTransport rev 0x00 pchb1 at pci0 dev 24 function 1 AMD AMD64 Address Map rev 0x00 pchb2 at pci0 dev 24 function 2 AMD AMD64 DRAM Cfg rev 0x00 pchb3 at pci0 dev 24 function 3 AMD AMD64 Misc Cfg rev 0x00 isa0 at mainbus0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pmsi0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pmsi0 mux 0 lm0 at isa0 port 0x290/8: W83627HF dkcsum: wd0 matched BIOS disk 80 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302
Re: HP DL145 G2?
On Monday 25 July 2005 16.52, Mike Shaw wrote: Hey folksI'm about to build another obsd server for some pseudo-mission critical work, and HP is kind of our standard now. I've verified with someone off list that a DL140's run well, but for performance and philosophical reasons I'm choosing AMD...looking at a DL145 G2 2Ghz SATA. I saw some troubles on the archives regarding this, but I wanted to verify the latest: * Are the broadcom nics reliable at this point? * I'm assuming amd64 OpenBSD is ready for prime time. * Any potential gotchas? Currently the DL145 G2 is not well supported for various reasons. There's an issue with the pci shitz on this server which makes OBSD unable to detect cards seated in the expansion slots. Since this server is based on Nvidia (nForce4) chipset I guess it's not prio one to support it due to lack of documentation etc. So before you shop HP stuff make sure it's not fitted with Nvidia motherboards as in the case with DL 145G2. Regards Johan M:son
Re: USB2 (EIDE) bad mojo...
On Tuesday 19 July 2005 21:43, you wrote: WARNING, this is likely going to sound offensive to some people... Johan M:son Lindman wrote: On Tuesday 19 July 2005 17:02, you wrote: Since OpenBSD is not very helpful in this case I can only enclose the dmesg without the enclosure plugged in. But first here's the info for the enclosure as Linux sees it (dmesg): Read this, http://www.openbsd.org/report.html (hint, you should try a -current snapshot to see if the problem has been fixed recently). Interesting assumption on your part that I hadn't read that document. I I did not assume anything. It's a good document everyone should read it, seeing as you have read it, good on you. have read it. And it doesn't say anything about trying current instead of the stable branch as I have. Your hint doesn't help most users as they don't run current but stable. This OpenBSD list seems to be filled with some of the most discourteous netizens I've encountered. If you You know, every so often people who actually get good sound advice on this list go all defensive, that's strange considering the people who help you are actually doing you a favour, they go out of their way to help you. wanted to say that I should use the current because there is a know problem pertaining to my situation that was fixed in current -- Then say so. And yes I have read the changelog for current and it does have entries for umass. But they provide no indication as to what problems the changes address. So they are useless from a users perspective. And Changelogs are not useless, of course. Anyways you don't HAVE to comprehend the changelog, that's why I told you to try -current, then you'd see first hand if it works or not. I'm not about to go digging in source histories and sources themselves to find out any more information than what is in the changelog. So please, if you, or others know of specific changes that pertain to my problem mention them. And I will try and figure out a way to use that As usual everyone else should do your [digging searching testing] for you, why am I not suprised? specific part of current, because I just can't follow current on a production server (as other users will also tell you). And if there's a This is the main problem right there. You're tinkering and fiddling with a production server. Don't. FAQ on how to use only some specific current changes, instead of the complete ball of wax, that would also be appreciated. No it doesn't work that way. Back porting changes from -current to -stable is not recommended nor supported. Just go for -current and you'll be good. As Theo like to stress from time to time, the quality of -current snapshots is very high. Regards Johan M:son
HP DL145 G2, new Opteron/nForce4 based server - mpt(4) problem
We recently got a bunch of the new HP DL145 G2 servers. In a rather retarded move HP decided that these generation 2 of the excellent DL145 series servers should be implemented on top of Nvidias nForce 4 chipset instead of as with the first generation which used the reference AMD chipset. So I tried installing latest snapshot on one of the DL145 G2s. The resulting dmesg is below. These DL145s have got some sort of mpt(4) in them however it is not at all recognized in the dmesg, hence I can't install OBSD. Now even if the mpt chipset was a new one that wasn't recognized it should still turn up in dmesg as an unconfigured device, right? The funny thing is it doesn't. I'd file a PR but I have this intense feeling I've missed something painfully obvious so I'm trying misc first. Could it be that the mpt is hiding behind some funny PCI bridge or PCI riser board that is not supported? Regards Johan M:son OpenBSD 3.7-current (RAMDISK_CD) #406: Tue Jul 12 13:28:26 MDT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 1072406528 (1047272K) avail mem = 909205504 (887896K) using 22937 buffers containing 107450368 bytes (104932K) of memory mainbus0 (root) cpu0 at mainbus0: (uniprocessor) cpu0: AMD Opteron(tm) Processor 246, 2009.49 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,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 pci0 at mainbus0 bus 0: configuration mode 1 Nvidia nForce4 DDR rev 0xa3 at pci0 dev 0 function 0 not configured Nvidia nForce4 ISA rev 0xa3 at pci0 dev 1 function 0 not configured Nvidia nForce4 SMBus rev 0xa2 at pci0 dev 1 function 1 not configured ohci0 at pci0 dev 2 function 0 Nvidia nForce4 USB rev 0xa2: irq 10, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: Nvidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ehci0 at pci0 dev 2 function 1 Nvidia nForce4 USB rev 0xa3: irq 11 ehci0: timed out waiting for BIOS usb1 at ehci0: USB revision 2.0 uhub1 at usb1 uhub1: Nvidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered pciide0 at pci0 dev 6 function 0 Nvidia nForce4 IDE rev 0xa2: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility pciide0: channel 0 disabled (no drives) pciide0: channel 1 disabled (no drives) pciide1 at pci0 dev 8 function 0 Nvidia nForce4 SATA 2 rev 0xa3: DMA (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide1: using irq 10 for native-PCI interrupt pciide1: channel 0 ignored (not responding; disabled or no drives?) pciide1: channel 1 ignored (not responding; disabled or no drives?) ppb0 at pci0 dev 9 function 0 Nvidia nForce4 PCI-PCI rev 0xa2 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 Nvidia GeForce2 MX rev 0xb2 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) ppb1 at pci0 dev 12 function 0 Nvidia nForce4 PCIE rev 0xa3 pci2 at ppb1 bus 2 bge0 at pci2 dev 0 function 0 Broadcom BCM5721 rev 0x11, BCM5750 B1 (0x4101): irq 11 address 00:13:21:b5:53:b6 brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0 ppb2 at pci0 dev 13 function 0 Nvidia nForce4 PCIE rev 0xa3 pci3 at ppb2 bus 3 bge1 at pci3 dev 0 function 0 Broadcom BCM5721 rev 0x11, BCM5750 B1 (0x4101): irq 10 address 00:13:21:b5:53:b7 brgphy1 at bge1 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0 ppb3 at pci0 dev 14 function 0 Nvidia nForce4 PCIE rev 0xa3 pci4 at ppb3 bus 4 pchb0 at pci0 dev 24 function 0 AMD AMD64 HyperTransport rev 0x00 pchb1 at pci0 dev 24 function 1 AMD AMD64 Address Map rev 0x00 pchb2 at pci0 dev 24 function 2 AMD AMD64 DRAM Cfg rev 0x00 pchb3 at pci0 dev 24 function 3 AMD AMD64 Misc Cfg rev 0x00 isa0 at mainbus0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 rd0: fixed, 3584 blocks root on rd0a rootdev=0x1100 rrootdev=0x2f00 rawdev=0x2f02 umass0 at uhub0 port 3 configuration 1 interface 0 umass0: TEAC USB CD-ROM 210PU, rev 1.10/1.36, addr 2 umass0: using ATAPI over Bulk-Only scsibus0 at umass0: 2 targets cd0 at scsibus0 targ 1 lun 0: TEAC, CD-210PU, 10A6 SCSI0 5/cdrom removable
Re: em0 and SMP problem
On Friday 01 July 2005 21.49, MichaE Koc wrote: Hello all, I've a problem with em0 (and eventually any other nic connected to the pci bus) on double Xeon, while I run smp kernel. What problem? Are you not even going to describe your problem? I have no idea what could couse it, there was problem with ICU but I've fixed it as follows: What is the actual problem you're refering to? pcibios0: no compatible PCI ICU found: ICU vendor 0x8086 product 0x2480 pcibios0: Warning, unable to fix up PCI interrupt routing to pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801CA LPC rev 0x00) That's nice, please submit the diff. but that did not fix em0 nic. Fix it how? What is it you need to get fixed? What is the actual problem? The motherboard is IntelB. Server Board SE7501HG2, two em0 onborad, not working. Bios upgrade does not change anything. If someone could point me out where to look for the problem, I would be extremely thankfull. I've got 4 machines with this configuration and I hate to run freebsd on them. I would be extremely thankfull if you could include the basics like dmesg when you post, heck even a description of the problem would be nice. Now, please have a look at http://www.openbsd.org/report.html and then file a proper problem report. Regards Johan M:son
Re: em0 and SMP problem
On Saturday 02 July 2005 00.22, MichaE Koc wrote:
Ok,
starting from the beginnig,
The em nics are visible in dmesg and ifconfig.
They do transmit packets as I can see in tcpdump on the destination
machine. But they do not recive any packets.
ie. I ping from SMP machine to dest
on dest I can se echo requests comming from SMP and echo replies going
to SMP.
But SMP does not recive anything back. Actually I can see replies going
to SMP on switch, but not on SMP.
The problem goes away when I disable SMP in kernel.
This looks like some issue witch device polling, maby.
Please DO provide a dmesg.
What I did with ICU is:
h/i386/pci/pci_intr_fixup.c
Index: sys/arch/i386/pci/pci_intr_fixup.c
===
RCS file: /cvs/src/sys/arch/i386/pci/pci_intr_fixup.c,v
retrieving revision 1.36
diff -u -r1.36 pci_intr_fixup.c
--- sys/arch/i386/pci/pci_intr_fixup.c 2004/09/26 20:17:42 1.36
+++ sys/arch/i386/pci/pci_intr_fixup.c 2005/07/01 22:20:28
@@ -148,6 +148,8 @@
piix_init },
{ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_82801BAM_LPC,
piix_init },
+ { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_82801CA_LPC,
+ piix_init },
{ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_82801CAM_LPC,
piix_init },
{ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_82801DB_LPC,
Thank in advance
MichaE Koc
Re: OpenBSD 3.1 and OpenBSD 3.5 pf problems
On Wednesday 29 June 2005 21.23, [EMAIL PROTECTED] wrote: Hi! After switching from OpenBSD 3.1 (with Intel fxp0) to OpenBSD 3.5 (with OpenBSD 3.5 is EOL (see link below) which means you can't expect support for it. The latest release is available at ftp://ftp.su.se/pub/OpenBSD/3.7/i386/ Get it and install it. Then please read this URL before you come back here and file a proper error report, http://www.openbsd.org/report.html. Regards Johan M:son
Re: Eric Raymond talks about GPL and BSD licenses on MyFreeBSD.com
On Thursday 16 June 2005 13.10, Jasper Lievisse Adriaanse wrote: Eric Raymond gave an interview on MyFreeBSD.com about the GPL and the BSD licenses. Though on MyFreeBSD.com, it ain't a FreeBSD specific article. Jasper http://www.catb.org/~esr/guns/ Regards Johan M:son
Re: Cross compile release from amd64 to i386?
On Monday 06 June 2005 23.04, you wrote: Hello everyone, Is it possible to use an AMD64 machine (as 64 bit not i386) to cross compile release for i386, without additional tools or extras? Google reveals that cross compiling releases is an issue for some people, but with i386 being fairly similar to AMD, would this still affect me? Also would the 64 bit of the AMD give me an advantage in compile time? Thank you so much! Oh come on man, that's too easy, search the archives, this has been dealt with before, numerous times. http://marc.theaimsgroup.com/?l=openbsd-miscm=107887014002080w=2 Regards Johan M:son
Re: [slightly OT] Zaurus -- to buy or not to buy?
On Tuesday 31 May 2005 23.11, Matthias Kilian wrote: Hi, reading the OpenBSD mailinglists, undeadly.org and several stories and interviews on kerneltrap.org, I'm increasingly tempted to order a Zaurus C3000 from Wim. It's really difficult to resist ;-) However, I wonder wether this device *really* worth 800 bucks. Yes, it certainly is worth it. Also worth noting is the very fast delivery and excellent service you get by Wim. So, here are some questions (all with running OpenBSD on it in mind): - Power consumption: how long last the batteries on normal use (editing with vi(1) here, ssh'ing there, read/write some mails, ksh'ing around)? What about compiling and testing? - Performance: how does it feel? Again, normal use -- I don't have to compile kernels in my pocket ;-) Feels very good, I used to have a Psion 5 MX and this device has the same kind of solid and thorough sense of quality to it. - What about console and/or xterm(1) output speed? In case console output is slow, would X11 be a *serious* option (wrt memory/cpu usage)? I've had some problems, Fvwm2 works just dandy, however trying to run IceWM it core:s on me. That may be because I've a bit out of synch -current right now though. While in X things may get a bit 'slow' at times (with dillo and say six or seven xterms and a port or two compiling in the background) but it's certainly nothing that bothers me . - Keyboard: it's a little bit small (of course). What's your experience using it? The keyboard has a very good feel to it, the best part is it works well both as a thumb keyboard when you're actually walking around and as a (well...) touch type keyboard when you're sitting down. - If on allready has a notebook, would it be silly to order a C3000? I work as a NOC monkey so this is the best device I could ever get. It's such a relief not having to bring a big beefy laptop everytime shit hits the fan and you need to get on the console of that cisco or server which you haven't yet strapped on a console server, I just plug in my uplcom(4) and have console access right there. Regards Johan M:son
