Re: 8-ports serial card compatible with OpenBSD

2012-06-18 Thread Alf Schlichting
On Sun, 17 Jun 2012 22:36:55 -0400
Nick Holland n...@holland-consulting.net wrote:

 On 06/17/12 18:24, Jiri B wrote:
  Hello,
  
  could anybody recommend OpenBSD compatible 8-ports serial card? I'd
  like to build a small console server.
  
  Thank you.
  
  jirib
 
 So cheap, it's worth a try:
 http://www.newegg.com/Product/Product.aspx?Item=N82E16815124099
 I bought a few of these cards a few years back.  They didn't work.
 Then somewhere around 4.8 or 4.9, support for the chip I had was
 added, but the older card I had didn't work on anything under than a
 P4, and even there, it caused a huge interrupt storm, slowed the
 machine down and drastically increased power consumption.  On a P3 or
 slower system (inc. macppc or sparc64), the system just hung as it
 spun up the serial ports. Then, somewhere before 5.1, iirc, something
 fixed that and now it works nicely on anything I've put it in.
 
 BUT:
 This is not the card I ordered.  Same vendor, same price point, but
 the card has clearly been revised.  So I can't tell you if THIS card
 works. I keep getting tempted to buy one, but I also look at the
 older card still in the box on my shelf...and think...sheesh, when I
 buy this one, it will be revised a week later, and nothing will be
 gained by anyone.
 
 Nick.
 

We use one from www.visionsystems.de: 
VSCOM 800H UPCI 8x RS232 16C950 (128Byte FIFO),921kbps
+ MINIBOX 8 X RS232/DB9 Anschlussbox RS232,8x DB9

puc0 at pci0 dev 7 function 0 VScom 400H/800H rev 0x00: ports: 4 com
com3 at puc0 port 0 irq 11: st16650, 32 byte fifo
com4 at puc0 port 1 irq 11: st16650, 32 byte fifo
com5 at puc0 port 2 irq 11: st16650, 32 byte fifo
com6 at puc0 port 3 irq 11: st16650, 32 byte fifo
puc1 at pci0 dev 7 function 1 VScom 800H rev 0x00: ports: 4 com
com7 at puc1 port 0 irq 11: st16650, 32 byte fifo
com8 at puc1 port 1 irq 11: st16650, 32 byte fifo
com9 at puc1 port 2 irq 11: st16650, 32 byte fifo
com10 at puc1 port 3 irq 11: st16650, 32 byte fifo
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo

in an old desktop PC - 2 other machines we tried couldn't
cope with it (died or crashed after 2-3 weeks uptime, maybe
unrelated though).

Alf



Re: HP DL360 G6

2009-11-09 Thread Alf Schlichting
Thanks! 

Alf

On Friday 06 November 2009 18:17:23 you wrote:
  machines and because the HP DL360 G6 seems to be cheaper (and 'newer'),
  does anyone here use such beast successfully with OpenBSD?

 As promised the output of dmesg and sysctl below.
 Note that the memory sockets in this machine are empty, e.g. it comes
 with 4 GB on board apparently by default.

 # sysctl hw
 hw.machine=i386
 hw.model=Intel(R) Xeon(R) CPU E5504 @ 2.00GHz (GenuineIntel 686-class)
 hw.ncpu=4
 hw.byteorder=1234
 hw.pagesize=4096
 hw.disknames=sd0,sd1,cd0
 hw.diskcount=3
 hw.sensors.acpitz0.temp0=8.30 degC (zone temperature)
 hw.sensors.cpu0.temp0=57.00 degC
 hw.cpuspeed=2001
 hw.vendor=Hewlett-Packard
 hw.product=ProLiant DL360 G6
 hw.serialno=CZJ929074N
 hw.uuid=34373030-3635-435a-4a39-32393037344e
 hw.physmem=3747438592
 hw.usermem=3747229696
 hw.ncpufound=4


 # dmesg
 OpenBSD 4.6 (GENERIC.MP) #89: Thu Jul  9 21:32:39 MDT 2009
 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
 cpu0: Intel(R) Xeon(R) CPU E5504 @ 2.00GHz (GenuineIntel 686-class) 2.01
 GHz cpu0:
 FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFL
