From henders254 at gmail.com  Thu Feb  4 13:01:04 2010
From: henders254 at gmail.com (Chris Henderson)
Date: Thu, 4 Feb 2010 23:01:04 +1100
Subject: pkg_add and regex
Message-ID: <d4ee74cf1002040401h4446bf2fwbacc4ca44f3877de@mail.gmail.com>

I been trying to install firefox and seems like regex doesn't work
with pkg_add when I look for the package; pkg_add -iv firefox or
pkg_add -iv "*firefox*" doesn't install anything.

I have to ftp to the package directory and find out the exact name of
the firefox package and then do pkg_add in order to install it.

Also noticed things are different with mutt. If I do pkg_add -iv mutt,
I get a list to choose from.

Is there any easy way around installing firefox or packages whose
names are not so obvious?

Thanks.

From kousue at gmail.com  Thu Feb  4 14:26:00 2010
From: kousue at gmail.com (Nick Guenther)
Date: Thu, 4 Feb 2010 08:26:00 -0500
Subject: pkg_add and regex
In-Reply-To: <d4ee74cf1002040401h4446bf2fwbacc4ca44f3877de@mail.gmail.com>
References: <d4ee74cf1002040401h4446bf2fwbacc4ca44f3877de@mail.gmail.com>
Message-ID: <98f5a8831002040526u6939068dm68a3fa6bc41aee55@mail.gmail.com>

On Thu, Feb 4, 2010 at 7:01 AM, Chris Henderson <henders254 at gmail.com> wrote:
> I been trying to install firefox and seems like regex doesn't work
> with pkg_add when I look for the package; pkg_add -iv firefox or
> pkg_add -iv "*firefox*" doesn't install anything.
>
> I have to ftp to the package directory and find out the exact name of
> the firefox package and then do pkg_add in order to install it.
>
> Also noticed things are different with mutt. If I do pkg_add -iv mutt,
> I get a list to choose from.
>
> Is there any easy way around installing firefox or packages whose
> names are not so obvious?
>

pkg_add looks for mutt-*.tgz in $PKG_PATH. It's not meant to take a
regex. If you want to explore the available packages use pkg_mgr
(pkg_add -v pkg_mgr), install the ports tree and use "make search
key=" (awkward but works), use http://openports.se or just load up
your mirror in a browser and look.

