Fails to see blank CD/DVDs for writing

Bug #220957 reported by Jamie Lokier
52
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
nautilus-cd-burner (Ubuntu)
Invalid
Low
Unassigned

Bug Description

I'm using Hardy, with latest updates.

Since upgrading from Gutsy to Hardy, I can no longer burn CDs/DVDs.

Now when I insert a blank CD-R or DVD-R into the drive, the drive spins up briefly but nothing appears on the desktop. With Gutsy, up came the options to burn a disc.

Also, if I manually click on an ISO for burning, then it asks me to insert blank media even though there already is one in the drive.

When I run the "cdinfo" command from the "cdtool" package, it outputs, simply:

    no_disc

Exactly the same as when there is really no disc. The "eject" command still works.

I've tried two different brands of CD-R, and two different brands of DVR-R, all gives the same results.

This is probably a software problem. I have just booted Windows XP a few minutes ago (not done that in months :-), and it detected all the blank discs fine, bringing up a menu of burn options after I insert them. I didn't actually try burning.

Then booting back to Ubuntu Hardy (after XP), it doesn't detect blank discs.

This problem is worst since upgrading to Hardy: all blank media is not detected. With Gutsy, I did see this problem with one brand of CD-R, but other discs were detected fine.

The machine is a Fujitsu-Siemens Si1520, and the output of "sudo hdparm -I /dev/cdrom":

    ATAPI CD-ROM, with removable media
        Model Number: _NEC DVD_RW ND-6750A
        Serial Number:
        Firmware Revision: 2.42

Kernel is 2.4.24-16-generic (current version in Hardy at the time of writing).

Any other info required, please ask.
Much thanks.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Jamie,

Can you comment what application you are using to burn your CD/DVD's? Can you also attach your entire 'dmesg' output after you've attempt to burn a CD/DVD. Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
Mark Weaver (blushingpenguin) wrote :

same here. cd burning software:

nautilius-cd-burner/k3b gives insert a blank or rewriteable disk/no media present
cd_info reports no_disc.

booting 2.6.22-14-generic with current hardy userspace gives the same results.

hdparm -I /dev/scd0

ATAPI CD-ROM, with removable media
 Model Number: PIONEER DVD+/-RW DR-K17Y
 Serial Number: GBDL024510WL
 Firmware Revision: 0.94
Standards:
 Likely used CD-ROM ATAPI-1
Configuration:
 DRQ response: 50us.
 Packet size: 12 bytes
Capabilities:
 LBA, IORDY(can be disabled)
 Buffer size: 64.0kB
 DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2
      Cycle time: min=120ns recommended=120ns
 PIO: pio0 pio1 pio2 pio3 pio4
      Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
 Enabled Supported:
    * Power Management feature set
    * PACKET command feature set
    * DEVICE_RESET command
HW reset results:
 CBLID- above Vih
 Device num = 0 determined by the jumper

I don't have windows on this machine but the CD that was not detected correctly I transferred to another machine and the cd can be written to successfully. I had no problem burning cds with gutsy using k3b.

on running cdinfo, dmesg says

Apr 29 00:17:25 alfred kernel: [ 530.131564] sr0: CDROM not ready. Make sure there is a disc in the drive.

(and
mark@alfred:~$ ls -l /dev/sr0
lrwxrwxrwx 1 root root 4 2008-04-28 23:55 /dev/sr0 -> scd0
)

Revision history for this message
drumour (drumour) wrote :

Not quite same here had no problem in Gutsy but with Hardy on 2 similar pc's both running 8.04 and patched up to date. When I insert a blank dvd or cd nothing happens. If I try and burn using Brasero for e.g. it reports "no disc" in drive.
fstab gives following for cd/dvd:
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

other commands tried and their results:

1) with blank dvd in drive: sudo mount /dev/scd0 /media/cdrom0
mount: No medium found

2) with blank dvd in drive: sudo lshw -C disk
*-cdrom
description: DVD writer
product: DVD+-RW ND-3570A
vendor: Optiarc
physical id: 0.0.0
bus info: scsi@2:0.0.0
logical name: /dev/cdrom
logical name: /dev/dvd
logical name: /dev/scd0
logical name: /dev/sr0
version: 104B
serial: [Optiarc DVD+-RW ND-3570A104B06031000
capabilities: removable audio cd-r cd-rw dvd dvd-r
configuration: ansiversion=5 status=open

3) with blank dvd in drive:/usr/lib/nautilus-cd-burner/list_cddrives
Drive:
name: DVD+-RW ND-3570A
device: /dev/scd0
door: open
type: CD-R, CD-RW, DVD-R, DVD-RW, DVD+R, DVD+R DL, DVD+RW, CD, DVD
is mounted: FALSE
max read speed: 8467 KiB/s (CD 56.4x, DVD 6.2x)
max write speed: 8467 KiB/s (CD 56.4x, DVD 6.2x)
write speeds: 8467 KiB/s (CD 56.4x, DVD 6.2x)
7056 KiB/s (CD 47.0x, DVD 5.2x)
5645 KiB/s (CD 37.6x, DVD 4.1x)
4234 KiB/s (CD 28.2x, DVD 3.1x)
2822 KiB/s (CD 18.8x, DVD 2.0x)
1411 KiB/s (CD 9.4x, DVD 1.0x)

Media:
label: ''
type: Couldn't open media
is writable: FALSE
is appendable: FALSE
capacity: Could not be determined
size: Could not be determined

4) hdparm -I /dev/scd0

/dev/scd0:
 HDIO_DRIVE_CMD(identify) failed: Permission denied
flint@flintpc:~$ sudo hdparm -I /dev/scd0

/dev/scd0:

ATAPI CD-ROM, with removable media
 Model Number: Optiarc DVD+/-RW ND-3570A
 Serial Number:
 Firmware Revision: 104B
Standards:
 Likely used CD-ROM ATAPI-1
Configuration:
 DRQ response: 3ms.
 Packet size: 12 bytes
Capabilities:
 LBA, IORDY(cannot be disabled)
 DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2
      Cycle time: min=120ns recommended=120ns
 PIO: pio0 pio1 pio2 pio3 pio4
      Cycle time: no flow control=120ns IORDY flow control

5) the eject and eject -t command work but eject -t takes longer than normal to complete

Revision history for this message
Mark Weaver (blushingpenguin) wrote :

For me, this turned out to be a hardware issue with the drive (would read/write dvds but not cds), so sorry for the noise.

Revision history for this message
Jamie Lokier (jamie-shareable) wrote :
Download full text (7.9 KiB)

Hi Leann,

