Audio Not Functional (please help)

[dyamuh]

Hey! Sorry in advance if this was already answered but I can't hear audio on my Arch with ML4W Dotfiles (latest as of now on both). I have an ASUS Vivobook 14 Flip which was bought recently. If you need any information to help please let me know.

Thanks!!

[mylinuxforwork]

Hi, can you try to install

sudo pacman -S alsa-utils pavucontrol pipewire pipewire-alsa pipewire-pulse wireplumber

Thanks for testing.

[dyamuh]

Yes of course! These dotfiles are very great and in my opinion the best balance between aesthetics and productivity.

Going back on topic, running the given command just reinstalled all of those packages with no error messages. I still cannot hear audio after running the commands. I have found a promising post that explains how to fix this issue on a similar model (TP3407SA) and I'm currently trying it. I'll let you know how that goes.

Thanks for the response!

[dyamuh]

I have figured out a solution and will post it under here in a bit.

I would like to mention that I'm pretty sure that this is not a problem with the dotfiles and that it will have the same issue on any Linux distribution above kernel 6.

[dyamuh]

STEPS TO FIX AUDIO ON ASUS VIVOBOOK LAPTOPS RUNNING LINUX KERNEL 6+

First, we need to find the i2c bus for your audio chip. Start by loading up the i2c kernel module with this command:
modprobe i2c-dev

Next, list all the i2c buses detected with this command:
ls -alh /sys/bus/i2c/devices/

You need to find the correct i2c bus for your speakers. To do this, check the list of buses from the previous command and look for the one(s) with a name similar to "Synopsys DesignWare". For the ones that had the name "Synopsys DesignWare", check the number after "i2c_" and remember all of the numbers for the different buses that have the name "Synopsys DesignWare".

We have to find the correct bus out of the ones that had the name "Synopsys DesignWare". To do this, use the numbers we memorized in the last step and run this command for each of the numbers:
sudo i2cdetect -r -y NUMBER

This will return a table looking output. From this output, you want to look for the one with the the amps of 0x38 and 0x3d (these might be different for you but on most models, they will be exactly like these). After you found the correct bus number which had the amps of 0x38 and 0x3d after running the previous command it's time to make a script to set your speakers to use that bus. Paste the following script into a new file preferably in /usr/local/bin. (I used /usr/local/bin/2pa-byps.sh).

Quick Disclaimer: The following script was not made by me, it was made by "rraks" (shoutout to him).

#!/bin/bash

export TERM=linux

modprobe i2c-dev
i2c_bus=<NUMBER>
echo "Using I2C bus: $i2c_bus"
i2c_addr=(0x38 0x3d)

count=0
for value in "${i2c_addr[@]}"; do
    val=$((count % 2))
    i2cset -f -y "$i2c_bus" "$value" 0x00 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x7f 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x01 0x01
    i2cset -f -y "$i2c_bus" "$value" 0x0e 0xc4
    i2cset -f -y "$i2c_bus" "$value" 0x0f 0x40
    i2cset -f -y "$i2c_bus" "$value" 0x5c 0xd9
    i2cset -f -y "$i2c_bus" "$value" 0x60 0x10
    if [ $val -eq 0 ]; then
        i2cset -f -y "$i2c_bus" "$value" 0x0a 0x1e
    else
        i2cset -f -y "$i2c_bus" "$value" 0x0a 0x2e
    fi
    i2cset -f -y "$i2c_bus" "$value" 0x0d 0x01
    i2cset -f -y "$i2c_bus" "$value" 0x16 0x40
    i2cset -f -y "$i2c_bus" "$value" 0x00 0x01
    i2cset -f -y "$i2c_bus" "$value" 0x17 0xc8
    i2cset -f -y "$i2c_bus" "$value" 0x00 0x04
    i2cset -f -y "$i2c_bus" "$value" 0x30 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x31 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x32 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x33 0x01

    i2cset -f -y "$i2c_bus" "$value" 0x00 0x08
    i2cset -f -y "$i2c_bus" "$value" 0x18 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x19 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x1a 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x1b 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x28 0x40
    i2cset -f -y "$i2c_bus" "$value" 0x29 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x2a 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x2b 0x00

    i2cset -f -y "$i2c_bus" "$value" 0x00 0x0a
    i2cset -f -y "$i2c_bus" "$value" 0x48 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x49 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x4a 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x4b 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x58 0x40
    i2cset -f -y "$i2c_bus" "$value" 0x59 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x5a 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x5b 0x00

    i2cset -f -y "$i2c_bus" "$value" 0x00 0x00
    i2cset -f -y "$i2c_bus" "$value" 0x02 0x00
    count=$((count + 1))
