On 02/23/17 04:35, Tobias Brodel wrote:
>> I noticed this too and mentioned it on a ports dev chat, I remember
>> it working a few weeks ago. But I'm not sure if it stopped working
>> before or after the 56.0.2924.87 update..
>>
>> It appears to affect only some HTML5 video streaming sites, like
>> Youtube and Twitch, but embedded <video> still works. It doesn't
>> appear to be drm(4) obviously related either as WebGL demos work
>> fine.
>>
>> At least a few people said it still works for them, so perhaps
>> it's a certain hardware combination that's causing this?
>>
>> -Bryan.
>>
> 
> I'm experiencing this too: Thinkpad T430 on recent snapshots.
> 
> inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09
> drm0 at inteldrm0
> inteldrm0: msi
> inteldrm0: 1366x768, 32bpp
> wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)

I'm having the same problem on recent snapshot with both Chromium and
Iridium. The machine has an Radeon graphics card (see below).

Kind regards,


Martijn Rijkeboer


$ sysctl kern.version
kern.version=OpenBSD 6.0-current (GENERIC.MP) #184: Mon Feb 20 22:44:10
MST 2017
    dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

$ pkg_info |egrep 'chromium|iridium'
chromium-56.0.2924.87 Chromium browser
iridium-54.0        Iridium browser

$ dmesg |grep drm
radeondrm0 at pci1 dev 0 function 0 "ATI Radeon HD 4350" rev 0x00
drm0 at radeondrm0
radeondrm0: msi
radeondrm0: 1920x1200, 32bpp
wsdisplay0 at radeondrm0 mux 1: console (std, vt100 emulation), using wskbd0

Reply via email to