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)
e1eph4nt has joined #aarch64-laptops
<JoshuaAshton>
jenneron[m]: It doesnt log the boot in journalctl at all
<JoshuaAshton>
It doesnt get that far
<JoshuaAshton>
the last boot was just what I did in 5.11
<jenneron[m]>
sorry, i don't know
<jenneron[m]>
you can try to disable some things in dts like usb, display (ofc enable efi fb), etc
<jenneron[m]>
or you can actually try an empty dtb (only include dtsi, model and compatible) with efi fb and start adding things one by one, but it's easier to disable then one by one, adding status = "disabled" to nodes
<jenneron[m]>
them*
<JoshuaAshton>
jenneron[m]: Display disabled and gpu disabled didn't help
<jenneron[m]>
with display you probably want to disable related things like dispcc
<JoshuaAshton>
dispcc? Thats not referenced in the dts?
<JoshuaAshton>
and the dtbs definitely built this time
<jenneron[m]>
try also disabling usb
<jenneron[m]>
then ufs
<JoshuaAshton>
ufs will leave me without storage though right?
<jenneron[m]>
yes
<jenneron[m]>
but
<jenneron[m]>
just to test
<jenneron[m]>
if all this doesn't give you later efi fb logs, then try "empty" dts
<jenneron[m]>
also, do you have clk_ignore_unused and pd_ignore_unused in cmdline?
<JoshuaAshton>
i do not right now
e1eph4nt has joined #aarch64-laptops
<jenneron[m]>
efi fb won't work this way
<jenneron[m]>
you need these cmdlines
<JoshuaAshton>
ive tried them before and it didnt fix anything
<JoshuaAshton>
empty dts gives me a kernel error with a backtrace so thats something
<jenneron[m]>
JoshuaAshton: you need it anyway, otherwise you will have black screen once kernel disables "unused" clocks and power domains
<jenneron[m]>
JoshuaAshton: start with adding PMICs with regulators, then UFS
<clover[m]>
HdkR: you have touchscreen working with your thinkpad right? can you show me the input line in your dmesg
<JoshuaAshton>
jenneron[m]: Well disabling UFS certainly made it at least give up waiting for root lmao
<JoshuaAshton>
ill add that back and see what happens
<JoshuaAshton>
i am guessing the keyboard is usb as it doesnt work now I disabled usb lol
<jenneron[m]>
yeah it's on usb mp
<JoshuaAshton>
no integrated ps2
<JoshuaAshton>
so sad
<clover[m]>
steev: what branch should i be looking at in your repo for hacking on dt
<jenneron[m]>
it could be hid over i2c, but samsung decided to do it another way
<JoshuaAshton>
IM IN!
<JoshuaAshton>
woot
<clover[m]>
nice
<JoshuaAshton>
okay lets try adding back USB
<JoshuaAshton>
Dont even have to reboot back to 5.11 this time thank god
<JoshuaAshton>
jenneron[m]: I think after all of this it might have been clk_ignore_unused or something... because I went back to stock DTS and it worked...?
<JoshuaAshton>
ugh
<JoshuaAshton>
I swear I tried that
<JoshuaAshton>
maybe I typoed it :(
<JoshuaAshton>
I feel stupid now
<JoshuaAshton>
oh well, at least I learned a bunch about dts and stuff. Thanks a lot for your time and sorry for the noise to everyone else in the channel ^^
<clover[m]>
jhovold: i noticed you have 'Verify' next to the touchscreen in the thinkpad device tree. I can tell you it doesn't seem to work on mine, is there something else i can try?
<JoshuaAshton>
jenneron[m]: I installed these
<JoshuaAshton>
I dont think wifi works for me rn though
<JoshuaAshton>
I don't see the interface in ip addr
<jenneron[m]>
you should also copy some .jsn files
<jenneron[m]>
from lenovo directory in /lib/firmware/qcom
<JoshuaAshton>
to sc8180x?
<jenneron[m]>
copy them to /lib/firmware/qcom/sc8180x/sm-w767/
<JoshuaAshton>
I have them :(
<JoshuaAshton>
joshua@frogpad:~$ ls /lib/firmware/qcom/sc8180x/sm-w767/
<jenneron[m]>
the problem is that these memory regions need to be in one big range and they must not overlap
<JoshuaAshton>
hmm
<jenneron[m]>
for now we have to chose between adsp and mpss, adsp is commented out
<jenneron[m]>
<qzed> "as far as I can tell, for the..." <- see this message ^
<jenneron[m]>
also, what i know is that mpss region may not work with another address rather than <0x0 0x8d800000 0x0 0xa000000>, however it's fine to move around other memory regions
<JoshuaAshton>
I can try playing with stuff tomorrow
<jenneron[m]>
the problem is that we need to fit everything in that range (8bd80000-9a500000) and that range seems to be not enough, but i'm really not good with numbers, i could mess up everything in my head and be mistaken
<JoshuaAshton>
I am pretty tired, gonna build the compositor I use daily and maybe try and run some stuff for fun for the rest of the day
<JoshuaAshton>
I will check it :)
<jenneron[m]>
<JoshuaAshton> "well, glxinfo also says FD680 as..." <- send new dmesg, i think it will now give another info about gpu
<JoshuaAshton>
well GPU seems to be working fine in stuff other than gnome shell... but here
<JoshuaAshton>
<JoshuaAshton> (that was output from vulkan info)
<JoshuaAshton>
I am just going to approach this from the compositor side. I know little about Gnome, so I am just going to try the compositor I use and debug daily and debug that if its broken
<jenneron[m]>
does gnome run on wayland?
<jenneron[m]>
gnome should work with freedreno
<JoshuaAshton>
yeah I was running wl
<steev>
clover[m]: same one you use
<steev>
lenovo-x13s-6.0.0-rc4
<clover[m]>
yeah dumb question
<clover[m]>
im learning about device trees rn
<steev>
oh right, sorry i got distracted, let me go back to looking
<clover[m]>
i was also wondering if the only way to find out device tree information is using ACPI tables
<derzahl>
any known issues or incompatibilities in the kernel that effect the keyboard functionality? having lots of issues with it lately, on any of the >5.17.0 kernels ive compiled.
<derzahl>
i have the i2c_hid(_of), hid_generic drivers as moduled now on 5.19.8
<derzahl>
keyboard works fine in grub but dead after boot
<clover[m]>
i2c_hid_of 0-0015 this one is my touch screen though
<clover[m]>
or its supposed to be
<clover[m]>
oh wait thats my touchpad
<clover[m]>
1-0010 should be the touch sceen
<clover[m]>
and thats the last i hear from it
e1eph4nt has joined #aarch64-laptops
<steev>
well the good, is that it sees it, and tries to give it power... the bad is... i dunno. bamse any ideas?
<steev>
or maybe jhovold has an idea
<bamse>
about the touchscreen?
<steev>
yeah, it gets the regulator and then nothing
<steev>
i don't have a ts, and no idea how to poke and prod, but i feel like we went over this a while back
<bamse>
it's been a few weeks, but iirc it acquires the regulator, then tries to read something from the i2c-hid device and get a response which it uses to decide that it's not a i2c-hid device and then just exits
<bamse>
but the fact that the i2c read goes through indicates that both regulators and the i2c bus is in goog shape
e1eph4nt has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
<clover[m]>
Interesting that it's the only one that starts with 1-
<steev>
it's (possibly?) on device one
mothenjoyer69 has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
derzahl has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
derzahl has joined #aarch64-laptops
<derzahl>
i thought there was some qualcom kernel driver that you guys purposely disabled because it conflicted with something else. wondering if that might be my prblem with the keyboard
<derzahl>
on another note, has anyone had any luck with qcom_tee_uefisecapp? i load the module but still get 'function not implemented' trying to list efivars or use efibootmgr
_alice has quit [Server closed connection]
_alice has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
arnd has quit [Server closed connection]
arnd has joined #aarch64-laptops
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
pundir has quit [Server closed connection]
pundir has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
luxio_39[m] has quit [Quit: Bridge terminating on SIGTERM]
mothenjoyer69 has quit [Quit: Bridge terminating on SIGTERM]
abc123bac2[m] has joined #aarch64-laptops
robclark has quit [Server closed connection]
robclark has joined #aarch64-laptops
e1eph4nt has joined #aarch64-laptops
matthias_bgg has joined #aarch64-laptops
djakov_ has joined #aarch64-laptops
djakov_ has quit [Remote host closed the connection]
djakov has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
rpirea__ has joined #aarch64-laptops
rpirea_ has quit [Read error: Connection reset by peer]
rpirea__ has quit [Read error: Connection reset by peer]
rpirea__ has joined #aarch64-laptops
e1eph4nt has joined #aarch64-laptops
derzahl has quit [Ping timeout: 480 seconds]
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
ajhalaney[m] has joined #aarch64-laptops
arisu has joined #aarch64-laptops
AlexMarty[m] has joined #aarch64-laptops
amstan has joined #aarch64-laptops
clover[m] has joined #aarch64-laptops
cmeerw[m] has joined #aarch64-laptops
danielt has joined #aarch64-laptops
davidebeatrici[m] has joined #aarch64-laptops
Dylanger has joined #aarch64-laptops
fevv8[m] has joined #aarch64-laptops
frytaped[m] has joined #aarch64-laptops
testing has joined #aarch64-laptops
harvests[m] has joined #aarch64-laptops
harvestz[m] has joined #aarch64-laptops
szclsya[m] has joined #aarch64-laptops
jenneron[m] has joined #aarch64-laptops
Lucy[m] has joined #aarch64-laptops
luxio_39[m] has joined #aarch64-laptops
mahmoudajawad[m] has joined #aarch64-laptops
Manis[m] has joined #aarch64-laptops
mothenjoyer69 has joined #aarch64-laptops
psydroid[m] has joined #aarch64-laptops
Guest206 has joined #aarch64-laptops
robertmader[m] has joined #aarch64-laptops
Sobek[m] has joined #aarch64-laptops
steevdave[m] has joined #aarch64-laptops
underpantsgnome[m] has joined #aarch64-laptops
travmurav[m] has joined #aarch64-laptops
ungeskriptet[m] has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
<Dylanger>
6.0.0-rc6 works perfectly on Strongbad/Trogdor
<Dylanger>
👍️
e1eph4nt has quit [Ping timeout: 480 seconds]
rpirea__ has quit []
rpirea has joined #aarch64-laptops
e1eph4nt has joined #aarch64-laptops
derzahl has joined #aarch64-laptops
owlman has quit [Remote host closed the connection]
e1eph4nt has quit [Ping timeout: 480 seconds]
<jhovold>
clover[m]: right, I don't have a touchscreen so still waiting for someone to verify that the device tree node matches the hardware. Sounds promising that it seemed to work for HdkR.
<qzed>
hid_multitouch is the driver for multi-touch capable touchpads
<clover[m]>
ok, i guess description `HID multitouch panels` makes it seem like a display panel
<qzed>
yeah, the name is a bit unfortunate
<jhovold>
clover[m]: the values (i2c address and hid descriptor offset) come from the reference design and matches the ACPI tables IIRC. So "should" work.
<jhovold>
clover[m]: and the touchscreen has address 0x10 (not 0x15) on X13s
<jhovold>
clover[m]: perhaps you can add some instrumentation to the hid driver and see where things fail. Take a look at i2c_hid_core_probe(). It seem likely that the touchscreen doesn't return any data. As if it isn't populated or at the expected address.
<clover[m]>
where is the hid driver in the kernel code?
<jhovold>
clover[m]: you can also just enable dynamic debugging for that function and see if you see that "nothing at this address" message during boot
<jhovold>
clover[m]: have you confirmed that the ts works in windows?
<qzed>
I guess youc ould try `echo file i2c-hid-core.c +p | sudo tee /sys/kernel/debug/dynamic_debug/control` if that doesn't produce too much output
<qzed>
or use the module name
<jhovold>
clover[m]: you need to set it on the command line. can't remember the syntax. or just recompile the module and turn that dev_dbg into dev_info
<jhovold>
clover[m]: kernel's command line when booting
<jhovold>
unless you can unload and reload the module, but you'd lose the keyboard I guess...
<qzed>
if I've got everything you were discussing so far right, the problem is that somehow the i2c-hid driver doesn't want to probe agains the i2c device
<qzed>
and I think it looks like that since there's no driver node in /sys/bus/i2c/devices/1-0010
<clover[m]>
right it only wants to bind touchpad@15 and keyboard@68