Warning: Possible Bug in BIOS DELL Latitude D400_A06 !

From: Uwe Dippel (udippel_at_uniten.edu.my)
Date: 07/28/04

  • Next message: Prasad Pimple: "KDE 100% CPU usage - kio_thumbnail - Excel fault" 
    To: debian-user@lists.debian.org
Date: Wed, 28 Jul 2004 13:02:16 +0800

    Serious Warning - Possible Bug in BIOS update !

    A06 will not support any UNIX-/ LINUX-GUI (at least on this machine).
    I tried Debian-Linux ('testing'); and tried OpenBSD 3.5 (multi-boot).

    Both will inevitably fail with a light yellow screen and an unresponsive keyboard
    (no Ctrl-Alt-Del; neither Ctrl-Alt-Backslash). Only hard reset will help.

    This also applies to the (possible) XFree86 configuration method:

    # cd
    # XFree86 -configure [goes through]
    # XFree86 -xf86config /root/XF86config.new [freezes as above]

    XP, however, starts well !

    Confirmation: I could - puuhh - flash it back to A03 and it is back at
    work without any problems.

    DELL must urgently investigate this problem and find out if this is
    machine-specific for my machine or a bug effecting everyone.

    I can also confirm, that during both flashing operations no error or
    warning was given; the checksums considered okay.
    So I have to assume that the problem is not based on a download-error.

    It *may* be machine-specific, though, since I had earlier filed a problem
    with DELL that the flashing operation had not been possible from XP. This
    problem had been unresolved despite various on- and off-site efforts by
    DELL technicians. (ET20040709_0000004929)

    Any BIOS-Update for this type of machine is discouraged as long as it is
    not guaranteed to be a problem of an individual machine. Still, YMMV. 

    -- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Prasad Pimple: "KDE 100% CPU usage - kio_thumbnail - Excel fault"

    Relevant Pages

    • Re: A critique of cgi.escape
      ... considered a bug. ... It isn't like there have never been backwards _in_compatible changes to ... unit tests which include specific tests for that behaviour, ... it doesn't need to be fixed *immediately* without warning; ...
      (comp.lang.python)
    • Re: Beta anti spyware
      ... The irony here is that I've installed the beta on three computers here. ... I've had only one 'bug' that wasn't the fault of the application. ... As I read in here, I don't post often, I find complaints and that's about ... The warning is clearly there in the ...
      (microsoft.public.security)
    • Re: cciss: WARNING/BUG in do_cciss_intr (its back)
      ... Subject: cciss: WARNING/BUG in do_cciss_intr ... I think this is a different bug than the one you reported previously. ... The first warning that now triggers is: ... still using kexec for loading/testing the new kernel. ...
      (Linux-Kernel)
    • Re: cciss: WARNING/BUG in do_cciss_intr (its back)
      ... Subject: cciss: WARNING/BUG in do_cciss_intr ... I think this is a different bug than the one you reported previously. ... The first warning that now triggers is: ... PCI Interrupt Link enabled at IRQ 54 cciss ...
      (Linux-Kernel)
    • Re: huge gcc 4.1.{0,1} __weak problem
      ... We currently give a #warning for 4.1.0. ... The huge problem is that "empty __weak function in the same file and ... several new usages added during this merge window alone. ... least it was when I encountered a gcc bug with these symptoms last year ...
      (Linux-Kernel)