All of lore.kernel.org
 help / color / mirror / Atom feed
From: Janosch Machowinski <scotch-cGBD8117FJM@public.gmane.org>
To: Carl-Daniel Hailfinger
	<c-d.hailfinger.devel.2005-hi6Y0CQ0nG0@public.gmane.org>
Cc: Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>,
	Erik Slagter <erik-KW7PGP3XNp7a5EbDDlwbIw@public.gmane.org>,
	Hans Kristian Rosbach
	<hk-lnVXpwuIOH4XWF+eFR7m5Q@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: ACER Aspire 5000 <- Will these bios bugs ever be	fixed?
Date: Wed, 31 Aug 2005 19:51:07 +0200	[thread overview]
Message-ID: <4315EE0B.7090407@tzi.de> (raw)
In-Reply-To: <4315B00F.1080805-hi6Y0CQ0nG0@public.gmane.org>

Carl-Daniel Hailfinger schrieb:
> Alan Cox schrieb:
> 
>>On Mer, 2005-08-31 at 10:52 +0200, Erik Slagter wrote:
>>
>>
>>>Dell is even worse. If you tell them you run Linux on your laptop they
>>>will try to convince you it may damage your hardware and you won't get
>>>any guarantee whatsoever etc. (this in reply to a simple purely hardware
>>>based question)
>>
>>
>>Random Dell techies might. If you've got specific demonstrable BIOS bugs
>>in modern Dell laptops make sure the Dell Linux folks get them but in an
>>easy to reproduce form, or with a fix. If you can get something through
>>to the Dell BIOS people my experience so far is that it actually gets
>>fixed. Getting something that far into Dell is "interesting"
> 
> 
> For many vendors, contacting some higher-level staff at trade fairs gets
> you better contacts than any other method. Especially if you offer to
> supply a detailed technical description of the problem and tell them
> their engineering will find a solution inside that description. Keep
> the email address of the person you talked to and regularly bug them
> if the problem persists.
> 

What also works is starting an online petition and setting it somehow up 
on slashdot ;-). In this way the battery issue of my M6 got fixed. 
Anyway, if you contact ASUS support you don't get a promise that they 
will fix it, but at least you get some links to patches that work 
arround the problem on linuxside...

Greets
    Janosch


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  parent reply	other threads:[~2005-08-31 17:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-29 18:08 ACER Aspire 5000 Matt R Hall
     [not found] ` <20050829180845.98096.qmail-ZDCUxwME616A/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2005-08-29 22:30   ` Andreas Domfors
2005-08-31 20:19   ` Matt R Hall
2005-08-30 14:36 ` Manuel J.Galan
     [not found]   ` <loom.20050830T163344-565-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2005-08-31  8:01     ` Re: ACER Aspire 5000 <- Will these bios bugs ever be fixed? Hans Kristian Rosbach
2005-08-31  8:52       ` Erik Slagter
     [not found]         ` <1125478354.20251.5.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-08-31 10:15           ` Carl-Daniel Hailfinger
     [not found]             ` <4315832E.6040005-hi6Y0CQ0nG0@public.gmane.org>
2005-08-31 10:22               ` Erik Slagter
2005-08-31 13:10           ` Alan Cox
     [not found]             ` <1125493848.3355.8.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-08-31 13:26               ` Carl-Daniel Hailfinger
     [not found]                 ` <4315B00F.1080805-hi6Y0CQ0nG0@public.gmane.org>
2005-08-31 17:51                   ` Janosch Machowinski [this message]
2005-08-31 13:09       ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4315EE0B.7090407@tzi.de \
    --to=scotch-cgbd8117fjm@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org \
    --cc=c-d.hailfinger.devel.2005-hi6Y0CQ0nG0@public.gmane.org \
    --cc=erik-KW7PGP3XNp7a5EbDDlwbIw@public.gmane.org \
    --cc=hk-lnVXpwuIOH4XWF+eFR7m5Q@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.