New EHCI driver fails on my system

A forum for AmigaOne XE and MicroA1-C specific issues.
User avatar
Hypex
Beta Tester
Beta Tester
Posts: 443
Joined: Mon Dec 20, 2010 2:23 pm
Location: Vic. Australia.

New EHCI driver fails on my system

Post by Hypex »

For many years I looked forward to USB2 support in AmigaOS4 knowing it had been delveloped and in testing for that long period. I also endured the "persecution" AmigaOS4 got for using SirionUSB with all the problems reported over the years and not the "rock solid superior USB2 supporting" Poseidon USB stack. And all the people who repeatedly kept askng why isn't Sirion dumped in favour of Poseidon as it's so much better and supports USB2. And bla bla bla. Actually after all these years why not!? I'm not qualified to answer them damn it! ;-)

However after initial testing of the new high speed USB drivers in OS4.1, I may be forced to agree. :-o

I've had a USB2 card slotted into my AmgaOne for a while now. It's also a VIA card and reports the same exact PCI ID as the onboard USB chipset, with additional EHCI hardware. So I expected it to be compatible. I've also used to connect my printer and flash drives and they have worked fine out of the box with OS4 UHCI USB. And also with Linux. As good as a DVD drive on OS3. :-)

But tonight, that all ends. I installed Update 3 and after getting past some other issues I tested out my USB. I plugged a few drives into my USB2 slots one at a time and was left disappointed as none of them now worked. Even using my printer as a hub for my SD cards cannot be done anymore. Is is unfortunate after all this time that I may have to disable EHCI USB. :-( A major feature of Update 3 and I can't use it! I even had an internal USB cable from AmigaKit already to go. :-(

What happens is OS4 tries to mount the drives. Sonetimes it can be reading endlessly for what would take moments on USB1.1. It even reported read errors! :-o Leaving USB0:Unintialised type icons on my Workbench if I am lucky otherwise nothing appears with no sign of a drive.

So does this mean I can't use my VIA USB2 card with AmigaOS4 anymore? And if all USB chipsets are meant to be compatible why not? And why does it work fine with the older USB1.1 drivers? :-?

Here is the PCI info as taken from PCIScan:
Hidden Text - Click to Show :
Device #12:
Vendor: 0x1106 (VIA Technologies, Inc.)
Device: 0x3038 (VT82xxxxx UHCI USB 1.1 Controller)
Class code: 0x0C0300
RevisionID: 0x62
Interrupt: Line 0x0A, Pin 0x01
Subsystem Vendor: 0x1106
Subsystem ID: 0x3038
Resource range #4 (IO)
Base address: 0x00802440
Physical address: 0x00802440
Size: 0x00000020

Device #13:
Vendor: 0x1106 (VIA Technologies, Inc.)
Device: 0x3038 (VT82xxxxx UHCI USB 1.1 Controller)
Class code: 0x0C0300
RevisionID: 0x62
Interrupt: Line 0x0B, Pin 0x02
Subsystem Vendor: 0x1106
Subsystem ID: 0x3038
Resource range #4 (IO)
Base address: 0x00802460
Physical address: 0x00802460
Size: 0x00000020

Device #14:
Vendor: 0x1106 (VIA Technologies, Inc.)
Device: 0x3104 (USB 2.0)
Class code: 0x0C0320
RevisionID: 0x65
Interrupt: Line 0x07, Pin 0x03
Subsystem Vendor: 0x1106
Subsystem ID: 0x3104
Resource range #0 (MEMORY)
Base address: 0x98100200
Physical address: 0x98100200
Size: 0x00000100
In closing, here is my USB log. I have disabled my back ports. My front ports are attached to an internal card reader. One port of which is connected directly to a front USB port. In the log I expect it is picking up my card reader. It is at this point that I turn on my printer and insert a drive. I also noted it looks like it is confusing the hubs on USB. It notes I have disabled a "Rear" hub and I have a USB2 "Additional" hub. But then it talks about detecting EHCI in the "rear" hub. Is Sirion confused? I am! :-?

I also note that it calls the Additional Roothub "uhci.usbhcd" but shouldn't this be "uhci.usbhcd/2" ? At least that's how the USB Inspector reports it to me. Could be a conflict there? I also tried disabling the onboard USB in UBoot but thiis made no effect on OS4 so maybe there is also a problem there if it ignores the UBoot variables.
Hidden Text - Click to Show :
I: [00:30:50] USB stack | | ==========
I: [00:30:50] USB stack | | USB System Software Task started
I: [00:30:50] USB stack | | Starting HCDs...
W: [00:30:50] UHCI Controller Task Unit 0 | UHCI | Rear USB ports are disabled in UBoot prefs.
E: [00:30:50] USB stack | New Fkt | fkt: 0x6FF57DC0 = Level -1
E: [00:30:50] USB stack | New Fkt | fkt: 0x6FF57E60 = Level 0
E: [00:30:50] USB stack | New Fkt | fkt: 0x6FF57F00 = Level -1
E: [00:30:50] USB stack | New Fkt | fkt: 0x6FDE4010 = Level 0
E: [00:30:50] USB stack | New Fkt | fkt: 0x6FDE40B0 = Level -1
E: [00:30:50] USB stack | New Fkt | fkt: 0x6FDE4150 = Level 0
E: [00:30:50] USB stack | New Fkt | fkt: 0x6FDE41F0 = Level -1
E: [00:30:50] USB stack | New Fkt | fkt: 0x6FDE4290 = Level 0
I: [00:30:50] USB stack | | ...HCDs started.
I: [00:30:50] USB Fkt Init | Init Fkt | Fkt 0x6FF57E60 is {Vendor: 0x0000, Product: 0x0000, Class: 09.00}
I: [00:30:50] USB Fkt Init | Init Fkt | Fkt 0x6FDE4010 is {Vendor: 0x0000, Product: 0x0000, Class: 09.00}
I: [00:30:50] USB Fkt Init | Init Fkt | Fkt 0x6FDE4150 is {Vendor: 0x0000, Product: 0x0000, Class: 09.00}
I: [00:30:50] USB Fkt Init | Init Fkt | Fkt 0x6FDE4290 is {Vendor: 0x0000, Product: 0x0000, Class: 09.00}
I: [00:30:50] USB Fkt Init | Init Fkt | Fkt 0x6FF57E60 initialized
I: [00:30:50] USB Fkt Init | Init Fkt | Fkt 0x6FDE4010 initialized
I: [00:30:50] USB Fkt Init | Init Fkt | Fkt 0x6FDE4150 initialized
I: [00:30:50] USB Fkt Init | Init Fkt | Fkt 0x6FDE4290 initialized
I: [00:30:50] hub.usbfd | HUB | Hub "Rear Roothub (uhci.usbhcd/0)" has TT thinktime of 8 full speed bittimes and protocol 0
I: [00:30:50] hub.usbfd | HUB | Hub "Front Roothub (uhci.usbhcd/1)" has TT thinktime of 8 full speed bittimes and protocol 0
I: [00:30:50] hub.usbfd | HUB | Hub "Additional Roothub (uhci.usbhcd" has TT thinktime of 8 full speed bittimes and protocol 0
I: [00:30:50] hub.usbfd | HUB | Hub "Rear Roothub (ehci.usbhcd/0)" has TT thinktime of 8 full speed bittimes and protocol 0
I: [00:30:50] hub.usbfd | HUB | All ports are empty
I: [00:30:50] hub.usbfd | HUB | All ports are empty
I: [00:30:50] hub.usbfd | HUB | All ports are empty
I: [00:30:50] hub.usbfd | HUB | Device found on port 1 of hub "Rear Roothub (uhci.usbhcd/0)".
I: [00:30:51] hub.usbfd | HUB | Port 1 of hub "Front Roothub (uhci.usbhcd/1)" disabled - port is empty.
I: [00:30:51] hub.usbfd | HUB | Port 2 of hub "Front Roothub (uhci.usbhcd/1)" disabled - port is empty.
I: [00:30:51] hub.usbfd | HUB | Port 1 of hub "Additional Roothub (uhci.usbhcd" disabled - port is empty.
I: [00:30:51] hub.usbfd | HUB | Port 2 of hub "Additional Roothub (uhci.usbhcd" disabled - port is empty.
I: [00:30:51] hub.usbfd | Hub port | Device at port 1 of hub "Rear Roothub (uhci.usbhcd/0)" is full-speed.
E: [00:30:51] USB stack | New Fkt | fkt: 0x6FDE45B0 = Level 1
I: [00:30:51] hub.usbfd | HUB | Device on hub port 1 successfully added.
I: [00:30:51] hub.usbfd | HUB | Port 2 of hub "Rear Roothub (uhci.usbhcd/0)" disabled - port is empty.
I: [00:30:51] hub.usbfd | HUB | Driver Running
I: [00:30:51] USB Fkt Init | Init Fkt | Fkt 0x6FDE45B0 is {Vendor: 0x058F, Product: 0x6362, Class: 00.00}
I: [00:30:51] USB Fkt Init | Init Fkt | Fkt 0x6FDE45B0 initialized
I: [00:30:51] MassStorage Device Task | Massstorage | Lun 0 has device type 0x00 (Direct access) and is removable
I: [00:30:51] MassStorage Device Task | Massstorage | Lun 1 has device type 0x00 (Direct access) and is removable
I: [00:30:51] MassStorage Device Task | Massstorage | Lun 2 has device type 0x00 (Direct access) and is removable
I: [00:30:51] MassStorage Device Task | Massstorage | Lun 3 has device type 0x00 (Direct access) and is removable
I: [00:30:52] MassStorage Device Task | Sys_EndInitialAttachmentPhase | Initial USB Attachment Phase terminated
I: [00:30:57] USB stack Process | | USB System Software Process started.
I: [00:30:57] USB stack Process | | Reading FD descriptors...
I: [00:30:57] USB stack Process | | ...FD infos read
I: [00:30:57] USB stack Process | | Starting HCDs...
I: [00:30:57] USB stack Process | | ...HCDs started.
I: [00:30:57] USB stack Process | Sys_EndInitialAttachmentPhase | Initial USB Attachment Phase terminated
I: [00:30:57] USB stack Process | | USB stack fullbooted
I: [00:31:36] hub.usbfd | HUB | Device found on port 3 of hub "Rear Roothub (ehci.usbhcd/0)".
I: [00:31:36] hub.usbfd | Hub port | Device at port 3 of hub "Rear Roothub (ehci.usbhcd/0)" is high-speed.
E: [00:31:36] USB stack | New Fkt | fkt: 0x5c9741e0 = Level 1
I: [00:31:36] hub.usbfd | HUB | Device on hub port 3 successfully added.
I: [00:31:36] EHCI Controller Task Unit 0 | EHCI | Port 2 is not in reset state.
I: [00:31:36] USB Fkt Init | Init Fkt | Fkt 0x5C9741E0 is {Vendor: 0x13FE, Product: 0x1F23, Class: 00.00}
I: [00:31:36] USB Fkt Init | Init Fkt | Fkt 0x5C9741E0 initialized
I: [00:31:36] MassStorage Device Task | Massstorage | Lun 0 has device type 0x00 (Direct access) and is removable
I: [00:33:53] hub.usbfd | HUB | Detaching Function removed from hub port 3
I: [00:33:57] hub.usbfd | HUB | Device found on port 2 of hub "Rear Roothub (ehci.usbhcd/0)".
I: [00:33:57] hub.usbfd | Hub port | Device at port 2 of hub "Rear Roothub (ehci.usbhcd/0)" is high-speed.
E: [00:33:57] USB stack | New Fkt | fkt: 0x5c9741e0 = Level 1
I: [00:33:57] hub.usbfd | HUB | Device on hub port 2 successfully added.
I: [00:33:57] EHCI Controller Task Unit 0 | EHCI | Port 1 is not in reset state.
I: [00:33:57] USB Fkt Init | Init Fkt | Fkt 0x5C9741E0 is {Vendor: 0x03F0, Product: 0x5711, Class: 00.00}
I: [00:33:57] USB Fkt Init | Init Fkt | Fkt 0x5C9741E0 initialized
I: [00:33:57] MassStorage Device Task | Massstorage | Lun 0 has device type 0x00 (Direct access) and is removable
E: [00:34:15] MassStorage Device Task | Massstorage | Reading 32 blocks starting from block 736 failed with USB error -33 and sense key MISCOMPARE (14)
E: [00:34:15] MassStorage Device Task | Massstorage | Reading 32 blocks starting from block 736 failed with USB error -33 and sense key NO SENSE (0)
E: [00:34:15] MassStorage Device Task | Massstorage | Reading 32 blocks starting from block 736 failed with USB error -33 and sense key NO SENSE (0)
E: [00:34:15] MassStorage Device Task | Massstorage | Reading 32 blocks starting from block 736 failed with USB error -33 and sense key NO SENSE (0)
E: [00:34:18] MassStorage Device Task | Massstorage | Reading 32 blocks starting from block 736 failed with USB error -33 and sense key NO SENSE (0)
E: [00:34:23] MassStorage Device Task | Massstorage | Reading 32 blocks starting from block 736 failed with USB error -35 and sense key NO SENSE (0)
E: [00:34:29] MassStorage Device Task | Massstorage | Reading 32 blocks starting from block 736 failed with USB error -35 and sense key NO SENSE (0)
E: [00:34:35] MassStorage Device Task | Massstorage | Reading 32 blocks starting from block 736 failed with USB error -35 and sense key NO SENSE (0)
E: [00:34:41] MassStorage Device Task | Massstorage | Reading 32 blocks starting from block 736 failed with USB error -35 and sense key NO SENSE (0)
E: [00:34:47] MassStorage Device Task | Massstorage | Reading 32 blocks starting from block 736 failed with USB error -35 and sense key NO SENSE (0)
I: [00:34:48] hub.usbfd | HUB | Device found on port 2 of hub "Rear Roothub (uhci.usbhcd/0)".
I: [00:34:48] hub.usbfd | HUB | No device on port 2 of hub "Rear Roothub (uhci.usbhcd/0)" after reset
W: [00:34:48] hub.usbfd | HUB | Resetting hub port 2 and trying again
I: [00:34:48] hub.usbfd | HUB | No device on port 2 of hub "Rear Roothub (uhci.usbhcd/0)" after reset
W: [00:34:48] hub.usbfd | HUB | Resetting hub port 2 and trying again
I: [00:34:48] hub.usbfd | HUB | No device on port 2 of hub "Rear Roothub (uhci.usbhcd/0)" after reset
W: [00:34:48] hub.usbfd | HUB | Resetting hub port 2 and trying again
I: [00:34:48] hub.usbfd | HUB | No device on port 2 of hub "Rear Roothub (uhci.usbhcd/0)" after reset
W: [00:34:48] hub.usbfd | HUB | Hub port 2 attachment was not possible
This last bit seems to go on forever!
User avatar
nbache
Beta Tester
Beta Tester
Posts: 1506
Joined: Mon Dec 20, 2010 7:25 pm
Location: Copenhagen, Denmark
Contact:

Re: New EHCI driver fails on my system

Post by nbache »

Hypex wrote:Here is the PCI info as taken from PCIScan:
Hidden Text - Click to Show :
Device #12:
Vendor: 0x1106 (VIA Technologies, Inc.)
Device: 0x3038 (VT82xxxxx UHCI USB 1.1 Controller)
Class code: 0x0C0300
RevisionID: 0x62
Interrupt: Line 0x0A, Pin 0x01
Subsystem Vendor: 0x1106
Subsystem ID: 0x3038
Resource range #4 (IO)
Base address: 0x00802440
Physical address: 0x00802440
Size: 0x00000020

Device #13:
Vendor: 0x1106 (VIA Technologies, Inc.)
Device: 0x3038 (VT82xxxxx UHCI USB 1.1 Controller)
Class code: 0x0C0300
RevisionID: 0x62
Interrupt: Line 0x0B, Pin 0x02
Subsystem Vendor: 0x1106
Subsystem ID: 0x3038
Resource range #4 (IO)
Base address: 0x00802460
Physical address: 0x00802460
Size: 0x00000020

Device #14:
Vendor: 0x1106 (VIA Technologies, Inc.)
Device: 0x3104 (USB 2.0)
Class code: 0x0C0320
RevisionID: 0x65
Interrupt: Line 0x07, Pin 0x03
Subsystem Vendor: 0x1106
Subsystem ID: 0x3104
Resource range #0 (MEMORY)
Base address: 0x98100200
Physical address: 0x98100200
Size: 0x00000100
I seem to have the same card, here's my PCIScan info:
Hidden Text - Click to Show :
Device #12:
Vendor: 0x1106 (VIA Technologies, Inc.)
Device: 0x3038 (VT82xxxxx UHCI USB 1.1 Controller)
Class code: 0x0C0300
RevisionID: 0x62
Interrupt: Line 0x0A, Pin 0x01
Subsystem Vendor: 0x1106
Subsystem ID: 0x3038
Resource range #4 (IO)
Base address: 0x00802440
Physical address: 0x00802440
Size: 0x00000020

Device #13:
Vendor: 0x1106 (VIA Technologies, Inc.)
Device: 0x3038 (VT82xxxxx UHCI USB 1.1 Controller)
Class code: 0x0C0300
RevisionID: 0x62
Interrupt: Line 0x0B, Pin 0x02
Subsystem Vendor: 0x1106
Subsystem ID: 0x3038
Resource range #4 (IO)
Base address: 0x00802460
Physical address: 0x00802460
Size: 0x00000020

Device #14:
Vendor: 0x1106 (VIA Technologies, Inc.)
Device: 0x3104 (USB 2.0)
Class code: 0x0C0320
RevisionID: 0x65
Interrupt: Line 0x07, Pin 0x03
Subsystem Vendor: 0x1106
Subsystem ID: 0x3104
Resource range #0 (MEMORY)
Base address: 0x98100800
Physical address: 0x98100800
Size: 0x00000100
It works just fine here on my A1 XE G4 which has been my main machine during all OS4 beta testing, including the Update 3 release candidates.
In closing, here is my USB log. I have disabled my back ports. My front ports are attached to an internal card reader. One port of which is connected directly to a front USB port. In the log I expect it is picking up my card reader. It is at this point that I turn on my printer and insert a drive. I also noted it looks like it is confusing the hubs on USB. It notes I have disabled a "Rear" hub and I have a USB2 "Additional" hub. But then it talks about detecting EHCI in the "rear" hub. Is Sirion confused? I am! :-?
I'm not sure what the deal is with those "front/rear" designations, they never quite made sense to me. But at least I can see that your setup is somewhat more complicated than mine, maybe that is also playing a role. I have a USB2.0 hub attached to one port of the card, and a simple extender cable to the other (which I sometimes plug devices into instead of the hub, for no good reason - hey, I'm a beta tester ;-)). My mouse (or rather the receiver of my wireless mouse) is still attached to one of the old builtin USB 1.1 ports (keyboard is PS/2). I haven't disabled anything.

