PCLinuxOS-Forums
News: ...FLASH!!! ...New PCLinuxOS Testing board now open. Register today! Be an active contributor to the PCLinuxOS future! ... Read all about it now, on THIS forum!!!..
 
*
Welcome, Guest. Please login or register. May 27, 2012, 07:29:52 AM


Login with username, password and session length


Pages: [1] 2   Go Down
  Print  
Author Topic: [Solved] M-Audio Transit USB Sound not working !!  (Read 1401 times)
charlescctdc
Jr. Member
**
Offline Offline

Posts: 10


« on: December 24, 2010, 08:19:24 AM »

Hi, I am a newbie on using Linux. I don't know anything about Linux but willing to learn. Recently I had installed PCLinuxOS on my computer a week ago, everything worked well except the followings occurred:
1) Computer freezes and need to re-boot after run Firefox about 5 minutes. (Now change to use 'Chromium')
2) Mouse control sometimes freezes and need to re-boot (may be after 10-15 minutes)
3) M-Audio Transit USB sound not working.

Regarding the M-Audio Transit USB, I had tried to search 'Madfuload' under Synaptic Package Manager, but no luck. I eventually searched 'Minisport' under Synaptic Package Manger and quickly to install this firmware. Then I choosed snd_usb_audio[ALSA] under Sound Configuration in Control Centre, but still no sound came out. I run the AlsaMixerGui and found out defalt card was still snd_atiiXP[ALSA]. Also, I found in the Minisport firmware list, none of Transit USB or Sonica listed. Afterwards, I searched some forums and alsa website and download the madfuload firmware. When I tried to install it under terminal, I had the following error came out from screen:

[root@localhost madfuload-1.2]# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for udev version... ./configure: line 2811: udevinfo: command not found
none
configure: error: udev version 057 or later is required
[root@localhost madfuload-1.2]#

Can anybody advise me how to solve the above-said problems?
Many many thanks for your help !!  Angry

 
 
Logged
menotu
PCLinuxOS Tester
Super Villain
*******
Offline Offline

Posts: 11988

┌∩┐(◕_◕)┌∩┐


« Reply #1 on: December 24, 2010, 09:03:00 AM »

Firstly, welcome to the forum charlescctdc  - nice to have you with us.

I hadn't heard of Madfuload but did a search in Synaptic and came across

madfu-firmware

so I'm unsure whether its of any use in your situation - it is described:

"Firmware loader for M-Audio/Midiman usb sound devices
This package allows you to use the USB Audio interfaces from M-Audio/
Midiman with Linux.  It sets up an hotplugging script to load the
firmware from the Windows driver files.

Firmware files are not distributed with this package but can be extracted
from the Windows drivers and placed in /usr/share/usb/maudio
."
Logged

If you can keep you head while all around you are losing theirs, then you have misunderstood the situation.

PCLinuxOS 32bit & 64bit; 3.2.17bfs kernel, KDE 4.8.3; nvidia 295.53, Athlon 64 X2 4200+; 4GB Ram; NVidia GeForce 8400GS 1GB; x.org 1.10.4 ; 500GB/320GB
charlescctdc
Jr. Member
**
Offline Offline

Posts: 10


« Reply #2 on: December 24, 2010, 09:55:49 AM »

Hi menotu, thanks for your prompt advice. I really appreciated. I followed your instruction and searched 'madfu-firmware' under Synaptic and actually I had installed already. I copied windows firmware for Transit (ma006100.bin)  into usr/shares/usb/maudio folder. Please advise me how to load this firmware and make it work. Once again, thanks for your helpful !!! Cheesy
Logged
charlescctdc
Jr. Member
**
Offline Offline

Posts: 10


« Reply #3 on: December 25, 2010, 08:13:44 AM »

Hi, can anybody sincerely give me some advice how to load the m-audio firmware and make the sound work? Thanks !
I had tried to amend the following 42-midisport-firmware.rules before, but not successful and no sound came out.

# midisport-firmware.rules - udev rules for loading firmware into MidiSport devices

# DEVPATH=="/*.0" selects interface 0 only
# (some udev versions don't work with ATTRS{bInterfaceNumber})