Firefox is mozilla-firefox, or firefox35 (so firefox doesn't find
anything because firefox-* doesn't exist, only firefox35-*).

-Nick

From bsd4me at cableone.net  Thu Feb  4 14:39:35 2010
From: bsd4me at cableone.net (Michael)
Date: Thu, 4 Feb 2010 06:39:35 -0700
Subject: pkg_add and regex
In-Reply-To: <d4ee74cf1002040401h4446bf2fwbacc4ca44f3877de@mail.gmail.com>
References: <d4ee74cf1002040401h4446bf2fwbacc4ca44f3877de@mail.gmail.com>
Message-ID: <20100204133935.GA4190@debian.my.domain>

On Thu, Feb 04, 2010 at 11:01:04PM +1100, Chris Henderson wrote:
> I been trying to install firefox and seems like regex doesn't work
> with pkg_add when I look for the package; pkg_add -iv firefox or
> pkg_add -iv "*firefox*" doesn't install anything.
> 
> I have to ftp to the package directory and find out the exact name of
> the firefox package and then do pkg_add in order to install it.
> 
> Also noticed things are different with mutt. If I do pkg_add -iv mutt,
> I get a list to choose from.
> 
> Is there any easy way around installing firefox or packages whose
> names are not so obvious?
> 
> Thanks.

I download the index.txt file, grep the file I'm looking for,  then copy and paste into my pkg_add command.
I have to be on an linux box right now, so can't show the grep command and response :(

Mike

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

From brakeb at gmail.com  Tue Feb  9 07:25:03 2010
From: brakeb at gmail.com (Bryan)
Date: Tue, 9 Feb 2010 00:25:03 -0600
Subject: Pulling xenocara takes longer and longer
Message-ID: <6532b7c81002082225s5a2b5e89i5e9c548b6cde302a@mail.gmail.com>

Can anyone tell me why it takes longer and longer to pull source.
It's getting to the point that it is faster for me to "rm -rf" my
/usr/xenocara, and do an entire pull of the directory.  /usr/src pulls
way faster, as well as /usr/ports, but I can spend 30 minutes pulling
/usr/xenocara from the same mirror that I pulled src and ports from.
I understand that there might be more files, but 30 minutes?

Is there anyway, other than a complete pull everytime, to speed things
up?  is there some housekeeping I can do on my end to speed things up?

Thanks
Bryan

From sparctacus at gmail.com  Tue Feb  9 07:43:19 2010
From: sparctacus at gmail.com (Bryan Irvine)
Date: Mon, 8 Feb 2010 22:43:19 -0800
Subject: Pulling xenocara takes longer and longer
In-Reply-To: <6532b7c81002082225s5a2b5e89i5e9c548b6cde302a@mail.gmail.com>
References: <6532b7c81002082225s5a2b5e89i5e9c548b6cde302a@mail.gmail.com>
Message-ID: <53d706301002082243r5794014cja8c75fcaa7f0405b@mail.gmail.com>

make clean beforehand?  :-D

On Mon, Feb 8, 2010 at 10:25 PM, Bryan <brakeb at gmail.com> wrote:
> Can anyone tell me why it takes longer and longer to pull source.
> It's getting to the point that it is faster for me to "rm -rf" my
> /usr/xenocara, and do an entire pull of the directory. ?/usr/src pulls
> way faster, as well as /usr/ports, but I can spend 30 minutes pulling
> /usr/xenocara from the same mirror that I pulled src and ports from.
> I understand that there might be more files, but 30 minutes?
>
> Is there anyway, other than a complete pull everytime, to speed things
> up? ?is there some housekeeping I can do on my end to speed things up?
>
> Thanks
> Bryan
> _______________________________________________
> Openbsd-newbies mailing list
> Openbsd-newbies at sfobug.org
> http://mailman.theapt.org/listinfo/openbsd-newbies
>

From lists at rensseltucky.com  Wed Feb 10 18:11:44 2010
From: lists at rensseltucky.com (Ed  D.)
Date: Wed, 10 Feb 2010 12:11:44 -0500
Subject: Ral wireless speed mode options listing gone
Message-ID: <4B72E8D0.3792.3FA9199@lists.rensseltucky.com>

Hi,

      I need to get pointed in the right direction..


       I'm back updating my access point to OpenBSD 4.6.
I'm using the ral based wireless card.

In order to get 54Mbps on my access point, I have
to use

media OFDM54 mode 11g 

in my hostname.ral0 file.

There used to be a listing of all the speed mode settings
in the ral configuration page.

It's now not there anymore.

Where do I find this info now?

I've searched the OpenBSD manual page and can't find it.

Anybody know where it is now?     Thanks,  Ed

From stu at spacehopper.org  Wed Feb 10 21:54:28 2010
From: stu at spacehopper.org (Stuart Henderson)
Date: Wed, 10 Feb 2010 20:54:28 +0000 (UTC)
Subject: Ral wireless speed mode options listing gone
References: <4B72E8D0.3792.3FA9199@lists.rensseltucky.com>
Message-ID: <slrnhn6786.lj4.stu@naiad.spacehopper.org>

On 2010-02-10, Ed  D. <lists at rensseltucky.com> wrote:
> In order to get 54Mbps on my access point, I have
> to use
>
> media OFDM54 mode 11g 
>
> in my hostname.ral0 file.
>
> There used to be a listing of all the speed mode settings
> in the ral configuration page.
>
> It's now not there anymore.
>
> Where do I find this info now?

It's in "ifconfig ral0 media".



From xrayserviceman at yahoo.com  Thu Feb 11 20:10:15 2010
From: xrayserviceman at yahoo.com (bubba)
Date: Thu, 11 Feb 2010 19:10:15 +0000 (UTC)
Subject: embarq (Centurylink) DSL Static IP
References: <4B42154C.18076.7CDE3F@lists.rensseltucky.com>
	<97b0e1031001041751m4e0cfacfp92911f13491539c6@mail.gmail.com>
Message-ID: <Xns9D1C902671970sorryaboutyourluck@80.91.229.13>

Woodchuck <marmot at pennswoods.net> wrote in 
news:97b0e1031001041751m4e0cfacfp92911f13491539c6 at mail.gmail.com:

> On Mon, Jan 4, 2010 at 11:20 AM, Ed  D. <lists at rensseltucky.com> wrote:
>> Hi,
>> ? ? ? I will soon need to get a 2 static IP Embarq/Centurylink DSL
>> account going.
>> The person has a modem/router called a "660" I think may be a
>> Zyxel.
>>
>> I'm going to use an OpenBSD 4.6 system as my router/firewall.
>>
>> I've googled in an attempt to find others using OpenBSD who've
>> had experience with doing this and found nothing useful.
>>
>> I would like to use the 660 in bridge mode and have the
>> OpenBSD 4.6 system handle the logon and connection,
>> like I have my own system on my network.
>>
>> Has anybody done this with Embark/Centurylink?
>> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 
> ? ? ? ? ? ? ?Thanks, ?Ed
> 
> I use embarq with dhcp if that would help.
> 
> Putting the embarq supplied modem in bridge mode was not
> a problem, you use a browser to do this.  (How stupid is that?)
> The embarq modem runs some sort of lame embedded Linux
> (version 1.x.x kernel) and has crude firewall capability (iptables,
> some NAT, very limited by a "friendly" clicky-point interface to
> a braindead wizard... so I went to bridge mode without even bothering
> with that penguin cruft).
> 
> Embarq, here in central-south Pennsylvania is just crappy service.
> My line is down 25-50% of the time, and although I pay for megabit
> I have seldom seen it dload at over maybe 100Kbit, usually more like
> 64Kbit, i.e. just above dialup speed.  I haven't called their
> customer service.  What can they possibly do?
> 
> Anyway, if my dhcp stuff is of any interest, let me know.
> 
> dave
>> Openbsd-newbies mailing list
>> Openbsd-newbies at sfobug.org
>> http://mailman.theapt.org/listinfo/openbsd-newbies
>>
> 
> 
> 
OpenBSD works fine with the 660 DSL setup have many servers on their 
service. I was on Embarq before Centurylink took over and the service has 
gone down hill! I used trafshow(port) and found they are caching the web 
traffic :< (not to say anything about the 404 hijacking)As the other 
person stated you just use the bridge mode. You can either put both ip's 
on your nic or use a switch and put the ip addresses on their own server.
 Hope this helps

DRX


From marmot at pennswoods.net  Mon Feb 15 21:47:29 2010
From: marmot at pennswoods.net (Woodchuck)
Date: Mon, 15 Feb 2010 15:47:29 -0500
Subject: Resuming an interrupted pkg_add
Message-ID: <97b0e1031002151247y6d48ca77y549a0296bb4a42c8@mail.gmail.com>

So, about halfway through pkg_add texlive...  (i.e. hours) the line drops.
(Thank you, embarq).  I am left with a "partial-texlive..." package.

About all I saw on the 'net was to pkg_delete the partial-texlive... thing
then start from scratch.  Now consider that the mean time my dsl line
is up (thank you, embarq) might be less than the time to install the package.
This would imply that it will be very difficult to ever install it.  I would be
better off grabbing source, and building from ports. (getting source can
be resumed if you're clever, using wget -c, manually).  Or I could manually
wget the compiled packages and install from my private ftp site on the lan.

One other webcomment was one of those @#$@# terse, clever tweet-style
snarky unhelps which said

    pkg_add -F conflicts name-of-package

and nothing else.  Will this actually resume installation or will it start from
scratch?

The man page says that it is safe to interrupt a pkg_add with your signal
of choice, but doesn't say what it means by "safe".

So is there a way to actually resume installation of an openbsd package?

I note with some shame that for Fedora and yum, the answer is "yes",
and the method is "just do it".

Thanks,

Dave
-- 
        teh google read my emails 'n' stuff!!!! Lolz!!!

From marmot at pennswoods.net  Tue Feb 16 00:57:36 2010
From: marmot at pennswoods.net (Woodchuck)
Date: Mon, 15 Feb 2010 18:57:36 -0500
Subject: Resuming an interrupted pkg_add
In-Reply-To: <20100215232920.GM78156@twomeeps.com>
References: <97b0e1031002151247y6d48ca77y549a0296bb4a42c8@mail.gmail.com>
	<20100215232920.GM78156@twomeeps.com>
Message-ID: <97b0e1031002151557qf44492aw4168738126e6d865@mail.gmail.com>

On Mon, Feb 15, 2010 at 6:29 PM, Bob Leigh <bobleigh at twomeeps.com> wrote:
>> So, about halfway through pkg_add texlive... ?(i.e. hours) the line drops.
>> (Thank you, embarq). ?I am left with a "partial-texlive..." package.
>
> Is this OpenBSD 4.6? ?On the i386 architecture? ?If so, here's what
> I see in ftp://mirror.planetunix.net/pub/OpenBSD/4.6/packages/i386/
> for package sizes for texlive:
>
> texlive_base-2008p11.tgz ? ? ? ? ?11,621 KB
> texlive_texmf-docs-2008p1.tgz ? ?607,700 KB
> texlive_texmf-full-2008p2.tgz ? ?164,893 KB
> texlive_texmf-minimal-2008p1.tgz 194,909 KB
>
> With files that size, yes, you might be better off doing a wget
> then local install.

Then there are the dependencies, but compared to the actaul
texlive packages, those are small.

What are these 100's of MB?  Fonts, stylesheets, that sort of
thing, mostly, and I believe theyare architecture-independent.  Shame
that the actual binaries aren't in some particular package,
"texlive-arch".

Yeah, the first one was for i386/4.6; tonight we do amd64,
I might have the source for this around here somewhere, I built it
from source under 4.2, I think.  TeX doesn't change too rapidly.

>> One other webcomment was one of those @#$@# terse, clever tweet-style
>> snarky unhelps which said
>>
>> ? ? pkg_add -F conflicts name-of-package
>>
>> and nothing else. ?Will this actually resume installation or will it start from
>
> From the pkg_add man page, '-F' means install ignoring conflicts
> (such as files already installed), so yes, that might be okay.
> Personally, I would do a pkg_delete then a local install, just to
> be even safer.

Bottom line, so far: interrupted pkg_add must be restarted from
scratch.

Note for the archives: if the pkg_add has gotten and installed
dependencies before being interrupted, those don't have to be
redone.

Thanks, Bob.

Dave
--
> Bob Leigh ? ? ? bobleigh at twomeeps.com
>



-- 
teh googlez read my emails 'n' STUFF!!!!  LOLZ!!!

From bobleigh at twomeeps.com  Tue Feb 16 00:29:20 2010
From: bobleigh at twomeeps.com (Bob Leigh)
Date: Mon, 15 Feb 2010 18:29:20 -0500
Subject: Resuming an interrupted pkg_add
In-Reply-To: <97b0e1031002151247y6d48ca77y549a0296bb4a42c8@mail.gmail.com>
References: <97b0e1031002151247y6d48ca77y549a0296bb4a42c8@mail.gmail.com>
Message-ID: <20100215232920.GM78156@twomeeps.com>

> So, about halfway through pkg_add texlive...  (i.e. hours) the line drops.
> (Thank you, embarq).  I am left with a "partial-texlive..." package.

Is this OpenBSD 4.6?  On the i386 architecture?  If so, here's what
I see in ftp://mirror.planetunix.net/pub/OpenBSD/4.6/packages/i386/
for package sizes for texlive:

texlive_base-2008p11.tgz	  11,621 KB
texlive_texmf-docs-2008p1.tgz	 607,700 KB
texlive_texmf-full-2008p2.tgz	 164,893 KB
texlive_texmf-minimal-2008p1.tgz 194,909 KB

With files that size, yes, you might be better off doing a wget
then local install.

> One other webcomment was one of those @#$@# terse, clever tweet-style
> snarky unhelps which said
> 
>     pkg_add -F conflicts name-of-package
> 
> and nothing else.  Will this actually resume installation or will it start from

>From the pkg_add man page, '-F' means install ignoring conflicts
(such as files already installed), so yes, that might be okay.
Personally, I would do a pkg_delete then a local install, just to
be even safer.

-- 
Bob Leigh	bobleigh at twomeeps.com

From stu at spacehopper.org  Tue Feb 16 16:41:10 2010
From: stu at spacehopper.org (Stuart Henderson)
Date: Tue, 16 Feb 2010 15:41:10 +0000 (UTC)
Subject: Resuming an interrupted pkg_add
References: <97b0e1031002151247y6d48ca77y549a0296bb4a42c8@mail.gmail.com>
	<20100215232920.GM78156@twomeeps.com>
	<97b0e1031002151557qf44492aw4168738126e6d865@mail.gmail.com>
Message-ID: <slrnhnlf4o.3hj.stu@naiad.spacehopper.org>

On 2010-02-15, Woodchuck <marmot at pennswoods.net> wrote:
>>
>> Is this OpenBSD 4.6? ?On the i386 architecture? ?If so, here's what
>> I see in ftp://mirror.planetunix.net/pub/OpenBSD/4.6/packages/i386/
>> for package sizes for texlive:
>>
>> texlive_base-2008p11.tgz ? ? ? ? ?11,621 KB
>> texlive_texmf-docs-2008p1.tgz ? ?607,700 KB
>> texlive_texmf-full-2008p2.tgz ? ?164,893 KB
>> texlive_texmf-minimal-2008p1.tgz 194,909 KB
>>
>> With files that size, yes, you might be better off doing a wget
>> then local install.
>
> What are these 100's of MB?  Fonts, stylesheets, that sort of
> thing, mostly, and I believe theyare architecture-independent.  Shame
> that the actual binaries aren't in some particular package,
> "texlive-arch".

They're in texlive_base, the arch-independent parts are in texlive_texmf.
You can install the texmf packages on any arch, just make sure they
match the texlive_base you're using. It's not immediately obvious
from the packages themselves, but you can 'pkg_add -f <pkgname>'
and look at the @arch line, or look for PKG_ARCH=* in the ports
Makefile (e.g. print/texlive/texmf/Makefile).

Note that snapshot package builds aren't synchronized between arch
(it takes some ~= 2 days to build, others ~= 3 months) so you won't
always find a matching set of packages if you do things this way,
but in some cases it can be a big help.



From marmot at pennswoods.net  Tue Feb 16 17:22:48 2010
From: marmot at pennswoods.net (Woodchuck)
Date: Tue, 16 Feb 2010 11:22:48 -0500
Subject: Resuming an interrupted pkg_add
In-Reply-To: <slrnhnlf4o.3hj.stu@naiad.spacehopper.org>
References: <97b0e1031002151247y6d48ca77y549a0296bb4a42c8@mail.gmail.com>
	<20100215232920.GM78156@twomeeps.com>
	<97b0e1031002151557qf44492aw4168738126e6d865@mail.gmail.com>
	<slrnhnlf4o.3hj.stu@naiad.spacehopper.org>
Message-ID: <97b0e1031002160822k51a63698p82fade3fb80039df@mail.gmail.com>

On Tue, Feb 16, 2010 at 10:41 AM, Stuart Henderson <stu at spacehopper.org> wrote:

> They're in texlive_base, the arch-independent parts are in texlive_texmf.
> You can install the texmf packages on any arch, just make sure they
> match the texlive_base you're using. It's not immediately obvious
> from the packages themselves, but you can 'pkg_add -f <pkgname>'
> and look at the @arch line, or look for PKG_ARCH=* in the ports
> Makefile (e.g. print/texlive/texmf/Makefile).

THanks, Stuart.  This is good to know.

> Note that snapshot package builds aren't synchronized between arch
> (it takes some ~= 2 days to build, others ~= 3 months) so you won't

It is easy to believe these times. TeX is what we call a "mature
system".

> always find a matching set of packages if you do things this way,
> but in some cases it can be a big help.

I tend to stay away from snapshots, but this is good to have in the
archives for others.  Keywords:

TeX, LaTeX, texlive, OpenBSD texlive, texlive package, texlive snapshot

Dave
-- 
teh googlez read my emails 'n' STUFF!!!!  LOLZ!!!  Urz 2!!!

From marmot at pennswoods.net  Tue Feb 16 19:17:58 2010
From: marmot at pennswoods.net (Woodchuck)
Date: Tue, 16 Feb 2010 13:17:58 -0500
Subject: Resuming an interrupted pkg_add
In-Reply-To: <slrnhnlf4o.3hj.stu@naiad.spacehopper.org>
References: <97b0e1031002151247y6d48ca77y549a0296bb4a42c8@mail.gmail.com>
	<20100215232920.GM78156@twomeeps.com>
	<97b0e1031002151557qf44492aw4168738126e6d865@mail.gmail.com>
	<slrnhnlf4o.3hj.stu@naiad.spacehopper.org>
Message-ID: <97b0e1031002161017w51d8fabcv23678a549e979a10@mail.gmail.com>

On Tue, Feb 16, 2010 at 10:41 AM, Stuart Henderson <stu at spacehopper.org> wrote:
....
> You can install the texmf packages on any arch, just make sure they
> match the texlive_base you're using. It's not immediately obvious
> from the packages themselves, but you can 'pkg_add -f <pkgname>'
> and look at the @arch line, or look for PKG_ARCH=* in the ports
> Makefile (e.g. print/texlive/texmf/Makefile).

Did you mean pkg_info -f <pkgname> here?  Can't find a -f for
pkg_add.

Dave
-- 
teh googlez read my emails 'n' STUFF!!!!  LOLZ!!! urz 2!!! LOLZ!!!

From stu at spacehopper.org  Wed Feb 17 13:13:06 2010
From: stu at spacehopper.org (Stuart Henderson)
Date: Wed, 17 Feb 2010 12:13:06 +0000 (UTC)
Subject: Resuming an interrupted pkg_add
References: <97b0e1031002151247y6d48ca77y549a0296bb4a42c8@mail.gmail.com>
	<20100215232920.GM78156@twomeeps.com>
	<97b0e1031002151557qf44492aw4168738126e6d865@mail.gmail.com>
	<slrnhnlf4o.3hj.stu@naiad.spacehopper.org>
	<97b0e1031002161017w51d8fabcv23678a549e979a10@mail.gmail.com>
Message-ID: <slrnhnnnak.3hj.stu@naiad.spacehopper.org>

On 2010-02-16, Woodchuck <marmot at pennswoods.net> wrote:
> On Tue, Feb 16, 2010 at 10:41 AM, Stuart Henderson <stu at spacehopper.org> wrote:
> ....
>> You can install the texmf packages on any arch, just make sure they
>> match the texlive_base you're using. It's not immediately obvious
>> from the packages themselves, but you can 'pkg_add -f <pkgname>'
>> and look at the @arch line, or look for PKG_ARCH=* in the ports
>> Makefile (e.g. print/texlive/texmf/Makefile).
>
> Did you mean pkg_info -f <pkgname> here?  Can't find a -f for
> pkg_add.

Oops, yes indeed.


From lists at rensseltucky.com  Thu Feb 18 20:25:16 2010
From: lists at rensseltucky.com (Ed  D.)
Date: Thu, 18 Feb 2010 14:25:16 -0500
Subject: courier-imap: MISSING /etc/courier/authdaemonrc
Message-ID: <4B7D941C.22781.E5546F@lists.rensseltucky.com>

Hi,
       I have an OpenBSD 4.6 i386 system
I installed courier-imap-4.1.1p2.tgz

When I 
# mkdir -p /var/run/courier{,-auth}/
# /usr/local/sbin/authdaemond start

I get:
/usr/local/sbin/authdaemond[16]: .: /etc/courier/authdaemonrc: not 
found

there is no  /etc/courier/authdaemonrc  file.

Does anybody know why this is?

I'm unable to start the authdaemon because of this.

I've googled and not found anybody with this problem.

                   HELP!                 Ed

From sgeorge.ml at gmail.com  Mon Feb 22 10:04:48 2010
From: sgeorge.ml at gmail.com (Siju George)
Date: Mon, 22 Feb 2010 14:34:48 +0530
Subject: PF Log analysys
Message-ID: <b713df2c1002220104v1d50b8ebr75911db8c1227ed1@mail.gmail.com>

Hi,

If I do not set and logging options in 'pf.conf' I guess PF will log
everything to /var/log/pflog and I can see the contents using tcpdump?

Also I have a file named 'pflog.bad.0756960b' in /var/log. What does it contain?

Thanks

--Siju

From vim.unix at googlemail.com  Sun Feb 28 23:25:39 2010
From: vim.unix at googlemail.com (Pau)
Date: Sun, 28 Feb 2010 23:25:39 +0100
Subject: macbook pro 13"
In-Reply-To: <30c383e71002281356y63beefaw6dd2fa13436ce3d3@mail.gmail.com>
References: <30c383e70911281215p302d949bobb8cf981f5c58872@mail.gmail.com>
	<98f5a8830911291422i7096d5ew82563658fb94b442@mail.gmail.com>
	<30c383e70911300452g14125588ocf9534b2b44d29d4@mail.gmail.com>
	<30c383e71002281343q13ca6b93ne3718f54e19bc05e@mail.gmail.com>
	<30c383e71002281356y63beefaw6dd2fa13436ce3d3@mail.gmail.com>
Message-ID: <30c383e71002281425l6d6ec94bhde742c83a90c10e9@mail.gmail.com>

Hello,

I figured out... with refit I can now boot into OpenBSD...
unfortunately X does not work :(

Too bad... I tried to run it on the fly, without xorg.conf and with X
-configure... the log follows

I guess the answer is: you will have to wait

Pau

(--) checkDevMem: using aperture driver /dev/xf86
(--) Using wscons driver on /dev/ttyC4 in pcvt compatibility mode (version 3.32)

X.Org X Server 1.6.5
Release Date: 2009-10-11
X Protocol Version 11, Revision 0
Build Operating System: OpenBSD 4.7 i386
Current Operating System: OpenBSD machorl.fritz.box 4.7 GENERIC.MP#424 i386
Build Date: 21 February 2010  06:12:32PM

	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Feb 28 23:18:22 2010
(II) Loader magic: 0x1dc0
(II) Module ABI versions:
	X.Org ANSI C Emulation: 0.4
	X.Org Video Driver: 5.0
	X.Org XInput driver : 4.0
	X.Org Server Extension : 2.0
(II) Loader running on openbsd
(--) PCI: (0:0:3:5) 10de:0aa3:10de:cb79 NVIDIA MCP79 Co-processor rev
177, Mem @ 0x00000000/524288
(--) PCI:*(0:2:0:0) 10de:0863:106b:00b9 NVIDIA GeForce 9400m rev 177,
Mem @ 0xd2000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432,
I/O @ 0x00001000/128, BIOS @ 0x????????/131072
(==) Using default built-in configuration (21 lines)
(==) --- Start of built-in configuration ---
	Section "Device"
		Identifier	"Builtin Default nv Device 0"
		Driver	"nv"
	EndSection
	Section "Screen"
		Identifier	"Builtin Default nv Screen 0"
		Device	"Builtin Default nv Device 0"
	EndSection
	Section "Device"
		Identifier	"Builtin Default vesa Device 0"
		Driver	"vesa"
	EndSection
	Section "Screen"
		Identifier	"Builtin Default vesa Screen 0"
		Device	"Builtin Default vesa Device 0"
	EndSection
	Section "ServerLayout"
		Identifier	"Builtin Default Layout"
		Screen	"Builtin Default nv Screen 0"
		Screen	"Builtin Default vesa Screen 0"
	EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default nv Screen 0" (0)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default nv Device 0"
(==) No monitor specified for screen "Builtin Default nv Screen 0".
	Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (1)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
	Using a default monitor configuration.
(==) Not automatically adding devices
(==) Not automatically enabling devices
(==) FontPath set to:
	/usr/X11R6/lib/X11/fonts/misc/,
	/usr/X11R6/lib/X11/fonts/TTF/,
	/usr/X11R6/lib/X11/fonts/OTF,
	/usr/X11R6/lib/X11/fonts/Type1/,
	/usr/X11R6/lib/X11/fonts/100dpi/,
	/usr/X11R6/lib/X11/fonts/75dpi/
(==) ModulePath set to "/usr/X11R6/lib/modules"
(==) |-->Input Device "<default pointer>"
(==) |-->Input Device "<default keyboard>"
(==) The core pointer device wasn't specified explicitly in the layout.
	Using the default mouse configuration.
(==) The core keyboard device wasn't specified explicitly in the layout.
	Using the default keyboard configuration.
(II) System resource ranges:
	[0] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[1] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[2] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[3] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[4] -1	0	0x00000000 - 0x000000ff (0x100) IX[B]
(II) LoadModule: "extmod"
(II) Loading /usr/X11R6/lib/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
	compiled for 1.6.5, module version = 1.0.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/X11R6/lib/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
	compiled for 1.6.5, module version = 1.0.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/X11R6/lib/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
	compiled for 1.6.5, module version = 1.0.0
	ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/X11R6/lib/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
	compiled for 1.6.5, module version = 1.0.0
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/X11R6/lib/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
	compiled for 1.6.5, module version = 1.1.0
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "nv"
(II) Loading /usr/X11R6/lib/modules/drivers//nv_drv.so
(II) Module nv: vendor="X.Org Foundation"
	compiled for 1.6.5, module version = 2.1.15
	Module class: X.Org Video Driver
	ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "vesa"
(II) Loading /usr/X11R6/lib/modules/drivers//vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
	compiled for 1.6.5, module version = 2.2.1
	Module class: X.Org Video Driver
	ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "mouse"
(II) Loading /usr/X11R6/lib/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
	compiled for 1.6.5, module version = 1.4.0
	Module class: X.Org XInput Driver
	ABI class: X.Org XInput driver, version 4.0
(II) LoadModule: "kbd"
(II) Loading /usr/X11R6/lib/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
	compiled for 1.6.5, module version = 1.3.2
	Module class: X.Org XInput Driver
	ABI class: X.Org XInput driver, version 4.0
(II) NV: driver for NVIDIA chipsets: RIVA 128, RIVA TNT, RIVA TNT2,
	Unknown TNT2, Vanta, RIVA TNT2 Ultra, RIVA TNT2 Model 64,
	Aladdin TNT2, GeForce 256, GeForce DDR, Quadro, GeForce2 MX/MX 400,
	GeForce2 MX 100/200, GeForce2 Go, Quadro2 MXR/EX/Go,
	GeForce2 Integrated GPU, GeForce2 GTS, GeForce2 Ti, GeForce2 Ultra,
	Quadro2 Pro, GeForce4 MX 460, GeForce4 MX 440, GeForce4 MX 420,
	GeForce4 MX 440-SE, GeForce4 440 Go, GeForce4 420 Go,
	GeForce4 420 Go 32M, GeForce4 460 Go, Quadro4 550 XGL,
	GeForce4 440 Go 64M, Quadro NVS, Quadro4 500 GoGL,
	GeForce4 410 Go 16M, GeForce4 MX 440 with AGP8X,
	GeForce4 MX 440SE with AGP8X, GeForce4 MX 420 with AGP8X,
	GeForce4 MX 4000, GeForce4 448 Go, GeForce4 488 Go, Quadro4 580 XGL,
	Quadro4 NVS 280 SD, Quadro4 380 XGL, Quadro NVS 50 PCI,
	GeForce4 448 Go, GeForce4 MX Integrated GPU, GeForce3,
	GeForce3 Ti 200, GeForce3 Ti 500, Quadro DCC, GeForce4 Ti 4600,
	GeForce4 Ti 4400, GeForce4 Ti 4200, Quadro4 900 XGL, Quadro4 750 XGL,
	Quadro4 700 XGL, GeForce4 Ti 4800, GeForce4 Ti 4200 with AGP8X,
	GeForce4 Ti 4800 SE, GeForce4 4200 Go, Quadro4 700 GoGL,
	Quadro4 980 XGL, Quadro4 780 XGL, GeForce FX 5800 Ultra,
	GeForce FX 5800, Quadro FX 2000, Quadro FX 1000,
	GeForce FX 5600 Ultra, GeForce FX 5600, GeForce FX 5600XT,
	GeForce FX Go5600, GeForce FX Go5650, Quadro FX Go700,
	GeForce FX 5200, GeForce FX 5200 Ultra, GeForce FX 5200,
	GeForce FX 5200LE, GeForce FX Go5200, GeForce FX Go5250,
	GeForce FX 5500, GeForce FX 5100, GeForce FX Go5200 32M/64M,
	Quadro NVS 55/280 PCI, Quadro FX 500/600 PCI,
	GeForce FX Go53xx Series, GeForce FX Go5100, GeForce FX 5900 Ultra,
	GeForce FX 5900, GeForce FX 5900XT, GeForce FX 5950 Ultra,
	GeForce FX 5900ZT, Quadro FX 3000, Quadro FX 700,
	GeForce FX 5700 Ultra, GeForce FX 5700, GeForce FX 5700LE,
	GeForce FX 5700VE, GeForce FX Go5700, GeForce FX Go5700,
	Quadro FX Go1000, Quadro FX 1100, GeForce 6800 Ultra, GeForce 6800,
	GeForce 6800 LE, GeForce 6800 XE, GeForce 6800 XT, GeForce 6800 GT,
	GeForce 6800 GT, GeForce 6800 GS, GeForce 6800 XT, Quadro FX 4000,
	GeForce 6800 GS, GeForce 6800, GeForce 6800 LE, GeForce 6800 XT,
	GeForce Go 6800, GeForce Go 6800 Ultra, Quadro FX Go1400,
	Quadro FX 3450/4000 SDI, Quadro FX 1400, GeForce 6600 GT,
	GeForce 6600, GeForce 6600 LE, GeForce 6600 VE, GeForce Go 6600,
	GeForce 6610 XL, GeForce Go 6600 TE/6200 TE, GeForce 6700 XL,
	GeForce Go 6600, GeForce Go 6600 GT, Quadro NVS 440, Quadro FX 550,
	Quadro FX 550, Quadro FX 540, GeForce 6200, GeForce 6500,
	GeForce 6200 TurboCache(TM), GeForce 6200SE TurboCache(TM),
	GeForce 6200 LE, GeForce Go 6200, Quadro NVS 285, GeForce Go 6400,
	GeForce Go 6200, GeForce Go 6400, GeForce 6250, GeForce 7100 GS,
	GeForce 6800, GeForce 6800 LE, GeForce 6800 GT, GeForce 6800 XT,
	GeForce 6200, GeForce 6200 A-LE, GeForce 7800 GTX, GeForce 7800 GTX,
	GeForce 7800 GT, GeForce 7800 GS, GeForce 7800 SLI, GeForce Go 7800,
	GeForce Go 7800 GTX, Quadro FX 4500, GeForce 7350 LE,
	GeForce 7300 LE, GeForce 7300 SE, GeForce Go 7200, GeForce Go 7300,
	GeForce Go 7400, GeForce Go 7400 GS, Quadro NVS 110M,
	Quadro NVS 120M, Quadro FX 350M, GeForce 7500 LE, Quadro FX 350,
	GeForce 7300 GS, GeForce 7650 GS, GeForce 7600 GT, GeForce 7600 GS,
	GeForce 7300 GT, GeForce 7600 LE, GeForce 7300 GT, GeForce Go 7700,
	GeForce Go 7600, GeForce Go 7600 GT, Quadro NVS 300M,
	GeForce Go 7900 SE, Quadro FX 550M, Quadro FX 560, GeForce 7900 GTX,
	GeForce 7900 GT, GeForce 7900 GS, GeForce 7950 GX2, GeForce 7950 GX2,
	GeForce 7950 GT, GeForce Go 7950 GTX, GeForce Go 7900 GS,
	GeForce Go 7900 GTX, Quadro FX 2500M, Quadro FX 1500M,
	Quadro FX 5500, Quadro FX 3500, Quadro FX 1500, Quadro FX 4500 X2,
	GeForce 6150, GeForce 6150 LE, GeForce 6100, GeForce Go 6150,
	Quadro NVS 210S / NVIDIA GeForce 6150LE, GeForce Go 6100,
	GeForce 6150SE, GeForce 6100 nForce 405, GeForce 6100 nForce 400,
	GeForce 6100 nForce 420, GeForce 8800 GTX, GeForce 8800 GTS,
	GeForce 8800 Ultra, Quadro FX 5600, Quadro FX 4600, GeForce 8600 GTS,
	GeForce 8600 GT, GeForce 8600 GT, GeForce 8600 GS, GeForce 8400 GS,
	GeForce 9500M GS, GeForce 8600M GT, GeForce 9650M GS,
	GeForce 8700M GT, Quadro FX 370, Quadro NVS 320M, Quadro FX 570M,
	Quadro FX 1600M, Quadro FX 570, Quadro FX 1700, GeForce 8400 SE,
	GeForce 8500 GT, GeForce 8400 GS, GeForce 8300 GS, GeForce 8400 GS,
	GeForce 8600M GS, GeForce 8400M GT, GeForce 8400M GS,
	GeForce 8400M G, Quadro NVS 140M, Quadro NVS 130M, Quadro NVS 135M,
	GeForce 9400 GT, Quadro FX 360M, GeForce 9300M G, Quadro NVS 290,
	GeForce GTX 280, GeForce GTX 260, GeForce 8800 GTS 512,
	GeForce 8800 GT, GeForce 9800 GX2, GeForce 8800 GS,
	GeForce 8800M GTS, GeForce 8800M GTX, GeForce 8800 GS,
	GeForce 9600 GSO, GeForce 8800 GT, GeForce 9800 GTX,
	GeForce 9800 GTK+, GeForce 9800 GT, Quadro FX 3700, Quadro FX 3600M,
	GeForce 9600 GT, GeForce 9600 GS, GeForce 9800M GTS,
	GeForce 9700M GTS, GeForce 9800M GTS, GeForce 9500 GT,
	GeForce 9600M GT, GeForce 9600M GS, GeForce 9600M GT,
	GeForce 9500M G, GeForce 9300 GE, GeForce 9300 GS, GeForce 8400 GS,
	GeForce 9300M GS, GeForce 9200M GS, GeForce 9300M GS,
	Quadro NVS 150M, Quadro NVS 160M, GeForce 9300 GE
(II) VESA: driver for VESA chipsets: vesa
(II) Primary Device is: PCI 02 at 00:00:0
(WW) NV: Ignoring unsupported device 0x10de0863 (GeForce 9400m) at 02 at 00:00:0
(WW) Falling back to old probe method for vesa
(EE) No devices detected.

Fatal server error:
no screens found

Please consult the The X.Org Foundation support
	 at http://wiki.x.org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional
information.



2010/2/28 Pau <vim.unix at googlemail.com>:
> PS: I have figured now out that pressing the "option" key will load up
> the boot menu, but I only see the Mac HD option... how can I add the
> second partition, where openbsd lives, to that menu?
>
> This is macosx fdisk output:
>
> machorl(s000)| sudo fdisk /dev/disk0
> Password:
> Disk: /dev/disk0 ? ? ? ?geometry: 30515/255/63 [490234752 sectors]
> Signature: 0xAA55
> ? ? ? ? Starting ? ? ? Ending
> ?#: id ?cyl ?hd sec - ?cyl ?hd sec [ ? ? start - ? ? ? size]
> ------------------------------------------------------------------------
> ?1: EE ? ?0 ? 0 ? 2 - ? 25 127 ?14 [ ? ? ? ? 1 - ? ? 409639] <Unknown ID>
> ?2: AF ? 25 127 ?15 - 1023 ?78 ?28 [ ? ?409640 - ?383516672] HFS+
> ?3: A6 1023 191 ?22 - 1023 164 ?49 [ 384190464 - ?106043392] OpenBSD
> ?4: 00 ? ?0 ? 0 ? 0 - ? ?0 ? 0 ? 0 [ ? ? ? ? 0 - ? ? ? ? ?0] unused
>
> 2010/2/28 Pau <vim.unix at googlemail.com>:
>> Hello,
>>
>> I got the macbook pro and just installed a recent snapshot. I used
>> that "bootcamp" programme of apple to resize the macosx partition. I
>> then installed openbsd but since bootcamp thinks you want to install
>> windows, the partition was formatted to vfat. I changed that in the
>> fdisk menu to a6, managed to screw up the mbr, restored it with the
>> apple install DVD and now macosx is again there... now... how do I
>> boot into openbsd? Is there a way to do that having the mbr reserved
>> for apple? Or do I have to install grub or so?
>> Thanks,
>>
>> Pau
>>
>> 2009/11/30 Pau <vim.unix at googlemail.com>:
>>> Hi Nick,
>>>
>>> thanks. Yes, I was imprecise. I was meaning a report on a recent
>>> snapshot or 4.6
>>>
>>> I didn't find anything but it's good to see that the keyboard is
>>> well-supported. Thanks,
>>>
>>> Pau
>>>
>>> 2009/11/29 Nick Guenther <kousue at gmail.com>:
>>>> On Sat, Nov 28, 2009 at 3:15 PM, Pau <vim.unix at googlemail.com> wrote:
>>>>> Hello,
>>>>>
>>>>> I will be soon getting a macbook pro 13" at work. I was wondering how
>>>>> well this is supported by openbsd... Has anybody tried it? I have
>>>>> googled and looked in the archives, but I seemingly was looking not
>>>>> well enough or there are no reports...
>>>>>
>>>>
>>>> Aaron Hsu has one, he's written a guide:
>>>> http://www.sacrideo.us/v1/papers/openbsd_macbook.txt. I know when I
>>>> went searching the archives I found more than just that, too, maybe
>>>> try different keywords?
>>>>
>>>> You're lucky you're getting a pro, the non-pro one gave me all sorts
>>>> of pain with OpenBSD.
>>>>
>>>> -Nick
>>>>
>>>
>>
>

From vim.unix at googlemail.com  Sun Feb 28 23:37:41 2010
From: vim.unix at googlemail.com (Pau)
Date: Sun, 28 Feb 2010 23:37:41 +0100
Subject: macbook pro 13"
In-Reply-To: <30c383e71002281425l6d6ec94bhde742c83a90c10e9@mail.gmail.com>
References: <30c383e70911281215p302d949bobb8cf981f5c58872@mail.gmail.com>
	<98f5a8830911291422i7096d5ew82563658fb94b442@mail.gmail.com>
	<30c383e70911300452g14125588ocf9534b2b44d29d4@mail.gmail.com>
	<30c383e71002281343q13ca6b93ne3718f54e19bc05e@mail.gmail.com>
	<30c383e71002281356y63beefaw6dd2fa13436ce3d3@mail.gmail.com>
	<30c383e71002281425l6d6ec94bhde742c83a90c10e9@mail.gmail.com>
Message-ID: <30c383e71002281437m34df45edq486e247c556a4c53@mail.gmail.com>

Sorry for the spamming... but probably I will not be the only one
trying to do this, so that it will hopefully be useful for others to
read these messages...

I have found out now that seemingly open has been installed on a FAT12
filesystem... I guess this is a mistake I have done by using the
stupid bootcamp thing... I will have to reformat that now and to
reinstall open again... Do you think that could be the reason for X
not running? I do not think so...

Pau

Current GPT partition table:
 #      Start LBA      End LBA  Type
 1             40       409639  EFI System (FAT)
 2         409640    383926311  Mac OS X HFS+
 3      384190464    490233855  Basic Data

Current MBR partition table:
 # A    Start LBA      End LBA  Type
 1              1       409639  ee  EFI Protective
 2         409640    383926311  af  Mac OS X HFS+
 3 *    384190464    490233855  a6  OpenBSD

MBR contents:
 Boot Code: Unknown, but bootable

Partition at LBA 40:
 Boot Code: None (Non-system disk message)
 File System: FAT32
 Listed in GPT as partition 1, type EFI System (FAT)

Partition at LBA 409640:
 Boot Code: None
 File System: HFS Extended (HFS+)
 Listed in GPT as partition 2, type Mac OS X HFS+
 Listed in MBR as partition 2, type af  Mac OS X HFS+

Partition at LBA 384190464:
 Boot Code: OpenBSD
 File System: FAT12
 Listed in GPT as partition 3, type Basic Data
 Listed in MBR as partition 3, type a6  OpenBSD, active



2010/2/28 Pau <vim.unix at googlemail.com>:
> Hello,
>
> I figured out... with refit I can now boot into OpenBSD...
> unfortunately X does not work :(
>
> Too bad... I tried to run it on the fly, without xorg.conf and with X
> -configure... the log follows
>
> I guess the answer is: you will have to wait
>
> Pau
>
> (--) checkDevMem: using aperture driver /dev/xf86
> (--) Using wscons driver on /dev/ttyC4 in pcvt compatibility mode (version 3.32)
>
> X.Org X Server 1.6.5
> Release Date: 2009-10-11
> X Protocol Version 11, Revision 0
> Build Operating System: OpenBSD 4.7 i386
> Current Operating System: OpenBSD machorl.fritz.box 4.7 GENERIC.MP#424 i386
> Build Date: 21 February 2010 ?06:12:32PM
>
> ? ? ? ?Before reporting problems, check http://wiki.x.org
> ? ? ? ?to make sure that you have the latest version.
> Markers: (--) probed, (**) from config file, (==) default setting,
> ? ? ? ?(++) from command line, (!!) notice, (II) informational,
> ? ? ? ?(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/Xorg.0.log", Time: Sun Feb 28 23:18:22 2010
> (II) Loader magic: 0x1dc0
> (II) Module ABI versions:
> ? ? ? ?X.Org ANSI C Emulation: 0.4
> ? ? ? ?X.Org Video Driver: 5.0
> ? ? ? ?X.Org XInput driver : 4.0
> ? ? ? ?X.Org Server Extension : 2.0
> (II) Loader running on openbsd
> (--) PCI: (0:0:3:5) 10de:0aa3:10de:cb79 NVIDIA MCP79 Co-processor rev
> 177, Mem @ 0x00000000/524288
> (--) PCI:*(0:2:0:0) 10de:0863:106b:00b9 NVIDIA GeForce 9400m rev 177,
> Mem @ 0xd2000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432,
> I/O @ 0x00001000/128, BIOS @ 0x????????/131072
> (==) Using default built-in configuration (21 lines)
> (==) --- Start of built-in configuration ---
> ? ? ? ?Section "Device"
> ? ? ? ? ? ? ? ?Identifier ? ? ?"Builtin Default nv Device 0"
> ? ? ? ? ? ? ? ?Driver ?"nv"
> ? ? ? ?EndSection
> ? ? ? ?Section "Screen"
> ? ? ? ? ? ? ? ?Identifier ? ? ?"Builtin Default nv Screen 0"
> ? ? ? ? ? ? ? ?Device ?"Builtin Default nv Device 0"
> ? ? ? ?EndSection
> ? ? ? ?Section "Device"
> ? ? ? ? ? ? ? ?Identifier ? ? ?"Builtin Default vesa Device 0"
> ? ? ? ? ? ? ? ?Driver ?"vesa"
> ? ? ? ?EndSection
> ? ? ? ?Section "Screen"
> ? ? ? ? ? ? ? ?Identifier ? ? ?"Builtin Default vesa Screen 0"
> ? ? ? ? ? ? ? ?Device ?"Builtin Default vesa Device 0"
> ? ? ? ?EndSection
> ? ? ? ?Section "ServerLayout"
> ? ? ? ? ? ? ? ?Identifier ? ? ?"Builtin Default Layout"
> ? ? ? ? ? ? ? ?Screen ?"Builtin Default nv Screen 0"
> ? ? ? ? ? ? ? ?Screen ?"Builtin Default vesa Screen 0"
> ? ? ? ?EndSection
> (==) --- End of built-in configuration ---
> (==) ServerLayout "Builtin Default Layout"
> (**) |-->Screen "Builtin Default nv Screen 0" (0)
> (**) | ? |-->Monitor "<default monitor>"
> (**) | ? |-->Device "Builtin Default nv Device 0"
> (==) No monitor specified for screen "Builtin Default nv Screen 0".
> ? ? ? ?Using a default monitor configuration.
> (**) |-->Screen "Builtin Default vesa Screen 0" (1)
> (**) | ? |-->Monitor "<default monitor>"
> (**) | ? |-->Device "Builtin Default vesa Device 0"
> (==) No monitor specified for screen "Builtin Default vesa Screen 0".
> ? ? ? ?Using a default monitor configuration.
> (==) Not automatically adding devices
> (==) Not automatically enabling devices
> (==) FontPath set to:
> ? ? ? ?/usr/X11R6/lib/X11/fonts/misc/,
> ? ? ? ?/usr/X11R6/lib/X11/fonts/TTF/,
> ? ? ? ?/usr/X11R6/lib/X11/fonts/OTF,
> ? ? ? ?/usr/X11R6/lib/X11/fonts/Type1/,
> ? ? ? ?/usr/X11R6/lib/X11/fonts/100dpi/,
> ? ? ? ?/usr/X11R6/lib/X11/fonts/75dpi/
> (==) ModulePath set to "/usr/X11R6/lib/modules"
> (==) |-->Input Device "<default pointer>"
> (==) |-->Input Device "<default keyboard>"
> (==) The core pointer device wasn't specified explicitly in the layout.
> ? ? ? ?Using the default mouse configuration.
> (==) The core keyboard device wasn't specified explicitly in the layout.
> ? ? ? ?Using the default keyboard configuration.
> (II) System resource ranges:
> ? ? ? ?[0] -1 ?0 ? ? ? 0x000f0000 - 0x000fffff (0x10000) MX[B]
> ? ? ? ?[1] -1 ?0 ? ? ? 0x000c0000 - 0x000effff (0x30000) MX[B]
> ? ? ? ?[2] -1 ?0 ? ? ? 0x00000000 - 0x0009ffff (0xa0000) MX[B]
> ? ? ? ?[3] -1 ?0 ? ? ? 0x0000ffff - 0x0000ffff (0x1) IX[B]
> ? ? ? ?[4] -1 ?0 ? ? ? 0x00000000 - 0x000000ff (0x100) IX[B]
> (II) LoadModule: "extmod"
> (II) Loading /usr/X11R6/lib/modules/extensions//libextmod.so
> (II) Module extmod: vendor="X.Org Foundation"
> ? ? ? ?compiled for 1.6.5, module version = 1.0.0
> ? ? ? ?Module class: X.Org Server Extension
> ? ? ? ?ABI class: X.Org Server Extension, version 2.0
> (II) Loading extension MIT-SCREEN-SAVER
> (II) Loading extension XFree86-VidModeExtension
> (II) Loading extension XFree86-DGA
> (II) Loading extension DPMS
> (II) Loading extension XVideo
> (II) Loading extension XVideo-MotionCompensation
> (II) Loading extension X-Resource
> (II) LoadModule: "dbe"
> (II) Loading /usr/X11R6/lib/modules/extensions//libdbe.so
> (II) Module dbe: vendor="X.Org Foundation"
> ? ? ? ?compiled for 1.6.5, module version = 1.0.0
> ? ? ? ?Module class: X.Org Server Extension
> ? ? ? ?ABI class: X.Org Server Extension, version 2.0
> (II) Loading extension DOUBLE-BUFFER
> (II) LoadModule: "glx"
> (II) Loading /usr/X11R6/lib/modules/extensions//libglx.so
> (II) Module glx: vendor="X.Org Foundation"
> ? ? ? ?compiled for 1.6.5, module version = 1.0.0
> ? ? ? ?ABI class: X.Org Server Extension, version 2.0
> (==) AIGLX enabled
> (II) Loading extension GLX
> (II) LoadModule: "dri"
> (II) Loading /usr/X11R6/lib/modules/extensions//libdri.so
> (II) Module dri: vendor="X.Org Foundation"
> ? ? ? ?compiled for 1.6.5, module version = 1.0.0
> ? ? ? ?ABI class: X.Org Server Extension, version 2.0
> (II) Loading extension XFree86-DRI
> (II) LoadModule: "dri2"
> (II) Loading /usr/X11R6/lib/modules/extensions//libdri2.so
> (II) Module dri2: vendor="X.Org Foundation"
> ? ? ? ?compiled for 1.6.5, module version = 1.1.0
> ? ? ? ?ABI class: X.Org Server Extension, version 2.0
> (II) Loading extension DRI2
> (II) LoadModule: "nv"
> (II) Loading /usr/X11R6/lib/modules/drivers//nv_drv.so
> (II) Module nv: vendor="X.Org Foundation"
> ? ? ? ?compiled for 1.6.5, module version = 2.1.15
> ? ? ? ?Module class: X.Org Video Driver
> ? ? ? ?ABI class: X.Org Video Driver, version 5.0
> (II) LoadModule: "vesa"
> (II) Loading /usr/X11R6/lib/modules/drivers//vesa_drv.so
> (II) Module vesa: vendor="X.Org Foundation"
> ? ? ? ?compiled for 1.6.5, module version = 2.2.1
> ? ? ? ?Module class: X.Org Video Driver
> ? ? ? ?ABI class: X.Org Video Driver, version 5.0
> (II) LoadModule: "mouse"
> (II) Loading /usr/X11R6/lib/modules/input//mouse_drv.so
> (II) Module mouse: vendor="X.Org Foundation"
> ? ? ? ?compiled for 1.6.5, module version = 1.4.0
> ? ? ? ?Module class: X.Org XInput Driver
> ? ? ? ?ABI class: X.Org XInput driver, version 4.0
> (II) LoadModule: "kbd"
> (II) Loading /usr/X11R6/lib/modules/input//kbd_drv.so
> (II) Module kbd: vendor="X.Org Foundation"
> ? ? ? ?compiled for 1.6.5, module version = 1.3.2
> ? ? ? ?Module class: X.Org XInput Driver
> ? ? ? ?ABI class: X.Org XInput driver, version 4.0
> (II) NV: driver for NVIDIA chipsets: RIVA 128, RIVA TNT, RIVA TNT2,
> ? ? ? ?Unknown TNT2, Vanta, RIVA TNT2 Ultra, RIVA TNT2 Model 64,
> ? ? ? ?Aladdin TNT2, GeForce 256, GeForce DDR, Quadro, GeForce2 MX/MX 400,
> ? ? ? ?GeForce2 MX 100/200, GeForce2 Go, Quadro2 MXR/EX/Go,
> ? ? ? ?GeForce2 Integrated GPU, GeForce2 GTS, GeForce2 Ti, GeForce2 Ultra,
> ? ? ? ?Quadro2 Pro, GeForce4 MX 460, GeForce4 MX 440, GeForce4 MX 420,
> ? ? ? ?GeForce4 MX 440-SE, GeForce4 440 Go, GeForce4 420 Go,
> ? ? ? ?GeForce4 420 Go 32M, GeForce4 460 Go, Quadro4 550 XGL,
> ? ? ? ?GeForce4 440 Go 64M, Quadro NVS, Quadro4 500 GoGL,
> ? ? ? ?GeForce4 410 Go 16M, GeForce4 MX 440 with AGP8X,
> ? ? ? ?GeForce4 MX 440SE with AGP8X, GeForce4 MX 420 with AGP8X,
> ? ? ? ?GeForce4 MX 4000, GeForce4 448 Go, GeForce4 488 Go, Quadro4 580 XGL,
> ? ? ? ?Quadro4 NVS 280 SD, Quadro4 380 XGL, Quadro NVS 50 PCI,
> ? ? ? ?GeForce4 448 Go, GeForce4 MX Integrated GPU, GeForce3,
> ? ? ? ?GeForce3 Ti 200, GeForce3 Ti 500, Quadro DCC, GeForce4 Ti 4600,
> ? ? ? ?GeForce4 Ti 4400, GeForce4 Ti 4200, Quadro4 900 XGL, Quadro4 750 XGL,
> ? ? ? ?Quadro4 700 XGL, GeForce4 Ti 4800, GeForce4 Ti 4200 with AGP8X,
> ? ? ? ?GeForce4 Ti 4800 SE, GeForce4 4200 Go, Quadro4 700 GoGL,
> ? ? ? ?Quadro4 980 XGL, Quadro4 780 XGL, GeForce FX 5800 Ultra,
> ? ? ? ?GeForce FX 5800, Quadro FX 2000, Quadro FX 1000,
> ? ? ? ?GeForce FX 5600 Ultra, GeForce FX 5600, GeForce FX 5600XT,
> ? ? ? ?GeForce FX Go5600, GeForce FX Go5650, Quadro FX Go700,
> ? ? ? ?GeForce FX 5200, GeForce FX 5200 Ultra, GeForce FX 5200,
> ? ? ? ?GeForce FX 5200LE, GeForce FX Go5200, GeForce FX Go5250,
> ? ? ? ?GeForce FX 5500, GeForce FX 5100, GeForce FX Go5200 32M/64M,
> ? ? ? ?Quadro NVS 55/280 PCI, Quadro FX 500/600 PCI,
> ? ? ? ?GeForce FX Go53xx Series, GeForce FX Go5100, GeForce FX 5900 Ultra,
> ? ? ? ?GeForce FX 5900, GeForce FX 5900XT, GeForce FX 5950 Ultra,
> ? ? ? ?GeForce FX 5900ZT, Quadro FX 3000, Quadro FX 700,
> ? ? ? ?GeForce FX 5700 Ultra, GeForce FX 5700, GeForce FX 5700LE,
> ? ? ? ?GeForce FX 5700VE, GeForce FX Go5700, GeForce FX Go5700,
> ? ? ? ?Quadro FX Go1000, Quadro FX 1100, GeForce 6800 Ultra, GeForce 6800,
> ? ? ? ?GeForce 6800 LE, GeForce 6800 XE, GeForce 6800 XT, GeForce 6800 GT,
> ? ? ? ?GeForce 6800 GT, GeForce 6800 GS, GeForce 6800 XT, Quadro FX 4000,
> ? ? ? ?GeForce 6800 GS, GeForce 6800, GeForce 6800 LE, GeForce 6800 XT,
> ? ? ? ?GeForce Go 6800, GeForce Go 6800 Ultra, Quadro FX Go1400,
> ? ? ? ?Quadro FX 3450/4000 SDI, Quadro FX 1400, GeForce 6600 GT,
> ? ? ? ?GeForce 6600, GeForce 6600 LE, GeForce 6600 VE, GeForce Go 6600,
> ? ? ? ?GeForce 6610 XL, GeForce Go 6600 TE/6200 TE, GeForce 6700 XL,
> ? ? ? ?GeForce Go 6600, GeForce Go 6600 GT, Quadro NVS 440, Quadro FX 550,
> ? ? ? ?Quadro FX 550, Quadro FX 540, GeForce 6200, GeForce 6500,
> ? ? ? ?GeForce 6200 TurboCache(TM), GeForce 6200SE TurboCache(TM),
> ? ? ? ?GeForce 6200 LE, GeForce Go 6200, Quadro NVS 285, GeForce Go 6400,
> ? ? ? ?GeForce Go 6200, GeForce Go 6400, GeForce 6250, GeForce 7100 GS,
> ? ? ? ?GeForce 6800, GeForce 6800 LE, GeForce 6800 GT, GeForce 6800 XT,
> ? ? ? ?GeForce 6200, GeForce 6200 A-LE, GeForce 7800 GTX, GeForce 7800 GTX,
> ? ? ? ?GeForce 7800 GT, GeForce 7800 GS, GeForce 7800 SLI, GeForce Go 7800,
> ? ? ? ?GeForce Go 7800 GTX, Quadro FX 4500, GeForce 7350 LE,
> ? ? ? ?GeForce 7300 LE, GeForce 7300 SE, GeForce Go 7200, GeForce Go 7300,
> ? ? ? ?GeForce Go 7400, GeForce Go 7400 GS, Quadro NVS 110M,
> ? ? ? ?Quadro NVS 120M, Quadro FX 350M, GeForce 7500 LE, Quadro FX 350,
> ? ? ? ?GeForce 7300 GS, GeForce 7650 GS, GeForce 7600 GT, GeForce 7600 GS,
> ? ? ? ?GeForce 7300 GT, GeForce 7600 LE, GeForce 7300 GT, GeForce Go 7700,
> ? ? ? ?GeForce Go 7600, GeForce Go 7600 GT, Quadro NVS 300M,
> ? ? ? ?GeForce Go 7900 SE, Quadro FX 550M, Quadro FX 560, GeForce 7900 GTX,
> ? ? ? ?GeForce 7900 GT, GeForce 7900 GS, GeForce 7950 GX2, GeForce 7950 GX2,
> ? ? ? ?GeForce 7950 GT, GeForce Go 7950 GTX, GeForce Go 7900 GS,
> ? ? ? ?GeForce Go 7900 GTX, Quadro FX 2500M, Quadro FX 1500M,
> ? ? ? ?Quadro FX 5500, Quadro FX 3500, Quadro FX 1500, Quadro FX 4500 X2,
> ? ? ? ?GeForce 6150, GeForce 6150 LE, GeForce 6100, GeForce Go 6150,
> ? ? ? ?Quadro NVS 210S / NVIDIA GeForce 6150LE, GeForce Go 6100,
> ? ? ? ?GeForce 6150SE, GeForce 6100 nForce 405, GeForce 6100 nForce 400,
> ? ? ? ?GeForce 6100 nForce 420, GeForce 8800 GTX, GeForce 8800 GTS,
> ? ? ? ?GeForce 8800 Ultra, Quadro FX 5600, Quadro FX 4600, GeForce 8600 GTS,
> ? ? ? ?GeForce 8600 GT, GeForce 8600 GT, GeForce 8600 GS, GeForce 8400 GS,
> ? ? ? ?GeForce 9500M GS, GeForce 8600M GT, GeForce 9650M GS,
> ? ? ? ?GeForce 8700M GT, Quadro FX 370, Quadro NVS 320M, Quadro FX 570M,
> ? ? ? ?Quadro FX 1600M, Quadro FX 570, Quadro FX 1700, GeForce 8400 SE,
> ? ? ? ?GeForce 8500 GT, GeForce 8400 GS, GeForce 8300 GS, GeForce 8400 GS,
> ? ? ? ?GeForce 8600M GS, GeForce 8400M GT, GeForce 8400M GS,
> ? ? ? ?GeForce 8400M G, Quadro NVS 140M, Quadro NVS 130M, Quadro NVS 135M,
> ? ? ? ?GeForce 9400 GT, Quadro FX 360M, GeForce 9300M G, Quadro NVS 290,
> ? ? ? ?GeForce GTX 280, GeForce GTX 260, GeForce 8800 GTS 512,
> ? ? ? ?GeForce 8800 GT, GeForce 9800 GX2, GeForce 8800 GS,
> ? ? ? ?GeForce 8800M GTS, GeForce 8800M GTX, GeForce 8800 GS,
> ? ? ? ?GeForce 9600 GSO, GeForce 8800 GT, GeForce 9800 GTX,
> ? ? ? ?GeForce 9800 GTK+, GeForce 9800 GT, Quadro FX 3700, Quadro FX 3600M,
> ? ? ? ?GeForce 9600 GT, GeForce 9600 GS, GeForce 9800M GTS,
> ? ? ? ?GeForce 9700M GTS, GeForce 9800M GTS, GeForce 9500 GT,
> ? ? ? ?GeForce 9600M GT, GeForce 9600M GS, GeForce 9600M GT,
> ? ? ? ?GeForce 9500M G, GeForce 9300 GE, GeForce 9300 GS, GeForce 8400 GS,
> ? ? ? ?GeForce 9300M GS, GeForce 9200M GS, GeForce 9300M GS,
> ? ? ? ?Quadro NVS 150M, Quadro NVS 160M, GeForce 9300 GE
> (II) VESA: driver for VESA chipsets: vesa
> (II) Primary Device is: PCI 02 at 00:00:0
> (WW) NV: Ignoring unsupported device 0x10de0863 (GeForce 9400m) at 02 at 00:00:0
> (WW) Falling back to old probe method for vesa
> (EE) No devices detected.
>
> Fatal server error:
> no screens found
>
> Please consult the The X.Org Foundation support
> ? ? ? ? at http://wiki.x.org
> ?for help.
> Please also check the log file at "/var/log/Xorg.0.log" for additional
> information.
>
>
>
> 2010/2/28 Pau <vim.unix at googlemail.com>:
>> PS: I have figured now out that pressing the "option" key will load up
>> the boot menu, but I only see the Mac HD option... how can I add the
>> second partition, where openbsd lives, to that menu?
>>
>> This is macosx fdisk output:
>>
>> machorl(s000)| sudo fdisk /dev/disk0
>> Password:
>> Disk: /dev/disk0 ? ? ? ?geometry: 30515/255/63 [490234752 sectors]
>> Signature: 0xAA55
>> ? ? ? ? Starting ? ? ? Ending
>> ?#: id ?cyl ?hd sec - ?cyl ?hd sec [ ? ? start - ? ? ? size]
>> ------------------------------------------------------------------------
>> ?1: EE ? ?0 ? 0 ? 2 - ? 25 127 ?14 [ ? ? ? ? 1 - ? ? 409639] <Unknown ID>
>> ?2: AF ? 25 127 ?15 - 1023 ?78 ?28 [ ? ?409640 - ?383516672] HFS+
>> ?3: A6 1023 191 ?22 - 1023 164 ?49 [ 384190464 - ?106043392] OpenBSD
>> ?4: 00 ? ?0 ? 0 ? 0 - ? ?0 ? 0 ? 0 [ ? ? ? ? 0 - ? ? ? ? ?0] unused
>>
>> 2010/2/28 Pau <vim.unix at googlemail.com>:
>>> Hello,
>>>
>>> I got the macbook pro and just installed a recent snapshot. I used
>>> that "bootcamp" programme of apple to resize the macosx partition. I
>>> then installed openbsd but since bootcamp thinks you want to install
>>> windows, the partition was formatted to vfat. I changed that in the
>>> fdisk menu to a6, managed to screw up the mbr, restored it with the
>>> apple install DVD and now macosx is again there... now... how do I
>>> boot into openbsd? Is there a way to do that having the mbr reserved
>>> for apple? Or do I have to install grub or so?
>>> Thanks,
>>>
>>> Pau
>>>
>>> 2009/11/30 Pau <vim.unix at googlemail.com>:
>>>> Hi Nick,
>>>>
>>>> thanks. Yes, I was imprecise. I was meaning a report on a recent
>>>> snapshot or 4.6
>>>>
>>>> I didn't find anything but it's good to see that the keyboard is
>>>> well-supported. Thanks,
>>>>
>>>> Pau
>>>>
>>>> 2009/11/29 Nick Guenther <kousue at gmail.com>:
>>>>> On Sat, Nov 28, 2009 at 3:15 PM, Pau <vim.unix at googlemail.com> wrote:
>>>>>> Hello,
>>>>>>
>>>>>> I will be soon getting a macbook pro 13" at work. I was wondering how
>>>>>> well this is supported by openbsd... Has anybody tried it? I have
>>>>>> googled and looked in the archives, but I seemingly was looking not
>>>>>> well enough or there are no reports...
>>>>>>
>>>>>
>>>>> Aaron Hsu has one, he's written a guide:
>>>>> http://www.sacrideo.us/v1/papers/openbsd_macbook.txt. I know when I
>>>>> went searching the archives I found more than just that, too, maybe
>>>>> try different keywords?
>>>>>
>>>>> You're lucky you're getting a pro, the non-pro one gave me all sorts
>>>>> of pain with OpenBSD.
>>>>>
>>>>> -Nick
>>>>>
>>>>
>>>
>>
>

From vim.unix at googlemail.com  Sun Feb 28 22:43:55 2010
From: vim.unix at googlemail.com (Pau)
Date: Sun, 28 Feb 2010 22:43:55 +0100
Subject: macbook pro 13"
In-Reply-To: <30c383e70911300452g14125588ocf9534b2b44d29d4@mail.gmail.com>
References: <30c383e70911281215p302d949bobb8cf981f5c58872@mail.gmail.com>
	<98f5a8830911291422i7096d5ew82563658fb94b442@mail.gmail.com>
	<30c383e70911300452g14125588ocf9534b2b44d29d4@mail.gmail.com>
Message-ID: <30c383e71002281343q13ca6b93ne3718f54e19bc05e@mail.gmail.com>

Hello,

I got the macbook pro and just installed a recent snapshot. I used
that "bootcamp" programme of apple to resize the macosx partition. I
then installed openbsd but since bootcamp thinks you want to install
windows, the partition was formatted to vfat. I changed that in the
fdisk menu to a6, managed to screw up the mbr, restored it with the
apple install DVD and now macosx is again there... now... how do I
boot into openbsd? Is there a way to do that having the mbr reserved
for apple? Or do I have to install grub or so?
Thanks,

Pau

2009/11/30 Pau <vim.unix at googlemail.com>:
> Hi Nick,
>
> thanks. Yes, I was imprecise. I was meaning a report on a recent
> snapshot or 4.6
>
> I didn't find anything but it's good to see that the keyboard is
> well-supported. Thanks,
>
> Pau
>
> 2009/11/29 Nick Guenther <kousue at gmail.com>:
>> On Sat, Nov 28, 2009 at 3:15 PM, Pau <vim.unix at googlemail.com> wrote:
>>> Hello,
>>>
>>> I will be soon getting a macbook pro 13" at work. I was wondering how
>>> well this is supported by openbsd... Has anybody tried it? I have
>>> googled and looked in the archives, but I seemingly was looking not
>>> well enough or there are no reports...
>>>
>>
>> Aaron Hsu has one, he's written a guide:
>> http://www.sacrideo.us/v1/papers/openbsd_macbook.txt. I know when I
>> went searching the archives I found more than just that, too, maybe
>> try different keywords?
>>
>> You're lucky you're getting a pro, the non-pro one gave me all sorts
>> of pain with OpenBSD.
>>
>> -Nick
>>
>

From vim.unix at googlemail.com  Sun Feb 28 22:56:21 2010
From: vim.unix at googlemail.com (Pau)
Date: Sun, 28 Feb 2010 22:56:21 +0100
Subject: macbook pro 13"
In-Reply-To: <30c383e71002281343q13ca6b93ne3718f54e19bc05e@mail.gmail.com>
References: <30c383e70911281215p302d949bobb8cf981f5c58872@mail.gmail.com>
	<98f5a8830911291422i7096d5ew82563658fb94b442@mail.gmail.com>
	<30c383e70911300452g14125588ocf9534b2b44d29d4@mail.gmail.com>
	<30c383e71002281343q13ca6b93ne3718f54e19bc05e@mail.gmail.com>
Message-ID: <30c383e71002281356y63beefaw6dd2fa13436ce3d3@mail.gmail.com>

PS: I have figured now out that pressing the "option" key will load up
the boot menu, but I only see the Mac HD option... how can I add the
second partition, where openbsd lives, to that menu?

This is macosx fdisk output:

machorl(s000)| sudo fdisk /dev/disk0
Password:
Disk: /dev/disk0        geometry: 30515/255/63 [490234752 sectors]
Signature: 0xAA55
         Starting       Ending
 #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
------------------------------------------------------------------------
 1: EE    0   0   2 -   25 127  14 [         1 -     409639] <Unknown ID>
 2: AF   25 127  15 - 1023  78  28 [    409640 -  383516672] HFS+
 3: A6 1023 191  22 - 1023 164  49 [ 384190464 -  106043392] OpenBSD
 4: 00    0   0   0 -    0   0   0 [         0 -          0] unused

2010/2/28 Pau <vim.unix at googlemail.com>:
> Hello,
>
> I got the macbook pro and just installed a recent snapshot. I used
> that "bootcamp" programme of apple to resize the macosx partition. I
> then installed openbsd but since bootcamp thinks you want to install
> windows, the partition was formatted to vfat. I changed that in the
> fdisk menu to a6, managed to screw up the mbr, restored it with the
> apple install DVD and now macosx is again there... now... how do I
> boot into openbsd? Is there a way to do that having the mbr reserved
> for apple? Or do I have to install grub or so?
> Thanks,
>
> Pau
>
> 2009/11/30 Pau <vim.unix at googlemail.com>:
>> Hi Nick,
>>
>> thanks. Yes, I was imprecise. I was meaning a report on a recent
>> snapshot or 4.6
>>
>> I didn't find anything but it's good to see that the keyboard is
>> well-supported. Thanks,
>>
>> Pau
>>
>> 2009/11/29 Nick Guenther <kousue at gmail.com>:
>>> On Sat, Nov 28, 2009 at 3:15 PM, Pau <vim.unix at googlemail.com> wrote:
>>>> Hello,
>>>>
>>>> I will be soon getting a macbook pro 13" at work. I was wondering how
>>>> well this is supported by openbsd... Has anybody tried it? I have
>>>> googled and looked in the archives, but I seemingly was looking not
>>>> well enough or there are no reports...
>>>>
>>>
>>> Aaron Hsu has one, he's written a guide:
>>> http://www.sacrideo.us/v1/papers/openbsd_macbook.txt. I know when I
>>> went searching the archives I found more than just that, too, maybe
>>> try different keywords?
>>>
>>> You're lucky you're getting a pro, the non-pro one gave me all sorts
>>> of pain with OpenBSD.
>>>
>>> -Nick
>>>
>>
>