Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Unable to access CDROM device to play music

72 views
Skip to first unread message

Carmel

unread,
Sep 25, 2010, 8:09:23 AM9/25/10
to
I am using FreeBSD 8.1 / amd64 with Platform Version 4.5.1 (KDE 4.5.1)
if that matters.Before updating my system to FreeBSD 8.1 / amd64, I had
the 7.3 /32 bit version installed. I completely erased the HD prior to
installed the newer version so as to eliminate any accumulated garbage
that might be hanging around. Previously, I was able to play CD Audio
files without any problem. The "cdcontrol" program worked fine and I
was able to play music files while using KDE using its audio player.

I now find that I can no-longer achieve that goal. When I place an audio
CD into the PC, this error message is displayed: (It will probably wrap)

Unable to mount Audio Disc
DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)


This is from the system log: (Sorry, but it will probably line wrap)

Sep 25 07:51:22 cyborg kernel: acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00
Sep 25 07:51:22 cyborg kernel: (cd0:ata1:0:0:0): READ(10). CDB: 28 0 0 0 0 0 0 0 40 0
Sep 25 07:51:22 cyborg kernel: (cd0:ata1:0:0:0): CAM status: SCSI Status Error
Sep 25 07:51:22 cyborg kernel: (cd0:ata1:0:0:0): SCSI status: Check Condition
Sep 25 07:51:22 cyborg kernel: (cd0:ata1:0:0:0): SCSI sense: ILLEGAL REQUEST asc:64,0 (Illegal mode for this track)
Sep 25 07:51:22 cyborg kernel: (cd0:ata1:0:0:0): cddone: got error 0x6 back

I am at a loss here. I don't believe I made any radical changes from
the configuration I was using in my older FreeBSD installation.

I might add that MPlayer cannot see the drive either; although, it use
to work fine. This problem exists whether KDE is running or not. The
"cdcontrol" player will open and close the door on the device; however,
no sound is emitted. Normal 'notification' sounds are emitted so I know
the speakers, etc. are working correctly. The KDE start-up
notifications works just fine.

--
Carmel ✌
carm...@hotmail.com
_______________________________________________
freebsd-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"

Paul B Mahol

unread,
Sep 25, 2010, 8:51:16 AM9/25/10
to

what is mixer output?
what sound driver are you using?

Carmel

unread,
Sep 25, 2010, 9:59:42 AM9/25/10
to
On Sat, 25 Sep 2010 12:51:16 +0000
Paul B Mahol <one...@gmail.com> articulated:

> what is mixer output?
> what sound driver are you using?

From the kernel file:

## SOUND
device sound # Install sound driver support
device snd_hda # nVidia MCP51 sound driver

Via mixer:

$ mixer
Mixer vol is currently set to 90:90
Mixer pcm is currently set to 42:45
Mixer speaker is currently set to 100:100
Mixer line is currently set to 100:100
Mixer mic is currently set to 0:0
Mixer cd is currently set to 100:100
Mixer mix is currently set to 0:0
Mixer rec is currently set to 75:75
Mixer igain is currently set to 0:0
Recording source: mic

Via pciconf -lv

hdac0@pci0:3:0:1: class=0x040300 card=0x00000000 chip=0x0be210de rev=0xa1 hdr=0x00
vendor = 'NVIDIA Corporation'
class = multimedia
subclass = HDA

I attached the "dmesg" output. I don't know if that works on this list
or not. I can always supply if separately. What bugs me is that this use
to work before I upgraded my system.

--
Carmel ✌
carm...@hotmail.com

dmesg.txt

Lowell Gilbert

unread,
Sep 25, 2010, 10:28:13 AM9/25/10
to
Carmel <carm...@hotmail.com> writes:

> I am using FreeBSD 8.1 / amd64 with Platform Version 4.5.1 (KDE 4.5.1)
> if that matters.Before updating my system to FreeBSD 8.1 / amd64, I had
> the 7.3 /32 bit version installed. I completely erased the HD prior to
> installed the newer version so as to eliminate any accumulated garbage
> that might be hanging around. Previously, I was able to play CD Audio
> files without any problem. The "cdcontrol" program worked fine and I
> was able to play music files while using KDE using its audio player.

If X isn't running, what does cdcontrol do?

Carmel

