Matshita DVD-RAM UJ-851S DVD-RAM doesn't always appear

[Jessica Litwin]

I have a HP Pavilion dv6245us that uses a Matshita DVD-RAM UJ-851S as the dvd+-r/rw drive. Using the 2.6.22-14-generic kernel (gutsy), the CD-ROM drive does not always appear in dmesg as valid hardware. Rebooting usually fixes this problem. Watching the BIOS output, the DVD-RAM drive is consistently detected and works fine in other operating systems. This was an issue that seemed to appear less in the 64-bit version of Gutsy.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux-source-2.6.22.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' after experiencing the issue and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

[Brian Murray (brian-murray)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.