[SOLVED] mageia-prime at mageia 7 beta2

This forum is dedicated to testing early releases and cauldron : Howtos, tips, tricks and user global feedback and thoughts...

Helpful tip :
For bugs tracking we use : https://bugs.mageia.org = The Mageia Bug Tracker
In this bug tracker you'll find already reported bugs and you'll be able to report those you have found....

[SOLVED] mageia-prime at mageia 7 beta2

Postby adhefe » Mar 16th, '19, 23:46

I've installed mageia-prime at mageia 7 beta2. During installation, required packages were also installed: dkms-nvidia, kernel-devel, etc.

Now, the output of,

$ /sbin/lsmod|grep nvidia

returns,

Code: Select all
nvidia_drm             49152  6
nvidia_modeset       1089536  13 nvidia_drm
nvidia              17629184  628 nvidia_modeset
ipmi_msghandler        61440  2 ipmi_devintf,nvidia
drm_kms_helper        196608  2 nvidia_drm,i915
drm                   475136  10 drm_kms_helper,nvidia_drm,i915


but, the output of,

$ glxinfo -i

returns,

Code: Select all
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  150 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  38
  Current serial number in output stream:  39


Did I miss any configuring step? Doesn't mageia-prime do everything required?

Thanks
Last edited by adhefe on Mar 19th, '19, 01:42, edited 1 time in total.
adhefe
 
Posts: 188
Joined: Mar 11th, '19, 02:08

Re: mageia-prime at mageia 7 beta2

Postby doktor5000 » Mar 18th, '19, 09:39

What do you get with
Code: Select all
DRI_PRIME=1 glxinfo
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17630
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: mageia-prime at mageia 7 beta2

Postby adhefe » Mar 18th, '19, 15:42

The outcome of

$ DRI_PRIME=1 glxinfo

is in the attachment

Thanks
Attachments
DRI_PRIME-1-glxinfo.txt
DRI_PRIME=1 glxinfo
(57.22 KiB) Downloaded 141 times
adhefe
 
Posts: 188
Joined: Mar 11th, '19, 02:08

Re: mageia-prime at mageia 7 beta2

Postby ITA84 » Mar 18th, '19, 16:13

adhefe wrote:but, the output of,

$ glxinfo -i

returns,

Code: Select all
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  150 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  38
  Current serial number in output stream:  39



Does running the plain glxinfo command (without -i) give the same error? If it doesn't, maybe GLX indirect rendering is disabled (which should be fine unless you specifically need it in place of direct rendering).
ITA84
 
Posts: 199
Joined: Mar 5th, '13, 18:15

Re: mageia-prime at mageia 7 beta2

Postby adhefe » Mar 18th, '19, 16:22

The plain glxinfo returns a list of messages as big as this one. To answer If It is the same list, I need to makes a diff..
adhefe
 
Posts: 188
Joined: Mar 11th, '19, 02:08

Re: mageia-prime at mageia 7 beta2

Postby adhefe » Mar 18th, '19, 16:25

They differ by a single line,

51c51
< Currently available dedicated video memory: 3829 MB
---
> Currently available dedicated video memory: 3851 MB
adhefe
 
Posts: 188
Joined: Mar 11th, '19, 02:08

Re: mageia-prime at mageia 7 beta2

Postby ITA84 » Mar 18th, '19, 17:04

I suppose indirect rendering is disabled then. But this also means the same card is used with DRI_PRIME=1 as normally. Is the output different if you run
Code: Select all
DRI_PRIME=0 glxinfo

?
ITA84
 
Posts: 199
Joined: Mar 5th, '13, 18:15

Re: mageia-prime at mageia 7 beta2

Postby adhefe » Mar 18th, '19, 18:20

DRI_PRIME=0 glxinfo

differ from

DRI_PRIME=1 glxinfo

by this line only,

51c51
< Currently available dedicated video memory: 3813 MB
---
> Currently available dedicated video memory: 3851 MB
adhefe
 
Posts: 188
Joined: Mar 11th, '19, 02:08

Re: mageia-prime at mageia 7 beta2

Postby ITA84 » Mar 18th, '19, 18:43

I don't have an NVidia card, but with my AMD card (hybrid Intel/AMD system) I can use the integrated Intel graphics by default and the discrete AMD card with DRI_PRIME=1. Judging by your outputs I'd say the discrete NVidia card is used in both cases for your system instead (unless with NVidia it works differently and glxinfo always outputs the same config); that aside, there doesn't seem to be any other problem
ITA84
 
Posts: 199
Joined: Mar 5th, '13, 18:15

Re: mageia-prime at mageia 7 beta2

Postby adhefe » Mar 18th, '19, 18:58

I would be surprised if nvidia is being used by default. I had hard times to be able to install, and then to boot, mageia 7 beta2 in this laptop. Nvidia is not connected to the screen support, all graphics are with intel.
adhefe
 
Posts: 188
Joined: Mar 11th, '19, 02:08

Re: mageia-prime at mageia 7 beta2

Postby adhefe » Mar 18th, '19, 21:10

I don't really think nvidia is controlling the graphics. Anyway, everything seems really good here. I've installed virtualgl package to use,

$ glxspheres64

and it returned,

Code: Select all
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
Visual ID of window: 0x9d
Context is Direct
OpenGL Renderer: GeForce GTX 1050 Ti/PCIe/SSE2


where it is explicitly said that rendering is being made by nvidia card!

Many thanks
adhefe
 
Posts: 188
Joined: Mar 11th, '19, 02:08

Re: mageia-prime at mageia 7 beta2

Postby adhefe » Mar 18th, '19, 21:38

I've tested going back to intel's gpu's with

$ mageia-prime-uninstall -z

I was told to reboot to get the new configuration. But upon rebooting I got a message/warning that I'm trying my best to translate to english:

"It was detected an exibition kernel module loaded an it is in conflict with X driver server set to be in use, initialization of X server may fail now" [OK]

well, it did not failed but some fonts in icons and konsoles were somewhat bigger.

I came back to nvidia's gpus with,

$ mageia-prime-install -z

and everything looked fine again.

Is it a documented feature? Isn't it because nvidia was still loaded during boot even when it was not set to handle rendering?

Thanks
adhefe
 
Posts: 188
Joined: Mar 11th, '19, 02:08

Re: mageia-prime at mageia 7 beta2

Postby adhefe » Mar 19th, '19, 01:38

Found the proper message in english:

Code: Select all
"Detected  loaded display driver kernel module which conflicts with the driver the X server is configured to use. Startup of the X server may now fail."

It is quoted here,

https://bugs.mageia.org/show_bug.cgi?id=24436#c28

in an apparently totally different scope.

Maybe, I'd better post this font change problem in another post.

Thanks again
adhefe
 
Posts: 188
Joined: Mar 11th, '19, 02:08


Return to Testing : Alpha, Beta, RC and Cauldron

Who is online

Users browsing this forum: No registered users and 1 guest