Re: davical on openbsd

2015-04-18 Thread Denis Fondras
 the UI is a bit dated (but who needs it besides admin?)
 

That's why I use https://github.com/ledeuns/davical-cmdlnut :)



Re: Usb-audio not working

2015-04-18 Thread Max Fillinger
On Fri, Apr 17, 2015 at 10:04:32PM +, Stuart Henderson wrote:
 On 2015-04-17, Timo Myyra timo.my...@wickedbsd.net wrote:
  After setting the sdiod_flags I get sound from headset but its distorted.
 
 This code isn't fully working yet.
 

FWIW, it works for me when the USB DAC is the only device on a hub.



Dmesg of Lenovo X250

2015-04-18 Thread Ville Valkonen
Hello,

dmesg of Lenovo X250 running snapshot dated on:
-rw-r--r--  1 1001  0   1889 Apr 15 15:57:09 2015 SHA256.sig

Most of the things work.

List of things that doesn't work:
  - Wireless network, though I'd guess this will start to work once the
firmware URL path points to snapshots again.
+  These lines appear in dmesg after scan and trying to join a
wap (scan works though):
   iwm0: hw rev: 0x210, fw ver 25.228 (API ver 9), address 60:57:18:6a:df:8d
   iwm0: could not initiate scan
  - Suspend, goes to sleep but doesn't resume.
  - X acceleration, VESA works though.
  - CPU turbomode doesn't work (I am aware it's mainly a marketing trick) and
CPUs seems to get recognized with different MHz on every boot:
cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.66 MHz
And different boot:
cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.60 MHz
cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 MHz
  - A few devices didn't get recognized:
$ dmesg |grep -i not 
intagp at vga1 not configured
Intel 9 Series MEI rev 0x03 at pci0 dev 22 function 0 not configured
Intel 9 Series Thermal rev 0x03 at pci0 dev 31 function 6 not configured


snip
### Dmesg
OpenBSD 5.7-current (GENERIC.MP) #926: Wed Apr 15 15:43:34 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8277168128 (7893MB)
avail mem = 8022466560 (7650MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xccbfd000 (64 entries)
bios0: vendor LENOVO version N10ET28W (1.05 ) date 01/23/2015
bios0: LENOVO 20CLS06D00
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT SSDT
SSDT SSDT SSDT SSDT SSDT PCCT SSDT UEFI POAT BATB FPDT UEFI DMAR
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.66 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.24 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.24 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.24 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 2 (EXP1)
acpiprt3 at acpi0: bus 3 (EXP2)
acpiprt4 at acpi0: bus -1 (EXP3)
acpicpu0 at acpi0: C3, C1, PSS
acpicpu1 at acpi0: C3, C1, PSS
acpicpu2 at acpi0: C3, C1, PSS
acpicpu3 at acpi0: C3, C1, PSS
acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1
acpipwrres1 at acpi0: NVP3, resource for PEG_
acpipwrres2 at acpi0: NVP2, resource for PEG_
acpitz0 at acpi0: critical 

Re: Dmesg of Lenovo X250

2015-04-18 Thread Theo de Raadt
 dmesg of Lenovo X250 running snapshot dated on:
 -rw-r--r--  1 1001  0   1889 Apr 15 15:57:09 2015 SHA256.sig
 
 Most of the things work.
 
 List of things that doesn't work:
   - Wireless network, though I'd guess this will start to work once the
 firmware URL path points to snapshots again.
 +  These lines appear in dmesg after scan and trying to join a
 wap (scan works though):
iwm0: hw rev: 0x210, fw ver 25.228 (API ver 9), address 
 60:57:18:6a:df:8d
iwm0: could not initiate scan
   - Suspend, goes to sleep but doesn't resume.
   - X acceleration, VESA works though.
   - CPU turbomode doesn't work (I am aware it's mainly a marketing trick) and
 CPUs seems to get recognized with different MHz on every boot:
 cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.66 MHz
 And different boot:
 cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.60 MHz
 cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 MHz
   - A few devices didn't get recognized:
 $ dmesg |grep -i not 
 intagp at vga1 not configured
 Intel 9 Series MEI rev 0x03 at pci0 dev 22 function 0 not configured
 Intel 9 Series Thermal rev 0x03 at pci0 dev 31 function 6 not configured