# MidiSport 2x2
ACTION=="add", SUBSYSTEM=="usb", DEVPATH=="/*.0", ENV{PRODUCT}=="763/1001/*", RUN+="/usr/sbin/fxload -s /usr/share/usb/maudio/MidiSportLoader.ihx -I /usr/share/usb/maudio/MidiSport2x2.ihx"
# MidiSport 1x1
ACTION=="add", SUBSYSTEM=="usb", DEVPATH=="/*.0", ENV{PRODUCT}=="763/1010/*", RUN+="/usr/sbin/fxload -s /usr/share/usb/maudio/MidiSportLoader.ihx -I /usr/share/usb/maudio/MidiSport1x1.ihx"
# KeyStation
ACTION=="add", SUBSYSTEM=="usb", DEVPATH=="/*.0", ENV{PRODUCT}=="763/1014/*", RUN+="/usr/sbin/fxload -s /usr/share/usb/maudio/MidiSportLoader.ihx -I /usr/share/usb/maudio/MidiSportKS.ihx"
# MidiSport 4x4
ACTION=="add", SUBSYSTEM=="usb", DEVPATH=="/*.0", ENV{PRODUCT}=="763/1020/*", RUN+="/usr/sbin/fxload -s /usr/share/usb/maudio/MidiSportLoader.ihx -I /usr/share/usb/maudio/MidiSport4x4.ihx"
# MidiSport 8x8
ACTION=="add", SUBSYSTEM=="usb", DEVPATH=="/*.0", ENV{PRODUCT}=="763/1031/110", RUN+="/usr/sbin/fxload -s /usr/share/usb/maudio/MidiSportLoader.ihx -I /usr/share/usb/maudio/MidiSport8x8-2.10.ihx"
ACTION=="add", SUBSYSTEM=="usb", DEVPATH=="/*.0", ENV{PRODUCT}=="763/1031/121", RUN+="/usr/sbin/fxload -s /usr/share/usb/maudio/MidiSportLoader.ihx -I /usr/share/usb/maudio/MidiSport8x8-2.21.ihx"
# Transit
ACTION=="add", SUBSYSTEM=="usb", DEVPATH=="/*.0", ENV{PRODUCT}=="0763/2806/*", RUN+="/usr/sbin/fxload -s /usr/share/usb/maudio/ma006100.bin -D $ENV{PRODUCT}"

# vim: ft=conf


I trusted I was done wrong ! Can anybody please tell me how to solve this and make the sound work?
Many many thanks to everybody. Cry
 
Logged
charlescctdc
Jr. Member
**
Offline Offline

Posts: 10


« Reply #4 on: December 29, 2010, 04:23:13 PM »

Hi, Are there any expert can help me solve the sound problem? Many many thanks !
Logged
Was_Just19
Hero Member
*****
Offline Offline

Posts: 6885


MLU


« Reply #5 on: December 29, 2010, 04:55:35 PM »

No expert here, but in the absence of anyone else .......

Plug in the device, in a terminal, do

lsusb

 and copy and paste the line that refers to your device from the output of the command.

Also while in the terminal, do

dmesg

and there should be a few lines at the end about the device, so copy and paste those also in your next post.

EDIT
          Forgot to ask ......  did you put the Windows firmware file from the accompanying CD into the correct directory for madu-firmware to find?

Wink
Logged
charlescctdc
Jr. Member
**
Offline Offline

Posts: 10


« Reply #6 on: December 29, 2010, 07:06:18 PM »

No expert here, but in the absence of anyone else .......

Plug in the device, in a terminal, do

lsusb

 and copy and paste the line that refers to your device from the output of the command.

Also while in the terminal, do

dmesg

and there should be a few lines at the end about the device, so copy and paste those also in your next post.

EDIT
          Forgot to ask ......  did you put the Windows firmware file from the accompanying CD into the correct directory for madu-firmware to find?

Wink

Hi Just19, Thank you so much for your prompt response! Hope this time my M-Audio Transit will work. Roll Eyes

[root@localhost ~]# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 148f:3070 Ralink Technology, Corp.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 004: ID 0763:2806 Midiman M-Audio Transit DFU
[root@localhost ~]#

