Stories
Slash Boxes
Comments

SoylentNews is people

posted by n1 on Saturday May 20 2017, @05:05AM   Printer-friendly
from the "bricks"-is-absolutely-accurate-this-time dept.

The Register (aka El Reg) reports:

Many [who installed the latest Dell BIOS update] now cannot boot up their machines. One typical explanation posted was: "Add me to the list Dell Inspiron 20 model 3052, updated on the weekend, woke up to a solid amber/orange light and a dead computer. Contacted Dell on facebook and this is what I was told "The updates Dell releases don't affect the system. But it would enhance the performance of the system" ummmm no....if they broke they need to fix it."

[...] Some users complained screens cycled through red, green, blue and white while others saw nothing but an amber or red power light and a dead screen.

The main model affected by the allegedly dodgy update is the Inspiron 20 3052, although a few users reported similar problems with Inspiron 3252s.

[...] Dell's initial reaction was to tell customers they needed to buy new motherboards.

[...] Although complaints in the forum date back to May 12, Dell took four days to offer up a possible solution... which users subsequently said didn't work. Dell has yet to send [El Reg] a statement.

Have we saved anyone from a big headache?

The relevant Dell forum thread can be found here.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2, Informative) by anubi on Saturday May 20 2017, @06:16AM (14 children)

    by anubi (2828) on Saturday May 20 2017, @06:16AM (#512535) Journal

    Ok... I will compare a "hobbyist grade" Arduino with a "business-grade" Dell.

    I have a six-pin hardware SPI-type port on the Arduino with which to burn any bootloader/BIOS code. This is done by plugging the six-pin port into either a programmer or another Arduino running some code to download a copy of the boot code. Personally, I am partial to Bill Westfield's "OptiLoader" boot code.

    Every Arduino-type system I have runs Westfield's code, whether it originally came that way or not. I am making enough of these devices that I dedicated several of my Arduino modules to transfer Westfield's OptiLoader boot code to whatever I plug into its SPI port. It makes no difference whatsoever what boot code the target ATMEL had in it, or even if it has any at all. What was there is a "don't care". It is overwritten by the incoming stream. The hardware takes care of it. I wiggle the correct pins of the SPI port and the correct sequence and it shifts the BIOS/Bootloader code right in.

    With the "hobbyist grade" architecture, I made numerous screwups while learning how to make my bootloader transfer modules, yet I have not bricked not ONE ATMEL chip. The most critical part of the startup code botched many times. 100% recovery from all screwups.

    Yes, I know the ATMEL is far simpler than a DELL. What I am trying to get at though, is transferring startup code is NOT rocket science. I see no reason really that even an Arduino could not be programmed to transfer startup code into a DELL if the DELL only had methods for getting the code into the BIOS flash chip.

    ( It goes without saying that the startup code for a DELL is substantially longer than that of an Arduino... therefore I might have to use a big flash eeprom on the Arduino to store the code necessary to boot a DELL, but the SPI hardware would be completely usable for this kind of thing. The ATMEL would just read it and poke it into the DELL the same way it would have poked it into another ATMEL. )

    One six-pin SPI connector directly driving the BIOS flash like the hobbyist-grade Arduino does it would make recovery from any failed flash download attempt recoverable by anyone who had a hardware programming interface - as by this time the DELL has already "lost its mind", is completely comatose, and unable to assist anymore.

    Once the Arduino has reloaded the DELL's flash with correct boot code, the expensive motherboard is now rescued.

    Hobbyist-grade systems have these recovery methods, but business-grade systems do not.

    If "business-grade" systems could only be made as resilient as "hobbyist-grade" systems concerning loss/corruption of boot code ( which I consider highly likely in this world of networked machines on the public internet - and the amount of malware targeting this area of a machine ), a binary file of the proper boot code could be reintroduced into the machine either by computer techs, or even a hobbyist with an Arduino with enough external flash eeprom to store the business-grade system's boot file.

    Seems the moneyed crowd looks beyond things like recovering from things like this. While hobbyists like me would find the hardware too finicky to use if stuff like this was not implemented.

    Business people buy this stuff. Purchasing a business-grade system usually includes a handshake with a man wearing a suit, whereas the hobbyist-grade system comes in a bag. But when the Business-system gets sick this way, its gotta be replaced, while hobbyists like me reconnect the programmer and reset the code.

    --
    "Prove all things; hold fast that which is good." [KJV: I Thessalonians 5:21]
    Starting Score:    1  point
    Moderation   +1  
       Informative=1, Total=1
    Extra 'Informative' Modifier   0  

    Total Score:   2  
  • (Score: 2, Disagree) by Chromium_One on Saturday May 20 2017, @06:30AM (12 children)

    by Chromium_One (4574) on Saturday May 20 2017, @06:30AM (#512538)

    This would add cost to the unit, therefore it is a complete non-starter.

    --
    When you live in a sick society, everything you do is wrong.
    • (Score: 1) by anubi on Saturday May 20 2017, @07:57AM (10 children)

      by anubi (2828) on Saturday May 20 2017, @07:57AM (#512544) Journal

      The loss of a motherboard for the lack of one 6-pin SPI connector for manually loading in BIOS code.

      With malware being what it is, I believe it would behoove ( Hopefully, I used the word correctly this time ) the manufacturers to make recovery from malware or failed bios upgrade attempts possible without having to change out the whole motherboard. This kind of "business thinking" is going to be quite a pain in the ass if the malware or botched bios update hits after the board is out of production, and another motherboard, with different architectures and drivers, has to be shoehorned into the business system to replace it.

      I GLADLY paid for this connector on the Arduino, and it was a significant factor in how much I trusted this Arduino-compatible ATMEL design for the control processor in my van.

      When I go where I am going to go with this thing, I simply can't have it fail. Good chance if it fails, I die. "Business-grade" stuff is not good enough for this design, as I am staking too much on it. Its not just another bullet-point brought up at a meeting and delegated out to someone else. I do not want to be stranded in the middle of the desert. These guys all sitting around conference tables, wearing business suits, have completely different needs than I do, I suppose.

      My grandpa used to always warn me about being "penny-wise and pound-foolish". I believe this is a good example of that.

      --
      "Prove all things; hold fast that which is good." [KJV: I Thessalonians 5:21]
      • (Score: 3, Informative) by coolgopher on Saturday May 20 2017, @08:30AM (4 children)

        by coolgopher (1157) on Saturday May 20 2017, @08:30AM (#512547)

        If you can remove the BIOS chip (aka SPI flash), you can use one of these [ebay.com.au] to rewrite the chip. I believe there should also be models which have the clamp/clip that you can snap on to the flash chip if it's soldered in place, but I haven't got a handy link.

        I had to acquire one of these BIOS flashers earlier this year to upgrade the BIOS on a motherboard I'd purchased as the old version it shipped with didn't support my CPUs, and the three documented ways of upgrading the BIOS all needed a running system (which is really hard when the BIOS refuses to recognise the installed CPUs). Getting that gadget off eBay was easier than wiring up any of the various microcontrollers I have access to.

        Oh, and thumbs-up on "behoove" use this time! :)

        • (Score: 1) by anubi on Saturday May 20 2017, @09:54AM (3 children)

          by anubi (2828) on Saturday May 20 2017, @09:54AM (#512567) Journal

          It behooves me to at least use the word properly.... lest I come off sounding like even more of a raving idjit than I am ;)

          Anyway.. I started off with several thingies like this [aliexpress.com] that plug into the 6-pin connector on Arduino and the Arduino-compatibles I make.

          The raw ATMEL 328's I buy have no bootloader in them at all. I was installing the bootloader this way at first, but now that I have gotten a bit more familiar of how this is done, I have other modules where I use their SPI port to generate the bootloader download stream. All I have to do is plug the two modules' SPI ports together then apply power. The way the connector is configured, one of those lines is a RESET line, and my bootloader "MASTER" asserts this to the slave, which now goes to sleep, and lets the master download the bootloader into the slave's EEPROM.

          On my version of the Arduino compatibles, I move a jumper on my board to convert it to be a "student" board. This converts the board's SPI port to an ISP ( InCircuit Serial Programming ) port, then I plug the SPI port of my master to the ISP port of my "student", apply power, then the master shows he's done the deed and wrote his code to the student, which happens in a blink of an eye.

          I then move the jumper of the student board back so the port is now configured as SPI, the board is now no longer a student, and I now have another board compatible with Arduino system download protocols.

          I was thinking of how easy it would be to do this for business-grade systems, so that fear of rogue code overwriting the BIOS eeprom would not be any more of a show-stopper for a business than it is for me. Security? To do what I do requires I have physical access to that connector. Once I have physical access, I can clean up any mess that a malware author or failed upgrade-over-the-internet may have left behind.

          All I need is the binary blob of code that's supposed to go into the boot eeprom.

          An even cheaper way would be to design the motherboard so a clip-in programmer like this [aliexpress.com] could be used. But I really hate messing with those. By its very nature, the chip package was not designed to be connected to this way, and the connection so obtained is tenuous at best. Maybe tolerable for business use but a hobbyist would scoff at it.

          I guess I come off a bit jaded as I used to work in corporate, and when I would bitch at things like this, I came off like a geologist claiming the universe is billions of years old - to a creationist preacher with a microphone and several kilowatts of audio amp behind him. I may know about the code, but the suit-guys knew how to play off the investors. Who am I to stand up to a MBA degree in an Armani suit?

          --
          "Prove all things; hold fast that which is good." [KJV: I Thessalonians 5:21]
          • (Score: 2) by coolgopher on Saturday May 20 2017, @10:32AM (2 children)

            by coolgopher (1157) on Saturday May 20 2017, @10:32AM (#512575)

            Meanwhile I'm simply missing the days of having to move a jumper on the motherboard to be able to write to the BIOS in the first place. ;)

            (Note that I am typically not missing the days of having to manually assign IRQs and I/O ranges via jumpers however)

            Thanks for the link to the clip-in programmer, that was exactly the sort of thing I had in mind.

            • (Score: 2, Insightful) by anubi on Saturday May 20 2017, @11:14AM (1 child)

              by anubi (2828) on Saturday May 20 2017, @11:14AM (#512580) Journal

              Yeh, I sure felt a lot more comfortable when I had the security of knowing exactly what my machine was doing. I knew better than to feed it rogue .exe or .com files off the bulletin board systems, and knew full good and well I could read anything safely as long as I did not use an ANSI editor. Plain old ascii was safe as could be. Worst they could do is fill my screen full of crap, which disappeared almost immediately with a few hits of the enter key.

              Even if they did infect the old systems... it wasn't all that much problem to clean it back out. Kinda like someone ringing your bell, tossing a bag of crap in your house when you open the door, and running. Yeh, a mess. But it wasn't a show-stopper. Just an annoyance. Gotta go clean up the mess.

              Those days where my computer was about as trustworthy as my old mechanical typewriter are gone.

              I thought you might like that clip in link... that's the reason I looked it back up for ya. You were hinting around with it in your link. I have done it that way but I do not like doing it that way, as sometimes the clip does not make good contact and I get a bad load. And sometimes some design idjit hooks the write enable pin up in such a way I have to force override some other totem-pole output of some gate, possibly damaging it in the process. I'd much rather have that nice standardized programming pin layout used by all those off-the-shelf SPI programmers. If I had my druthers, I much rather have a nice SPI access to the EEROM, with the jumper I have to physically install or remove to enable WRITE. I flat do not like things like rewriting my machine's BIOS done behind my back.

              --
              "Prove all things; hold fast that which is good." [KJV: I Thessalonians 5:21]
              • (Score: 0) by Anonymous Coward on Sunday May 21 2017, @09:09PM

                by Anonymous Coward on Sunday May 21 2017, @09:09PM (#513156)

                You are saying you feared that ansi graphics on bulletin boards would harm your computer?

                Do you visit this website in Lynx, as well?

      • (Score: 3, Insightful) by Chromium_One on Saturday May 20 2017, @12:14PM (2 children)

        by Chromium_One (4574) on Saturday May 20 2017, @12:14PM (#512592)

        You and I might gladly pay the cost difference to have this kind of feature available, but you are seriously underestimating what kind of cheap-assed short-sighted shitheads are in control of most PC manufacturing companies. A one penny per unit cost difference will be fought tooth and nail no matter what the benefit is.

        --
        When you live in a sick society, everything you do is wrong.
        • (Score: 3, Informative) by NCommander on Saturday May 20 2017, @07:44PM (1 child)

          by NCommander (2) Subscriber Badge <michael@casadevall.pro> on Saturday May 20 2017, @07:44PM (#512691) Homepage Journal

          I had this discussion when I was working in Canonical's OEM group. While I don't disagree with your assessment, this is the line of thinking that went into it:

          Let's say that adding a socketed flash adds 5 cents per unit costs (using round numbers for simplicity):
          This is a feature that only a very small number of users will ever use (let's say .1%)
          Your per-unit cost (for the logic board) is 100 dollars.
          You intend to ship 100,000 units.
          Your 5 cent change has a total cost of $5,000 now.

          As long as you don't brick 500 boards, or have 500 users that could replace a flash chip (and are willing to repair vs. replace), you're ahead.

          That's how they see it. It's not necessarily a "wrong" point of view, but it's not one I like.

          --
          Still always moving
          • (Score: 2) by Chromium_One on Saturday May 20 2017, @08:06PM

            by Chromium_One (4574) on Saturday May 20 2017, @08:06PM (#512697)

            The metric of cost-per-user-serviced-this-quarter is not meaningful for this type of feature, but instead over the lifetime of the product. Having a reputation for products that can be repaired when everyone else consistently makes disposable junk may result in more sales later, though your fuckhead MBA types will claim that anything easily field repairable is a lost new unit sale right then.

            --
            When you live in a sick society, everything you do is wrong.
      • (Score: 2) by Immerman on Saturday May 20 2017, @04:38PM (1 child)

        by Immerman (3985) on Saturday May 20 2017, @04:38PM (#512645)

        But how would that improve sales for Dell?

        • (Score: 2) by HiThere on Saturday May 20 2017, @05:01PM

          by HiThere (866) Subscriber Badge on Saturday May 20 2017, @05:01PM (#512649) Journal

          Well, it would have lessened the impact of this mistake. So less bad publicity, and possibly even some good publicity. ("My Dell was easy to recover after...")

          --
          Javascript is what you use to allow unknown third parties to run software you have no idea about on your computer.
    • (Score: 2) by kaszz on Saturday May 20 2017, @12:45PM

      by kaszz (4211) on Saturday May 20 2017, @12:45PM (#512600) Journal

      Business class usually imply cost insensitivity. And that total ownership cost is more important.
      Obviously someone did at least two dick choices here.

  • (Score: 3, Informative) by kaszz on Saturday May 20 2017, @12:42PM

    by kaszz (4211) on Saturday May 20 2017, @12:42PM (#512599) Journal

    There are ways to program a BIOS EEPROM despite computer hardware lockout [github.io]. Preferably one might as well install a switch on the "write enable circuit wire".