Re: [newbie] Burning frustration
If turning DMA on works, and you are satisfied --- use it! T :-) - Original Message - From: gikoreno To: [EMAIL PROTECTED] ; [EMAIL PROTECTED] Sent: Wednesday, November 06, 2002 12:12 AM Subject: Re: [newbie] Burning frustration Hey John,sorry to have taken so long to reply.I tried taking away the none in the fstab, but it didn't work. I think that's the way it is supposed to be on Mandrake 9.0.It turned out the reason why it wasn't burning at a decent speed was DMA related. I turned DMA on as per the other posts and it worked.Knowing how people warn on the reliability of CD-ROMS when coupled with DMA, I am not convinced it's the best idea (will corruption follow?), but the performance of the system definitely went tremendously up.So I guess I'll figure it out soon.Thanks!gikoreno Join Excite! - http://www.excite.comThe most personalized portal on the Web!
Re: [newbie] Burning frustration
Technoslick wrote: If turning DMA on works, and you are satisfied --- use it! T :-) - Original Message - *From:* gikoreno mailto:gikoreno;excite.com *To:* [EMAIL PROTECTED] mailto:BAGSOFCHOICE;oldtolley.fsnet.co.uk ; [EMAIL PROTECTED] mailto:newbie;linux-mandrake.com *Sent:* Wednesday, November 06, 2002 12:12 AM *Subject:* Re: [newbie] Burning frustration Hey John, It turned out the reason why it wasn't burning at a decent speed was DMA related. I turned DMA on as per the other posts and it worked. Knowing how people warn on the reliability of CD-ROMS when coupled with DMA, I am not convinced it's the best idea (will corruption follow?), but the performance of the system definitely went tremendously up. So I guess I'll figure it out soon. Thanks! gikoreno As a matter of interest, when it goes wrong using DMA, what is the result, I mean , is it just data loss or something, or is there permanent hardware breakage. John -- John Richard Smith [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] Burning frustration
No breakage. What I have noticed is that a CD-ROM drive becomes unreliable in reading. It works sometimes, other times not. Can't tell that the contents of the drive has changed. Or stops working. With storage mediums that you write to, like hard drives, it will begin to scramble it, until you are not able to use it. I have not seen any drives actually harmed. I ended up having to start over again in loading Windows. I tend to forget as much as I remember anymore, so when Tom Brinkman mentioned the problem was actually stemming from the motherboard's chipset, I remembered reading about that a long time ago. If you are using an older motherboard, especially one that happens to be a cheap brand, there is a chance that applying DMA witll cause a Read-Only device to not work properly or a hard drive to scramble its data. You need to keep in mind that I still use a lot of old equipment and therefore am more sensitive to these issues than those who are working with equipment less than a few years old. I am using EPOX, MicroStar and some VxPro boards, that have not been avaiable for years. The same goes for my peripheral cards and stuff. I have too many computers, and not the wallet to justfy replacing everything I own every few years to keep up with the Jones'. I agree with what has been said by many here that there shouldn't be any problems with today's equipment using DMA. My question is...How many users throughout the world are trying to use Mandrake Linux on an older box that may have problems activating DMA? I'll take some heat and good-natured debate over this if someone takes my advice and backs up their data first before taking the plunge on old equipment, knowing that it could be a problem. :-) T - Original Message - From: John Richard Smith [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, November 06, 2002 7:44 AM Subject: Re: [newbie] Burning frustration Technoslick wrote: If turning DMA on works, and you are satisfied --- use it! T :-) - Original Message - *From:* gikoreno mailto:gikoreno;excite.com *To:* [EMAIL PROTECTED] mailto:BAGSOFCHOICE;oldtolley.fsnet.co.uk ; [EMAIL PROTECTED] mailto:newbie;linux-mandrake.com *Sent:* Wednesday, November 06, 2002 12:12 AM *Subject:* Re: [newbie] Burning frustration Hey John, It turned out the reason why it wasn't burning at a decent speed was DMA related. I turned DMA on as per the other posts and it worked. Knowing how people warn on the reliability of CD-ROMS when coupled with DMA, I am not convinced it's the best idea (will corruption follow?), but the performance of the system definitely went tremendously up. So I guess I'll figure it out soon. Thanks! gikoreno As a matter of interest, when it goes wrong using DMA, what is the result, I mean , is it just data loss or something, or is there permanent hardware breakage. John -- John Richard Smith [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] Burning frustration
Technoslick wrote: No breakage. What I have noticed is that a CD-ROM drive becomes unreliable in reading. It works sometimes, other times not. Can't tell that the contents of the drive has changed. Or stops working. With storage mediums that you write to, like hard drives, it will begin to scramble it, until you are not able to use it. I have not seen any drives actually harmed. I ended up having to start over again in loading Windows. I tend to forget as much as I remember anymore, so when Tom Brinkman mentioned the problem was actually stemming from the motherboard's chipset, I remembered reading about that a long time ago. If you are using an older motherboard, especially one that happens to be a cheap brand, there is a chance that applying DMA witll cause a Read-Only device to not work properly or a hard drive to scramble its data. You need to keep in mind that I still use a lot of old equipment and therefore am more sensitive to these issues than those who are working with equipment less than a few years old. I am using EPOX, MicroStar and some VxPro boards, that have not been avaiable for years. The same goes for my peripheral cards and stuff. I have too many computers, and not the wallet to justfy replacing everything I own every few years to keep up with the Jones'. I agree with what has been said by many here that there shouldn't be any problems with today's equipment using DMA. My question is...How many users throughout the world are trying to use Mandrake Linux on an older box that may have problems activating DMA? I'll take some heat and good-natured debate over this if someone takes my advice and backs up their data first before taking the plunge on old equipment, knowing that it could be a problem. :-) Technoslick wrote: Well I guess you have a point because my msi mobo comes with a bios setting by default is DMA disabled. I don't suppose they do that for nothing. So I for one will keep the substance of this discussion stowed away at the back of my mind. Just in case. John -- John Richard Smith [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] Burning frustration
On Wednesday November 6 2002 08:04 am, John Richard Smith wrote: Technoslick wrote: I tend to forget as much as I remember anymore, so when Tom Brinkman mentioned the problem was actually stemming from the motherboard's chipset, I remembered reading about that a long time ago. If you are using an older motherboard, especially one that happens to be a cheap brand, there is a chance that applying DMA witll cause a Read-Only device to not work properly or a hard drive to scramble its data. It's got more to do with the quality and design of the motherboard. IE, layout design, races (imbeded wiring) and other components, eg, capacitors, rather than the chipset used (VIA, AMD, Intel, nForce, SiS, etc.). I know I upset some people by sayin this, but Abit is probly a good yet popular example of all the above, poor design, poor implementation, marginal components. OTOH, even a good mobo will have problems if powered by a marginal power supply. Well I guess you have a point because my msi mobo comes with a bios setting by default is DMA disabled. I don't suppose they do that for nothing. So I for one will keep the substance of this discussion stowed away at the back of my mind. Just in case. John MSI makes good boards, they're often some of the first ones on AMD's recommended list. They were the first for 2700+ XP's followed shortly by Asus and Gigabyte. Similar implied recommendation can be made for their Intel boards (IMO). For an insite into why DMA is disabled read down thru /etc/rc.sysinit till you get to # Turn off DMA on CD-ROMs. It more often than not The very next section will tell you how to turn it back on, # Turn on harddisk optimization IE, uncomment 'USE_DMA=1' and copy that 'fixed' harddisks file to 'harddiskhd?' for each drive you want DMA enabled. I always enable it for all drives. I use to do it with rc.local, but now use the newer method with 'harddisks' as it catches it earlier in the boot proccess. -- Tom Brinkman Corpus Christi, Texas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] Burning frustration
gikoreno wrote: Hey John, I have a scsi card, and it takes the first scsi bus (scsi0), that's why the burner is on scsi1 OK that explains it you have some sort of scsi card and it takes precidence over the numbering, so then are the writer and rom IDE devices ? or what ? Speed is 40x for CDR's... I've burned no problems at that speen when I still used Win2k... That's just fine, a fast modern writer , faster than it needs to be really, OK. who's complaining ? On lilo I do have those entries you are talking about. In that case you have two seperate ide devices , rom and writer so hdc = one , hdd= the other and they are both employing scsi emulation that is what hdc=scsi etc is saying. I have a CDROM and a burner, and here are the entries for both in fstab: Are we talking about M8.2 or M9.0 ? I don['t have M9.0 as yet but some things have changed. This looks to me like M9.0 and it's supermount. I'm not sure but I would like you to try removing the none, in front of the stanzas using a text editor save and exit. Hell you can always put it back again if it don't work and it will not stop you booting up to desktop to replace it. The reasoning I am applying here is that these are real devices, not suedo devices , usually in the past only suedo devices had none in front of them.Try it and see how you get on. none /mnt/cdrom supermount dev=/dev/hdb,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0 none /mnt/cdrom2 supermount dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0 gikoreno John -- John Richard Smith [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] Burning frustration
Does anybody know how rawdevices enters the grand scheme of things? I would have expected most of my filesysetms to use it, but none are. Is that correct? Would that affect CD burning? Miark On Mon, 28 Oct 2002 22:44:36 -0500 harry [EMAIL PROTECTED] wrote: hi, I have the same problems with my linux... I think it is still not very stable... I use windows whenever I need to burn a cd... harry - Original Message - From: Miark [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, October 28, 2002 7:40 PM Subject: Re: [newbie] Burning frustration I've got the same crap going on here. In the last three CDs I've burned * The CPU meter hits the roof. It maintains 99% usage the entire time. Under 8.2 burning duties never exceeded 1.5%. * A 16MB fifo buffer while burning a 600MB CD, stuggles to keep full, rarely maintaining 25% content. During my last try, it emptied 90 times! The drive was 6% away from having to employ burnfree. The CD before that did use burnfree 15 times. Other points: * xcdroast, eroaster, and cdrecord get the same results (duh) * My USB SmartMedia reader is device 0,0,0. My burner is 1,2,0. * Nero had no problems in WinXP with the same hardware and media. What's going on? Miark On Mon, 28 Oct 2002 03:38:33 -0500 (EST) gikoreno [EMAIL PROTECTED] wrote: Hi everyone, I hope you had a nice weekend. I've been trying to burn ISO images on my burner. It's the first time I try this on Linux, and so far it's been quite the disaster... The command I am using is the following: cdrecord -v -eject speed=4 driveropts=burnfree dev=1,2,0 /tmp/s.iso I started with speed 16, because on windows I could run it at speed 16 or above without much trouble... but then I thought I might have been getting buffer underruns... so I tried speed=4. The output error is the following: I don't understand what the problem is. I tried to trouble-shoot a bit with different options, but all I am getting is coasters. Thanks for the help in advance, gikoreno ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
[newbie] Burning frustration
Hi everyone, I hope you had a nice weekend. I've been trying to burn ISO images on my burner. It's the first time I try this on Linux, and so far it's been quite the disaster... The command I am using is the following: cdrecord -v -eject speed=4 driveropts=burnfree dev=1,2,0 /tmp/s.iso I started with speed 16, because on windows I could run it at speed 16 or above without much trouble... but then I thought I might have been getting buffer underruns... so I tried speed=4. The output "error" is the following: <<+ Cdrecord 1.11a32 (i586-mandrake-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '1,2,0' scsibus: 1 target: 2 lun: 0 Linux sg driver version: 3.1.24 Using libscg version 'schily-0.6' Driveropts: 'burnfree' atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 1 Vendor_info: 'PLEXTOR ' Identifikation : 'CD-R PX-W4012A' Revision : '1.02' Device seems to be: Generic mmc CD-RW. Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : SWABAUDIO BURNFREE VARIREC Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 4194304 = 4096 KB FIFO size : 4194304 = 4096 KB Track 01: data 639 MB Total size: 734 MB (72:48.88) = 327666 sectors Lout start: 735 MB (72:50/66) = 327666 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 6 Is not unrestricted Is not erasable Disk sub type: Medium Type C, low Beta category (C-) (6) ATIP start of lead in: -11231 (97:32/19) ATIP start of lead out: 359849 (79:59/74) Disk type:Short strategy type (Phthalocyanine or similar) Manuf. index: 27 Manufacturer: Prodisc Technology Inc. Trying to clear drive status. cdrecord: Drive needs to reload the media to return to proper status. Blocks total: 1166730 Blocks current: 1166730 Blocks remaining: 839064 Starting to write CD/DVD at speed 4 in real TAO mode for single session. Last chance to quit, starting real write in 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. BURN-Free is OFF. Turning BURN-Free on Performing OPC... cdrecord: Input/output error. read track info: scsi sendcmd: no error CDB: 52 01 00 00 00 FF 00 00 1C 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 24 00 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.000s timeout 240s Writing time:0.010s Fixating... cdrecord: Input/output error. close track/session: scsi sendcmd: no error CDB: 5B 00 02 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 27 00 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x27 Qual 0x00 (write protected) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.000s timeout 480s cmd finished after 0.000s timeout 480s Fixating time:0.001s Average write speed 999.0x. cdrecord: fifo had 64 puts and 0 gets. cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%. +>> I don't understand what the problem is. I tried to trouble-shoot a bit with different options, but all I am getting is coasters. Thanks for the help in advance, gikorenoJoin Excite! - http://www.excite.comThe most personalized portal on the Web!
Re: [newbie] Burning frustration
gikoreno wrote: Hi everyone, I hope you had a nice weekend. I've been trying to burn ISO images on my burner. It's the first time I try this on Linux, and so far it's been quite the disaster... The command I am using is the following: cdrecord -v -eject speed=4 driveropts=burnfree dev=1,2,0 /tmp/s.iso gikoreno I take it you downloaded an iso image file you want to write to disc as a data file, because if not then you have to create an iso image file with mkisofs first, like this, cd to destination directory, mkisofs -r -J -v -o temp.iso / sourcetofile then ,check which lun your device is on,in terminal type, cdrecord -scanbus here is mine, scsibus0: 0,0,0 0) 'PIONEER ' 'DVD-ROM DVD-116 ' '1.22' Removable CD-ROM 0,1,0 1) 'MITSUMI ' 'CR-48X9TE ' '1.0C' Removable CD-ROM my writer is on 0,1,0 dvd0,0,0 Then, cdrecord -v speed=8 dev=0,1,0 -eject -ignsize /sourcefile.iso you don't need -ignsize if it's a small file. That should do it. John -- John Richard Smith [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] Burning frustration
I've got the same crap going on here. In the last three CDs I've burned * The CPU meter hits the roof. It maintains 99% usage the entire time. Under 8.2 burning duties never exceeded 1.5%. * A 16MB fifo buffer while burning a 600MB CD, stuggles to keep full, rarely maintaining 25% content. During my last try, it emptied 90 times! The drive was 6% away from having to employ burnfree. The CD before that did use burnfree 15 times. Other points: * xcdroast, eroaster, and cdrecord get the same results (duh) * My USB SmartMedia reader is device 0,0,0. My burner is 1,2,0. * Nero had no problems in WinXP with the same hardware and media. What's going on? Miark On Mon, 28 Oct 2002 03:38:33 -0500 (EST) gikoreno [EMAIL PROTECTED] wrote: Hi everyone, I hope you had a nice weekend. I've been trying to burn ISO images on my burner. It's the first time I try this on Linux, and so far it's been quite the disaster... The command I am using is the following: cdrecord -v -eject speed=4 driveropts=burnfree dev=1,2,0 /tmp/s.iso I started with speed 16, because on windows I could run it at speed 16 or above without much trouble... but then I thought I might have been getting buffer underruns... so I tried speed=4. The output error is the following: I don't understand what the problem is. I tried to trouble-shoot a bit with different options, but all I am getting is coasters. Thanks for the help in advance, gikoreno ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] Burning frustration
hi, I have the same problems with my linux... I think it is still not very stable... I use windows whenever I need to burn a cd... harry - Original Message - From: Miark [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, October 28, 2002 7:40 PM Subject: Re: [newbie] Burning frustration I've got the same crap going on here. In the last three CDs I've burned * The CPU meter hits the roof. It maintains 99% usage the entire time. Under 8.2 burning duties never exceeded 1.5%. * A 16MB fifo buffer while burning a 600MB CD, stuggles to keep full, rarely maintaining 25% content. During my last try, it emptied 90 times! The drive was 6% away from having to employ burnfree. The CD before that did use burnfree 15 times. Other points: * xcdroast, eroaster, and cdrecord get the same results (duh) * My USB SmartMedia reader is device 0,0,0. My burner is 1,2,0. * Nero had no problems in WinXP with the same hardware and media. What's going on? Miark On Mon, 28 Oct 2002 03:38:33 -0500 (EST) gikoreno [EMAIL PROTECTED] wrote: Hi everyone, I hope you had a nice weekend. I've been trying to burn ISO images on my burner. It's the first time I try this on Linux, and so far it's been quite the disaster... The command I am using is the following: cdrecord -v -eject speed=4 driveropts=burnfree dev=1,2,0 /tmp/s.iso I started with speed 16, because on windows I could run it at speed 16 or above without much trouble... but then I thought I might have been getting buffer underruns... so I tried speed=4. The output error is the following: I don't understand what the problem is. I tried to trouble-shoot a bit with different options, but all I am getting is coasters. Thanks for the help in advance, gikoreno ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] Burning frustration
Hey John, I have a scsi card, and it takes the first scsi bus (scsi0), that's why the burner is on scsi1 Speed is 40x for CDR's... I've burned no problems at that speen when I still used Win2k... On lilo I do have those entries you are talking about. I have a CDROM and a burner, and here are the entries for both in fstab: none /mnt/cdrom supermount dev=/dev/hdb,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0 none /mnt/cdrom2 supermount dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0 gikoreno > This is correct so your Plextor (speed?) writer is 1,2,0, thats slightly > unusual > as they usually come in 0,0,0, 0,1,0 0,2,0 there is something unusual > here > I wonder what your /etc/lilo.conf entry looks like for hdd=ide-scsi > hdc=ide-scsi > > I wonder what your /etc/fstab cdrom entries look like > /dev/scd1 /mnt/cdrom2 auto > user,iocharset=iso8859-15,umask=0,exec,codepage=850,ro,noauto 0 0 > /dev/scd0 /mnt/cdrom auto > user,iocharset=iso8859-15,umask=0,exec,codepage=850,ro,noauto 0 0 > > and do you have /mnt/cdrom, and /mnt/cdrom2 or something like it.Join Excite! - http://www.excite.comThe most personalized portal on the Web!