USH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX
16,xTPR real mem  = 3747438592 (3573MB)
 avail mem = 3638829056 (3470MB)
 mainbus0 at root
 bios0 at mainbus0: AT/286+ BIOS, date 12/31/99, BIOS32 rev. 0 @
 0xf, SMBIOS rev. 2.6 @ 0xdf7fe000 (123 entries)
 bios0: vendor Hewlett-Packard version P64 date 06/02/2009
 bios0: Hewlett-Packard ProLiant DL360 G6
 acpi0 at bios0: rev 2
 acpi0: tables DSDT FACP SPCR MCFG HPET  SPMI ERST APIC SRAT 
 BERT HEST DMAR SSDT SSDT SSDT
 acpi0: wakeup devices
 acpitimer0 at acpi0: 3579545 Hz, 24 bits
 acpihpet0 at acpi0: 14318179 Hz
 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
 cpu0 at mainbus0: apid 0 (boot processor)
 cpu0: unknown i686 model 0x1a, can't get bus clock (0x0)
 cpu0: apic clock running at 133MHz
 cpu1 at mainbus0: apid 4 (application processor)
 cpu1: Intel(R) Xeon(R) CPU E5504 @ 2.00GHz (GenuineIntel 686-class) 2.01
 GHz cpu1:
 FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFL
USH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX
16,xTPR cpu2 at mainbus0: apid 2 (application processor)
 cpu2: Intel(R) Xeon(R) CPU E5504 @ 2.00GHz (GenuineIntel 686-class) 2.01
 GHz cpu2:
 FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFL
USH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX
16,xTPR cpu3 at mainbus0: apid 6 (application processor)
 cpu3: Intel(R) Xeon(R) CPU E5504 @ 2.00GHz (GenuineIntel 686-class) 2.01
 GHz cpu3:
 FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFL
USH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX
16,xTPR ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
 ioapic1 at mainbus0: apid 0 pa 0xfec8, version 20, 24 pins
 acpiprt0 at acpi0: bus 1 (IP2P)
 acpiprt1 at acpi0: bus -1 (IPT1)
 acpiprt2 at acpi0: bus 3 (PT01)
 acpiprt3 at acpi0: bus 10 (PT02)
 acpiprt4 at acpi0: bus 7 (PT03)
 acpiprt5 at acpi0: bus 11 (PT04)
 acpiprt6 at acpi0: bus 12 (PT05)
 acpiprt7 at acpi0: bus 13 (PT06)
 acpiprt8 at acpi0: bus 14 (PT07)
 acpiprt9 at acpi0: bus 2 (PT08)
 acpiprt10 at acpi0: bus 4 (PT09)
 acpiprt11 at acpi0: bus 15 (PT0A)
 acpiprt12 at acpi0: bus 0 (PCI0)
 acpicpu0 at acpi0: C3, C3, C1
 acpicpu1 at acpi0: C3, C3, C1
 acpicpu2 at acpi0: C3, C3, C1
 acpicpu3 at acpi0: C3, C3, C1
 acpitz0 at acpi0: critical temperature 31 degC
 bios0: ROM list: 0xc/0xb000 0xcc400/0x3600! 0xcfa00/0x1e00!
 0xd1800/0x4000 ipmi at mainbus0 not configured
 cpu0: EST: unknown system bus clock
 pci0 at mainbus0 bus 0: configuration mode 1 (bios)
 pchb0 at pci0 dev 0 function 0 vendor Intel, unknown product 0x3406 rev
 0x13 ppb0 at pci0 dev 1 function 0 Intel X58 PCIE rev 0x13
 pci1 at ppb0 bus 3
 ciss0 at pci1 dev 0 function 0 Hewlett-Packard Smart Array rev 0x01:
 apic 0 int 4 (irq 7)
 ciss0: 2 LDs, HW rev 2, FW 1.62/1.62, 64bit fifo rro
 scsibus0 at ciss0: 2 targets
 sd0 at scsibus0 targ 0 lun 0: HP, LOGICAL VOLUME, 1.62 SCSI3 0/direct
 fixed sd0: 139979MB, 512 bytes/sec, 286677120 sec total
 sd1 at scsibus0 targ 1 lun 0: HP, LOGICAL VOLUME, 1.62 SCSI3 0/direct
 fixed sd1: 139979MB, 512 bytes/sec, 286677120 sec total
 ppb1 at pci0 dev 2 function 0 Intel X58 PCIE rev 0x13
 pci2 at ppb1 bus 10
 ppb2 at pci0 dev 3 function 0 Intel X58 PCIE rev 0x13
 pci3 at ppb2 bus 7
 ppb3 at pci0 dev 4 function 0 Intel X58 PCIE rev 0x13
 pci4 at ppb3 bus 11
 ppb4 at pci0 dev 5 function 0 Intel X58 PCIE rev 0x13
 pci5 at ppb4 bus 12
 ppb5 at pci0 dev 6 function 0 Intel X58 PCIE rev 0x13
 pci6 at ppb5 bus 13
 ppb6 at pci0 dev 7 function 0 Intel X58 PCIE rev 0x13
 pci7 at ppb6 bus 14
 ppb7 at pci0 dev 8 function 0 Intel X58 PCIE rev 0x13
 pci8 at ppb7 bus 2
 bnx0 at pci8 dev 0 function 0 Broadcom BCM5709 rev 0x20: apic 0 int 7
 (irq 7) bnx1 at pci8 dev 0 

