Re: [mpv] --vo=gpu not working, permission denied

2024-02-27 Thread Jose Maldonado
El Tue, 27 Feb 2024 10:35:54 -
beecdadd...@danwin1210.de escribió:
> hi sorry it was a chown problem because tty0 and fbtab, someone else
> helped thanks for time
> question: vulken error is OK if you don't have vulkaninfo installed,
> yes?
> 
> On Tue, February 27, 2024 5:49 am, Jose Maldonado wrote:
> > El Mon, 26 Feb 2024 21:54:43 -
> > beecdadd...@danwin1210.de escribió:  
> >> hi list
> >>
> >> mpv does not work OpenBSD -current updated 2 days ago, pkg_add -u
> >> was done now Thinkpad T400 laptop with Intep GPU
> >> say if you need more info than this and down
> >>
> >> mpv gives this error (+) Video --vid=1 (*) (vp8 240x424 30.000fps)
> >> (+) Audio --aid=1 --alang=eng (*) (vorbis 2ch 48000Hz)
> >> libEGL warning: MESA-LOADER: failed to retrieve device information
> >>
> >> libEGL warning: failed to open /dev/dri/card0: Permission denied
> >>
> >> libEGL warning: DRI2: could not open /dev/dri/card0 (Permission
> >> denied) [vo/gpu/opengl] Suspected software renderer or indirect
> >> context. [vo/gpu/libplacebo] EnumeratePhysicalDevices(inst, ,
> >> NULL): VK_ERROR_INITIALIZATION_FAILED
> >> (../libplacebo-6.338.2/src/vulkan/context.c:984)
> >> [vo/gpu/libplacebo] Found no suitable device, giving up.
> >> [vo/gpu/libplacebo] Failed initializing vulkan device
> >> [vo/gpu/libplacebo] EnumeratePhysicalDevices(inst, , NULL):
> >> VK_ERROR_INITIALIZATION_FAILED
> >> (../libplacebo-6.338.2/src/vulkan/context.c:984)
> >> [vo/gpu] Failed initializing any suitable GPU context!
> >> Error opening/initializing the selected video_out (--vo) device.
> >> Video: no video
> >> Exiting... (Errors when loading file)
> >>
> >>
> >>
> >>
> >> dmesg gave this error, not fresh
> >> drm:pid8053:drm_atomic_helper_wait_for_flip_done *ERROR* [drm]
> >> *ERROR* [CRTC:45:pipe A] flip_done timed out
> >> drm:pid51733:intel_pipe_update_start *ERROR* [drm] *ERROR*
> >> Potential atomic update failure on pipe A
> >>  
> >
> > Hi!
> >
> >
> > Can you provide your mpv.conf and the exact output for theses
> > commands?
> >
> > 1) mpv -v --vo=gpu --gpu-api=opengl your_video
> >
> >
> > 2) mpv -v --vo=gpu --gpu-api=vulkan your_video
> >
> >
> > 3) glxinfo
> >
> >
> > 4) vulkaninfo
> >
> >
> > Please provide the info in separate files
> >
> >
> > --
> > *
> > Dios en su cielo, todo bien en la Tierra
> >
> >
> >  
> 
> 

Not problem, and Vulkan errors are normal, it is part of the mpv
testing system, if you do not have support it will not do anything
using that backend and will use the supported one (OpenGL or X11)


-- 
*
Dios en su cielo, todo bien en la Tierra



Re: [mpv] --vo=gpu not working, permission denied

2024-02-27 Thread beecdaddict
hi sorry it was a chown problem because tty0 and fbtab, someone else helped
thanks for time
question: vulken error is OK if you don't have vulkaninfo installed, yes?

On Tue, February 27, 2024 5:49 am, Jose Maldonado wrote:
> El Mon, 26 Feb 2024 21:54:43 -
> beecdadd...@danwin1210.de escribió:
>> hi list
>>
>> mpv does not work OpenBSD -current updated 2 days ago, pkg_add -u was
>> done now Thinkpad T400 laptop with Intep GPU
>> say if you need more info than this and down
>>
>> mpv gives this error (+) Video --vid=1 (*) (vp8 240x424 30.000fps)
>> (+) Audio --aid=1 --alang=eng (*) (vorbis 2ch 48000Hz)
>> libEGL warning: MESA-LOADER: failed to retrieve device information
>>
>> libEGL warning: failed to open /dev/dri/card0: Permission denied
>>
>> libEGL warning: DRI2: could not open /dev/dri/card0 (Permission denied)
>> [vo/gpu/opengl] Suspected software renderer or indirect
>> context. [vo/gpu/libplacebo] EnumeratePhysicalDevices(inst, , NULL):
>> VK_ERROR_INITIALIZATION_FAILED
>> (../libplacebo-6.338.2/src/vulkan/context.c:984)
>> [vo/gpu/libplacebo] Found no suitable device, giving up.
>> [vo/gpu/libplacebo] Failed initializing vulkan device
>> [vo/gpu/libplacebo] EnumeratePhysicalDevices(inst, , NULL):
>> VK_ERROR_INITIALIZATION_FAILED
>> (../libplacebo-6.338.2/src/vulkan/context.c:984)
>> [vo/gpu] Failed initializing any suitable GPU context!
>> Error opening/initializing the selected video_out (--vo) device.
>> Video: no video
>> Exiting... (Errors when loading file)
>>
>>
>>
>>
>> dmesg gave this error, not fresh
>> drm:pid8053:drm_atomic_helper_wait_for_flip_done *ERROR* [drm] *ERROR*
>> [CRTC:45:pipe A] flip_done timed out
>> drm:pid51733:intel_pipe_update_start *ERROR* [drm] *ERROR* Potential
>> atomic update failure on pipe A
>>
>
> Hi!
>
>
> Can you provide your mpv.conf and the exact output for theses
> commands?
>
> 1) mpv -v --vo=gpu --gpu-api=opengl your_video
>
>
> 2) mpv -v --vo=gpu --gpu-api=vulkan your_video
>
>
> 3) glxinfo
>
>
> 4) vulkaninfo
>
>
> Please provide the info in separate files
>
>
> --
> *
> Dios en su cielo, todo bien en la Tierra
>
>
>




