mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jarno Paananen <jpaana@s2.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [sata] libata update
Date: Wed, 31 Mar 2004 04:43:39 +0300	[thread overview]
Message-ID: <m34qs5iyes.fsf@kalahari.s2.org> (raw)
In-Reply-To: <4069FF46.7090604@pobox.com> (Jeff Garzik's message of "Tue, 30 Mar 2004 18:14:14 -0500")

Jeff Garzik <jgarzik@pobox.com> writes:

> Petr Sebor wrote:
>> Hi Jeff,
>> I have upgraded from 2.6.3 to 2.6.5-rc3 and can't see the secondary
>> sata drive anymore...
>
> Does this patch fix it?

I'm using the 2.4 kernel version (would be using 2.6 if there was
support for IT8212 ide-"raid" controller, hint hint Bart :) and had
the same problem. This fixed it:

libata version 1.02 loaded.
sata_via version 0.20
sata_via(00:0f.0): routed to hard irq line 5
ata1: SATA max UDMA/133 cmd 0xB400 ctl 0xB802 bmdma 0xC400 irq 20
ata2: SATA max UDMA/133 cmd 0xBC00 ctl 0xC002 bmdma 0xC408 irq 20
ata1: dev 0 cfg 49:2f00 82:346b 83:7f21 84:4003 85:3469 86:3e01
87:4003 88:407f
ata1: dev 0 ATA, max UDMA/133, 72303840 sectors (lba48)
ata1: dev 0 configured for UDMA/133
ata2: dev 0 cfg 49:2f00 82:346b 83:7f21 84:4003 85:3469 86:3e01
87:4003 88:203f
ata2: dev 0 ATA, max UDMA/100, 488397168 sectors (lba48)
ata2: dev 0 configured for UDMA/100
scsi1 : sata_via
scsi2 : sata_via
  Vendor: ATA       Model: WDC WD360GD-00FN  Rev: 1.02
  Type:   Direct-Access                      ANSI SCSI revision: 05
  Vendor: ATA       Model: WDC WD2500JD-22F  Rev: 1.02
  Type:   Direct-Access                      ANSI SCSI revision: 05
Attached scsi disk sda at scsi0, channel 0, id 3, lun 0
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
Attached scsi disk sdc at scsi2, channel 0, id 0, lun 0
SCSI device sda: 71833096 512-byte hdwr sectors (36779 MB)
 sda: sda1 sda2 sda3 < sda5 sda6 sda7 >
SCSI device sdb: 72303840 512-byte hdwr sectors (37020 MB)
 sdb: sdb1
SCSI device sdc: 488397168 512-byte hdwr sectors (250059 MB)
 sdc: sdc1 < sdc5 sdc6 >

(sda is a real SCSI disk)

Thanks,

// Jarno

  reply	other threads:[~2004-03-31  1:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-27  2:27 Jeff Garzik
2004-03-30 22:59 ` Petr Sebor
2004-03-30 23:14   ` Jeff Garzik
2004-03-31  1:43     ` Jarno Paananen [this message]
2004-03-31  1:50       ` Jeff Garzik
2004-03-31  1:53         ` Jarno Paananen
2004-03-30 23:16   ` Jeff Garzik
2004-03-30 23:26     ` Petr Sebor
2004-03-30 23:39     ` Bartlomiej Zolnierkiewicz
2004-03-30 23:47       ` Jeff Garzik
2004-03-31  0:28         ` Bartlomiej Zolnierkiewicz
2004-03-31  2:33           ` Jeff Garzik
2004-03-31  8:24   ` [PATCH] " Jeff Garzik
2004-03-31 11:50     ` Petr Sebor
2004-03-31 16:41       ` Jarno Paananen
2004-03-31 16:48       ` Jeff Garzik
2004-03-31 17:21         ` Jarno Paananen
2004-03-31 21:04           ` Jeff Garzik
2004-04-01  7:35             ` Petr Sebor
  -- strict thread matches above, loose matches on Subject: below --
2004-04-25  2:48 Jeff Garzik
2004-04-25  4:24 ` J. Ryan Earl
2004-03-31 21:02 Jeff Garzik
2004-04-03  0:45 ` Erik Andersen
2004-03-30 21:31 Jeff Garzik
2004-03-27 22:07 Henrik Gustafsson
2004-03-27 22:20 ` Jeff Garzik
2004-03-23 18:04 Jeff Garzik

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=m34qs5iyes.fsf@kalahari.s2.org \
    --to=jpaana@s2.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

Powered by JetHome