HP DL360 G6

2009-11-06 Thread Alf Schlichting
Hello, 

since we need a new server and had good experiences with HP DL360 G5
machines and because the HP DL360 G6 seems to be cheaper (and 'newer'),
does anyone here use such beast successfully with OpenBSD?

Alf



Re: Donations (was, sadly, European orders)

2009-04-02 Thread Alf Schlichting
Theo,

as far as i am concerned (and most likely the majority of OpenBSD
users) there is no need for you to justify yourself (or any other
developer) in public.
The product (OpenBSD) speeks for itself. 

Alf

P.S.:
To me the sentence about hiking on Wim's page looks like a
silly rethoric trick that gives the rest of his text an objectionable
taste.
On Wed, Apr 01, 2009 at 10:11:07PM -0600, Theo de Raadt wrote:
  So what if it's founder lives a mountain biking/hiking lifestyle?
 
 There are people being misled that I pay for this extravagant
 lifestyle out of donations.  Hah.  Shame on those people who spread
 that rumour, and also shame on those who are so easily deceived.
 
 I hike near conferences that I am invited to; flights paid for.  I
 hike near hackathons that I must attend with developers -- hackathons
 tend to be near hiking areas but I am not alone in preferring this
 (our hackathon locations are otherwise chosen for cheap accomodation
 with free internet2... perhaps internet2 usage is correleted to good
 terrain..).  Once a year I pay with my hard earned salary for a trip
 to hike somewhere.  Then one further time a year I use the reward
 points -- from all my other flights and hackathon hotel bills and
 developer flights paid with donation money -- to get to another hiking
 destination.
 
 Yes... I have to take time off to do this, but as many of you know
 when I get back from a trip I go through all the thousands of mails I
 received and the project moves on.  And between hikes in a foreign
 country I find insecure ways to partially get in touch a bit and some
 developers really hate that.  I work hard.  When I don't hike, and
 especially during pre-release times, I sometimes don't get outside for
 days at a time except on forced 10km runs.
 
 Extravagant?  No.  Just a life choice.
 
 I have had people accuse me privately of this.  I hope others are not
 so easily deceived.
 
 Trust me, with the OpenBSD donations are a loss.  Just look at this
 page, and estimate the hotel bills:
 
   http://www.openbsd.org/hackathons.html
 
 After you estimate those numbers, where would I find money to spend on
 even a slurpee?  Gimme a fucking break...  Donations help a lot, but
 they are not the whole picture.  That is why we are so eager -- as a
 project -- get the money that Wim has taken from us, because it will
 help OpenBSD run more hackathons.  The systems code you are running,
 almost half of it came from hackathons.
 
  If I can give him that and he can continue to provide this wonderful
  product for free, I'm happy to help him live his lifestyle (even if
  he doesn't play well with others at times).
 
 It's a deal.
 
  It's too bad the project
  doesn't have greater financial backing to allow more development of
  the OS goodness we enjoy--and also allow more OpenBSD people to live
  a Theo-like lifestyle, if they so choose.
 
 Others are trying to do it too, but they are just more quiet about it.
 
 And then there's the other catagory... the breeders...



Re: European orders

2009-03-25 Thread Alf Schlichting
On Tue, Mar 24, 2009 at 04:52:04PM -0600, Theo de Raadt wrote:
 From a commit message an hour or so ago:
 
 Disable future European orders since the distributor is way too far behind
 in reconciling payments to the project for past sales, and years of trying
 to resolve it have made very little progress.
 
 Sorry guys.
 
Hmm, I used to order my sets from http://www.ixsoft.de. Is this the
same channel for europe?
CD:
http://www.ixsoft.de/cgi-bin/web_store.cgi?ref=Products/de/OOOB0450DV.html

