salty murican detector going offf

my system doesnt has xev/wev/xinput, I tried finding the packages for those but I couldn’t, journalctl -b0 gave some interesting things

here are some snips of it that i think are relevant

[…]

Jun 21 13:36:16 fluffy kernel: /soc@0/clock-controller@1800000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/phy@1a94400
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/display-controller@1a01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000/panel@0
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/display-controller@1a01000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000/panel@0: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/phy@1a94400: Fixed dependency cycle(s) with /soc@0/clock-controller@1800000
Jun 21 13:36:16 fluffy kernel: /soc@0/camss@1b00020: Fixed dependency cycle(s) with /soc@0/cci@1b0c000/i2c-bus@0/s5k4h7yx@10
Jun 21 13:36:16 fluffy kernel: /soc@0/camss@1b00020: Fixed dependency cycle(s) with /soc@0/cci@1b0c000/i2c-bus@1/s5k5e9@2d
Jun 21 13:36:16 fluffy kernel: /soc@0/cci@1b0c000/i2c-bus@0/s5k4h7yx@10: Fixed dependency cycle(s) with /soc@0/camss@1b00020
Jun 21 13:36:16 fluffy kernel: /soc@0/cci@1b0c000/i2c-bus@1/s5k5e9@2d: Fixed dependency cycle(s) with /soc@0/camss@1b00020
Jun 21 13:36:16 fluffy kernel: /soc@0/spmi@200f000/pmic@2/typec@1500/connector: Fixed dependency cycle(s) with /soc@0/usb@7000000
Jun 21 13:36:16 fluffy kernel: /soc@0/usb@7000000: Fixed dependency cycle(s) with /soc@0/spmi@200f000/pmic@2/typec@1500/connector
Jun 21 13:36:16 fluffy kernel: /soc@0/clock-controller@b011050: Fixed dependency cycle(s) with /soc@0/clock-controller@b011050
Jun 21 13:36:16 fluffy kernel: /soc@0/clock-controller@1800000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/phy@1a94400
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000: Fixed dependency cycle(s) with /soc@0/interconnect@500000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000: Fixed dependency cycle(s) with /soc@0/clock-controller@1800000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/display-controller@1a01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000/panel@0
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/display-controller@1a01000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000/panel@0: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/phy@1a94400: Fixed dependency cycle(s) with /soc@0/clock-controller@1800000
Jun 21 13:36:16 fluffy kernel: /soc@0/camss@1b00020: Fixed dependency cycle(s) with /soc@0/cci@1b0c000/i2c-bus@0/s5k4h7yx@10
Jun 21 13:36:16 fluffy kernel: /soc@0/camss@1b00020: Fixed dependency cycle(s) with /soc@0/cci@1b0c000/i2c-bus@1/s5k5e9@2d
Jun 21 13:36:16 fluffy kernel: /soc@0/cci@1b0c000/i2c-bus@0/s5k4h7yx@10: Fixed dependency cycle(s) with /soc@0/camss@1b00020
Jun 21 13:36:16 fluffy kernel: /soc@0/cci@1b0c000/i2c-bus@1/s5k5e9@2d: Fixed dependency cycle(s) with /soc@0/camss@1b00020
Jun 21 13:36:16 fluffy kernel: /soc@0/spmi@200f000/pmic@2/typec@1500/connector: Fixed dependency cycle(s) with /soc@0/usb@7000000
Jun 21 13:36:16 fluffy kernel: /soc@0/spmi@200f000/pmic@2/typec@1500/connector: Fixed dependency cycle(s) with /soc@0/usb@7000000
Jun 21 13:36:16 fluffy kernel: /soc@0/usb@7000000: Fixed dependency cycle(s) with /soc@0/spmi@200f000/pmic@2/typec@1500/connector
Jun 21 13:36:16 fluffy kernel: /soc@0/clock-controller@b011050: Fixed dependency cycle(s) with /soc@0/clock-controller@b011050

[…]

