From bsd4me at cableone.net  Tue Nov  2 00:37:02 2010
From: bsd4me at cableone.net (Michael)
Date: Mon, 1 Nov 2010 17:37:02 -0600
Subject: Thank-you devs
Message-ID: <20101101233702.GB31349@getlost.my.domain>


Great job! 
Installed 4.8 over my old 4.6 installation.
Just as easy and smooth as I expected.
Thank-you all for all the hard work you do to provide such a great os.
Hopefully I'll be back to work and able to help financially.


Mike 

From sparctacus at gmail.com  Tue Nov  2 01:14:55 2010
From: sparctacus at gmail.com (Bryan Irvine)
Date: Mon, 1 Nov 2010 17:14:55 -0700
Subject: Thank-you devs
In-Reply-To: <20101101233702.GB31349@getlost.my.domain>
References: <20101101233702.GB31349@getlost.my.domain>
Message-ID: <AANLkTi=VeYqXA=YibtnRa30wJuQ1QNTk-eUniAEmvy6Q@mail.gmail.com>

You might have meant to post this to the misc list.  I'm not aware of
any devs on this list.  :-)



On Mon, Nov 1, 2010 at 4:37 PM, Michael <bsd4me at cableone.net> wrote:
>
> Great job!
> Installed 4.8 over my old 4.6 installation.
> Just as easy and smooth as I expected.
> Thank-you all for all the hard work you do to provide such a great os.
> Hopefully I'll be back to work and able to help financially.
>
>
> Mike
> _______________________________________________
> Openbsd-newbies mailing list
> Openbsd-newbies at sfobug.org
> http://mailman.theapt.org/listinfo/openbsd-newbies
>

From davidianwalker at gmail.com  Tue Nov  2 05:49:09 2010
From: davidianwalker at gmail.com (David Walker)
Date: Tue, 2 Nov 2010 15:19:09 +1030
Subject: Thank-you devs
In-Reply-To: <AANLkTi=VeYqXA=YibtnRa30wJuQ1QNTk-eUniAEmvy6Q@mail.gmail.com>
References: <20101101233702.GB31349@getlost.my.domain>
	<AANLkTi=VeYqXA=YibtnRa30wJuQ1QNTk-eUniAEmvy6Q@mail.gmail.com>
Message-ID: <AANLkTik3H6HH9Y8QsZ6G_jX5BJb=EoFh+FyMf9STOL7z@mail.gmail.com>

On 02/11/2010, Bryan Irvine <sparctacus at gmail.com> wrote:
> You might have meant to post this to the misc list.  I'm not aware of
> any devs on this list.  :-)

Yep misc is better ground for that but I think there's a couple of
lurkers, sthen@ and surely phessler@ is a developer (he posted a day
or so ago) and at least one other.

http://marc.info/?l=openbsd-newbies&m=128847387429611&w=2

Best wishes.

From stu at spacehopper.org  Tue Nov  2 09:40:06 2010
From: stu at spacehopper.org (Stuart Henderson)
Date: Tue, 2 Nov 2010 08:40:06 +0000 (UTC)
Subject: 4.8 torrents
References: <20101030120259.GB22953@getlost.my.domain>
	<20101030211906.GD737@gir.theapt.org>
Message-ID: <slrn3vfsicvjj6.4rc.stu@naiad.spacehopper.org>

