3 ms·
First you have to spend a few minutes searching your bash backlog for the exact modprobe command, then you realize you updated your kernel so you have to recomp
by Gigachad 4y ago
First you have to spend a few minutes searching your bash backlog for the exact modprobe command, then you realize you updated your kernel so you have to recompile and resign it, then you have to fiddle with your video inputs but the gui is somehow out of sync with the actual setting. Then run a test before joining the call. And then the other person has the window under their browser and never looks at your video.
- LtWorf 4y ago> First you have to spend a few minutes searching your bash backlog Ah, you don't have the keys "ctrl" and "R" on your keyboard? And I guess you also don't have grep, so you can't just history | grep modprobe. You should consider investing in a keyboard with all the alphabet on it.
- _joel 4y agoIt's via DKMS and loaded automatically at boot. That's the point of DKMS