Got a new asus zenbook 13 (um325u). Installed Fedora 34 and everything worked like a charm with kernel 5.11.12. After dnf upgrade (to kernel 5.14.9) got a black screen on reboot, tried to boot previous kernel (5.11.12) - keyboard and touchpad stopped working, I cannot decrypt the disk on boot. I am totally confused what's going on, does anybody have any ideas? I have performed a fresh install again and upgraded the kernel only (kernel, kernel-modules, kernel-core) and the problem reproduced with both kernels.
On 05/10/2021 12:09, Kseniya Blashchuk wrote:
Got a new asus zenbook 13 (um325u). Installed Fedora 34 and everything worked like a charm with kernel 5.11.12. After dnf upgrade (to kernel 5.14.9) got a black screen on reboot, tried to boot previous kernel (5.11.12) - keyboard and touchpad stopped working, I cannot decrypt the disk on boot. I am totally confused what's going on, does anybody have any ideas? I have performed a fresh install again and upgraded the kernel only (kernel, kernel-modules, kernel-core) and the problem reproduced with both kernels.
How do you unlock your luks boot disk? If with 'tpm' and automatically then I think package(s) *shim* might be the culprit if it/they change(upgrade) after luks device setup was done. Also BIOS down/upgrade can cause tpm auto-unlock fail, then in those cases manual passphare unlock and redo clevis-luks will be required. 5.14.9 on my laptop does not suffer from the problems you are experiencing.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
I am not sure about tpm or shim, I mean I cannot unlock because the keyboard stops working when I try to boot back to 5.11.12. With 5.14.9 it's just a black screen. The thing is that before I upgrade to 5.14.9 everything works well on 5.11.12, so kernel upgrade makes something with a previous kernel as well. I'll probably boot with a live cd and try to check the logs or maybe compare grub settings before and after upgrade.
On Tue, Oct 5, 2021 at 2:30 PM lejeczek via users < users@lists.fedoraproject.org> wrote:
On 05/10/2021 12:09, Kseniya Blashchuk wrote:
Got a new asus zenbook 13 (um325u). Installed Fedora 34 and everything worked like a charm with kernel 5.11.12. After dnf upgrade (to kernel 5.14.9) got a black screen on reboot, tried to boot previous kernel (5.11.12) - keyboard and touchpad stopped working, I cannot decrypt the disk on boot. I am totally confused what's going on, does anybody have any ideas? I have performed a fresh install again and upgraded the kernel only (kernel, kernel-modules, kernel-core) and the problem reproduced with both kernels.
How do you unlock your luks boot disk? If with 'tpm' and automatically then I think package(s) *shim* might be the culprit if it/they change(upgrade) after luks device setup was done. Also BIOS down/upgrade can cause tpm auto-unlock fail, then in those cases manual passphare unlock and redo clevis-luks will be required. 5.14.9 on my laptop does not suffer from the problems you are experiencing.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 05/10/2021 13:14, Kseniya Blashchuk wrote:
I am not sure about tpm or shim, I mean I cannot unlock because the keyboard stops working when I try to boot back to 5.11.12. With 5.14.9 it's just a black screen. The thing is that before I upgrade to 5.14.9 everything works well on 5.11.12, so kernel upgrade makes something with a previous kernel as well. I'll probably boot with a live cd and try to check the logs or maybe compare grub settings before and after upgrade.
On Tue, Oct 5, 2021 at 2:30 PM lejeczek via users users@lists.fedoraproject.org wrote:
On 05/10/2021 12:09, Kseniya Blashchuk wrote: > Got a new asus zenbook 13 (um325u). Installed Fedora 34 > and everything worked like a charm with kernel 5.11.12. > After dnf upgrade (to kernel 5.14.9) got a black screen on > reboot, tried to boot previous kernel (5.11.12) - keyboard > and touchpad stopped working, I cannot decrypt the disk on > boot. I am totally confused what's going on, does anybody > have any ideas? I have performed a fresh install again and > upgraded the kernel only (kernel, kernel-modules, > kernel-core) and the problem reproduced with both kernels. How do you unlock your luks boot disk? If with 'tpm' and automatically then I think package(s) *shim* might be the culprit if it/they change(upgrade) after luks device setup was done. Also BIOS down/upgrade can cause tpm auto-unlock fail, then in those cases manual passphare unlock and redo clevis-luks will be required. 5.14.9 on my laptop does not suffer from the problems you are experiencing. >
Grab Fedora 35 beta - it's in a shape good enough to use daily(will be released soon) ps. stick to mailing lists etiquette - replies go to the bottom (it's not just us two reading)
> _______________________________________________ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-leave@lists.fedoraproject.org > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Tue, 2021-10-05 at 14:06 +0100, lejeczek via users wrote:
unlock and redo clevis-luks will be required. 5.14.9 on my laptop does not suffer from the problems you are experiencing. >
Grab Fedora 35 beta - it's in a shape good enough to use daily(will be released soon) ps. stick to mailing lists etiquette - replies go to the bottom (it's not just us two reading)
It's also good netiquette to remove all the footer stuff when quoting, as it's going to be added again by the list manager.
poc
Thanks everyone for the answers and etiquette tips. Upgrade to 35 from working 34 resulted in black screen after reboot. Tried Fedora 35 live CD - keyboard did not work through the installation process so I could not set the encryption passphrase but I decided to proceed and see what happens next. I do not have any external keyboard at the moment to check with, tried screen keyboard but it did not appear for this input. The system booted well with everything working (kernel 5.14.0). It seems that dnf upgrade and kernel 5.14.9 did not break the system. I have also tried to install Fedora 34 without disk encryption and then performed dnf upgrade and everything was also fine. Not sure what I will do next, I have also an old dell xps 13 laptop with Fedora 34, now I'm a bit scared to upgrade to 5.14.9 and reboot it :). Probably I will try to encrypt the disk manually and see if it works or try to figure out what breaks the process.
On 05/10/2021 18:02, Kseniya Blashchuk wrote:
Thanks everyone for the answers and etiquette tips. Upgrade to 35 from working 34 resulted in black screen after reboot. Tried Fedora 35 live CD - keyboard did not work through the installation process so I could not set the encryption passphrase but I decided to proceed and see what happens next. I do not have any external keyboard at the moment to check with, tried screen keyboard but it did not appear for this input. The system booted well with everything working (kernel 5.14.0). It seems that dnf upgrade and kernel 5.14.9 did not break the system. I have also tried to install Fedora 34 without disk encryption and then performed dnf upgrade and everything was also fine. Not sure what I will do next, I have also an old dell xps 13 laptop with Fedora 34, now I'm a bit scared to upgrade to 5.14.9 and reboot it :). Probably I will try to encrypt the disk manually and see if it works or try to figure out what breaks the process.
What you (everybody really) should also do, in case you don't just yet, is do bugs submissions in Bugzilla. Check BIOS for updates. I have zero experience with Asus laptops but it's not unheard of some bits not fully working on new fancy hardware. Also, I hear Asus claim to have begun to treat Linux and its users seriously lately, so perhaps file a tech support request with Asus. (give them a test and let the list know what they said. Personally I'd hope Asus is better than Lenovo in this respect) Beside that external keyboard nothing as a temp workaround I can think of. Good luck. L.
-
Kseniya Blashchuk -
lejeczek -
Patrick O'Callaghan