Re: Pre-Order 4.4

2008-09-03 Thread K WESTERBACK
Just to be clear - this is/should be fixed in 4.4.

 Ken



- Original Message 
From: Ted Unangst [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: misc@openbsd.org
Sent: Wednesday, September 3, 2008 11:31:15 AM
Subject: Re: Pre-Order 4.4

On 9/3/08, Christophe Rioux [EMAIL PROTECTED] wrote:
  Do you know if the raid logic has being corrected in this new release. By
  corrected, I means following answer:

  http://marc.info/?l=openbsd-miscm=120855938821758w=2

  This is currently broken (deliberately) as changes are made to the
  logic concerning mounting the root disk. There are some more changes
  that need to be made before a fix to raidframe can be committed.

http://marc.info/?l=openbsd-cvsm=121150396015435w=2



Re: Failed installation on HP ProLiant ML110 G4 (with dmesg)

2007-02-07 Thread K WESTERBACK
As stupid-trick-with-install-scripts, one can simply manually enter the disks
of interest.

At the Proceed with install?' prompt simply enter

!export
DKDEVS=wd0

You should get the prompt back and be able to proceed normally.
 Ken

- Original Message 
From: Ron Oliver [EMAIL PROTECTED]
To:
misc@openbsd.org
Sent: Wednesday, February 7, 2007 12:37:43 PM
Subject: Failed
installation on HP ProLiant ML110 G4 (with dmesg)

Below is a capture from a
serial console during the installation.
Note that I've reduced most of the
repeated messages a la [last
message repeated x times]; otherwise, this would
be a 7000 line post.

Aside: how about a 3-wire serial console option that
doesn't need DCD
driven?  My beloved Cisco serial cables don't drive DCD; I
had to dig
deeply into my big bag o' adapters to find an old-school null modem
to
do it.  But I guess I'll appreciate that feature if I ever need a
serial
console through a modem. :)

This should also answer a previously posted
question on a related
failed ProLiant install: Why axe(4)?  Because it
seemed like a good
idea at the time to the kernel.  It wasn't a user
selection.  All
hardware is HP-supplied with the system; nothing added here.
I first tried this with the PS/2 keyboard that came with the unit, but
it was
unresponsive by the time I got to a prompt, hence the MS
Natural Pro plugged
in.

If anyone cares, it looks like Ubuntu 6.06LTS will install on it (and
the
PS/2 keyboard IS responsive under that OS.)  I'll go ahead and
install that
for the hell of it.  If anyone wants dmesg from that, let
me know.

Either
this will work soon, or it's going back; I can't afford to have
a science
project sitting around.  But if any developers want
something tried out, let
me know and I'll assist as I can.  I can also
hang it on a public IP if that
helps.

 OpenBSD/i386 BOOT 2.10
boot
booting fd0a:/bsd:
4692244+739940=0x52e4c0
entry point at 0x200120*
Copyright (c) 1982, 1986,
1989, 1991, 1993
The Regents of the University of California.  All rights
reserved.
Copyright (c) 1995-2006 OpenBSD. All rights reserved.
http://www.OpenBSD.org

