Yet again, I have just reinstalled Mageia 7 (full reinstall.)
The bugs
were accumulating. Somehow, after the reinstall, I finished up with two successive versions of dkms-nvidia installed, but that was easy to fix.
The default DM for a fresh install of Mageia 7 or 8 is lightdm. My new system's graphics were so slow that the display was unusable. So, I went hunting. A post on "Ask Ubuntu" suggested that the problem was
"probably a lightdm bug." Sure enough, switching to SDDM cured the
problem. There were other suggestions. See
Using teapot for Frames Per Second yielded ~60 FPS with Help screen enabled.
Added "vblank_mode=0 glxsphere" to kernel boot line. Result snippet
$ teapot
Frame rate: 893.000000
Frame rate: 889.000000
Frame rate: 886.000000
What and where is teapot
On 2020-09-17, Bit Twister <BitTwister@mouse-potato.com> wrote:
...
Using teapot for Frames Per Second yielded ~60 FPS with Help screen enabled.
Added "vblank_mode=0 glxsphere" to kernel boot line. Result snippet
$ teapot
Frame rate: 893.000000
Frame rate: 889.000000
Frame rate: 886.000000
On 2020-09-17, William Unruh <unruh@invalid.ca> wrote:
What and where is teapot
google was of no help but I finally found it using urpmf teapot|grep bin
It is in mesa-demos.
On 2020-09-17, Bit Twister <BitTwister@mouse-potato.com> wrote:
...
Using teapot for Frames Per Second yielded ~60 FPS with Help screen enabled.
Added "vblank_mode=0 glxsphere" to kernel boot line. Result snippet
What do those kernel options do?
And what can their side effects be?
What is glxsphere?
On Thu, 17 Sep 2020 16:39:43 -0000 (UTC), William Unruh wrote:noresume mitigations=off vblank_mode=0 glxspheres "
On 2020-09-17, William Unruh <unruh@invalid.ca> wrote:
What and where is teapot
google was of no help but I finally found it using urpmf teapot|grep bin
It is in mesa-demos.
On 2020-09-17, Bit Twister <BitTwister@mouse-potato.com> wrote:
...
Using teapot for Frames Per Second yielded ~60 FPS with Help screen enabled.
Added "vblank_mode=0 glxsphere" to kernel boot line. Result snippet
What do those kernel options do?
no idea.
And what can their side effects be?
Other than a message is the journal, none that I know of, that assumes
"side effects" means an undesired result.
What is glxsphere?
A poor mouse click/drag, should have been glxspheres.
$ grep glxsphere /etc/default/grub
GRUB_CMDLINE_LINUX="ipv6.disable=1 audit=0 splash=off plymouth.enable=0
On 2020-09-17, Bit Twister <BitTwister@mouse-potato.com> wrote:
Strange. I found glxspheres and it is a program.like teapot except the picture does not change with framerate, whereas teapot goes faster and
faster the hight the frame rate. Both print out the framerate
You can also try out vblank_mode=0 by making it an environment variable export vblank_mode=0
Doing that and running teaport, I get 1700 fps while it is 60
(presumably the vertical blanking rate of the monitor) without that.
The disadvantage may be tearing in the video apparently. I am still not
clear why you would want to run glxspheres from the kernel.
So you could also try putting
export vblank_mode=0
into your .bash_profile file
Easier to do and remove than putting it into the kernel boot stanza
On 2020-09-17, Bit Twister <BitTwister@mouse-potato.com> wrote:
$ grep glxsphere /etc/default/grub
GRUB_CMDLINE_LINUX="ipv6.disable=1 audit=0 splash=off plymouth.enable=0 noresume mitigations=off vblank_mode=0 glxspheres "
Strange. I found glxspheres and it is a program.like teapot except the picture does not change with framerate, whereas teapot goes faster and
faster the hight the frame rate. Both print out the framerate
You can also try out vblank_mode=0 by making it an environment variable export vblank_mode=0 So you could also try putting
export vblank_mode=0 into your .bash_profile file
Doing that and running teaport, I get 1700 fps while it is 60
(presumably the vertical blanking rate of the monitor) without that.
The disadvantage may be tearing in the video apparently.
I am still not
clear why you would want to run glxspheres from the kernel.
Oops that was glxgears that I ran.
On Thu, 17 Sep 2020 16:39:43 -0000 (UTC), William Unruh wrote:
Added "vblank_mode=0 glxsphere" to kernel boot line. Result snippet
What do those kernel options do?
no idea.
Yet again, I have just reinstalled Mageia 7 (full reinstall.) The bugs were accumulating. Somehow, after the reinstall, I finished up with two successive versions of dkms-nvidia installed, but that was easy to fix.
The default DM for a fresh install of Mageia 7 or 8 is lightdm. My new system's graphics were so slow that the display was unusable. So, I went hunting. A post on "Ask Ubuntu" suggested that the problem was
"probably a lightdm bug." Sure enough, switching to SDDM cured the problem. There were other suggestions. See
https://www.askubuntu.com/questions/1230620/
But that answer is dated 2014, and I have had no problem before today. I have my fingers crossed.
On 9/17/20 1:19 PM, Bit Twister wrote:
On Thu, 17 Sep 2020 16:39:43 -0000 (UTC), William Unruh wrote:
Fascinating. You surprise me, Bit. Applying a command/option when youAdded "vblank_mode=0 glxsphere" to kernel boot line. Result snippet
What do those kernel options do?
no idea.
have no idea what it does.
Isn't that the kind of thing that usually gets newbies in trouble?
On Fri, 18 Sep 2020 07:31:57 -0400, TJ wrote:
On 9/17/20 1:19 PM, Bit Twister wrote:
On Thu, 17 Sep 2020 16:39:43 -0000 (UTC), William Unruh wrote:Fascinating. You surprise me, Bit. Applying a command/option when you
Added "vblank_mode=0 glxsphere" to kernel boot line. Result snippet
What do those kernel options do?
no idea.
have no idea what it does.
Not necessary the same thing, knowing/doing. :)
I do not need to know what it does/how if it works.
Isn't that the kind of thing that usually gets newbies in trouble?
Kinda true, but I used the grub command line editor to test first and
found no problems. Options found while lurking in other groups, or just running across it during googling research.
vblank_mode=0 was given in the mageia dev mail list years ago.
Main newbie problem is when they do not know how to un-scramble their
eggs that were scrambled when experimenting.
Kernel command line options/arguments are a pain the run down. Args
might be used by kernel, or just passed along to other programs.
vblank_mode=0 was given in the mageia dev mail list years ago.
On Fri, 18 Sep 2020 09:02:27 -0400, Bit Twister<BitTwister@mouse-potato.com> wrote:
vblank_mode=0 was given in the mageia dev mail list years ago.
The option vblank_mode is not a kernel option. It's a mesa option.
A description of it's impact on mesa is available at https://www.reddit.com/r/linuxquestions/comments/4ua5tk/vblank_mode_setting/
I set environment variables I want to be system wide in /etc/rc.d/rc.local
Or does the kernel simply ignore commands it does not understand?
On Fri, 18 Sep 2020 10:01:14 -0400, David W. Hodgins wrote:
I set environment variables I want to be system wide in /etc/rc.d/rc.local
I would not have expected variables set in any of those files to show up
in user space.
Global file/locations for that are /etc/login.defs, /etc/environment, /etc/profile, /etc/profile.d/, /etc/bashrc /etc/bash.bashrc.
for a mageia install.
I am ignoring DM/DE startup files for this point in the conversation.
The Mageia 8 alpha 2 torrent is not working.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 69:45:48 |
| Calls: | 6,655 |
| Calls today: | 1 |
| Files: | 12,200 |
| Messages: | 5,332,101 |
| Posted today: | 1 |