Guest4 | hello. I got the security upgrade on multipath-tools (for CVE-2022-41973) | 07:21 |
---|---|---|
debdog | Leeloo Dallas M U L T I P A S S ! | 07:21 |
Guest4 | however, after rebooting, /run/shm is still mounted. per https://www.debian.org/lts/security/2022/dla-3250 , I am meant to change it /run/multipath-tools | 07:22 |
Guest4 | how do I do that? | 07:22 |
Guest4 | (also, there's no /run/multipath-tools in df's output, I feel lost) | 07:24 |
Guest4 | it appears the directory is set on file /etc/mtab, but I'm scared of changing it (out of my scope of knowledge) | 07:31 |
Guest4 | on farther inspection, it appears the package of systemd for tmpfiles is not installed (and did not get fetched) with the upgrade: systemd-standalone-tmpfiles/stable-backports 252.5-2~bpo11+1 amd64 | 07:51 |
Guest4 | standalone tmpfiles binary for use in non-systemd systems | 07:51 |
Guest4 | I will assume that devuan is not affected and not change anything | 07:51 |
Guest4 | (it still bugs me that the notice for the upgrade went through, maybe it is affected. I will let it be for now. I hope sharing this contributes to something) | 07:56 |
Guest4 | thank you all. have a nice day or night | 07:56 |
ham5urg | A libinput list-devices shows for devices a "Failed to open /dev/input/event16 (Permission denied)" from 0 to 20. Is this the cause that no touch nor pen works on my laptop? | 14:23 |
ham5urg | It's funny, the pen works at the login-prompt of GDM (Gnome) but not after Gnome takes over. | 14:35 |
ham5urg | I added the user to the input group and "libinput list-devices" does work now but the Gnome-Desktop does not accept pen or finger. | 14:38 |
ham5urg | As I use testing, maybe this is the problem | 14:58 |
celsius | Hello to all, | 18:20 |
celsius | I ask your kind help: | 18:20 |
celsius | I migrated from debian sid to devuan unstable via live-minimal (I had grub2 with dual boot debian windows 7). The migration happened successfully but when I boot into grub2 there is no windows 7 entry. I uninstalled and reinstalled grub2 but the result does not change. I note that both update-grub2, os-prober, grub-mkconfig -or /boot/grub/grub.cfg find windosws 7, also in the file /boot/grub/grub.cfg is normally the menuentry for windows | 18:20 |
celsius | 7. | 18:20 |
celsius | Note: "GRUB_DISABLE_OS_PROBER=false" in the /etc/default/grub file already uncomment. | 18:20 |
celsius | How can I fix it? | 18:20 |
celsius | Thanks in advance | 18:20 |
gnarface | celsius: i'm not clear on how the live image was needed for this. did you finish the upgrade with "apt-get dist-upgrade" ? | 18:23 |
gnarface | make sure you did "dist-upgrade" instead of just "upgrade" to make sure it completed fully | 18:24 |
gnarface | if that doesn't help, see what happens if you go to the grub console by hitting "e" to edit a menu entry and actually just type the windows7 entry in manually, to see if it works. | 18:24 |
gnarface | need to narrow down some possibilities here | 18:25 |
gnarface | since it's unstable, there's every possibility the software is just broken, but since it's recently upgraded there's plenty of other potential failure cases too | 18:26 |
celsius | gnarface, yes | 18:36 |
celsius | It's all ok, but grub not showing windows 7 at boot .... | 18:42 |
celsius | I repeat, but in n the file /boot/grub/grub.cfg is normally the menuentry for windows 7, strange .... | 18:42 |
gnarface | celsius: yea, that is weird, but maybe something is wrong with the format of the entry that the newer grub version doesn't like or something like that. try typing the entry directly into grub like i said to see if it works. | 18:43 |
gnarface | celsius: you should be able to hit "e" from somewhere on the grub screen during boot to get into a console | 18:44 |
celsius | gnarface: Yes, if at boot pressing "e", and in the grub I write all the code of the "menuentry" then win7 is displayed and I can start win7, strange .... | 18:49 |
gnarface | (or is it c? i | 18:49 |
gnarface | (or is it c? i'm pretty sure it was e) | 18:49 |
gnarface | celsius: alright, well that's good progress. maybe the parsing error is before it in the grub.cfg. that's an auto-generated file now, you should try moving it out of the way and regenerating it (don't delete it, move it to your home directory or something so you have a backup just in case) | 18:50 |
celsius | Done ok | 18:52 |
gnarface | celsius: when you regenerate it, does the win7 entry still show up in the regenerated copy? | 18:52 |
gnarface | i would diff it against the backup copy to see what changed, if anything | 18:53 |
celsius | gnarface: yes Win7 is regenerated in the file | 18:57 |
celsius | gnarface: The files are the same | 19:02 |
gnarface | identical, really? | 19:02 |
gnarface | weird | 19:02 |
gnarface | celsius: are any of the other entries in the grub.cfg missing from the menu when you boot, or just that win7 one? | 19:03 |
celsius | gnarface: only win7 | 19:06 |
celsius | Always windoz "breaking the balls" .....:-D | 19:12 |
gnarface | celsius: seems like there must be some disconnect between the current grub version and the current thing that's generating the config | 19:17 |
gnarface | celsius: did you check to see if there's anything in debian's bug tracker about this? | 19:17 |
gnarface | (these aren't devuan-forked packages in this case; this software is directly from debian unaltered) | 19:18 |
celsius | gnarface: I don't find nothing | 19:22 |
onefang | Maybe try rEFInd instead of grub? | 19:29 |
gnarface | celsius: maybe lilo? | 19:29 |
gnarface | celsius: do you have grub installed on the MBR or a partition? | 19:29 |
gnarface | celsius: is it possible you have multiple grub instances chained together? | 19:29 |
gnarface | like maybe an old one on the MBR that's chainloading one on your root partition and obscuring a fault? | 19:30 |
celsius | gnarface: I installed grub on the MBR | 19:34 |
gnarface | celsius: uh, just a quick sanity check though, you checked in the submenu of the grub screen right? there's like an advanced/other section now | 19:37 |
gnarface | maybe the win7 entry is actually there but just not in the same location | 19:37 |
celsius | gnarface: I have the /boot on a separate partition (/dev/sda5) | 19:37 |
gnarface | celsius: shouldn't matter to windows, i don't think | 19:39 |
gnarface | certainly shouldn't be interfering with this anyway | 19:39 |
gnarface | anyone else here dual-booting with windows and unstable and seen the windows entry go missing recently? | 19:40 |
luis__ | Hello guys, I have a very small problem. When booting the computer, it starts logging some stuff (which contains errors but we'll look into that after). At this point, and also while in grub, the graphics driver hasn't started, so the resolution is low and the image sucks. Is there a way to start the graphics driver earlier? | 20:10 |
gnarface | luis__: yes, but depending on your hardware and driver combo it might break things later | 20:11 |
gnarface | which gpu brand and (if AMD or Nvidia) which driver? | 20:11 |
luis__ | actually, I have a problem irl, I'll be back sorry | 20:12 |
gnarface | we'll be here | 20:12 |
_ds_ | “while in grub” – too soon for any Linux driver modules | 20:17 |
gnarface | _ds_: well, i didn't mention the part about the technical inaccuracy about the diagnosis. it's clear what they really meant was the resolution setting, which can be altered, but not always without consequence | 20:18 |
celsius | gnarface: as I told you when editing grub at boot it had neither menuentry nor submenu containing win7, so win7 is completely absent, but there is the classic menuentry and submenu of devuan. | 20:53 |
gnarface | celsius: yea, just making sure they hadn't moved it somewhere off the top level | 20:56 |
gnarface | sounds like you've hit a bug, really, but i'd stick around to see if anyone around here has a second opinion | 20:57 |
gnarface | fsmithred: do you happen to know anything about recent changes to grub's menu display logic? got a user here whose win7 entry has gone missing from grub but not the grub.cfg file (and yes, regenerating the grub.cfg has been tried) | 20:58 |
luis__ | I'm back. GPU is AMD 6600 XT | 21:00 |
luis__ | Graphics: | 21:00 |
luis__ | Device-1: AMD Navi 23 vendor: Micro-Star MSI driver: amdgpu v: kernel | 21:00 |
luis__ | bus ID: 2f:00.0 chip ID: 1002:73ff class ID: 0300 | 21:00 |
luis__ | Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu | 21:00 |
luis__ | unloaded: fbdev,modesetting,vesa alternate: ati | 21:00 |
luis__ | resolution: 2560x1440~144Hz s-dpi: 96 | 21:00 |
luis__ | OpenGL: renderer: AMD DIMGREY_CAVEFISH (DRM 3.48.0 6.0.0-0.deb11.6-amd64 | 21:00 |
luis__ | LLVM 11.0.1) | 21:00 |
luis__ | v: 4.6 Mesa 20.3.5 direct render: Yes | 21:01 |
luis__ | _ds_, yes but there might be some workaround | 21:01 |
gnarface | luis__: check your /etc/default/grub file, look for this line and make sure it's not commented: GRUB_GFXPAYLOAD_LINUX="keep" then make sure "nomodeset" isn't present in GRUB_CMDLINE_LINUX | 21:03 |
gnarface | luis__: you might also need the firmware-amd-graphics package for this, if you don't already have it | 21:04 |
fsmithred | gnarface, afaik you just set os-prober in /etc/default/grub so that it runs when you update-grub. | 21:04 |
gnarface | fsmithred: yea, that's been verified to work, and the entry gets put into grub.cfg correctly, but it still doesn't show up in the grub menu at boot time. as a sanity check, i had the user actually manually type it into the grub prompt as it appears in the grub.cfg, and it booted right, so i'm strongly suspecting this is a issue with grub's menu parsing/display logic | 21:05 |
gnarface | fsmithred: but since it's unstable i'm not sure there's much that can be done other than wait or file a bug upstream with debian | 21:05 |
gnarface | luis__: fyi, the firmware-amd-graphics package used to be in non-free but as of current testing it has been moved to a new section called non-free-firmware | 21:06 |
fsmithred | is there another linux install in this box? | 21:06 |
fsmithred | and did update-grub make any visible changes in the menu? (is it the right one?) | 21:07 |
gnarface | fsmithred: uh, i didn't ask. i did ask to make sure there was no other grub install and the user said no though. this system was upgraded from debian recently | 21:07 |
gnarface | celsius: can you weigh in on this here? i'm not sure the answer | 21:07 |
gnarface | celsius: do you just have devuan and win7 on this box or are there other linux installs too? | 21:08 |
gnarface | celsius: (fsmithered here knows his stuff) | 21:08 |
celsius | gnarface: devuan and win7 only | 21:10 |
gnarface | fsmithred: ^ | 21:10 |
luis__ | gnarface, thanks | 21:17 |
luis__ | fsmithred, what did you mean | 21:17 |
gnarface | luis__: no problem, but to be clear, fsmithred was talking about celsius's issue | 21:17 |
luis__ | oh okay | 21:18 |
gnarface | luis__: (we're tracking two grub issues at once here, i know it can get confusing) | 21:18 |
luis__ | yes | 21:19 |
luis__ | I don't have the two lines you meant | 21:19 |
luis__ | I have GRUB_CMDLINE_LINUX but it's empty | 21:19 |
gnarface | luis__: alright, try just adding GRUB_GFXPAYLOAD_LINUX="keep" on its own line after GRUB_CMDLINE_LINUX, but i'm not sure how long ago that was added; if your grub is very old it might not work | 21:21 |
gnarface | luis__: if that still doesn't work, you might have to actually set the resolution specifically in the GRUB_CMDLINE_LINUX | 21:22 |
luis__ | the heck, I can't check grub version with apt | 21:24 |
gnarface | luis__: like this: dpkg -l |grep grub | 21:25 |
luis__ | 2.06 | 21:25 |
gnarface | oh, that's not old at all | 21:26 |
gnarface | you must just not have been merging the stock /etc/default/grub changes during updates | 21:26 |
celsius | also update-grub2 not given error indications but everything ok, it’s all very strange ... | 21:26 |
celsius | I checked the various logs but I found nothing inherent .... | 21:31 |
luis_ | grub is still ugly | 21:32 |
gnarface | luis_: see what happens if you just add something like GRUB_GFXMODE="1920x1080x32" after GRUB_CMDLINE_LINUX (make the numbers match your display resolution and color depth) | 21:35 |
luis_ | grub tells to run vbeinfo but I can't run that | 21:37 |
gnarface | if luis_ comes back tell them it's in the package called vbetool | 21:40 |
luis_ | ok now it's got a good resolution, but there's still a screen flickering when logging stuff, probably because that's when the driver is loaded | 21:44 |
gnarface | luis_: just fyi, vbeinfo is in the vbetool package, but you can get the same info by adding "vga=ask" to GRUB_CMDLINE_LINUX | 21:49 |
gnarface | luis_: what did you change to fix it by the way? you just disconnected after "grub tells to run vbeinfo but I can't run that" | 21:50 |
luis_ | I set the resolution and update-grub | 21:52 |
gnarface | with GRUB_GFXMODE? | 21:53 |
luis_ | yes | 21:55 |
luis_ | that worked | 21:55 |
gnarface | cool | 21:56 |
gnarface | my guess is the issue is that your GPU is just so new | 21:56 |
gnarface | in a fair world it should auto-detect | 21:56 |
luis_ | maybe something is not up to date? | 22:00 |
luis_ | and what about the driver starting at a weird time? | 22:00 |
gnarface | there's not much other than grub to be up-to-date at that phase in boot up. you got the firmware-amd-graphics package, right? | 22:02 |
luis_ | yes, version 20210818 | 22:04 |
luis_ | should I upgrade to sid? | 22:05 |
luis_ | OH NO | 22:05 |
luis_ | I only added non-free, and not non-free-firmward, apt isn't seeing the bookworm version, brb gonna try that | 22:06 |
gnarface | wait | 22:06 |
gnarface | are you on testing right now or stable? | 22:06 |
luis_ | stable + backports | 22:06 |
luis_ | seems like non-free-firmware doens't exist.. | 22:07 |
gnarface | it doesn't exist until testing | 22:07 |
gnarface | but you should make sure your kernel and that firmware-amd-graphics package both came from backports | 22:08 |
gnarface | also any mesa or xorg packages | 22:08 |
gnarface | though there might not be any | 22:08 |
luis_ | I don't know, from backports I installed linux kernel, firmware-amd-graphics and xserver-xorg-video-amdgpu | 22:09 |
gnarface | run this real quick: apt-cache -t chimaera-backports search mesa | 22:11 |
luis_ | how do i add devuan non-free-firmware | 22:11 |
luis_ | there are results, what should I look for? | 22:12 |
gnarface | non-free-firmware i think is only in testing and unstable right now, i don't think it's relevant to this | 22:12 |
luis_ | It's just to install a more recent version of the firmware | 22:12 |
gnarface | you don't want to mix releases, it's a bad idea | 22:13 |
luis_ | yes | 22:13 |
gnarface | about the results; install any mesa packages from that backports search that also show up in the output of "dpkg -l |grep mesa" | 22:13 |
gnarface | (you probably actually want to install all of them but i can't be sure you're actually gonna use all of them) | 22:14 |
luis_ | actually, I'll just upgrade all the packages from the backports | 22:14 |
luis_ | is that a bad idea? | 22:14 |
gnarface | i would say it's probably a bad idea | 22:15 |
gnarface | some people do it, but it's caused me problems in the past | 22:15 |
luis_ | yolo | 22:15 |
gnarface | the software in backports isn't as well tested against itself | 22:15 |
luis_ | Yeah | 22:15 |
luis_ | This is just a test run anyway, to set up config and stuff, I'll reinstall it again later | 22:15 |
gnarface | usually you only want to install stuff that solves specific problems for you | 22:15 |
_ds_ | I don't see any Mesa packages in backports. | 22:16 |
gnarface | really??? | 22:16 |
gnarface | uh, luis_ maybe we should see your sources.list | 22:17 |
luis_ | what's the site to paste again? | 22:17 |
gnarface | paste.debian.net | 22:17 |
_ds_ | (I have chimaera-backports in my sources.list, and regardless I would expect to see it in Debian via rmadison if it were there.) | 22:18 |
luis_ | http://paste.debian.net/1272748/ | 22:18 |
luis_ | something wrong with my sources? | 22:21 |
gnarface | luis_: only two things weird i see about it, though i can't be sure either of them are actually causing issues; you have pkgmaster.devuan.org in one case when you should have deb.devuan.org for all lines, and you forgot to also include " contrib non-free" for the chimaera-updates lines | 22:21 |
_ds_ | I think that Mesa 20.3 should work with Navi 2x… I'd be interested in seeing output from “glxinfo -B” (glxinfo is in mesa-utils). | 22:22 |
luis_ | gnarface, I didn't touch the lines about chimaera-security | 22:23 |
onefang | pkgmaster should not be used, since it's the master that the other mirrors sync from, and we want to keep it's traffic down. | 22:23 |
gnarface | _ds_: the issue is actually just about the system virtual terminal flickering though i think | 22:23 |
gnarface | _ds_: i was just trying to pedantically cover everything graphically related to be sure | 22:23 |
luis_ | should I replace pkgmaster? | 22:23 |
luis_ | That's the system default | 22:24 |
gnarface | luis_: yes, replace it, but like i said that's not related | 22:24 |
gnarface | it's not gonna fix the flickering | 22:24 |
luis_ | yes | 22:24 |
luis_ | brb | 22:24 |
luis_ | back | 22:26 |
luis_ | it's not fixed | 22:26 |
gnarface | what type of flickering are you actually seeing? is it irregular flickering or does it just seem like low refresh rate? | 22:27 |
luis_ | It's not a flickering, it's what I presume the graphics driver loading, the screen only goes black for a second and comes back, but it's hard to read the logs and it messes the text a bit | 22:27 |
_ds_ | Hmm. Loading amdgpu (and the corresponding framebuffer console driver) will cause the display to be blanked briefly. | 22:28 |
luis_ | I believe that's it | 22:28 |
gnarface | yea, you might actually be describing expected behavior. grub hands off to the kernel at a certain point, it might blink out once while changing display handling. | 22:29 |
luis_ | I would like that to not mess the screen if possible | 22:29 |
_ds_ | $ cat /sys/class/graphics/fb0/name | 22:29 |
luis_ | ok it's not that important to be honest | 22:29 |
gnarface | you can make it inherit resolution from grub and you can override the font it uses (you will actually see it change fonts once after the hand-over in most cases) | 22:29 |
_ds_ | (will probably be amdgpudrmfb) | 22:29 |
luis_ | _ds_, that's it | 22:29 |
luis_ | well then, I'll just give up on that one | 22:30 |
gnarface | luis_: sorry, i actually thought you were having a display refresh rate issue | 22:30 |
luis_ | no, although the resolution does go back to a smaller one for a few seconds | 22:30 |
gnarface | luis_: those lines you're missing should still be in the output of "dmesg" shortly after boot | 22:30 |
gnarface | there's a package to make it log them to /var/log but i forget what it's named | 22:31 |
gnarface | boot something | 22:31 |
luis_ | nvm that, it's already in dmesg so it's fine | 22:31 |
luis_ | why does it go back to a smaller res for a few secs? Can I change that? | 22:32 |
gnarface | did you have GRUB_GFXPAYLOAD_LINUX="keep" in your /etc/default/grub still? | 22:32 |
gnarface | it's supposed to default to whatever grub used | 22:32 |
_ds_ | If it's only doing that lower-res display during Linux kernel startup (i.e. penguins displayed), it's nothing to worry about. | 22:32 |
gnarface | but independently of that the fonts might change; make sure you're not confusing a font change for a resolution change | 22:33 |
luis_ | I have no penguins | 22:33 |
luis_ | gnarface, font size changes | 22:33 |
luis_ | and it's pixelated | 22:33 |
luis_ | I do have that line | 22:33 |
gnarface | luis_: they removed the penguins from the stock debian kernel builds. you'll have to recompile to get them back, sadly. | 22:33 |
luis_ | :'( | 22:34 |
_ds_ | Boot message logging: bootlogd | 22:34 |
gnarface | ah, thanks _ds_ | 22:34 |
_ds_ | ⇒ /var/log/boot | 22:34 |
_ds_ | gnarface, no penguins? Not good… | 22:34 |
_ds_ | (custom kernels here, so I still have them) | 22:35 |
luis_ | Leaving, I'll try more tomorrow | 22:35 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!