previous
2022-11-30
11:08:54 <Jesse39> Hello, I'm having some trouble getting my wifi working
11:10:32 <Jesse39> I installled via ethernet and during install it said that I would need firmware "regulatory.db" and "iwlwifi-6000-4.ucode"
11:10:48 <Jesse39> And I'm not sure how to find or add them now
11:12:41 <debdog> according to https://packages.debian.org "iwlwifi-6000-4.ucode" is provided by the firmware-iwlwifi package
11:13:07 <Jesse39> so I only need to install that package?
11:13:30 <debdog> I think so, yes
11:14:08 <debdog> but I am not a wifi expert
11:16:11 <debdog> at least it is a step in probably the right direction
11:16:56 <Jesse39> thanks. I'll look in to it a bit more
11:17:26 <Jesse39> I've installed it on this computer before but can't remember what I had to do for wifi
11:19:30 <debdog> well, if installing said package doesn't improve your situation, you just can purge it afterwards
11:23:44 <Jesse39> I tink I need to add some repo
11:25:43 <Xenguy> Jesse39, paste your /etc/apt/sources.list to paste.debian.net if need be
11:28:20 <Jesse39> was able to install it by adding non-free repo to sources.list
11:30:18 <Xenguy> Jesse32, Great, for more info: https://www.devuan.org/os/packages
11:31:53 <Jesse32> it seems that I am still unable to use wifi
11:33:14 <debdog> but did it load the firmware? does "lspci -k" list a kernel driver for your wifi device?
11:33:42 <debdog> "Kernel drive in use" or simililar
11:33:52 <debdog> hehe *similar
11:36:54 <Jesse32> I'm not seeing the device there
11:37:09 <Jesse32> maybe I'm just overlooking it since I don't understand a lot of this
11:38:20 <debdog> could you paste the output, please? preferably on https://paste.debian.net/
11:38:32 <Jesse32> Network Controller?
11:39:02 <debdog> sounds about right. if uncertain the entire output
11:39:13 <Jesse32> https://paste.debian.net/1262451/
11:39:23 <Jesse32> I gave the whole output but I think this is it
11:40:01 <Jesse32> it sayss "Kernel modules: iwlwifi" but no driver in us3e
11:40:15 <debdog> 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35)
11:40:15 <debdog> Subsystem: Intel Corporation Centrino Advanced-N 6200 2x2 AGN
11:40:15 <debdog> Kernel modules: iwlwifi
11:41:23 <debdog> this is after a reboot, right?
11:41:38 <Jesse32> oof no I should probably try that
11:41:45 <Jesse32> I'll be right back
11:44:00 <Jesse17> yeah it seems to be working now
11:44:05 <Jesse17> Thanks for the help
11:44:46 <debdog> no worries. but celebrate when you have an actual connection
11:45:22 <Jesse17> I am connected
11:45:43 <debdog> well then... CELEBRATION
11:46:05 <Jesse17> Thanks again, I don't know why I wasn't able to find this solution
11:46:23 <Jesse17> This could have been a lot more frustrating lol
11:47:16 <debdog> your lspci output reminds me of an elderly laptop I recently installed win7 on... friggin PITA
13:05:01 <talismanick> https://0x0.st/o0In.txt
13:05:13 <talismanick> Is it supposed to do this?
13:05:32 <talismanick> same trouble with sysvinit-core instead of runit-init
13:12:12 <gnarface> use paste.debian.net and i'll actually look
13:32:17 <talismanick> gnarface: https://paste.debian.net/1262460/
13:33:38 <talismanick> (0x0 is what I have set up for pasting killed regions in Emacs)
13:43:23 <gnarface> talismanick: uh... yes that's expected behavior but you shouldn't have had systemd installed in the first place, are you attempting a migration from debian? if not, you have accidentally mixed repos at some point
13:43:37 <talismanick> gnarface: yes, migrating
13:45:07 <gnarface> there is detailed instructions on the safest path around here somewhere, but i'd recommend you have a live image you can boot from in case something goes wrong
13:45:52 <rrq> this one still works well: https://git.devuan.org/rrq/debian-to-devuan
13:46:44 <gnarface> talismanick: was this install bullseye or buster?
13:46:57 <talismanick> gnarface: I have everything backed up anyways, so I can roll back to the previous state and try again
13:47:49 <gnarface> talismanick: so the risky part is it's gonna have to remove systemd and all the dependencies, including the running kernel which will then have to be reinstalled along with all the devuan startup stuff before you reboot
13:48:10 <gnarface> the script might be a better choice if you're not sure of yourself
13:49:05 <gnarface> we've seen various pitfalls, especially in situations where your grub setup is weird
13:49:26 <gnarface> or if you get unlucky and your rootfs gets flagged for fsck on that critical reboot
13:49:42 <gnarface> most people just forget to put the kernel back in
13:50:30 <talismanick> rrq: Aside from using Alpine a bit in the past, I haven't used sysvinit/OpenRC much. What would the runit equivalents of lines 81-87 be?
13:51:17 <talismanick> gnarface: sounds like I should spin up a Devuan VM and move things over instead?
13:51:59 <gnarface> talismanick: well, no i'd still recommend rrq's script in this case, and just switch to runit after the migration is done
13:52:06 <gnarface> ... since you have backups
13:52:12 <gnarface> and this will be a good learning experience :)
13:52:27 <gnarface> if it goes well it should be a lot faster
13:53:00 <gnarface> just remember the thing about the kernel
13:53:08 <rrq> I don't know. Perhaps the best is to install sysvinit-core first and then replace to openrc (I don;t know the steps for that, but it's almost certainly easier that way)
13:53:53 <rrq> I think 81 -87 would stay as they are
13:54:37 <gnarface> talismanick: it might actually uninstall a lot of stuff, but you can just reinstall all of it
13:55:11 <gnarface> talismanick: just make sure you got the kernel, grub, and eudev installed again before you reboot
13:55:33 <gnarface> if it uninstalls your GUI you can reinstall that before or after reboot
13:56:15 <talismanick> There's no gui
13:56:17 <talismanick> it's a server
13:56:29 <gnarface> should be much easier then
13:56:34 <talismanick> yea
13:56:44 <gnarface> it's not dual-booting windows or anything right?
13:56:50 <talismanick> nope
13:56:57 <gnarface> and grub is on the first disk already?
13:57:02 <talismanick> yes
13:57:19 <gnarface> you should be fine if you don't panic and reboot before it's bootable again
13:57:28 <talismanick> just a plain Debian install, running several webservers
13:58:32 <gnarface> if for some reason you reboot before it's bootable again, it's usually pretty simple to just boot with a live image or other rescue image, chroot in, then install what's missing (usually consists of a kernel, eudev, and running update-grub again)
13:58:40 <rrq> mmm line 74 might need editing; there is a newer keyring
14:00:20 <rrq> you'd use _2022.11.15_all.deb nowadays
14:01:11 <rrq> ... and line 75 the same
16:14:19 <talismanick> Came back to see if it finished
16:14:30 <talismanick> it just dropped to a grub prompt
16:14:57 <talismanick> I think I'll just boot off a live ISO and pull everything else out of the backup
16:20:00 <gnarface> talismanick: no, don't do that, boot off the live image, chroot in, and run grub-install again
16:20:19 <gnarface> talismanick: and while you're in there make sure you have a kernel installed, like i said
16:20:44 <talismanick> gnarface: ...but why?
16:20:53 <talismanick> that only sounds like it's inviting more problems...
16:21:09 <gnarface> talismanick: we've been through this 1000 times or so by now
16:21:19 <gnarface> just trying to save you time
16:21:42 <talismanick> What usually happens if I do the opposite?
16:21:52 <gnarface> what do you mean the opposite?
16:22:14 <gnarface> what you did was the opposite; ignore me and just let it reboot without a kernel or grub configuration in plce
16:22:28 <gnarface> there's only so many things it can be missing here, it's a list of 2
16:22:34 <talismanick> fresh install from an ISO, boot the backup in a VM, and move over the files I need
16:22:54 <gnarface> you just waste another 1-4 hours when you could be up and running in 5 minutes
16:23:01 <talismanick> Oh, I see what you thought I meant
16:23:27 <talismanick> I meant downloading an ISO, installing to disk, and adding back what state I need from the backup
16:23:56 <gnarface> yea that's still going to take way more time than just finishing what you started
16:24:30 <gnarface> do you need instructions for how to chroot properly? i can give them to you step by step
16:25:15 <talismanick> I know how to chroot into another system from a live image, but I don't think there's an option to boot a live ISO and access the prior system
16:25:41 <gnarface> what????
16:25:49 <gnarface> false
16:25:56 <gnarface> you can access the harddrive from a live iso easily
16:26:35 <gnarface> you could do this without the live iso even if you know what to type into the grub prompt i just don't remember the exact commands
16:27:38 <gnarface> once you're chrooted in, with /sys, /proc, /dev, and /dev/pts all bind-mounted inside it, i guarantee that installing a kernel and re-running grub-install or update-grub will make it bootable
16:27:59 <gnarface> no need to restore from backup, you're like 99.9% of the way there and if you'd paid attention this would already have happened before you rebooted
16:28:07 <gnarface> and you're easily the 10th person i've had this argument with
16:28:41 <talismanick> alright, I'll listen
16:29:10 <gnarface> mount /dev/sda1 /mnt
16:29:17 <gnarface> mount -o bind /proc /mnt/proc
16:29:22 <gnarface> mount -o bind /sys /mnt/sys
16:29:27 <gnarface> mount -o bind /dev /mnt/dev
16:29:36 <gnarface> mount -o bind /dev/pts /mnt/dev/pts
16:29:52 <gnarface> chroot /mnt /bin/bash -i
16:30:08 <gnarface> apt-get update && apt-get install linux-image-amd64
16:30:14 <gnarface> update-grub
16:30:23 <gnarface> then just reboot
16:30:45 <talismanick> yeah, yeah, ye olde `for i in dev proc sys run; do mount --rbind /$i /mnt/$i; mount --make-rslave /mnt/$i; done`
16:31:08 <talismanick> or variations thereof
16:31:21 <gnarface> uh, i'm not sure whether that'll work or not, but what's important is that grub-install or update-grub sees the hardware right, or it'll misfire
16:31:22 <talismanick> can't say I can recall messing around with pts, though
16:32:05 <gnarface> pts may only be necessary if you're also running a tf2 server in there honestly, i just want to be sure you have everything for grub to be able to properly orient itself
16:32:28 <talismanick> What's special about TF2?
16:32:35 <talismanick> My curiosity is piqued
16:32:49 <gnarface> it's crappily programmed, i think, or it has a valve backdoor, fuck if i know. if you do this wrong it'll try to install grub to the livecd which will be useless
16:33:05 <talismanick> that's hilarious
16:33:17 <talismanick> "return to sender"
16:33:54 <gnarface> the bind mounts are so the kernel on the livecd, while in the chroot, knows where the real hardware is
16:34:15 <gnarface> it wouldn't be necessary if you'd done this step before rebooting
16:34:37 <gnarface> while you're in there make sure you have eudev installed too or you will get past the grub prompt but probably not much further
16:34:58 <talismanick> I just followed the instructions on the website verbatim
16:35:44 <gnarface> i didn't look at them so i can't tell you why they didn't work, this is the way i recovered from the mess the last dozen times it came up that's all
16:38:29 <gnarface> the bios found grub, grub didn't find a kernel
16:38:37 <gnarface> that means the kernel is missing or grub is out of place
16:38:47 <gnarface> the fix of reinstalling them both works either way
16:39:00 <talismanick> fair's fair
16:39:10 <talismanick> that makes sense to me
16:39:44 <gnarface> your main harddrive is called /dev/sda right?
16:39:58 <gnarface> this isn't something weird like an ARM machine or a VM right?
16:40:06 <talismanick> ...it is a vm
16:40:09 <talismanick> a vps
16:40:13 * gnarface facepalms
16:40:15 <talismanick> I thought I said this was a server
16:40:33 <talismanick> I was wondering why you were so adamant about this method
16:40:37 <gnarface> the instructions you were given most likely assumed it was a bare metal server
16:40:50 <gnarface> calling it a server also implies bare metal
16:40:58 <talismanick> bold of you to assume I have money
16:41:11 <gnarface> i don't have any money, i'm still using pentium3's here
16:41:31 <gnarface> wait if it's a vps how do you boot a live image on it?
16:41:39 <talismanick> Hetzner lets you
16:41:46 <talismanick> via the rescue mode reboot
16:42:11 <gnarface> this might still work, but we need to make sure grub is installed in the right place
16:42:36 <talismanick> Yeah, I do think this'd work - I don't see why it shouldn't
16:42:53 <talismanick> but, I hope my confusion about /why/ is clearer now
16:43:10 <gnarface> yea, being a VM it just introduces a lot of other unknowns, you should specify that more clearly in the future
16:43:19 <talismanick> mea culpa
16:43:30 <gnarface> bare metal, x86 hardware boots very uniformly, relatively
16:43:43 <gnarface> if you start getting into virtual setups, there's tons of weird different ways the hypervisor can work
16:43:53 <talismanick> true
16:44:07 <talismanick> I think I'll just install all the way as usual from the ISO
16:44:27 <gnarface> i'd still like to know if this will work though
16:44:36 <gnarface> you might learn something too
16:44:40 <gnarface> should only take a couple minutes to try
16:46:28 <talismanick> Well, if I can ever get it to recognize that I'm telling it to pull the ISO from an address...
16:46:43 <talismanick> Been a long time since I fell back on this option
16:46:54 <gnarface> you said they had a rescue image already preloaded?
16:47:14 <talismanick> To boot a custom ISO, you have to edit a conf file
16:47:14 <gnarface> see, i assumed you were sitting by the machine itself
16:47:53 <talismanick> And, I don't know how to get back to the default menu from this conf file
16:48:17 <talismanick> so it looks like I'm trapped in limbo until I can get it to go through without giving up and nuking the system
16:48:43 <gnarface> you literally can't figure out how to exit the conf file editor or something?
16:49:03 <talismanick> It drops you back into it if it doesn't recognize what it's suppose to do lol
16:49:29 <gnarface> can you show a screenshot?
16:50:43 <rrq> you know that the installer itself is like a live system? shift to a shell with C-A-F2 and go from there
16:51:52 <rrq> .. ah probably irrelevant here.. (where's my stone?)
16:52:08 <talismanick> https://0x0.st/o0Uu.png
16:53:11 <talismanick> ah, found how to get out
16:54:05 <talismanick> (surprisingly, not the "Cancel" button)
16:54:16 <gnarface> alright, good because i'm still not clicking on that domain
16:54:26 <talismanick> dude, it's just a pastebin
16:54:31 <talismanick> lol
16:54:59 <talismanick> (I like it because the default way to upload is via curl, so it's easy to script and attach to a button)
16:55:23 <gnarface> funny enough whenever i float my own links nobody clicks on them either
16:55:23 <talismanick> https://0x0.st/
16:56:02 <gnarface> so anyway, boot anything that can mount the drive
16:56:10 <gnarface> or virtual drive or whatever it is
16:56:37 <gnarface> if you got it as far as a grub prompt that still suggests this will work
16:56:43 <gnarface> it has grub after all
16:56:56 <talismanick> lsblk just says the biggest partition is sda1, at 38G, so that should be it
16:57:18 <gnarface> ok, when you run grub-install make sure to install to sda not sda1
16:57:25 <talismanick> ofc
16:57:27 <gnarface> but make sure a kernel is installed first
16:57:35 <talismanick> I've shot myself in the foot like that before :)
16:58:10 <gnarface> or you can run grub-install, then install the kernel, then just run update-grub
16:58:20 <gnarface> but i think grub-install will also imply update-grub
16:58:41 <gnarface> shouldn't hurt to run update-grub once extra as a last step just to be sure
17:00:04 <gnarface> the chroot and bind mount steps are still important, i only recommended the live image because i didn't realize you already had some sort of virtual manager with preloaded images
17:01:27 <talismanick> Well, that's a problem
17:01:35 <talismanick> no networking in chroot
17:01:49 <talismanick> so, no apt-get
17:02:02 <gnarface> there probably is networking, it probably just didn't get as far as creating your /etc/resolv.conf
17:02:09 <gnarface> try to ping something by IP
17:02:28 <gnarface> or run /sbin/ifconfig -a
17:03:00 <talismanick> yeah, eth0 up and running
17:03:13 <gnarface> just create a resolv.conf manually
17:03:26 <gnarface> were you using NetworkManager before or something like that?
17:03:33 <talismanick> no
17:03:40 <talismanick> not that I
17:03:43 <talismanick> 'm aware of
17:03:44 <gnarface> is resolv.conf missing?
17:05:06 <talismanick> ls say it's there, but cat says no such file
17:05:14 <gnarface> ls -l
17:05:24 <gnarface> it's probably an orphaned symlink
17:05:27 <talismanick> ls -l says it symlinks to /run/resolvconf/resolv.conf
17:05:30 <talismanick> yeah
17:05:40 <gnarface> delete it and just create a static one
17:05:56 <gnarface> doesn't have to be permanent, just has to be there long enough to finish this
17:06:37 <gnarface> you probably want to UNINSTALL the resolvconf package too, since that'll point it elsewhere looking for dns entries
17:07:32 <gnarface> what does this command return? dpkg -l |grep linux-image
17:08:05 <talismanick> rc linux-image-5.10.0-17-amd64 5.10.136-1 amd64 Linux 5.10 for 64-bit PCs (signed)
17:08:05 <talismanick> rc linux-image-amd64 5.10.136-1 amd64 Linux for 64-bit PCs (meta-package)
17:08:26 <gnarface> traces of two uninstalled kernels, that's the smoking gun
17:08:48 <gnarface> somehow this went off the rails before the reboot
17:09:42 <gnarface> well, linux-image-amd64 is just a meta-package that points to the latest stable kernel
17:09:50 <gnarface> but the "rc" means they've been uninstalled
17:09:58 <gnarface> that should be "ii"
17:10:00 <talismanick> As much as I like a good detective mystery, I'm feeling too tired for another episode
17:10:10 <talismanick> I think I'm going to bed for now
17:10:15 <rrq> talismanick: I wonder if you where running my script, or di you DIY ?
17:10:15 <talismanick> thanks for the help
17:11:03 <talismanick> rrq: I DIY'd from the migration instructions on the website, then tried your script when those didn't work
17:11:23 <talismanick> ergo nasal demons
17:11:28 <rrq> ok; maybe someone could try tohe opposite order sometime
17:12:36 <rrq> (ideally running my script should avoid the need for DIY :))
17:13:15 <talismanick> I read it over, and didn't see anything which tipped me off that it'd conflict
17:13:36 <talismanick> (at most, it repeated already-idempotent commands or added another)
17:13:39 <gnarface> talismanick: it doesn't matter why it didn't work, what matters is that if you put the resolv.conf back and reinstall them it starts working
17:13:48 <rrq> the key issue is to only repalce init before going further
17:14:04 <talismanick> gnarface: Where can I find the default resolv.conf?
17:14:12 <talismanick> to copy-paste
17:14:19 <gnarface> just use anything it's one line
17:14:26 <gnarface> don't you know the IPs of your DNS servers?
17:14:31 <talismanick> like, "foo bar baz"?
17:14:37 <talismanick> um, no
17:14:41 <gnarface> no, not literally anything but
17:14:48 <gnarface> check in /etc/network/interfaces
17:15:06 <gnarface> do you have lines for dns-nameservers and dns-search in there?
17:15:20 <talismanick> mmm, nyet
17:15:45 <gnarface> you can probably just use google's public dns temporarily until you can find the real ones
17:16:00 <talismanick> 8.8.8.8?
17:16:17 <gnarface> nameserver 8.8.8.8
17:16:19 <gnarface> that one line should be enough
17:16:24 <talismanick> oh
17:16:56 <talismanick> ah, works now
17:17:20 <gnarface> most likely your ISP will have provided their own nameservers for you, you should locate them later when you have a chance
17:18:13 <gnarface> some systemd component must have absorbed this, is my guess
17:19:02 <gnarface> so naturally they buried the evidence
17:20:20 <talismanick> wait fuck why did i reboot without exiting and umounting
17:20:49 <talismanick> oh, it didn't even do anything
17:20:57 <gnarface> for sysvinit you want to make sure you have: sysv-rc, sysvinit, sysvinit-core and sysvinit-utils
17:21:06 <gnarface> also make sure you have eudev, and linux-image-amd64
17:21:20 <gnarface> (we're assuming the system is 64-bit, is that wrong?)
17:21:39 <talismanick> oh, nice, it works
17:22:03 <talismanick> And, I fetched runit-init instead of sysvinit-core
17:22:22 <gnarface> well i just wanted to make sure you had stuff i knew would work but as long as it works that's what matters
17:22:31 <talismanick> ty
17:22:45 <gnarface> i thought it would be safer to fix this mess first then you can migrate to runit after you've got it booting
17:23:10 <talismanick> The two are orthogonal, no?
17:23:54 <gnarface> well, it's not a difficult migration and i'm not sure if the runit install can fall back on sysvinit scripts or not, the openrc one does
17:24:15 <talismanick> openrc is a skin over sysvinit iirc
17:24:27 <talismanick> runit is its own thing (it even works on BSDs, etc)
17:24:55 <gnarface> openrc is in debian but not in other distros... anywayit seemed safer to have sysvinit in place and working as a known quantity first
17:25:00 <talismanick> part of the daemontools family, like s6 if you've used that
17:25:00 <gnarface> anyway is it booting now?
17:25:04 <talismanick> yeah
17:25:08 <gnarface> great
17:25:13 <talismanick> I'm using runit on Void, actually
17:25:17 <talismanick> (the default)
17:25:29 <gnarface> i want to just point out for the record we spent more time debating the solution than actually doing it
17:25:38 <talismanick> fair
17:25:58 <gnarface> anyway, i'm stepping away for now, have fun with your devuan
17:26:07 <talismanick> thanks
19:29:59 <uvos> hi, devuan chimaera includes the iio-sensor-proxy package imported from debian
19:30:21 <uvos> however this package contains only a systemd unit file, makeing this deamon package pretty useless
19:30:53 <uvos> for previous beowulf we had a fork with a init script: https://github.com/maemo-leste-upstream-forks/iio-sensor-proxy/blob/maemo/beowulf/debian/iio-sensor-proxy.init
19:30:59 <uvos> i would be neat if this could be included in devuan
21:56:35 <gnarface> if ravehaver9000 comes back tell them to install the linux-headers-* package corresponding to their current kernel then re-run dpms as root, and just give up on nvidia-persistenced and set environment variable __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 instead
21:57:33 <gnarface> also warn them that i've got a heads-up from another channel that the latest nvidia driver release crippled pascal family cards just fair warning, upgrading might be a bad idea right now
22:01:12 <gnarface> (and incidentally, there being a catastrophic crippling regression in the official nvidia linux drivers on the same day as a major world of warcraft release is no longer even remotely plausibly a coincidence)
---------- 2022-12-01 ----------
05:13:38 <unclouded> Hi, debootstrap is giving me "chroot: failed to run command 'dpkg-deb': No such file or directory". It's dead right: There is no dpkg-deb in the target directory. The command is just "debootstrap beowulf /tmp/target http://mirror:3142/devuan", run from a chimaera installation
05:15:16 <unclouded> Does it matter than /tmp is tmpfs?
05:35:54 <markizano> unclouded, mirror:3142 is a valid mirror, right?
05:45:20 <___used> Is vlc 3.0.18 coming up for beowulf? It's not in packages, I'm on 3.0.17 and that has a nasty hole: https://securityonline.info/cve-2022-41325-vlc-media-player-remote-code-execution-vulnerability/
05:48:07 <Jjp137> you'll probably have to wait for Debian to update it since I don't think Devuan forks vlc, but you can keep an eye on it here: https://security-tracker.debian.org/tracker/source-package/vlc
05:48:32 <Jjp137> just remember what each Debian release maps to in Devuan of course
05:49:37 <unclouded> markizano: It's apt-cacher-ng, but the problem is the same when I use http://deb.devuan.org/devuan as the mirror
06:04:24 <unclouded> The problem is the same when run from a beowulf installation too
06:18:06 <unclouded> Doh! The problem is that I was using http://deb.devuan.org/devuan instead of http://deb.devuan.org/merged. Working now
06:20:40 <golinux> Sometimes it's the little things that get you . . .
06:22:33 <unclouded> :) It got me good
06:28:05 <ravehaver9000> back here, thanks for the advice gnarface
06:28:21 <ravehaver9000> my card is an ampere one so itd prob should be safe to do that
06:37:30 <ravehaver9000> whats dpms btw
06:37:50 <ravehaver9000> i dont really recogmize it at all and want to know what it means before i screw up anything
06:39:16 <unclouded> ravehaver9000: Is it this? https://en.wikipedia.org/wiki/VESA_Display_Power_Management_Signaling
06:40:12 <tux12> apropos dpms says X11::Protocol::Ext::DPMS (3pm) - Perl module for the X11 Protocol DPMS Extension
06:47:42 <ravehaver9000> ooh, so its a module for perl
06:48:16 <ravehaver9000> how do i restart it? i tried switching to root and using something like, "system dpms restart" but that ofc wouldnt wokr
06:48:55 <ravehaver9000> it prob doesnt help that the only init system i actually used was systemd. i used a bit of openrc when i was in artix but ive mostly unlearned it aside from everything starting with rc-service
06:49:03 <ravehaver9000> ive also tried runit. not for me to say the least
06:49:22 <rrq> no, DPMS is a monitor facility; power saving
06:50:52 <rrq> some docs via "man xset"
06:53:23 <rrq> not so important for LCD and LED monitors but CRTs where costlier
06:54:07 <ravehaver9000> yeah i can see that, crts def had an issue with that t. owned crt tvs until 2016
07:00:56 <bbliss> Hey all. I was hoping to figure out why my Intel i5-based 2020 MacBook's keyboard and trackpad do not work at all with the current Daedalus 11/28 preview, and possibly get the necessary support folded into Daedalus before it is released. USB keyboards work fine, and Daedalus generally installs okay, but not having KB+trackpad work out of the box is sorta frustrating. Ideas? Pointers to where
07:00:56 <bbliss> I should be looking?
07:46:54 <rwp> bbliss, That support is entirely within the Linux kernel. I would be looking there for solutions and support.
07:47:44 <rwp> If an older kernel works but a newer kernel fails then that would be a regression in the kernel. That's always easier to argue needs to be fixed.
08:15:11 <bbliss> rwp, yeah, that's what I'm trying to influence. I'm trying to influence the devuan-dev folks' choices for how to configure the kernel, and which optional modules to include alongside it. Right now, the 6.0.0-5 kernel does not have a suitable driver included or configured. The "linux on T2" wiki indicates that such a kernel module exists, but it's not present in Daedalus by default, apparently?
08:15:49 <bbliss> (required dkms and git clone'ing a random github repo)
08:16:16 <bbliss> (not sure what mainline Debian is doing with it, though, if anybody happens to know?)
08:52:05 <rwp> If it requires something from Github then that is probably on you to add as you are doing then.
08:52:25 <rwp> Since something from a 3rd party on Github means that it has not made it into the Linux kernel main source.
08:52:38 <rwp> And if it isn't there then I would not expect any software distribution to include it.
08:53:14 <rwp> Also the Linux kernel packages in Devuan are direct pass-through from Debian. Not just identical but the actual same package.
08:53:33 <rwp> Devuan is the same as Debian for the kernel and hardware support of this type.
08:54:13 <rwp> (The Devuan installers are somewhat different however and have included needed firmware.)
08:54:57 <bbliss> Ok. Seems likely then that Daedalus won't install on Intel MacBooks without a USB keyboard then :-(
08:56:30 <bbliss> (I tried doing this with Beowulf, it would not boot, I tried Chimaera, it wouldn't boot, Daedalus is the first release that has a >5.7 kernel in the box that can even boot a MacBook. I was assuming more people used Devuan on MacBooks, but apparently nobody does)
08:57:05 <bbliss> well, T2 macbooks at least, I guess
2022-12-01
next