Re: Logging in/out on console while logged in in X removes hardware acceleration

[Nils Reuße]

Hi Theo,

thank you for your reply.  Well then, I guess I just stop switching 
around between different login sessions ;)


Nils


Am 31.07.2020 um 16:08 schrieb Theo de Raadt:

I'm not sure what can be done about it.

/etc/fbtab's first role is to give access to subsystems, but it's
second more important role is to *take them away* later.

Unfortunately there is nothing "keeping state" about previous access
conditions, as well it is quite unclear if reverting to previous access
conditions would be a safe choice.


=?UTF-8?Q?Nils_Reu=c3=9fe?=  wrote:


Dear all,

logging in and out changes the owner of the /dev/drm0 file, so that one
loses hardware acceleration in X when additionally logging in and out on
a console.  Here's what I do:

1) Boot Openbsd and log into X with xenodm.  Ownership of /dev/drm0:

  $ ls -l /dev/drm0
  crw---  1 nils  wheel   87,   0 Jul 31 13:07 /dev/drm0

2) Switch to a console (e.g. CTRL-ALT-F1) and log in with the same user.
   The file is now owned by my user-group:

  $ ls -l /dev/drm0
  crw---  1 nils  nils   87,   0 Jul 31 13:07 /dev/drm0

3) Log out from the console.  Ownership changes back to root/wheel,
thereby disabling hardware acceleration in X:

  $ ls -l /dev/drm0
  crw---  1 root  wheel   87,   0 Jul 31 13:07 /dev/drm0

To regain hardware acceleration, I have to manually chown the file back
to my userid, or relogin with xenodm.  So I guess logging in chowns the
file with my user (even with my user group when logging in via console),
and logging out reassigns the file owner to root.

I guess not much can be done about this, or can it?

Nils

Logging in/out on console while logged in in X removes hardware acceleration

[Nils Reuße]

Dear all,

logging in and out changes the owner of the /dev/drm0 file, so that one 
loses hardware acceleration in X when additionally logging in and out on 
a console.  Here's what I do:


1) Boot Openbsd and log into X with xenodm.  Ownership of /dev/drm0:

$ ls -l /dev/drm0
crw---  1 nils  wheel   87,   0 Jul 31 13:07 /dev/drm0

2) Switch to a console (e.g. CTRL-ALT-F1) and log in with the same user. 
 The file is now owned by my user-group:


$ ls -l /dev/drm0
crw---  1 nils  nils   87,   0 Jul 31 13:07 /dev/drm0

3) Log out from the console.  Ownership changes back to root/wheel, 
thereby disabling hardware acceleration in X:


$ ls -l /dev/drm0
crw---  1 root  wheel   87,   0 Jul 31 13:07 /dev/drm0

To regain hardware acceleration, I have to manually chown the file back 
to my userid, or relogin with xenodm.  So I guess logging in chowns the 
file with my user (even with my user group when logging in via console), 
and logging out reassigns the file owner to root.


I guess not much can be done about this, or can it?

Nils

Re: Problems with inteldrm on ASRock J3455-ITX (Apollo Lake)

[Nils Reuße]

Hi all,

with the help of Chris i finally got it working and i'm happily writing this 
email from X!  I broke it down to these two settings one has to change in the 
UEFI:

* Disable c-states and enable legacy BIOS:

  - Advanced -> CPU Configuration -> CPU C States Support => Disable
  - Boot -> CSM => Enable

Also, i had to connect my monitor with VGA, with DVI the screen goes black when 
the graphics card gets initialized (did not try HDMI).

I'm a bit confused about the xrandr output, there's no VGA and no DVI, but eDP 
and DP, and also two HDMI connectors shown, even though the board only has one. 
 Could this be firmware—related?  Anyway, it works:

$ xrandr -q
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192
eDP-1 connected primary 1680x1050+0+0 (normal left inverted right x axis y 
axis) 474mm x 296mm
   1680x1050 59.88*+
   1400x1050 59.98
   1280x1024 75.0260.02
   1280x960  60.00
   1152x864  75.00
   1024x768  60.0475.0875.0370.0760.00
   960x720   60.00
   928x696   75.0060.05
   896x672   75.0560.01
   832x624   74.55
   800x600   75.0070.0065.0060.0072.1975.0060.32
56.25
   700x525   74.7659.98
   640x512   75.0260.02
   640x480   60.0075.0072.8172.8175.0066.6760.00
59.94
   720x400   70.08
   576x432   75.00
   512x384   75.0370.0760.00
   416x312   74.66
   400x300   72.1975.1260.3256.34
   320x240   72.8175.0060.05
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)

Here's an excerpt from dmesg for drm (full dmesg attached):

$ dmesg | grep -i drm
inteldrm0 at pci0 dev 2 function 0 vendor "Intel", unknown product 0x5a85 rev 
0x0b
drm0 at inteldrm0
inteldrm0: msi
error: [drm:pid0:i915_firmware_load_error_print] *ERROR* failed to load 
firmware i915/bxt_dmc_ver1.bin (-22)
error: [drm:pid0:i915_gem_init_hw] *ERROR* Failed to initialize GuC, error -8 
(ignored)
inteldrm0: 1680x1050, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
error: [drm:pid51995:intel_pipe_update_start] *ERROR* Potential atomic update 
failure on pipe A


I can quit from cwm to console and restart X as much as i like, it does not 
crash X.

Thanks to all of you who replied and especially to Chris for his time!

