On Monday 06 December 2004 11:53 am, Thomas Dodd wrote:
Where can I find a list of problems with the VT6202?
VIA hasn't been forthcoming ... we can do no better! :)
I mean know issues with the VIA chip and the linux driver.
The current mailing list isn't the most searchable, and the web sites are informative:(
I've got one, but cannot get it to work with ehci_hcd (from 2.6.9-1.6_FC2 kernel).
I expect you mean FC3, since 2.6.9 didn't exist with FC2 ... ;)
No, FC2. I'm about to update to FC3, but 2.6.9 has been released as and update for FC2. Built 18 Nov 2004 on bugs.build.redhat.com. I installed it 30 Nov, after picking up the card at Frys over thanksgiving.
It loads, the I get:
ehci_hcd 0000:00:08.2: USB 2.0 enabled, EHCI 0.95, driver 2004-May-10" hub 1-0:1.0: USB hub found hub 1-0:1.0: 4 ports detected ehci_hcd 0000:00:08.2: fatal error ehci_hcd 0000:00:08.2: HC died; cleaning up
Some boards have been reporting problems like that, and I'm not sure what's causing it ... since plenty of boards do NOT have that issue, and it doesn't appear to be chip-specific. Is your VT6202 on a PCI add-in card, or a motherboard?
Add on card. Macsense UP-400 (http://www.macsense.com/product/usb/usb1394_b.htm)
lspci show:
00:08.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev51) (prog-if 20 [EHCI]) Subsystem: VIA Technologies, Inc. (Wrong ID): Unknown device 1234 Flags: bus master, medium devsel, latency 32, IRQ 10 Memory at e7001000 (32-bit, non-prefetchable) Capabilities: [80] Power Management version 2
It on an MSI slotA board, AMD-750 chipset (751 [Irongate] and 756 [Viper]). BIOS report teh card with vend:1106, and Dev 3104, 3038, and 3038 (those 2 are the UHCI controllers right?)
My best guess is that the "fatal error during startup" issue has to do with power switching, since those started to crop up at about the time the driver started to forcibly power all ports off during startup (to handle some devices that didn't seem to want to enumerate without a power cycle). Maybe the powerdown needs a delay, or the powerup delay needs to be more than the 20 msec guaranteed by the EHCI spec ... but violating those timings doesn't seem like the sort of thing that'd make any EHCI controller resort suicide.
Any easy way to go back before that change and see? What files from what kernel?
-Thomas
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
