bug-xorriso
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-xorriso] building libisofs-1.4.4, libburn-1.4.4, libisoburn-1.4


From: SASANO Takayoshi
Subject: Re: [Bug-xorriso] building libisofs-1.4.4, libburn-1.4.4, libisoburn-1.4.4 on OpenBSD
Date: Mon, 12 Sep 2016 23:42:58 +0900
User-agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (Gojō) APEL/10.8 EasyPG/1.0.0 Emacs/24.5 (x86_64-unknown-openbsd) MULE/6.0 (HANACHIRUSATO)

Hello,

>> 20160909/ahci-bh14ns48.log:
>> ^Ccdrecord: Caught interrupt.
> 
> Do i get it right that you waited a due time before you killed cdrecord ?
> 
> In this case we can use cdrecord as demo program and prove that
> the problem is not because of libburn and its NetBSD/OpenBSD adapter.

Yes, I waited about 4~5 minutes after starting cdrecord,
and I hit Ctrl-C after checking BD-R's LED is not blinking.


>> 20160909/dmesg-bh14ns48.log:
>> ahci0: port 4: 1.5Gb/s
>> cd0 at scsibus1 targ 4 lun 0: <HL-DT-ST, BD-RE BH14NS48, 1.02> ATAPI 5/cdrom 
>> removable
>
>> 20160909/dmesg-ihas524.log:
>> ahci0: port 4: 1.5Gb/s
>> cd0 at scsibus1 targ 4 lun 0: <ATAPI, iHAS524 B, AL2A> ATAPI 5/cdrom 
>> removable
>
> Looks quite equal. Slow speed is good. But how come ?
> (My test machine has eSATA which works with an external drive only if
>  curbed from 3.0 Gb/s to 1.5 Gb/s. Linux slows down after the first
>  glitches spoiled a burn run. FreeBSD 8 stays at high speed until
>  it crashes during a burn run, unless i switch to 1.5 Gb/s manually.)

Both drives use SerialATA Gen.1, 1.5GB/sec.
So there is no problem to work that speed.


> -------------------------------------------------------------------
> Problem report draft:
> -------------------------------------------------------------------
(snip)
> If you like you may change "SASANO Takayoshi" to "I" and report yourself
> while pointing to me as source of theory and SCSI/MMC knowledge.

Please change to "I" because I am not SCSI expert.
I did simply execute xorriso/cdrom to test, you analyzed the log and
pointed out the problem.


> Where shall we post this request for help ?
> As problem report ?
> On address@hidden ?

address@hidden is suitable.

Regards,
-- 
SASANO Takayoshi <address@hidden>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]