Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.hardware > #1280 > unrolled thread

Installing Optiarc drive

Back to article view | Back to comp.os.linux.hardware

Contents

  Installing Optiarc drive Haines Brown <haines@histomat.net> - 2012-06-28 16:37 -0400
    Re: Installing Optiarc drive J G Miller <miller@yoyo.ORG> - 2012-06-28 21:15 +0000
      Re: Installing Optiarc drive Thad Floryan <thad@thadlabs.com> - 2012-06-28 21:57 -0700
        Re: Installing Optiarc drive J G Miller <miller@yoyo.ORG> - 2012-06-29 08:57 +0000
          Re: Installing Optiarc drive Chris Davies <chris-usenet@roaima.co.uk> - 2012-06-29 10:39 +0100
            Re: Installing Optiarc drive J G Miller <miller@yoyo.ORG> - 2012-06-29 10:06 +0000
            Re: Installing Optiarc drive Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2012-06-30 20:41 -0600
          Re: Installing Optiarc drive Richard Kettlewell <rjk@greenend.org.uk> - 2012-06-29 11:24 +0100
            Re: Installing Optiarc drive J G Miller <miller@yoyo.ORG> - 2012-06-29 12:01 +0000
      Re: Installing Optiarc drive Haines Brown <haines@histomat.net> - 2012-06-29 06:26 -0400
        Re: Installing Optiarc drive Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2012-06-30 20:53 -0600
          Re: Installing Optiarc drive Haines Brown <haines@histomat.net> - 2012-07-01 17:57 -0400
      Re: Installing Optiarc drive Haines Brown <haines@histomat.net> - 2012-06-29 07:37 -0400
        Re: Installing Optiarc drive J G Miller <miller@yoyo.ORG> - 2012-06-29 12:40 +0000
          Re: Installing Optiarc drive Haines Brown <haines@histomat.net> - 2012-07-01 18:04 -0400
            Re: Installing Optiarc drive J G Miller <miller@yoyo.ORG> - 2012-07-01 22:57 +0000
        Re: Installing Optiarc drive "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2012-06-29 17:16 -0400
          Re: Installing Optiarc drive Haines Brown <haines@histomat.net> - 2012-07-01 18:57 -0400
            Re: Installing Optiarc drive J G Miller <miller@yoyo.ORG> - 2012-07-02 09:32 +0000
              Re: Installing Optiarc drive Haines Brown <haines@histomat.net> - 2012-07-02 10:44 -0400
                Re: Installing Optiarc drive J G Miller <miller@yoyo.ORG> - 2012-07-02 15:44 +0000
                  Re: Installing Optiarc drive Haines Brown <haines@histomat.net> - 2012-07-04 12:38 -0400
                    Re: Installing Optiarc drive J G Miller <miller@yoyo.ORG> - 2012-07-04 16:52 +0000
        Re: Installing Optiarc drive Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2012-06-30 20:59 -0600
    Re: Installing Optiarc drive Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2012-06-30 20:49 -0600

Page 1 of 2  [1] 2  Next page →

#1280 — Installing Optiarc drive

For a long time I've been unable to get an Optiarc AD-7240S drive to
play CDs or DVDs and dmesg does not indicate any driver interface
file is loaded. 

I found the Optiarc driver web site by searching for "Debian Optiarc
Driver." Sure enough there is a driver page, and the first step to
install the current driver for my AD-7240S is: 

  "Choice 1:  Automatic Download and Update Debian Optiarc Driver"

It turns out that the last three words simply copy my search term, for
this installer file is named setup.exe, and $ file tells me it is a
Windows executable. Naturally I can't do anything with it.

  "Choice 3:  Enter the product name or number directly:"

When I enter my drive model it reports "we have found the driver for
AD-7240S; Download!" However, what gets downloaded is not a driver for
linux, but just the Windows setup.exe file again.

It turns out that Optiarc driver site drivers are in fact Windows only.
Isn't it true that Debian Etch should be expected to come with a driver
to support an older standard DVD drive?

