B.S. Biology; M.S. in Bioinformatics. ❤️ tech, FOSS, Lana Del Rey, Linux, Fedora, KDE, but also ARM MacBooks & iOS.
Good @ Python, forced to use R, learning Rust.
🎮 Prey (2017), Bioshock, Portal & Dead Space.
Bi, more into guys atm.
@hyfi:matrix.org
also [email protected]
You mean my headphones? They’re Sony WH-1000XM5.
On second thought, they don’t specifically have support for Atmos but I was under the impression that as long as the device playing the content natively supports it, it should be fine.
Spatial Audio settings:
Dolby Atmos settings when Spatial Audio is off:
Apple’s implementation of Spatial Audio uses Dolby Atmos, so I was wondering if the same was possible on Android.
But the question is, if I’m playing Dolby Atmos content, what should I use then? It’d make more sense to use the Dolby Atmos setting but that one doesn’t have head tracking (that my headphones support).
Is it possible to use Dolby Atmos AND Spatial Audio at the same time?
[https://lemmy.world/pictrs/image/c7ab0444-8c6c-4fde-b1fe-71e82bb4d29f.jpeg] I can’t understand if it just means that for some reason the settings cannot be changed (refer to the screenshot) or if it’s because Dolby Atmos is disabled when Spatial Audio is on. I could not find any information about this anywhere.
Swap causing very slow boot (and systemd says the swap partition became active after 500k years)
cross-posted from: https://lemmy.world/post/13313385 [https://lemmy.world/post/13313385] > I’m dualbooting Fedora Kinoite (ublue-nvidia image) with Windows 11 and I have a boot time of over 1 minute (only on the Fedora side). > > The output of systemd-analyze critical-chain is: > > graphical.target @16.435s > └─sddm.service @16.435s > └─plymouth-quit.service @16.315s +107ms > └─systemd-user-sessions.service @16.299s +12ms > └─remote-fs.target @16.298s > └─remote-fs-pre.target @16.298s > └─nfs-client.target @16.298s > └─gssproxy.service @16.288s +9ms > └─network.target @16.285s > └─wpa_supplicant.service @16.281s +4ms > └─basic.target @14.798s > └─dbus-broker.service @14.774s +22ms > └─dbus.socket @14.760s > └─sysinit.target @14.757s > └─systemd-resolved.service @14.696s +61ms > └─systemd-tmpfiles-setup.service @14.584s +96ms > └─local-fs.target @14.569s > └─run-user-1000-doc.mount @23.123s > └─run-user-1000.mount @22.463s > └─swap.target @1.410s > └─dev-disk-by\x2duuid-819f25f8\x2daf77\x2d4d7b\x2daaf7\x2dadb07819a7b1.swap @1.276s +35ms > └─dev-disk-by\x2duuid-819f25f8\x2daf77\x2d4d7b\x2daaf7\x2dadb07819a7b1.device @584542y 2w 2d 20h 46.792s +1min 3.997s > > > First of all, I would like to know what the hell is going on with that 584542 years active time lol > > Anyway, the x2dadb07819a7b1 UUID belongs to the swap partition. > > Output of lsblk -f: > > > NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS > zram0 [SWAP] > nvme0n1 > ├─nvme0n1p1 vfat FAT32 EFI AAFB-90EA 553.6M 7% /boot/efi > ├─nvme0n1p2 ext4 1.0 fedora-boot a1457f7b-c1fb-40da-9c6f-98356d9003e2 526.8M 39% /boot > ├─nvme0n1p3 ext4 1.0 fedora-root 0e748e63-f5f5-42f1-babd-818054eb9ee5 40.8G 35% /var > │ /sysroot/ostree/deploy/fedora/var > │ /usr > │ /etc > │ / > │ /sysroot > ├─nvme0n1p4 swap 1 fedora-swap 819f25f8-af77-4d7b-aaf7-adb07819a7b1 [SWAP] > ├─nvme0n1p5 crypto_LUKS 2 ea073ead-906c-4127-9555-efba204baabf > │ └─luks-ea073ead-906c-4127-9555-efba204baabf ext4 1.0 fedora-home e37f299a-84f5-46ce-976c-507b8e8e25f8 1T 1% /var/home > ├─nvme0n1p6 ntfs Extra 74FE8F25FE8EDF2C > ├─nvme0n1p7 > ├─nvme0n1p8 BitLocker 2 > └─nvme0n1p9 ntfs C02807922807869E > > > What should I do?
Swap causing very slow boot (and systemd says the swap partition became active after 500k years)
I’m dualbooting Fedora Kinoite (ublue-nvidia image) with Windows 11 and I have a boot time of over 1 minute (only on the Fedora side). The output of systemd-analyze critical-chain is: graphical.target @16.435s └─sddm.service @16.435s └─plymouth-quit.service @16.315s +107ms └─systemd-user-sessions.service @16.299s +12ms └─remote-fs.target @16.298s └─remote-fs-pre.target @16.298s └─nfs-client.target @16.298s └─gssproxy.service @16.288s +9ms └─network.target @16.285s └─wpa_supplicant.service @16.281s +4ms └─basic.target @14.798s └─dbus-broker.service @14.774s +22ms └─dbus.socket @14.760s └─sysinit.target @14.757s └─systemd-resolved.service @14.696s +61ms └─systemd-tmpfiles-setup.service @14.584s +96ms └─local-fs.target @14.569s └─run-user-1000-doc.mount @23.123s └─run-user-1000.mount @22.463s └─swap.target @1.410s └─dev-disk-by\x2duuid-819f25f8\x2daf77\x2d4d7b\x2daaf7\x2dadb07819a7b1.swap @1.276s +35ms └─dev-disk-by\x2duuid-819f25f8\x2daf77\x2d4d7b\x2daaf7\x2dadb07819a7b1.device @584542y 2w 2d 20h 46.792s +1min 3.997s First of all, I would like to know what the hell is going on with that 584542 years active time lol Anyway, the x2dadb07819a7b1 UUID belongs to the swap partition. Output of lsblk -f: NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS zram0 [SWAP] nvme0n1 ├─nvme0n1p1 vfat FAT32 EFI AAFB-90EA 553.6M 7% /boot/efi ├─nvme0n1p2 ext4 1.0 fedora-boot a1457f7b-c1fb-40da-9c6f-98356d9003e2 526.8M 39% /boot ├─nvme0n1p3 ext4 1.0 fedora-root 0e748e63-f5f5-42f1-babd-818054eb9ee5 40.8G 35% /var │ /sysroot/ostree/deploy/fedora/var │ /usr │ /etc │ / │ /sysroot ├─nvme0n1p4 swap 1 fedora-swap 819f25f8-af77-4d7b-aaf7-adb07819a7b1 [SWAP] ├─nvme0n1p5 crypto_LUKS 2 ea073ead-906c-4127-9555-efba204baabf │ └─luks-ea073ead-906c-4127-9555-efba204baabf ext4 1.0 fedora-home e37f299a-84f5-46ce-976c-507b8e8e25f8 1T 1% /var/home ├─nvme0n1p6 ntfs Extra 74FE8F25FE8EDF2C ├─nvme0n1p7 ├─nvme0n1p8 BitLocker 2 └─nvme0n1p9 ntfs C02807922807869E What should I do?