Trisquel Netinstall: Sound issue
- Inicie sesión ou rexístrese para enviar comentarios
I managed to bind the volume keys, but not the mute key.
The volume is indicated as being muted, so that's the first hurdle.
I've read about xev, but the mute key isn't recognised.
Then I tried xmodmap -pke, which gave me this (supposedly unassigned key):
keycode 121 = XF86AudioMute NoSymbol XF86AudioMute.
To get around xev not recognizing the mute key (even though xmodmap says it's assigned somewhere),
I tried this:
in etc/defaults/grub, I changed
GRUB_CMDLINE_LINUX=""
to
GRUB_CMDLINE_LINUX="acpi_osi="Linux""
and updated grub with sudo update-grub.
No success.
I know I have Pulseaudio installed, but alsa isn't selected in synaptic.
I've read that it's supposed to be part of the kernel, so it should be there.
I might be missing drivers.
Still with the idea of keeping my system as lean as possible (even though it's an X200), what could I try now?
Is trisquel-base installed (I think that particular metapackage takes care of dragging sound packages towards being installed on your system)?
I have trisquel-base-data, but not trisquel-base. There is some alsa stuff inside (or as dependecies).
I suggest (well, recommend, really)installing trisquel-base (it's the cheapest, albeit a slightly inefficient in terms of number of packages installed, way to make sure things go well on the computer (i.e. Archive-opening, sound-playing, etc).
Or at least that's what I think of triaquel-base as.
Thanks again David.
I see. Archive opening is ok, I see that I have cron installed for example. By default I have some of them.
Maybe they were installed with other software.
I guess I have two choices: either install trisquel-base and risk to add a few stuff I won't use, or pick the dependencies one by one whenever I have an issue.
I guess it can't hurt to try that.
Or just go with it and install on the side "linux from scratch" or Archlinux to really understand how it works.
The problem is, the more I install, the riskier it is to remove core packages because of related dependencies.
Well hey, just for the sake of it, I'll install the alsa related stuff first (though Pulseaudio is supposed to take care of key interaction) and see how it goes.
"or pick the dependencies one by one whenever I have an issue." Even if you go down that route I doubt you'll really have to pick the dependencies one-by-one. It's won't be that hard :)
And rather than trying Arch I think you should try Parabola instead. It's Libre Arch, basically.
Oh yeah, Parabola, I forgot about it!
That would be a good learning project, on a virtual machine for example.
I installed alsa-base and alsa-base-utils,
and it didn't work.
I tried then trisquel-base.
It suggested posfix configuration during the install.
I don't want it so I close the window.
Seems like something got broken during the install (an alert message I fail to remember).
I tried the sound without success. Can't remember if I restarted the computer though.
So I removed the package with the same postfix thing.
Back to square one. I'll try configuring postfix, reboot and see how it goes.
I can always remove the package afterwards.
"It suggested posfix configuration during the install."
You could've just selected "No configuration".....now if I'm not mistaken that may have left quite a few packages unconfigured. You may end up getting asked to dosudo dpkg --configure -a by Synaptic/APT(in which case you should just do it and all should be well).
I installed, rebooted and uninstalled again (because xev still doesn't recognize the mute key).
there was some fail message at the start of the uninstall, but no postfix.
What I did was probably too brutal, but for now my system seems ok.
I know there is also a trisquel-recommended package that I could try.
I searxed more about mute key and X200.
I tried several variants of the grub modification above.
But I have no luck, it doesn't work for me.
What I don't understand though is that "keycode 121 = XF86AudioMute NoSymbol XF86AudioMute"
It means that the mute command is assigned to the key associated with keycode 121?
if I remove it from xmodmap, will it be recognized by xev?
Anyway, it seems it's more directly related to the X200.
I've read a solution about kernel update, but I shouldn't need that since the mute button worked in a full trisquel install.
Also when I go in proc/acpi/ibm/volume, mute is marked as "off"... I don't get it.
Ok quick recap:
The mute button worked in the Full Trisquel install.
The mute is marked as off in in proc/acpi/ibm/volume.
Thus some package might be missing.
And it's not trisquel-base.
EDIT
With the X200 on it's base (and the headphones on), I managed to toggle the mute key on my external keyboard, but not on the X200 itself.
xev shows the data of up down and mute on the external keyboard as serial 34, while up and down on the X200 are serial 33.
I tried the grub thing again with a slightly different syntax, and it seems to work ok, even without the headphones. I can only unmute with the volumeup key, but it's fine.
Here's what I did, might help someone else in my case:
in etc/defaults/grub:
instead of GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
I did
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=Linux".
Then sudo update-grub and reboot.
I've seen several syntax variations on other forums and websites. But this one worked for me.
- Inicie sesión ou rexístrese para enviar comentarios