How do I find out if so, and what is its name is so that I can load it?
And what driver interface file is it likely to use? I had assumed it
would be /dev/sr0 for an audio CD and or /dev/dvd4 for a DVD disk in the
drive. 

Soundcore module is loaded but not used, and so not surprisingly:

    $ cdplay -d /dev/sr0
    cdplay: ioctl cdromplaymsf: Operation not supported

    $ cdplay -d /dev/dvd4
    cdplay: ioctl cdromplaymsf: Operation not supported


Haines Brown

[toc] | [next] | [standalone]

#1281

On Thursday, June 28th, 2012, at 16:37:27h -0400, Haines Brown wrote:

> For a long time I've been unable to get an Optiarc AD-7240S drive to
> play CDs or DVDs and dmesg does not indicate any driver interface
> file is loaded. 

Does dmesg indicate the presence of the drive at all?

What is the output of the command  run as root

        lshw -C disk

> Isn't it true that Debian Etch should be expected to come with a driver
> to support an older standard DVD drive?

No -- "drivers" are a Windoze thing.

[toc] | [prev] | [next] | [standalone]

#1282

On 6/28/2012 2:15 PM, J G Miller wrote:
>> [...]
>> Isn't it true that Debian Etch should be expected to come with a driver
>> to support an older standard DVD drive?
> 
> No -- "drivers" are a Windoze thing.

Oh?  Then why are there books such as the following (for just one
simple example):

"Linux Device Drivers", 3rd Edition:

http://lwn.net/Kernel/LDD3/

tarball of the PDF files:

http://lwn.net/images/pdf/LDD3/ldd3_pdf.tar.bz2

individual PDFs:

http://lwn.net/images/pdf/LDD3/TITLE.pdf        Title page
http://lwn.net/images/pdf/LDD3/COPYRIGHT.pdf    Copyright and credits
http://lwn.net/images/pdf/LDD3/ldr3TOC.fm.pdf   Table of Contents
http://lwn.net/images/pdf/LDD3/ch00.pdf         Preface
http://lwn.net/images/pdf/LDD3/ch01.pdf         Chapter 1: An Introduction to Device Drivers
http://lwn.net/images/pdf/LDD3/ch02.pdf         Chapter 2: Building and Running Modules
http://lwn.net/images/pdf/LDD3/ch03.pdf         Chapter 3: Char Drivers
http://lwn.net/images/pdf/LDD3/ch04.pdf         Chapter 4: Debugging Techniques
http://lwn.net/images/pdf/LDD3/ch05.pdf         Chapter 5: Concurrency and Race Conditions
http://lwn.net/images/pdf/LDD3/ch06.pdf         Chapter 6: Advanced Char Driver Operations
http://lwn.net/images/pdf/LDD3/ch07.pdf         Chapter 7: Time, Delays, and Deferred Work
http://lwn.net/images/pdf/LDD3/ch08.pdf         Chapter 8: Allocating Memory
http://lwn.net/images/pdf/LDD3/ch09.pdf         Chapter 9: Communicating with Hardware
http://lwn.net/images/pdf/LDD3/ch10.pdf         Chapter 10: Interrupt Handling
http://lwn.net/images/pdf/LDD3/ch11.pdf         Chapter 11: Data Types in the Kernel
http://lwn.net/images/pdf/LDD3/ch12.pdf         Chapter 12: PCI Drivers
http://lwn.net/images/pdf/LDD3/ch13.pdf         Chapter 13: USB Drivers
http://lwn.net/images/pdf/LDD3/ch14.pdf         Chapter 14: The Linux Device Model
http://lwn.net/images/pdf/LDD3/ch15.pdf         Chapter 15: Memory Mapping and DMA
http://lwn.net/images/pdf/LDD3/ch16.pdf         Chapter 16: Block Drivers
http://lwn.net/images/pdf/LDD3/ch17.pdf         Chapter 17: Network Drivers
http://lwn.net/images/pdf/LDD3/ch18.pdf         Chapter 18: TTY Drivers
http://lwn.net/images/pdf/LDD3/ldr3IX.fm.pdf    Index

