mirror of
https://github.com/netbootxyz/netboot.xyz.git
synced 2026-04-25 15:15:56 +03:00
[GH-ISSUE #1552] [Request] Add new category Firmware Update ISOs for (NVMe) drives #504
Labels
No labels
Hacktoberfest
Hacktoberfest
bootloader
bsd
bug
confirmed
documentation
duplicate
enhancement
enhancement
enhancement
eol
experimental-merged
freebsd
help wanted
invalid
investigate
ipxe
linux
live-os
memdisk
menu
no-issue-activity
no-issue-activity
pull-request
released
todo
upstream
windows
windows
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/netboot.xyz#504
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Firminator on GitHub (Dec 10, 2024).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1552
Antonym, is it possible to PXE-load SSD FW update ISOs? Through memdisk or whatever is being used these days? In the long distance past Crucial used to have ISOs that were PXE-bootable. It was a TinyCore distro with the FW update autostarting, but that's like 10 years ago. Idk if they still do or if they moved away, however Samsung has been offering for years now ISOs to update the firmware of SSDs.
This is important for Linux users due to Samsung not offering FW updates for consumer drives for Linux (only Windows is supported by their Magician Toolbox). LVFS doesn't support consumer drives either (see https://fwupd.org/lvfs/search?value=samsung )
Here are some links to 3 of their newish drives
They have about a dozen more @ https://semiconductor.samsung.com/consumer-storage/support/tools/
Seagate also has linux support, albeit no bootable FW afaik, just the goold old trusty bootable Seatools ISO @ https://www.seagate.com/content/dam/seagate/migrated-assets/old-support-files/seatools/USBbootSetup-SeaToolsBootable.zip
I remember a discussion here somewhere years ago where this was requested and you showed interest in adding a new category for Firmware. Basically I'm trying here to bring this back on the table for discussion.
Btw WD: support for Linux not existant for consumer drives
@antonym commented on GitHub (Dec 23, 2024):
Firmware tends to change pretty rapidly and it would probably go out of date often. I agree it'd be a great option but the maintenance of it and the breadth of the hardware would make it unmanageable.
If there are generic tools out there made by vendors that can detect versions and select firmware like what Dell has and boot over the network in Linux, I'm more open to those. Updating one tool that will manage mange versions and hardware is significantly easier to maintain.
@Firminator commented on GitHub (Dec 24, 2024):
One more comment before I get off your back :)
Usually yes and I agree this would create a never-ending stream of work. However the FW update ISOs I'm proposing to add into the netboot.xyz menu are Samsung consumer drives, not enterprise (also the DELL SUU ISO for example last time I used it several years was 8 GB, so unbootable over internet really). The FW on these SSDs drives doesn't change as often as Dell/HP server branded drives. There are maybe one or two updates after market release and then a third or fourth over the life span of those consumer drives... if at all (depending how severe an issues is and if there is significant enough public pressure/negative press).
There are only 22 drives w/ available FW listed on the Samsung site. Only 8 are possible candidates for future updates as some of Samsung's more or less recent SSD lineup doesn't even have FW updates available. The rest of them are EOL/EOS and won't receive updates anymore (so there is no maintenance here involved).
Also Samsung is the only vendor I know of who actually has publically linkable ISOs that could be booted with memdisk which is yet to be tested. So currently there is no risk that this would become unmanageable (albeit wishful thinking that other vendors do create bootable ISOs or join the LVFS .
Given that there is a market for used SSD drives for use in a spare linux laptop/desktop and/or hand downs to relatives or family members after an upgrade to a newer drive, I'd argue that easy accessible FW updates through a PXE boot menu are a thing and would make this a breeze.
SATA drives (only 1 drive that is not yet EOL/EOS, so no maintenance really)
NVMe drives (7 drives that are not EOL/EOS where maintenance would be needed; 3 of which with no FW updates released yet)
If you can show me how and where to implement those in the menu I could give it a try. I'm not a coder really (although I did manage to create my own custom working PXE menu years ago chainloading off your menu thanks to your work @ https://github.com/netbootxyz/netboot.xyz-custom ) but updating a few links is easy enough. Having those drives available in the menu would be start. Maybe put it in the development or Testing branch to get the ball rolling, and then we can see how it plays out updating the links to the ISO throughout the lifecycle of the drives?
Not a problem if you still disagree and close this out. I'm just trying to clarify what the workload would look like from my understanding.