[Fwd: Re: [mpv] --vo=gpu not working, permission denied]

2024-02-27 Thread beecdaddict
 Original Message 
Subject: Re: [mpv] --vo=gpu not working, permission denied
From:beecdadd...@danwin1210.de
Date:Tue, February 27, 2024 10:24 am
To:  "Stefan Hagen" 
--

thanks!
I remember doing in past and looking at GiveConsole
I can't believe I forgot about this of course I didn't know why it happened

it fixes this yes
can I ask why does console tty0 do that and not others, what is the purpose?

best regards

On Tue, February 27, 2024 6:00 am, Stefan Hagen wrote:
> beecdadd...@danwin1210.de wrote (2024-02-26 22:54 CET):
>> libEGL warning: failed to open /dev/dri/card0: Permission denied
>
> You can fix it with: chown  /dev/dri/card0 /dev/dri/renderD128
>
>
> Xenodm does this automatically when you log in.
> See /etc/X11/xenodm/GiveConsole
>
>
> The permission are also set when you log in on ttyC0.
> See /etc/fbtab and fbtab(5)
>
>
> Therefore the permissions are changing when you jump out of X
> with ctrl+alt+f1 and log in as root. When you hop back into X, the
> permissions are wrong.
>
> This only happens on the first console. Use another one instead
> (ctrl+alt+f2,3,4) while using X.
>
>
> Best Regards,
> Stefan




Re: [mpv] --vo=gpu not working, permission denied

2024-02-27 Thread beecdaddict
you are faster than me asking questions
well maybe a warning in dmesg or something will be nice so you don't get
same people asking this fix? or save the initial user who owned
/dev/dri/.. and then chown back to that after exit or something?

On Tue, February 27, 2024 6:13 am, Theo de Raadt wrote:
> This is because the fbtab subsystem is quite broken.  No good
> alternative designs have come forward.
>
> Stefan Hagen  wrote:
>
>
>> beecdadd...@danwin1210.de wrote (2024-02-26 22:54 CET):
>>> libEGL warning: failed to open /dev/dri/card0: Permission denied
>>
>> You can fix it with: chown  /dev/dri/card0 /dev/dri/renderD128
>>
>>
>> Xenodm does this automatically when you log in.
>> See /etc/X11/xenodm/GiveConsole
>>
>>
>> The permission are also set when you log in on ttyC0.
>> See /etc/fbtab and fbtab(5)
>>
>>
>> Therefore the permissions are changing when you jump out of X
>> with ctrl+alt+f1 and log in as root. When you hop back into X, the
>> permissions are wrong.
>>
>> This only happens on the first console. Use another one instead
>> (ctrl+alt+f2,3,4) while using X.
>>
>>
>> Best Regards,
>> Stefan
>>
>>
>
>




Re: [mpv] --vo=gpu not working, permission denied

2024-02-26 Thread Theo de Raadt
This is because the fbtab subsystem is quite broken.  No good
alternative designs have come forward.

Stefan Hagen  wrote:

> beecdadd...@danwin1210.de wrote (2024-02-26 22:54 CET):
> > libEGL warning: failed to open /dev/dri/card0: Permission denied
> 
> You can fix it with: chown  /dev/dri/card0 /dev/dri/renderD128
> 
> Xenodm does this automatically when you log in.
> See /etc/X11/xenodm/GiveConsole
> 
> The permission are also set when you log in on ttyC0.
> See /etc/fbtab and fbtab(5)
> 
> Therefore the permissions are changing when you jump out of X
> with ctrl+alt+f1 and log in as root. When you hop back into X,
> the permissions are wrong.
> 
> This only happens on the first console. Use another one instead 
> (ctrl+alt+f2,3,4) while using X.
> 
> Best Regards,
> Stefan
> 



