Re: SSL_ERROR_DECODE_ERROR_ALERT in Fedora 30 Firefox when connecting to some OpenBSD servers
On Wed, Jun 5, 2019, at 08:07, Frank Groeneveld wrote: > After updating to Firefox 67.0 on Fedora 30 it seems some OpenBSD > servers cannot be reached over HTTPS anymore. The error produced is > SSL_ERROR_DECODE_ERROR_ALERT. I get this with some of my own servers, > but also with https://cvsweb.openbsd.org/ > Anybody know what is going on? Chromium and openssl s_client on the > same system works fine and the same Firefox version in Ubuntu, Mac OS > and Windows don't have this problem. > > Thanks in advance. Sorry for the noise, apparently there is a bug in the Fedora side when connecting with newer versions of LibreSSL. Related bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1713777 Regards, Frank
SSL_ERROR_DECODE_ERROR_ALERT in Fedora 30 Firefox when connecting to some OpenBSD servers
After updating to Firefox 67.0 on Fedora 30 it seems some OpenBSD servers cannot be reached over HTTPS anymore. The error produced is SSL_ERROR_DECODE_ERROR_ALERT. I get this with some of my own servers, but also with https://cvsweb.openbsd.org/ Anybody know what is going on? Chromium and openssl s_client on the same system works fine and the same Firefox version in Ubuntu, Mac OS and Windows don't have this problem. Thanks in advance. -- Frank
Re: GitLab
Hello Oleg, Yes, I've hosted it for a few years on OpenBSD. It's a tough beast to get working though, because of all the dependencies and separate copmonents. If you're familiar with Ruby you can probably get it working, if not then I wouldn't advise you to try. I've contributed a number of patches to upstream and could install most versions without manual steps. However, last install I did was almost a year ago. Good luck! Frank On Wed, Mar 27, 2019, at 16:51, Oleg Pahl wrote: > Hi all, > > is it possible to install GitLab on OpenBSD? If yes .. any doc's? > > BR > > Oleg Pahl > >
Re: x260 hang at halt/reboot
On Wed, Aug 15, 2018, at 15:02, Stuart Henderson wrote: > Thanks for the suggestion, currently OpenBSD and UEFI only. > I'll give it a try with MBR when I can afford a better SSD and rebuild it > on that. > I need CSM mode enabled on my X260 to get it working correctly. Is it disabled for you? -- Frank
Re: Kaby Lake software rendering on Intel NUC
On Fri, Jul 13, 2018, at 16:51, Frank Groeneveld wrote: > After sending the email I noticed the first line in the Xorg log > (machdep.aperture=1) and that also doesn't seem to fix the software > rendering. Anybody have an idea? Thanks in advance. Frank
Re: Kaby Lake software rendering on Intel NUC
After sending the email I noticed the first line in the Xorg log (machdep.aperture=1) and that also doesn't seem to fix the software rendering. Frank
Kaby Lake software rendering on Intel NUC
Dear all, I'm trying to get OpenBSD 6.3 with Gnome working on an Intel NUC based on Intel Kaby Lake. I found that the amd64 webpage at https://www.openbsd.org/amd64.html states there is support for Intel Kaby Lake. Does that mean it should not fallback to software rendering? Because on this machine it does fallback to software rendering. Attached the dmesg and Xorg logs. Thanks, Frank [ 470.923] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem (Operation not permitted) Check that you have set 'machdep.allowaperture=1' in /etc/sysctl.conf and reboot your machine refer to xf86(4) for details [ 470.923] linear framebuffer access unavailable [ 470.935] (--) Using wscons driver on /dev/ttyC4 [ 470.939] X.Org X Server 1.19.6 Release Date: 2017-12-20 [ 470.939] X Protocol Version 11, Revision 0 [ 470.939] Build Operating System: OpenBSD 6.3 amd64 [ 470.939] Current Operating System: OpenBSD elliot.ivaldi.nl 6.3 GENERIC.MP#4 amd64 [ 470.939] Build Date: 24 March 2018 02:38:24PM [ 470.940] [ 470.940] Current version of pixman: 0.34.0 [ 470.940] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 470.940] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 470.940] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jul 13 16:18:22 2018 [ 470.940] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" [ 470.940] (==) No Layout section. Using the first Screen section. [ 470.940] (==) No screen section available. Using defaults. [ 470.940] (**) |-->Screen "Default Screen Section" (0) [ 470.940] (**) | |-->Monitor "" [ 470.940] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 470.940] (==) Automatically adding devices [ 470.940] (==) Automatically enabling devices [ 470.940] (==) Not automatically adding GPU devices [ 470.940] (==) Max clients allowed: 256, resource mask: 0x1f [ 470.940] (==) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF/, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fonts/100dpi/, /usr/X11R6/lib/X11/fonts/75dpi/ [ 470.940] (==) ModulePath set to "/usr/X11R6/lib/modules" [ 470.940] (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. [ 470.940] (II) Loader magic: 0xa5d7da42000 [ 470.940] (II) Module ABI versions: [ 470.940] X.Org ANSI C Emulation: 0.4 [ 470.940] X.Org Video Driver: 23.0 [ 470.940] X.Org XInput driver : 24.1 [ 470.940] X.Org Server Extension : 10.0 [ 470.940] (--) PCI:*(0:0:2:0) 8086:5927:8086:2068 rev 6, Mem @ 0xdb00/16777216, 0x9000/268435456, I/O @ 0xf000/64 [ 470.940] (II) LoadModule: "glx" [ 470.941] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so [ 470.942] (II) Module glx: vendor="X.Org Foundation" [ 470.942] compiled for 1.19.6, module version = 1.0.0 [ 470.942] ABI class: X.Org Server Extension, version 10.0 [ 470.942] (==) Matched wsfb as autoconfigured driver 0 [ 470.942] (==) Assigned the driver to the xf86ConfigLayout [ 470.942] (II) LoadModule: "wsfb" [ 470.942] (II) Loading /usr/X11R6/lib/modules/drivers/wsfb_drv.so [ 470.942] (II) Module wsfb: vendor="X.Org Foundation" [ 470.942] compiled for 1.19.6, module version = 0.4.1 [ 470.942] ABI class: X.Org Video Driver, version 23.0 [ 470.942] (II) wsfb: driver for wsdisplay framebuffer: wsfb [ 470.942] (WW) Falling back to old probe method for wsfb [ 470.943] (II) wsfb(0): using default device [ 470.943] (II) wsfb(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 470.943] (==) wsfb(0): Depth 24, (--) framebuffer bpp 32 [ 470.943] (==) wsfb(0): RGB weight 888 [ 470.943] (==) wsfb(0): Default visual is TrueColor [ 470.943] (==) wsfb(0): Using gamma correction (1.0, 1.0, 1.0) [ 470.943] (II) wsfb(0): Vidmem: 9000k [ 470.943] (==) wsfb(0): DPI set to (96, 96) [ 470.943] (**) wsfb(0): Using "Shadow Framebuffer" [ 470.943] (II) Loading sub module "shadow" [ 470.943] (II) LoadModule: "shadow" [ 470.943] (II) Loading /usr/X11R6/lib/modules/libshadow.so [ 470.943] (II) Module shadow: vendor="X.Org Foundation" [ 470.943] compiled for 1.19.6, module version = 1.1.0 [ 470.943] ABI class: X.Org ANSI C Emulation, version 0.4 [ 470.943] (II) Loading sub module "fb" [ 470.943] (II) LoadModule: "fb" [ 470.944] (II) Loading /usr/X11R6/lib/modules/libfb.so [ 470.944] (II) Module fb: vendor="X.Org Foundation" [ 470.944] compiled for 1.19.6, module version = 1.0.0 [ 470.944] ABI class: X.Org ANSI C Emulation, version 0.4 [ 470.944] (--) Depth 24 pixmap format is 32 bpp [
Re: Switching swap partition
On Tue, Oct 10, 2017, at 10:22, leo_...@volny.cz wrote: > Instead of sd0b? Then it appears fine. Yes, that was my point, everything seemed fine until I found that line in dmesg. > >> You might want to keep sd0b around as a dump partition though, just in > >> case it ever panics before going multiluser... > > > > The point of this operation was to reclaim that space for other use ;-) > > You could even just shrink it significantly -- I don't think a dump at > early boot would take up *that* much space... Good suggestion, I might do it like that indeed. Thanks! Frank
Re: Switching swap partition
On Tue, Oct 10, 2017, at 09:48, leo_...@volny.cz wrote: > It'd seem more wrong to me if it'd try to swap to a nonexistent > partition ;) Just in case, what is the output of 'swapctl -l' straight > after boot, preferably when still single-user? swapctl -l always lists /dev/sd1b correctly. > You might want to keep sd0b around as a dump partition though, just in > case it ever panics before going multiluser... The point of this operation was to reclaim that space for other use ;-) Frank
Switching swap partition
I recently switched the swap partition on a server from sd0b to sd1b. I've modified /etc/fstab accordingly and after a reboot swapctl -l lists it as being the only used swap partition correctly. Today I noticed this line in dmesg: root on sd0a (4340b9bfa4cdde0a.a) swap on sd0b dump on sd0b It still lists the old partition (which I modified to be of the "unknown" type in the disklabel, but removing the partition doesn't fix it either) as being the swap partition. How can I change this? I found a kernel compile option, but recompiling a kernel because I want swap on a different partition seems wrong. Thanks for any hints! Frank
Re: How do I try uwacom with a Graphire tablet
On Thu, May 18, 2017, at 09:01, Alfred Morgan wrote: > How difficult would it be to get the Wacom Graphire (it says ET-0405-U on > the bottom of my tablet) to work with the uwacom driver which claims to > only support the CTL-490? The uwacom driver was written for newer tables which have a broken usb descriptor. I believe your device is older and might already work without uwacom but needs modifications to pick up the fixes in /usr/src/sys/dev/usb/uhidev.c. Frank
Re: thinkpad x270
On Thu, May 18, 2017, at 14:42, Pau wrote: > Is anybody using a thinkpad x270? If so, could you please send me your > dmesg? Is it working fine? I have an x260 and it works fine when using the efifb driver, except for suspend/resume. > More importantly: Is the laptop resuming X/connection after suspending > if you disable TPM in bios? I have an x260 and it seems to me that we need a working graphics driver before we can start fixing suspend/resume. Frank
Re: Intuos Draw (uwacom) question
On Wed, Apr 12, 2017, at 08:16, Peter J. Philipp wrote: > I'm interested in buying an Wacom Intuos Draw which is supported in > 6.1. However when I go to reichelt.de the model that's available says > CTL-490DW I don't know if DW is supported, can someone let me know? > > https://www.reichelt.de/Grafiktabletts-stifte/WACOM-CTL-490DW/3/index.html?ACTION=3&LA=5&ARTICLE=160633&GROUPID=6271&artnr=WACOM+CTL-490DW > > Any feedback would be appreciated. > > Regards, > > -peter > Hello Peter, Yes, that will work. I'm the author of the driver and use it with a CTL-490DW-N (where -N probably means Dutch). It won't register pressure levels or proximity. I use the tablet as mouse replacement about 40 hours a week to prevent getting RSI. Two things of note though: 1. Unplugging while X is running results in the X log getting spammed (this happens with more devices, search tech@ for wacom). The fix is to restart X. 2. Once in a while the cursor jumps to the top left corner and back when you click something. This happens only a few times a day and doesn't cause me issues, but I want to fix it and haven't been able to so far. It seems the Linux driver just cuts of the lowest bit of the coordinates and I haven't figured out yet whether this will fix it or whether they use a different trick for it. Regards, Frank
Re: help with pf filtering on enc
On Tue, Mar 21, 2017, at 16:56, Marko Cupać wrote: > ... > > What exactly I should pass on enc interface so that the above packet > passes? > > Thank you in advance. Hi, You probably need to allow ipencap protocol packets. I also need l2tp packets, but that depends on whether you use it. -- Frank
Re: Kernel panic on 6.0-stable
On Sun, Nov 20, 2016 at 03:21:32PM +0100, Martin Pieuchot wrote: > On 20/11/16(Sun) 13:58, Frank Groeneveld wrote: > > A few week back there was an outage at my ISP. Afterwards, I kept > > getting crashed on igmpproxy after changing channels on the tv a few > > times: > > This has been fixed in -current. Thanks for the pointer. Does it fix both the igmpproxy crash and the kernel crash? Or just the igmpproxy crash? Frank
Kernel panic on 6.0-stable
A few week back there was an outage at my ISP. Afterwards, I kept getting crashed on igmpproxy after changing channels on the tv a few times: - Note: RECV Leave message from 192.168.1.2 to 224.0.0.2 (ip_hl 24, data 8) Debu: Got leave message from 192.168.1.2 to 224.0.251.136. Starting last member detection. Debu: Leaving group 224.0.251.136 upstream on IF address 10.36.229.63 Note: leaveMcGroup: 224.0.251.136 on vlan4 Debu: SENT Membership query from 192.168.1.1 to 224.0.251.136 Debu: Sent membership query from 192.168.1.1 to 224.0.251.136. Delay: 10 Debu: Created timeout 18 (#6) - delay 5 secs Debu: (Id:12, Time:1) Debu: (Id:13, Time:0) Debu: (Id:14, Time:1) Debu: (Id:15, Time:1) Debu: (Id:16, Time:1) Debu: (Id:17, Time:1) Debu: (Id:18, Time:5) Debu: (Id:10, Time:7) Debu: About to call timeout 12 (#0) Debu: Aging Origin 213.75.167.6 Dst 224.0.251.126 PktCnt 1022 -> 1022 Debu: Origin 213.75.167.6 Vif bits : 0x0002 Debu: Setting TTL for Vif 1 to 1 Debu: Identified VIF #2 as upstream. Note: Removing MFC: 213.75.167.6 -> 224.0.251.126, InpVIf: 2 igmpproxy(18177) in free(): error: use after free 0x1116efc3b400 Abort trap (core dumped) - Because I didn't have time to debug it, I started igmpproxy in a while true loop and was able to watch television with some minor hickups now and then. Today I finally had time to have a go at it, but wasn't able to figure out the cause. Still being on 5.9-stable I decided to first upgrade to 6.0-stable and see whether that helped. This made my problem worse, because now as soon as igmpproxy was running it would panic (full dmeg attached with the panic at the bottom). I found mention of said panic in plus60.html: > In pf(4), don't panic if an mbuf(9) already has a statekey. This should > help finding the remaining corner cases of packets looped back in the > stack. This leads me to believe that my panic should not occur, but it still is. Does anybody have a clue how I can work around this? Is there maybe something wrong with my pf rules? I've attached them and the igmpproxy.conf as well. For now I've downgraded to 5.9-stable again. Thanks in advance, Frank booting hd0a:/bsd: 6893364+2179280+267272+0+663552 [72+726864+483332]=0xab3a20 entry point at 0x1001000 [7205c766, 3404, 24448b12, 3be0a304] [ using 1210912 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2016 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 6.0-stable (GENERIC.MP) #6: Sun Nov 20 10:16:50 CET 2016 frank@phenom.local:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error ff real mem = 4246003712 (4049MB) avail mem = 4112846848 (3922MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdf16d820 (7 entries) bios0: vendor coreboot version "4.0" date 09/08/2014 bios0: PC Engines APU acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP SPCR HPET APIC HEST SSDT SSDT SSDT acpi0: wakeup devices AGPB(S4) HDMI(S4) PBR4(S4) PBR5(S4) PBR6(S4) PBR7(S4) PE20(S4) PE21(S4) PE22(S4) PE23(S4) PIBR(S4) UOH1(S3) UOH2(S3) UOH3(S3) UOH4(S3) UOH5(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD G-T40E Processor, 1000.14 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: 8 4MB entries fully associative cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 199MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD G-T40E Processor, 1000.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: 8 4MB entries fully associative cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins acpiprt0 at acpi0: bus -1 (AGPB) acpiprt1 at acpi0: bus -1 (HDMI) acpiprt2 at acpi0: bus 1 (PBR4) acpiprt3 at acpi0: bus 2 (PBR5) acpiprt4 at acpi0: bus 3 (PBR6) acpiprt5 at acpi0: bus -1 (PBR7) a
Re: ldapd(8) database bootstrap error
On Sat, Oct 29, 2016 at 10:14:00AM +0800, Zhang Huangbin wrote: > You must create the root dn (dc=example,dc=com) first. For example: > > dn: dc=example,dc=com > objectclass: dcObject > objectclass: organization > dc: example > o: example > > > Zhang Huangbin, founder of iRedMail project: http://www.iredmail.org/ > Time zone: GMT+8 (China/Beijing). That's it, thanks! I was under the wrong assumption that the namespace objects would already be there. Frank
ldapd(8) database bootstrap error
I'm trying to get ldapd working on 6.0-stable. Using the man page and /etc/examples/ldapd.conf I've created the following configuration file: schema "/etc/ldap/core.schema" schema "/etc/ldap/inetorgperson.schema" schema "/etc/ldap/nis.schema" listen on lo0 secure namespace "dc=example,dc=com" { rootdn "cn=admin,dc=example,dc=com" rootpw "secret" } Starting ldapd as root gives the following output: # ldapd -vd Oct 28 20:31:20.800 [83362] parsing config /etc/ldapd.conf Oct 28 20:31:20.800 [83362] parsing schema file '/etc/ldap/core.schema' Oct 28 20:31:20.804 [83362] parsing schema file '/etc/ldap/inetorgperson.schema' Oct 28 20:31:20.805 [83362] parsing schema file '/etc/ldap/nis.schema' Oct 28 20:31:20.806 [83362] parsing namespace dc=example,dc=com Oct 28 20:31:20.807 [83362] startup Oct 28 20:31:20.812 [46832] listening on 127.0.0.1:389 Oct 28 20:31:20.812 [46832] listening on fe80:3::1:389 Oct 28 20:31:20.812 [46832] listening on ::1:389 Oct 28 20:31:20.812 [46832] opening namespace dc=example,dc=com Oct 28 20:31:20.812 [46832] ldape: entering event loop All seems fine up until here. I try to add the following ldif: dn: ou=people,dc=example,dc=com objectClass: organizationalUnit ou: people This results in: $ ldapadd -D 'cn=admin,dc=example,dc=com' -x -w secret -f in.ldif adding new entry "ou=people,dc=example,dc=com" ldap_add: No such object (32) The server gives this output for the ldapadd commands received: Oct 28 20:35:56.526 [60646] accepted connection from 127.0.0.1 on fd 11 Oct 28 20:35:56.526 [60646] consumed 46 bytes Oct 28 20:35:56.527 [60646] got request type 0, id 1 Oct 28 20:35:56.527 [60646] bind dn = cn=admin,dc=example,dc=com Oct 28 20:35:56.527 [60646] successfully authenticated as cn=admin,dc=example,dc=com Oct 28 20:35:56.527 [60646] sending response 1 with result 0 Oct 28 20:35:56.527 [60646] consumed 91 bytes Oct 28 20:35:56.527 [60646] got request type 8, id 2 Oct 28 20:35:56.527 [60646] adding entry ou=people,dc=example,dc=com Oct 28 20:35:56.528 [60646] dc=example,dc=com: dn not found Oct 28 20:35:56.528 [60646] sending response 9 with result 32 Oct 28 20:35:56.528 [60646] consumed 7 bytes Oct 28 20:35:56.529 [60646] got request type 2, id 3 Oct 28 20:35:56.529 [60646] current bind dn = cn=admin,dc=example,dc=com Oct 28 20:35:56.529 [60646] end-of-file on connection 11 Oct 28 20:35:56.529 [60646] closing connection 11 So it seems it can't find the baseDN or namespace somehow. What am I doing wrong? The database files seem to be created just fine in /var/db/ldap/. Cheers, Frank
Re: php7.0 fail on stable
On Thu, Aug 18, 2016 at 09:09:38PM +0200, Thuban wrote: > Hello, > I was trying to build php7.0 with ports, but it fails (see configure > failure below). > > I'm running on 5.9 with stable patches (for both ports and src of > course). > > It seems that configure doesn't recognise the "--with-apxs" option". It's missing a dependency, see this thread: http://marc.info/?t=14605309296&r=1&w=2 This should be fixed in 6.0, but for 5.9 you can work around it by installing apache-httpd before compiling php. Frank
Re: Trying to get Wacom CTL-490 to work
On Mon, Jul 18, 2016 at 09:54:02AM +0200, Philip Guenther wrote: > > The privilege separation code in xenocara has a compiled in list of > devices that are permitted to be opened; of the uhid devices it only > currently includes /dev/uhid0 through /dev/uhid3. You can either > a) update the list and recompile the X server > b) symlink it to a different name that's already in the allowed list > but that's not used by OpenBSD (e.g., "/dev/ttyJ0") > c) ??? Great tip, thank you! The permission denied error is gone indeed. Unfortunately it seems the drive cannot do anythin with the raw uhid devices, it complains about missing X & Y directions. Frank
Re: Trying to get Wacom CTL-490 to work
On Sun, Jul 17, 2016 at 08:53:50PM +0200, Frank Groeneveld wrote: > [46.602] (EE) xf86OpenSerial: Cannot open device /dev/uhid6 > Operation not permitted. > [46.602] (EE) Error opening /dev/uhid6: Operation not permitted Forgot to mention: I had changed the file permissions on uhid6 to be worl readable and writable. Frank
Trying to get Wacom CTL-490 to work
I'm trying to get my new Wacom tablet working with X11 in -current. It's a Wacom Intuos Pen (CTL-490) and it shows up in dmesg like this: uhidev0 at uhub3 port 1 configuration 1 interface 0 "Wacom Co.,Ltd. Intuos PS" rev 2.00/1.00 addr 5 uhidev0: iclass 3/0, 192 report ids uhid0 at uhidev0 reportid 2: input=0, output=0, feature=1 uhid1 at uhidev0 reportid 3: input=0, output=0, feature=1 uhid2 at uhidev0 reportid 4: input=0, output=0, feature=1 uhid3 at uhidev0 reportid 5: input=0, output=0, feature=1 uhid4 at uhidev0 reportid 7: input=0, output=0, feature=9 uhid5 at uhidev0 reportid 8: input=0, output=0, feature=9 uhid6 at uhidev0 reportid 16: input=9, output=0, feature=2 uhid7 at uhidev0 reportid 17: input=0, output=0, feature=16 uhid8 at uhidev0 reportid 19: input=0, output=0, feature=1 uhid9 at uhidev0 reportid 20: input=0, output=0, feature=31 uhid10 at uhidev0 reportid 32: input=0, output=0, feature=5 uhid11 at uhidev0 reportid 33: input=0, output=0, feature=1 uhid12 at uhidev0 reportid 34: input=0, output=0, feature=1 uhid13 at uhidev0 reportid 35: input=0, output=0, feature=14 uhid14 at uhidev0 reportid 36: input=0, output=0, feature=31 uhid15 at uhidev0 reportid 37: input=0, output=0, feature=4 uhid16 at uhidev0 reportid 48: input=0, output=0, feature=2 uhid17 at uhidev0 reportid 49: input=0, output=0, feature=33 uhid18 at uhidev0 reportid 50: input=0, output=0, feature=33 uhid19 at uhidev0 reportid 51: input=0, output=0, feature=1 uhid20 at uhidev0 reportid 64: input=0, output=0, feature=10 uhid21 at uhidev0 reportid 192: input=9, output=0, feature=0 uhidev1 at uhub3 port 1 configuration 1 interface 1 "Wacom Co.,Ltd. Intuos PS" rev 2.00/1.00 addr 5 uhidev1: iclass 3/0, 3 report ids uhid22 at uhidev1 reportid 2: input=63, output=0, feature=0 uhid23 at uhidev1 reportid 3: input=63, output=0, feature=0 uhidev2 at uhub3 port 1 configuration 1 interface 2 "Wacom Co.,Ltd. Intuos PS" rev 2.00/1.00 addr 5 uhidev2: iclass 3/1, 1 report id ums0 at uhidev2 reportid 1: 5 buttons wsmouse1 at ums0 mux 0 When I run `cat /dev/uhid6` (after making that device) I get output that seems to suggest it is related to the pen movement. When not moving the pen there is less output etc. However, `cat /dev/wsmouse1` doesn't give any output. Searching the archives I found this suggested xorg.conf InputDevice section, which I tried: Section "InputDevice" Identifier "pen" Driver "usbtablet" Option "Type" "stylus" Option "Device" "/dev/uhid6" Option "Mode" "Absolute" EndSection Running this gives me the following error in my Xorg log file though. Maybe because it was old and only meant for serial-over-usb tablets? [46.602] (II) Using input driver 'usbtablet' for 'pen' [46.602] (**) Option "CorePointer" [46.602] (**) pen: always reports core events [46.602] (**) Stylus: always reports core events [46.602] (**) Stylus device is /dev/uhid6 [46.602] (**) Stylus is in absolute mode [46.602] (==) Stylus: threshold = 5 [46.602] (==) Stylus: suppress = 2 [46.602] (II) XINPUT: Adding extended input device "Stylus" (type: TABLET, id 6) [46.602] (**) Option "Device" "/dev/uhid6" [46.602] (EE) xf86OpenSerial: Cannot open device /dev/uhid6 Operation not permitted. [46.602] (EE) Error opening /dev/uhid6: Operation not permitted [46.602] (EE) Couldn't init device "Stylus" [46.602] (II) UnloadModule: "usbtablet" Finally I've modified the kernel and called uhidev_set_report with the same parameters as for the Graphire 3 & 4, because the Linux kernel driver seems to suggest that without that call the device will run in a more generic mouse mode. However, it did not change anything. Does anybody know how to get X working with the uhid device? Or is that not the suggested method? Based on my findings that uhid6 is for pen movement, might ums attach to the wrong device? Thanks for any help. Frank
Re: Can't change screen brightness Acer Aspire ES1-411
Does it help to disable acpivideo in the kernel? I need to do this on my UEFI Asus laptop to get it working. Frank On 06/16/16 20:52, j...@openmailbox.org wrote: Does this workaround work for you? http://marc.info/?l=openbsd-misc&m=146520183827302&w=2 http://marc.info/?l=openbsd-misc&m=146523968007324&w=2 If it does then it's related to this bug: http://marc.info/?l=openbsd-bugs&m=146451346724515 (I'm just an user, not a developer) Hello, thanks for the help, but it doesn't work.
Re: Request for a package & a feature
On 11/28/15 12:47, Loïc BLOT wrote: As i see OpenBSD's dhclient have the user-class (option 77) but i also need vendor-class-identifier (named as is in isc-dhcp-client) & authentication (option 90,https://www.ietf.org/rfc/rfc3118.txt). I didn't found those options. I use option 60 (vendor-class-identifier) in OpenBSD with dhclient like this: interface "vlan4" { send dhcp-class-identifier "IPTV_RG"; } I found that in /usr/src/sbin/dhclient/tables.c and it includes all other dhcp options. For you, these entries seem interesting: /* 60 */ { "dhcp-class-identifier", "t" }, /* 77 */ { "user-class", "t" }, /* 90 */ { "option-90", "X" }, If you use something like this you will be able to use the base system dhclient: interface "your_interface" { send dhcp-class-identifier "your_value"; send user-class "your_second_value"; send option-90 "your_third_value"; } Good luck! Frank
Re: wsconsctl dislay.brightness stopped working after upgrade to 5.6
On Sat, Nov 15, 2014 at 02:30:26PM +0100, Frank Groeneveld wrote: > I might be able to find out what change caused this regression if > somebody can hint where to look. I've already crawled through most of > the intel drm code, but I think this must be somewhere in the ACPI > layer. Where should I look? Could somebody please give me a hint? Thanks, Frank
Re: Patch for smtpd.conf.5
An improved version of the patch: mark path as optional for "deliver to maildir path". On Tue, Nov 18, 2014 at 08:53:51PM +0100, Frank Groeneveld wrote: > This little patch changes the tag argument to correctly display it as a > command > argument to the tagged keyword. > > Frank > --- /usr/src/usr.sbin/smtpd/smtpd.conf.5 Wed Jul 9 14:44:54 2014 > +++ smtpd.conf.5 Tue Nov 18 20:30:12 2014 > @@ -87,7 +87,7 @@ > .It Xo > .Ic tagged > .Op Ic \&! > -.Ic tag > +.Ar tag > .Xc > If specified, the rule will only be matched if the client session was tagged > with > .Ar tag . --- /usr/src/usr.sbin/smtpd/smtpd.conf.5Wed Jul 9 14:44:54 2014 +++ smtpd.conf.5Tue Nov 18 21:02:13 2014 @@ -87,7 +87,7 @@ .It Xo .Ic tagged .Op Ic \&! -.Ic tag +.Ar tag .Xc If specified, the rule will only be matched if the client session was tagged with .Ar tag . @@ -283,7 +283,7 @@ .Ux .Ar socket over LMTP. -.It Ic deliver to maildir Ar path +.It Ic deliver to maildir Op Ar path Mail is added to a maildir. Its location, .Ar path ,
Patch for smtpd.conf.5
This little patch changes the tag argument to correctly display it as a command argument to the tagged keyword. Frank --- /usr/src/usr.sbin/smtpd/smtpd.conf.5Wed Jul 9 14:44:54 2014 +++ smtpd.conf.5Tue Nov 18 20:30:12 2014 @@ -87,7 +87,7 @@ .It Xo .Ic tagged .Op Ic \&! -.Ic tag +.Ar tag .Xc If specified, the rule will only be matched if the client session was tagged with .Ar tag .
wsconsctl dislay.brightness stopped working after upgrade to 5.6
Hi, On my Asus Zenbook UX31A I used to be able to control the backlight in both X and on the console using wsconsctl display.brithness=xx. After upgrading to 5.6 this stopped working. Whatever I put in place of xx, the output reports: display.brightness -> 100.00% I've attached dmesg output below. I might be able to find out what change caused this regression if somebody can hint where to look. I've already crawled through most of the intel drm code, but I think this must be somewhere in the ACPI layer. Where should I look? Thanks in advance, Frank OpenBSD 5.6-stable (GENERIC.MP) #0: Sat Nov 15 13:45:26 CET 2014 r...@zenbook.frankgroeneveld.nl:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4157837312 (3965MB) avail mem = 4038373376 (3851MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeba60 (23 entries) bios0: vendor American Megatrends Inc. version "UX31A.219" date 06/14/2013 bios0: ASUSTeK COMPUTER INC. UX31A acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ECDT MCFG SSDT SSDT SSDT SSDT HPET SSDT SSDT SSDT SSDT DMAR MSDM acpi0: wakeup devices P0P1(S4) PEG0(S4) PEG1(S4) PEG2(S4) PEG3(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) EHC2(S3) USB5(S3) USB6(S3) USB7(S3) HDEF(S4) RP01(S4) RP02(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) i7-3517U CPU @ 1.90GHz, 1796.28 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 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.1.2, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-3517U CPU @ 1.90GHz, 1795.92 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i7-3517U CPU @ 1.90GHz, 1795.92 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-3517U CPU @ 1.90GHz, 1795.92 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiec0 at acpi0 acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus -1 (PEG0) acpiprt3 at acpi0: bus -1 (PEG1) acpiprt4 at acpi0: bus -1 (PEG2) acpiprt5 at acpi0: bus -1 (PEG3) acpiprt6 at acpi0: bus 1 (RP01) acpiprt7 at acpi0: bus 2 (RP02) acpiprt8 at acpi0: bus -1 (RP03) acpiprt9 at acpi0: bus -1 (RP04) acpiprt10 at acpi0: bus -1 (RP05) acpiprt11 at acpi0: bus -1 (RP06) acpiprt12 at acpi0: bus -1 (RP07) acpiprt13 at acpi0: bus -1 (RP08) acpicpu0 at acpi0: C2, C1, PSS acpicpu1 at acpi0: C2, C1, PSS acpicpu2 at acpi0: C2, C1, PSS acpicpu3 at acpi0: C2, C1, PSS acpitz0 at acpi0: critical temperature is 108 degC acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model "UX31-35" serial type LIon oem "ASUSTeK" acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: PWRB acpibtn2 at acpi0: SLPB acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: LCDD cpu0: Enhanced SpeedStep 1796 MHz: speeds: 2401, 2400, 2300, 2200, 2100, 1900, 1800, 1700, 1600, 1500, 1400, 1300, 1100, 1000, 900, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09 intagp at vga1 not configured inteldrm0 at vga1 drm0 at inteldrm0 drm: Memory usable by graphics device = 2048M inteldrm0: 1920x1080 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: scree
Re: Radeondrm firmware update on first boot
Hi Mark, On Wed, Mar 05, 2014 at 12:06:06AM +0100, Mark Kettenis wrote: > That's the intention. The idea is that if firmware is needed, but not > present, radeondrm(4) will detach and vga(4) will attach. > Unfortunately the codepaths are different for different hardware > generations and not all of them have been properly tested. I was thinking something like this was the problem, thanks for your explanation. > Can you send a dmesg from a boot *without* the firmware installed? > You can simply pkg_delete the radeon-firmware package and add it back > later, or just temporarily move /etc/firmware/radeon-* to a different > location and move it back afterwards. I'v attached the dmesg from a boot without firmware available. This resulted in a blank screen, just as the first boot. If you need me to test anything else, just let me know! Thanks, Frank OpenBSD 5.5 (GENERIC.MP) #301: Thu Feb 27 09:42:27 MST 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4275572736 (4077MB) avail mem = 4153147392 (3960MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0100 (59 entries) bios0: vendor Award Software International, Inc. version "F7" date 11/20/2009 bios0: Gigabyte Technology Co., Ltd. GA-MA790XT-UD4P acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT HPET MCFG TAMG APIC acpi0: wakeup devices USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) SBAZ(S4) P2P_(S5) PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) PCE6(S4) PCE7(S4) PCE8(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpihpet0 at acpi0: 14318180 Hz acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Phenom(tm) II X4 905e Processor, 2511.82 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache, 6MB 64b/line 48-way L3 cache cpu0: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu0: AMD erratum 721 detected and fixed cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 200MHz cpu0: mwait min=64, max=64, C-substates=0.0.0.0.0, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Phenom(tm) II X4 905e Processor, 2511.45 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache, 6MB 64b/line 48-way L3 cache cpu1: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu1: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu1: AMD erratum 721 detected and fixed cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: AMD Phenom(tm) II X4 905e Processor, 2511.45 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC cpu2: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache, 6MB 64b/line 48-way L3 cache cpu2: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu2: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu2: AMD erratum 721 detected and fixed cpu2: smt 0, core 3, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: AMD Phenom(tm) II X4 905e Processor, 2511.45 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC cpu3: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache, 6MB 64b/line 48-way L3 cache cpu3: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu3: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu3: AMD erratum 721 detected and fixed cpu3: smt 0, core 2, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 2 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 3 (P2P_) acpiprt2 at acpi0: bus 1 (PCE2) acpiprt3 at acpi0: bus -1 (PCE3) acpiprt4 at acpi0: bus -1 (PCE4) acpiprt5 at acpi0: bus -1 (PCE5) acpiprt6 at acpi0: bus -1 (PCE6) acpiprt7 at acp
Radeondrm firmware update on first boot
First of all: props to all the people who are working to make 5.5 one of the best releases! It's amazing to boot into Gnome 3.10 with Radeon KMS with machdep.allowaperture=0 :) Back to my "problem": I've installed my desktop machine (dmesg attached) twice from different snapshots. The newest snapshot was from the 28th of February. With both these snapshots I experienced a bug on first boot. During first boot, fw_update is run to download the firmware for my Radeon graphics card. However, the driver tries to do KMS before the firmware is available, which results in the screen turning blank. After SSH-ing to the box to make sure fw_update finished correctly, I can reboot the machine and everything works great on all further boots. I think the driver should somehow refrain from doing KMS on first boot, or the machine should automatically reboot after fw_update to prevent this from happening. Keep up the good work! Frank OpenBSD 5.5 (GENERIC.MP) #301: Thu Feb 27 09:42:27 MST 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4275572736 (4077MB) avail mem = 4153147392 (3960MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0100 (59 entries) bios0: vendor Award Software International, Inc. version "F7" date 11/20/2009 bios0: Gigabyte Technology Co., Ltd. GA-MA790XT-UD4P acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT HPET MCFG TAMG APIC acpi0: wakeup devices USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) SBAZ(S4) P2P_(S5) PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) PCE6(S4) PCE7(S4) PCE8(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpihpet0 at acpi0: 14318180 Hz acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Phenom(tm) II X4 905e Processor, 2511.81 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache, 6MB 64b/line 48-way L3 cache cpu0: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu0: AMD erratum 721 detected and fixed cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 200MHz cpu0: mwait min=64, max=64, C-substates=0.0.0.0.0, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Phenom(tm) II X4 905e Processor, 2511.45 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache, 6MB 64b/line 48-way L3 cache cpu1: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu1: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu1: AMD erratum 721 detected and fixed cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: AMD Phenom(tm) II X4 905e Processor, 2511.45 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC cpu2: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache, 6MB 64b/line 48-way L3 cache cpu2: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu2: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu2: AMD erratum 721 detected and fixed cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: AMD Phenom(tm) II X4 905e Processor, 2511.45 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC cpu3: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache, 6MB 64b/line 48-way L3 cache cpu3: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu3: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu3: AMD erratum 721 detected and fixed cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 2 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 3 (P2P_) acpiprt2 at acpi0: bus 1 (PCE2) acpiprt3 at acpi0: bus -1 (PCE3) acpiprt4 at acpi0: bus -1 (PCE4) acpiprt5