public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marco Adurno <marco.adurno@dotnetitalia.it>
To: garski@poczta.onet.pl
Cc: linux-kernel@vger.kernel.org
Subject: Re: SiI3112 Serial ATA - no response on boot
Date: Tue, 11 May 2004 21:06:58 +0200	[thread overview]
Message-ID: <40A12452.7010601@dotnetitalia.it> (raw)
In-Reply-To: <200405112052.44979.garski@poczta.onet.pl>

Please,
consider also to upgrade to libata driver.
Marcin Garski wrote:
> [Please CC me on replies, I am not subscribed to the list, thanks]
> Hi,
> 
> I have a Abit NF7-S V2.0 mainboard (nForce2 chipset + SiI3112 SATA), 
> with Seagate S-ATA connected to Sil3112.
> 
> During boot i get following messages:
> SiI3112 Serial ATA: IDE controller at PCI slot 0000:01:0b.0
> SiI3112 Serial ATA: chipset revision 2
> SiI3112 Serial ATA: 100% native mode on irq 11
>     ide2: MMIO-DMA , BIOS settings: hde:pio, hdf:pio
>     ide3: MMIO-DMA , BIOS settings: hdg:pio, hdh:pio
> hde: ST380013AS, ATA DISK drive
> ide2 at 0xe083c080-0xe083c087,0xe083c08a on irq 11
> hdg: no response (status = 0xfe)
> hdg: no response (status = 0xfe), resetting drive
> hdg: no response (status = 0xfe)
> 
> Each "no response" message delays booting about 20 seconds.
> I don't have any device connected to hdg.
> I was wondering how to speed up booting, because this "hdg: no response 
> (status = 0xfe), resetting drive" info is little irritating?
> I'm running on 2.6.6 kernel (on 2.6.4 this "no response" messages also 
> appear).



      parent reply	other threads:[~2004-05-11 19:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11 18:52 SiI3112 Serial ATA - no response on boot Marcin Garski
2004-05-11 19:05 ` Marco Adurno
2004-05-12 16:51   ` Marcin Garski
2004-05-12 17:26     ` Bartlomiej Zolnierkiewicz
2004-05-12 18:14       ` Marcin Garski
2004-05-11 19:06 ` Marco Adurno [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=40A12452.7010601@dotnetitalia.it \
    --to=marco.adurno@dotnetitalia.it \
    --cc=garski@poczta.onet.pl \
    --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