| targz | Thanks for adding the option to donate in crypto and that it is also in different, it's great! :) | 00:44 |
|---|---|---|
| targz | From Latin America it is a very necessary option if you want to donate to this type of projects. | 00:44 |
| hightower2 | Mm.. I installed Devuan daedalus successfully on Intel NUC 13 Extreme Kit NUC13RNGi9. Works like a charm. | 01:10 |
| hightower2 | Graphics is UHD 770, that's a i915 driver. I only have one visible graphics glitch in the video editor kdenlive, where the timeline below the video/movie window doesn't show. The same issue exists on Debian, even on 6.2-rc5 kernel. | 01:11 |
| gnarface | does it generate any relevant errors about it that you can find? | 01:15 |
| gnarface | also, i believe there may be at least two drivers that can support that hardware, and the default one may not be the best for all cases | 01:17 |
| gnarface | if you didn't specify in a xorg.conf or xorg.conf.d snippet file, it's probably actually using the modesetting driver rather than the intel driver | 01:19 |
| gnarface | a release or two ago, Intel themselves started recommending the modesetting driver over their own driver as a default, and Debian upstream adopted that default, but I've observed that on some hardware, in some cases, the intel driver does actually work better | 01:20 |
| hightower2 | mm, but I see i915 in lsmod.. I thought it was used for sure | 01:22 |
| gnarface | basically what i've surmised is that the modesetting driver was preferred because it does a better job of auto-detecting optimal display resolution both at the framebuffer console and inside xorg, but some hardware features on certain models might still be better supported by the intel driver | 01:22 |
| gnarface | check the Xorg.0.log to be sure what driver it's actually using | 01:23 |
| hightower2 | lemme check | 01:23 |
| gnarface | i don't think just the kernel having detected and loaded i915 means anything special with regards to Xorg | 01:23 |
| hightower2 | spot on, it's modesetting used | 01:24 |
| hightower2 | can I force i915 without writing xorg.conf ? | 01:24 |
| gnarface | no but you don't have to use a whole xorg.conf anymore, you can just use a partial one | 01:24 |
| hightower2 | or well, intel driver I mean | 01:24 |
| gnarface | yea it's "intel" | 01:24 |
| gnarface | it might not give you any better luck, or it might work for this then fail at something else, but as an exercise to evaluate the behavioral differences it's worthwhile | 01:26 |
| gnarface | "modesetting" is just some generic driver to replace the old default fallbacks of svga or framebuffer or whatever they used to fall back on | 01:27 |
| hightower2 | umm... hm same thing unfortunately | 01:32 |
| hightower2 | quite strange | 01:32 |
| gnarface | you checked the Xorg log to make sure it actually loaded the intel driver? | 01:33 |
| onefang | Is the kdenlive window just too big, so the bottom part is below where your monitor ends? | 01:33 |
| onefang | So maybe just resizing the window might help? | 01:34 |
| gnarface | if it did load the intel driver but the rendering error didn't change, then it could actually a mesa issue | 01:34 |
| gnarface | or something specific to kde's compositor | 01:35 |
| hightower2 | yes definitely checked the log, previously it said driver "modesetting", now it says driver "intel". Also it didn't want to start until I got xorg.conf right, confirming that it's seeing/honoring the setting | 01:35 |
| hightower2 | the kdenlive's timeline is below the video, which is around the middle of the screen, not at the very bottom, so surely not missing part of the image | 01:35 |
| hightower2 | See this screenshot (from someone else): | 01:35 |
| hightower2 | https://kdenlive.org/wp-content/uploads/2022/01/photo_2021-12-13_15-36-56-980x551.jpg | 01:36 |
| hightower2 | Notice the small marks just below both video windows | 01:36 |
| hightower2 | (the one on the right is more noticeable since it has a blue line all across) | 01:36 |
| hightower2 | in my case the player buttons (start, stop, rewind etc.) that are below that show fine, but the particular timeline (the thing between the video above and play controls below) does not | 01:37 |
| onefang | Odd that it's something missing in the middle of the window. | 01:38 |
| onefang | I'm on Chimeara, with a backported RT kernel, kdenlive looks OK here, but I have AMD graphics. | 01:39 |
| hightower2 | ok, thanks for feedback | 01:41 |
| hightower2 | but also the modesetting/intel thing was awesome, I never realized | 01:42 |
| gnarface | i would file a bug for this upstream at debian | 01:43 |
| gnarface | leave out the part about how you found it on devuan :-p | 01:44 |
| gnarface | if necessary they'll kick it further upstream to kdenlive themselves | 01:45 |
| hightower2 | I tested on debian too, same thing :) | 01:46 |
| gnarface | yea, you mentioned that, and that's good, so we know it's not a systemd issue | 01:46 |
| hightower2 | hehe :) | 01:46 |
| gnarface | but debian's policy is to register bugs with debian | 01:46 |
| gnarface | and to leave it to them to kick it further upstream if necessary | 01:47 |
| gnarface | the policy here is to only register bugs that aren't in debian | 01:47 |
| hightower2 | sure, sure | 01:48 |
| hightower2 | ok, might do that eventually, thanks | 01:49 |
| Necrodiver | i have a question, i am trying to find the crash logs for my pc, are they in changelog? How do i output the the details of it? | 12:18 |
| djph | they'd _probably_ be in /var/log/syslog | 13:11 |
| djph | or well the syslog that's dated about the time of the crash | 13:11 |
| Necrodiver | ah | 13:11 |
| Necrodiver | thats right, someone told me that recently but i forgot where it is | 13:12 |
| djph | could also be in the dmesg logfile (again,the one dated around the time of the crash) | 13:12 |
| Necrodiver | what should i do to output the information? | 13:13 |
| debdog | dmesg does output the kernel ringbuffer which is also stored in /var/log/syslog, I thought? | 13:17 |
| Necrodiver | i just dont know what the proper command is | 13:18 |
| hagbard | For dmesg use the command "dmesg". For /var/log/syslog you can use cat, or less. | 13:20 |
| Necrodiver | ah okay thanks | 13:20 |
| MetaYan | During a daedalus upgrade I got 'dpkg: error processing package ca-certificates-java (--configure): triggers looping, abandoned'. More in https://termbin.com/idhw . Anything to worry about? | 14:05 |
| hagbard | MetaYan: You could try to configure the package again by: dpkg --configure -a | 14:19 |
| fsmithred | MetaYan, on daedalus upgrade yesterday I got a bug warning for dpkg, so I instlalled the version from ceres before doing the upgrade. | 14:32 |
| MetaYan | hagbard: fsmithred: Thanks, 'dpkg --configure -a' worked. | 20:10 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
