.....
Failed to start adjustment method randr
....
I guess we found now why it's not working for you, probably it has to do with your hardware (combined with FossaPup).
Unfortunately I have no idea how to solve, maybe others do.
Moderator: Forum moderators
.....
Failed to start adjustment method randr
....
I guess we found now why it's not working for you, probably it has to do with your hardware (combined with FossaPup).
Unfortunately I have no idea how to solve, maybe others do.
in fossa redshift is preinstalled, so any terminal will (should) find it in /usr/bin etc or the normal places which executables are placed.. or path.
when you have an executable in a place where one would not normally run it from, like your downloads folder, preceding the command with a ./ will let it run, but the terminal will have to be 'in' the same folder.
rshift* is shorthand for rshift-portable-64. it could even be r* if nothing else starting with the letter r was in that folder. * is a wildcard
hopefully we can see some terminal output when run in slacko821 and see what your monitor works with
Slacko64-8.2.1 has a bug where screenshots don't work, so cell phone pic.
@williwaw , Launching it from CLI in terminal worked after trying a few things. Moving the slider didn't make any output.
last line in photo of it running in terminal looks like what it did for me, then
when I right click on the icon and "stop redshift" a line is added to the terminal output, in my case "using method 'randr'"
?
ASUS VA27EHE 27” Eye Care Monitor Full HD (1920 x 1080) IPS 75Hz Adaptive-Sync HDMI D-Sub Frameless
It's a new monitor, delivered in May. I looked it up in my shopping history.
@williwaw thanks. It says:
Code: Select all
Using method 'randr'
bigpup asks in the other thread?
What hardware is providing the graphics to the monitor??
Good question.
I am running out of ideas, but perhaps there are newer versions of the required drivers in 821? 75 hz?
slightly off topic, but at this point, what bugs in slacko64-821 do you find, that might be easier to trouble shoot, than debugging the monitor in pups where it does not work?
In Slacko64-8.2.1: Screenshot doesn't work, but that's been reported. I just found out that the screenshot not working bug, also affects that login hindrance where you have to move a puzzle piece into position to log in. That's really hard to do when you see colored lines instead of the image.
Gparted can't make a fat32 boot partition without a warning flag. Someone also found that.
I can't think of any others right now.
@williwaw I can only answer that question with the same question I asked there:
___ , how do I find the answer to that on sys-info or terminal or something? A friend told me I have some kind of graphics card, I don't know what it is.
From what I have read, you dont seem to have a problem with your graphics card so much as perhaps you need a newer version of the driver? the one that is in 821?
the slacko thread has been quiet, but.......
so hopefully 8.2.2 will address some of your other concerns if you cant patch slacko7 with a the 821 driver for your monitor
you might try looking at the output of
Code: Select all
# grep "LoadModule" /var/log/Xorg.0.log
from 821.
if you find something like nvidia, or the graphics card in question, the line should be identified by a time stamp
then try
Code: Select all
# less /var/log/Xorg.0.log
less will let you scroll through the file to locate the timestamp, and you should find more about the module a few lines below.
hopefully someone more familiar with xorg will see this and offer some insight, alternately you could start a new thread about identifying video drivers or modules as they are more properly called in Linux, seeing how we are moving away from a redshift issue with this discussion.
@williwaw , is that the useful part of the lines? It's quite a few lines, copy and paste still doesn't work in Slacko 8.2.1, and I'm too new to know exactly what I'm looking at.
we need to id your your gpu, and I am not sure what graphical utility is in slacko821 to see that
pup-sysinfo or hardinfo perhaps in the "system" submenu?
EDIT: this from the other thread....
and ->the video-info report? or you could run # lspci | grep -E "VGA"
say for instance it points to "amdgpu" (just a guess on my part) ,then the amdgpu @ 20.581 (from running grep "LoadModule" /var/log/Xorg.0.log), can direct you towards some additional driver info possibly the version number. It may be a few lines below the 20.581 time stamp in the log.
you can also attach a copy of /var/log/Xorg.0.log to your post rather than copy and paste.
just curious, is copy and paste broken in everything or just the terminal? both middle clicking and ctrl-c &ctrl-v
@williwaw Here's the pup-sys-info:
▶—— Video ——◀
Display Specifications:
• Monitor VertRefresh: 60.00 times/s
• Screen Dimensions: 1280x720 pixels (337x190 millimeters)
• Screen Depth: 24 bits (planes)Xorg Startup Log (/var/log/Xorg.0.log):
• Xorg Driver in use: amdgpu
• Loaded Modules: ati dbe dri2 fb fbdevhw glamoregl glx kbd mouse ramdac
• X.Org version: 1.20.11OpenGL 2D/3D Rendering:
• Direct Rendering: Yes
• Vendor: AMD
• Renderer: AMD Radeon RX 6800 (SIENNA_CICHLID, DRM 3.40.0, 5.10.0, LLVM 12.0.0)
• Version: 4.6 (Compatibility Profile) Mesa 21.1.1VGA controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1002:73bf] (rev c3)
• Kernel Driver: amdgpu
• Memory Used by Driver: 4648.00 KB
• Path: /lib/modules/5.10.0/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko
• Description: AMD GPU
• Video RAM: 16384M total, 256M 2M prefetchable
Code: Select all
~$ lspci | grep -E "VGA"
0c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] (rev c3)
~$
Code: Select all
~$ grep "LoadModule" /var/log/Xorg.0.log
[ 19.204] (II) LoadModule: "dbe"
[ 19.204] (II) LoadModule: "glx"
[ 19.205] (II) LoadModule: "amdgpu"
[ 19.206] (II) LoadModule: "ati"
[ 19.273] (II) LoadModule: "radeon"
[ 19.274] (II) LoadModule: "modesetting"
[ 19.275] (II) LoadModule: "fbdev"
[ 19.275] (II) LoadModule: "vesa"
[ 19.275] (II) LoadModule: "mouse"
[ 19.275] (II) LoadModule: "kbd"
[ 19.290] (II) LoadModule: "fbdevhw"
[ 19.290] (II) LoadModule: "fb"
[ 19.291] (II) LoadModule: "dri2"
[ 19.401] (II) LoadModule: "glamoregl"
[ 19.419] (II) LoadModule: "ramdac"
~$
Attached is /var/log/Xorg.0.log
If there are any commands I missed or mistyped, could you please write them on single lines? I'm still new enough to be a little confused where commands begin and end when they're part of a paragraph.
from pupsys-info I see "amdgpu"
from the output of grep I see a timestamp of 19.205 by that driver
and in the log at 19.205. I see
Code: Select all
[ 19.205] (II) LoadModule: "amdgpu"
[ 19.205] (II) Loading /usr/lib64/xorg/modules/drivers/amdgpu_drv.so
[ 19.206] (II) Module amdgpu: vendor="X.Org Foundation"
[ 19.206] compiled for 1.20.10, module version = 19.1.0
[ 19.206] Module class: X.Org Video Driver
If you look in /usr/lib64/xorg/modules/drivers/ you will find amdgpu_drv.so but it has no version number in the filename, The version is indicated 2 lines below "compiled for (Xorg)1.20.10, module version = 19.1.0"
It may be possible to replace the amdgpu driver in another puppy with the amdgpu (version 19.1.0) you take from slacko8.2.1, but as for what is the best practice for doing it, I am not the right guy to ask. I would recommend you open a new topic in the user section should you wish to proceed further.