There are one or two in the project now, and some work to make them
work...

Support for newer generations of machines becomes rapidly better once
more developers have them HINT.



Re: OpenBSD hosting in Hong Kong?

2015-04-18 Thread Rick Hanson
FWIW I have had an OpenBSD VPS with these dudes for about 6 months now.

https://www.vultr.com/

No downtime, no problems yet.  (Yeah, I know, it's not a lot of time.)  As
Paul said, they're not OpenBSD centric, but they allow you to install from
ISOs.  They have a web management interface, all SSD drives, snapshots,
data centers all over the globe, pricing, etc. all of which look a lot like
Digital Ocean BTW; but in addition to SSD, vultr has HDD (that's nice when
you need storage more than IO performance).

There are also a few smaller outfits that will probably give you really
good service too.  Keep your eyes open.



Re: OpenBSD hosting in Hong Kong?

2015-04-18 Thread Edgar Pettijohn III
On Apr 18, 2015, at 6:39 PM, Rick Hanson wrote:

 FWIW I have had an OpenBSD VPS with these dudes for about 6 months now.
 
 https://www.vultr.com/
 
 No downtime, no problems yet.  (Yeah, I know, it's not a lot of time.)  As
 Paul said, they're not OpenBSD centric, but they allow you to install from
 ISOs.  They have a web management interface, all SSD drives, snapshots,
 data centers all over the globe, pricing, etc. all of which look a lot like
 Digital Ocean BTW; but in addition to SSD, vultr has HDD (that's nice when
 you need storage more than IO performance).
 
 There are also a few smaller outfits that will probably give you really
 good service too.  Keep your eyes open.
 

I've been using vultr.com for about a year now and no problems.



Re: davical on openbsd

2015-04-18 Thread Landry Breuil
On Fri, Apr 17, 2015 at 1:16 PM, Marcus MERIGHI mcmer-open...@tor.at wrote:

 paol...@gmail.com (Paolo Aglialoro), 2015.04.15 (Wed) 03:10 (CEST):
  is there someone who already had experiences with davical in
  production on openbsd?

Yes, been running it at work since 6 years, previously on debian and
then on openbsd. Also a personal instance for caldav  carddav, using
lightning/thunderbird on the client side or caldav/carddav-sync on
android.
Just works.

  and internals'/externals' invitations?

invitations just work fine with lightning. Havent tested another client.


 Are you sure you've chosen the right tool (davical) for the task
 (caldav)? Please read the archives:

 most traffic:
 https://lists.sourceforge.net/lists/listinfo/davical-general
 seldom used:
 https://lists.sourceforge.net/lists/listinfo/davical-devel

 summary: original author left, project is being taken over by a
 community.

Just because the traffic is low doesnt really mean anything. davical
has been here for years, and has a big existing userbase (including
clients with iThings). Sure it's php, the UI is a bit dated (but who
needs it besides admin?) and the install procedure is a bit
cumbersome, but once it runs you dont need to touch it anymore.

Landry



Re: not known intel ethernet card

2015-04-18 Thread Holger Glaess
hi

dont worry , i'm happy that you care about this problem so fast.

holger

Am 17.04.2015 um 22:18 schrieb Dariusz Swiderski:
 Hi,

 was not quite expecting that, new diff is being cooked up, but expect 
 it later this night

 greets
 -- 
 Maciej 'sfires' Swiderski
 ---
 SysAdm | SecOff  | DS14145-RIPE| DS11-6BONE
 193.178.161.0/24 | 3ffe:8010:7:2a::/64 | AS16288
 ---
 A mouse is a device used to point at the xterm you want to type in.

 On 17 kwi 2015, at 18:45, Holger Glaess gla...@glaessixs.de 
 mailto:gla...@glaessixs.de wrote:

 hi

 Am 17.04.2015 um 13:28 schrieb Dariusz Swiderski:
 hi

 is this only on em1?
 yes just em1
 and can you try plugging each of this port to a switch and see in 
 ifconfig if
 media gets
 negotiated?
 i did and no negoation ,
 ifconfig says no link because the link led is on.

 if i do an ifconfig em3 up

 em3: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
lladdr 00:14:b7:00:61:66
priority: 0
media: Ethernet autoselect (1000baseT full-duplex)
status: active

 if i pull the cable

 same result like ahead.

 holger




 greets
 --
 Maciej 'sfires' Swiderski
 ---
 SysAdm | SecOff  | DS14145-RIPE| DS11-6BONE
 193.178.161.0/24 | 3ffe:8010:7:2a::/64 | AS16288
 ---
 A mouse is a device used to point at the xterm you want to type in.

 On 17 kwi 2015, at 13:21, Holger Glaess gla...@glaessixs.de 
 mailto:gla...@glaessixs.de wrote:

 hi

 looks good , but this unable to read is coming from
 not connected port ?

 Holger


 # dmesg | grep ^em
 em0 at pci1 dev 0 function 0 Intel 82574L rev 0x00: msi, address
 00:14:b7:00:61:63
 em1 at pci3 dev 0 function 0 Intel EP80579 LAN rev 0x01: apic 2 
 int 16,
 address 00:14:b7:00:61:64
 em2 at pci3 dev 1 function 0 Intel EP80579 LAN rev 0x01: apic 2 
 int 17,
 address 00:14:b7:00:61:65
 em3 at pci3 dev 2 function 0 Intel EP80579 LAN rev 0x01: apic 2 
 int 18,
 address 00:14:b7:00:61:66
 em1: unable to read phy 0 reg 2
 em1: unable to read phy 0 reg 3
 em1: unable to read phy 0 reg 2
 em1: unable to read phy 0 reg 3
 em1: unable to read phy 0 reg 2
 em1: unable to read phy 0 reg 3
 em1: unable to read phy 0 reg 1
 em1: unable to read phy 0 reg 1
 em1: unable to read phy 0 reg 1
 em1: unable to read phy 0 reg 1



 hi

 please apply attached patch on top of the previous one, build and 
 reboot
 :)

 greets
 dms

 On Fri, 17 Apr 2015, Holger Glaess wrote:

 hi

 after build and boot the a patched kernel
 i see now the em interface but
 he show an eeprom error.


 see demsg

 Holger

 OpenBSD 5.7-stable (GENERIC) #10: Fri Apr 17 10:48:45 CEST 2015
 root@DAF.rocki.intern 
 mailto:root@DAF.rocki.intern:/usr/src/sys/arch/i386/compile/GENERIC
 cpu0: Genuine Intel(R) processor 1.20GHz (GenuineIntel 
 686-class) 1.21
 GHz
 cpu0:

 FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,A
 CPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,PERF
 real mem  = 1072041984 (1022MB)
 avail mem = 1042157568 (993MB)
 mpath0 at root
 scsibus0 at mpath0: 256 targets
 mainbus0 at root
 bios0 at mainbus0: date 07/06/09, BIOS32 rev. 0 @ 0xfa530, SMBIOS 
 rev.
 2.2
 @ 0xf0800 (39 entries)
 bios0: vendor Phoenix Technologies, LTD version ANSA 3020  R01
 Jul,2,2009 date 07/06/2009
 acpi0 at bios0: rev 0
 acpi0: sleep states S0 S3 S4 S5
 acpi0: tables DSDT FACP MCFG APIC
 acpi0: wakeup devices EPA0(S3) EPA1(S3) PEX0(S5) PEX1(S5) PEX2(S5)
 PEX3(S5) HUB0(S5) PCI0(S5)
 acpitimer0 at acpi0: 3579545 Hz, 24 bits
 acpimcfg0 at acpi0 addr 0xe000, bus 0-255
 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 133MHz
 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
 acpiprt0 at acpi0: bus 0 (PCI0)
 acpiprt1 at acpi0: bus 2 (EPA1)
 acpiprt2 at acpi0: bus -1 (BR10)
 acpiprt3 at acpi0: bus -1 (BR11)
 acpiprt4 at acpi0: bus -1 (BR12)
 acpiprt5 at acpi0: bus -1 (BR13)
 acpiprt6 at acpi0: bus -1 (BR14)
 acpiprt7 at acpi0: bus 3 (P0P1)
 acpiprt8 at acpi0: bus -1 (PEX0)
 acpiprt9 at acpi0: bus -1 (PEX1)
 acpiprt10 at acpi0: bus -1 (PEX2)
 acpiprt11 at acpi0: bus -1 (PEX3)
 acpiprt12 at acpi0: bus -1 (HUB0)
 acpicpu0 at acpi0
 acpitz0 at acpi0: critical temperature is 75 degC
 acpibtn0 at acpi0: PWRB
 bios0: ROM list: 0xc8000/0x4000! 0xcc000/0x2200! 0xef000/0x1000!
 pci0 at mainbus0 bus 0: configuration mode 1 (bios)
 pchb0 at pci0 dev 0 function 0 Intel EP80579 Host rev 0x01
 Intel EP80579 Memory rev 0x01 at pci0 dev 0 function 1 not 
 configured
 Intel EP80579 EDMA rev 0x01 at pci0 dev 1 function 0 not configured
 ppb0 at pci0 dev 2 function 0 Intel EP80579 PCIE rev 0x01: apic 
 2 int
 16
 pci1 at ppb0 bus 1
 em0 at pci1 dev 0 function 0 Intel 82574L rev 0x00: msi, address
 

