New EHCI driver fails on my system

A forum for AmigaOne XE and MicroA1-C specific issues.
number6
Posts: 6
Joined: Fri Jun 17, 2011 8:12 pm

Re: New EHCI driver fails on my system

Post by number6 »

nbache wrote: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
Understood. There are posts about boot issues/device recognition issues, not just "usage" issues. I'm just covering multiple bases here.

#6
paulsy
Posts: 6
Joined: Sun Sep 04, 2011 5:11 pm

Re: New EHCI driver fails on my system

Post by paulsy »

I have read that NEC cards are suppose to work but I have a NEC card, which while it boots ok, freezes the system as soon as i plug in any usb devise. commenting out the EHCI driver and the card works. strangly the keyboard still works and I can reset with it. my keyborard and mouse are PS2.
I should point out that I have a Micro A1. Ranger gives the card as 0x00E0 REV:0x04
User avatar
Cyborg
Hyperion Entertainment
Hyperion Entertainment
Posts: 54
Joined: Wed Feb 16, 2011 1:29 pm

Re: New EHCI driver fails on my system

Post by Cyborg »

paulsy wrote:I have read that NEC cards are suppose to work but I have a NEC card, which while it boots ok, freezes the system as soon as i plug in any usb devise. commenting out the EHCI driver and the card works. strangly the keyboard still works and I can reset with it. my keyborard and mouse are PS2.
I should point out that I have a Micro A1. Ranger gives the card as 0x00E0 REV:0x04
It seems there is a general problem with MicroA1s and EHCI regardless of the used chip. The problem is known and logged in a bugreport. All depends on the USB gods now, which are unfortunately in holidays IIRC.
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 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.
Sounds like my setup apart from the different cards. I wonder then it if causes the PCI to allocate different base addresses?

Here is my NV PCI setup. Are these correct?
pci_irqa=9
pci_irqa_select=level
pci_irqb=10
pci_irqb_select=level
pci_irqc=11
pci_irqc_select=level
pci_irqd=7
pci_irqd_select=level
nbache wrote: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,
Yes I see your point. Well in my case my rear motherboard ports are unused and disabled in UBoot AFAICT since the other ports do work! And I have connected my card reader and front USB port to the internal UISB headers, which is what I deem the front ports. But they are on board header ports regardless.
nbache wrote:Hmm, I think I misread your setup description as being about your USB2 setup only.
Ah I see. Okay. :-)
nbache wrote:s for my USB2 setup, it's quite simple as well:
Ah yes now I see. :-)

At first I also was testing with an extended cable ans thought that nmay have played a part but it made no difference.

Well at this point I removed all attachments to my on board USB. I didn't disable them but booted it up and tested. I forgot to plug my mouse in so put this into my USB2 card. Worked fine. Checked log, came up as low speed device, so worked. Then I plugged in a flash drive. Detected, the icon came up on screen as tried to mount it. Sat for a while. No luck. USB log reported read errors as usual. Okay s I can cancel that out.

BTW I have an unfixed A1. But have inserted pull up resistors on the back of my plug going to my front port.
number6
Posts: 6
Joined: Fri Jun 17, 2011 8:12 pm

Re: New EHCI driver fails on my system

Post by number6 »

@NBache

I understand the point of urging use of this board and we've all made the recommendation to do so.
However, if you want to review the "theory" and those testing the theory by imitating the exact card layout on XE suggested by the OP of the theory, then:

Please start with post #27 by K-L.

btw-other XE users (fixed/unfixed/G3/G4) are either testing this or expressed interest in doing so.

I expect more comments in the above thread as a result.

#6
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 »

number6 wrote:However, if you want to review the "theory" and those testing the theory by imitating the exact card layout on XE suggested by the OP of the theory, then:
Okay, so the end result here is to test the USB cards in the lower PCI slot? I was going to try this but I don't think it wil help the situation. It's become obvious to me that the problem lies in the new EHCI driver. Why do I say that?

Because in my experience this isn't a hardware problem. I have had this USB card working fine with Linux and also with it's EHCI driver at respectable speeds. On top of that both the AmigaOS4.1 OHCI and UHCI drivers work fine with my card and still do.

That then leaves the problem with the EHCI driver, To which I have found more bugs. Tonight it crashed on me. I had my printer on after getting it to do a test page. And then turned on my AmigaOne. When Workbench had booted the EHCI driver had crashed. Which I note has happened to others as well on bootup. It only hit once. There was also an SD card in the slot which the EHCI driver fails to mount as usual.

Here is the log: :-)
Hidden Text - Click to Show :
Crash log for task "EHCI Controller Task Unit 0"
Generated by GrimReaper 53.2
Crash occured in module ehci.usbhcd at address 0x01CBD5F0
Type of crash: DSI (Data Storage Interrupt) exception

Register dump:
GPR (General Purpose Registers):
0: 00000020 6FD51EB0 00000000 00000000 0205481C 00000000 021A3650 021A3674
8: 00000001 A002000C 00000001 00000010 6FEEA510 00000000 00000000 6FFFEB80
16: 6FFFEB90 6FDD8490 BE009000 06008000 6FCA4028 0000001F 01CC47A8 6FDD8178
24: 0000001F 6FDD5C74 04000000 00000000 6FFFEA80 00000000 02000000 6FDD5740


