Kornell
Posts: 1
Joined: Sun Feb 05, 2017 12:58 am

Re: New Open GL Driver, Bug report thread

Sun Feb 05, 2017 1:16 am

Raspbbery 3
Raspbian jessie
hdmi_group=2
hdmi_mode=85 (1280x720, 60Hz, 720p)

Running: Panda 3D (game engine) demo scene
Working about an hour and freezes.
Tried different windowed resolutions: 320x240, 640x480, 800x600.
Run log:

[email protected]:~ $ python ~/_panda/panda-4.py
Known pipe types:
glxGraphicsPipe
(all display modules loaded.)
libGL error: MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
AL lib: (WW) alc_initconfig: Failed to initialize backend "pulse"

Message from [email protected] at Feb 5 03:11:58 ...
kernel:[ 9758.448337] Internal error: Oops: 17 [#1] SMP ARM

Message from [email protected] at Feb 5 03:11:58 ...
kernel:[ 9758.560018] Process w1_bus_master1 (pid: 186, stack limit = 0xaca36210)

Message from [email protected] at Feb 5 03:11:58 ...
kernel:[ 9758.566721] Stack: (0xaca37dc0 to 0xaca38000)

Message from [email protected] at Feb 5 03:11:58 ...
kernel:[ 9758.571136] 7dc0: 5bf7f528 6f6f4ab4 aca37df0 aca37dd8 8017c4d4 8017c44c aca37dfc aca37df8

Message from [email protected] at Feb 5 03:11:58 ...
kernel:[ 9758.579428] 7de0: aca37df8 aca37e14 aca37e00 8011dc7c 8017c4b8 806e0e04 fffffffa 00001b58

Message from [email protected] at Feb 5 03:11:58 ...
kernel:[ 9758.587720] 7e00: 00000000 a1c86250 aca37e2c aca37e18 803aaf6c 803ae764 a1c86284 a1c86250

... and so on, two last messages: ...

Message from [email protected] at Feb 5 03:11:58 ...
kernel:[ 9758.712099] 7fe0: 00000000 00000000 00000000 00000000 00000013 00000000 2ef77861 2ef77c61

Message from [email protected] at Feb 5 03:11:58 ...
kernel:[ 9758.735934] Code: e52de004 e8bd4000 e1a04000 e1a0e001 (e590000c)

-----------
I want to say thank you for this driver, it's awesome.
Great performance (incredible FPS for 35$ device) and less CPU usage (80% -> below 20% with my 3D experiments).
I wish you all the best of luck!

josephfarkas
Posts: 1
Joined: Tue Feb 07, 2017 10:14 pm

No Signal to Monitor

Tue Feb 07, 2017 10:26 pm

Hello, I just got a Raspberry Pi 3 for Christmas. I have done many projects since including a Minecraft server. I had also been looking forward to installing the full version of Minecraft (not Minecraft pi), using this tutorial (viewtopic.php?t=137279). I tried doing it but when I enabled the GL Driver and rebooted, it showed an error, and I had to reset the sd card. Yesterday I thought that you may have updated the driver so I tried again. Sure enough, when I rebooted I saw the color screen, black screen, code, and then no signal. I still saw the lights on the pi, and when I tried to ssh and vnc, it worked. When I pressed Ctr, Alt, F2 on the pi, it switched to the terminal. In ssh, I tried to edit the /boot/config.txt to change some settings but nothing worked. Finally, I went into sudo raspi-config and disabled the driver, and sure enough, the desktop loaded on the pi. Is this a problem with the monitor or with the driver. I will try a different monitor later, and I will reply the results.

pneumatics
Posts: 1
Joined: Sun Feb 26, 2017 4:24 pm

Re: New Open GL Driver, Bug report thread

Sun Feb 26, 2017 4:39 pm

Not working for me!
Box: R Pi 3 + Raspbian + LXDE + lightdm
Display: Dell P2217H (1920 x 1080 at 60Hz ) over HDMI
First tried G1. No x after reboot.(I did panic :o but sshed and restored to G3)
Second try G2.Display showing something weired. no taskbar / desktop background etc.

piInTheFace
Posts: 2
Joined: Sun Mar 05, 2017 3:53 pm

Re: New Open GL Driver, Bug report thread

Sun Mar 05, 2017 4:01 pm

Hi,

I have just tried to move to the openGL driver ( software I am building required openGL) I am running 1 pi3 headless and 2 with monitors.

After updating;the VNC client stops working and the 2 with screens become basically frozen even after reverting to the default driver . SSH still works on those but the headless one crashes with the following report after trying to revert back.

Code: Select all

Message from [email protected] at Mar  5 23:49:13 ...
 kernel:[   77.209335] Internal error: Oops: 5 [#1] SMP ARM

Message from [email protected] at Mar  5 23:49:13 ...
 kernel:[   77.307849] Process raspi-config (pid: 1148, stack limit = 0xaa43c210)

Message from [email protected] at Mar  5 23:49:13 ...
 kernel:[   77.314471] Stack: (0xaa43de68 to 0xaa43e000)

Message from [email protected] at Mar  5 23:49:13 ...
 kernel:[   77.318896] de60:                   b27dae00 b27dae18 aa43deb4 01200011 b26ee240 b26ee240

Message from [email protected] at Mar  5 23:49:13 ...
 kernel:[   77.327198] de80: 76fb5068 f76274f8 00000011 808d14c0 aa43deb4 aa43dea0 8018c75c 801490ac

Message from [email protected] at Mar  5 23:49:13 ...
 kernel:[   77.335502] dea0: 01200011 b9afd640 aa43df3c aa43deb8 800235bc 8018c738 80159b38 80175624

Message from [email protected] at Mar  5 23:49:13 ...
 kernel:[   77.343807] dec0: 00000020 aa43ded0 8016cfc4 00000001 a0000013 aa43df08 00000000 00000004

Message from [email protected] at Mar  5 23:49:13 ...
 kernel:[   77.352110] dee0: b8d0d300 b8d0d318 00000000 b9afd8a8 00000000 00000000 00000000 00000000

Message from [email protected] at Mar  5 23:49:13 ...
 kernel:[   77.360412] df00: f7627769 00000011 00000000 fffffff4 aa43df5c 76fb5068 01200011 76f38000

Message from [email protected] at Mar  5 23:49:13 ...
 kernel:[   77.368716] df20: 00000000 8000fd28 00000000 00000000 aa43df8c aa43df40 8002463c 80022e78

Message from [email protected] at Mar  5 23:49:13 ...
 kernel:[   77.377018] df40: 00000000 00000000 00000000 aa43c000 aa43df6c aa43df60 801758f0 801757f8

Message from [email protected] at Mar  5 23:49:13 ...
 kernel:[   77.385320] df60: aa43df94 76fb5068 7e9a4b38 76f38000 00000078 8000fd28 aa43c000 00000000

Message from [email protected] at Mar  5 23:49:13 ...
 kernel:[   77.393622] df80: aa43dfa4 aa43df90 80024aa0 800245d0 76fb5068 00000000 00000000 aa43dfa8

Message from [email protected] at Mar  5 23:49:13 ...
 kernel:[   77.401924] dfa0: 8000fb60 80024a78 76fb5068 7e9a4b38 01200011 00000000 00000000 00000000

Message from [email protected] at Mar  5 23:49:13 ...
 kernel:[   77.410227] dfc0: 76fb5068 7e9a4b38 76f38000 00000078 76fb5000 7e9a4ba8 0000047c 7e9a4b74

Message from [email protected] at Mar  5 23:49:13 ...
 kernel:[   77.418529] dfe0: 76fb54c0 7e9a4b38 0000047c 76e9a4ac 60000010 01200011 00000000 00000000

Message from [email protected] at Mar  5 23:49:13 ...
 kernel:[   77.465414] Code: e7905002 e3550000 0a00004c e5943014 (e795c003)

if there is anyway to fix this please post it.


Thank you

spl23
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 376
Joined: Fri Dec 26, 2014 11:02 am

Re: New Open GL Driver, Bug report thread

Sun Mar 05, 2017 7:54 pm

piInTheFace wrote: I have just tried to move to the openGL driver ( software I am building required openGL) I am running 1 pi3 headless and 2 with monitors.
I don't think the GL driver is likely to work headless at all, as it interacts directly with the screen buffer.

piInTheFace
Posts: 2
Joined: Sun Mar 05, 2017 3:53 pm

Re: New Open GL Driver, Bug report thread

Mon Mar 06, 2017 4:25 am

I don't think the GL driver is likely to work headless at all, as it interacts directly with the screen buffer.
Would you be able to explain why?
Is it an issue with the vnc server?
Is it an issue with the kernel/ or raspbian as a whole?

Also why would it also break the RPIs that are running with monitors?

User avatar
sconemad
Posts: 229
Joined: Thu Apr 28, 2016 1:47 pm
Location: Cambridge, UK
Contact: Website

Re: New Open GL Driver, Bug report thread

Mon Mar 06, 2017 9:54 am

If you're using the RealVNC server, then the "experimental direct capture mode" won't work if the GL driver is enabled.
It should work if you disable experimental direct capture, although it's been a while since I've tried this.

archdr01d
Posts: 1
Joined: Sat Mar 18, 2017 3:01 pm

Re: New Open GL Driver, Bug report thread

Sat Mar 18, 2017 3:26 pm

Hello,

I have the vc4-kms-v3d driver specified in config.txt.

I see the login prompt and command line console on the hdmi monitor, but when I try to run omxplayer, I see the text output of the program but no video.

Audio is working over hdmi, but no video.

I'm running: 4.4.45-1-ARCH #1 SMP Fri Jan 27 18:52:49 MST 2017 armv7l GNU/Linux

I've read of SD working, but no HD. So I tried a variety of 480p videos as well. Some show video details, but no video is displayed:

Code: Select all

[[email protected] ~]# omxplayer vhostVideo/Sakasama\ no\ Patema\ -\ 480p\ \[0B5CD640\].mkv 
Chapter :       0       00:00:00.000        0.00
Chapter :       1       00:07:46.883      466.00
Chapter :       2       00:13:11.541      791.00
Chapter :       3       00:21:30.789     1290.00
Chapter :       4       00:25:52.551     1552.00
Chapter :       5       00:32:02.129     1922.00
Chapter :       6       00:37:09.436     2229.00
Chapter :       7       00:44:14.527     2654.00
Chapter :       8       00:52:14.757     3134.00
Chapter :       9       00:56:54.953     3414.00
Chapter :       10      01:03:51.953     3831.00
Chapter :       11      01:11:01.174     4261.00
Chapter :       12      01:19:04.073     4744.00
Chapter :       13      01:25:03.265     5103.00
Chapter :       14      01:32:39.554     5559.00
Video codec omx-h264 width 848 height 480 profile 100 fps 23.976025
Audio codec aac channels 6 samplerate 48000 bitspersample 16
Subtitle count: 15, state: off, index: 1, delay: 0
I tried various --layer and --display options, it's always the same.

Is this a video format issue, or am I missing something in my configuration?

Thanks!

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5331
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: New Open GL Driver, Bug report thread

Sat Mar 18, 2017 8:45 pm

archdr01d wrote: I have the vc4-kms-v3d driver specified in config.txt.

I see the login prompt and command line console on the hdmi monitor, but when I try to run omxplayer, I see the text output of the program but no video.
Correct. vc4-kms-v3d will disable any gpu features that drive the display.
You can use the vc4-fkms-v3d overlay and then use "omxplayer --no-osd".

User avatar
ric96
Posts: 1253
Joined: Sun Mar 17, 2013 6:03 am
Location: NOIDA, India
Contact: Website

Re: New Open GL Driver, Bug report thread

Sat Mar 18, 2017 11:45 pm

So needed some clearance with the difference between the kms and fkms dtoverlay, and is it related to full kms and fake kms option recently introduced in the raspi-config?
My apologies for shameless YouTube Plugs...
youtube.com/sahajsarup
twitter @sahajsarup
skype srics1996
e-mail: [email protected]
Blog: http://www.geektillithertz.com/wordpress
Web: http://www.geektillithertz.com

wb9688
Posts: 3
Joined: Mon Dec 22, 2014 6:14 pm

Re: New Open GL Driver, Bug report thread

Sun Mar 19, 2017 8:08 am

When I enable it, only the rainbow screen is shown on a display connected to the 3.5mm jack output of my Raspberry Pi 3.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5331
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: New Open GL Driver, Bug report thread

Sun Mar 19, 2017 11:44 am

ric96 wrote:So needed some clearance with the difference between the kms and fkms dtoverlay, and is it related to full kms and fake kms option recently introduced in the raspi-config?
Did you you read the linked post? It describes the differences.
Yes, fkms is referred to as fake kms in raspi-config.

User avatar
ric96
Posts: 1253
Joined: Sun Mar 17, 2013 6:03 am
Location: NOIDA, India
Contact: Website

Re: New Open GL Driver, Bug report thread

Sun Mar 19, 2017 2:17 pm

dom wrote:
ric96 wrote:So needed some clearance with the difference between the kms and fkms dtoverlay, and is it related to full kms and fake kms option recently introduced in the raspi-config?
Did you you read the linked post? It describes the differences.
Yes, fkms is referred to as fake kms in raspi-config.
yup, just saw that, thanks for the clarification :D
My apologies for shameless YouTube Plugs...
youtube.com/sahajsarup
twitter @sahajsarup
skype srics1996
e-mail: [email protected]
Blog: http://www.geektillithertz.com/wordpress
Web: http://www.geektillithertz.com

User avatar
ric96
Posts: 1253
Joined: Sun Mar 17, 2013 6:03 am
Location: NOIDA, India
Contact: Website

Re: New Open GL Driver, Bug report thread

Sun Mar 19, 2017 2:27 pm

so just for clarification I can set resolution using framebuffer_width=x in config.txt if i am using fkms. But if I am using kms I will have to do it using xrandr.
My apologies for shameless YouTube Plugs...
youtube.com/sahajsarup
twitter @sahajsarup
skype srics1996
e-mail: [email protected]
Blog: http://www.geektillithertz.com/wordpress
Web: http://www.geektillithertz.com

nabilh2000
Posts: 1
Joined: Sat Jun 03, 2017 9:08 am

Re: New Open GL Driver, Bug report thread

Sat Jun 03, 2017 9:20 am

Ubuntu Mate on Raspb-pi 2 & 3 -

I will post a link to the dmesg.

- overscan works only with full OpenGL
- with full (or fake KMS) OpenGL, WiFi & / or BT iconon main toolbar panel unresponsive or disappear altogether.
- vlc with openmax-il allows to watch with full acceleration but only in full screen - with no access to menus - with no ability to exit - system becomes unresponsive when trying to exit, playing a video - will shut down if repatedly hitting ctrl-alt-del or ctrl-alt-esc
- in raspb-pi 3 system more stable with memory split 128
- in raspb-pi 2 system more stable with fake kms

It will be nice if vlc can give access to menus & exit option when playing a video, otherwise stuck until video ends.

cjc2
Posts: 1
Joined: Sat Jun 24, 2017 10:16 am

Re: New Open GL Driver, Bug report thread

Sat Jun 24, 2017 10:25 am

Hi,

I'm having some problems with the GL driver and the Pixel desktop. This is on a fresh install of the latest Raspbian Pixel image, on Pi 3, with HDMI to a TV. All I did after installing was disable overscan and enable the GL driver using raspi-config. (I had previously started from Raspbian Lite, installed raspberrypi-ui-mods, and launched the desktop with 'sudo systemctl start lightdm.service' - I thought I might have misconfigured something, so tried the Pixel image but have the same problem there.)
  • With the GL driver disabled, everything works normally (the system boots to the desktop and logs in automatically).
  • With GL (Full KMS) enabled, the Pi boots to the desktop, but all the icons on the menu bar at the top of the screen are missing (the bar is empty). When I installed on Raspbian Lite, the right-click menu on the desktop didn't work either, although in the Pixel image this works. The Pi hangs on reboot (through 'sudo reboot' over SSH, since the menu is missing) - first it sticks at 'started show plymouth reboot screen' for a few minutes, then the rest of the systemd messages appear up to 'stopped remount root and kernel file systems' after which it hangs altogether and never reboots.
  • With GL (Fake KMS) enabled, the menus are there, but the reboot problem still happens some of the time.
OpenGL itself seems to work (glxgears runs at 60 FPS, once installed). I couldn't see any obvious problems in .xsession-errors, the LXDE logs, or journalctl, but I'm not really sure what to look for - what information do you need to help debug this?

User avatar
rpiMike
Posts: 909
Joined: Fri Aug 10, 2012 12:38 pm
Location: Cumbria, UK

Re: New Open GL Driver, Bug report thread

Sat Jun 24, 2017 5:19 pm

cjc2 wrote:Hi,

I'm having some problems with the GL driver and the Pixel desktop. This is on a fresh install of the latest Raspbian Pixel image, on Pi 3, with HDMI to a TV. All I did after installing was disable overscan and enable the GL driver using raspi-config. (I had previously started from Raspbian Lite, installed raspberrypi-ui-mods, and launched the desktop with 'sudo systemctl start lightdm.service' - I thought I might have misconfigured something, so tried the Pixel image but have the same problem there.)
  • With the GL driver disabled, everything works normally (the system boots to the desktop and logs in automatically).
  • With GL (Full KMS) enabled, the Pi boots to the desktop, but all the icons on the menu bar at the top of the screen are missing (the bar is empty). When I installed on Raspbian Lite, the right-click menu on the desktop didn't work either, although in the Pixel image this works. The Pi hangs on reboot (through 'sudo reboot' over SSH, since the menu is missing) - first it sticks at 'started show plymouth reboot screen' for a few minutes, then the rest of the systemd messages appear up to 'stopped remount root and kernel file systems' after which it hangs altogether and never reboots.
  • With GL (Fake KMS) enabled, the menus are there, but the reboot problem still happens some of the time.
OpenGL itself seems to work (glxgears runs at 60 FPS, once installed). I couldn't see any obvious problems in .xsession-errors, the LXDE logs, or journalctl, but I'm not really sure what to look for - what information do you need to help debug this?
I'm seeing the same Open GL Full issue with missing menu bar icons.

User avatar
rpiMike
Posts: 909
Joined: Fri Aug 10, 2012 12:38 pm
Location: Cumbria, UK

Re: New Open GL Driver, Bug report thread

Wed Jun 28, 2017 8:11 am

After latest 'sudo apt-get update' and 'sudo apt-get upgrade' (28/06/17) the menu icons have re-appeared with OpenGL enabled. However using 'omxplayer example.mp3' the sound is now corrupted. Disabling OpenGL and the sound plays ok.

WhosChaosTK
Posts: 2
Joined: Sat Jul 08, 2017 12:18 am

Re: New Open GL Driver, Bug report thread

Mon Jul 10, 2017 5:34 pm

When I enable it (to play minecrft) for some reason it does the same thing like other people said sometimes it boots to a black screen, but when it does boot up audio is weird, the speaker on my pi top stopped working and if i use a bluetooth speaker it cuts out after like a min or 2. It is kinda annoying because I want to use my pi top for a lot of thing and i kinda need audio :lol: :lol: :lol:



I really hope this gets fixed! :!: :!: :!: :!: :!:

alexdev
Posts: 17
Joined: Sat Dec 30, 2017 10:33 am

Re: New Open GL Driver, Bug report thread

Sun Jan 14, 2018 10:07 am

On my Raspberry Pi 3 it works fine, except the fact that I get some white dots in the left side of the screen if the background is black. e.g: terminal window on the left side of the screen . Is this a common problem? On other CRT TV with Composite i get the same white dots, so it's not because of the TV.

Also I have found that if, for example, I open a white window the wallpaper changes its brightness a bit. This happens with the taskbar if I maximize the window.

User avatar
manuti
Posts: 21
Joined: Mon Jan 09, 2012 1:52 pm
Location: Spain
Contact: Website Twitter

Re: New Open GL Driver, Bug report thread

Tue Jan 08, 2019 10:44 am

rpiMike wrote:
Wed Jun 28, 2017 8:11 am
After latest 'sudo apt-get update' and 'sudo apt-get upgrade' (28/06/17) the menu icons have re-appeared with OpenGL enabled. However using 'omxplayer example.mp3' the sound is now corrupted. Disabling OpenGL and the sound plays ok.
Same problem here! omxplayer crashes, VLC not playing anything and audio stutter in games, mp3, everything.
Raspberry para torpeshttp:/raspberryparatorpes.net

dominic03
Posts: 81
Joined: Fri Dec 21, 2018 1:50 am

Re: New Open GL Driver, Bug report thread

Tue Jan 08, 2019 12:38 pm

It seems pixel doubling is not supported with the new GL drivers.
My setup:
Raspberry Pi 3b+ running Raspbian Buster, firmware date July 9 2019 (via PINN)
Kingston 32 GB class 10 (U1) SDHC card
Lexar 16GB flash drive for backups
pi-top 3 with drivers and pi-topHUB 2.0

Chris_G_Miller
Posts: 23
Joined: Sat Nov 14, 2015 3:45 pm
Location: Kent, England

Re: New Open GL Driver, Bug report thread

Fri Jun 14, 2019 9:33 pm

I have a DSI-attached non-official display which works fine with vc4-kms-v3d when in normal landscape mode.
However, if I switch to vc4-fkms-v3d I get no display at all.
If I try to rotate the display using xrandr, occasionally it works, but more often than not the DSI signals stop, and therefore my screen disappears.

I have the feeling that when one runs xrandr, some kind of temporary 'disable' is sent down the stack, and the vc4 driver stops the DSI - but then it never gets restarted.

1) I think vc4-fkms-v3d ought to work if the -kms- version does
2) Is anybody else managing to use either of those overlays with a rotated display? I need portrait...

With thanks

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5331
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: New Open GL Driver, Bug report thread

Sat Jun 15, 2019 2:14 pm

Chris_G_Miller wrote:
Fri Jun 14, 2019 9:33 pm
I have a DSI-attached non-official display which works fine with vc4-kms-v3d when in normal landscape mode.
However, if I switch to vc4-fkms-v3d I get no display at all.
fkms means firmware drives the display. Only official display are supported by firmware.
kms is the only option for non-official displays.

Return to “General discussion”