Tony Baldwin wrote:
> What do I do, put this somewhere in /boot/grub/grub.cfg, or
> /etc/default/grub
if you put it in /etc/default/grub you need to update /boot/grub/grub.cfg
try first /boot/grub/grub.cfg and then make it permanent for future grub
updates via /etc/default/grub
On 11/13/2016 02:50 PM, deloptes wrote:
Anthony Baldwin wrote:
Definitely not a new chip...I built this machine in 2010, and It didn't
have such problems with lenny, squeeze, or wheezy, just now with jessie,
probably another thing systemd screwed up? Sorry for top posting but the
gmx web
Anthony Baldwin wrote:
>
> Definitely not a new chip...I built this machine in 2010, and It didn't
> have such problems with lenny, squeeze, or wheezy, just now with jessie,
> probably another thing systemd screwed up? Sorry for top posting but the
> gmx web mail isn' t letting me write beneath
...When did "stable" stop meaning "stable" and start meaning
"useless"?
Tony
Sent: Sunday, November 13, 2016 at 3:11 PM
From: deloptes <delop...@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: Not Resolved: no sound again!
Anthony Baldwin wrote:
>
Anthony Baldwin wrote:
> This is the third time within the space of only two weeks, where one day
> I'm happily listening to music on my machine one day. then I wake up the
> next and there's no sound!
> Neither pavucontrol or alsamixer show anything muted.
> Last it seems a reboot (after
This is the third time within the space of only two weeks, where one day
I'm happily listening to music on my machine one day. then I wake up the
next and there's no sound!
Neither pavucontrol or alsamixer show anything muted.
Last it seems a reboot (after successfully trying and succeeding to
6 matches
Mail list logo
