ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
<flowriser>
Tomorrow I'll get started on making the keyboard work, then wifi/modem
iivanov has joined #aarch64-laptops
flowriser_ has joined #aarch64-laptops
flowriser has quit [Remote host closed the connection]
flowriser_ has quit []
flowriser has joined #aarch64-laptops
<flowriser>
Is there a way to create a initrd file without using a VM for aarch64?
<rfs613>
flowriser: you could use buildroot for example - or yocto if you prefer - or even just assemble the initrd manually (it's just a cpio archive with a certain compression)
<rfs613>
a VM is not required at all - though some people like to use them for isolation purposes.
<robclark>
yeah, with 8GB it would be pretty nice.. but still, for the price is good.. I don't think I've seen the 4GB/64GB lazor for less than $349
<amstan>
is the $100 worth the fiddling with device trees?
<amstan>
no to mention potentially weird type c implementations. i'm using the framework laptop now and boy it's quite the downgrade to what i'm used to on chromebooks
<robclark>
not to mention, lack of suzyq
<robclark>
but would be nice to see upstream support for the 7c windows laptops as well..
iivanov has quit []
derzahl has quit [Remote host closed the connection]
flowriser has quit [Remote host closed the connection]
<steev>
maybe 6/6 where it keeps the interrupts during probe?
<steev>
i'll play around with the set, and see if i can figure it out - i tried adding modprobe.blacklist=ipa and that only gets a wee bit further it seems
<bamse>
i don't think that says there's a problem in ipa...i thin it says that ipa gets stuck doing an scm call
<steev>
the boot after that, it got stuck in ext4lazyinit