Microphone Not Working and Ethernet DHCP Issues on Linux Mint
Asked by
MellowPine47
I'm using a Lenovo LOQ 15 with Linux Mint Cinnamon. My Sennheiser HD569 microphone works normally in Windows 11, but in Linux it doesn't pick up my voice and only seems to register tapping on the microphone. I tried installing pavucontrol, adjusting the microphone boost, and changing the left/right input levels, but nothing helped. I'm also having intermittent Ethernet problems: my connection occasionally stops working, and I end up switching between DHCP and a manually assigned IP address. I initially suspected that my ISP's CGNAT or DHCP setup might be involved. What should I check for both issues?
Answers
Your ISP cannot change your computer’s MAC address remotely. A DHCP server can assign your machine a different IP address when a lease expires, but that usually should not require repeatedly switching between automatic and manual configuration. Check whether the Ethernet interface is actually disconnecting, whether NetworkManager is reporting DHCP errors, and whether the router or ISP equipment is renewing the lease properly. Avoid using a permanent manual IP unless you know it is outside the router’s DHCP range.
Reply to this answer
The distribution itself is not necessarily the cause, but testing a current Fedora release with GNOME or KDE could help determine whether the issue is specific to Mint, its kernel, or its audio and network packages. Fedora GNOME is a solid option if you want to try the GNOME desktop, though the interface and workflow are quite different from Cinnamon.
Reply to this answer
For the microphone, try a different headset or microphone first. If another one works, the problem may be the headset’s connector, jack wiring, or Linux’s audio profile rather than the microphone itself. In pavucontrol, also check that the correct input device and profile are selected and that the input meter responds when you speak.
MellowPine47: The headset works correctly in Windows, so I’m not sure whether it’s faulty. I’ll still test another headset and check the selected input profile.
Reply to this answer
Add your answer
Answers are reviewed before publication.
MellowPine47: I may have described the problem incorrectly. The ISP uses an unusual local network setup, and even their support staff have not been able to explain exactly what happens. I suspect it is related to their DHCP service.