On 20/10/2020 23.17, Pany wrote:
Thank you so much for guiding me!
On Tue, Oct 20, 2020 at 12:04 PM M. Vefa Bicakci <m.v.b@xxxxxxxxxx> wrote:
[Snipped by Vefa]
Pany, in the mean-time, could you add the following string to your kernel's
command line (i.e., via GRUB, or the actual boot-loader that you use) and
let us know whether it helps to *work around* this issue with the latest
versions of 5.8.y kernels?
module_blacklist=apple-mfi-fastcharge
And I also installed the official built kernel-5.8.15-201.fc32.x86_64.rpm [5].
Adding module_blacklist=apple-mfi-fastcharge to the GRUB entry did not
succeed in the kernel booting.
With following kernel cmdline, I captured the journal [6]:
kernel: Command line:
BOOT_IMAGE=(hd5,gpt3)/vmlinuz-5.8.15-201.fc32.x86_64
root=/dev/mapper/fedora_localhost--live-root ro
resume=/dev/mapper/fedora_localhost--live-swap
rd.lvm.lv=fedora_localhost-live/root
rd.luks.uuid=luks-65d9ed28-ea08-4ea5-a1dd-7b2b086f5e09
rd.lvm.lv=fedora_localhost-live/swap
module_blacklist=apple-mfi-fastcharge systemd.debug-shell=1
Hello Pany,
My apologies, the original kernel command line entry I mentioned was
incorrect; the module name needs to be specified with underscore characters
("_") instead of dash ("-") characters. Could you try the following as well?
module_blacklist=apple_mfi_fastcharge
Using this string in the kernel command line causes "modprobe apple-mfi-fastcharge"
to fail with -EPERM on my system, and hence I am hoping that this should
at least unblock your day-to-day use of recent kernels.
Sorry again for the mistake in my earlier suggestion.
Vefa
