I should point out that many “large enterprises” in the west dumped their Lenovo systems out of concerns that they might have built-in security holes. Many scientists using laptops in field work found that Thinkpads outlasted other brands in the hands of agricultural workers and were not happy when forced to switch to Dell and HP.
Now we have logoFAIL firmware attack. Apple and many Dell devices did protect logo images. Thinkpads did not. It is understandable that companies supplying system boards to multiple vendors would allow changes to logo images, but Lenovo doesn’t have that excuse.
The mushroom is between the G, H, & B keys on english keyboards and is out of the way of finger paths for all who use two-hand typing. Thus it works for more than 99.9% of all users. Your minority case is not likely to gain any attention. (it only would affect the decisions of the manufacturer anyway)
The fix – learn 2 handed typing.
Now, please stop your rant on this one issue that is a non-issue for almost everyone.
We understand you do not like it, but it is of non-concern to most of us and you have other choices so use what works for you and quit complaining.
I just expressed my opinion. I didn’t expect (let alone try) to implement any changes to anything.
Why do you take it so personally, my opinion that is?
Learn to type 2 handed? I can type faster than anyone I know, including professionally trained speed typists. I DO type 2 handed, maybe check your assumptions.
Just a quick question. My new Yoga 7 16" (Model 16ARP8) is now running Fedora 39.
Just running through some updates/extension installs etc (taken from this useful video: https://www.youtube.com/watch?v=RrRpXs2pkzg)
I tried to call a friend on Signal (to test hardware) yesterday and after a few attempts (VPN caused them i think) we finally got connected. Video worked fine and I could hear him fine, but he couldn’t hear me. Looks like the mic isn’t working even though it’s chosen in settings (only option).
Knowing I bought a machine which isn’t OOTB-Linux-Ready (i know, I may end up selling but hoping to avoid that as it’s ideal for my needs) - what should I do to verify what the problem is? i.e. whether it’s drivers or whatever. Last time I played with drivers it was Windows 95 and I was right clicking hardware profiles and checking driver against latest available, just to set the scene!
What steps should I take to investigate the microphone hardware/drivers and try to fix it?
Is the microphone listed in Settings/Sound/Input Devices?
Is your microphone listed in the LHDB as “not found”, “detected”, or “working” in other distributions?
If the mocrophone is detected but not working, the issue could be “privacy” settings for key-strokes that disable the microphone in “BIOS” or power management.
As with pther sound devices, the quick fix is a USB microphone – most are much better audio quality than you get from “built-in” microphones and reduce the number of times you have to repeat or rephrase what you just said (in online classes not everyone will let you know about poor sound quality, so it is important to test your setup one-on-one).
Thank you George.
I have just navigated as you suggested. No, under “Input” it says “Input Device - No input devices”.
Damn it!
I have struggled and started to understand LHDB at least at a basic level. I found my device, there are 4 probes:
Thing is… none of them seem to mention microphone. I searched every probe, not one instance of “microphone” or “mic” in relation to microphone hardware.
Weird that the machine doens’t think it has one though, any advice very much appreciated.
I ran hw-probe as advised, I’d like to know how to do this (and curious to read it).
it said i had to install the utility to run it, so I agreed. It installed. I then ran hw-probe -all (it suggested that). I ran it and it says “reading logs … ok” and “Local probe path /root/HW_PROBE/LATEST/hw.info”
So next question, how do I “get” it, let alone read it
thanks
Sorry Alan, I’ve just found this page - Create a probe
I did as instructed and my probe has been uploaded to - (ha, wow, URLs in Terminal are hyperlinked, this really is the 1990s isnt it!)
Can I assume this is completely safe to share publicly. I note it said “Sanitized”, which I assume means yes, but just wanted to double check my drive encryption keys or wife’s underwear catalogue are not included for all to see.
PS - Been meaning to ask, what exactly is the difference between “detected” and “working”? I mean, obviously I know the literal meaning, but is “detected” a ‘bad’ result, meaning it won’t work?
Completely safe? Hmm. But, drive encryption keys are not exposed in those probes.
Detected is not a “bad” result. It means that this device is known to kernel. Even “failed” is not always a “bad” result. For example, here’s one of my old computers with “dreaded” BCM4312.[1] If You check the oldest probe (Feb 21, 2022) there’s a big row with failed device and additional explanation column. Since Ethernet adapter worked without any effort, I waited till (Mar 18, 2022) to fix Wi-Fi. Yes, lazy, and there were more important things for me to do.
Even “working” may not satisfy all use cases. Detected is the first step on the path to working, but that may require manual configuration, installing firmware updates, compiling drivers, etc. Microphones are often USB devices and will be detected, but there can be complications with “airplane mode” switches not properly recognized and handled in linux.
Probes are sanitized to omit details you wouldn’t want public, but if you are a target of TLA’s just knowing what make and model system you have may reveal a route to compromising your system.
Instead of using Signal, try if it works in simpler conditions, with something simple like gnome-sound-recorder (I guess You’ll have to install it first).
Thanks. I think I get the gist of what you mean, if I am not a hot target of a nation state or similar, sanitized is probably more than enough to preserve my privacy. I did google TLA but couldn’t find anything other than lung disease and airline diagnostics
hehe, yeah I know.
aah, the dreaded 3 letter agency stuff, yep I guessed roughly that. I can relax now, I already did my 20 yrs in the gulags and my record has been expunged
It, helps (output from pw-cli). It says that You have gnome settings open. Choose “Sound”, pick correct input device, move input volume slider to the right and see if the little bar (above Input device picker) reacts when You speak.
If You check the oldest probe (Feb 21, 2022) there’s a big row with failed device and additional explanation column. Since Ethernet adapter worked without any effort, I waited till (Mar 18, 2022) to fix Wi-Fi. Yes, lazy, and there were more important things for me to do.