Could you maybe try a simpler setup, just to see if it changes anything?

Best regards,

Niels
User avatar
nbache
Beta Tester
Beta Tester
Posts: 1506
Joined: Mon Dec 20, 2010 7:25 pm
Location: Copenhagen, Denmark
Contact:

Re: New EHCI driver fails on my system

Post by nbache »

Also note that:

1. There may well be more than one "VIA chipset", so just because there is a VIA chipset on your motherboard, it is not necessarily the same on any given PCI card (and I'd especially expect this to be true between the onboard USB 1.1 controller and a plugin USB 2.0 card).

2. Even if it were the same chipset, it might have very different working conditions on the motherboard and on a PCI card.

BTW, I just created another thread in this forum with details and pictures of the two cards I have working in my AmigaOnes.

Best regards,

Niels
User avatar
Hypex
Beta Tester
Beta Tester
Posts: 443
Joined: Mon Dec 20, 2010 2:23 pm
Location: Vic. Australia.

Re: New EHCI driver fails on my system

Post by Hypex »

nbache wrote:I seem to have the same card, here's my PCIScan info:
Yes it looks like you do. This is good news! :-)
It works just fine here on my A1 XE G4 which has been my main machine during all OS4 beta testing, including the Update 3 release candidates.
I have noticed one difference. Your base address is different! Where have you put yours in the slot and what else is around it?

