Re: : HP proliant DL140-G3 install problems

2007-07-04 Thread Raimo Niskanen
Why not run 4.1 stable and disable axe and uberry in the 
kernel configuration for the GENERIC kernel.



On Wed, Jul 04, 2007 at 09:51:46AM +0100, Doros Eracledes wrote:
> Thanks for the reply's guys.
> 
> 
> I need to setup 2 machine's to use as a pf + carp firewall by august.
> 
> My understanding is that 4.1-current has solved the axe and uberry
> problems and that will go into 4.2-stable.
> I don't know if it's a good idea to install 4.1-current on a production
> firewall and it looks like it's going to be difficult to get 4.1-stable
> to run on it.
> 
> Any suggestions on what to do?
> 
> If necessary I could provide access to the machine for a developer to
> try things out if this will help.
> 
> 
> Doros

-- 

/ Raimo Niskanen, Erlang/OTP, Ericsson AB



Re: HP proliant DL140-G3 install problems

2007-07-04 Thread Doros Eracledes
Thanks for the reply's guys.


I need to setup 2 machine's to use as a pf + carp firewall by august.

My understanding is that 4.1-current has solved the axe and uberry
problems and that will go into 4.2-stable.
I don't know if it's a good idea to install 4.1-current on a production
firewall and it looks like it's going to be difficult to get 4.1-stable
to run on it.

Any suggestions on what to do?

If necessary I could provide access to the machine for a developer to
try things out if this will help.


Doros



Re: HP proliant DL140-G3 install problems

2007-07-03 Thread Jonathan Gray
On Tue, Jul 03, 2007 at 06:26:42PM +0200, Reyk Floeter wrote:
> On Tue, Jul 03, 2007 at 04:18:35PM +0100, Doros Eracledes wrote:
> > I am trying to install 4.1 amd64 on a proliant DL140-G3 server and have
> > various problems.
> > 
> > I've found on previous postings that the axe and uberry driver are
> > causing a problem and the kernel fails to load.
> > 
> > What I've done until now is to install openbsd 4.1 on another machine
> > update and recompile the kernel after removing the following options
> > from it:
> > 
> 
> same thing on the DL145-G3 (the opteron version). there is something
> wrong with the usb attach code, i started looking into this but i
> didn't fix it yet.

This was fixed two months ago by miod in -current.
http://marc.info/?l=openbsd-cvs&m=117760690012315&w=2



Re: HP proliant DL140-G3 install problems

2007-07-03 Thread Reyk Floeter
On Tue, Jul 03, 2007 at 04:18:35PM +0100, Doros Eracledes wrote:
> I am trying to install 4.1 amd64 on a proliant DL140-G3 server and have
> various problems.
> 
> I've found on previous postings that the axe and uberry driver are
> causing a problem and the kernel fails to load.
> 
> What I've done until now is to install openbsd 4.1 on another machine
> update and recompile the kernel after removing the following options
> from it:
> 

same thing on the DL145-G3 (the opteron version). there is something
wrong with the usb attach code, i started looking into this but i
didn't fix it yet.

you don't have to recompile the kernel, just boot into UKC and type
disable axe
...

you can also modify the kernel image without recompiling it by running
config -f -e bsd.rd
from a system running the same arch.

see the manpages boot_config(8), boot(8), and config(8)

> #uberry*  at uhub?# Research In Motion Blackberry
> #axe* at uhub?# ASIX Electronics AX88172 USB
> Ethernet
> 
> #pckbc0   at isa? # PC keyboard controller
> #pckbd*   at pckbc?   # PC keyboard
> #pms*   at pckbc? # PS/2 mouse for wsmouse
> #pmsi*at pckbc?   # PS/2 "Intelli"mouse for
> wsmouse
> 
> After removing the ps2 keyboard and mouse controller from the kernel
> machine boots normally and keyboard and mouse is detected (seems like
> there is a USB to PS2 bridge).
> PS2 keyboard and mouse would make the machine to take very long time to
> boot (trying to initialize keyboard controller)
>  i386 install shows up the same behaviour.
> 
> I've tried the above using a 4.1-current install and now I need to try
> the same with 4.1-stable.
> 
> Is it possible that we get patches to allow 4.1-stable install CD to be
> able to install directly on the DL140-G3 machine?
>