(Bit annoyed because I just wrote a long answer, then hit Control-W by accident in Firefox and it's lost...)

I tried these methods today:

1. Insert a blank CD-R in the drive. Nothing happens. I'm expecting it to pop up a dialog asking what I want to do, or to show an icon for the blank CD-R on the Nautilus desktop, but neither happens.

2. With a blank CD-R in the drive, in Nautilus I double-click on a .iso file. Or right-click and select Open with "CD/DVD Creator". It shows a dialog for the drive selection (DVD_RW ND-6750A) and write speed (Maximum possible). I click the Write button, and a dialog appears with a progress bar. Then another dialog appears saying "Insert a rewritable or blank disc". There is one already so I click OK, and it just reappears. I eject the disc and insert it, or another one, and it does the same. No way past this.

3. Same as 2 with no blank CD-R in the drive to start with. Same results.

4. Using "cdrecord -v file.iso" from the command line, it detects the CD-R with details and writes successfully.

5. In Nautilus I right-click on a .iso file and select Open with "Brasero Disc Burning". This pops a dialog which clearly detects the type of CD-R inserted which is promising.

The first time I clicked the Burn button, it failed. But this was because I still had a CD/DVD Creator stuck in that "insert disc" loop open (buried under other windows). Not surprising, but the error message from Brasero was obscure and unhelpful: I thought Brasero wasn't also able to write discs because of it. It would be much better to say the drive is in use by another application.

After clearing that up, I started again. This time Brasero wrote the disc successfully, then ejected it, but didn't finish. Instead it popped up a dialog saying "Error while burning: the media in DVD_RW ND-6750A can't be ejected". The saved log is attached in brasero-session.log.

In all of this, there's no dmesg or /var/log/kern.log output.

Things noticed:

a. Disc writing does work, but the default burning app after upgrade from Gutsy, CD/DVD Creator (nautilus-cd-burner) doesn't work. I tried it from the command line too; there's no output to give a clue about the errors.

b. The dialog popping up on inserting a blank disc asking if you want to make a new CD, or the blank disc icon (I forget which one happens on Gutsy) aren't happening.

c. Even though I can right-click a .iso file and select Brasero, when I want to make a disc from individual files, I'll use the Nautilus "Places" menu and it only offers CD/DVD Creator. It's a Nautilus file browser where you can put files to prepare a data disc, then click to burn the disc. I didn't find any way to change this to use Brasero (see below).

e. Brasero (from a .iso file only) writes ok but finishes with an error. It's messages are unhelpful when there's a problem (other app locked the drive device, or Brasero confused about ejecting).

f. Brasero found the drive device locked when there were CD/DVD creators stuck in the background, but that didn't stop cdrecord from the command line from working.

g. Later, trying Brasero on a burned CD-R (one it made earlier) says "data can be...

Read more...

Revision history for this message
tanager (tanager) wrote :

Just want to add: I'm having the same problem. I haven't tried the command line yet - and I didn't have this issue with Gutsy.

Changed in linux:
status: Incomplete → New
Revision history for this message
Mike Perrin (mperrin) wrote :

I had a similar problem in 8.04 with a Plextor PX-W2410TA CD burner manufactured in October 2001. Nautilus would not recognize a blank CD. I could burn using either CD/DVD creator or Brasero, but Brasero produced a "could not eject" error. This drive was working perfectly with 6.10. The workaround was to replace it with a Memorex MRX523252AJI manufactured in 2004.

Perhaps this has something to do with 8.04 using the /dev/scd0 driver instead of /dev/hdc as in 6.10?

Revision history for this message
zertz (zertz) wrote :

This is a serious bug. It doesn't work in Hardy, but with the same hardware, works in Gutsy. I hate to be mean, and I dont think I am by saying this, but if Ubuntu wants to compete with windows its really got to avoid these kind of bugs. If a person only has two machines, Hardy doesn't work for burning, but windows always will. I can see how this bug would effect people Hardy users who have deployed in businesses.

Revision history for this message
Sebastien Bacher (seb128) wrote :

it's easier for microsoft, all the vendors make sure their hardware is correctly supported but the work has to do the other way around under linux, and it's not easy for the coders to have all the harwares available to make sure everything is working correctly

Revision history for this message
Sebastien Bacher (seb128) wrote :

note that the issue is not likely a nautilus-cd-burner one

Revision history for this message
tanager (tanager) wrote :

Sebastien, whether it works for Microsoft or not shouldn't matter. Recognizing black media worked in Gutsy, and the fact that the problem persists in Hardy - released in April - is pretty bad. I have to dump work on flash drives and go to my Mac to burn DVDs, and it's a pain. Considering there is nothing new in Hardy that's adding noticeable value to my system, this one bug is a severe functionality setback (for me, at least!)

Revision history for this message
tanager (tanager) wrote :

uh, that would be BLANK media...lol

Revision history for this message
Sebastien Bacher (seb128) wrote :

right, I don't discuss that's an issue, just explaining that making sure that things still work on hardware you don't have is not easy

Revision history for this message
zertz (zertz) wrote :

for what its worth, my failing hardware is a Pioneer 112D DVDR. its an ATAPI device. and the problem I am having is the same problem all of the people here have explained, which is perfectly good blank dvd's (haven't tried cd's) do not get recognized. blank dvd's are all i have.

Revision history for this message
zertz (zertz) wrote :

for me failing hardware, sudo hdparm -l /dev/cdrom

sudo hdparm -I /dev/cdrom
sudo: cannot get working directory
[sudo] password for me:

/dev/cdrom:

ATAPI CD-ROM, with removable media
 Model Number: PIONEER DVD-RW DVR-112D
 Serial Number: GCDP346786WL
 Firmware Revision: 1.15
Standards:
 Likely used CD-ROM ATAPI-1
Configuration:
 DRQ response: 50us.
 Packet size: 12 bytes
Capabilities:
 LBA, IORDY(can be disabled)
 Buffer size: 64.0kB
 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4
      Cycle time: min=120ns recommended=120ns
 PIO: pio0 pio1 pio2 pio3 pio4
      Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
 Enabled Supported:
    * Power Management feature set
    * PACKET command feature set
    * DEVICE_RESET command
HW reset results:
 CBLID- above Vih
 Device num = 0 determined by the jumper

_____

for my failing hardware sudo lshw -C disk

 *-cdrom
       description: DVD writer
       product: DVD-RW DVR-112D
       vendor: PIONEER
       physical id: 0.0.0
       bus info: scsi@6:0.0.0
       logical name: /dev/cdrom
       logical name: /dev/dvd
       logical name: /dev/scd0
       logical name: /dev/sr0
       version: 1.15
       capabilities: removable audio cd-r cd-rw dvd dvd-r
       configuration: ansiversion=5 status=ready
     *-medium
          physical id: 0
          logical name: /dev/cdrom

Revision history for this message
Andy (andy-xillean) wrote :

Will somebody at PLEASE fix this problem. I have several PCs and Laptops that continue to
exhibit this issue and they also refuse to read any data or movie DVDs. The drives are combo cdrw dvdrw drives and will only read burned CDs. This is a CRITICAL issue and all the PCs worked perfectly fine in Ubuntu 7.10 (Gutsy) Why are we having this problem now with hardware that used to work suddenly does not and no one seems to realize how *CRITICAL* this is. This is a MAJOR bug and its a problem with the KERNEL failure to read DVDs and blank media.
To summarize :
Many DVDrw drives will only read CDROMs
They will not read data or movie DVDs nor any blank media.
This problem is at the kernel level
These devices worked without problems in gutsy.

$ sudo mount -t udf /dev/cdrom /media/cdrom0
mount: No medium found

this problem manifest as several different bug reports with a plethora of different
suggestions to try such as
==========================================================
https://bugs.launchpad.net/ubuntu/+bug/228624
https://bugs.launchpad.net/ubuntu/+source/gnome-volume-manager/+bug/218834

Try to recheck if you did boot with the all_generic_ide=1
Other workarounds could be:
1. Booting with irqpoll.
2. Trying to use the 2.6.24-12 kernel.
3. Someone said that he got a better umda cable and now his drive speed was properly seen as udma2.
=======================================================

I hate to be harsh here but it has been 2 months since Hardy was released with a bug that should have never been released and yet this is not fixed. With ever release of ubuntu there are massive show stopping bugs that really turn people off.

Revision history for this message
zertz (zertz) wrote :

2 months without a fix is too serious of a bug for me for people to not fix. i'm going back to gutsy. i do not have the luxury of transferring my isos to a different computer to be burned.
i notice that all the people who have commented here, none of them have sata drives. i'm considering asking around if people have a fully updated hardy box and with a working sata burner, because i might be willing to upgrade to a newer burner just so this will work. if it does, its still no excuse for this problem not to be fixed. hardy was released by ubuntu with the intention of being adopted by businesses and with this fatal flaw, something as everyday task of atapi media not being detected, it sure is awful.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the comments indicate the issue is not a nautilus-cd-burner one

Changed in nautilus-cd-burner:
importance: Undecided → Low
status: New → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

could everybody having the issue attach an lshal log and look if syslog has errors when trying to read or burn a cd or dvd?

Revision history for this message
Jamie Lokier (jamie-shareable) wrote : Re: [Bug 220957] Re: Fails to see blank CD/DVDs for writing

Sebastien Bacher wrote:
> the comments indicate the issue is not a nautilus-cd-burner one

I disagree. Which comments?

The comment from me indicates that it's exactly nautilus-cd-burner.

Other burning programs work: Brasero, cdrecord, etc. (Apart from
Brasero getting confused at the end, trying to eject twice.)

In particular, the only reason I noticed this after upgrading to Hardy
is because the upgrade fails to change the default burning software
properly. It still runs nautilus-cd-burner, while new Hardy installs
will use Brasero, and that works.

Also, why have you changed the bug status to INVALID? The bug is
still present. The hardware is fine - it works with other versions of
Ubuntu and with other OSes. It's clearly a software problem, in
Hardy. And it shows up in nautilus-cd-burner and not other burning
apps.

-- Jamie

Revision history for this message
Sebastien Bacher (seb128) wrote :

> The comment from me indicates that it's exactly nautilus-cd-burner.

could you insert a blank media in the drive, run lshal and attach the log to the bug rather than make assumptions on the issue? the description seems to indicate that the is_blank hal properties is not correctly set which would be an hal or linux issue, other softwares would be working if they try recording anyway or look to the disc informations using some other way, note that the bug is not closed, only the nautilus-cd-burner entry has been marked invalid because the bug is not due to this one

Revision history for this message
Andy (andy-xillean) wrote :

Here is my lshal with a black DVD in the drive.

Revision history for this message
Andy (andy-xillean) wrote :

Here is my lshal with a DATA DVD in the drive that was burned on this system
with Gutsy right before it was wiped for a fresh install.

here is what happens when I try to mount the data DVD on the command line

$sudo mount -t udf /dev/dvd /media/cdrom0/
mount: No medium found

~$ sudo mount /dev/dvd
mount: No medium found

sudo mount /dev/dvdrw
mount: No medium found

And when I tried the modules posted here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/213639
the via82cxxx.ko loaded ok but same results. I did notice
this in the log files when i had those modules loaded.
syslog:Jun 9 11:24:15 ubuntu060608 kernel: [39459.478003] hdc: error code: 0x70 sense_key: 0x02 asc: 0x30 ascq: 0x00
syslog:Jun 9 11:24:15 ubuntu060608 kernel: [39459.479226] hdc: error code: 0x70 sense_key: 0x02 asc: 0x30 ascq: 0x00
syslog:Jun 9 11:24:15 ubuntu060608 kernel: [39459.479814] hdc: error code: 0x70 sense_key: 0x02 asc: 0x30 ascq: 0x00

No errors in dmesg or any log files with the default Hardy install fully updated to 2.6.24-19.
only when the modules are switched to the older ones do I get any kernel errors.

Revision history for this message
Andy (andy-xillean) wrote :

Oh one more thing.
I tried the all_generic_ide=1 Made no difference
Tried pollirq Made no difference
I also switched from 40pin to 80pin cable. Made no difference.

here is a hdparm info on the drive

===============================================
$ sudo hdparm -i /dev/dvd

/dev/dvd:

 Model=OPTORITEDVD RW DD1205 , FwRev=100e , SerialNo=
 Config={ Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
 RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
 BuffType=unknown, BuffSize=1024kB, MaxMultSect=0
 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
 IORDY=on/off, tPIO={min:383,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes: pio0 pio1 pio2 pio3 pio4
 DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 *udma2
 AdvancedPM=no

 * signifies the current active mode
==============================================

This drive was used to install Hardy on this system from the Hardy CD-ROM.
This system had Gutsy on it and it was backed up to DVD burned by this drive
on this system then wiped and installed a fresh installation of Hardy with this drive.
In Hardy it will only mount data and music CD-ROMS. No dvd media data or movies
can be mounted on this system since Hardy was installed.

Revision history for this message
tanager (tanager) wrote :

Here is my lshal log, with blank DVD in the drive.

Revision history for this message
Sebastien Bacher (seb128) wrote :

there is no disc listed in those logs which confirming an hal or linux issue

Revision history for this message
Martin Pitt (pitti) wrote :

tanager, your lshal.log looks fine, you have a DVD drive with a recognized DVD medium. What isn't working for you?

Revision history for this message
Martin Pitt (pitti) wrote :
Download full text (5.1 KiB)

So hal sees the drive and the capabilities, but does not detect the (empty) volume. Unfortunately I cannot tell much more from the currently existing information here.

If you insert a blank CD-ROM, wait a bit, and do "dmesg | tail" in a terminal, can you please copy&paste the output here? The only line that should appear after inserting a blank DVD is

  [12993.587466] cdrom: This disc doesn't have any tracks I recognize!

(different timestamp at the front, of course).

Also, it would be helpful to watch what hal is detecting. Can you please do the procedure on https://wiki.ubuntu.com/DebuggingHal and attach the log? Then we can compare it with the output on a system where it works (e. g. mine), see below.

For the record, I also have an ATAPI burner, and Hardy uses the SCSI emulation.

----- snip ----
[10783]: 10:59:33.019 [D] addon-storage.c:542: Media insertion detected on /dev/scd0
10:59:33.020 [D] hald_dbus.c:1652: udi=/org/freedesktop/Hal/devices/storage_model_DVDRAM_GSA_4163B, key=storage.removable.media_available
10:59:33.023 [I] hald_dbus.c:3052: entering, local_interface=1
10:59:33.023 [D] hald_dbus.c:3061: udi=/org/freedesktop/Hal/devices/storage_model_DVDRAM_GSA_4163B
10:59:33.023 [I] blockdev.c:1674: blockdev_rescan_device: udi=/org/freedesktop/Hal/devices/storage_model_DVDRAM_GSA_4163B
Run started hald-probe-storage (20000) (0)
! full path is '/usr/lib/hal/hald-probe-storage', program_dir is '/usr/lib/hal'
woohoo
[10785]: 10:59:33.025 [D] probe-storage.c:155: Doing probe-storage for /dev/scd0 (bus scsi) (drive_type cdrom) (udi=/org/freedesktop/Hal/devices/storage_model_DVDRAM_GSA_4163B) (--only-check-for-fs==1)
[10785]: 10:59:33.025 [D] probe-storage.c:163: Doing open ("/dev/scd0", O_RDONLY | O_NONBLOCK)
[10785]: 10:59:33.027 [D] probe-storage.c:169: Returned from open(2)
[10785]: 10:59:33.033 [D] probe-storage.c:310: Checking for optical disc on /dev/scd0
[10785]: 10:59:33.033 [D] probe-storage.c:318: Doing open ("/dev/scd0", O_RDONLY | O_NONBLOCK | O_EXCL)
[10785]: 10:59:33.036 [D] probe-storage.c:330: Open failed - Device Busy
[10785]: 10:59:33.136 [D] probe-storage.c:334: Attempting open w/ O_EXCL again
[10785]: 10:59:33.138 [D] probe-storage.c:348: PROBE HAS EXCLUSIVE LOCK ON CDROM
[10785]: 10:59:33.141 [D] probe-storage.c:390: media size = 2048
[10785]: 10:59:33.142 [D] probe-storage.c:398: PROBE CLOSED LOCK ON CDROM
10:59:33.142 [I] hald_dbus.c:1342: storage.cdrom.read_speed -> 13850
10:59:33.142 [I] hald_dbus.c:1342: storage.cdrom.write_speed -> 11080
10:59:33.143 [I] hald_dbus.c:1320: strlist elem storage.cdrom.write_speeds -> 11080
10:59:33.143 [I] hald_dbus.c:1320: strlist elem storage.cdrom.write_speeds -> 5540
10:59:33.143 [I] hald_dbus.c:1366: storage.removable.media_available -> True
10:59:33.143 [I] hald_dbus.c:1350: storage.removable.media_size -> 2048
pid 10785: rc=2 signaled=0: /usr/lib/hal/hald-probe-storage
10:59:33.151 [I] blockdev.c:1630: hald-probe-storage --only-check-for-media returned 2 (exit_type=0)
10:59:33.151 [I] blockdev.c:1646: Media insertion detected with file system on main block device; synthesizing hotplug add
10:59:33.151 [I] osspec.c:966: hal_util_find_known_parent: '/sys/block/sr0/f...

Read more...

Changed in linux:
status: New → Incomplete
Revision history for this message
tanager (tanager) wrote :

What isn't working is that the volume can never mount a blank CD or DVD!!! I have never seen:

cdrom: This disc doesn't have any tracks I recognize!

Here's what you requested:

tanager@tanager-laptop:~$ dmesg | tail
[222686.052597] end_request: I/O error, dev sr0, sector 320
[222686.105872] end_request: I/O error, dev sr0, sector 328
[222686.186495] end_request: I/O error, dev sr0, sector 328
[222686.247761] end_request: I/O error, dev sr0, sector 336
[111256.417965] end_request: I/O error, dev sr0, sector 340
[111256.565744] end_request: I/O error, dev sr0, sector 336
[111256.715285] end_request: I/O error, dev sr0, sector 344
[111256.887019] end_request: I/O error, dev sr0, sector 344
[222814.647556] UDF-fs: Partition marked readonly; forcing readonly mount
[111320.513102] UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume 'BECKET', timestamp 2007/03/31 04:45 (1f10)

Revision history for this message
tanager (tanager) wrote :

I amend: cdrecord seems to work, or look as if it will work. I have not tried Brasero. It is, as many have said, Nautilus that never sees media. Nor can I open the drive with blank media in it from the file browser. "No media in the drive"

Revision history for this message
Andy (andy-xillean) wrote :

hal.log inserted blank and data dvd.

Revision history for this message
Andy (andy-xillean) wrote :

Kern.log

Jun 9 11:47:02 ubuntu060608 kernel: [ 73.815990] eth1: no IPv6 routers present
Jun 9 11:52:26 ubuntu060608 kernel: [ 397.425860] UDF-fs: No VRS found
Jun 9 11:52:26 ubuntu060608 kernel: [ 397.452243] ISO 9660 Extensions: Microsoft Joliet Level 3
Jun 9 11:52:26 ubuntu060608 kernel: [ 397.488318] ISO 9660 Extensions: RRIP_1991A
Jun 9 12:08:43 ubuntu060608 kernel: [ 1374.318615] UDF-fs: No VRS found
Jun 9 12:08:43 ubuntu060608 kernel: [ 1374.349202] ISO 9660 Extensions: Microsoft Joliet Level 3
Jun 9 12:08:43 ubuntu060608 kernel: [ 1374.390843] ISO 9660 Extensions: RRIP_1991A

Revision history for this message
Andy (andy-xillean) wrote :

new lshal.txt (debug)

Revision history for this message
Martin Pitt (pitti) wrote :

tanager: you have a different problem then; the DVD you inserted wasn't blank, it already had an UDF file system. The problem seems to be that it cannot be read properly (all the I/O errors), which might indicate a hardware problem (cabling), or more likely a linux kernel bug if it works fine under Windows.

Revision history for this message
Martin Pitt (pitti) wrote :

Andy's logs show that hal cannot detect the media at all. If you do

  ps aux|grep addon-storage

do you see a process which looks like

  root 9689 0.0 0.0 24156 1272 ? S 08:21 0:00 hald-addon-storage: polling /dev/scd0 (every 2 sec)

?

Revision history for this message
Andy (andy-xillean) wrote :

~$ ps -aux|grep addon-storage
Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html
root 4916 0.0 0.2 3420 1156 ? S 06:39 0:00 hald-addon-storage: polling /dev/scd0 (every 2 sec)
me 5770 0.0 0.1 3008 772 pts/0 R+ 06:50 0:00 grep addon-storage

If I put a CD-rom Nautilus will pop-up with the contents of the CDROM
if I put a Data DVD or Movie DVD (unencrypted) it will do nothing.
if I put a blank CD-ROM it will do nothing

The chipset is a Via chipset

If I mount a Data DVD i get
~$ sudo mount /dev/dvd
mount: No medium found

I replace the cable with an 80 pin cable but no change

If I remove the DVD drive with the DVD in it and plug it into
the 2 gutsy boxes I have here and boot them up then every thing works.
I plug it back into the Hardy box and it will not work.

Revision history for this message
tanager (tanager) wrote :

Hm...Martin, this is a laptop. No cabling problems. I think I may have had a CD in there instead of a DVD; both were brand new, "blank" media. I can put in a DVD I've burned or a commercial movie, any CD I've put anything on or a mass-produced music CD - and all is fine. It's the new, "blank" media that won't work.

This drive not only worked fine under Windows, it worked fine under Gutsy! At least as far as reading blank CD-ROMS and burning whatever I wanted to them. I had not tried to burn or read DVDs yet.

Here's a thing: I ran dmesg | tail with a CD I'd put artwork on in the drive. Still got the same I/O errors, just lost the UDF-fs errors. Yet the CD is reading beautifully.

After the CD, I put the blank CD and the same DVD from before in and got:

tanager@tanager-laptop:~$ dmesg | tail
[212982.279995] end_request: I/O error, dev sr0, sector 324
[212982.397254] end_request: I/O error, dev sr0, sector 320
[212982.471630] end_request: I/O error, dev sr0, sector 328
[212982.592213] end_request: I/O error, dev sr0, sector 332
[212982.684542] end_request: I/O error, dev sr0, sector 328
[212982.777976] end_request: I/O error, dev sr0, sector 336
[212982.896201] end_request: I/O error, dev sr0, sector 340
[212982.987377] end_request: I/O error, dev sr0, sector 336
[212983.119758] end_request: I/O error, dev sr0, sector 344
[212983.239757] end_request: I/O error, dev sr0, sector 344

Note the lack of UDF-fs again? But those errors were there the first time I ran the command on this same blank media!

Anything else I should try?

Revision history for this message
reja (ubuntu-reja) wrote :

Same problem - reads cds and dvds fine, but when trying to record, it will not recognize disc in cd/dvd drive. Worked fine in Gutsy, but this problem started after upgrading to Hardy. Doesn't matter whether I use Nautilus, Rhythmbox, Brasero, etc.

With blank in drive:

 *-cdrom
       description: DVD writer
       product: DVD-RW DVR-108
       vendor: PIONEER
       physical id: 1
       bus info: scsi@1:0.0.0
       logical name: /dev/cdrom1
       logical name: /dev/dvd1
       logical name: /dev/scd0
       logical name: /dev/sr0
       version: 1.10
       capabilities: removable audio cd-r cd-rw dvd dvd-r
       configuration: ansiversion=5 status=open

Revision history for this message
reja (ubuntu-reja) wrote :

I got Brasero to recognize and write to a cd by going into the Root file system, then changing group permissions on /cdrom, /dev/cdrom1, and /dev/cdrw1 to myself, then changed group Folder Access to: Create and Delete Files. Don't know which one did the trick or if it was necessary to change permissions on all three, but it worked for me. I haven't tried it on any other burning software yet.

Revision history for this message
Brendan (brendanwatt) wrote :

I have the same problem in that i can no longer access any media on cdrom. My hardware is still fine on windows. But one thing to note is that when i upgraded to Hardy (at release time), i was able to access a music cd at least (didn't use any other feature from my dvd-rw). Since i apply all updated software on a regular basis, i can only presume something broke this ability. I can confirm i'm not able to mount any data cdrom or dvdrom, and have similar output to commands as listed above.

Noted above 2 x Pioneer models of DVD writers, mine is a Pioneer DVR-110 out of interest.

Revision history for this message
zertz (zertz) wrote :

seeing as the last person to follow had issues in their pioneer 110D dvd writer, i had a 112D dvd writer that wasn't working, and i had not updated the firmware for quite sometime (1.5years or so). i swapped it out to a windows machine just so i could update the firmware, after doing so, reinstalled hardy and it worked once again for me with no problems. i had even bought a sata burner which wasn't necessary, since i didn't expect this to work, but it did, for me, and that doesn't mean thats the solution to all these problems.

Revision history for this message
R (Chandra) Chandrasekhar (chandra) wrote :

I have reported similar behaviour in another Launchpad bug report. See:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/228624

and my report at

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/228624/comments/48

I repeat some of that info here:

hdparm -i /dev/scd1

gives

======
/dev/scd1:

 Model=PIONEER DVD-RW DVR-110 , FwRev=1.22 , SerialNo=
 Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
 RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
 BuffType=13395, BuffSize=64kB, MaxMultSect=0
 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes: pio0 pio1 pio2 pio3 pio4
 DMA modes: mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 *udma2 udma3 udma4
 AdvancedPM=no
 Drive conforms to: Unspecified: ATA/ATAPI-2,3,4,5

 * signifies the current active mode
======

ps aux|grep addon-storage

gives

======
root 5600 0.0 0.1 3420 1140 ? S Jul30 0:00 hald-addon-storage: no polling on /dev/fd0 because it is explicitly disabled
root 5617 0.0 0.1 3420 1148 ? S Jul30 0:00 hald-addon-storage: polling /dev/sdc (every 2 sec)
root 5620 0.0 0.1 3420 1156 ? S Jul30 0:00 hald-addon-storage: polling /dev/scd0 (every 2 sec)
root 5623 0.0 0.1 3420 1160 ? S Jul30 0:00 hald-addon-storage: polling /dev/scd1 (every 2 sec)
chandra 6799 0.0 0.0 3008 756 pts/1 R+ 00:42 0:00 grep addon-storage
======

and

the tail of dmesg with a blank CD-R in the drive is:

======
[ 590.465267] sr1: CDROM not ready. Make sure there is a disc in the drive.
[ 590.477516] sr1: CDROM not ready. Make sure there is a disc in the drive.
[ 603.758796] sr1: CDROM not ready. Make sure there is a disc in the drive.
[ 603.772636] sr1: CDROM not ready. Make sure there is a disc in the drive.
[ 717.377875] ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 717.377892] ata2.01: cmd a0/00:00:00:00:00/00:00:00:00:00/b0 tag 0
[ 717.377893] cdb 1b 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00
[ 717.377895] res 40/00:03:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 717.377898] ata2.01: status: { DRDY }
[ 722.412225] ata2: port is slow to respond, please be patient (Status 0xd0)
[ 727.390656] ata2: device not ready (errno=-16), forcing hardreset
[ 727.390665] ata2: soft resetting link
[ 732.580873] ata2: port is slow to respond, please be patient (Status 0x90)
[ 737.395481] ata2: SRST failed (errno=-16)
[ 737.395492] ata2: soft resetting link
[ 738.044299] ata2.00: configured for UDMA/33
[ 738.207340] ata2.01: configured for UDMA/33
[ 738.207361] ata2: EH complete
[ 1530.500330] sr1: CDROM not ready. Make sure there is a disc in the drive.
[ 1530.512764] sr1: CDROM not ready. Make sure there is a disc in the drive.
======

Please note that a blank CD-R is in the drive in question.

Can someone suggest some workaround please?

I am happy to provide more diagnostic reports if told what to provide.

Thanks.

Revision history for this message
R (Chandra) Chandrasekhar (chandra) wrote :

Perhaps this bug report is also relevant, at least to my case:

http://bugs.gentoo.org/show_bug.cgi?format=multiple&id=217465

Revision history for this message
Andy (andy-xillean) wrote :

Lets see. This problem has existed in Hardy since the first Alpha. It is still not fixed.
Reading and burning DVD media is unreliable in Ubuntu Hardy. That is a fact. I don't think it will be fixed in Hardy.
I think they are waiting to see if its fixed upstream or in Ibex. I dont think the ability to read or burn
DVDs is a priority for the Ubuntu people. I guess once you can browse the web then it works good enough.
But hey its free and u didnt have to pay for it so why complain?
I for one will not install Ubuntu Hardy on ANY more customers PCs until this FUNDAMENTAL problem is fixed.
I am installing PClinuxOS which works fine. And have installed it on 23 PCs so far none exhibit this problem.
So I will keep doing that until the Ubuntu people decide to make this problem,.. (a problem that has existed for
several months), a priority.

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you troll somewhere else than on the bug tracker? the bug just doesn't happen everywhere and it would be easier for somebody having the issue to debug it but looks like you prefer to rant there

Revision history for this message
tanager (tanager) wrote :

Trolling or not, I certainly still have the problem and nothing I've tried has worked. Maybe I'm not doing everything right, and maybe I'm not a Linux geek that understands all the suggestions here - maybe I'm not even savvy enough to provide the thread the reports and details needed to help understand the bug (I've tried, though!) - but does that mean a fix isn't merited? I hope Ubuntu developers didn't mean to imply that only Linux geeks should utilize Ubuntu and the rest of us are out of luck. I understand some folks have found workarounds, but I'm guessing not everyone who uses Ubuntu is capable of debugging on their own (I can't be the only one!!! I manage pretty well and it's all a great learning experience but I seem to have hit my knowledge limit on this one.)

I could be wrong, but the fact is that I did not have this problem under any previous Ubuntu release, and have had it since upgrading to Hardy. Logic suggests this is an issue with Hardy, as I have done nothing to my machine other than install regular upgrades and updates from Ubuntu. I'm otherwise very happy with Ubuntu and am just hoping this will not be an issue in the next release.

Revision history for this message
Sebastien Bacher (seb128) wrote :

nobody deny that this bug and the other 48659 bugs open in ubuntu should be fixed, the team working on those is just small and that's a lot of bugs, there is just a lot of different configurations, usecases, softwares, etc around and it's not possible to work on everything immediatly

it's understable that you and the other users who have hardware concerned by this are annoyed, as it's understable that
users who have a videocard not working under ubuntu are annoyed or users who have a machine which doesn't boot, etc

Leann, is there any extra information which would be required there or can the bug be confirmed now?

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Everyone,

One thing I'd be interested in is if people could test booting with the "all_generic_ide" boot option. It may be a possible workaround for some at the moment. (I saw in a previous comment Andy had tried this unsuccessfully, but I'd like to get feedback from others as well) If you can also comment on the version of the kernel you are running that would be great too. You can get this by doing 'cat /proc/version_signature'

Next, I'd like to know if anyone has had the chance to confirm this is still an issue with the upcoming Intrepid Ibex 8.10 release. We'll want to make sure we have this fix resolved in the upcoming release first and then backport any necessary patches to Hardy if possible. You can get the latest Alpha release of Intrepid (Alpha 3 at the time of this posting) from http://www.ubuntu.com/testing . It would be great if someone would be willing to test. If the issue still exists under Intrepid please attach an updated full dmesg output after you've inserted a blank CD.

We really appreciate everyone's patience as we try to resolve this issue. Please let us know your results. Thanks in advance.

Revision history for this message
R (Chandra) Chandrasekhar (chandra) wrote :

Leann Ogasawara wrote:
> Hi Everyone,
>
> One thing I'd be interested in is if people could test booting with
> the "all_generic_ide" boot option.

Booting with all_generic_ide=1 as a boot option does not change things.
I inserted a blank CD-R into the Pioneer drive and while the green LED
lights up all the time, I do not get any response about a blank medium
found in the drive. Please see my report dated 25 Jul 08 at:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/228624/comments/48

FYI, I have cut and pasted from dmesg what I think might be relevant,
after inserting a blank CD:

--- snip ----
[ 18.635185] ata2.00: ATAPI: LITEON DVD-ROM LTD-165H, CH0J, max UDMA/44
[ 18.635215] ata2.01: ATAPI: PIONEER DVD-RW DVR-110, 1.22, max UDMA/66
[ 18.635231] ata2.00: limited to UDMA/33 due to 40-wire cable
[ 18.635234] ata2.01: limited to UDMA/33 due to 40-wire cable
[ 18.706813] usb 2-1: new low speed USB device using uhci_hcd and address 2
[ 18.798943] ata2.00: configured for UDMA/33
[ 18.888823] usb 2-1: configuration #1 chosen from 1 choice
[ 18.970810] ata2.01: configured for UDMA/33
--- snip ----
[ 18.972043] scsi 1:0:0:0: CD-ROM LITEON DVD-ROM LTD-165H CH0J
PQ: 0 ANSI: 5
[ 18.978903] scsi 1:0:1:0: CD-ROM PIONEER DVD-RW DVR-110 1.22
PQ: 0 ANSI: 5
--- snip ----
[ 19.001417] Driver 'sd' needs updating - please use bus_type methods
--- snip ----
[ 19.001682] sda:<4>Driver 'sr' needs updating - please use bus_type methods
--- snip ----
[ 19.153587] sr0: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray
[ 19.153592] Uniform CD-ROM driver Revision: 3.20
[ 19.153640] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 19.184639] sr1: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2
cdda tray
[ 19.184718] sr 1:0:1:0: Attached scsi CD-ROM sr1
--- snip ----

> It may be a possible workaround for some at the moment. (I saw in a
> previous comment Andy had tried this unsuccessfully, but I'd like to
> get feedback from others as well) If you can also comment on the
> version of the kernel you are running that would be great too. You
> can get this by doing 'cat /proc/version_signature'

Ubuntu 2.6.24-19.36-generic

> Next, I'd like to know if anyone has had the chance to confirm this
> is still an issue with the upcoming Intrepid Ibex 8.10 release.
> We'll want to make sure we have this fix resolved in the upcoming
> release first and then backport any necessary patches to Hardy if
> possible. You can get the latest Alpha release of Intrepid (Alpha 3
> at the time of this posting) from http://www.ubuntu.com/testing . It
> would be great if someone would be willing to test. If the issue
> still exists under Intrepid please attach an updated full dmesg
> output after you've inserted a blank CD.

Do I need to run the second kernel in a VirtualBox VM? I have experience
building from Ibex source package in prevu for applications, and running
them, but never building a new kernel, let alone run it. If given a link
on how to do it, I am willing to try, because I want to see the back of
this bug.

Many thanks for your attention.

Chandra

Revision history for this message
Shang Wu (shangwu) wrote :

Hi everyone,

Has anyone tried to reboot the machine with the blank media in it and see if the machine can recognize the media and burn properly this way?

Revision history for this message
Ian Lowrie (nzukca-deactivatedaccount) wrote :

Interesting question.

I just did this and the DVD mounted and I was able to burn an ISO using Brasero!
A quick test suggests that blank DVDs are automounted - presumably till I next reboot without a blank dvd. Note that I only had mounting problems with DVDs, CDs are OK. Burner is LG GSA4082B.

Revision history for this message
Ian Lowrie (nzukca-deactivatedaccount) wrote :

Results of further testing:

Immediately after the above test, I was able to play a DVD movie (which was not happening before- at least since I upgraded to Hardy- alll was OK in Gutsy), and I went to bed relatively happy that a crude workaround was in place.

Now I cant repeat this last part... inconsistency? Still after a reboot with a blank DVD in place it automounts and Brasero sees it...

So!!!! Although I was able to burn an ISO and then do another one, it appears that after I closed the DVD application (Brasero and/or VLC) and with no disk in the drive things changed, and 'auto-mount' failed to happen thereafter. (Sorry, Im a bit of a newby and 'auto-mount' might not be the correct technical term!)

I also find that after a reboot with a blank DVD, if I immediately replace the DVD with a movie, the DVD burner 'disappears', and does not return - ie it is not a visible/mountable device (until a further reboot with a blank DVD in place...)

All very strange - I think that I will have to roll back to Gutsy after all. I was just getting into playing with video editing and compiling DVDs!!! ;^(

Ian

Revision history for this message
Shang Wu (shangwu) wrote :

@Nzukca

Can you provide me with your lshal command output from the terminal with and without booting the DVD in your DVD-ROM?

Here is how you can run the lshal command:
0. Boot with the DVD in your DVD-ROM drive
1. Open terminal from Applications> Accessories
2. Copy/Paste the following in the terminal:

lshal > lshal-with_dvd.txt

-------------------------------------------------
Repaet the same step without DVD, but use the following command:

lshal > lshal-without_dvd.txt

/////////////////////

Now, you will see 2 files under your home directory. Please zip them and upload them. :)

Revision history for this message
Ian Lowrie (nzukca-deactivatedaccount) wrote :

Shang

i did the test and the two files are in the archive ian.zip attached.
Hope this helps
Let me know if anything else needed...

Ian

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Mike Perrin (mperrin) wrote :

The computer I originally had the problem with is no longer available, but I installed 8.04 on a Biostar M7VKQ Duron 800 with the same Plextor model PX-W2410TA CD burner. The problem occurred as expected. I downloaded linux-image-2.6.27-2-generic_2.6.27-2.3_i386.deb from http://packages.ubuntu.com/intrepid/base/, installed it with dpkg, rebooted and verified that the new kernel was running by:
mike@benchwork:~$ cat /proc/version
Linux version 2.6.27-2-generic (buildd@palmer) (gcc version 4.3.2 (Ubuntu 4.3.2-0ubuntu1) ) #1 SMP Thu Aug 28 17:20:02 UTC 2008
Unfortunately, the new kernel did not fix the problem. Did I miss something?

Revision history for this message
Mike Perrin (mperrin) wrote :

I installed Intrepid alpha 4 on the system described in my previous post. A blank CD was recognized and the icon appeared on the Desktop. I used Synaptic to install the 2.26.27-2-generic kernel and rebooted; a blank CD was recognized and the icon appeared. Results so far: It won't work in Hardy and it won't break in Intrepid. Any suggestions?

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks for the update Mike. So this would appear to be resolved for Intrepid. Although from your comments it would appear this was not resolved with the newer 2.6.27 kernel as you mentioned originally testing showed no improvement with 2.6.27 but after an Intrepid Alpha4 installation this bug was resolved.

Can anyone else test and report back their results as well? Thanks.

Revision history for this message
Andy (andy-xillean) wrote :

How do i download and install the new 2.6.27 kernel in Hardy? I tried
apt-cache search 2.6.27 and nothing showed up.

I have the same problems here. This seems to be more common
with PATA DVD drives. The DVD-ROMs and DVD-RWs will only recognize CDs and the
DVD-RWs wont even read a blank DVD.

Revision history for this message
Jamie Lokier (jamie-shareable) wrote :

Leann Ogasawara wrote:
> Thanks for the update Mike. So this would appear to be resolved for
> Intrepid. Although from your comments it would appear this was not
> resolved with the newer 2.6.27 kernel as you mentioned originally
> testing showed no improvement with 2.6.27 but after an Intrepid Alpha4
> installation this bug was resolved.
>
> Can anyone else test and report back their results as well? Thanks.

I'm under the impression that the problem in Hardy occurs with
upgrades from an earlier Ubuntu version, not fresh installs. Is that
wrong? If that's so, a fresh Intrepid installation wouldn't really
test an upgrade to Intrepid (Gutsy->Hardy->Intrepid).

Revision history for this message
Andy (andy-xillean) wrote :

This happens with either fresh install or upgrades. Most of the times
I have ran into this issue is on new fresh installs.

Revision history for this message
Mike Perrin (mperrin) wrote :

Andy,

You can download the 2.6.27 deb file from http://packages.ubuntu.com/intrepid/base/ and install it with dpkg. Refer to my 2008-08-30 post.

Mike

Revision history for this message
R (Chandra) Chandrasekhar (chandra) wrote :

Leann Ogasawara wrote:
> Thanks for the update Mike. So this would appear to be resolved for
> Intrepid. Although from your comments it would appear this was not
> resolved with the newer 2.6.27 kernel as you mentioned originally
> testing showed no improvement with 2.6.27 but after an Intrepid Alpha4
> installation this bug was resolved.
>
> Can anyone else test and report back their results as well? Thanks.

I have tried the Kubuntu Intrepid Alpha-5 live CD on my Hardy system and
booted into it, running the 2.6.27 kernel.

I am sorry to say that none of the following is recognized either by
Dolphin or by k3b when inserted into the PIONEER DVD-RW DVR-110 drive:

(a) recorded CD-R

(b) blank CD-R

(c) audio CD.

It is not merely blank media but also recorded media.

(The new KDE 4.1 desktop does not seem to display inserted media but
that is entirely another issue altogether!)

This bug is threatening to result in serious loss of function if it
continues to persist into Intrepid Ibex.

I could not compile the 2.6.27 kernel using prevu because of failed
dependencies, and cannot comment on the performance of the 2.6.27 kernel
within Hardy.

I am happy to furnish further data if told what to acquire: I really
want to see this bug squashed.

Thanks.

Revision history for this message
Mike Perrin (mperrin) wrote :

Update to my 2008-08-31 post. I installed 8.10-beta on the same system and a blank CD was recognized when inserted. So on my hardware the problem has not occurred with Intrepid to date.

Revision history for this message
christianvaldes (aaronvaldes) wrote :

my current kernel is 2.6.24-10 generic
I am having the same issue with this drive.
 I am going to install a kernel update (2.6.24-21) that just came out for Hardy.
Did not fix issue...
So can someone confirm that this will work with Intrepid.
It comes out in two weeks.

Revision history for this message
Andy (andy-xillean) wrote :
Download full text (5.1 KiB)

Downloaded ubuntu live/DAILY intrepid from cdimages.ubuntu.com today on Oct18.
Installed to USB drive booted the system that has problems reading DVDs in Hardy, Inserted blank DVD, nothing happens. I try to click on the DVD/RW drive in Computer inside gnome and i get the same message . "Unable to mount location - No media in drive" in Hardy I have
ls -l /dev|grep scd0
cdrom ->scd0
cdrw ->scd0
sr0 ->scd0

In Intrepid daily I have
cdrom ->scd0
cdrw ->scd0
sr0 ->scd0
dvdrw1 ->scd0
dvd1 -> scd0

So i can confirm Booting from a live USB with Intrepid daily Oct18-2008
Inserting a blank DVD-R into the drive does nothing.
Inserting a blank CD pops up a "Blank CD-R dialog" asking what to do with blank CD.

here is my hardware.

ubuntu@ubuntu:/dev$ hdparm -i /dev/scd0

/dev/scd0:

 Model=OPTORITEDVD RW DD1205 , FwRev=100e , SerialNo=
 Config={ Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
 RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
 BuffType=unknown, BuffSize=1024kB, MaxMultSect=0
 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
 IORDY=on/off, tPIO={min:383,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes: pio0 pio1 pio2 pio3 pio4
 DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 *udma2
 AdvancedPM=no

 * signifies the current active mode

*-cdrom
             description: DVD writer
             product: DVD RW DD1205
             vendor: OPTORITE
             physical id: 1
             bus info: scsi@6:0.0.0
             logical name: /dev/cdrom1
             logical name: /dev/cdrw1
             logical name: /dev/dvd1
             logical name: /dev/dvdrw1
             logical name: /dev/scd0
             logical name: /dev/sr0
             version: 100e
             serial: 'OPTORITEDVD RW DD1205 100e0
             capabilities: removable audio cd-r cd-rw dvd dvd-r
             configuration: ansiversion=5 status=ready
           *-medium
                physical id: 0
                logical name: /dev/cdrom1

 This is with a blank CD-R in the drive

*-pci:1
          description: PCI bridge
          product: CK804 PCIE Bridge
          vendor: nVidia Corporation
          physical id: b
          bus info: pci@0000:00:0b.0
          version: a3
          width: 32 bits
          clock: 33MHz
          capabilities: pci pm msi ht pciexpress bus_master cap_list
          configuration: driver=pcieport-driver
     *-pci:2
          description: PCI bridge
          product: CK804 PCIE Bridge
          vendor: nVidia Corporation
          physical id: c
          bus info: pci@0000:00:0c.0
          version: a3
          width: 32 bits
          clock: 33MHz
          capabilities: pci pm msi ht pciexpress bus_master cap_list
          configuration: driver=pcieport-driver
     *-pci:3
          description: PCI bridge
          product: CK804 PCIE Bridge
          vendor: nVidia Corporation
          physical id: d
          bus info: pci@0000:00:0d.0
          version: a3
          width: 32 bits
          clock: 33MHz
          capabilities: pci pm msi ht pciexpress bus_master cap_list
          configuration: driver=pcieport-driver
     *-pci:4
        ...

Read more...

Revision history for this message
Geert Premereur (geert-subcribe1) wrote :

Just to let you know that I just upgraded to the new 2.6.24-21-generic Hardy kernel and CD reading works again for me. I wasn't able to read any kind of CD/DVD under 2.6.24.19.

lshw -C disk
  *-cdrom
       description: DVD writer
       product: DVD LS DW1655
       vendor: BENQ
       physical id: 0.0.0
       bus info: scsi@7:0.0.0
       logical name: /dev/scd0
       logical name: /dev/sr0
       logical name: /media/Ubuntu 7.10 i386
       version: BCAB
       capabilities: removable audio cd-r cd-rw dvd dvd-r
       configuration: ansiversion=5 mount.fstype=iso9660 mount.options=ro,nosuid,nodev,noatime,relatime state=mounted status=ready
     *-medium
          physical id: 0
          logical name: /dev/scd0
          logical name: /media/Ubuntu 7.10 i386
          configuration: mount.fstype=iso9660 mount.options=ro,nosuid,nodev,noatime,relatime state=mounted

Revision history for this message
Mike Perrin (mperrin) wrote :

On my problem hardware, Hardy with the 2.6.24-21-generic kernel and all other updates still does not recognize a blank CD. So for me the score remains: Hardy 0, Intrepid 100.

Revision history for this message
g7kse (g7kse) wrote :

Unfortunately after an upgrade to 8.10. The problem is still there for me. I can see blank DVD's, play CD's but pre recorded DVD's still not being recognised

lshw -C disk gives -
With pre recorded DVD:
  *-cdrom
       description: DVD writer
       product: DVD RW DW-D22A
       vendor: SONY
       physical id: 0.0.0
       bus info: scsi@2: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
       version: BYS3
       capabilities: removable audio cd-r cd-rw dvd dvd-r
       configuration: ansiversion=5 status=nodisc

With Blank DVD:

  *-cdrom
       description: DVD writer
       product: DVD RW DW-D22A
       vendor: SONY
       physical id: 0.0.0
       bus info: scsi@2: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
       version: BYS3
       capabilities: removable audio cd-r cd-rw dvd dvd-r
       configuration: ansiversion=5 status=ready
     *-medium
          physical id: 0
          logical name: /dev/cdrom

did the all_generic_ide=1 in grub as well as well
Can I give any more information?

Revision history for this message
kevin (kevin-penrose) wrote :

I have been following this bug since a very similar thing has happened to me.
I'm running Kubuntu Hardy Heron with all updates applied. Kernel 2.6.24-21 is in place. As recently as 2 - 3 weeks ago I was able to burn cd's and dvd's with no problem. Could play dvd's that I burned, didn't try commercial dvd's. Audio cd (both my burns and store bought) played perfectly well.
Some upgrade within that time period has completely futzed the cd/dvd system. Putting in blank cd's or dvd's no long results in the blank cd/dvd dialog popping up. Using k3b to set up and audio cd or dvd iso works up to the point where it requests that blank media be inserted. Doing so doesn't result in the media being recognized. At this point I haven't tried to play other dvd's or cd's as I use this computer primarily for burning dvd's from my video camera.
The cd/dvd burner is a Lite-On but I don't know the model right now. I'm at work, machine is at home. I plan to upgrade to Interpid over the weekend, so perhaps that will fix the problem, but I can state without any reservation, that Hardy worked fine up until very recently at which time some update must have broken the sub-system responsible for detecting blank media.

If you would like to see some dumps from my system, let me know, I'd be happy to supply them before I do the upgrade.

Revision history for this message
Mark (mae15) wrote :

I was able to recognize and burn onto blank CDs, then I clicked "no action" in the prompt window after inserting another blank CD, after which that CD ceased to be recognized, and I haven't been able to recognize one since.

Revision history for this message
kernel-janitor (kernel-janitor) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
larry rhoads (lrhoads7) wrote :

Hi folks - complete rookie here but this problem is still an issue. I'm using Jackalope, have both a CD burner and DVD burner and neither work unless booted with blank media. I've looked and looked and see no resolution this problem. I'd be perfectly willing to do whatever I can to assist if someone wants to use me as a guinea pig - as I said, complete rookie with Ubuntu but very capable at following explicit directions. Here is the issue, as I understand it. Media will not mount unless session was booted with blank media. Intermittent ability to burn cd and/or DVDs, depending on whether the particular session is seeing the drives. I've tried to use native gnome cd burning and just downloaded and installed k3b, which displays the error "K3b did not find an optical writing device in your system." I'm using 64-bit AMD system with unbuntu jaunty 64 bit with latest updates applied yesterday, 6/20/2009. Any help out there for this?

Thanks,

Larry

Changed in nautilus-cd-burner (Ubuntu):
status: Invalid → New
Revision history for this message
R (Chandra) Chandrasekhar (chandra) wrote :

I used to experience this problem with my previous i386 PC which had a Pioneer DVD reader-writer. The problem never went away.

I am now on an AMD 64 machine with an ASUS DVD reader-writer and am running Jaunty. There is no problem now.

It would perhaps be useful if you stated your brand and model of DVD reader-writer. I think that this problem arises with certain brand/model combinations of CD/DVD reader-writers and their device-level interactions with the kernel.

Revision history for this message
driven1 (dbaldwin1911) wrote :

I have this problem in Jaunty Ubuntu, amd64. This is from lshw with blank media in the drive. Apparently, the media is never recognized and mounted by Nautilus. This is a major annoyance. I tried rebooting with the media in the drive, but it didn't help.

*-cdrom
                description: DVD-RAM writer
                product: DVD-RAM GH22NP20
                vendor: HL-DT-ST
                physical id: 0.0.0
                bus info: scsi@6: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
                version: 1.00
                serial: [HL-DT-STDVD-RAM GH22NP201.0008/03/25 7U01
                capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
                configuration: ansiversion=5 status=nodisc

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance.

Changed in nautilus-cd-burner (Ubuntu):
status: New → Incomplete
Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Closing this bug because of no response.

Changed in nautilus-cd-burner (Ubuntu):
status: Incomplete → Invalid
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.