Re: FreeBSD daemon(8)-like command for OpenBSD

[Daniel Dickman]




>> On Jan 30, 2020, at 4:34 PM, Patrick Kristiansen  wrote:
> On Thu, Jan 30, 2020, at 21:10, Ingo Schwarze wrote:
>> Hi Patrick,
>> 
>> Patrick Kristiansen wrote on Thu, Jan 30, 2020 at 09:05:11PM +0100:
>> 
>>> The process I need to run is written in Clojure and thus runs on the
>>> Java Virtual Machine.  Do you have any suggestions on how to best go
>>> about making it "daemon-like"?
>> 
>> No, i'm sorry i have no advice on that.  I would certainly not run
>> soemthing like that under any circumstances, on any machine, and even
>> less so on any machine connected to the Internet.
> 
> Out of genuine curiosity, and not to be inflammatory, are you saying
> that running any internet-facing service/process/program is inadvisible

Hi Patrick, one of the risks is something like blind ROP. To quote from the 
website (emphasis mine):

“requires a stack overflow and a *service that restarts after a crash*”

https://www.scs.stanford.edu/brop/


> under all circumstances if not written to the standards of a daemon
> shipping with OpenBSD and with the facilities (pledge, unveil, etc.)
> available in OpenBSD?
> 
> Best regards,
> Patrick

Re: OpenBSD FAQ - Using S/Key - hash algorithm selection

[Daniel Dickman]

> On Jan 11, 2020, at 3:24 PM, Anders Andersson  wrote:
> 
> While perusing the OpenBSD FAQ I came across the S/Key login system
> and noticed that there are three possible hashing algorithms to choose
> from: MD5, SHA1, and RIPEMD-160.
> 
> Instinctively I wouldn't want to use any of these. RIPEMD-160 seems
> like the only one that hasn't been broken, but that's probably because
> no one really cares as much as they do with MD5 and SHA1.

Collision attacks are not the same as preimage attacks. The latter are much 
harder.  See: https://en.m.wikipedia.org/wiki/S/KEY#Security

Here’s an article that also may be of interest:

https://electriccoin.co/blog/lessons-from-the-history-of-attacks-on-secure-hash-functions/

> 
> But of course, it depends on how they are used. Is this a case of when
> it's fine to use them, or is it simply that nobody uses S/Key anymore
> so there's no real incentive to change them?
> 
> Just being curious, I didn't even know S/Key existed until a few minutes ago.
> 

Re: Linux equivalent of ifstated?

[Daniel Dickman]

> On Apr 18, 2019, at 9:10 AM, Paul Suh  wrote:
> 
> Folks, 
> 
> Sorry to pollute with with non-OpenBSD but it's sorta related. I need to work 
> on a Linux system and I need the functionality of ifstated(8), in particular 
> with respect to arbitrary tests as well as interface state. The ifupdown 
> scripts are not sufficient. Can anyone tell me the equivalent in Linux-land? 
> My Google-fu seems to be weak. 
> 
> Thanks! 
> 
> 
> --Paul
> 

someone did something with monit. maybe this could be useful?

http://mxb.unixconn.com/Blog/Entries/2012/4/14_ifstated_equivalent_in_Linux.html

Re: radeondrm failure on amd64 but not on i386?

[Daniel Dickman]

> On Dec 19, 2018, at 10:22 AM, Andy Bradford 
>  wrote:
> 
> Thus said Daniel Dickman on Fri, 14 Dec 2018 20:45:11 -0500:
> 
>> Try  previous releases  of OpenBSD/amd64  to check  if radeondrm  ever
>> worked for you on amd64.
> 
> That  was a  fruitful suggestion.  I tried  6.3 amd64  and it  works. So
> somewhere after  6.3 a change  was introduced that made  this particular
> Radeon card not work. I'll see if  I can discover which. What's the best
> way to bisect with CVS; update sources by date/time?

It was probably the big update to resync radeondrm with the linux 4.4.x kernel. 
Believe that happened shortly after 6.3 was released. Previous to this, 
radeondrm was synced against the linux 3.8.x kernel.

https://github.com/openbsd/src/commit/7ccd5a2c19d4480fd59ed7bbf02608c8980a7858

If you really wanted to bisect this you can use the github mirror. it would be 
interesting if the drm update is *not* the commit that broke things. anyway 
think you might be able to start with openbsd 6.3, install git package, 
download the git tree from github then bisect and recompile the kernel and 
reboot. (hopefully doesn’t need a full build of base here).

> 
>> If you  diff the dmesgs is  there any other on
>> already been reported?
> 
> I don't believe there were any other significant diffences.

btw I saw a note from kettenis@ that a drm update is being worked on:
https://marc.info/?l=openbsd-bugs=154512499015162=2

just fyi.

Re: radeondrm failure on amd64 but not on i386?

[Daniel Dickman]

> On Dec 14, 2018, at 5:41 PM, Andy Bradford 
>  wrote:
> 
> Thus said Allan Streib on Wed, 12 Dec 2018 14:09:06 -0500:
> 
>> Stillhavingthis   issueon-currentas   ofDec10.
>> machdep.allowaperture=2  does   get  me  past  this,   but  am  seeing
>> weird  behavior, some  regions  of screens/terminals  not painting  or
>> refreshing.
> 
> As far as I'm  aware no progress has been made. It seems  to be having a
> problem reading  the ATOM BIOS  and I haven't yet  figured out a  way to
> dump out what it is reading to disk so it can be analyzed. Maybe some of
> the commands  from the  other thread  on bugs@  will lead  to additional
> information.

Try previous releases of OpenBSD/amd64 to check if radeondrm ever worked for 
you on amd64. I wouldn’t check any version older than 6.1, but if any of the 
previous releases work that could give some more clues about where the problem 
could be.

Also would be interesting to uncomment DRMDEBUG and show full dmesg under both 
i386 and amd64 using -current releases. ie. 

https://github.com/openbsd/src/blob/master/sys/dev/pci/drm/drmP.h#L40

If you diff the dmesgs is there any other difference besides what’s already 
been reported?

> 
> Another alternative,  if you  can, is  to use i386  instead of  amd64. I
> found that on i386 it does correctly detect the ATOM BIOS.
> 
> Andy
> -- 
> TAI64 timestamp: 40005c1431b9
> 
> 

Re: cc: dereference NULL pointer inside switch brackets and no exception

