Re: Getting stuck on trying a fresh install to 7.4

[Daniel Ouellet]

On 12/8/23 3:34 AM, Stuart Henderson wrote:

On 2023-12-07, Daniel Ouellet  wrote:

On 12/7/23 7:37 AM, Stuart Henderson wrote:

On 2023-12-06, Daniel Ouellet  wrote:

Any suggestion woudl be greattly appreciated.


Old boot loaders cannot boot 7.4 kernels.
Upgrade your 6.7 system to 7.3 first (the usual advice to avoid
skipping releases during upgrades applies). Then upgrade to 7.4.


Specifically the interface used for communicating system
console information between the boot loader and the kernel was changed.
There was backwards compat but sadly it was removed after one single
release.

I think this brings the total number of people I know who have been
affected by this up to 6 now.


I didn't care what's on it now. All fresh install will do.
I have 22 to do. :(


You can copy a new bootloader to the old machines and run installboot.


Hi Stuart,

Just to be clear and to help others here.

You are talking about these two files only right?

/usr/mdec/boot
/usr/sbin/installboot

or should this one below be included too? I don't think it's needed, but
just want to be sure and make the info complete.

/usr/mdec/biosboot


Assuming standard partition table not GPT: /usr/mdec/boot and
/usr/mdec/biosboot. *Not* /usr/sbin/installboot, the new binary
is unlikely to run on new OS.



Thanks Stuart.

I will test it out. Plenty to test with anyway. (;

Re: Getting stuck on trying a fresh install to 7.4

[Stuart Henderson]

On 2023-12-07, Daniel Ouellet  wrote:
> On 12/7/23 7:37 AM, Stuart Henderson wrote:
>> On 2023-12-06, Daniel Ouellet  wrote:
>>>>> Any suggestion woudl be greattly appreciated.
>>>>
>>>> Old boot loaders cannot boot 7.4 kernels.
>>>> Upgrade your 6.7 system to 7.3 first (the usual advice to avoid
>>>> skipping releases during upgrades applies). Then upgrade to 7.4.
>> 
>> Specifically the interface used for communicating system
>> console information between the boot loader and the kernel was changed.
>> There was backwards compat but sadly it was removed after one single
>> release.
>> 
>> I think this brings the total number of people I know who have been
>> affected by this up to 6 now.
>> 
>>> I didn't care what's on it now. All fresh install will do.
>>> I have 22 to do. :(
>> 
>> You can copy a new bootloader to the old machines and run installboot.
>
> Hi Stuart,
>
> Just to be clear and to help others here.
>
> You are talking about these two files only right?
>
> /usr/mdec/boot
> /usr/sbin/installboot
>
> or should this one below be included too? I don't think it's needed, but 
> just want to be sure and make the info complete.
>
> /usr/mdec/biosboot

Assuming standard partition table not GPT: /usr/mdec/boot and
/usr/mdec/biosboot. *Not* /usr/sbin/installboot, the new binary
is unlikely to run on new OS.

Re: Getting stuck on trying a fresh install to 7.4

[Daniel Ouellet]

On 12/7/23 7:37 AM, Stuart Henderson wrote:

On 2023-12-06, Daniel Ouellet  wrote:

Any suggestion woudl be greattly appreciated.


Old boot loaders cannot boot 7.4 kernels.
Upgrade your 6.7 system to 7.3 first (the usual advice to avoid
skipping releases during upgrades applies). Then upgrade to 7.4.


Specifically the interface used for communicating system
console information between the boot loader and the kernel was changed.
There was backwards compat but sadly it was removed after one single
release.

I think this brings the total number of people I know who have been
affected by this up to 6 now.


I didn't care what's on it now. All fresh install will do.
I have 22 to do. :(


You can copy a new bootloader to the old machines and run installboot.


Hi Stuart,

Just to be clear and to help others here.

You are talking about these two files only right?

/usr/mdec/boot
/usr/sbin/installboot

or should this one below be included too? I don't think it's needed, but 
just want to be sure and make the info complete.


/usr/mdec/biosboot

Re: Getting stuck on trying a fresh install to 7.4

[Stuart Henderson]

On 2023-12-06, Daniel Ouellet  wrote:
>>> Any suggestion woudl be greattly appreciated.
>> 
>> Old boot loaders cannot boot 7.4 kernels.
>> Upgrade your 6.7 system to 7.3 first (the usual advice to avoid
>> skipping releases during upgrades applies). Then upgrade to 7.4.

Specifically the interface used for communicating system
console information between the boot loader and the kernel was changed.
There was backwards compat but sadly it was removed after one single
release.

I think this brings the total number of people I know who have been
affected by this up to 6 now.

> I didn't care what's on it now. All fresh install will do.
> I have 22 to do. :(

You can copy a new bootloader to the old machines and run installboot.

-- 
Please keep replies on the mailing list.

Re: Getting stuck on trying a fresh install to 7.4 (solved)

[Daniel Ouellet]

On 12/6/23 3:42 PM, Daniel Ouellet wrote:

Any suggestion woudl be greattly appreciated.


Old boot loaders cannot boot 7.4 kernels.
Upgrade your 6.7 system to 7.3 first (the usual advice to avoid
skipping releases during upgrades applies). Then upgrade to 7.4.


I didn't care what's on it now. All fresh install will do.
I have 22 to do. :(
All fresh as docs are good on what's needed and it's time to wipe clean.


Or try booting fresh 7.4 install media from a USB stick.


I do one to 7.3 now and it boot, so will see if after that I can boot 
bsd.rd 7.4.


Thank you for the clue stick, will know soon!

Daniel


Many thanks for the clue stick.

Simple solution as usual. I wish I thought of it, but never the less done.

All wipe out, fresh install, patch, configured, files restored and back 
in operation.


Thanks again!

21 more to go...

New dmesg
-

rebooting
OpenBSD 7.4 (GENERIC.MP) #0: Sun Oct 22 12:13:42 MDT 2023

r...@syspatch-74-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 34306371584 (32717MB)
avail mem = 33246916608 (31706MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb4c0 (54 entries)
bios0: vendor American Megatrends Inc. version "2.0c" date 04/30/2013
bios0: Supermicro X9SCD
acpi0 at bios0: ACPI 5.0
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT PRAD SPMI SSDT SSDT 
EINJ ERST HEST BERT
acpi0: wakeup devices UAR1(S4) P0P1(S4) USB1(S4) USB2(S4) USB3(S4) 
USB4(S4) USB5(S4) USB6(S4) USB7(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) 
RP03(S4) PXSX(S4) RP04(S4) [...]

acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E3-1220 V2 @ 3.10GHz, 3100.18 MHz, 06-3a-09, 
patch 0021
cpu0: 
FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 
64b/line 8-way L2 cache, 8MB 64b/line 16-way L3 cache

cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 100MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU E3-1220 V2 @ 3.10GHz, 3100.17 MHz, 06-3a-09, 
patch 0021
cpu1: 
FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 
64b/line 8-way L2 cache, 8MB 64b/line 16-way L3 cache

cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Xeon(R) CPU E3-1220 V2 @ 3.10GHz, 3100.32 MHz, 06-3a-09, 
patch 0021
cpu2: 
FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 
64b/line 8-way L2 cache, 8MB 64b/line 16-way L3 cache

cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Xeon(R) CPU E3-1220 V2 @ 3.10GHz, 3100.30 MHz, 06-3a-09, 
patch 0021
cpu3: 
FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu3: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 
64b/line 8-way L2 cache, 8MB 64b/line 16-way L3 cache

cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (P0P1)
acpiprt2 at acpi0: bus -1 (RP01)
acpiprt3 at acpi0: bus -1 (RP02)
acpiprt4 at acpi0: bus -1 (RP03)
acpiprt5 at acpi0: bus -1 (RP04)
acpiprt6 at acpi0: bus -1 (RP05)
a

Re: Getting stuck on trying a fresh install to 7.4

[Daniel Ouellet]

Any suggestion woudl be greattly appreciated.


Old boot loaders cannot boot 7.4 kernels.
Upgrade your 6.7 system to 7.3 first (the usual advice to avoid
skipping releases during upgrades applies). Then upgrade to 7.4.


I didn't care what's on it now. All fresh install will do.
I have 22 to do. :(
All fresh as docs are good on what's needed and it's time to wipe clean.


Or try booting fresh 7.4 install media from a USB stick.


I do one to 7.3 now and it boot, so will see if after that I can boot 
bsd.rd 7.4.


Thank you for the clue stick, will know soon!

Daniel

Re: Getting stuck on trying a fresh install to 7.4

[Daniel Ouellet]

On 12/6/23 3:26 PM, Crystal Kolipe wrote:

On Wed, Dec 06, 2023 at 03:08:09PM -0500, Daniel Ouellet wrote:

I try to do a fresh install on servers that run 6.7 to 7.4, but no matter
what I try, I get stuck.

I tried previous version and I was able to load 7.3. DMESG below for the
bsd.rd.


When you say, "fresh install", are you actually using the _bootloader_ from
7.4-release, or just trying to load the bsd.rd kernel from your existing
installation?

Or to put it another way, did you download the 7.4-release miniroot image
or just bsd.rd?


I did jut the download of bsd.rd, but I am not doing a full install of 
7.3 as suggested by Stefan and will try again and see.


I should know in a few minutes form now.

Thanks

Daniel

Re: Getting stuck on trying a fresh install to 7.4

[Crystal Kolipe]

On Wed, Dec 06, 2023 at 03:08:09PM -0500, Daniel Ouellet wrote:
> I try to do a fresh install on servers that run 6.7 to 7.4, but no matter
> what I try, I get stuck.
> 
> I tried previous version and I was able to load 7.3. DMESG below for the
> bsd.rd.

When you say, "fresh install", are you actually using the _bootloader_ from
7.4-release, or just trying to load the bsd.rd kernel from your existing
installation?

Or to put it another way, did you download the 7.4-release miniroot image
or just bsd.rd?

Re: Getting stuck on trying a fresh install to 7.4

[Stefan Sperling]

On Wed, Dec 06, 2023 at 03:08:09PM -0500, Daniel Ouellet wrote:
> Hi,
> 
> Hopefully you may have a clue stick to offer me.
> 
> I try to do a fresh install on servers that run 6.7 to 7.4, but no matter
> what I try, I get stuck.
> 
> I tried previous version and I was able to load 7.3. DMESG below for the
> bsd.rd.
> 
> I try BIOS change for EFI ONLY, or Legacy & EFI, or Legacy only. No eval.
> 
> It's not the console issue either.
> 
> I try to boot -c and disable the efi, no difference.
> 
> I try to load the bdr.rd i386 to see, or the amd64, still on both case no
> eval and I put before the different output of each one. The i386 reboot
> after a few second, the amd64 get stuck until I force a reboot.
> 
> I put the actual working dmesg of the current install s wlel for more info.
> 
> On google I saw a few reference at the output I got saying may be the cpu
> doesn't support 64 bits, bnut it is and have been runnign the AMD for years.
> So that's not it either.
> 
> That really shoildn't make a difference, but just for the records, I also
> run softradi on these servers as shown below.
> 
> Could this be a cause may be?
> 
> Any suggestion woudl be greattly appreciated.

Old boot loaders cannot boot 7.4 kernels.
Upgrade your 6.7 system to 7.3 first (the usual advice to avoid
skipping releases during upgrades applies). Then upgrade to 7.4.

Or try booting fresh 7.4 install media from a USB stick.

Getting stuck on trying a fresh install to 7.4

[Daniel Ouellet]

Hi,

Hopefully you may have a clue stick to offer me.

I try to do a fresh install on servers that run 6.7 to 7.4, but no 
matter what I try, I get stuck.


I tried previous version and I was able to load 7.3. DMESG below for the 
bsd.rd.


I try BIOS change for EFI ONLY, or Legacy & EFI, or Legacy only. No eval.

It's not the console issue either.

I try to boot -c and disable the efi, no difference.

I try to load the bdr.rd i386 to see, or the amd64, still on both case 
no eval and I put before the different output of each one. The i386 
reboot after a few second, the amd64 get stuck until I force a reboot.


I put the actual working dmesg of the current install s wlel for more info.

On google I saw a few reference at the output I got saying may be the 
cpu doesn't support 64 bits, bnut it is and have been runnign the AMD 
for years. So that's not it either.


That really shoildn't make a difference, but just for the records, I 
also run softradi on these servers as shown below.


Could this be a cause may be?

Any suggestion woudl be greattly appreciated.

Thanks

Daniel


--
Try to boot with i386 bsd.rd
--

I get this and the server reboot after a few seconds.

 [88+160+28]=0x9183001888\
entry point at 0xd02010003291667-

Nothing after that

--
Try to boot with amd64 bsd.rd
--

I get this and stop, nothing happens after that.

+444888+297417]=0xa7679847
entry point at 0x81001000808+3886664+0|

--
Also I tried to load the 74 bsd. I know it wouldn't work, or shouldn't 
with the userland, etc but I just wanted to see if it start to boot 
anyway and it just display the below and reboot.

--

+368672+0+1241088 [1340407+128+1321080+1013316]=0x1973738
entry point at 0x81001000142096|

--
And I tried to load the 74 bsd.mp. Same results, reboot after displaying 
the following.

--

+4137992+363792+0+1236992 [1342507+128+1317840+1011174]=0x1959a68
entry point at 0x81001000

--
Then I tried the 7.3 bsd.rd and it was able to load.
I didn't a full install, nbut I sure can, I just want to do a fresh 
install of 7.4 and I can't.


DMESG below of the working version 7.3 amd64 bsd.rd
--

 [109+440424+293778]=0xa667f0
entry point at 0x8100100047616-
 ?Copyright (c) 1982, 1986, 1989, 1991, 
1993

The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2023 OpenBSD. All rights reserved. 
https://www.OpenBSD.org


OpenBSD 7.3 (RAMDISK_CD) #1063: Sat Mar 25 10:41:49 MDT 2023
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 34306371584 (32717MB)
avail mem = 33262641152 (31721MB)
random: boothowto does not indicate good seed
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb4c0 (58 entries)
bios0: vendor American Megatrends Inc. version "2.0c" date 04/30/2013
bios0: Supermicro X9SCD
acpi0 at bios0: ACPI 5.0
acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT PRAD SPMI SSDT SSDT 
EINJ ERST HEST BERT

acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E3-1220 V2 @ 3.10GHz, 3100.55 MHz, 06-3a-09
cpu0: 
FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 
64b/line 8-way L2 cache, 8MB 64b/line 16-way L3 cache

cpu0: apic clock running at 100MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (P0P1)
acpiprt2 at acpi0: bus -1 (RP01)
acpiprt3 at acpi0: bus -1 (RP02)
acpiprt4 at acpi0: bus -1 (RP03)
acpiprt5 at acpi0: bus -1 (RP04)
acpiprt6 at acpi0: bus -1 (RP05)
acpiprt7 at acpi0: bus -1 (RP06)
acpiprt8 at acpi0: bus -1 (RP07)
acpiprt9 at acpi0: bus -1 (RP08)
acpiprt10 at acpi0: bus 1 (PEG0)
acpiprt11 at acpi0: bus -1 (PEG1)
acpiprt12 at acpi0: bus -1 (PEG2)
acpiprt13 at acpi0: bus -1 (PEG3)
acpiec0 at acpi0: not present
acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x
acpicmos0 at acpi0
com0 at acpi0 UAR1 addr 0x3f8/0x8 irq 4: ns16550a, 16 byte fifo
com1 at acpi0 UAR2 addr 0x2f8/0x8 irq 3: ns16550a, 16 byte fifo
com1: console
"IPI0001" at acpi0 not configured
"PNP0C0C" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"

Re: ImageMagick fails on OpenBSD 7.4 fresh install

[Stuart Henderson]

On 2023-10-22, Mark  wrote:
> pkg_add ImageMagick-6.9.12.88p0 gives me;
>
> (after fetching few libraries)
>
> "Can't install ImageMagick-6.9.12.88p0: can't resolve
> djvulibre-3.5.28p1,libheif-1.16.2p0"
>
> and then;
> "Couldn't install ImageMagick-6.9.12.88p0 djvulibre-3.5.28p1
> libheif-1.16.2p0."
>
> This is a fresh OpenBSD 7.4 amd64 release. My installurl is pointed to
> cdn.openbsd.org/pub/OpenBSD.
>
> Any other php packages were installed fine. But both pecl80-imagick-3.7.0p1
> and ImageMagick fail.
>
> Some idea would be much appreciated!

There was an issue with the gtk-update-icon-cache update between 7.3 and
7.4 (switching from gtk+3 to gtk+4) which causes this.

Try simply rerunning pkg_add -u, it has fixed things for me.

-- 
Please keep replies on the mailing list.

Re: ImageMagick fails on OpenBSD 7.4 fresh install

[Philip Guenther]

Ah, sorry for my misreading what you wrote.

Please use 'sendbug' to report the sequence of pkg_add operations that
didn't work.


Philip Guenther


On Sun, Oct 22, 2023 at 5:50 PM Mark  wrote:

> It wasn't an upgraded system, that's fresh install, a completely new
> OpenBSD 7.4 amd64.
>
> And the first package I wanted to install, was imagick. And it failed as on
> the screenshot image link.
>
> However, installing the "gtk-update-icon-cache" package, and after, pkg_add
> imagick solved the problem.
>
> That was the suggestion of "quinq", from IRC #openbsd. ("can you try
> installing that package, and then ImageMagick?")
>
> Philip Guenther , 23 Eki 2023 Pzt, 02:54 tarihinde
> şunu
> yazdı:
>
> > Don't know what's wrong with the pkg database (/var/db/pkg/) on your
> > system, but on mine the shared-mime-info-2.2 package includes a
> definition
> > for the update-mime-info tag, so if yours lacks that then something in
> > there got hosed during your upgrade.  Could be data loss from disk
> failure,
> > could be something pruned critical info from /var/db/pkg/, could be
> > something I can't think of.
> >
> > So, I would suggest starting with verifying your confidence in your
> > storage (no kernel log error messages about I/O errors?  If this machine
> > has suffered any file system issues then maybe backup, verify-backup,
> newfs
> > and restore?)
> >
> > Then I would probably reinstall *all* packages, but since I don't (fully)
> > trust the pkg database, I would probably do it with the
> > 1) pkg_info -mz > manual
> > 2) cd /var/db/pkg && pkg_delete *
> > 3) make sure nothing unexpected has been left behind in /var/db/pkg/ or
> > /usr/local/*
> > 4) pkg_add -l manual
> >
> >
> > Or maybe now's a good time to do a fresh install.  
> >
> >
> > Philip Guenther
> >
> >
> > On Sun, Oct 22, 2023 at 3:34 PM Mark  wrote:
> >
> >> Tried changing the installurl, an another mirror, but didn't help.
> >>
> >> Here's what actually happens;
> >>
> >> https://i.ibb.co/G0wbGf5/terminal-sshot.png
> >>
> >> Regards.
> >>
> >> Mark , 23 Eki 2023 Pzt, 01:16 tarihinde şunu
> >> yazdı:
> >>
> >> > pkg_add ImageMagick-6.9.12.88p0 gives me;
> >> >
> >> > (after fetching few libraries)
> >> >
> >> > "Can't install ImageMagick-6.9.12.88p0: can't resolve
> >> > djvulibre-3.5.28p1,libheif-1.16.2p0"
> >> >
> >> > and then;
> >> > "Couldn't install ImageMagick-6.9.12.88p0 djvulibre-3.5.28p1
> >> > libheif-1.16.2p0."
> >> >
> >> > This is a fresh OpenBSD 7.4 amd64 release. My installurl is pointed to
> >> > cdn.openbsd.org/pub/OpenBSD.
> >> >
> >> > Any other php packages were installed fine. But both
> >> > pecl80-imagick-3.7.0p1 and ImageMagick fail.
> >> >
> >> > Some idea would be much appreciated!
> >> >
> >> > Regards.
> >> >
> >>
> >
>

Re: ImageMagick fails on OpenBSD 7.4 fresh install

[Mark]

It wasn't an upgraded system, that's fresh install, a completely new
OpenBSD 7.4 amd64.

And the first package I wanted to install, was imagick. And it failed as on
the screenshot image link.

However, installing the "gtk-update-icon-cache" package, and after, pkg_add
imagick solved the problem.

That was the suggestion of "quinq", from IRC #openbsd. ("can you try
installing that package, and then ImageMagick?")

Philip Guenther , 23 Eki 2023 Pzt, 02:54 tarihinde şunu
yazdı:

> Don't know what's wrong with the pkg database (/var/db/pkg/) on your
> system, but on mine the shared-mime-info-2.2 package includes a definition
> for the update-mime-info tag, so if yours lacks that then something in
> there got hosed during your upgrade.  Could be data loss from disk failure,
> could be something pruned critical info from /var/db/pkg/, could be
> something I can't think of.
>
> So, I would suggest starting with verifying your confidence in your
> storage (no kernel log error messages about I/O errors?  If this machine
> has suffered any file system issues then maybe backup, verify-backup, newfs
> and restore?)
>
> Then I would probably reinstall *all* packages, but since I don't (fully)
> trust the pkg database, I would probably do it with the
> 1) pkg_info -mz > manual
> 2) cd /var/db/pkg && pkg_delete *
> 3) make sure nothing unexpected has been left behind in /var/db/pkg/ or
> /usr/local/*
> 4) pkg_add -l manual
>
>
> Or maybe now's a good time to do a fresh install.  
>
>
> Philip Guenther
>
>
> On Sun, Oct 22, 2023 at 3:34 PM Mark  wrote:
>
>> Tried changing the installurl, an another mirror, but didn't help.
>>
>> Here's what actually happens;
>>
>> https://i.ibb.co/G0wbGf5/terminal-sshot.png
>>
>> Regards.
>>
>> Mark , 23 Eki 2023 Pzt, 01:16 tarihinde şunu
>> yazdı:
>>
>> > pkg_add ImageMagick-6.9.12.88p0 gives me;
>> >
>> > (after fetching few libraries)
>> >
>> > "Can't install ImageMagick-6.9.12.88p0: can't resolve
>> > djvulibre-3.5.28p1,libheif-1.16.2p0"
>> >
>> > and then;
>> > "Couldn't install ImageMagick-6.9.12.88p0 djvulibre-3.5.28p1
>> > libheif-1.16.2p0."
>> >
>> > This is a fresh OpenBSD 7.4 amd64 release. My installurl is pointed to
>> > cdn.openbsd.org/pub/OpenBSD.
>> >
>> > Any other php packages were installed fine. But both
>> > pecl80-imagick-3.7.0p1 and ImageMagick fail.
>> >
>> > Some idea would be much appreciated!
>> >
>> > Regards.
>> >
>>
>

Re: ImageMagick fails on OpenBSD 7.4 fresh install

[Philip Guenther]

Don't know what's wrong with the pkg database (/var/db/pkg/) on your
system, but on mine the shared-mime-info-2.2 package includes a definition
for the update-mime-info tag, so if yours lacks that then something in
there got hosed during your upgrade.  Could be data loss from disk failure,
could be something pruned critical info from /var/db/pkg/, could be
something I can't think of.

So, I would suggest starting with verifying your confidence in your storage
(no kernel log error messages about I/O errors?  If this machine has
suffered any file system issues then maybe backup, verify-backup, newfs and
restore?)

Then I would probably reinstall *all* packages, but since I don't (fully)
trust the pkg database, I would probably do it with the
1) pkg_info -mz > manual
2) cd /var/db/pkg && pkg_delete *
3) make sure nothing unexpected has been left behind in /var/db/pkg/ or
/usr/local/*
4) pkg_add -l manual


Or maybe now's a good time to do a fresh install.  


Philip Guenther


On Sun, Oct 22, 2023 at 3:34 PM Mark  wrote:

> Tried changing the installurl, an another mirror, but didn't help.
>
> Here's what actually happens;
>
> https://i.ibb.co/G0wbGf5/terminal-sshot.png
>
> Regards.
>
> Mark , 23 Eki 2023 Pzt, 01:16 tarihinde şunu
> yazdı:
>
> > pkg_add ImageMagick-6.9.12.88p0 gives me;
> >
> > (after fetching few libraries)
> >
> > "Can't install ImageMagick-6.9.12.88p0: can't resolve
> > djvulibre-3.5.28p1,libheif-1.16.2p0"
> >
> > and then;
> > "Couldn't install ImageMagick-6.9.12.88p0 djvulibre-3.5.28p1
> > libheif-1.16.2p0."
> >
> > This is a fresh OpenBSD 7.4 amd64 release. My installurl is pointed to
> > cdn.openbsd.org/pub/OpenBSD.
> >
> > Any other php packages were installed fine. But both
> > pecl80-imagick-3.7.0p1 and ImageMagick fail.
> >
> > Some idea would be much appreciated!
> >
> > Regards.
> >
>

Re: ImageMagick fails on OpenBSD 7.4 fresh install

[Mark]

Tried changing the installurl, an another mirror, but didn't help.

Here's what actually happens;

https://i.ibb.co/G0wbGf5/terminal-sshot.png

Regards.

Mark , 23 Eki 2023 Pzt, 01:16 tarihinde şunu
yazdı:

> pkg_add ImageMagick-6.9.12.88p0 gives me;
>
> (after fetching few libraries)
>
> "Can't install ImageMagick-6.9.12.88p0: can't resolve
> djvulibre-3.5.28p1,libheif-1.16.2p0"
>
> and then;
> "Couldn't install ImageMagick-6.9.12.88p0 djvulibre-3.5.28p1
> libheif-1.16.2p0."
>
> This is a fresh OpenBSD 7.4 amd64 release. My installurl is pointed to
> cdn.openbsd.org/pub/OpenBSD.
>
> Any other php packages were installed fine. But both
> pecl80-imagick-3.7.0p1 and ImageMagick fail.
>
> Some idea would be much appreciated!
>
> Regards.
>

ImageMagick fails on OpenBSD 7.4 fresh install

[Mark]

pkg_add ImageMagick-6.9.12.88p0 gives me;

(after fetching few libraries)

"Can't install ImageMagick-6.9.12.88p0: can't resolve
djvulibre-3.5.28p1,libheif-1.16.2p0"

and then;
"Couldn't install ImageMagick-6.9.12.88p0 djvulibre-3.5.28p1
libheif-1.16.2p0."

This is a fresh OpenBSD 7.4 amd64 release. My installurl is pointed to
cdn.openbsd.org/pub/OpenBSD.

Any other php packages were installed fine. But both pecl80-imagick-3.7.0p1
and ImageMagick fail.

Some idea would be much appreciated!

Regards.

Re: A messed-up fresh install due to a careless user

[Odd Martin Baanrud]

Hello Brian,

I forgot to say that my site set did include the already prepared pf.conf, but 
not rc.conf.local, where pf was set to be disabled.
As the result, pf started with rules for nat/firewall, not the default ones.
And that created the “problem”.

Martin

Re: A messed-up fresh install due to a careless user

[Brian Conway]

On Sat, Apr 29, 2023, at 3:48 AM, Odd Martin Baanrud wrote:
> Yes, off course one should have a firewall.
> That was why I installed OpenBSD on the actual machine in the first place.
> I prepared it when it was on the LAN only, and then moved it into production.
> And now it works perfectely.
> But the firewall needed to be disabled while the machine was on the LAN only.

The default pf.conf is very sufficient for allowing incoming traffic in a LAN 
environment.

Brian Conway

Re: A messed-up fresh install due to a careless user

[Odd Martin Baanrud]

Hello Steve,

Yes, off course one should have a firewall.
That was why I installed OpenBSD on the actual machine in the first place.
I prepared it when it was on the LAN only, and then moved it into production.
And now it works perfectely.
But the firewall needed to be disabled while the machine was on the LAN only.

Regarding braille, I hope *BSD gets native support for braille displaies some 
day.
The software (brltty) compiles, but it doesn’t get any output from the console.
I guess this has to do with the console driver itself, not outputting data the 
way brltty needs.
OpenBSD has a port of brltty which can be run in “screen”, but the version is 
really out-dated.

Regards, Martin

Re: A messed-up fresh install due to a careless user

[Steve Litt]

Odd Martin Baanrud said on Fri, 28 Apr 2023 10:01:29 +0200

>Hello Stefan,
>
>Thanks for the clear-up.
>And now, it works!
>When I created the site set, I forgot to add /etc/rc.conf.local, where
>pf was set to be disabled. The reason was, as you see, pf. :-)
>So a simple “pfctl -d” solved the “problem”.
>Good to know that the fault actually wasn’t a careless user who
>installed the system, but rather a careless user who forgot to add a
>simple file to a tar archive. :-)
>
>Regards, Martin
>

You really should have a firewall though. Perhaps set up pf.conf to let
through what you need.


SteveT

Steve Litt 
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm

Re: A messed-up fresh install due to a careless user

[Odd Martin Baanrud]

Hello Stefan,

Thanks for the clear-up.
And now, it works!
When I created the site set, I forgot to add /etc/rc.conf.local, where pf was 
set to be disabled.
The reason was, as you see, pf. :-)
So a simple “pfctl -d” solved the “problem”.
Good to know that the fault actually wasn’t a careless user who installed the 
system, but rather a careless user who forgot to add a simple file to a tar 
archive. :-)

Regards, Martin

Re: A messed-up fresh install due to a careless user

[Stefan Hagen]

Hello Daniel,

I'm writing my text to the top of the email. This is probably easier for
you to read than inline quoting.

On the reboot question, you can ctrl+z + reboot. This would not have a
negative effect on the installation. This is exactly what the installer
would do if you answer "r" for reboot.

Also unplugging the USB stick has no negative effect at this point.

The boot loader has been installed, otherwise your OpenBSD installation
would not have started. And the boot loader is installed after all sets
have been extracted. Therefore it's unlikely that files are missing.

I can not tell why the network configuration has not been written. If
you type "mail" as root, you should find an email with all the questions
and answers that were used during the installation. Maybe this gives a
clue. I tend to believe that the network was not configured using the
installer.

Best Regards,
Stefan

Odd Martin Baanrud wrote (2023-04-27 23:31 CEST):
> Hello,
> 
> I’m blind, and got sighted help to install OpenBSD on the machine which 
> should become a new router.
> Unfortunately, I was stupid enough to detach the USB stick I booted from, 
> before I was to hit R for the reboot.
> The result was that the last selection disappeared due to the detach message 
> from the kernel, and I didn’t manage to get it back.
> The only way I thaught could be used for reboot was to hit ctrl+Z, and then 
> type reboot.
> And it “worked”.
> 
> When I connected the machine to the LAN afterwords, I didn’t get contact.
> After trying a few things, I finally got an IP on it, with the correct 
> hostname.
> (I connected a keyboard, logged in as root, and configured one of the 
> interfaces with ifconfig $if autoconf.)
> I’ve good expereince doing so without braille.
> 
> So the machine got an IP, but still no contact, either with ping or ssh.
> I then realized that mandatory files has not been written, including the 
> hostname.if file for the NIC used durring install.
> And I guess others too. :-)
> 
> Which files are actually written when rebooting the corret way?
> I’ve OpenBSD 7.3 installed on both a arm64 and a i386 machine.
> Can I use the missing files from one of those?
> I should be able to copy them to a USB stick, and mount it and get the files 
> in place without sighted help.
> And the network interface can be configured with dhcp for now.
> As soon as the machine is on the lan, I’ll ssh into it from a linux machine 
> with a braille display.
> 
> Regards, Martin
> 
> PS: I’ve now learned that one should reboot _BEFORE_ detaching any external 
> device when the installer is still running. :-)
> 

Re: A messed-up fresh install due to a careless user

[Odd Martin Baanrud]

Hello Daniel,

The problem is, as I told, that I’m blind.
I don’t have a screen at home, and it’s not easy to bring it to someone who has.

All went just fine until it was time to reboot.
So if someone could tell me what is missing, I guess it should work to get in 
the missing files from another install of the same version. (7.3)

Regards, Martin

Re: A messed-up fresh install due to a careless user

[Daniel Ouellet]

If that's a new install, may as well just redo it.

The install is really fast, so this way you are sure you have a clean 
system and NOT one that you may have problem down the road, specially if 
that's your first time.


That's what I would do anyway.

Compare to any other IS, the install for OpenBSD is the fastest I ever 
seen, except may be NixOS when you move it to a new system. (;







On 4/27/23 5:31 PM, Odd Martin Baanrud wrote:

Hello,

I’m blind, and got sighted help to install OpenBSD on the machine which should 
become a new router.
Unfortunately, I was stupid enough to detach the USB stick I booted from, 
before I was to hit R for the reboot.
The result was that the last selection disappeared due to the detach message 
from the kernel, and I didn’t manage to get it back.
The only way I thaught could be used for reboot was to hit ctrl+Z, and then 
type reboot.
And it “worked”.

When I connected the machine to the LAN afterwords, I didn’t get contact.
After trying a few things, I finally got an IP on it, with the correct hostname.
(I connected a keyboard, logged in as root, and configured one of the 
interfaces with ifconfig $if autoconf.)
I’ve good expereince doing so without braille.

So the machine got an IP, but still no contact, either with ping or ssh.
I then realized that mandatory files has not been written, including the 
hostname.if file for the NIC used durring install.
And I guess others too. :-)

Which files are actually written when rebooting the corret way?
I’ve OpenBSD 7.3 installed on both a arm64 and a i386 machine.
Can I use the missing files from one of those?
I should be able to copy them to a USB stick, and mount it and get the files in 
place without sighted help.
And the network interface can be configured with dhcp for now.
As soon as the machine is on the lan, I’ll ssh into it from a linux machine 
with a braille display.

Regards, Martin

PS: I’ve now learned that one should reboot _BEFORE_ detaching any external 
device when the installer is still running. :-)

A messed-up fresh install due to a careless user

[Odd Martin Baanrud]

Hello,

I’m blind, and got sighted help to install OpenBSD on the machine which should 
become a new router.
Unfortunately, I was stupid enough to detach the USB stick I booted from, 
before I was to hit R for the reboot.
The result was that the last selection disappeared due to the detach message 
from the kernel, and I didn’t manage to get it back.
The only way I thaught could be used for reboot was to hit ctrl+Z, and then 
type reboot.
And it “worked”.

When I connected the machine to the LAN afterwords, I didn’t get contact.
After trying a few things, I finally got an IP on it, with the correct hostname.
(I connected a keyboard, logged in as root, and configured one of the 
interfaces with ifconfig $if autoconf.)
I’ve good expereince doing so without braille.

So the machine got an IP, but still no contact, either with ping or ssh.
I then realized that mandatory files has not been written, including the 
hostname.if file for the NIC used durring install.
And I guess others too. :-)

Which files are actually written when rebooting the corret way?
I’ve OpenBSD 7.3 installed on both a arm64 and a i386 machine.
Can I use the missing files from one of those?
I should be able to copy them to a USB stick, and mount it and get the files in 
place without sighted help.
And the network interface can be configured with dhcp for now.
As soon as the machine is on the lan, I’ll ssh into it from a linux machine 
with a braille display.

Regards, Martin

PS: I’ve now learned that one should reboot _BEFORE_ detaching any external 
device when the installer is still running. :-)

Re: Not bootable after successfull fresh install

[George]

On 2023-03-06 07:55, Francois Pussault wrote:

using installboot  manually gave answer files are not given so ISO are faulted

Using / as rootinstalling bootstrap on /dev/rsd2cusing first-stage 
/usr/mdec/biosboot, second-stage /usr/mdec/bootinstallboot: /usr/mdec/biosboot: 
No such file or directory

Le 6 mars 2023 à 12:56, Francois Pussault  a écrit :
hello,

used all from https://www.openbsd.org/faq/faq4.html#Download
but no image iso/img/netimage/etc... (7.2) failed install  all are working 
perfectly   therefore reboot cannot be done  after the install process

it looks like it wrote the MBR nowhere or in ram or something similar  or 
install media itself  maybe.
how to force install of it properly on MBR on SDx choosen by me

get the standard "no OS found" error from bios


Hello Francois,

Please, make sure you pick the right disk at the prompt, not you can 
enter ? to get the list and judge by the size whether it is the right 
one usually sd0. You need to write the MBR to it.


Usually following the prompts exactly (i.e. no customizations) will 
result in a full install which works right of the bat. I use the 
install72.img installer normally.


Please post all commands and output errors and make sure your BIOS does 
not pose any restrictions (UEFI you'll need UEFI partition, etc..).


Good luck.

George




Cordialement

Francois Pussault
10 chemin de négo saoumos
apt 202 - bat 2
31300 Toulouse
+33 6 17 230 820
fpussa...@contactoffice.fr

Cordialement
Francois Pussault
10 chemin de négo saoumos
apt 202 - bat 2
31300 Toulouse
+33 6 17 230 820
fpussa...@contactoffice.fr

Re: Not bootable after successfull fresh install

[Stuart Henderson]

On 2023-03-06, Francois Pussault  wrote:
> using installboot  manually gave answer files are not given so ISO are faulted
>
> Using / as rootinstalling bootstrap on /dev/rsd2cusing first-stage 
> /usr/mdec/biosboot, second-stage /usr/mdec/bootinstallboot: 
> /usr/mdec/biosboot: No such file or directory

Those files are from the newly installed system and are expected
to be untarred as part of the 'base' set.

Did you include all the file sets (base, man, xbase, [...])?

Were any errors shown during extract?

-- 
Please keep replies on the mailing list.

Re: Not bootable after successfull fresh install

[Francois Pussault]

using installboot  manually gave answer files are not given so ISO are faulted

Using / as rootinstalling bootstrap on /dev/rsd2cusing first-stage 
/usr/mdec/biosboot, second-stage /usr/mdec/bootinstallboot: /usr/mdec/biosboot: 
No such file or directory

Le 6 mars 2023 à 12:56, Francois Pussault  a écrit :
hello, 

used all from https://www.openbsd.org/faq/faq4.html#Download
but no image iso/img/netimage/etc... (7.2) failed install  all are working 
perfectly   therefore reboot cannot be done  after the install process  

it looks like it wrote the MBR nowhere or in ram or something similar  or 
install media itself  maybe.
how to force install of it properly on MBR on SDx choosen by me 

get the standard "no OS found" error from bios

Cordialement

Francois Pussault
10 chemin de négo saoumos
apt 202 - bat 2
31300 Toulouse
+33 6 17 230 820 
fpussa...@contactoffice.fr

Cordialement
Francois Pussault
10 chemin de négo saoumos
apt 202 - bat 2
31300 Toulouse
+33 6 17 230 820 
fpussa...@contactoffice.fr

Not bootable after successfull fresh install

[Francois Pussault]

hello, 

used all from https://www.openbsd.org/faq/faq4.html#Download
but no image iso/img/netimage/etc... (7.2) failed install  all are working 
perfectly   therefore reboot cannot be done  after the install process  

it looks like it wrote the MBR nowhere or in ram or something similar  or 
install media itself  maybe.
how to force install of it properly on MBR on SDx choosen by me 

get the standard "no OS found" error from bios

Cordialement

Francois Pussault
10 chemin de négo saoumos
apt 202 - bat 2
31300 Toulouse
+33 6 17 230 820 
fpussa...@contactoffice.fr

Re: Problems with a fresh install not finding SSD drive over floppy img HTML5/KVM

[Chris Bennett]

On Tue, Nov 30, 2021 at 11:11:03PM -0700, Theo de Raadt wrote:
> I am dissapointed to see "long answers" to "short spurious claims".
> 
> Nick, your long mail didn't help anything.
> 
> Chris, your report sucks.  Use sendbug and file a bug report with no
> details missing.  Not one user has reported a drive missing on a ahci
> controller before you, and suddenly you say (paraphasing) "oh i hear this
> is very common!"). The intentionally vague way you approach this looks like
> you want to make us look bad.
> 

My apologies. The company does not allow cdrom images except from
Windows.
I used the floppy image.
It turns out that the floppy img does not support this type of drive.

After asking the company to mount the cdrom image from their side, no
problems.

FWIW, if I did not see this information, sorry.
If this is worth the effort, it would be helpful to have this noted.

I mentioned my Samsung drive because my really quick search on the
mailing list only mentioned problems for this brand of drive having
interface problems. It was not a detailed search.

Happy to now have amd64 -current.

-- 
Thank all of you for the help,
Chris Bennett

Re: Problems with a fresh install not finding SSD drive over floppy img HTML5/KVM

[Theo de Raadt]

I am dissapointed to see "long answers" to "short spurious claims".

Nick, your long mail didn't help anything.

Chris, your report sucks.  Use sendbug and file a bug report with no
details missing.  Not one user has reported a drive missing on a ahci
controller before you, and suddenly you say (paraphasing) "oh i hear this
is very common!"). The intentionally vague way you approach this looks like
you want to make us look bad.

Nick Holland  wrote:

> On 11/30/21 3:30 PM, Chris Bennett wrote:
> > After looking over the list, it looks like many SSD's have compatibility
> > problems, so I'm just going to switch over to a spinning drive.
> > Sorry for the noise.
> > 
> 
> categorical nonsense.
> 
> SSDs work.  Cheap ones work, expensive ones work.  Some work better than
> others,  I wish cost predicted success, hasn't in my experience, but
> some IBM branded SAN SSD drives have had an oddly low rate of failure at
> work...but then each drive probably costs as much as one of my cars,
> and stores a very modest amount of data...so maybe at the really high
> end you get what you pay for.  maybe.
> 
> I've had nothing but problems with /some/ Samsung drives, good luck
> with some junk no-name drives, but the key thing is...if the SATA or SAS
> port the drive is plugged into works, the drive will be recognized and
> work (though maybe better or worse than you wish...but that's not an OS
> issue).
> 
> For a system to boot, the BIOS must support the drive.  For the system
> to get installed, the OS must support the drive.  You can boot a kernel
> from a disk the OS doesn't recognize, and you can install the OS to a
> drive the system can't boot from.  The fact that you "see" the drive in
> the BIOS means only that the drive is hooked up properly.  Doesn't
> indicate OS support.
> 
> Make sure your BIOS is set to support the drives as "AHCI" if that's an
> option.  If you see "RAID", that won't work for good reasons.  If the
> drive is attached to a real RAID controller, the controller may not be
> supported, or you may have it configured wrong (i.e., the drives are there,
> but not configured on the RAID Card, so the RAID card isn't presenting
> "drives" to the OS).
> 
> Provide useful info rather than stomping your feet and saying "it worked
> before!".  Obviously, things are different.  The answer is almost
> certainly in the dmesg.
> 
> Nick.
> 

Re: Problems with a fresh install not finding SSD drive over floppy img HTML5/KVM

[Nick Holland]

On 11/30/21 3:30 PM, Chris Bennett wrote:

After looking over the list, it looks like many SSD's have compatibility
problems, so I'm just going to switch over to a spinning drive.

Sorry for the noise.



categorical nonsense.

SSDs work.  Cheap ones work, expensive ones work.  Some work better than
others,  I wish cost predicted success, hasn't in my experience, but
some IBM branded SAN SSD drives have had an oddly low rate of failure at
work...but then each drive probably costs as much as one of my cars,
and stores a very modest amount of data...so maybe at the really high
end you get what you pay for.  maybe.

I've had nothing but problems with /some/ Samsung drives, good luck
with some junk no-name drives, but the key thing is...if the SATA or SAS
port the drive is plugged into works, the drive will be recognized and
work (though maybe better or worse than you wish...but that's not an OS
issue).

For a system to boot, the BIOS must support the drive.  For the system
to get installed, the OS must support the drive.  You can boot a kernel
from a disk the OS doesn't recognize, and you can install the OS to a
drive the system can't boot from.  The fact that you "see" the drive in
the BIOS means only that the drive is hooked up properly.  Doesn't
indicate OS support.

Make sure your BIOS is set to support the drives as "AHCI" if that's an
option.  If you see "RAID", that won't work for good reasons.  If the
drive is attached to a real RAID controller, the controller may not be
supported, or you may have it configured wrong (i.e., the drives are there,
but not configured on the RAID Card, so the RAID card isn't presenting
"drives" to the OS).

Provide useful info rather than stomping your feet and saying "it worked
before!".  Obviously, things are different.  The answer is almost
certainly in the dmesg.

Nick.

Re: Problems with a fresh install not finding SSD drive over floppy img HTML5/KVM

[Chris Bennett]

On Tue, Nov 30, 2021 at 03:25:30PM -0700, Theo de Raadt wrote:
> Chris Bennett  wrote:
> 
> > After looking over the list, it looks like many SSD's have compatibility
> > problems, so I'm just going to switch over to a spinning drive.
> 
> That is news to us.
> 

I am also more than a little shocked by this.

>From amd64 7.0 -current floppy img:

OpenBSD 7.0-current Ramdisk #129 Tue Nov 30 11:03
Supermicro X11SSD-F
cpu0 Intel Xeon E3-1270 v6 3.80Ghz


>From an auto-installed FreeBSD 12.x by the company:

Samsung SSD 860 Pro 256GB RVM01B6Q ACS-4 ATA SATA 3.x device



Back to OpenBSD, amd64 shows sd0 as the floppy img
i386 (7.0 release) does not mention sd0 at all

I could not get network up at all under either OpenBSD or FreeBSD (zero
experience with FreeBSD).

However, I did get an error I have never seen before.
When they (supposedly) changed boxes, I kept the same /29 IP block.
I accidentally assigned the static IP addresses to em0 instead of em1.
Then I added it correctly to em1.

STDERR constantly repeated that I had assigned the same IP to both.
Bringing both down stopped the error.

However, I did not touch igb0 (em0) under FreeBSD. After changing igb1
(em1) to the correct address, I got the same error in FreeBSD.
Huh?

The company refuses to change the SSD to the spinning drive, but I can
add it as a second drive. This was a special offer, so I can't complain.
I looked at the specials again. All are only with this drive.

I am at a complete loss here about what's going on. I specifically
grabbed this to be able to run -current OpenBSD.
I previously ran this exact type of box with this company before with a
1TB drive. So I have used this IPMI before.

-- 
Frustrated,
Chris Bennett

Re: Problems with a fresh install not finding SSD drive over floppy img HTML5/KVM

[Theo de Raadt]

Chris Bennett  wrote:

> After looking over the list, it looks like many SSD's have compatibility
> problems, so I'm just going to switch over to a spinning drive.

That is news to us.

Re: Problems with a fresh install not finding SSD drive over floppy img HTML5/KVM

[Allan Streib]

On Tue, Nov 30, 2021, at 3:47 PM, Crystal Kolipe wrote:
> There are plenty of SSDs that work just fine with OpenBSD, and have done
> for a long time.
>
> We've used Corsair, Sandisk, and Kingston SSDs in various OpenBSD machines
> for many years with very few issues.

$ dmesg | grep ^sd

sd0 at scsibus2 targ 0 lun 0:  naa.50025385a01f1611
sd0: 488386MB, 512 bytes/sector, 1000215216 sectors, thin
sd1 at scsibus2 targ 1 lun 0:  naa.500a075112866a03
sd1: 976762MB, 512 bytes/sector, 2000409264 sectors, thin

Both working without issue for me.

Allan

Re: Problems with a fresh install not finding SSD drive over floppy img HTML5/KVM

[Crystal Kolipe]

On Tue, Nov 30, 2021 at 12:30:50PM -0800, Chris Bennett wrote:
> After looking over the list, it looks like many SSD's have compatibility
> problems, so I'm just going to switch over to a spinning drive.

There are plenty of SSDs that work just fine with OpenBSD, and have done
for a long time.

We've used Corsair, Sandisk, and Kingston SSDs in various OpenBSD machines
for many years with very few issues.

Re: Problems with a fresh install not finding SSD drive over floppy img HTML5/KVM

[Chris Bennett]

After looking over the list, it looks like many SSD's have compatibility
problems, so I'm just going to switch over to a spinning drive.

Sorry for the noise.
-- 
Chris Bennett

Problems with a fresh install not finding SSD drive over floppy img HTML5/KVM

[Chris Bennett]

Hi.
I have never done an install to a SSD drive.
The first server they gave me was a bust, so they swapped out boxes.
That has not helped. BIOS shows a Samsung SSD drive, but the settings
were at hard drive instead of SSD drive. I changed that.
Drive does not show up with either setting.
There were also weird networking problems with em0 and em1.

For both boxes, the KVM has been very wonky. Sometimes it works,
sometimes it doesn't, sometimes it disconnects.

I have used this type of server with this company before.
I had zero problems.
I have tried 7.0 and 6.9 amd64. floppy image shows up as sd0 and rd0a
I also tried 7.0 i386. With this one, no drive except rd0a

Shell does not show any drive.

I just did an automated FreeBSD 12 and that installed, but doesn't
manage ssh or pings. It shows up in KVM, but I can't get my keyboard or
virtual keyboard to work.

This server shows up with a status of up. The new one has a status of
NA.
Any help deeply appreciated.

I will probably end up requesting a spinning 1TB drive.
But I have some doubts at this point if I am getting junk boxes.
This was with a Black Friday discount.

--
Chris Bennett

Re: Alpine hangs on send in fresh install of 6.8

[Peter J. Philipp]

On Sat, Jan 23, 2021 at 08:33:11AM -0700, aus...@computershop.ca wrote:
> 
> Anyone out there still using Alpine mail client with 6.8?
> 
> Used Alpine for 20 years or more, and recently set up a new mail server.
> Old one used to be on a 5.3 OpenBSD version.
> 
> New one works fine in every respect for reading and saving incoming messages, 
> going to subfolders, but after composing a message it hangs as soon as I give
> the ^X to send it. Have to close the X-window to get rid of the session, and
> then kill the hanging task PID with a kill -9 
> 
> The basic "Mail" email client works fine -- and I am using it here,
> but it doesn't have the conveniences I am used to. 
> 
> Any suggestions appreciated.  
> 
> -- Austin

Hi Austin,

Here is how I would go about debugging this.  ktrace, it's a powerful tool.
ktrace -i alpine it and do what you normally do and then kill -9.  When
that's done use kdump to trace back where the SIGKILL signal killed it.  It's
usually at the end.  So if you do kdump | less and press 'G' no quotes it will
go right to the end.  From there scroll up, to see where it may be hanging.
You could be useing kdump -TR as well to see relative time since start of
the program...

One warning through ktrace will fill up a file called ktrace.out relatively
quickly.  A ktrace -C ensures that all ktraces are stopped in the system if
you suspect it's still ongoing.  To check that kdump -l perhaps or just 
ls -l ktrace.out.

You will be faced with every system call made by alpine including forks and
execution of other programs, so if you send mail it's possible that you see
the sendmail wrapper binary and any other binaries that are executed.  Do have
a good look at the ktrace and kdump manpages before doing my advice though.

Another warning is not to share that data, which makes it difficult to debug
if you don't know this set of programs.  It's private data and noone should 
have an insight of what your mailbox looks like.  So it's difficult...

Another advice I have is perhaps keep an eye on dmesg, perhaps you're hitting
a constraint somewhere?

Best Regards,

-peter

Alpine hangs on send in fresh install of 6.8

[austin]

Anyone out there still using Alpine mail client with 6.8?

Used Alpine for 20 years or more, and recently set up a new mail server.
Old one used to be on a 5.3 OpenBSD version.

New one works fine in every respect for reading and saving incoming messages, 
going to subfolders, but after composing a message it hangs as soon as I give
the ^X to send it. Have to close the X-window to get rid of the session, and
then kill the hanging task PID with a kill -9 

The basic "Mail" email client works fine -- and I am using it here,
but it doesn't have the conveniences I am used to. 

Any suggestions appreciated.  

-- Austin

Re: fresh install

[Hakan E. Duran]

Thank you so much Chris and Tom for your thoughtful and detailed
replies. I found them inspiring and full of wisdom and appreciate your
time in putting them together.

Hakan



signature.asc
Description: PGP signature

Re: fresh install

[Chris Bennett]

On Mon, Oct 19, 2020 at 05:55:59PM -0500, Hakan E. Duran wrote:
> Dear all,
> 
> Having been a linux user for quite a while, I am used to doing a fresh 
> install every few years, following a few upgrades. I usually set a separate 
> partition for the /home directory to be able to inherit my settings to the 
> fresh installation. This is the first time I did an upgrade in OpenBSD from 
> 6.7 to 6.8, which actually went flawless, but being a skeptical linux user, I 
> am wondering how I can do a fresh install if need be, by preserving my user 
> directory. I chose the auto-partitioning during the installation of OpenBSD 
> 6.7 but I don't know if that would be possible in a scenario like this, since 
> I am not sure if the installation algorithm would recognize the /home 
> directory or not. Your guidance will be greatly appreciated.
> 
> Hakan
> 

You can do a fresh install and preserve existing partitions with great
care and NOT using auto partition. Just don't add /home to the
partitions to be created and make absolutely sure that the area on the
disklabel doesn't include the space allocated for /home.
But only if this fresh install is after having done a fresh install
previously. Use Custom for the disklabel step, which will reflect the
already existing disklabel, except without the mount points. You will
need to delete the /home partition, finish the install, then use
disklabel to add the home partition, fsck -fp it, and mount it manually.
If OK, add to fstab if desired.

Be sure to backup the /home partition before doing this.
Since this is a bit complicated, practice this many times, read the
manual pages very well. Buy a USB drive to practice this on.
Be sure to do something wrong. Understanding this will really help you
if you somehow have a disaster, like a sudden power failure that messes
up a critical partition hopelessly.

This is not Linux. The rules are totally different. If you ask yourself
what you would do in Linux, you have failed in this task.

Auto-partition is really helpful for someone new to OpenBSD.
But I rarely partition across only a single disk and always partition
some special partitions like /var/postgresql, /home/vip-user, /var/www,
etc. /usr/src, /usr/obj are not needed by every user now that we have
syspatch.

Have fun,
Chris Bennett

Re: fresh install

[Tom Smyth]

Hi Hakan,
easiest method would be to have your /home on a separate drive if
possible...   that way when you run the installer
your "OS Disk"  can be blown away by the auto partitioning and then
you can manually update the /etc/fstab to mount
/home to the home partition on your "Own UserDisk"

this I think is the most foolproof  (tom proof anyway )   way of doing it ...

the partition method / offsets may change from version to version (in
my humble experience) it may be because the different
disk manufacturers.

that said the OpenBSD Installers / upgrade tools are designed to be
straightforward, not to be too complex

for instance if you dont install a given install set eg xbase.tgz  at
install time, you can simply download it and extract the tgz
file in / and it will install the set just like the installer would.

If you love your data and you are unfamiliar with OpenBSDs partitions
and installers I would not be reinstalling the OS
over existing partitions without a backup.

the upgrade tools bsd.rd  / sysupgrade or the latest install.iso or
install.img are pretty  reliable when it comes to upgrades.
(even when I dont use the standard partition layouts)

I hope this helps

Tom Smyth




On Tue, 20 Oct 2020 at 00:14, Hakan E. Duran  wrote:
>
> Dear all,
>
> Having been a linux user for quite a while, I am used to doing a fresh 
> install every few years, following a few upgrades. I usually set a separate 
> partition for the /home directory to be able to inherit my settings to the 
> fresh installation. This is the first time I did an upgrade in OpenBSD from 
> 6.7 to 6.8, which actually went flawless, but being a skeptical linux user, I 
> am wondering how I can do a fresh install if need be, by preserving my user 
> directory. I chose the auto-partitioning during the installation of OpenBSD 
> 6.7 but I don't know if that would be possible in a scenario like this, since 
> I am not sure if the installation algorithm would recognize the /home 
> directory or not. Your guidance will be greatly appreciated.
>
> Hakan
>


-- 
Kindest regards,
Tom Smyth.

fresh install

[Hakan E. Duran]

Dear all,

Having been a linux user for quite a while, I am used to doing a fresh install 
every few years, following a few upgrades. I usually set a separate partition 
for the /home directory to be able to inherit my settings to the fresh 
installation. This is the first time I did an upgrade in OpenBSD from 6.7 to 
6.8, which actually went flawless, but being a skeptical linux user, I am 
wondering how I can do a fresh install if need be, by preserving my user 
directory. I chose the auto-partitioning during the installation of OpenBSD 6.7 
but I don't know if that would be possible in a scenario like this, since I am 
not sure if the installation algorithm would recognize the /home directory or 
not. Your guidance will be greatly appreciated.

Hakan

Re: Cannot make update on updated ports on a fresh install

[lea.chescotta]

Thank you! Ill look up for that setting, so its best to make as normal user and 
then install i assume. Removing all those vars from /etc/mk.conf solved the 
issue, i got used to put those there in previous installs but now i have a 
bigger disk and i dont need them  as the /usr partition is bigger, so its 
solved now, thanks!


16. Aug 2018 22:07 by danj+o...@chown.me :


> On Thu, 16 Aug 2018 23:41:52 +0200 (CEST), <> lea.chesco...@tutanota.com 
> > >
> wrote:
>
> Probably not helping much but
>
>> lea@openbsd:/usr/ports/net/curl $ doas make update
>
> You shouldn't run this as root if you don't have PORTS_PRIVSEP
>
>> On my /etc/mk.conf i have:
>> SUDO=/usr/bin/doas
>> WRKOBJDIR=/usr/ports/build/wrkobjdir
>> DISTDIR=/usr/ports/build/distdir
>> PLIST_DB=/usr/ports/build/plist
>> BULK_COOKIES_DIR=/usr/ports/build/bulk_cookies
>> UPDATE_COOKIES_DIR=/usr/ports/build/update_cookies
>> PACKAGE_REPOSITORY=/usr/ports/build/pkgrepo
>> FETCH_PACKAGES=Yes
>
> Do you really need to configure all these var and not use the default?
>
> Cheers,
> Daniel

Re: Cannot make update on updated ports on a fresh install

[Daniel Jakots]

On Thu, 16 Aug 2018 23:41:52 +0200 (CEST), 
wrote:

Probably not helping much but

> lea@openbsd:/usr/ports/net/curl $ doas make update

You shouldn't run this as root if you don't have PORTS_PRIVSEP

> On my /etc/mk.conf i have:
> SUDO=/usr/bin/doas
> WRKOBJDIR=/usr/ports/build/wrkobjdir
> DISTDIR=/usr/ports/build/distdir
> PLIST_DB=/usr/ports/build/plist
> BULK_COOKIES_DIR=/usr/ports/build/bulk_cookies
> UPDATE_COOKIES_DIR=/usr/ports/build/update_cookies
> PACKAGE_REPOSITORY=/usr/ports/build/pkgrepo
> FETCH_PACKAGES=Yes

Do you really need to configure all these var and not use the default?

Cheers,
Daniel

Cannot make update on updated ports on a fresh install

[lea.chescotta]

Hi! im getting this error on a fresh install of openbsd 6.3 -stable, when 
trying to update any package after getting the ports tree and update it,  i 
surely missed something but cannot figure out what. Never happened to me on 
other installations that i can remember.

lea@openbsd:/usr/ports/net/curl $ doas make update
===>  Looking for curl-7.59.0p1.tgz in $PKG_PATH - not found
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1928 
'/usr/ports/build/pkgrepo/amd64/cache/curl-7.59.0p1.tgz':
@if /usr/bin/env -...)
===>  Checking files for curl-7.59.0p1
`/usr/ports/build/distdir' is up to date.
`/curl-7.59.0.tar.xz' is up to date.
>> cksum: cannot open curl-7.59.0.tar.xz: No such file or directory 
>>  
(SHA256) curl-7.59.0.tar.xz: MISSING
Make sure the Makefile and /usr/ports/net/curl/distinfo
are up to date.  If you want to fetch a good copy of this file  
 
from the OpenBSD main archive, type
    make REFETCH=true [other args]
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2324 
'_internal-checksum')    
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2508 
'/usr/ports/build/wrkobjdir/curl-7.59.0/.extract_done')  
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1938 
'/usr/ports/build/pkgrepo/amd64/all/curl-7.59.0p1.tgz')  
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1936 
'/usr/ports/build/pkgrepo/amd64/all/curl-7.59.0p1.tgz')  
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2440 
'_internal-package') 
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1965 
'/usr/ports/build/update_cookies/curl-7.59.0p1') 
*** Error 1 in /usr/ports/net/curl 
(/usr/ports/infrastructure/mk/bsd.port.mk:2419 'update')

On my /etc/mk.conf i have:
SUDO=/usr/bin/doas
WRKOBJDIR=/usr/ports/build/wrkobjdir
DISTDIR=/usr/ports/build/distdir
PLIST_DB=/usr/ports/build/plist
BULK_COOKIES_DIR=/usr/ports/build/bulk_cookies
UPDATE_COOKIES_DIR=/usr/ports/build/update_cookies
PACKAGE_REPOSITORY=/usr/ports/build/pkgrepo
FETCH_PACKAGES=Yes

And i had created those directories before:
lea@openbsd:/usr/ports/build $ ls -lahF 
 
total 32
drwxr-xr-x   8 root  wsrc   512B Aug 16 18:18 ./
drwxr-xr-x  47 root  wsrc   1.0K Aug 16 18:14 ../
drwxr-xr-x   2 root  wsrc   512B Aug 16 18:18 bulk_cookies/
drwxr-xr-x   2 root  wsrc   512B Aug 16 18:18 distdir/
drwxr-xr-x   3 root  wsrc   512B Aug 16 18:14 pkgrepo/
drwxr-xr-x   2 root  wsrc   512B Aug 16 18:18 plist/
drwxr-xr-x   2 root  wsrc   512B Aug 16 18:18 update_cookies/   
 
drwxr-xr-x   5 root  wsrc   512B Aug 16 18:21 wrkobjdir/

Re: [6.2] Problem with X, .cwmrc file missing from fresh install

[Luka Kosanovic]

Thanks for the info, I got a picture there needs to be a default one
from last thread. Ill read docs more carefully next time.

On Thu, Mar 8, 2018 at 8:49 AM, Maurice McCarthy  wrote:
> On 08/03/18 05:16, Luka Kosanovic wrote:
>> Hi, Im a new user and I have a problem with cwm, everything works, I
>> login and default xterm window appears but default keyboard shortcuts
>> do not work. I tried many standard shortcuts and nothing happens, then
>> I went on mailing lists and found somebody had the same problem a
>> month ago so I did a little bit of digging and found out .cwmrc conf
>> file doesnt exist.
>> Can you please tell me why is that, shouldnt there
>> be a default file in my home folder with a fresh install? Everything
>> else works as expected there were no problems.
>>
>> Thank you
>>
>
> The zero config is intentional. First have a read of man 5 cwmrc. My own
> ~/.cwmrc looks like this:
>
> command xterm   /usr/X11R6/bin/xterm -bg black -fg wheat -fn 10x20 -ls
>
> and ~/.xsession like this:
>
> exec /usr/X11R6/cwm
>
>
> and ~/.xinitrc like so:
>
> /usr/X11R6/bin/xconsole -geometry -0+0 -fn 8x10 & \
> /usr/X11R6/bin/xterm -e tmux -2u & \
> /usr/X11R6/bin/xterm & \
> /usr/X11R6/bin/cwm
>
> Good Luck
>

Re: [6.2] Problem with X, .cwmrc file missing from fresh install

[Maurice McCarthy]

On 08/03/18 05:16, Luka Kosanovic wrote:
> Hi, Im a new user and I have a problem with cwm, everything works, I
> login and default xterm window appears but default keyboard shortcuts
> do not work. I tried many standard shortcuts and nothing happens, then
> I went on mailing lists and found somebody had the same problem a
> month ago so I did a little bit of digging and found out .cwmrc conf
> file doesnt exist.
> Can you please tell me why is that, shouldnt there
> be a default file in my home folder with a fresh install? Everything
> else works as expected there were no problems.
> 
> Thank you
> 

The zero config is intentional. First have a read of man 5 cwmrc. My own
~/.cwmrc looks like this:

command xterm   /usr/X11R6/bin/xterm -bg black -fg wheat -fn 10x20 -ls

and ~/.xsession like this:

exec /usr/X11R6/cwm


and ~/.xinitrc like so:

/usr/X11R6/bin/xconsole -geometry -0+0 -fn 8x10 & \ 
/usr/X11R6/bin/xterm -e tmux -2u & \
/usr/X11R6/bin/xterm & \
/usr/X11R6/bin/cwm 

Good Luck

Re: [6.2] Problem with X, .cwmrc file missing from fresh install

[Kapfhammer, Stefan]

Hello Luca,

there is no default .cwmrc in a user's home folder.
The standard shortcuts are described in cwm(1)‎.

Stefan

  Origineel bericht
Van: Luka Kosanovic
Verzonden: donderdag 8 maart 2018 05:17
Aan: misc
Onderwerp: [6.2] Problem with X, .cwmrc file missing from fresh install


Hi, Im a new user and I have a problem with cwm, everything works, I
login and default xterm window appears but default keyboard shortcuts
do not work. I tried many standard shortcuts and nothing happens, then
I went on mailing lists and found somebody had the same problem a
month ago so I did a little bit of digging and found out .cwmrc conf
file doesnt exist.
Can you please tell me why is that, shouldnt there
be a default file in my home folder with a fresh install? Everything
else works as expected there were no problems.

Thank you

[6.2] Problem with X, .cwmrc file missing from fresh install

[Luka Kosanovic]

Hi, Im a new user and I have a problem with cwm, everything works, I
login and default xterm window appears but default keyboard shortcuts
do not work. I tried many standard shortcuts and nothing happens, then
I went on mailing lists and found somebody had the same problem a
month ago so I did a little bit of digging and found out .cwmrc conf
file doesnt exist.
Can you please tell me why is that, shouldnt there
be a default file in my home folder with a fresh install? Everything
else works as expected there were no problems.

Thank you

Re: pkg_add on OpenBSD 6.1, fresh install

[Maurice McCarthy]

On Tue, Apr 11, 2017 at 04:43:27PM -0600 or thereabouts, Anathae Townsend wrote:
> I have done a fresh install of 6.1 (downloaded it today, from
> ftp.openbsd.org/pub/OpenBSD/6.1/amd64 as the file install61.fs (I live in
> Edmonton, Alberta, that's why I use the source ftp)) and was trying to
> install some packages...
> 
> When I type in pkg_add -v http://ftp.openbsd.org/%m/joe (as an example),
> pkg_add reports joe not found.  If instead I do pkg_add -v
> http://ftp.openbsd.org/pub/OpenBSD/6.1/packages/amd64/joe, it works.  
> 
> Admittedly, I am running this from the root login... am I doing something
> wrong?
> 
> Anathae
> 

$ man pkg.conf
...
Special sequences â%a, %c, %m, %v will be expanded to
package architecture, OS version or snapshots,
full mirror pathâand OS version respectively.
... 

"%m" is the _whole _path

pkg_add on OpenBSD 6.1, fresh install

[Anathae Townsend]

I have done a fresh install of 6.1 (downloaded it today, from
ftp.openbsd.org/pub/OpenBSD/6.1/amd64 as the file install61.fs (I live in
Edmonton, Alberta, that's why I use the source ftp)) and was trying to
install some packages...

When I type in pkg_add -v http://ftp.openbsd.org/%m/joe (as an example),
pkg_add reports joe not found.  If instead I do pkg_add -v
http://ftp.openbsd.org/pub/OpenBSD/6.1/packages/amd64/joe, it works.  

Admittedly, I am running this from the root login... am I doing something
wrong?

Anathae

wsmoused conflicts with xorg on 6.0 Supermicro PDSMI+ fresh install

[Paolo Aglialoro]

Hello,

on this Supermicro PDSMI+ board (latest bios) it looks like that activating
wsmoused (both plain and with -2 flag) disables pointer control under Xorg
i.e. mouse works correctly in CLI but not in X.

Running "wsmoused -f -d" reports no output, both when moving/clicking in
CLI and X.

Any clues?
Thanks

Dmesg follows:

OpenBSD 6.0 (GENERIC.MP) #2319: Tue Jul 26 13:00:43 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4277010432 (4078MB)
avail mem = 4142915584 (3950MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.51 @ 0xdfeea000 (31 entries)
bios0: vendor Phoenix Technologies LTD version "6.00" date 03/05/2008
bios0: Supermicro PDSMi
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP MCFG APIC BOOT ASF! SSDT
acpi0: wakeup devices DEV1(S5) EXP1(S5) PXHA(S5) EXP5(S5) EXP6(S5) PCIB(S5)
KBC0(S1) MSE0(S1) COM1(S5) COM2(S5) USB1(S4) USB2(S4) USB3(S4) USB4(S4)
EUSB(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimcfg0 at acpi0 addr 0xf000, bus 0-14
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU X3230 @ 2.66GHz, 2660.40 MHz
cpu0:
FPU,VME,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,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR
cpu0: 4MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 266MHz
cpu0: mwait min=64, max=64, C-substates=0.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Xeon(R) CPU X3230 @ 2.66GHz, 2660.01 MHz
cpu1:
FPU,VME,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,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR
cpu1: 4MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Xeon(R) CPU X3230 @ 2.66GHz, 2660.01 MHz
cpu2:
FPU,VME,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,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR
cpu2: 4MB 64b/line 16-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Xeon(R) CPU X3230 @ 2.66GHz, 2660.01 MHz
cpu3:
FPU,VME,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,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR
cpu3: 4MB 64b/line 16-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins
ioapic1 at mainbus0: apid 5 pa 0xfec1, version 20, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (DEV1)
acpiprt2 at acpi0: bus 9 (EXP1)
acpiprt3 at acpi0: bus 10 (PXHA)
acpiprt4 at acpi0: bus 13 (EXP5)
acpiprt5 at acpi0: bus 14 (EXP6)
acpiprt6 at acpi0: bus 15 (PCIB)
acpicpu0 at acpi0: C1(@1 halt!), PSS
acpicpu1 at acpi0: C1(@1 halt!), PSS
acpicpu2 at acpi0: C1(@1 halt!), PSS
acpicpu3 at acpi0: C1(@1 halt!), PSS
"PNP0A05" at acpi0 not configured
"PNP0303" at acpi0 not configured
"PNP0F13" at acpi0 not configured
"PNP0501" at acpi0 not configured
"PNP0700" at acpi0 not configured
acpibtn0 at acpi0: PWRB
ipmi at mainbus0 not configured
cpu0: Enhanced SpeedStep 2660 MHz: speeds: 2667, 2400, 2133, 1867, 1600 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel E7230 Host" rev 0xc0
ppb0 at pci0 dev 1 function 0 "Intel E7230 PCIE" rev 0xc0: msi
pci1 at ppb0 bus 1
ppb1 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01: msi
pci2 at ppb1 bus 9
ppb2 at pci2 dev 0 function 0 "Intel 6702PXH PCIE-PCIX" rev 0x09
pci3 at ppb2 bus 10
"Intel IOxAPIC" rev 0x09 at pci2 dev 0 function 1 not configured
ppb3 at pci0 dev 28 function 4 "Intel 82801G PCIE" rev 0x01: msi
pci4 at ppb3 bus 13
em0 at pci4 dev 0 function 0 "Intel 82573E" rev 0x03: msi, address
00:30:48:9b:af:a6
ppb4 at pci0 dev 28 function 5 "Intel 82801G PCIE" rev 0x01: msi
pci5 at ppb4 bus 14
em1 at pci5 dev 0 function 0 "Intel 82573L" rev 0x00: msi, address
00:30:48:9b:af:a7
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x01: apic 4 int 23
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x01: apic 4 int 19
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x01: apic 4 int 18
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x01: apic 4 int 16
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x01: apic 4 int 23
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb5 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xe1
pci6 at ppb5 bus 15
radeondrm0 at pci6 dev 0 function 0 "ATI ES1000" rev 0x02
drm0 at radeondrm0
radeondrm0: apic 4 int 1

Re: Fresh install ftp SSL handshake failed

[Oliver Marugg]

Superb, many thanks.

On 28 Nov 2016, at 22:02, Janne Johansson wrote:

> Fix the clock so its not 7th of March?
>
>
> 2016-11-28 21:55 GMT+01:00 Oliver Marugg :
>
>> Hi
>>
>> I did a complete new install of OpenBSD 6.0-current today.
>>
>> After first boot I followed FAQ, sent dmesg, and read afterboot(8) but I
>> am running in some trouble downloading the initial ports.tar.gz,
>> packages install and DNS works fine. Just found out that Ntpd in
>> /var/log/messages shows the same error. Any ideas, what I could do?
>> Thanks oliver
>>
>> ---
>> FTP:
>> #  ftp https://ftp.openbsd.org/pub/OpenBSD/$(uname -r)/ports.tar.gz
>> Trying 129.128.5.191...
>> Requesting https://ftp.openbsd.org/pub/OpenBSD/6.0/ports.tar.gz
>> ftp: SSL read error: handshake failed: error:14090086:SSL
>> routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
>> #
>> ---
>> NTPD:
>>
>> WRONG DATE Mar  7 04:30:07 Hostname ntpd[51018]: tls write failed:
>> 172.217.19.164 (www.google.com): handshake failed: error:14090086:SSL
>> routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
>> ---
>>
>>
>
>
> -- 
> May the most significant bit of your life be positive.

Re: Fresh install ftp SSL handshake failed

[Janne Johansson]

Fix the clock so its not 7th of March?


2016-11-28 21:55 GMT+01:00 Oliver Marugg :

> Hi
>
> I did a complete new install of OpenBSD 6.0-current today.
>
> After first boot I followed FAQ, sent dmesg, and read afterboot(8) but I
> am running in some trouble downloading the initial ports.tar.gz,
> packages install and DNS works fine. Just found out that Ntpd in
> /var/log/messages shows the same error. Any ideas, what I could do?
> Thanks oliver
>
> ---
> FTP:
> #  ftp https://ftp.openbsd.org/pub/OpenBSD/$(uname -r)/ports.tar.gz
> Trying 129.128.5.191...
> Requesting https://ftp.openbsd.org/pub/OpenBSD/6.0/ports.tar.gz
> ftp: SSL read error: handshake failed: error:14090086:SSL
> routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
> #
> ---
> NTPD:
>
> WRONG DATE Mar  7 04:30:07 Hostname ntpd[51018]: tls write failed:
> 172.217.19.164 (www.google.com): handshake failed: error:14090086:SSL
> routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
> ---
>
>


-- 
May the most significant bit of your life be positive.

Fresh install ftp SSL handshake failed

[Oliver Marugg]

Hi

I did a complete new install of OpenBSD 6.0-current today.

After first boot I followed FAQ, sent dmesg, and read afterboot(8) but I 
am running in some trouble downloading the initial ports.tar.gz, 
packages install and DNS works fine. Just found out that Ntpd in 
/var/log/messages shows the same error. Any ideas, what I could do? 
Thanks oliver

---
FTP:
#  ftp https://ftp.openbsd.org/pub/OpenBSD/$(uname -r)/ports.tar.gz
Trying 129.128.5.191...
Requesting https://ftp.openbsd.org/pub/OpenBSD/6.0/ports.tar.gz
ftp: SSL read error: handshake failed: error:14090086:SSL 
routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
#
---
NTPD:

WRONG DATE Mar  7 04:30:07 Hostname ntpd[51018]: tls write failed: 
172.217.19.164 (www.google.com): handshake failed: error:14090086:SSL 
routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
---

fresh install to i386 kde4 only has UTC on clock...

[Luke Small]

Re: xenocara build on fresh install

[trondd]

On Sat, September 10, 2016 4:14 pm, Stephen Trotter wrote:
> hi, I am just curious if the defaults (namely the disk sizes) are supposed
> to be sufficient for building xenocara after a fresh install.
>
> i attempted to do so following release(8) and it ended unsuccessfully due
> to the drive/filesystem being full.
>
> (it does seem to have almost finished, by the way)
>
> All I have done else in the system is pulling source and making according
> to the faq5 page.  This is after skipping the "release" part and moving on
> to building xenocara.
>
> Let me know what else i need to include for assist.
>

No.  Generally users are encouraged to use snapshots and packages and not
build things themselves so the auto-partitioning mostly assumes that.  The
problem is that since the auto-partitioning layout doesn't include a
separate /usr/xenocara or /usr/xobj partitions, it all goes into /usr
which is allocated a max of 2G and probably not enough inodes.

See disklabel(8).

If you have a giant /home left over, carve out a /usr/xenocara and a
/usr/xobj for yourself.  I gave each 5G and am using ~15% of each.  To
give you an idea.

Tim.

xenocara build on fresh install

[Stephen Trotter]

hi, I am just curious if the defaults (namely the disk sizes) are supposed
to be sufficient for building xenocara after a fresh install.

i attempted to do so following release(8) and it ended unsuccessfully due
to the drive/filesystem being full.

(it does seem to have almost finished, by the way)

All I have done else in the system is pulling source and making according
to the faq5 page.  This is after skipping the "release" part and moving on
to building xenocara.

Let me know what else i need to include for assist.

Re: fresh install of 6.0 - cvs

[Stephen Trotter]

Thanks again for all the help! I just finished a fresh install, logged in
as root and updated the wsrc group on my user, then after login as the user
was able to start up CVS with no issue at all.  Just wanted to verify.

On Fri, Sep 9, 2016 at 10:33 AM, Theo Buehler  wrote:

> On Fri, Sep 09, 2016 at 10:19:21AM -0400, Stephen Trotter wrote:
> > Aha, this is probably what was going on.  I used su to add my user to the
> > group, then had just exited to my user shell to continue with the faq.
> > I'll probably do a fresh install and ensure it works out, and to make
> sure
> > I don't have any issues with CVS.  Thanks for the help!
>
> I added a couple of clarifications to faq5.html and anoncvs.html to
> avoid this confusion in the future. Thanks for the report.

Re: fresh install of 6.0 - cvs

[Theo Buehler]

On Fri, Sep 09, 2016 at 10:19:21AM -0400, Stephen Trotter wrote:
> Aha, this is probably what was going on.  I used su to add my user to the
> group, then had just exited to my user shell to continue with the faq.
> I'll probably do a fresh install and ensure it works out, and to make sure
> I don't have any issues with CVS.  Thanks for the help!

I added a couple of clarifications to faq5.html and anoncvs.html to
avoid this confusion in the future. Thanks for the report.

Re: fresh install of 6.0 - cvs

[Stephen Trotter]

Aha, this is probably what was going on.  I used su to add my user to the
group, then had just exited to my user shell to continue with the faq.
I'll probably do a fresh install and ensure it works out, and to make sure
I don't have any issues with CVS.  Thanks for the help!

Stephen J. Trotter

On Fri, Sep 9, 2016 at 9:38 AM, Christian Weisgerber 
wrote:

> On 2016-09-09, Theo Buehler  wrote:
>
> > I tried myself on a fresh install, added my user to wsrc, and I can
> > confirm that I got permission errors (write permissions denied to
> > /usr/src) which went away after logging out and logging in again.
>
> Yes, you have to login again for the new group membership to be
> active.
>
> --
> Christian "naddy" Weisgerber  na...@mips.inka.de

Re: fresh install of 6.0 - cvs

[Raf Czlonka]

On Fri, Sep 09, 2016 at 01:04:44PM BST, Stephen Trotter wrote:
> Raf,
> 
> Yes I was attempting to follow the instructions and was logged in as my
> user, not as root. And I was pulling the src from cvs (for the first time)
> and using the -r option for the stable version.

Well, in order to avoid root privileges, first you need to run at
least one command as root :^)

> Theo,
> 
> The user is a member of wsrc. That was part of the reason I was so confused
> at the time. (I can't verify with id at the moment, but I did check
> /etc/group to ensure the user was listed under wsrc.)

If you had added the user to the 'wsrc' group using su(1) or using
another terminal, then the change will obviously get reflected in
the /etc/group file but it won't take immediate effect if the user
is already logged on, so the easiest way is to simply re-logon.

> I suspect that /usr is not owned by wsrc possibly, and that cvs was trying
> to write to /usr but I cannot confirm right now. When I am able to, I will
> run cvs again without the -q option and see if there is any extra detail I
> can include.

/usr does not and should not have the group set to 'wsrc'.

If you had followed the information from FAQ then the cvs(1) command
should only write to /usr/src directory, whose group is already set
to 'wsrc'.

Regards,

Raf

Re: fresh install of 6.0 - cvs

[Christian Weisgerber]

On 2016-09-09, Theo Buehler  wrote:

> I tried myself on a fresh install, added my user to wsrc, and I can
> confirm that I got permission errors (write permissions denied to
> /usr/src) which went away after logging out and logging in again.

Yes, you have to login again for the new group membership to be
active.

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de

Re: fresh install of 6.0 - cvs

[Theo Buehler]

On Fri, Sep 09, 2016 at 08:10:19AM -0400, Stephen Trotter wrote:
> Also I should mention that I was able to get the commands to work by going
> into /usr/src and running from there, but did find afterward that a new
> copy of src was put into the folder ( i.e. /usr/src/src/ ) so I did end up
> moving everything up a directory. I am not sure, will this affect cvs in
> the future, or should I be ok as long as I run it with the full command to
> pull the src, from /usr (oppossed to running the update command first)?

I'd remove /usr/src/src, otherwise cvs will recurse into it and you'll
end up having two full source trees (which will likely not fit on the
default /usr/src partition). It is recommended that you work from a src
tree based on /usr, not one level up, especially if you're new to this.

I tried myself on a fresh install, added my user to wsrc, and I can
confirm that I got permission errors (write permissions denied to
/usr/src) which went away after logging out and logging in again.
Not entirely sure what happened there... Will investigate this later.

> > The user is a member of wsrc. That was part of the reason I was so
> > confused at the time. (I can't verify with id at the moment, but I did
> > check /etc/group to ensure the user was listed under wsrc.)
> >
> > I suspect that /usr is not owned by wsrc possibly, and that cvs was trying

That shouldn't be necessary. /usr is root:wheel with 755 permissions.

> > to write to /usr but I cannot confirm right now. When I am able to, I will
> > run cvs again without the -q option and see if there is any extra detail I
> > can include.
> >
> > Thanks, will reply again when I can run those.
> >
> > (As a side note, should doas be enabled by default? I don't recall any
> > instruction in the faq on setting it up, but when I try to use it, it
> > fails.)

Doas is not enabled by default, you enable it by creating an /etc/doas.conf
a line such as

permit youruser as root

should normally be enough. See also tedu's nice writeup here:
http://www.tedunangst.com/flak/post/doas-mastery
(note that the persist feature is only in -current).

Re: fresh install of 6.0 - cvs

[Stephen Trotter]

Also I should mention that I was able to get the commands to work by going
into /usr/src and running from there, but did find afterward that a new
copy of src was put into the folder ( i.e. /usr/src/src/ ) so I did end up
moving everything up a directory. I am not sure, will this affect cvs in
the future, or should I be ok as long as I run it with the full command to
pull the src, from /usr (oppossed to running the update command first)?

On Sep 9, 2016 8:04 AM, "Stephen Trotter" 
wrote:

> Raf,
>
> Yes I was attempting to follow the instructions and was logged in as my
> user, not as root. And I was pulling the src from cvs (for the first time)
> and using the -r option for the stable version.
>
> Theo,
>
> The user is a member of wsrc. That was part of the reason I was so
> confused at the time. (I can't verify with id at the moment, but I did
> check /etc/group to ensure the user was listed under wsrc.)
>
> I suspect that /usr is not owned by wsrc possibly, and that cvs was trying
> to write to /usr but I cannot confirm right now. When I am able to, I will
> run cvs again without the -q option and see if there is any extra detail I
> can include.
>
> Thanks, will reply again when I can run those.
>
> (As a side note, should doas be enabled by default? I don't recall any
> instruction in the faq on setting it up, but when I try to use it, it
> fails.)
>
> On Sep 9, 2016 1:20 AM, "Theo Buehler"  wrote:
>
>> On Fri, Sep 09, 2016 at 12:54:05AM -0400, Stephen Trotter wrote:
>> > hi,
>> > i was attempting a fresh install of 6.0 and got to the part where you
>> pull
>> > the source tree and update the system to stable.
>> > i was stuck because the faq states you can (should) use a regular user
>> with
>> > cvs, and i kept getting a permission error from cvs when attempting to
>> run
>> > from /usr
>> > so, just wondering if anyone else was getting this, or if there is
>> > something that i missed.
>> >
>>
>> Is your user member of the group wsrc?  Use id(1), for example.
>>
>> By default, /usr/src is owned by root:wsrc with permissions 0775.  This
>> means that you need to be root or a member of group wsrc in order to
>> write to it.  FAQ 5 'avoiding root' tells you how to add your user to
>> wsrc before running cvs: user mod -G wsrc youruser

Re: fresh install of 6.0 - cvs

[Stephen Trotter]

Raf,

Yes I was attempting to follow the instructions and was logged in as my
user, not as root. And I was pulling the src from cvs (for the first time)
and using the -r option for the stable version.

Theo,

The user is a member of wsrc. That was part of the reason I was so confused
at the time. (I can't verify with id at the moment, but I did check
/etc/group to ensure the user was listed under wsrc.)

I suspect that /usr is not owned by wsrc possibly, and that cvs was trying
to write to /usr but I cannot confirm right now. When I am able to, I will
run cvs again without the -q option and see if there is any extra detail I
can include.

Thanks, will reply again when I can run those.

(As a side note, should doas be enabled by default? I don't recall any
instruction in the faq on setting it up, but when I try to use it, it
fails.)

On Sep 9, 2016 1:20 AM, "Theo Buehler"  wrote:

> On Fri, Sep 09, 2016 at 12:54:05AM -0400, Stephen Trotter wrote:
> > hi,
> > i was attempting a fresh install of 6.0 and got to the part where you
> pull
> > the source tree and update the system to stable.
> > i was stuck because the faq states you can (should) use a regular user
> with
> > cvs, and i kept getting a permission error from cvs when attempting to
> run
> > from /usr
> > so, just wondering if anyone else was getting this, or if there is
> > something that i missed.
> >
>
> Is your user member of the group wsrc?  Use id(1), for example.
>
> By default, /usr/src is owned by root:wsrc with permissions 0775.  This
> means that you need to be root or a member of group wsrc in order to
> write to it.  FAQ 5 'avoiding root' tells you how to add your user to
> wsrc before running cvs: user mod -G wsrc youruser

Re: fresh install of 6.0 - cvs

[Raf Czlonka]

On Fri, Sep 09, 2016 at 05:54:05AM BST, Stephen Trotter wrote:
> hi,
> i was attempting a fresh install of 6.0 and got to the part where you pull
> the source tree and update the system to stable.
> i was stuck because the faq states you can (should) use a regular user with
> cvs, and i kept getting a permission error from cvs when attempting to run
> from /usr
> so, just wondering if anyone else was getting this, or if there is
> something that i missed.
> 

Hi Stephen,

Your description is very vague and you're not giving any details of
which command you ran and what error messages you got.

I'm trying to mind-read here - after issuing the commands described
under "Avoiding root privileges", have you logged on as the user
whom you just added to the 'wsrc' group?

Regards,

Raf

Re: fresh install of 6.0 - cvs

[Theo Buehler]

On Fri, Sep 09, 2016 at 12:54:05AM -0400, Stephen Trotter wrote:
> hi,
> i was attempting a fresh install of 6.0 and got to the part where you pull
> the source tree and update the system to stable.
> i was stuck because the faq states you can (should) use a regular user with
> cvs, and i kept getting a permission error from cvs when attempting to run
> from /usr
> so, just wondering if anyone else was getting this, or if there is
> something that i missed.
> 

Is your user member of the group wsrc?  Use id(1), for example.

By default, /usr/src is owned by root:wsrc with permissions 0775.  This
means that you need to be root or a member of group wsrc in order to
write to it.  FAQ 5 'avoiding root' tells you how to add your user to
wsrc before running cvs: user mod -G wsrc youruser

fresh install of 6.0 - cvs

[Stephen Trotter]

hi,
i was attempting a fresh install of 6.0 and got to the part where you pull
the source tree and update the system to stable.
i was stuck because the faq states you can (should) use a regular user with
cvs, and i kept getting a permission error from cvs when attempting to run
from /usr
so, just wondering if anyone else was getting this, or if there is
something that i missed.

Re: Fresh install of 5.1 doesn't allow me to creat user but after install I can.

[richardtoohey]

Quoting richardtoo...@paradise.net.nz:

> Quoting cody chandler :
> 
> > Hello,
> > 
> > On Tue, Jun 26, 2012 at 4:29 PM, 
> wrote:
> > 
> > > Quoting cody chandler :
> > >
> > > > Hello,
> > > >
> > > > OpenBSD 5.1 -Release. 4 installs tested. During install when it
> > first
> > > > asks do I want to creat a user. It does not allow me to creat the
> > user
> > > > name
> > > > II00I00II. But after the install I can use useradd or adduser and
> > am
> > > > able
> > > > to login with the user. Another issue I came accross. In the
> > sudoers
> > > > file
> > > > I have 2 names under root and not using the wheel group but using
> > the
> > > > name
> > > > for sudoers. The 2nd name works but this name "II00I00II" does
> not
> > work
> > > > with sudo. Is there a reason for this to not work as expected? To
> > > > clairify the name is capital i's with number 0's.
> > > >
> > >
> > > Same sort of thing bit me when using periods in the user name:
> > >
> > >
> > >
> >
>
http://old.nabble.com/Installer-adding-user---doesn%27t-allow-periods-in-user-name-td30129803.html
> > >
> > > The installer is more strict about the permitted user names.
> > >
> > > See also man adduser.
> > >
> > I did check the man page before asking in email.
> > 
> > Per the man page of "adduser(8)"
> > 
> > RESTRICTIONS
> > username
> > It is recommended that login names contain only lowercase
> > characters and digits. They may also contain uppercase
> > characters, non-leading hyphens, periods, underscores, and a
> > trailing `$'.
> > 
> > Thats what throws me off. The username I tried is "II00I00II" upper
> case
> > i
> > and number zero (0). Which are said to be of allowed per the man
> page.
> 
> If you read what Ted says on the link I sent, he explains that older
> software
> expects user names in a certain format - the format that is recommended
> by adduser.
> 
> Sorry it turned out to be a red herring for you - when I was caught out
> by this,
> the adduser man page helped me - it explained why I could do something
> in
> adduser and not the installer - adduser follows the "may" path, the
> installer
> follows the "recommended" path.
> 
> Also in the link I sent, was the code from the installer (4.7) - and
> that shows
> what the installer was/is doing.

On re-reading the code ... to be 100% correct, it is implementing the
recommended part (lowercase a-z, 0-9) but additionally allows underscores (in
the 4.7 version that I looked at.)

I think I've muddied the waters enough, back to lurking!
> 
> HTH.
> > 
> > 
> > >
> > > > Thanks
> > > > Cody

Re: Fresh install of 5.1 doesn't allow me to creat user but after install I can.

[cody chandler]

Thanks for putting it blunt.  I read the link but did not understand the
code..  Relooking I see where it say's in plain english...

user_setup() {
local _q="Setup a user? (enter a lower-case loginname, or 'no')"
I'll creat a more friendly username!


Thanks again!
Cody

On Tue, Jun 26, 2012 at 5:13 PM,  wrote:

>  Quoting cody chandler :
>
> > Hello,
> >
> > On Tue, Jun 26, 2012 at 4:29 PM,  wrote:
> >
> > > Quoting cody chandler :
> > >
> > > > Hello,
> > > >
> > > > OpenBSD 5.1 -Release. 4 installs tested. During install when it
> > first
> > > > asks do I want to creat a user. It does not allow me to creat the
> > user
> > > > name
> > > > II00I00II. But after the install I can use useradd or adduser and
> > am
> > > > able
> > > > to login with the user. Another issue I came accross. In the
> > sudoers
> > > > file
> > > > I have 2 names under root and not using the wheel group but using
> > the
> > > > name
> > > > for sudoers. The 2nd name works but this name "II00I00II" does not
> > work
> > > > with sudo. Is there a reason for this to not work as expected? To
> > > > clairify the name is capital i's with number 0's.
> > > >
> > >
> > > Same sort of thing bit me when using periods in the user name:
> > >
> > >
> > >
> >
>
> http://old.nabble.com/Installer-adding-user---doesn%27t-allow-periods-in-user-name-td30129803.html
> > >
> > > The installer is more strict about the permitted user names.
> > >
> > > See also man adduser.
> > >
> > I did check the man page before asking in email.
> >
> > Per the man page of "adduser(8)"
> >
> > RESTRICTIONS
> >  username
> >  It is recommended that login names contain only lowercase
> >  characters and digits. They may also contain uppercase
> >  characters, non-leading hyphens, periods, underscores, and a
> >  trailing `$'.
> >
> > Thats what throws me off. The username I tried is "II00I00II" upper case
> > i
> > and number zero (0). Which are said to be of allowed per the man page.
>
> If you read what Ted says on the link I sent, he explains that older
> software
> expects user names in a certain format - the format that is recommended by
> adduser.
>
> Sorry it turned out to be a red herring for you - when I was caught out by
> this,
> the adduser man page helped me - it explained why I could do something in
> adduser and not the installer - adduser follows the "may" path, the
> installer
> follows the "recommended" path.
>
> Also in the link I sent, was the code from the installer (4.7) - and that
> shows
> what the installer was/is doing.
>
> HTH.
> >
> >
> > >
> > > > Thanks
> > > > Cody

Re: Fresh install of 5.1 doesn't allow me to creat user but after install I can.

[richardtoohey]

Quoting cody chandler :

> Hello,
> 
> On Tue, Jun 26, 2012 at 4:29 PM,  wrote:
> 
> > Quoting cody chandler :
> >
> > > Hello,
> > >
> > > OpenBSD 5.1 -Release. 4 installs tested. During install when it
> first
> > > asks do I want to creat a user. It does not allow me to creat the
> user
> > > name
> > > II00I00II. But after the install I can use useradd or adduser and
> am
> > > able
> > > to login with the user. Another issue I came accross. In the
> sudoers
> > > file
> > > I have 2 names under root and not using the wheel group but using
> the
> > > name
> > > for sudoers. The 2nd name works but this name "II00I00II" does not
> work
> > > with sudo. Is there a reason for this to not work as expected? To
> > > clairify the name is capital i's with number 0's.
> > >
> >
> > Same sort of thing bit me when using periods in the user name:
> >
> >
> >
>
http://old.nabble.com/Installer-adding-user---doesn%27t-allow-periods-in-user-name-td30129803.html
> >
> > The installer is more strict about the permitted user names.
> >
> > See also man adduser.
> >
> I did check the man page before asking in email.
> 
> Per the man page of "adduser(8)"
> 
> RESTRICTIONS
>  username
>  It is recommended that login names contain only lowercase
>  characters and digits. They may also contain uppercase
>  characters, non-leading hyphens, periods, underscores, and a
>  trailing `$'.
> 
> Thats what throws me off. The username I tried is "II00I00II" upper case
> i
> and number zero (0). Which are said to be of allowed per the man page.

If you read what Ted says on the link I sent, he explains that older software
expects user names in a certain format - the format that is recommended by 
adduser.

Sorry it turned out to be a red herring for you - when I was caught out by this,
the adduser man page helped me - it explained why I could do something in
adduser and not the installer - adduser follows the "may" path, the installer
follows the "recommended" path.

Also in the link I sent, was the code from the installer (4.7) - and that shows
what the installer was/is doing.

HTH.
> 
> 
> >
> > > Thanks
> > > Cody

Re: Fresh install of 5.1 doesn't allow me to creat user but after install I can.

[Theo de Raadt]

> >  Quoting cody chandler :
> >
> > > Hello,
> > >
> > >  OpenBSD 5.1 -Release. 4 installs tested. During install when it first
> > > asks do I want to creat a user. It does not allow me to creat the user
> > > name
> > > II00I00II. But after the install I can use useradd or adduser and am
> > > able
> > > to login with the user. Another issue I came accross. In the sudoers
> > > file
> > > I have 2 names under root and not using the wheel group but using the
> > > name
> > > for sudoers. The 2nd name works but this name "II00I00II" does not work
> > > with sudo. Is there a reason for this to not work as expected? To
> > > clairify the name is capital i's with number 0's.
> > >
> >
> > Same sort of thing bit me when using periods in the user name:
> >
> >
> > http://old.nabble.com/Installer-adding-user---doesn%27t-allow-periods-in-user-name-td30129803.html
> >
> > The installer is more strict about the permitted user names.
> >
> > See also man adduser.
> >
> I did check the man page before asking in email.
> 
> Per the man page of "adduser(8)"
> 
> RESTRICTIONS
>  username
>  It is recommended that login names contain only lowercase
>  characters and digits.  They may also contain uppercase
>  characters, non-leading hyphens, periods, underscores, and a
>  trailing `$'.
> 
> Thats what throws me off.  The username I tried is "II00I00II" upper case i
> and number zero (0).  Which are said to be of allowed per the man page.

The install script does not use adduser.

Re: Fresh install of 5.1 doesn't allow me to creat user but after install I can.

[cody chandler]

Hello,

On Tue, Jun 26, 2012 at 4:29 PM,  wrote:

>  Quoting cody chandler :
>
> > Hello,
> >
> >  OpenBSD 5.1 -Release. 4 installs tested. During install when it first
> > asks do I want to creat a user. It does not allow me to creat the user
> > name
> > II00I00II. But after the install I can use useradd or adduser and am
> > able
> > to login with the user. Another issue I came accross. In the sudoers
> > file
> > I have 2 names under root and not using the wheel group but using the
> > name
> > for sudoers. The 2nd name works but this name "II00I00II" does not work
> > with sudo. Is there a reason for this to not work as expected? To
> > clairify the name is capital i's with number 0's.
> >
>
> Same sort of thing bit me when using periods in the user name:
>
>
> http://old.nabble.com/Installer-adding-user---doesn%27t-allow-periods-in-user-name-td30129803.html
>
> The installer is more strict about the permitted user names.
>
> See also man adduser.
>
I did check the man page before asking in email.

Per the man page of "adduser(8)"

RESTRICTIONS
 username
 It is recommended that login names contain only lowercase
 characters and digits.  They may also contain uppercase
 characters, non-leading hyphens, periods, underscores, and a
 trailing `$'.

Thats what throws me off.  The username I tried is "II00I00II" upper case i
and number zero (0).  Which are said to be of allowed per the man page.


>
> > Thanks
> > Cody

Re: Fresh install of 5.1 doesn't allow me to creat user but after install I can.

[richardtoohey]

Quoting cody chandler :

> Hello,
> 
>  OpenBSD 5.1 -Release. 4 installs tested. During install when it first
> asks do I want to creat a user. It does not allow me to creat the user
> name
> II00I00II. But after the install I can use useradd or adduser and am
> able
> to login with the user. Another issue I came accross. In the sudoers
> file
> I have 2 names under root and not using the wheel group but using the
> name
> for sudoers. The 2nd name works but this name "II00I00II" does not work
> with sudo. Is there a reason for this to not work as expected? To
> clairify the name is capital i's with number 0's.
> 

Same sort of thing bit me when using periods in the user name:

http://old.nabble.com/Installer-adding-user---doesn%27t-allow-periods-in-user-name-td30129803.html

The installer is more strict about the permitted user names.

See also man adduser.

> Thanks
> Cody

Fresh install of 5.1 doesn't allow me to creat user but after install I can.

[cody chandler]

Hello,

  OpenBSD 5.1 -Release.  4 installs tested.  During install when it first
asks do I want to creat a user. It does not allow me to creat the user name
II00I00II.  But after the install I can use useradd or adduser and am able
to login with the user.  Another issue I came accross.  In the sudoers file
I have 2 names under root and not using the wheel group but using the name
for sudoers.  The 2nd name works but this name "II00I00II" does not work
with sudo.  Is there a reason for this to not work as expected?  To
clairify the name is capital i's with number 0's.

Thanks
Cody

Re: Crash during boot. Fresh install of 4.7

[Todd]

On Mon, May 31, 2010 at 1:41 AM, Jan Stary  wrote:

> On May 30 12:39:44, Todd wrote:
> > On Tue, May 25, 2010 at 9:17 PM, Todd  wrote:
> >
> > >
> > >
> > > On Tue, May 25, 2010 at 1:22 PM, Marco Peereboom  >wrote:
> > >
> > >> Can you run diffs?
> > >>
> > >
> > > maybe, with some noob  hand holding.
> > >
> > >>
> > >> If not can you download and test a kernel?
> > >>
> > >
> > > Absolutely!  just tell me where to get it.
> > >
> > This is probably no shocking revelation to anyone, but I can boot a
> custom
> > kernel rebuilt with the line commented out of the config:
> > acpicpu* at acpi?
>
> (You said "noob", so here's a friendly reminder)
>
> The Right Way to do this is not to build a custom kernel with a modified
> config file, but to use the User Kernel Configuration *UKC) of the boot(8)
> utility while booting the standard kernel and say
>
>> boot -c
>> disable acpi
>> quit
>
> There's no need to recompile anything,
> the GENERIC kernel already has it all.
>
> http://www.openbsd.org/faq/faq5.html#BootConfig
>
>Jan

That's what I like about OpenBSD.  It's always easier than it first appears.
 I had looked at the config(8) man page and it wasn't clear to me that acpi
could be disabled at boot time.  But if had I searched the archive first,  I
would have found this.
http://www.mail-archive.com/t...@openbsd.org/msg00277.html
Thanks for the data.

Re: Crash during boot. Fresh install of 4.7

[Todd]

On Tue, May 25, 2010 at 9:17 PM, Todd  wrote:

>
>
> On Tue, May 25, 2010 at 1:22 PM, Marco Peereboom wrote:
>
>> Can you run diffs?
>>
>
> maybe, with some noob  hand holding.
>
>>
>> If not can you download and test a kernel?
>>
>
> Absolutely!  just tell me where to get it.
>
This is probably no shocking revelation to anyone, but I can boot a custom
kernel rebuilt with the line commented out of the config:
acpicpu* at acpi?

Let me know if a dmesg, acpidump, or anything else from the above mentioned
kernel would be usefull.

>
>> On Tue, May 18, 2010 at 06:24:53PM -0500, Todd wrote:
>> > On Mon, May 17, 2010 at 9:58 PM, Marco Peereboom 
>> wrote:
>> >
>> > > hrm,... i might have fixed that in -current.
>> > > got a dmesg?
>> > >
>> > I installed  the snapshot from 5-13 and there is still a crash with the
>> same
>> > error.  Below is everything that is still on the screen when the crash
>> > occurs and a dmesg from booting bsd.rd
>> >
>> > acpibat1 art acpi0: BAT2 not present
>> > acpibtn2 at acpi0: LID_
>> > acpidock0 at acpi0:DCK1 not docked(0)
>> > acpivideo0 at acpi0: VGA_
>> > acpivout0 at acpivideo0: CRT_
>> > acpivout1 at acpivideo0: TV0_
>> > acpivout2 at acpivideo0: LCD_
>> > acpivideo1 at acpi0: GFX0
>> > acpivout3 at acpivideo1: DD01
>> > acpivout4 at acpivideo1: DD02
>> > acpivout5 at acpivideo1: DD03
>> > acpivout6 at acpivideo1: DD04
>> > acpivout7 at acpivideo1: DD05
>> > bios0: ROM list: 0xc/0xfa00 0xdf000/0x800!
>> > cpu0: Enhanced SpeedStep 1664 MHzKernel: interger devide fault trap,
>> code=0
>> > Stopped at est_init+0x107: idivl %esi %eax
>> > est_init(d0992174,0,0,d04f6235) at est_init+0x107
>> > intel686_setperf_setup(d0992160,d0a43e98,d0a43ec8,d04f627d at
>> > intel686_setperf_setup+0x46
>> > mainbus_attach(0,d1c48c0,0,dbdef000,d0a42334) at mainbus_attach+0x236
>> > config_attach(0,d08686d4,0,0,0) at config_attach+0xfd
>> > config_rootfound(d0785242,0,d0a43f38,d04c37fe) at config_rootfound+0x27
>> > main(0,0,0,0,0) at main+0x3b2
>> >
>> >
>> > below is the dmesg from booting bsd.rd installed from the 4.7 release cd
>> >
>> > OpenBSD 4.7 (RAMDISK_CD) #353: Wed Mar 17 21:02:53 MDT 2010
>> > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
>> > cpu0: Genuine Intel(R) CPU T2300 @ 1.66GHz ("GenuineIntel" 686-class)
>> 1.67
>> > GHz
>> > cpu0:
>> >
>> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,VMX,EST,TM2,xTPR
>> > real mem  = 1071738880 (1022MB)
>> > avail mem = 1031536640 (983MB)
>> > mainbus0 at root
>> > bios0 at mainbus0: AT/286+ BIOS, date 01/13/06, BIOS32 rev. 0 @ 0xfd620,
>> > SMBIOS rev. 2.31 @ 0xdf010 (24 entries)
>> > bios0: vendor Gateway version "71.02" date 01/13/2006992
>> > bios0: Gateway MX6710
>> > acpi0 at bios0: rev 0
>> > acpi0: tables DSDT FACP APIC ASF! MCFG APIC BOOT SSDT
>> > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
>> > cpu0 at mainbus0: apid 0 (boot processor)
>> > cpu0: apic clock running at 166MHz
>> > cpu at mainbus0: not configured
>> > ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
>> > ioapic0: misconfigured as apic 2, remapped to apid 1
>> > acpiprt0 at acpi0: bus 0 (PCI0)
>> > acpiprt1 at acpi0: bus 1 (PEGP)
>> > acpiprt2 at acpi0: bus 2 (RP01)
>> > acpiprt3 at acpi0: bus 3 (RP02)
>> > acpiprt4 at acpi0: bus -1 (RP03)
>> > acpiprt5 at acpi0: bus 4 (PCIB)
>> > bios0: ROM list: 0xc/0xfa00 0xdf000/0x800!
>> > pci0 at mainbus0 bus 0: configuration mode 1 (bios)
>> > pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
>> > ppb0 at pci0 dev 1 function 0 "Intel 82945GM PCIE" rev 0x03: apic 1 int
>> 16
>> > (irq 11)
>> > pci1 at ppb0 bus 1
>> > vga1 at pci1 dev 0 function 0 "ATI Radeon Mobility X1400" rev 0x00
>> > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
>> > "Intel 82801GB HD Audio" rev 0x02 at pci0 dev 27 function 0 not
>> configured
>> > ppb1 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: apic 1 int
>> 17
>> > (irq 11)
>> > pci2 at ppb1 bus 2
>> > em0 at pci2 dev 0 function 0 "Intel PRO/1000MT (82573L)" rev 0x00: apic
>> 1
>> > int 16 (irq 11), address 00:e0:b8:94:d6:8a
>> > ppb2 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: apic 1 int
>> 16
>> > (irq 11)
>> > pci3 at ppb2 bus 3
>> > wpi0 at pci3 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02:
>> apic 1
>> > int 17 (irq 11), MoW1, address 00:13:02:04:21:f8
>> > uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 1 int
>> 23
>> > (irq 11)
>> > uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 1 int
>> 19
>> > (irq 10)
>> > uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 1 int
>> 18
>> > (irq 10)
>> > uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 1 int
>> 16
>> > (irq 11)
>> > ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic 1 int
>> 23
>> > (irq 11)
>> > usb0 at ehci0: USB revision 2.0
>> > uhub0 at usb0 "Intel EHCI root hub" rev 2

Re: Crash during boot. Fresh install of 4.7

[Marco Peereboom]

I'll look at it.

On Tue, May 18, 2010 at 06:24:53PM -0500, Todd wrote:
> On Mon, May 17, 2010 at 9:58 PM, Marco Peereboom  wrote:
> 
> > hrm,... i might have fixed that in -current.
> > got a dmesg?
> >
> I installed  the snapshot from 5-13 and there is still a crash with the same
> error.  Below is everything that is still on the screen when the crash
> occurs and a dmesg from booting bsd.rd
> 
> acpibat1 art acpi0: BAT2 not present
> acpibtn2 at acpi0: LID_
> acpidock0 at acpi0:DCK1 not docked(0)
> acpivideo0 at acpi0: VGA_
> acpivout0 at acpivideo0: CRT_
> acpivout1 at acpivideo0: TV0_
> acpivout2 at acpivideo0: LCD_
> acpivideo1 at acpi0: GFX0
> acpivout3 at acpivideo1: DD01
> acpivout4 at acpivideo1: DD02
> acpivout5 at acpivideo1: DD03
> acpivout6 at acpivideo1: DD04
> acpivout7 at acpivideo1: DD05
> bios0: ROM list: 0xc/0xfa00 0xdf000/0x800!
> cpu0: Enhanced SpeedStep 1664 MHzKernel: interger devide fault trap, code=0
> Stopped at est_init+0x107: idivl %esi %eax
> est_init(d0992174,0,0,d04f6235) at est_init+0x107
> intel686_setperf_setup(d0992160,d0a43e98,d0a43ec8,d04f627d at
> intel686_setperf_setup+0x46
> mainbus_attach(0,d1c48c0,0,dbdef000,d0a42334) at mainbus_attach+0x236
> config_attach(0,d08686d4,0,0,0) at config_attach+0xfd
> config_rootfound(d0785242,0,d0a43f38,d04c37fe) at config_rootfound+0x27
> main(0,0,0,0,0) at main+0x3b2
> 
> 
> below is the dmesg from booting bsd.rd installed from the 4.7 release cd
> 
> OpenBSD 4.7 (RAMDISK_CD) #353: Wed Mar 17 21:02:53 MDT 2010
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
> cpu0: Genuine Intel(R) CPU T2300 @ 1.66GHz ("GenuineIntel" 686-class) 1.67
> GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,VMX,EST,TM2,xTPR
> real mem  = 1071738880 (1022MB)
> avail mem = 1031536640 (983MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 01/13/06, BIOS32 rev. 0 @ 0xfd620,
> SMBIOS rev. 2.31 @ 0xdf010 (24 entries)
> bios0: vendor Gateway version "71.02" date 01/13/2006992
> bios0: Gateway MX6710
> acpi0 at bios0: rev 0
> acpi0: tables DSDT FACP APIC ASF! MCFG APIC BOOT SSDT
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: apic clock running at 166MHz
> cpu at mainbus0: not configured
> ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
> ioapic0: misconfigured as apic 2, remapped to apid 1
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 1 (PEGP)
> acpiprt2 at acpi0: bus 2 (RP01)
> acpiprt3 at acpi0: bus 3 (RP02)
> acpiprt4 at acpi0: bus -1 (RP03)
> acpiprt5 at acpi0: bus 4 (PCIB)
> bios0: ROM list: 0xc/0xfa00 0xdf000/0x800!
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
> ppb0 at pci0 dev 1 function 0 "Intel 82945GM PCIE" rev 0x03: apic 1 int 16
> (irq 11)
> pci1 at ppb0 bus 1
> vga1 at pci1 dev 0 function 0 "ATI Radeon Mobility X1400" rev 0x00
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> "Intel 82801GB HD Audio" rev 0x02 at pci0 dev 27 function 0 not configured
> ppb1 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: apic 1 int 17
> (irq 11)
> pci2 at ppb1 bus 2
> em0 at pci2 dev 0 function 0 "Intel PRO/1000MT (82573L)" rev 0x00: apic 1
> int 16 (irq 11), address 00:e0:b8:94:d6:8a
> ppb2 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: apic 1 int 16
> (irq 11)
> pci3 at ppb2 bus 3
> wpi0 at pci3 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02: apic 1
> int 17 (irq 11), MoW1, address 00:13:02:04:21:f8
> uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 1 int 23
> (irq 11)
> uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 1 int 19
> (irq 10)
> uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 1 int 18
> (irq 10)
> uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 1 int 16
> (irq 11)
> ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic 1 int 23
> (irq 11)
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
> ppb3 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2
> pci4 at ppb3 bus 4
> cbb0 at pci4 dev 9 function 0 "TI PCIXX12 CardBus" rev 0x00: apic 1 int 17
> (irq 255), CardBus support disabled
> "TI PCIXX12 FireWire" rev 0x00 at pci4 dev 9 function 1 not configured
> "TI PCIXX12 Multimedia Card Reader" rev 0x00 at pci4 dev 9 function 2 not
> configured
> cardslot0 at cbb0 slot 0 flags 0
> pcmcia0 at cardslot0
> ichpcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x02: PM
> disabled
> pciide0 at pci0 dev 31 function 1 "Intel 82801GB IDE" rev 0x02: 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:  ATAPI
> 5/cdrom removable
> cd0(pciide0:0:0): using PIO mode 

Re: Crash during boot. Fresh install of 4.7

[Todd]

On Mon, May 17, 2010 at 9:58 PM, Marco Peereboom  wrote:

> hrm,... i might have fixed that in -current.
> got a dmesg?
>
I installed  the snapshot from 5-13 and there is still a crash with the same
error.  Below is everything that is still on the screen when the crash
occurs and a dmesg from booting bsd.rd

acpibat1 art acpi0: BAT2 not present
acpibtn2 at acpi0: LID_
acpidock0 at acpi0:DCK1 not docked(0)
acpivideo0 at acpi0: VGA_
acpivout0 at acpivideo0: CRT_
acpivout1 at acpivideo0: TV0_
acpivout2 at acpivideo0: LCD_
acpivideo1 at acpi0: GFX0
acpivout3 at acpivideo1: DD01
acpivout4 at acpivideo1: DD02
acpivout5 at acpivideo1: DD03
acpivout6 at acpivideo1: DD04
acpivout7 at acpivideo1: DD05
bios0: ROM list: 0xc/0xfa00 0xdf000/0x800!
cpu0: Enhanced SpeedStep 1664 MHzKernel: interger devide fault trap, code=0
Stopped at est_init+0x107: idivl %esi %eax
est_init(d0992174,0,0,d04f6235) at est_init+0x107
intel686_setperf_setup(d0992160,d0a43e98,d0a43ec8,d04f627d at
intel686_setperf_setup+0x46
mainbus_attach(0,d1c48c0,0,dbdef000,d0a42334) at mainbus_attach+0x236
config_attach(0,d08686d4,0,0,0) at config_attach+0xfd
config_rootfound(d0785242,0,d0a43f38,d04c37fe) at config_rootfound+0x27
main(0,0,0,0,0) at main+0x3b2


below is the dmesg from booting bsd.rd installed from the 4.7 release cd

OpenBSD 4.7 (RAMDISK_CD) #353: Wed Mar 17 21:02:53 MDT 2010
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: Genuine Intel(R) CPU T2300 @ 1.66GHz ("GenuineIntel" 686-class) 1.67
GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,VMX,EST,TM2,xTPR
real mem  = 1071738880 (1022MB)
avail mem = 1031536640 (983MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 01/13/06, BIOS32 rev. 0 @ 0xfd620,
SMBIOS rev. 2.31 @ 0xdf010 (24 entries)
bios0: vendor Gateway version "71.02" date 01/13/2006992
bios0: Gateway MX6710
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP APIC ASF! MCFG APIC BOOT SSDT
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 166MHz
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 2, remapped to apid 1
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PEGP)
acpiprt2 at acpi0: bus 2 (RP01)
acpiprt3 at acpi0: bus 3 (RP02)
acpiprt4 at acpi0: bus -1 (RP03)
acpiprt5 at acpi0: bus 4 (PCIB)
bios0: ROM list: 0xc/0xfa00 0xdf000/0x800!
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82945GM PCIE" rev 0x03: apic 1 int 16
(irq 11)
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "ATI Radeon Mobility X1400" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
"Intel 82801GB HD Audio" rev 0x02 at pci0 dev 27 function 0 not configured
ppb1 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: apic 1 int 17
(irq 11)
pci2 at ppb1 bus 2
em0 at pci2 dev 0 function 0 "Intel PRO/1000MT (82573L)" rev 0x00: apic 1
int 16 (irq 11), address 00:e0:b8:94:d6:8a
ppb2 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: apic 1 int 16
(irq 11)
pci3 at ppb2 bus 3
wpi0 at pci3 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02: apic 1
int 17 (irq 11), MoW1, address 00:13:02:04:21:f8
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 1 int 23
(irq 11)
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 1 int 19
(irq 10)
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 1 int 18
(irq 10)
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 1 int 16
(irq 11)
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic 1 int 23
(irq 11)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb3 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2
pci4 at ppb3 bus 4
cbb0 at pci4 dev 9 function 0 "TI PCIXX12 CardBus" rev 0x00: apic 1 int 17
(irq 255), CardBus support disabled
"TI PCIXX12 FireWire" rev 0x00 at pci4 dev 9 function 1 not configured
"TI PCIXX12 Multimedia Card Reader" rev 0x00 at pci4 dev 9 function 2 not
configured
cardslot0 at cbb0 slot 0 flags 0
pcmcia0 at cardslot0
ichpcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x02: PM
disabled
pciide0 at pci0 dev 31 function 1 "Intel 82801GB IDE" rev 0x02: 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:  ATAPI
5/cdrom removable
cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 ignored (disabled)
ahci0 at pci0 dev 31 function 2 "Intel 82801GBM AHCI" rev 0x02: apic 1 int
19 (irq 10), AHCI 1.1
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0:  SCSI3 0/direct
fixed
sd0: 95396MB, 512 bytes/sec, 195371568 sec total
"Intel 828

Re: Crash during boot. Fresh install of 4.7

[Marco Peereboom]

hrm,... i might have fixed that in -current.
got a dmesg?

On Fri, May 14, 2010 at 08:55:38PM -0500, Todd wrote:
> I ordered the 4.7 cd and have successfully installed it on 2 machines, but
> the third is giving me some trouble.  The install went OK, but after reboot,
> there was a crash.  I took pictures of the screen and typed what I think is
> most important below.  I get the same message if I type trace at the ddb
> prompt.
> 
> I though I may have forgotten to flag the partition as active, so I rebooted
> the install cd and verified that it was active.  If it matters, OpenBSD is
> installed on the 4th primary partition.
> 
> I'm still fairly new to OpenBSD and am not sure if there is really something
> wrong, of if I have done something dumb.
> 
> 
> 
> Stopped at est_init+0x017: idivl %esi %eax
> est_init(d0992174,0,0,d04f6235) at est_init+0x107
> intel686_setperf_setup(d0992160,d0a43e98,d0a43ec8,d04f627d at
> intel686_setperf_setup+0x46
> mainbus_attach(0,d1c48c0,0,dbdef000,d0a42334) at mainbus_attach+0x236
> config_attach(0,d08686d4,0,0,0) at config_attach+0xfd
> config_rootfound(d0785242,0,d0a43f38,d04c37fe) at config_rootfound+0x27
> main(0,0,0,0,0) at main+0x3b2
> 
> 
> show panic
> the kernel did not panic

Re: Crash during boot. Fresh install of 4.7

[Ted Unangst]

It really helps if you provide more of the output, like everything the
kernel printed up to the point of the crash.  If your disassembly is
accurate, it looks like a divide by zero because high and low have the
same value near the end of est_init.

You can probably work around this by booting with -d, then writing
some big number like 1000 to setperf_prio.  Then build a kernel that
prints out a few of the relevant values near there (est_fqlist->n,
cpuspeed, high, low before doing the divide).  And send a complete
dmesg.

On Mon, May 17, 2010 at 9:04 PM, Todd  wrote:
> On Fri, May 14, 2010 at 8:55 PM, Todd  wrote:
>
>> I ordered the 4.7 cd and have successfully installed it on 2 machines, but
>> the third is giving me some trouble.  The install went OK, but after
reboot,
>> there was a crash.  I took pictures of the screen and typed what I think
is
>> most important below.  I get the same message if I type trace at the ddb
>> prompt.
>>
>> I though I may have forgotten to flag the partition as active, so I
>> rebooted the install cd and verified that it was active.  If it matters,
>> OpenBSD is installed on the 4th primary partition.
>>
>> I'm still fairly new to OpenBSD and am not sure if there is really
>> something wrong, of if I have done something dumb.
>>
>>
>>
>> Stopped at est_init+0x017: idivl %esi %eax
>> est_init(d0992174,0,0,d04f6235) at est_init+0x107
>> intel686_setperf_setup(d0992160,d0a43e98,d0a43ec8,d04f627d at
>> intel686_setperf_setup+0x46
>> mainbus_attach(0,d1c48c0,0,dbdef000,d0a42334) at mainbus_attach+0x236
>> config_attach(0,d08686d4,0,0,0) at config_attach+0xfd
>> config_rootfound(d0785242,0,d0a43f38,d04c37fe) at config_rootfound+0x27
>> main(0,0,0,0,0) at main+0x3b2
>>
>>
>> show panic
>> the kernel did not panic
>>
>
>
> I am trying to follow the debug instructions from the faq.  I built the
> kernel and ran the following:
>
> #objdump --line --disassemble --reloc est.o >est.dis
> # grep ":" est.dis
> 01e4 :
>
> so,  0x1e4 + 0x017 = 0x1FB
>
> here is part of est.dis, but there is no line 0x1FB, and realized I made a
> typo.  The stop was at 0x107, not 0x017.  so then 0x1e4 + 0x107 = 0x2EB  I
> think this is the applicable section of est.dis, but it is not clear to me
> whick line of the est.c is cousing the trouble.
>
> 2d3: R_386_32 cpuspeed
>  2d7: 29 c8 sub%ecx,%eax
>  2d9: 8d 04 80 lea(%eax,%eax,4),%eax
>  2dc: 0f b7 52 02   movzwl 0x2(%edx),%edx
>  2e0: 8d 04 80 lea(%eax,%eax,4),%eax
>  2e3: 29 ca sub%ecx,%edx
>  2e5: c1 e0 02 shl$0x2,%eax
>  2e8: 89 d6 mov%edx,%esi
>  2ea: 99   cltd
>  2eb: f7 fe idiv   %esi
>  2ed: a3 00 00 00 00   mov%eax,0x0
> 2ee: R_386_32 perflevel
>  2f2: c7 04 24 1e 00 00 00 movl   $0x1e,(%esp)
> 2f5: R_386_32 .rodata.str1.1
>  2f9: e8 fc ff ff ff   call   2fa 
> 2fa: R_386_PC32 printf
>  2fe: a1 00 00 00 00   mov0x0,%eax

Re: Crash during boot. Fresh install of 4.7

[Todd]

On Fri, May 14, 2010 at 8:55 PM, Todd  wrote:

> I ordered the 4.7 cd and have successfully installed it on 2 machines, but
> the third is giving me some trouble.  The install went OK, but after reboot,
> there was a crash.  I took pictures of the screen and typed what I think is
> most important below.  I get the same message if I type trace at the ddb
> prompt.
>
> I though I may have forgotten to flag the partition as active, so I
> rebooted the install cd and verified that it was active.  If it matters,
> OpenBSD is installed on the 4th primary partition.
>
> I'm still fairly new to OpenBSD and am not sure if there is really
> something wrong, of if I have done something dumb.
>
>
>
> Stopped at est_init+0x017: idivl %esi %eax
> est_init(d0992174,0,0,d04f6235) at est_init+0x107
> intel686_setperf_setup(d0992160,d0a43e98,d0a43ec8,d04f627d at
> intel686_setperf_setup+0x46
> mainbus_attach(0,d1c48c0,0,dbdef000,d0a42334) at mainbus_attach+0x236
> config_attach(0,d08686d4,0,0,0) at config_attach+0xfd
> config_rootfound(d0785242,0,d0a43f38,d04c37fe) at config_rootfound+0x27
> main(0,0,0,0,0) at main+0x3b2
>
>
> show panic
> the kernel did not panic
>


I am trying to follow the debug instructions from the faq.  I built the
kernel and ran the following:

#objdump --line --disassemble --reloc est.o >est.dis
# grep ":" est.dis
01e4 :

so,  0x1e4 + 0x017 = 0x1FB

here is part of est.dis, but there is no line 0x1FB, and realized I made a
typo.  The stop was at 0x107, not 0x017.  so then 0x1e4 + 0x107 = 0x2EB  I
think this is the applicable section of est.dis, but it is not clear to me
whick line of the est.c is cousing the trouble.

2d3: R_386_32 cpuspeed
 2d7: 29 c8 sub%ecx,%eax
 2d9: 8d 04 80 lea(%eax,%eax,4),%eax
 2dc: 0f b7 52 02   movzwl 0x2(%edx),%edx
 2e0: 8d 04 80 lea(%eax,%eax,4),%eax
 2e3: 29 ca sub%ecx,%edx
 2e5: c1 e0 02 shl$0x2,%eax
 2e8: 89 d6 mov%edx,%esi
 2ea: 99   cltd
 2eb: f7 fe idiv   %esi
 2ed: a3 00 00 00 00   mov%eax,0x0
2ee: R_386_32 perflevel
 2f2: c7 04 24 1e 00 00 00 movl   $0x1e,(%esp)
2f5: R_386_32 .rodata.str1.1
 2f9: e8 fc ff ff ff   call   2fa 
2fa: R_386_PC32 printf
 2fe: a1 00 00 00 00   mov0x0,%eax

Re: Crash during boot. Fresh install of 4.7

[Robert]

On Fri, 14 May 2010 20:55:38 -0500
Todd  wrote:

> Stopped at est_init+0x017: idivl %esi %eax
> est_init(d0992174,0,0,d04f6235) at est_init+0x107
> intel686_setperf_setup(d0992160,d0a43e98,d0a43ec8,d04f627d at
> intel686_setperf_setup+0x46
> mainbus_attach(0,d1c48c0,0,dbdef000,d0a42334) at mainbus_attach+0x236
> config_attach(0,d08686d4,0,0,0) at config_attach+0xfd
> config_rootfound(d0785242,0,d0a43f38,d04c37fe) at
> config_rootfound+0x27 main(0,0,0,0,0) at main+0x3b2


Looks like some problem with ACPI.
Those that might have a clue need to see a dmesg of that system and
acpidump output.

Crash during boot. Fresh install of 4.7

[Todd]

I ordered the 4.7 cd and have successfully installed it on 2 machines, but
the third is giving me some trouble.  The install went OK, but after reboot,
there was a crash.  I took pictures of the screen and typed what I think is
most important below.  I get the same message if I type trace at the ddb
prompt.

I though I may have forgotten to flag the partition as active, so I rebooted
the install cd and verified that it was active.  If it matters, OpenBSD is
installed on the 4th primary partition.

I'm still fairly new to OpenBSD and am not sure if there is really something
wrong, of if I have done something dumb.



Stopped at est_init+0x017: idivl %esi %eax
est_init(d0992174,0,0,d04f6235) at est_init+0x107
intel686_setperf_setup(d0992160,d0a43e98,d0a43ec8,d04f627d at
intel686_setperf_setup+0x46
mainbus_attach(0,d1c48c0,0,dbdef000,d0a42334) at mainbus_attach+0x236
config_attach(0,d08686d4,0,0,0) at config_attach+0xfd
config_rootfound(d0785242,0,d0a43f38,d04c37fe) at config_rootfound+0x27
main(0,0,0,0,0) at main+0x3b2


show panic
the kernel did not panic

Re: after a fresh install

[Tudod Ki]

sorry
PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/4.6/packages/amd64/
installed from this:ftp://ftp.openbsd.org/pub/OpenBSD/4.6/amd64/install46.iso
--- On Sun, 12/13/09, patrick keshishian  wrote:

From: patrick keshishian 
Subject: Re: after a fresh install
To: "Tudod Ki" 
Cc: "openbsd misc" 
Date: Sunday, December 13, 2009, 4:09 AM

On Sat, Dec 12, 2009 at 7:43 PM, Tudod Ki  wrote:
> I wanted to install mc.
pkg_add mcCan't find unzip-5.52p0/usr/sbin/pkg_add: unzip-5.52p0:Fatal error
> Ok, then how could I install "unzip"?

fresh install of what? 4.6? snapshot? Which architecture? Where is
your PKG_PATH pointing to?

Re: after a fresh install

[patrick keshishian]

On Sat, Dec 12, 2009 at 7:43 PM, Tudod Ki  wrote:
> I wanted to install mc.pkg_add mcCan't find unzip-5.52p0/usr/sbin/pkg_add: 
> unzip-5.52p0:Fatal error
> Ok, then how could I install "unzip"?

fresh install of what? 4.6? snapshot? Which architecture? Where is
your PKG_PATH pointing to?

after a fresh install

[Tudod Ki]

I wanted to install mc.pkg_add mcCan't find unzip-5.52p0/usr/sbin/pkg_add: 
unzip-5.52p0:Fatal error
Ok, then how could I install "unzip"?

Re: boot halts halfway after fresh install, bsd.rd boots fine...

[Jasper Bal]

To finish what i started and for the record.

Owain Ainsworth wrote:
>boot -c
>disable agp
>
>Alternatively, could you try and boot -current on that machine? Quite
>some things have changed in that area.

Installed -current from snapshot. The problem remains, but has a new 
name: intelagp


boot -c works fine. Tested 3 different video cards. They all worked. 
Wich makes me beleave the problem is in the agp bus driver. The machine 
is a HP E60 netserver from 1999. Made the disable permanent with 
config(8). Because it's just an old rusty junkbox for testing I don't 
really mind the agp problem. In case a developer is interested, i've 
included some dmesges:


>> OpenBSD/i386 BOOT 3.02
boot> boot
booting hd0a:/bsd: 6019356+1059784 [52+335888+318217]=0x7601a8
entry point at 0x200120

[ using 654532 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
   The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2009 OpenBSD. All rights reserved.  
http://www.OpenBSD.org


OpenBSD 4.5-beta (GENERIC) #1685: Sun Feb 15 21:05:40 MST 2009
   dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium III ("GenuineIntel" 686-class, 512KB L2 cache) 552 MHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,SER,MMX,FXSR,SSE

real mem  = 133722112 (127MB)
avail mem = 121044992 (115MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 01/14/00, BIOS32 rev. 0 @ 0xfd80c, 
SMBIOS rev. 2.2 @ 0xf0940 (54 entries)

bios0: vendor Phoenix Technologies LTD version "4.06.25 PN" date 01/14/2000
bios0: Hewlett Packard HP NetServer
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP APIC BOOT
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins
cpu0 at mainbus0: apid 1 (boot processor)
cpu0: disabling processor serial number
cpu0: apic clock running at 100MHz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (PCI1)
acpicpu0 at acpi0
bios0: ROM list: 0xc/0x8000 0xc8000/0x5800 0xcd800/0x800
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
intelagp0 at pchb0

>> OpenBSD/i386 BOOT 3.02
boot> boot
booting hd0a:bsd.rd: 5184724+918896 [52+204416+189284]=0x6325d0
entry point at 0x200120

Copyright (c) 1982, 1986, 1989, 1991, 1993
   The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2009 OpenBSD. All rights reserved.  
http://www.OpenBSD.org


OpenBSD 4.5-beta (RAMDISK_CD) #1083: Sun Feb 15 21:21:00 MST 2009
   dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: Intel Pentium III ("GenuineIntel" 686-class, 512KB L2 cache) 552 MHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,SER,MMX,FXSR,SSE

real mem  = 133722112 (127MB)
avail mem = 122679296 (116MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 01/14/00, BIOS32 rev. 0 @ 0xfd80c, 
SMBIOS rev. 2.2 @ 0xf0940 (54 entries)

bios0: vendor Phoenix Technologies LTD version "4.06.25 PN" date 01/14/2000
bios0: Hewlett Packard HP NetServer
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP APIC BOOT
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins
cpu0 at mainbus0: apid 1 (boot processor)
cpu0: disabling processor serial number
cpu0: apic clock running at 100MHz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (PCI1)
bios0: ROM list: 0xc/0x8000 0xc8000/0x5800 0xcd800/0x800
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "ATI Mach64" rev 0x7a
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
pcib0 at pci0 dev 4 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
pciide0 at pci0 dev 4 function 1 "Intel 82371AB IDE" rev 0x01: DMA, 
channel 0 wired to compatibility, channel 1 wired to compatibility

atapiscsi0 at pciide0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0:  ATAPI 5/cdrom 
removable

cd0(pciide0:0:0): using PIO mode 4, DMA mode 2
wd0 at pciide0 channel 1 drive 0: 
wd0: 16-sector PIO, LBA, 114473MB, 234441648 sectors
wd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 4 function 2 "Intel 82371AB USB" rev 0x01: apic 0 int 
19 (irq 11)

"Intel 82371AB Power" rev 0x02 at pci0 dev 4 function 3 not configured
ahc0 at pci0 dev 5 function 0 "Adaptec AIC-7895" rev 0x04: apic 0 int 18 
(irq 10)

ahc0: Host Adapter Bios disabled.  Using default SCSI device parameters
scsibus1 at ahc0: 16 targets, initiator 7
sd0 at scsibus1 targ 0 lun 0:  SCSI2 
0/direct fixed

sd0: 8678MB, 512 bytes/sec, 17773524 sec total
ahc1 at pci0 dev 5 function 1 "Adaptec AIC-7895" rev 0x04: apic 0 int 18 
(irq 10)

ahc1: Host Adapter 

Re: boot halts halfway after fresh install, bsd.rd boots fine...

[Owain Ainsworth]

On Thu, Feb 12, 2009 at 08:56:15PM +0100, Jasper Bal wrote:
> As I was able to pull the dmesg with a serial console and found a floppy  
> after turning upside down the entire office, I now give you, as  
> promised, the dmesg in question. First one is regular boot. It halts at  
> "agp0 at vga1:". I found an old 4x/2x AGP videocard and switched it with  
> the one present. Same difference. I also immediately installed a second  
> copy of 4.4 on the second disk. Again, same difference. bsd.rd boots  
> fine. dmesg included.
>
> Any ideas? Don't know where to start.

boot -c
disable agp

Alternatively, could you try and boot -current on that machine? Quite
some things have changed in that area.

Cheers,

-0-
-- 
Since we have to speak well of the dead, let's knock them while they're
alive.
-- John Sloan

boot halts halfway after fresh install, bsd.rd boots fine...

[Jasper Bal]

As I was able to pull the dmesg with a serial console and found a floppy 
after turning upside down the entire office, I now give you, as 
promised, the dmesg in question. First one is regular boot. It halts at 
"agp0 at vga1:". I found an old 4x/2x AGP videocard and switched it with 
the one present. Same difference. I also immediately installed a second 
copy of 4.4 on the second disk. Again, same difference. bsd.rd boots 
fine. dmesg included.


Any ideas? Don't know where to start.

Kind regards,
Jasper

>> OpenBSD/i386 BOOT 3.02
boot>
booting hd0a:/bsd: 6238560+1041588 [52+319712+302630]=0x7896c4
entry point at 0x200120

[ using 622768 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
  The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2008 OpenBSD. All rights reserved.  
http://www.OpenBSD.org


OpenBSD 4.4 (GENERIC) #1021: Tue Aug 12 17:16:55 MDT 2008
  dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium III ("GenuineIntel" 686-class, 512KB L2 cache) 552 MHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,SER,MMX,FXSR,SSE 


cpu0: disabling processor serial number
real mem  = 133722112 (127MB)
avail mem = 120881152 (115MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 01/14/00, BIOS32 rev. 0 @ 0xfd80c, 
SMBIOS rev. 2.2 @ 0xf0940 (54 entries)

bios0: vendor Phoenix Technologies LTD version "4.06.25 PN" date 01/14/2000
bios0: Hewlett Packard HP NetServer
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP APIC BOOT
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (PCI1)
acpicpu0 at acpi0
bios0: ROM list: 0xc/0x8000 0xc8000/0x5800 0xcd800/0x800
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "ATI Mach64 GZ" rev 0x7a
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
agp0 at vga1:


>> OpenBSD/i386 BOOT 3.02
boot>
boot> AT S7=45 S0=0 L
boot> boot hd0a:/bsd.rd
booting hd0a:/bsd.rd: 5155412+901212 [52+196192+181801]=0x6230e4
entry point at 0x200120

Copyright (c) 1982, 1986, 1989, 1991, 1993
  The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2008 OpenBSD. All rights reserved.  
http://www.OpenBSD.org


OpenBSD 4.4 (RAMDISK_CD) #857: Tue Aug 12 17:31:49 MDT 2008
  dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: Intel Pentium III ("GenuineIntel" 686-class, 512KB L2 cache) 552 MHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,SER,MMX,FXSR,SSE 


cpu0: disabling processor serial number
real mem  = 133722112 (127MB)
avail mem = 122728448 (117MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 01/14/00, BIOS32 rev. 0 @ 0xfd80c, 
SMBIOS rev. 2.2 @ 0xf0940 (54 entries)

bios0: vendor Phoenix Technologies LTD version "4.06.25 PN" date 01/14/2000
bios0: Hewlett Packard HP NetServer
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP APIC BOOT
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (PCI1)
bios0: ROM list: 0xc/0x8000 0xc8000/0x5800 0xcd800/0x800
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "ATI Mach64 GZ" rev 0x7a
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
pcib0 at pci0 dev 4 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
pciide0 at pci0 dev 4 function 1 "Intel 82371AB IDE" rev 0x01: DMA, 
channel 0 wired to compatibility, channel 1 wired to compatibility

atapiscsi0 at pciide0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets, initiator 7
cd0 at scsibus0 targ 0 lun 0:  ATAPI 5/cdrom 
removable

cd0(pciide0:0:0): using PIO mode 4, DMA mode 2
wd0 at pciide0 channel 1 drive 0: 
wd0: 16-sector PIO, LBA, 114473MB, 234441648 sectors
wd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 4 function 2 "Intel 82371AB USB" rev 0x01: irq 11
"Intel 82371AB Power" rev 0x02 at pci0 dev 4 function 3 not configured
ahc0 at pci0 dev 5 function 0 "Adaptec AIC-7895" rev 0x04: irq 10
ahc0: Host Adapter Bios disabled.  Using default SCSI device parameters
scsibus1 at ahc0: 16 targets, initiator 7
sd0 at scsibus1 targ 0 lun 0:  SCSI2 
0/direct fixed

sd0: 8678MB, 11474 cyl, 5 head, 309 sec, 512 bytes/sec, 17773524 sec total
ahc1 at pci0 dev 5 function 1 "Adaptec AIC-7895" rev 0x04: irq 10
ahc1: Host Adapter Bios disabled.  Using default SCSI device parameters
scsibus2 at ahc1: 16 targets, initiator 7
fxp0 at pci0 dev 6 function 0 "Intel 8255x" rev 0x08, i82559: irq 11, 
address 00:e0:18:c3:18:2b

inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4

Re: Fresh install question

[Denny White]

On Mon, Nov 17, 2008 at 01:14:46AM -0600, Denny White spoke thusly:
> I've always tried to do a fresh install any time possible,
> and then copy all my backed up /home and /data stuff back
> to the new installed system. I'm just trying to figure out
> if there's a way to keep those 2 slices intact while wiping
> out and recreating everything else, i.e., /usr, /var, & /tmp.
> I rebooted on the new 4.4 install cd and tried to see if there
> was a different way to go about things but couldn't figure it
> out there. I read up on disklabel & fdisk & googled around for
> a couple of days before asking the list. So, if someone knows
> where I can find some info on it, I'd really appreciate it. 
> 

Replying to myself to say the advice from Nick, Girish, Jorge,
Alexander, and Tom was great. Never went through a smoother
reinstall! All /home and /data intact with no need to work this
aging box any harder than is necessary. Thanks to all and thanks
to Theo and the devs for a great OS! 4.4 is tops, just as expected.

-- 

Denny White

===
GnuPG key  : 0x1644E79A  |  http://wwwkeys.nl.pgp.net
Fingerprint: D0A9 AD44 1F10 E09E 0E67  EC25 CB44 F2E5 1644 E79A
===

Re: Fresh install question

[Denny White]

On Tue, Nov 18, 2008 at 06:58:22AM +0530, Girish Venkatachalam spoke thusly:
> On 15:34:47 Nov 17, Jorge Valbuena wrote:
> > One simple thing that i will try is:
> > 
> > If is already installed OpenBSD 4.2 and  wants to install 4.3 or 4.4 , 
> > first take a look at the /etc/fstab file and write down the name of the 
> > /home partition
> > 
> > /dev/wd0h /home ffs rw,nodev,nosuid 1 2
> > 
> > 
> > When installing the new version leave untouched that partition,  and after 
> > first boot put the line manually in your new /etc/fstab
> > 
> > I hope this can help !
> > 
> 
> It also helps to note down the starting and ending cylinders of the
> partition you want to preserve.
> 
> You can think of the OpenBSD fdisk partition as one big contiguous block
> of sectors. Irrespective of its physical location, it is one single
> unidimensional series of sectors. Each sector is exactly 512 bytes.
> 
> OpenBSD fdisk and disklabel unlike the ones found in other OSes always
> tell us the cylinder boundaries.
> 
> This has helped me think a bit more clearly.
> 
> -Girish
> 

Thanks, Girish. Believe it or not, I actually thought to do that.
I know, miracles never cease. But thanks for reminding me. You
know from off list correspondence about how much my memory banks
will hold (or won't). ;)


-- 

Denny White

===
GnuPG key  : 0x1644E79A  |  http://wwwkeys.nl.pgp.net
Fingerprint: D0A9 AD44 1F10 E09E 0E67  EC25 CB44 F2E5 1644 E79A
===

Re: Fresh install question

[Denny White]

>  Original-Nachricht 
> > Datum: Mon, 17 Nov 2008 01:14:46 -0600
> > Von: Denny White <[EMAIL PROTECTED]>
> > An: OpenBSD Questions 
> > Betreff: Fresh install question
> 
> > I've always tried to do a fresh install any time possible,
> > and then copy all my backed up /home and /data stuff back
> > to the new installed system. I'm just trying to figure out
> > if there's a way to keep those 2 slices intact while wiping
> > out and recreating everything else, i.e., /usr, /var, & /tmp.
> > I rebooted on the new 4.4 install cd and tried to see if there
> > was a different way to go about things but couldn't figure it
> > out there. I read up on disklabel & fdisk & googled around for
> > a couple of days before asking the list. So, if someone knows
> > where I can find some info on it, I'd really appreciate it. 
> > 
> > 
> > -- 
> > 
> > Denny White
> 
> -- 
> Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten 
> Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
> 
On Mon, Nov 17, 2008 at 03:34:47PM +0100, Jorge Valbuena spoke thusly:
> One simple thing that i will try is:
> 
> If is already installed OpenBSD 4.2 and  wants to install 4.3 or 4.4 , first 
> take a look at the /etc/fstab file and write down the name of the /home 
> partition
> 
> /dev/wd0h /home ffs rw,nodev,nosuid 1 2
> 
> 
> When installing the new version leave untouched that partition,  and after 
> first boot put the line manually in your new /etc/fstab
> 
> I hope this can help !
> 
> Jorge

Yep, that's been the general consensus in the other replies. Thanks
for the help, Jorge. Along with just having dumped everything and
rsynced my homedir, I also have fstab & quite a few other etc files
saved separately on my 2nd backup drive. Now all I have to do is try
to avoid 'fat fingers' as Nick advised. ;)
 
-- 

Denny White

===
GnuPG key  : 0x1644E79A  |  http://wwwkeys.nl.pgp.net
Fingerprint: D0A9 AD44 1F10 E09E 0E67  EC25 CB44 F2E5 1644 E79A
===

Re: Fresh install question

[Denny White]

On Mon, Nov 17, 2008 at 07:04:31AM -0500, Nick Holland spoke thusly:
> Denny White wrote:
> > I've always tried to do a fresh install any time possible,
> > and then copy all my backed up /home and /data stuff back
> > to the new installed system. I'm just trying to figure out
> > if there's a way to keep those 2 slices intact while wiping
> > out and recreating everything else, i.e., /usr, /var, & /tmp.
> > I rebooted on the new 4.4 install cd and tried to see if there
> > was a different way to go about things but couldn't figure it
> > out there. I read up on disklabel & fdisk & googled around for
> > a couple of days before asking the list. So, if someone knows
> > where I can find some info on it, I'd really appreciate it. 
> 
> Just don't define mount points for the partitions you wish to
> keep, and they won't be newfs'd (i.e., existing data will be
> preserved).
> 
> AFTER the install, you will go in and edit /etc/fstab and add
> your "saved" partitions.  Ta-da! your data is back.
> 
> Have a backup anyway, of course.  Sucks to fat-finger something
> in the process...
> 
> Nick.
> 
> 

Thanks, Nick. Yeah, that's what some other replies said. And, like
I said too in my answer, everything's just been dumped & homedir
rsynced, so I'm going to give it a try. And yes, fat fingers suck.
I know from experience. ;) Thanks for the help.

Good case in point. Forgot cc [EMAIL PROTECTED] What a dweeb! ;) Fat fingers
rule!

-- 

Denny White

===
GnuPG key  : 0x1644E79A  |  http://wwwkeys.nl.pgp.net
Fingerprint: D0A9 AD44 1F10 E09E 0E67  EC25 CB44 F2E5 1644 E79A
===

Re: Fresh install question

[Denny White]

On Mon, Nov 17, 2008 at 10:50:13AM +0100, Alexander Hall spoke thusly:
> Denny White wrote:
>> I've always tried to do a fresh install any time possible,
>> and then copy all my backed up /home and /data stuff back
>> to the new installed system. I'm just trying to figure out
>> if there's a way to keep those 2 slices intact while wiping
>> out and recreating everything else, i.e., /usr, /var, & /tmp.
>> I rebooted on the new 4.4 install cd and tried to see if there
>> was a different way to go about things but couldn't figure it
>> out there. I read up on disklabel & fdisk & googled around for
>> a couple of days before asking the list. So, if someone knows
>> where I can find some info on it, I'd really appreciate it. 
>
> Something like replying "no" to "Do you want to use the entire disk for 
> openbsd" could be a good start. I believe that would keep the existing 
> partitions, and you could map them to their respective mount mounts again. 
> I think, however, that you need to _not_ specify mount points for the file 
> systems you want to preserve to prevent them from being newfs'd.
>
> Since I seldom, if ever, do that kind of "fresh reinstalls", you'd better 
> compare the above with install.sh et al. In any way i think it should be 
> possible, but pretty please do make those backups before anyway. :-)
>
> /Alexander

Thanks, Alexander. I'll give it a shot. I just did a dump on everything
to a separate drive. Also rsync my homedir to that drive nightly. Worse
case is, I screw it up & just copy everything back like before. ;)

-- 

Denny White

===
GnuPG key  : 0x1644E79A  |  http://wwwkeys.nl.pgp.net
Fingerprint: D0A9 AD44 1F10 E09E 0E67  EC25 CB44 F2E5 1644 E79A
===

Re: Fresh install question

[Girish Venkatachalam]

On 15:34:47 Nov 17, Jorge Valbuena wrote:
> One simple thing that i will try is:
> 
> If is already installed OpenBSD 4.2 and  wants to install 4.3 or 4.4 , first 
> take a look at the /etc/fstab file and write down the name of the /home 
> partition
> 
> /dev/wd0h /home ffs rw,nodev,nosuid 1 2
> 
> 
> When installing the new version leave untouched that partition,  and after 
> first boot put the line manually in your new /etc/fstab
> 
> I hope this can help !
> 

It also helps to note down the starting and ending cylinders of the
partition you want to preserve.

You can think of the OpenBSD fdisk partition as one big contiguous block
of sectors. Irrespective of its physical location, it is one single
unidimensional series of sectors. Each sector is exactly 512 bytes.

OpenBSD fdisk and disklabel unlike the ones found in other OSes always
tell us the cylinder boundaries.

This has helped me think a bit more clearly.

-Girish

Re: Fresh install question

[Jorge Valbuena]

One simple thing that i will try is:

If is already installed OpenBSD 4.2 and  wants to install 4.3 or 4.4 , first 
take a look at the /etc/fstab file and write down the name of the /home 
partition

/dev/wd0h /home ffs rw,nodev,nosuid 1 2


When installing the new version leave untouched that partition,  and after 
first boot put the line manually in your new /etc/fstab

I hope this can help !

Jorge




 Original-Nachricht 
> Datum: Mon, 17 Nov 2008 01:14:46 -0600
> Von: Denny White <[EMAIL PROTECTED]>
> An: OpenBSD Questions 
> Betreff: Fresh install question

> I've always tried to do a fresh install any time possible,
> and then copy all my backed up /home and /data stuff back
> to the new installed system. I'm just trying to figure out
> if there's a way to keep those 2 slices intact while wiping
> out and recreating everything else, i.e., /usr, /var, & /tmp.
> I rebooted on the new 4.4 install cd and tried to see if there
> was a different way to go about things but couldn't figure it
> out there. I read up on disklabel & fdisk & googled around for
> a couple of days before asking the list. So, if someone knows
> where I can find some info on it, I'd really appreciate it. 
> 
> 
> -- 
> 
> Denny White
> 
> ===
> GnuPG key  : 0x1644E79A  |  http://wwwkeys.nl.pgp.net
> Fingerprint: D0A9 AD44 1F10 E09E 0E67  EC25 CB44 F2E5 1644 E79A
> ===

-- 
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten 
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser