Re: Media autochanger driver changed behavior.

[Jesper Krogh <jesper@krogh.cc>]

James Bottomley wrote:
> On Thu, 2008-07-10 at 07:59 +0200, Jesper Krogh wrote:
>> James Bottomley wrote:
>>> On Wed, 2008-07-09 at 23:56 +0200, Jesper Krogh wrote:
>>>> James Bottomley wrote:
>>>>> On Wed, 2008-07-09 at 22:51 +0200, Jesper Krogh wrote:
>>>>>> Hi.
>>>>>>
>>>>>> Upgrading the OS from an quite old kernel to a newer (2.6.24) changed
>>>>>> the behavior of the "ch" driver. Now it does a inventory to the changer
>>>>>> on load. This command makes the barcode-reader scan the entire library
>>>>>> at driver load time.
>>>>> Do I take it from this that your old kernel simply didn't auto load the
>>>>> ch driver?  or that something has changed in the way the driver now
>>>>> works?
>>>> It sure did load the driver and it worked just fine. It just didnt make 
>>>> the library unit force scan the barcodes. (the library do that on bootup 
>>>> by itself, but it can be forced with mtx over the changer device).
>>>>
>>>> mtx -f /dev/changer inventory => Force scans barcodes
>>>> mtx -f /dev/changer status => Reads out the barcodes labels and slots
>>>> from the changer device without forcing the library to scan.
>>>> (note I dont know if it is library specific).
>>> OK, so it's not the autoloading code which I thought it might be.
>>>
>>> Which is the latest version of the kernel that works? ... that will at
>>> least give me the set of changes to look at.
>> I cant give you that, since I havent testet all, but I'm quite sure 
>> 2.6.20 worked,
>> completely sure that 2.6.15 was Ok.
>>
>> I know this is a large timespan, sorry.
> 
> It would be enormously helpful if you could boot 2.6.20 and confirm.
> There are 3 changes to ch between 2.6.20 and 2.6.24.  There are 8
> between 2.6.15 and 2.6.24.

I'll get it done and report but, but we're a bit behind on the 
backup-schedules. So when the system has catched up I'll do some testing.

-- 
Jesper