Firefox/4.0b8pre SeaMonkey/2.1b2pre   
   From: Peter Brown    
      
   Hi Dave   
      
   Dave Yeo wrote:   
   > Lars Erdmann wrote:   
   >> Hallo Dave,   
   >>   
   >> why are you listing only one OHCI controller from the pci.exe output   
   >> when in fact you have 2 of them ?   
   >   
   > Sorry, I thought the second would be redundant. I'll add it at the bottom.   
   >   
   >> I will have to look into the detection logic (obviously HCIMONIT is able   
   >> to detect them, I'll have   
   >> a look what it does differently from what the drivers do ...).   
   >> I assume you DO load OHCI drivers from config.sys ? In what order do you   
   >> load USBOHCD.SYS / USBEHCD.SYS ?   
   > from config.sys,   
   > rem BASEDEV=USBEHCD.SYS /V   
   > BASEDEV=USBUHCD.SYS /V   
   > BASEDEV=USBUHCD.SYS /V   
   > BASEDEV=USBD.SYS /REQ:USBUHCD$,USBOHCD$,USBEHCD$   
   >   
   > The install did not add the USBEHCD.SYS, it was added by USBCFGB7A and I   
   > remmed it out so the system would boot.   
      
      
   Sounds like you are using the /APIC switch with acpi.psd   
      
   If you have 2 OHCI controllers and no UHCI controllers why are you    
   loading 2 instances of UHCI drivers? USBcfg should have reported what    
   controllers are available on the system.   
      
   The EHCI driver should be after UHCI and OHCI drivers in the config.sys    
   - the later build of USBcfg gets that right    
   http://hobbes.nmsu.edu/download/pub/os2/system/USBcfgb071.zip   
      
   Also you may want to delete /REQ:USBUHCD$,USBOHCD$,USBEHCD$ from the    
   BASEDEV=USBD.SYS line as that switch should not be needed.   
      
   Regards   
      
   Pete   
      
      
      
    I'll try reversing them later   
   > when the system is quiet.   
   >   
   >> Can you revert the order and retry ?   
   >>   
   >> Are you saying that on your system you have NO UHCI even though you have   
   >> EHCI ? In other words: EHCI "builds   
   >> on top of" OHCI and not on UHCI ?   
   >   
   > That is what pci.exe and hcimonit.exe report.   
   >   
   >>   
   >>   
   >> Lars   
   >>   
   >> Dave Yeo wrote:   
   >>> Lars Erdmann wrote:   
   >>>> I have updated the USB host controller drivers   
   >>>> USBUHCD.SYS,USBOHCD.SYS,USBEHCD.SYS.   
   >>>> I have now placed these on hobbes.   
   >>>> They will eventually make it into directory:   
   >>>> /pub/os2/system/drivers/misc   
   >>>>   
   >>>> Lars   
   >>>   
   >>> I was hoping these would help me but with both the stock and yours I   
   >>> get the message that no OHCI drivers can be found on the PCI bus. The   
   >>> EHCI driver causes a crash in the kernel when loading JFS. HCIMONIT   
   >>> does report 2 PCI USB OHCI host   
   >>> controllers and one EHCI.   
   >>>   
   >>> Vendor 10DEh Nvidia Corp   
   >>> Device 0067h nForce2 OHCI USB Controller   
   >>> Command 0007h (I/O Access, Memory Access, BusMaster)   
   >>> Status 00B0h (Has Capabilities List, Supports 66MHz,   
   >>> Supports Back-To-Back Trans., Fast Timing)   
   >>> Revision A4h, Header Type 80h, Bus Latency Timer 00h   
   >>> Minimum Bus Grant 03h, Maximum Bus Latency 01h   
   >>> Self test 00h (Self test not supported)   
   >>> PCI Class Serial, type USB (OHCI)   
   >>> Subsystem ID 0C111043h Unknown   
   >>> Subsystem Vendor 1043h ASUSTeK Computer Inc   
   >>> Address 0 is a Memory Address (anywhere in 0-4GiB) : ED083000h   
   >>> System IRQ 5, INT# A   
   >>> New Capabilities List Present:   
   >>> Power Management Capability, Version 1.1   
   >>> Supports low power State D1   
   >>> Supports low power State D2   
   >>> Supports PME# signalling from mode(s) D0, D1, D2, D3hot, D3cold   
   >>> PME# signalling is currently disabled   
   >>> Current Power State : D0 (Device operational, no power saving)   
   >>>   
   >>> Vendor 10DEh Nvidia Corp   
   >>> Device 0068h nForce2 EHCI USB 2.0 Controller   
   >>> Command 0006h (Memory Access, BusMaster)   
   >>> Status 00B0h (Has Capabilities List, Supports 66MHz,   
   >>> Supports Back-To-Back Trans., Fast Timing)   
   >>> Revision A4h, Header Type 80h, Bus Latency Timer 00h   
   >>> Minimum Bus Grant 03h, Maximum Bus Latency 01h   
   >>> Self test 00h (Self test not supported)   
   >>> PCI Class Serial, type USB 2.0 (EHCI)   
   >>> Subsystem ID 0C111043h Unknown   
   >>> Subsystem Vendor 1043h ASUSTeK Computer Inc   
   >>> Address 0 is a Memory Address (anywhere in 0-4GiB) : ED082000h   
   >>> System IRQ 11, INT# C   
   >>> New Capabilities List Present:   
   >>> USB 2.0 EHCI Debug Port Capability   
   >>> Power Management Capability, Version 1.1   
   >>> Supports low power State D1   
   >>> Supports low power State D2   
   >>> Supports PME# signalling from mode(s) D0, D1, D2, D3hot, D3cold   
   >>> PME# signalling is currently disabled   
   >>> Current Power State : D0 (Device operational, no power saving)   
   >>>   
   > Vendor 10DEh Nvidia Corp   
   > Device 0067h nForce2 OHCI USB Controller   
   > Command 0007h (I/O Access, Memory Access, BusMaster)   
   > Status 00B0h (Has Capabilities List, Supports 66MHz,   
   > Supports Back-To-Back Trans., Fast Timing)   
   > Revision A4h, Header Type 80h, Bus Latency Timer 00h   
   > Minimum Bus Grant 03h, Maximum Bus Latency 01h   
   > Self test 00h (Self test not supported)   
   > PCI Class Serial, type USB (OHCI)   
   > Subsystem ID 0C111043h Unknown   
   > Subsystem Vendor 1043h ASUSTeK Computer Inc   
   > Address 0 is a Memory Address (anywhere in 0-4GiB) : ED081000h   
   > System IRQ 10, INT# B   
   > New Capabilities List Present:   
   > Power Management Capability, Version 1.1   
   > Supports low power State D1   
   > Supports low power State D2   
   > Supports PME# signalling from mode(s) D0, D1, D2, D3hot, D3cold   
   > PME# signalling is currently disabled   
   > Current Power State : D0 (Device operational, no power saving)   
   >   
   > Thanks,   
   > Dave   
      
   --- Internet Rex 2.31   
    * Origin: virginmedia.com (1:261/20.999)   
|