From: Parag Warudkar <kernel-stuff@comcast.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Chris Boot <bootc@bootc.net>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: IDE CDROM - No DMA
Date: Sun, 12 Mar 2006 14:47:26 -0500 [thread overview]
Message-ID: <200603121447.26252.kernel-stuff@comcast.net> (raw)
In-Reply-To: <200603121429.06372.kernel-stuff@comcast.net>
On Sunday 12 March 2006 14:29, Parag Warudkar wrote:
> Funny situation - I cannot figure what my root device is. Earlier without
> the patch it was /dev/sda3 and now I try everything (hda3, hdb3, hdc3,
> hdd3, sda3, sdb3...) but it panics - not able to mount rootfs.
Never mind - I am dumb enough to not realize I needed SCSI Disk in built or as
modules copied over to proper place :)
It boots but I don't think DMA is in effect on the CDROM drive though - (I get
3Mb/s transfer speeds from it. LS of a 1500 file directory is too slow).
dmesg says ata2 configured for UDMA/33 but doesn't seem like it has
actually.
Memory: 2065588k/2087756k available (2495k kernel code, 21676k reserved, 722k
data, 216k init, 0k highmem)
libata version 1.20 loaded.
ata_piix 0000:00:1f.2: version 1.05-ac7
ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xBFA0 irq 14
ata1: dev 0 cfg 49:2f00 82:746b 83:7f09 84:6023 85:7469 86:3e09 87:6023
88:203f
ata1: dev 0 ATA-6, max UDMA/100, 153356490 sectors: LBA48
ata1: dev 0 configured for UDMA/100
scsi0 : ata_piix
ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xBFA8 irq 15
ata2: dev 0 cfg 49:0f00 82:0210 83:4011 84:4000 85:0000 86:0001 87:4000
88:0407
ata2: dev 0 ATAPI, max UDMA/33
ata2(0): applying bridge limits
ata2: dev 0 configured for UDMA/33
scsi1 : ata_piix
EXT3-fs: mounted filesystem with ordered data mode.
Hard disk is fine - gives around 31 Mb/S.
Parag
prev parent reply other threads:[~2006-03-12 19:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 23:42 IDE CDROM - No DMA Parag Warudkar
2006-03-12 6:28 ` Parag Warudkar
2006-03-12 15:53 ` Chris Boot
2006-03-12 17:09 ` Parag Warudkar
2006-03-12 18:03 ` Alan Cox
2006-03-12 19:29 ` Parag Warudkar
2006-03-12 19:47 ` Parag Warudkar [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=200603121447.26252.kernel-stuff@comcast.net \
--to=kernel-stuff@comcast.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bootc@bootc.net \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).