I just got a Dell Dimension e521 (AMD 64 x2, nVidia MCP51 chipset) and
so far it has been fine. Today I tried to burn some CD-R and DVD-R
disks and have been able to do nothing but make coasters. The drive is
a TSST TS-H653a (Samsung OEM) and does have the current firmware.
Playing back data, audio, and video disks work just fine, but recording
is a different matter.
The drive shows up as /dev/scd0 and all the symlinks for /dev/cdrom,
/dev/cdwriter, /dev/dvd, and /dev/dvdwriter point to that device. Both
cdrecord and growisofs complete without any errors, but when I try to
remount the just-recorded disk I get an error:
[jleafey at jaybird Downloads]$ mount /media/cdrecorder/
/dev/scd0: Invalid argument
mount: block device /dev/scd0 is write-protected, mounting read-only
/dev/scd0: Invalid argument
mount: I could not determine the filesystem type, and none was specified
I have also tried to explicitly mount it specifying the device and fs type:
[jleafey at jaybird Downloads]$ sudo mount -t iso9660 /dev/scd0 \
/media/cdrecorder/
mount: block device /dev/scd0 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/scd0,
or too many mounted file systems
The output of dmesg shows the message "cdrom: This disc doesn't have
any
tracks I recognize!" when this happens.
Since I also get an error on the eject command UNLESS RUN AS ROOT
(eject: unable to eject, last error: Inappropriate ioctl for device) I
thought it might be a permission problem, but the device (/dev/scd0) is
showing up as being "owned" by me, courtesy of Gnome no doubt. I get
the bad burns whether I run as root or a regular user.
At this point I don't know whether to think the problem is with cdrecord
or the sata_nv driver. Anybody got any ideas on where to look next?
Thanks!
--
Jay Leafey - Memphis, TN
jay.leafey at mindless.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4011 bytes
Desc: S/MIME Cryptographic Signature
URL:
<http://lists.centos.org/pipermail/centos/attachments/20070403/c1dc603a/attachment-0004.bin>
On Tue, 3 Apr 2007, Jay Leafey wrote:> I just got a Dell Dimension e521 (AMD 64 x2, nVidia MCP51 chipset)I seem to have this as well, recently purchased: [root at amd64 ~]# cdrecord --scanbus ... scsibus1: 1,0,0 100) 'TSSTcorp' 'DVD+-RW TS-H553A' 'DE04' Removable CD-ROM ... [root at amd64 ~]# /sbin/lspci -v | grep -i MCP51 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3) 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3) 00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3) and in the dmesg: Vendor: TSSTcorp Model: DVD+-RW TS-H553A Rev: DE04 Type: CD-ROM ANSI SCSI revision: 05 ... and later ... sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 Attached scsi CD-ROM sr0 at scsi1, channel 0, id 0, lun 0 I remember being surprised seeing a SATA CD drive i it when I popped it open to remove (the never powered up) proprietary OS tax hard drive, and dropping in a Seagate with a five year warranty ;)> The drive shows up as /dev/scd0 and all the symlinks for /dev/cdrom,hmm -- I'll check tomorrow, but I would suspect, from the following, that it can be used at the TUI command line by root by cdrecord (I actually rarely burn media, but it was included in the price that I got from Dell), with the setting of: dev='1,0,0' and an iso image, etc. [root at amd64 proc]# cdrecord dev='1,0,0' driveropts=help -checkdrive ... scsidev: '1,0,0' scsibus: 1 target: 0 lun: 0 Linux sg driver version: 3.5.27 Using libscg version 'schily-0.8'. cdrecord: Warning: using inofficial libscg transport code version (schily - RedHat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright1997 J. Schilling'). Device type : Removable CD-ROM Version : 5 Response Format: 2 Capabilities : Vendor_info : 'TSSTcorp' Identifikation : 'DVD+-RW TS-H553A' Revision : 'DE04' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Driver options: burnfree Prepare writer to use BURN-Free technology noburnfree Disable using BURN-Free technology [root at amd64 proc]# -- Russ Herrold
Jay Leafey wrote:> I just got a Dell Dimension e521 (AMD 64 x2, nVidia MCP51 chipset) and > so far it has been fine. Today I tried to burn some CD-R and DVD-R > disks and have been able to do nothing but make coasters. The drive is > a TSST TS-H653a (Samsung OEM) and does have the current firmware. > Playing back data, audio, and video disks work just fine, but recording > is a different matter. > > The drive shows up as /dev/scd0 and all the symlinks for /dev/cdrom, > /dev/cdwriter, /dev/dvd, and /dev/dvdwriter point to that device. Both > cdrecord and growisofs complete without any errors, but when I try to > remount the just-recorded disk I get an error: > > [jleafey at jaybird Downloads]$ mount /media/cdrecorder/ > /dev/scd0: Invalid argument > mount: block device /dev/scd0 is write-protected, mounting read-only > /dev/scd0: Invalid argument > mount: I could not determine the filesystem type, and none was specified > > I have also tried to explicitly mount it specifying the device and fs type: > > [jleafey at jaybird Downloads]$ sudo mount -t iso9660 /dev/scd0 \ > /media/cdrecorder/ > mount: block device /dev/scd0 is write-protected, mounting read-only > mount: wrong fs type, bad option, bad superblock on /dev/scd0, > or too many mounted file systems > > The output of dmesg shows the message "cdrom: This disc doesn't have any > tracks I recognize!" when this happens. > > Since I also get an error on the eject command UNLESS RUN AS ROOT > (eject: unable to eject, last error: Inappropriate ioctl for device) I > thought it might be a permission problem, but the device (/dev/scd0) is > showing up as being "owned" by me, courtesy of Gnome no doubt. I get > the bad burns whether I run as root or a regular user. > > At this point I don't know whether to think the problem is with cdrecord > or the sata_nv driver. Anybody got any ideas on where to look next?On one of my systems with an AM2 MCP51 motherboard, I had some problems with it handling the SATA disk, so I built and installed the most recent (at that time) kernel [2.6.20.1]. That seems to solve both my onboard gigabit nic and the sata_nv problems. --peter gross