| Summary: | Sata Dvd burner (SH-S183A) not working after upgrade to 2.6.24-gentoo-r4 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Pierre AUSSAGUEL <pierre_aussaguel> |
| Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | boagenator |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | linux-2.6.25 | ||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
.config for 2.6.24 kernel
.config for 2.6.22 kernel dmesg output lshal output lspci output ls -lah /dev/cdr* output - before launching k3b ls -lah /dev/cdr* output - after launching k3b k3b output cdrecord output |
||
|
Description
Pierre AUSSAGUEL
2008-05-09 15:25:40 UTC
(In reply to comment #0) > Burning does works using 2.6.22-gentoo-r9, and does not with 2.6.24-gentoo-r4 > neither with 2.6.24-tuxonice-r4 > > On 2.6.24 the burner is seen by the system, but after having lauched K3B, the > drive disappeared from system. I am no more able to open tray. > I have to power off the computer to see ot again (reboot is not sufficient) What does "see it again" mean? > More details in this topic : > http://forums.gentoo.org/viewtopic.php?p=5088184#5088184 > > I can attach any files here if needed. > > Reproducible: Always > > Steps to Reproduce: > 1. boot with 2.6.24 kernel > 2. launch k3b So is it a k3b problem or does any cd/dvd burning app cause the drive to "disappear"? > Actual Results: > drive has "disappeared" from system Again, what does this mean? Is the device node still present? Does the kernel (dmesg?) complain of a SATA channel being taken offline or a SATA device (controller?) no longer responding? (In reply to comment #0) > More details in this topic : > http://forums.gentoo.org/viewtopic.php?p=5088184#5088184 I'm sorry, but bugzilla doesn't work that way. bugs.gentoo.org is the place where you present information as accurate and complete as possible so that someone on the Gentoo developer team can be assigned to work on the problem. Presently, it may be your faulty SATA controller/SATA drive, a change in the kernel that causes a bug or merely exposes a bug, it could be lots of things. Either you present the bug you have found here, or you don't do it at all. Please reopen this bug when you have found the cause of your problem. Created attachment 152671 [details]
.config for 2.6.24 kernel
Created attachment 152673 [details]
.config for 2.6.22 kernel
Created attachment 152675 [details]
dmesg output
Created attachment 152677 [details]
lshal output
Created attachment 152679 [details]
lspci output
Created attachment 152681 [details]
ls -lah /dev/cdr* output - before launching k3b
Created attachment 152683 [details]
ls -lah /dev/cdr* output - after launching k3b
Created attachment 152685 [details]
k3b output
Created attachment 152687 [details]
cdrecord output
Disappeared means that there is no mode /dev/sr0 in the system. Using gnomebaker finds the burner, but says the media is not a recordable media (I tried with 3 different blank dvd) Il will emerge other burning apps if needed. (In reply to comment #12) > Disappeared means that there is no mode /dev/sr0 in the system. > sorry for the typo ... read "no more" More info : I emerged brasero and Xcdroast. - Brasero says that the media is unwritable although I tried 3 of them - Xcdroast says that I only can burn CD's and that the DvD support is not installed. I have dvd and dvdr in my USE flags, and dvd+rw-tools is emerged. (In reply to comment #12) > Disappeared means that there is no mode /dev/sr0 in the system. > > Using gnomebaker finds the burner, but says the media is not a recordable media > (I tried with 3 different blank dvd) > > Il will emerge other burning apps if needed. Why would you do that? The problem obviously isn't in userland but in the kernel. At least, that's what the Summary suggests... That's what I think too, since I am able to burn using 2.6.22 ... But you asked me in comment "1 "So is it a k3b problem or does any cd/dvd burning app cause the drive to "disappear"?". The answer is "no ... but" K3B is the only app I tested that causes it to disappear, the other does not want to burn, but /dev/sr0 is still there. Could you try with 2.6.25, please? There have been some fixes for similar bugs since 2.6.24 so it is worth trying first. 2.6.25-gentoo-r3 solves the problem. Thank you. Excellent, thanks. upgrading to 2.6.25 works. In my case 2.6.25-tuxonice-r3 I'm getting this same issue with 2.6.26. I can read data from my drive just fine but writing is a no go.
Not sure what more "relevant" information I can give, my drivers are obviously set up correctly or I wouldn't be able to read the drive, my user is in the relevant permissions groups. My /dev/sr0 does not "disappear" like this chap claims, I just get this from k3b:
(K3bDevice::HalConnection) initializing HAL >= 0.5
Mapping udi /org/freedesktop/Hal/devices/storage_model_DVD_RW_ND_2500A to device /dev/sr0
/dev/sr0 resolved to /dev/sr0
(K3bDevice::Device) could not open device /dev/sr0 for reading
(No such device or address)
could not open device /dev/sr0 (No such device or address)
/dev/sr0 resolved to /dev/sr0
(K3bDevice::Device) could not open device /dev/sr0 for reading
(No such device or address)
could not open device /dev/sr0 (No such device or address)
Devices:
------------------------------
ninpo@ncc-1701-e ~ $ ls -al /dev/sr0
brw-rw---- 1 root cdrom 11, 0 Aug 15 2008 /dev/sr0
Let me know if there's anything else I can provide. I couldn't reopen the bug so..
|
