* Donald Henson [12-27-03 08:24]:

On Fri, 2003-12-26 at 18:18, Sid Boyce wrote:

...

James Mohr wrote: [snip ...] I experienced some problems with k3b, so I switched to xcdroast on 9.0, using a MSI DVD-R/CDRW - no probs.

Apparently, SuSE 9.0 shipped with a defective version of K3B. I upgraded K3B and it now works. Yu might want to try that before taking more extreme measures.

Please, Gentlemen, trim your quotes. It is not necessary to quote and requote 12k of log output and the sigs and auto generated trailers for list posts for 2 or 3 line replies. Thankyou for your consideration. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org

* Sid Boyce [12-27-03 09:06]: [snip ...]

I agree, it's a nonsense that seem to have built up on this group. I once was admonished for making my responses at the beginning rather than here at the end, which means scrolling down past the cruft you've already read to get to what you want to see, trimming quotes makes sense, but I guess you'll get contrary opinions.

Thanks again. IIANM, the standard is to only quote that which is necessary to maintain the context of your answers. Answering at the top of a post incourages _no_ trimming. Answering at the point of question or after the entire question encourages and maintains the flow if information and understanding and allows researchers (those who would search the archives before posing a question to the list) a better opportunity to solve their own particular situation with a minimized effort. Contrary _opinions_ build understanding and a better social system <grin>. gud luk, -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org

Donald Henson wrote:

On Sat, 2003-12-27 at 07:16, Patrick Shanahan wrote:

...

* Sid Boyce [12-27-03 09:06]: [snip ...]

Didn't you guys just hijack this thread? I only mention it because I've seen lots of other people get jumped on for doing that.

Yep, sorry - hit send before prefixing OT:. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.

On Monday 29 December 2003 14:14, Örn Hansen wrote:

To the original problem, I've had problems with AOpen on a Dell... according to what I've been able to research, it may be related to DMA and/or cable setup (that is, set as slave/cs when as master or reverse). Don't know if that helps, but its worth a try.

mvh, Örn

I was hoping for a software solution (i.e. a setting somewhere). However, since all of the software solutions I have tried have not solved the problem it does look more like it is a hardware problem. Either the cabling or settings are wrong as you suggest or maybe the drive has gone bad, as Lee suggested. Since this was working before, I am guessing that the drive has gone bad. This is a new machine, so if the drive is bad I will hopefully get a new one. We'll see. Thanks to everyone for their help so far. Regards, jimmo -- --------------------------------------- "Be more concerned with your character than with your reputation. Your character is what you really are while your reputation is merely what others think you are." -- John Wooden --------------------------------------- The Linux Tutorial needs your help! Visit us at http://www.linux-tutorial.info

Donald Henson wrote:

On Fri, 2003-12-26 at 18:18, Sid Boyce wrote:

...

James Mohr wrote:

...

Hi All!

I am using the default version of k3b which came with Suse 9.0 (0.10). I have tried writing as both root and my normal user, with various speeds, but it always dies at about 8%. Someone posted a bug reported on kde.org with basically the same problem although they say that they cannot write at all. This was reported about a month ago and it is still listed as "unconfirmed".

I am using an AOPEN CD-RW CRW5224 and thing most annoying thing is that it did work once. Obviously something happened, but I cannot figure out what it was. Any help would be greatly appreaciated.

Regards,

jimmo

the error was: _______________________________________ ... Cdrecord returned an unknown error! (code 254) Unkown Error 254 Please send me an email with the last output.

System ----------------------- K3b Version: 0.10 KDE Version: 3.1.4 QT Version: 3.2.1

