jmontleon / pixelbook-fedora

How to install Fedora on a Pixelbook with reasonable results
60 stars 12 forks source link

Sound broken with kernel 6.1 #51

Closed jmontleon closed 1 year ago

jmontleon commented 1 year ago

Audio is broken in 6.1 again.

joeknock90 commented 1 year ago

I'm coming back to this after having switched daily driver laptops for a while.

I'm not sure what I'm doing wrong here, but after a fresh install of both Fedora and Arch, i still have no sound. I've run the playbook on fedora. Not sure what to do here. Only seemling relevant dmesg output is this, but I can provide more if needed.

[ 6.589056] rt5514 i2c-10EC5514:00: Device with ID register e0220042 is not rt5514

here's some kernel info

Linux pixbook 6.2.7-300.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Mar 17 16:02:49 UTC 2023 x86_64 GNU/Linux

saxa commented 1 year ago

Hi @joeknock90 , its good you mentioned it, as I am too with a non working sound on my Fedora install.

jmontleon commented 1 year ago

@joeknock90 can you open a new issue please and share the full dmesg output? I can't do anything with a couple lines.

Can you also tell me whether you are using the full uefi core boot or legacy? https://mrchromebox.tech/#bootmodes

I know @saxa is using legacy and seems to be having problems. It would be interesting to know if others having problems are using legacy or not.

I also haven't updated to Fedora 38, so could somehow be something there, though I'm on kernel 6.2.6 on Fedora 37 at the moment without a problem...

saxa commented 1 year ago

Hi @jmontleon , i still see these kernel traces in my dmesg and a lot of snd_ modules listed. I suspect that something makes go nuts pulseaudio. And this happens on slackware install too.

jmontleon commented 1 year ago

"...these kernel traces..." doesn't mean anything to me. Please open a new issue and share. There's no reason to spam a whole bunch of participants on an old issue for an old problem that's been resolved.

Also, please stick to one configuration when diagnosing. Flipping between Fedora, Slack, Arch, etc. between every post makes it impossible to determine what's going wrong. It's possible both systems/distros are affected by the same issue, but it's also entirely possible they are not.

joeknock90 commented 1 year ago

Also, please stick to one configuration when diagnosing.

I really wish I had read that a bit earlier....

I'll open a new issue.