FPR (Floating Point Registers, NaN = Not a Number):
0: nan 1.08349e-319 0 0
4: 0 0 0 0
8: 0 0 0 0
12: 0 0 -3.26984e-96 3.42611e-19
16: -7.92792e-10 -3.53737e-74 -2.92604e+284 1.73337e-17
20: -1.39149e-27 -1.5528e+280 -0.000954149 7.10921e+210
24: 3.51829e-28 -7.50989e-06 -8.42539e-81 -5.46309e-48
28: 0.00168966 -5.87814e-18 -3.75228e-37 5.1232e-159

FPSCR (Floating Point Status and Control Register): 0x82008000


SPRs (Special Purpose Registers):
Machine State (msr) : 0x0000F030
Condition (cr) : 0x42000088
Instruction Pointer (ip) : 0x01CBD5F0
Xtended Exception (xer) : 0x00000000
Count (ctr) : 0x01812C98
Link (lr) : 0x01CBD57C
DSI Status (dsisr) : 0x40000000
Data Address (dar) : 0xA002000C



680x0 emulated registers:
DATA: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ADDR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
FPU0: 0 0 0 0
FPU4: 0 0 0 0



Symbol info:
Instruction pointer 0x01CBD5F0 belongs to module "ehci.usbhcd" (HUNK/Kickstart)

Stack trace:
native kernel module ehci.usbhcd+0x000003f0
native kernel module ehci.usbhcd+0x00002540
native kernel module ehci.usbhcd+0x000060c4
native kernel module kernel+0x0001d668

PPC disassembly:
01cbd5e8: 90010010 stw r0,16(r1)
01cbd5ec: 6129000c ori r9,r9,12
*01cbd5f0: 80090000 lwz r0,0(r9)
01cbd5f4: 3d200227 lis r9,551
01cbd5f8: 8069f9a8 lwz r3,-1624(r9)

System information:

CPU
Model: IBM PowerPC 750 FX V2.2
CPU speed: 800 MHz
FSB speed: 133 MHz
Extensions: performancemonitor

Machine
Machine name: AmigaOne
Memory: 2097152 KB
Extensions: bus.pci bus.agp

Expansion buses
PCI/AGP
00:00.0 Vendor 0x10CC Device 0x0660
Range 0: 00000000 - 00400000 (PREF.MEM)
00:01.0 Vendor 0x10CC Device 0x0661
00:06.0 Vendor 0x10B7 Device 0x9200
Range 0: 00802000 - 00802080 (IO)
Range 1: 98100000 - 98100080 (MEM)
00:07.0 Vendor 0x1106 Device 0x0686
00:07.1 Vendor 0x1106 Device 0x0571
Range 4: 0000CC00 - 0000CC10 (IO)
00:07.2 Vendor 0x1106 Device 0x3038
Range 4: 00802080 - 008020A0 (IO)
00:07.3 Vendor 0x1106 Device 0x3038
Range 4: 008020A0 - 008020C0 (IO)
00:07.4 Vendor 0x1106 Device 0x3057
00:07.5 Vendor 0x1106 Device 0x3058
Range 0: 0000DC00 - 0000DD00 (IO)
Range 1: 0000E000 - 0000E008 (IO)
Range 2: 0000E400 - 0000E408 (IO)
00:07.6 Vendor 0x1106 Device 0x3068
Range 0: 00802300 - 00802400 (IO)
00:08.0 Vendor 0x1095 Device 0x0680
Range 0: 00802400 - 00802408 (IO)
Range 1: 00802408 - 00802410 (IO)
Range 2: 00802410 - 00802418 (IO)
Range 3: 00802418 - 00802420 (IO)
Range 4: 00802420 - 00802430 (IO)
00:09.0 Vendor 0x1106 Device 0x3038
Range 4: 00802440 - 00802460 (IO)
00:09.1 Vendor 0x1106 Device 0x3038
Range 4: 00802460 - 00802480 (IO)
00:09.2 Vendor 0x1106 Device 0x3104
Range 0: 98100200 - 98100300 (MEM)
00:0A.0 Vendor 0x1102 Device 0x0002
Range 0: 00802480 - 008024A0 (IO)
00:0A.1 Vendor 0x1102 Device 0x7002
Range 0: 008024A0 - 008024A8 (IO)
01:00.0 Vendor 0x1002 Device 0x5964
Range 0: 80000000 - 88000000 (PREF.MEM)
Range 1: 00002000 - 00002100 (IO)
Range 2: 88000000 - 88010000 (MEM)
01:00.1 Vendor 0x1002 Device 0x5D44
Range 0: 90000000 - 98000000 (PREF.MEM)
Range 1: 98000000 - 98010000 (MEM)
royleith
Posts: 9
Joined: Sun Sep 04, 2011 9:36 am

Re: New EHCI driver fails on my system

Post by royleith »

@ paulsy