cdrecord ----------------------- scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 Linux sg driver version: 3.1.25 /usr/bin/cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de-scsi-linux-sg.c-1.75-resmgr-patch '@(#)scsi-linux-sg.c 1.75 02/10/21 Copyright 1997 J. Schilling'). SCSI buffer size: 64512 Cdrecord-Clone 2.01a18-dvd (i686-suse-linux) Copyright (C) 1995-2003 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to . Note: The author of cdrecord is not to be bothered with problems in this version. TOC Type: 1 = CD-ROM Using libscg version 'schily-0.7' atapi: 1 Device type : Removable CD-ROM Version : 0 Response Format: 1 Vendor_info : 'AOPEN ' Identifikation : 'CD-RW CRW5224 ' Revision : '1.05' Device seems to be: Generic mmc CD-RW. Current: 0x0009 Profile: 0x0008 Profile: 0x0009 (current) Profile: 0x000A Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE FORCESPEED Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R96R Drive buf size : 1359872 = 1328 KB FIFO size : 4194304 = 4096 KB Track 01: data 625 MB Total size: 717 MB (71:07.80) = 320085 sectors Lout start: 718 MB (71:09/60) = 320085 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 5 Is not unrestricted Is not erasable Disk sub type: Medium Type B, low Beta category (B-) (4) ATIP start of lead in: -11933 (97:22/67) ATIP start of lead out: 359849 (79:59/74) Disk type: Short strategy type (Phthalocyanine or similar) Manuf. index: 43 Manufacturer: Acer Media Technology, Inc. Blocks total: 359849 Blocks current: 359849 Blocks remaining: 39764 Forcespeed is OFF. Starting to write CD/DVD at speed 1 in real SAO mode for single session. Last chance to quit, starting real write in 2 seconds. 1 seconds. 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. trackno=0 BURN-Free is OFF. Performing OPC... Sending CUE sheet... Writing pregap for track 1 at -150 Starting new track at sector: 0 Track 01: 0 of 625 MB written. Track 01: 1 of 625 MB written (fifo 100%) [buf 40%] 0.9x. Track 01: 2 of 625 MB written (fifo 87%) [buf 33%] 12.9x. Track 01: 3 of 625 MB written (fifo 98%) [buf 38%] 25.6x. Track 01: 4 of 625 MB written (fifo 100%) [buf 43%] 24.9x. Track 01: 5 of 625 MB written (fifo 98%) [buf 48%] 25.6x. Track 01: 6 of 625 MB written (fifo 100%) [buf 52%] 24.5x. Track 01: 7 of 625 MB written (fifo 96%) [buf 56%] 25.7x. Track 01: 8 of 625 MB written (fifo 96%) [buf 62%] 25.1x. Track 01: 9 of 625 MB written (fifo 98%) [buf 67%] 25.9x. Track 01: 10 of 625 MB written (fifo 96%) [buf 72%] 25.1x. Track 01: 11 of 625 MB written (fifo 98%) [buf 59%] 20.8x. Track 01: 12 of 625 MB written (fifo 98%) [buf 63%] 25.0x. Track 01: 13 of 625 MB written (fifo 98%) [buf 67%] 25.8x. Track 01: 14 of 625 MB written (fifo 100%) [buf 71%] 25.0x. Track 01: 15 of 625 MB written (fifo 98%) [buf 75%] 25.6x. Track 01: 16 of 625 MB written (fifo 98%) [buf 78%] 25.0x. Track 01: 17 of 625 MB written (fifo 100%) [buf 82%] 25.8x. Track 01: 18 of 625 MB written (fifo 100%) [buf 85%] 24.9x. Track 01: 19 of 625 MB written (fifo 96%) [buf 88%] 25.6x. Track 01: 20 of 625 MB written (fifo 98%) [buf 87%] 24.8x. Track 01: 21 of 625 MB written (fifo 98%) [buf 77%] 20.9x. Track 01: 22 of 625 MB written (fifo 98%) [buf 79%] 24.8x. Track 01: 23 of 625 MB written (fifo 96%) [buf 81%] 25.6x. Track 01: 24 of 625 MB written (fifo 100%) [buf 82%] 24.5x. Track 01: 25 of 625 MB written (fifo 95%) [buf 84%] 25.6x. Track 01: 26 of 625 MB written (fifo 100%) [buf 86%] 24.7x. Track 01: 27 of 625 MB written (fifo 98%) [buf 87%] 25.4x. Track 01: 28 of 625 MB written (fifo 98%) [buf 88%] 24.6x. Track 01: 29 of 625 MB written (fifo 98%) [buf 89%] 25.5x. Track 01: 30 of 625 MB written (fifo 98%) [buf 72%] 21.2x. Track 01: 31 of 625 MB written (fifo 100%) [buf 73%] 24.0x. Track 01: 32 of 625 MB written (fifo 100%) [buf 73%] 24.6x. Track 01: 33 of 625 MB written (fifo 98%) [buf 72%] 25.1x. Track 01: 34 of 625 MB written (fifo 100%) [buf 72%] 26.1x. Track 01: 35 of 625 MB written (fifo 100%) [buf 72%] 25.2x. Track 01: 36 of 625 MB written (fifo 96%) [buf 71%] 26.0x. Track 01: 37 of 625 MB written (fifo 96%) [buf 70%] 25.1x. Track 01: 38 of 625 MB written (fifo 98%) [buf 69%] 25.9x. Track 01: 39 of 625 MB written (fifo 100%) [buf 68%] 25.2x. Track 01: 40 of 625 MB written (fifo 93%) [buf 48%] 21.0x. Track 01: 41 of 625 MB written (fifo 98%) [buf 47%] 25.1x. Track 01: 42 of 625 MB written (fifo 98%) [buf 44%] 25.5x. Track 01: 43 of 625 MB written (fifo 96%) [buf 42%] 25.1x. Track 01: 44 of 625 MB written (fifo 98%) [buf 39%] 25.7x. Track 01: 45 of 625 MB written (fifo 98%) [buf 37%] 25.0x. Track 01: 46 of 625 MB written (fifo 95%) [buf 34%] 25.8x. Track 01: 47 of 625 MB written (fifo 100%) [buf 32%] 25.0x. Track 01: 48 of 625 MB written (fifo 98%) [buf 29%] 25.7x. Track 01: 49 of 625 MB written (fifo 100%) [buf 19%] 23.3x. Track 01: 50 of 625 MB written (fifo 96%) [buf 2%] 21.8x. /usr/bin/cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 00 64 DF 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 06 00 00 00 00 0C 00 00 00 00 29 00 00 00 Sense Key: 0x6 Unit Attention, Segment 0 Sense Code: 0x29 Qual 0x00 (power on, reset, or bus device reset occurred) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 39.887s timeout 200s /usr/bin/cdrecord: A write error occured. /usr/bin/cdrecord: Please properly read the error message above. write track data: error after 52885504 bytes Writing time: 80.158s Average write speed 59.2x. Min drive buffer fill was 2% Total of 1 possible drive buffer underruns predicted. Fixating... Fixating time: 0.003s /usr/bin/cdrecord: fifo had 897 puts and 834 gets. /usr/bin/cdrecord: fifo was 0 times empty and 257 times full, min fill was 84%.