On a side note, I see a OpenBSD 4.5 DVD there, is it authorized?
http://www.ixsoft.de/cgi-bin/web_store.cgi?ref=Products/de/IXOB0450DV.html

Alf



The right thing to do

2007-12-17 Thread Alf Schlichting
Instead of bla-blaing on dump threads to obvious fanatics,
do what i did.

Show the FSF the $-finger and donate.

Because that flame really burns;)


Alf



Re: need a machine for an itanium port

2007-06-09 Thread Alf Schlichting
On Sat, Jun 09, 2007 at 12:56:08AM -0400, Martin Gignac wrote:
 One more just donated $100.
 
 And here's another one.
 
 Ditto.
 
 -Martin

One more.

Alf



Re: shutdown gets stuck at `syncing discs...'

2007-04-23 Thread Alf Schlichting
I had this problem too and seems like it is fixed in the latest snapshot.

Synopsis: sync(8) hangs on reboots

State-Changed-From-To: open-closed
State-Changed-By: pedro
State-Changed-When: Fri Apr 20 02:56:01 MDT 2007
State-Changed-Why: 
Very likely fixed in revision 1.21 of vfs_cache.c, thanks for the report


Alf

Am Montag, 23. April 2007 14:42:01 schrieb Han Boetes:
 Otto Moerbeek wrote:
  On Mon, 23 Apr 2007, Han Boetes wrote:
   Of course I crash, I crash at every reboot, I got the problem
   where the rebooting proces gets stuck at `syncing disks' after
   which I have to m-c-ESC and then boot sync.
  
   I have this on a i386 and I met someone on #openbsd who had it
   on a sparc.
  
   When will this bug be fixed?
 
  After you provide a proper report?

 About 50% of the shutdowns get stuck at `syncing discs...' The
 only filesystem which is marked dirty is /

 Here is the output of `dmesg  dmesg'. Yes dmesg remembers the
 output of the previous boot on my system. And this time it didn't
 happen.

 Anything else you'd like to know? Would you like me to post this
 one with sendbug?


 ontaining 40366080 bytes (39420K) of memory
 mainbus0 (root)
 bios0 at mainbus0: AT/286+ BIOS, date 03/28/02, BIOS32 rev. 0 @ 0xfdad0,
 SMBIOS rev. 2.3 @ 0xf0630 (22 entries) bios0: MSI MS-6380E
 apm0 at bios0: Power Management spec V1.2
 apm0: AC on, battery charge unknown
 apm0: flags 30102 dobusy 0 doidle 1
 pcibios0 at bios0: rev 2.1 @ 0xf/0x1
 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf7f00/192 (10 entries)
 pcibios0: PCI Interrupt Router at 000:17:0 (VIA VT8233 ISA rev 0x00)
 pcibios0: PCI bus #1 is the last bus
 bios0: ROM list: 0xc/0xf800
 acpi at mainbus0 not configured
 cpu0 at mainbus0
 pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
 pchb0 at pci0 dev 0 function 0 VIA VT8366 PCI rev 0x00
 ppb0 at pci0 dev 1 function 0 VIA VT8366 AGP rev 0x00
 pci1 at ppb0 bus 1
 vga1 at pci1 dev 0 function 0 NVIDIA GeForce4 MX 4000 rev 0xa4
 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
 wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
 uhci0 at pci0 dev 6 function 0 VIA VT83C572 USB rev 0x50: irq 5
 uhci1 at pci0 dev 6 function 1 VIA VT83C572 USB rev 0x50: irq 12
 ehci0 at pci0 dev 6 function 2 VIA VT6202 USB rev 0x51: irq 10
 usb0 at ehci0: USB revision 2.0
 uhub0 at usb0
 uhub0: VIA EHCI root hub, rev 2.00/1.00, addr 1
 uhub0: 4 ports with 4 removable, self powered
 re0 at pci0 dev 7 function 0 Realtek 8169 rev 0x10: RTL8169S (0x0400),
 irq 12, address 00:08:a1:3c:34:7a rgephy0 at re0 phy 7: RTL8169S/8110S PHY,
 rev. 0
 rl0 at pci0 dev 10 function 0 Realtek 8139 rev 0x10: irq 5, address
 00:e0:4c:67:52:80 rlphy0 at rl0 phy 0: RTL internal PHY
 viapm0 at pci0 dev 17 function 0 VIA VT8233A ISA rev 0x00
 iic0 at viapm0
 iic0: addr 0x2f 00=00 02=0f 03=00 04=00 06=0f 07=00 08=00 0a=06 0b=00 0c=00
 0d=07 0e=84 0f=00 10=c0 11=11 12=00 13=60 pciide0 at pci0 dev 17 function 1
 VIA VT82C571 IDE rev 0x06: ATA133, channel 0 configured to compatibility,
 channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0:
 Maxtor 6Y080L0
 wd0: 16-sector PIO, LBA, 78167MB, 160086528 sectors
 wd1 at pciide0 channel 0 drive 1: Maxtor 6L250R0
 wd1: 16-sector PIO, LBA48, 239372MB, 490234752 sectors
 wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 6
 wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 6
 atapiscsi0 at pciide0 channel 1 drive 1
 scsibus0 at atapiscsi0: 2 targets
 cd0 at scsibus0 targ 0 lun 0: LITE-ON, LTR-40125S, ZS0N SCSI0 5/cdrom
 removable cd0(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2
 uhci2 at pci0 dev 17 function 2 VIA VT83C572 USB rev 0x23: irq 10
 uhci3 at pci0 dev 17 function 3 VIA VT83C572 USB rev 0x23: irq 10
 usb1 at uhci0: USB revision 1.0
 uhub1 at usb1
 uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1
 uhub1: 2 ports with 2 removable, self powered
 usb2 at uhci1: USB revision 1.0
 uhub2 at usb2
 uhub2: VIA UHCI root hub, rev 1.00/1.00, addr 1
 uhub2: 2 ports with 2 removable, self powered
 usb3 at uhci2: USB revision 1.0
 uhub3 at usb3
 uhub3: VIA UHCI root hub, rev 1.00/1.00, addr 1
 uhub3: 2 ports with 2 removable, self powered
 usb4 at uhci3: USB revision 1.0
 uhub4 at usb4
 uhub4: VIA UHCI root hub, rev 1.00/1.00, addr 1
 uhub4: 2 ports with 2 removable, self powered
 isa0 at mainbus0
 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
 pcppi0 at isa0 port 0x61
 midi0 at pcppi0: PC speaker
 spkr0 at pcppi0
 lm0 at isa0 port 0x290/8: W83697HF
 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
 biomask fffd netmask fffd ttymask 
 pctr: user-level cycle counter enabled
 mtrr: Pentium Pro MTRR support
 wd0c: aborted command, interface CRC error reading fsbn 64 (wd0 bn 64; cn 0
 tn 1 sn 1), retrying wd0: transfer error, downgrading to Ultra-DMA mode 5
 wd0(pciide0:0:0): using PIO mode 4, 

Re: Strange behavior for booting new kernel?

2006-09-24 Thread Alf Schlichting
Am Samstag, 23. September 2006 22:51 schrieben Sie:
 On 9/23/06, Tom Cosgrove [EMAIL PROTECTED] wrote:
   Greg Thomas 23-Sep-06 19:37 
  
   I just upgraded my storage box to -current to test the ath upgrades
   on another slower computer.  I ran make install after compiling the
   kernel instead of copying the kernel manually:
  
   [EMAIL PROTECTED]:/home/ethant# ls -al /*bsd*
   -rwxr-xr-x  1 root  wheel  6049422 Sep 23 10:53 /bsd
   -rw-r--r--  1 root  wheel  5002407 Aug 21 18:00 /bsd.rd
   -rw-r--r--  1 root  wheel  6028254 Aug 21 18:00 /obsd
  
   But the first 3 times I rebooted the system it booted the Aug 21
   /obsd kernel.  The 4th time it finally booted the Sep 23 one.  I kept
   getting interrupted by the cat, the phone, and the cat while at the
   boot prompt while I was troubleshooting and then the last time it
   finally booted /bsd.
  
   Any ideas on why that happened?
 
  I doubt this is what happened.

 In this case I'm sure of what I saw because I scrolled through the
 entire dmesg and saw 4.0-current compiled by Theo 2 times before the
 one 4.0-current compiled by me even though I had rebooted several
 times with new kernel in place.

 Anyway, I've rebooted enough times now that they're all my kernel so
 I'll just strike it up to me not having had coffee yet.

 Greg

You may be a victim of the feature that ( for hardware related reasons)
the dmesg buffer doesn't get cleared after reboot so you actually have 2
dmesgs, (or maybe even more ?)  one after the other, in dmesg buffer. 
This can easily  be overlooked by scrolling back to fast.

The exact reasons are somewhere in the archives.

Alf