Author Topic: MSI Digivox not recognized (?)  (Read 2704 times)

warpcafe

  • Guest
MSI Digivox not recognized (?)
« on: February 26, 2010, 07:33:01 PM »
Hi,

I just recently had the chance to get hold of a Digivox II v3.0... at least that's what I've been told it is.
I downloaded and installed the latest Emperoar but when I launch it, it tells me there is no suitable hardware present.

Question: how can I check if my device really is a supported one? (e.g. what should be the pci ids? "pci&ven&rev"...)

Cheers,
Thomas

Rudi

  • Global Moderator
  • Super Senior Member
  • *****
  • Posts: 572
    • http://www.s-t.de/emperoar
Re: MSI Digivox not recognized (?)
« Reply #1 on: February 27, 2010, 01:20:14 AM »
Hi Thomas,

> Question: how can I check if my device really is a supported one? (e.g. what should be the pci ids? "pci&ven&rev"...)

I guess you mean USB ID... The Digivox II v3.0 uses the generic ID assigned by the chip manufacturer, which is 15A4:9016.

A common reason for Emperoar not recognizing a (suppported) USB device is, that it might have been connected to an USB 1.1 port or the USB2.0 base driver is not installed correctly. And when we are talking about USB base drivers: please use the copy of USBEHCD.SYS that comes with ETV.



warpcafe

  • Guest
Re: MSI Digivox not recognized (?)
« Reply #2 on: February 27, 2010, 03:01:20 AM »
Moin,

I guess you mean USB ID... The Digivox II v3.0 uses the generic ID assigned by the chip manufacturer, which is 15A4:9016.
Yes, you are correct. I meant the USB ID.
Well, the 15A4:9016 matches. However... I have plugged it into the Windows machine to see what it says... and for the &rev it tells me "0200". Ouch.

A common reason for Emperoar not recognizing a (suppported) USB device is, that it might have been connected to an USB 1.1 port or the USB2.0 base driver is not installed correctly. And when we are talking about USB base drivers: please use the copy of USBEHCD.SYS that comes with ETV.
Yes, I know about the USB 2.0 requirement but can assure you that the ports are 2.0 types. However, for the USBEHCD.SYS... I didn't know at all there was a special version for ETV. Does this get installed automatically? Hm... don't think so, otherwise you wouldn't have pointed me to that, right? ;) Will give it another try and let you know if that did the trick. However, since I am almost sure the Digivox is a 2.0 version... ah, who cares. Better be safe than sorry, I'll check it.

Thanks! Thomas.

Rudi

  • Global Moderator
  • Super Senior Member
  • *****
  • Posts: 572
    • http://www.s-t.de/emperoar
Re: MSI Digivox not recognized (?)
« Reply #3 on: February 27, 2010, 05:09:30 AM »
Well, the 15A4:9016 matches. However... I have plugged it into the Windows machine to see what it says... and for the &rev it tells me "0200". Ouch.

That's fine. But doesn't matter either... 


However, since I am almost sure the Digivox is a 2.0 version

You mean because of the "0200" reported on USB ? That is normal. This number does not reflect the "v3.0" in the name of the product.


Does this get installed automatically ?

No. But it shouldn't have something to do with device detection. Unless your USB stack is not at buildlevel 10.162...
Do you have USBResMgr installed on that machine. If not, do so and investigate the device report (right mouse click).

It should say something like this:

Code: [Select]
<<< Device Description >>>
 Type            : 01
 USB Rev         : 200
 Class           : Reserved (0)
 Subclass        : Reserved (0)
 Protocol        : Reserved (0)
  Device Information is defined at interface Level
 Max. packetsize : 40
 Vendor  ID      : 15A4
 Product ID      : 9016
 Device Release# : 0200
 Strings:
  Manufacturer Name : Afatech
  Product Name      : DVB-T 2
  Serial number     : Not implemented
 Number of Configurations : 1

 Configuration 0 :

...

   Interface 0

...

   Endpoint 0:
    Address     : 81
    Attributes  : 02
    Packetsize  : 0200   <------- !!!!
    Interval    : 0
...


If your device is properly detected by the USB base drivers, "Packetsize" should be 0200.

BTW, to rule out something really stupid: You do have the line:

DEVICE=X:\...\AF9015.SYS

in your CONFIG ? If not, you might have forgotten to select the proper device driver during install.

« Last Edit: February 27, 2010, 05:24:25 AM by Rudi »

