LyD

joined 2 years ago
[–] LyD@lemmy.ca 3 points 12 hours ago
I solved the daily #CluesBySam, Feb 1st 2026 (Hard), in less than 15 minutes
🟨🟩🟩🟩
🟨🟩🟩🟩
🟩🟩🟩🟩
🟩🟩🟩🟩
🟩🟩🟩🟩
https://cluesbysam.com/
[–] LyD@lemmy.ca 3 points 1 day ago
I solved the daily #CluesBySam, Jan 31st 2026 (Hard), in less than 16 minutes
🟩🟩🟩🟩
🟩🟩🟩🟩
🟩🟩🟨🟩
🟩🟩🟩🟩
🟩🟩🟩🟩
https://cluesbysam.com/
[–] LyD@lemmy.ca 3 points 3 days ago
I solved the daily #CluesBySam, Jan 29th 2026 (Tricky), in less than 11 minutes
🟩🟩🟩🟩
🟩🟩🟩🟩
🟩🟩🟩🟩
🟩🟩🟩🟩
🟩🟩🟩🟩
https://cluesbysam.com/
[–] LyD@lemmy.ca 1 points 4 days ago
I solved the daily #CluesBySam, Jan 28th 2026 (Tricky), in less than 14 minutes
🟩🟩🟩🟩
🟩🟩🟩🟩
🟩🟩🟩🟩
🟩🟩🟩🟩
🟩🟩🟩🟩
https://cluesbysam.com/
[–] LyD@lemmy.ca 1 points 4 days ago (1 children)

Both Tyler, our paid test solver, and Kelsey, my wife, our unpaid test solver, read PUTTING as PUTTING and not PUTTING. Odds are you did too. Just remember: PUTTING can be pronounced PUTTING or PUTTING.

[–] LyD@lemmy.ca 1 points 6 days ago
I solved the daily #CluesBySam, Jan 26th 2026 (Easy), in 03:41
🟩🟩🟩🟩
🟩🟩🟩🟩
🟩🟩🟩🟩
🟩🟩🟩🟩
🟩🟩🟩🟩
https://cluesbysam.com/
[–] LyD@lemmy.ca 1 points 1 week ago

I got Hexcodle #899 in 4! Score: 69%

β«πŸ”ΌπŸ”ΌπŸ”½πŸ”½β« β«βœ…βœ…πŸ”ΌπŸ”½πŸ”½ πŸ”Όβ¬βœ…πŸ”½βœ…βœ… βœ…βœ…βœ…βœ…βœ…βœ…

https://hexcodle.com/

[–] LyD@lemmy.ca 3 points 1 week ago (1 children)
[–] LyD@lemmy.ca 1 points 1 week ago (1 children)

Thanks for the help. If it's the hardware then it's the hardware. I will try a few more things like booting from the drive in a different PC, but I may have to spend some money.

[–] LyD@lemmy.ca 1 points 1 week ago (3 children)

Checked the logs in Windows, you're right! A corrected hardware error has occurred from PCI Express Root Port. I reseated the drive with no change.

I should mention that this laptop has always had issues with what I assumed to be thermal throttling. It would play games fine for 10-15 minutes before becoming a slideshow. I eventually stopped trying.

I have set that option and I am currently downloading a GPU benchmark. Is that an appropriate test? What should I be looking for in dmesg?

[–] LyD@lemmy.ca 2 points 1 week ago (5 children)

Installed Linux Mint on my old personal laptop (Dell XPS 9560) and unfortunately ran into some issues that made me switch back to Windows. I really want to make it work

It seems to have revealed either a hardware bug or failing hardware in the NVMe drive.

First problem was log spam that filled up the partition:

spoiler

2025-12-29T12:15:46.439880-05:00 redacted kernel: pcieport 0000:00:1d.0: AER: Correctable error message received from 0000:04:00.0
2025-12-29T12:15:46.439934-05:00 redacted kernel: nvme 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
2025-12-29T12:15:46.439936-05:00 redacted kernel: nvme 0000:04:00.0:   device [126f:2262] error status/mask=00000001/0000e000
2025-12-29T12:15:46.439938-05:00 redacted kernel: nvme 0000:04:00.0:    [ 0] RxErr                  (First)
2025-12-29T12:15:46.439939-05:00 redacted kernel: pcieport 0000:00:1d.0: AER: Multiple Correctable error message received from 0000:04:00.0
2025-12-29T12:15:46.439940-05:00 redacted kernel: pcieport 0000:00:1d.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
2025-12-29T12:15:46.439941-05:00 redacted kernel: pcieport 0000:00:1d.0:   device [8086:a118] error status/mask=00001000/00000000
2025-12-29T12:15:46.439943-05:00 redacted kernel: pcieport 0000:00:1d.0:    [12] Timeout               
2025-12-29T12:15:46.439944-05:00 redacted kernel: nvme 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
2025-12-29T12:15:46.439945-05:00 redacted kernel: nvme 0000:04:00.0:   device [126f:2262] error status/mask=00000001/0000e000
2025-12-29T12:15:46.439946-05:00 redacted kernel: nvme 0000:04:00.0:    [ 0] RxErr                  (First)

Some forum posts I found (example) suggested that this was a hardware bug and I could set pcie_aspm=off in grub to work around it. This stopped the log spam and everything seemed to be working fine.

Later while I was doing some programming, everything froze for a while. When it came back, the partition was set to readonly. It wouldn't boot on restart and loaded up busybox instead. I was able to set it to writable, but it happened again soon after.

I decided to switch back to Windows where there doesn't seem to be any issues.

I really want to make it work. If it's failing hardware then I have no choice but to replace the drive, but if it's just a bug then I want to find a fix without buying new hardware. That would kind of defeat the point for me and I don't want to spend the money.

I would appreciate any help. I booted into Mint again to grab the logs and I really want to keep using it.

[–] LyD@lemmy.ca 1 points 1 week ago
Crossherd #320
β¬›οΈπŸŸ©πŸŸ©πŸŸ©πŸŸ©
β¬›οΈπŸŸ©πŸŸ©πŸŸ©πŸŸ©
🟩🟩🟩🟩🟩
πŸŸ©πŸŸ©πŸŸ©πŸŸ©β¬›οΈ
πŸŸ©πŸŸ©πŸŸ©πŸŸ©β¬›οΈ
Time: 0:39
crossherd.clevergoat.com 🐐
 
 
 

Pretty cool that they're doing a separate game like this. I wonder if there will be VR support.

view more: next β€Ί