BUG: unable to handle kernel paging request at f8dbf000 "isight_firmware"

BUG: unable to handle kernel paging request at f8dbf000 "isight_firmware"

[Justin Mattock]

Hello; first I want to thank's for the acknowledgment "that really
touches me man",
Now on to the status with isight firmware, It seems The two modules
are loading uvcvideo and isight_firmware, but there not talking with
each other upon booting,
 under dmesg i see:

[   14.971002] firmware: requesting isight.fw
[   15.183152] usbcore: registered new interface driver isight_firmware

[   16.849152] usbcore: registered new interface driver uvcvideo

I've changed /etc/modules with the order of loading, but still same
results, usually to get it working I need to start the system, and
then once up and running
I need to rrmod uvcvideo, and isight_firmware, and then modprobe both,
and then reboot to have the two talk with each other.
Should I set something in /etc/udev/rules.d/* or is this something
else. Besides that once the two are working, everything is good.
regards;

-- 
Justin P. Mattock

Re: BUG: unable to handle kernel paging request at f8dbf000 "isight_firmware"

[Matthew Garrett]

On Sun, Jun 08, 2008 at 06:51:42PM +0000, Justin Mattock wrote:

> Now on to the status with isight firmware, It seems The two modules
> are loading uvcvideo and isight_firmware, but there not talking with
> each other upon booting,

I'm not quite sure I understand. They don't talk to each other as such - 
the firmware driver loads the firmware, at which point the isight will 
disconnect and reappear with a new USB id. uvcvideo should then be able 
to bind. What are you actually seeing?

-- 
Matthew Garrett | mjg59@srcf.ucam.org

Re: BUG: unable to handle kernel paging request at f8dbf000 "isight_firmware"

[Justin Mattock]

On Sun, Jun 8, 2008 at 11:11 PM, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> On Sun, Jun 08, 2008 at 06:51:42PM +0000, Justin Mattock wrote:
>
>> Now on to the status with isight firmware, It seems The two modules
>> are loading uvcvideo and isight_firmware, but there not talking with
>> each other upon booting,
>
> I'm not quite sure I understand. They don't talk to each other as such -
> the firmware driver loads the firmware, at which point the isight will
> disconnect and reappear with a new USB id. uvcvideo should then be able
> to bind. What are you actually seeing?
>
> --
> Matthew Garrett | mjg59@srcf.ucam.org
>

There not binding, or uvcvideo is not binding,
under dmesg I see:
when not binding:
[   14.971002] firmware: requesting isight.fw
[   15.183152] usbcore: registered new interface driver isight_firmware

[   16.849152] usbcore: registered new interface driver uvcvideo

when binded:

[   15.319330] firmware: requesting isight.fw
[   15.433080] usbcore: registered new interface driver isight_firmware

[   16.810149] usbcore: registered new interface driver uvcvideo
[   17.810745] uvcvideo: Found UVC 1.00 device Built-in iSight (05ac:8501)
[   17.819252] uvcvideo: Failed to query (135) UVC control 1 (unit 0)
: -32 (exp. 26).

I've noticed the not binding more than binding. Usually I have to
start the system and remove the two modules, and then modprobe the two
 then a reboot to have a proper load or binding of the two. Keep in
mind I am using a uvcvideo module that is a few weeks old, so maybe
this
is whats causing this.
regards;
-- 
Justin P. Mattock

Re: BUG: unable to handle kernel paging request at f8dbf000 "isight_firmware"

[Justin Mattock]

On Mon, Jun 9, 2008 at 12:23 AM, Justin Mattock <justinmattock@gmail.com> wrote:
> On Sun, Jun 8, 2008 at 11:11 PM, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
>> On Sun, Jun 08, 2008 at 06:51:42PM +0000, Justin Mattock wrote:
>>
>>> Now on to the status with isight firmware, It seems The two modules
>>> are loading uvcvideo and isight_firmware, but there not talking with
>>> each other upon booting,
>>
>> I'm not quite sure I understand. They don't talk to each other as such -
>> the firmware driver loads the firmware, at which point the isight will
>> disconnect and reappear with a new USB id. uvcvideo should then be able
>> to bind. What are you actually seeing?
>>
>> --
>> Matthew Garrett | mjg59@srcf.ucam.org
>>
>
> There not binding, or uvcvideo is not binding,
> under dmesg I see:
> when not binding:
> [   14.971002] firmware: requesting isight.fw
> [   15.183152] usbcore: registered new interface driver isight_firmware
>
> [   16.849152] usbcore: registered new interface driver uvcvideo
>
> when binded:
>
> [   15.319330] firmware: requesting isight.fw
> [   15.433080] usbcore: registered new interface driver isight_firmware
>
> [   16.810149] usbcore: registered new interface driver uvcvideo
> [   17.810745] uvcvideo: Found UVC 1.00 device Built-in iSight (05ac:8501)
> [   17.819252] uvcvideo: Failed to query (135) UVC control 1 (unit 0)
> : -32 (exp. 26).
>
> I've noticed the not binding more than binding. Usually I have to
> start the system and remove the two modules, and then modprobe the two
>  then a reboot to have a proper load or binding of the two. Keep in
> mind I am using a uvcvideo module that is a few weeks old, so maybe
> this
> is whats causing this.
> regards;
> --
> Justin P. Mattock
>

O.K. after loading the latest uvcvideo, the issue is still prevalent.,
Hopefully I explain to you so you can get an
idea of what I'm seeing: on a cold boot the isight_firmware and
uvcvideo are not binding, but If after the system starts from the cold
boot, with
isight_firmware and uvcvideo not binding, a simlple rmmod and modprobe
of the two modules will bind the two. then with a reboot
the two will almost certainly stay binded, but if instead of a reboot
a shutdown -h now. upon starting up the two won't be binded anymore.
almost as if the firmware is loading in the wrong location, but am
uncertain how that area works.
Hope this helps you, better see the problem I'm looking at.
regards;

-- 
Justin P. Mattock