I have just installed a pair of AudioEngine speakers and have many problems:
The stock Fedora-34 with pipewire allows some audio output from the speakers but with problems. However the system with pipewire was so unstable that I was unable to investigate: * device names changed * audio configuration changed in unexpected ways, for unknown reasons * system locked up (probably KDE Plasma lockup) * audio went from one device to another and back every second or so * ...
So I reverted to pulseaudio. The audio is now stable, but the speakers are not recognized. Here are suspicious sections of the starts of the journals for the two setups:
With pipewire: ... Oct 07 15:50:10 amito kernel: usb 3-14: reset full-speed USB device number 6 using xhci_hcd Oct 07 15:50:11 amito kernel: usb 3-14.1: new full-speed USB device number 9 using xhci_hcd Oct 07 15:50:11 amito kernel: usb 3-14.1: New USB device found, idVendor=0a12, idProduct=4007, bcdDevice=14.86 Oct 07 15:50:11 amito kernel: usb 3-14.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 07 15:50:11 amito kernel: usb 3-14.1: Product: Audioengine 2+ Oct 07 15:50:11 amito kernel: usb 3-14.1: Manufacturer: Audioengine LLC Oct 07 15:50:11 amito kernel: usb 3-14.1: SerialNumber: AE202010001A2002 Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 48000 to ep 0x3 Oct 07 15:50:11 amito kernel: hid-generic 0003:0A12:4007.0007: hiddev97,hidraw3: USB HID v1.11 Device [Audioengine LLC Audioengine 2+] on usb-0000:00:14.0-14.1/input2 Oct 07 15:50:11 amito upowerd[2720]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-14 Oct 07 15:50:11 amito upowerd[2720]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-14 Oct 07 15:50:11 amito mtp-probe[6841]: checking bus 3, device 9: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-14/3-14.1" Oct 07 15:50:11 amito mtp-probe[6841]: bus: 3, device: 9 was not an MTP device Oct 07 15:50:11 amito plasmashell[4490]: UdevQt: unhandled device action "bind" Oct 07 15:50:11 amito plasmashell[4490]: UdevQt: unhandled device action "bind" Oct 07 15:50:11 amito plasmashell[4490]: UdevQt: unhandled device action "bind" Oct 07 15:50:11 amito mtp-probe[6869]: checking bus 3, device 9: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-14/3-14.1" Oct 07 15:50:11 amito mtp-probe[6869]: bus: 3, device: 9 was not an MTP device Oct 07 15:50:11 amito plasmashell[4490]: UdevQt: unhandled device action "bind" Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to ep 0x3 Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to ep 0x3 Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to ep 0x3 Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to ep 0x3 Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to ep 0x3 Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to ep 0x3 Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to ep 0x3 ...
Using pulseaudio: ... Oct 07 17:45:46 amito kernel: usb 3-14.1: New USB device found, idVendor=0a12, idProduct=4007, bcdDevice=14.86 Oct 07 17:45:46 amito kernel: usb 3-14.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 07 17:45:46 amito kernel: usb 3-14.1: Product: Audioengine 2+ Oct 07 17:45:46 amito kernel: hid-generic 0003:046D:400A.0005: input,hidraw2: USB HID v1.11 Mouse [Logitech Wireless Device PID:400a] on usb-0000:00:14.0-13/input2:1 Oct 07 17:45:46 amito kernel: hub 3-14:1.0: hub_ext_port_status failed (err = -71) Oct 07 17:45:46 amito kernel: input: Logitech M325 as /devices/pci0000:00/0000:00:14.0/usb3/3-13/3- 13:1.2/0003:046D:C52B.0004/0003:046D:400A.0005/input/input13 ... Oct 07 17:45:46 amito kernel: usb 3-14.1: New USB device found, idVendor=0a12, idProduct=4007, bcdDevice=14.86 Oct 07 17:45:46 amito kernel: usb 3-14.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 07 17:45:46 amito kernel: usb 3-14.1: Product: Audioengine 2+ Oct 07 17:45:46 amito kernel: usb 3-14.1: Manufacturer: Audioengine LLC Oct 07 17:45:46 amito kernel: usb 3-14.1: can't set config #1, error - 71 ...
It would help to know what the various errors mean.
System is Fedora-34 with all updates installed, in detail: Operating System: Fedora 34 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.9-200.fc34.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600
On Thu, 2021-10-07 at 18:55 -0700, Jonathan Ryshpan wrote:
The stock Fedora-34 with pipewire allows some audio output from the speakers but with problems. However the system with pipewire was so unstable that I was unable to investigate:
- device names changed
- audio configuration changed in unexpected ways, for unknown reasons
- system locked up (probably KDE Plasma lockup)
- audio went from one device to another and back every second or so
- ...
So I reverted to pulseaudio. The audio is now stable, but the speakers are not recognized. Here are suspicious sections of the starts of the journals for the two setups:
Today's upgrade has mostly but not completely cured the problem, at least for pulseaudio. The speakers started working as soon as the upgrade had taken effect, even before a reboot. I don't see what upgraded package could have caused the device to appear; the record of the upgrade is attached (dnf-upgrade-1021-10-08.txt). Unfortunately, the computer audio system does not always recognize the Audioengine-2+ speakers. Maybe there is some kind of race condition.
Here are extracts from system journals showing two different boot sequences, one that works and one that doesn't:
A boot that works: Oct 08 14:06:08 amito kernel: usb 3-14.1: New USB device found, idVendor=0a12, idProduct=4007, bcdDevice=14.86 Oct 08 14:06:08 amito kernel: usb 3-14.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 08 14:06:08 amito kernel: usb 3-14.1: Product: Audioengine 2+ Oct 08 14:06:08 amito kernel: usb 3-14.1: Manufacturer: Audioengine LLC Oct 08 14:06:08 amito kernel: usb 3-14.1: SerialNumber: AE202010001A2002 Oct 08 14:06:08 amito kernel: hid-generic 0003:0A12:4007.0006: hiddev97,hidraw3: USB HID v1.11 Device [Audioengine LLC Audioengine 2+] on usb-0000:00:14.0-14.1/input2
The boot just before the one above, which doesn't work: Oct 08 14:00:31 amito kernel: usb 3-14.1: new full-speed USB device number 8 using xhci_hcd Oct 08 14:00:31 amito kernel: usb 3-14.1: New USB device found, idVendor=0a12, idProduct=4007, bcdDevice=14.86 Oct 08 14:00:31 amito kernel: usb 3-14.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 08 14:00:31 amito kernel: usb 3-14.1: Product: Audioengine 2+ Oct 08 14:00:31 amito kernel: usb 3-14.1: Manufacturer: Audioengine LLC Oct 08 14:00:31 amito kernel: usb 3-14.1: can't set config #1, error - 71
On 09/10/2021 05:58, Jonathan Ryshpan wrote:
Here are extracts from system journals showing two different boot sequences, one that works and one that doesn't:
A boot that works: Oct 08 14:06:08 amito kernel: usb 3-14.1: New USB device found, idVendor=0a12, idProduct=4007, bcdDevice=14.86 Oct 08 14:06:08 amito kernel: usb 3-14.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 08 14:06:08 amito kernel: usb 3-14.1: Product: Audioengine 2+ Oct 08 14:06:08 amito kernel: usb 3-14.1: Manufacturer: Audioengine LLC Oct 08 14:06:08 amito kernel: usb 3-14.1: SerialNumber: AE202010001A2002 Oct 08 14:06:08 amito kernel: hid-generic 0003:0A12:4007.0006: hiddev97,hidraw3: USB HID v1.11 Device [Audioengine LLC Audioengine 2+] on usb-0000:00:14.0-14.1/input2
The boot just before the one above, which doesn't work: Oct 08 14:00:31 amito kernel: usb 3-14.1: new full-speed USB device number 8 using xhci_hcd Oct 08 14:00:31 amito kernel: usb 3-14.1: New USB device found, idVendor=0a12, idProduct=4007, bcdDevice=14.86 Oct 08 14:00:31 amito kernel: usb 3-14.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 08 14:00:31 amito kernel: usb 3-14.1: Product: Audioengine 2+ Oct 08 14:00:31 amito kernel: usb 3-14.1: Manufacturer: Audioengine LLC Oct 08 14:00:31 amito kernel:usb 3-14.1: can't set config #1, error -71
What results do you get if you boot your system with the USB speakers disconnected and the connect them once the system is fully booted?
-- On Facebook it is called Vaguebooking.
On Sat, 2021-10-09 at 06:40 +0800, Ed Greshko wrote:
What results do you get if you boot your system with the USB speakers disconnected and the connect them once the system is fully booted?
Here are two extracts of a boot log: * plugAfterBoot.txt: System boot followed by connecting USB speakers (speakers visible in pavucontrol) * unplugPlug.txt: Disconnecting USB speakers followed by connecting them (speakers visible in pavucontrol)
I'm a little surprised that the system sees the speakers after reporting so many errors.
On Sat, 2021-10-09 at 06:40 +0800, Ed Greshko wrote:
What results do you get if you boot your system with the USB speakers disconnected and the connect them once the system is fully booted?
I was listening to some audio when the sound stopped; AudioEngine had disappeared from the list of output devices. A log extract is attached (Audio-Crash.txt).
There may be a problem with the cable. The speakers are attached to the computer with a USB extender cable, which may not give as good a connection as is needed. So I moved things around and connected the speakers without the extender; we'll see if things get better. A log extract is attached (Audio-Restore-ShortCable.txt).
On 10/10/2021 07:48, Jonathan Ryshpan wrote:
On Sat, 2021-10-09 at 06:40 +0800, Ed Greshko wrote:
What results do you get if you boot your system with the USB speakers disconnected and the connect them once the system is fully booted?
I was listening to some audio when the sound stopped; AudioEngine had disappeared from the list of output devices. A log extract is attached (Audio-Crash.txt).
There may be a problem with the cable. The speakers are attached to the computer with a USB extender cable, which may not give as good a connection as is needed. So I moved things around and connected the speakers without the extender; we'll see if things get better. A log extract is attached (Audio-Restore-ShortCable.txt).
Oh, I never did have much luck with USB extender cables. FWIW, I don't use USB devices all that much. Other than dongles I only have an HDMI capture device hooked to USB.
With speakers, I use Bluetooth. I find them more versatile.
-- On Facebook it is called Vaguebooking.
On Sat, 2021-10-09 at 16:48 -0700, Jonathan Ryshpan wrote:
There may be a problem with the cable. The speakers are attached to the computer with a USB extender cable, which may not give as good a connection as is needed. So I moved things around and connected the speakers without the extender; we'll see if things get better. A log extract is attached (Audio-Restore-ShortCable.txt).
Are the speakers USB powered, too? Powering devices from the computer can show up disconnection problems when the computer is unable to adequately supply them. I've a computer with about 7 USB ports, but if about two of them, any of them, are used with devices that require a modest amount of power, failures repeatedly occur. It seems like all they're good for is keyboard and mouse (even then not that great).
USB extenders can be a problem, in themselves. You've another pair of not-so-great plugs and sockets in the path. Long cables can be a problem for data and power. Amplified long cables can help, but are no panacea (and won't help if the computer didn't supply adequate power). Unshielded cables can suffer interference.
If you have a motherboard that tries to be eco-friendly and power manage USB ports, I suppose it might do that job badly, and add to problems.
I use a 4-way USB hub to connect keyboard and mouse to a computer where their cables are a bit short. If I plug a second mouse into it, things often go bad (for what seems like power supply reasons, rather than software causes). Ironically, the hub could it could have its power boosted externally another supply (not included), through a micro USB socket. Theoretically, I could plug two USB leads into the hub and computer, and then it ought to be able to connect 4 USB devices into the hub. Though, I don't believe the computer is good enough to be the supply. Another wall wart would be needed.
On Sun, 2021-10-10 at 08:38 +0800, Ed Greshko wrote:
On 10/10/2021 07:48, Jonathan Ryshpan wrote:
On Sat, 2021-10-09 at 06:40 +0800, Ed Greshko wrote:
What results do you get if you boot your system with the USB speakers disconnected and the connect them once the system is fully booted?
I was listening to some audio when the sound stopped; AudioEngine had disappeared from the list of output devices. A log extract is attached (Audio-Crash.txt).
There may be a problem with the cable. The speakers are attached to the computer with a USB extender cable, which may not give as good a connection as is needed. So I moved things around and connected the speakers without the extender; we'll see if things get better. A log extract is attached (Audio-Restore- ShortCable.txt).
Oh, I never did have much luck with USB extender cables. FWIW, I don't use USB devices all that much. Other than dongles I only have an HDMI capture device hooked to USB.
With speakers, I use Bluetooth. I find them more versatile.
I have changed the connection to Bluetooth, which worked well for a while, except that sound quality may be a little less good. However the connection is still flaky: After plugging in another sound device via USB, Bluetooth disconnects from the speakers, producing the log message: Oct 10 08:14:28 amito bluetoothd[15557]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to AC:A9:B4:00:06:2E: Connection refused (111) Does anyone know what this means? The connection also drops fairly frequently for no apparent reason. The only way to reconnect is to either remove and reinsert the Bluetooth adapter or to reboot the system.
The Bluetooth adapter, an old Belkin USB dongle, produces this log message when recognized: Oct 09 22:01:10 amito udisksd[2157]: Mounted /dev/sr0 at /run/media/jonrysh/我的光碟 on behalf of uid 1000 Definitely made in China.
I would like to try a different adapter (dongle). Can anyone recommend one? There are a lot of choices, and the ones recommended (for M$ Windows) may not be the best for Linux.
On 13/10/2021 01:15, Jonathan Ryshpan wrote:
On Sun, 2021-10-10 at 08:38 +0800, Ed Greshko wrote:
On 10/10/2021 07:48, Jonathan Ryshpan wrote:
On Sat, 2021-10-09 at 06:40 +0800, Ed Greshko wrote:
What results do you get if you boot your system with the USB speakers disconnected and the connect them once the system is fully booted?
I was listening to some audio when the sound stopped; AudioEngine had disappeared from the list of output devices. A log extract is attached (Audio-Crash.txt).
There may be a problem with the cable. The speakers are attached to the computer with a USB extender cable, which may not give as good a connection as is needed. So I moved things around and connected the speakers without the extender; we'll see if things get better. A log extract is attached (Audio-Restore-ShortCable.txt).
Oh, I never did have much luck with USB extender cables. FWIW, I don't use USB devices all that much. Other than dongles I only have an HDMI capture device hooked to USB.
With speakers, I use Bluetooth. I find them more versatile.
I have changed the connection to Bluetooth, which worked well for a while, except that sound quality may be a little less good. However the connection is still flaky: After plugging in another sound device via USB, Bluetooth disconnects from the speakers, producing the log message: Oct 10 08:14:28 amito bluetoothd[15557]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to AC:A9:B4:00:06:2E: Connection refused (111) Does anyone know what this means? The connection also drops fairly frequently for no apparent reason. The only way to reconnect is to either remove and reinsert the Bluetooth adapter or to reboot the system.
The Bluetooth adapter, an old Belkin USB dongle, produces this log message when recognized: Oct 09 22:01:10 amito udisksd[2157]: Mounted /dev/sr0 at /run/media/jonrysh/我的光碟 on behalf of uid 1000 Definitely made in China.
I would like to try a different adapter(dongle). *Can anyone recommend one?* There are a lot of choices, and the ones recommended (for M$ Windows) may not be the best for Linux.
I have this one https://tinyurl.com/ykymt57u (bought here in Taiwan) and it works just fine. Auto-connects when I power on my Sony speakers. Never disconnects. Before using the TP-Link I was using an adapter from Buffalo. Forgot why I changed.
I think any adapter with Cambridge Silicon Radio CSR8510 will work just fine.
The only thing I've found, info is more than a year old, is that not all V5.0 bluetooth adapters are supported in linux.
-- On Facebook it is called Vaguebooking.
On Sun, 2021-10-10 at 08:38 +0800, Ed Greshko wrote:
On 10/10/2021 07:48, Jonathan Ryshpan wrote:
On Sat, 2021-10-09 at 06:40 +0800, Ed Greshko wrote:
What results do you get if you boot your system with the USB speakers disconnected and the connect them once the system is fully booted?
I was listening to some audio when the sound stopped; AudioEngine had disappeared from the list of output devices. A log extract is attached (Audio-Crash.txt).
There may be a problem with the cable. The speakers are attached to the computer with a USB extender cable, which may not give as good a connection as is needed. So I moved things around and connected the speakers without the extender; we'll see if things get better. A log extract is attached (Audio-Restore- ShortCable.txt).
Oh, I never did have much luck with USB extender cables. FWIW, I don't use USB devices all that much. Other than dongles I only have an HDMI capture device hooked to USB.
With speakers, I use Bluetooth. I find them more versatile.
Everything is working now. A new USB cable long enough to reach from the speakers to the computer without an extension has made USB reliable. And a new Bluetooth dongle from tp-link has made Bluetooth reliable. And there have been some upgrades to pipewire, which may have affected things. The sound using USB seems slightly superior to that using Bluetooth.
On 2021-10-12 10:15, Jonathan Ryshpan wrote:
The Bluetooth adapter, an old Belkin USB dongle, produces this log message when recognized: Oct 09 22:01:10 amito udisksd[2157]: Mounted /dev/sr0 at /run/media /jonrysh/我的光碟 on behalf of uid 1000
It pretends to be a cdrom drive to provide (Windows) drivers. You might see a USB modeswitch message after that (not sure if that is logged or not).
On 2021-10-16 03:32, Jonathan Ryshpan wrote:
things. The sound using USB seems slightly superior to that using Bluetooth.
Bluetooth audio uses compression. There isn't enough bandwidth for raw audio.
On 17/10/2021 05:55, Samuel Sieb wrote:
On 2021-10-16 03:32, Jonathan Ryshpan wrote:
things. The sound using USB seems slightly superior to that using Bluetooth.
Bluetooth audio uses compression. There isn't enough bandwidth for raw audio.
I have a NAS which contains all my music.
My Fedora 34 system accesses the NAS via a wired connection.
My Samsung phone accesses the NAS via Wifi.
Both use Bluetooth to connect to the same speakers.
Sound quality from the Samsung is better than from Fedora. When I have time I'll try to determine why that is so. I'm sorta suspecting pipewire. But I have to find the instructions for switching between pipewire and pulseaudio.
-- On Facebook it is called Vaguebooking.
On 2021-10-16 16:46, Ed Greshko wrote:
On 17/10/2021 05:55, Samuel Sieb wrote:
On 2021-10-16 03:32, Jonathan Ryshpan wrote:
things. The sound using USB seems slightly superior to that using Bluetooth.
Bluetooth audio uses compression. There isn't enough bandwidth for raw audio.
I have a NAS which contains all my music.
My Fedora 34 system accesses the NAS via a wired connection.
My Samsung phone accesses the NAS via Wifi.
Both use Bluetooth to connect to the same speakers.
Sound quality from the Samsung is better than from Fedora. When I have time I'll try to determine why that is so. I'm sorta suspecting pipewire. But I have to find the instructions for switching between pipewire and pulseaudio.
There are multiple compression methods and the better ones have patents. Try installing "pipewire-codec-aptx" from rpmfusion and see if that makes a difference. There's a similar one called "pulseaudio-module-bluetooth-freeworld" for pulseaudio.
On Sun, 2021-10-17 at 07:46 +0800, Ed Greshko wrote:
I have a NAS which contains all my music.
My Fedora 34 system accesses the NAS via a wired connection.
My Samsung phone accesses the NAS via Wifi.
Both use Bluetooth to connect to the same speakers.
Sound quality from the Samsung is better than from Fedora. When I have time I'll try to determine why that is so.
The codecs and hardware will have an effect.
Two differently engineered codecs for the same type of data can have different results (just the same as, long ago, some MP3 encoders were noticeably inferior to others). Likewise with the audio hardware. Given exactly the same data, some do a better job of turning into audio.
There's also a difference between "better" and "nicer." From a purists point of view, better means *accurate* reproduction. Another person thinks it's nicer if they boost the bass &/or treble. That's *inaccurate*, and the problems compound when you use several things in tandem that have been tweaked. I have a pair of headphones with very boosted bass that turn good music into whumpy sound, they don't need something else doctoring the sound, as well.
On 17/10/2021 11:39, Tim via users wrote:
On Sun, 2021-10-17 at 07:46 +0800, Ed Greshko wrote:
I have a NAS which contains all my music.
My Fedora 34 system accesses the NAS via a wired connection.
My Samsung phone accesses the NAS via Wifi.
Both use Bluetooth to connect to the same speakers.
Sound quality from the Samsung is better than from Fedora. When I have time I'll try to determine why that is so.
The codecs and hardware will have an effect.
The codecs didn't improve matters. After testing various SW I'm leaning towards HW.
There's also a difference between "better" and "nicer." From a purists point of view, better means *accurate* reproduction. Another person thinks it's nicer if they boost the bass &/or treble. That's *inaccurate*, and the problems compound when you use several things in tandem that have been tweaked. I have a pair of headphones with very boosted bass that turn good music into whumpy sound, they don't need something else doctoring the sound, as well.
I should have defined the issue better.
The Fedora system produces sound with, hard to describe, some "stuttering". So, it gives the impression of clicks, but there aren't any.
I don't often use the Fedora system for music, so not sure if it is worth trying fix it.
-- On Facebook it is called Vaguebooking.
On Sun, 2021-10-17 at 12:58 +0800, Ed Greshko wrote:
The Fedora system produces sound with, hard to describe, some "stuttering". So, it gives the impression of clicks, but there aren't any.
I wonder if that's a buffering or a sample rate conversion issue. For instance, if one piece of the puzzle decides it's going to convert 44.1 to 48 kHz samples (though it could have just passed it through, as-is) it might introduce noticeable distortions.
I find it very annoying to watch movies with music on one of our TV channels, SBS. The entire way through there's a burble to the audio, that sounds like someone's playing an audio file at 101% speed, and it hiccups on the dropped samples (very similar to the effect you got when fast-forwarding through an audio compact disc, back in the days when we used compact disc players). My guess might be that they're speeding up and slowing down non-50 Hertz video, to 50 Hertz frame rates, and handling the audio very badly.
In this day and age, it's probably that all TV stations could show any program in its native format, and let the receiver switch modes. Though commercial stations wouldn't like the glitches between programs and commercials.
I don't often use the Fedora system for music, so not sure if it is worth trying fix it.
There is always that... However, if you got it working nicer, maybe you'd use it more.
On 17/10/2021 18:37, Tim via users wrote:
On Sun, 2021-10-17 at 12:58 +0800, Ed Greshko wrote:
The Fedora system produces sound with, hard to describe, some "stuttering". So, it gives the impression of clicks, but there aren't any.
I wonder if that's a buffering or a sample rate conversion issue. For instance, if one piece of the puzzle decides it's going to convert 44.1 to 48 kHz samples (though it could have just passed it through, as-is) it might introduce noticeable distortions.
OK, I've "fixed" the problem.
I'm using KDE and I went to System Settings-->Hardware-->Audio-->Configure and for the profile for the Bluetooth speaker output I picked
High Fidelity Playback (A2DP Sink, codec ACC)
and now everything is great!
-- On Facebook it is called Vaguebooking.
On Sun, 2021-10-17 at 07:46 +0800, Ed Greshko wrote:
Sound quality from the Samsung is better than from Fedora. When I have time I'll try to determine why that is so. I'm sorta suspecting pipewire. But I have to find the instructions for switching between pipewire and pulseaudio.
I had to do this a couple of times while investigating the AudioEngine speakers. Here's what worked for my system:
To change from pulseaudio to pipewire: dnf swap --allowerasing pulseaudio pipewire-pulseaudio To change from pipewire to pulseaudio: dnf swap --allowerasing pipewire-pulseaudio pulseaudio
On 17/10/2021 22:33, Jonathan Ryshpan wrote:
On Sun, 2021-10-17 at 07:46 +0800, Ed Greshko wrote:
Sound quality from the Samsung is better than from Fedora. When I have time I'll try to determine why that is so. I'm sorta suspecting pipewire. But I have to find the instructions for switching between pipewire and pulseaudio.
I had to do this a couple of times while investigating the AudioEngine speakers. Here's what worked for my system:
To change from pulseaudio to pipewire: dnf swap --allowerasing pulseaudio pipewire-pulseaudio To change from pipewire to pulseaudio: dnf swap --allowerasing pipewire-pulseaudio pulseaudio
Thanks.... I did find that. And it wasn't the problem. See my other reply.
-- On Facebook it is called Vaguebooking.
On Sun, 2021-10-17 at 19:50 +0800, Ed Greshko wrote:
On 17/10/2021 18:37, Tim via users wrote:
On Sun, 2021-10-17 at 12:58 +0800, Ed Greshko wrote:
The Fedora system produces sound with, hard to describe, some "stuttering". So, it gives the impression of clicks, but there aren't any.
I wonder if that's a buffering or a sample rate conversion issue. For instance, if one piece of the puzzle decides it's going to convert 44.1 to 48 kHz samples (though it could have just passed it through, as-is) it might introduce noticeable distortions.
OK, I've "fixed" the problem.
I'm using KDE and I went to System Settings-->Hardware-->Audio--
Configure and for the profile for the Bluetooth speaker output I
picked High Fidelity Playback (A2DP Sink, codec ACC) and now everything is great!
Interesting. The choices on my system are much less informative. For AudioEngine 2+ Device Profile: * Off * Analog Stereo Output * Digital Stereo (E958) Output <=== * Pro Audio Speaker Placement and Testing * AudioEngine 2+ Digital Stereo (E958) <=== * Build in Audio Analog Stereo Right now the marked choices are active, the sound is good, and the connection hasn't been dropped for the last day.
Does anyone know what these choices mean? In particular, what is "Digital Stereo (E958)"?
On 18/10/2021 04:04, Jonathan Ryshpan wrote:
On Sun, 2021-10-17 at 19:50 +0800, Ed Greshko wrote:
On 17/10/2021 18:37, Tim via users wrote:
On Sun, 2021-10-17 at 12:58 +0800, Ed Greshko wrote:
The Fedora system produces sound with, hard to describe, some "stuttering". So, it gives the impression of clicks, but there aren't any.
I wonder if that's a buffering or a sample rate conversion issue. For instance, if one piece of the puzzle decides it's going to convert 44.1 to 48 kHz samples (though it could have just passed it through, as-is) it might introduce noticeable distortions.
OK, I've "fixed" the problem.
I'm using KDE and I went to System Settings-->Hardware-->Audio-->Configure and for the profile for the Bluetooth speaker output I picked High Fidelity Playback (A2DP Sink, codec ACC) and now everything is great!
Interesting. The choices on my system are much less informative. For AudioEngine 2+ Device Profile:
- Off
- Analog Stereo Output
- Digital Stereo (E958) Output <===
- Pro Audio
Speaker Placement and Testing
- AudioEngine 2+ Digital Stereo (E958) <===
- Build in Audio Analog Stereo
Right now the marked choices are active, the sound is good, and the connection hasn't been dropped for the last day.
Does anyone know what these choices mean? In particular, what is "Digital Stereo (E958)"?
Maybe the manual for the speaker would have some insight?
FWIW, the manual for mine indicated that " Optimal codec is automatically selected from AAC, LDAC, and SBC." LDAC in System Settings was the one causing bad results.
In thinking about it, it sorta sound like talking in front of an electric fan.
-- On Facebook it is called Vaguebooking.
On 18/10/21 09:39, Ed Greshko wrote:
On 18/10/2021 04:04, Jonathan Ryshpan wrote:
On Sun, 2021-10-17 at 19:50 +0800, Ed Greshko wrote:
On 17/10/2021 18:37, Tim via users wrote:
On Sun, 2021-10-17 at 12:58 +0800, Ed Greshko wrote:
The Fedora system produces sound with, hard to describe, some "stuttering". So, it gives the impression of clicks, but there aren't any.
I wonder if that's a buffering or a sample rate conversion issue. For instance, if one piece of the puzzle decides it's going to convert 44.1 to 48 kHz samples (though it could have just passed it through, as-is) it might introduce noticeable distortions.
OK, I've "fixed" the problem.
I'm using KDE and I went to System Settings-->Hardware-->Audio-->Configure and for the profile for the Bluetooth speaker output I picked High Fidelity Playback (A2DP Sink, codec ACC) and now everything is great!
Interesting. The choices on my system are much less informative. For AudioEngine 2+ Device Profile:
* Off * Analog Stereo Output * Digital Stereo (E958) Output <=== * Pro Audio
Speaker Placement and Testing
* AudioEngine 2+ Digital Stereo (E958) <=== * Build in Audio Analog Stereo
Right now the marked choices are active, the sound is good, and the connection hasn't been dropped for the last day.
Does anyone know what these choices mean? In particular, what is "Digital Stereo (E958)"?
Maybe the manual for the speaker would have some insight?
FWIW, the manual for mine indicated that " Optimal codec is automatically selected from AAC, LDAC, and SBC." LDAC in System Settings was the one causing bad results.
In thinking about it, it sorta sound like talking in front of an electric fan.
I have the same issue as Jonathan, in that all I see are: Off Analog Stereo Duplex Analog Stereo Output Analog Stereo Input But I am running Fedora in a Vmware VM using vmware's built in Audio interface. The device it sees is ES1371/ES1373/Creative Labs CT2518(Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]. I think that selection came from Pulseaudio as System Settings->Hardware->Audio doesn't provide me with any option to select different Hardware if I want to. I'm using Logitech 7.1 headphones and with these settings usage of the volume control on the headphones is a bit dodgy at times in that it doesn't always actually control the volume. The profile options change if I disconnect the Logitech G533 headphones from the host and connect them to the VM, but I don't get anything like the options that Ed mentioned, but that may also be because Fedora doesn't seem to have direct support for those headphones (at least the last time I looked, and I haven't looked for a while) and Logitech don't provide any interfaces for Linux like they do for windows. Since moving F34 I haven't tried getting my "water fountain" bluetooth speakers working again with the Bluetooth 4.0 dongle as I found it very fiddly to actually get working and the usage of the speakers doesn't warrant the effort in setting it up again.
regards, Steve
-- On Facebook it is called Vaguebooking. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 27/10/2021 06:46, Stephen Morris wrote:
Maybe the manual for the speaker would have some insight?
FWIW, the manual for mine indicated that " Optimal codec is automatically selected from AAC, LDAC, and SBC." LDAC in System Settings was the one causing bad results.
In thinking about it, it sorta sound like talking in front of an electric fan.
I have the same issue as Jonathan, in that all I see are: Off Analog Stereo Duplex Analog Stereo Output Analog Stereo Input But I am running Fedora in a Vmware VM using vmware's built in Audio interface. The device it sees is ES1371/ES1373/Creative Labs CT2518(Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]. I think that selection came from Pulseaudio as System Settings->Hardware->Audio doesn't provide me with any option to select different Hardware if I want to. I'm using Logitech 7.1 headphones and with these settings usage of the volume control on the headphones is a bit dodgy at times in that it doesn't always actually control the volume. The profile options change if I disconnect the Logitech G533 headphones from the host and connect them to the VM, but I don't get anything like the options that Ed mentioned, but that may also be because Fedora doesn't seem to have direct support for those headphones (at least the last time I looked, and I haven't looked for a while) and Logitech don't provide any interfaces for Linux like they do for windows. Since moving F34 I haven't tried getting my "water fountain" bluetooth speakers working again with the Bluetooth 4.0 dongle as I found it very fiddly to actually get working and the usage of the speakers doesn't warrant the effort in setting it up again.
LDAC, AAC, and SBC are options you'd see if the audio HW was bluetooth. In your case, it isn't. If you want to use BT in a VM you'd need a BT dongle and you would have to user USB Redirection to give the VM access to the HW.
I don't know much about the G533 headset but doubt there are Linux drivers for it. It also connects via the Unifying Receiver from Logitech, yes?
-- On Facebook it is called Vaguebooking.
On 10/26/21 15:46, Stephen Morris wrote:
I have the same issue as Jonathan, in that all I see are: Off Analog Stereo Duplex Analog Stereo Output Analog Stereo Input But I am running Fedora in a Vmware VM using vmware's built in Audio interface. The device it sees is ES1371/ES1373/Creative Labs CT2518(Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]. I think that selection came from Pulseaudio as System Settings->Hardware->Audio doesn't provide me with any option to select different Hardware if I want to. I'm using Logitech 7.1 headphones and with these settings usage of the volume control on the headphones is a bit dodgy at times in that it doesn't always actually control the volume. The profile options change if I disconnect the Logitech G533 headphones from the host and connect them to the VM, but I don't get anything like the options that Ed mentioned, but that may also be because Fedora doesn't seem to have direct support for those headphones (at least the last time I looked, and I haven't looked for a while) and Logitech don't provide any interfaces for Linux like they do for windows. Since moving F34 I haven't tried getting my "water fountain" bluetooth speakers working again with the Bluetooth 4.0 dongle as I found it very fiddly to actually get working and the usage of the speakers doesn't warrant the effort in setting it up again.
If it's in a VM, then it can only see the virtual device that the VM host is providing which is going to be completely different from the real device and won't likely have many options. Any specific control of the real device has to be done in the host OS.
On 27/10/21 10:04, Ed Greshko wrote:
On 27/10/2021 06:46, Stephen Morris wrote:
Maybe the manual for the speaker would have some insight?
FWIW, the manual for mine indicated that " Optimal codec is automatically selected from AAC, LDAC, and SBC." LDAC in System Settings was the one causing bad results.
In thinking about it, it sorta sound like talking in front of an electric fan.
I have the same issue as Jonathan, in that all I see are: Off Analog Stereo Duplex Analog Stereo Output Analog Stereo Input But I am running Fedora in a Vmware VM using vmware's built in Audio interface. The device it sees is ES1371/ES1373/Creative Labs CT2518(Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]. I think that selection came from Pulseaudio as System Settings->Hardware->Audio doesn't provide me with any option to select different Hardware if I want to. I'm using Logitech 7.1 headphones and with these settings usage of the volume control on the headphones is a bit dodgy at times in that it doesn't always actually control the volume. The profile options change if I disconnect the Logitech G533 headphones from the host and connect them to the VM, but I don't get anything like the options that Ed mentioned, but that may also be because Fedora doesn't seem to have direct support for those headphones (at least the last time I looked, and I haven't looked for a while) and Logitech don't provide any interfaces for Linux like they do for windows. Since moving F34 I haven't tried getting my "water fountain" bluetooth speakers working again with the Bluetooth 4.0 dongle as I found it very fiddly to actually get working and the usage of the speakers doesn't warrant the effort in setting it up again.
LDAC, AAC, and SBC are options you'd see if the audio HW was bluetooth. In your case, it isn't. If you want to use BT in a VM you'd need a BT dongle and you would have to user USB Redirection to give the VM access to the HW.
I don't know much about the G533 headset but doubt there are Linux drivers for it. It also connects via the Unifying Receiver from Logitech, yes?
Yes, it does connect via the Unifying Receiver, which is only being used for the headphones, I have a Logitech G910 keyboard but that is direct USB connected, and I have a Logitech Pro wireless mouse that is connected and battery charging through the Logitech Powerplay mouse mat that is direct USB connected. If I direct connect the headphones to the vm, pulseaudio provides more audio selection options including the ability for 7.1 surround sound which the headphones are supposed to emulate. I should probably have a look at setting up the bluetooth speakers again by connecting the dongle to the vm and activating the facilities, to see if I get the audio issues you mentioned, as I think last time I connected them, the audio was very stuttery.
regards, Steve
-- On Facebook it is called Vaguebooking. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 27/10/21 10:04, Samuel Sieb wrote:
On 10/26/21 15:46, Stephen Morris wrote:
I have the same issue as Jonathan, in that all I see are: Off Analog Stereo Duplex Analog Stereo Output Analog Stereo Input But I am running Fedora in a Vmware VM using vmware's built in Audio interface. The device it sees is ES1371/ES1373/Creative Labs CT2518(Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]. I think that selection came from Pulseaudio as System Settings->Hardware->Audio doesn't provide me with any option to select different Hardware if I want to. I'm using Logitech 7.1 headphones and with these settings usage of the volume control on the headphones is a bit dodgy at times in that it doesn't always actually control the volume. The profile options change if I disconnect the Logitech G533 headphones from the host and connect them to the VM, but I don't get anything like the options that Ed mentioned, but that may also be because Fedora doesn't seem to have direct support for those headphones (at least the last time I looked, and I haven't looked for a while) and Logitech don't provide any interfaces for Linux like they do for windows. Since moving F34 I haven't tried getting my "water fountain" bluetooth speakers working again with the Bluetooth 4.0 dongle as I found it very fiddly to actually get working and the usage of the speakers doesn't warrant the effort in setting it up again.
If it's in a VM, then it can only see the virtual device that the VM host is providing which is going to be completely different from the real device and won't likely have many options. Any specific control of the real device has to be done in the host OS.
The control of the real device is being done via the Logitech windows driver application and in the vm, when I use the volume control on the headphones sometimes I get a volume level widget displayed on the screen and sometimes I don't, and sometimes using the headphones volume control manipulates the volume levels and sometimes it does nothing. Even when the volume is at 100% it is sometimes hard to hear the audio, and it get better if I direct connect the headphones to the vm.
regards, Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 27/10/2021 18:41, Stephen Morris wrote:
On 27/10/21 10:04, Samuel Sieb wrote:
On 10/26/21 15:46, Stephen Morris wrote:
I have the same issue as Jonathan, in that all I see are: Off Analog Stereo Duplex Analog Stereo Output Analog Stereo Input But I am running Fedora in a Vmware VM using vmware's built in Audio interface. The device it sees is ES1371/ES1373/Creative Labs CT2518(Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]. I think that selection came from Pulseaudio as System Settings->Hardware->Audio doesn't provide me with any option to select different Hardware if I want to. I'm using Logitech 7.1 headphones and with these settings usage of the volume control on the headphones is a bit dodgy at times in that it doesn't always actually control the volume. The profile options change if I disconnect the Logitech G533 headphones from the host and connect them to the VM, but I don't get anything like the options that Ed mentioned, but that may also be because Fedora doesn't seem to have direct support for those headphones (at least the last time I looked, and I haven't looked for a while) and Logitech don't provide any interfaces for Linux like they do for windows. Since moving F34 I haven't tried getting my "water fountain" bluetooth speakers working again with the Bluetooth 4.0 dongle as I found it very fiddly to actually get working and the usage of the speakers doesn't warrant the effort in setting it up again.
If it's in a VM, then it can only see the virtual device that the VM host is providing which is going to be completely different from the real device and won't likely have many options. Any specific control of the real device has to be done in the host OS.
The control of the real device is being done via the Logitech windows driver application and in the vm, when I use the volume control on the headphones sometimes I get a volume level widget displayed on the screen and sometimes I don't, and sometimes using the headphones volume control manipulates the volume levels and sometimes it does nothing. Even when the volume is at 100% it is sometimes hard to hear the audio, and it get better if I direct connect the headphones to the vm.
I'm a bit confused based on the last 2 of your posts.
Is your VM a Fedora VM or a Windows VM?
-- On Facebook it is called Vaguebooking.
On 27/10/21 22:09, Ed Greshko wrote:
On 27/10/2021 18:41, Stephen Morris wrote:
On 27/10/21 10:04, Samuel Sieb wrote:
On 10/26/21 15:46, Stephen Morris wrote:
I have the same issue as Jonathan, in that all I see are: Off Analog Stereo Duplex Analog Stereo Output Analog Stereo Input But I am running Fedora in a Vmware VM using vmware's built in Audio interface. The device it sees is ES1371/ES1373/Creative Labs CT2518(Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]. I think that selection came from Pulseaudio as System Settings->Hardware->Audio doesn't provide me with any option to select different Hardware if I want to. I'm using Logitech 7.1 headphones and with these settings usage of the volume control on the headphones is a bit dodgy at times in that it doesn't always actually control the volume. The profile options change if I disconnect the Logitech G533 headphones from the host and connect them to the VM, but I don't get anything like the options that Ed mentioned, but that may also be because Fedora doesn't seem to have direct support for those headphones (at least the last time I looked, and I haven't looked for a while) and Logitech don't provide any interfaces for Linux like they do for windows. Since moving F34 I haven't tried getting my "water fountain" bluetooth speakers working again with the Bluetooth 4.0 dongle as I found it very fiddly to actually get working and the usage of the speakers doesn't warrant the effort in setting it up again.
If it's in a VM, then it can only see the virtual device that the VM host is providing which is going to be completely different from the real device and won't likely have many options. Any specific control of the real device has to be done in the host OS.
The control of the real device is being done via the Logitech windows driver application and in the vm, when I use the volume control on the headphones sometimes I get a volume level widget displayed on the screen and sometimes I don't, and sometimes using the headphones volume control manipulates the volume levels and sometimes it does nothing. Even when the volume is at 100% it is sometimes hard to hear the audio, and it get better if I direct connect the headphones to the vm.
I'm a bit confused based on the last 2 of your posts.
Is your VM a Fedora VM or a Windows VM?
Hi Ed, my vm is Vmware Player on a Windows 10 host. It has also just had an update to provide Windows 11 support, which I also assume means it now supports UEFI even though there is not an explicit setting for it. UEFI support raises some questions about how Fedora installs are done, but that is a question for another thread.
regards, Steve
-- On Facebook it is called Vaguebooking. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 30/10/2021 09:08, Stephen Morris wrote:
Is your VM a Fedora VM or a Windows VM?
Hi Ed, my vm is Vmware Player on a Windows 10 host. It has also just had an update to provide Windows 11 support, which I also assume means it now supports UEFI even though there is not an explicit setting for it. UEFI support raises some questions about how Fedora installs are done, but that is a question for another thread.
Sorry, I'm still a bit confused.
It sounds to me like you're running Windows 11 on bare metal hardware. I say this since you wrote "Windows 10 host" It then sounds to me that your running Fedora as a guest in Vmware Player.
Is that your configuration?
-- On Facebook it is called Vaguebooking.
On 30/10/21 16:05, Ed Greshko wrote:
On 30/10/2021 09:08, Stephen Morris wrote:
Is your VM a Fedora VM or a Windows VM?
Hi Ed, my vm is Vmware Player on a Windows 10 host. It has also just had an update to provide Windows 11 support, which I also assume means it now supports UEFI even though there is not an explicit setting for it. UEFI support raises some questions about how Fedora installs are done, but that is a question for another thread.
Sorry, I'm still a bit confused.
It sounds to me like you're running Windows 11 on bare metal hardware. I say this since you wrote "Windows 10 host" It then sounds to me that your running Fedora as a guest in Vmware Player.
Is that your configuration?
Hi Ed, yes, Fedora is a guest in Vmware Player, with Vmware Player running on a Windows 10 host. The Vmware Player upgrade I was referring to has now provided Vmware player (apparently) with the ability to run Windows 11 as a guest, which previously there appeared to be no way to run Windows 11 as a guest. I have the windows 11 installer on a usb disk, so I could install Windows 10 as a guest and then try upgrading to Windows 11. Virtualbox, on a Windows 10 host, already had the support for UEFI (it is a selectable option in the Virtualbox configuration), and to me a stupid Windows 11 support implementation, in that if I run Virtualbox in windowed mode, Windows 11 says the environment is not suitable for installation, but if I switch Virtualbox into Full Screen mode, then Windows 11 installs quite happily. I don't know if the fact that on my system the tpm (I think that is what the hardware is called) is implemented in the motherboard bios rather than a physical piece of hardware, and I don't understand what the difference between windowed mode and full screen mode is that would allow that "device" to be detected in one and not the other.
regards, Steve
-- On Facebook it is called Vaguebooking. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 31/10/2021 09:11, Stephen Morris wrote:
Hi Ed, yes, Fedora is a guest in Vmware Player, with Vmware Player running on a Windows 10 host
OK. Now I understand your configuration and how it applies in the context of Audio.
-- On Facebook it is called Vaguebooking.
On 2021-10-30 18:11, Stephen Morris wrote:
On 30/10/21 16:05, Ed Greshko wrote:
On 30/10/2021 09:08, Stephen Morris wrote:
Is your VM a Fedora VM or a Windows VM?
Hi Ed, my vm is Vmware Player on a Windows 10 host. It has also just had an update to provide Windows 11 support, which I also assume means it now supports UEFI even though there is not an explicit setting for it. UEFI support raises some questions about how Fedora installs are done, but that is a question for another thread.
Sorry, I'm still a bit confused.
It sounds to me like you're running Windows 11 on bare metal hardware. I say this since you wrote "Windows 10 host" It then sounds to me that your running Fedora as a guest in Vmware Player.
Is that your configuration?
Hi Ed, yes, Fedora is a guest in Vmware Player, with Vmware Player running on a Windows 10 host. The Vmware Player upgrade I was referring to has now provided Vmware player (apparently) with the ability to run Windows 11 as a guest, which previously there appeared to be no way to run Windows 11 as a guest. I have the windows 11 installer on a usb disk, so I could install Windows 10 as a guest and then try upgrading to Windows 11. Virtualbox, on a Windows 10 host, already had the support for UEFI (it is a selectable option in the Virtualbox configuration), and to me a stupid Windows 11 support implementation, in that if I run Virtualbox in windowed mode, Windows 11 says the environment is not suitable for installation, but if I switch Virtualbox into Full Screen mode, then Windows 11 installs quite happily. I don't know if the fact that on my system the tpm (I think that is what the hardware is called) is implemented in the motherboard bios rather than a physical piece of hardware, and I don't understand what the difference between windowed mode and full screen mode is that would allow that "device" to be detected in one and not the other.
It's probably not the TPM, but more likely that the screen resolution is too low. Unless you have some indication that it is the TPM that it's complaining about.
On 31/10/2021 12:17, Samuel Sieb wrote:
It's probably not the TPM, but more likely that the screen resolution is too low. Unless you have some indication that it is the TPM that it's complaining about.
FWIW, it seems this is getting off on a tangent from the original intention of the post.
I would suggest that if this is important to Steve he should start a new post/thread to make it easier to track it and find it later if need be.
-- On Facebook it is called Vaguebooking.
On 31/10/21 15:25, Ed Greshko wrote:
On 31/10/2021 12:17, Samuel Sieb wrote:
It's probably not the TPM, but more likely that the screen resolution is too low. Unless you have some indication that it is the TPM that it's complaining about.
FWIW, it seems this is getting off on a tangent from the original intention of the post.
I would suggest that if this is important to Steve he should start a new post/thread to make it easier to track it and find it later if need be.
Hi Ed, you are right, it is getting off on a tangent to the original intent of the thread. I'm not that concerned about the Virtualbox functionality, so we can let that drop.
regards, Steve
-- On Facebook it is called Vaguebooking. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
-
Ed Greshko -
Jonathan Ryshpan -
Samuel Sieb -
Stephen Morris -
Tim