see above, use config(8)

reyk
 
> 
> Here is an 4.1-current (i386) dmesg:
> 
> OpenBSD 4.1-current (TEL) #7: Mon Jul  2 20:21:22 EEST 2007
> [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/TELXXX

  ^^^ FOR PORN?

> cpu0: Intel(R) Xeon(R) CPU E5310 @ 1.60GHz ("GenuineIntel" 686-class)
> 1.60 GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,
> CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,TM2
> ,CX16,xTPR
> real mem  = 2146050048 (2095752K)
> avail mem = 1844817920 (1801580K)
> using 4278 buffers containing 214855680 bytes (209820K) of memory
> mainbus0 (root)
> bios0 at mainbus0: AT/286+ BIOS, date 12/31/99, BIOS32 rev. 0 @ 0xfd361,
> SMBIOS rev. 2.31 @ 0xdc010 (57 entries)
> bios0: HP ProLiant DL140 G3
> 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 @ 0xfd360/0xca0
> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdde0/512 (30 entries)
> pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82371FB ISA" rev
> 0x00)
> pcibios0: PCI bus #16 is the last bus
> bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xc9000/0x1600
> 0xca800/0x1600 0xdc000/0x4000!
> acpi at mainbus0 not configured
> mainbus0: Intel MP Specification (Version 1.4)
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: apic clock running at 265 MHz
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Xeon(R) CPU E5310 @ 1.60GHz ("GenuineIntel" 686-class)
> 1.60 GHz
> cpu1:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,
> CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,TM2
> ,CX16,xTPR
> cpu2 at mainbus0: apid 2 (application processor)
> cpu2: Intel(R) Xeon(R) CPU E5310 @ 1.60GHz ("GenuineIntel" 686-class)
> 1.60 GHz
> cpu2:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,
> CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,TM2
> ,CX16,xTPR
> cpu3 at mainbus0: apid 3 (application processor)
> cpu3: Intel(R) Xeon(R) CPU E5310 @ 1.60GHz ("GenuineIntel" 686-class)
> 1.60 GHz
> cpu3:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,
> CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,TM2
> ,CX16,xTPR
> mainbus0: bus 0 is type PCI
> mainbus0: bus 1 is type PCI
> mainbus0: bus 2 is type PCI
> mainbus0: bus 14 is type PCI
> mainbus0: bus 15 is type PCI
> mainbus0: bus 16 is type PCI
> mainbus0: bus 17 is type ISA
> ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins
> ioapic1 at mainbus0: apid 5 pa 0xfec8, version 20, 24 pins
> pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
> pchb0 at pci0 dev 0 function 0 "Intel 5000X Host" rev 0x31
> ppb0 at pci0 dev 2 function 0 "Intel 5000 PCIE" rev 0x31
> pci1 at ppb0 bus 1
> ppb1 at pci1 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01
> pci2 at ppb1 bus 2
> ppb2 at pci2 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01
> pci3 at ppb2 bus 3
> ppb3 at pci1 dev 0 function 3 "Intel 6321ESB PCIE-PCIX" rev 0x01
> pci4 

HP proliant DL140-G3 install problems

2007-07-03 Thread Doros Eracledes
I am trying to install 4.1 amd64 on a proliant DL140-G3 server and have
various problems.

I've found on previous postings that the axe and uberry driver are
causing a problem and the kernel fails to load.

What I've done until now is to install openbsd 4.1 on another machine
update and recompile the kernel after removing the following options
from it:

#uberry*at uhub?# Research In Motion Blackberry
#axe*   at uhub?# ASIX Electronics AX88172 USB
Ethernet

#pckbc0 at isa? # PC keyboard controller
#pckbd* at pckbc?   # PC keyboard
#pms* at pckbc? # PS/2 mouse for wsmouse
#pmsi*  at pckbc?   # PS/2 "Intelli"mouse for
wsmouse

