I adore Fedor. I have been using the OS for more than 7 years. No alternatives. Everything works amazing!
I recently became the proud owner of the latest laptop Yoga Air 14s. One of the distinctive features is a very powerful sound subsystem, consisting of 6(!) speakers.
According to tradition, I installed Fedor 39, kernel 6.5.10 on it.
The system works almost perfectly. There is no sleep mode (the manufacturer promises to fix it in the new BIOS firmware version) and… sound! he’s gone!
I started looking on the Internet for a solution to this problem. I read a lot of discussions on various forums. But I couldn’t find any clear and easy-to-use advice.
Reddit - Dive into anything - the solution is described here, but I don’t understand how to apply it and it’s for Ubuntu.
As I understand from the above forums, there may be a solution to problems with sound in the 6.6 kernel version, but how can I check this?
I ask my beloved developers to pay attention to this problem.
I tried to install Fedor Rawhide, it says kernel 6.7 but there is no sound there either.
(the laptop comes with Windows and there is sound and it is incredibly cool, so the problem with the hard drive can be ruled out)
Ready to help with testing or providing additional information.
Could not resist! I installed kernel 6.6.1 from the week of testing (and sent the report).
I did everything in accordance with the instructions. The sound has appeared!!!
my launch config: ./alsa-controller -m 100 --src_hw hw:1
When it comes to comparing the sound on Win and Linux, Win is the undoubted winner
Volume adjustment is smoother, sound quality is better and more consistent.
On Linux it was quieter, and the bass rattled a little.
I think that in the next firmware all this will be improved.
Special HUGE thanks to Mr. Darin Peshev for the work done!
Who will build, do not forget after “cmake .” do "cmake --build . "
if I could work out how to do the above mentioned steps, do you guys think it would work on a Yoga 7 16ARP8?
Just got it, audio levels are very low (lower than phone) and really need to see if I can sort it or I may need to return laptop within return window. (Running Fedora from LiveUSB currently, if that matters). Thanks
That’s interesting thanks, and I did wonder about that. Trouble is, I have to ‘destroy’ this machine by overwriting Windows with Fedora, to find out!
I feel pretty stuck at the moment. I absolutely LOVE this machine (hardware wise, it’s gorgeous, and nice big screen which I want), but starting to feel I may be forced to return it and go back to the drawing board. It’s tablet/touch features make it ideal as it means my wife can use it as well and it will get more use from us in various ways.
My main concerns at the moment are BIOS updates (one due now, and future ones), and the sound. The sound I THINK will be resolvable, if not immediately then in the future, and I could use a bluetooth speaker or headphones if necessary. I’d rather that than return it! But wondering if it’s just as Linux friendly as many other Lenovo models.
P.S. - Maybe I am placing too much importance on BIOS updates, is it really that crucial? I have never thought about it in the past! (Which probably doesn’t mean anything!)
You can always shrink the windows parition and create a Fedora install on the shrunken partition, if all works as planned, kill windows if you wish and add that space to the Fedora install.
While Lenovo does target specific models for Fedora and Linux, they do try to keep things working even on systems which don’t target Linux. The biggest issue tends to be things like cameras which have no open source driver at all. They don’t tend to break things which are working, and if they do, they are good about trying to get a fix out.
You could boot from windows PE on a USB to do the bios updates from a windows environment. Thus not having windows installed becomes a moot point.
This is the source (one of many) for a bootable iso that could be placed on a ventoy usb stick (or on its own usb) for booting to a windows environment. Hirens Boot CD works great for me. https://www.hirensbootcd.org/download/
I did think about that idea (shrinking windows to install Fedora alongside). Trouble is, I haven’t the feintest clue how to do it! I did look into it but it seemed pretty complex so I was hoping to find an easier solution, but if needs must then I will have to give that a crack. Thanks
And my apologies, I just realised I was replying on a different thread here so I took it off topic slightly (BIOS). Re Audio would be VERY cool if a full install of Fedora already had some audio fixes. I don’t mind if it isn’t as good as the audio on Windows, so long as it’s usable. But if not, I hope to somehow learn how to apply the patches/fixes mentioned early on this thread.
Open the Windows disk administration utility, elect the C: drive, right click and select “shrink volume”. I would probably leave it at 25-30GB at the smallest. That should leave you with a good bit of “unallocated” space which is what you will install Fedora on.
Sorry, I didn’t spot this USB Booting | Hiren's BootCD PE
I will follow that guide, I’ll do it on Windows as none of this stuff ever plays nice on Mac. Thanks
I heard someone mention Fedora 39. Pretty sure my installer is for 38, not sure why as only deleted it in past week or two I think. Either way… what’s the general approach to updates? Is it best to go for the very latest all the time or, like some softwares, is it ‘safer’ to go with the older one for a while?
I am wondering if 39 might give me more chance of fixes/patches for audio stuff etc? Happy to stick with 38 if 39 isn’t “proven” yet.
The first few weeks after a new version is released there are usually a lot of updates done. After a month or so things tend to stabilize. On critical systems I try to run the older version until the newer one has the bugs shaken out so I wait a month or two after release before I update everything.
Since I have more than one machine I usually update one almost immediately, sometimes while still in Beta, so I can feel out the changes. Then when I am satisfied I upgrade everything.
If your install usb is F38 that is no issue. Simply install it as normal, then upgrade to the most recent software following which do the version upgrade to F39 and latest software.
install F38
upgrade F38 sudo dnf upgrade
upgrade to F39 sudo dnf system-upgrade --releasever=39 download
followed by sudo dnf system-upgrade reboot
The system is now fully updated to F39 with the latest package versions.
This is the way I and many others do the upgrades from version to version. My laptop has not had a fresh install since it was new with F33, and has been upgraded with each new release.
Superb thank you. I wondered how to do an upgrade to new version (either in CLI or ‘Software’).
I actually had to overwrite my F38 USB installer so I could make a Windows PE live installer. And I am pleased to say that after a heart-stopping moment where the phrases “bricked” came to mind, it did work (I think)! Bios now updated to latest version, and I proved I can do it so have confidence moving forward for any future BIOS udates (not that I will probably ever think to check for BIOS updates again!)
You’re a genius, thank you.
One small comment, every time I powered up the Yoga it would take me into a Windows welcome process where, after selecting language and keyboard type, it insisted on network connection. It was a big white screen. I forced a power down each time. Since updating the BIOS (I confirmed the later version number in BIOS menu), the screen looks different. It’s a blue screen which says “Why did my PC restart?”, and underneath: “There’s a problem thats keeping us from getting your PC ready to use, we think an update could help things get working again…”. It’s as if the machine thinks it had a bad shutdown and needs to recover/repair itself. Should I be nervous?
If Windows is screwed, I couldn’t care less! Just find it a bit suspicious, unless the updated BIOS changes this welcome screen/procedure, but can’t see how that’s the case as you know BIOS when you see it, and this looks very much like a Windows-generated screen.
Either way, I am sure Fedora will go on fine now. I may as well make a F39 installer now, would you agree? (or best to do F38 and update as you said above?)
Don’t be nervous.
The boot drive and bios are initially configured for windows. Since the bios is now different than when it was delivered it triggers that message from the initial boot sequence the OEM installed.
You are overthinking and installing fedora will eliminate those type messages.
Do the F39 install since it eliminates quite a bit of download and one version install. You only then need to do steps 1 & 2 above.
Thanks a million Jeff. Flashing F39 now. Onwards and upwards.
I knew about sudo dnf update and sudo dnf upgrade, not entirely sure of the difference but I do them both usually. Am I correct to assume ‘Software’ takes care of all that fully, or is there a bit more behind the terminal commands which makes it best to use those? If not, I will just do the updates via GUI.
thanks again, will be nice to be past this and on to playing with Fedora and getting my files on there.
You can use either the gui or dnf from the cli. (dnf upgrade & dnf update are exactly the same. One is an alias for the other)
Personally I prefer the cli since then I can see exactly what is being done and any error messages. The software gui hides all that.
