ASUS X205T

Need help with peripherals or devices?
Post Reply
Message
Author
abraham111
Posts: 9
Joined: 2020-11-25 21:14

ASUS X205T

#1 Post by abraham111 »

Hello

I recently installed Debian on my Asus x205t and are enjoying it a lot so far but there's only one remaining problem (after following the instructions on the wifi and working seemlessly). I need to fix my audio drivers and I've already installed Pulse Audio and Alsa but it didn't seem to fix the problem. Right now I have only dummy output in the audio options in pauvcontrol graphic version, and different outputs that freezes youtube unless I put it on off.

Is there a new solutions that isn't outdated and can you guys help me fix this issue. Because I would be very pleased with my new Debian OS if just the sound worked so I can participate in seminaries and conference calls online.

Right now there's a lot of solutions on the forums that are outdated, if anyone can provide a solution and an active link for i386 processor Asus x205t that would be apprieciated.

I really love the debian experience and would really like to see a solution to this!
Inxi:

System:
Host: localhost Kernel: 4.19.0-12-686-pae i686 bits: 32 compiler: gcc
v: 8.3.0 Desktop: Xfce 4.12.4 tk: Gtk 2.24.32 info: xfce4-panel wm: xfwm4
dm: LightDM 1.26.0 Distro: Debian GNU/Linux 10 (buster)
Machine:
Type: Laptop System: ASUSTeK product: X205TA v: 1.0 serial: <filter>
Mobo: ASUSTeK model: X205TA v: 1.0 serial: <filter>
UEFI: American Megatrends v: X205TA.208 date: 12/18/2014
Battery:
ID-1: BATC charge: 5.2 Wh condition: 30.3/38.0 Wh (80%) volts: 8.2/7.6
model: Intel SR 1 SR Real Battery type: Li-ion serial: <filter>
status: Charging cycles: 455
CPU:
Topology: Quad Core model: Intel Atom Z3735F bits: 64 type: MCP
arch: Silvermont rev: 8 L1 cache: 224 KiB L2 cache: 1024 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 10662
Speed: 500 MHz min/max: 500/1833 MHz Core speeds (MHz): 1: 500 2: 500
3: 620 4: 558
Graphics:
Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display
vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0f31
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel Bay Trail x86/MMX/SSE2 v: 4.2 Mesa 18.3.6
compat-v: 3.0 direct render: Yes
Audio:
Device-1: Intel HDMI/DP LPE Audio driver: HdmiLpeAudio
message: bus/chip ids unavailable
Device-2: chtrt5645 driver: chtrt5645 message: bus/chip ids unavailable
Sound Server: ALSA v: k4.19.0-12-686-pae
Network:
Message: No Device data found.
IF-ID-1: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 29.12 GiB used: 3.80 GiB (13.1%)
ID-1: /dev/mmcblk1 model: SDW32G size: 29.12 GiB serial: <filter> rev: 0x7
scheme: GPT
Partition:
ID-1: / size: 26.14 GiB used: 3.80 GiB (14.5%) fs: ext4
dev: /dev/mmcblk1p2
ID-2: swap-1 size: 1.94 GiB used: 0 KiB (0.0%) fs: swap
dev: /dev/mmcblk1p3
Sensors:
System Temperatures: cpu: 6280.0 C mobo: N/A
Fan Speeds (RPM): cpu: 0
Info:
Processes: 152 Uptime: 16m Memory: 1.87 GiB used: 534.6 MiB (28.0%)
Init: systemd v: 241 runlevel: 5 Compilers: gcc: N/A Shell: bash (su)
v: 5.0.3 running in: xfce4-terminal inxi: 3.0.32

Last edited by abraham111 on 2020-11-26 12:09, edited 1 time in total.

User avatar
stevepusser
Posts: 12430
Joined: 2009-10-06 05:53
Has thanked: 8 times
Been thanked: 6 times

Re: ASUS X205T

#2 Post by stevepusser »

When you post a hardware related question, could you provide as much information on the hardware as possible in a concise manner? One of the best ways is to install the inxi package and give us the output of this command in code tags here:

Code: Select all

inxi -Fxxxz
MX Linux packager and developer

abraham111
Posts: 9
Joined: 2020-11-25 21:14

Re: ASUS X205T

#3 Post by abraham111 »

stevepusser wrote:When you post a hardware related question, could you provide as much information on the hardware as possible in a concise manner? One of the best ways is to install the inxi package and give us the output of this command in code tags here:

Code: Select all

inxi -Fxxxz
root@localhost:/tmp# apt-get install inxi
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package inxi

