libera/#devuan/ Friday, 2024-08-30

freaxeh"ACPI Error: AE_NOT_FOUND, while resolving a named reference package element"11:00
freaxehany hints?11:00
djphUsually either a bios in need of update; or ignorable (although "something" with ACPI won't work)11:04
freaxehright11:04
gnarfacefreaxeh: yea, bios issue... i thought i remember there was some way to insert the missing data into acpi directly, but you would also have to locate the missing data somehow. in a fair world, it'd be fixable with a bios update, though usually it won't be ever fixed and often it's completely unimportant11:30
buZzoften you can spoof 'the OS' to acpi too12:12
buZzmanufacturers dont really test the 'linux' acpi often12:12
freaxehthats good that its a non issue because the bios is 14 years old and came out in 2010 and its the latest bios for this motherboard :D13:52
buZzhehe, well , many ACPI tables in bios are jsut faulty ;)14:13
buZzits often not a big deal if you get such ACPI errors14:14
buZzor are you actually having issues, beside 'there is a message' ?14:14
freaxehnope no issues just the message, I am the voice of the kernel!14:15
freaxehnot really...14:16
buZzits safe to ignore ;)14:16
freaxehyep :)14:16
drdozerHI - I just updated my devuan and the nvidia driver failed to compile.16:53
drdozerIt is apparently a now-fixed source incompattibility between the kernel version and driver source16:54
drdozerbut I can't see how to encourage apt to use a newer version of the driver :(16:54
drdozerI am on daedolas and using the nvidia driver PPA16:55
drdozerdeb https://ppa.launchpadcontent.net/graphics-drivers/ppa/ubuntu/ noble main16:55
drdozerLinux taiwaif 6.9.7+bpo-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.9.7-1~bpo12+1 (2024-07-03) x86_64 GNU/Linux16:56
drdozerI'm not sure what I should try -- I could perhaps stop the kernel updating to 6.10.*?16:59
gnarfacedrdozer: you should absolutely never have mixed ubuntu packages into your install17:01
drdozergnarface, ok -- I can remove that ppa and update17:02
gnarfacemaybe17:02
gnarfaceyou might have a mess on your hands17:02
gnarfacethe current stable devuan versions had that problem recently too, but i think it's been fixed17:03
gnarfacewhich version of devuan are you using? daedalus?17:03
drdozeryes17:03
drdozerI think a fix for this has been pushed to debian, but not to devuan17:04
gnarfaceshouldn't be any difference17:04
drdozerIt is this issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=107784117:05
gnarfacethe problem is, ubuntu's versions are higher, so the package manager will think you're already up-to-date, so you might have to manually downgrade packages or remove them first17:05
gnarfaceyea, that's not the stable kernel either. looks like you're also using a backports kernel? did you get that kernel from the ubuntu backports or the debian backports?17:06
gnarfacethere are devuan backports repos you should use17:06
gnarface(only if you need them)17:06
drdozerMy apt sources list is:17:07
drdozerdeb http://mirrors.dotsrc.org/devuan/merged daedalus main non-free-firmware non-free contrib17:07
drdozerdeb http://mirrors.dotsrc.org/devuan/merged daedalus-updates main non-free contrib17:07
drdozerdeb http://mirrors.dotsrc.org/devuan/merged daedalus-security main non-free contrib17:07
drdozerdeb http://mirrors.dotsrc.org/devuan/merged daedalus-backports main non-free contrib17:07
gnarfaceah, that's also an issue17:07
gnarfacei'm pretty sure you need "non-free-firmware" on all lines17:07
drdozerI have added non-free-firmware and tried again17:09
gnarfacebut for it not to ignore the daedalus-backports line, you might also have to add "-t daedalus-backports" to your apt-get command-line17:09
gnarfaceor apt-cache17:09
gnarfacetry: apt-cache -t daedalus-backports search ^nvidia17:09
gnarfaceor: apt-cache -t daedalus-backports search nvidia17:09
gnarfacealso: apt-cache -t daedalus-backports search linux-image17:10
gnarface(make sure you ran "apt-get update" once after changing your sources.list)17:10
drdozershould I see a difference with and without the -t daedalus-backports?17:11
gnarfaceuh... i think so?17:11
gnarfacelemme make sure that's a official mirror...17:11
gnarfacehmm, yes, appears to be17:12
drdozerdiffing the nvidia searches says they are identical17:12
gnarfacethe difference would just be in version numbers17:12
gnarfacewhat version to you see?17:12
drdozerthe linux-image searches are different17:13
gnarfaceaah, hmm... maybe there are no backports nvidia drivers right at the moment then17:13
gnarfaceit doesn't always happen right away17:13
gnarfaceusually you're better off not having them though17:13
drdozerunderstood17:14
gnarfacedid you have a particular reason to go up beyond the daedalus version other than the build error?17:14
gnarfacebecause it should be fixed by now but that unfortunately means downgrading a bunch of stuff, which can be a pain in the ass...17:14
drdozerjust the build error -- I now have a half-built 6.10 kernel which worries me a bit17:15
gnarfaceif 6.10 has a similar issue that's probably easiest avoided by just going back to the current stable kernel, which should be 6.1.0 something17:15
gnarfaceyou didn't have a reason to upgrade to 6.10 did you?17:16
gnarfaceif you did, at least use the devuan-backports one instead of the ubuntu one17:16
gnarfacebut it seems like it's not ready for nvidia yet17:16
drdozer6.9 works fine -- it failed when trying to build the nvidia driver against 6.1017:16
gnarfaceyea, that's bad news17:16
gnarfacecurrent stable should be 6.1.0-something17:17
gnarfacei think17:17
drdozeryeah, the internet says 6.1.*17:17
gnarfacebut that one should work fine with the current stable nvidia driver versions, which should be 535.183.01-1~deb12u117:17
drdozeris there a magic incantation to tell apt to roll back the kernel version?17:18
gnarfaceit might not have actually even uninstalled the last one17:18
gnarfaceyou might just be able to reboot and select it at the grub prompt17:19
gnarfacedpkg -l |grep linux-image17:19
gnarfaceshould show you which ones are installed17:19
gnarfaceassuming the right one is still there, just reboot to it, then uninstall the 6.10 one17:19
gnarface(then re-run "update-grub" to flush it out of your boot menu)17:20
gnarfacedon't forget your corresponding linux-headers-* packages17:21
drdozerit is indeed still there - so can I just do "apt remove linux-image-6.10.6-1~bpo12+1" and cross my fingers?17:22
gnarfaceuh, don't do it while you're running it. reboot to the old one first17:22
gnarfacethen no finger-crossing should be necessary17:22
drdozerI'm booted into 6.9 as the update never fully completed17:22
gnarfaceare you sure? that's what "uname -a" says?17:22
drdozerLinux taiwaif 6.9.7+bpo-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.9.7-1~bpo12+1 (2024-07-03) x86_64 GNU/Linux17:23
gnarfacealright, if that one is working for you then i can't argue with it17:23
drdozerAh, it looks like the package is calling itself linux-image-amd64, which is uselessly generic17:23
gnarfaceso that's not an actual kernel, that's just a meta-package that always refers to the current stable one17:25
gnarfaceif you have it installed, a regular "apt-get upgrade" will always pull in the newest kernel stable kernel, but note that it's still older than the 6.9 backports one you're using, so that will be irrelevant17:26
drdozerfigured it out: sudo apt remove linux-image-6.10.6+bpo-amd6417:26
gnarfaceoh, sorry, forgot to tell you the important part17:27
drdozerupdate-grub has done the right thing, and not added an entry for 6.10, so I think I'm good to go17:29
drdozerunless there's something else17:29
gnarfacenothing important that i can think of. only other thing is, don't forget to remove linux-headers-6.10.6+bpo-amd64 and linux-headers-6.10.6+bpo-common too17:30
gnarfacebut they should be harmless, merely wasting some disk space17:30
gnarfaceand make sure "dpkg -l |grep nvidia" turns up a list of all the same versions for the ones that are formatted like 5**.***.**-...17:31
drdozergreat, and an autoremove has got rid of some other junk17:31
gnarface(one of the big pitfalls of using the nvidia drivers is accidentally mixing adjacent versions, which sometimes even mostly works, but mostly working is the worst type of working, usually)17:32
drdozeryeah, apparently I'm 53517:32
drdozerthanks - you're a life saver17:32
gnarfacesome of them have weird serial number or datestamp versions, you can't really do much but make sure they're the latest, but where it's bad is if for example you have a few 565.** or whatever ones mixed in with the 535.** ones17:33
gnarfaceno problem17:33
plasma41freaxeh: For anything ACPI-related, I'd say your best bet is to ask in #osdev20:28

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