Was audio changed with the last update?
I cant go to settings>Audio>and put audio level above 100%
100% is the highest it'll go.
My laptop has pretty low audio, I have bad hearing also, so it helps putting audio at 130%.
where garuda-inxi?
1 Like
Sorry I rarely have issues and forgot about this. In my opinion nothing is broken, Iām just deaf and need it to be louder.
garuda-inxi
mdoverl@mdoverl in ~
ā°āĪ» garuda-inxi
System:
Kernel: 6.2.2-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=fae2eeb3-5612-408c-9d4e-749b6c3448cb rw rootflags=subvol=@
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=4f532041-9bce-4418-b7d5-4b9fdfba3d44 loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.3 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Laptop System: ASUSTeK product: TP501UAM v: 1.0
serial:
Mobo: ASUSTeK model: TP501UAM v: 1.0 serial:
UEFI: American Megatrends v: TP501UAM.201 date: 04/18/2016
Battery:
ID-1: BAT0 charge: 16.5 Wh (100.0%) condition: 16.5/38.0 Wh (43.3%)
volts: 7.6 min: 7.6 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
status: not charging cycles: 114
CPU:
Info: model: Intel Core i5-6200U bits: 64 type: MT MCP arch: Skylake
gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
model-id: 0x4E (78) stepping: 3 microcode: 0xF0
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 2667 high: 2791 min/max: 400/2800 scaling:
driver: intel_pstate governor: performance cores: 1: 2777 2: 2400 3: 2700
4: 2791 bogomips: 19200
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Graphics:
Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: ASUSTeK driver: i915
v: kernel arch: Gen-9 process: Intel 14n built: 2015-16 ports: active: eDP-1
empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:1916 class-ID: 0300
Device-2: Chicony USB2.0 VGA UVC WebCam type: USB driver: uvcvideo
bus-ID: 1-6:4 chip-ID: 04f2:b496 class-ID: 0e02
Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8
compositor: kwin_x11 driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: eDP-1 model: ChiMei InnoLux 0x15c4 built: 2013 res: 1920x1080
hz: 60 dpi: 142 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5")
ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 520 (SKL
GT2) direct-render: Yes
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_soc_avs
bus-ID: 00:1f.3 chip-ID: 8086:9d70 class-ID: 0403
Sound API: ALSA v: k6.2.2-zen2-1-zen running: yes
Sound Interface: sndio v: N/A running: no
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.67 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: e000 bus-ID: 01:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac:
Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:095a class-ID: 0280
IF: wlp2s0 state: down mac:
Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
bus-ID: 1-8:6 chip-ID: 8087:0a2a class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 5 state: up address:
Drives:
Local Storage: total: 931.51 GiB used: 359.49 GiB (38.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WDS100T2B0B-00YS70 size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s type: SSD serial: rev: 00WD
scheme: GPT
Partition:
ID-1: / raw-size: 918.98 GiB size: 918.98 GiB (100.00%)
used: 359.49 GiB (39.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 608 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 918.98 GiB size: 918.98 GiB (100.00%)
used: 359.49 GiB (39.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 918.98 GiB size: 918.98 GiB (100.00%)
used: 359.49 GiB (39.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 918.98 GiB size: 918.98 GiB (100.00%)
used: 359.49 GiB (39.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 11.12 GiB used: 621.2 MiB (5.5%)
priority: 100 dev: /dev/zram0
ID-2: swap-2 type: partition size: 12.24 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda3 maj-min: 8:3
Sensors:
System Temperatures: cpu: 52.0 C pch: 47.5 C mobo: N/A
Fan Speeds (RPM): cpu: 3400
Info:
Processes: 257 Uptime: 2d 19h 51m wakeups: 11 Memory: 11.12 GiB
used: 4.68 GiB (42.1%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 12.2.1 Packages: 2159 pm: pacman pkgs: 2152
libs: 597 tools: octopi,pamac,paru pm: appimage pkgs: 0 pm: flatpak pkgs: 7
Shell: fish v: 3.6.0 default: Bash v: 5.1.16 running-in: konsole
inxi: 3.3.25
Garuda (2.6.15-1):
System install date: 2022-12-10
Last full system update: 2023-03-16 ā»
Is partially upgraded: No
Relevant software: snapper NetworkManager mkinitcpio
Windows dual boot: No/Undetected
Failed units:
Among the KDE audio settings, there is a checkbox that allows you to go over 100% volume. I really cannot recommend that though, as it causes a lot of distortion.
2 Likes
Thank you, that was it. I'm not worried about distortion because I need to be able to hear what I'm listening to.
1 Like
You might want to try a hardware audio amplifier for that. They seem to go mostly without distortion and can go very loud. They do however require analog headphones to my knowledge
Edit: E.g. the Chord Mojo (I don't know really many more, all my knowledge regarding that is from DankPods blowing up headphones lol)
There is a risk of blowing out your speakers when you push your audio past 100%. Some people have been made very sorry over the years from doing this. Fair warning to those using this option that it comes with the potential for damaging your hardware.
We have gotten some user complaints in the past blaming the damage on the distro. If you choose to implement this option and you damage your audio hardware that's on you, (not the distro). Just a word of caution for those thinking of using this option with a set of fairly expensive speakers, (you may regret it).
2 Likes
"Why don't you just make ten louder, and make ten be the top number, and make that a little louder?"
"...These go to eleven."
3 Likes
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.