Results 1 to 4 of 4
Hi Friends:
Thanks in advance for you help.
As the subject indicates, I purchased a P170HM laptop (made by Clevo), and installed
and patched Fedora 14 on it. Being a ...
- 02-09-2011 #1Just Joined!
- Join Date
- Jan 2009
- Posts
- 11
Can't see audio controllers(s) (Fedora 14 + Clevo P170HM laptop) ...
Hi Friends:
Thanks in advance for you help.
As the subject indicates, I purchased a P170HM laptop (made by Clevo), and installed
and patched Fedora 14 on it. Being a modern high end laptop, I have some work to do in
getting the necessary drivers for it (or configuring them properly for this laptop if they
already exist).
(Note: I already have Video working thanks to the nVidia packages in the yum repositories).
My issue here is Audio. Every the audio control applet whether in Gnome or Icewm,
indicate no audio device found. Similarly, on the command line, the output of aplay
indicates the same:
root# aplay -l
aplay: device_list:235: no soundcards found...
To help you help me, I attached a file to this post called "Sysinfo.txt.bz2", which has the
following output contained in it:
- lspci -v
- lsmod
- alsa-info
From the looks of it (in that file), there appears to be two Audio controllers in this
system, one from nVidia (unrelated to the nVidia Video Card), and one from Intel:
#########################################
!!Soundcards recognised by ALSA
!!-------------------------------------------------------------
0 [PCH ]: HDA-Intel - HDA Intel PCH
1 [NVidia ]: HDA-Intel - HDA NVidia
!!PCI Soundcards installed in the system
!!------------------------------------------------------------
00:1b.0 Audio device: Intel Corporation Cougar Point High Definition Audio Controller (rev 04)
01:00.1 Audio device: nVidia Corporation Device 0beb (rev a1)
##########################################
(Note: The attached file has much more information. Unfortunately I had to bzip2 compress
it due to forum restrictions).
For whatever it's worth, I compiled and installed the latest Realtek codec Linux drivers (from
RealTek site). I got that idea by booting to the Windows partition and seeing what the
Audio drivers there were (there were actually two: a ReakTek HD Audio driver, and a
Microsoft HD Audio driver). See second attachment if curious what Windows uses....
(P170HM_Windows7_SystemSummary_Output.txt.bz2).
So I'm not sure how to proceed. It appears first I have to determine what the Audio
controller is, and indeed if there are TWO as the above and attached seem to suggest,
which one to try to find drivers for and configure. For all I know, there may already be
proper drivers installed in this Fedora 14 O/S, and it's just a configuration issue.
But see attached. Any pointers / guidance would be appreciated.
Best regards & Thanks,
NYCeyes
- 02-09-2011 #2Just Joined!
- Join Date
- Jan 2009
- Posts
- 11
More specific information on these Audio devices...
Update ....
After performing an update-pciids(1), and then a lspci(1), the two audio devices are
more specifically divulged as:
00:1b.0 Audio device: Intel Corporation 6 Series Chipset Family High Definition Audio
Controller (rev 04)
01:00.1 Audio device: nVidia Corporation GF104 High Definition Audio Controller (rev a1)
- 02-09-2011 #3Just Joined!
- Join Date
- Jan 2009
- Posts
- 11
SOLVED: Can't see audio controller(s) (Fedora 14 + Clevo P170HM laptop
SOLVED:
It turned out to be two things:
(1) Of these packages alsa-plugins-pulseaudio, pulseaudio, pulseaudio-module-jack,
alsa-plugins-jack, jack-audio-connection-kit tuned", I was missing alsa-plugins-jack,
and pulseaudio-module-jack. This is significant because of HDMI and other available
outputs.
(2) I forgot to add myself to a few Audio related Unix groups. Do this with the following
command to add yourself (and reboot just to be sure):
su -c "usermod -aG pulse,pulse-access,jackuser,audio userName"
(or manually with vi(1) if you prefer).
Number (2) irritates me because I had solved that particular problem in December of
2009. Google this to find it: "PulseAudio volume works at runLevel5:
Because this laptop is quite new and high-end, I expected things to *not* work
... surely it had to be harder than that old solution
. It wasn't. Oh how we've come along
way with Linux and the ability to keep up with the newest hardware (thanks to dedicated
developers globally - thank you!).
- 02-09-2011 #4
Thanks for posting your solution, hopefully it will help others.
I do not respond to private messages asking for Linux help, Please keep it on the forums only.
All new users please read this.** Forum FAQS. ** Adopt an unanswered post.


Reply With Quote