NilsOpenBSD 6.2-current (GENERIC.MP) #379: Sat Jan 20 14:30:55 MST 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8209772544 (7829MB)
avail mem = 7954006016 (7585MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xed450 (18 entries)
bios0: vendor American Megatrends Inc. version "P1.40" date 07/14/2017
bios0: ASRock J3455-ITX
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT PRAM WSMT 
SSDT SSDT AAFT SSDT SSDT SSDT SSDT SSDT UEFI WDAT NHLT
acpi0: wakeup devices SIO1(S3) UAR1(S4) HDAS(S3) XHC_(S4) XDCI(S4) BRCM(S0) 
PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) 
PXSX(S4) RP05(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 1920 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Celeron(R) CPU J3455 @ 1.50GHz, 1497.14 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,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT
cpu0: 1MB 64b/line 16-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 19MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Celeron(R) CPU J3455 @ 1.50GHz, 1496.55 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,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT
cpu1: 1MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Celeron(R) CPU J3455 @ 1.50GHz, 1496.55 MHz
cpu2: 

Re: Problems with inteldrm on ASRock J3455-ITX (Apollo Lake)

[Nils Reuße]

Hi all,

I'm still investigating the issue, and while reading the motherboards handbook, 
i noticed that it has a COM1 connection port.  I've never done anything over 
serial, but if i understand the FAQ correctly, i could attach an adapter and 
get the boot messages over the serial console, and if there is a kernel panic 
even play around in ddb.

Is that correct, and would i need any (other) hardware than the ones listed 
below? (sorry for german amazon)

https://www.amazon.de/dp/B0015S32W4/
https://www.amazon.de/dp/B00QUZY4UG/


Nils

Re: Problems with inteldrm on ASRock J3455-ITX (Apollo Lake)

[Nils Reuße]

On 01/14/2018 08:54 PM, Chris Schultz wrote:



On Jan 14, 2018, at 12:32, Eric Furman <ericfur...@fastmail.net> wrote:


On Sun, Jan 14, 2018, at 12:53 PM, Nils Reuße wrote:
Hi there,

i got a new board (ASRock J3455-ITX) that's based intels apollo lake
SoC.  I've updated the bios to the latest version (1.4) and all things i
need are supported by openbsd out of the box on 6.2-current, except for
the graphic chip, an integrated Intel HD Graphics 500 chip.

Unfortunately, when i boot the system, the screen goes black very soon
(after the cpu info scrolls by) and then it never fully boots (login via
ssh is not possible), so i cannot see or check what's wrong.

If i disable inteldrm on boot, the system boots, ssh works and i can use
the system.  Trying to start X fails however.

As i intend to use the system as a headless server, i do not really care
if the card really works, but i'd like to be able to boot the system
without disabling inteldrm every time.

This is the firmware i've currently installed:

   $ doas fw_update -i
   Installed: intel-firmware-20180108

The graphics card shows as

   vga1 at pci0 dev 2 function 0 vendor "Intel", unknown product 0x5a85
rev 0x0b

Is anyone else here using this board, or is this error due to some
changes in the recent snapshots? Any help is appreciated.


This is not an OBSD specific problem.
Intel integrated graphics is crap.
They cause problems for a lot of people.
Do yourself a favor and disable the integrated graphics
and get yourself any cheap graphics card.
Preferably AMD based.



I have the same motherboard running the 2018-01-06 snapshot just fine, albeit 
without inteldrm installed (according to fw_update -i).





Hi Eric,

that sounds great!  Would you mind sharing your dmesg?  Do you use the 
UEFI or the compatibility mode?  Did you make specific changes in the bios?


Nils

Problems with inteldrm on ASRock J3455-ITX (Apollo Lake)

[Nils Reuße]

Hi there,

i got a new board (ASRock J3455-ITX) that's based intels apollo lake 
SoC.  I've updated the bios to the latest version (1.4) and all things i 
need are supported by openbsd out of the box on 6.2-current, except for 
the graphic chip, an integrated Intel HD Graphics 500 chip.


Unfortunately, when i boot the system, the screen goes black very soon 
(after the cpu info scrolls by) and then it never fully boots (login via 
ssh is not possible), so i cannot see or check what's wrong.


If i disable inteldrm on boot, the system boots, ssh works and i can use 
the system.  Trying to start X fails however.


As i intend to use the system as a headless server, i do not really care 
if the card really works, but i'd like to be able to boot the system 
without disabling inteldrm every time.


This is the firmware i've currently installed:

  $ doas fw_update -i
  Installed: intel-firmware-20180108

The graphics card shows as

  vga1 at pci0 dev 2 function 0 vendor "Intel", unknown product 0x5a85 
rev 0x0b


Is anyone else here using this board, or is this error due to some 
changes in the recent snapshots? Any help is appreciated.



I've only found a dmesg for the 'biger brother' ASRock J4205 (HD 
Graphics 505) from october, where the system recognized the graphics 
card (https://marc.info/?l=openbsd-misc=150970512103946=2):


  inteldrm0 at pci0 dev 2 function 0 vendor "Intel", unknown product 
0x5a84 rev 0x0b

  drm0 at inteldrm0
  inteldrm0: msi
  error: [drm:pid0:i915_firmware_load_error_print] *ERROR* failed to 
load firmware i915/bxt_dmc_ver1.bin (-22)
  error: [drm:pid0:i915_gem_init_hw] *ERROR* Failed to initialize GuC, 
error -8 (ignored)

  inteldrm0: 1920x1080, 32bpp


dmesg from my system is attached.

Best regards
Nils
OpenBSD 6.2-current (GENERIC.MP) #357: Sun Jan 14 00:37:52 MST 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8411095040 (8021MB)
avail mem = 8149233664 (7771MB)
User Kernel Config
UKC> disable inteldrm
226 inteldrm* disabled
UKC> quit
Continuing...
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xed450 (18 entries)
bios0: vendor American Megatrends Inc. version "P1.40" date 07/14/2017
bios0: ASRock J3455-ITX
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT PRAM WSMT 
SSDT SSDT AAFT SSDT SSDT SSDT SSDT SSDT UEFI DMAR WDAT NHLT
acpi0: wakeup devices SIO1(S3) HDAS(S3) XHC_(S4) XDCI(S4) BRCM(S0) PXSX(S4) 
RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) 
RP05(S4) PXSX(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 1920 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Celeron(R) CPU J3455 @ 1.50GHz, 1497.20 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,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT
cpu0: 1MB 64b/line 16-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 19MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Celeron(R) CPU J3455 @ 1.50GHz, 1496.56 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,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT
cpu1: 1MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Celeron(R) CPU J3455 @ 1.50GHz, 1496.56 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,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT
cpu2: 1MB 64b/line 16-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Celeron(R) CPU J3455 @ 1.50GHz, 1496.56 MHz
cpu3: 

Re: old macbook not resuming X

[Nils Reuße]

> Jan Stary  hat am 22. Mai 2017 um 10:41 geschrieben:
> 
> 
> Sorry for the long post.
> 
> This is current/amd64 on a MacBook2,1 (model A1181), dmesg below.
> I experience the same on a MacBook1,1 running current/i386.
> 
> On the console, each of apm -S -z -Z works, closing the lid as well.
> Each of them also resumes as expected.
> 
> On the other hand, trying to get to sleep from an xterm
> (via apm -S or -z or -Z) does not fully resume: upon resuming,
> X gets killed, the console keyboard does not reconnect properly,
> and keyboard input becomes garbage.  There is nothing to do but
> press the power button to reboot. (Or do it remotely.)
> 
> As the symptoms are the same for standby, suspend and hibernate,
> I will use suspend (apm -z) in the examples.
> 
> /var/log/messages of the console resume (good)
> and the X resume (bad) seem mostly the same (both below),
> except the naming order of the u* device being (re)attached;
> and the messages from the X suspend have some extra newlines
> in the middle of the message lines (which seems strange).
> Here is the diff lines (minus the leading timestamps):
> 
>   --- apm.goodMon May 22 09:45:56 2017
>   +++ apm.bad Mon May 22 09:46:00 2017
> 
>   -uhub0 detached
>   +uhub2 detached
> 
>   -uhub2 detached
>   +uhub3 detached
> 
>   -uhub3 detached
>   +uhub4 detached
> 
>   -uhub4 detached
>   +uhub0 detached
> 
>   -uhidev1 at uhub0 port 2 configuration 1 interface 1 "Apple Computer Apple 
> Internal Keyboard / Trackpad" rev 2.00/0.18 addr 2
>   +uhidev1 at uhub0
>   + port 2 configuration 1 interface 1 "Apple Computer Apple Internal 
> Keyboard / Trackpad" rev 2.00/0.18 addr 2
> 
>   -uhid2 at uhidev3 reportid 37: input=4, output=0, feature=0
>   +uhid2 at uhidev3 reportid 37
>   +: input=4, output=0, feature=0
> 
> 
> Please also see the Xorg log of the killed X session below.
> Firstly, it complains about /dev/xf86 and /dev/mem
> and asks for 'machdep.allowaperture=1'.
> 
>   (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
> (Operation not permitted)
> Check that you have set 'machdep.allowaperture=1'
> 
> Is that expected with inteldrm(4)?
> Is that related to the following drm errors in dmesg?
> Can it be related to the X not resuming?
> 
> drm: render error detected, EIR: 0x0010
> drm: page table error
> drm:   PGTBL_ER: 0x0102
> error: [drm:pid0:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x0010, 
> masking
> drm: render error detected, EIR: 0x0010
> drm: page table error
> drm:   PGTBL_ER: 0x0102
> 
> The X log also says:
> 
>   (II) The server relies on wscons to provide the list of input devices.
>   If no devices become available, reconfigure wscons or disable 
> AutoAddDevices.
> 
> and later ends (when X gets killed upon resume) with
> 
>   Fatal server error:
>   [   257.752] (EE) can't switch keyboard to raw mode.
>   Enable support for it in the kernel or use for example:
> 
> Option "Protocol" "wskbd"
> Option "Device" "/dev/wskbd0"
> 
>   in your xorg.conf(5) file
> 
> 
> I don't have a xorg.conf, because X works just fine beside this.
> Apparently, it has something to do with reattaching the wskbd,
> but that's way over my head. How do I enable support for
> "raw keyboard mode" in the kernel (it that's my problem)?
> 
> How can I help debug this?
> 
>   Jan
> 
> 
> boot dmesg:
> 
> OpenBSD 6.1-current (GENERIC.MP) #0: Sat May 20 12:31:37 CEST 2017
> h...@macbook.stare.cz:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 3171909632 (3024MB)
> avail mem = 3070050304 (2927MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe (37 entries)
> bios0: vendor Apple Inc. version "MB21.88Z.00A5.B07.0706270922" date 06/27/07
> bios0: Apple Inc. MacBook2,1
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP HPET APIC MCFG ASF! SBST ECDT SSDT SSDT SSDT
> acpi0: wakeup devices ADP1(S3) LID0(S3) PXS1(S4) PXS2(S4) USB1(S3) USB2(S3) 
> USB3(S3) USB4(S3) USB7(S3) EC__(S3)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpihpet0 at acpi0: 14318179 Hz
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz, 2161.65 MHz
> cpu0: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR
> cpu0: 4MB 64b/line 16-way L2 cache
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 166MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz, 2161.25 MHz
> cpu1: 
> 

Re: pkg.conf

[Nils Reuße]

> Theo Buehler  hat am 2. März 2017 um 22:44 geschrieben:
>
>
> On Thu, Mar 02, 2017 at 10:31:50PM +0100, Jan Stary wrote:
> > current.html says to # rm /etc/pkg.conf
> > after the switch to installurl(5).
> > Should it also say to
> >
> >   # rm /usr/share/man/man5/pkg.conf.5
>
> yes. fixed, thanks
>

I guess one should remove /etc/examples/pkg.conf then as well?

[patch] Enable support for Subpixel Antialiasing / LCD Filter

[Nils Reuße]

TL;DR: This patch allows users to use subpixel antialiasing/lcd filter
on openbsd, like on FreeBSD/most Linux distributions.  It does not
change the defaults. For full use, see my other patch at [7].


Dear all,

this patch enables subpixel rendering, which is disabled by default in
freetype (due to software patents), and enables users to use RGB
Antialiasing, which is a big improvements for low-DPI displays (e.g.
with a DPI of 96).

The current default ist greyscale AA (and no lcd filter), which is not
changed by this patch.  To use subpixel AA/lcd filter, you have to
manually enable it (see my config below).

>From [1]:

  By default, FreeType's scan-line converter returns "gray" sub-pixel
  images, where for each pixel the color components are equal (this is,
  R=G=B). The result is visually identical to gray anti-aliasing and
  cannot infringe any of the ClearType patents.

  Similarly, the LCD-specific filtering API is disabled by default,
  which means that it returns an error and doesn't alter sub-pixel
  images.

  You can override these limitations by activating option
  FT_CONFIG_OPTION_SUBPIXEL_RENDERING in FreeType's ftoption.h
  configuration file, but you should do that at your own risk.

Other Linux/BSD systems have this option enabled for a long time now,
under them Ubuntu, Debian [2], Freebsd [3], Arch Linux [4] and more.

There has been a privious discussion on this list on this topic [5]
where tedu@ mentions, that this issue is irrelevant once you get a
decent display with a higher DPI (or use bitmap fonts), which is of
course true [6].  But at least for me, at work we still have (and buy)
new monitors that have a DPI of 96 (e.g. Dell U2412M).  On these
displays, bitmap fonts are too tiny for me and don't scale well, so
subpixel rendering with enabled lcd filter really makes a difference.

For this patch, hinting should be set to "slight".  This is also
upstreams default, but unfortunately, openbsd forgot to merge the
relevant changes, so for now, unless the user does not change the
settings, it is hintfull.  See my patch at [7], which make slight
hinting the default.  More information from the freetype page at [8].

Once you recompile freetype with the patch, you can enable subpixel
hinting by adding the following snipped to your .config/fontconfig/fonts.conf:

  
  
  

  
rgb
  
  
lcddefault
  

  

Is there a chance to get this enabled in xenocara?

Regards
Nils

[1] https://www.freetype.org/patents.html
[2] 
http://metadata.ftp-master.debian.org/changelogs/main/f/freetype/freetype_2.5.2-3+deb8u1_changelog
[3] http://www.freshports.org/print/freetype2/
[4] 
https://git.archlinux.org/svntogit/packages.git/tree/trunk/0002-Enable-subpixel-rendering.patch?h=packages/freetype2
[5] http://marc.info/?l=openbsd-misc=146065800429682=2
[6] http://marc.info/?l=openbsd-misc=146315386122046=2
[7] http://marc.info/?l=openbsd-tech=148353268331986=2
[8] 
https://www.freetype.org/freetype2/docs/text-rendering-general.html#slight-hinting-invokes-the-native-hinter-if-possible


Index: lib/freetype/include/freetype/config/ftoption.h
===
RCS file: /cvs/xenocara/lib/freetype/include/freetype/config/ftoption.h,v
retrieving revision 1.19
diff -u -p -r1.19 ftoption.h
--- lib/freetype/include/freetype/config/ftoption.h 28 Oct 2016 21:41:15 
-  1.19
+++ lib/freetype/include/freetype/config/ftoption.h 9 Jan 2017 13:55:13 
-
@@ -122,7 +122,7 @@ FT_BEGIN_HEADER
   /* This is done to allow FreeType clients to run unmodified, forcing */
   /* them to display normal gray-level anti-aliased glyphs.*/
   /*   */
-/* #define FT_CONFIG_OPTION_SUBPIXEL_RENDERING */
+#define FT_CONFIG_OPTION_SUBPIXEL_RENDERING
 
 
   /*/

Re: simultaneous sound as many users

[Nils Reuße]

As a remark, to simultaneously listen to mpds music and the sound of a 
youtube video in Firefox (running under your user), you have to copy 
your cookie to /var/empty/ (_mpds home dir).


$ doas ls -l .aucat_cookie /var/empty/.aucat_cookie
-rw---  1 nils  nils  16 May 29  2015 .aucat_cookie
-rw---  1 _mpd  _mpd  16 May 29  2015 /var/empty/.aucat_cookie

$ doas sha1 -r .aucat_cookie /var/empty/.aucat_cookie
e8d33a71594c0ba7816e075d17afa81e0ba220ce .aucat_cookie
e8d33a71594c0ba7816e075d17afa81e0ba220ce /var/empty/.aucat_cookie

Re: simultaneous sound as many users

[Nils Reuße]

On 04/01/2016 08:42 PM, Roman Gorelov wrote:

My sndio configuration is default, OBSD 5.9.
When I run a media file in e.g. mpv, and pause it without closing, and
try to listen to smth in chrome _as another user_, there is no sound:



Hi Roman,

you need to share your sndio session cookie between the two users.  I 
got it working previously (the same problem arises with mpd, where the 
daemon runs as a separate user).  There should be a file called 
`~/.aucat_cookie` in your home-dir, and if i remember correctly, you 
just need to copy this file to the second users home dir.  Will check 
later when i'm back at home.


From sndio(7):

AUTHENTICATION

  If a shared sndiod(8) server is running, for privacy reasons only one
  user may have connections to it at a given time (though the same user
  could have multiple connections to it).  Users are identified by their
  session cookie, which is automatically generated by audio or MIDI
  applications upon the first connection to the server.  The cookie is
  stored in $HOME/.aucat_cookie and contains 128 bits of raw random
  data.

  If a session needs to be shared between multiple users, they can
  connect to the server using the same cookie.


Hope that helps
Nils

following -stable vs patches, "make clean" needed?

[Nils Reuße]

Hi misc,

i'm running 5.8-stable and am looking for a way automatically update my 
machine in case of updates.  Patches are fine, but they require manual 
interaction and i would like to avoid that as much as possible.


Both FAQ 5 [1] and the stable-page [2] propose to clean up before trying 
to (re)build the system, i.e. "make clean" or "rm -rf /usr/obj/*". 
Patches, on the other hand, do not propose to cleanup before rebuilding 
the changed parts (as far as i've seen).


So i was wondering if a pre-cleanup is required for a new -stable build, 
especially if i would make sure that a new build is only performed if 
the source files changed?


E.g. patch 5 for 5.8 affects the kernel and recommends to do

cd /usr/src/sys/arch/`machine`/conf
KK=`sysctl -n kern.osversion | cut -d# -f1`
config $KK
cd ../compile/$KK
make
make install

So no "make clean" here.  Is it safe to assume that -stable-updates will 
never require a cleanup?



Regards
Nils


[1] http://www.openbsd.org/faq/faq5.html#BldKernel
[2] http://www.openbsd.org/stable.html

Re: cdio(1) cdrip (error correction / why WAVE).

[Nils Reuße]

On 08/24/2015 11:25 AM, Marc Espie wrote:

As for complete cd ripping, abcde (in ports) comes to mind.
It is a fairly horrible script, but it works like a champ, and can be
easily configured to rip/tag/convert to the format of your choice.



I rip with cdparanoia, convert wav to flac and then tag with beets (from 
ports).


Here's my script (tagging with beets not included):

http://sprunge.us/XUdT?sh

Best
Nils

Re: Sluggish/laggy browser behaviour

[Nils Reuße]

On 07/28/2015 11:08 PM, Matthew Martin wrote:

On 7/26/15, Henrik Friedrichsen hen...@diff.cc wrote:

Hey

On Sun, Jul 26, 2015 at 10:46:30PM +0100, Dimitris Papastamos wrote:

Try viewtube[0] and gecko-mediaplayer instead.  No hangs on my system
at all.


Yeah, that is a workaround. Sometimes I use youtube_dl with mpv. That
was just one example, though ;p




I've used essentially this[1] bound to a key in cwm ever since coming
across it to watch videos... I prefer browsers to just browse[2].

#!/bin/sh
# needs zenity, youtube-dl and vlc installed

URL=$(zenity --entry --text Enter Video URL:)
if [ $URL =  ]; then
 echo You must enter a url.
 exit
fi
TMPFILE=$(mktemp /tmp/youtube-vid.XX)
youtube-dl --no-part -f 18/0/h264-sd -o $TMPFILE $URL 
DL_PID=$!
sleep 5
cvlc -f $TMPFILE vlc://quit
kill $DL_PID
rm $TMPFILE

---

[1] 
http://daemonforums.org/showpost.php?s=985087eedf0b6bd2d04482749e5fd726p=50021postcount=29

[2] I say as typing this into gmail...



Ha, someone's using my script on the internet ;) Nowadays mpv uses 
youtube-dl, so mpv url works with even less dependencies. Here's a 
newer version of my script:


#!/bin/sh

URL=$(xclip -o)
if [ $URL =  ]; then
echo You must select a url.
exit 1
fi
mpv -fs $URL

Re: X really slow dragging windows

[Nils Reuße]

On 04.03.2015 02:39, Jason Adams wrote:

Somewhere along the road of moving from 5.5 to 5.6 (i386) my performance in X 
has really taken a hit
when dragging windows around.  The window trails the pointer by several inches. 
 X performance used
to be surprisingly good on 5.5.

I note the following lines in Xorg.0.log:


[56.517] (--) RADEON(0): Chipset: ATI Radeon Mobility 7000 IGP 4437 
(ChipID = 0x4437)
[56.519] (II) RADEON(0): GPU accel disabled or not working, using shadowfb 
for KMS


fw_update reports no updates, (it does list a couple radeon entries as it 
checks for firmware).

Any clues as to what may be the issue here?  Is this fixable?




Hi Jason,

i can confirm this issue, though i have no idea how to fix it.  I also 
use an ATI card (HD 4250), but mine is supported and used with KMS. 
I've noticed this quite a while ago, but it doesn't bug me that much 
using a tiling wm.


Regards
Nils

Re: X really slow dragging windows

[Nils Reuße]

On 05.03.2015 08:14, Nils Reuße wrote:

On 04.03.2015 22:42, Jason Adams wrote:

On 03/04/2015 01:16 PM, Nils Reuße wrote:

On 04.03.2015 02:39, Jason Adams wrote:

Somewhere along the road of moving from 5.5 to 5.6 (i386) my performance in X 
has really taken a hit
when dragging windows around.  The window trails the pointer by several inches. 
 X performance used
to be surprisingly good on 5.5.

I note the following lines in Xorg.0.log:


[56.517] (--) RADEON(0): Chipset: ATI Radeon Mobility 7000 IGP 4437 
(ChipID = 0x4437)
[56.519] (II) RADEON(0): GPU accel disabled or not working, using shadowfb 
for KMS


fw_update reports no updates, (it does list a couple radeon entries as it 
checks for firmware).

Any clues as to what may be the issue here?  Is this fixable?




Hi Jason,

i can confirm this issue, though i have no idea how to fix it.  I also use an 
ATI card (HD 4250),
but mine is supported and used with KMS. I've noticed this quite a while ago, 
but it doesn't bug
me that much using a tiling wm.

Regards


Are you seeing the GPU disabled line in your Xorg.0.log?
My card is also supported, but I get that GPU not working line, and until that 
gets solved
I am stuck using shadowfb, (and ugly friends).  And I believe that is the 
reason for the slowness.



No, i don't see anything beeing disabled in my xorg log, and my card is
working fine (just tried openarena, which always worked and still works
fine).

In my last mail i forgot to mention that i'm running the latest -current
snapshot as of yesterday, but as is said, i've noticed this problem a
few months before (but after 5.6).  dmesg and my xorg log attached.
OpenBSD 5.7-beta (GENERIC.MP) #871: Tue Mar  3 17:40:49 MST 2015
 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3738107904 (3564MB)
avail mem = 3634679808 (3466MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0100 (61 entries)
bios0: vendor Award Software International, Inc. version F5 date 09/30/2010
bios0: Gigabyte Technology Co., Ltd. GA-880GMA-UD2H
acpi0 at bios0: rev 0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT HPET MCFG MATS APIC
acpi0: wakeup devices USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) 
USB6(S3) SBAZ(S4) PEX0(S5) PEX1(S5) PEX2(S5) PEX3(S5) P2P_(S5) PCE2(S4) 
PCE3(S4) PCE4(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 Athlon(tm) II X2 240e Processor, 2813.27 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,PAGE1GB,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, 1MB 64b/line 
16-way L2 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 Athlon(tm) II X2 240e Processor, 2812.93 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,PAGE1GB,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, 1MB 64b/line 
16-way L2 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
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 5 (PEX0)
acpiprt2 at acpi0: bus 6 (PEX1)
acpiprt3 at acpi0: bus -1 (PEX2)
acpiprt4 at acpi0: bus -1 (PEX3)
acpiprt5 at acpi0: bus 4 (P2P_)
acpiprt6 at acpi0: bus -1 (PCE2)
acpiprt7 at acpi0: bus -1 (PCE3)
acpiprt8 at acpi0: bus -1 (PCE4)
acpiprt9 at acpi0: bus -1 (PCE5)
acpiprt10 at acpi0: bus -1 (PCE6)
acpiprt11 at acpi0: bus -1 (PCE7)
acpiprt12 at acpi0: bus 2 (PCE9)
acpiprt13 at acpi0: bus 3 (PCEA)
acpiprt14 at acpi0: bus -1 (PCEB)
acpiprt15 at acpi0: bus -1 (PCEC)
acpiprt16 at acpi0: bus 1 (AGP_)
acpicpu0 at acpi0: PSS
acpicpu1 at acpi0: PSS
acpibtn0 at acpi0: PWRB
cpu0: 2813 MHz: speeds: 2800 2100 1600 800 MHz
pci0 at mainbus0 bus 0
0:0:0: mem address conflict 0xe000/0x2000
pchb0 at pci0 dev 0 function 0 AMD RS880 Host rev 0x00
ppb0 at pci0 dev 1 function 0 AMD

Re: X really slow dragging windows

[Nils Reuße]

On 04.03.2015 22:42, Jason Adams wrote:
 On 03/04/2015 01:16 PM, Nils Reuße wrote:
 On 04.03.2015 02:39, Jason Adams wrote:
 Somewhere along the road of moving from 5.5 to 5.6 (i386) my performance in 
 X has really taken a hit
 when dragging windows around.  The window trails the pointer by several 
 inches.  X performance used
 to be surprisingly good on 5.5.

 I note the following lines in Xorg.0.log:

 [56.517] (--) RADEON(0): Chipset: ATI Radeon Mobility 7000 IGP 4437 
 (ChipID = 0x4437)
 [56.519] (II) RADEON(0): GPU accel disabled or not working, using 
 shadowfb for KMS

 fw_update reports no updates, (it does list a couple radeon entries as it 
 checks for firmware).

 Any clues as to what may be the issue here?  Is this fixable?



 Hi Jason,

 i can confirm this issue, though i have no idea how to fix it.  I also use 
 an ATI card (HD 4250),
 but mine is supported and used with KMS. I've noticed this quite a while 
 ago, but it doesn't bug
 me that much using a tiling wm.

 Regards

 Are you seeing the GPU disabled line in your Xorg.0.log?
 My card is also supported, but I get that GPU not working line, and until 
 that gets solved
 I am stuck using shadowfb, (and ugly friends).  And I believe that is the 
 reason for the slowness.


No, i don't see anything beeing disabled in my xorg log, and my card is 
working fine (just tried openarena, which always worked and still works 
fine).

In my last mail i forgot to mention that i'm running the latest -current 
snapshot as of yesterday, but as is said, i've noticed this problem a 
few months before (but after 5.6).  dmesg and my xorg log attached.
OpenBSD 5.7-beta (GENERIC.MP) #871: Tue Mar  3 17:40:49 MST 2015
t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3738107904 (3564MB)
avail mem = 3634679808 (3466MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0100 (61 entries)
bios0: vendor Award Software International, Inc. version F5 date 09/30/2010
bios0: Gigabyte Technology Co., Ltd. GA-880GMA-UD2H
acpi0 at bios0: rev 0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT HPET MCFG MATS APIC
acpi0: wakeup devices USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) 
USB6(S3) SBAZ(S4) PEX0(S5) PEX1(S5) PEX2(S5) PEX3(S5) P2P_(S5) PCE2(S4) 
PCE3(S4) PCE4(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 Athlon(tm) II X2 240e Processor, 2813.27 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,PAGE1GB,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, 1MB 64b/line 
16-way L2 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 Athlon(tm) II X2 240e Processor, 2812.93 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,PAGE1GB,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, 1MB 64b/line 
16-way L2 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
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 5 (PEX0)
acpiprt2 at acpi0: bus 6 (PEX1)
acpiprt3 at acpi0: bus -1 (PEX2)
acpiprt4 at acpi0: bus -1 (PEX3)
acpiprt5 at acpi0: bus 4 (P2P_)
acpiprt6 at acpi0: bus -1 (PCE2)
acpiprt7 at acpi0: bus -1 (PCE3)
acpiprt8 at acpi0: bus -1 (PCE4)
acpiprt9 at acpi0: bus -1 (PCE5)
acpiprt10 at acpi0: bus -1 (PCE6)
acpiprt11 at acpi0: bus -1 (PCE7)
acpiprt12 at acpi0: bus 2 (PCE9)
acpiprt13 at acpi0: bus 3 (PCEA)
acpiprt14 at acpi0: bus -1 (PCEB)
acpiprt15 at acpi0: bus -1 (PCEC)
acpiprt16 at acpi0: bus 1 (AGP_)
acpicpu0 at acpi0: PSS
acpicpu1 at acpi0: PSS
acpibtn0 at acpi0: PWRB
cpu0: 2813 MHz: speeds: 2800 2100 1600 800 MHz
pci0 at mainbus0 bus 0
0:0:0: mem address conflict 0xe000/0x2000
pchb0 at pci0 dev 0 function 0 AMD RS880 Host rev 0x00
ppb0 at pci0 dev 1 function 0 AMD RS780 PCIE rev 0x00

Problems with Dell ALPS touchpad on -current

[Nils Reuße]

I did some more research and got the following (including vendor and
product ids) from my Arch Linux installation:

$ uname -rsm
Linux 3.3.4-2-ARCH x86_64


$ cat /proc/bus/input/devices
[...]
I: Bus=0011 Vendor=0002 Product=0008 Version=
N: Name=DualPoint Stick
P: Phys=isa0060/serio1/input1
S: Sysfs=/devices/platform/i8042/serio1/input/input7
U: Uniq=
H: Handlers=mouse0 event7
B: PROP=0
B: EV=7
B: KEY=7 0 0 0 0
B: REL=3

I: Bus=0011 Vendor=0002 Product=0008 Version=7326
N: Name=AlpsPS/2 ALPS DualPoint TouchPad
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input8
U: Uniq=
H: Handlers=mouse1 event8
B: PROP=8
B: EV=b
B: KEY=e420 7 0 0 0 0
B: ABS=2608103
[...]


$ lsinput
[...]
/dev/input/event7
   bustype : BUS_I8042
   vendor  : 0x2
   product : 0x8
   version : 0
   name: DualPoint Stick
   phys: isa0060/serio1/input1
   bits ev : EV_SYN EV_KEY EV_REL

/dev/input/event8
   bustype : BUS_I8042
   vendor  : 0x2
   product : 0x8
   version : 29478
   name: AlpsPS/2 ALPS DualPoint TouchPad
   phys: isa0060/serio1/input0
   bits ev : EV_SYN EV_KEY EV_ABS
[...]


Does this help? lsinput comes from
http://www.kraxel.org/releases/input/ and is available in
debian/ubuntu.

Best regards,
Nils

Re: Problems with Dell ALPS touchpad on -current

[Nils Reuße]

Hi Martin, thank you for the hint. Unfortunately, I have no experience
with driver programming, so I won't be able to provide diffs :(

Best regards,
Nils



2012/5/8 Martin Pieuchot mpieuc...@nolizard.org:
 On 08/05/12(Tue) 13:53, Nils Reu_e wrote:
 I did some more research and got the following (including vendor and
 product ids) from my Arch Linux installation:

 [...]

 I: Bus=0011 Vendor=0002 Product=0008 Version=7326
   

 If you look at /sys/dev/pckbc/pms.c you'll find:

#if 0
 { 0x7326, 0, 0 },   /* XXX Uses unknown v3 protocol */
#endif

 Your touchpad uses a different protocol and is currently not supported
 under OpenBSD. But if like you said Linux now supports this version of
 ALPS touchpads, it should be possible to learn this protocol from their
 driver.

 If you have some diffs, don't hesitate to contact me.

 Martin

Problems with Dell ALPS touchpad on -current

[Nils Reuße]

Hi misc@,

I have a problem with an ALPS touchpad on my Dell Latitude E5420:
Moving the cursor is really slow and scrolling does not work. This
problem still exists with the latest -current snapshot (amd64). Reading
http://www.openbsd.org/plus.html, I saw that some support for Dell ALPS
touchpads was added, but it seems that my specific model was left out.

Grepping for `mouse' in /var/log/Xorg.0.log results in:

$ grep mouse /var/log/Xorg.0.log
[515289.032] (==) intel(0): Silken mouse disabled
[515293.915] (II) config/wscons: checking input device /dev/wsmouse
[515293.937] (II) Using input driver 'ws' for '/dev/wsmouse'
[515293.937] (**) /dev/wsmouse: always reports core events
[515293.937] (II) ws: /dev/wsmouse: debuglevel 0
[515293.937] (**) Option Device /dev/wsmouse
[515293.937] (**) ws: /dev/wsmouse: ZAxisMapping: buttons 4 and 5
[515293.937] (**) ws: /dev/wsmouse: WAxisMapping: buttons 6 and 7
[515293.937] (**) ws: /dev/wsmouse: associated screen: 0
[515296.107] (II) ws: /dev/wsmouse: minimum x position: 0
[515296.107] (II) ws: /dev/wsmouse: maximum x position: 1599
[515296.107] (II) ws: /dev/wsmouse: minimum y position: 0
[515296.107] (II) ws: /dev/wsmouse: maximum y position: 899
[515296.107] (==) ws: /dev/wsmouse: Buttons: 7
[515296.125] (**) ws: /dev/wsmouse: YAxisMapping: buttons 4 and 5
[515296.125] (II) XINPUT: Adding extended input device /dev/wsmouse
(type: MOUSE, id 7)
[515298.285] (**) /dev/wsmouse: (accel) keeping acceleration scheme 1
[515298.285] (**) /dev/wsmouse: (accel) acceleration profile 0
[515298.285] (**) /dev/wsmouse: (accel) acceleration factor: 2.000
[515298.285] (**) /dev/wsmouse: (accel) acceleration threshold: 4


dmesg says:

$ dmesg | grep pms
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0


The same problem existed on Linux up to kernel 3.2, where the touchpad
was recognized as a ps/2 device. This was fixed with version 3.3. On
Arch Linux, some patches could be applied with this package, just in
case that this could be of help: http://aur.archlinux.org/packages.php?ID=52538.

I am not sure what else I could supply to solve this problem, so if I
forgot something important, please tell me :) For now, I append the full
Xorg.0.log and dmesg.

Best regards,
Nils


dmesg:

OpenBSD 5.1-current (GENERIC.MP) #290: Thu Apr 26 01:27:14 MDT 2012
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error 3fconfig_unit,memory_size,fixed_disk,invalid_time
real mem = 8481353728 (8088MB)
avail mem = 8233230336 (7851MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf20f0 (80 entries)
bios0: vendor Dell Inc. version A03 date 09/19/2011
bios0: Dell Inc. Latitude E5420
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC TCPA SSDT ASF! MCFG HPET BOOT SSDT SSDT DMAR
acpi0: wakeup devices UAR1(S3) HDEF(S4) PXSX(S4) RP01(S4) PXSX(S4)
RP02(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4)
PXSX(S4) RP07(S4) PXSX(S4) RP08(S4) PEG0(S4) PEGP(S4) PEG1(S4)
GLAN(S4) PEG2(S4) PEG3(S4) PXSX(S4) RP03(S4) EHC2(S1) EHCI(S1)
LID_(S3) PBTN(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2494.71 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,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,XSAVE,AVX,NXE,LONG,LAHF
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: apic clock running at 99MHz
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2494.33 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,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,XSAVE,AVX,NXE,LONG,LAHF
cpu1: 256KB 64b/line 8-way L2 cache
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2494.33 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,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,XSAVE,AVX,NXE,LONG,LAHF
cpu2: 256KB 64b/line 8-way L2 cache
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2494.33 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,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,XSAVE,AVX,NXE,LONG,LAHF
cpu3: 256KB 64b/line 8-way L2 cache
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (P0P1)
acpiprt2 at acpi0: bus 1 (RP01)

Difference between openbsd.org and www.openbsd.org

[Nils Reuße]

Hi misc@,

I just noticed that http://openbsd.org/errata50.html (without www) does
not list the RELIABILITY FIX 001. http://www.openbsd.org/errata50.html
does have it though. Keep up the good work :)

Regards,
Nils