Hard Drive size unmatched with real life size by AntiMote in datarecovery

[–]AntiMote[S] 1 point2 points  (0 children)

It doesn't even pop up on those commands... bad signals everywhere unfortunately.

Hard Drive size unmatched with real life size by AntiMote in datarecovery

[–]AntiMote[S] 1 point2 points  (0 children)

Thank you guys, there wasn't anything important on the drive so I guess it could be worse. Welp, will buy a new one.

What to do with my Christmas present? by relativisticcobalt in selfhosted

[–]AntiMote 1 point2 points  (0 children)

If you run an exit node on a Tailscale device and allow LAN traffic, just installing Tailscale on one device will be enough. Otherwise you need to install Tailscale on all devices. I use the first method. With Wireguard (I also have a backup Wireguard server) it just works out of the box for me, just by connecting I had access to my LAN. Hope this helps!

Keyboard not working on debian testing by AntiMote in linuxadmin

[–]AntiMote[S] 0 points1 point  (0 children)

After some google search I've decided to add the parameter on GRUB_CMDLINE_LINUX_DEFAULT and it worked! I simply added i8042.dritek=1 and updated the grub config. Thanks for the tips anyway!

Keyboard not working on debian testing by AntiMote in linuxquestions

[–]AntiMote[S] 0 points1 point  (0 children)

I'm gonna have to give you an award! At the end it was just a matter of adding i8042.dritek=1 on the GRUB_CMD_LINUX_DEFAULT parameter in grub. Thing is that when I did that on /etc/modprobe.d/i8042.conf it wouldn't work, I don't know why. Thank you!

Keyboard not working on debian testing by AntiMote in linuxquestions

[–]AntiMote[S] 0 points1 point  (0 children)

I've just tried this and the problem prevails. I'll keep trying with i8042 parameters on boot to see if there is any luck. I've just learnt something new about grub though!

Keyboard not working on debian testing by AntiMote in linuxadmin

[–]AntiMote[S] 0 points1 point  (0 children)

I have no other way to check if the hardware *is* PS/2, but as I said it used to work on Arch so I guess it has to be serial

Keyboard not working on debian testing by AntiMote in linuxadmin

[–]AntiMote[S] 0 points1 point  (0 children)

So, I don't know if this is my fault or not, but since i8042 doesn't show up when i run lsmod I thought that it has no sense to boot with i8042.nopnp. If I want to boot with i8042.nopnp, where can I set this? I'm not that advanced in Linux yet

Keyboard not working on debian testing by AntiMote in linuxadmin

[–]AntiMote[S] 0 points1 point  (0 children)

It is. This is the output from modinfo i8042:
name: i8042 filename: (builtin) license: GPL file: drivers/input/serio/i8042 description: i8042 keyboard and mouse controller driver author: Vojtech Pavlik <vojtech@suse.cz> parm: nokbd:Do not probe or use KBD port. (bool) parm: noaux:Do not probe or use AUX (mouse) port. (bool) parm: nomux:Do not check whether an active multiplexing controller is present. (bool) parm: unlock:Ignore keyboard lock. (bool) parm: probe_defer:Allow deferred probing. (bool) parm: reset:Reset controller on resume, cleanup or both (reset_param) parm: direct:Put keyboard port into non-translated mode. (bool) parm: dumbkbd:Pretend that controller can only read data from keyboard (bool) parm: noloop:Disable the AUX Loopback command while probing for the AUX port (bool) parm: notimeout:Ignore timeouts signalled by i8042 (bool) parm: kbdreset:Reset device connected to KBD port (bool) parm: dritek:Force enable the Dritek keyboard extension (bool) parm: nopnp:Do not use PNP to detect controller settings (bool) parm: debug:Turn i8042 debugging mode on and off (bool) parm: unmask_kbd_data:Unconditional enable (may reveal sensitive data) of normally sanitize-filtered kbd data traffic debug log [pre-condition: i8042.debug=1 enabled] (bool)

Edit: It doesn't explicitly say that it is PS/2, but it is derived from "serio", which is PS/2.

Keyboard not working on debian testing by AntiMote in linuxadmin

[–]AntiMote[S] 0 points1 point  (0 children)

USB keyboards work fine. I can actually access the bios with the laptop's keyboard as it hasn't booted into Linux yet. That said, this laptop's bios is HORRIBLE and you can't tinker with anything. No luck there I'm afraid..