OpenBSD 4.0 (RAMDISK_CD) #39: Sat Sep 16 19:34:26 MDT
2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: Intel(R) Xeon(R) CPU 3040 @ 1.86GHz (GenuineIntel 686-class) 1.87 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX
16
real mem  = 1071788032 (1046668K)
avail mem = 971149312 (948388K)
using
4256 buffers containing 53690368 bytes (52432K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(7b) BIOS, date 12/31/99, BIOS32 rev. 0 @ 0xfd460,
SMB
IOS rev. 2.4 @ 0xdc010 (47 entries)
bios0: HP ProLiant ML110 G4
pcibios0
at bios0: rev 2.1 @ 0xfd460/0xba0
pcibios0: PCI IRQ Routing Table rev 1.0 @
0xfdee0/256 (14 entries)
pcibios0: PCI Interrupt Router at 000:31:0 (Intel
82371FB ISA rev 0x00)
pcibios0: PCI bus #10 is the last bus
bios0: ROM list:
0xc/0x8000 0xdc000/0x4000!
cpu0 at mainbus0
pci0 at mainbus0 bus 0:
configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 Intel E7230
MCH rev 0xc0
ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x01
pci1 at ppb0 bus 2
ppb1 at pci0 dev 28 function 4 Intel 82801G PCIE rev 0x01
pci2 at ppb1 bus 3
vga1 at pci2 dev 0 function 0 vendor Matrox, unknown
product 0x0522 rev
0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100
emulation)
ppb2 at pci0 dev 28 function 5 Intel 82801G PCIE rev 0x01
pci3 at
ppb2 bus 4
bge0 at pci3 dev 0 function 0 Broadcom BCM5721 rev 0x21, BCM5750
C1
(0x4201):
irq 12, address 00:18:fe:79:02:af
brgphy0 at bge0 phy 1: BCM5750
10/100/1000baseT PHY, rev. 0
uhci0 at pci0 dev 29 function 0 Intel 82801GB
USB rev 0x01: irq 10
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0:
Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable,
self powered
uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: irq
5
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: Intel UHCI root hub,
rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2 at
pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: irq 11
usb2 at uhci2: USB
revision 1.0
uhub2 at usb2
uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3 at pci0 dev 29 function 3
Intel 82801GB USB rev 0x01: irq 7
usb3 at uhci3: USB revision 1.0
uhub3 at
usb3
uhub3: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2
removable, self powered
ehci0 at pci0 dev 29 function 7 Intel 82801GB USB
rev 0x01: irq 10
ehci0: timed out waiting for BIOS
usb4 at ehci0: USB revision
2.0
uhub4 at usb4
uhub4: Intel EHCI root hub, rev 2.00/1.00, addr 1
uhub4: 8
ports with 8 removable, self powered
ppb3 at pci0 dev 30 function 0 Intel
82801BA AGP rev 0xe1
pci4 at ppb3 bus 10
ichpcib0 at pci0 dev 31 function 0
Intel 82801GB LPC rev 0x01: PM disabled
pciide0 at pci0 dev 31 function 1
Intel 82801GB IDE rev 0x01: 

Re: SCSI and several adapters on the same bus

2006-11-25 Thread K WESTERBACK
Depends what you mean by handle. I would expect each target on the
bus to be 'discovered' by each adapter during the probe process. Thus
giving you a choice in how to access the target. There is no code I 
know of that tries to organize the resulting confusion. So if you are really
careful it may work. If several adaptors try to send I/O to the same 
target you can probably kiss your data goodbye.

 Ken

- Original Message 
From: Michael Schmidt [EMAIL PROTECTED]
To: misc@openbsd.org
Sent: Friday, November 24, 2006 8:05:42 AM
Subject: SCSI and several adapters on the same bus

Hello,

does OpenBSD handle several adapters on the same SCSI bus?

Clarifying: Several adapters of course with different SCSI ids,
but connected via one cable on the same SCSI bus.
It may happen that I have a need for this, so would be fine to read
which experiences [EMAIL PROTECTED] have.

Have a nice day
Michael

-- 
Michael Schmidt MIRRORS:
DJGPP   ftp://ftp.fh-koblenz.de/pub/CompilerTools/DJGPP/
Watcom  ftp://ftp.fh-koblenz.de/pub/CompilerTools/Watcom/
OpenOffice  ftp://ftp.fh-koblenz.de/pub/OpenOffice/



Re: SCSI stuff

2005-08-17 Thread K WESTERBACK
Solved in the sense that 'the stuff is in the mail'.
Not yet in the sense 'hey, it's here and working!'.
:-).

 Ken

--- J.C. Roberts [EMAIL PROTECTED] wrote:

 Ken,
 
 Did the needed eclosure/carrier stuff get solved?
 
 JCR