DVD+RW PHILIPS PBDV824DP not detected by nautilus and is not mountable

Bug #365633 reported by Arnaud Soyez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After installing Jaunty, I cannot access my cdrom drive from nautilus or any other way.
I cannot mount it manually and 'cdrecord -scanbus' returns 'no found media'. I cannot eject it either using the push-button on it.

It worked fine with Intrepid (that's how I got to burn my jaunty CD). I didn't make any hardware changes.

* hwinfo --cdrom gives me this:

25: SCSI 300.0: 10602 CD-ROM
  [Created at block.247]
  UDI: /org/freedesktop/Hal/devices/storage_model_PBDV824DP
  Unique ID: KD9E.8OY62biVri1
  Parent ID: rKvl.JFrSjWtAyME
  SysFS ID: /class/block/sr0
  SysFS BusID: 3:0:0:0
  SysFS Device Link: /devices/pci0000:00/0000:00:0f.1/host3/target3:0:0/3:0:0:0
  Hardware Class: cdrom
  Model: "PHILIPS PBDV824DP"
  Vendor: "PHILIPS"
  Device: "PBDV824DP"
  Revision: "B3.3"
  Driver: "pata_via", "sr"
  Device File: /dev/sr0 (/dev/sg3)
  Device Number: block 11:0 (char 21:3)
  Features: CD-R, CD-RW, DVD-R, DVD+R, DVD+RW
  Drive status: no medium
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #12 (IDE interface)
  Drive Speed: 40

* lshw gives:

           *-cdrom
                description: DVD writer
                physical id: 1
                bus info: scsi@3:0.0.0
                logical name: /dev/scd0
                logical name: /dev/sr0
                capabilities: audio cd-r cd-rw dvd dvd-r
                configuration: status=open

* Some more info:
Description: Ubuntu 9.04
Release: 9.04
Linux glados 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux

The odd thing is that it says Driver: "pata_via", "sr", and I don't have any of these drivers in lsmod. It might not even be the cause of the issue.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=UUID=5195420d-04d6-446b-b264-b13b9d509569
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic 2.6.28-11.42
ProcCmdLine: root=UUID=5b79fcb1-edcb-48e3-ab0b-507a7d64a478 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
SourcePackage: linux

Revision history for this message
Arnaud Soyez (weboide) wrote :
Revision history for this message
Arnaud Soyez (weboide) wrote :

Note that I was using intrepid x86 (32bits), but now I'm using Jaunty amd64.

Revision history for this message
huntz (fuku-riu) wrote :

I'm getting the same error No cdrom devices in /dev, dmesg detects both of my cdroms but no device files are made, i did have a custom kernel but it has IDE, support, im not sure why this is happening though, im also on amd64

Revision history for this message
Arnaud Soyez (weboide) wrote :

Today (june 23rd) linux-image update seems to have fixed this. My drive now works and I can read dvd's.

Here's the output than I get know.

hwinfo --cdrom:
25: SCSI 300.0: 10602 CD-ROM
  [Created at block.247]
  UDI: /org/freedesktop/Hal/devices/storage_model_PBDV824DP
  Unique ID: KD9E.8OY62biVri1
  Parent ID: rKvl.JFrSjWtAyME
  SysFS ID: /class/block/sr0
  SysFS BusID: 3:0:0:0
  SysFS Device Link: /devices/pci0000:00/0000:00:0f.1/host3/target3:0:0/3:0:0:0
  Hardware Class: cdrom
  Model: "PHILIPS PBDV824DP"
  Vendor: "PHILIPS"
  Device: "PBDV824DP"
  Revision: "B3.3"
  Driver: "pata_via", "sr"
  Device File: /dev/sr0 (/dev/sg3)
  Device Number: block 11:0 (char 21:3)
  Features: CD-R, CD-RW, DVD-R, DVD+R, DVD+RW
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #12 (IDE interface)
  Drive Speed: 40
  Volume ID: "DVD-VIDEO"
  Application: "GENISOIMAGE ISO 9660/HFS FILESYSTEM CREATOR (C) 1993 E.YOUNGDALE (C) 1997-2006 J.PEARSON/J.SCHILLING (C) 2006-2007 CDRKIT TEAM"
  Creation date: "2008091018090400"

lshw:
           *-cdrom
                description: DVD writer
                product: PBDV824DP
                vendor: PHILIPS
                physical id: 1
                bus info: scsi@3:0.0.0
                logical name: /dev/cdrom
                logical name: /dev/cdrw
                logical name: /dev/dvd
                logical name: /dev/dvdrw
                logical name: /dev/scd0
                logical name: /dev/sr0
                logical name: /media/cdrom0
                version: B3.3
                capabilities: removable audio cd-r cd-rw dvd dvd-r
                configuration: ansiversion=5 mount.fstype=udf mount.options=ro,nosuid,nodev,utf8 state=mounted status=ready
              *-medium
                   physical id: 0
                   logical name: /dev/cdrom
                   logical name: /media/cdrom0
                   configuration: mount.fstype=udf mount.options=ro,nosuid,nodev,utf8 state=mounted

Changed in linux (Ubuntu):
status: New → Fix Released
Revision history for this message
Fred Wong (wongfb) wrote :

At the end of the comment trace it says Fix Released. Where is the fix? Is it in the latest kernel? Or is it going to be included in the next release of Ubuntu? After upgrading to Jaunty with much pain (together with loss of data), I would like to get my DVD/CDROM writer working. It is working with Ubuntu 7.04 and 8.04. 9.04 is so broken unfortunately because I have found so many issues on the net regarding 9.04.

Changed in linux (Ubuntu):
status: Fix Released → Invalid
Revision history for this message
xq19space (tuxlux) wrote :

This should not be a question.

This is a serious issue with Jaunty.

We loaded jaunty on a Clevo notebook running XP. Somehow GRUB blew out the cd/dvd drives. They are not detected. In XP, they aren't even detected in device manager.....nothing, nada, simply gone. The cd/dvd aren't even in the registry anymore.

However, when you put in a CD, the light comes on, it spins for a couple of seconds, then stops.
We checked the BIOS, the drives are there but GRUB did something to break them. We can confirm its GRUB because LILO brought the drives back up.

After searching the web, we found hundreds of people with the same problem.

Changing this to a question is not beneficial to anyone. This needs to be addressed.

The problem can be worked around using LILO, however, LILO breaks with the next kernel update. This happened to us and now we don't even have an OS.

Please put this in critical status as our company is on the verge of going back to XP because of this.
Our managers are watching this very closely to see how it will be handled.

No one can use a OS that blows out hardware.

Revision history for this message
Jagmax (wateranimal) wrote :

Quote: "Today (june 23rd) linux-image update seems to have fixed this. My drive now works and I can read dvd's."

Today Sat, Sept, 26, 2009 I just loaded ubuntu 9.04 and my drive is gone. So linux-image update is worthless.

Does anybody know if this is even being address. An OS that breaks hardware is no good.

I know the team is busy but this is a critical problem. Please.

Revision history for this message
Arnaud Soyez (weboide) wrote :

This bug is now invalid, so if you experience problems accessing your hardware, PLEASE file a new bug report specific to that hardware that is not working.
And complaining will not help fix anything, but filing bugs with relevent information would most likely help. (see https://wiki.ubuntu.com/HardwareIdentification)
Thank you for your understanding.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.