Ramiro Alba Queipo (ramiro@labtie.mmt.upc.es)
Tue, 03 Nov 1998 17:45:30 +0100
grant@torque.net wrote:
> > modprobe pcd
>
> The documentation specifically discourages the use of modprobe/kerneld etc,
> for precisely this reason.
>
> Please use insmod to load the _three_ required modules:
>
> insmod paride
> insmod epat
> insmod pcd
>
> > /lib/modules/2.0.34/misc/pcd.o: init_module: Device or resource busy
>
> NB: your module configuration is messed up if you are loading 2.0.35
> modules from a 2.0.34 directory.
>
> > paride: version 1.02 installed
> > pcd: pcd version 1.03s, major 46, nice 0
> > pcd0: Autoprobe failed
> > pcd: No CDrom drive found
>
> Notice that there is no indication that epat has been loaded. There is
> no dependency on epat that any autoloader can detect. You must either
> fix your conf.modules to tell modprobe and friends about epat (read the
> kerneld documentation), or load the modules by hand.
>
> > The results are similar the pg driver.
>
> For the same reason.
>
> > I also tried to compiled the drivers inside the kernel, and when booting
> > it says:
>
> When you configured the kernel, did you remember to include the epat
> module ? Again, it is not mentioned in the log messages you report.
Hi Grant:
Right, the problem was that I did not included the epat module (sorry). Now, I
can access to the drive with the pcd driver without apparent problems, but
with the pg driver is another history.
Once I compiled as modules all the drivers, and booted with the new kernel (I
path the 2.0.34 kernel with paride), I followed the instructions at
http://www.torque.net/parport/cdr.html in order to use cdrecord.
First, I install the driver:
insmod paride
insmod epat
insmod pg
Then at the dmesg output I can see:
paride: version 1.02 installed
paride: epat registered as protocol 0
pg: pg version 1.01s, major 97
pg0: epat 1.01, Shuttle EPAT chip c6 at 0x378, mode 0 (4-bit), delay 1
pg0: HP CD-Writer+ 7200, slave
Then I scaned for scsi devices:
cdrecord -dummy -scanbus
Cdrecord release 1.6 Copyright (C) 1995-1998 Jörg Schilling
scsibus0:
0) 'HP ' 'CD-Writer+ 7200 ' '2.02' Removable CD-ROM
1) *
2) *
3) *
4) *
5) *
6) *
7) *
Finaly I make a test to the drive (the options to cdrecord are sugested in the
Debian 2.0 -witch I use - distribution in order to record a CD for its
official distribution):
nice -20 time cdrecord -eject -v -isosize speed=2 dev=0,0 \
-dummy -data -pad /mnt/CD-image/contrib_non-free.iso
Cdrecord release 1.6 Copyright (C) 1995-1998 Jörg Schilling
TOC Type: 1 = CD-ROM
scsidev: '0,0'
scsibus: 0 target: 0 lun: 0
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'HP '
Identifikation : 'CD-Writer+ 7200 '
Revision : '2.02'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags : SWABAUDIO
Track 01: data 205 MB padsize: 30 KB
Total size: 235 MB (23:21.28) = 105096 sectors
Lout start: 236 MB (23:23/21) = 105096 sectors
Blocks total: 336225 Blocks remaining: 336225
Starting to write CD at speed 2 in dummy mode for single session.
Last chance to quit, starting dummy write in 1 seconds.
Waiting for reader process to fill input-buffer ... input-buffer ready.
Starting new track at sector: 0
cdrecord: Success. write_g1: scsi sendcmd: retryable error
CDB: 2A 00 00 00 04 60 00 00 10 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: F0 00 03 00 00 00 00 19 00 0E 94 3C 0C 09 00 00 00 00
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x0C Qual 0x09 (write error - loss of streaming) Fru 0x0
Sense flags: Blk 0 (valid)
cmd finished after 0.493s timeout 40s
write track data: error after 2293760 bytes
Sense Bytes: F0 00 00 00 00 00 00 19 00 0E 98 ED 00 00 00 00 00 00
Writing time: 19.735s
Fixating...
WARNING: Some drives don't like fixation in dummy mode.
Fixating time: 124.712s
cdrecord: fifo had 198 puts and 71 gets.
cdrecord: fifo was 0 times empty and 3 times full, min fill was 63%.
Command exited with non-zero status 254
0.09user 12.38system 2:38.40elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1255major+1063minor)pagefaults 0swaps
Did I make somthing wrongly? What is the problem then?
I heard, there were problems with this paride version with are solved in a
patch you sent to the list and witch will be included in the 2.0.36 kernel.
Can I have this patch if this is the point?
Finally, I tried to use de xcdroast interface but it ask for a sg driver. How
can I make it recognize the pg driver compiled in cdrecord?
Thank you for your bothering
Regards
-- Ramiro Alba Laboratori de Termotecnia i EnergeticaDepartament de Maquines i Motors Termics ETS d'Enginyers Industrials de Terrassa
C/Colom 11
Tf: 34 - 93 739 82 43 Fax: 34 - 93 739 81 01
e-mail: ramiro@labtie.mmt.upc.es
This archive was generated by hypermail 2.0b3 on Wed 30 Dec 1998 - 10:18:44 EST