Ubuntu Hardy & Gutsy unables to mount DVD-RAM

Bug #219918 reported by Daniel
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Since Gutsy , Ubuntu is unable to automaticly mount DVD-RAM.
(Dapper & Edgy just needed a modification of Fstab and worked properly...)
In Gutsy, I used to work with the attached scripts, but they don't work any more in Hardy.
No way to use DVD-RAM without MSWin!!!

Tags: cft-2.6.27
Revision history for this message
Daniel (bigweld) wrote :
Revision history for this message
Daniel (bigweld) wrote :
Revision history for this message
Daniel (bigweld) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote : Package assigned

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.

Revision history for this message
Brian Murray (brian-murray) wrote : Need more information

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' 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!

Revision history for this message
Guenter (ubuntu-linux-stueck) wrote :
Revision history for this message
Guenter (ubuntu-linux-stueck) wrote :
Revision history for this message
Guenter (ubuntu-linux-stueck) wrote :
Revision history for this message
Guenter (ubuntu-linux-stueck) wrote :
Revision history for this message
Guenter (ubuntu-linux-stueck) wrote :

Because I have exactly the same problem as Brian, I have attached my output as requested.

But I'm not sure if this is really a kernel problem.

Revision history for this message
Brian Murray (brian-murray) wrote :

Your 'dmesg' log file doesn't seem to capture a DVD-RAM disc being inserted into the drive. Could you please add the output of 'dmesg' after inserting a DVD-RAM disc and trying to mount it? Thanks again.

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
Michele Mangili (mangilimic) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
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.