cdrecord comand: ----------------------- /usr/bin/cdrecord -v gracetime=2 dev=0,0,0 speed=1 -dao -eject -data -tsize=320085s -

mkisofs ----------------------- 320085 0.16% done, estimate finish Fri Dec 26 21:31:06 2003 0.31% done, estimate finish Fri Dec 26 21:31:06 2003 0.47% done, estimate finish Fri Dec 26 21:31:06 2003 0.63% done, estimate finish Fri Dec 26 21:31:06 2003 0.78% done, estimate finish Fri Dec 26 22:17:53 2003 0.94% done, estimate finish Fri Dec 26 22:13:43 2003 1.10% done, estimate finish Fri Dec 26 22:07:33 2003 1.25% done, estimate finish Fri Dec 26 22:03:03 2003 1.41% done, estimate finish Fri Dec 26 21:59:31 2003 1.57% done, estimate finish Fri Dec 26 21:57:41 2003 1.72% done, estimate finish Fri Dec 26 21:55:18 2003 1.88% done, estimate finish Fri Dec 26 21:53:18 2003 2.03% done, estimate finish Fri Dec 26 21:52:25 2003 2.19% done, estimate finish Fri Dec 26 21:50:52 2003 2.34% done, estimate finish Fri Dec 26 21:49:35 2003 2.50% done, estimate finish Fri Dec 26 21:48:24 2003 2.66% done, estimate finish Fri Dec 26 21:48:01 2003 2.81% done, estimate finish Fri Dec 26 21:47:05 2003 2.97% done, estimate finish Fri Dec 26 21:46:15 2003 3.13% done, estimate finish Fri Dec 26 21:46:00 2003 3.28% done, estimate finish Fri Dec 26 21:45:18 2003 3.44% done, estimate finish Fri Dec 26 21:44:40 2003 3.59% done, estimate finish Fri Dec 26 21:44:04 2003 3.75% done, estimate finish Fri Dec 26 21:43:59 2003 3.91% done, estimate finish Fri Dec 26 21:43:27 2003 4.06% done, estimate finish Fri Dec 26 21:42:59 2003 4.22% done, estimate finish Fri Dec 26 21:42:33 2003 4.37% done, estimate finish Fri Dec 26 21:42:31 2003 4.53% done, estimate finish Fri Dec 26 21:42:07 2003 4.69% done, estimate finish Fri Dec 26 21:41:45 2003 4.85% done, estimate finish Fri Dec 26 21:41:45 2003 5.00% done, estimate finish Fri Dec 26 21:41:25 2003 5.16% done, estimate finish Fri Dec 26 21:41:07 2003 5.32% done, estimate finish Fri Dec 26 21:40:49 2003 5.47% done, estimate finish Fri Dec 26 21:40:50 2003 5.63% done, estimate finish Fri Dec 26 21:40:34 2003 5.78% done, estimate finish Fri Dec 26 21:40:19 2003 5.94% done, estimate finish Fri Dec 26 21:40:21 2003 6.09% done, estimate finish Fri Dec 26 21:40:07 2003 6.25% done, estimate finish Fri Dec 26 21:39:54 2003 6.41% done, estimate finish Fri Dec 26 21:39:40 2003 6.56% done, estimate finish Fri Dec 26 21:39:43 2003 6.72% done, estimate finish Fri Dec 26 21:39:32 2003 6.87% done, estimate finish Fri Dec 26 21:39:20 2003 7.03% done, estimate finish Fri Dec 26 21:39:23 2003 7.19% done, estimate finish Fri Dec 26 21:39:12 2003 7.34% done, estimate finish Fri Dec 26 21:39:02 2003 7.50% done, estimate finish Fri Dec 26 21:38:52 2003 7.66% done, estimate finish Fri Dec 26 21:38:56 2003 7.81% done, estimate finish Fri Dec 26 21:38:46 2003 7.97% done, estimate finish Fri Dec 26 21:38:37 2003 8.13% done, estimate finish Fri Dec 26 21:38:28 2003 8.28% done, estimate finish Fri Dec 26 21:38:32 2003 8.44% done, estimate finish Fri Dec 26 21:38:24 2003 8.59% done, estimate finish Fri Dec 26 21:38:16 2003

