ProfessorHoover

joined 3 months ago
sorted by: new top controversial old
You can shove that lightsaber deep up in your Death Star. in c/memes@lemmy.world
[–] ProfessorHoover 1 points 1 hour ago

Through Fortnite. I'm not joking, they did a promotional thing with Palpatine in Fortnite.

3rd-person shooters optimized for controllers? in c/patientgamers@sh.itjust.works
[–] ProfessorHoover 3 points 2 days ago

Have you played Returnal? It's an action focussed third person shooter bullet hell roguelite. There's a story of sorts, but I'm sure you can play without acknowledging it.

The Final Final Layer_new(3) in c/programmer_humor@programming.dev
[–] ProfessorHoover 3 points 3 days ago

Probably Kernighan and Ritchie. Ritchie invented C, Kernighan teamed up with him to write the first C programming book.

Valve reportedly cooking native Linux version of Half-Life: Alyx, optimized for Steam Frame VR in c/linux_gaming@lemmy.world
[–] ProfessorHoover 1 points 1 week ago

Completely stops it launching? Most recently I could get to the main menu but would crash on loading a save, previously I could get to early quarantine zone before crashing on a level transition when I gave up. But if it's that simple I'll have to try unplugging my flight sim gear.

Proxmox host stops responding, LXC continues in c/proxmox@lemmy.world
[–] ProfessorHoover 1 points 2 weeks ago

Thanks, I have already reserved the IP address for my host.

Proxmox host stops responding, LXC continues in c/proxmox@lemmy.world
[–] ProfessorHoover 1 points 2 weeks ago (1 children)

I'm running it on both the host and the container

Proxmox host stops responding, LXC continues in c/proxmox@lemmy.world
[–] ProfessorHoover 2 points 2 weeks ago (3 children)

Thanks, I'll try that. Something odd is also happening where I just realised I can access it by tailscale, but not the local network so that narrows it down a bit, but I'll give the spare drive a go first.

Proxmox host stops responding, LXC continues in c/proxmox@lemmy.world
[–] ProfessorHoover 1 points 2 weeks ago (1 children)

I wonder if it is the same issue. I installed on an emmc module which isn't recommended by Proxmox but I thought I'd get away with it. I might try reinstalling to another drive and see if it still happens.

6
Proxmox host stops responding, LXC continues (self.proxmox)
 

I'm running Proxmox 9 on a server with currently a single LXC running. On no apparent time schedule, within a day but frequently within an hour, the host will stop responding to SSH, pings and the web UI stops updating. However, the LXC continues to run happily. The only way to bring the host back up is to power cycle the server.

Has anyone got any troubleshooting tips?

Study Boldly Claims 4K And 8K TVs Aren't Much Better Than HD To Your Eyes, But Is It True? in c/technology@lemmy.world
[–] ProfessorHoover 5 points 4 weeks ago (1 children)

You're just jealous we can breath above water, cephalopod.

Tempe Police arrest man suspected of vandalizing "Penis Man" on buildings in c/funny@sh.itjust.works
[–] ProfessorHoover 1 points 1 month ago (2 children)

Given the topic, what was so crude you had to censor the rightmost sign?

Firefly, the shinest damn show in the 'Verse in c/newcommunities@lemmy.world
[–] ProfessorHoover 2 points 2 months ago (1 children)

How so? I don't recall any canon breaks, but it has been a long time.

You are stardust. in c/science_memes@mander.xyz
[–] ProfessorHoover 1 points 2 months ago (1 children)

You might like the book Determined by Robert Sapolsky. It's very dense and I haven't gotten far into it yet but it's about the science of free will.

15
[Solved - likely hardware issue] large USB storage devices don't work since Debian 13 update (self.linuxquestions)
submitted 3 months ago* (last edited 2 months ago) by ProfessorHoover to c/linuxquestions@lemmy.zip
5 comments fedilink
 

2nd Edit: the problem was not the PSU but either the motherboard or the CPU. I installed a USB expansion card with an internal USB 3 header that has narrowed down the issue. I am aware that early Ryzen chips had issues with USB reliability, so maybe the Trixie update installed a new chipset driver that caused this. Either way I'm saving for an upgrade so hopefully won't be an issue too much longer.

Edit: I've now tested in other OSes and had the same issue. So it's probably just a poorly timed hardware issue.

Since I updated my desktop to Debian 13, my external SSDs (Over 1TB) are only detected by gnome-disks as "no media". They also bring down my other USB drives if I leave the unrecognised SSDs plugged in while trying to make other transfers. All these drives work in Debian 12 on my laptop.

I've checked dmesg for my external SSD:

`[ 1801.737164] usb 1-4: new high-speed USB device number 7 using xhci_hcd

[ 1801.909543] usb 1-4: New USB device found, idVendor=152d, idProduct=0580, bcdDevice= 2.14

[ 1801.909549] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 1801.909551] usb 1-4: Product: PX10

[ 1801.909552] usb 1-4: Manufacturer: SP

[ 1801.909554] usb 1-4: SerialNumber: 2405185321200000000D

[ 1801.946647] scsi host41: uas

[ 1801.947031] scsi 41:0:0:0: Direct-Access SP PX10 0214 PQ: 0 ANSI: 6

[ 1801.949657] sd 41:0:0:0: Attached scsi generic sg7 type 0

[ 1803.041153] usb 2-3: USB disconnect, device number 2

[ 1813.106975] sd 41:0:0:0: [sdg] Unit Not Ready

[ 1813.106981] sd 41:0:0:0: [sdg] Sense Key : Hardware Error [current]

[ 1813.106984] sd 41:0:0:0: [sdg] ASC=0x44 <>ASCQ=0x81

[ 1813.107229] sd 41:0:0:0: [sdg] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK

[ 1813.107232] sd 41:0:0:0: [sdg] Sense Key : Hardware Error [current]

[ 1813.107235] sd 41:0:0:0: [sdg] ASC=0x44 <>ASCQ=0x81

[ 1813.107549] sd 41:0:0:0: [sdg] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK

[ 1813.107552] sd 41:0:0:0: [sdg] Sense Key : Hardware Error [current]

[ 1813.107555] sd 41:0:0:0: [sdg] ASC=0x44 <>ASCQ=0x81

[ 1813.107631] sd 41:0:0:0: [sdg] 0 512-byte logical blocks: (0 B/0 B)

[ 1813.107634] sd 41:0:0:0: [sdg] 0-byte physical blocks

[ 1813.107872] sd 41:0:0:0: [sdg] Test WP failed, assume Write Enabled

[ 1813.107952] sd 41:0:0:0: [sdg] Asking for cache data failed

[ 1813.107955] sd 41:0:0:0: [sdg] Assuming drive cache: write through

[ 1813.108195] sd 41:0:0:0: [sdg] Preferred minimum I/O size 4096 bytes not a multiple of physical block size (0 bytes)

[ 1813.108198] sd 41:0:0:0: [sdg] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes)

[ 1813.108560] sd 41:0:0:0: [sdg] Attached SCSI disk`

I'd assume the issue is corruption in my SSD, but it's happening with two different drives.

view more: next ›