| Summary: | when automatically erasing a cd-rw before a burn, the cd tray opens in my laptop prompting me to manually close the tray | ||
|---|---|---|---|
| Product: | [Applications] k3b | Reporter: | Reginald Thomas <rethomas> |
| Component: | Burning/Hardware | Assignee: | Sebastian Trueg <trueg> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | CC: | richlv |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Reginald Thomas
2004-03-09 18:08:18 UTC
actually this is quite a problem for me - i am not able to erase cd-rw in my laptop at all (and thus also no recording is possible). when k3b tries to erase cd-rw it diplays "erasing" window, shortly afterwards ejects cd-rom. then it prompts to manually reload it and press [ok]. the problem is, for some reason cd-rw is not erased. i've tried different sequences, nothing helps. this is true for 3 modes i found to erase cd-rw : a) tools->cd->erase rw; b) answer yes to the question when trying to burn someting on rw; c) select an option to automatically erase rw. as i understand, creator of this issue at least get's his cd-rw erased, so i probably have another problem. just in case i'll provide additional details about hardware : fujitsu-siemens lifebook c-1020; qsi cd-rw/dvd-rom sbw-081 fwrev=nx09 (first line from hdparm -i) _if_ it should erase cd-rw anyway i'll file another issue; if the problem is with automatic reloading, probably handling of manual reloading is at the fault. it's ok for me to reload it manually, but erasing it doesn't work, so unfortunately rws are not usable in laptop... did you ever try "full" erasing or cdrdao (advanced settings->manual writing app selection) a note about my recording problem : probably hardware problem, as adding -immed to cdrecord parameters fixed this problem. i still have to reload manually, disks are written correctly. from what i have seen, in some cases device shows previous file state if there was no ejecting after writing. if this is the data that is reported by device there probably is no way to make it work without ejecting the disk. It is not possible to reload without ejecting Why not? At what level would this have to be changed to avoid this behaviour? Kernel-level? AFAIK yes, linux needs the medium to be reloaded in order to return to a proper state. |