All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Sean Bruno <sean.bruno@dsl-only.net>
Cc: "Hodle, Brian" <BHodle@harcroschem.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'ipsoa@posiden.hopto.org'" <ipsoa@posiden.hopto.org>
Subject: Re: ASUS K8N-DL Beta BIOS
Date: Tue, 05 Jul 2005 16:54:38 +0100	[thread overview]
Message-ID: <1120578876.23127.19.camel@localhost.localdomain> (raw)
In-Reply-To: <1120246927.2764.26.camel@home-lap>

On Gwe, 2005-07-01 at 20:42, Sean Bruno wrote:
> This is pretty much the reaction that I am getting from calling ASUS
> tech support.  They have told me on several occasions that they will
> "call me back" and never do. 

Ditto with problems I've seen on ASUS boards, even the high end ones. 

  parent reply	other threads:[~2005-07-05 16:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01 19:19 ASUS K8N-DL Beta BIOS Hodle, Brian
2005-07-01 19:42 ` Sean Bruno
2005-07-02 17:43   ` Alistair John Strachan
2005-07-02 19:44     ` Andi Kleen
2005-07-03  4:32       ` Sean Bruno
2005-07-03  7:37         ` Alexander Nyberg
2005-07-04 20:06           ` Sean Bruno
2005-07-04 21:02             ` Sean Bruno
2005-07-04 21:26               ` Andi Kleen
2005-07-04 21:39                 ` Sean Bruno
2005-07-04 21:43               ` [WORKAROUND] For ASUS K8N-DL PCI allocation issues Sean Bruno
2005-07-04 21:37             ` ASUS K8N-DL Beta BIOS Andi Kleen
2005-07-05 15:54   ` Alan Cox [this message]
2005-07-05 16:43     ` Lee Revell
2005-07-03  5:05 ` Karim Yaghmour
  -- strict thread matches above, loose matches on Subject: below --
2005-07-05  4:00 Hodle, Brian
     [not found] <4lznf-1XY-7@gated-at.bofh.it>
     [not found] ` <4lzQi-2fw-21@gated-at.bofh.it>
2005-07-03  4:37   ` Robert Hancock
2005-06-28 22:05 Sean Bruno
2005-06-29  1:46 ` Karim Yaghmour

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=1120578876.23127.19.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=BHodle@harcroschem.com \
    --cc=ipsoa@posiden.hopto.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sean.bruno@dsl-only.net \
    /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.