Logged
Was_Just19
Hero Member
*****
Offline Offline

Posts: 6885


MLU


« Reply #7 on: December 29, 2010, 07:14:04 PM »

Quote
usb 3-1: new full speed USB device using ohci_hcd and address 4
usb 3-1: New USB device found, idVendor=0763, idProduct=2806
usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-1: Product: Unknown
usb 3-1: Manufacturer: Unknown

That is all I wanted ......  which should have been last from demsg if you had just plugged in the device as I said.

So have you put the Win firmware into the directory or not?
Logged
charlescctdc
Jr. Member
**
Offline Offline

Posts: 10


« Reply #8 on: December 29, 2010, 07:23:36 PM »

Quote
usb 3-1: new full speed USB device using ohci_hcd and address 4
usb 3-1: New USB device found, idVendor=0763, idProduct=2806
usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-1: Product: Unknown
usb 3-1: Manufacturer: Unknown

That is all I wanted ......  which should have been last from demsg if you had just plugged in the device as I said.

So have you put the Win firmware into the directory or not?


usb 3-1: new full speed USB device using ohci_hcd and address 4
usb 3-1: New USB device found, idVendor=0763, idProduct=2806
usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-1: Product: Unknown
usb 3-1: Manufacturer: Unknown

[root@localhost ~]#

I had the firmware 'ma006100.bin' and temporary put it into Download folder. Sorry I don't know how to load it into system via CLI. Please advise me how to do that. Thanks!
Logged
Was_Just19
Hero Member
*****
Offline Offline

Posts: 6885


MLU


« Reply #9 on: December 29, 2010, 07:29:22 PM »

EDIT:  Just copy the firmware file to the location specified .......  nothing else. Do it with a file manager.

Overview:

The way I *think* this should work for you.

After installing the madfu-firmware package in PCLOS, all you need to do after that is to copy the correct firmware file into  /usr/share/usb/maudio .....  may be named ma006100.bin or something similar.

Reboot the PC.

Thereafter, inserting the device should cause a script (which has been installed with the repository package) to run and enable your device.

You can check the output of

lsusb

again after that and the "DFU" should have disappeared from the output line, so it looks something like this

Code:
Bus 003 Device 004: ID 0763:2806 Midiman M-Audio Transit
Logged
charlescctdc
Jr. Member
**
Offline Offline

Posts: 10


« Reply #10 on: December 29, 2010, 07:39:53 PM »

EDIT:  Just copy the firmware file to the location specified .......  nothing else. Do it with a file manager.

Overview:

The way I *think* this should work for you.

After installing the madfu-firmware package in PCLOS, all you need to do after that is to copy the correct firmware file into  /usr/share/usb/maudio .....  may be named ma006100.bin or something similar.

Reboot the PC.

Thereafter, inserting the device should cause a script (which has been installed with the repository package) to run and enable your device.

You can check the output of

lsusb

again after that and the "DFU" should have disappeared from the output line, so it looks something like this

Code:
Bus 003 Device 004: ID 0763:2806 Midiman M-Audio Transit

Thank you so much! I try it now and let you know the result.
Logged
charlescctdc
Jr. Member
**
Offline Offline

Posts: 10


« Reply #11 on: December 29, 2010, 08:03:28 PM »

EDIT:  Just copy the firmware file to the location specified .......  nothing else. Do it with a file manager.

Overview:

The way I *think* this should work for you.

After installing the madfu-firmware package in PCLOS, all you need to do after that is to copy the correct firmware file into  /usr/share/usb/maudio .....  may be named ma006100.bin or something similar.

Reboot the PC.

Thereafter, inserting the device should cause a script (which has been installed with the repository package) to run and enable your device.

You can check the output of

lsusb

again after that and the "DFU" should have disappeared from the output line, so it looks something like this

Code:
Bus 003 Device 004: ID 0763:2806 Midiman M-Audio Transit

Hi Just19, I followed your instruction, install madfu-firmware package and copy the 'ma006100.bin' file into /usr/share/usb/maudio; then reboot and I still see the DFU shown on terminal.

