libera/#devuan/ Thursday, 2023-03-02

Guest4hello. I got the security upgrade on multipath-tools (for CVE-2022-41973)07:21
debdogLeeloo Dallas   M U L T I P A S S !07:21
Guest4however, 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-tools07:22
Guest4how do I do that?07:22
Guest4(also, there's no /run/multipath-tools in df's output, I feel lost)07:24
Guest4it appears the directory is set on file /etc/mtab, but I'm scared of changing it (out of my scope of knowledge)07:31
Guest4on 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 amd6407:51
Guest4  standalone tmpfiles binary for use in non-systemd systems07:51
Guest4I will assume that devuan is not affected and not change anything07: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
Guest4thank you all. have a nice day or night07:56
ham5urgA 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
ham5urgIt's funny, the pen works at the login-prompt of GDM (Gnome) but not after Gnome takes over.14:35
ham5urgI 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
ham5urgAs I use testing, maybe this is the problem14:58
celsiusHello to all,18:20
celsiusI ask your kind help:18:20
celsiusI 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 windows18:20
celsius 7.18:20
celsiusNote: "GRUB_DISABLE_OS_PROBER=false" in the /etc/default/grub file already uncomment.18:20
celsiusHow can I fix it?18:20
celsiusThanks in advance18:20
gnarfacecelsius: 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
gnarfacemake sure you did "dist-upgrade" instead of just "upgrade" to make sure it completed fully18:24
gnarfaceif 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
gnarfaceneed to narrow down some possibilities here18:25
gnarfacesince 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 too18:26
celsiusgnarface, yes18:36
celsiusIt's all ok, but grub not showing windows 7 at boot ....18:42
celsiusI repeat, but in n the file /boot/grub/grub.cfg is normally the menuentry for windows 7, strange ....18:42
gnarfacecelsius: 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
gnarfacecelsius: you should be able to hit "e" from somewhere on the grub screen during boot to get into a console18:44
celsiusgnarface: 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? i18:49
gnarface(or is it c? i'm pretty sure it was e)18:49
gnarfacecelsius: 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
celsiusDone ok18:52
gnarfacecelsius: when you regenerate it, does the win7 entry still show up in the regenerated copy?18:52
gnarfacei would diff it against the backup copy to see what changed, if anything18:53
celsiusgnarface: yes Win7 is regenerated in the file18:57
celsiusgnarface: The files are the same19:02
gnarfaceidentical, really?19:02
gnarfaceweird19:02
gnarfacecelsius: are any of the other entries in the grub.cfg missing from the menu when you boot, or just that win7 one?19:03
celsiusgnarface: only win719:06
celsiusAlways windoz "breaking  the balls" .....:-D19:12
gnarfacecelsius: seems like there must be some disconnect between the current grub version and the current thing that's generating the config19:17
gnarfacecelsius: 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
celsiusgnarface: I don't find nothing19:22
onefangMaybe try rEFInd instead of grub?19:29
gnarfacecelsius: maybe lilo?19:29
gnarfacecelsius: do you have grub installed on the MBR or a partition?19:29
gnarfacecelsius: is it possible you have multiple grub instances chained together?19:29
gnarfacelike maybe an old one on the MBR that's chainloading one on your root partition and obscuring a fault?19:30
celsiusgnarface:  I installed grub on the MBR19:34
gnarfacecelsius: uh, just a quick sanity check though, you checked in the submenu of the grub screen right? there's like an advanced/other section now19:37
gnarfacemaybe the win7 entry is actually there but just not in the same location19:37
celsiusgnarface: I have the /boot on a separate partition (/dev/sda5)19:37
gnarfacecelsius: shouldn't matter to windows, i don't think19:39
gnarfacecertainly shouldn't be interfering with this anyway19:39
gnarfaceanyone 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
gnarfaceluis__: yes, but depending on your hardware and driver combo it might break things later20:11
gnarfacewhich gpu brand and (if AMD or Nvidia) which driver?20:11
luis__actually, I have a problem irl, I'll be back sorry20:12
gnarfacewe'll be here20:12
_ds_“while in grub” – too soon for any Linux driver modules20: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 consequence20:18
celsiusgnarface: 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
gnarfacecelsius: yea, just making sure they hadn't moved it somewhere off the top level20:56
gnarfacesounds like you've hit a bug, really, but i'd stick around to see if anyone around here has a second opinion20:57
gnarfacefsmithred: 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 XT21:00
luis__Graphics:21:00
luis__  Device-1: AMD Navi 23 vendor: Micro-Star MSI driver: amdgpu v: kernel21:00
luis__  bus ID: 2f:00.0 chip ID: 1002:73ff class ID: 030021:00
luis__  Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu21:00
luis__  unloaded: fbdev,modesetting,vesa alternate: ati21:00
luis__  resolution: 2560x1440~144Hz s-dpi: 9621:00
luis__  OpenGL: renderer: AMD DIMGREY_CAVEFISH (DRM 3.48.0 6.0.0-0.deb11.6-amd6421:00
luis__  LLVM 11.0.1)21:00
luis__  v: 4.6 Mesa 20.3.5 direct render: Yes21:01
luis___ds_, yes but there might be some workaround21:01
gnarfaceluis__: 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_LINUX21:03
gnarfaceluis__: you might also need the firmware-amd-graphics package for this, if you don't already have it21:04
fsmithredgnarface, afaik you just set os-prober in /etc/default/grub so that it runs when you update-grub.21:04
gnarfacefsmithred: 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 logic21:05
gnarfacefsmithred: 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 debian21:05
gnarfaceluis__: 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-firmware21:06
fsmithredis there another linux install in this box?21:06
fsmithredand did update-grub make any visible changes in the menu? (is it the right one?)21:07
gnarfacefsmithred: 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 recently21:07
gnarfacecelsius: can you weigh in on this here? i'm not sure the answer21:07
gnarfacecelsius: do you just have devuan and win7 on this box or are there other linux installs too?21:08
gnarfacecelsius: (fsmithered here knows his stuff)21:08
celsiusgnarface: devuan and win7 only21:10
gnarfacefsmithred: ^21:10
luis__gnarface, thanks21:17
luis__fsmithred, what did you mean21:17
gnarfaceluis__: no problem, but to be clear, fsmithred was talking about celsius's issue21:17
luis__oh okay21:18
gnarfaceluis__: (we're tracking two grub issues at once here, i know it can get confusing)21:18
luis__yes21:19
luis__I don't have the two lines you meant21:19
luis__I have GRUB_CMDLINE_LINUX but it's empty21:19
gnarfaceluis__: 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 work21:21
gnarfaceluis__: if that still doesn't work, you might have to actually set the resolution specifically in the GRUB_CMDLINE_LINUX21:22
luis__the heck, I can't check grub version with apt21:24
gnarfaceluis__: like this: dpkg -l |grep grub21:25
luis__2.0621:25
gnarfaceoh, that's not old at all21:26
gnarfaceyou must just not have been merging the stock /etc/default/grub changes during updates21:26
celsiusalso update-grub2 not given error indications but everything ok, it’s all very strange ...21:26
celsiusI checked the various logs but I found nothing inherent ....21:31
luis_grub is still ugly21:32
gnarfaceluis_: 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 that21:37
gnarfaceif luis_ comes back tell them it's in the package called vbetool21: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 loaded21:44
gnarfaceluis_: just fyi, vbeinfo is in the vbetool package, but you can get the same info by adding "vga=ask" to GRUB_CMDLINE_LINUX21:49
gnarfaceluis_: 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-grub21:52
gnarfacewith GRUB_GFXMODE?21:53
luis_yes21:55
luis_that worked21:55
gnarfacecool21:56
gnarfacemy guess is the issue is that your GPU is just so new21:56
gnarfacein a fair world it should auto-detect21:56
luis_maybe something is not up to date?22:00
luis_and what about the driver starting at a weird time?22:00
gnarfacethere'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 2021081822:04
luis_should I upgrade to sid?22:05
luis_OH NO22:05
luis_I only added non-free, and not non-free-firmward, apt isn't seeing the bookworm version, brb gonna try that22:06
gnarfacewait22:06
gnarfaceare you on testing right now or stable?22:06
luis_stable + backports22:06
luis_seems like non-free-firmware doens't exist..22:07
gnarfaceit doesn't exist until testing22:07
gnarfacebut you should make sure your kernel and that firmware-amd-graphics package both came from backports22:08
gnarfacealso any mesa or xorg packages22:08
gnarfacethough there might not be any22:08
luis_I don't know, from backports I installed linux kernel, firmware-amd-graphics and xserver-xorg-video-amdgpu22:09
gnarfacerun this real quick: apt-cache -t chimaera-backports search mesa22:11
luis_how do i add devuan non-free-firmware22:11
luis_there are results, what should I look for?22:12
gnarfacenon-free-firmware i think is only in testing and unstable right now, i don't think it's relevant to this22:12
luis_It's just to install a more recent version of the firmware22:12
gnarfaceyou don't want to mix releases, it's a bad idea22:13
luis_yes22:13
gnarfaceabout 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 backports22:14
luis_is that a bad idea?22:14
gnarfacei would say it's probably a bad idea22:15
gnarfacesome people do it, but it's caused me problems in the past22:15
luis_yolo22:15
gnarfacethe software in backports isn't as well tested against itself22:15
luis_Yeah22:15
luis_This is just a test run anyway, to set up config and stuff, I'll reinstall it again later22:15
gnarfaceusually you only want to install stuff that solves specific problems for you22:15
_ds_I don't see any Mesa packages in backports.22:16
gnarfacereally???22:16
gnarfaceuh, luis_ maybe we should see your sources.list22:17
luis_what's the site to paste again?22:17
gnarfacepaste.debian.net22: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
gnarfaceluis_: 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 lines22: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-security22:23
onefangpkgmaster 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 think22:23
gnarface_ds_: i was just trying to pedantically cover everything graphically related to be sure22:23
luis_should I replace pkgmaster?22:23
luis_That's the system default22:24
gnarfaceluis_: yes, replace it, but like i said that's not related22:24
gnarfaceit's not gonna fix the flickering22:24
luis_yes22:24
luis_brb22:24
luis_back22:26
luis_it's not fixed22:26
gnarfacewhat 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 bit22: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 it22:28
gnarfaceyea, 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 possible22:29
_ds_$ cat /sys/class/graphics/fb0/name22:29
luis_ok it's not that important to be honest22:29
gnarfaceyou 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 it22:29
luis_well then, I'll just give up on that one22:30
gnarfaceluis_: sorry, i actually thought you were having a display refresh rate issue22:30
luis_no, although the resolution does go back to a smaller one for a few seconds22:30
gnarfaceluis_: those lines you're missing should still be in the output of "dmesg" shortly after boot22:30
gnarfacethere's a package to make it log them to /var/log but i forget what it's named22:31
gnarfaceboot something22:31
luis_nvm that, it's already in dmesg so it's fine22:31
luis_why does it go back to a smaller res for a few secs? Can I change that?22:32
gnarfacedid you have GRUB_GFXPAYLOAD_LINUX="keep" in your /etc/default/grub still?22:32
gnarfaceit's supposed to default to whatever grub used22: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
gnarfacebut independently of that the fonts might change; make sure you're not confusing a font change for a resolution change22:33
luis_I have no penguins22:33
luis_gnarface, font size changes22:33
luis_and it's pixelated22:33
luis_I do have that line22:33
gnarfaceluis_: 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: bootlogd22:34
gnarfaceah, thanks _ds_22:34
_ds_⇒ /var/log/boot22: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 tomorrow22:35

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!