done

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PLEASE REPLACE NUMBER IN THE SCRIPT WITH THE APPROPRIATE BUS NUMBER

After saving this script and making it executable using chmod, run it using sudo and test your speakers. If the speaker directions (left and right) are reversed, replace i2c_addr=(0x38 0x3d) with i2c_addr=(0x3d 0x38).

If your speakers didn't work, you chose the wrong bus number in which case you should replace the bus number in the script with others with the name of "Synopsys DesignWare".

Congrats, you now have audio on your Arch Linux setup which should obviously be using ML4W dotfiles.

thank you to dwilliam62 for formatting the bash script

[dwilliam62]

for formatting you can add three back ticks in a row (on the ~ key) then the word bash Then paste your code and three more backticks

[dwilliam62]

#!/bin/bash

export TERM=linux

modprobe i2c-dev
i2c_bus=
echo "Using I2C bus: $i2c_bus"
i2c_addr=(0x38 0x3d)

count=0
for value in "${i2c_addr[@]}"; do
val=$((count % 2))
i2cset -f -y "$i2c_bus" "$value" 0x00 0x00
i2cset -f -y "$i2c_bus" "$value" 0x7f 0x00
i2cset -f -y "$i2c_bus" "$value" 0x01 0x01
i2cset -f -y "$i2c_bus" "$value" 0x0e 0xc4
i2cset -f -y "$i2c_bus" "$value" 0x0f 0x40
i2cset -f -y "$i2c_bus" "$value" 0x5c 0xd9
i2cset -f -y "$i2c_bus" "$value" 0x60 0x10
if [ $val -eq 0 ]; then
i2cset -f -y "$i2c_bus" "$value" 0x0a 0x1e
else
i2cset -f -y "$i2c_bus" "$value" 0x0a 0x2e
fi
i2cset -f -y "$i2c_bus" "$value" 0x0d 0x01
i2cset -f -y "$i2c_bus" "$value" 0x16 0x40
i2cset -f -y "$i2c_bus" "$value" 0x00 0x01
i2cset -f -y "$i2c_bus" "$value" 0x17 0xc8
i2cset -f -y "$i2c_bus" "$value" 0x00 0x04
i2cset -f -y "$i2c_bus" "$value" 0x30 0x00
i2cset -f -y "$i2c_bus" "$value" 0x31 0x00
i2cset -f -y "$i2c_bus" "$value" 0x32 0x00
i2cset -f -y "$i2c_bus" "$value" 0x33 0x01

i2cset -f -y "$i2c_bus" "$value" 0x00 0x08
i2cset -f -y "$i2c_bus" "$value" 0x18 0x00
i2cset -f -y "$i2c_bus" "$value" 0x19 0x00
i2cset -f -y "$i2c_bus" "$value" 0x1a 0x00
i2cset -f -y "$i2c_bus" "$value" 0x1b 0x00
i2cset -f -y "$i2c_bus" "$value" 0x28 0x40
i2cset -f -y "$i2c_bus" "$value" 0x29 0x00
i2cset -f -y "$i2c_bus" "$value" 0x2a 0x00
i2cset -f -y "$i2c_bus" "$value" 0x2b 0x00

i2cset -f -y "$i2c_bus" "$value" 0x00 0x0a
i2cset -f -y "$i2c_bus" "$value" 0x48 0x00
i2cset -f -y "$i2c_bus" "$value" 0x49 0x00
i2cset -f -y "$i2c_bus" "$value" 0x4a 0x00
i2cset -f -y "$i2c_bus" "$value" 0x4b 0x00
i2cset -f -y "$i2c_bus" "$value" 0x58 0x40
i2cset -f -y "$i2c_bus" "$value" 0x59 0x00
i2cset -f -y "$i2c_bus" "$value" 0x5a 0x00
i2cset -f -y "$i2c_bus" "$value" 0x5b 0x00

i2cset -f -y "$i2c_bus" "$value" 0x00 0x00
i2cset -f -y "$i2c_bus" "$value" 0x02 0x00
count=$((count + 1))```

[mylinuxforwork]

It's not a ML4W OS issue, right?

[dwilliam62]

It's not a ML4W OS issue, right?

Since it's an OS level issue and he was using Arch also, I would say it's a very likely to happen with your ISO as well.

[dyamuh]

It's not a ML4W OS issue, right?

Nah, it's for any Linux distribution that is kernel 6 or higher running on a new ASUS Vivobook.

[mylinuxforwork]

I assume that this isn't a ML4W OS issue.

[dwilliam62]

I assume that this isn't a ML4W OS issue.

Not specifically no. But an ML4W user with that hardware will likely have the issue. SO you might want to save this solution in case someone hits it. I don't know that you want to specifically guard against it in code though. Hopefully it will be resolved upstream