Attention! Motu 828mk3 Firewire Expresscard Users

[acidrecords]

@ all people here which are using the 828mk3 with a notebook with win xp and a firewire expresscard. (not pcmcia! expresscard only!)

do you have any problems with the mk3?

eg. no sound from 828mk3 / yellow exclamation mark in windows device manager.

if yes/no please also always post your servicepack, motu driver version, expresscard vendor + notebook vendor.

thanks

chris

[Recorder]

Why taking a list only from notebook users? I have this problem you said (yellow exclamation point on Wave driver in Device manager) and I have a high end desktop computer (Win XP PRO SP3, driver 1.06).

[majdid]

mine is a Belkin FW Expresscard, tried it with two recent laptops, XP SP3 and Vista SP1, BSOD all the time, doesnt work at all. im sticking to my stock FW port (RICOH), works but not stable at all. latest motu drivers/firmware

[acidrecords]

@ Recorder

why i`ve asked about notebooks only?
because with onboard chipsets it works for me (tested on desktop + notebook)

with expresscards i have massive problems.

but lets expand this thread to booth > onboard + express + pcie firewirecards.

but @ all please >>> please always provide the asked infos. (fw chipset and so on from first post in this thread)
extra problems and tests from you > please open new thread with error description + all your test you`ve done + post link to your issue thread here in this thread.

thank you. i will check this and report it to motu. parallel please open motu techlinks in your motu account. (if not allready done)

[acidrecords]

additional infos:

it seems that motu does not proper test their products.

until today i`ve not seen any customer which got it running without problems with expresscard.

i`m also in contact with my notebook vendor since 3 month now. yesterday i`ve got the info from them that they think (99%) that the 828mk3 is the problem.

because: fw expresscard works with all gear (fw hdd, fw camcorder, focusrite liquidmix and so on)
only the 828mk3 does not work.

>>>>>>>>>>To sum up,
If you got an error code 12 with the PCI ExpressCard only, it might a BIOS
issue.
However, if you got the error code when you connect the audio interface,
this usually means the memory, I/O, or prefetch is more than what the
ExpressCard has allocated in the Driver. Maybe, you need a driver solution to get more resource.
<<<<<<<<


>>>>>>>>> tests i`ve done with my notebook:


