robclark changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
shoragan has quit [Read error: Network is unreachable]
valida-69[m] has quit []
smpl has quit [Ping timeout: 480 seconds]
psydroid[m] has quit []
jjardon[m] has quit [Quit: Client limit exceeded: 20000]
cachoeira has joined #aarch64-laptops
arisu has quit []
frolfer-n-a-tux[m] has joined #aarch64-laptops
frolfer-n-a-tux[m] has left #aarch64-laptops [#aarch64-laptops]
ajhalaney[m] has quit []
cachoeira has quit []
cachoeira has joined #aarch64-laptops
matrix638[m] has quit []
juergh1 has quit [Quit: Client limit exceeded: 20000]
cmeerw[m] has quit []
nekogirl[m] has quit [Quit: Client limit exceeded: 20000]
cachoeira9 has joined #aarch64-laptops
cachoeira9 has quit []
cachoeira0 has joined #aarch64-laptops
cachoeira0 has quit []
cachoeira has quit [Remote host closed the connection]
underpantsgnome[m] has quit []
cachoeira has joined #aarch64-laptops
cachoeira has quit [Remote host closed the connection]
cachoeira has joined #aarch64-laptops
WirelesslyWired[m] has joined #aarch64-laptops
possiblemeatball has quit [Remote host closed the connection]
alfredo has joined #aarch64-laptops
<colemickens>
I wonder how hard it is to find the firmware CABs from WU. Even if I have to mark it unfree/no-redist, it would be nice to use that to write Nix derivation for the firmware instead of manually copying from Windows driver store.
alfredo has quit [Read error: Connection reset by peer]
<JensGlathe[m]>
list all .mbn files in /mnt/Windows/System32/DriverStore/FileRepository for a first approach?
<travmurav[m]>
(the uuid is howid for "manufacturer+family" from fwupd hwids)
<Jasper[m]>
uupdump driver download branch may work too
<Jasper[m]>
in bulk
HgGamer has joined #aarch64-laptops
smpl has joined #aarch64-laptops
HgGamer has quit [Quit: Page closed]
jhovold has joined #aarch64-laptops
SintayewGashaw[m] has quit []
kuter has joined #aarch64-laptops
jhovold has quit [Quit: WeeChat 4.2.1]
bruno_rodriguezz[m] has quit []
possiblemeatball has joined #aarch64-laptops
<robclark>
strongtz[m]: did the keyboard work for you in grub menu (with the yoga)? Somehow it doesn't for me (but does work in bios menu)
possiblemeatball has quit [Remote host closed the connection]
possiblemeatball has joined #aarch64-laptops
possiblemeatball has quit []
<strongtz[m]>
robclark: it does
<robclark>
hmm, weird
KhalIshaIii[m] has quit []
kuter has quit [Quit: Leaving]
possiblemeatball has joined #aarch64-laptops
kuter has joined #aarch64-laptops
<abelvesa>
robclark: is the keyboard issue in grub happening when you boot from usb ?
<robclark>
yeah, usb boot at this stage
<robclark>
debian installer also has kb issues if I boot with it's kernel.. if I replace the kernel kb works, but it can't find network (probably because wrong set of modules).. fedora image is fine with init=/bin/sh but without that it reboots before I get to login (no idea if that is a kernel issue or not.. seems a bit like an insta-reboot (ie. unclocked access or something) but not sure, and not sure why it doesn't happen if
<robclark>
systemd tries to get to multi-user
<robclark>
also, fwiw, external usb kb is fine at grub.. anyways, I guess I have a different fw version than strongtz.. keyboard input at grub can't be anything other than a fw issue
<abelvesa>
robclark: there are two ways to boot from usb, one of them makes the grub freeze, on vivobook at least
<robclark>
hmm, I didn't see any freezing, but w/ debian image I had to edit grub.cfg to set a timeout (to workaround kb issue)
<abelvesa>
hmm
<robclark>
fwiw, either orientation w/ usb-c drive was the same, I didn't see any difference (which kinda implies the orientation switch is working for me)
<abelvesa>
if you append modules to it, you should be able to have a starting point to debug further why it reboots when switching to fedora rootfs
<robclark>
I can try one of those a bit later.. I think init=/bin/sh shows the kernel is _basically_ ok, I guess the reboot is userspace triggering the kernel to do something
<robclark>
but not sure what yet
<robclark>
looking at journal when I plug usb-c drive back into x13s, I see: