Re: Resolving the Lan users hostnames
On Wed, Apr 30, 2014 at 10:28:24AM -0400, sven falempin wrote: > On Tue, Apr 29, 2014 at 11:43 PM, Stuart Henderson > wrote: > > On 2014-04-28, sven falempin wrote: > >> Reading unbound doc i saw i can insert name to be resolved but i have > >> to each time > > > > configure things for unbound-control, then you can do > > "unbond-control local_data somehost.exaple.com A 192.0.2.1". > > > > would it be interesting to patch dhcpd (like Ted did) but directly > call the unbound-control work (both are in base) ? > using a suffix for the hostname given the default domain configured. > Someone hacked together a related solution with DNSMasq, described here: http://www.22decembre.eu/2014/04/14/local-dns-setup-with-dnsmasq-nsd-and-unbound/ -- John D. Verne
Re: No hw.setperf on Intel Atom CPU D2550 64bit system
Am 01.05.2014 05:51, schrieb Thomas Bohl: Am 01.05.2014 03:56, schrieb Jonathan Gray: It wouldn't hurt to check with md5 -tt and/or a power meter to see if there is actually a difference between hw.setperf=0 and hw.setperf=100. hw.setperf=100 16.5 Watt # md5 -tt MD5 time trial. Processing 10 1-byte blocks... Digest = 766a2bb5d24bddae466c572bcabca3ee Time = 39.389348 seconds Speed = 25387574.325932 bytes/second hw.setperf=0 16.9 Watt # md5 -tt MD5 time trial. Processing 10 1-byte blocks... Digest = 766a2bb5d24bddae466c572bcabca3ee Time = 4.672665 seconds Speed = 214010634.188413 bytes/second So the CPU actually gets slowed down quite heavily (apm shows 224 MHz). But the system has a greater power consumption while doing so. (Now that happens if you buy stuff in a hurry. I was aiming for a 10 Watt system. My bad!) Sorry, I mixed up the md5 results. hw.setperf=100 16.5 Watt # md5 -tt MD5 time trial. Processing 10 1-byte blocks... Digest = 766a2bb5d24bddae466c572bcabca3ee Time = 4.672665 seconds Speed = 214010634.188413 bytes/second hw.setperf=0 16.9 Watt # md5 -tt MD5 time trial. Processing 10 1-byte blocks... Digest = 766a2bb5d24bddae466c572bcabca3ee Time = 39.389348 seconds Speed = 25387574.325932 bytes/second
Re: No hw.setperf on Intel Atom CPU D2550 64bit system
Am 01.05.2014 03:56, schrieb Jonathan Gray: It wouldn't hurt to check with md5 -tt and/or a power meter to see if there is actually a difference between hw.setperf=0 and hw.setperf=100. hw.setperf=100 16.5 Watt # md5 -tt MD5 time trial. Processing 10 1-byte blocks... Digest = 766a2bb5d24bddae466c572bcabca3ee Time = 39.389348 seconds Speed = 25387574.325932 bytes/second hw.setperf=0 16.9 Watt # md5 -tt MD5 time trial. Processing 10 1-byte blocks... Digest = 766a2bb5d24bddae466c572bcabca3ee Time = 4.672665 seconds Speed = 214010634.188413 bytes/second So the CPU actually gets slowed down quite heavily (apm shows 224 MHz). But the system has a greater power consumption while doing so. (Now that happens if you buy stuff in a hurry. I was aiming for a 10 Watt system. My bad!)
Cubieboard question
Hi I am a bit confused about wether Cubiebord A20 or Cubieboard 3 are supported. On the http://www.openbsd.org/armv7.html it mentiones Cubieboard and Cubieboard 2, but it also says "A20". Would either work on OpenBSD 5.5? Kind regards.
Re: Can't replace /sbin/init
"Ben Dibell" wrote: > === "Ben Dibell" wrote: > === > ===> Hi, I've tried other resources, even reading the > source for init, but I > ===> can't seem to locate the magic that > makes /sbin/init the approved init. > ===> I'm porting my init > system Epoch to BSD for personal reasons, and I'd > ===> like > ===> it to work under OpenBSD, which I've been enjoying as of late. I > come > ===> from > ===> the linux world where init=/bin/sh is > perfectly valid, so some aspects > ===> are > ===> probably > simpler in Linux. I am hoping there is a concise and clean > ===> > explanation as to how to write/port an init system to BSD. Is it signal > ===> trickery? A checksum burned into the kernel? I'm lost. I'm given > "init > ===> has > ===> died, signal 0 exit 0" or > something nearly identical to this. There are > ===> no > ===> > further useful debug messages and my keyboard becomes unresponsive on > ===> the > ===> debugging prompt or the kernel locks up or > something, so I can't do more > ===> there. > ===> > ===> Thanks for your time. > ===> > ===> -Ben > === > > === The kernel doesn't support any command line syntax like that but > I don't > === know why it wouldn't let you use any static binary. You > should read > === kernel sources too if you're serious about this. > === > === But I don't see your point. Obviously you can do what > makes you happy on > === your systems but have you thought about what > OpenBSD init does vs. what > === your init does? init (among other > things) exists to run getty and start > === /etc/rc. You mention status > in a further message. You probably want to > === keep logs and manage > daemon state like the other newfangled init > === systems. You're going > to have to rewrite both init and the rc system. > === And you won't get > any support for such a system. > === > === And if you want to > monitor daemons you'll be better off monitoring the > === service the > daemons are supposed to provide. It doesn't matter if httpd > === > hasn't exited yet if you can't connect to it. > === > === - Martin > Brandenburg > === > > Well, I'm not asking for anyone to > support me once I get it going. Right now I just want to get stdout/stderr > working and perhaps I can get it running in a crippled but visibly > semi-functional state so I can continue my work porting. You've heard that fds 0, 1, and 2 are guaranteed to be open to your process when it starts. You are trying to make use of them, but you are writing the first userspace code to run on a system. So you must ask when they get open. If you would actually read init.c, you will see a function like setctty which must be called to perform this work. I recommend you learn what login_tty does as well. If you open /dev/console you can write things to the console. Otherwise write(1, ...) fails. (What's more, I have bothered to test this, so I know I'm telling the truth.) You are expected to read code and figure these things out yourself. You are unlikely to get someone to do this for you again on this list. - Martin Brandenburg
Re: Can't replace /sbin/init
=== "Ben Dibell" wrote: === ===> Hi, I've tried other resources, even reading the source for init, but I ===> can't seem to locate the magic that makes /sbin/init the approved init. ===> I'm porting my init system Epoch to BSD for personal reasons, and I'd ===> like ===> it to work under OpenBSD, which I've been enjoying as of late. I come ===> from ===> the linux world where init=/bin/sh is perfectly valid, so some aspects ===> are ===> probably simpler in Linux. I am hoping there is a concise and clean ===> explanation as to how to write/port an init system to BSD. Is it signal ===> trickery? A checksum burned into the kernel? I'm lost. I'm given "init ===> has ===> died, signal 0 exit 0" or something nearly identical to this. There are ===> no ===> further useful debug messages and my keyboard becomes unresponsive on ===> the ===> debugging prompt or the kernel locks up or something, so I can't do more ===> there. ===> ===> Thanks for your time. ===> ===> -Ben === === The kernel doesn't support any command line syntax like that but I don't === know why it wouldn't let you use any static binary. You should read === kernel sources too if you're serious about this. === === But I don't see your point. Obviously you can do what makes you happy on === your systems but have you thought about what OpenBSD init does vs. what === your init does? init (among other things) exists to run getty and start === /etc/rc. You mention status in a further message. You probably want to === keep logs and manage daemon state like the other newfangled init === systems. You're going to have to rewrite both init and the rc system. === And you won't get any support for such a system. === === And if you want to monitor daemons you'll be better off monitoring the === service the daemons are supposed to provide. It doesn't matter if httpd === hasn't exited yet if you can't connect to it. === === - Martin Brandenburg === Well, I'm not asking for anyone to support me once I get it going. Right now I just want to get stdout/stderr working and perhaps I can get it running in a crippled but visibly semi-functional state so I can continue my work porting.
Re: No hw.setperf on Intel Atom CPU D2550 64bit system
On 04/30/14 21:56, Jonathan Gray wrote: > On Wed, Apr 30, 2014 at 07:28:16PM +0200, Thomas Bohl wrote: >> Am 30.04.2014 05:23, schrieb Jonathan Gray: >> >On Tue, Apr 29, 2014 at 10:22:29PM +0200, Thomas Bohl wrote: >> >>cpu0 at mainbus0: apid 0 (boot processor) >> >>cpu0: Intel(R) Atom(TM) CPU D2550 @ 1.86GHz, 1867.07 MHz >> >>cpu0: >> >>FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,ITSC >> > >> >We only do speedstep if the processor advertises that speedstep is >> >supported in cpuid (ie there should be a 'EST' flag above). >> > >> >According to >> >http://ark.intel.com/products/65470/Intel-Atom-Processor-D2550-(1M-Cache-1_86-GHz) >> >it doesn't do speedstep as well. >> > >> >i386 fakes a table with high/low values for older processors that >> >still have a fsb, which was mostly used before the code to fetch >> >tables from acpi was added. >> >> Thank you for your explanation. >> i386 it is then. > > It wouldn't hurt to check with md5 -tt and/or a power meter > to see if there is actually a difference between > hw.setperf=0 and hw.setperf=100. > A power meter would be more "useful" -- at least the first generation of Atom systems, the Northbridge chip drew more power than the CPU (really -- the heatsink and fan was on the Northbridge chip, NOT the CPU!! This may explain the lack of speedstep); if you could wack the CPU down to zero power consumption (you can't), it would hardly have changed the TOTAL system power draw at all. Nick.
Re: Can't replace /sbin/init
"Ben Dibell" wrote: > Hi, I've tried other resources, even reading the source for init, but I > can't seem to locate the magic that makes /sbin/init the approved init. > I'm porting my init system Epoch to BSD for personal reasons, and I'd like > it to work under OpenBSD, which I've been enjoying as of late. I come from > the linux world where init=/bin/sh is perfectly valid, so some aspects are > probably simpler in Linux. I am hoping there is a concise and clean > explanation as to how to write/port an init system to BSD. Is it signal > trickery? A checksum burned into the kernel? I'm lost. I'm given "init has > died, signal 0 exit 0" or something nearly identical to this. There are no > further useful debug messages and my keyboard becomes unresponsive on the > debugging prompt or the kernel locks up or something, so I can't do more > there. > > Thanks for your time. > > -Ben The kernel doesn't support any command line syntax like that but I don't know why it wouldn't let you use any static binary. You should read kernel sources too if you're serious about this. But I don't see your point. Obviously you can do what makes you happy on your systems but have you thought about what OpenBSD init does vs. what your init does? init (among other things) exists to run getty and start /etc/rc. You mention status in a further message. You probably want to keep logs and manage daemon state like the other newfangled init systems. You're going to have to rewrite both init and the rc system. And you won't get any support for such a system. And if you want to monitor daemons you'll be better off monitoring the service the daemons are supposed to provide. It doesn't matter if httpd hasn't exited yet if you can't connect to it. - Martin Brandenburg
Re: No hw.setperf on Intel Atom CPU D2550 64bit system
On Wed, Apr 30, 2014 at 07:28:16PM +0200, Thomas Bohl wrote: > Am 30.04.2014 05:23, schrieb Jonathan Gray: > >On Tue, Apr 29, 2014 at 10:22:29PM +0200, Thomas Bohl wrote: > >>cpu0 at mainbus0: apid 0 (boot processor) > >>cpu0: Intel(R) Atom(TM) CPU D2550 @ 1.86GHz, 1867.07 MHz > >>cpu0: > >>FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,ITSC > > > >We only do speedstep if the processor advertises that speedstep is > >supported in cpuid (ie there should be a 'EST' flag above). > > > >According to > >http://ark.intel.com/products/65470/Intel-Atom-Processor-D2550-(1M-Cache-1_86-GHz) > >it doesn't do speedstep as well. > > > >i386 fakes a table with high/low values for older processors that > >still have a fsb, which was mostly used before the code to fetch > >tables from acpi was added. > > Thank you for your explanation. > i386 it is then. It wouldn't hurt to check with md5 -tt and/or a power meter to see if there is actually a difference between hw.setperf=0 and hw.setperf=100.
Re: Can't replace /sbin/init
I did read init.c, it didn't help. But my tests have shown that things are willing to run in place of init, but, stdout/stderr/stdin are unavailable to init? I assume this is some kind of security thing. freopen() has failed me here. === Wow, what chatter. === === It is obvious that you have not read the source to our init.c, === nor looked at the commit logs. === === I don't understand society is producing a generation of people === incapable of self-help. Probably something in the water. === ===> === On Wed, Apr 30, 2014 at 12:02 AM, Ben Dibell ===> === wrote: ===> ===> Hi, I've tried other resources, even reading the source for init, ===> but I ===> ===> can't seem to locate the magic that makes /sbin/init the approved ===> init. ===> ===> I'm porting my init system Epoch to BSD for personal reasons, and ===> I'd ===> ===> like ===> ===> it to work under OpenBSD, which I've been enjoying as of late. I ===> come ===> ===> from ===> ===> the linux world where init=/bin/sh is perfectly valid, ===> === ===> === Hmm, I haven't tried, but /bin/sh should work. ===> === ===> === ===> ===> so some aspects are ===> ===> probably simpler in Linux. I am hoping there is a concise and clean ===> ===> explanation as to how to write/port an init system to BSD. Is it ===> signal ===> ===> trickery? A checksum burned into the kernel? I'm lost. I'm given ===> "init ===> ===> has ===> ===> died, signal 0 exit 0" or something nearly identical to this. ===> === ===> === This means the original thread of process 1 exited. Are you by ===> chance ===> === trying to write a threaded init, because there are a number of ===> places ===> === where the kernel currently assumes pid 1 is not a threaded process. ===> === ===> === ===> === Philip Guenther ===> === ===> ===> Thanks, hmm, yeah no, /bin/sh didn't work. Epoch is single threaded and ===> is ===> mature and stable on Linux at 1.0.1. I tried a statically linked build ===> but ===> it didn't work either. ===> It's possible it's a bug in Epoch somewhere, but I've read the code many ===> times and it should have printed something to the console, anything by ===> the ===> time it dies, since all the previous code seems pretty fool-proof, and ===> since /bin/sh wouldn't work as an init either, it makes me strongly ===> suspect it's not Epoch's fault. ===> ===> === BSD has an init system. The source is there. ===> === What exactly is your problem? What do you want to do ===> === with your init that you can't do with the default install? ===> ===> Jan: A lot of things can be done in Epoch easier, actually. Especially ===> status related stuff is quite nice in Epoch, I made sure of it since I ===> use ===> it a lot. To answer the question as to what problems I have, the agency ===> has not yet finished collating the list. I'll be sure to write when they ===> complete it. ===> ===> === Not that I know what init=/bin/sh means, ===> === but how does it make anything simpler? ===> ===> It allows me to use not only any binary as init, but Linux permits ===> executable scripts with a hashbang to be run as init as well. Reaping ===> however, is a little more complicated. Most shells seem to do this on ===> their own somehow anyways. ===> === === === Acrt
Re: 5.5 CDs arriving
On Wed, 30 Apr 2014, JJ Jumpercables wrote: >On Wed, Apr 30, 2014 at 12:56 PM, Dave Anderson wrote: >> Just got mine, near Boston, Mass. >> > >Jut curious... how long ago did you order? As soon as I saw the announcement that orders were open -- I don't remember exactly when, but it was within a day after the announcement went up. Dave -- Dave Anderson
Re: 5.5 CDs arriving
I ordered April 5. They havent arrived yet and Im only two provinces over. Figure its because there is a shirt and two posters in the order as well. You can never have enough OpenBSD loot. g...@grub.net PGP Key ID DB8BF93C On Apr 30, 2014, at 2:08 PM, Matt Behrens wrote: > On Apr 30, 2014, at 12:56 PM, Dave Anderson wrote: > >> Just got mine, near Boston, Mass. > > Mine arrived in Grand Rapids, MI yesterday. > >> My thanks to everyone involved. > > And mine as well! > > [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc] [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: Can't replace /sbin/init
Wow, what chatter. It is obvious that you have not read the source to our init.c, nor looked at the commit logs. I don't understand society is producing a generation of people incapable of self-help. Probably something in the water. > === On Wed, Apr 30, 2014 at 12:02 AM, Ben Dibell > === wrote: > ===> Hi, I've tried other resources, even reading the source for init, but I > ===> can't seem to locate the magic that makes /sbin/init the approved init. > ===> I'm porting my init system Epoch to BSD for personal reasons, and I'd > ===> like > ===> it to work under OpenBSD, which I've been enjoying as of late. I come > ===> from > ===> the linux world where init=/bin/sh is perfectly valid, > === > === Hmm, I haven't tried, but /bin/sh should work. > === > === > ===> so some aspects are > ===> probably simpler in Linux. I am hoping there is a concise and clean > ===> explanation as to how to write/port an init system to BSD. Is it signal > ===> trickery? A checksum burned into the kernel? I'm lost. I'm given "init > ===> has > ===> died, signal 0 exit 0" or something nearly identical to this. > === > === This means the original thread of process 1 exited. Are you by chance > === trying to write a threaded init, because there are a number of places > === where the kernel currently assumes pid 1 is not a threaded process. > === > === > === Philip Guenther > === > > Thanks, hmm, yeah no, /bin/sh didn't work. Epoch is single threaded and is > mature and stable on Linux at 1.0.1. I tried a statically linked build but > it didn't work either. > It's possible it's a bug in Epoch somewhere, but I've read the code many > times and it should have printed something to the console, anything by the > time it dies, since all the previous code seems pretty fool-proof, and > since /bin/sh wouldn't work as an init either, it makes me strongly > suspect it's not Epoch's fault. > > === BSD has an init system. The source is there. > === What exactly is your problem? What do you want to do > === with your init that you can't do with the default install? > > Jan: A lot of things can be done in Epoch easier, actually. Especially > status related stuff is quite nice in Epoch, I made sure of it since I use > it a lot. To answer the question as to what problems I have, the agency > has not yet finished collating the list. I'll be sure to write when they > complete it. > > === Not that I know what init=/bin/sh means, > === but how does it make anything simpler? > > It allows me to use not only any binary as init, but Linux permits > executable scripts with a hashbang to be run as init as well. Reaping > however, is a little more complicated. Most shells seem to do this on > their own somehow anyways.
Re: Can't replace /sbin/init
=== On Wed, Apr 30, 2014 at 12:02 AM, Ben Dibell === wrote: ===> Hi, I've tried other resources, even reading the source for init, but I ===> can't seem to locate the magic that makes /sbin/init the approved init. ===> I'm porting my init system Epoch to BSD for personal reasons, and I'd ===> like ===> it to work under OpenBSD, which I've been enjoying as of late. I come ===> from ===> the linux world where init=/bin/sh is perfectly valid, === === Hmm, I haven't tried, but /bin/sh should work. === === ===> so some aspects are ===> probably simpler in Linux. I am hoping there is a concise and clean ===> explanation as to how to write/port an init system to BSD. Is it signal ===> trickery? A checksum burned into the kernel? I'm lost. I'm given "init ===> has ===> died, signal 0 exit 0" or something nearly identical to this. === === This means the original thread of process 1 exited. Are you by chance === trying to write a threaded init, because there are a number of places === where the kernel currently assumes pid 1 is not a threaded process. === === === Philip Guenther === Thanks, hmm, yeah no, /bin/sh didn't work. Epoch is single threaded and is mature and stable on Linux at 1.0.1. I tried a statically linked build but it didn't work either. It's possible it's a bug in Epoch somewhere, but I've read the code many times and it should have printed something to the console, anything by the time it dies, since all the previous code seems pretty fool-proof, and since /bin/sh wouldn't work as an init either, it makes me strongly suspect it's not Epoch's fault. === BSD has an init system. The source is there. === What exactly is your problem? What do you want to do === with your init that you can't do with the default install? Jan: A lot of things can be done in Epoch easier, actually. Especially status related stuff is quite nice in Epoch, I made sure of it since I use it a lot. To answer the question as to what problems I have, the agency has not yet finished collating the list. I'll be sure to write when they complete it. === Not that I know what init=/bin/sh means, === but how does it make anything simpler? It allows me to use not only any binary as init, but Linux permits executable scripts with a hashbang to be run as init as well. Reaping however, is a little more complicated. Most shells seem to do this on their own somehow anyways.
Re: pppoe over vlan problem
On Tue, Sep 24, 2013 at 9:57 PM, Henning Brauer wrote: > * Daniel Gillen [2013-09-24 17:36]: > > After some debugging with tcpdump, I found out that from 5.0 to 5.1, > > OpenBSD introduced vlan priorisation support (IEEE 802.1p) and per > > default sets the vlan PCP field to the value 3. > > > > Unfortunately, my ISP only allows connections when this field is set to > 0 :( > > what? you are kidding, right? > > talk to the ISP and tell them they're on drugs. it is perfectly fine > to ignore the prio field, but requiring a specific value is absolutely > ridiculous. if they don't fix it, share who it is to warn people. > > that said, resetting should hav worked, I have a vague idea where that > bug might sit; can't check deeper right now tho. oh how much i wish we > had a bug tracker.one you can." > Actually, Orange, the biggest french ISP only accepts PPPoE connections with PCP field set to 0. Asking them to change this stupid behavior might be... "difficult". There is a plethora of xDSL providers here. But with optical fiber, we are totally screwed. This ISP is the only choice.
Re: Weird disklabel problem
On 30 Apr 2014 03:28, "Martijn Rijkeboer" wrote: > > Hello, > > I've got a weird disklabel related problem (or so it seems). When I > partition my harddisk with fdisk and add an OpenBSD (A6) primary > partition the system can still boot, but once I place a disklabel > on the partition (disklabel -E sd0) I can't boot the system anymore > (it freezes during the post). > > System Info: > - OS: OpenBSD-current AMD64 > - CPU: Intel Core i3 4130T > - Motherboard: Gigabyte GA-B85M-DS3H > - Harddisk: WD Green 1TB (SATA) > > It is possible that it's a Gigabyte specific problem since Karl > Karlsson has the same problem with his Gigabyte GA-Z87MX-DH3 > motherboard. > > The other strange thing is that if I use an USB-stick instead > of the harddisk I can install and boot OpenBSD without problems. > Even with the harddisk present, but without a disklabel, I can > still boot from the USB stick, but as soon as I place a disklabel > on the harddisk (although it isn't used, nor in the boot sequence) > the system freezes during the post again. > > Any suggestions on how to fix this or should I just buy a different > motherboard? > > Kind regards, > > > Martijn Rijkeboer > Can you provide a hex dump of the MBR Linux produces? The evidence would seem to point at the boot code stored in the MBR. To which I made a recent minor tweak. So you might also try a 5.4 install to see if it works. Ken
Re: 5.5 CDs arriving
On Apr 30, 2014, at 12:56 PM, Dave Anderson wrote: > Just got mine, near Boston, Mass. Mine arrived in Grand Rapids, MI yesterday. > My thanks to everyone involved. And mine as well! [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: Weird disklabel problem
On 30 Apr 2014 15:57, "Kenneth Westerback" wrote: > > > On 30 Apr 2014 15:39, "Martijn Rijkeboer" wrote: > > > > > Please post at least a dmesg with the disk attached but no disklabel > > > plus fdisk and disklabel output after setting the label but before the > > > (failing) reboot. > > > > Below you will find the dmesg and output from fdisk and disklabel before > > and after labeling. I used Linux to partition the harddisk, because if I > > use the "Whole" option from the OpenBSD installer in can't boot... > > > > Kind regards, > > > > > > Martijn Rijkeboer > > > > dmesg > > = > > > > OpenBSD 5.5-current (GENERIC.MP) #86: Tue Apr 29 03:35:46 MDT 2014 > > t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > real mem = 8443088896 (8051MB) > > avail mem = 8209612800 (7829MB) > > mpath0 at root > > scsibus0 at mpath0: 256 targets > > mainbus0 at root > > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb5f0 (76 entries) > > bios0: vendor American Megatrends Inc. version "F2" date 01/18/2014 > > bios0: Gigabyte Technology Co., Ltd. B85M-DS3H > > acpi0 at bios0: rev 2 > > acpi0: sleep states S0 S3 S4 S5 > > acpi0: tables DSDT FACP APIC FPDT SSDT SSDT MCFG HPET SSDT SSDT DMAR > > acpi0: wakeup devices PS2K(S3) PS2M(S3) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(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) i3-4130T CPU @ 2.90GHz, 2893.72 MHz > > cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,A ES,XSAVE,AVX,F16C,RDRAND,LONG,LAHF,ABM,PERF,ITSC > > cpu0: 256KB 64b/line 8-way L2 cache > > mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges > > cpu0: apic clock running at 99MHz > > cpu0: mwait min=25345, max=46847 (bogus) > > cpu1 at mainbus0: apid 2 (application processor) > > cpu1: Intel(R) Core(TM) i3-4130T CPU @ 2.90GHz, 2893.30 MHz > > cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,A ES,XSAVE,AVX,F16C,RDRAND,LONG,LAHF,ABM,PERF,ITSC > > cpu1: 256KB 64b/line 8-way L2 cache > > 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 1 (RP01) > > acpiprt2 at acpi0: bus 2 (RP03) > > acpiprt3 at acpi0: bus -1 (P0P2) > > acpiprt4 at acpi0: bus -1 (P0PA) > > acpiprt5 at acpi0: bus -1 (P0PB) > > acpiprt6 at acpi0: bus -1 (PEG0) > > acpiprt7 at acpi0: bus -1 (PEG1) > > acpiprt8 at acpi0: bus -1 (PEG2) > > acpiec0 at acpi0: Failed to read resource settings > > acpicpu0 at acpi0: C2, C1, PSS > > acpicpu1 at acpi0: C2, C1, PSS > > acpipwrres0 at acpi0: FN00, resource for FAN0 > > acpipwrres1 at acpi0: FN01, resource for FAN1 > > acpipwrres2 at acpi0: FN02, resource for FAN2 > > acpipwrres3 at acpi0: FN03, resource for FAN3 > > acpipwrres4 at acpi0: FN04, resource for FAN4 > > acpitz0 at acpi0: critical temperature is 90 degC > > acpitz1 at acpi0: critical temperature is 90 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: DD1F > > cpu0: Enhanced SpeedStep 2893 MHz: speeds: 2900, 2800, 2600, 2500, 2300, 2200, 2100, 1900, 1800, 1600, 1500, 1400, 1200, 1100, 900, 800 MHz > > pci0 at mainbus0 bus 0 > > pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06 > > vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4600" rev 0x06 > > intagp0 at vga1 > > agp0 at intagp0: aperture at 0xe000, size 0x1000 > > inteldrm0 at vga1 > > drm0 at inteldrm0 > > error: [drm:pid0:i915_write32] *ERROR* Unknown unclaimed register before writing to 10 > > inteldrm0: 1920x1200 > > wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) > > wsdisplay0: screen 1-5 added (std, vt100 emulation) > > azalia0 at pci0 dev 3 function 0 "Intel Core 4G HD Audio" rev 0x06: msi > > azalia0: No codecs found > > "Intel 8 Series xHCI" rev 0x05 at pci0 dev 20 function 0 not configured > > "Intel 8 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured > > puc0 at pci0 dev 22 function 3 "Intel 8 Series KT" rev 0x04: ports: 1 com > > com4 at puc0 port 0 apic 2 int 19: ns16550a, 16 byte fifo > > com4: probed fifo depth: 0 bytes > > ehci0 at pci0 dev 26 function 0 "Intel 8 Series USB" rev 0x05: apic 2 int 16 > > usb0 at ehci0: USB revision 2.0 > > uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00
Re: 5.5 CDs arriving
On Wed, Apr 30, 2014 at 12:56 PM, Dave Anderson wrote: > Just got mine, near Boston, Mass. > Jut curious... how long ago did you order?
Re: Weird disklabel problem
On 30 Apr 2014 15:39, "Martijn Rijkeboer" wrote: > > > Please post at least a dmesg with the disk attached but no disklabel > > plus fdisk and disklabel output after setting the label but before the > > (failing) reboot. > > Below you will find the dmesg and output from fdisk and disklabel before > and after labeling. I used Linux to partition the harddisk, because if I > use the "Whole" option from the OpenBSD installer in can't boot... > > Kind regards, > > > Martijn Rijkeboer > > dmesg > = > > OpenBSD 5.5-current (GENERIC.MP) #86: Tue Apr 29 03:35:46 MDT 2014 > t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 8443088896 (8051MB) > avail mem = 8209612800 (7829MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb5f0 (76 entries) > bios0: vendor American Megatrends Inc. version "F2" date 01/18/2014 > bios0: Gigabyte Technology Co., Ltd. B85M-DS3H > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT SSDT SSDT MCFG HPET SSDT SSDT DMAR > acpi0: wakeup devices PS2K(S3) PS2M(S3) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(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) i3-4130T CPU @ 2.90GHz, 2893.72 MHz > cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,A ES,XSAVE,AVX,F16C,RDRAND,LONG,LAHF,ABM,PERF,ITSC > cpu0: 256KB 64b/line 8-way L2 cache > mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges > cpu0: apic clock running at 99MHz > cpu0: mwait min=25345, max=46847 (bogus) > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Core(TM) i3-4130T CPU @ 2.90GHz, 2893.30 MHz > cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,A ES,XSAVE,AVX,F16C,RDRAND,LONG,LAHF,ABM,PERF,ITSC > cpu1: 256KB 64b/line 8-way L2 cache > 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 1 (RP01) > acpiprt2 at acpi0: bus 2 (RP03) > acpiprt3 at acpi0: bus -1 (P0P2) > acpiprt4 at acpi0: bus -1 (P0PA) > acpiprt5 at acpi0: bus -1 (P0PB) > acpiprt6 at acpi0: bus -1 (PEG0) > acpiprt7 at acpi0: bus -1 (PEG1) > acpiprt8 at acpi0: bus -1 (PEG2) > acpiec0 at acpi0: Failed to read resource settings > acpicpu0 at acpi0: C2, C1, PSS > acpicpu1 at acpi0: C2, C1, PSS > acpipwrres0 at acpi0: FN00, resource for FAN0 > acpipwrres1 at acpi0: FN01, resource for FAN1 > acpipwrres2 at acpi0: FN02, resource for FAN2 > acpipwrres3 at acpi0: FN03, resource for FAN3 > acpipwrres4 at acpi0: FN04, resource for FAN4 > acpitz0 at acpi0: critical temperature is 90 degC > acpitz1 at acpi0: critical temperature is 90 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: DD1F > cpu0: Enhanced SpeedStep 2893 MHz: speeds: 2900, 2800, 2600, 2500, 2300, 2200, 2100, 1900, 1800, 1600, 1500, 1400, 1200, 1100, 900, 800 MHz > pci0 at mainbus0 bus 0 > pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06 > vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4600" rev 0x06 > intagp0 at vga1 > agp0 at intagp0: aperture at 0xe000, size 0x1000 > inteldrm0 at vga1 > drm0 at inteldrm0 > error: [drm:pid0:i915_write32] *ERROR* Unknown unclaimed register before writing to 10 > inteldrm0: 1920x1200 > wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) > wsdisplay0: screen 1-5 added (std, vt100 emulation) > azalia0 at pci0 dev 3 function 0 "Intel Core 4G HD Audio" rev 0x06: msi > azalia0: No codecs found > "Intel 8 Series xHCI" rev 0x05 at pci0 dev 20 function 0 not configured > "Intel 8 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured > puc0 at pci0 dev 22 function 3 "Intel 8 Series KT" rev 0x04: ports: 1 com > com4 at puc0 port 0 apic 2 int 19: ns16550a, 16 byte fifo > com4: probed fifo depth: 0 bytes > ehci0 at pci0 dev 26 function 0 "Intel 8 Series USB" rev 0x05: apic 2 int 16 > usb0 at ehci0: USB revision 2.0 > uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 > azalia1 at pci0 dev 27 function 0 "Intel 8 Series HD Audio" rev 0x05: msi > azalia1: codecs: Realtek/0x0887 > audio0 at azalia1 > ppb0 at pci0 dev 28 function 0 "Intel 8 Series PCIE" rev 0xd5: msi > pci1 at ppb0 bus 1 > ppb1 at pci0 dev
Re: Weird disklabel problem
> Please post at least a dmesg with the disk attached but no disklabel > plus fdisk and disklabel output after setting the label but before the > (failing) reboot. Below you will find the dmesg and output from fdisk and disklabel before and after labeling. I used Linux to partition the harddisk, because if I use the "Whole" option from the OpenBSD installer in can't boot... Kind regards, Martijn Rijkeboer dmesg = OpenBSD 5.5-current (GENERIC.MP) #86: Tue Apr 29 03:35:46 MDT 2014 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8443088896 (8051MB) avail mem = 8209612800 (7829MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb5f0 (76 entries) bios0: vendor American Megatrends Inc. version "F2" date 01/18/2014 bios0: Gigabyte Technology Co., Ltd. B85M-DS3H acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT SSDT SSDT MCFG HPET SSDT SSDT DMAR acpi0: wakeup devices PS2K(S3) PS2M(S3) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(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) i3-4130T CPU @ 2.90GHz, 2893.72 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,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,LONG,LAHF,ABM,PERF,ITSC cpu0: 256KB 64b/line 8-way L2 cache mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=25345, max=46847 (bogus) cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i3-4130T CPU @ 2.90GHz, 2893.30 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,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,LONG,LAHF,ABM,PERF,ITSC cpu1: 256KB 64b/line 8-way L2 cache 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 1 (RP01) acpiprt2 at acpi0: bus 2 (RP03) acpiprt3 at acpi0: bus -1 (P0P2) acpiprt4 at acpi0: bus -1 (P0PA) acpiprt5 at acpi0: bus -1 (P0PB) acpiprt6 at acpi0: bus -1 (PEG0) acpiprt7 at acpi0: bus -1 (PEG1) acpiprt8 at acpi0: bus -1 (PEG2) acpiec0 at acpi0: Failed to read resource settings acpicpu0 at acpi0: C2, C1, PSS acpicpu1 at acpi0: C2, C1, PSS acpipwrres0 at acpi0: FN00, resource for FAN0 acpipwrres1 at acpi0: FN01, resource for FAN1 acpipwrres2 at acpi0: FN02, resource for FAN2 acpipwrres3 at acpi0: FN03, resource for FAN3 acpipwrres4 at acpi0: FN04, resource for FAN4 acpitz0 at acpi0: critical temperature is 90 degC acpitz1 at acpi0: critical temperature is 90 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: DD1F cpu0: Enhanced SpeedStep 2893 MHz: speeds: 2900, 2800, 2600, 2500, 2300, 2200, 2100, 1900, 1800, 1600, 1500, 1400, 1200, 1100, 900, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06 vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4600" rev 0x06 intagp0 at vga1 agp0 at intagp0: aperture at 0xe000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 error: [drm:pid0:i915_write32] *ERROR* Unknown unclaimed register before writing to 10 inteldrm0: 1920x1200 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) azalia0 at pci0 dev 3 function 0 "Intel Core 4G HD Audio" rev 0x06: msi azalia0: No codecs found "Intel 8 Series xHCI" rev 0x05 at pci0 dev 20 function 0 not configured "Intel 8 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured puc0 at pci0 dev 22 function 3 "Intel 8 Series KT" rev 0x04: ports: 1 com com4 at puc0 port 0 apic 2 int 19: ns16550a, 16 byte fifo com4: probed fifo depth: 0 bytes ehci0 at pci0 dev 26 function 0 "Intel 8 Series USB" rev 0x05: apic 2 int 16 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 azalia1 at pci0 dev 27 function 0 "Intel 8 Series HD Audio" rev 0x05: msi azalia1: codecs: Realtek/0x0887 audio0 at azalia1 ppb0 at pci0 dev 28 function 0 "Intel 8 Series PCIE" rev 0xd5: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 2 "Intel 8 Series PCIE" rev 0xd5: msi pci2 at ppb1 bus 2 re0 at pci2 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E-VL (0x2c80), msi, address 74:d4:35:04:aa:86 rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 5 ehci1 at pci0
Re: No hw.setperf on Intel Atom CPU D2550 64bit system
Am 30.04.2014 05:23, schrieb Jonathan Gray: On Tue, Apr 29, 2014 at 10:22:29PM +0200, Thomas Bohl wrote: cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Atom(TM) CPU D2550 @ 1.86GHz, 1867.07 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,ITSC We only do speedstep if the processor advertises that speedstep is supported in cpuid (ie there should be a 'EST' flag above). According to http://ark.intel.com/products/65470/Intel-Atom-Processor-D2550-(1M-Cache-1_86-GHz) it doesn't do speedstep as well. i386 fakes a table with high/low values for older processors that still have a fsb, which was mostly used before the code to fetch tables from acpi was added. Thank you for your explanation. i386 it is then.
Re: no sound recording
On Wed, Apr 30, 2014 at 07:07:56AM +0200, Jan Stary wrote: > On this Dell Inspiron 3700 (current i386, see dmesg below) > I can't seem to record sound. It's a maestro(4): > > maestro0 at pci0 dev 8 function 0 "ESS Maestro 2E" rev 0x10: irq 5 > ac97: codec id 0x83847609 (SigmaTel STAC9721/23) > ac97: codec features 18 bit DAC, 18 bit ADC, SigmaTel 3D > audio0 at maestro0 > > The BUGS section of maestro(4) says "Recording should work soon", > since May 2007 apparently. Is there any point in working on this? sure, as long as you have the hardware and you plan to use it. > If so, can somebody (ratchov?) please help me get started? > The datasheet seems to be available here: ftp://ftp.sunet.se/pub/Linux/alsa/manuals/ess/DSMaestro2.pdf The effect processor, wavetable, FM synth, speaker virtualisation and friends make it look complicated, but only the DMA and interrupts and codec handling parts are relevant. Look at sys/dev/pci/maestro.c; also see netbsd, freebsd and linux drivers; they may have the recording working, possibly with interesting comments in the sources. Most probably, play and rec directions work the same way, so the code will be very "symmetric"; this helps quickly identifying the missing (or broken) bits. There's one important point: play and rec directions must run at the same rate, and there might be subtle differences (rounding errors) that may cause clock skew (sndiod will complain about that after few minutes/hours of full-duplex operation). If so (or if you're unsure), just lock both directions to 48kHz. Furthermore, play and rec directions must use the same encodings, if certain encodings are not usable in one direction, you could drop them from the other direction. FWIW, anything but s16le is very unlikely to be used. Don't loose your time on format conversions (they will be tedu'ed very soon). Feel free to contact me if you need some help -- Alexandre
5.5 CDs arriving
Just got mine, near Boston, Mass. My thanks to everyone involved. Dave -- Dave Anderson
Re: Can't replace /sbin/init
On Wed, Apr 30, 2014 at 12:02 AM, Ben Dibell wrote: > Hi, I've tried other resources, even reading the source for init, but I > can't seem to locate the magic that makes /sbin/init the approved init. > I'm porting my init system Epoch to BSD for personal reasons, and I'd like > it to work under OpenBSD, which I've been enjoying as of late. I come from > the linux world where init=/bin/sh is perfectly valid, Hmm, I haven't tried, but /bin/sh should work. > so some aspects are > probably simpler in Linux. I am hoping there is a concise and clean > explanation as to how to write/port an init system to BSD. Is it signal > trickery? A checksum burned into the kernel? I'm lost. I'm given "init has > died, signal 0 exit 0" or something nearly identical to this. This means the original thread of process 1 exited. Are you by chance trying to write a threaded init, because there are a number of places where the kernel currently assumes pid 1 is not a threaded process. Philip Guenther
Re: Problem booting OpenBSD-current AMD64
Martijn Rijkeboer wrote: > I've installed OpenBSD-current AMD64 on my new computer without problems, > but as soon as I reboot the system, it freezes in the post. The only way > to go past the post is wiping the first few megabytes of the harddisk > using another computer and than start again. After installing I can't even > enter the bios setup. > > The system contains the following components: > - Motherboard: Gigabyte GA-B85M-DS3H > - CPU: Intel Core i3 4130T > - Memory: Kingston ValueRAM 8 GB DDR3-1600 Kit > > I've configured the bios the following way: > - Windows 8 Features: "Other OS" > - Boot Mode Selection: "Legacy Only" > - VGA Support: "Auto" (Enables legacy option) > > The system is working since I can install and run Ubuntu 14.04 AMD64 > without problems. > > Any suggestions on how to fix this? > > Kind regards, > > > Martijn Rijkeboer Experienced something similar today with a Gigabyte board from the Core 2 Duo era. (this may not be an OpenBSD problem in my opinion) Used an disk with a working Fedora 20/OpenBSD 5.4 install on it to do a clean install of OpenSUSE 13.1. Upon first boot the system hangs in the Intel AHCI screen. Normally a list of SATA ports and connected disks would appear but nothing happens. Eventually the simple solution for me was to use the second SATA controller this board has. So it may be an issue with how the Intel SATA BIOS detects the disks. I don't want to waste more time on this so I'm posting some minimal info which may or may not useful: The disk originally had its first partitions start at offset 63: Disk: sd0 geometry: 9729/255/63 [156301488 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- *0: 83 5660 19 56 - 5723 208 53 [90929152: 1024000 ] Linux files* 1: 8E 5723 208 54 - 9729 78 13 [91953152:64348160 ] Linux LVM 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 3: A6 0 1 1 - 5659 254 63 [ 63:90927837 ] OpenBSD Now, in the non-working situation, it starts at 2048 (first MB was reserved by the OpenSUSE installer). Another disk that used to work has its first partition start at offset 64: Disk: sd0 geometry: 7297/255/63 [117231408 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused *3: A6 0 1 2 - 7297 36 27 [ 64: 117228536 ] OpenBSD
Re: OpenBGPD crashing
On 2014/04/30 15:51, Andy wrote: > Hi sorry to reply with a stupid question but I get this error; > > [LIVE]root@mg1311:~# pkg_add -i symon > symon-2.86p0:libart-2.3.21: ok > symon-2.86p0:png-1.6.2p0: ok > Can't install rrdtool-1.2.30p3 because of libraries > |library freetype.20.0 not found > | not found anywhere > Direct dependencies for rrdtool-1.2.30p3 resolve to png-1.6.2p0 > libart-2.3.21 > Full dependency tree is png-1.6.2p0 libart-2.3.21 > Can't install symon-2.86p0: can't resolve rrdtool-1.2.30p3 > > I've come across this issue of missing freetype in the OpenBSD sources > before in older versions. Install xbase - see http://www.openbsd.org/faq/faq4.html#AddFileSet and note the ldconfig step. Alternatively any other way to grab process information would do - even as simple as running 'ps -axlww | grep [b]gpd.*route | logger' (if it's like I've seen, you'll probably want this every 15 seconds or so to actually catch it .. symon normally records every 5 seconds) > Anyway, I think you could be on the money as every time this has happened, > it always happens just after seeing the message nexthop now valid. > > We don't use nexthop-self on our cisco routers which are connected to > Transits and IXPs. > At the moment the OpenBSD routers only have iBGP neighborships with two > cisco ABR routers (no eBGP transit or IXP connections, just internal AS). > Thus the BGP nexthop networks (transit and IXP links) are redistributed to > the internal OpenBSD routers by IGP (OSPF) to validate the BGP nexthops and > provide BGP prefix independent convergence. > > In most cases as far as I can remember, the penultimate message before the > crash is the CARP partner's nexthop becoming valid. > > Just to throw the question out there. iBGP should always be a full mesh (or > use RRs etc), and so we run iBGP from both of the OpenBSD firewalls to every > other router, and I also run iBGP between the CARP pair themselves too. Is > the iBGP between the CARP pair really needed?? > I'd imagine not as they are always active-backup and one should not be > handing packets to the other etc.. (we only direct packets to the CARP > addresses as they are running as both stateful firewalls *and* stateless > routers, hence other posts here regarding trying to set the nexthop on BGP > announcements to the CARP IPs). It shouldn't be needed unless you are also carrying internal routes (i.e. networks behind the firewalls) in BGP.
Re: OpenBGPD crashing
Hi sorry to reply with a stupid question but I get this error; [LIVE]root@mg1311:~# pkg_add -i symon symon-2.86p0:libart-2.3.21: ok symon-2.86p0:png-1.6.2p0: ok Can't install rrdtool-1.2.30p3 because of libraries |library freetype.20.0 not found | not found anywhere Direct dependencies for rrdtool-1.2.30p3 resolve to png-1.6.2p0 libart-2.3.21 Full dependency tree is png-1.6.2p0 libart-2.3.21 Can't install symon-2.86p0: can't resolve rrdtool-1.2.30p3 I've come across this issue of missing freetype in the OpenBSD sources before in older versions. Anyway, I think you could be on the money as every time this has happened, it always happens just after seeing the message nexthop now valid. We don't use nexthop-self on our cisco routers which are connected to Transits and IXPs. At the moment the OpenBSD routers only have iBGP neighborships with two cisco ABR routers (no eBGP transit or IXP connections, just internal AS). Thus the BGP nexthop networks (transit and IXP links) are redistributed to the internal OpenBSD routers by IGP (OSPF) to validate the BGP nexthops and provide BGP prefix independent convergence. In most cases as far as I can remember, the penultimate message before the crash is the CARP partner's nexthop becoming valid. Just to throw the question out there. iBGP should always be a full mesh (or use RRs etc), and so we run iBGP from both of the OpenBSD firewalls to every other router, and I also run iBGP between the CARP pair themselves too. Is the iBGP between the CARP pair really needed?? I'd imagine not as they are always active-backup and one should not be handing packets to the other etc.. (we only direct packets to the CARP addresses as they are running as both stateful firewalls *and* stateless routers, hence other posts here regarding trying to set the nexthop on BGP announcements to the CARP IPs). Thanks for your thought Stuart. Cheers, Andy. On Wed 30 Apr 2014 04:14:55 BST, Stuart Henderson wrote: On 2014-04-28, Andy wrote: Yea thats all I see in /var/log/messages .. /var/log/daemon had; 2014-04-28T01:02:21.238360+01:00 mg1311 ospf6d[25154]: send_rtmsg: action 1, prefix ::/0: File exists 2014-04-28T01:02:22.048344+01:00 mg1311 ospfd[19386]: desync; scheduling fib reload 2014-04-28T01:02:32.518186+01:00 mg1311 ospfd[19386]: reloading interface list and routing table 2014-04-28T01:02:59.077656+01:00 mg1311 bgpd[18490]: nexthop 185.25.32.22 now valid: directly connected 2014-04-28T01:03:01.762457+01:00 mg1311 bgpd[18490]: dispatch_imsg in main: pipe closed 2014-04-28T01:03:01.762473+01:00 mg1311 bgpd[18490]: Lost child: route decision engine exited 2014-04-28T01:03:01.762756+01:00 mg1311 bgpd[18490]: kernel routing table 0 (Loc-RIB) decoupled 2014-04-28T01:03:01.778424+01:00 mg1311 bgpd[18490]: Terminating It had been up for about a month before this. bgpd on the carp backup is still up and running fine and never dies. It might be interesting to monitor memory use (symon is fairly good for this), one failure mode is that bgpd can't handle nexthop revalidation churn fast enough and the rde eats all memory (or at least runs into login.conf datasize limits - make sure these are sufficiently high if you haven't already done so). I don't remember all of the various ways this can show up in logs, but what you're seeing here does ring a bell. I work around this by only feeding a partial table to routers which are particularly likely to suffer ospf churn ... not ideal but stability improved a lot after doing that. (It used to happen more often but there was a change in 5.2 which seriously reduced the situations that trigger this). It's always been the master that falls over. I might make the other firewall the master and see if it still crashes on the same box. Is there anyway I can increase the session engine logging? There's bgpd_flags="-v" if you're not already using it - I'm not too sure if it will actually give you any more information but worth a try. Make sure syslogd does actually log the messages - I use memory buffer logs for these, syslogd_flags="-s /var/run/syslogd.sock" with this the top of syslog.conf: !!bgpd *.* :256:bgpd daemon.info /var/log/daemon !*
Re: Resolving the Lan users hostnames
On Tue, Apr 29, 2014 at 11:43 PM, Stuart Henderson wrote: > On 2014-04-28, sven falempin wrote: >> Reading unbound doc i saw i can insert name to be resolved but i have >> to each time > > configure things for unbound-control, then you can do > "unbond-control local_data somehost.exaple.com A 192.0.2.1". > would it be interesting to patch dhcpd (like Ted did) but directly call the unbound-control work (both are in base) ? using a suffix for the hostname given the default domain configured. -- - () ascii ribbon campaign - against html e-mail /\
Firefox tweaking
Hello,
I am running a very recent snapshot and I want to try Firefox again (now at
version -28.0p0). It seems that I get some unresponsive behaviour, like
intermitent scrolling, long delays for content rendering, etc. I must say
that I had no crash whatsoever. I am using Openbox as a window manager. I
have no plugins or extension installed in Firefox.
My dmesg is at the bottom, but I want to ask for a few tweaks for Firefox
tuning if those are available, please. If my hardware is too weak, then I
will go back to Chromium wich works faster for now.
Thank you.
OpenBSD 5.5-current (GENERIC) #63: Tue Apr 29 02:37:44 MDT 2014
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) 4 CPU 3.20GHz ("GenuineIntel" 686-class) 3.20 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,PBE,SSE3,DTES64,MWAIT,DS-CPL,CNXT-ID,xTPR,PERF
real mem = 1072132096 (1022MB)
avail mem = 1042214912 (993MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 01/21/08, BIOS32 rev. 0 @ 0xfd6dc,
SMBIOS rev. 2.34 @ 0xefc30 (52 entries)
bios0: vendor IBM version "2BKT53AUS" date 01/21/2008
bios0: IBM 814438G
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP TCPA APIC BOOT MCFG
acpi0: wakeup devices EXP0(S5) EXP1(S5) EXP2(S5) EXP3(S5) USB1(S3) USB2(S3)
USB3(S3) USB4(S3) USBE(S3) SLOT(S5) KBC_(S3) PSM_(S3) COMA(S5) COMB(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 199MHz
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xe000, bus 0-9
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PEG_)
acpiprt2 at acpi0: bus -1 (EXP0)
acpiprt3 at acpi0: bus -1 (EXP1)
acpiprt4 at acpi0: bus -1 (EXP2)
acpiprt5 at acpi0: bus -1 (EXP3)
acpiprt6 at acpi0: bus 10 (SLOT)
acpicpu0 at acpi0
acpitz0 at acpi0: critical temperature is 105 degC
acpibtn0 at acpi0: PWRB
bios0: ROM list: 0xc/0xf600 0xe/0x1!
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82915G Host" rev 0x04
ppb0 at pci0 dev 1 function 0 "Intel 82915G PCIE" rev 0x04: apic 1 int 16
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 0 function 0 "ATI Radeon X1650 Pro" rev 0x9e
drm0 at radeondrm0
radeondrm0: msi
"ATI Radeon X1650 Pro Sec" rev 0x9e at pci1 dev 0 function 1 not configured
uhci0 at pci0 dev 29 function 0 "Intel 82801FB USB" rev 0x03: apic 1 int 23
uhci1 at pci0 dev 29 function 1 "Intel 82801FB USB" rev 0x03: apic 1 int 19
uhci2 at pci0 dev 29 function 2 "Intel 82801FB USB" rev 0x03: apic 1 int 18
uhci3 at pci0 dev 29 function 3 "Intel 82801FB USB" rev 0x03: apic 1 int 16
ehci0 at pci0 dev 29 function 7 "Intel 82801FB USB" rev 0x03: apic 1 int 23
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb1 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xd3
pci2 at ppb1 bus 10
bge0 at pci2 dev 11 function 0 "Broadcom BCM5705K" rev 0x03, BCM5705 A3
(0x3003): apic 1 int 16, address 00:11:25:f6:32:36
brgphy0 at bge0 phy 1: BCM5705 10/100/1000baseT PHY, rev. 2
auich0 at pci0 dev 30 function 2 "Intel 82801FB AC97" rev 0x03: apic 1 int
17, ICH6 AC97
ac97: codec id 0x41445374 (Analog Devices AD1981B)
ac97: codec features headphone, 20 bit DAC, No 3D Stereo
audio0 at auich0
ichpcib0 at pci0 dev 31 function 0 "Intel 82801FB LPC" rev 0x03: PM disabled
pciide0 at pci0 dev 31 function 1 "Intel 82801FB IDE" rev 0x03: DMA,
channel 0 configured to compatibility, channel 1 configured to compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: ATAPI
5/cdrom removable
cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4
pciide0: channel 1 disabled (no drives)
pciide1 at pci0 dev 31 function 2 "Intel 82801FB SATA" rev 0x03: DMA,
channel 0 configured to native-PCI, channel 1 configured to native-PCI
pciide1: using apic 1 int 19 for native-PCI interrupt
wd0 at pciide1 channel 0 drive 0:
wd0: 16-sector PIO, LBA48, 305245MB, 625142448 sectors
wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 6
ichiic0 at pci0 dev 31 function 3 "Intel 82801FB SMBus" rev 0x03: apic 1
int 19
iic0 at ichiic0
adt0 at iic0 addr 0x2e: lm96000 rev 0x68
spdmem0 at iic0 addr 0x50: 256MB DDR SDRAM non-parity PC3200CL3.0
spdmem1 at iic0 addr 0x51: 256MB DDR SDRAM non-parity PC3200CL3.0
spdmem2 at iic0 addr 0x52: 512MB DDR SDRAM non-parity PC3200CL3.0
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb4 at uhci3: USB revision 1.0
uhub4 at usb4 "Intel UHCI root hub
Re: Can't replace /sbin/init
On Wed, Apr 30, 2014 at 12:02:22AM -0700, Ben Dibell wrote: > Hi, I've tried other resources, even reading the source for init, but I > can't seem to locate the magic that makes /sbin/init the approved init. > I'm porting my init system Epoch to BSD for personal reasons, and I'd like > it to work under OpenBSD, which I've been enjoying as of late. I come from > the linux world where init=/bin/sh is perfectly valid, so some aspects are > probably simpler in Linux. I am hoping there is a concise and clean > explanation as to how to write/port an init system to BSD. Is it signal > trickery? A checksum burned into the kernel? I'm lost. I'm given "init has > died, signal 0 exit 0" or something nearly identical to this. There are no > further useful debug messages and my keyboard becomes unresponsive on the > debugging prompt or the kernel locks up or something, so I can't do more > there. > > Thanks for your time. > > -Ben As far as am aware, any executable should do, as long as it is statically linked. I grepped for you error message, but could not find it. Please list the *exact* error you are getting, otherwise we cannot help you. -Otto
Re: Weird disklabel problem
On Wed, Apr 30, 2014 at 01:36:53AM -0600, Martijn Rijkeboer wrote: > Hello, > > I've got a weird disklabel related problem (or so it seems). When I > partition my harddisk with fdisk and add an OpenBSD (A6) primary > partition the system can still boot, but once I place a disklabel > on the partition (disklabel -E sd0) I can't boot the system anymore > (it freezes during the post). > > System Info: > - OS: OpenBSD-current AMD64 > - CPU: Intel Core i3 4130T > - Motherboard: Gigabyte GA-B85M-DS3H > - Harddisk: WD Green 1TB (SATA) > > It is possible that it's a Gigabyte specific problem since Karl > Karlsson has the same problem with his Gigabyte GA-Z87MX-DH3 > motherboard. > > The other strange thing is that if I use an USB-stick instead > of the harddisk I can install and boot OpenBSD without problems. > Even with the harddisk present, but without a disklabel, I can > still boot from the USB stick, but as soon as I place a disklabel > on the harddisk (although it isn't used, nor in the boot sequence) > the system freezes during the post again. > > Any suggestions on how to fix this or should I just buy a different > motherboard? > > Kind regards, > > > Martijn Rijkeboer Please post at least a dmesg with the disk attached but no disklabel plus fdisk and disklabel output after setting the label but before the (failing) reboot. -Otto
Weird disklabel problem
Hello, I've got a weird disklabel related problem (or so it seems). When I partition my harddisk with fdisk and add an OpenBSD (A6) primary partition the system can still boot, but once I place a disklabel on the partition (disklabel -E sd0) I can't boot the system anymore (it freezes during the post). System Info: - OS: OpenBSD-current AMD64 - CPU: Intel Core i3 4130T - Motherboard: Gigabyte GA-B85M-DS3H - Harddisk: WD Green 1TB (SATA) It is possible that it's a Gigabyte specific problem since Karl Karlsson has the same problem with his Gigabyte GA-Z87MX-DH3 motherboard. The other strange thing is that if I use an USB-stick instead of the harddisk I can install and boot OpenBSD without problems. Even with the harddisk present, but without a disklabel, I can still boot from the USB stick, but as soon as I place a disklabel on the harddisk (although it isn't used, nor in the boot sequence) the system freezes during the post again. Any suggestions on how to fix this or should I just buy a different motherboard? Kind regards, Martijn Rijkeboer
Can't replace /sbin/init
Hi, I've tried other resources, even reading the source for init, but I can't seem to locate the magic that makes /sbin/init the approved init. I'm porting my init system Epoch to BSD for personal reasons, and I'd like it to work under OpenBSD, which I've been enjoying as of late. I come from the linux world where init=/bin/sh is perfectly valid, so some aspects are probably simpler in Linux. I am hoping there is a concise and clean explanation as to how to write/port an init system to BSD. Is it signal trickery? A checksum burned into the kernel? I'm lost. I'm given "init has died, signal 0 exit 0" or something nearly identical to this. There are no further useful debug messages and my keyboard becomes unresponsive on the debugging prompt or the kernel locks up or something, so I can't do more there. Thanks for your time. -Ben