Re: [mpv] --vo=gpu not working, permission denied

2024-02-26 Thread Stefan Hagen
beecdadd...@danwin1210.de wrote (2024-02-26 22:54 CET):
> libEGL warning: failed to open /dev/dri/card0: Permission denied

You can fix it with: chown  /dev/dri/card0 /dev/dri/renderD128

Xenodm does this automatically when you log in.
See /etc/X11/xenodm/GiveConsole

The permission are also set when you log in on ttyC0.
See /etc/fbtab and fbtab(5)

Therefore the permissions are changing when you jump out of X
with ctrl+alt+f1 and log in as root. When you hop back into X,
the permissions are wrong.

This only happens on the first console. Use another one instead 
(ctrl+alt+f2,3,4) while using X.

Best Regards,
Stefan



Re: [mpv] --vo=gpu not working, permission denied

2024-02-26 Thread Jose Maldonado
El Mon, 26 Feb 2024 21:54:43 -
beecdadd...@danwin1210.de escribió:
> hi list
> 
> mpv does not work
> OpenBSD -current updated 2 days ago, pkg_add -u was done now
> Thinkpad T400 laptop with Intep GPU
> say if you need more info than this and down
> 
> mpv gives this error
>  (+) Video --vid=1 (*) (vp8 240x424 30.000fps)
>  (+) Audio --aid=1 --alang=eng (*) (vorbis 2ch 48000Hz)
> libEGL warning: MESA-LOADER: failed to retrieve device information
> 
> libEGL warning: failed to open /dev/dri/card0: Permission denied
> 
> libEGL warning: DRI2: could not open /dev/dri/card0 (Permission
> denied) [vo/gpu/opengl] Suspected software renderer or indirect
> context. [vo/gpu/libplacebo] EnumeratePhysicalDevices(inst, ,
> NULL): VK_ERROR_INITIALIZATION_FAILED
> (../libplacebo-6.338.2/src/vulkan/context.c:984)
> [vo/gpu/libplacebo] Found no suitable device, giving up.
> [vo/gpu/libplacebo] Failed initializing vulkan device
> [vo/gpu/libplacebo] EnumeratePhysicalDevices(inst, , NULL):
> VK_ERROR_INITIALIZATION_FAILED
> (../libplacebo-6.338.2/src/vulkan/context.c:984)
> [vo/gpu] Failed initializing any suitable GPU context!
> Error opening/initializing the selected video_out (--vo) device.
> Video: no video
> Exiting... (Errors when loading file)
> 
> 
> 
> dmesg gave this error, not fresh
> drm:pid8053:drm_atomic_helper_wait_for_flip_done *ERROR* [drm] *ERROR*
> [CRTC:45:pipe A] flip_done timed out
> drm:pid51733:intel_pipe_update_start *ERROR* [drm] *ERROR* Potential
> atomic update failure on pipe A
> 

Hi! 

Can you provide your mpv.conf and the exact output for theses
commands?

1) mpv -v --vo=gpu --gpu-api=opengl your_video

2) mpv -v --vo=gpu --gpu-api=vulkan your_video

3) glxinfo 

4) vulkaninfo 

Please provide the info in separate files 

-- 
*
Dios en su cielo, todo bien en la Tierra



[mpv] --vo=gpu not working, permission denied

2024-02-26 Thread beecdaddict
hi list

mpv does not work
OpenBSD -current updated 2 days ago, pkg_add -u was done now
Thinkpad T400 laptop with Intep GPU
say if you need more info than this and down

mpv gives this error
 (+) Video --vid=1 (*) (vp8 240x424 30.000fps)
 (+) Audio --aid=1 --alang=eng (*) (vorbis 2ch 48000Hz)
libEGL warning: MESA-LOADER: failed to retrieve device information

libEGL warning: failed to open /dev/dri/card0: Permission denied

libEGL warning: DRI2: could not open /dev/dri/card0 (Permission denied)
[vo/gpu/opengl] Suspected software renderer or indirect context.
[vo/gpu/libplacebo] EnumeratePhysicalDevices(inst, , NULL):
VK_ERROR_INITIALIZATION_FAILED
(../libplacebo-6.338.2/src/vulkan/context.c:984)
[vo/gpu/libplacebo] Found no suitable device, giving up.
[vo/gpu/libplacebo] Failed initializing vulkan device
[vo/gpu/libplacebo] EnumeratePhysicalDevices(inst, , NULL):
VK_ERROR_INITIALIZATION_FAILED
(../libplacebo-6.338.2/src/vulkan/context.c:984)
[vo/gpu] Failed initializing any suitable GPU context!
Error opening/initializing the selected video_out (--vo) device.
Video: no video
Exiting... (Errors when loading file)



dmesg gave this error, not fresh
drm:pid8053:drm_atomic_helper_wait_for_flip_done *ERROR* [drm] *ERROR*
[CRTC:45:pipe A] flip_done timed out
drm:pid51733:intel_pipe_update_start *ERROR* [drm] *ERROR* Potential
atomic update failure on pipe A