Re: Bug 11581

[Borislav Petkov <petkovbb@googlemail.com>]

On Mon, Nov 10, 2008 at 01:02:02PM +0100, Santiago Vila wrote:
> On Mon, 10 Nov 2008, Borislav Petkov wrote:
> 
> > Ok, so it looks like your drive gets puzzled again by a
> > GET_CONFIGURATION command despite 2.6.18 which used to work, as you say.
> > But I think it fails this time because you've updated to debian testing
> > and, correct me if I'm wrong, but the udev utility cdrom_id came with
> > the update and it sends all those GET_CONFIGURATION commands. Have you
> > thought of updating the drive's firmware - that helps sometimes?
> 
> Ok, I tried that today, using Wine and the root account, but the unit
> is not detected by the firmware updating utility. Which of the multiple
> patched kernels should I try? Neither 2.6.18 or 2.6.26 from Debian
> seem to work this time.

I'm afraid that you need to boot into Windoze in order for the firmware
update utility to recognize your drive. I'm pretty sure there are some
ways to that without windows but they could be risky and damage your
drive permanently. I'll think of something better and get back to you.

-- 
Regards/Gruss,
    Boris.