After removing the ps2 keyboard and mouse controller from the kernel
machine boots normally and keyboard and mouse is detected (seems like
there is a USB to PS2 bridge).
PS2 keyboard and mouse would make the machine to take very long time to
boot (trying to initialize keyboard controller)
 i386 install shows up the same behaviour.

I've tried the above using a 4.1-current install and now I need to try
the same with 4.1-stable.

Is it possible that we get patches to allow 4.1-stable install CD to be
able to install directly on the DL140-G3 machine?


Here is an 4.1-current (i386) dmesg:

OpenBSD 4.1-current (TEL) #7: Mon Jul  2 20:21:22 EEST 2007
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/TELXXX
cpu0: Intel(R) Xeon(R) CPU E5310 @ 1.60GHz ("GenuineIntel" 686-class)
1.60 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,
CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,TM2
,CX16,xTPR
real mem  = 2146050048 (2095752K)
avail mem = 1844817920 (1801580K)
using 4278 buffers containing 214855680 bytes (209820K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+ BIOS, date 12/31/99, BIOS32 rev. 0 @ 0xfd361,
SMBIOS rev. 2.31 @ 0xdc010 (57 entries)
bios0: HP ProLiant DL140 G3
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 @ 0xfd360/0xca0
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdde0/512 (30 entries)
pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82371FB ISA" rev
0x00)
pcibios0: PCI bus #16 is the last bus
bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xc9000/0x1600
0xca800/0x1600 0xdc000/0x4000!
acpi at mainbus0 not configured
mainbus0: Intel MP Specification (Version 1.4)
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 265 MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Xeon(R) CPU E5310 @ 1.60GHz ("GenuineIntel" 686-class)
1.60 GHz
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,
CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,TM2
,CX16,xTPR
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Xeon(R) CPU E5310 @ 1.60GHz ("GenuineIntel" 686-class)
1.60 GHz
cpu2:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,
CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,TM2
,CX16,xTPR
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Xeon(R) CPU E5310 @ 1.60GHz ("GenuineIntel" 686-class)
1.60 GHz
cpu3:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,
CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,TM2
,CX16,xTPR
mainbus0: bus 0 is type PCI
mainbus0: bus 1 is type PCI
mainbus0: bus 2 is type PCI
mainbus0: bus 14 is type PCI
mainbus0: bus 15 is type PCI
mainbus0: bus 16 is type PCI
mainbus0: bus 17 is type ISA
ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins
ioapic1 at mainbus0: apid 5 pa 0xfec8, version 20, 24 pins
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 5000X Host" rev 0x31
ppb0 at pci0 dev 2 function 0 "Intel 5000 PCIE" rev 0x31
pci1 at ppb0 bus 1
ppb1 at pci1 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01
pci2 at ppb1 bus 2
ppb2 at pci2 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01
pci3 at ppb2 bus 3
ppb3 at pci1 dev 0 function 3 "Intel 6321ESB PCIE-PCIX" rev 0x01
pci4 at ppb3 bus 5
ppb4 at pci0 dev 3 function 0 "Intel 5000 PCIE" rev 0x31
pci5 at ppb4 bus 6
ppb5 at pci0 dev 4 function 0 "Intel 5000X PCIE" rev 0x31
pci6 at ppb5 bus 8
ppb6 at pci0 dev 5 function 0 "Intel 5000 PCIE" rev 0x31
pci7 at ppb6 bus 9
ppb7 at pci0 dev 6 function 0 "Intel 5000 PCIE" rev 0x31
pci8 at ppb7 bus 10
ppb8 at pci0 dev 7 function 0 "Intel 5000 PCIE" rev 0x31
pci9 at ppb8 bus 11
pchb1 at pci0 dev 16 function 0 "Intel 5000 Error Reporting" rev 0x31
pchb2 at pci0 dev 16 function 1 "Intel 5000 Error Reporting" rev 0x31
pchb3 at pci0 dev 16 function 2 "Intel 5000 Error Reporting" rev 0x31
pchb4 at pci0 dev 17 function 0 "Intel 5000 Reserved" rev 0x31
pchb5 at pci0 dev 19 function 0 "Intel 5000 Reserved" rev 0x31
pchb6 at pci0 dev 21 function 0 "Intel 5000 FBD" rev