TEST #1
>
> pc started without battery.
> expresscard deinstalled and removed > reboot.
> card installed normally witout windows promt to reboot the system.
> audiointerface turned on & connected to the expresscard> audiointerface
> was
> recognized but no sound from the audiointerface + the config-gui from the
> audiointerface is extremely slow and stutters.
> after that: expresscard removed with rightclick on the "remove hardware"
> taskbar icon + expresscard removed from expresscard slot.
> after that: expresscard inserted again (with turned on audiointerface) >
> same thing again > no sound + gui slow and stutters.
> then > after normal reboot > expresscard not shown in devicemanager.
> after that: shutdown + ac removed. waited for ~1min + restartet
> audiointerface + turned on pc.
> in devicemanager > yellow exclamation mark (code 12).
> again reboot (with expresscard connected + audiointerface turned on) > no
> change > yellow exclamation mark (code 12).
> TEST END.
>
>
> ##############################
>
> TEST #2
>
> battery in notebook.
> expresscard deinstalled + removed from system + shutdown.
> bootup without card.
> shutdown.
> bootup with card (without audiointerface connected) > card installed
> without
> problems.
> shutdown (with card in expresscard slot)
> expresscard removed from turned off system.
> then > startup without expresscard + shutdown.
> then > removed battery + removed ac. > audiointerface connected to
> expresscard. expresscard inserted in expresscard slot + audiointerface
> turned on.
> startup > expresscard recognized but audiointerface not. usb port from
> expresscard also works!
> reboot system with audiointerface connected to expresscard > yellow
> exclamation mark (code 12) in devicemanager.
> then > shutdown + ac removed + restarted audiointerface. > bootup >
> audiointerface works without problems + audiointerface gui works also
> without problems.
> reboot (with audiointerface turned on) > expresscard not recognized from
> windows.
> again reboot > expresscard has yellow exclamation mark (code 12) in
> devicemanager.
> shutdown with audiointerface connected. (without notebook ac removed) >
> restarted audiointerface + started pc > yellow exclamation mark (code 12)
> in
> devicemanager.
> again shutdown + ac removed + audiointerface restarted > yellow
> exclamation
> mark (code 12) in devicemanager.
> again shutdown + ac removed + audiointerface restarted > all is working
> fine!!!
> reboot with audiointerface connected > expresscard not recognized.
> again shutdown + ac removed + audiointerface restarted > yellow
> exclamation
> mark (code 12) in devicemanager.
> and also again shutdown + ac removed + audiointerface restarted > yellow
> exclamation mark (code 12) in devicemanager.
> TEST END.
>
>
> ###########
>
> TEST #3
>
> pc started (without battery) without deinstalling expresscardcard from
> system. (expresscard had yellow exclamation mark (code 12) in
> devicemanager>
> from last test.)
> shutdown.
> expresscard connected to system. > expresscard recognized without
> problems.
> > shutdown (with expresscard connected to pc) + ac removed +
> audiointerface
> connected to expresscard + started pc.
> expresscard recognized but only as pci standard to pci bridge.
> shutdown system again (without removing the expresscard) > ac removed +
> audiointerface restarted.
> pc started. > all is working fine!! audiointerface ha no problems.
> audiointerface turned off while windows was running. > audiointerface
> normaly removed from devicemanager.
> audiointerface turned on again > no problems > all working fine!
> > shutdown > audiointerface not restarted. > pc started > expresscard not
> recognized from system.
> > shutdown (without removing expresscard, without turning off
> audiointerface) > ac removed from notebook + audiointerface restarted.
> pc turned on > yellow exclamation mark (code 12) in devicemanager.
> TEST END
>
> #########################
>
> TEST #4
>
> expresscard deinstalled and removed from expresscard slot.
> expresscard inserted in expresscard slot. > windows installed drivers +
> promts that it needs reboot to make it work.
> pc rebooted > windows loaded > audiointerface started + connected to
> expresscard. > audiointerface works without problems! audiointerface also
> works without problems.
> audiointerface turned off > bluescreen > irql not less or equal!!
> TEST END.


i know some testresults look really crazy, but that`s how it is.

[Recorder]

OK acidrecords, I understand. So, this is my long post (you just replied today):
http://www.motunation.com/forum/viewtop ... 58&start=0
Please note that in my situation I have Error code 10 (not 12), and I can confirm what you said about MOTU problem, because all other device connected to Firewire ports in my computer work very well. Last week I made a two hours long (2 hours!!!) video capture using my Canopus device and it didn't loose ANY FRAMES!!! You can read all infos and tests in my thread, and Motu Techlink told me again to test a TI chipset (I just tested Agere they suggest).
Thank you for your support.

[acidrecords]

hey recorder

please also post this thread in your techlink and tell them to read the thread.
because then they will see that the problem is not the expresscard / chipset and that the motu driver is the source of the problem!

[Recorder]

OK acidrecords, just done now. I believe that everyone having a MOTU Techlink opened could post this link there; reading many different situation maybe MOTU's technicians could have more ideas and we can hope they could solve all our problem.

[acidrecords]

you wrote that you can use any other fw gear without problems.
it`s the same here. fw hdd works for me without problems, fw camcorder capture also works without problems but the only one that does not is the 828mk3. (code 12)

[jamie3]

hey everyone.

looks like you are having the same issues that i am

here is my specs:

Motu 828 MK3 v1.04 works fine on my windows desktop (has onboard TI chipset)

Does NOT work with my dell m65 laptop
Onyx2 firewire chipset
XP SP2

