From: Norbert van Nobelen <norbert-kernel@edusupport.nl>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DVD-RW writes but doesn't read
Date: Wed, 22 Dec 2004 07:51:46 +0100 [thread overview]
Message-ID: <200412220751.46781.norbert-kernel@edusupport.nl> (raw)
In-Reply-To: <cone.1103672037.983890.28853.502@pc.kolivas.org>
Did you try one of the disks you have written with it in another dvdplayer
yet?
If the written dvds really work, then it is clearly a miracle (-:. The first
thing the drive does, is a read action to see if it has an empty disc or
something like multisession. If the drive reading is so terrible, that action
should fail most of the time too.
On Wednesday 22 December 2004 00:33, you wrote:
> Hi Jens et al
>
> I have a laptop DVD-RW that is working fine when burning but has endless
> streams of errors with any kernel I try when trying to read anything
> (cd/dvd audio/video/data).
>
> hdc: command error: status=0x51 { DriveReady SeekComplete Error }
> hdc: command error: error=0x50
> ide: failed opcode was 100
> end_request: I/O error, dev hdc, sector 571832
> Buffer I/O error on device hdc, logical block 71479
>
> If I'm persistent I can read the data off the drive but I'll probably
> kill the drive in the process. It doesn't matter what iosched I use but I
> use cfq by default. I've tried disabling dma and so on without success. Any
> ideas?
>
> Con
>
>
> Here is some relevant data
>
> lspci -vvv
>
> 00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4) Ultra ATA
> Storage Controller (rev 03) (prog-if 8a [Master SecP PriP])
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
> Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 0
> Interrupt: pin A routed to IRQ 10
> Region 0: I/O ports at <unassigned>
> Region 1: I/O ports at <unassigned>
> Region 2: I/O ports at <unassigned>
> Region 3: I/O ports at <unassigned>
> Region 4: I/O ports at 1100 [size=16]
> Region 5: Memory at 3e000000 (32-bit, non-prefetchable) [size=1K]
>
>
> hdparm -i /dev/hdc
>
> /dev/hdc:
>
> Model=MATSHITADVD-RAM UJ-820S, FwRev=1.00, SerialNo=
> Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
> RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
> BuffType=unknown, BuffSize=0kB, MaxMultSect=0
> (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
> IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
> PIO modes: pio0 pio1 pio2 pio3 pio4
> DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2
> UDMA modes: udma0 udma1 *udma2
> AdvancedPM=no
> Drive conforms to: device does not report version:
>
> * signifies the current active mode
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-12-22 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 23:33 DVD-RW writes but doesn't read Con Kolivas
2004-12-22 6:51 ` Norbert van Nobelen [this message]
2004-12-22 8:56 ` Con Kolivas
-- strict thread matches above, loose matches on Subject: below --
2004-12-22 8:40 surya
2005-02-04 5:05 Samuel Torres
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=200412220751.46781.norbert-kernel@edusupport.nl \
--to=norbert-kernel@edusupport.nl \
--cc=kernel@kolivas.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