On 2010-10-30, Peter Hessler <phessler at openbsd.org> wrote:
> However, there is an 'install48.iso' file that will be uploaded to the
> ftp mirrors for you to fetch.  Pick your favorite (if you avoid
> ftp.openbsd.org and ftp.usa.openbsd.org, you'll get good speeds) and
> download away.

http://spacehopper.org/up2date.html will show you which mirrors
already have 4.8.



From manoel.domingues.junior at gmail.com  Fri Nov  5 12:03:12 2010
From: manoel.domingues.junior at gmail.com (Manoel Domingues Junior)
Date: Fri, 5 Nov 2010 09:03:12 -0200
Subject: Problems with ACPI
Message-ID: <AANLkTi=DpiYr5pUAnyiHxevEMgXZ8zEuOUSeP6dquSxP@mail.gmail.com>

Dear,

Finished my installation of the latest OpenBSD on my laptop.
The installation was uneventful, it was pretty quick, as I expected.

When performing the first boot after installation, my system was stopped,
even loading the kernel, with the phrase:

*acpitz0 at acpi0*

I thought it would take to detect and left for 6 hours.
Nothing happened.

To solve the problem quickly, I disabled ACPI.

Does anyone know another way to solve this problem?


Hugs,
-- 
--
Manoel Domingues Junior
"Collecting data is only the first step toward knowledge but sharing data is
the first step toward civilization."
"Coletar dados ? o primeiro passo para a sabedoria, mas compartilhar dados ?
o primeiro passo para a comunidade."
IBM - Prodigy Linux
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.theapt.org/pipermail/openbsd-newbies/attachments/20101105/7c891582/attachment-0001.htm>

From kousue at gmail.com  Fri Nov  5 16:20:57 2010
From: kousue at gmail.com (Nick Guenther)
Date: Fri, 5 Nov 2010 11:20:57 -0400
Subject: Problems with ACPI
In-Reply-To: <AANLkTi=DpiYr5pUAnyiHxevEMgXZ8zEuOUSeP6dquSxP@mail.gmail.com>
References: <AANLkTi=DpiYr5pUAnyiHxevEMgXZ8zEuOUSeP6dquSxP@mail.gmail.com>
Message-ID: <AANLkTikLGjigSz2bBdQBPJCeuNrJrOd6s3SNfGaWxYJL@mail.gmail.com>

On Fri, Nov 5, 2010 at 7:03 AM, Manoel Domingues Junior
<manoel.domingues.junior at gmail.com> wrote:
> Dear,
>
> Finished my installation of the latest OpenBSD on my laptop.
> The installation was uneventful, it was pretty quick, as I expected.
>
> When performing the first boot after installation, my system was stopped,
> even loading the kernel, with the phrase:
>
> acpitz0 at acpi0
>
> I thought it would take to detect and left for 6 hours.
> Nothing happened.
>
> To solve the problem quickly, I disabled ACPI.
>
> Does anyone know another way to solve this problem?

ACPI is super complex and flakey, what you did is, as far as I'm
aware, the standard answer in such situations. Well, the other answer
is "write the code to fix it yourself and submit a patch" but to us
mere mortals you're probably going to have to make do with ACPI not
working.

From phessler at theapt.org  Fri Nov  5 16:24:52 2010
From: phessler at theapt.org (Peter Hessler)
Date: Fri, 5 Nov 2010 16:24:52 +0100
Subject: Problems with ACPI
In-Reply-To: <AANLkTi=DpiYr5pUAnyiHxevEMgXZ8zEuOUSeP6dquSxP@mail.gmail.com>
References: <AANLkTi=DpiYr5pUAnyiHxevEMgXZ8zEuOUSeP6dquSxP@mail.gmail.com>
Message-ID: <20101105152451.GC9433@gir.theapt.org>

Hi Manoel.

First, try disabling only acpitz.  Secondly, can you try the most recent
snapshot, to see if it has been fixed since then?

If it isn't fixed with the most recent snapshot, please send a report
using sendbug(1).  This will include all of the details an ACPI
developer will need to investigate the problem more deeply (specifically,
full dmesg and acpidump).

Thanks!


On 2010 Nov 05 (Fri) at 09:03:12 -0200 (-0200), Manoel Domingues Junior wrote:
:Dear,
:
:Finished my installation of the latest OpenBSD on my laptop.
:The installation was uneventful, it was pretty quick, as I expected.
:
:When performing the first boot after installation, my system was stopped,
:even loading the kernel, with the phrase:
:
:*acpitz0 at acpi0*
:
:I thought it would take to detect and left for 6 hours.
:Nothing happened.
:
:To solve the problem quickly, I disabled ACPI.
:
:Does anyone know another way to solve this problem?
:
:
:Hugs,
:-- 
:--
:Manoel Domingues Junior
:"Collecting data is only the first step toward knowledge but sharing data is
:the first step toward civilization."
:"Coletar dados ? o primeiro passo para a sabedoria, mas compartilhar dados ?
:o primeiro passo para a comunidade."
:IBM - Prodigy Linux

:_______________________________________________
:Openbsd-newbies mailing list
:Openbsd-newbies at sfobug.org
:http://mailman.theapt.org/listinfo/openbsd-newbies


-- 
"I'd love to go out with you, but I'm having all my plants neutered."

From kousue at gmail.com  Sun Nov 14 07:18:45 2010
From: kousue at gmail.com (Nick Guenther)
Date: Sun, 14 Nov 2010 01:18:45 -0500
Subject: 64 or 32 bit?
Message-ID: <AANLkTim8StWRi2JibSMzSXf0EeZ1nbhhvyLaUWKdDBWM@mail.gmail.com>

Okay, stupid question time: how do I figure out if my CPU is 64 or 32
bit on OpenBSD?

dmesg and `sysctl hw` tell me the same thing:
$ sysctl hw
hw.machine=i386
hw.model=Genuine Intel(R) CPU U7300 @ 1.30GHz ("GenuineIntel" 686-class)
...

The googles do nothing for "U7300". I mean, I suppose it probably is
64 bit (Google does find pages selling laptops with this cpu and 4gigs
of ram so presumably..), but what's the process here normally? Try to
install amd64 and if that breaks you know you don't have a 64 bit
machine?

-Nick

From phessler at theapt.org  Sun Nov 14 09:21:12 2010
From: phessler at theapt.org (Peter Hessler)
Date: Sun, 14 Nov 2010 09:21:12 +0100
Subject: 64 or 32 bit?
In-Reply-To: <AANLkTim8StWRi2JibSMzSXf0EeZ1nbhhvyLaUWKdDBWM@mail.gmail.com>
References: <AANLkTim8StWRi2JibSMzSXf0EeZ1nbhhvyLaUWKdDBWM@mail.gmail.com>
Message-ID: <20101114082112.GL30436@gir.theapt.org>

On my amd64 enabled laptop:

	$ sysctl hw.machine
	hw.machine=amd64
	$

You can also check, using file(1), to see what the binaries are compiled
as.  This is reliable since we do not support running 32-bit binaries on
a 64bit kernel.

	$ file /bin/ls
	/bin/ls: ELF 64-bit LSB executable, x86-64, version 1, for OpenBSD, statically linked, stripped
	$


On 2010 Nov 14 (Sun) at 01:18:45 -0500 (-0500), Nick Guenther wrote:
:Okay, stupid question time: how do I figure out if my CPU is 64 or 32
:bit on OpenBSD?
:
:dmesg and `sysctl hw` tell me the same thing:
:$ sysctl hw
:hw.machine=i386
:hw.model=Genuine Intel(R) CPU U7300 @ 1.30GHz ("GenuineIntel" 686-class)
:...
:
:The googles do nothing for "U7300". I mean, I suppose it probably is
:64 bit (Google does find pages selling laptops with this cpu and 4gigs
:of ram so presumably..), but what's the process here normally? Try to
:install amd64 and if that breaks you know you don't have a 64 bit
:machine?
:
:-Nick
:_______________________________________________
:Openbsd-newbies mailing list
:Openbsd-newbies at sfobug.org
:http://mailman.theapt.org/listinfo/openbsd-newbies

-- 
Any father who thinks he's all important should remind himself that
this country honors fathers only one day a year while pickles get a
whole week.

From stu at spacehopper.org  Sun Nov 14 16:01:00 2010
From: stu at spacehopper.org (Stuart Henderson)
Date: Sun, 14 Nov 2010 15:01:00 +0000 (UTC)
Subject: 64 or 32 bit?
References: <AANLkTim8StWRi2JibSMzSXf0EeZ1nbhhvyLaUWKdDBWM@mail.gmail.com>
Message-ID: <slrn3vfsidvudc.6t.stu@naiad.spacehopper.org>

On 2010-11-14, Nick Guenther <kousue at gmail.com> wrote:
> Okay, stupid question time: how do I figure out if my CPU is 64 or 32
> bit on OpenBSD?
>
> dmesg and `sysctl hw` tell me the same thing:
> $ sysctl hw
> hw.machine=i386
> hw.model=Genuine Intel(R) CPU U7300 @ 1.30GHz ("GenuineIntel" 686-class)
> ...
>
> The googles do nothing for "U7300". I mean, I suppose it probably is
> 64 bit (Google does find pages selling laptops with this cpu and 4gigs
> of ram so presumably..), but what's the process here normally? Try to
> install amd64 and if that breaks you know you don't have a 64 bit
> machine?

basically, yes.

there is a way to test for 64-bit mode via cpuid flags, we test it
in amd64 kernels (the flag LONG is printed in the cpu attach line there)
but I suspect the flag holding it has different meanings depending
on the type of cpu, so it's probably not a good idea to do the same
thing in an i386 kernel which could be run on many more types of
unusual cpu.



From phessler at theapt.org  Sun Nov 14 16:13:37 2010
From: phessler at theapt.org (Peter Hessler)
Date: Sun, 14 Nov 2010 16:13:37 +0100
Subject: 64 or 32 bit?
In-Reply-To: <slrn3vfsidvudc.6t.stu@naiad.spacehopper.org>
References: <AANLkTim8StWRi2JibSMzSXf0EeZ1nbhhvyLaUWKdDBWM@mail.gmail.com>
	<slrn3vfsidvudc.6t.stu@naiad.spacehopper.org>
Message-ID: <20101114151336.GM30436@gir.theapt.org>

On 2010 Nov 14 (Sun) at 15:01:00 +0000 (+0000), Stuart Henderson wrote:
:On 2010-11-14, Nick Guenther <kousue at gmail.com> wrote:
:> Okay, stupid question time: how do I figure out if my CPU is 64 or 32
:> bit on OpenBSD?
:>
:> dmesg and `sysctl hw` tell me the same thing:
:> $ sysctl hw
:> hw.machine=i386
:> hw.model=Genuine Intel(R) CPU U7300 @ 1.30GHz ("GenuineIntel" 686-class)
:> ...
:>
:> The googles do nothing for "U7300". I mean, I suppose it probably is
:> 64 bit (Google does find pages selling laptops with this cpu and 4gigs
:> of ram so presumably..), but what's the process here normally? Try to
:> install amd64 and if that breaks you know you don't have a 64 bit
:> machine?
:
:basically, yes.
:
:there is a way to test for 64-bit mode via cpuid flags, we test it
:in amd64 kernels (the flag LONG is printed in the cpu attach line there)
:but I suspect the flag holding it has different meanings depending
:on the type of cpu, so it's probably not a good idea to do the same
:thing in an i386 kernel which could be run on many more types of
:unusual cpu.
:

If the cpu supports it, LONG is always printed in the CPU flags for both
i386 and amd64 kernels these days.  The other thing the OP can try, is
just booting an amd64 bsd.rd kernel, and see if it boots. It fails
extremely early on i386 only systems. 


-- 
Miss, n.:
	A title with which we brand unmarried women to indicate that
	they are in the market.
		-- Ambrose Bierce, "The Devil's Dictionary"