Yes, it's listed in lsusb output.
Here's svlogtail output
2025-02-12T11:59:59.37471 kern.info: [ 8726.412768] usb 4-2: new full-speed USB device number 2 using uhci_hcd 2025-02-12T11:59:59.54085 kern.info: [ 8726.578922] usb 4-2: New USB device found, idVendor=045e, idProduct=0b12, bcdDevice= 5.09 2025-02-12T11:59:59.54125 kern.info: [ 8726.578957] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2025-02-12T11:59:59.54147 kern.info: [ 8726.578974] usb 4-2: Product: Controller 2025-02-12T11:59:59.54125 kern.info: [ 8726.578957] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2025-02-12T11:59:59.54147 kern.info: [ 8726.578974] usb 4-2: Product: Controller 2025-02-12T11:59:59.54164 kern.info: [ 8726.578986] usb 4-2: Manufacturer: Microsoft 2025-02-12T11:59:59.54191 kern.info: [ 8726.578997] usb 4-2: SerialNumber: 3039564C30313733323634323337 2025-02-12T11:59:59.54164 kern.info: [ 8726.578986] usb 4-2: Manufacturer: Microsoft 2025-02-12T11:59:59.54191 kern.info: [ 8726.578997] usb 4-2: SerialNumber: 3039564C30313733323634323337 2025-02-12T12:00:00.14687 user.info: Feb 12 15:00:00 mtp-probe: checking bus 4, device 2: "/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-2" 2025-02-12T12:00:00.15166 user.info: Feb 12 15:00:00 mtp-probe: bus: 4, device: 2 was not an MTP device 2025-02-12T12:00:00.58454 kern.warn: [ 8727.623272] xone_gip: loading out-of-tree module taints kernel. 2025-02-12T12:00:00.58477 kern.notice: [ 8727.623294] xone_gip: module verification failed: signature and/or required key missing - tainting kernel 2025-02-12T12:00:00.58454 kern.warn: [ 8727.623272] xone_gip: loading out-of-tree module taints kernel. 2025-02-12T12:00:00.58477 kern.notice: [ 8727.623294] xone_gip: module verification failed: signature and/or required key missing - tainting kernel 2025-02-12T12:00:00.58454 kern.warn: [ 8727.623272] xone_gip: loading out-of-tree module taints kernel. 2025-02-12T12:00:00.58477 kern.notice: [ 8727.623294] xone_gip: module verification failed: signature and/or required key missing - tainting kernel 2025-02-12T12:00:00.70751 kern.info: [ 8727.745802] usb 4-2: reset full-speed USB device number 2 using uhci_hcd 2025-02-12T12:00:00.86144 kern.info: [ 8727.896637] usbcore: registered new interface driver xone-wired 2025-02-12T12:00:00.88730 user.info: Feb 12 15:00:00 mtp-probe: checking bus 4, device 2: "/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-2" 2025-02-12T12:00:00.88984 user.info: Feb 12 15:00:00 mtp-probe: bus: 4, device: 2 was not an MTP device
Model 1914 (the one currently used with Series S/X) I'm trying to connect it using the usb port
How do I know which? I'm using whatever is default on void
Helix because it's easy to setup and hassle free, and it runs well on my 2009 ASUS Eee
Okay I made a mistake, there's no js entry in /dev/input
The LED is off, which means the controller isn't connected
The LED is off and I've tried retroarch and a game, retroarch detects the controller but takes no input, the game didn't detect it at all
I've installed xone and xboxdrv.
The controller vibrates on plug in but the LED stays off, if I hold down the Xbox button it boots in Bluetooth mode.
Xboxdrv reports no controllers found.
lsusb reports the controller and it has a file in /dev/js0 (or something similar).
Update: there's no js file in /dev/input
retroarch reports detection of Xbox controller on plug in.
I added my user to input group.
My system is up to date.
I installed the system with the XFCE build.
The controller works as intended on Arch, Windows and Android via USB and Bluetooth
Update 2: I installed jstest-gtk and it's not detecting the controller at all
I've been trying exclusively a wired connection to dodgr Bluetooth issues, the controller is detected by the system (it's creating a /dev/input/js0) and the controller vibrates on connecting but the LED is off and no input is received on the laptop's side
Nope, xone ain't doing it, it's an Xbox series controller, but it could be related to my laptop hardware being extremely outdated idk, I should've tried it on a different distros, it works ootb on different machines running Arch and Pop
Reinstalled the xfce build, everything works well, except my controller tho
Both bash and fish are returning incorrect password upon trying to execute any command with sudo
It says incorrect password, I'm pretty sure it is entered correctly
I've tried
exec dbus-run-session -- startlxqt
Nothing changed
I also tried
exec lxqt-session
It ran a broken session with no panel, I tried to sudo from there but it also said incorrect password
I looked up void docs, the only recommended thing I found was enabling elogind :/
I installed LXDM and LightDM, I couldn't login from the DM in either cases, so I decided to run LXQt using startx which worked, except I couldn't sudo from the terminal emulator inside LXQt, while I was able to sudo normally in tty, I've tried enabling elogind, nothing changed, my user is in the wheel group and my system is up to date
Not even close, Proton is a translation layer from Win32 API to whatever works similar for Linux, SDL just gives a higher level API of lower level stuff, like instead of using Xorg/Wayland directly, you get a nicer cross platform API that does the job well
I have the following migration:
(Schema::create('user_images',function(Blueprint $table){ $table->id(); $table->binary('image'); $table->unsignedBigInteger('user_id'); $table->foreign('user_id')->references('id')->on('users'); });)
And the following corresponding model:
`class UserImage extends Model { protected $fillable=[ 'image' ];
public function user():BelongsTo{ return $this->belongsTo(User::class); } }`
I am trying to create new UserImage records with UserImage::create but it is always failing, I am sending the image data using curl:
curl -v -F image=@$1 $URL/api/users -H "Accept: application/json"
I have tried so many things but I got different SQL-related errors, I am not sure how am I supposed to encode the image data to get them stored, I know that accessing $request->image returns only a temporary path of the image on the HDD.