[Daniel Dickman]

On Mon, Sep 3, 2018 at 7:53 AM, Denis Buga  wrote:
> int main()
> {
> char * ptr = NULL;
> switch( *ptr )
> {
> default:
> fprintf(stderr,
>
> "where is exception ? default label exist for"
> "exclusive value, not for non-existent ! "
>
> "it can be security issue, when dereferencing NULL "
> "in switch formally pass and we go to default label\n");
> } }
>
> No ?
>
> 6.3 GENERIC.MP#8 amd64


Your code has no case statement, so it's equivalent to just removing
the switch block and only keeping the code in the default case.

Add any case statement you like and you should get the segfault you're
looking for...

Re: SNI PCD-5T - MP operation on OpenBSD 6.3-current

[Daniel Dickman]

Hi Frank —

> I got this nice old "workstation" from the mid 90ies with dual P54C
> processors and i430NX chipset and want to operate it in MP mode with
> OpenBSD. Unfortunately this doesn't work as expected currently.

Are you able to describe "doesn't work as expected" a bit more? Does it hang 
after the dmesg? do you get to login? Something else?

> I've
> already tried with 6.1, 6.2 and 6.3-current-1521924436. Find attached
> the full dmesg output for 6.3-[...] below, but I suspect that the
> following message is the most relevant one:
> 
> ```
> [...]
> bios0: MP default configuration 6 not supported
> [...]
> ```
> 
> I actually don't know the meaning of it, can someone perhaps shed some
> light on it?

It means you got to this bit of code (see sys/arch/i386/i386/mpbios.c):

   if (mp_fps->pap == 0) {
   if (mp_fps->mpfb1 == 0)
   printf("%s: MP fps invalid: "
   "no default config and no configuration table\n",
   self->dv_xname);
   else
   printf("%s: MP default configuration %d not "
   "supported\n", self->dv_xname, mp_fps->mpfb1);
   goto err;
   }

mp_fps is the "MP floating point structure" (see 4.1 in the MP spec). Now, we 
know the pap (Physical Address Pointer) is zero which means the MP config table 
doesn't exist on your system. So when there's no config table, the spec wants 
to use a default setup. (see section 5 of the spec).

To know which default config to use we’d need to use the MP information byte #1 
according to the spec. Your dmesg shows the value is 6 and the spec says a 
value of 6 refers to 2 cpus with EISA+PCI bus and integrated APIC).

It may be the case that more work is needed to add support for this setup. 
Haven’t looked much further than that so far...

Re: OpenBSD fuzzy testing

[Daniel Dickman]

Hi there.

> On Aug 23, 2017, at 3:56 AM, Infoomatic  wrote:
> 
> Hi,
> As nowadays I read quite a lot of projects being fuzzy tested or 
> vulnerabilities detected by fuzzy testing, I am quite curious: what is the 
> status of OpenBSD kernel/base system concerning fuzzy testing?

yes fuzzers have been used for a very long time. if you search through the 
commit archives you'll see that one recent example is afl which has been used 
on both userland and kernel.

Some links:
http://www.undeadly.org/cgi?action=article=20150121093259
http://lcamtuf.coredump.cx/afl/
https://github.com/nccgroup/TriforceOpenBSDFuzzer

other fuzzers have been used too as far as I know.

More work in this space is always welcome too.

> Is there a plan on using the Google fuzzer? thanks

to be clear, you're asking about oss-fuzz? if yes, then someone motivated 
enough might be able to get it going but it looks like a good amount of work to 
set it all up in a docker environment, etc.

I might explore... at some point... maybe.

But right now I'm personally more focused on static analysis of the kernel 
using tools like coverity.

> 
> regards,
> infoomatic
> 

Re: Interest in POWER platform?

[Daniel Dickman]

> On May 25, 2017, at 8:28 AM, Karel Gardas  wrote:
> 
>> On Thu, May 25, 2017 at 2:05 PM, valerij zaporogeci  
>> wrote:
>> 2017-05-25 3:46 GMT+03:00, Chris Cappuccio :
>>> 
>>> OpenBSD is moving ahead on armv7, arm64, and mips64 (loongson, octeon, sgi)
>>> as viable alternatives to i386/amd64. Other platforms are not well supported
>>> usually due to lack of available hardware and, therefore, developer
>>> interest.
>>> 
>>> Chris
>>> 
>> 
>> Sorry for off-topic, but I didn't want to start a new thread, it's
>> just a small question. Is OpenBSD "moving ahead" to mips32 too under
>> this mentioned move? :) More specifically is there an effort to run it
>> on such a mips SBC like Imagination's Mips Creator CI20? I know it's
>> just a tiny mini-PC, not a sever thingy, but it's not worse than
>> Raspperry Pi by the hardware capabilies.
>> I am asking because I am trying to write an UEFI implementation on it,
>> xD and am wondering if OpenBSD had support for this board, would it
>> use efi loader approach on this architecture or not.
>> I know, there is no UEFI support for mips even in the UEFI
>> specification, that's why I am doing my attempt. :)
> 
> Search the archives, but IIRC last "message" was that mips32 is a no
> go. The reason if I'm not mistaken is some MMU thingy or limitation or
> whatever. I'm sure you will be able to find it in archive of this
> mailing list.
> 


https://www.sccs.swarthmore.edu/users/16/mmcconv1/others/miod-mips32.txt

Re: Openbsd broke my hard drive twice! Getting frustrated

[Daniel Dickman]

On Thu, Feb 5, 2015 at 3:22 AM, Daniel Dickman didick...@gmail.com wrote:


 On Monday, December 22, 2014, Ted Unangst t...@tedunangst.com wrote:

 On Tue, Dec 23, 2014 at 00:53, Henrique Lengler wrote:
  On 2014-12-23 00:50, Edgar Pettijohn III wrote:
  Have you tried installing something other than OpenBSD since you ran
  into this issue?
 
  Since I ran into this issue I can't even access my bios with the HDD
  sata connected.

 That can only be a problem with your BIOS. Update it? Get a better
 one? I don't know. But if your BIOS doesn't work with some drive
 attached, your BIOS is broken.


 I just bought a system with what seems like the same problem as in this
 thread (dell laptop). I upgraded the drive to an ssd. the laptop firmware
 and the ssd firmware were both upgraded to the latest versions.

 with windows installed I can press F2 and get into the firmware menu just
 fine. with openbsd I just get a black screen when I press F2 at boot.

 I did a test. after i installed openbsd, I overwrote the mbr with all
 zeroes. when I rebooted I could access the bios menu via F2 again.

 does seem like a firmware bug based on the contents of the mbr. will see if
 I can diagnose further.

