From: Daniel Schroeder <sec@dschroeder.info>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: [MCP-55] IDE problem after bios update
Date: Mon, 10 Mar 2008 21:08:55 +0100 [thread overview]
Message-ID: <47D59557.6040904@dschroeder.info> (raw)
In-Reply-To: <20080222195833.37c88767@core>
Alan Cox wrote:
> On Fri, 22 Feb 2008 20:57:54 +0100
> Daniel Schroeder <sec@dschroeder.info> wrote:
>
>> hi there,
>>
>> this is an asus m2n32-sli deluxe with nvidia chipset. After updating the
>> bios from 1503 to 1701 following in dmesg, and ide drive doesn't work.
>> Kernel is 2.6.24.2
>
> If it broke with the BIOS change you need to report it to the BIOS vendor
>
> Feb 21 22:37:02 isla-magica NFORCE-MCP55: IDE port disabled
>
reported to bios vendor. Usual "turn it off and on again", "reset cmos
and install the newest chipset driver from nvidia.de"
this is a link to the same or similar problem and the following command
"hdparm -w /dev/hda" resurrects my drive.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/182996/comments/4
prev parent reply other threads:[~2008-03-10 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 19:57 [MCP-55] IDE problem after bios update Daniel Schroeder
2008-02-22 19:58 ` Alan Cox
2008-03-10 20:08 ` Daniel Schroeder [this message]
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=47D59557.6040904@dschroeder.info \
--to=sec@dschroeder.info \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).