Re: no atapi cdrecord burning with 2.6.0-test11-bk10 / bk13

From: Gene Heskett
Date: Wed Dec 17 2003 - 12:29:49 EST


On Wednesday 17 December 2003 11:49, Jens Axboe wrote:
>On Wed, Dec 17 2003, Gene Heskett wrote:
>> On Wednesday 17 December 2003 11:25, Thomas Voegtle wrote:
>> >On Wed, 17 Dec 2003, Gene Heskett wrote:
>> >> I take that it is attempting to scan all 8 addresses of the
>> >> scsi bus even though its actually hitting the atapi stuff? Or
>> >> do I need an even fresher version of cdrecord? or libscg?
>> >
>> >Sorry, I shortend my output of cdrecord. With 2.6.0-test11 it
>> > looks like this:
>> >
>> >Using libscg version 'schily-0.7'
>> >scsibus0:
>> >cdrecord: Warning: controller returns wrong size for CD
>> > capabilities page. 0,0,0 0) 'CREATIVE' ' CD5233E '
>> > '2.05' Removable CD-ROM 0,1,0 1) 'PLEXTOR ' 'CD-R
>> > PX-W1610A' '1.04' Removable CD-ROM 0,2,0 2) *
>> > 0,3,0 3) *
>> > 0,4,0 4) *
>> > 0,5,0 5) *
>> > 0,6,0 6) *
>> > 0,7,0 7) *
>>
>> I see. I also don't see the warning you are getting, and this may
>> be the reason you can't burn. I also do not have the normal cdrom
>> as device 0. What happens if you swap the master/slave jumpers
>> and put the recorder first? It might be worth a try, and any
>> changes in how it works would be a clue as to where the real
>> stoppage is.
>
>The reason is that Thomas is using ATAPI which will go through
>CDROM_SEND_PACKET (which is broken in -bk), while you are probably
> not using that transport (and thus going to SG_IO directly, which
> works).

I'm using /dev/hdc for burning in the k3b configuration screens,
however that path may actually be defined. I haven't quite "grok"ed
all the details, but it works, and works with <10% of the cpu
involved when burning.

To me, thats a roaring success :-)

--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/