[ATrpms-users] Problem with package wis-go7007-linux

[Jason "Foxdie" Bhalla-Gaunt]

Hello again,

I booted into the most up to date kernel available to me (2.6.18-53), 
built the source code from scratch after applying the most up to date 
patch (even though its for a previous kernel) to the WIS GO7007 source 
code, it built perfectly first time and installed no problem.

I'm still left with the same issue, this is what /var/log/messages has 
to say about it:

    Dec 30 20:24:36 artlite kernel: usb 3-3: new high speed USB device 
using ehci_hcd and address 4
    Dec 30 20:24:36 artlite kernel: usb 3-3: device descriptor read/64, 
error -32
    Dec 30 20:24:36 artlite kernel: usb 3-3: device descriptor read/64, 
error -32
    Dec 30 20:24:37 artlite kernel: usb 3-3: new high speed USB device 
using ehci_hcd and address 5
    Dec 30 20:24:37 artlite kernel: usb 3-3: device descriptor read/64, 
error -32
    Dec 30 20:24:37 artlite kernel: usb 3-3: device descriptor read/64, 
error -32
    Dec 30 20:24:37 artlite kernel: usb 3-3: new high speed USB device 
using ehci_hcd and address 6
    Dec 30 20:24:37 artlite kernel: usb 3-3: device not accepting 
address 6, error -32
    Dec 30 20:24:38 artlite kernel: usb 3-3: new high speed USB device 
using ehci_hcd and address 7
    Dec 30 20:24:38 artlite kernel: usb 3-3: device not accepting 
address 7, error -32

Again, I tried both hotplugging it, and coldplugging it. No difference, 
but now if I "modprobe -r ehci_hcd" the kernel doesn't panic. Sadly the 
device isn't usable in USB 1.1 mode with it being a video capture 
device, and reloading EHCI with "modprobe ehci_hcd" just spouts more 
errors like above and the device isn't recognised with lsusb anymore. 
Any thoughts?

Kind regards,

Bart Vanbrabant wrote:
>> I believe both the above are before fxload is run (because the initial
>> kernel driver for it isn't loaded, could be wrong though). I've had this
>> card working with 0.9.8 drivers under Debian a year or so ago, I just
>> can't understand why it isn't working under CentOS / 2.6.18-8.
>>     
>
> Sorry, didn't catch that in the previous mails so it really is a
> driver problem and not related to the firmware. Do you have some
> oopses from when the crash occurs? I mostly just patched up the driver
> to work with the updated v4l2 api. I haven't tried my box on a CentOS
> machine but it used to work fine on FC6 on which CentOS is based.
>
> I would try a kernel from FC7 or FC8 and recompile the srpm on your
> centos box and try that. You could also try installing the driver from
> source, here are my patches http://bart.ulyssis.org/go7007/
>
> gr,
>
> Bart
>
>   

-- 
Jason "Foxdie" Bhalla-Gaunt
http://www.foxdie.co.uk/
(All email content is for the intended eye(s) of the recipient
and may NOT be used without express permission in a court of law or any
other legal or business proceedings) 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.atrpms.net/pipermail/atrpms-users/attachments/20071230/26896b71/attachment.html