[toc] | [prev] | [next] | [standalone]

#1283

On Thursday, June 28th, 2012, 21:57:37h -0700, Thad Floryan wrote:

> Then why are there books such as the following (for just one
> simple example):

Probably because they are written by somebody who comes from a 
Windoze background writing for people who come from a Windoze
background.

The Linux kernel has *modules* for providing hardware support.

Why do you think the directory is called /lib/modules
and not /lib/drivers?

Why is the user program called modprobe?

"modprobe - Add and remove modules from the Linux Kernel"

Just because some authors decide to use the wrong term,
does not mean that the term they use is correct.

[toc] | [prev] | [next] | [standalone]

#1284

J G Miller <miller@yoyo.org> wrote:
> The Linux kernel has *modules* for providing hardware support.

> Why do you think the directory is called /lib/modules
> and not /lib/drivers?

Modules are dynamically loadable pieces of the kernel. Depending on its
functionality, a module may (or may not) implement a device driver. A
device driver is the piece of code responsible for communicating at a
hardware level with a device.

See http://lwn.net/Kernel/LDD3/. I wouldn't want to try arguing with
the likes of Greg Kroah-Hartman.

Chris

[toc] | [prev] | [next] | [standalone]

#1285

On Friday, June 29th, 2012, at 10:39:07h +0100, Chris Davies wrote:

> Modules are dynamically loadable pieces of the kernel. Depending on its
> functionality, a module may (or may not) implement a device driver. A
> device driver is the piece of code responsible for communicating at a
> hardware level with a device.

So clearly in the context of discussion of the problem posted by
Haines Brown, it is not a question of drivers but of which module
is needed to provided functionality for his optical drive.

Probably libata.

[toc] | [prev] | [next] | [standalone]

#1295

Chris Davies <chris-usenet@roaima.co.uk> writes:

> J G Miller <miller@yoyo.org> wrote:
>> The Linux kernel has *modules* for providing hardware support.

It has modules for doing lots of things.  Some of them are device
drivers -- there is absolutely nothing Windows-specific about that
term.

>> Why do you think the directory is called /lib/modules
>> and not /lib/drivers?
>
> Modules are dynamically loadable pieces of the kernel. Depending on its
> functionality, a module may (or may not) implement a device driver. A
> device driver is the piece of code responsible for communicating at a
> hardware level with a device.
>
> See http://lwn.net/Kernel/LDD3/. I wouldn't want to try arguing with
> the likes of Greg Kroah-Hartman.

And, of course, it's possible for a device driver to be compiled-in, and
not a module.

[toc] | [prev] | [next] | [standalone]

#1286

J G Miller <miller@yoyo.ORG> writes:
> Thad Floryan wrote:

>> Then why are there books such as the following (for just one simple
>> example):
>
> Probably because they are written by somebody who comes from a 
> Windoze background writing for people who come from a Windoze
> background.

It's not a Windows-specific term at all.

> The Linux kernel has *modules* for providing hardware support.
>
> Why do you think the directory is called /lib/modules
> and not /lib/drivers?
>
> Why is the user program called modprobe?
>
> "modprobe - Add and remove modules from the Linux Kernel"

Modules are a means of delivering code to the kernel at runtime, not a
Linux-specific term for "driver".

> Just because some authors decide to use the wrong term,
> does not mean that the term they use is correct.

In this case, however, they didn't use the wrong term.

-- 
http://www.greenend.org.uk/rjk/

[toc] | [prev] | [next] | [standalone]

#1289

On Friday, June 29th, 2012, at 11:24:17h +0100, Richard Kettlewell explained:

> Modules are a means of delivering code to the kernel at runtime, not a
> Linux-specific term for "driver".

Thank you for making the distinction clear.

And do you have any intention of helping to resolve the
problem with the Optiarc device since you clearly understand
the finer details?

[toc] | [prev] | [next] | [standalone]

#1287

> On Thursday, June 28th, 2012, at 16:37:27h -0400, Haines Brown wrote:

