> I literally can't use my headphones without special OEM or Realtek software (forgot which) on Windows, and I can't use them at all on Linux because there's no equivalent.
If the problem is no output at all, it may be just a matter of toggling some HDA codec GPIO or EAPD pin to power up external amplifier chip, which can be done with hda-analyzer. But if it's some combo headphone/mic jack and detection doesn't work then I have no idea.
I am pretty sure it is not hardware problem since I am using it for development and do all kinds of crazy stuff for last half a year. :) The thing about windows - you get more support from hardware manufacturer, but you get screwed by the fact it is all proprietary and often stuff from one manufacturer is not working with software from different one. And due to closed source approach there is no way to peek into it to see if it can be fixed or there could be workaround.
Another gem from this fresh windows install - headphones will work only if I boot into Windows while headphones are plugged in. If I boot without headphones and then plug headphones after I log in - no sound in headphones :)
My point is - there are all kinds of bugs in all popular OSes. I bet MacOS have bunch of them too. You just getting used to ones. Like it is never a problem for me to fix a webcam in linux, but it frustrates me to download 600 megs of drivers software to get my video card functional. The same way OP really frustrated by broken webcam and not really concerned about windows needs to update drivers, constantly monitor for viruses, etc.
One thing I noted tho - most frustration with Ubuntu (or any really linux desktop) I see comes the fact that some particular hardware is not working. The same hardware often have problems on Windows platform. And more often than not drivers/software for this hardware are closed source with bugs which never get fixed (because manufacturer's business in selling hardware, not software.) So apparently we would not have most of these issues with any OS if software required to run hardware would be open sourced. This will never happen probably tho..
Try removing pulseaudio, if only temporarily. I know pulseaudio is one of the few linux things that actually does things based on headset jack detection. For all I know the driver on your system might be broken, or sending spurious inputs.
I have the same issue with Samsung earbuds on Linux. My solution was to get a nice webcam with a solid camera, or to use an external mic. Win-win -- good quality sound, video, and mic.
Huh. I had this happen on Linux, too. I chalked it up to PulseAudio getting lost with my multiple sound cards and connecting / disconnecting peripherals.
My major struggle in Linux (Ubuntu) is with audio.
1. I have an external USB microphone. Works fine (most of the time, see below), except it's always a default device for both input and output. I don't understand why. I expect my extrnal speakers to be the output source if nothing else is plugged in. I have to often manually change the output source.
2. Sometimes I want to use headphones. And sometimes when I plug them in, the output doesn't switch to the headphones. So I have to do it manually. Occasionally it still doesn't work and the sound continues playing through the speakers.
3. Happened to me a few times - my USB microphone disappears completely from the device list. Even though the light is on. Unplugging and replugging doesn't work either; only a complete reboot does.
I even have a custom bash command that restarts pulseaudio. I'm using it more often than I should.
Audio has always been a tough spot for Linux in my experience. That said, I also have problems with MacOS too so my problem might lie somewhere between my chair and keyboard.
When I use USB audio out in Linux, all kinds of bugs happen, including movies sometimes freezing for no reason in vlc and mpv (audio output can make movies pause?), and audio stopping permanently in some games until you restart them depending on turning on/off headphones and what not.
Using the 3.5mm output jack of the computer into a bluetooth transmitter works much better for me. 3.5mm does the one thing it should do, transmit the audio signal, without all kinds of unwanted software side effects, the PC has no clue what I do with my headphones and given the bugs mentioned above that's a good thing.
I wonder what's wrong with my system to have such bad USB audio experience :/
Yeah it seems isolated to some type of combo of hardware I have.
After I finish this next course I will try again with a different distro, and then see if my other USB mic that worked on the Chromebook (running native Linux) also works on my main machine.
Does the mic in your headphones work? Let me know the model, I'll check it out for myself.
reply