Is there an alternate way (I got the same problem with snaps)?

User avatar
sunrat
Global Moderator
Global Moderator
Posts: 3749
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 3 times
Been thanked: 11 times

Re: ASUS X205T

#4 Post by sunrat »

You have more problems than just sound if you can't install a package with apt. Post the output of

Code: Select all

apt policy
We went through a similar sound issue a few days ago in http://forums.debian.net/viewtopic.php?f=7&t=148054
The OP didn't get it sorted there but I suspect it was because he didn't follow advice correctly or supply requested information. The steps advised are a logical way to diagnose and correct sound problems.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

abraham111
Posts: 9
Joined: 2020-11-25 21:14

Re: ASUS X205T

#5 Post by abraham111 »

sunrat wrote:You have more problems than just sound if you can't install a package with apt. Post the output of

Code: Select all

apt policy
We went through a similar sound issue a few days ago in http://forums.debian.net/viewtopic.php?f=7&t=148054
The OP didn't get it sorted there but I suspect it was because he didn't follow advice correctly or supply requested information. The steps advised are a logical way to diagnose and correct sound problems.
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://security.debian.org/debian-security buster/updates/main i386 Packages
release v=10,o=Debian,a=stable,n=buster,l=Debian-Security,c=main,b=i386
origin security.debian.org
Pinned packages:

User avatar
sunrat
Global Moderator
Global Moderator
Posts: 3749
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 3 times
Been thanked: 11 times

Re: ASUS X205T

#6 Post by sunrat »

abraham111 wrote:
sunrat wrote:You have more problems than just sound if you can't install a package with apt. Post the output of

Code: Select all

apt policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://security.debian.org/debian-security buster/updates/main i386 Packages
release v=10,o=Debian,a=stable,n=buster,l=Debian-Security,c=main,b=i386
origin security.debian.org
Pinned packages:
You don't have the main repo active which is why you can't install anything. Look for "Sources list" in the wiki and follow instructions to edit and correct your sources.list file as shown in the example.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

abraham111
Posts: 9
Joined: 2020-11-25 21:14

Re: ASUS X205T

#7 Post by abraham111 »

sunrat wrote:
abraham111 wrote:
sunrat wrote:You have more problems than just sound if you can't install a package with apt. Post the output of

Code: Select all

apt policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://security.debian.org/debian-security buster/updates/main i386 Packages
release v=10,o=Debian,a=stable,n=buster,l=Debian-Security,c=main,b=i386
origin security.debian.org
Pinned packages:
You don't have the main repo active which is why you can't install anything. Look for "Sources list" in the wiki and follow instructions to edit and correct your sources.list file as shown in the example.
Hello

Ok, so I followed your instructions btw this is a good video explaining how you will do it correctly (step-by-step): https://www.youtube.com/watch?v=CjFL5td27ls

Go to example sources.list and copy the non-free one after the few steps in terminal.
Go to terminal:

su
nano /etc/apt/sources.list

Enter the following (as can be seen in wiki):

deb http://deb.debian.org/debian buster main contrib non-free
deb-src http://deb.debian.org/debian buster main contrib non-free

deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free
deb-src http://deb.debian.org/debian-security/ buster/updates main contrib non-free

deb http://deb.debian.org/debian buster-updates main contrib non-free
deb-src http://deb.debian.org/debian buster-updates main contrib non-free

Control + 0 and Enter, then Ctrl + x to exit.

Type clear and then apt-get update while still in terminal.

lsb_release -a

Check the correct version is installed.

apt-get dist-upgrade

apt-get install sudo

Now we can install inxi (still in terminal):

apt-get install inxi
Done!
Last edited by abraham111 on 2020-11-26 12:15, edited 1 time in total.

abraham111
Posts: 9
Joined: 2020-11-25 21:14

Re: ASUS X205T

#8 Post by abraham111 »

stevepusser wrote:When you post a hardware related question, could you provide as much information on the hardware as possible in a concise manner? One of the best ways is to install the inxi package and give us the output of this command in code tags here:

Code: Select all

inxi -Fxxxz
InxI (inxi -Fxxxz):

