driver for ICON umix1008 usb audio interface

[stemsee]

I bought a secondhand icon umix1008 10 in 8 out 96/192khz usb recording interface at a bargain price. I have plugged it into my laptop and no drivers loaded for it .... i was hoping that usb audio driver would pick it up, alas no. lsusb shows the device as

Code: Select all

Bus 001 Device 008: ID 1d03:000a iCON Umix1008 Satellite

how would i go about finding an appropriate driver or forcing an existing driver to work with it? I did a quick search of the kernel config file but found nothing.

[mikewalsh]

@stemsee :-

D'you by any chance have a picture of it? A web search for

Code: Select all

Device ID 1d03:000a

.....was very vague, and gave lots of results totally unrelated to your item.

Normally, the 4 characters prior to the ":" indicate the manufacturer, while those after indicate the item itself. Even the Windows driver sites - which are very good at identifying this stuff! - couldn't find a match. It could be a mislabelled item, i.e., it's 'generic'.....made in an anonymous "sweat shop" somewhere in the Far East, and sold to 100s of manufacturers who then slap their own labels/model numbers on it.

We might strike lucky, we might not....

Ah. Is this the item in question?

https://iconproaudio.com/product/umix1008-satellite/

Mm... Mm-hm..... Uh-huh..... Um. I reckon you're going to be out of luck with this - under Puppy, that is. States very clearly Windows and MacOS only. I had a look at the driver downloads; hoping to perhaps find some source code, but....nah. This looks to be very definitely proprietary, closed-source & closely-guarded. You can only obtain the drivers in ready-to-use format; they're not letting anybody compile this themselves.....

Looks like you're SOL, buddy.

Mike.

[stemsee]

Yes, I think you are right.....proprietary driver only.....but i remember there was a work around using some network driver manipulation tool, i forgot what it was called. It allowed the use of windows drivers for network cards and other hardware. But I don't think it will work.

This is the correct device as that in your link.

[mikewalsh]

Yes, I think you are right.....proprietary driver only.....but i remember there was a work around using some network driver manipulation tool, i forgot what it was called. It allowed the use of windows drivers for network cards and other hardware. But I don't think it will work.

This is the correct device as that in your link.

Hm. Were you thinking of ndiswrapper ?

Mike.

[stemsee]

yes, that is it!