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

[Jason "Foxdie" Bhalla-Gaunt]

There's one thing I failed to point out last night, on Centos after 
installing I did a full yum update which installed a new Kernel, a uname 
-r revealed "2.6.18-53.1.4.el5", but for the purpose of testing I had 
booted the previous kernel (it left it installed with an option in the 
grub bootloader menu) "2.6.18-8.el5".

I also tried with the newer Kernel, but even after running "modprobe -r 
ehci_hcd" the TX-100 wasn't detected properly (no Kernel crash, it just 
didn't detect it properly, probably because the Kernel module for it was 
built for 2.6.18-8.el5 and not 2.6.18-53).

Hope this attendum helps,

Axel Thimm wrote:
> On Sun, Dec 30, 2007 at 01:33:55AM +0000, Jason Foxdie Bhalla-Gaunt wrote:
>   
>> Hi all,
>>
>> Been trying to get this sorted out with the good chaps in #centos on 
>> freenode IRC but we've narrowed it down to a possible faulty driver.
>> Here is an outlay of my current system:
>>
>> * AMD Athlon 1800+ running on a Biostar M7SUA (M7VKQ PRO in North 
>> America), recent BIOS installed
>> * H&B TX-100 USB2.0 MPEG4 Hardware Encoder (WIS GO7007 Chip)
>> * Centos 5 Linux running Kernel 2.6.18-8
>>
>> I installed the "wis-go7007-linux" package successfully from the ATRPMS 
>> repo, the problem I have is when I try and bootup I get the following 
>> error message:
>>
>>     usb 3-3: device descriptor read/64, error -32
>>     usb 3-3: new high speed USB device using ehci_hcd and address 6
>>     usb 3-3: device not accepting address 6, error -32
>>
>> Naturally I assume 3-3 is the USB port of the TX-100, I've tried a 
>> different USB 2.0 cable, and a different USB 2.0 port on the 
>> motherboard. This device functions perfectly in Windows XP (although 
>> only with one piece of software, which is why I'm using it under Linux) 
>> and I managed to get it working once under a 2.4.xx Kernel a couple of 
>> years ago under Debian.
>>
>> Googling the above errors, people have suggested running "modprobe -r 
>> ehci_hcd" to bump it into working, unfortunately this means it would 
>> only work in USB 1.1 mode, but alas, when I try this, I get a warning 
>> about how the device should be plugged into a USB 2.0 port only, then a 
>> couple of seconds later, the kernel panics.
>>
>> I've tried an array of things such as booting up with the device plugged 
>> in, booting up THEN plugging it in, and both the aformentioned with and 
>> without removing the ehci_hcd module, the results are always the same; 
>> either the device isn't detected and initialised properly, or the kernel 
>> panics due to the driver. Oh and I also tried booting up with NOACPI and 
>> NOAPIC options passed to the Kernel on bootup. It makes no difference.
>>
>> Can anyone advise please? I fear I will go bald from tearing my hair out ;)
>>     
>
> I have copied Bart Vanbrabant, who maintains patches for bringing
> go7007 to the latest kernels, he could maybe know what's wrong in your
> setup (given that RHEL5's kernel is 2.6.18 based and Bart had already
> done the patching years ago w/o anyone reporting this I assume that
> the driver is OK).
>   

-- 
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/6df22b34/attachment-0001.html