Re: linux-next: Tree for June 13: IO APIC breakage on HP nx6325



On Mon, 30 Jun 2008, Rafael J. Wysocki wrote:

Well, there are lots of pieces of hardware that are not up to the
specifications, more or less, and I don't think that's a good enough reason
for us to refuse to support them. The same applies to BIOSes IMO.

Refusing to support broken hardware would provide some incentive to
manufacturers to improve it, because people would rather not buy
unsupported pieces of junk. I realise that may be impractical though --
we would get the blame anyway, because "it runs the other OS just fine."

I think we may legitimately request something in return for our effort
though, for example at least minimal support from hardware manufacturers.
It is not that we would waste a lot of their time, because in general
anything we do not filter out must be really tough.

Of course, the _default_ should be to follow the spec, but if that doesn't work
on given hardware/BIOS combination and we know what to do to handle it, we
should just handle it instead of asking users to fix their BIOSes.

I think we should insist on getting issues reported back to the
manufacturer. We may implement workarounds independently and leave it up
to the users whether they want to do a BIOS upgrade or not.

I have seen enough failed BIOS upgrades to be very cautious about such things.
Certainly, I wouldn't have seriously asked anyone to upgrade the BIOS in a
notebook, because if that had failed, the user would have end up with a piece
of electronic junk.

That's a valid point, although making the point of quality yet clearer --
being critical enough, I would expect it to have been thorougly tested by
the manufacturer. Also solutions like protected Flash areas have been
available for many years now, which means a machine should be operative
enough for recovery to be doable if an upgrade fails. So perhaps the very
first thing to do after a new purchase should be doing a BIOS update, so
that you can claim your warranty if something goes wrong.

Technically upgrading a laptop should be safer as bearing an on-board UPS
they are protected from power failures, which may be problematic for some
users of other equipment.

Maciej
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



Relevant Pages

  • Re: Why I should use FBSD 4.9/10 and not 5.2.1?
    ... the instability was caused by a buggy BIOS on his SMP ... > -that the upgrade doesn't succeed and the machine is rendered unbootable ... > obviously this depends on the hardware, ... But an attempt over the weekend to install 5.2.1 on a Dell ...
    (comp.unix.bsd.freebsd.misc)
  • Re: upgrading Me to XP Pro compatibitiy questions
    ... Unfortunately I am marginally computer literate...how do I update BIOS ... My real options are buy/upgrade hardware to HP 5150 or Dell Precision 390 ... with XP Pro and Office 2003 installed and then try to transfer my files, ... times an upgrade will be fine as long as you prep the machine. ...
    (microsoft.public.windowsxp.general)
  • Re: teething probs with Sun Ultra 10 & Solaris 10
    ... Unfortunately, it only takes 3 128MB SIMMs, and there's no BIOS ... I cannot upgrade the Slot 1 processor ... hardware / any old hardware is a hassle. ... either Solaris 9 or Solaris 10. ...
    (comp.unix.solaris)
  • Re: Why I should use FBSD 4.9/10 and not 5.2.1?
    ... the instability was caused by a buggy BIOS on his SMP ... -that the upgrade doesn't succeed and the machine is rendered unbootable ... FreeBSD-4 was much better around 4.5 than it is now. ... obviously this depends on the hardware, ...
    (comp.unix.bsd.freebsd.misc)
  • Re: Will A WindowsXP Upgrade Repair Win98 Problems
    ... I think you have to consider the "Upgrade" option as being a gamble in any ... hardware of course. ... first download and burn SP2 onto CD so you can install that before even ... your system to XP and hopefully resolve the problem that way. ...
    (microsoft.public.windowsxp.general)