TheButtonJustSpins

joined 3 years ago

LFG!!

Considering how many people said his name the past couple days, this was clearly coming. Now just need the secret ballots to go the right way.

[–] TheButtonJustSpins@infosec.pub 38 points 1 day ago (6 children)

Connected glasses. I'm all for privacy-respecting HUD that connects to your phone, I think that's cool. But recording others? Connecting it to Meta? Fuck that.

[–] TheButtonJustSpins@infosec.pub 9 points 3 days ago (1 children)

Do you like hanging out with friends? Imagine you're also related to them.

[–] TheButtonJustSpins@infosec.pub 4 points 4 days ago (1 children)

The end of the 2026 midterms last week marked the unofficial start of the 2028 election cycle,

😭

Long term, 2 is best, but 1 is a great immediate fix. Also, you should be able to assign a static IP based on the printers MAC address, which will keep the IP stable.

[–] TheButtonJustSpins@infosec.pub 11 points 5 days ago (1 children)

Soon-to-be Democratic Speaker of the House Hakeem Jeffries

I sure hope not.

[–] TheButtonJustSpins@infosec.pub 1 points 1 week ago* (last edited 1 week ago)

I'm not saying that crimes are violence - I'm saying that punishing crimes can only happen because the state threatens violence.

[–] TheButtonJustSpins@infosec.pub 1 points 1 week ago (2 children)

What is the goal of prosecuting the crimes? To put people in prison. Why do people go to prison? Not because someone says so. Because the group sending you to prison can apply violence to you. All governing is through inherent threat of violence. We as a society agree when that's appropriate. (Or, that's how it should work. Right now, in the US, money decides.)

I'd prefer no violence. Since that's currently not an option, I prefer the violence be pointed at oppressors like Kirk. Nothing of value was lost.

[–] TheButtonJustSpins@infosec.pub 1 points 1 week ago (4 children)

Any punishments are applied by threat of violence. For the purposes of this discussion, I'm not sure that distinguishing between threat of violence and applied violence makes you against any form of violence.

[–] TheButtonJustSpins@infosec.pub 133 points 1 week ago (12 children)

Punch up, not down. Violence used to fight for freedom and against an oppressor: good. Violence by the state: bad. This is not an inconsistent position.

17
Proxmox Crash (infosec.pub)
submitted 1 month ago* (last edited 1 month ago) by TheButtonJustSpins@infosec.pub to c/selfhosted@lemmy.world
 

My new-this-year MS-02 crashed tonight, so I'm going through journalctl -b -1 -p warning -r and I see a bunch of this repeated over and over going back for days:

Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4:    [20] UnsupReq              
Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00300000/00000000
Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Requester ID)
Oct 12 23:59:49 proxmox-06 kernel: aer_ratelimit: 119 callbacks suppressed
Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4:    [15] HeaderOF              
Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00008000/00002000
Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Correctable, type=Transaction Layer, (Receiver ID)
Oct 12 23:59:49 proxmox-06 kernel: aer_ratelimit: 119 callbacks suppressed

Does this mean one of the SSDs is failing already? I have 1 Crucial P310 4TB SSD for the main drive and another for backups.

=== START OF INFORMATION SECTION ===
Model Number:                       CT4000P310SSD8
Serial Number:                      25465454F087
Firmware Version:                   V8CR010
PCI Vendor/Subsystem ID:            0xc0a9
IEEE OUI Identifier:                0x00a075
Controller ID:                      0
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          4,000,787,030,016 [4.00 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            00a075 015454f087
Local Time is:                      Tue Oct 13 00:30:43 2026 EDT
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x00d7):     Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp Verify
Log Page Attributes (0x1e):         Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg
Maximum Data Transfer Size:         64 Pages
Warning  Comp. Temp. Threshold:     86 Celsius
Critical Comp. Temp. Threshold:     88 Celsius
Namespace 1 Features (0x18):        No_ID_Reuse NP_Fields

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     6.30W       -        -    0  0  0  0        0       0
 1 +     2.40W       -        -    1  1  1  1        0       0
 2 +     1.50W       -        -    2  2  2  2        0       0
 3 -   0.0300W       -        -    3  3  3  3     1500    5000
 4 -   0.0025W       -        -    4  4  4  4     5000   30000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0
 1 -    4096       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning:                   0x00
Temperature:                        41 Celsius
Available Spare:                    100%
Available Spare Threshold:          5%
Percentage Used:                    1%
Data Units Read:                    428,281,946 [219 TB]
Data Units Written:                 44,641,186 [22.8 TB]
Host Read Commands:                 15,033,643,064
Host Write Commands:                1,728,938,256
Controller Busy Time:               25,445
Power Cycles:                       24
Power On Hours:                     3,255
Unsafe Shutdowns:                   18
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               41 Celsius