unread,
Sep 25, 2010, 1:19:18 PM9/25/10
to
On Sat, 25 Sep 2010 10:28:13 -0400
Lowell Gilbert <freebsd-que...@be-well.ilk.org> articulated:

> If X isn't running, what does cdcontrol do?

Nothing. It will open or close the tray, but that is about it.

--
Carmel ✌
carm...@hotmail.com

Polytropon

unread,
Sep 25, 2010, 4:31:39 PM9/25/10
to
On Sat, 25 Sep 2010 08:09:23 -0400, Carmel <carm...@hotmail.com> wrote:
> I am using FreeBSD 8.1 / amd64 with Platform Version 4.5.1 (KDE 4.5.1)
> if that matters.Before updating my system to FreeBSD 8.1 / amd64, I had
> the 7.3 /32 bit version installed. I completely erased the HD prior to
> installed the newer version so as to eliminate any accumulated garbage
> that might be hanging around. Previously, I was able to play CD Audio
> files without any problem. The "cdcontrol" program worked fine and I
> was able to play music files while using KDE using its audio player.
>
> I now find that I can no-longer achieve that goal. When I place an audio
> CD into the PC, this error message is displayed: (It will probably wrap)
>
> Unable to mount Audio Disc
> DBus error org.freedesktop.DBus.Error.NoReply:
> Message did not receive a reply (timeout by message bus)

You cannot mount audio CDs.

The important lines from your system log are:

acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00

SCSI status: Check Condition


SCSI sense: ILLEGAL REQUEST asc:64,0 (Illegal mode for this track)

This seems to indicate that the CD cannot be read. Can it be read
with a different drive? Maybe the drive is faulty. Or the media
is. Can you check the media in a "hardware CD player"?

> I am at a loss here. I don't believe I made any radical changes from
> the configuration I was using in my older FreeBSD installation.

First of all, HAL seems to be interfering. To check, make sure HAL
is not running, then do "cdcontrol play 1". Have the "mixer" program
push all volumes up.

> I might add that MPlayer cannot see the drive either; although, it use
> to work fine.

In how far does mplayer "see a drive"?

> This problem exists whether KDE is running or not. The
> "cdcontrol" player will open and close the door on the device; however,
> no sound is emitted.

Does the drive have a phones connector at the front? Does it maybe
play from there? Playing audio CDs is a feature of drives that does
not neccessarily need CPU / system attention (except for starting
the playback by a drive command).

Are you accessing the drive by ATAPI or ATAPICAM?

> Normal 'notification' sounds are emitted so I know
> the speakers, etc. are working correctly. The KDE start-up
> notifications works just fine.

So no problem on this side.

--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

dan

unread,
Sep 25, 2010, 5:21:29 PM9/25/10
to

If you are accessing ATAPI device using the SCSI subsystem make sure the
user has all the required permissions to read/write xpt* pass* cd*.
Run "camcontrol devlist" as a normal user and see if it shows you any
drive (http://www.freebsd.org/doc/en/books/handbook/creating-cds.html
Section 18.6.9).

If this matters somehow I get many of the following messages

