Good day, a few days ago I got a Thinkpad X13s. I would like to
participate to the testing for Linux support. Do we have a list of
things that need to be tested?
At the moment I am setting up the Linaro image of Debian I got at URL
https://forums.lenovo.com/t5/Other-Linux-Discussions/Does-anybody-know-if-t…
Best regards
hi All,
Arm are hosting an on-line DevSummit event and this includes a birds-
of-a-feather session on laptop platforms. I'm going to be present along
with some of the other folks who care about AArch64 laptops. It would
be great to see you there!
Tuesday, Oct 6
11:00 AM - 11:30 AM PDT
Registration is required (zero cost):
https://devsummit.arm.com/arm-infrastructure
best regards,
Richard
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi All,
I have Ubuntu installed from Dmitri's installer. update-grub2 works
well from that OS. I now have Fedora Rawhide in a separate partition
and I would like to do have Fedora take over efi management. I have
read through a bit about EFI management on Linux and it looks like
efibootmgr is the primary tool.
Using efibootmgr from both Ubuntu 19.10 and Fedora Rawhide and I get
identical errors:
$ efibootmgr -c -d /dev/sda -p 1 -l \\EFI\\fedora\\grubaa64.efi -L
skipping unreadable variable "Boot0000": Invalid argument
Could not prepare Boot variable: Invalid argument
Does anyone have a suggestion for the next steps for me to try?
best regards,
Richard
--
Richard.Henwood(a)arm.com
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi All,
A fellow laptop user has been looking into efi=novamap requirement. I
was sharing with him that I thought only firmware could solve this
problem and he has questioned me on that assertion and pointed me to
this commit:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=4e46…
It appears from my reading that efi=novamap is required because: It is
fiddly to make the kernel function SetVirtualAddressMap() work
correctly on AArch64. Without documentation for the laptops I care
about, it does not appear to be a valuable use of time to make
SetVirtualAddressMap() work. For now, efi=novamap is a good-enough
work-around.
Is that more a more accurate analysis on my part?
best regards,
Richard
--
Richard.Henwood(a)arm.com
Server Software Eco-System
Tel: +1 512 410 9612
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi all,
I am playing with the Fedora Rawhide aarch64 kernel on my lenovo c630. Today this is a 5.6 kernel. I guess it is missing some config options stuff because the laptop keyboard isn't available. It also seems like systemd userspace is pretty unhappy too, but that is seconday to the keyboard for me currently.
I haven't spent time looking though the know working configs that are already available, but appealing to the knowledge on this list: are there some kernel config options folks can suggest to me to improve the situation?
Best regards
Richard
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