mkisofs comand: ----------------------- /usr/bin/mkisofs -gui -graft-points -V Young Net B1 -volset -A K3B THE CD KREATOR VERSION 0.10 (C) 2003 SEBASTIAN TRUEG AND THE K3B TEAM -P -p K3b - Version 0.10 -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-root/ k3bhMe6Ra.tmp -r -hide-list /tmp/kde-root/k3bzuoZob.tmp -l -iso-level 2 -path-list /tmp/kde-root/k3bJSnrUb.tmp

I experienced some problems with k3b, so I switched to xcdroast on 9.0, using a MSI DVD-R/CDRW - no probs. Regards Sid.

Apparently, SuSE 9.0 shipped with a defective version of K3B. I upgraded K3B and it now works. Yu might want to try that before taking more extreme measures.

Don Henson

I got a version of K3B from RPMseek.com, and it fixed all my troubles with the version shipped with 9.0 Here is a link: http://rpmseek.com/rpm/k3b-0.9.cvs20030901-59.i586.html?hl=com&cs=k3b:PN:0:0:1:0:968866 Cheers

Op zondag 28 december 2003 15:22, schreef James Mohr:

k3b-0.9 seems to be more or less the same version that was provided by default in SuSE 9.0. However, I downloaded it and I am still having the same problems. I also downloaded the both the k3b-0.10.2-suse82.i386.rpm and k3b-0.10.3 source code. Both of them have the exact same  problem.

