Page 3 of 4
FujitsuS7020 working. How get the keyb soundControl working?
Posted: Wed 18 Mar 2009, 12:33
by jeffjeff
I've been tearing my hair about the sound. On a slightly different model I got the sound going with TeenPup just using the Audio Wizard (though I had to try a couple variant).
On this model, S7020, I tried older and 2008 Teenpup without success. The master control in the mixer would be locked at the bottom.Tried 2.15 CE, Pup 3, pup 4 without getting it working. (Though I must admit I didn't check then to see if the headphone output may have been working in spite of no loudspeaker sound)
After read this thread, i checked the hardware: realtek ALC260 and then I added an option model=fujitsu and now it is working with Puppy 4.1.12. At first I just got sound on the headphones output. The mixers are a bit odd.
With sgmixer the control "phone out" actually controls the speaker. and pcm2 controls the headphones.
With the AlsaMixer one had to "scroll" to the right quite a ways before seeing "speaker". It is rather unusual that the headphone doesn't cut out the speakers, they can be modified independently.
Anyone know a way to get the Keyboard controls to influence the sound? Like [Fn]+[F9] = raise volume, etc.
Posted: Wed 18 Mar 2009, 13:29
by mikeb
Anyone know a way to get the Keyboard controls to influence the sound? Like [Fn]+[F9] = raise volume, etc.
xbindkeys works a treat...one binary and a config file and pretty simple to set up.(not worth using the gui). Then use it in conjunction with a little script or directly to set volumes via say setvol command.
setvol
http://hocwp.free.fr/xbindkeys/xbindkeys.html
With the AlsaMixer one had to "scroll" to the right quite a ways before seeing "speaker". It is rather unusual that the headphone doesn't cut out the speakers, they can be modified independently.
when we eventually get an alsa update a card here does the same thing...odd ... could use xbindkeys for mute and restore speaker volume...there is probably a way of detecting headphones inserted via /proc/asound...... try cat /proc/asound... various files to test.
regards
mike
Posted: Wed 18 Mar 2009, 15:18
by rjbrewer
Jeffjeff
A few mentions of fujitsu sound here:
http://tilos.csl.mech.ntua.gr/~apoikos/s7020.html
rjb
Posted: Wed 18 Mar 2009, 15:19
by tempestuous
jeffjeff wrote:Anyone know a way to get the Keyboard controls to influence the sound? Like [Fn]+[F9] = raise volume, etc.
The current convention is to use the "acpid" daemon. This certainly works with the Asus Eee. See "Hotkeys on all ASUS Eee models"
http://www.murga-linux.com/puppy/viewto ... 744#237744
You will see that the situation with the Eee is similar to your Fujitsu -
Fn+F8: Decrease Volume Level
Fn+F9: Increase Volume Level
mikeb wrote:set volumes via say setvol command
The acpid people suggest using the standard ALSA utility; amixer.
First check that amixer works by trying this command to decrease volume -
and this command to increase volume -
If it works, then you can go ahead and install one of my "acpid-Eee-*" dotpets - all 3 are identical regarding the amixer commands.
Once the dotpet is installed, start the acpid daemon -
If the F8 and F9 keys don't work at this point, it may be necessary to also load the "fujitsu-laptop" module -
I think this passes keycode events to a config file which can be read by acpid.
Now try the F8 and F9 keys again.
Posted: Wed 18 Mar 2009, 16:13
by mikeb
The current convention is to use the "acpid" daemon. This certainly works with the Asus Eee.
Well that's handy though xbindkeys is pretty useful for more general uses such as getting multimedia keys working.
I've been working on a HP2133 ...good machine but hardware control is more manual (plus I managed to wipe the suse install with puppy install but no hard feelings and they were using a 2.6.18 kernel)
The backlight keys still work but not sure how...
anyway drifting off topic
regards
mike
Posted: Fri 07 Aug 2009, 21:36
by mikeb
Alsa 1.0.20 for standard and retro puppies...should be a great help
http://www.murga-linux.com/puppy/viewto ... 132#330132
mike
internal microphone doesn't work, external does. Why?
Posted: Wed 09 Sep 2009, 03:00
by stevesr0
I have a Fujitsu convertible laptop (model T4220), which has two internal microphones.
These don't work under Puppy (4.2.1 frugal install). I attached a USB webcam w microphone (Logitech Quickcam for notebooks). The video worked, but not the audio. I installed the 1.0.20 version of Alsa, but haven't been able to adjust the settings to enable the internal microphone.
I attached a microphone to the external microphone connection and that works.
This seems rather strange.
Appreciate suggestions and comments.
Steve
Followup to my last post
Posted: Sat 12 Sep 2009, 02:21
by stevesr0
Purchased a Syba webcam (model CL-MG-MC-BK) at Outlet PC), after seeing a recommendation on a Puppy Linux forum thread about which webcam to use.
I just plugged this in the USB port (as I had with the Logitech I tried previously and when I did a test call with Skype, both sound and audio immediately worked.
In the audio section of Skype's options, there were two choices for Venus (I assume this is the Syba Webcam driver), but the hdwr intel was selected and I didn't change this.
I am not sure if somehow I made some change in the ALSA settings since last trying the Logitech (and the sound input is actually from the internal microphone), but I don't care at this moment.
Steve
Posted: Sat 12 Sep 2009, 02:36
by mikeb
I thought I had replied...was when the forum was acting up...
the space bar selects inputs in alsamixer...just for reference.
mike
Why won't logitech's USB microphone work, when Syba's will?
Posted: Thu 17 Sep 2009, 01:42
by stevesr0
As I posted previously, a logitech quickcam for notebooks audio didn't work (under Skype) with this laptop with Intel HD audio. However, with another brand of webcam, the builtin USB microphone worked immediately.
I thought the microphone issue was related to the intel hd linux driver, which should be the same with different USB microphones plugged into the same port, no?
Appreciate suggestions about checking out why the other one didn't work and this one does.
Thanks.
Steve
Posted: Sun 25 Oct 2009, 14:28
by tempestuous
Puppy's version of ALSA has changed several times since this thread was started in October 2007.
Puppy 4.3 now has ALSA ver 1.0.20.
Shortly I will update the options now available for the snd-hda-intel ALSA 1.0.20 driver.
While browsing the ALSA documentation, I saw some options relating specifically to ASUS Eee models, which might solve the Eee audio problems reported on the forum recently:
eeepc-p703 ASUS Eeepc P703 P900A
eeepc-p901 ASUS Eeepc P901 S101
eeepc-p701 ASUS Eeepc P701
eeepc-ep20 ASUS Eeepc EP20
For example, with the Eee 900A you would add this line to /etc/modprobe.conf
Code: Select all
options snd-hda-intel model=eeepc-p703
then reboot.
Oh, and for the Acer Aspire One -
acer-aspire
Posted: Sun 25 Oct 2009, 15:03
by scabz
hey i added this line to modprobe.conf
Code: Select all
options snd-hda-intel model=eeepc-p703
and then i rebooted.
It did not work same problems.
EeePC 900a
Posted: Sun 25 Oct 2009, 18:39
by Flash
Here's the block diagram of my Gigabyte motherboard. Do you think I'll ever be able to get the sound to go through the HDMI cable? I can't see how it could be done, but it works in Windows, with the drivers that came with the Gigabyte board.
options snd-hda-intel model=eeepc-p901
Posted: Sun 25 Oct 2009, 20:59
by mawebb88
scabz wrote:hey i added this line to modprobe.conf
Code: Select all
options snd-hda-intel model=eeepc-p703
and then i rebooted.
It did not work same problems.
EeePC 900a
Same for me i.e. no change to the audio problem when i added the 901 bit:
Code: Select all
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF version 1.0.20 ---
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
# --- END: Generated by ALSACONF, do not edit. ---
options snd-hda-intel model=eeepc-p901
Anyone known where can I get the downgrade pet to that in 412 (v1.0.18 I think) which works fine
Rgds Mike
EeePC901
Posted: Mon 26 Oct 2009, 01:37
by tempestuous
Flash, I just made a post about HDMI audio in your original thread on this subject -
http://www.murga-linux.com/puppy/viewto ... 763#354763
Posted: Mon 26 Oct 2009, 03:46
by Flash
Thanks! I replied to your post in that thread.
Posted: Sat 10 Apr 2010, 20:38
by arslan79
tempestuous wrote:Puppy's version of ALSA has changed several times since this thread was started in October 2007.
Puppy 4.3 now has ALSA ver 1.0.20.
Shortly I will update the options now available for the snd-hda-intel ALSA 1.0.20 driver.
While browsing the ALSA documentation, I saw some options relating specifically to ASUS Eee models, which might solve the Eee audio problems reported on the forum recently:
eeepc-p703 ASUS Eeepc P703 P900A
eeepc-p901 ASUS Eeepc P901 S101
eeepc-p701 ASUS Eeepc P701
eeepc-ep20 ASUS Eeepc EP20
For example, with the Eee 900A you would add this line to /etc/modprobe.conf
Code: Select all
options snd-hda-intel model=eeepc-p703
then reboot.
Oh, and for the Acer Aspire One -
acer-aspire
Hi, I have acer aspire one 110, and I did all that you posted here. New parameters appeared in alsaconf. So how should I set it up??? The external|internal mic doesnt work anyway (((((((( Pls help!
alsaconf -m
Posted: Sun 15 May 2011, 06:34
by cwisefool
I realize this post is about 6 years later than original -- but this is one of the first topic posts that I found in my search -- and it provided almost 100% of what I needed to get my sound working! After adding model=acer to /etc/modprobe.d/alsa.conf (I guess location changed for puppy 5.2.5, which I am running) I still wasn't having working sound -- but I then rebooted and typed in alsaconf -m, went through alsaconf install and behold -- I heard the elusive barking sound -- now sound is working fine. Just posting this in case the same extra step will help anyone else get their sound working. Thanks to original poster for taking me 90% of the way there!
Re: alsaconf -m
Posted: Sun 29 May 2011, 18:31
by playdayz
Nevermind,. I was wrong.
Posted: Sun 06 Nov 2011, 20:05
by kpfuser
I tried to edit the modprobe.conf file as per the first post of this thread. The particulars of my system are as follows:
Laptop: ASUS X42J Series
Soundcard: Intel Corporation Ibex Peak High Definition Audio (rev 06) - as per alsaconf
Codec: Realtek ALC259
Unfortunately this codec is not mentioned in the first post of this thread.
Doing a search for model parameters for this codec unearthed the post
http://forums.fedoraforum.org/showthread.php?t=259791
where the suggested line to add to modprobe.conf is
options snd-hda-intel model=auto position_fix=0
I tried it and had partial success, that is sound comes through the laptop's speakers but not through the headphones. At the same time, the retrovol full window displays just five fields, i.e., Master, PCM, Speaker, Capture, and Mic Boost. Of these, only Master, Speaker, and Capture come up with a small selection box where a check mark can be placed. The PCM and Mic Boost fields have no such box, i.e., they cannot be selected. Is there some way I can get sound through the headphones?
A rather unusual feature of this laptop is that it has a single jack for headphones and microphone. If it runs the pre-installed Windows 7, once a device is plugged into this single jack, a window pops up asking you to state whether the device you plugged is headphones or a microphone. Could this provide some clue as to why no sound comes through the headphones?