On my machine a SBLive in the bottom PCI, my USB2 card above that and an 0680 above that with my Radeon 9200SE AGP on top.
I'm not sure what the deal is with those "front/rear" designations, they never quite made sense to me.
Thankyou for the understanding there! :-)
But at least I can see that your setup is somewhat more complicated than mine, maybe that is also playing a role. I
I'm afraid I don't know what you mean here. I read your description and I am confused! That looks more complicatd than mine! :-P

But let me clarify my setup. On my motherboard USB an internal card reader is attached to one front port. (The other port is a straight through for a front USB tower port and left empty.) It (card reader) contains a hub so we might as well view it as an empty hub. (No cards are plugged in.) On my USB2 card I usually have a printer attached that is usually off until I need it. For these tests my card reader was left as is and my USB2 ports cleared with only USB2 flash drives plugged into to test. My onboard USB was still working fine. My USB2 ports played up.

I will note here that prior to Update 3 I had no problems at all using my USB2 card. My printer worked fine. I could use my printer as a hub and view SD cards plugged into it. I could plug flash drives in with no problems. I will also add that I have tested a Linux 2.6.31-1 kernel with my USB2 card and it has also worked fine including giving me a faster speed.

I also tried disabllng the USB2 driver and rebooting. After an initial random yellow alert about USB babble I rebooted again and tested. The ports then started working fine as before. So I determine the problem lies in the new EHCI driver. This is confirmed by plugging in a USB1 hub into the USB2 ports and testing a USB2 device in the hub; which worked fine! Since it was forced to use the OHCI/UHCI driver which has no problem. :-)
Could you maybe try a simpler setup, just to see if it changes anything?
You suggest I simplify my setup but I don't know how else I would on the USB2 card! Since it is empty. ;-) The only thing I can do is remove my card reader from the internal USB ports. But since these ports are working fine how would this affect the EHCI driver? Also I have 15K pull up resistors on my internal USB ports, could this cause a conflict? In any case I will remove all attachments to my internal USB ports in the hope there wil be a change. I will post the result.