Re: davical on openbsd

2015-04-18 Thread Paolo Aglialoro
Thank you all for these first answers.
I also had checked out about radicale and baikal, while completely
forgotten about sogo.

Concerning this latter one I downloaded the .ova of ZEG just to give it a
try and I found its management through webmin cumbersome (e.g. the
interface for users' management of LDAP database didn't connect with it,
etc.). As people honestly wrote in forums, to have zeg adapted takes the
guys of inverse who produce it to tie it to another domain and customize it
for you. But I don't really wanna run on Ubuntu. Plus I don't need either
mail management or any domain thereof.

Here I come to the real need: giving a small group of volunteers (no more
than 20) who mostly operate with iCal but also outlook (it's a scattered
group) the ability to coordinate their social activity together by:

1. creating events with attendees on 2/3 calendars over which some users
are rw and others ro

2. send invitations to the outside world (could be 50-100 people) when they
want to make a public event all together and get answers also from from
invitees who are not davical/baikal/radicale users (although this should be
managed by the client and not by the server, true?)

I thought that a lightweight product like davical, radicale or baikal would
be better fit to manage, but it's the first time I try this thing. Honestly
I don't know which one of them better fills the bill. *** especially on
openbsd ***

At the moment I was trying both davical and baikal, configuring them with
nginx, considering that openbsd has quit apache and that nginx is the web
server I have had most experiences with (and that the new httpd is so new
that it is a completely unsupported config). In the first case I arrived
where the setup.php complains it cannot attach to the database, in the
second one, using the same nginx.conf provided with the package files, the
webpage is fixed on error 502.

My sensation is that these products are extremely messy to configure as
their laconic install documents leave most of the details uncovered. I am
following the few hints found in /usr/local/share/doc/pkg-readmes/ as the
rest of the docs (e.g. INSTALL from package dir, webpages) are mostly
linux-centric, so they are useful more for inspiration rather than
step-by-step procedure.

One of the details I find nowhere, for instance, is about the permissions
that the files should be given: installed from packages most files are
either root:bin or root:daemon while tutorials often say they should be
www:www (exactly www-data:www-data as they're linux-centric).

Another doubt that I have is about backups and troubleshooting. I have no
idea which product would be easier/more consistent to manage, especially in
a disaster recovery scenery and in a half yearly upgrade one. Surely, the
idea that under davical runs pg looks like more thorough than some sqlite
or different, but things at least things have to work. To which point I am
not yet.

Looking forward for your further inspiration.
Thanks