Fedora 40 audio and touch screen not working after dual booting with windows 11

Ask Fedora
, , , , , , , , ,
1

So basically, i dual booted windows 11 with fedora 40 because i wanted to try linux, however, when i do so, neither my touch screen nor audio work. Loading windows, audio and touch screen work there, but not on fedora. I’ve tried ubuntu and mint, and neither of them made any difference. Here is the result from inxi -Fzxx

System:
  Kernel: 6.8.5-301.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.41-34.fc40
  Desktop: GNOME v: 46.0 tk: GTK v: 3.24.41 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 40 (Workstation Edition)
Machine:
  Type: Convertible System: HP product: HP ENVY x360 2-in-1 Laptop 13-bf0xxx
    v: Type1ProductConfigId serial: <superuser required> Chassis: type: 31
    serial: <superuser required>
  Mobo: HP model: 8A28 v: 21.49 serial: <superuser required>
    part-nu: 6X0Q8PA#ABG UEFI: Insyde v: F.30 date: 03/26/2024
Battery:
  ID-1: BAT1 charge: 53.9 Wh (100.0%) condition: 53.9/66.5 Wh (81.0%)
    volts: 8.5 min: 7.7 model: Hewlett-Packard PABAS0241231 serial: <filter>
    status: full
  Device-1: hidpp_battery_0 model: Logitech M350 Wireless Mouse
    serial: <filter> charge: 55% (should be ignored) status: discharging
CPU:
  Info: 10-core (2-mt/8-st) model: 12th Gen Intel Core i7-1250U bits: 64
    type: MST AMCP arch: Alder Lake rev: 4 cache: L1: 928 KiB L2: 6.5 MiB
    L3: 12 MiB
  Speed (MHz): avg: 787 high: 1054 min/max: 400/4700:3500 cores: 1: 899
    2: 991 3: 924 4: 400 5: 1054 6: 1037 7: 970 8: 400 9: 1013 10: 400 11: 965
    12: 400 bogomips: 45158
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Alder Lake-UP4 GT2 [Iris Xe Graphics]
    vendor: Hewlett-Packard driver: i915 v: kernel arch: Gen-12.2 ports:
    active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-1 bus-ID: 00:02.0
    chip-ID: 8086:46aa
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.4
    compositor: gnome-shell driver: gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: BOE Display 0x0adc res: 1920x1200 dpi: 171
    diag: 337mm (13.3")
  API: OpenGL v: 4.6 vendor: intel mesa v: 24.0.5 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel Graphics (ADL GT2)
    device-ID: 8086:46aa display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel Alder Lake Imaging Signal Processor vendor: Hewlett-Packard
    driver: N/A bus-ID: 00:05.0 chip-ID: 8086:465d
  Device-2: Intel Alder Lake Smart Sound Audio vendor: Hewlett-Packard
    driver: sof-audio-pci-intel-tgl bus-ID: 00:1f.3 chip-ID: 8086:51cc
  API: ALSA v: k6.8.5-301.fc40.x86_64 status: kernel-api
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.0.4 status: active with: 1: wireplumber
    status: active 2: pipewire-alsa type: plugin
  Server-3: PulseAudio v: 16.1 status: active
Network:
  Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:51f0
  IF: wlo1 state: up mac: <filter>
Bluetooth:
  Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 3-10:3 chip-ID: 8087:0033
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
    lmp-v: 12
Drives:
  Local Storage: total: 476.94 GiB used: 6.61 GiB (1.4%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WD PC SN810
    SDCPNRY-512G-1006 size: 476.94 GiB speed: 63.2 Gb/s lanes: 4
    serial: <filter> temp: 34.9 C
Partition:
  ID-1: / size: 173.46 GiB used: 6.29 GiB (3.6%) fs: btrfs dev: /dev/nvme0n1p6
  ID-2: /boot size: 973.4 MiB used: 237.2 MiB (24.4%) fs: ext4
    dev: /dev/nvme0n1p5
  ID-3: /boot/efi size: 256 MiB used: 90.6 MiB (35.4%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 173.46 GiB used: 6.29 GiB (3.6%) fs: btrfs
    dev: /dev/nvme0n1p6
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 41.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 0 fan-2: 0
Info:
  Memory: total: 16 GiB note: est. available: 15.31 GiB used: 3.31 GiB (21.6%)
  Processes: 410 Power: uptime: 3m wakeups: 0 Init: systemd v: 255
    target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 2
    Compilers: N/A Shell: Bash v: 5.2.26 running-in: gnome-terminal inxi: 3.3.34

on windows the audio is running on bang and olufsen so that might be the problem, but honestly i have no idea and any help would be great

2

I can see from your kernel version that your system is not up to date.
Please update your system and test again.

I have edited your post to put the inxi output into a pre-formatted text block.

3

Ok after updating to latest kernel, audio now works, however, touch screen still does not work.

4

See: Reddit Linux Distro with Good Touchscreen Support – there is support in the kernel, but it can take time for new hardware to be enabled.

When reporting problems you should always ensure that Fedora packages and vendor firmware are current so you aren’t chasing a solved problem.

The LHDB collects detail “probes” of linux systems, and often has user comments with workarounds for things like touch-screens. You can search for probes of your model as well as other touch-screen laptops.

5

What are you actually saying I should do? I have the latest kernel now, and my touch screen still is not working. LHDB doesn’t even recognize that I have a touch screen, even though i definitely do, and the Reddit post doesn’t say anything about fixing a non-functional touch screen.

6

When you boot and got login screen select user and on bottom right screen will appear :gear: select it and will show options like gnome , gnome classic and gnome on xorg . Chose gnome on xorg and see it will touch screen works.

7

I thought that input devices use the same library, (libinput?) on Wayland and X11.
In which case it does not matter if its X11 or Wayland you run under.

I think what @gnwiii is thinking is that the kernel may not have support for this laptops touch screen. (The sad thing is that touch screen are far from standard and need lots of unique kernel support).

8

There are a lot more packages than just the kernel that may be involved, including vendor firmware.

Yes, it can take some time for that support to appear, even longer if the hardware is significantly different from previous devices and the vendor isn’t contributing.

9

So I can’t do anything about it?

10

If you do not have the driver it will not work. End of story.

If you can find a driver that works it may solve the problem.