Did you try the k3b version from the packman side? The available version is: k3b;0.10.3-0.pm.1;i586;packman -- Richard Bos Without a home the journey is endless

James Mohr wrote:

Any ideas on what I can/should do to return the system (i.e. the CD writer components, devices, etc-) to a fresh state without re-installing. This isn't Windows, ya know. ;-)

I had problems with kb3 in SuSE 9.0, and I ended up removing anything connected with burning (k3b - xcdroast - cdrecord - mkisofs ...) and reinstalling the latest versions with apt-get (Packman would do too, I guess). The usual advice would also be to make an image with mkisofs and burn it from the command line to check where the problem lies. I found multiple references to error 254 in cdrecord on a french list, it concerned backupedge, and this was the advice, roughly inserting immed after cdrecord. http://www.microlite.com/support/edgefax66.ts.html ) : Upgrade to BackupEDGE 01.02.04 or later. Then edit the file /usr/lib/edge/config/devices.def. Find the write commands that refer cdrecord. Insert the flag "-immed" in the as illustrated in the example below. The write command may look like: WRITE_CMD [3] p/cdrecord dev=0,4,0 B speed=s - Change it to : WRITE_CMD [3] p/cdrecord dev=0,4,0 -immed B speed=s - Save the change. This has been found to remedy this issue cdrecord immed on trouve ( http://dchlb.de/cdrecord/man_cdrecord.html ) : -immed Tell cdrecord to set the SCSI IMMED flag in certain commands (load/eject/blank/close_track/close_session). This can be useful on broken systems with ATAPI harddisk and CD/DVD writer on the same bus or with SCSI systems that don't use disconnect/reconnect. These systems will freeze while blanking or fixating a CD/DVD or while a DVD writer is filling up a session to the minimum amount (approx. 800 MB). Setting the -immed flag will request the command to return immediately while the operation proceeds in background, making the bus usable for the other devices and avoiding the system freeze. This is an experimental feature which may work or not, depending on the model of the CD/DVD writer. A correct solution would be to set up a correct cabling but there seem to be notebooks around that have been set up the wrong way by the manufacturer. As it is impossible to fix this problem in notebooks, the -immed option has been added. A second experimental feature of the -immed flag is to tell cdrecord to try to wait short times wile writing to the media. This is expected to free the IDE bus if the CD/DVD writer and the data source are connected to the same IDE cable. In this case, the CD/DVD writer would otherwise usually block the IDE bus for nearly all the time making it impossible to fetch data from the source drive. See also minbuf= and -v option. Use both features at your own risk. If it turns out that it would make sense to have a separate option for the the wait feature, write to the author and convince him. fx -- ______________________ Courtesy of SuSE Linux http://www.nibz.org

On Saturday 27 December 2003 02:18, Sid Boyce wrote:

I experienced some problems with k3b, so I switched to xcdroast on 9.0, using a MSI DVD-R/CDRW - no probs. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.

