You are not logged in.
Hi all.
uname -a ✔ 3.04 Dur 16:15
Linux turing 5.16.10-arch1-1 #1 SMP PREEMPT Wed, 16 Feb 2022 19:35:18 +0000 x86_64 GNU/Linuxlsusb
Bus 008 Device 004: ID 1058:262f Western Digital Technologies, Inc. Game Drivelsblk 1 ↵ 0.00 Dur 16:14
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 465.8G 0 disk
├─nvme0n1p1 259:2 0 16M 0 part
└─nvme0n1p2 259:3 0 465.7G 0 part
nvme1n1 259:1 0 232.9G 0 disk
├─nvme1n1p1 259:4 0 1G 0 part /boot
├─nvme1n1p2 259:5 0 16G 0 part [SWAP]
└─nvme1n1p3 259:6 0 215.9G 0 part /dmesg
[18230.274339] usb 8-4: new SuperSpeed USB device number 4 using xhci_hcd
[18230.291567] usb 8-4: New USB device found, idVendor=1058, idProduct=262f, bcdDevice=50.02
[18230.291571] usb 8-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[18230.291572] usb 8-4: Product: Game Drive
[18230.291573] usb 8-4: Manufacturer: Western Digital
[18230.291574] usb 8-4: SerialNumber: 575832324436304144393037 This is a new drive that I tried to learn how to automount with. I played around with udiskie months ago, upon reboot with the drive plugged in, I would get a black screen before the bios even showed. I unplugged it and didn't worry about it for months. Now I plan on using it again, I've decided to tackle the issue. I'm not sure where to start with getting it up and running again.
I have read some of https://www.systutorials.com/docs/linux/man/8-udiskie/ to look to undo any changes (I do not recall exactly what I did). I have looked through my launch configs from .xinitrc -> i3wm -> custom launchFile.sh. None of which have "udiskie &". Any help would be amazing. Thank you in advance.
Edit1: No usb in any port works. Thought I would just test that. I know one of the usbs is a bootable arch iso, the others are not (not sure what file system). I have a windows partition I'll use worst case scenario. I'm thinking its somewhere between the input and the OS though.
Last edited by Boogz_Linux (2022-03-24 09:23:20)
Offline
No usb in any port works. Thought I would just test that. I know one of the usbs is a bootable arch iso
The most common cause is that the usb-storage module can't be loaded because you're running a kernel older than the installed one. If you just didn't reboot after an update, a reboot will fix that. Otherwise the update went wrong.
pacman -Qs linuxOffline
Thanks for the reply seth. This has cleared up that edit, although the main issue persists. Any ideas?
Edit:
pacman -Qs linux
local/linux 5.16.16.arch1-1
The Linux kernel and modulesuname -a ✔ 20:20
Linux turing 5.16.16-arch1-1 #1 SMP PREEMPT Mon, 21 Mar 2022 22:59:40 +0000 x86_64 GNU/LinuxEdit2: nevermind, resolved! Thank you
)
Last edited by Boogz_Linux (2022-03-24 09:23:02)
Offline