> > For a long time I've been unable to get an Optiarc AD-7240S drive to
> > play CDs or DVDs and dmesg does not indicate any driver interface
> > file is loaded. 

> Does dmesg indicate the presence of the drive at all?

  scsi 0:0:1:0: CD-ROM   Optiarc  DVD RW AD-7240S  1.02 PQ: 0 ANSI: 5

What is the output of the command  run as root

        lshw -C disk

I don't have lshw installed because apptitude thinks my texlive2011 is
not configured and so all aptitude installations are blocked. My TL2011
works fine and I hesitate to reinstall it.

Sorry, I'm runing Debian Squeeze, not Etch.

Haines Brown

[toc] | [prev] | [next] | [standalone]

#1297

Haines Brown <haines@histomat.net> writes:

>> On Thursday, June 28th, 2012, at 16:37:27h -0400, Haines Brown wrote:
>
>> > For a long time I've been unable to get an Optiarc AD-7240S drive to
>> > play CDs or DVDs and dmesg does not indicate any driver interface
>> > file is loaded. 
>
>> Does dmesg indicate the presence of the drive at all?
>
>   scsi 0:0:1:0: CD-ROM   Optiarc  DVD RW AD-7240S  1.02 PQ: 0 ANSI: 5
>
> What is the output of the command  run as root
>
>         lshw -C disk
>
> I don't have lshw installed because apptitude thinks my texlive2011 is
> not configured and so all aptitude installations are blocked. My TL2011
> works fine and I hesitate to reinstall it.

You have much more serious problems than not being able to play CDs.
You need to figure out what's going on with package management and fix
it, so you can keep up to date.

> Sorry, I'm runing Debian Squeeze, not Etch.

Ah.  Never mind my earlier hypothesis.  It shouldn't be a driver
problem; your drive should work just fine with the standard SATA
drivers.

[toc] | [prev] | [next] | [standalone]

#1299

Joe Pfeiffer <pfeiffer@cs.nmsu.edu> writes:

> Haines Brown <haines@histomat.net> writes:
>
>>> On Thursday, June 28th, 2012, at 16:37:27h -0400, Haines Brown wrote:
>>
>>> > For a long time I've been unable to get an Optiarc AD-7240S drive to
>>> > play CDs or DVDs and dmesg does not indicate any driver interface
>>> > file is loaded. 
>>
>> I don't have lshw installed because apptitude thinks my texlive2011 is
>> not configured and so all aptitude installations are blocked. My TL2011
>> works fine and I hesitate to reinstall it.
>
> You have much more serious problems than not being able to play CDs.
> You need to figure out what's going on with package management and fix
> it, so you can keep up to date.

I should have provided more information. I run TL2012 from CTAN. When
I found out that it conflicted with my old debian installation of tl
2009, I removed it. But for some reason, my system still thought it was
installed but unconfigured. I removed it with aptitude. TL2011 works
fine, and I was able to install the lshw.

Hanies   
 

[toc] | [prev] | [next] | [standalone]

#1288

J G Miller <miller@yoyo.ORG> writes:

> On Thursday, June 28th, 2012, at 16:37:27h -0400, Haines Brown wrote:
>
>> For a long time I've been unable to get an Optiarc AD-7240S drive to
>> play CDs or DVDs and dmesg does not indicate any driver interface
>> file is loaded. 

> What is the output of the command  run as root
>
>         lshw -C disk

In frustration, I purged texlive and so was able to install lshw. This
is what it shows:

  *-cdrom
       description: DVD-RAM writer
       product: DVD RW AD-7240S
       vendor: Optiarc
       physical id: 0.1.0
       bus info: scsi@0:0.1.0
       logical name: /dev/cdrom4
       logical name: /dev/cdrw4
       logical name: /dev/dvd4
       logical name: /dev/dvdrw4
       logical name: /dev/scd0
       logical name: /dev/sr0
       version: 1.02
       capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
       configuration: ansiversion=5 status=ready
     *-medium
          physical id: 0
          logical name: /dev/cdrom4

This cdrom4 is a symlink to sr0. 

