ChanServ 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
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
nothorseface has quit []
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
nothorseface has joined #aarch64-laptops
davidinux is now known as Guest132
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
tobhe_ has joined #aarch64-laptops
nothorseface has quit []
tobhe has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
chrisl has quit [Ping timeout: 480 seconds]
unalmasIRC has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
indy has joined #aarch64-laptops
lak has left #aarch64-laptops [#aarch64-laptops]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
nothorseface has joined #aarch64-laptops
nothorseface has quit [Remote host closed the connection]
davidinux has joined #aarch64-laptops
Guest132 has quit [Ping timeout: 480 seconds]
<kuruczgy[m]>
Yes indeed, it also works with 4 lanes. Image quality looks better, but maybe still not 100% right. (Though it could be just a perception issue, compared to the OLED of the yoga everything else looks worse.)
tobhe_ is now known as tobhe
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
jglathe_x13s has quit [Remote host closed the connection]
iivanov_ has joined #aarch64-laptops
iivanov_ has quit [Remote host closed the connection]
iivanov_ has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
nothorseface has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alfredo has quit [Quit: alfredo]
iivanov_ has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
pinskia has quit [Read error: Connection reset by peer]
pinskia has joined #aarch64-laptops
nothorseface has quit [Remote host closed the connection]
jglathe_x13s has joined #aarch64-laptops
<macc24>
<kuruczgy[m]> "Aand I am getting DP output. I..." <- > <@kuruczgy:matrix.org> Aand I am getting DP output. I cherry picked the two relevant commits from the ubuntu tree (87f07f4fe544 and 350f8e8802be), and reduced the lanes to only two (not sure if needed). During boot the screen goes black (I have to type disk pw blind, maybe an initramfs module is missing? (Maybe drm_dp_aux_bus?))
pinskia has quit [Read error: Connection reset by peer]
<macc24>
> The output appears gray/low contrast (mode: 1920x1080@60.000 Hz). I am using the HDMI adapter that came with the laptop. Also only the ports on the left work, on the right one the link training fails.
<macc24>
you might have hdmi range setting set to limited or similar
pinskia has joined #aarch64-laptops
<kuruczgy[m]>
Uhh which component would this be in the stack? What should I look at?
<jhovold>
macc24: please try to avoid matrix quoting here
<macc24>
sprry
<macc24>
*sorry
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
<dgilmore>
jhovold: I suspect my t14s has something different in it. booting from usb-c I have the firmware listed https://github.com/jhovold/linux/wiki/T14s extracted from the download exe from lenovo's website. and using your 6.12 kernel config. the last text on the screen is checking the filesystems, then the screen turns blue and about 30 seconds later the system reboots. there is no journal saved to disk
<farchord>
Screen turns blue.... isn'T that the dreaded Linux BSOD?
<maz>
that's probably the firmware resetting the box, not Linux.
chrisl has quit [Ping timeout: 480 seconds]
* travmurav[m]
wonders if someone should start programming UNDERFLOW_COLOR register so people aren't as confused talking about "blue screen"
<travmurav[m]>
at least that register existed 10 years ago
<maz>
is t14s known to have easy to reach serial pins?
<maz>
s/pins/pads/
<jhovold>
dgilmore: you said you had the 64 GB version IIRC? then you may need to disable the upper 32 GB...
<travmurav[m]>
maz: did the devkit end up /that/ disappointing? xD
<dgilmore>
jhovold: I do,
<jhovold>
tobhe provided a grub command that may help: cutmem 0x8800000000 0x8fffffffff
<maz>
travmurav[m]: it is usable, if you aren't too picky about some really ugly behaviours.
<maz>
travmurav[m]: the t14s looks similar enough to my current laptop that I could be tempted, but I need console access -- that's not negotiable ;-)
<travmurav[m]>
all of which are firmware I guess? xD
<travmurav[m]>
tbh my impression is that t14s is the most janky firmware of them all considering people complain of non-working EBS all the time xD
<maz>
nope. there's at least one issue that I'm awaiting feedback on, because that's a CPU ... "feature".
<dgilmore>
my grub build does not have cutmem as a command
<travmurav[m]>
maz: ah so phoenix v1 has some fun stuff too I guess?
* travmurav[m]
wonders if they cut NV from oryon2 they put into 8 elite et all
<maz>
the issue I see is not even related to NV. looks like someone read the pseudocode the wrong way.
<travmurav[m]>
lol
<travmurav[m]>
I see, the nv remark was unrelated I guess
<travmurav[m]>
since presumably they say they re-made the cores from scratch and given they put them into phones, my first thoguht was that the NV will be cut out again
<maz>
but that's when I started running NV stuff that it became apparent that something was off. then I looked at it a bit more closely, and ... oh well.
<maz>
NV is not that costly, actually. it's a lot of extra traps, but there isn't a lot of impact once you already have the VHE redirection (it is basically the inverse).
<maz>
the only "new" thing is the VNCR redirection to memory.
<maz>
which plugs the sysreg access into the LSU. hardly a big deal.
<deathmist>
JensGlathe[m]: just booted https://github.com/jhovold/linux/tree/wip/x1e80100-6.12 + HP stuff from ubuntu tree, trying brightness in KDE Plasma 6 I can go as low as 3% before the display goes pitch black at 2%, and at 95% it goes weirdly dim compared to 94% which appears to be max brightness
<JensGlathe[m]>
Okay thanks for confirming. There is a launchpad bug on ubuntu-concept x1e for this. Depending on the levels curve you set you come to mx 94% or max 96%.
<JensGlathe[m]>
And I had one occasion where the system booted and brightness was set to 100%
<dgilmore>
can anyone point me to a grub binary that supports 64GiB ram and has the cutmem command?
<jhovold>
the ubuntu one is supposed to have a workaround even if I couldn't get it to work when building their sources:
<jhovold>
but then I only have the 32 GB version, and the bugs I'm running into are possibly separate ones
<dgilmore>
without that patch in grub the system resets before grub can display anything
Melody91 has joined #aarch64-laptops
erebion[m] has joined #aarch64-laptops
<erebion[m]>
Not really laptops, but has anyone looked into the new "Microsoft 365 Cloud PCs"? Apparently they're fan less and supposed to be used with online services only. I wonder whether those are just ARM PCs that could be used for other stuff. :D
<craftyguy>
sounds like "thin clients" from the 90s are making a comeback 😆
<craftyguy>
I guess they get some fake points for persistence
<Jasper[m]>
I wish they stopped trying half-assed attempts at getting sued another time for anti-competitive behaviour
<Jasper[m]>
(and Google too for that matter)
<craftyguy>
I'm fine with MS being sued away, but that's probably just me. I never forgot MS from the 90s/00s
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<kuruczgy[m]>
I narrowed down the initramfs modules needed with the dp alt mode devicetree patches (slim 7x): it's ps883x, pmic_glink_altmode, and qrtr. Without these, the (builtin) display goes black, and only comes back after the initramfs.
<kuruczgy[m]>
ps883x and pmic_glink_altmode somewhat make sense (though I still don't get why the symptom is "builtin display goes black"), but I have no idea how qrtr is even related to any dp altmode stuff.
SpieringsAE has joined #aarch64-laptops
<SpieringsAE>
sadly no luck getting my usb type a working, so it looks like there is some digging to do in the end
<robclark>
kuruczgy[m]: is qrtr also involved in adsp things (since some of the usb-c/dp functions that would normally be handled by an EC seem to be on adsp in last couple gens of qc things (maybe a BoM reduction move?)
<robclark>
display going black is probably the first time display probe defers, the gdsc is disabled by driver core
<robclark>
so that is "normal"
Dylanger[m] has joined #aarch64-laptops
<Dylanger[m]>
<erebion[m]> "389 USD for an Intel CPU with..." <- Yeah this is terrid
jglathe_x13s has quit [Ping timeout: 480 seconds]
<rfs613>
they could just call it "software defined cloud computer" :-)
<kuruczgy[m]>
Oh for some reason sway maps the touchscreen to the external monitor
<kuruczgy[m]>
Actually, it maps the touchscreen to both. So half the touchscreen to the monitor, half to the builtin display...
SpieringsAE has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
<deathmist>
kuruczgy[m]: ig sway assumes the touchscreen is some kinda graphics tablet
<deathmist>
or rather a drawing table like a wacom
<kuruczgy[m]>
no, all the multitouch gestures work fine (e.g. two finger zooming in firefox), so wayland definitely knows that this is a touchscreen. I think it just doesn't know which screen it's supposed to be attached to.
<ppd[m]>
it seems like the speaker parameters are inside the .qdb(?) file that configures a qcom ACX filter, which is locked behind the qualcomm audio configuration filter
<ppd[m]>
audio configuration program* not filter
<Jasper[m]>
ppd, WILD pfp btw
<ppd[m]>
I guess I have to brute force modifiy the ucm config, which is "great"
chrisl has joined #aarch64-laptops
<ppd[m]>
(oh and for the IRC logs: Jasper is talking about my profile picture on matrix)
<steev>
figured as much
<steev>
would the speaker parameters you mention be usable in the speakersafetyd config?
<Jasper[m]>
It's Homer Simpson french kissing an anime lady
<Jasper[m]>
I'm assuming the latter anyway
<Jasper[m]>
steev, what happened to the speaker amp driver based apparoach?
<ppd[m]>
steev: no because the .qdb file is unreadable unless someone has access to the qualcomm audio calibration tool
<steev>
ahh
<ppd[m]>
poking at it a bit didn't really reveal anything. I might do further inspection with a hex editor later but I dunno. I would need more of these files to compare
<Jasper[m]>
Someone told me qact is downloadable for free on the dev portal
<Jasper[m]>
if you wanna tesy
<Jasper[m]>
*test
<Jasper[m]>
(with a qcom portal account that is)
chrisl has quit [Ping timeout: 480 seconds]
SpieringsAE has joined #aarch64-laptops
<SpieringsAE>
yep something is off for some reason, getting: [ 20.190974] platform a400000.usb: deferred probe pending: dwc3: failed to initialize core
<SpieringsAE>
a400000 is usb_mp_dwc3
SpieringsAE has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
<ppd[m]>
Jasper: I had tried getting that last night with my dev acc but qcom decided to not let me in. Prob a cookie issue. Tried again today and got a very nice message:
<ppd[m]>
> Your access to certain software in the Qualcomm Software Center is limited. Qualcomm Software & Tool visibility is governed by agreements that your company signed with Qualcomm.
<ppd[m]>
Oh wait, it's letting me now. Just need windows, apparently. Of course, the one time I leave my separate windows SSD at home is when I need it.
<ppd[m]>
I know "IANAL", but is what I am doing here (getting the properties of these speakers) potentially under scrutiny ala ReactOS/WINE contributions (not being able to contribute those projects if you ever looked at leaked windows code or developed on windows)?
<Jasper[m]>
Good question
<robclark>
iirc at some point, someone pointed to an open src speaker protection thing for android (although idk what it needs in terms of parameters or where those come from)
<ppd[m]>
The problem is extracting and contributing those parameters. I don't know what copyright says about their usage.
hogliux has joined #aarch64-laptops
Dalphon has joined #aarch64-laptops
<hogliux>
is the in-kernel pd-mapper <-> sound race condition still an issue for some?
<hogliux>
what I find is that as long as the snd_soc_wsa884x kernel module is loaded before the in-kernel pd-mapper (or userspace pd-mapper FWIW), everything seems to work
<hogliux>
I use my slim 7x as a daily driver and have been using this setup for month or two now and never had the race condition
<hogliux>
before, when not loading snd_soc_wsa884x in initramfs (i.e. letting udev load them for me during normal bootup after initramfs), I would occasionally hit the race-condition and not have sound
<ppd[m]>
> AudioReach Creator(ARC), also known as Qualcomm Audio Calibration Tool (QACT), is PC-based software providing GUI to audio system designer for composing, configuring, and storing audio graphs into audio calibration database(ACDB) for intended use cases.
<ppd[m]>
Yeah, this seems like the correct thing. How did I not find this?
chrisl has joined #aarch64-laptops
<steev>
so would they be part of the audioreach topology file then?
<ppd[m]>
No, I think this would be another daemon
<ppd[m]>
Can't tell exactly. Will need more research.
chrisl has quit [Ping timeout: 480 seconds]
jhovold has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<ppd[m]>
steev: Still too early to confirm, but I think this is the software that should create the right UCM for ALSA with various filters.