public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <safemode@comcast.net>
To: Prakash Punnoor <prakash@punnoor.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: New libata PATA patch for 2.6.16-rc1
Date: Wed, 15 Mar 2006 06:29:16 -0500	[thread overview]
Message-ID: <4417FA8C.7090106@comcast.net> (raw)
In-Reply-To: <200603151154.15691.prakash@punnoor.de>

Prakash Punnoor wrote:

>Am Montag März 13 2006 23:31 schrieb Prakash Punnoor:
>  
>
>>Hi,
>>
>>I tried your ide1 patch with 2.6.16-rc6 and NFORCE2 board, thus using the
>>AMD driver (and sil sata driver).
>>    
>>
>
>[...]
>
>  
>
>>I will see how the DVD+RW drive behaves and let you know whether it makes
>>troubles. :-)
>>    
>>
>
>Ok, I am having some troubles burning CDs/DVDs. I am using k3b as front-end 
>and it has troubles to detect the type of disc inserted. If you eg insert a 
>cd-rw the dialog changes the detected medium around (about each second): 
>cd-rom, cd-rw, etc. Same with DVD+R. It detects DVD+R, waiting a second, than 
>appendable DVD+R etc. But then it thinks it is a RW so it wants to 
>blank/format/whatever it and this breaks, ie. I can't start the burning. It 
>worked fine with a DVD+RW though. And ignoring the message and blanking in 
>menu, I could also write a cd-rw.
>
>
>I am not sure what is causing the problem. Could dbus/hal be also trouble 
>makers? I don't know whether k3b is making something stupid, as well. Last 
>time I tried I had no problem with the ide driver though. So I don't know 
>whether ATAPI support in libata still needs polishing or whether Alan's PATA 
>patch is missing something or whatever...
>
>
>What infos should I provide to make diagnosis easier?
>  
>
graveman had the same problem.   I went and used cdrecord-prodvd and 
haven't had a problem with direct command line, gcombust, or xcdroast 
(those are all plain frontends to the userspace tools).   

This seems to be a userspace problem in operating with libata/pata.    
xcdroast/gcombust and regular commandline usage of cdrecord-prodvd work 
fine.

  reply	other threads:[~2006-03-15 11:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-13 15:07 New libata PATA patch for 2.6.16-rc1 Alan Cox
2006-03-13 16:39 ` Alistair John Strachan
2006-03-13 17:13   ` Alistair John Strachan
2006-03-14  1:24     ` Alan Cox
2006-03-14 10:48       ` Alistair John Strachan
2006-03-14 19:54         ` Chris Boot
2006-03-17 14:57         ` Alan Cox
2006-03-18 16:14           ` Chris Boot
2006-03-13 20:28 ` Matthieu CASTET
2006-03-13 20:41   ` Matthieu CASTET
2006-03-13 20:39 ` Kevin Radloff
2006-03-13 22:31 ` Prakash Punnoor
2006-03-15 10:54   ` Prakash Punnoor
2006-03-15 11:29     ` Ed Sweetman [this message]
2006-03-15 14:02       ` Prakash Punnoor
2006-03-14  0:39 ` Chris Boot
2006-03-14  1:23   ` Alan Cox
     [not found] <20060313195722.6ADBF1401F@rhn.tartu-labor>
2006-03-13 20:08 ` Meelis Roos
2006-03-14  1:21   ` Alan Cox
2006-03-14  7:31     ` Meelis Roos
2006-03-14  7:36     ` Meelis Roos

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=4417FA8C.7090106@comcast.net \
    --to=safemode@comcast.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prakash@punnoor.de \
    /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