[root@localhost ~]# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 148f:3070 Ralink Technology, Corp.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 0763:2806 Midiman M-Audio Transit DFU

Now, what should I do?
Logged
Was_Just19
Hero Member
*****
Offline Offline

Posts: 6885


MLU


« Reply #12 on: December 29, 2010, 08:16:53 PM »

That seems to imply that the script to insert the firmware was not run ......

Maybe try rebooting with the device inserted .......  or if that is what you did try taking it out and waiting a few seconds and reinserting it.

Try rebooting a couple of times to be sure.

If none of those work then we will have to see about running a suitable command to grab the firmware for the device.

You quoted earlier in the thread an excerpt which had such commands ........  you could try adding this one to those .......

Code:
# Transit
ACTION=="add", SUBSYSTEM=="usb", ENV{PRODUCT}=="763/2806/*", RUN+="/usr/sbin/madfuload -l -3 -f /usr/share/usb/maudio/ma006100.bin
-D $env{DEVNAME}"

If it doesn't work there then maybe creating a udev rule for it would be the best option ......  getting out of my depth here though ......

Try those options first.
The madfu-firmware package clearly says it sets up a hotplugging script to load the firmware you copied into the maudio directory. So it should work when you take out and put the device back in.   Huh
Logged
Was_Just19
Hero Member
*****
Offline Offline

Posts: 6885


MLU


« Reply #13 on: December 29, 2010, 08:33:42 PM »

I have taken a quick look through the udev rules that are on my install after installing the madfu-firmware package, and do not see one for it.
It may be elsewhere so if anyone has info about that hopefully they will post.

If none of the above get the device working I would be inclined to create a rule and then try again.

Using a text editor, create a file called

42-madfuload.rules

Into that file copy and paste the following

Code:
# Transit
ACTION=="add", SUBSYSTEM=="usb", ENV{PRODUCT}=="763/2806/*", RUN+="/usr/sbin/madfuload -l -3 -f /usr/share/usb/maudio/ma006100.bin
-D $env{DEVNAME}"

Please note ....  those are not all separate lines, so do a proper copy and paste to get it right.

Now copy, as root, that file into the following location

/lib/udev/rules.d/

Now when you insert the device, and run lsusb hopefully the firmware will have been loaded correctly.

I would still be concerned about the existence of the hotplugging script referenced in the info about the package.
Doing the above might just cause some conflicts .........

So if anyone can clarify the situation that would be good.

regards.
Logged
charlescctdc
Jr. Member
**
Offline Offline

Posts: 10


« Reply #14 on: December 29, 2010, 09:03:03 PM »

I have taken a quick look through the udev rules that are on my install after installing the madfu-firmware package, and do not see one for it.
It may be elsewhere so if anyone has info about that hopefully they will post.

If none of the above get the device working I would be inclined to create a rule and then try again.

Using a text editor, create a file called

42-madfuload.rules

Into that file copy and paste the following

Code:
# Transit
ACTION=="add", SUBSYSTEM=="usb", ENV{PRODUCT}=="763/2806/*", RUN+="/usr/sbin/madfuload -l -3 -f /usr/share/usb/maudio/ma006100.bin
-D $env{DEVNAME}"

Please note ....  those are not all separate lines, so do a proper copy and paste to get it right.

Now copy, as root, that file into the following location

/lib/udev/rules.d/

Now when you insert the device, and run lsusb hopefully the firmware will have been loaded correctly.

I would still be concerned about the existence of the hotplugging script referenced in the info about the package.
Doing the above might just cause some conflicts .........

So if anyone can clarify the situation that would be good.

regards.

Hi Just19, I created a 42-madfuload.rules and put it into /lib/udev/rules.d. Then check lsusb via terminal. Now the DFU is disappeared. What should I do now? I pick hardware - sound configuration via Administration Centre and choose snd_usb_audio[AlSA], then click 'advance' and I don't know which driver I had to choose. Please advise. Thanks
Logged
Pages: [1] 2   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.16 | SMF © 2011, Simple Machines

Valid XHTML 1.0! Valid CSS! Dilber MC Theme by HarzeM