Caterpillar has quit [Quit: Konversation terminated!]
<steev>
gwolf: the X13s is still my favorite
<steev>
but when i gave my talk at defcon i used the t14s
<gwolf>
X13s works beautifully, and has a great form-factor. I also enjoy it very much
<gwolf>
There are several details of the Yoga I prefer (i.e. the ports placement, or the 360° hinges), but technically, I'll stay with the X13s for sure.
rigo has quit [Read error: Connection reset by peer]
antoinelassagne7 has joined #aarch64-laptops
antoinelassagne has quit [Read error: Connection reset by peer]
antoinelassagne7 is now known as antoinelassagne
Caterpillar has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Ping timeout: 480 seconds]
<dgilmore>
I prefer the x13s, I just wish I got 32GiB ram. though maybe if I got 32GiB ram in the t14s I would like it better
Caterpillar has quit [Ping timeout: 480 seconds]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
enyalios_ is now known as enyalios
ginger has joined #aarch64-laptops
ginger has left #aarch64-laptops [#aarch64-laptops]
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
hexdump0815 has joined #aarch64-laptops
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
hexdump01 has quit [Ping timeout: 480 seconds]
flto has quit [Ping timeout: 480 seconds]
eluks has quit [Remote host closed the connection]
eluks has joined #aarch64-laptops
avenuest has joined #aarch64-laptops
mbuhl_ has joined #aarch64-laptops
mbuhl has quit [Remote host closed the connection]
mbuhl_ is now known as mbuhl
avenuest has quit [Remote host closed the connection]
sally has quit [Remote host closed the connection]
sally has joined #aarch64-laptops
flto has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Remote host closed the connection]
Caterpillar has joined #aarch64-laptops
bandini has joined #aarch64-laptops
Caterpillar has quit [Quit: Konversation terminated!]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Ping timeout: 480 seconds]
hexa- has quit [Quit: Disconnected]
hexa- has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
rigo has joined #aarch64-laptops
<rigo>
gwolf: i'm back
<rigo>
i've been thinking about getting an x13s. i'm starting to see some cheap ones on ebay now
rigo has quit [Read error: Connection reset by peer]
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
dc7800_ has quit [Read error: Connection reset by peer]
notHorseface has joined #aarch64-laptops
dc7800 has quit [Ping timeout: 480 seconds]
dc7800 has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
dc7800 has quit [Ping timeout: 480 seconds]
dc7800 has joined #aarch64-laptops
ieyasu_ has quit [Read error: Connection reset by peer]
ieyasu has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800- has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
dc7800 has quit [Ping timeout: 480 seconds]
dc7800- has quit [Ping timeout: 480 seconds]
dc7800 has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Ping timeout: 480 seconds]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
dc7800 has quit [Ping timeout: 480 seconds]
dc7800 has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
<serdeliuk[m]>
Hi all, what boot loader is appropriate to load slbounce on zenbook a14? grub is not able to, what do you use?
bandini has quit [Quit: WeeChat 4.9.5]
<travmurav[m]>
sd-boot supports drop in drivers, some people boot via efi shell init scripts
<JensGlathe[m]>
psydroid: I tested the resolute image boot on the mini x , and it failed here, too. Will find it.
<serdeliuk[m]>
<travmurav[m]> "sd-boot supports drop in drivers..." <- i try to enable ramoops and does not seems to work using uefi boot menu, then usefi shell > load drivers, then return to grub and boot the right thing
<travmurav[m]>
ramoops?
<travmurav[m]>
I think people said on x1e inline ram encryption scrambles ram on reboot so ramoops is useless, idk if it's also the case on previous things
<travmurav[m]>
s/ram/keys/
<serdeliuk[m]>
oh, that may be the issue :( i have sudden reboots generated by Iris in EL2 and want to find out why, but i am not able to catch anything
<travmurav[m]>
serdeliuk: is it x13s or newer?
<travmurav[m]>
then again on x13s reboots were caused by dumb qhee firmware...
<serdeliuk[m]>
it is zenbook a14 X126100
<travmurav[m]>
right, I've heard efivar pstore works
<travmurav[m]>
isntead of ramoops
<travmurav[m]>
though /me also seen claims that abusing efivars and filling them fully might cause issues
<travmurav[m]>
hopefully qcom firmware isn't as shit though
<travmurav[m]>
(then again we seen so many things already)
<serdeliuk[m]>
hmmm....
<serdeliuk[m]>
yeah, should be careful
<Mis012[m]>
may not even be qcom's fault if something in the vendor edk customization dies
<travmurav[m]>
right that too
<serdeliuk[m]>
yeah, asus uefi is bad too indeed
<Mis012[m]>
I think Linux can be set to never go over X % of efivar storage
<JensGlathe[m]>
psydroid: found it - the dt I placed is hamoa-based (as in the name, duh), and there are both variants. Next image will have both. I want to bring up mine, too, which is Purwa. And very British.
notHorseface has joined #aarch64-laptops
sboyd has joined #aarch64-laptops
jglathe_t14s has quit [Quit: Leaving]
dc7800_ has joined #aarch64-laptops
programmerin-wonderland has joined #aarch64-laptops
dc7800 has quit [Ping timeout: 480 seconds]
<programmerin-wonderland>
switched to your UCM2, unfortunately still having the issue
<JensGlathe[m]>
Hmm restarted pipewire ofc
<programmerin-wonderland>
actually rebooted my whole PC to be safe LOL
<misyl>
Sukiru[m]: What is OGC?
<JensGlathe[m]>
Nothing‘s odd with alsa, but grmpf
<programmerin-wonderland>
wondering if its something in my outdated kernel atp, still on 7.0.0-rc4+
<valpackett>
@programmerin-wonderland:gitter.im make sure you've replaced the configs in the correct path, ucm2 paths are a mess and it's easy to place it in the wrong path that doesn't get loaded lol. also uhh erase alsa state
<valpackett>
`/var/lib/alsa/asound.state` usually
pabs has quit [Ping timeout: 480 seconds]
gwolf has quit [Read error: No route to host]
psydroid|2 has quit []
gwolf has joined #aarch64-laptops
gwolf has quit [Ping timeout: 480 seconds]
gwolf has joined #aarch64-laptops
Caterpillar has joined #aarch64-laptops
<steev>
make sure to stop the service that saves the current settings before rebooting
Caterpillar has quit [Ping timeout: 480 seconds]
dc7800 has quit [Read error: Connection reset by peer]
dc7800_ has quit [Read error: Connection reset by peer]
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Remote host closed the connection]
rigo has quit [Quit: leaving]
rigo has joined #aarch64-laptops
<gwolf>
rigo: Well, sadly... no luck on my part
<gwolf>
Or rather: your image booted just fine (and gave me my first glimpse of what Arch looks like ;-) )
<gwolf>
But I didn't get it to find my wireless card any more than my older Debian kernel could :-(
<gwolf>
Got a photo from the boot process... https://nube.iiec.unam.mx/s/92owStHFHGzzJ9q (later I also got a dmesg, but I must have it on a USB stick upstairs... and I'm too lazy ;-) )
<rigo>
bummer
<gwolf>
but in short, at t=12.77, qcom-q6v5-mss reports a timeout, and it's only error reporting since that point onwards
<gwolf>
Exactly the same I had seen with my 6.1x kernel about a year ago :-(
<gwolf>
No need, I guess. The interface is not even reported. And if I connect an external wifi card, it _does_ detect it and I can set it up correctly
<gwolf>
oh, OK, I see one of them is the firmware loader... Maybe it can do the trick
<gwolf>
will try later, I guess! It won't hurt, and booting it takes me ~30 seconds, so no harm...
<rigo>
yea the wifi doesn't start automatically
<rigo>
you gotta enable those services so they startup once the os is installed
<gwolf>
Right, but the interface _is_ available automatically, no?
<gwolf>
(other than the wpa_supplicant)
<gwolf>
Anyway, I'll try that later
<gwolf>
I want to do some home-tidying stuff before our sun becomes a cloud and then a thunderstorm, as usual :-]
<clover[m]>
ip a should show an interface
<gwolf>
clover[m]: right, and it does not
<rigo>
no worries
<gwolf>
anyway, TTYL!
<clover[m]>
if it's not there, might be missing firmware, or something wrong with the dtb
<gwolf>
...or with the hardware, in my case!
<gwolf>
(as I used it very happily for ~4 years until one fine day it went missing)
<rigo>
the ISO comes preloaded with the dtb and all the firmware needed
<rigo>
it just doesn't have those qcom services enabled. i could look into having them start automatically in the ISO
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Remote host closed the connection]
rigo has quit [Read error: Connection reset by peer]
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
<valpackett>
gwolf: rigo: is `CONFIG_RESET_QCOM_PDC` enabled in the kernel config?
rigo has joined #aarch64-laptops
<valpackett>
"failed to acquire pdc reset" is not something fixable with services or firmware
<valpackett>
especially since the remoteproc is deferred after that error.. that just tells me that the "error" there is the `pdc_reset` not having been probed, which is most likely just the driver for it not being present
rigo has quit []
<valpackett>
it is `=m` (enabled as module) in the upstream arm64 defconfig, maybe it's not loaded somehow
<valpackett>
also maybe everything is there but the stupid deferred probe timeout hits before it's loaded
<valpackett>
if q6v5-mss is in the initramfs but reset-qcom-pdc isn't, that would do it (with the default `CONFIG_DRIVER_DEFERRED_PROBE_TIMEOUT`)
<rigo>
they left a comment saying that enabling added some weird race conditions
<valpackett>
"weird race conditions. Stick to the userspace one for now (6.13). still seem to happen in 7.1rc1. makes mic not working in poco f1. no idea why." ugh lol
<rigo>
maybe they've been resolved though
<valpackett>
postmarketos's qcom-sdm845 does have `CONFIG_QCOM_PD_MAPPER=m`
<rigo>
hmm, yea
enyalios has quit [Ping timeout: 480 seconds]
<rigo>
valpackett: i'm confused where are you seeing that?
<rigo>
i guess its in the defconfig
<rigo>
but, that would get overriden by the fragment i think
<rigo>
i've checked the config that i'm running and I have CONFIG_RESET_QCOM_PDC=m but CONFIG_QCOM_PD_MAPPER is not set
<valpackett>
on the pmos side? the fully generated config is stored in the pmaports repo
<Mis012[m]>
so are the fragments
rigo has quit [Quit: Lost terminal]
anthony25 has joined #aarch64-laptops
rigo has joined #aarch64-laptops
<rigo>
i was unware about the in-kernel pd-mapper maybe I should dabble with it. the service seems to be working decent enough for me
<rigo>
i'm gonna put up a new release that comes with those services enabled so all you have to do is connect to your wifi