warpcafe

  • Guest
Re: MSI Digivox not recognized (?)
« Reply #4 on: February 28, 2010, 09:41:45 AM »
Hi Rudi,

I just D/L'ed and installed USBRESMGR. It says:

Quote
<<< Device Description >>>
 Type            : 01
 USB Rev         : 200
 Class           : Reserved (0)
 Subclass        : Reserved (0)
 Protocol        : Reserved (0)
  Device Information is defined at interface Level
 Max. packetsize : 40
 Vendor  ID      : 15A4
 Product ID      : 9016
 Device Release# : 0200
 Strings:
  Manufacturer Name : Afatech
  Product Name      : DVB-T 2
  Serial number     : 010101010600001
 Number of Configurations : 1

 Configuration 0 :
  Lenght     : 71
  Name       : <NONE>
  Value      : 1
  Attributes : 0x80
  Power      : 500 mA
  Interfaces : 2

  Interface 0
   Alt Setting : 0
   Name        : <NONE>
   Class       : Vendor specific
   SubClass    : Vendor specific
   Protocol    : Vendor specific
   Endpoints   : 4

   Endpoint 0:
    Address     : 81
    Attributes  : 02
    Packetsize  : 0200
    Interval    : 0

   Endpoint 1:
    Address     : 02
    Attributes  : 02
    Packetsize  : 0200
    Interval    : 0

   Endpoint 2:
    Address     : 84
    Attributes  : 02
    Packetsize  : 0200
    Interval    : 0

   Endpoint 3:
    Address     : 85
    Attributes  : 02
    Packetsize  : 0200
    Interval    : 0

  Interface 1
   Alt Setting : 0
   Name        : <NONE>
   Class       : Human Interface Device (HID)
   SubClass    : No Subclass
   Protocol    : Keyboard
   Endpoints   : 1
   HID Description:
    Length          : 09
    HID Rel. Number : 101
    Country Code    : 0000
    Descriptors     : 1
     Type          : 22
     Length        : 0
     Type          : 07
     Length        : 0

   Endpoint 0:
    Address     : 83
    Attributes  : 03
    Packetsize  : 0000
    Interval    : 16

Looks OK as far as I can judge.
However, Emperoar still complains... although I also changed to use the USBEHCD you told me.

BTW - since I have that USB driver loaded, I get "beeps" when the Digivox is plugged in:
- plugin: low beep
- ~1 sec. later: high beep
- then nothing happens in matters of beeps... until I launch Emperoar:
- low beep, repeated every 5 seconds until I plug-out (remove) the Digivox

I have eCS RC6a installed. The USB drivers say "10.162"... (except for USBUHCD2.SYS which is downlevel to 10.058).
I can't tell which ACPI stuff I have installed, but can dig that out if it's relevant.

Cheers,
Thomas
« Last Edit: February 28, 2010, 09:59:17 AM by warpcafe »

Rudi

  • Global Moderator
  • Super Senior Member
  • *****
  • Posts: 572
    • http://www.s-t.de/emperoar
Re: MSI Digivox not recognized (?)
« Reply #5 on: February 28, 2010, 11:59:24 AM »
Quote
Looks OK as far as I can judge.

Yes, it does.

Quote
BTW - since I have that USB driver loaded, I get "beeps" when the Digivox is plugged in:
- plugin: low beep
- ~1 sec. later: high beep

That is good. The first beep indicates that AF9015.SYS got notified by the USB stack about
the device attachment. The second say that the firmware upload has completed and that the
stick is ready to use.


Quote
- then nothing happens in matters of beeps... until I launch Emperoar:
- low beep, repeated every 5 seconds until I plug-out (remove) the Digivox

Hmm, something strange is going on in your system... I'll contact you directly.


Rudi

  • Global Moderator
  • Super Senior Member
  • *****
  • Posts: 572
    • http://www.s-t.de/emperoar
Re: MSI Digivox not recognized (?)
« Reply #6 on: March 04, 2010, 02:48:22 AM »
O.K., this is a strange problem:  In version 2.04a I added a feature, that would reset the
USB port in case of certain errors beeing reported by the base drivers. For some reason
these type of errors occure on your system right after device attachment and do not go
away on reset.

The new version 2.05a reverted to the old behavior.
I.e. it simply ignores these errors and tries to continue. This version also includes some
cosmetic fixes to the GUI.

« Last Edit: March 04, 2010, 02:50:10 AM by Rudi »