clementine stutters when playing local files
Hi, When playing local mp3 files in clementine, there are frequent short skips. Listening to the same files over network (icecast) everything is ok. This is modern laptop with SSD disk, I guess it should be faster than wifi. Any advice on where should I start looking for solution? Thank you in advance, -- Marko Cupać https://www.mimar.rs/
Re: xfce4-power-manager not updating battery status
On Wed, 17 Dec 2014 17:33:36 +0100
Alessandro DE LAURENZIS just22@gmail.com wrote:
Maybe useless to say, but you should add the user session d-bus part
too; in .xinitrc, something like:
# Start a session bus instance of dbus-daemon
if [ -x /usr/local/bin/dbus-launch -a -z ${DBUS_SESSION_BUS_ADDRESS} ]; then
eval `dbus-launch --sh-syntax --exit-with-session`
fi
(see /usr/local/share/doc/pkg-readmes/dbus-x.y.z, maybe not needed if
your login/session manager does that for you).
Alessandro,
are you sure I need both dbus sessions? As far as I understand, it is
either system-wide dbus in pkg_scripts, or per-user, when one does not
want to run system-wide service.
--
Marko Cupać
https://www.mimar.rs/
Re: clementine stutters when playing local files
On Thu, 18 Dec 2014 09:13:31 +0100 Marko Cupać marko.cu...@mimar.rs wrote: Hi, When playing local mp3 files in clementine, there are frequent short skips. Listening to the same files over network (icecast) everything is ok. I searched around, and It appears that I have I/O bottleneck, as vmstat constantly shows blocked processes even though laptop does close to nothing: procsmemory pagediskstraps cpu r b wavm fre flt re pi po fr sr sd0 sd1 int sys cs us sy id 1 5 0 817348 6063372 680 0 0 0 0 0 11 1068 1911 26543 4849 6 6 88 2 5 0 817364 6063352 41 0 0 0 0 0 0 0 131 7076 933 4 0 96 2 5 0 817424 6063288 37 0 0 0 0 0 0 0 135 7334 983 3 1 96 1 5 0 817436 6067428 37 0 0 0 0 0 0 0 143 6822 921 3 1 96 1 5 0 817516 6067348 43 0 0 0 0 0 0 0 134 7337 976 5 0 95 0 5 0 817520 6067340 25 0 0 0 0 0 0 0 133 7001 939 3 1 96 1 5 0 817744 6067116 80 0 0 0 0 0 0 0 136 7419 998 4 0 96 2 5 0 817760 6067100 38 0 0 0 0 0 0 0 134 6944 936 2 1 97 2 5 0 818096 6066764 176 0 0 0 0 0 0 0 134 7668 1147 4 1 95 2 5 0 818124 6066720 34 0 0 0 0 0 2 0 132 6949 941 3 0 97 2 5 0 818420 6066424 112 0 0 0 0 0 0 0 141 8124 1058 3 2 95 1 5 0 818416 6066428 27 0 0 0 0 0 0 0 134 7435 981 3 1 96 2 5 0 818656 6066236 136 0 0 0 0 0 0 0 168 7714 1069 4 1 95 1 5 0 818672 6075136 27 0 0 0 0 0 0 0 141 7140 947 4 2 94 Here's atactl identify output: Model: KINGSTON SV300S37A240G, Rev: 521ABBF0, Serial #: 50026B72410EC74E Device type: ATA, fixed Cylinders: 16383, heads: 16, sec/track: 63, total sectors: 468862128 Device capabilities: ATA standby timer values IORDY operation IORDY disabling Device supports the following standards: ATA-2 ATA-3 ATA-4 ATA-5 ATA-6 ATA-7 ATA-8 Master password revision code 0xfffe Device supports the following command sets: NOP command READ BUFFER command WRITE BUFFER command Host Protected Area feature set Read look-ahead Write cache Power Management feature set Security Mode feature set SMART feature set Flush Cache Ext command Flush Cache command 48bit address feature set Set Max security extension commands Set Features subcommand required Power-up in standby feature set Advanced Power Management feature set DOWNLOAD MICROCODE command IDLE IMMEDIATE with UNLOAD FEATURE SMART self-test SMART error logging Device has enabled the following command sets/features: NOP command READ BUFFER command WRITE BUFFER command Host Protected Area feature set Read look-ahead Write cache Power Management feature set SMART feature set Flush Cache Ext command Flush Cache command 48bit address feature set Set Features subcommand required Advanced Power Management feature set DOWNLOAD MICROCODE command Any advice on where should I start looking for solution? Thank you in advance, -- Marko Cupać https://www.mimar.rs/
Re: xfce4-power-manager not updating battery status
On Thu, Dec 18, 2014 at 09:30:43AM +0100, Marko Cupać wrote:
On Wed, 17 Dec 2014 17:33:36 +0100
Alessandro DE LAURENZIS just22@gmail.com wrote:
Maybe useless to say, but you should add the user session d-bus part
too; in .xinitrc, something like:
# Start a session bus instance of dbus-daemon
if [ -x /usr/local/bin/dbus-launch -a -z ${DBUS_SESSION_BUS_ADDRESS} ];
then
eval `dbus-launch --sh-syntax --exit-with-session`
fi
(see /usr/local/share/doc/pkg-readmes/dbus-x.y.z, maybe not needed if
your login/session manager does that for you).
Alessandro,
are you sure I need both dbus sessions? As far as I understand, it is
either system-wide dbus in pkg_scripts, or per-user, when one does not
want to run system-wide service.
You need both, I believe.
On my system with XFCE running I see:
$ pgrep -fl dbus
6078 /usr/local/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
10590 /usr/local/bin/dbus-launch --sh-syntax --exit-with-session xfce4-session
20502 /usr/local/bin/dbus-daemon --system
Re: ospf point to point network
Hi, Not sure what want, but ospfd seems to properly detect interfaces, that are p2p by their nature (gif, gre, ppp, ) So I don't think it is necessary to specify. On 12/17/2014 06:25 PM, Kapetanakis Giannis wrote: Hi, I'd like to ask if point-to-point support has been added in ospfd. I've read this http://marc.info/?l=openbsd-miscm=136580208222751w=2 but I cant seem to find relevant entries in the source tree so probably is still out? regards, Giannis
Re: xfce4-power-manager not updating battery status
On Thu, 18 Dec 2014 10:52:42 +0100 Stefan Sperling s...@stsp.name wrote: You need both, I believe. On my system with XFCE running I see: $ pgrep -fl dbus 6078 /usr/local/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session 10590 /usr/local/bin/dbus-launch --sh-syntax --exit-with-session xfce4-session 20502 /usr/local/bin/dbus-daemon --system I tried both ways, with and without mentioned lines in ~/.xinitrc. I would still say that there is no need for them in ~/.xinitrc, as they are already in system-wide /etc/X11/xinit/xinitrc, as stated in mentioned pkg-readmes/dbus-X.X.X One way or another, battery status is still not updated in xfce4-power-manager. As for Stefan's suggestion for removing external battery, I have just tried it, and xfce4-power-manager still does not update status. Here's what sensors say without external battery: pacija@efreet:/usr/local/share/doc/pkg-readmes $ sysctl -a | grep bat hw.sensors.acpibat0.volt0=11.10 VDC (voltage) hw.sensors.acpibat0.volt1=12.38 VDC (current voltage) hw.sensors.acpibat0.power0=5.46 W (rate) hw.sensors.acpibat0.watthour0=18.86 Wh (last full capacity) hw.sensors.acpibat0.watthour1=0.94 Wh (warning capacity) hw.sensors.acpibat0.watthour2=0.20 Wh (low capacity) hw.sensors.acpibat0.watthour3=17.28 Wh (remaining capacity), OK hw.sensors.acpibat0.watthour4=23.20 Wh (design capacity) hw.sensors.acpibat0.raw0=2 (battery charging), OK After inserting external battery live, without reboot: pacija@efreet:/usr/local/share/doc/pkg-readmes $ sysctl -a | grep bat hw.sensors.acpibat0.volt0=11.10 VDC (voltage) hw.sensors.acpibat0.volt1=12.34 VDC (current voltage) hw.sensors.acpibat0.power0=0.00 W (rate) hw.sensors.acpibat0.watthour0=18.86 Wh (last full capacity) hw.sensors.acpibat0.watthour1=0.94 Wh (warning capacity) hw.sensors.acpibat0.watthour2=0.20 Wh (low capacity) hw.sensors.acpibat0.watthour3=17.78 Wh (remaining capacity), OK hw.sensors.acpibat0.watthour4=23.20 Wh (design capacity) hw.sensors.acpibat0.raw0=0 (battery idle), OK hw.sensors.acpibat1.volt0=0.00 VDC (voltage) hw.sensors.acpibat1.volt1=11.59 VDC (current voltage) hw.sensors.acpibat1.power0=25.05 W (rate) hw.sensors.acpibat1.watthour0=0.00 Wh (last full capacity) hw.sensors.acpibat1.watthour1=0.00 Wh (warning capacity) hw.sensors.acpibat1.watthour2=0.00 Wh (low capacity) hw.sensors.acpibat1.watthour3=1.08 Wh (remaining capacity), OK hw.sensors.acpibat1.watthour4=0.00 Wh (design capacity) hw.sensors.acpibat1.raw0=2 (battery full), OK While we are at it, which value is apm supposed to show? Combined acpibat0 and acpibat1? Thanks to all the participants for help. -- Marko Cupać https://www.mimar.rs/
Re: clementine stutters when playing local files
Yes, there are issues related to the fact that disk I/O causes major - from the audio's point of view - pauses. Unfortunately I'm not expert in this area, but this is what you could do: 1. Disable sonogram in Clementine. Yes, this helps a bit, but I was too lazy to investigate, why. :) 2. Try to _lower_ buffer sizes. Larger buffer causes larger read. Eventually I'll look at Clementine 2.x... -- Vadim Zhukov 18 дек. 2014 г. 12:23 полÑзоваÑÐµÐ»Ñ Marko CupaÄ marko.cu...@mimar.rs напиÑал: On Thu, 18 Dec 2014 09:13:31 +0100 Marko CupaÄ marko.cu...@mimar.rs wrote: Hi, When playing local mp3 files in clementine, there are frequent short skips. Listening to the same files over network (icecast) everything is ok. I searched around, and It appears that I have I/O bottleneck, as vmstat constantly shows blocked processes even though laptop does close to nothing: procsmemory pagediskstraps cpu r b wavm fre flt re pi po fr sr sd0 sd1 int sys cs us sy id 1 5 0 817348 6063372 680 0 0 0 0 0 11 1068 1911 26543 4849 6 6 88 2 5 0 817364 6063352 41 0 0 0 0 0 0 0 131 7076 933 4 0 96 2 5 0 817424 6063288 37 0 0 0 0 0 0 0 135 7334 983 3 1 96 1 5 0 817436 6067428 37 0 0 0 0 0 0 0 143 6822 921 3 1 96 1 5 0 817516 6067348 43 0 0 0 0 0 0 0 134 7337 976 5 0 95 0 5 0 817520 6067340 25 0 0 0 0 0 0 0 133 7001 939 3 1 96 1 5 0 817744 6067116 80 0 0 0 0 0 0 0 136 7419 998 4 0 96 2 5 0 817760 6067100 38 0 0 0 0 0 0 0 134 6944 936 2 1 97 2 5 0 818096 6066764 176 0 0 0 0 0 0 0 134 7668 1147 4 1 95 2 5 0 818124 6066720 34 0 0 0 0 0 2 0 132 6949 941 3 0 97 2 5 0 818420 6066424 112 0 0 0 0 0 0 0 141 8124 1058 3 2 95 1 5 0 818416 6066428 27 0 0 0 0 0 0 0 134 7435 981 3 1 96 2 5 0 818656 6066236 136 0 0 0 0 0 0 0 168 7714 1069 4 1 95 1 5 0 818672 6075136 27 0 0 0 0 0 0 0 141 7140 947 4 2 94 Here's atactl identify output: Model: KINGSTON SV300S37A240G, Rev: 521ABBF0, Serial #: 50026B72410EC74E Device type: ATA, fixed Cylinders: 16383, heads: 16, sec/track: 63, total sectors: 468862128 Device capabilities: ATA standby timer values IORDY operation IORDY disabling Device supports the following standards: ATA-2 ATA-3 ATA-4 ATA-5 ATA-6 ATA-7 ATA-8 Master password revision code 0xfffe Device supports the following command sets: NOP command READ BUFFER command WRITE BUFFER command Host Protected Area feature set Read look-ahead Write cache Power Management feature set Security Mode feature set SMART feature set Flush Cache Ext command Flush Cache command 48bit address feature set Set Max security extension commands Set Features subcommand required Power-up in standby feature set Advanced Power Management feature set DOWNLOAD MICROCODE command IDLE IMMEDIATE with UNLOAD FEATURE SMART self-test SMART error logging Device has enabled the following command sets/features: NOP command READ BUFFER command WRITE BUFFER command Host Protected Area feature set Read look-ahead Write cache Power Management feature set SMART feature set Flush Cache Ext command Flush Cache command 48bit address feature set Set Features subcommand required Advanced Power Management feature set DOWNLOAD MICROCODE command Any advice on where should I start looking for solution? Thank you in advance, -- Marko CupaÄ https://www.mimar.rs/
Re: ospf point to point network
On 18/12/14 11:59, Gregory Edigarov wrote: Hi, Not sure what want, but ospfd seems to properly detect interfaces, that are p2p by their nature (gif, gre, ppp, ) So I don't think it is necessary to specify. On 12/17/2014 06:25 PM, Kapetanakis Giannis wrote: Hi, I'd like to ask if point-to-point support has been added in ospfd. I've read this http://marc.info/?l=openbsd-miscm=136580208222751w=2 but I cant seem to find relevant entries in the source tree so probably is still out? regards, Giannis I'm not talking about p2p interfaces. I'm talking about normal ethernet interfaces (vlan) which should operate ospf in point-to-point network mode. G
constant blocked procs in vmstat
Hi, I have constant number of blocked procs in vmstat after xfce starts when system-wide dbus is enabled in pkg_scripts on my laptop: pacija@efreet:~ $ vmstat 1 10 procsmemory pagedisk traps cpu r b wavm fre flt re pi po fr sr sd0 int sys cs us sy id 1 4 0 201148 7327260 3506 0 0 0 0 0 228 340 14801 1258 2 2 96 0 4 0 201148 7327260 28 0 0 0 0 0 0 35 540 75 0 0 100 0 4 0 201156 7327248 42 0 0 0 0 0 0 625 2742 436 0 1 99 0 4 0 201160 7327240 13 0 0 0 0 0 0 256 904 138 0 0 100 0 4 0 201248 7327148 173 0 0 0 0 0 0 602 5636 737 0 0 100 0 4 0 201248 7327148 13 0 0 0 0 0 0 614 3147 460 0 0 100 0 4 0 201256 7327140 15 0 0 0 0 0 0 202 2064 238 0 0 100 0 4 0 201256 7327140 13 0 0 0 0 0 0 22 1355 170 0 0 100 0 4 0 201268 7327128 52 0 0 0 0 0 0 25 2183 399 1 0 99 0 4 0 201268 7327128 24 0 0 0 0 0 0 18 1518 185 0 0 100 If i disable system-wide dbus, it drops to constant 1. How can I find out what are blocked processes? And why are they constantly blocked? Thank you in advance, -- Marko Cupać https://www.mimar.rs/
Re: clementine stutters when playing local files
On Thu, 18 Dec 2014 16:12:38 +0400 Vadim Zhukov persg...@gmail.com wrote: Yes, there are issues related to the fact that disk I/O causes major - from the audio's point of view - pauses. Unfortunately I'm not expert in this area, but this is what you could do: 1. Disable sonogram in Clementine. Yes, this helps a bit, but I was too lazy to investigate, why. :) 2. Try to _lower_ buffer sizes. Larger buffer causes larger read. Eventually I'll look at Clementine 2.x... Hi Vadim, thank you for the tip. I lowered buffer size to 1000ms and disabled moodbar generation, and I do not experience any more stutters. What remains unanswered is why my 50€ SSD gives worse throughput than 5€ wifi adapter, but let's leave it for another thread. -- Marko Cupać https://www.mimar.rs/
Re: simple way to block one word domains?
On 2014-12-09 11:33, John Merriam wrote:
On Tue, 9 Dec 2014, Ted Unangst wrote:
Curious if anyone knows a simple way to prevent resolution of one word
hostnames. Either via resolv.conf or unbound.conf.
*snip*
I'm by no means a DNS expert but I've been dealing with it for a long
time. The only thing I can think of to force one word hostnames to be
resolved in the search domain exclusively would be to patch the
resolver
library.
*snip*
This TLD explosion bothers me too. After thinking about it for a while
I came up with a solution that works for me. It does not involve
patching the resolver library as I mentioned before. It would be nice
to patch the resolver library because it would guarantee that your
systems wouldn't look up any of the crummy TLDs that you don't want them
to regardless of what DNS servers they're using. But I decided against
doing that because I figured it would be a controversial issue and it
probably wouldn't be accepted for inclusion in OpenBSD and carrying
around local patches isn't fun.
So, I quickly hacked together a dirty little script I call tldblocker.
It downloads the list of TLDs from IANA then removes the TLDs you want
to allow then uses the trimmed TLD list that contains the TLDs you want
to block to create a file that can be included in your DNS server config
that points the blocked TLDs at an empty zone file. This isn't exactly
what you were looking for but I am sending it along in case you find it
useful.
Here is the script:
#!/usr/bin/perl
# tldblocker v0.0.1
# Use this at your own risk...
# You should check what this thing is really doing at least
occasionally.
$tldurl = http://data.iana.org/TLD/tlds-alpha-by-domain.txt;;
$adminaddress = admin\@example.com;
$allowedfile = /usr/local/var/tldblocker/tldblocker.allowedtlds;
$tldfile = /usr/local/var/tldblocker/tldblocker.alltlds;
$tempfile = /tmp/tldblocker.alltlds.temp;
$md5cmd = /bin/md5 -q;
$downloadcmd = /usr/local/bin/wget -q -O . $tempfile . . $tldurl;
$outfile = /var/named/namedb/named.zones.tldblocker;
$emptyzonefile = namedb/empty.zone;
$namedrestartcmd = /etc/rc.d/isc_named restart;
$smprog = /usr/sbin/sendmail;
if (!-s $allowedfile) {
# I think we should allow at least some TLDs!
die I could not find the allowed TLDs file!\n;
}
system $downloadcmd;
# Did download command exit with status 0?
if ($? != 0) {
# Download command failed, send message to admin...
system echo -e \Subject: tldblocker failed to download TLD
file!\\n\\ntldblocker failed to download the TLD file from the following
URL:\\n\\n$tldurl\\n\\nGo take a look.\ | $smprog $adminaddress;
exit 1;
}
# Do a basic sanity check on the downloaded file
open TLDFH, $tempfile;
@tldsin = TLDFH;
close TLDFH;
$quickcheck = join , @tldsin;
if (($tldsin[0] !~ /^# Version /) ||
($quickcheck !~ /\nCOM\n/i) ||
($quickcheck !~ /\nNET\n/i) ||
($quickcheck !~ /\nORG\n/i) ||
($quickcheck !~ /\nEDU\n/i) ||
($quickcheck !~ /\nGOV\n/i) ||
($quickcheck !~ /\nMIL\n/i) ||
($quickcheck !~ /\nINT\n/i) ||
($quickcheck !~ /\nARPA\n/i)) {
# This doesn't look right, send message to admin
system echo -e \Subject: tldblocker dowloaded TLD file failed sanity
check!\\n\\nThe TLD file downloaded by tldblocker from the following
URL:\\n\\n$tldurl\\n\\nfailed the basic sanity check. Go take a look.\
| $smprog $adminaddress;
exit 1;
}
undef $quickcheck;
# See if we need to do anything
$oldtldmd5 = `$md5cmd $tldfile`;
$newtldmd5 = `$md5cmd $tempfile`;
$oldallowedmd5 = `cat $allowedfile.MD5`;
$newallowedmd5 = `$md5cmd $allowedfile`;
$updateneeded = 0;
$dontunlink = 0;
if ($oldtldmd5 ne $newtldmd5) {
$updateneeded = 1;
system mv $tempfile $tldfile;
$dontunlink = 1;
}
if ($oldallowedmd5 ne $newallowedmd5) {
$updateneeded = 1;
system $md5cmd $allowedfile $allowedfile.MD5;
}
# Update if necessary
if ($updateneeded == 1) {
open ALLOWEDFH, $allowedfile;
@allowed = ALLOWEDFH;
close ALLOWEDFH;
$i = 0;
foreach $i (0..$#allowed) {
chomp $allowed[$i];
}
@blocktlds = @tldsin;
undef @tldsin;
splice @blocktlds, 0, 1;
$c = 0;
$blocktldsend = $#blocktlds;
while ($c = $blocktldsend) {
chomp $blocktlds[$c];
if ($blocktlds[$c] =~ /^([A-Za-z0-9\-])+$/) {
$i = 0;
foreach $i (0..$#allowed) {
if ($blocktlds[$c] =~ /^$allowed[$i]$/i) {
splice @blocktlds, $c, 1;
$c--;
$blocktldsend--;
last;
}
}
} else {
# Probably a comment?
splice @blocktlds, $c, 1;
$c--;
$blocktldsend--;
}
$c++;
}
if (($#blocktlds = 0) ($blocktlds[0] ne )) {
$i = 0;
foreach $i (0..$#blocktlds) {
$zonesout .= zone \;
$zonesout .= $blocktlds[$i];
$zonesout .= \ in { type master; file \;
$zonesout .= $emptyzonefile;
$zonesout .= \; };\n;
}
$zonesoutlen = length $zonesout;
open OUTFH, $outfile;
syswrite OUTFH, $zonesout,
Re: xfce4-power-manager not updating battery status
On Tue, 16 Dec 2014 22:29:29 +0100, Marko Cupać marko.cu...@mimar.rs wrote: Hi, not being satisfied with various Linux flavours on my ThinkPad T440, I have reverted back to OpenBSD. With the exception of non-supported internal wifi card (realtek usb dongle works more or less fine with urtwn), and not having sound over HDMI (I have dedicated another older laptop for HTPC use), I use it without significant problems so far. As a long time xfce user, I got used to monitor my battery status with xfce4-power-manager. Unfortunately, I don't have much use of it, as it does not update battery status in real time. Upon start it shows the correct status, but it does not update afterwards. I need to restart the application in order to update. Any chance for fixing this? Thank you in advance. Hi Marko, Can you provide the output of upower -d please? Cheers, Daniel
Re: DigitalOcean's BSD debut is FreeBSD only
Rather than discuss provider by provider, when looking for an OpenBSD VPS, look for KVM. OpenBSD runs on virtually any KVM provider and there are many, at both the low $3-4/month end and at the high end. I've run OpenBSD on KVM for several years at a variety of providers. OpenBSD obviously does not run on OpenVZ or Virtuozzo (as they are only virtualizing the OS, not the machine). With Xen, it depends as there are a couple different modes, but in the commercial marketplace, it seems most providers are supporting Linux only. Some providers (DO, Vultr, 6sync, etc.) are setup to only handle Linux but under the hood they'e running KVM and there is no technical barrier, though they may not want to support BSD. Other providers (AWS, Azure, etc.) are using internally modified Xen which may or may not provide full machine virtualization. People run FreeBSD at AWS and Azure, though I have not yet heard of anyone running OpenBSD there. OpenBSD also runs fine in VMware's server products but I haven't seen a lot of providers using that. In short - the list of VPS providers who can support OpenBSD is actually very big. Andrew Fabbro and...@fabbro.org https://raindog308.com
Re: DigitalOcean's BSD debut is FreeBSD only
On 14-12-18 12:06 PM, andrew fabbro wrote: In short - the list of VPS providers who can support OpenBSD is actually very big. I have to take issue with that statement... The list of VPS providers where OpenBSD will run, more or less correctly, more or less all of the time, is actually very big. It will even run correctly all of the time on a fairly large list of providers. However, the list of VPS providers who are willing to *support* OpenBSD is extremely small. What do you do if one day you're only getting 100kbps throughput? Call support, who - as soon as they learn you're running OpenBSD - tell you that's not supported, sorry and hang up. When ACPI goes haywire (normal under KVM so far)... same thing. Not naming names, but this isn't just a theoretical problem. If you're lucky, great - go get bargain-basement VPS hosting on KVM (or Xen or whatever happens to work for you). If you're not so lucky, or you need better guarantees that it might work, then your options are quite limited. -- -Adam Thompson athom...@athompso.net Cell: +1 204 291-7950 Fax: +1 204 489-6515
Re: DigitalOcean's BSD debut is FreeBSD only
On Thu, Dec 18, 2014 at 10:24 AM, Adam Thompson athom...@athompso.net wrote: The list of VPS providers where OpenBSD will run, more or less correctly, more or less all of the time, is actually very big. It will even run correctly all of the time on a fairly large list of providers. However, the list of VPS providers who are willing to *support* OpenBSD is extremely small Yes, this is true. With the unmanaged providers, OpenBSD is no better or worse than any other OS. The provider will help if there's something broken on the hardware they manage, but inside your VPS, you're on your own. And unfortunately, and perhaps not surprisingly, Linux distros running on a Linux virutalization tech (KVM) generally run fine out of the box while OpenBSD requires a bit more special handling (setting vio flags, turning APIC off, etc.) and tends to reveal more bugs in KVM. Even there, often times unmanaged providers are familiar with the typical problems a Debian or Centos VPS will have and will assist, while OpenBSD is alien to them. With managed providers...there are very few who support OpenBSD. running OpenBSD - tell you that's not supported, sorry and hang up. When ACPI goes haywire (normal under KVM so far)... I haven't had it go haywire per se, but sometimes have to turn it off during install, back on during regular use, and I have to turn APIC off. Oddly, the exact same settings with the exact same bsd.rd will cause a panic on one KVM and not on another.
Re: DigitalOcean's BSD debut is FreeBSD only
On Thu, Dec 18, 2014 at 12:24:45PM -0600, Adam Thompson wrote: On 14-12-18 12:06 PM, andrew fabbro wrote: In short - the list of VPS providers who can support OpenBSD is actually very big. I have to take issue with that statement... The list of VPS providers where OpenBSD will run, more or less correctly, more or less all of the time, is actually very big. It will even run correctly all of the time on a fairly large list of providers. However, the list of VPS providers who are willing to *support* OpenBSD is extremely small. What do you do if one day you're only getting 100kbps throughput? Call support, who - as soon as they learn you're running OpenBSD - tell you that's not supported, sorry and hang up. When ACPI goes haywire (normal under KVM so far)... same thing. Not naming names, And your bug report for this is ... where? -ml
Re: DigitalOcean's BSD debut is FreeBSD only
2014-12-18 19:37 GMT+01:00 andrew fabbro and...@fabbro.org: On Thu, Dec 18, 2014 at 10:24 AM, Adam Thompson athom...@athompso.net wrote: The list of VPS providers where OpenBSD will run, more or less correctly, more or less all of the time, is actually very big. It will even run correctly all of the time on a fairly large list of providers. However, the list of VPS providers who are willing to *support* OpenBSD is extremely small Yes, this is true. http://www.bsws.de/en/ http://www.bsws.de/en/sicherheit/ It is based on OpenBSD, if someone is interested. BS actively supports the development of OpenBSD (yup developers). Maybe it's worth to publish on openbsd.org a list of companies with such an offer (OpenBSD based VPS)? btw. I do not have nothing to do with them, provides a link only. Best regards, Daniel
Re: DigitalOcean's BSD debut is FreeBSD only
On 12/18/14 13:57, Mike Larkin wrote: On Thu, Dec 18, 2014 at 12:24:45PM -0600, Adam Thompson wrote: On 14-12-18 12:06 PM, andrew fabbro wrote: In short - the list of VPS providers who can support OpenBSD is actually very big. I have to take issue with that statement... The list of VPS providers where OpenBSD will run, more or less correctly, more or less all of the time, is actually very big. It will even run correctly all of the time on a fairly large list of providers. However, the list of VPS providers who are willing to *support* OpenBSD is extremely small. What do you do if one day you're only getting 100kbps throughput? Call support, who - as soon as they learn you're running OpenBSD - tell you that's not supported, sorry and hang up. When ACPI goes haywire (normal under KVM so far)... same thing. Not naming names, And your bug report for this is ... where? It was a hypothetical situation not a known issue. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: DigitalOcean's BSD debut is FreeBSD only
On Thu, Dec 18, 2014 at 10:57 AM, Mike Larkin mlar...@azathoth.net wrote: And your bug report for this is ... where? I thought about filing a bug report regarding a couple panics I've had on install (that went away with ACPI disabled in the provider's KVM control panel), but when I started to think about actually saying hey OpenBSD developers, I have a problem when running OpenBSD inside a Linux Kernel Virtualization Mode machine I just couldn't bring myself to do it. I was guessing that running OpenBSD inside the Linux kernel was not something that developers would be very interested in, particularly as the bugs are probably more likely to be outside OpenBSD than within it. However, if it would be beneficial to the project, I can certainly document and submit them.
Re: DigitalOcean's BSD debut is FreeBSD only
On 14-12-18 12:57 PM, Mike Larkin wrote: On Thu, Dec 18, 2014 at 12:24:45PM -0600, Adam Thompson wrote: On 14-12-18 12:06 PM, andrew fabbro wrote: In short - the list of VPS providers who can support OpenBSD is actually very big. I have to take issue with that statement... The list of VPS providers where OpenBSD will run, more or less correctly, more or less all of the time, is actually very big. It will even run correctly all of the time on a fairly large list of providers. However, the list of VPS providers who are willing to *support* OpenBSD is extremely small. What do you do if one day you're only getting 100kbps throughput? Call support, who - as soon as they learn you're running OpenBSD - tell you that's not supported, sorry and hang up. When ACPI goes haywire (normal under KVM so far)... same thing. Not naming names, And your bug report for this is ... where? -ml The last time I filed a bugreport on OpenBSD in a virtualized environment, I got flamed for not running it on real hardware. Haven't bothered since. However, that was a few years ago, and the ACPI shutdown issue is a big enough PITA that I'll file again soon. Difficult to debug, though, since the all I/O except wscons just freezes upon receipt of the ACPI signal. -- -Adam Thompson athom...@athompso.net
Re: DigitalOcean's BSD debut is FreeBSD only
Maybe it's worth to publish on openbsd.org a list of companies with such an offer (OpenBSD based VPS)? Maybe it is worth publishing a list of laptops OpenBSD works on? Or, maybe a list of ethernet cards. Is this purpose's project to maintain lists, or to try to make the code better as best as we can? I think it is better to just make things work as best we can, and let the market sort itself out. Managing the supply side is properly your burden.
Re: ospf point to point network
On 2014-12-17, Kapetanakis Giannis bil...@edu.physics.uoc.gr wrote: Hi, I'd like to ask if point-to-point support has been added in ospfd. I've read this http://marc.info/?l=openbsd-miscm=136580208222751w=2 but I cant seem to find relevant entries in the source tree so probably is still out? regards, Giannis No, diff didn't work so it wasn't added.
Re: support update
Hi All. Does anyone know if this is being updated? Dhu On Tue, 16 Dec 2014 09:43:18 -0700 Duncan Patton a Campbell campb...@neotext.ca wrote: # This version of the template is a bib-like file with one # line per field except notes, which can be any number of lines. # All I want to get back from you is lines like these (minus the # # character and the tab indent): # 0 This line is a delimiter and must be first (digit zero at the start) # C USA # P Arizona # T Cactus Grove # Z Postal Code # A General Delivery # O Acme Widgets # I Wile E. Coyote # M w.coy...@acme.com # U http://www.acme.com/openbsd # B 555-555-1212 # X 555-555-1213 # N Home of the best Acme # widgets around. # # Do not bother sending this in unless your web site's main page clearly shows # that you are engaged in providing support services for OpenBSD. # We reserve the right to delete listings that no longer do so. # # DELETE ALL # COMMENT LINES BEFORE SUBMITTING # # SEND AS PLAIN TEXT IN THE BODY OF YOUR MAIL: NO MIME OR ATTACHMENTS! # Use html character entities (like egrave;) for accented characters. # We reserve the right to edit any and all submissions as we please. 0 C Canada P Alberta T Edmonton Z T6A-2P7 O Neotext I Duncan Patton a Campbell A 10908-65a st. M campb...@neotext.ca U http://www.neotext.com/ # with trailing slash unless a specific resource B 780 466 0109 X 780 469 0930 N Open Systems Integration and Reverse-Engineering, Legacy Sytems, RealTime AI, Air Traffic Control, Remote Sensing, TestBed/Laboratory Development, Remote/Onsite Support, Wireless, RFID, Tracking/Mapping Systems, Barcoding, Inventory/supply-line, SAP integration, C3I, Web Catalogs, Competitive Intelligence Search Engines, Risk AssessmentReduction, Motorola, Intermec, Symbol devices. UNIX -- OpenBSD, FreeBSD, HPUX, Solaris/SunOS in Industrial Environments. And PCs: (Minix, Desqview, QNX) 30+ years experience, competence and integrity. secure(ish) contact point -- https://neotext.ca/cgi-bin/getxt -- Ne obliviscaris, vix ea nostra voco. -- Ne obliviscaris, vix ea nostra voco.
Re: DigitalOcean's BSD debut is FreeBSD only
On Thu, Dec 18, 2014 at 01:21:47PM -0600, Adam Thompson wrote: On 14-12-18 12:57 PM, Mike Larkin wrote: On Thu, Dec 18, 2014 at 12:24:45PM -0600, Adam Thompson wrote: On 14-12-18 12:06 PM, andrew fabbro wrote: In short - the list of VPS providers who can support OpenBSD is actually very big. I have to take issue with that statement... The list of VPS providers where OpenBSD will run, more or less correctly, more or less all of the time, is actually very big. It will even run correctly all of the time on a fairly large list of providers. However, the list of VPS providers who are willing to *support* OpenBSD is extremely small. What do you do if one day you're only getting 100kbps throughput? Call support, who - as soon as they learn you're running OpenBSD - tell you that's not supported, sorry and hang up. When ACPI goes haywire (normal under KVM so far)... same thing. Not naming names, And your bug report for this is ... where? -ml The last time I filed a bugreport on OpenBSD in a virtualized environment, I got flamed for not running it on real hardware. Haven't bothered since. However, that was a few years ago, and the ACPI shutdown issue is a big enough PITA that I'll file again soon. Difficult to debug, though, since the all I/O except wscons just freezes upon receipt of the ACPI signal. -- -Adam Thompson athom...@athompso.net It would be useful to at least see if this is a real ACPI issue or if this some problem KVM is causing. The former will elicit more sympathy than the latter. -ml
Re: Dell R630 high interrupts on acpi0
Hi!
The diff for extracting memory ranges from ACPI was obviously not tested
with ACPI disabled...so we definitely have to check if the values in
pcimem_range make some sense. The diff below now uses the old values in
case ACPI is disabled or does not return valid values.
I hope this is somewhat interesting for someone else as well :)
Please let me know if this is just noise or if there is anything else I
am missing.
Index: sys/arch/amd64/include/pci_machdep.h
===
RCS file: /cvs/src/sys/arch/amd64/include/pci_machdep.h,v
retrieving revision 1.22
diff -u -p -b -r1.22 pci_machdep.h
--- sys/arch/amd64/include/pci_machdep.h6 Nov 2013 10:40:36 -
1.22
+++ sys/arch/amd64/include/pci_machdep.h17 Dec 2014 06:00:01 -
@@ -64,6 +64,7 @@ extern int pci_mcfg_min_bus, pci_mcfg_ma
struct pci_attach_args;
+extern uint64_t pcimem_range[2];
extern struct extent *pciio_ex;
extern struct extent *pcimem_ex;
extern struct extent *pcibus_ex;
Index: sys/arch/amd64/pci/pci_machdep.c
===
RCS file: /cvs/src/sys/arch/amd64/pci/pci_machdep.c,v
retrieving revision 1.60
diff -u -p -b -r1.60 pci_machdep.c
--- sys/arch/amd64/pci/pci_machdep.c16 Dec 2014 23:13:20 - 1.60
+++ sys/arch/amd64/pci/pci_machdep.c18 Dec 2014 22:01:29 -
@@ -66,6 +66,7 @@
*/
#include sys/types.h
+#include sys/stdint.h
#include sys/param.h
#include sys/time.h
#include sys/systm.h
@@ -592,6 +593,7 @@ pci_intr_disestablish(pci_chipset_tag_t
intr_disestablish(cookie);
}
+uint64_t pcimem_range[2] = {UINT64_MAX, 0};
struct extent *pciio_ex;
struct extent *pcimem_ex;
struct extent *pcibus_ex;
@@ -618,31 +620,32 @@ pci_init_extents(void)
if (pcimem_ex == NULL) {
/*
-* Cover the 36-bit address space addressable by PAE
-* here. As long as vendors continue to support
-* 32-bit operating systems, we should never see BARs
-* outside that region.
-*
-* Dell 13G servers have important devices outside the
-* 36-bit address space. Until we can extract the address
-* ranges from ACPI, expand the allowed range to suit.
+* Cover the address space extracted from
+* ACPI. Fallback to fixed ranges in case ACPI is
+* disabled or reporting an invalid address range.
*/
+ if(pcimem_range[0] = pcimem_range[1]) {
+ pcimem_range[0] = 0;
+ pcimem_range[1] = 0x400UL;
+ }
+
pcimem_ex = extent_create(pcimem, 0, 0xUL,
M_DEVBUF, NULL, 0, EX_NOWAIT);
if (pcimem_ex == NULL)
return;
- extent_alloc_region(pcimem_ex, 0x400UL,
- 0xfc00UL, EX_NOWAIT);
+ extent_alloc_region(pcimem_ex, pcimem_range[1] + 1,
+ (0xUL - pcimem_range[1]), EX_NOWAIT);
for (bmp = bios_memmap; bmp-type != BIOS_MAP_END; bmp++) {
/*
-* Ignore address space beyond 4G.
+* Ignore address space beyond fixed/extracted
+* address range.
*/
- if (bmp-addr = 0x1ULL)
+ if (bmp-addr pcimem_range[1])
continue;
size = bmp-size;
- if (bmp-addr + size = 0x1ULL)
- size = 0x1ULL - bmp-addr;
+ if (bmp-addr + size pcimem_range[1])
+ size = pcimem_range[1] - bmp-addr + 1;
/* Ignore zero-sized regions. */
if (size == 0)
Index: sys/dev/acpi/acpi.c
===
RCS file: /cvs/src/sys/dev/acpi/acpi.c,v
retrieving revision 1.277
diff -u -p -b -r1.277 acpi.c
--- sys/dev/acpi/acpi.c 9 Dec 2014 06:58:29 - 1.277
+++ sys/dev/acpi/acpi.c 17 Dec 2014 05:59:36 -
@@ -385,0 +385,0 @@ TAILQ_HEAD(, acpi_pci) acpi_pcirootdevs
int acpi_getpci(struct aml_node *node, void *arg);
int acpi_getminbus(union acpi_resource *crs, void *arg);
+int acpi_getmemrange(union acpi_resource *crs, void *arg);
+
+int
+acpi_getmemrange(union acpi_resource *crs, void *arg)
+{
+ int typ = AML_CRSTYPE(crs);
+ uint64_t *range = arg; /* size 2 */
+ uint64_t min, max;
+
+ switch(typ) {
+ case LR_24BIT:
+ min = crs-lr_m24._min;
+ max = crs-lr_m24._max;
+ break;
+ case LR_32BIT:
+ case LR_32BITFIXED:
+ min =
Re: DigitalOcean's BSD debut is FreeBSD only
On Thu, 18 Dec 2014, andrew fabbro wrote: Rather than discuss provider by provider, when looking for an OpenBSD VPS, look for KVM. OpenBSD runs on virtually any KVM provider and there are many, at both the low $3-4/month end and at the high end. I've run OpenBSD on KVM for several years at a variety of providers. FYI, Xen [free] is also usable with OpenBSD, .. makes a great VM platform, been using it for years here in the shop. Lee
Re: xfce4-power-manager not updating battery status
On 12/18/2014 01:52 AM, Stefan Sperling wrote:
On Thu, Dec 18, 2014 at 09:30:43AM +0100, Marko Cupać wrote:
On Wed, 17 Dec 2014 17:33:36 +0100
Alessandro DE LAURENZIS just22@gmail.com wrote:
Maybe useless to say, but you should add the user session d-bus part
too; in .xinitrc, something like:
# Start a session bus instance of dbus-daemon
if [ -x /usr/local/bin/dbus-launch -a -z ${DBUS_SESSION_BUS_ADDRESS} ];
then
eval `dbus-launch --sh-syntax --exit-with-session`
fi
(see /usr/local/share/doc/pkg-readmes/dbus-x.y.z, maybe not needed if
your login/session manager does that for you).
Alessandro,
are you sure I need both dbus sessions? As far as I understand, it is
either system-wide dbus in pkg_scripts, or per-user, when one does not
want to run system-wide service.
You need both, I believe.
On my system with XFCE running I see:
$ pgrep -fl dbus
6078 /usr/local/bin/dbus-daemon --fork --print-pid 5 --print-address 7
--session
10590 /usr/local/bin/dbus-launch --sh-syntax --exit-with-session xfce4-session
20502 /usr/local/bin/dbus-daemon --system
I see the exact same thing as you show above, but did nothing to start it
twice, so
assume XFCE4 is doing that for me.
There is language in /etc/xdg/xfce4/xinitrc to check for a properly operating
dbus and launch one if needed.
--
Those who do not understand Unix are condemned to reinvent it, poorly.
xfce4/apm Power-Management falls off a cliff
Upon, pulling the plug from the wall on my older Toshiba Satellite (which has a new-ish battery) both xfce4 and apm agree while reporting declining battery power down to about 85% then both fall off a cliff and immediately indicate 8% and start warning about imminent battery exhaustion. 85% to 8% in the blink of an eye. And nothing in between. If I plug it back in, let it charge for a 10 minutes, it will be back up around 24%. If I again unplug, it will drop roughly in a linear fashion. with no sudden drops. This seems like a bug in what ever apm and xfce4 use to obtain readings. Any clue where I should start looking for this? -- Those who do not understand Unix are condemned to reinvent it, poorly.
OpenBSD sound system
hello, I am willing to know the sound system of OpenBSD, so I started to read the manpages. I summarized with a graph below, it is right? sndio(7): The sndio audio and MIDI system provides access to audio and MIDI hardware and to services provided by sndiod, summarized below. |--| |--| |--| | app1 | | app2 | | appN | |--| |--| |--| || | \|/ \|/ \|/ |---| |sndio.h| | sio_open(3)/mio_open(3) | | interface to audio devices and MIDI streams | |---| | \|/ |---| | sndiod(1) | | audio/midi server | |---| | | \|/ \|/ || |-| | audio(4) | | midi(4) | | device-independent | | raw device | |driver layer| | independent | || | interface | ||-| | | \|/ \|/ |-| |device dependent driver | | (azalia(4), ac97(4), ...) | |-| | \|/ |--| | [audio][MIDI] | | | | Hardware| |--| Regards Alfonso -- Alfonso Sabato Siciliano alfi...@gmail.com
suggested change to upgrade56.html
Because this is a new thing that even experienced users can easily forget (like I did)... Index: faq/upgrade56.html === RCS file: /cvs/www/faq/upgrade56.html,v retrieving revision 1.10 diff -u -r1.10 upgrade56.html --- faq/upgrade56.html10 Nov 2014 12:11:12 -1.10 +++ faq/upgrade56.html19 Dec 2014 03:33:50 - @@ -661,7 +661,8 @@ p The package tools support in-place updating using ttpkg_add -u/tt. -For instance, to update all your packages, make sure ttPKG_PATH/tt is +For instance, to update all your packages, make sure ttPKG_PATH/tt (and +/etc/pkg.conf if applicable) is pointing to the 5.6 packages directory on your CD or nearest FTP mirror, and use something like -- -Adam Thompson athom...@athompso.net
Re: DigitalOcean's BSD debut is FreeBSD only
On 19/12/14 08:21, Adam Thompson wrote: The last time I filed a bugreport on OpenBSD in a virtualized environment, I got flamed for not running it on real hardware. Haven't bothered since. Ummm... Harden up. Flames are common around here. But I feel your pain. I use VPS to run OpenBSD in two places. I have been following this thread with interest. Some cheap VPS providers allow you to use a custom ISO which is a straight forward process, but looking at this thread I am wondering if I have the whole picture. Is this a suggestion for a new chapter in the FAQ? Worik -- Why is the legal status of chardonnay different to that of cannabis? worik.stan...@gmail.com 021-1680650, (03) 4821804 Aotearoa (New Zealand) I voted for love
Re: xfce4/apm Power-Management falls off a cliff
On Thu, Dec 18, 2014 at 08:14:03PM EST, Jason Adams wrote: Upon, pulling the plug from the wall on my older Toshiba Satellite (which has a new-ish battery) ^^^ Given that batteries are treated as consumables nowadays and their lifespan deteriorates at various rates, I'd personally start there. Do some tests with a timer, i.e. how long does the battery keep the power for, leave it running to way below 8%, how long does it show 8%, and below, for and what's the running time after that. Testing with another battery would be ideal. Regards, Raf
Re: OpenBSD sound system
On 19.12.2014 04:28, Alfonso Sabato Siciliano wrote: hello, I am willing to know the sound system of OpenBSD, so I started to read the manpages. I summarized with a graph below, it is right? You may want to read these two as well http://www.openbsd.org/papers/asiabsdcon2010_sndio_slides.pdf http://www.openbsd.org/papers/asiabsdcon2010_sndio.pdf sndio(7): The sndio audio and MIDI system provides access to audio and MIDI hardware and to services provided by sndiod, summarized below. |--| |--| |--| | app1 | | app2 | | appN | |--| |--| |--| || | \|/ \|/ \|/ |---| |sndio.h| | sio_open(3)/mio_open(3) | | interface to audio devices and MIDI streams | |---| | \|/ |---| | sndiod(1) | | audio/midi server | |---| | | \|/ \|/ || |-| | audio(4) | | midi(4) | | device-independent | | raw device | |driver layer| | independent | || | interface | ||-| | | \|/ \|/ |-| |device dependent driver | | (azalia(4), ac97(4), ...) | |-| | \|/ |--| | [audio][MIDI] | | | | Hardware| |--| Regards Alfonso -- Alfonso Sabato Siciliano alfi...@gmail.com
About special configs to do in OpenBSD for KVM environments
Hi all, Please, first of all, I don't want to start a flame or quite similar. I only want to know what problems I can encounter when I need to install OpenBSD in kvm environments (mostly CentOS 6.x servers). Yes, I know, OpenBSD is not supported to run in virtualization environments, but many of us only have access to that kind of environments for testing (new pf rules, updates, etc). We can't use physical server and although I am not a big fan of this type of technology, it is here to stay. My questions are KVM specific. As far as I know: a) OpenBSD/i386: turn APIC off and set up vio flags to 0x02 b) OpenBSD/amd64: set up vio flags to 0x02 Anything else??
Re: About special configs to do in OpenBSD for KVM environments
On 2014 Dec 19 (Fri) at 07:35:28 + (+), C. L. Martinez wrote: :b) OpenBSD/amd64: set up vio flags to 0x02 The man page for vio(4) says: Setting the bit 0x2 in the flags disables the RingEventIndex feature. This can be tried as a workaround for possible bugs in host implementations of vio at the cost of slightly reduced performance. What bugs in the host implementation, which versions are affected, how bad is the performance hit, and should this be the default? -- California is a fine place to live -- if you happen to be an orange. -- Fred Allen
Re: About special configs to do in OpenBSD for KVM environments
19 дек. 2014 г. 10:36 полÑзоваÑÐµÐ»Ñ C. L. Martinez carlopm...@gmail.com напиÑал: Hi all, Please, first of all, I don't want to start a flame or quite similar. I only want to know what problems I can encounter when I need to install OpenBSD in kvm environments (mostly CentOS 6.x servers). Yes, I know, OpenBSD is not supported to run in virtualization environments, but many of us only have access to that kind of environments for testing (new pf rules, updates, etc). We can't use physical server and although I am not a big fan of this type of technology, it is here to stay. My questions are KVM specific. As far as I know: a) OpenBSD/i386: turn APIC off and set up vio flags to 0x02 b) OpenBSD/amd64: set up vio flags to 0x02 Anything else?? I have few 5.5/amd64 in production under CentOS 6.2, without either direct or indirect access to Internet. No problems so far, no adjustments on OpenBSD side. -- Vadim Zhukov
