Re: OpenBSD on IBM Power
On Mon, Apr 14, 2014 at 2:48 AM, Zeljko Jovanovic < zelj...@tesla.rcub.bg.ac.rs> wrote: > On 09.04.2014. 18:24, Fil Di Noto wrote: > >> Is there any hope of OpenBSD running on IBM Power hardware (System P, >> LPAR) in the future? >> > ... > > OS on that hardware without cooperation from IBM? I don't see any >> Linux distros that do not have a relationship with IBM that run on >> Power. >> > > Slackware Linux has an IBM port, although it has not been updated for > several years now: http://www.slack390.org > > I am not sure what are the differences between largest IBM machines > (System Z, formerly known as System/390), and smaller systems such as > System P. But I am sure that Slackware project certainly does not have a > relationship with any company. > > By the way, as you probably know, Slackware is the oldest surviving Linux > distribution, and adversises as the most "UNIX-like" among Linuxes. Also, > its /etc layout is of BSD type, not System V like in other Linux > distribution. The overall "look and feel" after instalation is similar to > OpenBSD. Even the BSD games packages, with fortune program enabled by > default is there. :) > The question is for how long. Especially RedHat is pushing a lot of stuff in a way which even MS need to yet discover (:-)). And crap like systemd and similar is just a start. Man that stupid stuff is not even able to boot automatically system which is supposed to mount automatically with filesystem residing on LVM (OpenSuse 12.x). You add aditional disk, create LVM on it, some ext filesystem, put it in /etc/fstab, mount.oo works.. till reboot which always end in emergency mode where you need to comment that new entry in /etc/fstab, reboot, manually start LVM service (!), manually mount new entry in /etc/fstab again. WHAT AN IMPROVEMENT ! ' And I'm describing just stuff which admins are and were doing for years on Linux. Simple new disk/partition with LVM. Stuff which was not needed to hack somewhat around after reboot just to get system back working. Too much bored to look at that shit in details, but seems like it's not able to start services in proper order and completely breaking functional thing like simple /etc/fstab which was working for such long time in Unix world.
Re: OpenBSD on IBM Power
On Mon, Apr 14, 2014 at 2:48 AM, Zeljko Jovanovic < zelj...@tesla.rcub.bg.ac.rs> wrote: > On 09.04.2014. 18:24, Fil Di Noto wrote: > >> Is there any hope of OpenBSD running on IBM Power hardware (System P, >> LPAR) in the future? >> > ... > > OS on that hardware without cooperation from IBM? I don't see any >> Linux distros that do not have a relationship with IBM that run on >> Power. >> > > Slackware Linux has an IBM port, although it has not been updated for > several years now: http://www.slack390.org > > I am not sure what are the differences between largest IBM machines > (System Z, formerly known as System/390), and smaller systems such as > System P. But I am sure that Slackware project certainly does not have a > relationship with any company. > > By the way, as you probably know, Slackware is the oldest surviving Linux > distribution, and adversises as the most "UNIX-like" among Linuxes. Also, > its /etc layout is of BSD type, not System V like in other Linux > distribution. The overall "look and feel" after instalation is similar to > OpenBSD. Even the BSD games packages, with fortune program enabled by > default is there. :)
Re: -current not building
It is a live development tree: 118 2014/03/26 180 2014/03/27 81 2014/03/28 57 2014/03/29 63 2014/03/30 97 2014/03/31 65 2014/04/01 45 2014/04/02 77 2014/04/03 32 2014/04/04 34 2014/04/05 42 2014/04/06 74 2014/04/07 47 2014/04/08 47 2014/04/09 46 2014/04/10 51 2014/04/11 39 2014/04/12 86 2014/04/13 That is the daily commit count. If we had better network, we would get data to out to the fanout mirrors faster. It is what it is. Work with it. >Guess I'm missing the point, Downloaded src from scratch and now >getting a different error (on two separate systems) when trying to >build userland: > >mandoc -Tlint -Wfatal /usr/src/usr.sbin/ntpd/ntpctl.8 >===> usr.sbin/openssl >cc -O2 -pipe -DMONOLITH -DTERMIOS -DANSI_SOURCE -DOPENSSL_NO_RC5 >-DOPENSSL_NO_SSL2 -I/usr/src/usr.sbin/openssl/../../lib/libssl/src >-c /usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c >/usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c:72: >error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cb' >/usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c: In >function 'verify_main': >/usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c:97: >error: 'cb' undeclared (first use in this function) >/usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c:97: >error: (Each undeclared identifier is reported only once >/usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c:97: >error: for each function it appears in.) >/usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c: At top level: >/usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c:311: >error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cb' >*** Error 1 in usr.sbin/openssl (:87 'verify.o') >*** Error 1 in usr.sbin (:48 'all') >*** Error 1 in . (:48 'all') >*** Error 1 in /usr/src (Makefile:89 'build') > >These things built -current fine a week ago. > >Chris > >On Sun, Apr 13, 2014 at 4:12 PM, Theo de Raadt wrote: >> Get new code. A shared library was not cranked correctly. >> >> >>> -current not currently building: >>> == >>> mandoc -Tlint -Wfatal /usr/src/usr.sbin/ldapd/ldapd.conf.5 >>> cc -o ldapd ber.o log.o control.o util.o ldapd.o ldape.o conn.o >>> attributes.o namespace.o btree.o filter.o search.o parse.o auth.o >>> modify.o index.o ssl.o ssl_privsep.o validate.o uuid.o schema.o >>> imsgev.o syntax.o matching.o -levent -lssl -lcrypto -lz -lutil >>> /usr/lib/libssl.so.22.0: undefined reference to `CRYPTO_memcmp' >>> collect2: ld returned 1 exit status >>> *** Error 1 in usr.sbin/ldapd (:95 'ldapd') >>> *** Error 2 in usr.sbin (:48 'all') >>> *** Error 2 in . (:48 'all') >>> *** Error 2 in /usr/src (Makefile:89 'build') >>> ==
Re: very low audio volume on MacPro1,1
Apple machines tend to need gpio pin related quirks. If you include the output of 'pcidump -v' for the audio device it will help figure out which set of quirks your machine needs.
Re: OpenBSD on IBM Power
>There are a bunch of things that are needed for an OpenBSD port, >including at least: >1) Interest by a developer. Right. >2) Hardware in the developer's hand. Totall irrelevant. If there is interest, they will ask to get for it. >3) Availability of hardware for other developers at a reasonable price. >4) A user base to stimulate #1 I've seen this cycle a bunch of times. From what I've seen, above two points are completely irrelevant. You've missed a point. 3) Something unknown makes sure the developer has time. >If you disagree, go ahead, do the work to make it run, submit the code, >keep it running, and your reward will be seeing a new platform supported >by OpenBSD...as long as you do the work to keep it running. Wow, that >sounds really depressing when I put it that way. This doesn't help. It's like talking to me neighbour about changing oil.
Re: -current not building
We'd love to rsync the repository more real-time, but haven't got the bandwidth. And even if we did, there still would be moments between when you fetch, start a build. Hint to everyone: Fetch. Build. See error? re-fetch, rebuild. If it happens the 2nd time, then maybe... Do you understand it is a lot of noise? >OK, I'll try again. I do follow the source changes via gmane with a >newsreader but I think there's a bit of delay. > >Thanks. > >On Sun, Apr 13, 2014 at 11:27 PM, Ted Unangst wrote: >> On Sun, Apr 13, 2014 at 23:15, Chris Smith wrote: >>> Guess I'm missing the point, Downloaded src from scratch and now >>> getting a different error (on two separate systems) when trying to >>> build userland: >>> >>> mandoc -Tlint -Wfatal /usr/src/usr.sbin/ntpd/ntpctl.8 >>> ===> usr.sbin/openssl >>> cc -O2 -pipe -DMONOLITH -DTERMIOS -DANSI_SOURCE -DOPENSSL_NO_RC5 >>> -DOPENSSL_NO_SSL2 -I/usr/src/usr.sbin/openssl/../../lib/libssl/src >>> -c /usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c >>> /usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c:72: >>> error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cb' >> >>> These things built -current fine a week ago. >> >> If you're not subscribed to source-changes, you should be. And if you >> are, you should have seen a few dozen commits to libssl recently. >> >> Do you need to build current? Probably not. That's why we provide >> snapshots. >> >> Build errors that don't come with patches aren't very interesting >> because by the time you report it, somebody else will have found it >> and fixed it.
Re: -current not building
OK, I'll try again. I do follow the source changes via gmane with a newsreader but I think there's a bit of delay. Thanks. On Sun, Apr 13, 2014 at 11:27 PM, Ted Unangst wrote: > On Sun, Apr 13, 2014 at 23:15, Chris Smith wrote: >> Guess I'm missing the point, Downloaded src from scratch and now >> getting a different error (on two separate systems) when trying to >> build userland: >> >> mandoc -Tlint -Wfatal /usr/src/usr.sbin/ntpd/ntpctl.8 >> ===> usr.sbin/openssl >> cc -O2 -pipe -DMONOLITH -DTERMIOS -DANSI_SOURCE -DOPENSSL_NO_RC5 >> -DOPENSSL_NO_SSL2 -I/usr/src/usr.sbin/openssl/../../lib/libssl/src >> -c /usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c >> /usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c:72: >> error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cb' > >> These things built -current fine a week ago. > > If you're not subscribed to source-changes, you should be. And if you > are, you should have seen a few dozen commits to libssl recently. > > Do you need to build current? Probably not. That's why we provide > snapshots. > > Build errors that don't come with patches aren't very interesting > because by the time you report it, somebody else will have found it > and fixed it.
Re: -current not building
On Sun, Apr 13, 2014 at 23:15, Chris Smith wrote: > Guess I'm missing the point, Downloaded src from scratch and now > getting a different error (on two separate systems) when trying to > build userland: > > mandoc -Tlint -Wfatal /usr/src/usr.sbin/ntpd/ntpctl.8 > ===> usr.sbin/openssl > cc -O2 -pipe -DMONOLITH -DTERMIOS -DANSI_SOURCE -DOPENSSL_NO_RC5 > -DOPENSSL_NO_SSL2 -I/usr/src/usr.sbin/openssl/../../lib/libssl/src > -c /usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c > /usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c:72: > error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cb' > These things built -current fine a week ago. If you're not subscribed to source-changes, you should be. And if you are, you should have seen a few dozen commits to libssl recently. Do you need to build current? Probably not. That's why we provide snapshots. Build errors that don't come with patches aren't very interesting because by the time you report it, somebody else will have found it and fixed it.
Re: OpenBSD on IBM Power
Nick Holland wrote: There's a lot of reasons developers can be interested in particular hardware The P series are perfectly good systems for AIX, Linux, and i Series OS (OS400). They would also be fine for OpenBSD if there were any call for that, but in the IBM community, the open-source *nix niche was filled in the 1999 by IBM mutineers creating a Linux port. The technology spread from the 390 to the AS400 and the P series (which latter subsumed the AS400). All attempts to revisit the issue of *nix-on-IBM-big-iron have been spectacularly unsuccessful at gaining adherents, e.g., the excellent SOL390 (Open Solaris for mainframes) port was born only to die a lonely death. -- Jack Woehr # "We commonly say we have no time when, Box 51, Golden CO 80402 # of course, we have all that there is." http://www.softwoehr.com # - James Mason, _The Art of Chess_, 1905
Re: -current not building
Guess I'm missing the point, Downloaded src from scratch and now getting a different error (on two separate systems) when trying to build userland: mandoc -Tlint -Wfatal /usr/src/usr.sbin/ntpd/ntpctl.8 ===> usr.sbin/openssl cc -O2 -pipe -DMONOLITH -DTERMIOS -DANSI_SOURCE -DOPENSSL_NO_RC5 -DOPENSSL_NO_SSL2 -I/usr/src/usr.sbin/openssl/../../lib/libssl/src -c /usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c /usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c:72: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cb' /usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c: In function 'verify_main': /usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c:97: error: 'cb' undeclared (first use in this function) /usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c:97: error: (Each undeclared identifier is reported only once /usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c:97: error: for each function it appears in.) /usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c: At top level: /usr/src/usr.sbin/openssl/../../lib/libssl/src/apps/verify.c:311: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cb' *** Error 1 in usr.sbin/openssl (:87 'verify.o') *** Error 1 in usr.sbin (:48 'all') *** Error 1 in . (:48 'all') *** Error 1 in /usr/src (Makefile:89 'build') These things built -current fine a week ago. Chris On Sun, Apr 13, 2014 at 4:12 PM, Theo de Raadt wrote: > Get new code. A shared library was not cranked correctly. > > >> -current not currently building: >> == >> mandoc -Tlint -Wfatal /usr/src/usr.sbin/ldapd/ldapd.conf.5 >> cc -o ldapd ber.o log.o control.o util.o ldapd.o ldape.o conn.o >> attributes.o namespace.o btree.o filter.o search.o parse.o auth.o >> modify.o index.o ssl.o ssl_privsep.o validate.o uuid.o schema.o >> imsgev.o syntax.o matching.o -levent -lssl -lcrypto -lz -lutil >> /usr/lib/libssl.so.22.0: undefined reference to `CRYPTO_memcmp' >> collect2: ld returned 1 exit status >> *** Error 1 in usr.sbin/ldapd (:95 'ldapd') >> *** Error 2 in usr.sbin (:48 'all') >> *** Error 2 in . (:48 'all') >> *** Error 2 in /usr/src (Makefile:89 'build') >> ==
Re: OpenBSD on IBM Power
On 04/13/14 20:47, Zeljko Jovanovic wrote: > On 09.04.2014. 18:24, Fil Di Noto wrote: >> Is there any hope of OpenBSD running on IBM Power hardware (System P, >> LPAR) in the future? > ... >> OS on that hardware without cooperation from IBM? I don't see any >> Linux distros that do not have a relationship with IBM that run on >> Power. > > Slackware Linux has an IBM port, although it has not been updated for several > years now: http://www.slack390.org um. Linux kernel 2.4? Are you kidding me? dead dead dead. > I am not sure what are the differences between largest IBM machines (System > Z, > formerly known as System/390), and smaller systems such as System P. But I am > sure that Slackware project certainly does not have a relationship with any > company. > > By the way, as you probably know, Slackware is the oldest surviving Linux > distribution, and adversises as the most "UNIX-like" among Linuxes. Also, its > /etc layout is of BSD type, not System V like in other Linux distribution. > The > overall "look and feel" after instalation is similar to OpenBSD. Even the BSD > games packages, with fortune program enabled by default is there. :) There are a bunch of things that are needed for an OpenBSD port, including at least: 1) Interest by a developer. 2) Hardware in the developer's hand. 3) Availability of hardware for other developers at a reasonable price. 4) A user base to stimulate #1 There's not a lot of hardware out there to be had, not a lot of it in developer's hands, and what's there isn't overly cheap. And it probably won't do anything better than other hardware out there to stimulate developer interest, either. I've got a couple IBM Power machines -- one with the performance of maybe a iMac G3, the other with the performance of a single processor G5. I could put a second processor in it, IF I could find an IBM processor module for a price I was willing to pay ($5 might do it. $20, definitely not. "free" would be the only "definitely" for me). As I recall, some years ago, someone managed to use a NetBSD boot loader to boot an OpenBSD kernel on something akin to my G3-ish machine, and the bloody thing actually kinda came up (missing a lot of hw, but still). The problem is... so what? If I do something serious with either of these machines, my ability to get a spare /cheaply/ is low, and for a fraction of the price and power consumption, I can get a BETTER in every way i386 or amd64 system...or a scrap MacPPC system. There's a lot of reasons developers can be interested in particular hardware when pure logic might dictate that "mainstream Intel-ish is better" but I'm not seeing much about those IBM systems to make them overly lovable from either a purely rational or emotional standpoint. If you disagree, go ahead, do the work to make it run, submit the code, keep it running, and your reward will be seeing a new platform supported by OpenBSD...as long as you do the work to keep it running. Wow, that sounds really depressing when I put it that way. Nick.
Re: OpenBSD on IBM Power
On 09.04.2014. 18:24, Fil Di Noto wrote: Is there any hope of OpenBSD running on IBM Power hardware (System P, LPAR) in the future? ... OS on that hardware without cooperation from IBM? I don't see any Linux distros that do not have a relationship with IBM that run on Power. Slackware Linux has an IBM port, although it has not been updated for several years now: http://www.slack390.org I am not sure what are the differences between largest IBM machines (System Z, formerly known as System/390), and smaller systems such as System P. But I am sure that Slackware project certainly does not have a relationship with any company. By the way, as you probably know, Slackware is the oldest surviving Linux distribution, and adversises as the most "UNIX-like" among Linuxes. Also, its /etc layout is of BSD type, not System V like in other Linux distribution. The overall "look and feel" after instalation is similar to OpenBSD. Even the BSD games packages, with fortune program enabled by default is there. :)
Re: very low audio volume on MacPro1,1
On Sun, Apr 13, 2014 at 07:22:12PM -0400, Allan Streib wrote: > For what it's worth, I get the same low volume when I use the "speaker" > jack on the back of the computer. I've also verified that the speakers > themselves are working properly, using another audio source. OK. It was just the first thing I saw in your report. My apologies for the noise on my part, and the lack of same for your system.
Re: very low audio volume on MacPro1,1
Josh Grosse writes:
> I noticed this in your mixerctl results. It may be the root of the
> problem.
>
>> outputs.spkr_mute=on [ off on ]
>
> All other "mute" settings in your mixerctl results show as *off*.
I think what's going on here is that when I ran mixerctl I had my
speakers plugged in to the headphone (hp) jack on the front panel, which
causes the speaker output to be muted.
outputs.hp_sense=plugged [ unplugged plugged ]
outputs.spkr_muters=hp { hp }
I'm assuming that means that the headphones are sensed as being plugged
in, and this will cause the speaker output to mute.
For what it's worth, I get the same low volume when I use the "speaker"
jack on the back of the computer. I've also verified that the speakers
themselves are working properly, using another audio source.
Thanks,
Allan
Re: very low audio volume on MacPro1,1
On Sun, Apr 13, 2014 at 06:05:02PM -0400, Allan Streib wrote: > I'm running OpenBSD 5.5-current on a MacPro1,1. dmesg (complete below) > shows azalia Intel 6321ESB HD Audio with Realtek ALC885 codec. After > working through the FAQ I have managed to get a very low level of audio... I noticed this in your mixerctl results. It may be the root of the problem. > outputs.spkr_mute=on [ off on ] All other "mute" settings in your mixerctl results show as *off*.
very low audio volume on MacPro1,1
I'm running OpenBSD 5.5-current on a MacPro1,1. dmesg (complete below)
shows azalia Intel 6321ESB HD Audio with Realtek ALC885 codec. After
working through the FAQ I have managed to get a very low level of audio
but even using mixerctl to set outputs.master to the maximum level I get
barely audible volume from either the speaker or headphone. I have tried
enabling the hp_boost and spkr_boost options, which makes no difference.
Wondering if anything in the following stands out as a cause:
$ audioctl
name=HD-Audio
version=1.0
config=azalia0
encodings=slinear_le:16:2:1,slinear_le:20:4:1,slinear_le:24:4:1
properties=full_duplex,independent
full_duplex=0
fullduplex=0
blocksize=4160
hiwat=7
lowat=6
output_muted=0
monitor_gain=0
mode=
play.rate=48000
play.channels=1
play.precision=16
play.bps=2
play.msb=1
play.encoding=slinear_le
play.gain=255
play.balance=32
play.port=0x0
play.avail_ports=0x0
play.seek=0
play.samples=0
play.eof=0
play.pause=1
play.error=0
play.waiting=0
play.open=0
play.active=0
play.buffer_size=32768
play.block_size=4160
play.errors=0
record.rate=48000
record.channels=2
record.precision=16
record.bps=2
record.msb=1
record.encoding=slinear_le
record.gain=125
record.balance=32
record.port=0x0
record.avail_ports=0x0
record.seek=0
record.samples=0
record.eof=0
record.pause=0
record.error=0
record.waiting=0
record.open=0
record.active=0
record.buffer_size=65536
record.block_size=9600
record.errors=0
$ mixerctl -av
record.adc-0:1_mute=off [ off on ]
record.adc-0:1=125,125
record.adc-2:3_mute=off [ off on ]
record.adc-2:3=125,125
record.adc-4:5_mute=off [ off on ]
record.adc-4:5=125,125
record.dig-adc-0:1_sou=SPDIF-in [ SPDIF-in ]
inputs.mix_source=hp,line-in,beep,line { hp line-in beep line }
inputs.mix_hp=120,120
inputs.mix_line-in=120,120
inputs.mix_beep=120,120
inputs.mix_line=120,120
outputs.mix2=126,126
inputs.mix2_source=dac-2:3,mix { dac-2:3 mix }
outputs.mix3=192,192
inputs.mix3_source=dac-0:1,mix { dac-0:1 mix }
outputs.mix4=192,192
inputs.mix4_source=dac-4:5,mix { dac-4:5 mix }
outputs.mix5=192,192
inputs.mix5_source=dac-6:7,mix { dac-6:7 mix }
outputs.line_source=mix3 [ mix2 mix3 mix4 mix5 mix9 ]
outputs.line_mute=off [ off on ]
inputs.line=85,85
outputs.line_dir=output [ none output input input-vr0 input-vr50 input-vr80
input-vr100 ]
outputs.line_boost=off [ off on ]
outputs.hp_source=mix4 [ mix2 mix3 mix4 mix5 mix9 ]
outputs.hp_mute=off [ off on ]
inputs.hp=85,85
outputs.hp_dir=output [ none output input input-vr0 input-vr50 input-vr80
input-vr100 ]
outputs.hp_boost=on [ off on ]
outputs.line-in_source=mix2 [ mix2 mix3 mix4 mix5 mix9 ]
outputs.line-in_mute=off [ off on ]
inputs.line-in=85,85
outputs.line-in_dir=input [ none output input input-vr0 input-vr50 input-vr80
input-vr100 ]
outputs.line-in_boost=off [ off on ]
outputs.spkr_source=mix5 [ mix2 mix3 mix4 mix5 mix9 ]
outputs.spkr_mute=on [ off on ]
outputs.spkr_dir=output [ none output input input-vr0 input-vr50 input-vr80
input-vr100 ]
outputs.spkr_boost=off [ off on ]
outputs.SPDIF_source=dig-dac-0:1 [ dig-dac-0:1 ]
record.adc-4:5_source=hp,line-in,beep,line,mix { hp line-in beep line mix }
record.adc-2:3_source=hp,line-in,beep,line,mix { hp line-in beep line mix }
record.adc-0:1_source=hp,line-in,beep,line,mix { hp line-in beep line mix }
outputs.mix9=126,126
inputs.mix9_source=dac-8:9,mix { dac-8:9 mix }
outputs.hp_sense=plugged [ unplugged plugged ]
outputs.spkr_muters=hp { hp }
outputs.master=255,255
outputs.master.mute=off [ off on ]
outputs.master.slaves=mix3,mix4,mix5,line,hp,spkr { mix2 mix3 mix4 mix5 line
hp line-in spkr mix9 }
record.volume=125,125
record.volume.mute=off [ off on ]
record.volume.slaves=adc-0:1,adc-2:3,adc-4:5 { adc-0:1 adc-2:3 adc-4:5 line hp
line-in spkr }
outputs.mode=analog [ analog digital ]
record.mode=analog [ analog digital ]
$ dmesg
OpenBSD 5.5-current (GENERIC.MP) #54: Sat Apr 5 00:15:15 MDT 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 10715041792 (10218MB)
avail mem = 10421055488 (9938MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe00f0 (73 entries)
bios0: vendor Apple Computer, Inc. version "MP11.88Z.005C.B08.0707021221" date
07/02/07
bios0: Apple Computer, Inc. MacPro1,1
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT ECDT FACP HPET APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT
SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT
acpi0: wakeup devices P2P5(S4) P2P3(S4) ARPT(S4) RP04(S4) UHC1(S3) UHC2(S3)
UHC3(S3) UHC4(S3) EHCI(S3) AC9M(S4) EC__(S3) NRP4(S4) SRP1(S4) SRP3(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU 5150 @ 2.66GHz, 2660.37 MHz
cpu0:
FPU,VME,DE,PSE,TSC
Re: -current not building
Get new code. A shared library was not cranked correctly. > -current not currently building: > == > mandoc -Tlint -Wfatal /usr/src/usr.sbin/ldapd/ldapd.conf.5 > cc -o ldapd ber.o log.o control.o util.o ldapd.o ldape.o conn.o > attributes.o namespace.o btree.o filter.o search.o parse.o auth.o > modify.o index.o ssl.o ssl_privsep.o validate.o uuid.o schema.o > imsgev.o syntax.o matching.o -levent -lssl -lcrypto -lz -lutil > /usr/lib/libssl.so.22.0: undefined reference to `CRYPTO_memcmp' > collect2: ld returned 1 exit status > *** Error 1 in usr.sbin/ldapd (:95 'ldapd') > *** Error 2 in usr.sbin (:48 'all') > *** Error 2 in . (:48 'all') > *** Error 2 in /usr/src (Makefile:89 'build') > ==
-current not building
-current not currently building: == mandoc -Tlint -Wfatal /usr/src/usr.sbin/ldapd/ldapd.conf.5 cc -o ldapd ber.o log.o control.o util.o ldapd.o ldape.o conn.o attributes.o namespace.o btree.o filter.o search.o parse.o auth.o modify.o index.o ssl.o ssl_privsep.o validate.o uuid.o schema.o imsgev.o syntax.o matching.o -levent -lssl -lcrypto -lz -lutil /usr/lib/libssl.so.22.0: undefined reference to `CRYPTO_memcmp' collect2: ld returned 1 exit status *** Error 1 in usr.sbin/ldapd (:95 'ldapd') *** Error 2 in usr.sbin (:48 'all') *** Error 2 in . (:48 'all') *** Error 2 in /usr/src (Makefile:89 'build') ==
Re: How to apply a patch in OpenBSD?
Hi, ohh, whyyy wrote on Sun, Apr 13, 2014 at 07:54:12PM +0200: > # cd /root && ftp http://ftp.openbsd.org/pub/OpenBSD/`uname -r`/src.tar.gz > && tar -xzf /root/src.tar.gz -C /usr/src If you want to patch the kernel, you need sys.tar.gz, too. Yours, Ingo
How to apply a patch in OpenBSD?
Hi list! I installed the comp54.tgz set too when I installed http://ftp.openbsd.org/pub/OpenBSD/5.4/amd64/install54.iso then: # cd /root && ftp http://ftp.openbsd.org/pub/OpenBSD/`uname -r`/src.tar.gz && tar -xzf /root/src.tar.gz -C /usr/src # uname -r 5.4 # pwd /usr/src # ls -la total 124 drwxrwxr-x 17 root wsrc 512 Apr 13 19:35 . drwxr-xr-x 17 root wheel512 Jul 30 2013 .. drwxr-xr-x2 root wsrc 512 Jul 29 2013 CVS -rw-r--r--1 root wsrc3456 Jul 24 2013 Makefile -rw-r--r--1 root wsrc 16419 Jul 7 2013 Makefile.cross drwxr-xr-x 36 root wsrc1024 Jul 29 2013 bin drwxr-xr-x 31 root wsrc 512 Jul 29 2013 distrib drwxr-xr-x 35 root wsrc2560 Jul 29 2013 etc drwxr-xr-x 44 root wsrc1024 Jul 29 2013 games drwxr-xr-x9 root wsrc 512 Jul 29 2013 gnu drwxr-xr-x7 root wsrc2048 Jul 7 2013 include drwxr-xr-x 11 root wsrc 512 Jul 29 2013 kerberosV drwxr-xr-x 40 root wsrc1024 Jul 29 2013 lib drwxr-xr-x 40 root wsrc1024 Jul 29 2013 libexec drwxr-xr-x 15 root wsrc 512 Jul 10 2010 regress drwxr-xr-x 78 root wsrc1536 Jul 29 2013 sbin drwxr-xr-x 14 root wsrc 512 Jul 29 2013 share drwxr-xr-x 228 root wsrc4096 Jul 29 2013 usr.bin drwxr-xr-x 144 root wsrc2560 Jul 29 2013 usr.sbin # which gcc /usr/bin/gcc # # ftp http://ftp.openbsd.org/pub/OpenBSD/patches/5.4/common/001_pflow.patch Trying 129.128.5.191... Requesting http://ftp.openbsd.org/pub/OpenBSD/patches/5.4/common/001_pflow.patch 100% |***| 803 00:00 803 bytes received in 0.00 seconds (11.10 MB/s) # # patch -p0 < 001_pflow.patch Hmm... Looks like a unified diff to me... The text leading up to this was: -- |Apply by doing: | cd /usr/src | patch -p0 < 001_pflow.patch | |Then build and install a new kernel. | |Index: sys/net/if_pflow.c |=== |RCS file: /vol/openbsd/cvs/src/sys/net/if_pflow.c,v |retrieving revision 1.32 |diff -u -p -r1.32 if_pflow.c |--- sys/net/if_pflow.c 5 Jul 2013 17:14:27 - 1.32 |+++ sys/net/if_pflow.c 7 Nov 2013 16:48:45 - -- File to patch: # what do I need to write here??? No file found--skip this patch? [n] patch: can't find # # How do I get through the "File to patch: "? I cannot find the solution to it on: http://www.openbsd.org/faq/faq10.html or with a google search: site:www.openbsd.org "File to patch" What am I missing? Thank you in anticipation
Re: softeaid rebuild very slow
On Sun, 13 Apr 2014, John Cox wrote: > Hi > > I'm running OpenBSD 5.4 (dmesg below) with softraid in mirror mode. > One of the drives failed so I replaced it - the first time that RAID > has actually saved my data as opposed to simply making my life harder! > Thank you softraid. > > They are 3T drives and it looks like the rebuild is going to take ~5 > days to do. Is this expected? Is there any config parameter that I > should have set up to improve performance? 5 days = ~7MBytes / sec > and I know the drives can run a lot faster than that. The current code is designed to be robust rather than fast - it does a read from one of the online chunks (in this case you presumably only have one of those) and then does a write to all chunks (including both the online ones and the rebuilding one). In order to speed things up you want to read from one online chunk and only write to the chunk that needs rebuilding - the problem with this is that you need to prevent changes to the blocks that you are rebuilding until that write completes. Unfortunately that means some more restructing and additional code, plus a whole bunch of testing... > Can I reboot the system during the rebuild or if I do will it start at > the beginning again? I could try it but I'm now about 3 days in and > don't wish to waste it. The rebuild progress is stored in the softraid metadata - if you reboot (or even if the power goes out) it should pick up where it left off and complete the rebuild. > #dmesg > OpenBSD 5.4 (GENERIC.MP) #41: Tue Jul 30 15:30:02 MDT 2013 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 16973672448 (16187MB) > avail mem = 16514109440 (15749MB) > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xec420 (81 entries) > bios0: vendor Intel Corp. version "MKQ7710H.86A.0065.2014.0318.1044" > date 03/18/2014 > bios0: Intel Corporation DQ77MK > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT TCPA MCFG HPET SSDT SSDT SSDT DMAR > ASF! > acpi0: wakeup devices PS2K(S3) PS2M(S3) UAR1(S3) P0P1(S4) USB1(S3) > USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) PXSX(S4) > RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) [...] > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM) i5-3470T CPU @ 2.90GHz, 2893.85 MHz > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFL >USH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL, >VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLI >NE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: smt 0, core 0, package 0 > cpu0: apic clock running at 99MHz > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Core(TM) i5-3470T CPU @ 2.90GHz, 2893.43 MHz > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFL >USH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL, >VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLI >NE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS > cpu1: 256KB 64b/line 8-way L2 cache > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 1 (application processor) > cpu2: Intel(R) Core(TM) i5-3470T CPU @ 2.90GHz, 2893.43 MHz > cpu2: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFL >USH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL, >VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLI >NE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS > cpu2: 256KB 64b/line 8-way L2 cache > cpu2: smt 1, core 0, package 0 > cpu3 at mainbus0: apid 3 (application processor) > cpu3: Intel(R) Core(TM) i5-3470T CPU @ 2.90GHz, 2893.43 MHz > cpu3: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFL >USH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL, >VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLI >NE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS > cpu3: 256KB 64b/line 8-way L2 cache > cpu3: smt 1, core 1, package 0 > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins > acpimcfg0 at acpi0 addr 0xf800, bus 0-63 > acpihpet0 at acpi0: 14318179 Hz > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus 3 (P0P1) > acpiprt2 at acpi0: bus 1 (RP01) > acpiprt3 at acpi0: bus -1 (RP02) > acpiprt4 at acpi0: bus -1 (RP03) > acpiprt5 at acpi0: bus -1 (RP04) > acpiprt6 at acpi0: bus -1 (RP05) > acpiprt7 at acpi0: bus -1 (RP06) > acpiprt8 at acpi0: bus 2 (RP07) > acpiprt9 at acpi0: bus -1 (RP08) > acpiprt10 at acpi0: bus -1 (PEG0) > acpiprt11 at acpi0: bus -1 (PEG1) > acpiprt12 at acpi0: bus -1 (PEG2) > acpiprt13 at acpi0: bus -1 (PEG3) > acpiec0 at acpi0: F
Re: softeaid rebuild very slow
On Sun, Apr 13, 2014 at 5:22 AM, John Cox wrote: > Hi > > I'm running OpenBSD 5.4 (dmesg below) with softraid in mirror mode. > One of the drives failed so I replaced it - the first time that RAID > has actually saved my data as opposed to simply making my life harder! > Thank you softraid. > > They are 3T drives and it looks like the rebuild is going to take ~5 > days to do. Is this expected? Is there any config parameter that I > should have set up to improve performance? 5 days = ~7MBytes / sec > and I know the drives can run a lot faster than that. > > Can I reboot the system during the rebuild or if I do will it start at > the beginning again? I could try it but I'm now about 3 days in and > don't wish to waste it. As I've seen in my testing you _can_ reboot/poweroff the machine and you won't lose rebuild progress. > Many thanks
softeaid rebuild very slow
Hi I'm running OpenBSD 5.4 (dmesg below) with softraid in mirror mode. One of the drives failed so I replaced it - the first time that RAID has actually saved my data as opposed to simply making my life harder! Thank you softraid. They are 3T drives and it looks like the rebuild is going to take ~5 days to do. Is this expected? Is there any config parameter that I should have set up to improve performance? 5 days = ~7MBytes / sec and I know the drives can run a lot faster than that. Can I reboot the system during the rebuild or if I do will it start at the beginning again? I could try it but I'm now about 3 days in and don't wish to waste it. Many thanks John Cox #dmesg OpenBSD 5.4 (GENERIC.MP) #41: Tue Jul 30 15:30:02 MDT 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 16973672448 (16187MB) avail mem = 16514109440 (15749MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xec420 (81 entries) bios0: vendor Intel Corp. version "MKQ7710H.86A.0065.2014.0318.1044" date 03/18/2014 bios0: Intel Corporation DQ77MK acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT TCPA MCFG HPET SSDT SSDT SSDT DMAR ASF! acpi0: wakeup devices PS2K(S3) PS2M(S3) UAR1(S3) P0P1(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-3470T CPU @ 2.90GHz, 2893.85 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 cpu0: apic clock running at 99MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-3470T CPU @ 2.90GHz, 2893.43 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-3470T CPU @ 2.90GHz, 2893.43 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-3470T CPU @ 2.90GHz, 2893.43 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 3 (P0P1) acpiprt2 at acpi0: bus 1 (RP01) acpiprt3 at acpi0: bus -1 (RP02) acpiprt4 at acpi0: bus -1 (RP03) acpiprt5 at acpi0: bus -1 (RP04) acpiprt6 at acpi0: bus -1 (RP05) acpiprt7 at acpi0: bus -1 (RP06) acpiprt8 at acpi0: bus 2 (RP07) acpiprt9 at acpi0: bus -1 (RP08) acpiprt10 at acpi0: bus -1 (PEG0) acpiprt11 at acpi0: bus -1 (PEG1) acpiprt12 at acpi0: bus -1 (PEG2) acpiprt13 at acpi0: bus -1 (PEG3) acpiec0 at acpi0: Failed to read resource settings acpicpu0 at acpi0: C2, C1, PSS acpicpu1 at acpi0: C2, C1, PSS acpicpu2 at acpi0: C2, C1, PSS acpicpu3 at acpi0: C2, C1, PSS acpipwrres0 at acpi0: FN00 acpipwrres1 at acpi0: FN01 acpipwrres2 at acpi0: FN02 acpipwrres3 at acpi0: FN03 acpipwrres4 at acpi0: FN04 acpitz0 at acpi0: critical temperature is 92 degC acpitz1 at acpi0: critical temperature is 92 degC acpibat0 at acpi0: BAT0 not present acpibat1 at acpi0: BAT1 not present acpibat2 at acpi0: BAT2 not present acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: LID0 acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: DD01 acpivout1 at acpivideo0: DD02 acpivout2 at acpivideo0: DD03 acpivout3 at acpivideo0: DD04 acpivout4 at acpivideo0: DD05 acpivout5 at acpivideo0: DD06 acpivout6 at acpivideo0: DD07 acpivout7 at acpivideo0: DD08 cpu0: Enhanced SpeedStep 2893 MHz: speeds: 2901, 2900, 2800, 2700, 2600, 2500, 2400, 2300, 2200, 2100, 2000, 1900, 1800, 1700, 1600 MHz pci0 at main
Re: OpenSMTPD exits with value 1 when clients attempd to authenticate
On Fri, Apr 11, 2014 at 03:07:02PM +0200, Eric Faurot wrote: > [...] > This is a fallout due to the merging of multiple processes. It's been > fixed in cvs two days agos. > [...] Wonderful. Everything is back to normal now, thanks. -- Gregor Best
5.5 current resume hangs
From at least a couple of month my laptop doesn't resume after suspend. Mine is a thinkpad T410 with intel integrated gpu. The behaviour seems to be the same as reported in: http://openbsd.7691.n7.nabble.com/T410i-resume-broken-with-amd64-bsd-mp-and-revision-1-249-of-acpi-c-td240150.html But, I think in december 2013 my laptop was able to resume with current. With the SP kernel the system suspends and resumes perfectly. I didn't see any other report besides the previous one about this issue. Thanks in advance, Jes