System:
Host: localhost Kernel: 4.19.0-12-686-pae i686 bits: 32 compiler: gcc
v: 8.3.0 Desktop: Xfce 4.12.4 tk: Gtk 2.24.32 info: xfce4-panel wm: xfwm4
dm: LightDM 1.26.0 Distro: Debian GNU/Linux 10 (buster)
Machine:
Type: Laptop System: ASUSTeK product: X205TA v: 1.0 serial: <filter>
Mobo: ASUSTeK model: X205TA v: 1.0 serial: <filter>
UEFI: American Megatrends v: X205TA.208 date: 12/18/2014
Battery:
ID-1: BATC charge: 5.2 Wh condition: 30.3/38.0 Wh (80%) volts: 8.2/7.6
model: Intel SR 1 SR Real Battery type: Li-ion serial: <filter>
status: Charging cycles: 455
CPU:
Topology: Quad Core model: Intel Atom Z3735F bits: 64 type: MCP
arch: Silvermont rev: 8 L1 cache: 224 KiB L2 cache: 1024 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 10662
Speed: 500 MHz min/max: 500/1833 MHz Core speeds (MHz): 1: 500 2: 500
3: 620 4: 558
Graphics:
Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display
vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0f31
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel Bay Trail x86/MMX/SSE2 v: 4.2 Mesa 18.3.6
compat-v: 3.0 direct render: Yes
Audio:
Device-1: Intel HDMI/DP LPE Audio driver: HdmiLpeAudio
message: bus/chip ids unavailable
Device-2: chtrt5645 driver: chtrt5645 message: bus/chip ids unavailable
Sound Server: ALSA v: k4.19.0-12-686-pae
Network:
Message: No Device data found.
IF-ID-1: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 29.12 GiB used: 3.80 GiB (13.1%)
ID-1: /dev/mmcblk1 model: SDW32G size: 29.12 GiB serial: <filter> rev: 0x7
scheme: GPT
Partition:
ID-1: / size: 26.14 GiB used: 3.80 GiB (14.5%) fs: ext4
dev: /dev/mmcblk1p2
ID-2: swap-1 size: 1.94 GiB used: 0 KiB (0.0%) fs: swap
dev: /dev/mmcblk1p3
Sensors:
System Temperatures: cpu: 6280.0 C mobo: N/A
Fan Speeds (RPM): cpu: 0
Info:
Processes: 152 Uptime: 16m Memory: 1.87 GiB used: 534.6 MiB (28.0%)
Init: systemd v: 241 runlevel: 5 Compilers: gcc: N/A Shell: bash (su)
v: 5.0.3 running in: xfce4-terminal inxi: 3.0.32


abraham111
Posts: 9
Joined: 2020-11-25 21:14

Re: ASUS X205T

#9 Post by abraham111 »

Now you can also install snapd and snap-store:

And the app can be found here and dragged to the shortcut-bar:

/var/lib/snapd/desktop/applications

Image

User avatar
stevepusser
Posts: 12430
Joined: 2009-10-06 05:53
Has thanked: 8 times
Been thanked: 6 times

Re: ASUS X205T

#10 Post by stevepusser »

Your machine dates back to 2014, so I don't believe it requires any extra firmware for sound, unlike more recent Intel chipsets. You could install firmware-misc-nonfree just to check--it won't hurt anything to do so, or to remove it afterwards.

You should install spectre-meltdown-checker and intel-microcode, then run spectre-meltdown-checker as root or with sudo to check for any open security holes.
MX Linux packager and developer

abraham111
Posts: 9
Joined: 2020-11-25 21:14

Re: ASUS X205T

#11 Post by abraham111 »

stevepusser wrote:Your machine dates back to 2014, so I don't believe it requires any extra firmware for sound, unlike more recent Intel chipsets. You could install firmware-misc-nonfree just to check--it won't hurt anything to do so, or to remove it afterwards.

You should install spectre-meltdown-checker and intel-microcode, then run spectre-meltdown-checker as root or with sudo to check for any open security holes.
abraham@localhost:~$ sudo spectre-meltdown-checker
Spectre and Meltdown mitigation detection tool v0.42

Checking for vulnerabilities on current system
Kernel is Linux 4.19.0-12-686-pae #1 SMP Debian 4.19.152-1 (2020-10-18) i686
CPU is Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz

