How to get K3b to find optical drive? SOLVED

[Michael Butash]

I've had this happen over time when a drive is nearing EOL, as generally 
the drive would get flaky and not show up occasionally.  Replacing it 
with a new one worked...  This has happened several times with internal 
or usb units.

Run "tail -f /var/log/syslog" to see if udev finds it when inserted and 
creates the /dev/sr0 interface for it.  Flaky ones would usually probe, 
but not respond correctly giving errors in syslog, and thus not fully 
building the /dev/sr0 interface being amiss.

-mb


On 12/08/2012 12:26 PM, joe at actionline.com wrote:
>
> Thanks to all.  It is working now.
> Actually, I did not change anything,
> but when I tried it again today,
> it worked fine.
>
> ---------
>> You did not say what distro or release you are running so some answers
>> people supply may not be right for your system.  That said, see below:
>>
>> On Fri, Dec 7, 2012 at 12:49 PM,<joe at actionline.com>  wrote:
>>
>>> I have an external dvd burner connected to my computer,
>>> but when I try to run K3b, the following message appears:
>>>
>>>> No optical drive found.
>>>> K3b did not find any optical device in your system.
>>>> Solution: Make sure HAL daemon is running, it is used
>>>> by K3b for finding devices.
>>>
>>> How can I determine if the HAL daemon is running?
>>> Or if it is not, what do I need to do to make sure that
>>> it always does run?
>>>
>>
>> On my Ubuntu 12.04 and 12.10 systems, I do not see a hal daemon running,
>> but plugging in an external USB CD/DVD drive is visible and usable (I am
>> not set to use k3b).  That makes me wonder if hal has been replaced.
>>
>> Are you plugging in the external burner BEFORE starting k3b?  Sometimes a
>> program queries for available devices only on program start.  If you start
>> k3b first, exit and only start it AFTER plugging in the device.  Also, try
>> having some media in the drive before starting k3b.
>>
>> Is it only k3b that does not see the external drive.  If the who system
>> does not see it, the problem is more likely the external drive or not
>> having a valid driver for it.  You might try an lsusb to see if it is even
>> visible to Linux.  I get "Bus 002 Device 004: ID 0411:01dc BUFFALO INC.
>> (formerly MelCo., Inc.)".
>>
>> You could also do an lshw -short before plugging it in and another after
>> to
>> see if another line was listed such as "/2             scsi7   storage".
>>
>> If you don't, try some other external USB device as a test.
>>
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------
>>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>>> To subscribe, unsubscribe, or to change your mail settings:
>>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>>
>>
>>
>>
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>
>