Can not initialize device may be related to an invalid IRQ

The intent of this forum is to discuss my DOS TSR programs (available at http://bretjohnson.us), how they work and don't work, new/missing features, status of updates, and anything else related to them that may need to be discussed.

Can not initialize device may be related to an invalid IRQ

Postby Arandy » Tue Jul 23, 2019 4:40 am

Hello Bret,

I'm trying to use your USBUHCI program under Freedos 13beta.

The system is a 486 PCI board with SIS chipset. CPU is Am5x86-133ADZ. No overclocking is done, BIOS has default values and NO USB support.

I have two VIA VT6202 cards and none of them works, no matter changing the options i use. I've tested them under Windows98, they works fine.

USBHOSTS works fine and i get the list of UHCI devices (one at ioaddr 6000h irq9 and a second one at ioaddr 6100h irq10, EHCI part is listed aswell).

I would really like to make it work because I don't want to spend 65$ for a commercial version of this program: www.dosusb.net.....yet. (Do you know it?)

I don't want to waste your time but some hints would be very apreciated.

Thank you.
Arandy
 
Posts: 3
Joined: Tue Jul 23, 2019 4:27 am

Re: Can not initialize device may be related to an invalid IRQ

Postby Bret » Tue Jul 23, 2019 9:10 am

A couple of things to try.

First of all, try installing the driver for the second UHCI controller (Index 1) before the first controller (Index 0). I've had computers where that was the only way to get them to work correctly:

USBUHCIL Index:1

If that doesn't help, try installing with the ProgramDebug (or PD) option. This prints out a bunch of debugging messages as USBUHCIL is installing letting you know what happens during each step of the installation. Send the output of that and I may be able to tell exactly which step of the installation process isn't working correctly.
Bret
 
Posts: 478
Joined: Fri Oct 10, 2008 3:43 am
Location: Rio Rancho, NM

Re: Can not initialize device may be related to an invalid IRQ

Postby Arandy » Tue Jul 23, 2019 10:13 am

First of all thank you for this quick response.

I tried /Index 1 but it had no effect. Still same message.

I tried to gather more information so here it is. This the output of USBHOSTS command:

USBHOSTS 0.06, (C) 2007-2009, Bret E. Johnson.

PCI BUS
══════════ BASE USB DRIVER
I B D F BASE PHYSICAL ═══════════════════
HOST d u v n USB IRQ I/O MEMORY HST BW
TYPE x s c c VENDR PROD VER NUM ADDR ADDRESS IDX STATUS USED
════ ═ ═══ ══ ═ ═════ ═════ ═══ ═══ ═════ ══════════ ═══ ══════════ ════
UHCI 0 0 15 0 1106h 3038h 1.0 10 6000h ▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒
VIA Technologies Inc

UHCI 1 0 15 1 1106h 3038h 1.0 11 6100h ▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒
VIA Technologies Inc

════ ═ ═══ ══ ═ ═════ ═════ ═══ ═══ ═════ ══════════ ═══ ══════════ ════
EHCI 0 0 15 2 1106h 3104h 2.0 9 ▒▒▒▒▒ F400_0000h ▒▒▒ ▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒
VIA Technologies Inc

I used another utility (pcicfg) that outouts the same data:

PCI bus 00 device 0F function 00: Header Type 'non-bridge' (multi-func)
Vendor: 1106 VIA Technologies
Device: 3038 AMD-645 / VT82C586A/B PBC, USB controller
Class: 0C serial bus Revision: 50
SubClass: 03 USB ProgramI/F: 00
CommandReg: 0007 = I/O-on mem-on busmstr
Status Reg: 0210 = CapList (med)
CacheLine: 00 Latency: 20 BIST: 00
SubsysVendor: 0925 SubsysDevice: 1234
Base Addresses:
(4) 00006001 = I/O base=00006000 len=32
CardBus: 00000000 ExpansionROM: 00000000 (no ROM)
INTline: 0A INTpin: 01
MinGrant: 00 MaxLatency: 00
Device-Specific Data:
40: 00031040 003000C2 00000000 00000000 00000000 00000000
58: 00000000 00000000 00000010 00000000 00000000 00000000
70: 00000000 00000000 00000000 00000000 00020001 00000000
88: 00000000 00000000 00000000 00000000 00000000 00000000
A0: 00000000 00000000 00000000 00000000 00000000 00000000
B8: 00000000 00000000 00002000 00000000 00000000 00000000
D0: 00000000 00000000 00000000 00000000 00000000 00000000
E8: 00000000 00000000 00000000 03000000 00000000 00000000
Capabilities List:
ID @80 = 01 PCI Power Management
PMC =
DynClk = 0, PCI_PM version = 2
PMCSR = 0000, data-select=0 unknown/unimplemented
state=D0
PMCSRX = -- -- -- --
Data = 00

-----------------------------------------------------------
PCI bus 00 device 0F function 01: Header Type 'non-bridge' (multi-func)
Vendor: 1106 VIA Technologies
Device: 3038 AMD-645 / VT82C586A/B PBC, USB controller
Class: 0C serial bus Revision: 50
SubClass: 03 USB ProgramI/F: 00
CommandReg: 0007 = I/O-on mem-on busmstr
Status Reg: 0210 = CapList (med)
CacheLine: 00 Latency: 20 BIST: 00
SubsysVendor: 0925 SubsysDevice: 1234
Base Addresses:
(4) 00006101 = I/O base=00006100 len=32
CardBus: 00000000 ExpansionROM: 00000000 (no ROM)
INTline: 0B INTpin: 02
MinGrant: 00 MaxLatency: 00
Device-Specific Data:
40: 00031040 003000C2 00000800 00000000 00000000 00000000
58: 00000000 00000000 00000010 00000000 00000000 00000000
70: 00000000 00000000 00000000 00000000 00020001 00000000
88: 00000000 00000000 00000000 00000000 00000000 00000000
A0: 00000000 00000000 00000000 00000000 00000000 00000000
B8: 00000000 00000000 00002000 00000000 00000000 00000000
D0: 00000000 00000000 00000000 00000000 00000000 00000000
E8: 00000000 00000000 00000000 03000000 00000000 00000000
Capabilities List:
ID @80 = 01 PCI Power Management
PMC =
DynClk = 0, PCI_PM version = 2
PMCSR = 0000, data-select=0 unknown/unimplemented
state=D0
PMCSRX = -- -- -- --
Data = 00

-----------------------------------------------------------
PCI bus 00 device 0F function 02: Header Type 'non-bridge' (multi-func)
Vendor: 1106 VIA Technologies
Device: 3104 ???
Class: 0C serial bus Revision: 51
SubClass: 03 USB ProgramI/F: 20
CommandReg: 0007 = I/O-on mem-on busmstr
Status Reg: 0210 = CapList (med)
CacheLine: 00 Latency: 20 BIST: 00
SubsysVendor: 0925 SubsysDevice: 1234
Base Addresses:
(0) F4000000 = mem base=F4000000 len=256
CardBus: 00000000 ExpansionROM: 00000000 (no ROM)
INTline: 09 INTpin: 03
MinGrant: 00 MaxLatency: 00
Device-Specific Data:
40: 00010000 00000000 00000080 00000000 80005A00 00000000
58: BBBB0B04 00000053 00010020 00000000 00000000 00000000
70: 00000000 00000000 00000000 00000000 480A0001 00000000
88: 00000000 00000000 00000000 00000000 00000000 00000000
A0: 00000000 00000000 00000000 00000000 00000000 00000000
B8: 00000000 00000000 00000000 00000000 00000000 00000000
D0: 00000000 00000000 00000000 00000000 00000000 00000000
E8: 00000000 00000000 00000000 03000000 00000000 00000000
Capabilities List:
ID @80 = 01 PCI Power Management
PMC = PME-Clk PME#-D0 PME#-D3hot
DynClk = 0, PCI_PM version = 2
PMCSR = 0000, data-select=0 unknown/unimplemented
state=D0
PMCSRX = -- -- -- --
Data = 00

I've added /pd option and this is the output:

DEBUG: PCI Bus-Dev-Func: 0-15-0
DEBUG: PCI Search Index: 0
DEBUG: IRQ Number: 10
DEBUG: Base I/O Address: 6000h
DEBUG: Frame List Addr: 0013_9000h

DEBUG: Stopping Host
DEBUG: Enabling I/O Access & Bus Mastering
DEBUG: Disabling SMI Flags
DEBUG: Enabling Resume/Connect Detection
DEBUG: Redirecting Host IRQ Interrupt
DEBUG: Resetting Host
DEBUG: Enabling IRQ Generation
DEBUG: Setting Frame List Address
DEBUG: Setting Frame Timing
DEBUG: Restoring Root Hub Port 1 Status
DEBUG: Restoring Root Hub Port 2 Status
DEBUG: Setting Start Frame Number
DEBUG: Enabling SMI Flags
DEBUG: Restoring IRQ Number
DEBUG: Enabling IRQ Flags
DEBUG: Restoring PCI Configuration
The USB Host Controller failed to initialize properly.
Aborting Installation
This could be related to an invalid IRQ#.

Any ideas?
Arandy
 
Posts: 3
Joined: Tue Jul 23, 2019 4:27 am

Re: Can not initialize device may be related to an invalid IRQ

Postby Bret » Thu Jul 25, 2019 5:41 am

Investigating this further -- please give me a few days.
Bret
 
Posts: 478
Joined: Fri Oct 10, 2008 3:43 am
Location: Rio Rancho, NM

Re: Can not initialize device may be related to an invalid IRQ

Postby Arandy » Thu Jul 25, 2019 10:15 am

Thank you Bret! you're very kind!

To add more information the motherboard I am using (model LE-486E) has SIS 85C496 PCI/CPU Memory Controller and SIS 85C497 AT BUS Controller
Arandy
 
Posts: 3
Joined: Tue Jul 23, 2019 4:27 am

Re: Can not initialize device may be related to an invalid IRQ

Postby Bret » Mon Aug 05, 2019 5:39 am

Unfortunately, I wasn't able to figure anything out. The point where it is failing is where the host controller is resetting/initializing and for whatever reason the host just isn't responding correctly.

Thee only thing I think I can suggest is playing around with whatever USB options you have in the BIOS, including turing the USB completely on (or off) in the BIOS and see what happens. Soryry I can't help more than that.
Bret
 
Posts: 478
Joined: Fri Oct 10, 2008 3:43 am
Location: Rio Rancho, NM


Return to Programs

Who is online

Users browsing this forum: No registered users and 4 guests

cron