public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Aravamudan <nacc@us.ibm.com>
To: Karim Yaghmour <karim@opersys.com>
Cc: sean.bruno@dsl-only.net, ak@suse.de, LKML <linux-kernel@vger.kernel.org>
Subject: Re: The system works (2.6.14-rc2): functional k8n-dl
Date: Fri, 23 Sep 2005 10:16:49 -0700	[thread overview]
Message-ID: <20050923171649.GG5910@us.ibm.com> (raw)
In-Reply-To: <43332254.1040603@opersys.com>

On 22.09.2005 [17:29:56 -0400], Karim Yaghmour wrote:
> 
> Nish,
> 
> OK, I can confirm that with version 1006 of the BIOS it works flawlessly
> with Linux. I was able to install full FC4 and boot without a problem
> even with the SATA disk plugged to the nVidia controller (reading the
> archives you will see that the nVidia SATA controller is something I
> was simply unable to get working.) I didn't need to recompile anything.
> The kernel that came with FC4 worked just fine.

Great!

> This is great news. That box had been sitting on my rack for the past
> couple of months because I was just not able to get Linux to work
> properly. I had figured I would put a cheap network card in there just
> to get things started, but it really wasn't doing what I bought it
> for. Now it works as would be expected.

That's actually why I bothered sending out a report. I had *no* problems
booting with "noapic nolapic pci=noacpi" with BIOS revisions 1003 and
1004. When I saw that both you and Sean had problems, I figured I would
let you know what progress I was making.

> Hopefully next time ASUS releases a board they actually test that it
> works with all major OSes before making the release. In this case, I
> feel as if I was tricked into buying a board that really didn't perform
> as planned, and as a result I wasted lots of time which could been for
> more productive work.

Again, I find it odd that it worked OOB for me (with the aforementioned
boot params).

Regardless, I'm glad it is working for you now.

Thanks,
Nish

  parent reply	other threads:[~2005-09-23 17:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22 15:52 The system works (2.6.14-rc2): functional k8n-dl Nishanth Aravamudan
2005-09-22 17:20 ` Karim Yaghmour
2005-09-22 19:19 ` Bill Davidsen
2005-09-23 17:15   ` Nishanth Aravamudan
2005-09-23 17:43     ` Bill Davidsen
2005-09-23 17:55       ` Nishanth Aravamudan
2005-09-24 17:30         ` Bill Davidsen
2005-09-22 21:29 ` Karim Yaghmour
2005-09-23 17:08   ` Sean Bruno
2005-09-23 17:20     ` Nishanth Aravamudan
2005-09-23 17:22       ` Sean Bruno
2005-09-23 17:37         ` Nishanth Aravamudan
2005-09-23 17:16   ` Nishanth Aravamudan [this message]
2005-09-23 18:22     ` Karim Yaghmour
2005-09-23 18:16       ` Nishanth Aravamudan
2005-09-23 20:38       ` 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=20050923171649.GG5910@us.ibm.com \
    --to=nacc@us.ibm.com \
    --cc=ak@suse.de \
    --cc=karim@opersys.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox