$ groups
users floppy audio video cdrom plugdev power netdev

Anyway, I can't seem to figure out where the problem is.
The best I can make out, the problem is either:
1. the way the cds were burned
2. a hardware problem
3. an os/software problem

1. some of the cds were burned in xp using roxio easy cd creator
and some were burned in slackware using k3b (the only thing in
common is the fact that they were all formatted iso9660).
2. I don't think it's a hardware problem because the cds
work just fine on the same hardware using windows.
3. I think it's an os/software problem because the problem
now occurs on two separate machines using slackware while
the problem does not occur in windows (on either machine).

I'm even seeing the problem with the cds I used to
successfully install slackware from.

was there ever resolution for this?

kthxbai

in my slackware 13.1 system i just put the cd and just click it in dolphin and it shows all contents, i dont have to mount anything.

most likely it is some windows program created some file that slackware refuses to read when you burned those cd's

No, because those "some windows program" worked just fine on 13.0 but not 13.1 ...

I was still having some problems about a month ago, but I haven't checked recently. I suppose that I should.

molossus, syslog/messages get huge using cdparanoia/vlc

audio commercial cd's rip/play fine, the log floods are annoying

this happens on two different laptops, installed stock kernel and recompiled

i might write script to remove annoying log messages, unless i can find how to turn off syslog/messages kernel logging

I just got my remote control working in 2.6.38-rc2 to be followed by our old "friend" ... MythTV is struggling severely to play a DVD ... The following error is with the option, libata.force=noncq, on in lilo.conf:

247.776051] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 247.776059] sr 1:0:0:0: [sr0] CDB: cdb[0]=0x28: 28 00 00 29 b5 9a 00 00 02 00
[ 247.776073] ata2.00: cmd a0/01:00:00:00:10/00:00:00:00:00/a0 tag 0 dma 4096 in
[ 247.776074] res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 247.776078] ata2.00: status: { DRDY }
[ 247.776084] ata2: hard resetting link
[ 247.776087] ata2: nv: skipping hardreset on occupied port
[ 248.230047] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 248.241145] ata2.00: configured for UDMA/33
[ 248.242783] ata2: EH complete
[ 282.720057] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 282.720064] sr 1:0:0:0: [sr0] CDB: cdb[0]=0x28: 28 00 00 29 b5 9c 00 00 08 00
[ 282.720078] ata2.00: cmd a0/01:00:00:00:40/00:00:00:00:00/a0 tag 0 dma 16384 in
[ 282.720080] res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 282.720083] ata2.00: status: { DRDY }
[ 282.720090] ata2: hard resetting link
[ 282.720092] ata2: nv: skipping hardreset on occupied port
[ 283.174050] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 283.183122] ata2.00: configured for UDMA/33
[ 283.184771] ata2: EH complete

I'll have to re-investigate this error later...

I googled some more on the problem I am having
on my two machines and came across this post:

http://forum.kde.org/viewtopic.php?f=19&t=91402#
(although I'm not using kde 4.5)

It mentions the problem being hal and to set
storage.media_check_enabled to true for the drive.

Mine is already set to true.
I still get the errors in the log.
And the cds will not automount.

However, If I set storage.media_check_enabled to false.
I do not get the errors in the log.
And the cds will not automount
(I'm assuming they wouldn't with a false setting)

But I can mount them (as a regular user) without
getting all the errors in the log file if I have
the following entry in /etc/fstab:
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro,users 0 0

So is it really a hal problem?
Something to do with the storage.media_check_enabled setting?
Just curious...

Since I was attempting to play a DVD, I rediscovered this error. I really don't have much spare time to investigate this issue properly, but it's looking like a semi-permanent error with Linux somewhere. MS Windows plays this particular DVD just fine with the nVidia chipset driving the internal DVD as does my portable USB DVD player if plugged into the computer while Linux is running. The on-board nVidia chipset driving the internal DVD continues to function improperly with Linux, however. Creating the media storage file for HAL doesn't change the actual malfunction of the internal drive although some error messages change.

1 members found this post helpful.

I think I found the problem with my nforce 430 chipset (preliminary at this point as I need more testing):

I have both PATA and SATA controllers. The SATA controller drives both my hard and optical drives. No devices are attached to the PATA controller. However, both the PATA and SATA controllers were enabled in the BIOS. For giggles, I simply disabled the PATA controller since no devices were attached. I rebooted my computer and the problems with reading/burning optical discs have apparently vanished. The only parameter to the kernel that's optionally enabled at boot is libata.force=noncq . Apparently, just prior to the release of Slackware 13.1, the kernel (libata?) was changed which adversely impacts my optical drive if both the PATA and SATA controllers are enabled. I'll have to do more testing ...

1 members found this post helpful.

I recently, swapped out my nforce3 nvidia chipset motherboard for one with an ATI/AMD chipset and the CD/DVD automounting issues seem to have vanished - at least for the CD/DVDs I have tried so far. Another system with and intel chipset also had issues automounting, I just updated that one to Slackware32 13.17 rc 4.66.. so I will try to find time to test today.