Purchased a Syba expresscard model# SD-EXPC34-2F1U which has a TI XIO2200 Chipset
Still no luck. Get the same problems as the Onyx2. DRIVER_IRQL_NOT_LESS_OR_EQUAL.

Going to try and disable some devices (if they share the same IRQ).

crossing fingers

[jamie3]

hey everyone.

looks like you are having the same issues that i am

here is my specs:

Motu 828 MK3 v1.04 works fine on my windows desktop (has onboard TI chipset)

Does NOT work with my dell m65 laptop
Onyx2 firewire chipset
XP SP2

Purchased a Syba expresscard model# SD-EXPC34-2F1U which has a TI XIO2200 Chipset
Still no luck. Get the same problems as the Onyx2. DRIVER_IRQL_NOT_LESS_OR_EQUAL.

Going to try and disable some devices (if they share the same IRQ).

crossing fingers

well no luck. disabled nearly all devices from the bios. even additional devices within windows. the ti chipset shows in the device manager but the card doesnt work. ableton wont even load.

so the TI chipset compatibility is untrue.

[APADRecordings]

Several of us are looking at this same issue. It appears there is a definite problem with the Core 2 Duo computer architecture. The Dell D830 exhibits this same problem as do many other computers.

There have been many posts by others about running only this program or that program, disabling features, etc. None of this should be necessary. I have older computers here with single core processors that handle firewire recording just fine while running several other programs.

I have yet to see a Core 2 Duo machine (945, 946GZ chipsets, PCIe buss, SATA drives) that can stream audio, without interruption, over the 1394 buss, whether using the internal 1394 chipset, or a cardbus or Expresscard adapter (even with the TI chipset).

Unfortunately Firewire implementation is going backward at the speed of light. And with audio/video users being less than 1% of computer users I'm sure we're so far under the radar that Intel could care less.

[miko]

I had: Sony Vaio SZ2M/B (core 2) with the 828mkII attached to internal Firewire 400 slot, running Cubase Studio 4 on Vista 32bit: all worked well.

I have now: Zepto Nox A15 notebook (core 2) without Firewire, Vista 32bit, a Belkin USB/FW Expresscard (Texas Instruments driver) plugged in the cardslot with 828mkII attached and this gives me "no MOTU audio device detected" when opening CueMix or Audio Console after 'succesfully' installing the old driver. Main result is no sound or communication with the device.

The new driver allows me to enter the CueMix/FX and Audio Console, but everything in CueMix/FX is real slow and trying to do settings will just reset. Again no sound or communication with the 828mkII here.

When I use the Main Out of the 828mkII and try to play some mp3's and video on youtube, the video/audio streams starting (without sound though) but hang as soon as it tries to make its way through the Firewire expresscard to the 828mkII. So to me it looks like the drivers arent able to communicate via the expresscard with the audio device.

So what is the difference between a digital cam/firewire HDD that can work with the FW expresscard, and the MOTU 828mkII/III? I wished it just worked the same like any data stream should, but the MOTU device just says "hold it there, stop now" ...

[kikok]

Have exactly the same problem with the Ultralite mk3...
Tested all version of Vista and XP (32 and 64 bit) on-board and ExpressCard TI Chipset for Firewire.
Problems are always the same:
- No interaction between the OS and the Sound Device
OR
- BSOD with the IRQL_NOT_LESS_OR_EQUAL
No helpfrom the Tech support, completely incompetent on their products and they are unable to give any target date for new drivers or firmware...
I heard MOTU were serious about their drivers, it seems like it's not really the case... Wait&See

[acidrecords]

@ all


read this document! >> the problems with code 12 and so on come from issuficient bridge resources!

so the pc / notebook vendors have to do > bios updates.

read the whole doc`s

http://b.imagehost.org/download/0991/PC ... ardBus.doc

http://b.imagehost.org/download/0680/PCI-rsc.doc

this files are for pci + pci-express !

i really don`t know why pc vendors are so brainless....