Thanks but no cigar. xcdroast-0.98alpha14-44 dies as well with the output below. One thing that annoys me is that it says "Average write speed 55.1x." Each time I try to write I get a different value, but most importantly I set the cd write speed to write with 1x. So why is it trying to write faster??? I also changed the size of the CD writer fifo to 16MB. This got me to about 80% of a 600MB image before it died. Regards, jimmo Writing pregap for track 1 at -150 Starting new track at sector: 0 cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 01 31 A4 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 71 00 03 00 00 00 00 0C 00 00 00 00 0C 00 00 00 Sense Key: 0x3 Medium Error, deferred error, Segment 0 Sense Code: 0x0C Qual 0x00 (write error) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 9.661s timeout 200s cdrecord: A write error occured. cdrecord: Please properly read the error message above. write track data: error after 160243712 bytes Writing time: 88.295s Average write speed 55.1x. Min drive buffer fill was 4% Total of 6 possible drive buffer underruns predicted. Fixating... Fixating time: 0.002s BURN-Free was 18 times used. cdrecord: fifo had 2588 puts and 2525 gets. cdrecord: fifo was 0 times empty and 1237 times full, min fill was 93%. -- --------------------------------------- "Be more concerned with your character than with your reputation. Your character is what you really are while your reputation is merely what others think you are." -- John Wooden --------------------------------------- The Linux Tutorial needs your help! Visit us at http://www.linux-tutorial.info

On Sunday 28 December 2003 10:47 am, James Mohr wrote:

On Saturday 27 December 2003 02:18, Sid Boyce wrote:

...

I experienced some problems with k3b, so I switched to xcdroast on 9.0, using a MSI DVD-R/CDRW - no probs. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.

Thanks but no cigar. xcdroast-0.98alpha14-44 dies as well with the output below. One thing that annoys me is that it says "Average write speed 55.1x." Each time I try to write I get a different value, but most importantly I set the cd write speed to write with 1x. So why is it trying to write faster???

I also changed the size of the CD writer fifo to 16MB. This got me to about 80% of a 600MB image before it died.

Regards,

jimmo ================

Have you even considered that the drive could have gone bad? If all those programs produce the same result or worse, it seems to me you are looking in the wrong place for your problem! Check the drive on another system or try another drive on your system. Check your cable on your drive. Look at the buffer fill you mentioned, 4%? and the 6 buffer underruns? Unless you are trying to compile or some other cpu/drive intensive operation while trying to write, those aren't good. You are not trying to copy from CD to CDRW are you? Not a good idea on an IDE chain. Lee -- --- KMail v1.5.4 --- SuSE Linux Pro v9.0 --- Registered Linux User #225206 On any other day, that might seem strange...

Carl William Spitzer IV wrote:

If your using the k3b out of the box remove it and use the one from k3b.org There have been past reports that the one with 9.0 is busted. k3b.org maintains versions for several distros.

CWSIV

I did that, but still have a problem on 9.0, I reckon it may be to do with the 2.6 kernel (2.6.1-rc1-mm1). There was quite a bit of controversy between folk in the kernel mailing list regarding cdrecord and its use of ide-scsi which Linus and others think is an evil hotchpotch that has to be got rid of as the IDE driver supports CD burinig to IDE devices. xcdroast works equally well, so I'm happy using it. Thanks & Regards Sid.

On Tue, 30 Dec 2003 23:28:21 +0100 Richard Bos writes:

...

Op maandag 29 december 2003 14:14, schreef =D6rn Hansen:

...

On Saturday 27 December 2003 15:16, Patrick Shanahan wrote:

...

* Sid Boyce [12-27-03 09:06]: [snip ...]

[snop...]

...

Mandrake has the same problem: http://bugs.kde.org/show_bug.cgi?id=3D71521

________________________________________________________________ The best thing to hit the internet in years - Juno SpeedBand! Surf the web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to sign up today!

-- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.