Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just found some info about my DVD player from Kinfocenter. When I clicked on CD Rom information, the entry said, CD Rom information ld, and in the list was:
Can write DVD-R and under the value for hdd and hdc was set to 0 0
Can write DVD-RAM and that value was also set to 0 0
0 means, "no" or "off", right?
I've asked a number of questions (thread here: http://www.linuxquestions.org/questi...o-dvds-554399/) of why I couldn't burn DVD's with my Sony DVD burner (SONY DVD+RW DRU-120A 1.51) -- could this be the reason why? Can this be changed? I'm pretty sure that this DVD player/burner was able to make DVD's when it was installed in the Windows computer.
cdrecord -prcap hdc
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
cdrecord: No CD/DVD-Recorder device specified.
Usage: cdrecord [options] track1...trackn
Use cdrecord -help
to get a list of valid options.
Use cdrecord blank=help
to get a list of valid blanking options.
Use cdrecord dev=b,t,l driveropts=help -checkdrive
to get a list of drive specific options.
Use cdrecord dev=help
to get a list of possible SCSI transport specifiers.
All the stuff for showing mounted and unmounted DVD media is checked off in in the KDE control center.
When I put a blank DVD+R in the drive and on the desktop, right click (after a few seconds) I see a mount command but no unmount. The "properties" says, unmounted but k3b recognizes that there is media present and says what it is (DVD+R).
My version of k3b is 1.0.1. I didn't know that they have 1.0.4. I just tried checking and there is no k3b 1.0.4 for my system. They are all for 10.2+ and I have 10.0.
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790
Rep:
I said exactly cdrecord -prcap do not add anything to the command please.
Example output:
Code:
$ cdrecord -prcap
Cdrecord-Clone 2.01 (cpu-pc-linux-gnu) Copyright (C) 1995-2004 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 http://bugzilla.redhat.com/bugzilla
Note: The author of cdrecord should not be bothered with problems in this version.
scsidev: '/dev/cdrom'
devname: '/dev/cdrom'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling').
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'PIONEER '
Identifikation : 'DVD-RW DVR-K16RS'
Revision : '1.39'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Drive capabilities, per MMC-3 page 2A:
Does read CD-R media
Does write CD-R media
Does read CD-RW media
Does write CD-RW media
Does read DVD-ROM media
Does read DVD-R media
Does write DVD-R media
Does read DVD-RAM media
Does write DVD-RAM media
Does support test writing
Does read Mode 2 Form 1 blocks
Does read Mode 2 Form 2 blocks
Does read digital audio blocks
Does restart non-streamed digital audio reads accurately
Does support Buffer-Underrun-Free recording
Does read multi-session CDs
Does read fixed-packet CD media using Method 2
Does not read CD bar code
Does not read R-W subcode information
Does read raw P-W subcode data from lead in
Does return CD media catalog number
Does return CD ISRC information
Does not support C2 error pointers
Does not deliver composite A/V data
Does play audio CDs
Number of volume control levels: 256
Does support individual volume control setting for each channel
Does support independent mute setting for each channel
Does not support digital output on port 1
Does not support digital output on port 2
Loading mechanism type: tray
Does support ejection of CD via START/STOP command
Does not lock media on power up via prevent jumper
Does allow media to be locked in the drive via PREVENT/ALLOW command
Is not currently in a media-locked state
Does not support changing side of disk
Does not have load-empty-slot-in-changer feature
Does not support Individual Disk Present feature
Maximum read speed: 4233 kB/s (CD 24x, DVD 3x)
Current read speed: 4233 kB/s (CD 24x, DVD 3x)
Maximum write speed: 4233 kB/s (CD 24x, DVD 3x)
Current write speed: 4233 kB/s (CD 24x, DVD 3x)
Rotational control selected: CLV/PCAV
Buffer size in KB: 2000
Copy management revision supported: 1
Number of supported write speeds: 5
Write speed # 0: 4233 kB/s CLV/PCAV (CD 24x, DVD 3x)
Write speed # 1: 3528 kB/s CLV/PCAV (CD 20x, DVD 2x)
Write speed # 2: 2822 kB/s CLV/PCAV (CD 16x, DVD 2x)
Write speed # 3: 1764 kB/s CLV/PCAV (CD 10x, DVD 1x)
Write speed # 4: 705 kB/s CLV/PCAV (CD 4x, DVD 0x)
I don't get any of that nice readout on my system. This is the result of the command:
Code:
cdrecord: No CD/DVD-Recorder device specified.
Usage: cdrecord [options] track1...trackn
Use cdrecord -help
to get a list of valid options.
Use cdrecord blank=help
to get a list of valid blanking options.
Use cdrecord dev=b,t,l driveropts=help -checkdrive
to get a list of drive specific options.
Use cdrecord dev=help
to get a list of possible SCSI transport specifiers.
That's why I added the hdc because it told me, "No cd/dvd-recorder device specified" so I thought I had to do that.
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790
Rep:
What does the typed commands show;
cdrecord -scanbus
ls -al /dev/cdrom
ls -al /dev/cdrom0
ls -al /dev/cdrom1
Something is not right, the cdrecord -prcap should have produced a nice output like the example I posted. here is an excerpt from the typed command man cdrecord;
Quote:
-prcap Print the drive capabilities for SCSI-3/mmc compliant drives as
obtained from mode page 0x2A. Values marked with kB use 1000
bytes as kilo-byte, values marked with KB use 1024 bytes as
Kilo-byte.
-inq Do an inquiry for the drive, print the inquiry info and exit.
-scanbus
Scan all SCSI devices on all SCSI busses and print the inquiry
strings. This option may be used to find SCSI address of the
CD/DVD-Recorder on a system. The numbers printed out as labels
are computed by: bus * 100 + target
These are the results of the above commands:
cdrecord -scanbus ls /dev/cdrom
Code:
cdrecord -scanbus ls /dev/cdrom
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
cdrecord: No tracks allowed with this option
Usage: cdrecord [options] track1...trackn
Use cdrecord -help
to get a list of valid options.
Use cdrecord blank=help
to get a list of valid blanking options.
Use cdrecord dev=b,t,l driveropts=help -checkdrive
to get a list of drive specific options.
Use cdrecord dev=help
to get a list of possible SCSI transport specifiers.
cdrecord -scanbus ls -al /dev/cdrom
Code:
cdrecord -scanbus ls -al /dev/cdrom
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
cdrecord: Bad Option: -al.
Usage: cdrecord [options] track1...trackn
Use cdrecord -help
to get a list of valid options.
Use cdrecord blank=help
to get a list of valid blanking options.
Use cdrecord dev=b,t,l driveropts=help -checkdrive
to get a list of drive specific options.
Use cdrecord dev=help
to get a list of possible SCSI transport specifiers.
cdrecord -scanbus
Code:
cdrecord -scanbus
Cdrecord-Clone 2.01 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling
Note: This version is an unofficial (modified) version
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to http://www.suse.de/feedback
Note: The author of cdrecord should not be bothered with problems in this version.
Linux sg driver version: 3.5.33
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de-scsi-linux-sg.c-1.83-resmgr-patch '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling').
scsibus2:
2,0,0 200) 'Generic ' 'USB SD Reader ' '2.00' Removable Disk
2,1,0 201) *
2,2,0 202) *
2,3,0 203) *
2,4,0 204) *
2,5,0 205) *
2,6,0 206) *
2,7,0 207) *
It looks like scanbus or cdrecord does not see my cdrom/dvd drives but k3b knows they're there and so does the system because I can play dvd's just fine and I can record to CD-R's just fine.
Notice the device hdc is the cd/dvd rom. If your device is a sata then replace the command with 'dmesg |grep -i sd'.
If the hardware was recognized at boot by the kernel then you should be able to access. Do you have your user(s) in the proper group? Are you performing the commands as 'root'?
Cdrecord-Clone 2.01 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling
Note: This version is an unofficial (modified) version
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to http://www.suse.de/feedback
Note: The author of cdrecord should not be bothered with problems in this version.
scsidev: 'ATAPI'
devname: 'ATAPI'
scsibus: -2 target: -2 lun: -2
Warning: Using ATA Packet interface.
Warning: The related Linux kernel interface code seems to be unmaintained.
Warning: There is absolutely NO DMA, operations thus are slow.
cdrecord: No such file or directory. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
cdrdao scanbus
Code:
Cdrdao version 1.2.0 - (C) Andreas Mueller <andreas@daneb.de>
SCSI interface library - (C) Joerg Schilling
Paranoia DAE library - (C) Monty
Check http://cdrdao.sourceforge.net/drives.html#dt for current driver tables.
Using libscg version 'schily-0.8'
ATA:1,0,0 SONY , DVD+RW DRU-120A, 1.51
ATA:1,1,0 RICOH , CD-R/RW MP7040A , 1.40
I can't upgrade to the latest k3b because there are no rpm's available for SuSE 10.0. I like using rpm's because YaST works out the dependencies so I don't have to deal with them. My system is considered "old" by Novell's standards it seems. I just installed it 2 years ago. I was hoping that this computer would last for me longer than the Windows computers (being able to get updates, program packages, etc). I guess I must be wrong about that.
---
Hello onebuck,
The distro I'm using is SuSE 10.0
uname -a is one command I can remember. Here's the result:
Linux linux 2.6.13-15.15-smp #1 SMP Mon Feb 26 14:11:33 UTC 2007 i686 i686 i386 GNU/Linux
So, here's the result of dmesg |grep -i hd:
Code:
Kernel command line: root=/dev/hda2 vga=0x317 selinux=0 resume=/dev/hda1 splash=silent
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA
hda: WDC WD800JB-00CRA1, ATA DISK drive
hda: max request size: 128KiB
hda: 156301488 sectors (80026 MB) w/8192KiB Cache, CHS=65535/16/63, UDMA(100)
hda: cache flushes not supported
hda: hda1 hda2
hdc: SONY DVD+RW DRU-120A, ATAPI CD/DVD-ROM drive
hdd: RICOH CD-R/RW MP7040A, ATAPI CD/DVD-ROM drive
hdc: ATAPI 32X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
hdd: ATAPI 20X CD-ROM CD-R/RW drive, 2048kB Cache, DMA
ReiserFS: hda2: found reiserfs format "3.6" with standard journal
ReiserFS: hda2: using ordered data mode
ReiserFS: hda2: journal params: device hda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda2: checking transaction log (hda2)
ReiserFS: hda2: Using r5 hash to sort names
Adding 1028120k swap on /dev/hda1. Priority:-1 extents:1
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
I suggest using SCSI emulation. You will need to modify the bootloader and add hdc=ide-scsi and hdd=ide-scsi. Your drives will not have a device ID of /dev/scd0 and /dev/scd1. You will need to change the fstab file and your applications to reflect the new device IDs. Your version of cdrecord does not support ATAPI devices without the SCSI emulation.
The need for SCSI emulation was eliminated with the 2.6 kernels but this is a fairly early kernel version and there still might of been some problems. I'm sure others will chime in to help fill in the details.
cat /usr/src/linux/.config |grep -i idecd
CONFIG_BLK_DEV_IDECD=y <--- this indicates the
IDECD is static
With 2.6 the idecd is the current means to handle the atapi device. The ide-scsi is deprecated. Your devices are recognized. You could roll back to a previous cdrecord to see if that helps. Some 2.6.21 kernel users have experienced problems with cdrecord and corrected by a roll back to a previous cdrecord version.
Quote:
Originally Posted by gymnart
I can't upgrade to the latest k3b because there are no rpm's available for SuSE 10.0. I like using rpm's because YaST works out the dependencies so I don't have to deal with them. My system is considered "old" by Novell's standards it seems. I just installed it 2 years ago. I was hoping that this computer would last for me longer than the Windows computers (being able to get updates, program packages, etc). I guess I must be wrong about that.
I don't use SUSE for the reason that you don't control it. It controls you via Novell just like the way M$ attempts to. I really don't like Novell either. I used and maintained Novell for years but wouldn't touch it again.
Just like any tool, SUSE is that. Some like the feel and the OS meets the needs of that user. I just like to control my systems. That's why I use Slackware. No dependency nightmares for me.
Last edited by onebuck; 12-01-2007 at 01:53 PM.
Reason: grammar
No, I did not compile a new kernel. I have updated it with the YOU tool a few times though and the last time that was done, the module responsible for my being able to use Kino for capturing video from my camcorder has not worked properly since. I haven't updated it since then because of now having to re-install my Nvidia graphics card driver and I don't feel like having the deal with that again.
Here are the results of the command cat /usr/src/linux/.config |grep -i idecd:
Code:
cat: /usr/src/linux/.config: No such file or directory
Quote:
That's why I use Slackware. No dependency nightmares for me.
So, you can just install stuff and that's it? No busted apps? If something did break, how would you track down what went wrong and fix it?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.