(cd0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 2 99 77 0 0 1 0
(cd0:umass-sim0:0:0:0): CAM status: SCSI Status Error
(cd0:umass-sim0:0:0:0): SCSI status: Check Condition
(cd0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST csi:28,a,1,20

asc:64,0 (Illegal mode for this track)

(cd0:umass-sim0:0:0:0): cddone: got error 0x6 back
(cd0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 0 0 20 0 0 4 0
(cd0:umass-sim0:0:0:0): CAM status: SCSI Status Error
(cd0:umass-sim0:0:0:0): SCSI status: Check Condition
(...)
when an audio cd is pre-loaded at bootup into my external dvd rewriter.
But the drive is functional (or at least seems to be... :-D).

d

Carmel

unread,
Sep 25, 2010, 5:32:27 PM9/25/10
to
On Sat, 25 Sep 2010 22:31:39 +0200
Polytropon <fre...@edvax.de> articulated:

> On Sat, 25 Sep 2010 08:09:23 -0400, Carmel <carm...@hotmail.com>
> wrote:
> > I am using FreeBSD 8.1 / amd64 with Platform Version 4.5.1 (KDE
> > 4.5.1) if that matters.Before updating my system to FreeBSD 8.1 /
> > amd64, I had the 7.3 /32 bit version installed. I completely erased
> > the HD prior to installed the newer version so as to eliminate any
> > accumulated garbage that might be hanging around. Previously, I was
> > able to play CD Audio files without any problem. The "cdcontrol"
> > program worked fine and I was able to play music files while using
> > KDE using its audio player.
> >
> > I now find that I can no-longer achieve that goal. When I place an
> > audio CD into the PC, this error message is displayed: (It will
> > probably wrap)
> >
> > Unable to mount Audio Disc
> > DBus error org.freedesktop.DBus.Error.NoReply:
> > Message did not receive a reply (timeout by message bus)
>
> You cannot mount audio CDs.
>
> The important lines from your system log are:
>
> acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00
> SCSI status: Check Condition
> SCSI sense: ILLEGAL REQUEST asc:64,0 (Illegal mode for this track)
>
> This seems to indicate that the CD cannot be read. Can it be read
> with a different drive? Maybe the drive is faulty. Or the media
> is. Can you check the media in a "hardware CD player"?

I have tries several different disks, all with the same results. These
CDs work fine on my Windows machines.

I used information at URL:

http://www.freebsd.org/doc/handbook/creating-cds.html

18.6.9 Using the ATAPI/CAM Driver

This worked fine on my previous version of FreeBSD. Now, entering the
command:

mount -t cd9660 /dev/cd0 /mnt

Gets me this error message:

mount_cd9660: /dev/cd0: Input/output error

> > I am at a loss here. I don't believe I made any radical changes from
> > the configuration I was using in my older FreeBSD installation.
>
> First of all, HAL seems to be interfering. To check, make sure HAL
> is not running, then do "cdcontrol play 1". Have the "mixer" program
> push all volumes up.
>
> > I might add that MPlayer cannot see the drive either; although, it
> > use to work fine.
>
> In how far does mplayer "see a drive"?

MPlayer cannot play a file from a CD because it never finds a CD to
use. It did work previously.

> > This problem exists whether KDE is running or not. The
> > "cdcontrol" player will open and close the door on the device;
> > however, no sound is emitted.
>
> Does the drive have a phones connector at the front? Does it maybe
> play from there? Playing audio CDs is a feature of drives that does
> not neccessarily need CPU / system attention (except for starting
> the playback by a drive command).
>
> Are you accessing the drive by ATAPI or ATAPICAM?

ATAPICAM

> > Normal 'notification' sounds are emitted so I know
> > the speakers, etc. are working correctly. The KDE start-up
> > notifications works just fine.
>
> So no problem on this side.

Polytropon

unread,
Sep 25, 2010, 6:49:16 PM9/25/10
to
On Sat, 25 Sep 2010 17:32:27 -0400, Carmel <carm...@hotmail.com> wrote:
> I have tries several different disks, all with the same results. These
> CDs work fine on my Windows machines.
>
> I used information at URL:
>
> http://www.freebsd.org/doc/handbook/creating-cds.html
>
> 18.6.9 Using the ATAPI/CAM Driver
>
> This worked fine on my previous version of FreeBSD.

I'm also using this setup for many years now.

> Now, entering the
> command:
>
> mount -t cd9660 /dev/cd0 /mnt
>
> Gets me this error message:
>
> mount_cd9660: /dev/cd0: Input/output error

Does this refer to an audio CD? In that case: Won't work.

Mounting a data CD (ISO-9660 filesystem) _should_ work. From the
error message, I don't think you have permission problems, but make
sure that - as you're using ATAPICAM - have sufficient permissions
for /dev/cd*, /dev/xpt* and /dev/pass*.

Have you tried mounting using the ATAPI driver?

# mount -o ro -t cd9660 /dev/acd0 /mnt

Does this work for data CDs?

> MPlayer cannot play a file from a CD because it never finds a CD to
> use. It did work previously.

Okay, seems that you're accessing the audio CD by mplayer, I now
understand. You can specify -dvd-device <dev> as a command line
parameter for mplayer to indicate which drive to use. Oh, and
many programs use $CDROM and $CDPLAYER environment variables.

> > Are you accessing the drive by ATAPI or ATAPICAM?
>
> ATAPICAM

To make sure there are no other problems, try with ATAPI, too,
as shown above.


--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

Carmel

unread,
Sep 25, 2010, 7:46:08 PM9/25/10
to
On Sun, 26 Sep 2010 00:49:16 +0200
Polytropon <fre...@edvax.de> articulated:

> Have you tried mounting using the ATAPI driver?
>
> # mount -o ro -t cd9660 /dev/acd0 /mnt
>
> Does this work for data CDs?

I get this error message:

mount_cd9660: /dev/acd0: Invalid argument

--
Carmel ✌
carm...@hotmail.com

Polytropon

unread,
Sep 25, 2010, 8:03:28 PM9/25/10
to
On Sat, 25 Sep 2010 19:46:08 -0400, Carmel <carm...@hotmail.com> wrote:
> On Sun, 26 Sep 2010 00:49:16 +0200
> Polytropon <fre...@edvax.de> articulated:
>
> > Have you tried mounting using the ATAPI driver?
> >
> > # mount -o ro -t cd9660 /dev/acd0 /mnt
> >
> > Does this work for data CDs?
>
> I get this error message:
>
> mount_cd9660: /dev/acd0: Invalid argument

This seems to show that there's no ISO-9660 file system on
the (data) CD, or the session is not finished, or any other
problem on file system level. Can you check

% file - < /dev/acd0
% cdcontrol info

Here's an example for the output for a data CD:

% file - < /dev/acd0
/dev/stdin: ISO 9660 CD-ROM filesystem data
'FreeBSD_Install ' (bootable)

% cdcontrol info
Starting track = 1, ending track = 1, TOC size = 18 bytes
track start duration block length type
-------------------------------------------------
1 0:02.00 57:57.56 0 260831 data
170 57:59.56 - 260831 - -

And for an audio CD:

% file - < /dev/acd0
/dev/stdin: ERROR: cannot read `(null)' (Invalid argument)

% cdcontrol info
Starting track = 1, ending track = 18, TOC size = 154 bytes
track start duration block length type
-------------------------------------------------
1 0:02.00 3:31.03 0 15828 audio
2 3:33.03 2:52.67 15828 12967 audio
...
17 52:24.53 7:27.30 235703 33555 audio
18 59:52.08 2:48.67 269258 12667 audio
170 62:41.00 - 281925 - -

Do you get the same results for the respective CD content types?

--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

Carmel

unread,
Sep 26, 2010, 7:43:37 AM9/26/10
to
On Sun, 26 Sep 2010 02:03:28 +0200
Polytropon <fre...@edvax.de> articulated:

I made some file permission changes, rebooted and made sure that the
changes were static, and then ran a few test.

The cdcontrol program will not play a CDROM although it claims it is. I
can play an audio CD from within KDE; however, it is like pulling teeth
to accomplish it. Way too much trouble. MPlayer cannot access the audio
CD naively.

DATA CDs are another story. I cannot mount them.

Using a data CD:

# file - < /dev/acd0
/dev/stdin: ERROR: cannot read `(null)' (Input/output error)

# file - < /dev/cd0


/dev/stdin: ERROR: cannot read `(null)' (Invalid argument)

# cdcontrol info
cdcontrol: getting toc header: Invalid argument
cdcontrol: Invalid argument

With an audio CD:

# file - < /dev/acd0


/dev/stdin: ERROR: cannot read `(null)' (Invalid argument)

# file - < /dev/cd0
/dev/stdin: ERROR: cannot read `(null)' (Device not configured)

# cdcontrol info
Starting track = 1, ending track = 3, TOC size = 34 bytes


track start duration block length type
-------------------------------------------------

1 0:02.00 6:32.00 0 29400 audio
2 6:34.00 3:55.12 29400 17637 audio
3 10:29.12 3:42.23 47037 16673 audio
170 14:11.35 - 63710 - -

Finally, just trying a mount command from the command line:

$ sudo mount -o ro -t cd9660 /dev/acd0 /mnt
mount_cd9660: /dev/acd0: Invalid argument

$ sudo mount -o ro -t cd9660 /dev/cd0 /mnt
mount_cd9660: /dev/cd0: Device not configured

This is getting to be far more trouble and wasting way too much time
than it is worth. I can just put the CDs in one of my Windows machines
and then transfer the data over the network to the FreeBSD units. What
is strange is that this use to work before I upgraded.

By the way, Polytropon, please do not CC me. I am on the list and I
really do not need two copies of every post. Others may appreciate it;
however, I don't.

--
Carmel ✌
carm...@hotmail.com

0 new messages