After some more digging. It's not the MBR itself that's the problem.

The firmware on my laptop reads all the partitions in the MBR except
ones marked as type EE (EFI). It then seems to try to read into those
partitions for something else. If there is even 1 OpenBSD partition,
it chokes on something in it. No idea why the firmware is reading past
the MBR and into the actual disk partitions, seems strange.

Dunno if this helps anyone else with a similar problem, but at least
for my system I know for sure it's a firmware bug.

Re: Openbsd broke my hard drive twice! Getting frustrated

[Daniel Dickman]

On Monday, December 22, 2014, Ted Unangst t...@tedunangst.com wrote:

 On Tue, Dec 23, 2014 at 00:53, Henrique Lengler wrote:
  On 2014-12-23 00:50, Edgar Pettijohn III wrote:
  Have you tried installing something other than OpenBSD since you ran
  into this issue?
 
  Since I ran into this issue I can't even access my bios with the HDD
  sata connected.

 That can only be a problem with your BIOS. Update it? Get a better
 one? I don't know. But if your BIOS doesn't work with some drive
 attached, your BIOS is broken.


I just bought a system with what seems like the same problem as in this
thread (dell laptop). I upgraded the drive to an ssd. the laptop firmware
and the ssd firmware were both upgraded to the latest versions.

with windows installed I can press F2 and get into the firmware menu just
fine. with openbsd I just get a black screen when I press F2 at boot.

I did a test. after i installed openbsd, I overwrote the mbr with all
zeroes. when I rebooted I could access the bios menu via F2 again.

does seem like a firmware bug based on the contents of the mbr. will see if
I can diagnose further.

Re: Clarification on patching 5.5-release...

[Daniel Dickman]

Hi Andrew,

On Sat, Jan 17, 2015 at 4:13 PM, Andrew Lester martinblan...@gmail.com wrote:
 Hello misc,

 I've got some simple questions on the patch process which I couldn't find 
 answers to on
 my own. Currently I am running 5.5-RELEASE, and sitting on my 5.6 disc set 
 waiting to
 upgrade. I want to make sure I've been patching my 5.5 system correctly 
 first, though. :)

You don't need to apply the 5.5 patches to upgrade to 5.6. Use your CD
to upgrade to 5.6 and then apply the 5.6 errata.


 1) Can patches be applied selectively and out of order?

Don't do that.


 2) Is it necessary to reboot the system between each patch, or can a batch be 
 applied,
 and then a reboot performed?

Read the instructions at the top of each patch. If it says to reboot,
reboot. Obviously if you update your kernel you should reboot at the
end.


 3) Early on I made what I hope is an inconsequential mistake. One of the 
 first patches
 that I applied, I ran the signify command not from root, but using sudo, and 
 didn't put
 sudo in the second part of the piped command. I didn't catch this until after 
 going
 through the make obj, make and make install process (with sudo). When I 
 realized the
 second part of the original signify command didn't work successfully as it 
 was not run
 with root privileges, I just went through the process again, from the root 
 account. Doing
 this seemed to be successful. Does anybody know if this would have failed for 
 any reason?

I've no idea what you did. Follow the instructions and you won't have a problem.


 My next question is regarding patching the kernel, as is the case with the 
 013, 016 and
 017 patches for OpenBSD 5.5-RELEASE. Unlike the other patches, kernel patches 
 don't have
 explicit instructions on rebuilding the kernel. I believe I've found a 
 correct procedure,
 and would like to confirm it will work. My system uses the AMD64 GENERIC.MP 
 kernel. Is the
 below process correct?

See the FAQ:
http://www.openbsd.org/faq/faq5.html#BldKernel


