Re: k3b can't find cdrecord
On Wednesday, 12/28/16 01:00:52 PM Gary Dale wrote: > On 28/12/16 12:34 PM, Alberto Luaces wrote: > > Gary Dale writes: > >> I'm running Debian/Stretch AMD64 using plasma desktop and I'm trying > >> to burn a CD image. However when I start k3b, I get an error message > >> "unable to find cdrecord executable" along with the suggestion that I > >> install cdrtools. K3b refuses to burn the CD image. > >> > >> There is no package cdrtools but there was libcdr-tools. Unfortunately > >> installing that didn't help. Google was no help and neither was a > >> search of packages.debian.org. > >> > >> I realize optical media is passé these days, but I find it difficult > >> to believe that support for burning CDs has been dropped. What do I > >> have to do to get k3b to burn a CD? > > > > You can install wodim, this is what I use and it works fine. > > Had wodim installed for a long time. One thing I find strange is that > the k3b package still refers to cdrecord instead of to wodim since it > appears to use wodim natively (locate doesn't find a cdrecord link to > wodim). I think this is what you are looking for: If you open K3b, go to the settings menu, choose "configure K3b", and then in the Settings - K3b screen choose "Programs" you will see how cdrecord is linked to wodim. (and lots of other useful stuff)
Re: k3b can't find cdrecord
On 28/12/16 12:34 PM, Alberto Luaces wrote: Gary Dale writes: I'm running Debian/Stretch AMD64 using plasma desktop and I'm trying to burn a CD image. However when I start k3b, I get an error message "unable to find cdrecord executable" along with the suggestion that I install cdrtools. K3b refuses to burn the CD image. There is no package cdrtools but there was libcdr-tools. Unfortunately installing that didn't help. Google was no help and neither was a search of packages.debian.org. I realize optical media is passé these days, but I find it difficult to believe that support for burning CDs has been dropped. What do I have to do to get k3b to burn a CD? You can install wodim, this is what I use and it works fine. Had wodim installed for a long time. One thing I find strange is that the k3b package still refers to cdrecord instead of to wodim since it appears to use wodim natively (locate doesn't find a cdrecord link to wodim).
Re: k3b can't find cdrecord
Gary Dale writes: > I'm running Debian/Stretch AMD64 using plasma desktop and I'm trying > to burn a CD image. However when I start k3b, I get an error message > "unable to find cdrecord executable" along with the suggestion that I > install cdrtools. K3b refuses to burn the CD image. > > There is no package cdrtools but there was libcdr-tools. Unfortunately > installing that didn't help. Google was no help and neither was a > search of packages.debian.org. > > I realize optical media is passé these days, but I find it difficult > to believe that support for burning CDs has been dropped. What do I > have to do to get k3b to burn a CD? > > You can install wodim, this is what I use and it works fine. -- Alberto
Re: k3b can't find cdrecord
On 28/12/16 11:29 AM, Gary Dale wrote: I'm running Debian/Stretch AMD64 using plasma desktop and I'm trying to burn a CD image. However when I start k3b, I get an error message "unable to find cdrecord executable" along with the suggestion that I install cdrtools. K3b refuses to burn the CD image. There is no package cdrtools but there was libcdr-tools. Unfortunately installing that didn't help. Google was no help and neither was a search of packages.debian.org. I realize optical media is passé these days, but I find it difficult to believe that support for burning CDs has been dropped. What do I have to do to get k3b to burn a CD? OK, got it. I tried to use wodim from the command line and didn't have permission. Changing it to a+x allowed k3b to find it.
k3b can't find cdrecord
I'm running Debian/Stretch AMD64 using plasma desktop and I'm trying to burn a CD image. However when I start k3b, I get an error message "unable to find cdrecord executable" along with the suggestion that I install cdrtools. K3b refuses to burn the CD image. There is no package cdrtools but there was libcdr-tools. Unfortunately installing that didn't help. Google was no help and neither was a search of packages.debian.org. I realize optical media is passé these days, but I find it difficult to believe that support for burning CDs has been dropped. What do I have to do to get k3b to burn a CD?
Re: CDRecord vs WODIM
Houve uma substituição, no Debian e nas distro derivadas. Alguns alegam problemas com a licença do cdrecord e a dificuldade para convencer o seu autor Jörg Shilling a fazer mudanças neste sentido; Por outro lado, o Jörg se diz vítima de um complô e que não há problema algum com o licenciamento do seu software. O fato é que o wodim é um fork de uma versão muito antiga do cdrecord e, portanto, tem uma série de limitações e bugs. O cdrecord, por exemplo, é capaz de gravar blu-ray e o wodim não, por exemplo. Eu estava tentando fazer, sem sucesso, backup de algumas ISO para playstation 2 e achava que o problema pudesse ser algum bug não resolvido no wodim. Antes de fazer a troca, eu queria saber se alguém já passou por isto. Obrigado! On 23-09-2013 17:22, Fábio de Sousa wrote: Cara eu também não saco muito sobre o assunto! Mas tenho notado que 99% dos aplicativos gráficos usam o wodim! Por algum motivo, os desenvolvedores dos mesmos, devem ter escolhido o wodim por algo interessante. Um exemplo é o k3b, ele usa o wodim! Abraço, Fabiocs ~ /| Fábio de Sousa / .ºvº. /| / /(_)\ | /Seja livre, use LINUX/ .^.^. | /Socialmente justo, economicamente viável e tecnologicamente sustentável/ 2013/9/22 Elias Praciano eliaspraci...@gmail.com mailto:eliaspraci...@gmail.com Bom dia! Não me julgo capacitado a opinar na celeuma que envolve os dois pacotes. Apenas desejo saber se alguém fez ou recomenda a substituição do WODIM pelo CDRecord?! Obrigado! -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org mailto:debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org mailto:listmas...@lists.debian.org Archive: http://lists.debian.org/523ed7c1.40...@gmail.com
Re: CDRecord vs WODIM
Cara eu também não saco muito sobre o assunto! Mas tenho notado que 99% dos aplicativos gráficos usam o wodim! Por algum motivo, os desenvolvedores dos mesmos, devem ter escolhido o wodim por algo interessante. Um exemplo é o k3b, ele usa o wodim! Abraço, Fabiocs ~ *| Fábio de Sousa * .ºvº. *| * /(_)\ | *Seja livre, use LINUX* .^.^. | *Socialmente justo, economicamente viável e tecnologicamente sustentável* 2013/9/22 Elias Praciano eliaspraci...@gmail.com Bom dia! Não me julgo capacitado a opinar na celeuma que envolve os dois pacotes. Apenas desejo saber se alguém fez ou recomenda a substituição do WODIM pelo CDRecord?! Obrigado! -- To UNSUBSCRIBE, email to debian-user-portuguese-**requ...@lists.debian.orgdebian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/**523ed7c1.40...@gmail.comhttp://lists.debian.org/523ed7c1.40...@gmail.com
CDRecord vs WODIM
Bom dia! Não me julgo capacitado a opinar na celeuma que envolve os dois pacotes. Apenas desejo saber se alguém fez ou recomenda a substituição do WODIM pelo CDRecord?! Obrigado! -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/523ed7c1.40...@gmail.com
erro no cdrecord
Estou tentando gravar um cd via linha de comando, e estou obtendo o seguinte problema/erro: to...@machine:~$ cdrecord -v -fs=16M speed=48 dev=/dev/hdc -data debian-testing-i386-netinst.iso wodim: No write mode specified. wodim: Asuming -tao mode. wodim: Future versions of wodim may have different drive dependent defaults. TOC Type: 1 = CD-ROM wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/hdc' devname: '/dev/hdc' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.9 SCSI buffer size: 64512 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'PIONEER ' Identification : 'DVD-RW DVR-110D' Revision : '1.17' Device seems to be: Generic mmc2 DVD-R/DVD-RW. wodim: Cannot load media with this drive! wodim: Try to load media by hand. Current: 0x (Reserved/Unknown) Profile: 0x002B (DVD+R/DL) Profile: 0x001B (DVD+R) Profile: 0x001A (DVD+RW) Profile: 0x0016 (DVD-R/DL layer jump recording) Profile: 0x0015 (DVD-R/DL sequential recording) Profile: 0x0014 (DVD-RW sequential recording) Profile: 0x0013 (DVD-RW restricted overwrite) Profile: 0x0011 (DVD-R sequential recording) Profile: 0x0010 (DVD-ROM) Profile: 0x000A (CD-RW) Profile: 0x0009 (CD-R) Profile: 0x0008 (CD-ROM) Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 1267712 = 1238 KB Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. FIFO size : 16777216 = 16384 KB Track 01: data 152 MB Total size: 175 MB (17:23.94) = 78296 sectors Lout start: 175 MB (17:25/71) = 78296 sectors wodim: Cannot load media with this drive! wodim: Try to load media by hand. wodim: Cannot load media. to...@machine:~$ Dei uma olhada no google sobre esse problema de Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/hdc' e me parece que tem algo a ver com suid, e que teria que rodar um dpkg-statoverride, como consta essa thread: http://www.nabble.com/CD-burning-stopped-working-td16749293.html Mas desconfio não estar acertando nas opções. machine:~# dpkg-statoverride --add --admindir /usr/bin/wodim /usr/sbin/dpkg-statoverride: cannot open statoverride: Not a directory Alguem poderia me dar uma ajuda por favor? Thanx
Re: erro no cdrecord
1 - vc ja gravou algum cd ou dvd antes com esse comando?.porque na mensagem tb diz que vc não especificou nenhum modo de escritaTAO, SAO, etc.., acrescenta mais essa informação pra ver se corrigi o erro. 2 - e outra.posta o teu fstab pra ver... falou! :-) 2009/4/8 tombs tombs.li...@gmail.com Estou tentando gravar um cd via linha de comando, e estou obtendo o seguinte problema/erro: to...@machine:~$ cdrecord -v -fs=16M speed=48 dev=/dev/hdc -data debian-testing-i386-netinst.iso wodim: No write mode specified. wodim: Asuming -tao mode. wodim: Future versions of wodim may have different drive dependent defaults. TOC Type: 1 = CD-ROM wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/hdc' devname: '/dev/hdc' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.9 SCSI buffer size: 64512 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'PIONEER ' Identification : 'DVD-RW DVR-110D' Revision : '1.17' Device seems to be: Generic mmc2 DVD-R/DVD-RW. wodim: Cannot load media with this drive! wodim: Try to load media by hand. Current: 0x (Reserved/Unknown) Profile: 0x002B (DVD+R/DL) Profile: 0x001B (DVD+R) Profile: 0x001A (DVD+RW) Profile: 0x0016 (DVD-R/DL layer jump recording) Profile: 0x0015 (DVD-R/DL sequential recording) Profile: 0x0014 (DVD-RW sequential recording) Profile: 0x0013 (DVD-RW restricted overwrite) Profile: 0x0011 (DVD-R sequential recording) Profile: 0x0010 (DVD-ROM) Profile: 0x000A (CD-RW) Profile: 0x0009 (CD-R) Profile: 0x0008 (CD-ROM) Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 1267712 = 1238 KB Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. FIFO size : 16777216 = 16384 KB Track 01: data 152 MB Total size: 175 MB (17:23.94) = 78296 sectors Lout start: 175 MB (17:25/71) = 78296 sectors wodim: Cannot load media with this drive! wodim: Try to load media by hand. wodim: Cannot load media. to...@machine:~$ Dei uma olhada no google sobre esse problema de Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/hdc' e me parece que tem algo a ver com suid, e que teria que rodar um dpkg-statoverride, como consta essa thread: http://www.nabble.com/CD-burning-stopped-working-td16749293.html Mas desconfio não estar acertando nas opções. machine:~# dpkg-statoverride --add --admindir /usr/bin/wodim /usr/sbin/dpkg-statoverride: cannot open statoverride: Not a directory Alguem poderia me dar uma ajuda por favor? Thanx
Re: erro no cdrecord
2009/4/8 Rodolfo rof20...@gmail.com 1 - vc ja gravou algum cd ou dvd antes com esse comando?.porque na mensagem tb diz que vc não especificou nenhum modo de escritaTAO, SAO, etc.., acrescenta mais essa informação pra ver se corrigi o erro. 2 - e outra.posta o teu fstab pra ver... falou! :-) 2009/4/8 tombs tombs.li...@gmail.com Estou tentando gravar um cd via linha de comando, e estou obtendo o seguinte problema/erro: to...@machine:~$ cdrecord -v -fs=16M speed=48 dev=/dev/hdc -data debian-testing-i386-netinst.iso wodim: No write mode specified. wodim: Asuming -tao mode. wodim: Future versions of wodim may have different drive dependent defaults. TOC Type: 1 = CD-ROM wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/hdc' devname: '/dev/hdc' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.9 SCSI buffer size: 64512 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'PIONEER ' Identification : 'DVD-RW DVR-110D' Revision : '1.17' Device seems to be: Generic mmc2 DVD-R/DVD-RW. wodim: Cannot load media with this drive! wodim: Try to load media by hand. Current: 0x (Reserved/Unknown) Profile: 0x002B (DVD+R/DL) Profile: 0x001B (DVD+R) Profile: 0x001A (DVD+RW) Profile: 0x0016 (DVD-R/DL layer jump recording) Profile: 0x0015 (DVD-R/DL sequential recording) Profile: 0x0014 (DVD-RW sequential recording) Profile: 0x0013 (DVD-RW restricted overwrite) Profile: 0x0011 (DVD-R sequential recording) Profile: 0x0010 (DVD-ROM) Profile: 0x000A (CD-RW) Profile: 0x0009 (CD-R) Profile: 0x0008 (CD-ROM) Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 1267712 = 1238 KB Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. FIFO size : 16777216 = 16384 KB Track 01: data 152 MB Total size: 175 MB (17:23.94) = 78296 sectors Lout start: 175 MB (17:25/71) = 78296 sectors wodim: Cannot load media with this drive! wodim: Try to load media by hand. wodim: Cannot load media. to...@machine:~$ Dei uma olhada no google sobre esse problema de Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/hdc' e me parece que tem algo a ver com suid, e que teria que rodar um dpkg-statoverride, como consta essa thread: http://www.nabble.com/CD-burning-stopped-working-td16749293.html Mas desconfio não estar acertando nas opções. machine:~# dpkg-statoverride --add --admindir /usr/bin/wodim /usr/sbin/dpkg-statoverride: cannot open statoverride: Not a directory Alguem poderia me dar uma ajuda por favor? Thanx Rodolfo...valeu a ajuda Eu nao especifiquei nenhum modo de escrita, mas o cdrecord tem essa passagem: wodim: No write mode specified. wodim: Asuming -tao mode. fstab: /dev/hdd/media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/hdc/media/cdrom1 udf,iso9660 user,noauto 0 0
Fwd: erro no cdrecord
-- Forwarded message -- From: Rodolfo rof20...@gmail.com Date: 2009/4/8 Subject: Re: erro no cdrecord To: tombs tombs.li...@gmail.com ok...então segundo seu fstabvc tem 2 drive de CD/DVD certo?vc tem isso mesmo? se sim.poste aqui as especificações de cada por exemplo: SONY DVDR ... e informe qual deles tem capacidade de gravaçãoe tal... VC NAO ME INFORMOU SE JA CONSEGUIU GRAVAR ALGUMA COISA COM ESSE COMANDO aguardando resposta da pergunta acima tb 2009/4/8 tombs tombs.li...@gmail.com 2009/4/8 Rodolfo rof20...@gmail.com 1 - vc ja gravou algum cd ou dvd antes com esse comando?.porque na mensagem tb diz que vc não especificou nenhum modo de escritaTAO, SAO, etc.., acrescenta mais essa informação pra ver se corrigi o erro. 2 - e outra.posta o teu fstab pra ver... falou! :-) 2009/4/8 tombs tombs.li...@gmail.com Estou tentando gravar um cd via linha de comando, e estou obtendo o seguinte problema/erro: to...@machine:~$ cdrecord -v -fs=16M speed=48 dev=/dev/hdc -data debian-testing-i386-netinst.iso wodim: No write mode specified. wodim: Asuming -tao mode. wodim: Future versions of wodim may have different drive dependent defaults. TOC Type: 1 = CD-ROM wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/hdc' devname: '/dev/hdc' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.9 SCSI buffer size: 64512 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'PIONEER ' Identification : 'DVD-RW DVR-110D' Revision : '1.17' Device seems to be: Generic mmc2 DVD-R/DVD-RW. wodim: Cannot load media with this drive! wodim: Try to load media by hand. Current: 0x (Reserved/Unknown) Profile: 0x002B (DVD+R/DL) Profile: 0x001B (DVD+R) Profile: 0x001A (DVD+RW) Profile: 0x0016 (DVD-R/DL layer jump recording) Profile: 0x0015 (DVD-R/DL sequential recording) Profile: 0x0014 (DVD-RW sequential recording) Profile: 0x0013 (DVD-RW restricted overwrite) Profile: 0x0011 (DVD-R sequential recording) Profile: 0x0010 (DVD-ROM) Profile: 0x000A (CD-RW) Profile: 0x0009 (CD-R) Profile: 0x0008 (CD-ROM) Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 1267712 = 1238 KB Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. FIFO size : 16777216 = 16384 KB Track 01: data 152 MB Total size: 175 MB (17:23.94) = 78296 sectors Lout start: 175 MB (17:25/71) = 78296 sectors wodim: Cannot load media with this drive! wodim: Try to load media by hand. wodim: Cannot load media. to...@machine:~$ Dei uma olhada no google sobre esse problema de Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/hdc' e me parece que tem algo a ver com suid, e que teria que rodar um dpkg-statoverride, como consta essa thread: http://www.nabble.com/CD-burning-stopped-working-td16749293.html Mas desconfio não estar acertando nas opções. machine:~# dpkg-statoverride --add --admindir /usr/bin/wodim /usr/sbin/dpkg-statoverride: cannot open statoverride: Not a directory Alguem poderia me dar uma ajuda por favor? Thanx Rodolfo...valeu a ajuda Eu nao especifiquei nenhum modo de escrita, mas o cdrecord tem essa passagem: wodim: No write mode specified. wodim: Asuming -tao mode. fstab: /dev/hdd/media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/hdc/media/cdrom1 udf,iso9660 user,noauto 0 0
Re: erro no cdrecord
2009/4/8 Rodolfo rof20...@gmail.com -- Forwarded message -- From: Rodolfo rof20...@gmail.com Date: 2009/4/8 Subject: Re: erro no cdrecord To: tombs tombs.li...@gmail.com ok...então segundo seu fstabvc tem 2 drive de CD/DVD certo?vc tem isso mesmo? se sim.poste aqui as especificações de cada por exemplo: SONY DVDR ... e informe qual deles tem capacidade de gravaçãoe tal... VC NAO ME INFORMOU SE JA CONSEGUIU GRAVAR ALGUMA COISA COM ESSE COMANDO aguardando resposta da pergunta acima tb 2009/4/8 tombs tombs.li...@gmail.com 2009/4/8 Rodolfo rof20...@gmail.com 1 - vc ja gravou algum cd ou dvd antes com esse comando?.porque na mensagem tb diz que vc não especificou nenhum modo de escritaTAO, SAO, etc.., acrescenta mais essa informação pra ver se corrigi o erro. 2 - e outra.posta o teu fstab pra ver... falou! :-) 2009/4/8 tombs tombs.li...@gmail.com Estou tentando gravar um cd via linha de comando, e estou obtendo o seguinte problema/erro: to...@machine:~$ cdrecord -v -fs=16M speed=48 dev=/dev/hdc -data debian-testing-i386-netinst.iso wodim: No write mode specified. wodim: Asuming -tao mode. wodim: Future versions of wodim may have different drive dependent defaults. TOC Type: 1 = CD-ROM wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/hdc' devname: '/dev/hdc' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.9 SCSI buffer size: 64512 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'PIONEER ' Identification : 'DVD-RW DVR-110D' Revision : '1.17' Device seems to be: Generic mmc2 DVD-R/DVD-RW. wodim: Cannot load media with this drive! wodim: Try to load media by hand. Current: 0x (Reserved/Unknown) Profile: 0x002B (DVD+R/DL) Profile: 0x001B (DVD+R) Profile: 0x001A (DVD+RW) Profile: 0x0016 (DVD-R/DL layer jump recording) Profile: 0x0015 (DVD-R/DL sequential recording) Profile: 0x0014 (DVD-RW sequential recording) Profile: 0x0013 (DVD-RW restricted overwrite) Profile: 0x0011 (DVD-R sequential recording) Profile: 0x0010 (DVD-ROM) Profile: 0x000A (CD-RW) Profile: 0x0009 (CD-R) Profile: 0x0008 (CD-ROM) Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 1267712 = 1238 KB Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. FIFO size : 16777216 = 16384 KB Track 01: data 152 MB Total size: 175 MB (17:23.94) = 78296 sectors Lout start: 175 MB (17:25/71) = 78296 sectors wodim: Cannot load media with this drive! wodim: Try to load media by hand. wodim: Cannot load media. to...@machine:~$ Dei uma olhada no google sobre esse problema de Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/hdc' e me parece que tem algo a ver com suid, e que teria que rodar um dpkg-statoverride, como consta essa thread: http://www.nabble.com/CD-burning-stopped-working-td16749293.html Mas desconfio não estar acertando nas opções. machine:~# dpkg-statoverride --add --admindir /usr/bin/wodim /usr/sbin/dpkg-statoverride: cannot open statoverride: Not a directory Alguem poderia me dar uma ajuda por favor? Thanx Rodolfo...valeu a ajuda Eu nao especifiquei nenhum modo de escrita, mas o cdrecord tem essa passagem: wodim: No write mode specified. wodim: Asuming -tao mode. fstab: /dev/hdd/media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/hdc/media/cdrom1 udf,iso9660 user,noauto 0 0 Rodolfo... Nao, nunca gravei nada nessa maquina. Estou tentando gravar pq na minha maquina principal, ta dando pau. Entao estou tentando numa outra. cdrecord -scanbus scsibus1000: 1000,0,0 10) * 1000,1,0 11) * 1000,2,0 12) 'PIONEER ' 'DVD-RW DVR-110D' '1.17' Removable CD-ROM 1000,3,0 13) 'HL-DT-ST' 'RW/DVD GCC-4480B' '1.00' Removable CD-ROM 1000,4,0 14) * 1000,5,0 15) * 1000,6,0 16) * 1000,7,0 17) * O Pioneer é um gravador, e o HL-DT-ST(Samsung) é um combo. O jumper esta com o Pioneer como master.
Re: erro no cdrecord
Olá, 2009/4/8 tombs tombs.li...@gmail.com: Estou tentando gravar um cd via linha de comando, e estou obtendo o seguinte problema/erro: [...] wodim: Cannot load media with this drive! wodim: Try to load media by hand. wodim: Cannot load media. to...@machine:~$ Estas linhas aí acima não significam que o wodim não conseguiu fechar a bandeja do gravador, certo? Isto terá interferido em alguma coisa? [...] -- Gunther Furtado Curitiba - Paraná - Brasil gunfurt...@gmail.com ...agora, só nos sobrou o futuro..., visto em www.manuchao.net -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: erro no cdrecord
2009/4/8 Gunther Furtado gunfurt...@gmail.com Olá, 2009/4/8 tombs tombs.li...@gmail.com: Estou tentando gravar um cd via linha de comando, e estou obtendo o seguinte problema/erro: [...] wodim: Cannot load media with this drive! wodim: Try to load media by hand. wodim: Cannot load media. to...@machine:~$ Estas linhas aí acima não significam que o wodim não conseguiu fechar a bandeja do gravador, certo? Isto terá interferido em alguma coisa? [...] -- Gunther Furtado Curitiba - Paraná - Brasil gunfurt...@gmail.com ...agora, só nos sobrou o futuro..., visto em www.manuchao.net Só para constar na threadEu ja consegui gravar, usando o outro drive, o Samsung. Penso que deva ter sido problemas com os jumpers. Não tive a oportunidade de verifica-los. Mas deu certo. Valeu a ajuda Rodolfo e Gunther. [ ]
K3B / cdrecord : mode mixte et DAO
Salut, Je cherche à graver un CD qui comporte - 54 pistes audio générées à partir d'un seul fichier wav (issu de Ardour puis Jamin) et d'un fichier cue (créé par Ardour aussi), - 1 piste multimedia comprenant une vidéo, des exemplaires de la licence Art Libre, un VLC, un README Le tout doit être gravé en Disk-at-once (DAO ou SAO), car les 48 premières pistes audio sont enchaînées. Je n'arrive absolument pas à graver en combinant tout ça, quel que soit le mode mixte retenu (CD-Extra, avant la première piste, après la dernière piste), dans tous les cas la fichier cue l'emmerde à un moment donné. En pratique, j'ai ressayé de découper toutes les pistes wav à la main (très ardu, et peu convaincant, car risque de saut du signal audio entre deux morceaux), et, bien qu'il n'y ait plus de fichier .cue, il doit probablement en générer un quand même, car il n'en veut pas non plus. J'ai viré le mode CD-text, etc., mais ça n'a pas fonctionné mieux. Bref, impossible de m'en sortir, et pourtant, je suis presque persuadé de l'avoir fait pour un précédent pressage en 2008. A noter que l'option track-at-once est totalement à proscrire car dans ce cas, l'écriture des lead out sur chaque piste entraîne 2 secondes de trous entre chacune d'entre elles, ce qui n'est pas tenable. Evidemment, j'ai bien vérifié qu'il n'y avait aucune pause de demandée entre les pistes, et enlever le préemphasis et posé un prégap nul. Est-ce que ce que je veux faire est techniquement impossible, est-ce que je ne cherceh pas dans la bonne direction, ou autre chose ? Le man de cdrecord ne fait pas mention de problèmes particuliers, et cdrecord est mot-clef très peu pertinent sur google (k3b aussi, du reste). Merci. Aurélien PS : Je dois être très prudent sur cette gravure, avec une vitesse lente, etc. car l'objectif est de graver ce qu'on appelle un CD-master qui sert par la suite de moule pour la duplication dudit CD en usine. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
[Resolved] Re: Cdrecord loses permission to write CD's...
On Mon, 2008-10-27 at 18:31 +0100, Emanoil Kotsev wrote: Kenward Vaughan wrote: On Sun, 2008-10-26 at 23:58 +0100, Jochen Schulz wrote: Kenward Vaughan: On Sun, 2008-10-26 at 23:29 +0100, Jochen Schulz wrote: ... Do you have DMA enabled at all? Check with 'hdparm -d /dev/$foo', replacing $foo with your cd/dvd device and your hard disk(s). J. I've tried that at times with no luck on the CDs: hpotter:/home/daddy# hdparm -d on /dev/hda on: No such file or directory hpotter:/home/daddy# hdparm -d 1 /dev/hda /dev/hda: setting using_dma to 1 (on) HDIO_SET_DMA failed: Operation not permitted using_dma = 0 (off) My HDs are SATAs, so hdparm doesn't work, written as above, at least. Do you know whether there is a setting or series of settings in my kernel that I don't realize need to be changed?? (I roll my own.) Thanks, Kenward Hi, I had the same issue with activeting the GENERIC_IDE option in the kernel. Look at ATA/ATAPI/MFM/RLL under Device Drivers generic/default IDE chipset support - CONFIG_IDE_GENERIC Generic PCI IDE Chipset Support - CONFIG_BLK_DEV_GENERIC Disable them or set them to M this way no generic ide is setup and the ata_* code takes effect which leads to u/DMA getting enabled After this your drive (and/or cd/dvd) will be found as /dev/sdX respectively /dev/srX hope this helps for me it worked regards Emanoil, Wonderful! I finally got time to try this, and it worked great. The CDs are flying out of the tray now. Thanks to Jochen too, for your help as well with this! Kenward -- In a completely rational society, the best of us would aspire to be _teachers_ and the rest of us would have to settle for something less, because passing civilization along from one generation to the next ought to be the highest honor and the highest responsibility anyone could have. - Lee Iacocca -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Resolved] Re: Cdrecord loses permission to write CD's...
Kenward Vaughan wrote: On Mon, 2008-10-27 at 18:31 +0100, Emanoil Kotsev wrote: Kenward Vaughan wrote: On Sun, 2008-10-26 at 23:58 +0100, Jochen Schulz wrote: Kenward Vaughan: On Sun, 2008-10-26 at 23:29 +0100, Jochen Schulz wrote: ... Do you have DMA enabled at all? Check with 'hdparm -d /dev/$foo', replacing $foo with your cd/dvd device and your hard disk(s). J. I've tried that at times with no luck on the CDs: hpotter:/home/daddy# hdparm -d on /dev/hda on: No such file or directory hpotter:/home/daddy# hdparm -d 1 /dev/hda /dev/hda: setting using_dma to 1 (on) HDIO_SET_DMA failed: Operation not permitted using_dma = 0 (off) My HDs are SATAs, so hdparm doesn't work, written as above, at least. Do you know whether there is a setting or series of settings in my kernel that I don't realize need to be changed?? (I roll my own.) Thanks, Kenward Hi, I had the same issue with activeting the GENERIC_IDE option in the kernel. Look at ATA/ATAPI/MFM/RLL under Device Drivers generic/default IDE chipset support - CONFIG_IDE_GENERIC Generic PCI IDE Chipset Support - CONFIG_BLK_DEV_GENERIC Disable them or set them to M this way no generic ide is setup and the ata_* code takes effect which leads to u/DMA getting enabled After this your drive (and/or cd/dvd) will be found as /dev/sdX respectively /dev/srX hope this helps for me it worked regards Emanoil, Wonderful! I finally got time to try this, and it worked great. The CDs are flying out of the tray now. Thanks to Jochen too, for your help as well with this! Kenward welcome, Glad to hear that. It took me about half an year among all my other duties to get used to the new kernel (2.6.2X) and read most of the documentation and finally find out what is going on with my dvd recorder. regards -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cdrecord loses permission to write CD's...
Kenward Vaughan wrote: On Sun, 2008-10-26 at 23:58 +0100, Jochen Schulz wrote: Kenward Vaughan: On Sun, 2008-10-26 at 23:29 +0100, Jochen Schulz wrote: Kenward Vaughan: Speed set to 7056 KB/s /usr/bin/wodim: DMA speed too slow (OK for 6x). Cannot write at speed 40x. This might be your problem. Did you already try burning in a slower mode? I don't get the DMA issue, to be honest. I wonder if that was lost when I got this box a while back (I don't burn discs too often). It wasn't a question with my older machine. I did successfully burn a disc at 4x. Do you have DMA enabled at all? Check with 'hdparm -d /dev/$foo', replacing $foo with your cd/dvd device and your hard disk(s). J. I've tried that at times with no luck on the CDs: hpotter:/home/daddy# hdparm -d on /dev/hda on: No such file or directory hpotter:/home/daddy# hdparm -d 1 /dev/hda /dev/hda: setting using_dma to 1 (on) HDIO_SET_DMA failed: Operation not permitted using_dma = 0 (off) My HDs are SATAs, so hdparm doesn't work, written as above, at least. Do you know whether there is a setting or series of settings in my kernel that I don't realize need to be changed?? (I roll my own.) Thanks, Kenward Hi, I had the same issue with activeting the GENERIC_IDE option in the kernel. Look at ATA/ATAPI/MFM/RLL under Device Drivers generic/default IDE chipset support - CONFIG_IDE_GENERIC Generic PCI IDE Chipset Support - CONFIG_BLK_DEV_GENERIC Disable them or set them to M this way no generic ide is setup and the ata_* code takes effect which leads to u/DMA getting enabled After this your drive (and/or cd/dvd) will be found as /dev/sdX respectively /dev/srX hope this helps for me it worked regards -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Cdrecord loses permission to write CD's...
After copying one CD, I find cdrecord losing it's permission to write to the blank for a second, new CD. Any thoughts why this is happening? Info is in the debugging output below. I was running Fluxbox after a reboot. FWIW I have difficulties as well getting the Plextor drive to be recognized under Gnome, with it winding up spitting out not ready messages on every terminal screen following attempts to use K3B or any other CD software. I've had to reboot to reset things. Is this a hald issue perhaps? TIA for any help! Kenward --- Below is the debugging output from K3B: System --- K3b Version: 1.0.5 KDE Version: 3.5.9 QT Version: 3.3.8b Kernel: 2.6.26 Devices --- LITE-ON DVD D LH-16D1P TL13 (/dev/hdb, ) [CD-ROM, DVD-ROM] [DVD-ROM, CD-ROM] [None] PLEXTOR DVDR PX-708A 1.03 (/dev/hda, ) [CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD+R, DVD+RW] [DVD-ROM, DVD-R Sequential, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite] Used versions --- cdrecord: 1.1.8 cdrecord --- /usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/hda' devname: '/dev/hda' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.8 SCSI buffer size: 64512 Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. TOC Type: 0 = CD-DA Driveropts: 'burnfree' Device type: Removable CD-ROM Version: 0 Response Format: 1 Vendor_info: 'PLEXTOR ' Identification : 'DVDR PX-708A ' Revision : '1.03' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x0009 (CD-R) Profile: 0x001B (DVD+R) Profile: 0x001A (DVD+RW) Profile: 0x0014 (DVD-RW sequential recording) Profile: 0x0013 (DVD-RW restricted overwrite) Profile: 0x0011 (DVD-R sequential recording) Profile: 0x0010 (DVD-ROM) Profile: 0x000A (CD-RW) Profile: 0x0009 (CD-R) (current) Profile: 0x0008 (CD-ROM) Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 1190112 = 1162 KB Drive DMA Speed: 1341 kB/s 7x CD 0x DVD FIFO size : 12582912 = 12288 KB Encoding speed : 909x (68123 sectors/s) for libedc from Heiko Eißfeldt Track1 Start: '32' (32) pregap1: 182 Track 01: audio 38 MB (03:49.70) no preemp pregapsize: 182 Track 02: audio 10 MB (01:02.86) no preemp pregapsize: 0 ... Track 25: audio 18 MB (01:52.77) no preemp pregapsize: 0 Total size: 548 MB (54:17.80) = 244335 sectors Lout start: 548 MB (54:19/60) = 244335 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 5 Is not unrestricted Is not erasable Disk sub type: Medium Type A, high Beta category (A+) (3) ATIP start of lead in: -11634 (97:26/66) Speed set to 7056 KB/s /usr/bin/wodim: DMA speed too slow (OK for 6x). Cannot write at speed 40x. ATIP start of lead out: 359846 (79:59/71) Disk type:Short strategy type (Phthalocyanine or similar) Manuf. index: 3 Manufacturer: CMC Magnetics Corporation Blocks total: 359846 Blocks current: 359846 Blocks remaining: 115511 Starting to write CD/DVD at speed 40.0 in real RAW/RAW96R mode for single session. Last chance to quit, starting real write in2 seconds. 1 seconds. 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Performing OPC... Errno: 0 (Success), write_g1 scsi sendcmd: no error CDB: 2A 00 FF FF D4 7C 00 00 1A 00 status: 0x2 (CHECK CONDITION) Sense Bytes: F0 00 03 FF FF D5 12 0A 00 00 00 00 0C 07 00 00 Sense Key: 0x3 Medium Error, Segment 0 Sense Code: 0x0C Qual 0x07 (write error - recovery needed) Fru 0x0 Sense flags: Blk -10990 (valid) resid: 63648 cmd finished after 1.861s timeout 40s /usr/bin/wodim: Could not write Lead-in. Writing lead-in at sector -11634 write leadin data: error after 1209312 bytes Writing time: 30.620s /usr/bin/wodim: fifo had 191 puts and 0 gets. /usr/bin/wodim: fifo was 0 times empty and 0 times full, min fill was 100%. cdrecord command: --- /usr/bin/wodim -v gracetime=2 dev=/dev/hda speed=40 -raw96r driveropts=burnfree -eject -text -useinfo -audio -shorttrack /opt/film/k3bCdCopy0/Track01.wav /opt/film/k3bCdCopy0/Track02.wav /opt/film/k3bCdCopy0/Track03.wav /opt/film/k3bCdCopy0/Track04.wav /opt/film/k3bCdCopy0/Track05.wav /opt/film/k3bCdCopy0/Track06.wav /opt/film/k3bCdCopy0/Track07.wav /opt/film/k3bCdCopy0/Track08.wav /opt/film/k3bCdCopy0/Track09.wav /opt/film/k3bCdCopy0/Track10.wav /opt/film/k3bCdCopy0/Track11.wav /opt/film/k3bCdCopy0/Track12.wav /opt/film/k3bCdCopy0/Track13.wav /opt/film/k3bCdCopy0/Track14.wav /opt/film/k3bCdCopy0/Track15.wav /opt/film
Re: Cdrecord loses permission to write CD's...
On Sun, 2008-10-26 at 12:09 -0700, Kenward Vaughan wrote: After copying one CD, I find cdrecord losing it's permission to write to the blank for a second, new CD. Any thoughts why this is happening? Info is in the debugging output below. I was running Fluxbox after a ... Restarting K3B and trying to burn an iso image started off well, then died 80% of the way through with a similar error message... Kenward -- If you can't explain it simply, you don't understand it well enough. -- Albert Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cdrecord loses permission to write CD's...
Kenward Vaughan: Speed set to 7056 KB/s /usr/bin/wodim: DMA speed too slow (OK for 6x). Cannot write at speed 40x. This might be your problem. Did you already try burning in a slower mode? J. -- If nightclub doormen recognised me I would be more fulfilled. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
Re: Cdrecord loses permission to write CD's...
On Sun, 2008-10-26 at 23:29 +0100, Jochen Schulz wrote: Kenward Vaughan: Speed set to 7056 KB/s /usr/bin/wodim: DMA speed too slow (OK for 6x). Cannot write at speed 40x. This might be your problem. Did you already try burning in a slower mode? J. It's on auto, so I hadn't tried to change that. I'll look at it. I don't get the DMA issue, to be honest. I wonder if that was lost when I got this box a while back (I don't burn discs too often). It wasn't a question with my older machine. Thanks, Kenward -- The church says the earth is flat, but I know that it is round, for I have seen the shadow on the moon, and I have more faith in a shadow than in the church.--Ferdinand Magellan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cdrecord loses permission to write CD's...
Kenward Vaughan: On Sun, 2008-10-26 at 23:29 +0100, Jochen Schulz wrote: Kenward Vaughan: Speed set to 7056 KB/s /usr/bin/wodim: DMA speed too slow (OK for 6x). Cannot write at speed 40x. This might be your problem. Did you already try burning in a slower mode? I don't get the DMA issue, to be honest. I wonder if that was lost when I got this box a while back (I don't burn discs too often). It wasn't a question with my older machine. Do you have DMA enabled at all? Check with 'hdparm -d /dev/$foo', replacing $foo with your cd/dvd device and your hard disk(s). J. -- If I could travel through time I would go back to yesterday and apologise. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
Re: Cdrecord loses permission to write CD's...
On Sun, 2008-10-26 at 23:58 +0100, Jochen Schulz wrote: Kenward Vaughan: On Sun, 2008-10-26 at 23:29 +0100, Jochen Schulz wrote: Kenward Vaughan: Speed set to 7056 KB/s /usr/bin/wodim: DMA speed too slow (OK for 6x). Cannot write at speed 40x. This might be your problem. Did you already try burning in a slower mode? I don't get the DMA issue, to be honest. I wonder if that was lost when I got this box a while back (I don't burn discs too often). It wasn't a question with my older machine. I did successfully burn a disc at 4x. Do you have DMA enabled at all? Check with 'hdparm -d /dev/$foo', replacing $foo with your cd/dvd device and your hard disk(s). J. I've tried that at times with no luck on the CDs: hpotter:/home/daddy# hdparm -d on /dev/hda on: No such file or directory hpotter:/home/daddy# hdparm -d 1 /dev/hda /dev/hda: setting using_dma to 1 (on) HDIO_SET_DMA failed: Operation not permitted using_dma = 0 (off) My HDs are SATAs, so hdparm doesn't work, written as above, at least. Do you know whether there is a setting or series of settings in my kernel that I don't realize need to be changed?? (I roll my own.) Thanks, Kenward -- In a completely rational society, the best of us would aspire to be _teachers_ and the rest of us would have to settle for something less, because passing civilization along from one generation to the next ought to be the highest honor and the highest responsibility anyone could have. - Lee Iacocca -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord - need for troubleshoot help
* linuksos [EMAIL PROTECTED] 09.10.2008 No difference. I can see enormous hard disk activity but no positive result... On Tue, Oct 7, 2008 at 1:33 AM, Hugo Vanwoerkom [EMAIL PROTECTED] wrote: snip On the cmdline: cdrecord -v dev=/dev/device blank=fast xxx.iso Hello linuksos, do you have the original cdrecord from Jörg Schilling or do you work with the debian package? If you do not have the original, give it a try. The homepage is ftp://ftp.berlios.de/pub/cdrecord/alpha/;. There you find the actual version, which is *cdrtools-2.01.01a51.tar.bz2*. I don't know why the package is in the alpha folder, because I don't think it's alpha. You must compile it by yourself, but that's no problem. The only problem in my opinion is that you install it and apt and dpkg knows nothing. You can use equivs for making a pseudo package because of the packages which depends on wodim. Hth Michael PS: This is no flame against wodim and pro cdrecord, but I think the OP shall test it, because sometimes I read from problems with wodim. -- Everybody should believe in something... I believe I'll have another drink. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord - need for troubleshoot help
I have tried couple of them but the same result. Which driver exactly do you have in mind? thank you On Mon, Oct 6, 2008 at 8:16 PM, Lalit Dhiri [EMAIL PROTECTED] wrote: Try changing the driver selection in K3B. I think you'll find this at K3b configure Devices Cdrdao driver. Linux the Root to no GPFs Date: Mon, 6 Oct 2008 16:50:48 +1100 From: [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: cdrecord - need for troubleshoot help Hello Guys, I'm trying to erase and burn my cd-rw. I'm sure that there is no problem with my cd-rw media as it works on my other system. After unsuccessful attempt to burn it with k3b I have gone to command line to see what is going on. For command line I have followed steps described here: http://www.linuxconfig.org/Create_and_burn_ISO_images_with_mkisofs_%26_cdrecord Here is a output, everything looks fine but last 6 lines. Help is much appreciated. Thank you OUTPUT: wodim: No write mode specified. wodim: Asuming -tao mode. wodim: Future versions of wodim may have different drive dependent defaults. TOC Type: 1 = CD-ROM scsidev: '/dev/hdc' devname: '/dev/hdc' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.2 SCSI buffer size: 64512 atapi: 1 Device type : Removable CD-ROM Version : 0 Response Format: 2 Capabilities : Vendor_info : 'COMPAL ' Identification : 'TSD80Y1 DVD RW ' Revision : 'D010' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x000A (CD-RW) Profile: 0x001B (DVD+R) Profile: 0x001A (DVD+RW) Profile: 0x0014 (DVD-RW sequential recording) Profile: 0x0013 (DVD-RW restricted overwrite) Profile: 0x0011 (DVD-R sequential recording) Profile: 0x0010 (DVD-ROM) Profile: 0x000A (CD-RW) (current) Profile: 0x0009 (CD-R) Profile: 0x0008 (CD-ROM) Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 1638400 = 1600 KB Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. Drive DMA Speed: 4449 kB/s 25x CD 3x DVD FIFO size : 12582912 = 12288 KB Track 01: data 556 MB Total size: 639 MB (63:21.21) = 285091 sectors Lout start: 639 MB (63:23/16) = 285091 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 2 Reference speed: 6 Is not unrestricted Is erasable Disk sub type: High speed Rewritable (CAV) media (1) ATIP start of lead in: -11077 (97:34/23) ATIP start of lead out: 359849 (79:59/74) 1T speed low: 4 1T speed high: 10 2T speed low: 2 2T speed high: 10 power mult factor: 2 6 recommended erase/write power: 5 A1 values: 24 2C DC A2 values: 14 A4 4A A3 values: 04 C4 80 Disk type: Phase change Manuf. index: 11 Manufacturer: Mitsubishi Chemical Corporation Blocks total: 359849 Blocks current: 359849 Blocks remaining: 74758 Speed set to 2116 KB/s Starting to write CD/DVD at speed 12.0 in real TAO mode for single session. Last chance to quit, starting real write 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Performing OPC... Errno: 0 (Success), send opc scsi sendcmd: no error CDB: 54 01 00 00 00 00 00 00 00 00 status: 0x4 (CONDITION MET/GOOD) cmd finished after 60.053s timeout 60s wodim: OPC failed. Writing time: 174.939s -- lubo http://www.linuxconfig.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] _ Win New York holidays with Kellogg's Live Search http://clk.atdmt.com/UKM/go/111354033/direct/01/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- lubo http://www.linuxconfig.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord - need for troubleshoot help
No difference. I can see enormous hard disk activity but no positive result... On Tue, Oct 7, 2008 at 1:33 AM, Hugo Vanwoerkom [EMAIL PROTECTED] wrote: linuksos wrote: Hello Guys, I'm trying to erase and burn my cd-rw. I'm sure that there is no problem with my cd-rw media as it works on my other system. After unsuccessful attempt to burn it with k3b I have gone to command line to see what is going on. For command line I have followed steps described here: http://www.linuxconfig.org/Create_and_burn_ISO_images_with_mkisofs_%26_cdrecord snip On the cmdline: cdrecord -v dev=/dev/device blank=fast xxx.iso Hugo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- lubo http://www.linuxconfig.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: cdrecord - need for troubleshoot help
Try changing the driver selection in K3B. I think you'll find this at K3b configure Devices Cdrdao driver. Linux the Root to no GPFs Date: Mon, 6 Oct 2008 16:50:48 +1100 From: [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: cdrecord - need for troubleshoot help Hello Guys, I'm trying to erase and burn my cd-rw. I'm sure that there is no problem with my cd-rw media as it works on my other system. After unsuccessful attempt to burn it with k3b I have gone to command line to see what is going on. For command line I have followed steps described here: http://www.linuxconfig.org/Create_and_burn_ISO_images_with_mkisofs_%26_cdrecord Here is a output, everything looks fine but last 6 lines. Help is much appreciated. Thank you OUTPUT: wodim: No write mode specified. wodim: Asuming -tao mode. wodim: Future versions of wodim may have different drive dependent defaults. TOC Type: 1 = CD-ROM scsidev: '/dev/hdc' devname: '/dev/hdc' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.2 SCSI buffer size: 64512 atapi: 1 Device type : Removable CD-ROM Version : 0 Response Format: 2 Capabilities : Vendor_info : 'COMPAL ' Identification : 'TSD80Y1 DVD RW ' Revision : 'D010' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x000A (CD-RW) Profile: 0x001B (DVD+R) Profile: 0x001A (DVD+RW) Profile: 0x0014 (DVD-RW sequential recording) Profile: 0x0013 (DVD-RW restricted overwrite) Profile: 0x0011 (DVD-R sequential recording) Profile: 0x0010 (DVD-ROM) Profile: 0x000A (CD-RW) (current) Profile: 0x0009 (CD-R) Profile: 0x0008 (CD-ROM) Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 1638400 = 1600 KB Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. Drive DMA Speed: 4449 kB/s 25x CD 3x DVD FIFO size : 12582912 = 12288 KB Track 01: data 556 MB Total size: 639 MB (63:21.21) = 285091 sectors Lout start: 639 MB (63:23/16) = 285091 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 2 Reference speed: 6 Is not unrestricted Is erasable Disk sub type: High speed Rewritable (CAV) media (1) ATIP start of lead in: -11077 (97:34/23) ATIP start of lead out: 359849 (79:59/74) 1T speed low: 4 1T speed high: 10 2T speed low: 2 2T speed high: 10 power mult factor: 2 6 recommended erase/write power: 5 A1 values: 24 2C DC A2 values: 14 A4 4A A3 values: 04 C4 80 Disk type: Phase change Manuf. index: 11 Manufacturer: Mitsubishi Chemical Corporation Blocks total: 359849 Blocks current: 359849 Blocks remaining: 74758 Speed set to 2116 KB/s Starting to write CD/DVD at speed 12.0 in real TAO mode for single session. Last chance to quit, starting real write 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Performing OPC... Errno: 0 (Success), send opc scsi sendcmd: no error CDB: 54 01 00 00 00 00 00 00 00 00 status: 0x4 (CONDITION MET/GOOD) cmd finished after 60.053s timeout 60s wodim: OPC failed. Writing time: 174.939s -- lubo http://www.linuxconfig.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] _ Win New York holidays with Kellogg’s Live Search http://clk.atdmt.com/UKM/go/111354033/direct/01/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord - need for troubleshoot help
linuksos wrote: Hello Guys, I'm trying to erase and burn my cd-rw. I'm sure that there is no problem with my cd-rw media as it works on my other system. After unsuccessful attempt to burn it with k3b I have gone to command line to see what is going on. For command line I have followed steps described here: http://www.linuxconfig.org/Create_and_burn_ISO_images_with_mkisofs_%26_cdrecord snip On the cmdline: cdrecord -v dev=/dev/device blank=fast xxx.iso Hugo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cdrecord - need for troubleshoot help
Hello Guys, I'm trying to erase and burn my cd-rw. I'm sure that there is no problem with my cd-rw media as it works on my other system. After unsuccessful attempt to burn it with k3b I have gone to command line to see what is going on. For command line I have followed steps described here: http://www.linuxconfig.org/Create_and_burn_ISO_images_with_mkisofs_%26_cdrecord Here is a output, everything looks fine but last 6 lines. Help is much appreciated. Thank you OUTPUT: wodim: No write mode specified. wodim: Asuming -tao mode. wodim: Future versions of wodim may have different drive dependent defaults. TOC Type: 1 = CD-ROM scsidev: '/dev/hdc' devname: '/dev/hdc' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.2 SCSI buffer size: 64512 atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'COMPAL ' Identification : 'TSD80Y1 DVD RW ' Revision : 'D010' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x000A (CD-RW) Profile: 0x001B (DVD+R) Profile: 0x001A (DVD+RW) Profile: 0x0014 (DVD-RW sequential recording) Profile: 0x0013 (DVD-RW restricted overwrite) Profile: 0x0011 (DVD-R sequential recording) Profile: 0x0010 (DVD-ROM) Profile: 0x000A (CD-RW) (current) Profile: 0x0009 (CD-R) Profile: 0x0008 (CD-ROM) Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 1638400 = 1600 KB Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. Drive DMA Speed: 4449 kB/s 25x CD 3x DVD FIFO size : 12582912 = 12288 KB Track 01: data 556 MB Total size: 639 MB (63:21.21) = 285091 sectors Lout start: 639 MB (63:23/16) = 285091 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 2 Reference speed: 6 Is not unrestricted Is erasable Disk sub type: High speed Rewritable (CAV) media (1) ATIP start of lead in: -11077 (97:34/23) ATIP start of lead out: 359849 (79:59/74) 1T speed low: 4 1T speed high: 10 2T speed low: 2 2T speed high: 10 power mult factor: 2 6 recommended erase/write power: 5 A1 values: 24 2C DC A2 values: 14 A4 4A A3 values: 04 C4 80 Disk type:Phase change Manuf. index: 11 Manufacturer: Mitsubishi Chemical Corporation Blocks total: 359849 Blocks current: 359849 Blocks remaining: 74758 Speed set to 2116 KB/s Starting to write CD/DVD at speed 12.0 in real TAO mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Performing OPC... Errno: 0 (Success), send opc scsi sendcmd: no error CDB: 54 01 00 00 00 00 00 00 00 00 status: 0x4 (CONDITION MET/GOOD) cmd finished after 60.053s timeout 60s wodim: OPC failed. Writing time: 174.939s -- lubo http://www.linuxconfig.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: CD gravés avec cdrecord illisibles ss Win
Jean-Yves F. Barbier a écrit : vi, avec des DVD-RW 8x, alors que mon graveur ne peut monter qu'à 4x: claquage impec, pas de récrimination de k3b; mais rin de rin sur le DVD-RW (question de puissance de la diode LASER) Mon problème est un peu différent (ou alors je n'ai pas bien compris ce que tu voulais dire) : mon CD est bien gravé son contenu est accessible sans problème sous Linux. Mais apparaît vide sous l'OS du mal... P. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
CD gravés avec cdrecord illisibles ss Win
Bonjour la liste Le titre est explicite : depuis deux lenny à jour (donc deux graveurs différents) je viens de graver deux CD-RW de données et j'ai tenté sans succès de les lire sur deux postes Windows XP différents avec le même résultat : le label est reconnu mais le contenu est à 0 octets alors que tout est accessible sans pb depuis Nunux. Quelqu'un a rencontré le même problème ? P. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: CD gravés avec cdrecord illisibles ss Win
Bonjour, As-tu coché l'extension joliet ? Le 04/10/07, pascal [EMAIL PROTECTED] a écrit : Bonjour la liste Le titre est explicite : depuis deux lenny à jour (donc deux graveurs différents) je viens de graver deux CD-RW de données et j'ai tenté sans succès de les lire sur deux postes Windows XP différents avec le même résultat : le label est reconnu mais le contenu est à 0 octets alors que tout est accessible sans pb depuis Nunux. Quelqu'un a rencontré le même problème ? P. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: CD gravés avec cdrecord illisibles ss Win
christophe jenaux a écrit : Bonjour, As-tu coché l'extension joliet ? Oui...je me suis fendu d'un joli mkisofs -J (entre autres) pour l'image... J'ai utlisé Xcdroast *et* un script maison qui ts deux marchaient impecc auparavant... P. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: CD gravés avec cdrecord illisibles ss Win
vi, avec des DVD-RW 8x, alors que mon graveur ne peut monter qu'à 4x: claquage impec, pas de récrimination de k3b; mais rin de rin sur le DVD-RW (question de puissance de la diode LASER) pascal a écrit : Bonjour la liste Le titre est explicite : depuis deux lenny à jour (donc deux graveurs différents) je viens de graver deux CD-RW de données et j'ai tenté sans succès de les lire sur deux postes Windows XP différents avec le même résultat : le label est reconnu mais le contenu est à 0 octets alors que tout est accessible sans pb depuis Nunux. Quelqu'un a rencontré le même problème ? P. -- Well, it don't make the sun shine, but at least it don't deepen the shit. -- Straiter Empy, in _Riddley_Walker_ by Russell Hoban
Re: cdrecord vs. wodim again
Wayne Topa wrote: steef([EMAIL PROTECTED]) is reported to have said: hi all and *especially jörg s., long-term initiator of cdrecord and cdrtools*. two weeks ago i asked on this list 'what is better': cdrecord or wodim. on one of the responses i answered that the most recent version of cdrecord/cdr-tools completely damaged two brandnew cdrom's. jörg asked me for more info: and here comes some. 1. only one cd/dvd-burner om my machine produced this undesirable effect. a couple of other burners worked flawlessly with the most recent bêta of jörg sch. so it could be that jörg did not make this beta recognize this burner: see /dev/hdb (from dmesg |less): hda: MAXTOR STM3250820A, ATA DISK drive hdb: Optiarc DVD RW AD-7173A, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: ST3120026A, ATA DISK drive Right! Neither cdrecord or wodim can burn to a _Hard Disk_. a good day to you all, And to you. WT hey man, you did not read the first message well. /dev/hdb = a burner. s. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord vs. wodim again
Mumia W.. wrote: On 10/02/2007 05:11 AM, steef wrote: hi all and *especially jörg s., long-term initiator of cdrecord and cdrtools*. two weeks ago i asked on this list 'what is better': cdrecord or wodim. on one of the responses i answered that the most recent version of cdrecord/cdr-tools completely damaged two brandnew cdrom's. jörg asked me for more info: and here comes some. [...] Debian-user is the wrong place for this question. You should address your question to Jörg Shilling at [EMAIL PROTECTED] or [EMAIL PROTECTED] Visit his web site http://cdrecord.berlios.de/ and see what your support options are. yes you are right. but : in the first thread schiiling answered my complaint on the debian list. that's the reason i acted the way i did, reg., steef -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[Fwd: Re: cdrecord vs. wodim again]
Andrew Sackville-West wrote: On Tue, Oct 02, 2007 at 03:46:51PM -0400, Wayne Topa wrote: steef([EMAIL PROTECTED]) is reported to have said: hi all and *especially jörg s., long-term initiator of cdrecord and cdrtools*. two weeks ago i asked on this list 'what is better': cdrecord or wodim. on one of the responses i answered that the most recent version of cdrecord/cdr-tools completely damaged two brandnew cdrom's. jörg asked me for more info: and here comes some. 1. only one cd/dvd-burner om my machine produced this undesirable effect. a couple of other burners worked flawlessly with the most recent bêta of jörg sch. so it could be that jörg did not make this beta recognize this burner: see /dev/hdb (from dmesg |less): hda: MAXTOR STM3250820A, ATA DISK drive hdb: Optiarc DVD RW AD-7173A, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: ST3120026A, ATA DISK drive Right! Neither cdrecord or wodim can burn to a _Hard Disk_. where do you get this? He provided no info on what command he used and if you look, hdb is clearly an optical drive... are you drinking too much coffee? ;) A hi andrew, i used the normal command(s): something like: @ sudo cdrecord speed=8 dev=/dev/hdb (and later what -scanbus told me to use, the 'old way') -tao -v -data -eject /home/steef/.iso reg., steef -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord vs. wodim again
Andrew Sackville-West wrote: hdc: ST3120026A, ATA DISK drive Right! Neither cdrecord or wodim can burn to a _Hard Disk_. where do you get this? He provided no info on what command he used and if you look, hdb is clearly an optical drive... are you drinking too much coffee? ;) A hi andrew, hi. so sorry, I don't know a thing about your problem other than what I think you posited -- that its a player that is incorrectly handled by cdrecord. that is right. I was merely speaking up in your defence since he was getting all sarcastic because he couldn't read... thanks. yes: that stupid sarcasm sometimes is really is a problem. i used the normal command(s): something like: @ sudo cdrecord speed=8 dev=/dev/hdb (and later what -scanbus told me to use, the 'old way') -tao -v -data -eject /home/steef/.iso I don't see why it won't work. neither do i. that's the problem. BTW, why do you need sudo for this? put yourself in the cdrom group (I think). long time ago i did that. i learned my (then young) twins the commands to burn cdroms under potato and woody. got myself after some time out of the usergroup without teling them to come home after work and have some cdroms left. so: an old habit kind regards, steef f A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord vs. wodim again
On Wed, Oct 03, 2007 at 04:05:38PM +, steef wrote: Andrew Sackville-West wrote: I was merely speaking up in your defence since he was getting all sarcastic because he couldn't read... thanks. yes: that stupid sarcasm sometimes is really is a problem. Wayne already apologised for this, BTW, and I was not flaming with the above comment. A signature.asc Description: Digital signature
Re: cdrecord vs. wodim again
Andrew Sackville-West wrote: On Wed, Oct 03, 2007 at 04:05:38PM +, steef wrote: Wayne already apologised for this, BTW, and I was not flaming with the above comment. you are right. i did not see that message up till now. i withdraw my remark. regards, steef A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord vs. wodim again
On Tue, Oct 02, 2007 at 03:46:51PM -0400, Wayne Topa wrote: steef([EMAIL PROTECTED]) is reported to have said: hi all and *especially j?rg s., long-term initiator of cdrecord and cdrtools*. two weeks ago i asked on this list 'what is better': cdrecord or wodim. on one of the responses i answered that the most recent version of cdrecord/cdr-tools completely damaged two brandnew cdrom's. j?rg asked me for more info: and here comes some. 1. only one cd/dvd-burner om my machine produced this undesirable effect. a couple of other burners worked flawlessly with the most recent b?ta of j?rg sch. so it could be that j?rg did not make this beta recognize this burner: see /dev/hdb (from dmesg |less): hda: MAXTOR STM3250820A, ATA DISK drive hdb: Optiarc DVD RW AD-7173A, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: ST3120026A, ATA DISK drive Right! Neither cdrecord or wodim can burn to a _Hard Disk_. a good day to you all, And to you. WT ROFLOLBTTME -- Chris. == -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cdrecord vs. wodim again
hi all and *especially jörg s., long-term initiator of cdrecord and cdrtools*. two weeks ago i asked on this list 'what is better': cdrecord or wodim. on one of the responses i answered that the most recent version of cdrecord/cdr-tools completely damaged two brandnew cdrom's. jörg asked me for more info: and here comes some. 1. only one cd/dvd-burner om my machine produced this undesirable effect. a couple of other burners worked flawlessly with the most recent bêta of jörg sch. so it could be that jörg did not make this beta recognize this burner: see /dev/hdb (from dmesg |less): hda: MAXTOR STM3250820A, ATA DISK drive hdb: Optiarc DVD RW AD-7173A, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: ST3120026A, ATA DISK drive my machine: ($lspci -v) 0:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: access denied 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: 66MHz, fast devsel 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: 66MHz, fast devsel 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: 66MHz, fast devsel 00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: bus master, 66MHz, fast devsel, latency 0 00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: access denied 00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: 66MHz, fast devsel 00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: 66MHz, fast devsel 00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: d000-dfff Memory behind bridge: fd80-fd8f Prefetchable memory behind bridge: fd70-fd7f Capabilities: access denied 00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: b000-bfff Memory behind bridge: fde0-fdef Prefetchable memory behind bridge: fdd0-fddf Capabilities: access denied 00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: e000-efff Memory behind bridge: fdc0-fdcf Prefetchable memory behind bridge: fd90-fd9f Capabilities: access denied 00:05.0 VGA compatible controller: nVidia Corporation C51PV [GeForce 6150] (rev a2) (prog-if 00 [VGA]) Subsystem: ASUSTeK Computer Inc. Unknown device 81cd Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 58 Memory at fc00 (32-bit, non-prefetchable) [size=16M] Memory at e000 (64-bit, prefetchable) [size=256M] Memory at fb00 (64-bit, non-prefetchable) [size=16M] [virtual] Expansion ROM at 5000 [disabled] [size=128K] Capabilities: access denied 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: access denied 00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: bus master, 66MHz, fast devsel, latency 0 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: 66MHz, fast devsel, IRQ 5 I/O ports at 4c00 [size=64] I/O ports at 4c40 [size=64] Capabilities: access denied 00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: 66MHz, fast devsel 00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) (prog-if 10 [OHCI
cdrecord vs. wodim again
hi all and *especially jörg s., long-term initiator of cdrecord and cdrtools*. two weeks ago i asked on this list 'what is better': cdrecord or wodim. on one of the responses i answered that the most recent version of cdrecord/cdr-tools completely damaged two brandnew cdrom's. jörg asked me for more info: and here comes some. 1. only one cd/dvd-burner om my machine produced this undesirable effect. a couple of other burners worked flawlessly with the most recent bêta of jörg sch. so it could be that jörg did not make this beta recognize this burner: see /dev/hdb (from dmesg |less): hda: MAXTOR STM3250820A, ATA DISK drive hdb: Optiarc DVD RW AD-7173A, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: ST3120026A, ATA DISK drive my machine: ($lspci -v) 0:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: access denied 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: 66MHz, fast devsel 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: 66MHz, fast devsel 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: 66MHz, fast devsel 00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: bus master, 66MHz, fast devsel, latency 0 00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: access denied 00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: 66MHz, fast devsel 00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: 66MHz, fast devsel 00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: d000-dfff Memory behind bridge: fd80-fd8f Prefetchable memory behind bridge: fd70-fd7f Capabilities: access denied 00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: b000-bfff Memory behind bridge: fde0-fdef Prefetchable memory behind bridge: fdd0-fddf Capabilities: access denied 00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: e000-efff Memory behind bridge: fdc0-fdcf Prefetchable memory behind bridge: fd90-fd9f Capabilities: access denied 00:05.0 VGA compatible controller: nVidia Corporation C51PV [GeForce 6150] (rev a2) (prog-if 00 [VGA]) Subsystem: ASUSTeK Computer Inc. Unknown device 81cd Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 58 Memory at fc00 (32-bit, non-prefetchable) [size=16M] Memory at e000 (64-bit, prefetchable) [size=256M] Memory at fb00 (64-bit, non-prefetchable) [size=16M] [virtual] Expansion ROM at 5000 [disabled] [size=128K] Capabilities: access denied 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: access denied 00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: bus master, 66MHz, fast devsel, latency 0 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: 66MHz, fast devsel, IRQ 5 I/O ports at 4c00 [size=64] I/O ports at 4c40 [size=64] Capabilities: access denied 00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0 Flags: 66MHz, fast devsel 00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) (prog-if 10 [OHCI]) Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Re: cdrecord vs. wodim again
steef([EMAIL PROTECTED]) is reported to have said: hi all and *especially jörg s., long-term initiator of cdrecord and cdrtools*. two weeks ago i asked on this list 'what is better': cdrecord or wodim. on one of the responses i answered that the most recent version of cdrecord/cdr-tools completely damaged two brandnew cdrom's. jörg asked me for more info: and here comes some. 1. only one cd/dvd-burner om my machine produced this undesirable effect. a couple of other burners worked flawlessly with the most recent bêta of jörg sch. so it could be that jörg did not make this beta recognize this burner: see /dev/hdb (from dmesg |less): hda: MAXTOR STM3250820A, ATA DISK drive hdb: Optiarc DVD RW AD-7173A, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: ST3120026A, ATA DISK drive Right! Neither cdrecord or wodim can burn to a _Hard Disk_. a good day to you all, And to you. WT -- | LINUX - Because a PC is a terrible thing to waste..on WinDoze | ___
Re: cdrecord vs. wodim again
On Tue, Oct 02, 2007 at 03:46:51PM -0400, Wayne Topa wrote: steef([EMAIL PROTECTED]) is reported to have said: hi all and *especially jörg s., long-term initiator of cdrecord and cdrtools*. two weeks ago i asked on this list 'what is better': cdrecord or wodim. on one of the responses i answered that the most recent version of cdrecord/cdr-tools completely damaged two brandnew cdrom's. jörg asked me for more info: and here comes some. 1. only one cd/dvd-burner om my machine produced this undesirable effect. a couple of other burners worked flawlessly with the most recent bêta of jörg sch. so it could be that jörg did not make this beta recognize this burner: see /dev/hdb (from dmesg |less): hda: MAXTOR STM3250820A, ATA DISK drive hdb: Optiarc DVD RW AD-7173A, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: ST3120026A, ATA DISK drive Right! Neither cdrecord or wodim can burn to a _Hard Disk_. where do you get this? He provided no info on what command he used and if you look, hdb is clearly an optical drive... are you drinking too much coffee? ;) A signature.asc Description: Digital signature
Re: cdrecord vs. wodim again
On Tue, Oct 02, 2007 at 10:11:29AM +, steef wrote: two weeks ago i asked on this list 'what is better': cdrecord or wodim. on one of the responses i answered that the most recent version of cdrecord/cdr-tools completely damaged two brandnew cdrom's. Just to clarify, do you mean that the cdrom (the $1 or so disc) or do you mean that it damanged the drive itself (the $50-100 drive)? Since the drive has a laser, I can see that a bad app/driver could point that thing at the wrong spot on the disc and wreck it. It would be a whole 'nother ball of wax if we risk killing hardware running a standard app. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord vs. wodim again
Andrew Sackville-West([EMAIL PROTECTED]) is reported to have said: On Tue, Oct 02, 2007 at 03:46:51PM -0400, Wayne Topa wrote: steef([EMAIL PROTECTED]) is reported to have said: hi all and *especially jörg s., long-term initiator of cdrecord and cdrtools*. two weeks ago i asked on this list 'what is better': cdrecord or wodim. on one of the responses i answered that the most recent version of cdrecord/cdr-tools completely damaged two brandnew cdrom's. jörg asked me for more info: and here comes some. 1. only one cd/dvd-burner om my machine produced this undesirable effect. a couple of other burners worked flawlessly with the most recent bêta of jörg sch. so it could be that jörg did not make this beta recognize this burner: see /dev/hdb (from dmesg |less): hda: MAXTOR STM3250820A, ATA DISK drive ###hdb: Optiarc DVD RW AD-7173A, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: ST3120026A, ATA DISK drive Right! Neither cdrecord or wodim can burn to a _Hard Disk_. where do you get this? He provided no info on what command he used and if you look, hdb is clearly an optical drive... are you drinking too ^^^ But I didn't see that! much coffee? ;) I wish. The line ### commented was not on my radar. I saw the line above my comment and thought Why is he trying to burn a cd on an ATA Disk Dirve. My bad. With the mail being so light today, I was working on a couple of laptops and just missed the hdb line. Easily confused ... need ...MORE COFFEE. WT -- Please trim quotes to minimum for context, then reply below or interleave point-by-point replies. ___
Re: cdrecord problem
hallo joerg, your two emails plus the info on your website contain enough points/arguments for me to get rid of wodim and install the latest version of cdrecords and the tools again. before wodim appeared i used cdrecord for many years without any problem: the program did what it promised. kind regards, steef van duin groningen holland Joerg Schilling wrote: I have both cdrecord (Cdrecord-Clone 2.01.01a01) and wodim (1.1.6) on my Sarge system. I'm using kernel 2.6.22 right now. This is a very very old version of cdrecord! It is definitely unable to work around the bugs in a Linus-2.6 kernel. Use a recent version of cdrecord http://cdrecord.berlios.de/old/private/linux-dist.html#packages Jörg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord problem
I have both cdrecord (Cdrecord-Clone 2.01.01a01) and wodim (1.1.6) on my Sarge system. I'm using kernel 2.6.22 right now. This is a very very old version of cdrecord! It is definitely unable to work around the bugs in a Linus-2.6 kernel. Use a recent version of cdrecord http://cdrecord.berlios.de/old/private/linux-dist.html#packages Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord problem
I have an Etch box with a linux-image-2.6.18-5-k7. All works well but wodim -devices Beginning native device scan. This may take a while ... wodim: Invalid argument. Cannot Set SG_SET_TIMEOUT Apt-get install wodim confirms I have the latest release. I have also run apt-get dist-upgrade but still get the same result from wodim -devices. What's wrong? The problem is still unsolved. Do not expect this to be fixed in wodim. Wodim was an attempt to harm free software at the expense of the users. The first 8 months, there was some speudo acticivies but since 4.5 months it is dead. linux-image-2.6.18-5-amd64 kernel, a Lite-On DVDRW drive and a CompUSA CD_RW drive.With the linux cdrecord (wodim) I get the wodim: Invalid argument. Cannot Set SG_SET_TIMEOUT message. With the original cdrecord the cdrecord -scanbus finds both drives immediately but when I try to burn a cd neither works. If I specify the Lite-On drive there are grinding noises and, after several delays, most of the Did you use a recent cdrecord version? Recent is 2.01.01a35 and the old versions (including wodim) you find on the non-cooperative Linux distributions do not include workarounds for the bugs in recent Linux kernels. http://cdrecord.berlios.de/old/private/linux-dist.html#packages If you did never compile software, you may try to use the Ubuntu binaries... Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord problem - Correction
Joerg Schily's original cdrecord works perfectly. Apparently I have a box of bad blank cdrw disks, 100 of them unfortunately. I tried cdrw disks from another box and cdrecord ran the Lite-On drive at 25x with no problems. Tom George -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord problem - Correction
Thomas H. George [EMAIL PROTECTED]: Joerg Schily's original cdrecord works perfectly. Apparently I have a box of bad blank cdrw disks, 100 of them unfortunately. I tried cdrw disks from another box and cdrecord ran the Lite-On drive at 25x with no problems. fwiw, I've heard a lot of stories about CD-RW being pretty unreliable. Every time you blank them, expect them to get smaller (capacity), which I expect is reasonable. I don't use them anymore. Dunno if this helps. -- Any technology distinguishable from magic is insufficiently advanced. (*)http://blinkynet.net/comp/uip5.html Linux Counter #80292 - -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cdrecord problem
On Sept. 7 I posted a problem, I have an Etch box with a linux-image-2.6.18-5-k7. All works well but wodim -devices Beginning native device scan. This may take a while ... wodim: Invalid argument. Cannot Set SG_SET_TIMEOUT Apt-get install wodim confirms I have the latest release. I have also run apt-get dist-upgrade but still get the same result from wodim -devices. What's wrong? The problem is still unsolved. I received several responses but was unable to respond to the thread until yesterday due to an MTA problem. Most of the responses suggested the difficulty was the lack of SCSI emulation. The config.gz accompanying the linux-image-2.6.18-5-k7 confirms that the kernel was not compiled with SCSI emulation as this is no longer necessary for 2.6 kernels. Joerg Schily also responded with an emphatic message that linux uses an old, broken version of his cdrecord program and recommending I download the latest version of the original free program. I did but have not yet been able to make it work either though the problems are different. I switched to another Etch box with an AMD 64 cpu, a linux-image-2.6.18-5-amd64 kernel, a Lite-On DVDRW drive and a CompUSA CD_RW drive.With the linux cdrecord (wodim) I get the wodim: Invalid argument. Cannot Set SG_SET_TIMEOUT message. With the original cdrecord the cdrecord -scanbus finds both drives immediately but when I try to burn a cd neither works. If I specify the Lite-On drive there are grinding noises and, after several delays, most of the preliminary messages are written to the screen and then the report that the drive is not ready. If I specify the CD_RW drive again most of the preliminary messages are displayed and then the message No disk, wrong disk. I know that two months ago I burnt an iso with one of the drives on this box. To the best of my recollection I have made no changes other than dist-upgrades since then. Any suggestions as to what has gone wrong? Tom George -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord problem
On Sun, Sep 16, 2007 at 08:29:18PM -0400, Thomas H. George wrote: On Sept. 7 I posted a problem, I have an Etch box with a linux-image-2.6.18-5-k7. All works well but wodim -devices Beginning native device scan. This may take a while ... wodim: Invalid argument. Cannot Set SG_SET_TIMEOUT Apt-get install wodim confirms I have the latest release. I have also run apt-get dist-upgrade but still get the same result from wodim -devices. What's wrong? The problem is still unsolved. I received several responses but was unable to respond to the thread until yesterday due to an MTA problem. Most of the responses suggested the difficulty was the lack of SCSI emulation. The config.gz accompanying the linux-image-2.6.18-5-k7 confirms that the kernel was not compiled with SCSI emulation as this is no longer necessary for 2.6 kernels. true Joerg Schily also responded with an emphatic message that linux uses an old, broken version of his cdrecord program and recommending I download the latest version of the original free program. I did but have not yet been able to make it work either though the problems are different. I switched there was a fork of cdrecord to wodim (this is from memory). some simple things to try can you see the device normally - ie can you mount a cd from that device have you tried just a wodim -inq /dev/hda (if its known as /dev/hda ?). If you get an error here what is in dmesg or /var/log/messages or /var/log/syslog to another Etch box with an AMD 64 cpu, a linux-image-2.6.18-5-amd64 kernel, a Lite-On DVDRW drive and a CompUSA CD_RW drive.With the linux cdrecord (wodim) I get the wodim: Invalid argument. Cannot Set SG_SET_TIMEOUT message. With the original cdrecord the cdrecord -scanbus finds both drives immediately but when I try to burn a cd neither works. If I specify the Lite-On drive there are grinding noises and, after several delays, most of the preliminary messages are written to the screen and then the report that the drive is not ready. If I specify the CD_RW drive again most of the preliminary messages are displayed and then the message No disk, wrong disk. I know that two months ago I burnt an iso with one of the drives on this box. To the best of my recollection I have made no changes other than dist-upgrades since then. Any suggestions as to what has gone wrong? Tom George -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: cdrecord problem
On 09/16/2007 07:29 PM, Thomas H. George wrote: On Sept. 7 I posted a problem, I have an Etch box with a linux-image-2.6.18-5-k7. All works well but wodim -devices Beginning native device scan. This may take a while ... wodim: Invalid argument. Cannot Set SG_SET_TIMEOUT Apt-get install wodim confirms I have the latest release. I have also run apt-get dist-upgrade but still get the same result from wodim -devices. What's wrong? The problem is still unsolved. I received several responses but was unable to respond to the thread until yesterday due to an MTA problem. Most of the responses suggested the difficulty was the lack of SCSI emulation. The config.gz accompanying the linux-image-2.6.18-5-k7 confirms that the kernel was not compiled with SCSI emulation as this is no longer necessary for 2.6 kernels. Joerg Schily also responded with an emphatic message that linux uses an old, broken version of his cdrecord program and recommending I download the latest version of the original free program. I did but have not yet been able to make it work either though the problems are different. I switched to another Etch box with an AMD 64 cpu, a linux-image-2.6.18-5-amd64 kernel, a Lite-On DVDRW drive and a CompUSA CD_RW drive.With the linux cdrecord (wodim) I get the wodim: Invalid argument. Cannot Set SG_SET_TIMEOUT message. With the original cdrecord the cdrecord -scanbus finds both drives immediately but when I try to burn a cd neither works. If I specify the Lite-On drive there are grinding noises and, after several delays, most of the preliminary messages are written to the screen and then the report that the drive is not ready. If I specify the CD_RW drive again most of the preliminary messages are displayed and then the message No disk, wrong disk. I know that two months ago I burnt an iso with one of the drives on this box. To the best of my recollection I have made no changes other than dist-upgrades since then. Any suggestions as to what has gone wrong? Tom George I have both cdrecord (Cdrecord-Clone 2.01.01a01) and wodim (1.1.6) on my Sarge system. I'm using kernel 2.6.22 right now. The command wodim -devices works properly on my system--but I'm using SCSI emulation. I have the 'ide-scsi' driver take over /dev/hdb (my CDRW drive) at boot. This is on my kernel command line: hdb=ide-scsi And I have a startup script that loads ide-scsi at boot time. Basically, I'm treating my 2.6 kernel as a 2.4 kernel for the sake of cdrecord/wodim harmony. I would that it would be as easy to create harmony between certain cdrecord developers and Debian :-P -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cdrecord with a 2.4 kernel
Woohoo, reloading works indeed. The files are visible when I use the -eject flag and mount the cd afterwards. Thanks for the helping part Regards, Ben 2007/1/30, Eduard Bloch [EMAIL PROTECTED]: #include hallo.h * Sonixxfx [Tue, Jan 23 2007, 03:11:47PM]: Hi, I am trying to burn multisession cd's with cdrecord but I have a problem. After I have written a multisession disc, and mount it, the burned files are not shown at /media/cdrom. The files are written to the disc though, because I can access/see them when I have rebooted my system and mount the cd. Reboot? OMG. Just reload the disk. Eduard.
Re: Cdrecord with a 2.4 kernel
#include hallo.h * Sonixxfx [Tue, Jan 23 2007, 03:11:47PM]: Hi, I am trying to burn multisession cd's with cdrecord but I have a problem. After I have written a multisession disc, and mount it, the burned files are not shown at /media/cdrom. The files are written to the disc though, because I can access/see them when I have rebooted my system and mount the cd. Reboot? OMG. Just reload the disk. Eduard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cdrecord with a 2.4 kernel
Please help me! Thanks :) 2007/1/23, Sonixxfx [EMAIL PROTECTED]: Hi, I am trying to burn multisession cd's with cdrecord but I have a problem. After I have written a multisession disc, and mount it, the burned files are not shown at /media/cdrom. The files are written to the disc though, because I can access/see them when I have rebooted my system and mount the cd. I am running Debian Sarge with a 2.4 kernel. I don't have this problem with a 2.6 kernel. I have tried cdrecord and mkisofs from Debian stable, I have tried wodim from backports.org , and I have tried the latest Cdrecord which I have compiled and installed myself. I have also tried my own compiled 2.4 kernel. I believe I have done everything that is needed to run Cdrecord together with a 2.4 kernel: 1) I have appended hdc=ide-scsi to the kernel line in Grub. 2) I have loaded the modules sr_mod, sd_mod, ide-scsi and sg. 3) I did not load the ide-cd module. 4) I also adapted /etc/fstab and substituted the /dev/hdc part with /dev/scd0 Also cdrecord -scanbus shows my (Sony but I have also tried this with a HP) writer, and burning and everything else seems to go fine. So does someone know what I can do about this? Thanks for your help. Regards, Ben
Cdrecord with a 2.4 kernel
Hi, I am trying to burn multisession cd's with cdrecord but I have a problem. After I have written a multisession disc, and mount it, the burned files are not shown at /media/cdrom. The files are written to the disc though, because I can access/see them when I have rebooted my system and mount the cd. I am running Debian Sarge with a 2.4 kernel. I don't have this problem with a 2.6 kernel. I have tried cdrecord and mkisofs from Debian stable, I have tried wodim from backports.org, and I have tried the latest Cdrecord which I have compiled and installed myself. I have also tried my own compiled 2.4kernel. I believe I have done everything that is needed to run Cdrecord together with a 2.4 kernel: 1) I have appended hdc=ide-scsi to the kernel line in Grub. 2) I have loaded the modules sr_mod, sd_mod, ide-scsi and sg. 3) I did not load the ide-cd module. 4) I also adapted /etc/fstab and substituted the /dev/hdc part with /dev/scd0 Also cdrecord -scanbus shows my (Sony but I have also tried this with a HP) writer, and burning and everything else seems to go fine. So does someone know what I can do about this? Thanks for your help. Regards, Ben
Re: Cdrecord with a 2.4 kernel
I thought this problem only occured with a 2.4 kernel, but it is also happening with a 2.6 kernel. Thanks Ben 2007/1/23, Sonixxfx [EMAIL PROTECTED]: Hi, I am trying to burn multisession cd's with cdrecord but I have a problem. After I have written a multisession disc, and mount it, the burned files are not shown at /media/cdrom. The files are written to the disc though, because I can access/see them when I have rebooted my system and mount the cd. I am running Debian Sarge with a 2.4 kernel. I don't have this problem with a 2.6 kernel. I have tried cdrecord and mkisofs from Debian stable, I have tried wodim from backports.org , and I have tried the latest Cdrecord which I have compiled and installed myself. I have also tried my own compiled 2.4 kernel. I believe I have done everything that is needed to run Cdrecord together with a 2.4 kernel: 1) I have appended hdc=ide-scsi to the kernel line in Grub. 2) I have loaded the modules sr_mod, sd_mod, ide-scsi and sg. 3) I did not load the ide-cd module. 4) I also adapted /etc/fstab and substituted the /dev/hdc part with /dev/scd0 Also cdrecord -scanbus shows my (Sony but I have also tried this with a HP) writer, and burning and everything else seems to go fine. So does someone know what I can do about this? Thanks for your help. Regards, Ben
cdrecord / xcdroast on Sarge / 2.6.8-3 as user - FYI
Call this redundant (and soon - with Etch - outdated). The archive is full of posts on this topic, but none seems to wrap it up. Instead of you having to to sort it out, try this: 1. All this 'ATAPI' is logically correct, but not technically. Use 'ATA'. 2. 'cdrecord dev=ATA: -scanbus' is the way to go. 3. Then use the result of 2 above for your commands for cdrecord; as in cdrecord -v blank=fast dev=ATA:1,1,0 (whatever 2 came up with). 4. Delete the found device in xcdroast, add [ATA:1,1,0] manually in the setup, wait for it to recognize the drive. Save. Enjoy either of the two as user. Instead of sudo, root or set-uid: # ls -l /usr/bin/cdrecord* -rwxr-xr-x 1 root root133 2005-01-10 00:55 /usr/bin/cdrecord -rwxr-xr-x 1 root root 348556 2005-01-10 00:55 /usr/bin/cdrecord.mmap -rwxr-xr-x 1 root root 351404 2005-01-10 00:55 /usr/bin/cdrecord.shm # ls -l /dev/hdd brw-rw 1 root disk 22, 64 2004-04-30 08:27 /dev/hdd The only thing needed is that your user is member of group 'disk'. The latter shows why. Have fun, Uwe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord / xcdroast on Sarge / 2.6.8-3 as user - FYI
On Sun, Nov 26, 2006 at 01:22:47AM +0800, Uwe Dippel wrote: # ls -l /dev/hdd brw-rw 1 root disk 22, 64 2004-04-30 08:27 /dev/hdd The only thing needed is that your user is member of group 'disk'. The latter shows why. Don’t use the group disk, use group cdrom instead. Anyone in group disk can read and write direct to the disks (e.g deleting partitions). You don’t want this. Shade and sweet water! Stephan -- | Stephan SeitzE-Mail: [EMAIL PROTECTED] | | PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html | signature.asc Description: Digital signature
Re: cdrecord / xcdroast on Sarge / 2.6.8-3 as user - FYI
On Sat, 25 Nov 2006 19:04:21 +0100, Stephan Seitz wrote: Don't use the group disk, use group cdrom instead. Anyone in group disk can read and write direct to the disks (e.g deleting partitions). You don't want this. Ah, sure ! - I think now it is perfect. Thanks, Uwe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cdrecord
Salut Suite à une install toute fraîche de etch (via bussinesscard) et ayant choisi desktop avec taskel, je découvre la version de cette distrib. Impossible d'effacer des cdrw par défaut car le paquet cdrecord n'y figure pas, il m'a fallu le télécharger pour que tout rentre dans l'ordre. C'est un peu déroutant comme choix par défaut. Cela dit, je sais que cdrecord et debian ne sont pas copain mais quand même, cela peut dérouter un nouveau venu. Voilà, c'était juste pour servir d'info si quelqu'un à les mêmes soucis. nono signature.asc Description: Ceci est une partie de message numériquement signée
Gnomebaker, wodim et cdrecord...
Re-bonjour, J'ai maintenant un problème avec gnomebaker... En effet, pour l'utiliser avec un user simple (non root), je faisais auparavant un dpkg-reconfigure cdrecord et j'activais le bit suid root. A présent, cette commande ne fait plus rien et il semble même que gnomebaker utilise wodim et non plus cdrecord. J'ai manuellement mis le bit suid root sur wodim mais j'ai toujours des soucis... Auriez-vous une petite piste ? Merci d'avance. David. signature.asc Description: Ceci est une partie de message numériquement signée
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
Am Dienstag, 24. Oktober 2006 20:46 schrieb Meinolf Sander: * Peter Kuechler schrieb: Am Montag, 23. Oktober 2006 21:01 schrieb Joerg Schilling: frank paulsen [EMAIL PROTECTED] wrote: Jörg, ob dein betriebsystem nun kaputt vorkonfiguriert ist, oder nicht: die deklaration des zeichensatzes in deinem header ist einzig und allein von dir zu verantworten. Da die einzigen, die Probleme mit dem Lesen zu haben scheinen, bestimmte Linux Varianten verwenden und z.B. SuSE Linux nachweislich keine Probleme hat und die von Solaris verwendete Zeichensatzbenennung seit 16 Jahren verwendet wird, solltest Du Dir vielleicht mal Gedenken machen wie Du die Probleme mit Deinem BS behebst... Ach du dickes Ding, jetzt hast du aber eine Rakete abgeschosssen! Also wenn _das_ tatsächlich deine Einstellung ist, so lässt sie die endlose Diskussion um cdrecord usw. in einem etwas anderen Licht erscheinen. Volles ACK. Das ist Ignoranz, gepaart mit Sturheit, in Reinform. Wer es noch nicht mal auf die Reihe kriegt, seine Mails standardkonform zu deklarieren, sollte besser kleinere Brötchen backen. Ob er es nicht kann möchte ich nicht beurteilen. Was mich mehr nervt ist die Einstellung Was Sun Microsystems macht ist richtig. Punkt!. Wenn etwas laut offizieller Regel (und die RFCs sind ja wohl offiziell) falsch ist, dann ist es eben falsch. Nur weil man etwas immer wieder falsch macht, wird es dadurch nicht richtiger. Auch dann nicht, wenn die Firma Sun heist und jemand wie Jörg Solaris-Fan ist. Jörg Schilling kann man jedenfalls nicht mehr ernst nehmen. Zumindest muß ich seine Aussagen jetzt anders bewerten. -- mfg Peter Küchler
Re: Überlange CD mit 'cdrecord'
Am Dienstag, 24. Oktober 2006 21:39 schrieb Eduard Bloch: #include hallo.h * Rolf Hermann [Tue, Oct 24 2006, 06:55:55PM]: Hi zusammen! Ich habe mir mit 'mkisofs' ein Image gemacht, dass ich gerne brennen möchte. Die Iso-Datei ist genau 730.757.120 Bytes groß. Ich frage mich allerdings, ob das auf einen 700-MB-Rohling passt -- ich Track 01: data 696 MB ^^ Willkommen bei dem grossen WirrWar um die Einheiten. Bei Rohlingen sind mit MB MebiByte gemeint (1048576 Byte), bei Festplatten Megabyte Auch auf die Gefahr hin mich jetzt zu blamieren, aber was zum Geier ist ein MebiByte (10^6Byte). Die binären Einheiten gibt es offiziell aber erst seit 1996, davor wurde MB und Megabyte willkürlich für binäre Einheiten verwendet. ??? Meine Verwirrung steigt... wo ist der Unterschied zwischen MB und Megabyte? Ist mit binären Einheiten Megabit gemeint? Leider hat sich das MB = Megabyte = 2^10 in den Köpfen einiger Softwareentwickler festgefressen. Es würde mich nicht wundern, wenn wir auch noch in 10 Jahren neuen Programmen begegnen, bei dennen es falsch gemacht wird. Eduard. -- mfg Peter Küchler
Re: Überlange CD mit 'cdrecord'
Am Mittwoch 25 Oktober 2006 11:07 schrieb Peter Kuechler: Auch auf die Gefahr hin mich jetzt zu blamieren, aber was zum Geier ist ein MebiByte http://de.wikipedia.org/wiki/Bin%C3%A4rpr%C3%A4fix Gruß Chris -- A: because it distrupts the normal process of thought Q: why is top posting frowned upon
Re: Überlange CD mit 'cdrecord'
Hallo, Auch auf die Gefahr hin mich jetzt zu blamieren, aber was zum Geier ist ein MebiByte Kurze Erklärung findet sich in der Wikipedia: http://de.wikipedia.org/wiki/Megabyte VG Michael -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
Meinolf schrieb am 24. Oct um 20:46 Uhr: Jörg Schilling kann man jedenfalls nicht mehr ernst nehmen. Warum soll ich jemanden nicht ernst nehmen, der ein tolles, gut funktionierendes und freies CD-Brennprogramm für Linux geschrieben hat, das ich seit Jahren gern und oft benutze? Und stattdessen Leute ernstnehmen, die sich darüber streiten, ob eine Zeichensatzdeklaration ein Minuszeichen enthalten muss oder nicht? Na ja. Wie auch immer. Jedem das seine. Gruß Christian -- Christian Knoke* * *http://cknoke.de * * * * * * * * * Ceterum censeo Microsoft esse dividendum. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
Hallo Christian, * Christian Knoke [EMAIL PROTECTED] [20061025 11:55]: Meinolf schrieb am 24. Oct um 20:46 Uhr: Jörg Schilling kann man jedenfalls nicht mehr ernst nehmen. Warum soll ich jemanden nicht ernst nehmen, der ein tolles, gut funktionierendes und freies CD-Brennprogramm für Linux geschrieben hat, Weil Schily seit Jahren ein Rumpelstilzchen ist. Dass gewisse Leute nicht seiner Meinung sind kann er nicht ertragen, deshalb kommt von ihm in den meisten Foren und Mailinglisten nur noch dummes bashing. Google liefert Beispiele. Und stattdessen Leute ernstnehmen, die sich darüber streiten, ob eine Zeichensatzdeklaration ein Minuszeichen enthalten muss oder nicht? Tja, wer streitet denn darüber? -- | /\ ASCII Ribbon | Felix M. Palmen (Zirias)http://zirias.ath.cx/ | | \ / Campaign Against | [EMAIL PROTECTED] encrypted mail welcome | | XHTML In Mail | PGP key: http://zirias.ath.cx/pub.txt | | / \ And News | ED9B 62D0 BE39 32F9 2488 5D0C 8177 9D80 5ECF F683 | signature.asc Description: Digital signature
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
* Christian Knoke wrote: Und stattdessen Leute ernstnehmen, die sich darüber streiten, ob eine Zeichensatzdeklaration ein Minuszeichen enthalten muss oder nicht? _Das_ ist es ja eben. Standards werden geschaffen, damit das Streiten aufhört. Trotzdem weigern sich manche, Standards zu akzeptieren (Jörg, Microsoft, Sun?, ...). IMO ist das nicht schön ;( Ciao, Christian -- (o_ Christian Hoeller (aka zy3) (o _o) (o_ //\ (/)_ (/)_ (/)_ V_/_ http://www.linux-drivers.org -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Knoke wrote: Meinolf schrieb am 24. Oct um 20:46 Uhr: Jörg Schilling kann man jedenfalls nicht mehr ernst nehmen. Warum soll ich jemanden nicht ernst nehmen, der ein tolles, gut funktionierendes und freies CD-Brennprogramm für Linux geschrieben hat, das ich seit Jahren gern und oft benutze? Windows XP SP2 funktioniert auch und tut. Dennoch sind wir hier eine DEBIAN ML mit entsprechenden Lizenzen. Nur weil etwas gut funktioniert und es kostenfrei erhältlich ist, ist es noch lange nicht kompatibel mit den Forderungen der Distribution. Wem das nicht gefällt darf selber basteln oder wechselt eben. Und stattdessen Leute ernstnehmen, die sich darüber streiten, ob eine Zeichensatzdeklaration ein Minuszeichen enthalten muss oder nicht? Na ja. Wie auch immer. Jedem das seine. Standards sind Standards. Wenn man sich nicht dran hält bekommt man eben sowas wie Outlook oder andere derartigen Produkte. Ich schreibe ja auch nicht auf einmal in Koreanisch und erkläre, daß Ich jetzt korrekt schreibe und alle anderen sich anpassen müssen. Gruß Christian MfG, Lars Schimmer - -- - - TU Graz, Institut für ComputerGraphik WissensVisualisierung Tel: +43 316 873-5405 E-Mail: [EMAIL PROTECTED] Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFP0fwmWhuE0qbFyMRAtC7AJ98ontCWC61HRMFon0o5myZBQWqMACdF0tl 0xWOrkJJfOE3nritSs4awMk= =871b -END PGP SIGNATURE- -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
On Wed, Oct 25, 2006 at 11:55:30AM +0200, Christian Knoke wrote: Meinolf schrieb am 24. Oct um 20:46 Uhr: Jörg Schilling kann man jedenfalls nicht mehr ernst nehmen. Warum soll ich jemanden nicht ernst nehmen, der ein tolles, gut funktionierendes und freies CD-Brennprogramm für Linux geschrieben hat, das ich seit Jahren gern und oft benutze? Vieleicht meinen wir unterschedliche Leute. JS faellt hier seit Jahren vor allem als Troll auf. Seine Qualitaeten als Entwickler finden leider keine Ergaenzung in sozialer Kompetenz. Belege finden sich in dengäigen Usenet/ML- Arciven, oder z.B. auch bei heise.de. Und stattdessen Leute ernstnehmen, die sich darüber streiten, ob eine Zeichensatzdeklaration ein Minuszeichen enthalten muss oder nicht? Wer als Entwickler grosse Sprueche ueber die Kompetenz der Kollegen ablaesst, sollte sich selbst an gaengigen Standards messen lassen. cu ulf -- Ulf Volmer [EMAIL PROTECTED] +49-2271-837590 www.u-v.de -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Überlange CD mit 'cdrecord'
Am Mittwoch, 25. Oktober 2006 11:14 schrieb Michael Windelen: Hallo, Auch auf die Gefahr hin mich jetzt zu blamieren, aber was zum Geier ist ein MebiByte Kurze Erklärung findet sich in der Wikipedia: http://de.wikipedia.org/wiki/Megabyte Hui, da wird man immer älter und um sowas kümmert man sich nicht;-) Danke für die Hinweise, ich habe die Seiten mit interesse gelesen und wieder was gelernt. -- mfg Peter Küchler
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
Moin, Felix schrieb am 25. Oct um 13:06 Uhr: * Christian Knoke [EMAIL PROTECTED] [20061025 11:55]: Meinolf schrieb am 24. Oct um 20:46 Uhr: Jörg Schilling kann man jedenfalls nicht mehr ernst nehmen. Warum soll ich jemanden nicht ernst nehmen, der ein tolles, gut funktionierendes und freies CD-Brennprogramm für Linux geschrieben hat, Weil Schily seit Jahren ein Rumpelstilzchen ist. Dass gewisse Leute nicht seiner Meinung sind kann er nicht ertragen, deshalb kommt von ihm in den meisten Foren und Mailinglisten nur noch dummes bashing. Google liefert Beispiele. Ich hab das in den letzten Wochen, wo ich es verfolge, etwas anders wahrgenommen. Jörg wird von vielen angegriffen, weil er die Lizenz geändert hat. Er hat eine andere Meinung, und er äußert sie. Dummes Bashing war das nicht IMHO. Sich zu verteidigen ist sein Recht. Und stattdessen Leute ernstnehmen, die sich darüber streiten, ob eine Zeichensatzdeklaration ein Minuszeichen enthalten muss oder nicht? Tja, wer streitet denn darüber? Jörg wurde hier angegriffen wegen eines mail headers, und dies wurde in Bezug gesetzt zu seiner Softwarearbeit. Im übrigen hat der Recht, der die Arbeit macht. Gruß Christian -- Christian Knoke* * *http://cknoke.de * * * * * * * * * Ceterum censeo Microsoft esse dividendum. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
On 25.10.06 21:08:17, Christian Knoke wrote: Moin, Felix schrieb am 25. Oct um 13:06 Uhr: * Christian Knoke [EMAIL PROTECTED] [20061025 11:55]: Meinolf schrieb am 24. Oct um 20:46 Uhr: Jörg Schilling kann man jedenfalls nicht mehr ernst nehmen. Warum soll ich jemanden nicht ernst nehmen, der ein tolles, gut funktionierendes und freies CD-Brennprogramm für Linux geschrieben hat, Weil Schily seit Jahren ein Rumpelstilzchen ist. Dass gewisse Leute nicht seiner Meinung sind kann er nicht ertragen, deshalb kommt von ihm in den meisten Foren und Mailinglisten nur noch dummes bashing. Google liefert Beispiele. Ich hab das in den letzten Wochen, wo ich es verfolge, etwas anders wahrgenommen. Jörg wird von vielen angegriffen, weil er die Lizenz geändert hat. Er hat eine andere Meinung, und er äußert sie. Dummes Bashing war das nicht IMHO. Sich zu verteidigen ist sein Recht. Hmm, ich hab bei weitem nicht alles gelesen aber ein grosser Teil dessen was Joerg von sich gibt ist weitab von sachlicher Diskussion. (Das gilt fuer andere Diskussionsteilnehmer genauso). Und er greift seine Diskussions-Gegenueber genauso an. Es macht immernoch der Ton die Musik, und die von Joerg hoert sich IMHO ziemlich grausig an. Ich will ja nicht behaupten cdrecord waere Muell oder aehnliches, aber was ich bisher im Zusammenhang mit den aktuellen Lizenzproblemen von ihm gelesen habe zeugt nicht unbedingt von sozialer Kompetenz... Im übrigen hat der Recht, der die Arbeit macht. Nein, wer existierende Standards ignoriert und dann behauptet alle anderen Systeme waeren kaputt hat Unrecht. Andreas -- Day of inquiry. You will be subpoenaed. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
Am Mittwoch, 25. Oktober 2006 21:08 schrieb Christian Knoke: Ich hab das in den letzten Wochen, wo ich es verfolge, etwas anders wahrgenommen. Jörg wird von vielen angegriffen, weil er die Lizenz geändert hat. Er hat eine andere Meinung, und er äußert sie. Dummes Bashing war das nicht IMHO. Sich zu verteidigen ist sein Recht. Naja, die letzte Mail von ihm, die er im anderen Teil des Threads gesendet hat, ist leider hier nichtmehr angekommen, da ich im CC stand, kann man schon sagen das er gebasht hat. Leider hab ich sie schon gelöscht, sonst hätte ich sie dir gerne zukommen lassen. Jörg wurde hier angegriffen wegen eines mail headers, und dies wurde in Bezug gesetzt zu seiner Softwarearbeit. Nicht wirklich, Jörg hat nur wirklich sehr verquere Ansichten zu manchen Punkten. Ebenso ist er nicht in der Lage seinen Standpunkt zu vertreten, ohne auf persönliche Beleidungen etc zurückzugreifen. Im übrigen hat der Recht, der die Arbeit macht. Aha, heute ist die Gesundheitsreform auf erster Stufe abgesegnet worden. Die die sie gemacht haben, sagen sie wäre gut. Siehst du das auch so? -- MfG usw. Werner Mahr registered Linuxuser: 295882 pgpgtIaodc7Nh.pgp Description: PGP signature
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
Hallo Christian, * Christian Knoke [EMAIL PROTECTED] [20061025 21:08]: Felix schrieb am 25. Oct um 13:06 Uhr: Weil Schily seit Jahren ein Rumpelstilzchen ist. Dass gewisse Leute nicht seiner Meinung sind kann er nicht ertragen, deshalb kommt von ihm in den meisten Foren und Mailinglisten nur noch dummes bashing. Google liefert Beispiele. Ich hab das in den letzten Wochen, wo ich es verfolge, etwas anders wahrgenommen. Jörg wird von vielen angegriffen, weil er die Lizenz geändert hat. Er hat eine andere Meinung, und er äußert sie. Dummes Bashing war das nicht IMHO. Sich zu verteidigen ist sein Recht. ich habe DIESE Diskussion nicht verfolgt. Mit gutem Grund. Einmal kurz reingeschaut und es war wieder das gleiche Schema. Ich kenne Schilys Postings einfach schon zu lange. Glaub mit, was er betreibt ist nicht Verteidigung sondern Angriff. Ja, Angriff (nicht konstruktive Kritik) und oft genug noch unqualifizierter. Ist die Bits nicht wert, die da über die Leitungen fließen. -- | /\ ASCII Ribbon | Felix M. Palmen (Zirias)http://zirias.ath.cx/ | | \ / Campaign Against | [EMAIL PROTECTED] encrypted mail welcome | | XHTML In Mail | PGP key: http://zirias.ath.cx/pub.txt | | / \ And News | ED9B 62D0 BE39 32F9 2488 5D0C 8177 9D80 5ECF F683 | signature.asc Description: Digital signature
Re: cdrecord replacement (wodim) fails (WORKS NOW)
Wayne Topa([EMAIL PROTECTED]) is reported to have said: Just upgraded cdrecord and k3b to burn a Knoppix CD and find that the new replacement for cdrecord, wodim, can't handle it. It fails saying the file is larger the the CD. I have burned 6-8 of these CD's with k3b/cdrecord with never a problem, unitl wodim. I am currently downloading a jigdo stable installation disk and can only hope that I haven't just wasted my time (26K dialup) doing it. I had to reboot, due to a power failure, and on reboot k3b (wodim) was able to burn the CD without errors. Strange, but it does work! Wayne -- There are two ways to write error-free programs. Only the third one works. ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord replacement (wodim) fails (WORKS NOW)
On Wed October 25 2006 09:12, Wayne Topa wrote: Wayne Topa([EMAIL PROTECTED]) is reported to have said: Just upgraded cdrecord and k3b to burn a Knoppix CD and find that the new replacement for cdrecord, wodim, can't handle it. It fails saying the file is larger the the CD. I have burned 6-8 of these CD's with k3b/cdrecord with never a problem, unitl wodim. I am currently downloading a jigdo stable installation disk and can only hope that I haven't just wasted my time (26K dialup) doing it. I had to reboot, due to a power failure, and on reboot k3b (wodim) was able to burn the CD without errors. Strange, but it does work! It seems to work here too, mostly. I can't seem to burn a mixed mode CD anymore. I wonder why the change to wodim, cdrecord has been the main stay for cd burning for as long as I can remember. If wodim is the default now I hope it will work as well as cdrecord has all these years. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord replacement (wodim) fails (WORKS NOW)
[...] I wonder why the change to wodim, cdrecord has been the main stay for cd burning for as long as I can remember. If wodim is the default now I hope it will work as well as cdrecord has all these years. http://lwn.net/Articles/198171/ -- Javier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord replacement (wodim) fails (WORKS NOW)
On Wed October 25 2006 09:45, Javier-Elias Vasquez-Vivas wrote: [...] I wonder why the change to wodim, cdrecord has been the main stay for cd burning for as long as I can remember. If wodim is the default now I hope it will work as well as cdrecord has all these years. http://lwn.net/Articles/198171/ Ah, that explains it. Thank goodness we have a debburn group to handle that situation. I wonder if those guys can fix KDE's recent icon-zooming issues? Oh, never mind.. ;) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
On Mon, 23 Okt 2006, Joerg Schilling wrote: Da die einzigen, die Probleme mit dem Lesen zu haben scheinen, bestimmte Linux Varianten verwenden und z.B. SuSE Linux nachweislich keine Probleme hat und die von Solaris verwendete Zeichensatzbenennung seit 16 Jahren verwendet wird, solltest Du Dir vielleicht mal Gedenken machen wie Du die Probleme mit Deinem BS behebst... Spricht einer der immer so auf Standard-Konformität pocht, aber in anderne Bereichen eben auf RFCs etc sch Sehr einseitige Wahrnehmung. Norbert --- Dr. Norbert Preining [EMAIL PROTECTED]Università di Siena Debian Developer [EMAIL PROTECTED] Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- it's at times like this, when I'm trapped in a Vogon airlock with a man from Betelgeuse, and about to die from asphyxiation in deep space that I really wish I'd listened to what my mother told me when I was young.' `Why, what did she tell you?' `I don't know, I didn't listen.' --- Arthur coping with certain death as best as he could. --- Douglas Adams, The Hitchhikers Guide to the Galaxy -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
#include hallo.h * Joerg Schilling [Mon, Oct 23 2006, 09:01:01PM]: frank paulsen [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] (Joerg Schilling) writes: J.rg Schilling ist auch nach aufforderung nicht in der lage, mails mit nach MIME-standard korrekt deklariertem zeichensatz zu versenden. Wenn Du Probleme mit einer seit .ber 16 Jahren .blichen Praxis bei der Benennung von Lokalen hast, dann kannst Du es ja mal mit einem Bug-Report an dieser Stelle versuchen: Jörg, ob dein betriebsystem nun kaputt vorkonfiguriert ist, oder nicht: die deklaration des zeichensatzes in deinem header ist einzig und allein von dir zu verantworten. Da die einzigen, die Probleme mit dem Lesen zu haben scheinen, bestimmte Wenn es dir scheint muss es noch lange nicht für andere gelten. Linux Varianten verwenden und z.B. SuSE Linux nachweislich keine Probleme Wer hat was nachgewiesen? Oder meinst du Beweis durch Behauptung und nichtrepresäntativen Test? hat und die von Solaris verwendete Zeichensatzbenennung seit 16 Jahren verwendet wird, solltest Du Dir vielleicht mal Gedenken machen wie Du die Probleme mit Deinem BS behebst... Und wie kommst du darauf, dass die Nomenklatur von Solaris für den MIME-Standard relevant ist? Die Referenzen auf relevante Dokumente wurden schon genannt. Hier ein Beispiel für einen MUA, der es unter SunOS richtig macht: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.1i Abgeschickt von: SunOS poker 5.9 Generic_118558-34 sun4u sparc locale: LANG=de_DE.ISO8859-1 LC_CTYPE=de_DE.ISO8859-1 ... Eduard. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Überlange CD mit 'cdrecord'
Hi zusammen! Ich habe mir mit 'mkisofs' ein Image gemacht, dass ich gerne brennen möchte. Die Iso-Datei ist genau 730.757.120 Bytes groß. Ich frage mich allerdings, ob das auf einen 700-MB-Rohling passt -- ich möchte meinen Brenner nicht kaputt machen, falls es über die CD raus brennen würde . . . Im Dummy-Modus angestartet gibt 'cdrecord' zu Beginn das Folgende aus: --- Track 01: data 696 MB Total size: 800 MB (79:17.53) = 356815 sectors Lout start: 800 MB (79:19/40) = 356815 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 4 Is not unrestricted Is not erasable Disk sub type: Medium Type A, low Beta category (A-) (2) ATIP start of lead in: -12508 (97:15/17) ATIP start of lead out: 359845 (79:59/70) --- Habt ihr einen Tipp, wie ich sicherstellen kann, dass das Image -- inklusive Lead-in und Lead-out -- auf den Rohling passt? Danke, Rolf
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
Am Montag, 23. Oktober 2006 21:01 schrieb Joerg Schilling: frank paulsen [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] (Joerg Schilling) writes: J.rg Schilling ist auch nach aufforderung nicht in der lage, mails mit nach MIME-standard korrekt deklariertem zeichensatz zu versenden. Wenn Du Probleme mit einer seit .ber 16 Jahren .blichen Praxis bei der Benennung von Lokalen hast, dann kannst Du es ja mal mit einem Bug-Report an dieser Stelle versuchen: Jörg, ob dein betriebsystem nun kaputt vorkonfiguriert ist, oder nicht: die deklaration des zeichensatzes in deinem header ist einzig und allein von dir zu verantworten. Da die einzigen, die Probleme mit dem Lesen zu haben scheinen, bestimmte Linux Varianten verwenden und z.B. SuSE Linux nachweislich keine Probleme hat und die von Solaris verwendete Zeichensatzbenennung seit 16 Jahren verwendet wird, solltest Du Dir vielleicht mal Gedenken machen wie Du die Probleme mit Deinem BS behebst... Ach du dickes Ding, jetzt hast du aber eine Rakete abgeschosssen! Also wenn _das_ tatsächlich deine Einstellung ist, so lässt sie die endlose Diskussion um cdrecord usw. in einem etwas anderen Licht erscheinen. -- mfg Peter Küchler
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
* Peter Kuechler schrieb: Am Montag, 23. Oktober 2006 21:01 schrieb Joerg Schilling: frank paulsen [EMAIL PROTECTED] wrote: Jörg, ob dein betriebsystem nun kaputt vorkonfiguriert ist, oder nicht: die deklaration des zeichensatzes in deinem header ist einzig und allein von dir zu verantworten. Da die einzigen, die Probleme mit dem Lesen zu haben scheinen, bestimmte Linux Varianten verwenden und z.B. SuSE Linux nachweislich keine Probleme hat und die von Solaris verwendete Zeichensatzbenennung seit 16 Jahren verwendet wird, solltest Du Dir vielleicht mal Gedenken machen wie Du die Probleme mit Deinem BS behebst... Ach du dickes Ding, jetzt hast du aber eine Rakete abgeschosssen! Also wenn _das_ tatsächlich deine Einstellung ist, so lässt sie die endlose Diskussion um cdrecord usw. in einem etwas anderen Licht erscheinen. Volles ACK. Das ist Ignoranz, gepaart mit Sturheit, in Reinform. Wer es noch nicht mal auf die Reihe kriegt, seine Mails standardkonform zu deklarieren, sollte besser kleinere Brötchen backen. Jörg Schilling kann man jedenfalls nicht mehr ernst nehmen. Meinolf -- GPG key ID: 0x43891B76 -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Überlang e CD mit 'cdrecord'
#include hallo.h * Rolf Hermann [Tue, Oct 24 2006, 06:55:55PM]: Hi zusammen! Ich habe mir mit 'mkisofs' ein Image gemacht, dass ich gerne brennen möchte. Die Iso-Datei ist genau 730.757.120 Bytes groß. Ich frage mich allerdings, ob das auf einen 700-MB-Rohling passt -- ich Track 01: data 696 MB ^^ Willkommen bei dem grossen WirrWar um die Einheiten. Bei Rohlingen sind mit MB MebiByte gemeint (1048576 Byte), bei Festplatten Megabyte (10^6Byte). Die binären Einheiten gibt es offiziell aber erst seit 1996, davor wurde MB und Megabyte willkürlich für binäre Einheiten verwendet. Leider hat sich das MB = Megabyte = 2^10 in den Köpfen einiger Softwareentwickler festgefressen. Es würde mich nicht wundern, wenn wir auch noch in 10 Jahren neuen Programmen begegnen, bei dennen es falsch gemacht wird. Eduard. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Überlange CD mit 'cdrecord'
Rolf Hermann wrote: Habt ihr einen Tipp, wie ich sicherstellen kann, dass das Image -- inklusive Lead-in und Lead-out -- auf den Rohling passt? Micha Beyer wrote: Nein, probiere es doch aus, vergiss den Schalter --overburn nicht P.S. So schnell gehen Brenner nicht kaputt. :-) Ich habe '--overburn' weggelassen und es ging trotzdem durch. Habe zuvor testweise mal ein paar MB größeres Image mit '--dummy' gestartet und dann meinte 'cdrecord' auch netterweise, dass das nicht aufs Medium passe. Man scheint also ganz gut geschützt zu sein. Grüße, Rolf :-)
cdrecord replacement (wodim) fails
Just upgraded cdrecord and k3b to burn a Knoppix CD and find that the new replacement for cdrecord, wodim, can't handle it. It fails saying the file is larger the the CD. I have burned 6-8 of these CD's with k3b/cdrecord with never a problem, unitl wodim. I am currently downloading a jigdo stable installation disk and can only hope that I haven't just wasted my time (26K dialup) doing it. Has anyone else used wodim and got it to work? I sure hope so. Wayne -- Disclaimer: Any errors in spelling, tact, or fact are transmission errors. ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord replacement (wodim) fails
#include hallo.h * Wayne Topa [Tue, Oct 24 2006, 03:08:08PM]: Just upgraded cdrecord and k3b to burn a Knoppix CD and find that the new replacement for cdrecord, wodim, can't handle it. It fails saying the file is larger the the CD. Show your media data, wodim -atip. And the exact output when tryin to burn, doing wodim -vv imagefile. Eduard. -- Der Aberglaube an die automatische Wirkung der Einsicht kommt außerhalb der schematischen Propaganda nur noch bei alten Mathematikern vor. -- Ernst Bloch -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
On 10815 March 1977, Norbert Preining wrote: Dann frage ich mich, welchen Sinn ein aus Lizenzgründen gemachter Fork hat, wenn der split point lizenzrechtlich auf unsicherem Boden steht. Bis zum split gibt es noch die Möglichkeit der Inklusion in Debian. Danach mit der neuen Lizenz nicht mehr. Es gab die Möglichkeit solange es keine Lizenzprobleme gab. Nach a08 wurde CDDL eingeführt, und ungeachtet ob das eine freie Lizenz ist oder nicht ist sie inkompatibel mit GPL. Seitdem cdrtools nun halt parts hat wo beide kombiniert sind gibt es keine Möglichkleit für irgendeine Distribution die legal zu verteilen, sofern man auch nur halbwegs Interesse an Legalität hat. Ja ich weiss dass Joerg behauptet wir hätten nie gesagt wo wir Probleme mit dieser Kombination haben. Dies ist ne glatte Falschaussage, das haben wir bereits des öfteren getan, jeder der dem nur halbwegs folgt (oder nun google bemüht) kann dies herausfinden. Ich weiss auch dass Joerg nicht müde wird zu behaupten CDDL wäre nach OSI und nach DFSG frei. Ich verstehe nur nicht wo das irgendwie auch nur im entferntesten relevant wäre, wir haben nie behauptet dass CDDL an sich unfrei ist. Oder frei. Oder sonstwas. Das wurde von uns so nie bewertet, wir haben nur die Kombination aus CDDL und GPL bewertet. -- bye Joerg Aquariophile geht nur in IE Aquariophile unter win Aquariophile autsch ich glaub das war ein eigentor -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
frank paulsen [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] (Joerg Schilling) writes: J.rg Schilling ist auch nach aufforderung nicht in der lage, mails mit nach MIME-standard korrekt deklariertem zeichensatz zu versenden. Wenn Du Probleme mit einer seit .ber 16 Jahren .blichen Praxis bei der Benennung von Lokalen hast, dann kannst Du es ja mal mit einem Bug-Report an dieser Stelle versuchen: Jörg, ob dein betriebsystem nun kaputt vorkonfiguriert ist, oder nicht: die deklaration des zeichensatzes in deinem header ist einzig und allein von dir zu verantworten. Da die einzigen, die Probleme mit dem Lesen zu haben scheinen, bestimmte Linux Varianten verwenden und z.B. SuSE Linux nachweislich keine Probleme hat und die von Solaris verwendete Zeichensatzbenennung seit 16 Jahren verwendet wird, solltest Du Dir vielleicht mal Gedenken machen wie Du die Probleme mit Deinem BS behebst... Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
On Sat, Oct 21, 2006 at 08:49:23PM +0200, Joerg Schilling wrote: So und nun ein paar Erläuterungen dazu warum daß, was die Leute um Herrn Bloch mit den cdrtools tun, eine pure Schädigung des Projektes zum Ziel hat und kein Fork ist. Einen Fork macht man nach dem man vergeblich versucht hat Erweiterungen zum Projekt beim Autor anzubringen. Wenn man einen Fork beginnt, dann benennt man zunächst alle Kompilations-Ergebnisse des Originalprogramms um, um Probleme zu vermeiden und Klarheit zu schaffen. Danach beginnt man damit Erweiterungen einzubauen. Keines dieser drei Kriterien trifft auf den Speudofork zu... Das waren nur zwei... Was beweist, das du nicht nur Probleme mit dem Verstaendnis von Lizenzen hast. cu ulf -- Ulf Volmer [EMAIL PROTECTED] www.u-v.de -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
Moin, wieso lasst ihr Jörg nicht einfach Jörg sein und hört euch auf provozieren zu lassen. Fakt ist einfach, dass die Lizenz von cdrecord nicht DFSG¹-frei ist und somit nicht nach Debian kommt. Begründungen fielen schon zahlreiche und die möchte ich hier nicht nochmals aufzählen. Es ist nur gut von mir gemeint, sonst schießt ihr euch noch in den Weltraum und habt immernoch nichts davon. @Jörg bitte sei so nett und antworte doch mal im Thread, es ist extrem schwer nachzuvollziehen, zu welchem Teil eines Threads deine Mail gehört. In der ganzen Diskussion habe ich übrigens nahezu keine Entwicklung gesehen, eventuell sollte man sich einmal vernünftiger damit auseinandersetzen. cheers Pierre ¹ Debian Richtlinien für freie Software, sind anders als die Richtlinien vom FSF
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
On 22.10.06 10:01:18, Pierre Gillmann wrote: Es ist nur gut von mir gemeint, sonst schießt ihr euch noch in den Weltraum und habt immernoch nichts davon. Noe ich mich bestimmt nicht, dafuer ists hier viel zu schoen ;) Joerg vllt. irgendwann In der ganzen Diskussion habe ich übrigens nahezu keine Entwicklung gesehen, eventuell sollte man sich einmal vernünftiger damit auseinandersetzen. Also ich hab nicht alle verlinkten Threads auf debian-devel oder in irgendwelchen Bugreports gelesen aber die 2-3 rein sachlichen Mails von Eduard sehe ich schon als Fortschritt an, leider kam auf diese von Joerg noch keine Antwort, die evtl. helfen wuerde cdrecord wieder in Debian zu integrieren. Andreas -- Your love life will be... interesting. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Erleuchtet mich zu wodim oder wer hat cdrecord geklaut?
alle Kompilations-Ergebnisse des Originalprogramms um, um Probleme zu vermeiden und Klarheit zu schaffen. Danach beginnt man damit Erweiterungen einzubauen. Wenn das nicht geschehen wäre, warum gibt es auf meinem System zwar /usr/bin/wodim (was ja dann garnicht existieren dürfte) und kein cdrecord? Wenn es bei Dir kein cdrecord gibt, dann liegt es wohl daran, daß Du kein Interesse an funktionierenden Programmen hast und/oder zu faul bist die offiziellen Programme durch Eingabe von make zu kompilieren. Wie ist es mit readcd, cdda2wav, mkisofs isoinfo, isodebug, ? Keines dieser drei Kriterien trifft auf den Speudofork zu... Auf einen Pseudofork nicht, auf cdrkit schon. cdrkit _ist_ ein Speudofork weil nicht umbenannt wird und weil keine neuen Features hinzugefügt wurden. Das Einzige was sich an dem Speudofork seit der lautstarken Ankündigung getan hat ist Selbstbeschäftigung mit Problemen die man durch das Wegwerfen eines funktionierenden Build-Systems selbst unnötigerweise verursacht hat. Ich habe zwar das alte System nicht gekannt, und auch keine Ahnung welches jetzt verwendet wird, aber die Tatsache das ich ein Binary hier liegen habe, bedeutet zumindest mal, das es funktionieren muss. Jetzt wird selbstverständlich auch noch mein buildsystem benutzt, aber bei dem Speudofork wird etwas verwendet, von dem man nicht weis ob überhaupt die Kompilation unter Linux/x86 korrekt funktioniert, geschweige denn auf den 30 anderen Platformen. Einen vorangehenden Versuch zur Zusammenarbeit durch Herrn Bloch hat es auch nicht gegeben. Bis jetzt kamen in diesem Thread hier einige URLs die aber genau den gegenteiligen Anschein erwecken. Gibt es auch etwas, das diese Aussage untermauert? ??? Bislang kamen von Herrn Bloch Ablenkungsmanöver davon, daß _er_ unwillig zu einer Zusammenarbeit ist. Ein gutes Beispiel ist sein versuchter Seitenhieb mit AIX: Er behauptet, daß cdrtools auf AIX5 nicht kompilieren würden, liefert aber keinerlei Informationen die seine Behauptung belegen und weigert sich die Informationen zu liefern, die benötigt würden um das Problem zu untersuchen. So, ich warte immer noch darauf, daß man sämliche Programme aus den cdrtools umbenannt falls sie nicht sämtliche dokumentierten Eigenschaften einer aktuellen Originalversion haben, oder falls bei ihnen noch Bugs vorhanden sind die im Original nicht mehr zu finden sind. Und natürlich kannst du auch benennen welche das sein sollen. Nur um Sicher zu gehen, das alle beteiligten darunter auch das selbe verstehen. ??? Hast Du wirklich noch immer nicht verstanden _was_ alles in den cdrtools ist? Wenn Du hier mitdiskutieren willst, wäre es doch schön wenn Du Dich mal zum Thema informieren würdest. Das trifft zur Zeit auf _alle_ Programme aus den cdrtools zu, die durch Debian unter dem Namen cdrkit verbreitet werden. Also bist du der Urentwickler von wodim? Wes soll dieser Unsinn? Zum Abschluß noch eine Bemerkung zu den kürzlichen Äußerungen Herrn Bloch's: Er hat es vorgezogen mich von der Adressatenliste zu streichen weil er sich wohl selbst über den geringen Wahrheitsgehalt seiner Ausführungen bewußt ist. Als Beweis eine kurze Erläuterung: Wenn man nur die SCCS-id des aktuellen Originals übernimmt, dann aber den Code wieder ausbaut, der den Workaround für aktuelle Linux Versionen enthält, dann ist es ehrlicher zuzuzgeben, daß man eine 2 Jahre alte Version verwendet. Naja, wenn man sich nicht auf einer Mailingliste anmeldet (oder auch wieder abmeldet) sollte man sich nicht wundern, wenn man keine Mails dieser Liste bekommt. Zu Sicherheit kann man aber ein CC anfordern. Der Güte halber geht diese Antwort aber auch per CC raus. Für mich brauchst du aber keine CCs zu setzen, ich bin subscribed. Deine SCSI ausführungen kann ich nicht nachvollziehen, da ich keine solchen Geräte in Betrieb habe. Vielleicht solltest Du Dir mal die Hintergründe ansehen.. Ich bin nicht auf der Liste. Ich suche allerdings im Netz nach Falschdarstellungen und versuchte diese punktuell zu korrigieren wo es am schlimmsten ist. Vielleicht nocheinmal eine Kurzzusammenfaßung: - Herrn Bloch fehlen wichtige Grundkenntnisse und er weigert sich diese zu erlangen - Herr Bloch ist unwillig zu einer Zusammenarbeit - Herr Bloch geht von der irrigen Annahme aus, eine _SW-Lizenz_ könnte ihm jede beliebige Freiheit geben was ein Irrglaube ist, denn die SW-Lizenz ist immer im Zuzsammenhang mit dem Urheberrecht und anderen Rechten zu sehen die durch die SW-Lizenz nicht aufgehoben werden. Die Randbedingungen dazu habe ich Herrn Bloch lang und breit erklärt; ich habe ihm auch erklärt warum Dinge, die er z.B. als unzulässige Einschränkungen z.B. der GPL betrachtet, stattdessen vom Urheberrecht und von den betreffenden Lizenzen so gefordert werden. Jörg