Hardware check
* Hardware support (CPU microcode) for mitigation techniques
* Indirect Branch Restricted Speculation (IBRS)
* SPEC_CTRL MSR is available: NO
* CPU indicates IBRS capability: NO
* Indirect Branch Prediction Barrier (IBPB)
* PRED_CMD MSR is available: NO
* CPU indicates IBPB capability: NO
* Single Thread Indirect Branch Predictors (STIBP)
* SPEC_CTRL MSR is available: NO
* CPU indicates STIBP capability: NO
* Speculative Store Bypass Disable (SSBD)
* CPU indicates SSBD capability: NO
* L1 data cache invalidation
* FLUSH_CMD MSR is available: NO
* CPU indicates L1D flush capability: NO
* Microarchitecture Data Sampling
* VERW instruction is available: NO
* Enhanced IBRS (IBRS_ALL)
* CPU indicates ARCH_CAPABILITIES MSR availability: NO
* ARCH_CAPABILITIES MSR advertises IBRS_ALL capability: NO
* CPU explicitly indicates not being vulnerable to Meltdown/L1TF (RDCL_NO): NO
* CPU explicitly indicates not being vulnerable to Variant 4 (SSB_NO): NO
* CPU/Hypervisor indicates L1D flushing is not necessary on this system: NO
* Hypervisor indicates host CPU might be vulnerable to RSB underflow (RSBA): NO
* CPU explicitly indicates not being vulnerable to Microarchitectural Data Sampling (MDS_NO): NO
* CPU supports Software Guard Extensions (SGX): NO
* CPU microcode is known to cause stability problems: NO (model 0x37 family 0x6 stepping 0x8 ucode 0x829 cpuid 0x30678)
* CPU microcode is the latest known available version: NO (latest version is 0x838 dated 2019/04/22 according to builtin MCExtractor DB v111 - 2019/05/18)
* CPU vulnerability to the speculative execution attack variants
* Vulnerable to CVE-2017-5753 (Spectre Variant 1, bounds check bypass): YES
* Vulnerable to CVE-2017-5715 (Spectre Variant 2, branch target injection): YES
* Vulnerable to CVE-2017-5754 (Variant 3, Meltdown, rogue data cache load): YES
* Vulnerable to CVE-2018-3640 (Variant 3a, rogue system register read): YES
* Vulnerable to CVE-2018-3639 (Variant 4, speculative store bypass): NO
* Vulnerable to CVE-2018-3615 (Foreshadow (SGX), L1 terminal fault): NO
* Vulnerable to CVE-2018-3620 (Foreshadow-NG (OS), L1 terminal fault): NO
* Vulnerable to CVE-2018-3646 (Foreshadow-NG (VMM), L1 terminal fault): NO
* Vulnerable to CVE-2018-12126 (Fallout, microarchitectural store buffer data sampling (MSBDS)): YES
* Vulnerable to CVE-2018-12130 (ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)): YES
* Vulnerable to CVE-2018-12127 (RIDL, microarchitectural load port data sampling (MLPDS)): YES
* Vulnerable to CVE-2019-11091 (RIDL, microarchitectural data sampling uncacheable memory (MDSUM)): YES

CVE-2017-5753 aka 'Spectre Variant 1, bounds check bypass'
* Mitigated according to the /sys interface: YES (Mitigation: usercopy/swapgs barriers and __user pointer sanitization)
* Kernel has array_index_mask_nospec: UNKNOWN (couldn't check (missing 'readelf' tool, please install it, usually it's in the 'binutils' package))
* Kernel has the Red Hat/Ubuntu patch: UNKNOWN (missing 'strings' tool, please install it, usually it's in the binutils package)
* Kernel has mask_nospec64 (arm64): UNKNOWN (couldn't check (missing 'readelf' tool, please install it, usually it's in the 'binutils' package))
* Checking count of LFENCE instructions following a jump in kernel... UNKNOWN (couldn't check (missing 'readelf' tool, please install it, usually it's in the 'binutils' package))
> STATUS: NOT VULNERABLE (Mitigation: usercopy/swapgs barriers and __user pointer sanitization)

CVE-2017-5715 aka 'Spectre Variant 2, branch target injection'
* Mitigated according to the /sys interface: YES (Mitigation: Full generic retpoline, STIBP: disabled, RSB filling)
* Mitigation 1
* Kernel is compiled with IBRS support: YES
* IBRS enabled and active: NO
* Kernel is compiled with IBPB support: UNKNOWN (in offline mode, we need the kernel image to be able to tell)
* IBPB enabled and active: NO
* Mitigation 2
* Kernel has branch predictor hardening (arm): NO
* Kernel compiled with retpoline option: YES
* Kernel compiled with a retpoline-aware compiler: YES (kernel reports full retpoline compilation)
> STATUS: NOT VULNERABLE (Full retpoline is mitigating the vulnerability)
IBPB is considered as a good addition to retpoline for Variant 2 mitigation, but your CPU microcode doesn't support it

CVE-2017-5754 aka 'Variant 3, Meltdown, rogue data cache load'
* Mitigated according to the /sys interface: YES (Mitigation: PTI)
* Kernel supports Page Table Isolation (PTI): YES
* PTI enabled and active: YES
* Reduced performance impact of PTI: NO (PCID/INVPCID not supported, performance impact of PTI will be significant)
* Running as a Xen PV DomU: NO
> STATUS: NOT VULNERABLE (Mitigation: PTI)

