On Wed, 29 Jun 2005, Jonathan Selby wrote:
> I posted a strange problem a couple of weeks ago and Alan gave me some
> homework to get more data.
>
> I am now back with this data and a few gray hairs in the bargain.
>
> I was having getting an ISO driver to run and we were able to point
> to an EHCD problem - Fine however I was able to bypass that problem and
> eventually ended up with another problem and that was getting the driver
> to run on SUSE 9.3 Kernel 2.6.11.
>
> Alan Stern suggested I try different kernels to see where the problem
> lay there. In the meantime I successfully ran the driver on Debian
> running 2.6.11 kernel.
>
> To this day I have not succeeded in getting the driver to run on SuSE
> 9.3. with the stock kernel. 9.2 yes 9.3 no.
>
> I have conduced a thorough code review and cleaned some dark corners
> however the driver will still not run.
>
> Following Alan's suggestion I have loaded Kernel 2.6.10 and also
> 2.6.12.1 on the SuSE 9.3 ,machine that run perfectly when I had SuSE 9.2
> (2.6.8) running - We know the machine will run the driver and it is not
> a hardware issue.
>
> OK Following me so far: Running 2.6.10 - Driver ran perfectly. 2.6.11
> and 2.6.12 no dice My ISO callback comes back and every frame has a
> status code of -84.
>
> OK This story is going to get stranger. On my production machine running
> SuSE 9.3 I am running VMWARE 5.0 and am able so get ISO transfers
> through that machine in windows. SuSE ISO is working with my hardware. I
> double checked to see if my driver would work - lo and behold it works
> perfectly.
>
> So to get my driver to work in SuSE 9.3 I need to run VMware and load a
> virtual windows machine. I can then run my driver to my hearts content.
> even after vmware has been shutdown and from then on after. On a freshly
> booted machine the driver repeatedly will not allow ISO in.
Just out of curiosity...
Can you post the /proc/bus/usb/devices entry for your device from a SuSE
9.3 system:
before running VMware or your driver,
while running your driver unsuccessfully before starting VMware,
after running and exiting from VMware but before running your
driver,
and after running and exiting from VMware and then unplugging
and replugging the device, but before running your driver.
Does your driver still work for that fourth test?
If you turn on CONFIG_USB_DEBUG and recompile the USB drivers, there will
be additional debugging information about the EHCI controller available in
sysfs. However I don't know how to interpret it; maybe someone else can
help.
Alan Stern
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