Jun 21 13:36:16 fluffy :   ❬❬ PMOS STAGE 1 ❭❭
Jun 21 13:36:16 fluffy : initramfs version: 3.11.0-r1
Jun 21 13:36:16 fluffy :   ❬❬ PMOS STAGE 2 ❭❭
Jun 21 13:36:16 fluffy kernel: mmc1: new HS400 MMC card at address 0001
Jun 21 13:36:16 fluffy kernel: mmcblk1: mmc1:0001 S0J9N8 58.2 GiB
Jun 21 13:36:16 fluffy kernel:  mmcblk1: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 p29 p30 p31 p32 p33 p34 p35 p36 p37 p38 p39 p40 p41 p42 p43 p44 p45 p46 p47 p48 p49 p50 p51 p52 p53 p54 p55 p56 p57 p58 p59 p60 p61 p62 p63 p64
Jun 21 13:36:16 fluffy kernel: mmcblk1boot0: mmc1:0001 S0J9N8 4.00 MiB
Jun 21 13:36:16 fluffy kernel: mmcblk1boot1: mmc1:0001 S0J9N8 4.00 MiB
Jun 21 13:36:16 fluffy kernel: mmcblk1rpmb: mmc1:0001 S0J9N8 16.0 MiB, chardev (244:0)
Jun 21 13:36:16 fluffy kernel: platform 1a01000.display-controller: Adding to iommu group 4
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/display-controller@1a01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/display-controller@1a01000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000/panel@0
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/display-controller@1a01000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000/panel@0: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000/panel@0
Jun 21 13:36:16 fluffy kernel: /soc@0/display-subsystem@1a00000/dsi@1a94000/panel@0: Fixed dependency cycle(s) with /soc@0/display-subsystem@1a00000/dsi@1a94000
Jun 21 13:36:16 fluffy kernel: panel-boe-624-v0 1a94000.dsi.0: supply vsn not found, using dummy regulator
Jun 21 13:36:16 fluffy kernel: panel-boe-624-v0 1a94000.dsi.0: supply vsp not found, using dummy regulator
Jun 21 13:36:16 fluffy kernel: msm_dpu 1a01000.display-controller: bound 1a94000.dsi (ops dsi_ops [msm])
Jun 21 13:36:16 fluffy kernel: adreno 1c00000.gpu: supply vdd not found, using dummy regulator
Jun 21 13:36:16 fluffy kernel: adreno 1c00000.gpu: supply vddcx not found, using dummy regulator
Jun 21 13:36:16 fluffy kernel: msm_dpu 1a01000.display-controller: bound 1c00000.gpu (ops a3xx_ops [msm])
Jun 21 13:36:16 fluffy kernel: [drm:dpu_kms_hw_init:1173] dpu hardware revision:0x10100000
Jun 21 13:36:16 fluffy kernel: [drm] Initialized msm 1.13.0 for 1a01000.display-controller on minor 0
Jun 21 13:36:16 fluffy kernel: msm_dpu 1a01000.display-controller: Direct firmware load for qcom/a530_pm4.fw failed with error -2
Jun 21 13:36:16 fluffy kernel: msm_dpu 1a01000.display-controller: [drm:adreno_request_fw [msm]] *ERROR* failed to load a530_pm4.fw
Jun 21 13:36:16 fluffy kernel: Console: switching to colour frame buffer device 135x141
Jun 21 13:36:16 fluffy kernel: fb0: sys_imageblit: framebuffer is not in virtual address space.
Jun 21 13:36:16 fluffy kernel: fb0: sys_fillrect: framebuffer is not in virtual address space.
Jun 21 13:36:16 fluffy kernel: msm_dpu 1a01000.display-controller: [drm] fb0: msmdrmfb frame buffer device
Jun 21 13:36:16 fluffy kernel: rmi4_i2c 3-0020: rmi_set_page: set page failed: -6.
Jun 21 13:36:16 fluffy kernel: rmi4_i2c 3-0020: Failed to set page select to 0
Jun 21 13:36:16 fluffy :   Setting up USB gadget through configfs
Jun 21 13:36:16 fluffy kernel: configfs-gadget.g1 gadget.0: HOST MAC 12:90:53:60:2f:9f
Jun 21 13:36:16 fluffy kernel: configfs-gadget.g1 gadget.0: MAC e6:d2:7e:64:fc:7e
Jun 21 13:36:16 fluffy : Trying to start server with parameters: Server IP addr: 172.16.42.1:67, client IP addr: 172.16.42.2, interface: usb0
Jun 21 13:36:16 fluffy : Setting framebuffer mode to: U:1080x2270p-0
Jun 21 13:36:16 fluffy kernel: msm_dpu 1a01000.display-controller: Direct firmware load for qcom/a530_pm4.fw failed with error -2
Jun 21 13:36:16 fluffy kernel: msm_dpu 1a01000.display-controller: [drm:adreno_request_fw [msm]] *ERROR* failed to load a530_pm4.fw
Jun 21 13:36:16 fluffy : Trying to mount subpartitions for 10 seconds...

I don’t know, never tried them even in a vms myself

there is Gloire OS based on the Iron Clad kernel, partially formal proofed written mostly in Ada, their git repositories can be found in Codeberg, there is Genode OS which follows Qt style GPL with caveats, where one corporate entity sells commericial licenses, and holds full copyright through CLA

worst part of GTK

you forgot the oldest of them all, Debian and the its museum, their repos

only one inch?

well, in the mean time, as soon as rumors and myths of such vulnerability appear recruits will make their makeshift solutions on the spot

are you sure that one can just open the hatch on modern tanks? this seems like the type of oversight that should be well known to not be made

rage bait used to be believable

one arm business

ash, shares shared history with dash, integrated into busybox, default shell in alpine

toybox’s shell, toybox’s equivalent of busybox’s ash

tcsh, a shell often found in BSDs for interactive usage by default

never happenwd to me

apt --update full-upgrade

krita is right there, grab a pen

I will never understand this association of “creatives” (extremely vague term) with apple products

shirley temple? who that

I made my own !!

a lot of the features of the controller are not supported by X input, I still think they should’ve added an X input switch somewhere somehow, ideally this device gets its own custom driver for windows, since it is fairly unique generic controller drivers just wouldnt provide full fearure set, hopefully valve makes a full open source in trww driver for it on linux which can be used as a basis for other devices like this,

hopefully valve also provides documentation on how provided ingame integration (basically the game turns on its own “steam” input) and a proper sdk, that would allow developrs to integrate natively the controller without needing steam

stay inside naked