Thanks for responding to my situation. :-)
User avatar
nbache
Beta Tester
Beta Tester
Posts: 1506
Joined: Mon Dec 20, 2010 7:25 pm
Location: Copenhagen, Denmark
Contact:

Re: New EHCI driver fails on my system

Post by nbache »

Hypex wrote:I have noticed one difference. Your base address is different! Where have you put yours in the slot and what else is around it?

On my machine a SBLive in the bottom PCI, my USB2 card above that and an 0680 above that with my Radeon 9200SE AGP on top.
I have my sound card in the bottom slot as well, currently it's an M-Audio Revolution 5. Above that is the USB card, and in the third slot is an SiI3114 card. My AGP slot has my Radeon 9250.
I'm not sure what the deal is with those "front/rear" designations, they never quite made sense to me.
Thankyou for the understanding there! :-)
Well, what I meant was that "front" and "rear" would depend on how you connect your internal leads, wouldn't it? So calling headers on the motherboard "front" and "rear" does not guarantee that they will be connected to the front rsp. rear sockets in the case. IIRC, I only have the plugs at the back of my A1 case connected, and USBInspector does see my mouse receiver on the "rear roothub", so apparently I chose the correct header on the mobo back when I set that up ;-). Pure coincidence, though.
I'm afraid I don't know what you mean here. I read your description and I am confused! That looks more complicatd than mine! :-P
Hmm, I think I misread your setup description as being about your USB2 setup only. I agree that I wouldn't expect what you do with your builtin USB 1.1 connections to influence on the EHCI stuff -- but I'm not sure. USB is weird sometimes. Maybe Sebastian or others know more.

