[News] Foxconn Reported to FTC for Sabotage Against Linux - Linux

This is a discussion on [News] Foxconn Reported to FTC for Sabotage Against Linux - Linux ; -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Foxconn deliberately sabotaging their BIOS to destroy Linux ACPI ,----[ Quote ] | Complained to the Federal Trade Commission | | http://www.ftc.gov | | Foxconn | 458 E. Lambert Road Fullerton | Fullerton, CA ...

+ Reply to Thread
Results 1 to 16 of 16

Thread: [News] Foxconn Reported to FTC for Sabotage Against Linux

  1. [News] Foxconn Reported to FTC for Sabotage Against Linux

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    Foxconn deliberately sabotaging their BIOS to destroy Linux ACPI

    ,----[ Quote ]
    | Complained to the Federal Trade Commission
    |
    | http://www.ftc.gov
    |
    | Foxconn
    | 458 E. Lambert Road Fullerton
    | Fullerton, CA
    | 92835
    |
    | FOXCONN PHONE NUMBER: 714-871-9968
    |
    | Company sold me a computer motherboard, model G33M-S, claiming that it was
    | compliant with ACPI versions 1.0, 2.0, and 3.0.
    |
    | Linux and FreeBSD do not work with this motherboard due to it's ACPI
    | configuration, using a disassembler program, I have found that it detects
    | Linux specifically and points it to bad DSDT tables, thereby corrupting it's
    | hardware support, changing this and setting the system to override the BIOS
    | ACPI DSDT tables with a customized version that passes the Windows versions
    | to Linux gives Linux ACPI support stated on the box, I am complaining because
    | I feel this violates an anti-trust provision in the Microsoft settlement, I
    | further believe that Microsoft is giving Foxconn incentives to cripple their
    | motherboards if you try to boot to a non-Windows OS.
    |
    | We have received your complaint.
    |
    | Thank you for contacting the FTC. Your complaint has been entered into
    | Consumer Sentinel, a secure online database available to thousands of civil
    | and criminal law enforcement agencies worldwide. Your reference number is:
    | 19642372
    |
    | [...]
    |
    | They detect Linux, give it a bad DSDT table, one that looks ok at a glance,
    | but broken in subtle ways so that some of it works, but not correctly.
    |
    | You call them to ask why their board won't run Linux.
    |
    | They tell you to buy Vista.
    |
    | They're basically rubbing Microsoft's back.
    `----

    http://ubuntuforums.org/showthread.php?t=869249


    Related:

    ,----[ Quote ]
    | From: Bill Gates
    | Sent: Sunday, January 24, 1999 8:41 AM
    | To: Jeff Westorinen; Ben Fathi
    | Cc: Carl Stork (Exchange); Nathan Myhrvold; Eric Rudder
    | Subject: ACPI extensions
    |
    | One thing I find myself wondering about is whether we shouldn't try
    | and make the "ACPI" extensions...
    |
    | It seems unfortunate if we do this work and get our partners to do the
    | work and the results is that Linux...
    |
    | Maybe there is no way to avoid this problem but it does bother me.
    |
    | Maybe we could define the APIs so that they work well with NT and not
    | the others even if they are open.
    |
    | Or maybe we could patent something related to this.
    `----

    http://edge-op.org/iowa/www.iowacons...00/px03020.pdf
    http://antitrust.slated.org/www.iowa...00/PX03020.pdf
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.9 (GNU/Linux)

    iEYEARECAAYFAkiKIpcACgkQU4xAY3RXLo4PBwCfU1zbPEXgy1 evDqUkmzLm8IZJ
    aMgAnRVAxeLfQb3WetcmTclMzOdMNV4J
    =hYaW
    -----END PGP SIGNATURE-----

  2. Re: [News] Foxconn Reported to FTC for Sabotage Against Linux

    Roy Schestowitz wrote:

    > -----BEGIN PGP SIGNED MESSAGE-----
    > Hash: SHA1
    >
    > Foxconn deliberately sabotaging their BIOS to destroy Linux ACPI
    >
    > ,----[ Quote ]
    > | Complained to the Federal Trade Commission
    > |
    > | http://www.ftc.gov
    > |
    > | Foxconn
    > | 458 E. Lambert Road Fullerton
    > | Fullerton, CA
    > | 92835
    > |
    > | FOXCONN PHONE NUMBER: 714-871-9968
    > |
    > | Company sold me a computer motherboard, model G33M-S, claiming that it
    > | was compliant with ACPI versions 1.0, 2.0, and 3.0.
    > |
    > | Linux and FreeBSD do not work with this motherboard due to it's ACPI
    > | configuration, using a disassembler program, I have found that it
    > | detects Linux specifically and points it to bad DSDT tables, thereby
    > | corrupting it's hardware support, changing this and setting the system
    > | to override the BIOS ACPI DSDT tables with a customized version that
    > | passes the Windows versions to Linux gives Linux ACPI support stated on
    > | the box, I am complaining because I feel this violates an anti-trust
    > | provision in the Microsoft settlement, I further believe that Microsoft
    > | is giving Foxconn incentives to cripple their motherboards if you try to
    > | boot to a non-Windows OS.
    > |
    > | We have received your complaint.
    > |
    > | Thank you for contacting the FTC. Your complaint has been entered into
    > | Consumer Sentinel, a secure online database available to thousands of
    > | civil and criminal law enforcement agencies worldwide. Your reference
    > | number is: 19642372
    > |
    > | [...]
    > |
    > | They detect Linux, give it a bad DSDT table, one that looks ok at a
    > | glance, but broken in subtle ways so that some of it works, but not
    > | correctly.
    > |
    > | You call them to ask why their board won't run Linux.
    > |
    > | They tell you to buy Vista.
    > |
    > | They're basically rubbing Microsoft's back.
    > `----
    >
    > http://ubuntuforums.org/showthread.php?t=869249



    Fscking BASTARDS!

    I have always suspected this FoxCON of material con jobbie.
    Thank goodness I never bought dodgy Foxcon mboards.

    There is a lot of dicing about and bundling that tells you
    there is something wrong with their business - its all a con job
    to bundle micoshaftee vendor lock in things with the mboard.
    Now its gone official, the anti-trust complaints should be
    widened and micoshaft banned from trading me thinks along
    with Foxcon for their big con.

    Did Balmer discuss foxcon con job with Nellie Kroes when he parachuted
    in to the EU?




  3. Re: [News] Foxconn Reported to FTC for Sabotage Against Linux


    How does the motherboard know you are using Linux? Is it a setting
    somewhere in the non-volatile BIOS settings? If so, what happens if you
    simply change the setting to say you are running Windows?

    --
    --Tim Smith

  4. Re: [News] Foxconn Reported to FTC for Sabotage Against Linux


    "Tim Smith" wrote in message
    news:reply_in_group-A4BAC9.16532325072008@news.supernews.com...
    >
    > How does the motherboard know you are using Linux? Is it a setting
    > somewhere in the non-volatile BIOS settings? If so, what happens if
    > you
    > simply change the setting to say you are running Windows?
    >
    > --
    > --Tim Smith


    This is the same idea as your Web browser can tell
    the other party you're using Windows software; and I
    expect a fix will be published shortly.

    But a better fix, is to publish how one identifies a
    Foxconn motherboard so that everyone can know these
    boards are defective and don't buy them. *That*
    should get the mfr's attention as well as be very
    useful information to everyone.

    The interesting question this raises is, is Microsoft
    the instigator of this scheme? Where else are they
    doing this to us? ??

    And, it shows Microsoft products cannot stand on their,
    uh, merits; and Microsoft knows it.

    Titeotwawki -- mha [2008 Jly 25]



  5. Re: [News] Foxconn Reported to FTC for Sabotage Against Linux

    * Tim Smith peremptorily fired off this memo:

    > How does the motherboard know you are using Linux? Is it a setting
    > somewhere in the non-volatile BIOS settings? If so, what happens if you
    > simply change the setting to say you are running Windows?


    That would be hard to say. If you read the article, it notes that
    different tables are loaded depending on the OS, and that the Linux
    table is faulty. The article describes how to read the ACPI tables from
    the /sys/firmware/... directory, edit the code, save the file, make it
    part of the initrd system so that the kernel will use it.

    On my DELL, the only reference to an OS is:

    Name (W98S, "Microsoft Windows")
    Name (NT5S, "Microsoft Windows NT")
    Name (WINM, "Microsoft WindowsME: Millennium Edition")
    Name (WXP, "Windows 2001")
    Name (WLG, "Windows 2006")

    and then it sets up a bit-masked, with a different bit set depending on
    which version of Windows, and bit 0 if "none of the above". Then a lot
    of decisions are made based on that bit value such as calling Notify()
    and Sleep() functions with varying values.

    The guy in this article
    gets this "admission" from FoxConn:

    This board was never certified for Linux. It is only certified for
    Vista. See URL below. So please test under Vista. Does this issue
    also occured under Vista or Winxp?

    He gets pretty irate, too.

    I saw you targeting Linux with an intentionally broken ACPI table,
    you also have one for NT and ME, a separate one for newer NT variants
    like 2000, XP, Vista, and 2003/2008 Server, I'm sure that if you
    actually wrote to Intel ACPI specs instead of whatever quirks you can
    get away with for 8 versions of Windows and then go to the trouble of
    giving a botched table to Linux (How much *is* Microsoft paying you?)
    it would end up working a lot better, but I have this idea you don't
    want it to.

    Collusion, laziness, not caring about the non-Windows market, or just
    plain stupidity?

    One wonders, when Foxconn says "we only support Vista", yet the ACPI
    code contains explicit references to Linux that cause bad data to be
    loaded that makes Linux screw up in power-management situations.

    --
    I have never been one to sacrifice my appetite on the altar of appearance.
    -- A. M. Readyhough

  6. Re: [News] Foxconn Reported to FTC for Sabotage Against Linux

    * Martha Adams peremptorily fired off this memo:

    > This is the same idea as your Web browser can tell
    > the other party you're using Windows software; and I
    > expect a fix will be published shortly.
    >
    > But a better fix, is to publish how one identifies a
    > Foxconn motherboard so that everyone can know these
    > boards are defective and don't buy them. *That*
    > should get the mfr's attention as well as be very
    > useful information to everyone.
    >
    > The interesting question this raises is, is Microsoft
    > the instigator of this scheme? Where else are they
    > doing this to us? ??
    >
    > And, it shows Microsoft products cannot stand on their,
    > uh, merits; and Microsoft knows it.


    Well, corporate stupidity or developer laziness/stupidity are still
    possible explanations. I personally don't suspect that Microsoft or
    Intel had any direct hand in it.

    My Dell laptop has an issue when I boot to the DSL (Damn Small Linux)
    that's part of Billix. The author of that package, Bill Childers sent
    me an email indicating to use the "acpi=off" option, and that did the
    trick for me.

    --
    This night methinks is but the daylight sick.
    -- William Shakespeare, "The Merchant of Venice"

  7. Re: [News] Foxconn Reported to FTC for Sabotage Against Linux

    Linonut wrote:

    > My Dell laptop has an issue when I boot to the DSL (Damn Small Linux)
    > that's part of Billix. The author of that package, Bill Childers sent
    > me an email indicating to use the "acpi=off" option, and that did the
    > trick for me.


    That's Linux cripple-ware for you - disable features just so it will run.

    Even the "best" (that's rich), "most popular" (also rich) Linux distro,
    Ubuntu, often chokes and freezes unless you use ACPI=off.

    Linux = computing asceticism




  8. Re: [News] Foxconn Reported to FTC for Sabotage Against Linux

    Verily I say unto thee, that Roy Schestowitz spake thusly:

    > Foxconn deliberately sabotaging their BIOS to destroy Linux ACPI


    Check out Foxconn's response:

    You are incorrect in that the motherboard is not ACPI complaint. If it
    were not, then it would not have received Microsoft Certification for WHQL.

    > http://ubuntuforums.org/showthread.php?t=869249


    ROTFLMFAO!!!

    OK, so maybe there's no conspiracy here, and it's just Foxconn's sheer
    incompetence, but to claim that their board /must/ be OK just because
    "Microsoft says so" is arrogant in the extreme, not to mention /stupid/
    given the demonstrable errors in the BIOS.

    As for this garbage about "Linux is not certified" for this board ...
    all they have to do is ensure ACPI compliance, and it /will be/
    "certified" in the sense that it works. We don't need Foxconn's rubber
    stamp on /that/, we just need them to stop being idiots.

    > ,----[ Quote ]
    > | From: Bill Gates

    [...]
    > | Maybe we could define the APIs so that they work well with NT and
    > | not the others even if they are open.
    > |
    > | Or maybe we could patent something related to this.
    > `----
    >
    > http://edge-op.org/iowa/www.iowacons...00/px03020.pdf
    > http://antitrust.slated.org/www.iowa...00/PX03020.pdf


    Yeah, of course that was back in the bad ol' days before Asus started
    shipping Linux embedded into millions of motherboards, and installed
    onto millions of Netbooks.

    --
    K.
    http://slated.org

    ..----
    | By bucking Microsoft for open source, says Gunderloy, "I'm no
    | longer contributing to the eventual death of programming."
    | ~ http://www.linux.com/feature/142083
    `----

    Fedora release 8 (Werewolf) on sky, running kernel 2.6.23.8-63.fc8
    05:00:50 up 218 days, 1:36, 4 users, load average: 0.27, 0.32, 0.32

  9. Re: [News] Foxconn Reported to FTC for Sabotage Against Linux

    In article ,
    Linonut wrote:
    > One wonders, when Foxconn says "we only support Vista", yet the ACPI
    > code contains explicit references to Linux that cause bad data to be
    > loaded that makes Linux screw up in power-management situations.


    Well, notice that people are saying that the ACPI code it has for Linux
    is for the wrong hardware, or something like that. Does this mean they
    have other boards where ACPI *does* work for Linux?

    If so, then the explanation is obvious: they copied the BIOS code from
    one of their other boards, and fixed the parts that were wrong for Vista
    on the new board. They left the Linux parts as is, since they decided
    for some reason to only support Vista on this board.


    --
    --Tim Smith

  10. Re: [News] Foxconn Reported to FTC for Sabotage Against Linux

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    ____/ Homer on Saturday 26 July 2008 04:01 : \____

    > Verily I say unto thee, that Roy Schestowitz spake thusly:
    >
    >> Foxconn deliberately sabotaging their BIOS to destroy Linux ACPI

    >
    > Check out Foxconn's response:
    >
    >
    > You are incorrect in that the motherboard is not ACPI complaint. If it
    > were not, then it would not have received Microsoft Certification for WHQL.
    >
    >
    >> http://ubuntuforums.org/showthread.php?t=869249

    >
    > ROTFLMFAO!!!
    >
    > OK, so maybe there's no conspiracy here, and it's just Foxconn's sheer
    > incompetence, but to claim that their board /must/ be OK just because
    > "Microsoft says so" is arrogant in the extreme, not to mention /stupid/
    > given the demonstrable errors in the BIOS.
    >
    > As for this garbage about "Linux is not certified" for this board ...
    > all they have to do is ensure ACPI compliance, and it /will be/
    > "certified" in the sense that it works. We don't need Foxconn's rubber
    > stamp on /that/, we just need them to stop being idiots.
    >
    >> ,----[ Quote ]
    >> | From: Bill Gates

    > [...]
    >> | Maybe we could define the APIs so that they work well with NT and
    >> | not the others even if they are open.
    >> |
    >> | Or maybe we could patent something related to this.
    >> `----
    >>
    >> http://edge-op.org/iowa/www.iowacons...00/px03020.pdf
    >> http://antitrust.slated.org/www.iowa...00/PX03020.pdf

    >
    > Yeah, of course that was back in the bad ol' days before Asus started
    > shipping Linux embedded into millions of motherboards, and installed
    > onto millions of Netbooks.


    Spotted earlier:

    http://www.techtree.com/India/News/E...91486-581.html

    "Benson Lin: Currently, we're closely tied up with Microsoft and the EEE PC
    with Windows XP..."

    Seems like someone decided to rub someone's back because Linux became a top
    seller in shops like Amazon.

    Not to worry. Ballmer and the grease gun run out of ammo. It'll get harder to
    bribe (in the soft bribe sense).

    "Microsoft loses 90 Billion Dollars"

    http://slated.org/microsoft_loses_90_billion_dollars



    - --
    ~~ Best of wishes

    Roy S. Schestowitz | Rid your machine from malware. Install GNU/Linux.
    http://Schestowitz.com | RHAT GNU/Linux | PGP-Key: 0x74572E8E
    07:00:01 up 4 days, 17:06, 1 user, load average: 0.44, 0.77, 0.73
    http://iuron.com - help build a non-profit search engine
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.9 (GNU/Linux)

    iEYEARECAAYFAkiKzG4ACgkQU4xAY3RXLo7VigCePfyOicLR52 CVha7YFQ+oNdQR
    oKMAn0VUCcb5wzMZK7JtJtXe1qKIAR3+
    =MYfz
    -----END PGP SIGNATURE-----

  11. Re: [News] Foxconn Reported to FTC for Sabotage Against Linux

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    ____/ 7 on Friday 25 July 2008 21:40 : \____

    > Roy Schestowitz wrote:
    >
    >> -----BEGIN PGP SIGNED MESSAGE-----
    >> Hash: SHA1
    >>
    >> Foxconn deliberately sabotaging their BIOS to destroy Linux ACPI
    >>
    >> ,----[ Quote ]
    >> | Complained to the Federal Trade Commission
    >> |
    >> | http://www.ftc.gov
    >> |
    >> | Foxconn
    >> | 458 E. Lambert Road Fullerton
    >> | Fullerton, CA
    >> | 92835
    >> |
    >> | FOXCONN PHONE NUMBER: 714-871-9968
    >> |
    >> | Company sold me a computer motherboard, model G33M-S, claiming that it
    >> | was compliant with ACPI versions 1.0, 2.0, and 3.0.
    >> |
    >> | Linux and FreeBSD do not work with this motherboard due to it's ACPI
    >> | configuration, using a disassembler program, I have found that it
    >> | detects Linux specifically and points it to bad DSDT tables, thereby
    >> | corrupting it's hardware support, changing this and setting the system
    >> | to override the BIOS ACPI DSDT tables with a customized version that
    >> | passes the Windows versions to Linux gives Linux ACPI support stated on
    >> | the box, I am complaining because I feel this violates an anti-trust
    >> | provision in the Microsoft settlement, I further believe that Microsoft
    >> | is giving Foxconn incentives to cripple their motherboards if you try to
    >> | boot to a non-Windows OS.
    >> |
    >> | We have received your complaint.
    >> |
    >> | Thank you for contacting the FTC. Your complaint has been entered into
    >> | Consumer Sentinel, a secure online database available to thousands of
    >> | civil and criminal law enforcement agencies worldwide. Your reference
    >> | number is: 19642372
    >> |
    >> | [...]
    >> |
    >> | They detect Linux, give it a bad DSDT table, one that looks ok at a
    >> | glance, but broken in subtle ways so that some of it works, but not
    >> | correctly.
    >> |
    >> | You call them to ask why their board won't run Linux.
    >> |
    >> | They tell you to buy Vista.
    >> |
    >> | They're basically rubbing Microsoft's back.
    >> `----
    >>
    >> http://ubuntuforums.org/showthread.php?t=869249

    >
    >
    > Fscking BASTARDS!
    >
    > I have always suspected this FoxCON of material con jobbie.
    > Thank goodness I never bought dodgy Foxcon mboards.
    >
    > There is a lot of dicing about and bundling that tells you
    > there is something wrong with their business - its all a con job
    > to bundle micoshaftee vendor lock in things with the mboard.
    > Now its gone official, the anti-trust complaints should be
    > widened and micoshaft banned from trading me thinks along
    > with Foxcon for their big con.
    >
    > Did Balmer discuss foxcon con job with Nellie Kroes when he parachuted
    > in to the EU?


    Sweaty the Impaler: "The BIOS ain't done until Lunix-fsckin-cancer won't run."

    - --
    ~~ Best of wishes

    Welcome to standards-compliant Web browsing. http://www.spreadfirefox.com/
    http://Schestowitz.com | Free as in Free Beer | PGP-Key: 0x74572E8E
    Load average (/proc/loadavg): 0.75 0.82 0.80 4/272 21599
    http://iuron.com - semantic search engine project initiative
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.9 (GNU/Linux)

    iEYEARECAAYFAkiK0wwACgkQU4xAY3RXLo7jSQCfbQdTBmyLEk KlOnIjdgIR/254
    gE4AoKa//9IVdqaoUwk0Wxc050SWrbb3
    =69ig
    -----END PGP SIGNATURE-----

  12. Re: [News] Foxconn Reported to FTC for Sabotage Against Linux

    Linonut writes:

    > * Tim Smith peremptorily fired off this memo:
    >
    >> How does the motherboard know you are using Linux? Is it a setting
    >> somewhere in the non-volatile BIOS settings? If so, what happens if you
    >> simply change the setting to say you are running Windows?

    >
    > That would be hard to say. If you read the article, it notes that
    > different tables are loaded depending on the OS, and that the Linux
    > table is faulty. The article describes how to read the ACPI tables from
    > the /sys/firmware/... directory, edit the code, save the file, make it
    > part of the initrd system so that the kernel will use it.
    >
    > On my DELL, the only reference to an OS is:
    >
    > Name (W98S, "Microsoft Windows")
    > Name (NT5S, "Microsoft Windows NT")
    > Name (WINM, "Microsoft WindowsME: Millennium Edition")
    > Name (WXP, "Windows 2001")
    > Name (WLG, "Windows 2006")
    >
    > and then it sets up a bit-masked, with a different bit set depending on
    > which version of Windows, and bit 0 if "none of the above". Then a lot
    > of decisions are made based on that bit value such as calling Notify()
    > and Sleep() functions with varying values.
    >
    > The guy in this article
    > gets this "admission" from FoxConn:
    >
    > This board was never certified for Linux. It is only certified for
    > Vista. See URL below. So please test under Vista. Does this issue
    > also occured under Vista or Winxp?
    >
    > He gets pretty irate, too.
    >
    > I saw you targeting Linux with an intentionally broken ACPI table,
    > you also have one for NT and ME, a separate one for newer NT variants
    > like 2000, XP, Vista, and 2003/2008 Server, I'm sure that if you
    > actually wrote to Intel ACPI specs instead of whatever quirks you can
    > get away with for 8 versions of Windows and then go to the trouble of
    > giving a botched table to Linux (How much *is* Microsoft paying you?)
    > it would end up working a lot better, but I have this idea you don't
    > want it to.
    >
    > Collusion, laziness, not caring about the non-Windows market, or just
    > plain stupidity?
    >
    > One wonders, when Foxconn says "we only support Vista", yet the ACPI
    > code contains explicit references to Linux that cause bad data to be
    > loaded that makes Linux screw up in power-management situations.


    Wonderful googling from the resident fraud. Sounds almost as easy as
    trying to get a Debian system to use a splash screen:


    http://www.linuxquestions.org/questi...g-boot-379559/

    Still, all good fun! :-)


    (for the humour impaired, it has got a little bit better but not by
    much)



    --
    "Your Ref header shows bt.com. The "kustomkomputer" troll nymshifted again?"
    -- William Poaster boring people to death with his header compulsion in comp.os.linux.advocacy

  13. Re: [News] Foxconn Reported to FTC for Sabotage Against Linux

    * Tim Smith peremptorily fired off this memo:

    > In article ,
    > Linonut wrote:
    >> One wonders, when Foxconn says "we only support Vista", yet the ACPI
    >> code contains explicit references to Linux that cause bad data to be
    >> loaded that makes Linux screw up in power-management situations.

    >
    > Well, notice that people are saying that the ACPI code it has for Linux
    > is for the wrong hardware, or something like that. Does this mean they
    > have other boards where ACPI *does* work for Linux?
    >
    > If so, then the explanation is obvious: they copied the BIOS code from
    > one of their other boards, and fixed the parts that were wrong for Vista
    > on the new board. They left the Linux parts as is, since they decided
    > for some reason to only support Vista on this board.


    Could well be. But then they follow up on this decision with, I think,
    negligence, or at least without due diligence to their customers.

    --
    BELA LUGOSI is my co-pilot ...

  14. Re: [News] Foxconn Reported to FTC for Sabotage Against Linux

    On Fri, 25 Jul 2008 23:58:54 -0400, DFS wrote:

    > Linonut wrote:
    >
    >> My Dell laptop has an issue when I boot to the DSL (Damn Small Linux)
    >> that's part of Billix. The author of that package, Bill Childers sent
    >> me an email indicating to use the "acpi=off" option, and that did the
    >> trick for me.

    >
    > That's Linux cripple-ware for you - disable features just so it will run.
    >
    > Even the "best" (that's rich), "most popular" (also rich) Linux distro,
    > Ubuntu, often chokes and freezes unless you use ACPI=off.
    >
    > Linux = computing asceticism


    Classic Linux....

    ACPI and Power Management has been a problem for Linux for years and still
    they have not made it work as well as it does with Windows.

    Here is an example of a Linux pre-loaded laptop that has a LOT of things
    that don't work.
    Could you imagine buying this thing and finding out how much you paid for
    is useless using Linux, but only after you booted the thing and read a
    Readme file?

    I would be pissed!!

    I'll bet a lot of people returned this POS...
    After the initial boot and logon, we were faced with a clean,
    well-organized desktop, but one element caught our eye right away¡Xa text
    document called ThinkPad Readme.txt. We launched it and found that the
    document¡¦s first line was ¡§Limitations, Workarounds and How To¡¦s for
    SLED10.¡¨ We did not like the sound of that ¡§limitations¡¨ element. After
    all, isn¡¦t Linux supposed to be about overcoming limitations?

    The first part of the document covered ¡§features not supported.¡¨ Some of
    those features are:

    * ThinkVantage Active Protection System.
    * ThinkVantage Access Connections for SUSE Linux
    * ThinkPad Configuration for SUSE Linux
    * ThinkPad Power Manager for SUSE Linux
    * Wireless WAN Adapter
    * ThinkVantage Button
    * (Intel Graphics System) DVI Output

    From our point of view, Lenovo was not off to a good start.

    http://www.channelinsider.com/c/a/Re...-of-Questions/


    --
    Moshe Goldfarb
    Collector of soaps from around the globe.
    Please visit The Hall of Linux Idiots:
    http://linuxidiots.blogspot.com/

  15. Re: [News] Foxconn Reported to FTC for Sabotage Against Linux

    On Sat, 26 Jul 2008 07:32:28 +0000, Roy Schestowitz wrote:

    > -----BEGIN PGP SIGNED MESSAGE-----
    > Hash: SHA1
    >
    > ____/ 7 on Friday 25 July 2008 21:40 : \____
    >
    >> Roy Schestowitz wrote:
    >>
    >>> -----BEGIN PGP SIGNED MESSAGE-----
    >>> Hash: SHA1
    >>>
    >>> Foxconn deliberately sabotaging their BIOS to destroy Linux ACPI
    >>>
    >>> ,----[ Quote ]
    >>> | Complained to the Federal Trade Commission
    >>> |
    >>> | http://www.ftc.gov
    >>> |
    >>> | Foxconn
    >>> | 458 E. Lambert Road Fullerton
    >>> | Fullerton, CA
    >>> | 92835
    >>> |
    >>> | FOXCONN PHONE NUMBER: 714-871-9968
    >>> |
    >>> | Company sold me a computer motherboard, model G33M-S, claiming that it
    >>> | was compliant with ACPI versions 1.0, 2.0, and 3.0.
    >>> |
    >>> | Linux and FreeBSD do not work with this motherboard due to it's ACPI
    >>> | configuration, using a disassembler program, I have found that it
    >>> | detects Linux specifically and points it to bad DSDT tables, thereby
    >>> | corrupting it's hardware support, changing this and setting the system
    >>> | to override the BIOS ACPI DSDT tables with a customized version that
    >>> | passes the Windows versions to Linux gives Linux ACPI support stated on
    >>> | the box, I am complaining because I feel this violates an anti-trust
    >>> | provision in the Microsoft settlement, I further believe that Microsoft
    >>> | is giving Foxconn incentives to cripple their motherboards if you try to
    >>> | boot to a non-Windows OS.
    >>> |
    >>> | We have received your complaint.
    >>> |
    >>> | Thank you for contacting the FTC. Your complaint has been entered into
    >>> | Consumer Sentinel, a secure online database available to thousands of
    >>> | civil and criminal law enforcement agencies worldwide. Your reference
    >>> | number is: 19642372
    >>> |
    >>> | [...]
    >>> |
    >>> | They detect Linux, give it a bad DSDT table, one that looks ok at a
    >>> | glance, but broken in subtle ways so that some of it works, but not
    >>> | correctly.
    >>> |
    >>> | You call them to ask why their board won't run Linux.
    >>> |
    >>> | They tell you to buy Vista.
    >>> |
    >>> | They're basically rubbing Microsoft's back.
    >>> `----
    >>>
    >>> http://ubuntuforums.org/showthread.php?t=869249

    >>
    >>
    >> Fscking BASTARDS!
    >>
    >> I have always suspected this FoxCON of material con jobbie.
    >> Thank goodness I never bought dodgy Foxcon mboards.
    >>
    >> There is a lot of dicing about and bundling that tells you
    >> there is something wrong with their business - its all a con job
    >> to bundle micoshaftee vendor lock in things with the mboard.
    >> Now its gone official, the anti-trust complaints should be
    >> widened and micoshaft banned from trading me thinks along
    >> with Foxcon for their big con.
    >>
    >> Did Balmer discuss foxcon con job with Nellie Kroes when he parachuted
    >> in to the EU?

    >
    > Sweaty the Impaler: "The BIOS ain't done until Lunix-fsckin-cancer won't run."


    Why bother?

    It looks like the people preloading Linux laptops are doing a fine job of
    ensuring Linux is a piker......

    http://www.channelinsider.com/c/a/Re...-of-Questions/

    After the initial boot and logon, we were faced with a clean,
    well-organized desktop, but one element caught our eye right away¡Xa text
    document called ThinkPad Readme.txt. We launched it and found that the
    document¡¦s first line was ¡§Limitations, Workarounds and How To¡¦s for
    SLED10.¡¨ We did not like the sound of that ¡§limitations¡¨ element. After
    all, isn¡¦t Linux supposed to be about overcoming limitations?

    The first part of the document covered ¡§features not supported.¡¨ Some of
    those features are:

    * ThinkVantage Active Protection System.
    * ThinkVantage Access Connections for SUSE Linux
    * ThinkPad Configuration for SUSE Linux
    * ThinkPad Power Manager for SUSE Linux
    * Wireless WAN Adapter
    * ThinkVantage Button
    * (Intel Graphics System) DVI Output

    From our point of view, Lenovo was not off to a good start.


    All Ballmer has to do is sit back and laugh his ass off.
    I'm sure he is.



    --
    Moshe Goldfarb
    Collector of soaps from around the globe.
    Please visit The Hall of Linux Idiots:
    http://linuxidiots.blogspot.com/

  16. Re: [News] Foxconn Reported to FTC for Sabotage Against Linux

    In comp.os.linux.advocacy, Linonut

    wrote
    on Fri, 25 Jul 2008 22:42:48 -0400
    :
    > * Tim Smith peremptorily fired off this memo:
    >
    >> How does the motherboard know you are using Linux? Is it a setting
    >> somewhere in the non-volatile BIOS settings? If so, what happens if you
    >> simply change the setting to say you are running Windows?

    >
    > That would be hard to say. If you read the article, it notes that
    > different tables are loaded depending on the OS, and that the Linux
    > table is faulty. The article describes how to read the ACPI tables from
    > the /sys/firmware/... directory, edit the code, save the file, make it
    > part of the initrd system so that the kernel will use it.
    >
    > On my DELL, the only reference to an OS is:
    >
    > Name (W98S, "Microsoft Windows")
    > Name (NT5S, "Microsoft Windows NT")
    > Name (WINM, "Microsoft WindowsME: Millennium Edition")
    > Name (WXP, "Windows 2001")
    > Name (WLG, "Windows 2006")


    This would be an interesting[*] requirement to preinstall
    Microsoft Windows on hardware...make sure that the BIOS
    checks that it is indeed running Genuine Microsoft Windows
    during POST, somehow.

    That would be written into the purchase contract, tested
    on an occasional basis, and of course would ensure that
    all Microsoft preinstalled hardware can run *nothing else*.

    Not even ReactOS.

    The purchase contract would also require that all machines
    have this BIOS.

    Illegal? An interesting question.

    >
    > and then it sets up a bit-masked, with a different bit set depending on
    > which version of Windows, and bit 0 if "none of the above". Then a lot
    > of decisions are made based on that bit value such as calling Notify()
    > and Sleep() functions with varying values.
    >
    > The guy in this article
    > gets this "admission" from FoxConn:
    >
    > This board was never certified for Linux. It is only certified for
    > Vista. See URL below. So please test under Vista. Does this issue
    > also occured under Vista or Winxp?


    Who's doing the certification?

    >
    > He gets pretty irate, too.
    >
    > I saw you targeting Linux with an intentionally broken ACPI table,
    > you also have one for NT and ME, a separate one for newer NT variants
    > like 2000, XP, Vista, and 2003/2008 Server, I'm sure that if you
    > actually wrote to Intel ACPI specs instead of whatever quirks you can
    > get away with for 8 versions of Windows and then go to the trouble of
    > giving a botched table to Linux (How much *is* Microsoft paying you?)
    > it would end up working a lot better, but I have this idea you don't
    > want it to.
    >
    > Collusion, laziness, not caring about the non-Windows market, or just
    > plain stupidity?


    Stupidity would work for most. ;-)

    >
    > One wonders, when Foxconn says "we only support Vista", yet the ACPI
    > code contains explicit references to Linux that cause bad data to be
    > loaded that makes Linux screw up in power-management situations.
    >

    [*] though not in a good way.

    --
    #191, ewill3@earthlink.net
    Been there, done that, didn't get the T-shirt.
    ** Posted from http://www.teranews.com **

+ Reply to Thread