12:40 <sewn> hi

15:38 <rohan_k> hi guys

15:38 <rohan_k> how is kiss doing?

15:50 <ERROR_404_NULL> Hi, I copied the linux kernel and initramfs images from my desktop to my laptop (because compiling the kernel manually wasn't even spitting text onto the screen), and it booted (after a grub-mkconfig), but my keyboard isn't detected (and neither is any USB keyboard I've tried), anyone have any suggestions

16:30 <ERROR_404_NULL> Is there a specific package that I have to install to enable the keyboard or something?

16:36 <sewn> ERROR_404_NULL: your issue is quite common but the issue relies in your kernel configuratiohn

16:36 <sewn> you can search the IRC archives for many people who have faced your issue: https://libera.irclog.whitequark.org/kisslinux

16:36 <sewn> rohan: fine

17:55 <ERROR_404_NULL> sewn: I wouldn't think that it would be a configuration issue, as it's just the default Arch kernel (6.4.10)

18:02 <sewn> configure your own kernel or something, you need an initramfs for an arch kernel

18:02 <sewn> as everything in a distribution kernel is most likely modules

18:05 <ERROR_404_NULL> I uh

18:05 <ERROR_404_NULL> Copied the initramfs as well

18:06 <ERROR_404_NULL> I think I'm just gonna copy the Arch config and search for the keyboard and mouse configs

19:24 <ERROR_404_NULL> If it's related, the boot messages include "Killing device manager to make way for service"

23:16 <ERROR_404_NULL> Is there a default minimal kernel config that I could use?

23:16 <ERROR_404_NULL> (That will at least load everything functionally on common hardware)

23:24 <illiliti> you can steal config from some well-known distro. as you already mentioned arch is a good option

23:25 <illiliti> but it wouldn't be minimal because those configs are too generic and include all shit.

23:25 <ERROR_404_NULL> Yea

23:25 <illiliti> plus they require initramfs to load all that shit

23:26 <ERROR_404_NULL> Yea, I copied the initramfs along with the kernel, and it still failed to detect any input devices

23:27 <illiliti> usually initramfs don't need input devices in order to boot system

23:28 <illiliti> it needs only fs drivers to mount root and boot into it

23:29 <illiliti> then it's up to host system to mess with input devices

23:30 <ERROR_404_NULL> Wdym by 'host system'

23:31 <illiliti> system that you are booting into

23:31 <ERROR_404_NULL> So the software

23:32 <ERROR_404_NULL> Ok, what in there could be messed up to not allow a standard (old) ThinkPad keyboard to not get detected

23:33 <illiliti> no idea

23:34 <illiliti> if kernel and initramfs configured correctly you should be able to boot even without input devices

23:34 <illiliti> so something wrong with kernel/initramfs

23:35 <ERROR_404_NULL> illiliti: It boots just fine, the issue is that it won't detect device input

23:36 <ERROR_404_NULL> (Rebooting to apply kernel updates, brb)

23:37 <illiliti> is there anything in /dev/input? is mdev running?

23:37 <ERROR_404_NULL> I have no clue because, as previously stated, ***no input devices have any effect***

23:38 <ERROR_404_NULL> The TTY just doesn't respond

23:40 <illiliti> ah then modules weren't loaded

23:42 <ERROR_404_NULL> So I just `$(lsmod) > /mnt/etc/modules` from a live env?

23:43 <ERROR_404_NULL> (Minus the $() that I added for some reason)

23:43 <illiliti> no it won't work

23:43 <illiliti> modules are second-class citizens in kiss

23:44 <illiliti> what's your mdev.conf? default?

23:44 <ERROR_404_NULL> Ye

23:44 <ERROR_404_NULL> I just linked it from /etc/sv to /var/service with no conf

23:45 <ERROR_404_NULL> (Side note, it would be really nice if KISS had package descs)

23:46 <illiliti> $MODALIAS=.* root:root 660 @modprobe -q "$MODALIAS"

23:46 <illiliti> add this to your mdev.conf

23:50 <illiliti> then reboot

23:50 <illiliti> /lib/modules/<kernel> is present right?

23:52 <ERROR_404_NULL> Yea

23:53 <ERROR_404_NULL> Wait, not for the right kernel

23:53 <ERROR_404_NULL> That explains a lot

23:53 <illiliti> perhaps

23:53 <illiliti> check also /lib/firmware if you need it

23:56 <ERROR_404_NULL> That should only be required for wireless, for my devices

23:56 <ERROR_404_NULL> s/devices/device

23:59 <illiliti> ack