[...snip]


 Finally, I arrive at my last question, and it relates to another careless 
 mistake on my
 part. :( I downloaded the sig files, and ran the associated signify commands 
 for patch 013
 and 016 before realizing they were kernel patches and I didn't know how to 
 recompile the
 kernel yet. I caught 017 luckily (fool me thrice?).

 Is it a problem that the source patches for 013 and 016 have both been 
 applied, without
 going through the make process between? If so, is there a way I can revert 
 the 016 source
 patch so I can first make and install the 013 patch? If not, is it safe to 
 recompile the
 kernel with both source patches in place? If yes, I assume it would also be 
 safe to throw
 in 017 as well so I can get all three patches in with a single compile, 
 correct?


Don't waste your time on this, upgrade to 5.6 then follow the
instructions for all the errata and you should be in good shape..

Re: A christmassy related issue with traceroute

[Daniel Dickman]

On Wed, Dec 24, 2014 at 7:26 PM, Mike lesniewskis...@gmail.com wrote:
 Hi All,

 While performing an install and catching up with some Christmas spirited
 news, I heard that someone had put a Christmas song in DNS records for our
 enjoyment.

 Alas, I was disappointed to see that the OpenBSD traceroute seems to munge
 the output. :(

 To test, run traceroute -m 255 xmas.futile.net

Oh, that just won't do. See if you get better results with this instead:
traceroute -q1 -m 255 xmas.futile.net

Re: Why doesn't 'l' in ed(1) show a trailing '$'?

[Daniel Dickman]

On Sun, Nov 23, 2014 at 4:43 PM, Jason McIntyre j...@kerhand.co.uk wrote:
 On Sun, Nov 23, 2014 at 10:46:23AM +0100, Ezequiel Garz?n wrote:
 Hello, everyone. I've noticed that in OpenBSD ed(1) doesn't mark the
 end of each line with a '$' when the list command 'l' is invoked. Is
 this a deliberate deviation from the POSIX standard? Is there any
 rationale for it? It looks like this should help print the addressed
 lines unambiguously when dealing with trailing spaces, no?

 Thanks and cheers,

 Ezequiel


 i don't know, but i'd like to.

 there is nothing in bin/ed/POSIX concerning `l', but commit history to
 that file is not exactly inspiring.

 there is nothing in the posix page for ed documenting whether this is
 something recent. it's there in 2008, and in the 2013 update.

 it would be good to know how other bsds behave, and whether the
 behaviour is considered desireable. then we'd know if behaviour should
 be changed, or whether a doc update is enough.

 if i don;t get any concrete feedback on that, i'll update the doc.

 anyone want to chip in?

 jmc


Hi Jason, commenting out CFLAGS+=-DBACKWARDS and recompiling will show
the $ at the end of long lines.

bin/ed/README says:
BACKWARDS   - for backwards compatibility

This hasn't changed since 1995. Anyone know what ed is supposed to be
backwards compatible with?

Re: making firefox less insecure

[Daniel Dickman]

On Sun, Nov 16, 2014 at 2:08 PM, Jonathan Thornburg
jth...@astro.indiana.edu wrote:
 Web browsers scare me: they're huge pieces of code, un-audited, they
 have embedded Turing-complete interpreters, they live in a horribly
 imsecure environment,

[...snip...]


 Are there other practical ways of securing an OpenBSD web browser?
 [I'm afraid just say no fails the practical test. :( ]


one practical thing I'd love to see is for someone to port the Quark
web browser:
http://goto.ucsd.edu/quark/

I've no idea if it's good enough for practical use, but it seems like
an interesting piece of work.

Re: make does try BSDmakefile anymore?

[Daniel Dickman]

yep, it's intended: see:
https://www.mail-archive.com/source-changes@openbsd.org/msg54858.html

On Tue, Oct 28, 2014 at 4:56 PM, Carsten Kunze carsten.ku...@arcor.de wrote:
 Hello,

 in OpenBSD 5.5 make did try makefiles in order BSDmakefile - makefile - 
 Makefile.

 In Current BSDmakefile is not tried anymore, at least not with highest 
 priority.  Is this intended?

 Carsten

Re: Why .cshrc and .profile in / ?

[Daniel Dickman]

On Sun, Oct 19, 2014 at 6:32 PM, worik worik.stan...@gmail.com wrote:
 In a fresh(ish) OpenBSD installation I note .cshrc and .profile in /.

 Why?


Not sure there's an answer but it was discussed at least one time before:
http://marc.info/?t=11910307971r=1w=2

Re: Real time programming in OpenBSD

[Daniel Dickman]

 On Tue, Sep 9, 2014 at 4:30 PM, Matti Karnaattu mkarnaa...@gmail.com wrote:
 Hello,
 
 Is it possible to dedicate CPU core to process?

This thread may or may not be useful to read over:
http://marc.info/?t=13588288892r=1w=1

 
 What I'm looking for is simple way to take advantage of high quality and
 secure code base of OpenBSD to use in real time/embedded applications.
 If this trick can be achived, it is simple to use OpenBSD as platform
 when critical parts of software can run on own CPU core and rest of the
 software can developed conventional means.

real time/embedded is pretty broad. I would encourage you to create a test 
setup to see how things work for you. Also if you were to provide more 
specifics about your goals, others may have more input.

to me embedded means resource (memory/disk) constrained for which I feel like 
OpenBSD is quite well suited.

On the other for hard/soft hard real-time I might look elsewhere.

 
 If this can be done, or this kind of feature may be noted and put to
 roadmap, I may have motivations to audit time requirements of library
 functions etc. and formally verify parts of the system.

I would be very interested in any effort to formally verify parts of the 
system. Can you give more details about what tools/techniques you have in mind?

Re: Real time programming in OpenBSD

[Daniel Dickman]

On Tue, Sep 9, 2014 at 7:29 PM, Matti Karnaattu mkarnaa...@gmail.com wrote:
Also if you were to provide more specifics about your goals, others may
have more input.

 At the moment I'm looking hobby project to maintain/improve my skills
 developing open source software and my goal is to develop/improve some
 open source component(s) to be suitable on safety critical use.

hobby and safety critical don't often go together. if you just
want to improve your skills i say go for it but aiming for safety
critical is a high bar to achieve.

But if you're really looking to do safety critical, which industry are
you going to target? is it aviation (hope you're well versed in
DO-178C), automotive (you've looked over ISO 26262 and MISRA C,
right?) nuclear, medical? something else? Not exactly light reading or
easy to achieve...


 What I need is some place to start, and starting point is to find
 developer community whose interest is quality code, sharing some same
 values and suitable platform.

Well, if a POSIX-like platform that pays attention to detail is one of
your goals, then OpenBSD is one of the cleanest places to start in my
biased opinion.


On the other for hard/soft hard real-time I might look elsewhere

 I'm looking possibility to isolate process on own CPU core because when
 looking from safety perspective, it is bad thing if some other process
 can jam CPU. Memory and hard drive isolation are easy tasks but if OS
 have possibility to isolate CPU too, that opens new possibilities.

 If this can be done, it is not long way to improve real time
 capabilities.

I'm not sure I agree that memory isolation is an easy task. OpenBSD
includes so many mitigation strategies against memory corruption for a
reason. See:
http://www.openbsd.org/security.html


 Not sure yet am I looking from right place. I just LOVE to browse
 OpenBSD source tree. It is clean in many ways, simple and I have found
 it to be realiable. However, it is unclear what are interests of OpenBSD
 developers and where project is heading.

These are listed on the interwebs:
http://www.openbsd.org/goals.html


 I consider that going deep kernel internals is out of scope for my
 interests so some developer hacking kernel every week should have
 interests to enable OpenBSD suitable for safety programming. Otherwise I
 have to look elsewhere.

The only person who will mold things around your interests is *you*.


Can you give more details about what tools/techniques you have in mind?

 Formal specifications defined with modified condition/decision coverage,
 model checking, automated theorem proving etc. To get that point, I have
 to use heavy static analysis to clean code to the point that it can be
 tested
 thoroughly.

Ah, so MC/DC makes me think you're interested in DO-178B/C. Ok, but
this is a somewhat questionable/controversial technique, no?

Interactive theorem proving is used heavily in sel4 as far as I know,
so that might be a more interesting place for you to look rather than
OpenBSD. It's pretty interesting work and it's open source.

Static analysis, on the other hand, has been used extensively on the
OpenBSD code base over the years with some good success. More work
could certainly be done on this front though. Patches addressing bugs
found through static analysis are always welcome.


 OpenBSD is aiming security and using proactive methods + code auditing
 to achive that, but proving that some pieces of code are correct raises bar.
 Zero defects means zero security holes.

Sure formal methods could help. If you do something using formal
methods then by all means, feel to submit patches. If you stay on this
list long enough you'll learn that people consider talk to be cheap...

And remember just because you've formally proved some piece of code is
free of buffer overflows doesn't mean you've proved there are no
security holes.

Re: Seagate ST3250310AS not recognized

[Daniel Dickman]

Hi Charlie. Bit of a shot in the dark. what sata ports are on the motherboard? 
can you switch the ports the hard drive is connected to? i have a machine with 
a similar problem but things work if I connect the hard drive to the sata 2 
port instead of the sata 3 port.

 On Mar 26, 2014, at 4:59 PM, Charlie Farinella 
 cfarine...@appropriatesolutions.com wrote:
 
 I'm trying to install OpenBSD 5.4 on a Dell Vostro 400, it's several years 
 old but not ancient.  4GB RAM, 250GB Seagate ST3250310AS hard drive.  The 
 installation goes normally until it tries to find the hard drive and then 
 tells me no hard drive is available.  
 
 I've wiped the drive (it had ESXi on it before), repartitioned it, 
 unpartitioned it, installed Linux, installed FreeBSD all without problem, but 
 no matter what I do to it, OpenBSD won't see it.
 
 I would really like to get this working so any suggestions or guidance is 
 very much appreciated.
 
 Thanks,
 
 --charlie
 
 --
 Charles Farinella
 Systems Administrator
 Appropriate Solutions, Inc.
 603-924-6079

Re: Help on understanding mbr.S

[Daniel Dickman]

The 1: is the target for the preceding ljmp instruction. This is a local
label. Reference here:
http://sourceware.org/binutils/docs/as/Symbol-Names.html#Symbol-Names

The reason the ljmp is needed in the first place is because In real mode there
are multiple ways to refer to the same memory address. The mbr does a ljmp
early on to set the real mode segment:offset to known values. See:
http://wiki.osdev.org/MBR_%28x86%29#Initial_Environment

What are you trying to do though? Working with x86 in real mode and dealing
with ancient PC conventions is probably not the easiest place to start.

Re: Building a High-performance Computing Cluster Using OpenBSD

[Daniel Dickman]

 Could anybody kindly point me to any literature regarding
 building a high-performance computing cluster using OpenBSD. I am not
 interested in FreeBSD and NetBSD related papers on this topics. I can
 find them easily. I am specifically interested in OpenBSD.
 Applications I am planning to run are related to Bifurcation Theory.

You'll probably want to provide just a bit more detail about what you
have in mind. But you can take a look at devel/lam and
sysutils/clusterit if you haven't already...

Re: ath AR5424 support

[Daniel Dickman]

 1) Most of the code I'm using is from Linux driver which is AFAIK GPL'ed code.
Is this a problem?

Why do you think the code is GPL'ed? What driver did you look at? Some
of the atheros code in the linux kernel comes from OpenBSD. For
example:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/net/wireless/ath/ath5k/ath5k.h;h=6a2a967621cc1523aadbad93a22e9edc4382;hb=HEAD

Note the copyright at the top:
Copyright (c) 2004-2007 Reyk Floeter r...@openbsd.org

Not to mention the non-GPL license that follows...

 2) I know nothing about wireless cards and my code is probably doing very
stupid things.  This means that I will not be able to provide any kind of
support to it.

I'd imagine a dmesg with and without your patch would no doubt be
helpful to start...

Re: Lastet supported jdk on OpenBSD

[Daniel Dickman]

See this link:
http://openbsd.org/faq/faq8.html#Programming

On 5/16/08, John Nietzsche [EMAIL PROTECTED] wrote:
 Dear users,

 i would like to add support for java on my 4.3 openbsd desktop. Has
 anybody already done so? May you point a url where i could download
 the package(s) from?

 Thanks in advance.

patch for mkhybrid man page

[Daniel Dickman]

Here's a patch for the mkhybrid man page:
http://dickman.org/openbsd/mkhybrid_man_update.patch

Changes are as follows:
- remove references to outdated cd burning packages and non-working urls
- update the url for the creator/type database to a working link
- spelling fixes

Re: patch for mkhybrid man page

[Daniel Dickman]

  Here's a patch for the mkhybrid man page:
  http://dickman.org/openbsd/mkhybrid_man_update.patch
 
  Changes are as follows:
  - remove references to outdated cd burning packages and non-working urls
  - update the url for the creator/type database to a working link
  - spelling fixes

 general policy is, if it's 3rd party software, please check your fixes
 against the latest source, and send your fixes upstream.

 jmc


What would be considered upstream for mkhybrid? mkisofs (which
mkhybrid seems to be based on) is now part of the cdrtools package
(http://cdrecord.berlios.de/private/cdrecord.html). And as
announced[1] while mkisofs is still GPL, it seems to depend on libscg
which is licensed under Sun's CDDL.

[1] ftp://ftp.berlios.de/pub/cdrecord/alpha/AN-2.01.01a09

acpi/ehci/pcibios broken on Sony VGN-FZ145E

[Daniel Dickman]

Just installed a recent OpenBSD snapshot (May25) on my brand new Sony
VGN-FZ145E. Main issues seem to be in the following areas which must
all be disabled to boot
- acpi
- ehci
- pcibios

Happy to test any patches to try to fix these issues...

The very bottom of the email shows the error when each of the above is
enabled, but first a successful boot dmesg with all 3 disabled:


OpenBSD 4.1-current (GENERIC) #178: Fri May 25 03:22:20 MDT 2007
   [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz (GenuineIntel
686-class) 1.80 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR
cpu0: unknown Core FSB_FREQ value 2 (0x4288)

--- new processor. Needs an FSB_FREQ to be added. Happy to provide a
patch if someone could point me to the right value to use.

real mem  = 2137419776 (2038MB)
avail mem = 1943977984 (1853MB)
using 4278 buffers containing 106995712 bytes (104488K) of memory
User Kernel Config
UKC disable pcibios
305 pcibios0 disabled
UKC disable ehci
137 ehci* disabled
138 ehci* disabled
UKC quit
Continuing...
mainbus0 (root)
bios0 at mainbus0: AT/286+ BIOS, date 04/03/07, BIOS32 rev. 0 @
0xfdbd0, SMBIOS rev. 2.4 @ 0xdc010 (17 entries)
bios0: Sony Corporation VGN-FZ145E
pcibios at bios0 function 0x1a not configured
bios0: ROM list: 0xc/0xee00! 0xdc000/0x4000! 0xe/0x1800!
acpi at mainbus0 not configured
cpu0 at mainbus0
cpu0: EST: unknown system bus clock
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 vendor Intel, unknown product 0x2a00 rev 0x0c

-- Mobile PM965/GM965/GL960 Memory Controller Hub

vga1 at pci0 dev 2 function 0 vendor Intel, unknown product 0x2a02
rev 0x0c: can't map aperture
: AGP GART

-- Mobile GM965/GL960 Integrated Graphics Controller

wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
vendor Intel, unknown product 0x2a03 (class display subclass
miscellaneous, rev 0x0c) at pci0 dev 2 function 1 not configured

-- Mobile GM965/GL960 Integrated Graphics Controller

uhci0 at pci0 dev 26 function 0 Intel 82801H USB rev 0x03: irq 5
uhci1 at pci0 dev 26 function 1 Intel 82801H USB rev 0x03: irq 11
Intel 82801H USB rev 0x03 at pci0 dev 26 function 7 not configured
azalia0 at pci0 dev 27 function 0 Intel 82801H HD Audio rev 0x03: irq 11
azalia0: host: High Definition Audio rev. 1.0
azalia0: codec: 0x8384/0x7662 (rev. 2.1), HDA version 1.0
azalia0: codec: 0x14f1/0x2c06 (rev. 0.0), HDA version 1.0
azalia0: codec[1]: No support for modem function groups
azalia0: codec[1]: No audio function groups
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 Intel 82801H PCIE rev 0x03
pci1 at ppb0 bus 2
ppb1 at pci0 dev 28 function 1 Intel 82801H PCIE rev 0x03
pci2 at ppb1 bus 4
ppb2 at pci0 dev 28 function 2 Intel 82801H PCIE rev 0x03
pci3 at ppb2 bus 6
vendor Intel, unknown product 0x4229 (class network subclass
miscellaneous, rev 0x61) at pci3 dev 0 function 0 not configured

-- PRO/Wireless 4965 AG or AGN Network Connection

ppb3 at pci0 dev 28 function 4 Intel 82801H PCIE rev 0x03
pci4 at ppb3 bus 8
mskc0 at pci4 dev 0 function 0 Marvell Yukon 88E8036 rev 0x16,
Yukon-2 FE (0x1): irq 5
msk0 at mskc0 port A, address xx:xx:xx:xx:xx:xx
eephy0 at msk0 phy 0: Marvell 88E3082 10/100 PHY, rev. 3
ukphy0 at msk0 phy 3: Generic IEEE 802.3u media interface, rev. 0: OUI
0x121012, model 0x0004
ukphy0: no media present
ukphy1 at msk0 phy 4: Generic IEEE 802.3u media interface, rev. 0: OUI
0x020802, model 0x0002
ukphy2 at msk0 phy 5: Generic IEEE 802.3u media interface, rev. 0: OUI
0x020802, model 0x0002
ukphy3 at msk0 phy 6: Generic IEEE 802.3u media interface, rev. 0: OUI
0x024c02, model 0x0013
ukphy4 at msk0 phy 7: Generic IEEE 802.3u media interface, rev. 0: OUI
0x020802, model 0x0002
uhci2 at pci0 dev 29 function 0 Intel 82801H USB rev 0x03: irq 10
uhci3 at pci0 dev 29 function 1 Intel 82801H USB rev 0x03: irq 10
uhci4 at pci0 dev 29 function 2 Intel 82801H USB rev 0x03: irq 7
Intel 82801H USB rev 0x03 at pci0 dev 29 function 7 not configured
ppb4 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0xf3
pci5 at ppb4 bus 9
cbb0 at pci5 dev 3 function 0 TI PCIXX12 CardBus rev 0x00: irq 5
vendor TI, unknown product 0x803a (class serial bus subclass
Firewire, rev 0x00) at pci5 dev 3 function 1 not configured

-- PCIxx12 OHCI Compliant IEEE 1394 Host Controller

TI PCIXX12 Multimedia Card Reader rev 0x00 at pci5 dev 3 function 2
not configured
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 10 device 0 cacheline 0x10, lattimer 0x20
pcmcia0 at cardslot0
pcib0 at pci0 dev 31 function 0 vendor Intel, unknown product 0x2815 rev 0x03

-- 82801HEM (ICH8M) LPC Interface Controller

pciide0 at pci0 dev 31 function 1 vendor Intel, unknown product
0x2850 rev 0x03: DMA (unsupported), channel 0 configured to
compatibility, channel 1 

Re: accessing the MBR in multibooted systems?

[Daniel Dickman]

On 5/31/07, James Hartley [EMAIL PROTECTED] wrote:

Section 4.8 of the FAQ discusses how to capture the PBR for multibooting
with dd:

# dd if=/dev/rwd0a of=openbsd.pbr bs=512 count=1

Two questions.

* For stand-alone installations, is the PBR the same thing as the MBR?

* More importantly, how can I use dd to access the MBR in a multibooted
system of Vista  OpenBSD?

Thanks for any insight.




I can only guess your end goal is to be able to multiboot Vista and
OpenBSD. That's the setup I have on my machine. It's a little tricky,
but here's basically how I did it:

1) install Vista on a primary partition first.
2) install OpenBSD on another primary partition, make sure to keep the
Vista MBR though. (in another words be careful what you're doing
during the fdisk stage of OBSD installation).

At this point you have both OS's on your machine but can only boot
into Vista. So now:
1) Use windows dd from Vista to copy the PBR from OpenBSD onto your
windows partition (This app can be found here:
http://www.chrysocome.net/downloads/dd-0.5.zip)
2) Note one tricky thing here. When you open the Vista command console
to run dd you must right click and select Run as administrator.
3) Use the Vista bcdedit command to set OpenBSD as a boot option under
Vista. Here's the best tutorial I've seen on the topic
(http://www.bsdforums.org/forums/showthread.php?t=48405).

Note that if you don't know what you're doing you can very easily lose
ALL your data with the smallest of mistakes, so be sure not to try
this on a machine that has data you care about unless you have
everything you need backup up.

Enjoy.

getting ^L to clear the screen?

[Daniel Dickman]

Does anyone know how to bind ^L to clear the screen in a default 3.9 
installation? I'd prefer to not have to change to bash if I don't have to...

OpenBSD/i386 3.9 install doesn't boot

[Daniel Dickman]

Hello,

I just received my newly purchased copy of OpenBSD/i386 3.9 and tried to install 
it on my Compaq R3140US laptop. Unfortunately it freezes when booting the 
install CD (see below for output). I searched on the web for a solution, but the 
only thing I found was Jeff's extremely similar looking problem with OpenBSD 3.5:


http://marc.theaimsgroup.com/?l=openbsd-bugsm=108841644430006w=2

I also tried -current, but got the exact same problem. Any ideas on how I can 
diagnose this and hopefully get OpenBSD installed?


Thanks for any help,
Daniel




booting cd0a:/3.9/i386/bsd.rd: 4435508+740284 [52+155376+141982]=0x538528
entry point at 0x100120


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


OpenBSD 3.9 (RAMDISK_CD) #1025: Thu Mar  2 02:43:29 MST 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: AMD Athlon(tm) 64 Processor 3000+ (AuthenticAMD 686-class, 1024KB L2 
cache) 798 MHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFL-USH,

MMX,FXSR,SSE,SSE2
real mem  = 535863296 (523304K)
avail mem = 483098624 (471776K)
using 4278 buffers containing 26894336 bytes (26264K) of memory
mainbus0 (root)
bios0 at mainbus: AT/286+(18) BIOS, date 12/23/04, BIOS32 rev. 0 @ 0xfd750
pcibios0 at bios0: rev. 2.1 @ 0xfd750/0x8b0
pcibios0: PCI IRQ Routing Table rev. 1.0 @ 0xfdf10/208 (11 entries)
pcibios0: no compatible PCI ICU found: ICU vendor 0x10de product 0x00d0
pcibios0: Warning, unable to fix up PCI interrupt routing
pcibios0: PCI bus #4 is the last bus
bios0: ROM list: 0xc000/0xfc00 0xd/0x4000! 0xd4000/0x1000

Re: OpenBSD/i386 3.9 install doesn't boot

[Daniel Dickman]

Terrific! disable pcibios worked for me. Here's my dmesg in case it's at all 
useful. Is there any way to include this automatic workaround in a future 
release? I'm not skilled enough to try to code something up myself, but I'd be 
happy to do any testing or provide any further info.




OpenBSD 3.9 (GENERIC) #617: Thu Mar  2 02:26:48 MST 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Athlon(tm) 64 Processor 3000+ (AuthenticAMD 686-class, 1024KB L2 
cache) 798 MHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2

cpu0: AMD Powernow: TS FID VID TTP
real mem  = 535863296 (523304K)
avail mem = 481943552 (470648K)
using 4278 buffers containing 26894336 bytes (26264K) of memory
User Kernel Config
UKC disable pcibios
277 pcibios0 disabled
UKC quit
Continuing...
mainbus0 (root)
bios0 at mainbus0: AT/286+(18) BIOS, date 12/23/04, BIOS32 rev. 0 @ 0xfd750
pcibios at bios0 function 0x1a not configured
bios0: ROM list: 0xc/0xfc00 0xd/0x4000! 0xd4000/0x1000
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 NVIDIA nForce3 PCI Host rev 0xa4
pcib0 at pci0 dev 1 function 0 NVIDIA nForce3 ISA rev 0xa6
nviic0 at pci0 dev 1 function 1 NVIDIA nForce3 SMBus rev 0xa4
iic0 at nviic0
iic1 at nviic0
ohci0 at pci0 dev 2 function 0 NVIDIA nForce3 USB rev 0xa5: irq 11, version 
1.0, legacy support

usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: NVIDIA OHCI root hub, rev 1.00/1.00, addr 1
uhub0: 3 ports with 3 removable, self powered
ohci1 at pci0 dev 2 function 1 NVIDIA nForce3 USB rev 0xa5: irq 10, version 
1.0, legacy support

usb1 at ohci1: USB revision 1.0
uhub1 at usb1
uhub1: NVIDIA OHCI root hub, rev 1.00/1.00, addr 1
uhub1: 3 ports with 3 removable, self powered
ehci0 at pci0 dev 2 function 2 NVIDIA nForce3 USB rev 0xa2: irq 10
usb2 at ehci0: USB revision 2.0
uhub2 at usb2
uhub2: NVIDIA EHCI root hub, rev 2.00/1.00, addr 1
uhub2: 6 ports with 6 removable, self powered
auich0 at pci0 dev 6 function 0 NVIDIA nForce3 AC97 rev 0xa2: irq 11, nForce3 
AC97
ac97: codec id 0x41445374 (Analog Devices AD1981B)
ac97: codec features headphone, 20 bit DAC, No 3D Stereo
audio0 at auich0
NVIDIA nForce3 Modem rev 0xa2 at pci0 dev 6 function 1 not configured
pciide0 at pci0 dev 8 function 0 NVIDIA nForce3 IDE rev 0xa5: DMA, channel 0 
configured to compatibility, channel 1 configured to compatibility

wd0 at pciide0 channel 0 drive 0: ST980825A
wd0: 16-sector PIO, LBA48, 76319MB, 156301488 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: TOSHIBA, ODD-DVD SD-R6252, 1A14 SCSI0 5/cdrom 
removable

cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
ppb0 at pci0 dev 10 function 0 NVIDIA nForce3 PCI-PCI rev 0xa2
pci1 at ppb0 bus 2
rl0 at pci1 dev 1 function 0 Realtek 8139 rev 0x10: irq 11, address 
00:02:3f:22:d2:96

rlphy0 at rl0 phy 0: RTL internal PHY
Broadcom BCM4306 rev 0x03 at pci1 dev 2 function 0 not configured
cbb0 at pci1 dev 4 function 0 Texas Instruments PCI1620 CardBus rev 0x01: irq 
11
cbb1 at pci1 dev 4 function 1 Texas Instruments PCI1620 CardBus rev 0x01: irq 
11
Texas Instruments PCI1620 Misc rev 0x01 at pci1 dev 4 function 2 not 
configured
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 0 device 0 cacheline 0x8, lattimer 0x40
pcmcia0 at cardslot0
cardslot1 at cbb1 slot 1 flags 0
cardbus1 at cardslot1: bus 0 device 0 cacheline 0x8, lattimer 0x40
pcmcia1 at cardslot1
ppb1 at pci0 dev 11 function 0 NVIDIA nForce3 PCI-PCI rev 0xa4
pci2 at ppb1 bus 1
vga1 at pci2 dev 0 function 0 NVIDIA GeForce4 420 Go 32M rev 0xa3
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pchb1 at pci0 dev 24 function 0 AMD AMD64 HyperTransport rev 0x00
pchb2 at pci0 dev 24 function 1 AMD AMD64 Address Map rev 0x00
pchb3 at pci0 dev 24 function 2 AMD AMD64 DRAM Cfg rev 0x00
pchb4 at pci0 dev 24 function 3 AMD AMD64 Misc Cfg rev 0x00
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
viasio0 at isa0 port 0x4e/2: VT1211 rev 0x02: HM: not activated WDG: not 
activated
npx0 at isa0 port 0xf0/16: using exception 16
biomask ef7d netmask ef7d ttymask 
pctr: user-level cycle counter enabled
dkcsum: wd0 matches BIOS drive 0x80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302

Marco Peereboom wrote:

at the boot prompt type -c
disable pcibios
quit

try that.

On Mon, May 22, 2006 at 06:31:43PM -0400, Daniel Dickman wrote:


Hello,

I just received my newly purchased copy of OpenBSD/i386 3.9 and tried to 
install it on my Compaq

help switching from linux to openbsd

[Daniel Dickman]

Hello, until recently I've been a Linux user but have decided to get my feet 
wet with OpenBSD. I had a few basic questions that I wasn't able to solve after 
reading the FAQ and doing some web searches and was hoping someone could point 
me in the right direction. (I'm running a freshly built 3.8-current on an amd64 
machine). In any case, here are the things I'm trying to do:
 
1. I'd like to switch consoles with Alt-FN instead of Ctrl-Alt-FN. How can 
I do that? (The main reason is that I prefer to be able to switch consoles with 
one hand and using the Ctrl key is a bit awkward for me to do without using 
both hands.)
 
2. My mouse doesn't seem to work under X. I have a USB mouse and see the 
following message in dmesg: uhub0: device problem, disabling port 1 and not 
sure if this is the indicating the problem. In any case, I've enclosed the full 
dmesg below and I'm happy to give out any more information that's needed.
 
Thanks very much for any help,
Daniel
 
 
OpenBSD 3.8-current (GENERIC) #0: Mon Jan 16 19:21:53 EST 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 938012672 (916028K)
avail mem = 791314432 (772768K)
using 22937 buffers containing 94007296 bytes (91804K) of memory
mainbus0 (root)
cpu0 at mainbus0: (uniprocessor)
cpu0: AMD Athlon(tm) 64 Processor 3000+, 1791.09 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 
16-way L2 cache
cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
pci0 at mainbus0 bus 0: configuration mode 1
pchb0 at pci0 dev 0 function 0 ATI RS480 Host rev 0x00
ppb0 at pci0 dev 1 function 0 ATI RS480 PCIE rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 5 function 0 ATI Radeon XPRESS 200 rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pciide0 at pci0 dev 17 function 0 ATI IXP400 SATA rev 0x00: DMA
pciide0: using irq 11 for native-PCI interrupt
pciide1 at pci0 dev 18 function 0 ATI IXP400 SATA rev 0x00: DMA
pciide1: using irq 10 for native-PCI interrupt
pciide1: port 0: device present, speed: 1.5Gb/s
wd0 at pciide1 channel 0 drive 0: ST3160827AS
wd0: 16-sector PIO, LBA48, 152627MB, 312581808 sectors
wd0(pciide1:0:0): using BIOS timings, Ultra-DMA mode 6
ohci0 at pci0 dev 19 function 0 ATI IXP400 USB rev 0x00: irq 10, version 1.0, 
legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: ATI OHCI root hub, rev 1.00/1.00, addr 1
uhub0: 4 ports with 4 removable, self powered
ohci1 at pci0 dev 19 function 1 ATI IXP400 USB rev 0x00: irq 10, version 1.0, 
legacy support
usb1 at ohci1: USB revision 1.0
uhub1 at usb1
uhub1: ATI OHCI root hub, rev 1.00/1.00, addr 1
uhub1: 4 ports with 4 removable, self powered
ehci0 at pci0 dev 19 function 2 ATI IXP400 USB2 rev 0x00: irq 10
usb2 at ehci0: USB revision 2.0
uhub2 at usb2
uhub2: ATI EHCI root hub, rev 2.00/1.00, addr 1
uhub2: 8 ports with 8 removable, self powered
ATI IXP400 SMBus rev 0x04 at pci0 dev 20 function 0 not configured
pciide2 at pci0 dev 20 function 1 ATI IXP400 IDE rev 0x00: DMA, channel 0 
configured to compatibility, channel 1 configured to compatibility
atapiscsi0 at pciide2 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: HL-DT-ST, RW/DVD GCC-4480B, 1.02 SCSI0 5/cdrom 
removable
cd0(pciide2:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 2
pcib0 at pci0 dev 20 function 3 ATI IXP400 ISA rev 0x00
ppb1 at pci0 dev 20 function 4 ATI IXP400 PCI rev 0x00
pci2 at ppb1 bus 2
Texas Instruments ACX100A rev 0x00 at pci2 dev 0 function 0 not configured
rl0 at pci2 dev 3 function 0 Realtek 8139 rev 0x10: irq 5, address 
00:13:d3:09:d0:99
rlphy0 at rl0 phy 0: RTL internal phy
VIA VT6306 FireWire rev 0x80 at pci2 dev 4 function 0 not configured
auixp0 at pci0 dev 20 function 5 ATI IXP400 AC97 rev 0x00: irq 3
auixp0: soft resetting aclink
pchb1 at pci0 dev 24 function 0 AMD AMD64 HyperTransport rev 0x00
pchb2 at pci0 dev 24 function 1 AMD AMD64 Address Map rev 0x00
pchb3 at pci0 dev 24 function 2 AMD AMD64 DRAM Cfg rev 0x00
pchb4 at pci0 dev 24 function 3 AMD AMD64 Misc Cfg rev 0x00
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
spkr0 at pcppi0
sysbeep0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
uhub0: device problem, disabling port 1
dkcsum: wd0 matches BIOS drive 0x80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
ac97: codec id 0x414c4780 (Avance Logic ALC658)
ac97: codec features 20 bit DAC, 18 bit ADC, No 3D Stereo
audio0 at auixp0