First of all, thank you for all your great work. It is
people like you that are turning Linux into an easier to use
platform.
Second, thanks for the prompt response!
Third, I was trying to avoid finding a Win machine where to
unpack the driver from the manufacturer's website. I found a
post somewhere suggesting the use of wine for exactly this
purpose.
Result: I got my .SYS file through wine, and subsequently
the .ihx file using your software. The firmware now
downloads to the USB device (via fxload & hotplugging), I
get the "heartbeat" LED on the device itself, and
/var/log/messages shows the disconnection/reconnection of
the USB device.
Now all I have to do is get the rest of the MIDI software
talking to each other.
Additional info for the avid reader:
Please note that all the above seemed to work flawlessly in
my 32-bit Athlon-based machine.
Using the exact same .SYS file and procedure on my 64-bit
Athlon based machine yielded the exact same contents for the
.ihx files. But the released fxload (compiled natively) on
the machine did not like the loader hex file -- it
complained of too short a line on the very first line of the
file and stopped.
The latest CVS version of fxload (also compiled natively)
did not complain on the files, and seemed to download them.
But I never got the LED "heartbeat" on the device or the
disconnect/reconnect messages on the log.
So far, I have tried dowloading -- via fxload from CVS --
the GPL firmware included in the traball at:
I download only the firmware; no loader firmware. I get the
"heartbeat", but no disconnection/reconnection yet. I am
guessing that the USB device is not warm booting after the
download.
But I guess all this has little to do with the fimware
extractor. I just posted it here in case it is useful for
anybody.
My apologies if I have abused this space.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=240068
The driver from the CD is another version (probably older)
that is not supported by the loader.
Please download the exact driver version from the URL in the
README
(<http://www.m-audio.com/images/global/drivers/MS1x1_1010_web.exe>).
Logged In: NO
First of all, thank you for all your great work. It is
people like you that are turning Linux into an easier to use
platform.
Second, thanks for the prompt response!
Third, I was trying to avoid finding a Win machine where to
unpack the driver from the manufacturer's website. I found a
post somewhere suggesting the use of wine for exactly this
purpose.
Result: I got my .SYS file through wine, and subsequently
the .ihx file using your software. The firmware now
downloads to the USB device (via fxload & hotplugging), I
get the "heartbeat" LED on the device itself, and
/var/log/messages shows the disconnection/reconnection of
the USB device.
Now all I have to do is get the rest of the MIDI software
talking to each other.
Additional info for the avid reader:
Please note that all the above seemed to work flawlessly in
my 32-bit Athlon-based machine.
Using the exact same .SYS file and procedure on my 64-bit
Athlon based machine yielded the exact same contents for the
.ihx files. But the released fxload (compiled natively) on
the machine did not like the loader hex file -- it
complained of too short a line on the very first line of the
file and stopped.
The latest CVS version of fxload (also compiled natively)
did not complain on the files, and seemed to download them.
But I never got the LED "heartbeat" on the device or the
disconnect/reconnect messages on the log.
So far, I have tried dowloading -- via fxload from CVS --
the GPL firmware included in the traball at:
http://homepage3.nifty.com/StudioBreeze/software/usbmidi-e.html
I download only the firmware; no loader firmware. I get the
"heartbeat", but no disconnection/reconnection yet. I am
guessing that the USB device is not warm booting after the
download.
But I guess all this has little to do with the fimware
extractor. I just posted it here in case it is useful for
anybody.
My apologies if I have abused this space.
Logged In: YES
user_id=240068
Your remaining problem looks like a fxload issue, if the
kernel version and the USB controller hardware are the same.