hi
Can anyone tell
1) how device driver will be selected to the microphone on kernel.
2) what part of linux code will detect the usb devices and loads the device driver.
3) how to know whether the perticular microphone is supported by the kernel.
Thank u..
does a (strange unnamed) device appear in the lsusb listing at all, if you plug in just the mic? sometimes there is just an entry missing in the kernel id table and it can't print a name. it should always print the id and the device type, if not, the mic is not recognized as a valid usb device at all.
are mic and headphone one physical device? if so, the mic could 'hide' inside the headphone, i.e. the headphone device is bidirectional.
hi
Thank u for the reply.The device is not appearing in the lsusb.
Is the kernel id table you are reffering about is the usb.ids?
The mic and the headphone is on one physical device but microphone appears seperately on lsusb in other linux version(2.6.22)
ok, working on a later revision is an important information: so 2.6.10 is too old. as first thing you should scan the usb chapters of the changelogs of 2.6.11 to 2.6.22 if there is a relevant change (e.g. "microphone support" or "don't ignore second device"). to make this work simpler, you could bisect by trying 2.6.16 and so on. if you are lucky, you arrive at a backportable changeset. apart from the official changelogs you should also check the annotated changelogs on kernelnewbies.org .
Hi,
sorry i was wrong,the microphone will be listed in lsusb even in 2.6.10 same as it is listing in 2.6.22,,...but when i give arecord it gives : arecord: main:508: audio open error: No such file or directory.
So what may be the problem is it a problem of the usb.ids,device driver or the 2.6.10 kernel?
which 'file or directory' does arecord miss? why does it even try to open a non-existing file? you can use strace to find out.
what are your audio settings for arecord? do the needed devices exists in /dev ? do you have udev or is your kernel too old for this and you have to create devices with MAKEDEV or manually?
hi,
when we connect usb headset only /dev/dsp and /dev/dsp1 are created not the /dev/audio and /dev/audio1 which are created on mic detection..
So why is it?
/dev/audio* are just alternate format versions of /dev/dsp* (see devices.txt in Documentation directory), maybe the usb device doesn't support ancient 8 bit sample formats. under oss you play _and_ record via /dev/dsp*. which kernel driver (module) handles the usb sound of the headset and does it support the mic in 2.6.10? why can't you upgrade? why can't you change to maintained drivers and use alsa (and maybe aoss to be backwards compatible)?
Hi,
Thanks for the reply.
As you said,now linux 2.6.23 with ALSA SUPPORT IS USED.bUT WHEN inserting the module for usb detecion the kernel will stuck after detecting and reporting the information about the usb audio device.
Can you suggest any solution
usb mic device driver
hi
Can anyone tell
1) how device driver will be selected to the microphone on kernel.
2) what part of linux code will detect the usb devices and loads the device driver.
3) how to know whether the perticular microphone is supported by the kernel.
Thank u..
lsusb
does a (strange unnamed) device appear in the lsusb listing at all, if you plug in just the mic? sometimes there is just an entry missing in the kernel id table and it can't print a name. it should always print the id and the device type, if not, the mic is not recognized as a valid usb device at all.
are mic and headphone one physical device? if so, the mic could 'hide' inside the headphone, i.e. the headphone device is bidirectional.
id table
hi
Thank u for the reply.The device is not appearing in the lsusb.
Is the kernel id table you are reffering about is the usb.ids?
The mic and the headphone is on one physical device but microphone appears seperately on lsusb in other linux version(2.6.22)
12 steps
ok, working on a later revision is an important information: so 2.6.10 is too old. as first thing you should scan the usb chapters of the changelogs of 2.6.11 to 2.6.22 if there is a relevant change (e.g. "microphone support" or "don't ignore second device"). to make this work simpler, you could bisect by trying 2.6.16 and so on. if you are lucky, you arrive at a backportable changeset. apart from the official changelogs you should also check the annotated changelogs on kernelnewbies.org .
is your headset behind a hub?
usb mic
Hi,
sorry i was wrong,the microphone will be listed in lsusb even in 2.6.10 same as it is listing in 2.6.22,,...but when i give arecord it gives : arecord: main:508: audio open error: No such file or directory.
So what may be the problem is it a problem of the usb.ids,device driver or the 2.6.10 kernel?
which 'file or directory'
which 'file or directory' does arecord miss? why does it even try to open a non-existing file? you can use strace to find out.
what are your audio settings for arecord? do the needed devices exists in /dev ? do you have udev or is your kernel too old for this and you have to create devices with MAKEDEV or manually?
arecord
hi
@strcmp
I am working with OSS not ALSA.So arecord is not supported right?
/dev/audio
hi,
when we connect usb headset only /dev/dsp and /dev/dsp1 are created not the /dev/audio and /dev/audio1 which are created on mic detection..
So why is it?
don't know
/dev/audio* are just alternate format versions of /dev/dsp* (see devices.txt in Documentation directory), maybe the usb device doesn't support ancient 8 bit sample formats. under oss you play _and_ record via /dev/dsp*. which kernel driver (module) handles the usb sound of the headset and does it support the mic in 2.6.10? why can't you upgrade? why can't you change to maintained drivers and use alsa (and maybe aoss to be backwards compatible)?
usb device on linux 2.6.23
Hi,
Thanks for the reply.
As you said,now linux 2.6.23 with ALSA SUPPORT IS USED.bUT WHEN inserting the module for usb detecion the kernel will stuck after detecting and reporting the information about the usb audio device.
Can you suggest any solution