Results 1 to 9 of 9
I am not able to get the internal mic to work on my slackware x86_64 installation 13.37. (Works fine under the windoze partition.) Any Ideas? I have tried setting various ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 11-22-2011 #1Just Joined!
- Join Date
- Nov 2011
- Posts
- 4
Internal mic not working, thinkpad t520, cx20590
I am not able to get the internal mic to work on my slackware x86_64 installation 13.37. (Works fine under the windoze partition.) Any Ideas? I have tried setting various model=xxx parameters without success. Any pointers would be very helpful.
> lspci -v
00:1b.0 Audio device: Intel Corporation 6 Series Chipset Family High Definition Audio Controller (rev 04)
Subsystem: Lenovo Device 21cf
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at f3a20000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: HDA Intel
> cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.23.
> cat /proc/asound/pcm
00-00: CONEXANT Analog : CONEXANT Analog : playback 1 : capture 1
00-01: Conexant Digital : Conexant Digital : playback 1
> cat /proc/asound/cards
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf3a20000 irq 44
cat /proc/asound/PCH/pcm0c/info
card: 0
device: 0
subdevice: 0
stream: CAPTURE
id: CONEXANT Analog
name: CONEXANT Analog
subname: subdevice #0
class: 0
subclass: 0
subdevices_count: 1
subdevices_avail: 1
> cat /proc/asound/oss/sndstat
Sound Driver:3.8.1a-980706 (ALSA v1.0.23 emulation code)
Kernel: Linux meb-4506-01 2.6.37.6-k7 #5 SMP Mon Nov 14 11:46:37 MST 2011 x86_64
Config options: 0
Installed drivers:
Type 10: ALSA emulation
Card config:
HDA Intel PCH at 0xf3a20000 irq 44
Audio devices:
0: CONEXANT Analog (DUPLEX)
Synth devices: NOT ENABLED IN CONFIG
Midi devices: NOT ENABLED IN CONFIG
Timers:
31: system timer
Mixers:
0: Conexant CX20590
- 11-23-2011 #2
I don't run Slackware or your IBM laptop. Maybe My EEEPC mic fix I posted may give you some ideas. Maybe not.
I had to edit /var/lib/alsa/asound.state file to get mine to work. Thread I made below.
antiX-forum - View topic - eeepc 900 Microphone debian wheezy fix AntiX 11Linux Registered User # 475019
Lead,Follow, or get the heck out of the way
AntiX,Puppy,Windows 7=(cuz of scooters)
Free Linux Books
Free R Books
- 11-23-2011 #3Trusted Penguin
- Join Date
- May 2011
- Posts
- 3,663
Have you tried the alsamixer utility? You can adjust volume there - it is an ncurses-based app.
- 11-23-2011 #4Just Joined!
- Join Date
- Nov 2011
- Posts
- 4
Thanks rokytnji, but my cpature switch in asound.state is already true for both values (in control.5 for me). Here is the file:
state.PCH {
control.1 {
iface MIXER
name 'Master Playback Volume'
value.0 62
value.1 62
comment {
access 'read write'
type INTEGER
count 2
range '0 - 74'
dbmin -7400
dbmax 0
dbvalue.0 -1200
dbvalue.1 -1200
}
}
control.2 {
iface MIXER
name 'Master Playback Switch'
value true
comment {
access 'read write'
type BOOLEAN
count 1
}
}
control.3 {
iface MIXER
name 'Analog Mic Boost Capture Enum'
value '0dB'
comment {
access 'read write'
type ENUMERATED
count 1
item.0 '0dB'
item.1 '10dB'
item.2 '20dB'
item.3 '30dB'
item.4 '40dB'
}
}
control.4 {
iface MIXER
name 'Capture Volume'
value.0 80
value.1 80
comment {
access 'read write'
type INTEGER
count 2
range '0 - 80'
dbmin -7400
dbmax 600
dbvalue.0 600
dbvalue.1 600
}
}
control.5 {
iface MIXER
name 'Capture Switch'
value.0 true
value.1 true
comment {
access 'read write'
type BOOLEAN
count 2
}
}
control.6 {
iface MIXER
name 'IEC958 Playback Con Mask'
value '0fff000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 000'
comment {
access read
type IEC958
count 1
}
}
control.7 {
iface MIXER
name 'IEC958 Playback Pro Mask'
value '0f00000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 000'
comment {
access read
type IEC958
count 1
}
}
control.8 {
iface MIXER
name 'IEC958 Playback Default'
value '0449000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 000'
comment {
access 'read write'
type IEC958
count 1
}
}
control.9 {
iface MIXER
name 'IEC958 Playback Switch'
value false
comment {
access 'read write'
type BOOLEAN
count 1
}
}
control.10 {
iface MIXER
name 'IEC958 Default PCM Playback Switch'
value true
comment {
access 'read write'
type BOOLEAN
count 1
}
}
control.11 {
iface MIXER
name 'Capture Source'
value 'Mic B'
comment {
access 'read write'
type ENUMERATED
count 1
item.0 'Mic B'
item.1 'Mic C'
item.2 'Mic E'
item.3 'Mic F'
}
}
}
- 11-23-2011 #5
All I can say is did you look at my link in that thread I started pointing to how I got skype mic working in AntiX 8.5 and Puppy Linux. Over at the HardKap forum for Macpup. I'm kinda at a loss on what to do in Slackware for trouble shooting a mic as I have certain tools that you may not have or you may use different mic trouble shooting tools than I do.
Linux Registered User # 475019
Lead,Follow, or get the heck out of the way
AntiX,Puppy,Windows 7=(cuz of scooters)
Free Linux Books
Free R Books
- 11-23-2011 #6Just Joined!
- Join Date
- Nov 2011
- Posts
- 4
Yes I did. Thank you for the pointer.
In mulling this over more, there happens to be a mic mute button (as well as a speaker mute button) on the keyboard of the T520. The light doesn't toggle like on the speaker mute, so I'm wondering if the button configs are not set up right for this new thinkpad.
- 11-23-2011 #7You got me thinking with that. I got all my Hotkeys to work using eeepc-acpi-scripts from Debian Sid EEEPC repositories. I don't know if Slackware has a pre-built script for IBM acpi but it may be worth searching for on your end.so I'm wondering if the button configs are not set up right for this new thinkpad.
Edit: I find it funny that a Debian user like me is trying to help in Slackware when I have no clue on running it.
We need a Slackware user in this thread and I know some users here run Slackware.
If you get no joy here. Try linuxquestions.org. They are chock full of Slackware users there and have some pretty knowledgeable slackware gurus there, Hope I don't get into trouble recommending another forum but I wish to see you solve this problem. If they sort it out for you. Post a link to the thread here. I know you don't have enough posts yet to post a link. just put a space between h t t p in the link and it should past ok.Last edited by rokytnji; 11-24-2011 at 12:07 AM.
Linux Registered User # 475019
Lead,Follow, or get the heck out of the way
AntiX,Puppy,Windows 7=(cuz of scooters)
Free Linux Books
Free R Books
- 11-24-2011 #8Trusted Penguin
- Join Date
- May 2011
- Posts
- 3,663
Regarding the Function keys, is the machine dual-booted w/Windows? Sometimes people have had luck with this type of problem by temporarily going into Windows, where that Function works, toggling the setting, then rebooting into Windows.
I also had to install a special driver and app when I last tried to use them on a Thinkpad (T41 I think). You might be able to find something over at ThinkWiki.
- 11-25-2011 #9Just Joined!
- Join Date
- Nov 2011
- Posts
- 4
Hi everyone,
Thanks so much for the help and mindshare.
It turns out that this new hardware isn't fully supported yet by alsa version 1.0.23. I found some guys working on T520's with the alsa project, downloaded their latest development snapshot, that did the trick.
cheers -Ken


Reply With Quote

