-
-
that's actually surprisingly well-written, and you can even build it for EFI
1 reply 0 retweets 3 likes -
1 reply 0 retweets 1 like -
-
Replying to @whitequark @rqou_
I like 44. Program manufacturing information and 33. Erase non-volatile adapter storage. I bet some combination thereof will solve all the pesky crossflashing problems. I have both an IBM M5010 and a Dell PERC... wonder if I can completely rewrite the latter.
1 reply 0 retweets 0 likes -
as far as I can tell building this for EFI and enabling expert mode should just naturally allow overriding all VID/PID checks
1 reply 0 retweets 0 likes -
Replying to @whitequark @rqou_
ManufacturingPage2 seems to contain the first chunk of what I called the SBR. I wonder if that really is the SBR itself or some kind of mirror in NVRAM (which would explain the complaints from the other tools even after you write SBR).
1 reply 0 retweets 1 like -
"44. Program manufacturing information" seems to write all that stuff. I wonder if it writes just NVRAM or also SBR.
1 reply 0 retweets 0 likes -
Oh, and that magic byte that fixed half the ports on my Fujitsu board? It's called HardwareConfig. Surprise.
1 reply 0 retweets 2 likes -
I'm really tempted to mess with the Dell adapter in my backup server now, see if I can convert it to vanilla firmware straight from Linux. Even though it's a 3 hour train ride away. YOLO, right? It's not used for the boot drives...
1 reply 0 retweets 2 likes
Also I bet this can be ported to run in "DOS/EFI" mode (raw access) under linux (with pcilib) to recover bricked adapters without the kernel driver being involved.
-
-
yup! To be honest I was surprised that it used the Linux driver, seems superfluous
1 reply 0 retweets 0 likes -
Replying to @whitequark @rqou_
You want to use the Linux driver when it's loaded (otherwise you're stepping on its toes; this thing is supposed to be usable on live systems) but it makes no sense not to offer the direct option as well.
1 reply 0 retweets 1 like - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.