I also have an NEC card. It does not get initialised as USB2
A1XE - no USB or other fixes.
NEC, 4-port USB 2 card installed in first pci slot (i.e. beneath the AGP slot).

USB inspector:
Hidden Text - Click to Show :
Rear Roothub (ehci.usbhcd/0)
Type:Interface
Product:Rear Roothub (ehci.usbhcd/0)
Vendor no.:0x0000
Serial no.:<unspecified>
Version: 1.0

Class:Hub
Subclass:0
Driver:none
.............................................
(The ohci hub has a Driver:hub.usbfd)
Workbench, repeatedly, gives the following notification for each of the four ports on the card. So, it knows it's there and keeps trying to set it up.

USB Device Notification
Unable to reset hub port.
Device adding aborted
................................
PCISCAN:
:
06 0x1106 0x3038 VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
07 0x1106 0x3038 VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
08 0x1106 0x3057 VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]

16 0x1033 0x0035 NEC Corporation USB
17 0x1033 0x0035 NEC Corporation USB
18 0x1033 0x00E0 NEC Corporation USB 2.0
I'm not too upset as I bought a couple of cheap cards on the off-chance that they might work. Can anyone suggest a source and product description of a card with the VIA chippery that has worked for them?

[edit] disabling the EHCI driver does not let the NEC card work in USB1.1. Even an optical mouse is not detected, but a thumb-drive gets its light lit up, but does not mount. There are no Workbench notifications and the OHCI and UHCI ports are not shown in the USB Inspector. I think that there is a general problem with this card.[/edit]

[edit2] As you were. Workbench notifications have now started to appear, as before.[/edit2]
Regards
Roy Leith
royleith
Posts: 9
Joined: Sun Sep 04, 2011 9:36 am

Re: New EHCI driver fails on my system- Ooops!

Post by royleith »

@all

I decided to rearrange the order of the PCI cards and put the USB card in a lower slot. When I took out the existing cards to re-order them, I noticed that there was a fourth PCI slot, unused. :oops:

I had installed the USB card in the graphics card 66MHz PCI slot just under the AGP slot instead of the remaining 33MHz slot. I have just copied over a half a GB of files to a 4GB flash drive and it is still going fast and strong. :roll:

So, yes the new USB2 driver works just fine with my cheap NEC USB card.

Regards
Roy Leith
Lio
Posts: 46
Joined: Tue Sep 13, 2011 8:07 pm

Re: New EHCI driver fails on my system

Post by Lio »

I jumped on the USB2 train by purchasing a second hand NEC 4+1 PCI USB card and inserted it either in slot 1-2-3, disabling/enabling front/rear onboard USB of my fixed A1XEG4 and it does not work properly !

The only thing I get is the notification errors !
USB Device Notification
Unable to reset hub port.
Device adding aborted

ranger is giving the following information :
ID Bus: 0x00 Device: 0x09 Function: 0x00
Class USB UHCI
Device 0x0035 rev 0x43 (n/a)
Vendor 0x1033 (n/a)

and pciscan :
m## Vendor Device Vendor name Descriptionm
01 0x10CC 0x0660 Mai Logic Incorporated Articia S Host Bridge
02 0x10CC 0x0661 Mai Logic Incorporated Articia S PCI Bridge
03 0x10B7 0x9200 3Com Corporation 3c905C-TX/TX-M [Tornado]
04 0x1106 0x0686 VIA Technologies, Inc. VT82C686 [Apollo Super South]
05 0x1106 0x0571 VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE
06 0x1106 0x3038 VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
07 0x1106 0x3038 VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
08 0x1106 0x3057 VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
09 0x1106 0x3058 VIA Technologies, Inc. VT82C686 AC97 Audio Controller
10 0x1106 0x3068 VIA Technologies, Inc. AC'97 Modem Controller
11 0x1095 0x0680 Silicon Image, Inc. PCI0680 Ultra ATA-133 Host Controller
12 0x1095 0x3512 Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller
13 0x1033 0x0035 NEC Corporation USB
14 0x1033 0x0035 NEC Corporation USB
15 0x1033 0x00E0 NEC Corporation USB 2.0

16 0x1002 0x4966 ATI Technologies Inc Radeon RV250 If [Radeon 9000]
17 0x1002 0x496E ATI Technologies Inc Radeon RV250 [Radeon 9000] (Secondary)

I also tried to disable the usb related stuff in my kicklayout like ehci (still error) or ohci (no error but usb stick not recognised)

so so far USB2 is a nogo for me.
User avatar
Noel Fuller
Beta Tester
Beta Tester
Posts: 13
Joined: Wed Aug 31, 2011 9:07 pm

Re: New EHCI driver fails on my system

Post by Noel Fuller »

Lio wrote:I jumped on the USB2 train by purchasing a second hand NEC 4+1 PCI USB card and inserted it either in slot 1-2-3, disabling/enabling front/rear onboard USB of my fixed A1XEG4 and it does not work properly !
I suppose I have the same card, at least it is NEC 4+1
MM-U2NEC101-4E1I

It works fine on my A1 XE G3

However, I had loads of trouble with a faulty cable to the hub I was using.

Noel
Post Reply