home.social

#supermicro — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #supermicro, aggregated by home.social.

  1. SK Telecom, Supermicro and Schneider Electric Sign MOU on Total Solutions for AI Data Center Deployment

    – Collaborate on adoption of a pre-fabricated modular model for integrated server and infrastructure design – Accelerated artificial…
    #France #FR #Europe #EU #SchneiderElectric #AIcompany #AIDC #datacenters #modulardesign #SKTelecom #Supermicro
    europesays.com/france/20680/

  2. Schneider Electric Links AI Data Center Growth With Sustainability Focus

    Track your investments for FREE with Simply Wall St, the portfolio command center trusted by over 7 million…
    #France #FR #Europe #EU #SchneiderElectric #datacenter #SKTelecom #Supermicro #sustainabilityprojects #sustainableprocurement
    europesays.com/france/20639/

  3. Taiwan prosecutors investigate 3 people over Nvidia chip smuggling to China

    Authorities in Taiwan are investigating three people on suspicion of using forged documents to smuggle computer servers c…
    #Conflict #Conflicts #War #California #California-basedSuperMicroComputerInc #China #ChinaTaiwanConflicts #export #HongKong #KeelungDistrictProsecutorsOffice #macao #Nvidia #NvidiaandSuperMicro #SanJose #Servers #smuggle #supermicro #SuperMicroComputerInc. #Taiwan
    europesays.com/3007370/

  4. US Said to Suspect Nvidia Chips Smuggled to Alibaba Via Thailand

    (Bloomberg) — A key company behind Thailand’s national AI effort is suspected of helping to smuggle billions of…
    #NewsBeep #News #Artificialintelligence #AI #ArtificialIntelligence #Bloomberg #CA #Canada #Nvidia #OBON #SuperMicro #Technology #Thailand
    newsbeep.com/ca/658950/

  5. US Said to Suspect Nvidia Chips Smuggled to Alibaba Via Thailand

    (Bloomberg) — A key company behind Thailand’s national AI effort is suspected of helping to smuggle billions of…
    #NewsBeep #News #US #USA #UnitedStates #UnitedStatesOfAmerica #Artificialintelligence #AI #ArtificialIntelligence #Bloomberg #NVIDIA #OBON #SuperMicro #Technology #Thailand
    newsbeep.com/us/632491/

  6. @tj @DianeBruce @tykling We need someone to #Depenguinate #ONIE switches, or at least get #FreeBSD installing on them. Achieving #Broadcom #OpenBCM support is another task. x86 would be easier. I have two #x86 ONIE switches in .UK bootmarked but the #HPE #Alto product line and #Supermicro #whitebox switches are where to look.

  7. @tj @DianeBruce @tykling We need someone to #Depenguinate #ONIE switches, or at least get #FreeBSD installing on them. Achieving #Broadcom #OpenBCM support is another task. x86 would be easier. I have two #x86 ONIE switches in .UK bootmarked but the #HPE #Alto product line and #Supermicro #whitebox switches are where to look.

  8. @tj @DianeBruce @tykling We need someone to #Depenguinate #ONIE switches, or at least get #FreeBSD installing on them. Achieving #Broadcom #OpenBCM support is another task. x86 would be easier. I have two #x86 ONIE switches in .UK bootmarked but the #HPE #Alto product line and #Supermicro #whitebox switches are where to look.

  9. @tj @DianeBruce @tykling We need someone to #Depenguinate #ONIE switches, or at least get #FreeBSD installing on them. Achieving #Broadcom #OpenBCM support is another task. x86 would be easier. I have two #x86 ONIE switches in .UK bootmarked but the #HPE #Alto product line and #Supermicro #whitebox switches are where to look.

  10. @tj @DianeBruce @tykling We need someone to #Depenguinate #ONIE switches, or at least get #FreeBSD installing on them. Achieving #Broadcom #OpenBCM support is another task. x86 would be easier. I have two #x86 ONIE switches in .UK bootmarked but the #HPE #Alto product line and #Supermicro #whitebox switches are where to look.

  11. It is really petty and ridiculous that on H12 platforms #SuperMicro no longer allows virtual media from the console.

    To install a system you need a license¹ unless you go and stick a USB stick in it.

    I find it ridiculous that you pay for a stupid PC *server*² and then need to stick a USB in it to be able to install… where do they think you install servers? They know full well that you will need to get either remote hands or pay for a license. What else could you possibly want IPMI for?

    __
    ¹ on H12 you cannot use the various tools to generate a license as the license file JSON is now digitally signed by SuperMicro…
    ² stupid because PC servers are not really servers, just headless PCs with all that goes with it. I hate PC design, crap from a IBM cheap thing still with us.

  12. It is really petty and ridiculous that on H12 platforms #SuperMicro no longer allows virtual media from the console.

    To install a system you need a license¹ unless you go and stick a USB stick in it.

    I find it ridiculous that you pay for a stupid PC *server*² and then need to stick a USB in it to be able to install… where do they think you install servers? They know full well that you will need to get either remote hands or pay for a license. What else could you possibly want IPMI for?

    __
    ¹ on H12 you cannot use the various tools to generate a license as the license file JSON is now digitally signed by SuperMicro…
    ² stupid because PC servers are not really servers, just headless PCs with all that goes with it. I hate PC design, crap from a IBM cheap thing still with us.

  13. It is really petty and ridiculous that on H12 platforms #SuperMicro no longer allows virtual media from the console.

    To install a system you need a license¹ unless you go and stick a USB stick in it.

    I find it ridiculous that you pay for a stupid PC *server*² and then need to stick a USB in it to be able to install… where do they think you install servers? They know full well that you will need to get either remote hands or pay for a license. What else could you possibly want IPMI for?

    __
    ¹ on H12 you cannot use the various tools to generate a license as the license file JSON is now digitally signed by SuperMicro…
    ² stupid because PC servers are not really servers, just headless PCs with all that goes with it. I hate PC design, crap from a IBM cheap thing still with us.

  14. It is really petty and ridiculous that on H12 platforms #SuperMicro no longer allows virtual media from the console.

    To install a system you need a license¹ unless you go and stick a USB stick in it.

    I find it ridiculous that you pay for a stupid PC *server*² and then need to stick a USB in it to be able to install… where do they think you install servers? They know full well that you will need to get either remote hands or pay for a license. What else could you possibly want IPMI for?

    __
    ¹ on H12 you cannot use the various tools to generate a license as the license file JSON is now digitally signed by SuperMicro…
    ² stupid because PC servers are not really servers, just headless PCs with all that goes with it. I hate PC design, crap from a IBM cheap thing still with us.

  15. It is really petty and ridiculous that on H12 platforms #SuperMicro no longer allows virtual media from the console.

    To install a system you need a license¹ unless you go and stick a USB stick in it.

    I find it ridiculous that you pay for a stupid PC *server*² and then need to stick a USB in it to be able to install… where do they think you install servers? They know full well that you will need to get either remote hands or pay for a license. What else could you possibly want IPMI for?

    __
    ¹ on H12 you cannot use the various tools to generate a license as the license file JSON is now digitally signed by SuperMicro…
    ² stupid because PC servers are not really servers, just headless PCs with all that goes with it. I hate PC design, crap from a IBM cheap thing still with us.

  16. > BIOS can't pass the secure validation.

    #SuperMicro great, they of course had to implement a bios validation to prevent me from just patching in the ReBAR support...

    So where is my in-circuit flasher? And where is the bios chip on the H11DSi?

    #BIOS #UEFI

  17. > BIOS can't pass the secure validation.

    #SuperMicro great, they of course had to implement a bios validation to prevent me from just patching in the ReBAR support...

    So where is my in-circuit flasher? And where is the bios chip on the H11DSi?

    #BIOS #UEFI

  18. > BIOS can't pass the secure validation.

    #SuperMicro great, they of course had to implement a bios validation to prevent me from just patching in the ReBAR support...

    So where is my in-circuit flasher? And where is the bios chip on the H11DSi?

    #BIOS #UEFI

  19. > BIOS can't pass the secure validation.

    #SuperMicro great, they of course had to implement a bios validation to prevent me from just patching in the ReBAR support...

    So where is my in-circuit flasher? And where is the bios chip on the H11DSi?

    #BIOS #UEFI

  20. > BIOS can't pass the secure validation.

    #SuperMicro great, they of course had to implement a bios validation to prevent me from just patching in the ReBAR support...

    So where is my in-circuit flasher? And where is the bios chip on the H11DSi?

    #BIOS #UEFI

  21. I wanted to add a button to Home Assistant that would turn on my remote server via IPMI. I also did not want to add the ipmitool dependencies to my #HASS container. Since IPMI supports redfish, a simple rest command in home assistant is enough. Add this to your `configuration.yaml`:

    ```yaml
    rest_command:
    # Command to turn the server ON
    server_power_on:
    url: "https://192.168.100.111/redfish/v1/Systems/1/Actions/ComputerSystem.Reset"
    method: post
    username: "hass"
    password: "eX4mP13p455w0Rd"
    verify_ssl: false
    headers:
    Content-Type: "application/json"
    payload: '{"ResetType": "On"}'

    # Command to gracefully shut down the OS via IPMI (ACPI signal)
    server_power_off:
    url: "https://192.168.100.111/redfish/v1/Systems/1/Actions/ComputerSystem.Reset"
    method: post
    username: "hass"
    password: "eX4mP13p455w0Rd"
    verify_ssl: false
    headers:
    Content-Type: "application/json"
    payload: '{"ResetType": "GracefulShutdown"}'

    sensor:
    - platform: rest
    name: "Server Power State"
    resource: "https://192.168.100.111/redfish/v1/Systems/1"
    method: GET
    username: "hass"
    password: "eX4mP13p455w0Rd"
    verify_ssl: false
    scan_interval: 10 # Checks every 10 seconds
    value_template: "{{ value_json.PowerState }}"

    template:
    - switch:
    - name: "Server"
    state: "{{ is_state('sensor.server_power_state', 'On') }}"
    icon: >-
    {% if is_state('sensor.server_power_state', 'On') %}
    mdi:server-network
    {% else %}
    mdi:server-network-off
    {% endif %}
    turn_on:
    action: rest_command.server_power_on
    turn_off:
    action: rest_command.server_power_off

    ```

    Make sure to create a separate IPMI user with "Operator" privileges (allowed to start/shutdown, but not to modify settings). If you have e.g. #Proxmox on the server, it will receive the IPMI Graceful Shutdown command and cleanly stop all VMs before exiting.

    Works great!

    #hass #homeassistant #redfish #api #ipmi #supermicro #homelab

  22. I wanted to add a button to Home Assistant that would turn on my remote server via IPMI. I also did not want to add the ipmitool dependencies to my #HASS container. Since IPMI supports redfish, a simple rest command in home assistant is enough. Add this to your `configuration.yaml`:

    ```yaml
    rest_command:
    # Command to turn the server ON
    server_power_on:
    url: "https://192.168.100.111/redfish/v1/Systems/1/Actions/ComputerSystem.Reset"
    method: post
    username: "hass"
    password: "eX4mP13p455w0Rd"
    verify_ssl: false
    headers:
    Content-Type: "application/json"
    payload: '{"ResetType": "On"}'

    # Command to gracefully shut down the OS via IPMI (ACPI signal)
    server_power_off:
    url: "https://192.168.100.111/redfish/v1/Systems/1/Actions/ComputerSystem.Reset"
    method: post
    username: "hass"
    password: "eX4mP13p455w0Rd"
    verify_ssl: false
    headers:
    Content-Type: "application/json"
    payload: '{"ResetType": "GracefulShutdown"}'

    sensor:
    - platform: rest
    name: "Server Power State"
    resource: "https://192.168.100.111/redfish/v1/Systems/1"
    method: GET
    username: "hass"
    password: "eX4mP13p455w0Rd"
    verify_ssl: false
    scan_interval: 10 # Checks every 10 seconds
    value_template: "{{ value_json.PowerState }}"

    template:
    - switch:
    - name: "Server"
    state: "{{ is_state('sensor.server_power_state', 'On') }}"
    icon: >-
    {% if is_state('sensor.server_power_state', 'On') %}
    mdi:server-network
    {% else %}
    mdi:server-network-off
    {% endif %}
    turn_on:
    action: rest_command.server_power_on
    turn_off:
    action: rest_command.server_power_off

    ```

    Make sure to create a separate IPMI user with "Operator" privileges (allowed to start/shutdown, but not to modify settings). If you have e.g. #Proxmox on the server, it will receive the IPMI Graceful Shutdown command and cleanly stop all VMs before exiting.

    Works great!

    #hass #homeassistant #redfish #api #ipmi #supermicro #homelab

  23. I wanted to add a button to Home Assistant that would turn on my remote server via IPMI. I also did not want to add the ipmitool dependencies to my #HASS container. Since IPMI supports redfish, a simple rest command in home assistant is enough. Add this to your `configuration.yaml`:

    ```yaml
    rest_command:
    # Command to turn the server ON
    server_power_on:
    url: "https://192.168.100.111/redfish/v1/Systems/1/Actions/ComputerSystem.Reset"
    method: post
    username: "hass"
    password: "eX4mP13p455w0Rd"
    verify_ssl: false
    headers:
    Content-Type: "application/json"
    payload: '{"ResetType": "On"}'

    # Command to gracefully shut down the OS via IPMI (ACPI signal)
    server_power_off:
    url: "https://192.168.100.111/redfish/v1/Systems/1/Actions/ComputerSystem.Reset"
    method: post
    username: "hass"
    password: "eX4mP13p455w0Rd"
    verify_ssl: false
    headers:
    Content-Type: "application/json"
    payload: '{"ResetType": "GracefulShutdown"}'

    sensor:
    - platform: rest
    name: "Server Power State"
    resource: "https://192.168.100.111/redfish/v1/Systems/1"
    method: GET
    username: "hass"
    password: "eX4mP13p455w0Rd"
    verify_ssl: false
    scan_interval: 10 # Checks every 10 seconds
    value_template: "{{ value_json.PowerState }}"

    template:
    - switch:
    - name: "Server"
    state: "{{ is_state('sensor.server_power_state', 'On') }}"
    icon: >-
    {% if is_state('sensor.server_power_state', 'On') %}
    mdi:server-network
    {% else %}
    mdi:server-network-off
    {% endif %}
    turn_on:
    action: rest_command.server_power_on
    turn_off:
    action: rest_command.server_power_off

    ```

    Make sure to create a separate IPMI user with "Operator" privileges (allowed to start/shutdown, but not to modify settings). If you have e.g. #Proxmox on the server, it will receive the IPMI Graceful Shutdown command and cleanly stop all VMs before exiting.

    Works great!

    #hass #homeassistant #redfish #api #ipmi #supermicro #homelab

  24. I wanted to add a button to Home Assistant that would turn on my remote server via IPMI. I also did not want to add the ipmitool dependencies to my #HASS container. Since IPMI supports redfish, a simple rest command in home assistant is enough. Add this to your `configuration.yaml`:

    ```yaml
    rest_command:
    # Command to turn the server ON
    server_power_on:
    url: "https://192.168.100.111/redfish/v1/Systems/1/Actions/ComputerSystem.Reset"
    method: post
    username: "hass"
    password: "eX4mP13p455w0Rd"
    verify_ssl: false
    headers:
    Content-Type: "application/json"
    payload: '{"ResetType": "On"}'

    # Command to gracefully shut down the OS via IPMI (ACPI signal)
    server_power_off:
    url: "https://192.168.100.111/redfish/v1/Systems/1/Actions/ComputerSystem.Reset"
    method: post
    username: "hass"
    password: "eX4mP13p455w0Rd"
    verify_ssl: false
    headers:
    Content-Type: "application/json"
    payload: '{"ResetType": "GracefulShutdown"}'

    sensor:
    - platform: rest
    name: "Server Power State"
    resource: "https://192.168.100.111/redfish/v1/Systems/1"
    method: GET
    username: "hass"
    password: "eX4mP13p455w0Rd"
    verify_ssl: false
    scan_interval: 10 # Checks every 10 seconds
    value_template: "{{ value_json.PowerState }}"

    template:
    - switch:
    - name: "Server"
    state: "{{ is_state('sensor.server_power_state', 'On') }}"
    icon: >-
    {% if is_state('sensor.server_power_state', 'On') %}
    mdi:server-network
    {% else %}
    mdi:server-network-off
    {% endif %}
    turn_on:
    action: rest_command.server_power_on
    turn_off:
    action: rest_command.server_power_off

    ```

    Make sure to create a separate IPMI user with "Operator" privileges (allowed to start/shutdown, but not to modify settings). If you have e.g. #Proxmox on the server, it will receive the IPMI Graceful Shutdown command and cleanly stop all VMs before exiting.

    Works great!

    #hass #homeassistant #redfish #api #ipmi #supermicro #homelab

  25. I wanted to add a button to Home Assistant that would turn on my remote server via IPMI. I also did not want to add the ipmitool dependencies to my #HASS container. Since IPMI supports redfish, a simple rest command in home assistant is enough. Add this to your `configuration.yaml`:

    ```yaml
    rest_command:
    # Command to turn the server ON
    server_power_on:
    url: "https://192.168.100.111/redfish/v1/Systems/1/Actions/ComputerSystem.Reset"
    method: post
    username: "hass"
    password: "eX4mP13p455w0Rd"
    verify_ssl: false
    headers:
    Content-Type: "application/json"
    payload: '{"ResetType": "On"}'

    # Command to gracefully shut down the OS via IPMI (ACPI signal)
    server_power_off:
    url: "https://192.168.100.111/redfish/v1/Systems/1/Actions/ComputerSystem.Reset"
    method: post
    username: "hass"
    password: "eX4mP13p455w0Rd"
    verify_ssl: false
    headers:
    Content-Type: "application/json"
    payload: '{"ResetType": "GracefulShutdown"}'

    sensor:
    - platform: rest
    name: "Server Power State"
    resource: "https://192.168.100.111/redfish/v1/Systems/1"
    method: GET
    username: "hass"
    password: "eX4mP13p455w0Rd"
    verify_ssl: false
    scan_interval: 10 # Checks every 10 seconds
    value_template: "{{ value_json.PowerState }}"

    template:
    - switch:
    - name: "Server"
    state: "{{ is_state('sensor.server_power_state', 'On') }}"
    icon: >-
    {% if is_state('sensor.server_power_state', 'On') %}
    mdi:server-network
    {% else %}
    mdi:server-network-off
    {% endif %}
    turn_on:
    action: rest_command.server_power_on
    turn_off:
    action: rest_command.server_power_off

    ```

    Make sure to create a separate IPMI user with "Operator" privileges (allowed to start/shutdown, but not to modify settings). If you have e.g. #Proxmox on the server, it will receive the IPMI Graceful Shutdown command and cleanly stop all VMs before exiting.

    Works great!

    #hass #homeassistant #redfish #api #ipmi #supermicro #homelab

  26. Oh great, I cannot execute their "saa" support tool because of #NixOS "things"...

    Could not start dynamically linked executable: ./saa
    NixOS cannot run dynamically linked executables intended for generic
    linux environments out of the box. For more information, see:
    nix.dev/permalink/stub-ld

    #Linux #SuperMicro

  27. Oh great, I cannot execute their "saa" support tool because of #NixOS "things"...

    Could not start dynamically linked executable: ./saa
    NixOS cannot run dynamically linked executables intended for generic
    linux environments out of the box. For more information, see:
    nix.dev/permalink/stub-ld

    #Linux #SuperMicro

  28. Oh great, I cannot execute their "saa" support tool because of #NixOS "things"...

    Could not start dynamically linked executable: ./saa
    NixOS cannot run dynamically linked executables intended for generic
    linux environments out of the box. For more information, see:
    nix.dev/permalink/stub-ld

    #Linux #SuperMicro

  29. Oh great, I cannot execute their "saa" support tool because of #NixOS "things"...

    Could not start dynamically linked executable: ./saa
    NixOS cannot run dynamically linked executables intended for generic
    linux environments out of the box. For more information, see:
    nix.dev/permalink/stub-ld

    #Linux #SuperMicro

  30. Oh great, I cannot execute their "saa" support tool because of #NixOS "things"...

    Could not start dynamically linked executable: ./saa
    NixOS cannot run dynamically linked executables intended for generic
    linux environments out of the box. For more information, see:
    nix.dev/permalink/stub-ld

    #Linux #SuperMicro

  31. I wrote an email to the #Supermicro support asking if it would be possible to get resizable BAR support for the H11DSi motherboard as that appears to be the only way to actually fix this hardware issue here at its root.

    #Linux #KDE #kWin

  32. I wrote an email to the #Supermicro support asking if it would be possible to get resizable BAR support for the H11DSi motherboard as that appears to be the only way to actually fix this hardware issue here at its root.

    #Linux #KDE #kWin

  33. I wrote an email to the #Supermicro support asking if it would be possible to get resizable BAR support for the H11DSi motherboard as that appears to be the only way to actually fix this hardware issue here at its root.

    #Linux #KDE #kWin

  34. I wrote an email to the #Supermicro support asking if it would be possible to get resizable BAR support for the H11DSi motherboard as that appears to be the only way to actually fix this hardware issue here at its root.

    #Linux #KDE #kWin

  35. I wrote an email to the #Supermicro support asking if it would be possible to get resizable BAR support for the H11DSi motherboard as that appears to be the only way to actually fix this hardware issue here at its root.

    #Linux #KDE #kWin

  36. europesays.com/people/12894/ Supermicro owes its rapid rise to $4 trillion Nvidia—but China smuggling allegations and a high-profile arrest could blow up the partnership #CharlesLiang #JensenHuang #Nvidia #Supermicro

  37. Hardware photos. ASCII art. Tables of data. This post has it all! Updated my notes on my homelab hardware for those of you who are binary curious. #odroid #supermicro #radxa #raspberrypi #freebsd #debian #alpinelinux

    markmcb.com/hardware/

  38. Hardware photos. ASCII art. Tables of data. This post has it all! Updated my notes on my homelab hardware for those of you who are binary curious. #odroid #supermicro #radxa #raspberrypi #freebsd #debian #alpinelinux

    markmcb.com/hardware/

  39. Hardware photos. ASCII art. Tables of data. This post has it all! Updated my notes on my homelab hardware for those of you who are binary curious. #odroid #supermicro #radxa #raspberrypi #freebsd #debian #alpinelinux

    markmcb.com/hardware/

  40. Hardware photos. ASCII art. Tables of data. This post has it all! Updated my notes on my homelab hardware for those of you who are binary curious.

    markmcb.com/hardware/

  41. Hardware photos. ASCII art. Tables of data. This post has it all! Updated my notes on my homelab hardware for those of you who are binary curious. #odroid #supermicro #radxa #raspberrypi #freebsd #debian #alpinelinux

    markmcb.com/hardware/