As for my USB2 setup, it's quite simple as well: One port only has the (usually) empty extender cable, and the other has the hub, also normally empty. Then I plug stuff (sticks, cameras, card readers etc.) into either the extender cable or the hub. I only use those two ports, which are on the back plate of the card. None of the internal ports of the card are used.

Best regards,

Niels
number6
Posts: 6
Joined: Fri Jun 17, 2011 8:12 pm

Re: New EHCI driver fails on my system

Post by number6 »

nbache wrote:Also note that:

1. There may well be more than one "VIA chipset", so just because there is a VIA chipset on your motherboard, it is not necessarily the same on any given PCI card (and I'd especially expect this to be true between the onboard USB 1.1 controller and a plugin USB 2.0 card).

2. Even if it were the same chipset, it might have very different working conditions on the motherboard and on a PCI card.

BTW, I just created another thread in this forum with details and pictures of the two cards I have working in my AmigaOnes.

Best regards,

Niels
I see you are admirably trying to get user input here. I would like to suggest that XE users filing reports make mention of whether they are commenting about either a (1)fixed or (2)un-fixed XE. Thank you for all you are trying to do.

#6
User avatar
nbache
Beta Tester
Beta Tester
Posts: 1506
Joined: Mon Dec 20, 2010 7:25 pm
Location: Copenhagen, Denmark
Contact:

Re: New EHCI driver fails on my system

Post by nbache »

Good point. Both of my A1s are unfixed, both regarding the DMA fix and regarding USB.

Best regards,

Niels
number6
Posts: 6
Joined: Fri Jun 17, 2011 8:12 pm

Re: New EHCI driver fails on my system

Post by number6 »

nbache wrote:Good point. Both of my A1s are unfixed, both regarding the DMA fix and regarding USB.

Best regards,

Niels
Thank you. I'm trying to get that "little" detail from users in irc to complement what you learn.
I'll post when I feel it is relevant.

#6
number6
Posts: 6
Joined: Fri Jun 17, 2011 8:12 pm

Re: New EHCI driver fails on my system

Post by number6 »

nbache wrote:Good point. Both of my A1s are unfixed, both regarding the DMA fix and regarding USB.

Best regards,

Niels
Another request regarding "terms" used. People are saying VIA without mentioning whether it is onboard or a card. I think it is important to give as much detail as possible in these reports.

#6
User avatar
nbache
Beta Tester
Beta Tester
Posts: 1506
Joined: Mon Dec 20, 2010 7:25 pm
Location: Copenhagen, Denmark
Contact:

Re: New EHCI driver fails on my system

Post by nbache »

The onboard VIA chips on an A1 motherboard do not support USB2. Anything to do with USB2 in an A1 must therefore be on a PCI card.

Best regards,

Niels
Post Reply