Re: Geting rid of ide-scsi ?
On Fri, Dec 19, 2003 at 05:15:31PM +0200, Thanos Kyritsis wrote: > So, what if the .bin is in 2352 byte sectors format ? My question exactly. And right now, the answer is use cdrdao and ide-scsi. Maybe at some point cdrecord will add support for that or cdrdao will be updated.
Re: Geting rid of ide-scsi ?
On Fri, Dec 19, 2003 at 05:15:31PM +0200, Thanos Kyritsis wrote: > So, what if the .bin is in 2352 byte sectors format ? My question exactly. And right now, the answer is use cdrdao and ide-scsi. Maybe at some point cdrecord will add support for that or cdrdao will be updated. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Need help with Sony DW-U10A
Hi! I've just purchased my first dvd-writer and it works as well as it is possible! All of you write about the problems! What kind of problem are you writing about??? Just normally make the contact between dvd-writer and your PC (IDE cable, for example secondary master), and Windows XP realizes this hardware, no need any installation! Just use : NERO 6!!! This software recorded my first dwd-rw disc completely!There were no problems! Have a lot of fun! Laci from Hungary (If you have any suggestion, just mail me! [EMAIL PROTECTED])
Re: Need help with Sony DW-U10A
Hi! I've just purchased my first dvd-writer and it works as well as it is possible! All of you write about the problems! What kind of problem are you writing about??? Just normally make the contact between dvd-writer and your PC (IDE cable, for example secondary master), and Windows XP realizes this hardware, no need any installation! Just use : NERO 6!!! This software recorded my first dwd-rw disc completely!There were no problems! Have a lot of fun! Laci from Hungary (If you have any suggestion, just mail me! [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Pioneer DVR-106D issues
> >-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing > >-fno-common -mpreferred-stack-boundary=2 -march=pentium3 > >-fomit-frame-pointer > > In the Schily makefile system (Developer set up) these warning options are > used: > > CWOPTS= -Wall -Wtraditional \ > -Wshadow -Wmissing-prototypes -Wstrict-prototypes > > -Wtraditional more and more created problems with GCC-3.x -Wtraditional clearly does not fit in Linux kernel makefiles - the kernel uses ISO C constructions extensively. So -Wshadow and -Wmissing-prototypes might be worth trying. I did try them both (compiling 2.6.0, the latest stable kernel, with allmodconfig - i.e. all drivers compiled as modules, except rebuilding Adaptec firmware which I have no tools for and except kernel debug info since it generates HUGE output files and I was running out of disk space) and compared the build logs. -Wshadow gave 5 warnings in build tools (firmware image generation and conversion etc) and -Wmissing-prototypes gave 57 warnings but also only in build tools (documentation generation, module generation, dependency generation, kernel symbol table generation, console character map generation, initial ramfs generation, ATM firmware image generation and x86 boot image generation). No single additional warning in kernel code itself! So adding these warning options would improve the build tools but not the kernel itself (the build tools obviously work, dependency generation is the only one that could theoretically cause yet undetected problem in the real kernel). Adding them might still be worth it - _IF_ I clean the warnings first. Will see if I get time for this. So we have come up with no added warnings in the kernel code itself. I am going to try -Wcast-align next on sparc-linux since it has helped me several times in userland Sparc development. > May be the problem is that there just too many false warnings so people > did oversee the real bugs. I would not say so, when compiling my normal kernel (drivers for all the hardware that I own plus all USB drivers) with many hundreds of files, I see about 3-4 warnings scroll by, and they are easily noticed. > >other parts of the kernel, IDE code and drivers use strongly typed > >function pointers everywhere. Vast mayority of function parameters are > >also strongly typed for any non-atomic types. The only functions I found > >that have void* arguments that are not IO addresses are the following: > _You_ are looking at the wrong places :-( > > The important things are called via function pointers that are in > a structure... Please reread what I said. All _function pointers_ (inside structs) are strongly typed. See include/linux/ide.h yourself if you do not believe! In addition to this, the majority of other functions have prototypes with strongly typed arguments (except the functions I showed and some I/O address parameters). Frohe Weinachten! -- Meelis Roos ([EMAIL PROTECTED])
Re: Pioneer DVR-106D issues
> >-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing > >-fno-common -mpreferred-stack-boundary=2 -march=pentium3 > >-fomit-frame-pointer > > In the Schily makefile system (Developer set up) these warning options are > used: > > CWOPTS= -Wall -Wtraditional \ > -Wshadow -Wmissing-prototypes -Wstrict-prototypes > > -Wtraditional more and more created problems with GCC-3.x -Wtraditional clearly does not fit in Linux kernel makefiles - the kernel uses ISO C constructions extensively. So -Wshadow and -Wmissing-prototypes might be worth trying. I did try them both (compiling 2.6.0, the latest stable kernel, with allmodconfig - i.e. all drivers compiled as modules, except rebuilding Adaptec firmware which I have no tools for and except kernel debug info since it generates HUGE output files and I was running out of disk space) and compared the build logs. -Wshadow gave 5 warnings in build tools (firmware image generation and conversion etc) and -Wmissing-prototypes gave 57 warnings but also only in build tools (documentation generation, module generation, dependency generation, kernel symbol table generation, console character map generation, initial ramfs generation, ATM firmware image generation and x86 boot image generation). No single additional warning in kernel code itself! So adding these warning options would improve the build tools but not the kernel itself (the build tools obviously work, dependency generation is the only one that could theoretically cause yet undetected problem in the real kernel). Adding them might still be worth it - _IF_ I clean the warnings first. Will see if I get time for this. So we have come up with no added warnings in the kernel code itself. I am going to try -Wcast-align next on sparc-linux since it has helped me several times in userland Sparc development. > May be the problem is that there just too many false warnings so people > did oversee the real bugs. I would not say so, when compiling my normal kernel (drivers for all the hardware that I own plus all USB drivers) with many hundreds of files, I see about 3-4 warnings scroll by, and they are easily noticed. > >other parts of the kernel, IDE code and drivers use strongly typed > >function pointers everywhere. Vast mayority of function parameters are > >also strongly typed for any non-atomic types. The only functions I found > >that have void* arguments that are not IO addresses are the following: > _You_ are looking at the wrong places :-( > > The important things are called via function pointers that are in > a structure... Please reread what I said. All _function pointers_ (inside structs) are strongly typed. See include/linux/ide.h yourself if you do not believe! In addition to this, the majority of other functions have prototypes with strongly typed arguments (except the functions I showed and some I/O address parameters). Frohe Weinachten! -- Meelis Roos ([EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Error under OSX
On Fri, Dec 19, 2003 at 01:55:57PM +0100, Joerg Schilling wrote: > >> If you have problems with the quality of the medium, it helps > >> a lot of you include a cdrecord -atip output. > > >The error message is unclaer for me: is it a bad media or nor? > > Bad media or a broken drive. ;-) OK, then here the requested output: Cdrecord-ProDVD-Clone 2.01a11 (powerpc-apple-macosx1.4) Copyright (C) 1995-2003 Jörg Schilling Unlocked features: Limited features: TOC Type: 1 = CD-ROM scsidev: 'IODVDServices' devname: 'IODVDServices' scsibus: -2 target: -2 lun: -2 cdrecord-prodvd: No such file or directory. Unable to get exclusive access to device. Cannot open SCSI driver. cdrecord-prodvd: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord-prodvd: For possible transport specifiers try 'cdrecord dev=help'. How could I send you a more usable result as the DVD is readable by the OS? Thank you very much, Grégoire http://magma.epfl.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED]
Re: Geting rid of ide-scsi ?
On 19. December 2003 at 8:21AM -0500, Rob Bogus <[EMAIL PROTECTED]> wrote: > Emmanuel Charpentier wrote: > > > I just read the release notes for the still-wet 2.6.0 Linux > > kernel. Among other thigs is mentioned the fact that the > > ide-scsi emulation module is currently broken in this kernel, > > and that there exists very few enthousiasm to fix it. > > > 1 - no, it's not totally broken > 2 - for CD/DVD burning you don't need to use it Even for external (USB 2.0 or firewire) burners? What's the interface (/dev/*) for such devices without ide-scsi?
Re: Error under OSX
On Fri, Dec 19, 2003 at 01:55:57PM +0100, Joerg Schilling wrote: > >> If you have problems with the quality of the medium, it helps > >> a lot of you include a cdrecord -atip output. > > >The error message is unclaer for me: is it a bad media or nor? > > Bad media or a broken drive. ;-) OK, then here the requested output: Cdrecord-ProDVD-Clone 2.01a11 (powerpc-apple-macosx1.4) Copyright (C) 1995-2003 Jörg Schilling Unlocked features: Limited features: TOC Type: 1 = CD-ROM scsidev: 'IODVDServices' devname: 'IODVDServices' scsibus: -2 target: -2 lun: -2 cdrecord-prodvd: No such file or directory. Unable to get exclusive access to device. Cannot open SCSI driver. cdrecord-prodvd: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord-prodvd: For possible transport specifiers try 'cdrecord dev=help'. How could I send you a more usable result as the DVD is readable by the OS? Thank you very much, Grégoire http://magma.epfl.ch/greg ICQ:16624071 mailto:[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Geting rid of ide-scsi ?
On 19. December 2003 at 8:21AM -0500, Rob Bogus <[EMAIL PROTECTED]> wrote: > Emmanuel Charpentier wrote: > > > I just read the release notes for the still-wet 2.6.0 Linux > > kernel. Among other thigs is mentioned the fact that the > > ide-scsi emulation module is currently broken in this kernel, > > and that there exists very few enthousiasm to fix it. > > > 1 - no, it's not totally broken > 2 - for CD/DVD burning you don't need to use it Even for external (USB 2.0 or firewire) burners? What's the interface (/dev/*) for such devices without ide-scsi? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dvd+rw-tools-5.14.4.7.4 / BTC - sequence error
Hello,
On Wed, 17 Dec 2003 11:00:20 +0100
Andy Polyakov <[EMAIL PROTECTED]> wrote:
> > in the company I've the same BTC drive and there I've the
> > following error:
> >
> > [EMAIL PROTECTED]:/vol/data/dvd> growisofs -dvd-compat -Z
> > /dev/scd0=myDVD.udf
> > Executing 'builtin_dd if=myDVD.udf of=/dev/scd0 obs=32k seek=0'
> > /dev/scd0: "Current Write Speed" is 4.0x1385KBps.
> > :-! "COMMAND SEQUENCE ERROR(52c00)" at 0h. Is media being read?
>
> It means every word of it. See first paragraph in Tutorial on
> dvd+rw-tools page. A.
I read this tutorial before I wrote the email. But the device
wasn't mounted and I didn't try to access the auto-mount-point.
As long as I understand the "autofs" daemon, the device is used
when the device is mounted or I try to access the mount-point.
May be I'm wrong in this.
But I had better results, when I recompiled the kernel (2.4.23)
with DMA on for CDROM. I didn't change the autofs setup and
a DVD+R was burned fine and plays also as expected.
But now when I try to burn a DVD-R (Verbatim media) it burns
and at the end I see the following:
[..]
1513848832/1529421824 (99.0%) @2.0x, remaining 0:05
1523122176/1529421824 (99.6%) @2.0x, remaining 0:02
/dev/scd0: flushing cache
/dev/scd0: updating RMA
:-( unable to CLOSE TRACK (2h/30h/05h): No medium found
/dev/scd0: closing disc
:-( unable to CLOSE DISC (2h/30h/05h): No medium found
/dev/scd0: reloading tray
At the kernel level ("dmesg") I didn't see an error.
Any ideas?
cu
rasca
--
Welchen Unterschied macht es für die Toten, die Waisen und die Heimatlosen,
ob irrsinnige Vernichtung im Namen der Diktatur oder im heiligen Namen der
Freiheit und Demokratie geschieht? - Gandhi -
Re: dvd+rw-tools-5.14.4.7.4 / BTC - sequence error
Hello,
On Wed, 17 Dec 2003 11:00:20 +0100
Andy Polyakov <[EMAIL PROTECTED]> wrote:
> > in the company I've the same BTC drive and there I've the
> > following error:
> >
> > [EMAIL PROTECTED]:/vol/data/dvd> growisofs -dvd-compat -Z /dev/scd0=myDVD.udf
> > Executing 'builtin_dd if=myDVD.udf of=/dev/scd0 obs=32k seek=0'
> > /dev/scd0: "Current Write Speed" is 4.0x1385KBps.
> > :-! "COMMAND SEQUENCE ERROR(52c00)" at 0h. Is media being read?
>
> It means every word of it. See first paragraph in Tutorial on
> dvd+rw-tools page. A.
I read this tutorial before I wrote the email. But the device
wasn't mounted and I didn't try to access the auto-mount-point.
As long as I understand the "autofs" daemon, the device is used
when the device is mounted or I try to access the mount-point.
May be I'm wrong in this.
But I had better results, when I recompiled the kernel (2.4.23)
with DMA on for CDROM. I didn't change the autofs setup and
a DVD+R was burned fine and plays also as expected.
But now when I try to burn a DVD-R (Verbatim media) it burns
and at the end I see the following:
[..]
1513848832/1529421824 (99.0%) @2.0x, remaining 0:05
1523122176/1529421824 (99.6%) @2.0x, remaining 0:02
/dev/scd0: flushing cache
/dev/scd0: updating RMA
:-( unable to CLOSE TRACK (2h/30h/05h): No medium found
/dev/scd0: closing disc
:-( unable to CLOSE DISC (2h/30h/05h): No medium found
/dev/scd0: reloading tray
At the kernel level ("dmesg") I didn't see an error.
Any ideas?
cu
rasca
--
Welchen Unterschied macht es für die Toten, die Waisen und die Heimatlosen,
ob irrsinnige Vernichtung im Namen der Diktatur oder im heiligen Namen der
Freiheit und Demokratie geschieht? - Gandhi -
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