But I'm still in the dark about whether a driver for this drive is being
loaded.

Incidentally, the term "driver" I believe originated with Unix in 1960s
and by ca. 1970 was becoming a standard computer term. I don't recall
from my VAX days whether "drivers" were involved, but I seem to remember
that DOS used the term. Could it be that "device driver" is conventional
(not specific to Microsoft), and "module" popped up at some point for
some reason with Linux? I get the impression the term driver was used in
MINIX, but I'm ignorant about such things. Did Linus T. borrow the term
"module" from how MINIX characterized its microkernel, a technology he
rejected?

Haines Brown

[toc] | [prev] | [next] | [standalone]

#1290

On Friday, June 29th, 2012, at 07:37:50h -0400, Haines Brown wrote:

> In frustration, I purged texlive and so was able to install lshw.

I do not understand why you would need to purge texlive in order
to install lshw.

They both happily coexist on this Debian testing machine.

dpkg -l texlive
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                               Version                            Description
+++-==================================-==================================-====================================================================================
ii  texlive                            2012.20120611-1                    TeX Live: A decent selection of the TeX Live packages

dpkg -l lshw
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                               Version                            Description
+++-==================================-==================================-====================================================================================
ii  lshw                               02.15-2                            information about hardware configuration


> This is what it shows:
> 
>   *-cdrom
>        description: DVD-RAM writer
>        product: DVD RW AD-7240S
>        vendor: Optiarc
>        physical id: 0.1.0
>        bus info: scsi@0:0.1.0
>        logical name: /dev/cdrom4
>        logical name: /dev/cdrw4
>        logical name: /dev/dvd4
>        logical name: /dev/dvdrw4
>        logical name: /dev/scd0
>        logical name: /dev/sr0
>        version: 1.02
>        capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
>        configuration: ansiversion=5 status=ready
>      *-medium
>           physical id: 0
>           logical name: /dev/cdrom4
> 
> This cdrom4 is a symlink to sr0.

So obviously your device is seen by the kernel, and udev has
created some convenience symbolic links.

> But I'm still in the dark about whether a driver for this drive is being
> loaded.

The kernel loads modules.

What happens when you insert a data CD into the drive and try to mount it,
if /mnt/tmp does not exist then create  /mnt/tmp and try

       mount -t iso9660 /dev/sr0 /mnt/tmp

after you insert a data CD with iso9660 file system into the drive?

[toc] | [prev] | [next] | [standalone]

#1300

J G Miller <miller@yoyo.ORG> writes:

> What happens when you insert a data CD into the drive and try to mount
> it, if /mnt/tmp does not exist then create /mnt/tmp and try
>
>        mount -t iso9660 /dev/sr0 /mnt/tmp
>
> after you insert a data CD with iso9660 file system into the drive?

No problem. I can mount and access the files on the data CD.

Haines

[toc] | [prev] | [next] | [standalone]

#1301

On Sunday, July 1st, 2012, at 18:04:47h -0400, Haines Brown wrote:

> I can mount and access the files on the data CD.

So then your DVD drive is fully functional and will
no doubt be made accessible through the kernel libata
module.

  <https://ata.wiki.kernel.ORG/index.php/Main_Page>
 

Now if you want to play CDs on the device, you should
alter the udev rules so that instead of creating the convenience
link cdrom4 it creates cdrom, and instead of dvd4 it creates the
convenience link dvd as suggested by another poster.


Here is part of my /etc/udev/rules.d/70-persistent-cd.rules
for doing just that

SUBSYSTEM=="block",     ENV{GENERATED}="1", ENV{ID_CDROM}=="?*",       \
                        ENV{ID_PATH}=="pci-0000:00:04.1-scsi-1:0:0:0", \
                        SYMLINK+="cdrom"
#
SUBSYSTEM=="block",     ENV{GENERATED}="1", ENV{ID_CDROM}=="?*",       \
                        ENV{ID_PATH}=="pci-0000:00:04.1-scsi-1:0:0:0", \
                        SYMLINK+="cdtooldev"