CVE-2018-3640 aka 'Variant 3a, rogue system register read'
* CPU microcode mitigates the vulnerability: NO
> STATUS: VULNERABLE (an up-to-date CPU microcode is needed to mitigate this vulnerability)

CVE-2018-3639 aka 'Variant 4, speculative store bypass'
* Mitigated according to the /sys interface: YES (Not affected)
* Kernel supports disabling speculative store bypass (SSB): YES (found in /proc/self/status)
* SSB mitigation is enabled and active: NO (not vulnerable)
> STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)

CVE-2018-3615 aka 'Foreshadow (SGX), L1 terminal fault'
* CPU microcode mitigates the vulnerability: N/A
> STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)

CVE-2018-3620 aka 'Foreshadow-NG (OS), L1 terminal fault'
* Mitigated according to the /sys interface: YES (Not affected)
* Kernel supports PTE inversion: * PTE inversion enabled and active: NO
> STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)

CVE-2018-3646 aka 'Foreshadow-NG (VMM), L1 terminal fault'
* Information from the /sys interface: Not affected
* This system is a host running a hypervisor: NO
* Mitigation 1 (KVM)
* EPT is disabled: NO
* Mitigation 2
* L1D flush is supported by kernel: UNKNOWN (missing 'strings' tool, please install it, usually it's in the binutils package)
* L1D flush enabled: NO
* Hardware-backed L1D flush supported: NO (flush will be done in software, this is slower)
* Hyper-Threading (SMT) is enabled: NO
> STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)

CVE-2018-12126 aka 'Fallout, microarchitectural store buffer data sampling (MSBDS)'
* Mitigated according to the /sys interface: NO (Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled)
* Kernel supports using MD_CLEAR mitigation: UNKNOWN
* Kernel mitigation is enabled and active: NO
* SMT is either mitigated or disabled: YES
> STATUS: VULNERABLE (Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled)

CVE-2018-12130 aka 'ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)'
* Mitigated according to the /sys interface: NO (Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled)
* Kernel supports using MD_CLEAR mitigation: UNKNOWN
* Kernel mitigation is enabled and active: NO
* SMT is either mitigated or disabled: YES
> STATUS: VULNERABLE (Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled)

CVE-2018-12127 aka 'RIDL, microarchitectural load port data sampling (MLPDS)'
* Mitigated according to the /sys interface: NO (Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled)
* Kernel supports using MD_CLEAR mitigation: UNKNOWN
* Kernel mitigation is enabled and active: NO
* SMT is either mitigated or disabled: YES
> STATUS: VULNERABLE (Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled)

CVE-2019-11091 aka 'RIDL, microarchitectural data sampling uncacheable memory (MDSUM)'
* Mitigated according to the /sys interface: NO (Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled)
* Kernel supports using MD_CLEAR mitigation: UNKNOWN
* Kernel mitigation is enabled and active: NO
* SMT is either mitigated or disabled: YES
> STATUS: VULNERABLE (Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled)

> SUMMARY: CVE-2017-5753:OK CVE-2017-5715:OK CVE-2017-5754:OK CVE-2018-3640:KO CVE-2018-3639:OK CVE-2018-3615:OK CVE-2018-3620:OK CVE-2018-3646:OK CVE-2018-12126:KO CVE-2018-12130:KO CVE-2018-12127:KO CVE-2019-11091:KO

Need more detailed information about mitigation options? Use --explain
A false sense of security is worse than no security at all, see --disclaimer

abraham111
Posts: 9
Joined: 2020-11-25 21:14

Re: ASUS X205T

#12 Post by abraham111 »

Image
Image
Image
Image
Image
Image

abraham111
Posts: 9
Joined: 2020-11-25 21:14

Re: ASUS X205T

#13 Post by abraham111 »

This thread is solved!

Here's how I fixed it after installing pulseaudio and alsamixer components in synpatic.

ASUS x205T sound fix

You just have to paste one line in terminal and reboot voila:

Image

User avatar
sunrat
Global Moderator
Global Moderator
Posts: 3749
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 3 times
Been thanked: 11 times

Re: ASUS X205T

#14 Post by sunrat »

abraham111 wrote:This thread is solved!

Here's how I fixed it after installing pulseaudio and alsamixer components in synpatic.

ASUS x205T sound fix
Nice find. You didn't need to install Pulseaudio as it's part of a default installation.
And you don't need to install snapd. A kitten dies every time you use a snap in Debian. Leave that rubbish for *buntu users.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

Post Reply