-
Notifications
You must be signed in to change notification settings - Fork 7
/
CD-Writing-HOWTO
2091 lines (1370 loc) · 74.7 KB
/
CD-Writing-HOWTO
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
CD-Writing HOWTO
Winfried Trümper <[email protected]>
v2.9.3, 23 July 2000
This document explains how to write CD-ROMs under Linux.
______________________________________________________________________
Table of Contents
1. Introduction
1.1 Copyright, license and terms of usage
1.2 Availability
1.3 Suggested readings
1.4 Terminology ... lasers at maximum ... fire!
1.4.1 Adaptor vs. Adapter
1.5 Supported CD-writers
1.6 Supported "features"
1.7 Mailing Lists
2. Setup the Linux-system for writing CD-ROMs
2.1 Quickstart
2.1.1 Special notes about SCSI CD-writers
2.1.2 Special notes about CD-writers for the parallel port
2.1.3 Compiling missing kernel modules (optional)
2.2 Get the user software for burning CD-Rs
2.2.1 Command line utilities
2.2.2 Graphical user interfaces (optional)
3. Burning CD-Rs
3.1 Writing CD-ROMs (pure data)
3.1.1 Creating an image of the later CD-ROM
3.1.2 Test the CD-image
3.1.3 Write the CD-image to a CD
3.2 Writing audio CDs
3.2.1 Writing audio CDs (TAO)
3.2.2 DAO
3.3 Mixed mode CD-ROMs
4. Dear Winfried,...
4.1 How sensitive is the burning process?
4.2 Has file fragmentation a bad impact on the throughput?
4.3 Is it possible to store the CD-image on an UMSDOS-filesystem?
4.4 Isn't there some way to get around the ISO-9660 limitations?
4.5 How to read the tracks from audio CDs?
4.6 How to probe for SCSI devices after boot?
4.7 Is it possible to make a 1:1 copy of a data CD?
4.8 Can Linux read Joliet CD-ROMs? (obsolete answer)
4.9 How do I read/mount CD-ROMs with the CD-writer?
4.10 How to put even more data on the CD-R?
4.11 How to make bootable CD-ROMs?
4.12 How to make CD-ROMs writable like a hard disk?
4.13 Is it possible to use several writers at once?
4.14 What about Solaris, *BSD, AIX, HP-UX, etc.? Is my variant of Unix supported?
4.15 Where to store the local configuration permanently?
4.16 How can the CD-info be retrieved?
4.17 What about re-writing
4.18 How to create a multi-session CD?
4.19 Should I use the SCSI adapter shipped with the writer?
4.20 How to burn over the network?
4.21 I hear a crack or click sound at the end of the each track.
4.22 How can this be set up so that a user can burn CDs instead of always being root?
4.23 Where do I get the "Yellow Book" and "Orange Book" standards?
4.24 I've been searching for information on burning Video-CD under Linux.
4.25 Which is easier to set up, IDE or SCSI?
4.26 How can I overburn a CD using {cdrecord,cdrdao}?
4.27 What will cdrecord do when it stops getting input from the pipe?
4.28 Is there an equivalent to ignore=hdX for the ide-scsi emulation?
4.29 How many times can you re-use CD-RW before they become faulty?
4.30 Which format to choose for a platform independant CD-ROM?
4.31 Is multi-session for audio tracks possible?
4.32 What hardware resources do I need? Is an old Pentium enough?
5. Troubleshooting
5.1 It doesn't work: under Linux
5.2 Error-message: No read access for 'dev=0,6,0'.
5.3 It doesn't work: under DOS and friends
5.4 SCSI errors during the burning phase
5.5 Medium errors If cdrecord reports medium errors in the form of "Sense Key: ... Medium Error, Segment ...", then the medium is not empty. If you use CD-RW, then try to switch from blank=fast to the more reliable blank=all. If you use CD-R only, then make sure the CD-R has never seen a CD-writer before or try out discs from another manufacturer.
5.6 Newly written CDs are not readable on some players.
5.7 My scanner stopped working after I loaded the ide-scsi module
6. Credits
______________________________________________________________________
1. Introduction
Many people use Linux to burn CD-ROMs, because it is reliable and
easy. No bluescreens while burning and no headaches about getting the
right combination of hard- and software. It just works once properly
set up. The CD-writing HOWTO explains the setup, how to put data on
the media and gives some interesting applications kindly submitted by
the readers.
1.1. Copyright, license and terms of usage
Copyright Winfried Trümper 1996-2000. All rights reserved.
Redistribution and use, with or without modification, are permitted
provided that the name of the author may not be used to endorse or
promote products derived from this software without specific prior
written permission. In this sense, translations are welcome and need
not to be authorized by me.
The author disclaims all warranties with regard to this document,
including all implied warranties of merchantability and fitness for a
certain purpose; in no event shall the author be liable for any
special, indirect or consequential damages or any damages whatsoever
resulting from loss of use, data or profits, whether in an action of
contract, negligence or other tortious action, arising out of or in
connection with the use of this document.
Short: read and use at your own risk. No money-back guarantee. If you
want to understand why this document has always been under a very weak
license and not under the gnu GPL or similar restrictive, then you
should read this article from the german computer magazine c't:
<http://www.heise.de/tp/deutsch/inhalt/te/8375/1.html> (currently only
in German language).
1.2. Availability
As the editor of this document I mostly sum up what other people
report to me. I'm not a software developer nor an expert in hardware,
so for specific problems with hard- or software you may want to ask
somebody else. What always makes sense is to report solutions for
problems not already covered by the HOWTO to me.
I get several hundred e-mails concerning the CD-Writing HOWTO each
year. So please be patient with me, as I cannot always answer within
hours. However, I read everything immediately and put you on my CDR-
queue. Before you ask a question, please make sure you are aware of
the newest version of this document; it is always available from
<http://www.guug.de/~winni/linux/>.
1.3. Suggested readings
You may need the handbook for your Linux-distribution to learn about
installing a new kernel. I'm really clueless about this issue when it
comes to any other Linux distribution than my own.
The CD-R FAQ <http://www.fadden.com/cdrfaq/> is a general FAQ about
compact-disk recordables (CD-R), CD-writers and the required software.
As most CD-writers can be used to read CD-ROMs, too, you may want to
read the Linux CD-ROM HOWTO, the Linux SCSI HOWTO and the Linux Kernel
HOWTO.
1.4. Terminology ... lasers at maximum ... fire!
CD-ROM stands for Compact Disc Read Only Memory, a storage medium
utilizing an optical laser to sense microscopic pits on a colorful
shimmering disk. The pits represent the bits of the information and
are so petite that some billions of them fit on the disc. Thus a CD is
a mass-storage medium.
The term CD-R is a short form of CD-ROM recordable and refers to a CD
that doesn't have those microscopic pits on its surface. Thus it is
empty. The CD-R has a special chemical film inside into which pits can
be burned. This is done by giving the laser which normally just senses
the pits a little bit more power so it burns the pits. This action can
only be taken once on a CD-R. You can leave out some areas for later
writing, creating a so called multi-session CD.
The CD-ROM rewritable (short: CD-RW) was developed to work around the
limitation of CD-R media. With a CD-RW burner the laser can do both,
burn pits into the media and also melt the media back into its
original state. This is possible, because the laser does not really
burn holes into the media, which would get lost in a puff of smoke. A
decent analogy for the technique is an ice-hockey game: by driving
over the ice, a players (laser) leave scratches in it. The pattern in
the ice (media) is a recording of what happened on the ice during one
round. In between the periods of the game, the Zamboni cleaning car
drives over the ice and fills the scratches by melting the very top
layer of the ice. (Zamboni is the brand name for cleaning cars in
ice-hockey stadiums). This way the pattern on the ice is cleared and
a new round can begin. The scientific term for evaporating,
condensing, melting and freezing is "phase change", thus the name
"phase change devices" for CD-RW-writers.
This HOWTO deals with the task of writing CD-Rs and CD-RWs. Welcome
on board, captain.
1.4.1. Adaptor vs. Adapter
The the most frequent spelling within the kernel sources is adapter
(adapter: 4283, adaptor: 154). Even more important, the parameters of
module options and aliases are naturally affected, like in
"scsi_hostadapter". So in order to achieve a consistent spelling
throughout configuration examples and document text, I follow that
convention regardless of the correct spelling.
1.5. Supported CD-writers
USB CD-writers are currently not supported at all. Apart from that you
can safely assume that most newer IDE/ATAPI- and SCSI-writers work
under Linux. Newer drives are mostly MMC-compliant and are therefore
supported. If the SCSI-version of a particular writer works, the
IDE/ATAPI-version will most likely work and vice versa. However, some
people want to get a warm and fuzzy feeling by reading the exact model
of their writer in some sort of compatibility list. That is the
reason why I didn't throw the following list out of the HOWTO. Here
is a comprehensive summary of drives reported to work with cdrecord:
Acer: CDRW 4432A, CDRW 6206A, CD-R/RW 6X4X32, 8432A
BTC: BCE 621E (IDE)
Compro: CW-7502, CW-7502B
Creative: MK 4211, RW 4224E,
Delta: OME-W 141
Dysan: CRW-1622
Elite: Elite b444.41
Goldstar: CED-8041B
Grundig: CDR 100 IPW
Guillemot: Maxi CD-R 4X/8X
HP: SureStore 4020i, SureStore 6020i,
C4324, C4325
CD-writer+ 7100, 7200i, 7500e, 8100i, 8110i, 8200i Plus,
8250i, 9100i, 9110i, 9200e, 9210, 9300i, 9310i
Hi-Val: CDD 2242, CDD-3610,
Iomega: ZIPCD 4x650
JVC: XR-W 2001, XR-W 2010, XR-W 2040, XR-W 2042, XR-RW 2224,
YR 2626
Kiss: CDRW (no model given)
Kodak: PCD 200, PCD 225, PCD 260, PCD 600
Matsushita: matsushita is the japanese name for panasonic, please see there
Memorex: CRW-620, CDR-622, CRW-1622, CRW-2224, CDRW-4420
Microboards: PlayWrite 2000, PlayWrite 4000 RW, PlayWrite 4001 RW
MicroNet: MasterCD Plus 4x4, MasterCD Plus 4x6
Mitsubishi: CDRW-226
Mitsumi: CR-2401-TS, CR-2600 TE, CR-2801 TE,
CR-4801 TE, CR-4802 TE, CR-4804 TE
Nomai: 680.RW
Olympus: CDS 615E, CDS 620E
Optima: DisKovery 650 CD-R
OTI: CDRW 965, CDRW 975 (Socrates 1.0)
Panasonic: CW-7285, CW-7502, CW-7503, CW-7582
Philips: CDD-521/10, CDD-522,
CDD-2000, CDD-2600, CDD-3600, CDD-3610, CDD 4201
PCA 267cr, PCA 460 RW, PCRW 404,
Omniwriter 26, Omniwriter 26A,
CDRW800
Pinnacle: RCD-100, RCD-1000, RCD-5020, RCD-5040
Pioneer: DW-S114X
Plasmon: CDR 480, CDR 4220, RF-4100, RF-4102, CDR 4400
Plextor: CDR PX-24 CS, PX-412 C, PX-R412 C
PX-R 810Ti, PX-R 820T, PX-W 4220Ti, PX-W 8220T, PX-W 8432T
Plexwriter RW 4/2/20
Procom: PCDR 4
REC: 820s
Ricoh: RO-1420C+, MP 1420C, MP 6200S, MP 6201S, MP 7040A, MP-7060A
Samsung: SW-204
Sanyo: CRD-R24S
Smart and
Friendly: CD-RW 226, CD-R 1002, CD-R 1002/PRO, CD-R 1004,
CD-R 2004, CD-R 2006 PLUS, CD-R 2006 PRO, CD-RW 2224,
CD-R 4000, CD-R 4006, CD-R 4012, CD-RW 4424A
CD-R 8020, CD-R 8220
Sony: CDRX 100E, CDRX 120E, CDRX 140S-RP,
CDU 920S, CDU 924, CDU 926S, CDU 928E, CDU 948S
Taiyo Yuden: EW-50
TEAC: CD-R50S, CD-R55S, CDR-55S, CDR-55K,
CDR-56S-400, CD-R56S-600, R56S-614
Traxdata: CRW 2260,
CDR 4120, CDR 4120 Pro, CDRW 4260, CDRW 4424, CDR 4800
Turtle Beach: 2040R
Waitec: wt 2036, wt 2444ei
WPI (Wearnes): CDRW-622, CDR-632P
Yamaha: CDR-100, CDR 102, CDR-200, CDR-200t, CDR-200tx
CDR-400, CDR-400c, CDR-400t, CDR-400tx, CDR-400Atx
CDW-2216E, CRW-2260, CRW-2260t,
CRW-4250tx, CRW-4260t, CRW-4260tx, CRW-4261, CRW-4416S,
CRW-6416S, CRW-8424E
The detailed list of models which have been reported to work or not to
work under various Unix-like operating systems is available online
from <http://www.guug.de:8080/cgi-bin/winni/lsc-orig.pl>.
If your hardware isn't supported you can still use Linux to create an
image of the CD. You may wish to do so because most burning software
for DOS does not deal with RockRidge-extensions (Unix-like filesystems
on CD-ROM). In a second step, you can use DOS or Macintosh software to
write the image to the CD-R.
1.6. Supported "features"
Two There are two classes of utilities: the hardware drivers and the
data-formatters. The hardware drivers support the following features:
Supported Feature cdwrite-2.1 cdrecord-1.6 cdrdao
----------------------------------------------------------
IDE/ATAPI yes yes yes
Parallel Port no yes yes
CD-RW no yes yes
Audio CD yes yes yes
Data CD-ROM yes yes partial
Multisession partial yes no
TAO (track at once) yes yes yes
DAO (disk at once) no partial yes
packet writing no no no
cdwrite is unmaintained software referenced only for completeness.
Please use cdrecord instead, as it supports a wider range of hardware
and has significantly more features. The main benefit of cdrdao is the
ability to create audio CDs without two seconds of silence between the
tracks (writing in disk-at-once (DAO) mode).
The tools classified as "data-formatters" organize the data on the
media ("put a filesystem on it").
Feature mkisofs mkhybrid mkvcdfs
-------------------------------------------------------
ISO 9660 yes yes no
RockRidge yes yes no
El Torito yes yes no
HFS no yes no
Joliet yes yes no
Multisession yes yes no
CD-Extra yes yes no
Video-CD no no yes
The most obvious difference between the ISO 9660 filesystem compared
to the ReiserFS or Extended-2 filesystem is: you can't modify files
once they are written. Other limitations of the ISO-9660-filesystem
include:
· only 8 levels of sub-directories allowed (counted from the top-
level directory of the CD)
· maximum length for filenames: 32 characters
· 650 MB capacity
RockRidge is an extension to allow longer filenames and a deeper
directory hierarchy for the ISO-9660 filesystem. When reading a CD-ROM
with RockRidge extensions under Linux, all the known properties of
files like owner, group, permissions, symbolic links appear ("feels
like a Unix filesystem"). These extensions are not available when
reading the CD-ROM under DOS or the heterogenous Windows-family of
operating systems.
El Torito can be used to produce bootable CD-ROMs. For this feature to
work, the BIOS of your PC must support it. Roughly speaking, the first
1.44 (or 2.88 if supported) Mbytes of the CD-ROM contains a floppy-
disk image supplied by you. This image is treated like a floppy by the
BIOS and booted from. (As a consequence, while booting from this
virtual floppy, your original drive A: (/dev/fd0) may not be
accessible.)
HFS lets a Macintosh read the CD-ROM as if it were an HFS volume (the
native filesystem for MacOS).
Joliet brings long filenames (among other things) to newer variants of
Windows (95, 98, NT). However, the author knows of no tool that allows
long filenames under plain DOS or Windows 3.11.
Video-CDs can be directly played on DVD-devices.
Section 2.8 lists the availability of the mentioned software.
1.7. Mailing Lists
If you want to join the development team (with the intention to
actively help them), send e-mail to [email protected]
and put the word subscribe in body of the message.
2. Setup the Linux-system for writing CD-ROMs
This section applies to the following types of CD-writers: SCSI,
IDE/ATAPI and the devices for the parallel port. USB CD-writers are
not supported as of May 2000. Non-SCSI writers require compatibility
drivers, which make them appear as if they were real SCSI devices. On
the one side such a unifying strategy is easy ("everything is SCSI"),
because on the application level you can share your knowledge with
other users regardless of their kind of CD-writer. On the other side,
you have to reconfigure applications like audio CD players or the
mount utility to reflect the change of the driver name. For example,
if you accessed your ATAPI CD-writer through the device file /dev/hdc
before, you will have to access it through /dev/scd0 after activating
the SCSI compatibility drivers.
Once you succeed setting up your hardware and the rest of your Linux-
system, the command cdrecord -scanbus shows you a list of devices on
your SCSI busses. The goal of this section is to guide you in setting
up your Linux-system, so that you finally end up seeing something
like:
shell> cdrecord -scanbus
Cdrecord release 1.7a1 Copyright (C) 1995-1998 Jörg Schilling
scsibus0:
0,0,0) 'Quantum ' 'XP34300 ' 'F76D' Disk
0,1,0) 'SEAGATE ' 'ST11200N ' '8334' Disk
0,2,0) *
0,3,0) 'TOSHIBA ' 'MK537FB/ ' '6258' Disk
0,4,0) 'WANGTEK ' '5150ES SCSI 36 ' 'ESB6' Removable Tape
0,5,0) 'EXABYTE ' 'EXB-8500-85QUE ' '0428' Removable Tape
0,6,0) 'TOSHIBA ' 'XM-3401TASUNSLCD' '3593' Removable CD-ROM
0,7,0) *
scsibus1:
1,0,0) 'Quantum ' 'XP31070W ' 'L912' Disk
1,1,0) *
1,2,0) *
1,3,0) 'TEAC ' 'CD-R55S ' '1.0H' Removable CD-ROM
1,4,0) 'MATSHITA' 'CD-R CW-7502 ' '4.02' Removable CD-ROM
1,5,0) *
1,6,0) 'YAMAHA ' 'CDR400t ' '1.0d' Removable CD-ROM
1,7,0) *
The example was provided by Jörg Schilling and shows a total of four
CD-writers. Please note that -scanbus also reports other devices, e.g.
regular CD-ROMs and hard disk drives. The last column gives the SCSI
description of the device, from which you cannot clearly distinguish
ordinary CD-ROM drives from those with burning capability. But the
product identification (middle column) often has hints about the
feature in form of a R, -R or -RW.
2.1. Quickstart
This section is an attempt to provide an fast and easy description of
the configuration. Not all possible setups are covered, but please go
on and try it out anyways. First of all, check the Linux kernel
version printed by the command "uname -r". It should be something
like 2.0.X or 2.2.Y, where X is higher than 36 and Y is higher than
11. If you run older versions or the so called development kernels,
you are on your own. Installing a new kernel is as much work as fixing
an old one, so I have removed all hints you need for buggy kernels.
The listing below shows a set of commands you could start with. The
commands create device file entries under /dev unless they already
exists.
test `whoami` = 'root' || echo "You must be root to execute the commands."
cd /dev/
umask -S u=rwx,g=rwx,o-rwx
[ -f loop0 ] \
|| ./MAKEDEV loop \
|| for i in 0 1 2 3 4 5 6 7; do mknod loop$i b 7 $i; done
[ -f sg0 -o -f sga ] \
|| ./MAKEDEV sg \
|| for i in 0 1 2 3 4 5 6 7; do mknod sg$i c 21 $i; done
Hardware access is usally implemented through device files under
Linux. So before any other thing you make sure those files do exists
in the directory /dev. Still nobody could give me a compelling reason
why this has not been automated through techniques like the device
filesystem (devfs). The devfs is available for years know, brings a
safer (!) and a far clearer naming of devices and makes the device
entries appear automatically under /dev. Some prominent people argue
devfs is not the perfect solution, but they do not come up with
anything better, not even something comparable and last but least
nothing available and tested now. Lets start to use devfs, so I can
remove the above commands from this document. (
<http://www.atnf.CSIRO.AU/~rgooch/linux/kernel-patches.html>)
Next thing to ensure is, that the Linux kernel is equiped with the
necessary drivers. The following commands check various files for the
presence of drivers in the running Linux kernel. Usally the command
"cdrecord -scanbus" should trigger an automatic loading of all
drivers. In case a driver is not present in the kernel afterwards, it
is reported and the modularized driver (module) is manually loaded
through insmod.
test `whoami` = 'root' || echo "You must be root to execute the commands."
cdrecord -scanbus > /dev/null
if ! (pidof kerneld || test -f "/proc/sys/kernel/modprobe"); then
echo "Neither kerneld nor kmod are running to automatically load modules".
fi
report_no_autoload() {
echo "Ensure the module $1 is loaded automatically next time."
}
if test ! -f "/proc/scsi/scsi"; then
report_no_autoload scsi_mod && insmod scsi_mod
fi
if ! grep "^........ sg_" /proc/ksyms > /dev/null; then
report_no_autoload sg && insmod sg
fi
if ! grep "^........ sr_" /proc/ksyms > /dev/null; then
report_no_autoload sr_mod && insmod sr_mod
fi
if ! grep "^........ loop_" /proc/ksyms > /dev/null; then
report_no_autoload loop && insmod loop
fi
if ! grep iso9660 /proc/filesystems > /dev/null; then
report_no_autoload iso9660 && insmod iso9660
fi
echo "The following is only needed for IDE/ATAPI CD-writers."
if ! grep ide-scsi /proc/ide/drivers > /dev/null; then
report_no_autoload ide-scsi && insmod ide-scsi
fi
cdrecord -scanbus
Please read the next chapter if insmod complains about missing module
files. If you are in text mode (console), the loading of modules may
cause some messages to be printed on your screen. If you are in
graphics mode (X11, KDE, Gnome), you can recall these messages with
the command dmesg.
There are several ways to load the modules next time you start up your
Linux system:
(1) Put the relevant insmod command into the startup sequence
(a shell script named rc.local or equivalent).
(2a) Run kerneld or kmod and
(2b) configure them in /etc/modules.conf (to be more precise,
you configure the utility modprobe, which is called by the daemons)
People with a SCSI-writer can skip the rest of this section, because
cdrecord will most likely already detect their hardware. If not, then
please send me an email with some information about your setup, so I
can improve the section about SCSI-writers.
Now to the people with CD-writers for IDE/ATAPI. As written in the
previous chapter, you have to load the compatibility driver ide-scsi.
But this driver can only access your CD-Writer if no other driver has
already done so. In other words, you have to tell the regular IDE
driver to leave your CD-writer unrecognized, so the ide-scsi driver
can grab it.
hda = IDE bus/connector 0 master device
hdb = IDE bus/connector 0 slave device
hdc = IDE bus/connector 1 master device
hdd = IDE bus/connector 1 slave device
The table above shows the relation of device file names and the
placing of devices on the IDE busses. The device file name
representing your CD-Writer has to be passed to the driver in the
Linux kernel. Example: hdb=ide-scsi. Such a setting should be added
to lilo.conf or chos.conf if the driver is statically compiled into
your kernel, which seems to be the most common setup. If you need to
pass more than one parameter to the kernel, then seperate them with
spaces (like shown in the chos example). The next two listings show
example configurations containing more lines than just the relevant
append-line. Please note the append- and cmdline-entries are image-
specific (ie. don't add them immediatly at the top).
image=/boot/zImage-2.2.14
label=Linux
read-only
append="hdb=ide-scsi"
linux "Linux 2.1.14" {
image=/boot/zImage-2.0.37
cmdline= root=/dev/hda5 readonly hdb=ide-scsi
}
If the driver for IDE/ATAPI CD-ROMs is loaded as a module, then the
above won't make any difference to you, but make sure you include the
options-line from the next listing. The last three lines of that
listing are generally suggested to further automate the loading of the
required modules.
options ide-cd ignore=hdb # tell the ide-cd module to ignore hdb
alias scd0 sr_mod # load sr_mod upon access of scd0
#pre-install ide-scsi modprobe imm # uncomment for some ZIP drives only
pre-install sg modprobe ide-scsi # load ide-scsi before sg
pre-install sr_mod modprobe ide-scsi # load ide-scsi before sr_mod
pre-install ide-scsi modprobe ide-cd # load ide-cd before ide-scsi
If your CD-writer is the only CD-ROM attached to your machine, then
remember you have to access the CD-ROM in the writer through the
device file /dev/scd× where ×=0,..,8. You may want to change the
symbolic name cdrom to point to the new device file name. The listing
below shows the command to achieve this with the example scd0.
cd /dev && rm cdrom && ln -s scd0 cdrom
If your CD-writer and CD-ROM-drive are two different devices, then
don't change the cdrom symlink.
2.1.1. Special notes about SCSI CD-writers
Please make sure that your writer is recognized by the BIOS of your
SCSI hostadaptor card. Every SCSI hostadaptor scans the SCSI bus after
power on and reports all devices found connected to the bus. The
report includes the SCSI ID of the devices and their product label. It
makes no sense to proceed unless your CD writer is listed in that
report.
If you plan to connect your SCSI device through the parallel port (not
to confuse with the IDE drives for the parallel port), you need a
special active cable and a special kernel driver. Read
<http://www.torque.net/parport/parscsi.html> to learn more about this
option.
2.1.2. Special notes about CD-writers for the parallel port
I have no clue about this, sorry. Please read
<http://www.torque.net/parport/paride.html> or your local file
/usr/src/linux/Documentation/paride.txt.
2.1.3. Compiling missing kernel modules (optional)
You don't need to read this section if you hardware is already
sucessfully recognized and configured by the previously described
configuration steps.
The Linux kernel can be equipped with drivers for various features.
You can compile the drivers into the kernel image statically or you
can compile them as a module for on-demand loading. The last method is
preferred for drivers not essential for bringing your Linux-system
into life, because your kernel will be smaller and faster then.
However, some drivers are essential for the system to come up and you
shouldn't compile them as a module. Example: if your system lives on
an IDE hard disk, you must have the driver for IDE hard disks in the
kernel -- not as a module.
There are three different types of CD-writers: SCSI, IDE/ATAPI and
external writers that work through the parallel port. The table shows
how to configure the Linux kernel for those hardware types. The first
column of the table is the section of the kernel configuration menu,
where you can find the setting. The second column is the description
of the feature (taken from the kernel configuration menu, too). The
third column gives the name of the resulting module. The columns named
SCSI, IDE and PP contain the necessary options for the associated
hardware (PP = parallel port).
Sect. Description Module SCSI IDE PP
------------------------------------------------------------
BLOCK Enhanced IDE/MFM/RLL... Y
BLOCK IDE/ATAPI CDROM ide-cd M
BLOCK SCSI emulation support ide-scsi M
BLOCK Loopback device loop M M M
PARIDE Parallel port IDE device paride Y/M
PARIDE Parallel port ATAPI CD-ROMs M
PARIDE Parallel port generic ATAPI M
PARIDE (select a low-level driver) Y
SCSI SCSI support scsi_mod Y/M Y/M
SCSI SCSI CD-ROM support sr_mod Y/M Y/M
SCSI Enable vendor-specific Y Y
SCSI SCSI generic support sg Y/M Y/M
SCSI (select a low-level driver) Y
FS ISO 9660 CDROM filesystem iso9660 Y/M Y/M Y/M
FS Microsoft Joliet cdrom... joliet Y Y Y
Y stands for yes and means you should put the beast into the kernel.
M stands for module and means you should or must compile this feature
as a module. Y/M gives you the option to decide between either (order
indicates choices with less potential problems). Empty settings don't
need to be modified and not changing them increases the chance that
the resulting kernel will work for you (if it did before...).
Especially in environments where SCSI and ATAPI devices are mixed, you
better build most things as modules.
Compiling loopback device is optional. It allows you to test the
image before writing it to the media. If you want to be able to read
CD-ROMs, you need support for the ISO 9660 filesystem. This driver
automatically includes RockRidge Extensions. The Microsoft Joliet CD-
ROM extensions have to be explicitly added to the ISO 9660 filesystem.
In any case, you need a low-level driver for your hardware. Low-level
refers to the driver, which interacts directly with the hardware. For
SCSI and the parallel port, there are a lot of low-level drivers
available.
Installing the resulting Linux-kernel is beyond the scope of this
HOWTO. Please consult the documentation of your Linux-distribution.
Users of RedHat Linux be aware that you have to compile in the
features "Ramdisk support" and "Initial ramdisk". Furthermore, you
have to generate a new ramdisk with the new modules by issuing a
command like "mkintrd --preload ide-cd initrd-2.2.14.img 2.2.14".
2.2. Get the user software for burning CD-Rs
A more detailed survey of tools related to produce CD-ROMs is
available from
<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdb.html>.
2.2.1. Command line utilities
One of the following packages are required to generate images of CD-Rs
(only required for data CD-ROMs):
<ftp://tsx-11.mit.edu/pub/linux/packages/mkisofs/> (mkisofs)
<ftp://ftp.ge.ucl.ac.uk/pub/mkhfs> (mkhybrid)
To write images to the CD-R, you need one of the following software
packages:
<ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/> (cdrecord)
<http://www.ping.de/sites/daneb/cdrdao.html> (cdrdao)
<http://www.munich-vision.de/vcd/> (mkvcdfs)
Don't trust the man page of old versions of mkisofs which state you
need version 1.5 of cdwrite. Just use cdrecord and you are fine.
Please note that newer versions of cdrecord ship with an enhanced
version of mkisofs and some extra tools in the subdirectory misc/
(readcd, isosize) not found elsewhere.
2.2.2. Graphical user interfaces (optional)
Front-ends are really front-ends under Linux. That means, you still
have to install the command-line utilities, but you access them in a
better looking manner.
X-CD-Roast is a program package dedicated to easy CD creation under
Linux. It combines command line tools like cdrecord and mkisofs into a
nice graphical user interface.
<http://www.fh-muenchen.de/home/ze/rz/services/pro
jects/xcdroast/e_overview.html>
BurnIT is a JAVA front-end to cdrecord, mkisofs and cdda2wav-0.95
making it a complete package for burning CDs on the Unix platform. It
is available from
<http://sunsite.auc.dk/BurnIT/>
CD-Tux is a character based frontend for the programs mkisofs and
cdrecord. "It creates an easy to use enviroment for doing almost
anything to a CD in full color through the use of the (in)famous
NCURSES Library. And it does all this whith an executable of under
75K."
<http://www.datadictator.co.za/cdtux/>
3. Burning CD-Rs
"If to smoke you turn I shall not cease to fiddle while you
burn." (Roman emperor Nero about burning his own classic-
CDs, AD64. He misunderstood it completely and burned Rome
down.)
Writing CD-ROMs consists of two steps under Linux:
· packaging the desired data (files, music or both) into files with
special formats
· writing the data from the files to the CD-R with the utility
cdrecord
This chapter describes the steps for data and audio CDs in greater
detail.
3.1. Writing CD-ROMs (pure data)
Note that collecting the data to put onto a CD usually takes longer
than one expects. Consider that missing files cannot be added once the
CD is written and fixated. This is also true for CD-RW, which can
currently only be rewritten as a whole. Using the multi-session
feature is no option for single files, as it consumes much space for a
new complete table of contents (TOC). UDF is not ready yet for Linux.
Also keep in mind that a certain amount of the free space of a CD is
used for storing the information of the ISO-9660-filesystem (usually a
few MB). 620 MB data will always fit on a 650 MB CD-R.
3.1.1. Creating an image of the later CD-ROM
Before any storage medium (e.g. floppy disk, hard disk or CD) can be
used, it must get a filesystem (DOS speak: get formatted). The
filesystem is responsible for organizing and incorporating the files
that should be stored on the medium.
The usual utilities for creating filesystems on hard disk partitions
write an empty filesystem onto them, which is then mounted and filled
with files by the users as they need it. A writable CD is only
writable once so if we wrote an empty filesystem to it, it would get
formatted and remain completely empty forever. This is also true for
rewritable media as you cannot change arbitrary sectors yet; you must
erase their whole content.
So what we need is a tool that creates the filesystem while copying
the files to the CD. This tool is called mkisofs. A sample usage
looks as follows:
mkisofs -r -o cd_image private_collection/
`---------' `-----------------'
| |
write output to take directory as input
The option '-r' sets the permissions of all files to be public
readable on the CD and enables RockRidge-extensions. You probably want
to use this option unless you really know what you're doing (hint:
without '-r' the mount point gets the permissions of
private_collection!).
mkisofs will try to map all filenames to the 8.3 format used by DOS to
ensure the highest possible compatibility. In case of naming conflicts
(different files have the same 8.3 name), numbers are used in the
filenames and information about the chosen filename is printed via
STDERR (usually the screen). Don't panic: Under Linux you will never
see these odd 8.3 filenames because Linux makes use of the Rock Ridge
extensions which contain the original file information (permissions,
filename, etc.).
Remeber do use the Option -J (MS Joliet extensions) or use mkhybrid if
you want to generate a more Windows-friendly CD-ROM. For HFS CD-ROMS
used on the Macintosh, you better read the man-page of mkisofs' bigger
sister mkhybrid for details on various options.
Now you may wonder why the output of mkisofs is not directly sent to
the writer device. There are three reasons:
· mkisofs knows nothing about driving CD-writers.
· You may want to test the image before burning it.
· On slow machines it would not be reliable (see section 4.).
There is a method to write a CD-R in one go, which will be described
below.
One also could think of creating an extra partition and writing the
image to that partition instead to a file. I vote against such a
strategy because if you write to the wrong partition due to a typo,
you can lose your complete Linux system. Read: that happened to me...
Furthermore, it is a waste of disk space because the CD-image is
temporary data that can be deleted after writing the CD. However,
using raw partitions saves you the time for deleting files of 650 MB
size.
3.1.2. Test the CD-image
Linux has the ability to mount files as if they were disk partitions.
This feature is useful to check that the directory layout and file
access permissions of the CD image matches your wishes. Although media
is very cheap today, the writing process is still time consuming, and
you may at least want to save your time by doing a quick test.
To mount the file cd_image created above on the directory /cdrom, give
the command
mount -t iso9660 -o ro,loop=/dev/loop0 cd_image /cdrom
Now you can inspect the files under /cdrom -- they appear exactly as
they were on a real CD. To umount the CD-image, just say umount
/cdrom. (Warning: On Linux kernels prior to 2.0.31 the last file on
/cdrom may not be fully readable. Please use a more recent kernel like
2.0.36. The option -pad for cdrecord applies to audio CDs only and the
option -pad for mkisofs requires a patch, which is as much work to
apply than to upgrade to a bug-free Linux kernel.)
Note:
Some ancient versions of mount are not able to deal with
loopback devices. If you have such an old version of mount,
then upgrade your Linux-system. Several people have already
suggested putting information about how to get the newest
mount utilities into this HOWTO. I always refuse this. If
your Linux distribution ships with an ancient mount, report
it as a bug. If your Linux distribution is not easily
upgradable, report it as a bug.
If I include all the information that is necessary to work
around bugs in badly designed Linux distributions, this
HOWTO would be a lot bigger and harder to read.
3.1.3. Write the CD-image to a CD
This section only covers writing data CDs in TAO mode, because it is
the most frequently used mode for data. For more information about the
differences of TAO and DAO, please see the chapter about audio CD-Rs.
If you use DAO mode with the tool cdrdao, then remember to add a dummy
audio track at the end of the TOC file (see the README).
Not much more left to do. If you haven't already tried, it's a good
time for the command
cdrecord -scanbus
This will tell you to which SCSI device your CD-writer is attached to.
All other methods of guessing the information printed so nicely by
cdrecord have been removed from the HOWTO.
Before showing you the last command, let me warn you that CD-writers
want to be fed with a constant stream of data. So the process of
writing the CD image to the CD must not be interrupted or a corrupt CD
will result. It's easy to interrupt the data stream by deleting a very