#
SUBSYSTEM=="block",     ENV{GENERATED}="1", ENV{ID_CDROM}=="?*",       \
                        ENV{ID_PATH}=="pci-0000:00:04.1-scsi-1:0:0:0", \
                        SYMLINK+="dvd"


Obviously you need to replace  "pci-0000:00:04.1-scsi-1:0:0:0"
with the appropriate string for you machine which can be found
by doing

   ls  /dev/disk/by-path/  | egrep sr0

The cdtooldev link is used by the command line cdplay program.

And remember for you to be able to hear the CD, if you use a non
digital audio extraction CD player software program, you will
need to connect preferably a digital SPDIF audio cable from your
Optiarc device to the digital IN on your sound card or onboard
sound device.  If that does not have digital in, then it will
have to be an analog cable to the CDROM in connector if your
sound device has such.

The version of xmcd supplied by Debian does not have DAE,
so such an audio cable (for analog or digital connection)
is necessary.

And obviously do not forget to adjust the mixer level
appropriately in alsamixer for the CD analog input
or digital SPDIF input.

For playback of DVDs, if they are commercial disks (encrypted),
then you will need to install libdvdcss2.

Probably the best program for playback of DVDs because of its
support for menus, is vlc.

[toc] | [prev] | [next] | [standalone]

#1291

On Fri, 29 Jun 2012 07:37:50 -0400, Haines Brown <haines@histomat.net> wrote:

>   *-cdrom
>        description: DVD-RAM writer
>        product: DVD RW AD-7240S
>        vendor: Optiarc
>        physical id: 0.1.0
>        bus info: scsi@0:0.1.0
>        logical name: /dev/cdrom4
>        logical name: /dev/cdrw4
>        logical name: /dev/dvd4
>        logical name: /dev/dvdrw4
>        logical name: /dev/scd0
>        logical name: /dev/sr0

The problem may be that the program you are using is only looking for /dev/cdrom
rather then /dev/cdrom4.

If this is the only drive remove all of the non-comment lines from
/etc/udev/rules.d/70-persistent-cd.rules and reboot.  Then the symlinks created by
udev should be /dev/cdrom->/dev/sr0.

I'm using Mageia linux, so the location of the file or the exact name may be different.

Btw, regarding the driver, linux doesn't use a driver/module for the drive.  It uses a
module for the controller the drive is connected to.

Regards, Dave Hodgins

-- 
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

[toc] | [prev] | [next] | [standalone]

#1302

"David W. Hodgins" <dwhodgins@nomail.afraid.org> writes:

> The problem may be that the program you are using is only looking for
> /dev/cdrom rather then /dev/cdrom4.

To reconfigure udev at this point requires a reboot, and that would
interfere too much with my work. Later, maybe.

The program I'm using, cdpay, can take an option to specify the
interface:

        # cdplay -d /dev/sr0
        cdplay: ioctl cdromplaymsf: Operation not supported

I debug:
        # cdplay -d /dev/sr0 -D
        cdplay: reading track 1 tocentry
        cdplay: reading track 2 tocentry
        ...
        cdplay: reading track 9 tocentry
        cdplay: reading track 170 tocentry
        do_play:  called, trk0=0, trk1=0
        do_play:  trk[0.1]==0, status=0
        cdplay: ioctl subchnl: INVALID
        cdplay: ioctl cdromplaymsf: Operation not supported

I try # xfreecd and configure it to use /dev/sr0. However, it only says
"No Disk". When I click Play, the LED on the drive does not go on.

