From: Erik Steffl <steffl@bigfoot.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org, Ben Collins <bcollins@debian.org>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: 2.6.0-test9 SATA and 1394 problems
Date: Tue, 04 Nov 2003 16:22:41 -0800 [thread overview]
Message-ID: <3FA842D1.4090502@bigfoot.com> (raw)
In-Reply-To: <5.2.0.9.0.20031104234330.02451b70@mailhost.ivimey.org>
Ruth Ivimey-Cook wrote:
> Folks,
>
> I have been running 2.6.0-t9 on an Asus A7V600 VIA VT600-based MB for a
> few days now. All seems relatively stable, which is good. A few issues
> to report, though, the most serious of which is that my SATA controller
> (VIA 8237 Southbridge) is only detected properly when the machine is
> fully power-cycled (that is, plug out the back, not just soft-off). When
> that is done, all seems well and the drives run fine. If you reboot the
> machine without a full power-cycle, the SATA controller is detected but
> no drives are found. Drives are new Seagate 7200.7 SATA 120Gig. I've
> tried disabling acpi, setting pci=noacpi and setting pci=usepirqmask as
> suggested in the acpi startup messages, but none of this helped.
I have similar problem with intel D865PERL motherboard. only it
happens rarely. It seems that _sometime_ when I restart system the BIOS
does not recognize SATA drives (it waits for a fairly long time), linux
then does not recognize SATA drives either.
it doesn't seem to be linux specific (IIRC it happened when rebooting
win xp pro as well).
erik
prev parent reply other threads:[~2003-11-05 0:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 0:07 2.6.0-test9 SATA and 1394 problems Ruth Ivimey-Cook
2003-11-05 0:22 ` Erik Steffl [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=3FA842D1.4090502@bigfoot.com \
--to=steffl@bigfoot.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=bcollins@debian.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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