Error Information (NVMe Log 0x01, 16 of 255 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06, NSID 0xffffffff)
Self-test status: No self-test in progress
No Self-tests Logged
=== START OF INFORMATION SECTION ===
Model Number:                       CT4000P310SSD8
Serial Number:                      2545543AD7B7
Firmware Version:                   V8CR010
PCI Vendor/Subsystem ID:            0xc0a9
IEEE OUI Identifier:                0x00a075
Controller ID:                      0
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          4,000,787,030,016 [4.00 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            00a075 01543ad7b7
Local Time is:                      Tue Oct 13 00:28:48 2026 EDT
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x00d7):     Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp Verify
Log Page Attributes (0x1e):         Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg
Maximum Data Transfer Size:         64 Pages
Warning  Comp. Temp. Threshold:     86 Celsius
Critical Comp. Temp. Threshold:     88 Celsius
Namespace 1 Features (0x18):        No_ID_Reuse NP_Fields

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     6.30W       -        -    0  0  0  0        0       0
 1 +     2.40W       -        -    1  1  1  1        0       0
 2 +     1.50W       -        -    2  2  2  2        0       0
 3 -   0.0300W       -        -    3  3  3  3     1500    5000
 4 -   0.0025W       -        -    4  4  4  4     5000   30000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0
 1 -    4096       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning:                   0x00
Temperature:                        38 Celsius
Available Spare:                    100%
Available Spare Threshold:          5%
Percentage Used:                    6%
Data Units Read:                    2,161,355 [1.10 TB]
Data Units Written:                 154,163,444 [78.9 TB]
Host Read Commands:                 8,882,927
Host Write Commands:                610,221,348
Controller Busy Time:               2,682
Power Cycles:                       24
Power On Hours:                     3,278
Unsafe Shutdowns:                   18
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               38 Celsius

Error Information (NVMe Log 0x01, 16 of 255 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06, NSID 0xffffffff)
Self-test status: No self-test in progress
No Self-tests Logged
 

Any idea why Lidarr can't find https://musicbrainz.org/release-group/165b34c9-6132-4632-b1f4-981f51f87235 ? It finds the other four albums but not this one.

 

Is it possible to add a SoundStack radio station to Symfonium? I can't figure out the URL to use.

I'm trying to add Kapa Radio: https://live.mystreamplayer.com/pmghawaii?station=KAPAFM

 

Clarification: pills that are smaller in size and thus easier to swallow.

 

New to CircuitPython, this feels like it should work according to the docs but it prints six Falses. Any ideas?

#!/usr/bin/env python
import board
import digitalio
import time

class body_controller:

  def __init__(self):
    SWDIO = board.D5
    self._reset_pin = digitalio.DigitalInOut(SWDIO)
    print(self._reset_pin.value)
    self._reset_pin.switch_to_output(True)
    print(self._reset_pin.value)

  def turn_on(self):
    print(self._reset_pin.value)
    self._reset_pin.value = False
    print(self._reset_pin.value)
    time.sleep(1)
    print(self._reset_pin.value)
    self._reset_pin.value = True
    print(self._reset_pin.value)

body = body_controller()
time.sleep(1)
body.turn_on()
time.sleep(1)
 

This happens if I use set_time or set_position. Is this typical, or am I just not doing it right?

This is on a Pi Zero 2 W, so not the most powerful, but should be able to handle this.

These are the relevant bits of how I'm setting up the player:

    self._vlc = vlc.Instance()
    self._player = self._vlc.media_player_new()
    self._list_player = self._vlc.media_list_player_new()
    self._list_player.set_media_player(self._player)

    playlist = self._vlc.media_list_new()
    for index in self._play_order:
      playlist.add_media(self._vlc.media_new_path(self._songs[index]))

    self._list_player.stop()
    self._list_player.set_media_list(playlist)
    self._list_player.play()

And trying to seek is just this:

    self._player.set_time(_s_to_ms(seconds))

Any ideas would be greatly appreciated!

 

I have a Keybow MINI hooked up to a Raspberry Pi Zero W, and I'm using Python to respond to events. I have one button that kicks off playing a song on a passive buzzer, and I'm wondering if there's a way to have a button press stop the song before it completes.

 

Do anyone else's wrist hairs get caught in the little gap between the frame and the trackpad/spacers?

 

Does anyone know if it's possible to have events from the Keybow keyboard cause effects on the Pi Zero W running the keyboard instead of outputting to another machine? Or do I need to go with a different OS and figure out the handling of the keys myself?

 

Anyone have a list of changes that they've made to increase battery life? I've got about three hours (with 80% limit in BIOS, which I might get rid of), so I'm sure there's a lot that can be changed.

 

I know the drivers come in the distro package manager, but, is there a set straight from AMD? Trying to use Brave causes freezes and black screen flashes, which I'm pretty sure is a driver thing.

 

Is there any way to complete the Outpost Control job? It's that only (non-First Order) job I haven't completed, and I'm not sure how to. I thought maybe I'd need to install and retrieve the skimmer, but I did that today and it didn't progress the job chat.

Edit: I've tried installing defenses on every panel, but that also didn't work. Next time I'm on planet, I'll try installing the skimmer and leaving it long enough to gather some credits.

Edit2: Okay, I think maybe it doesn't actually complete until one faction gains control of the outpost for the day, and not enough people play for that to happen. Damn.

view more: next ›