A trace for cdplay -d /dev/sr0:

  execve("/usr/bin/cdplay", ["cdplay", "-d", "/dev/sr0"], [/* 27 vars */]) = 0
  brk(0)                                  = 0x84cf000
  access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
  mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb77da000
  access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
  open("/etc/ld.so.cache", O_RDONLY)      = 3
  fstat64(3, {st_mode=S_IFREG|0644, st_size=72023, ...}) = 0
  mmap2(NULL, 72023, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb77c8000
  close(3)                                = 0
  access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
  open("/lib/i686/cmov/libc.so.6", O_RDONLY) = 3
  read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0n\1\0004\0\0\0"..., 512) = 512
  fstat64(3, {st_mode=S_IFREG|0755, st_size=1327556, ...}) = 0
  mmap2(NULL, 1337704, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7681000
  mprotect(0xb77c1000, 4096, PROT_NONE)   = 0
  mmap2(0xb77c2000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x140) = 0xb77c2000
  mmap2(0xb77c5000, 10600, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb77c5000
  close(3)                                = 0
  mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7680000
  set_thread_area({entry_number:-1 -> 6, base_addr:0xb76806c0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0
  mprotect(0xb77c2000, 8192, PROT_READ)   = 0
  mprotect(0xb77f8000, 4096, PROT_READ)   = 0
  munmap(0xb77c8000, 72023)               = 0
  stat64("/dev/sr0", {st_mode=S_IFBLK|0660, st_rdev=makedev(11, 0), ...}) = 0
  open("/dev/sr0", O_RDONLY|O_NONBLOCK)   = 3
  brk(0)                                  = 0x84cf000
  brk(0x84f0000)                          = 0x84f0000
  ioctl(3, CDROMSUBCHNL, 0x84cf4c8)       = 0
  ioctl(3, CDROMREADTOCHDR, 0x84cf014)    = 0
  ioctl(3, CDROMREADTOCENTRY, 0x84cf018)  = 0
  ioctl(3, CDROMREADTOCENTRY, 0x84cf024)  = 0
  ioctl(3, CDROMREADTOCENTRY, 0x84cf030)  = 0
  ioctl(3, CDROMREADTOCENTRY, 0x84cf03c)  = 0
  ioctl(3, CDROMREADTOCENTRY, 0x84cf048)  = 0
  ioctl(3, CDROMREADTOCENTRY, 0x84cf054)  = 0
  ioctl(3, CDROMREADTOCENTRY, 0x84cf060)  = 0
  ioctl(3, CDROMREADTOCENTRY, 0x84cf06c)  = 0
  ioctl(3, CDROMREADTOCENTRY, 0x84cf078)  = 0
  ioctl(3, CDROMREADTOCENTRY, 0x84cf084)  = 0
  ioctl(3, CDROMSTART, 0x9)               = 0
  ioctl(3, CDROMPLAYMSF, 0x84cf4e0)       = -1 EOPNOTSUPP (Operation not supported)
  write(2, "cdplay", 6cdplay)                   = 6
  write(2, ": ioctl cdromplaymsf: Operation "..., 45: ioctl cdromplaymsf: Operation not supported) = 45
  write(2, "\n", 1
  )                       = 1
  close(3)                                = 0
  exit_group(0)                           = ?

I don't know what to make of this.

Nothing in syslog.

I can eject with # eject /dev/sr0, but $ eject -d commant reports the
default device file is "cdrom".  

> Btw, regarding the driver, linux doesn't use a driver/module for the
> drive.  It uses a module for the controller the drive is connected to.

Perhaps this clears up the side driver/module discussion.

Haines

[toc] | [prev] | [next] | [standalone]

#1303

On Sunday, July 1st, 2012, at 18:57:36h -0400, Haines Brown explained:

> ioctl cdromplaymsf: Operation not supported

If your Optiarc DVD drive does not support ioctl cdromplaymsf
then you will have to use a DAE software CD player in order
to play CDs.

[toc] | [prev] | [next] | [standalone]

#1304

J G Miller <miller@yoyo.ORG> writes:

> On Sunday, July 1st, 2012, at 18:57:36h -0400, Haines Brown explained:
>
>> ioctl cdromplaymsf: Operation not supported
>
> If your Optiarc DVD drive does not support ioctl cdromplaymsf
> then you will have to use a DAE software CD player in order
> to play CDs.

Aha! That was the answer. Thanks for clearing up the DAE/analog issue. I
tried using alsaplayer, configuring it to use /dev/sr0, and apparently
it is a DAE player, for now I'm able to cope with CDs.

Thank you for your patience.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.os.linux.hardware

csiph-web