00:01
<
_[m]123 >
ah that s because I changed to highger frequency but so no more external screen âšī¸ tried 6.7 and 6.8
00:08
<
_[m]123 >
works again hmpf
00:17
hightower3 has joined #aarch64-laptops
00:23
hightower4 has quit [Ping timeout: 480 seconds]
00:38
<
konradybcio >
enjoy
03:26
schaeffer has quit [Ping timeout: 480 seconds]
03:48
f_ has quit [Read error: Connection reset by peer]
03:49
f_ has joined #aarch64-laptops
04:25
jglathe_volterra has quit [Remote host closed the connection]
04:27
iivanov has quit [Quit: Leaving...]
04:29
jglathe_volterra has joined #aarch64-laptops
04:53
hexdump01 has joined #aarch64-laptops
04:55
hexdump0815 has quit [Ping timeout: 480 seconds]
06:38
jhovold has joined #aarch64-laptops
07:09
ungeskriptet has joined #aarch64-laptops
07:37
martiert has joined #aarch64-laptops
07:45
matthias_bgg has joined #aarch64-laptops
07:57
iivanov has joined #aarch64-laptops
07:57
ungeskriptet has joined #aarch64-laptops
09:14
Caterpillar has quit [Ping timeout: 480 seconds]
09:25
KREYREN_oftc has joined #aarch64-laptops
09:33
ungeskriptet has joined #aarch64-laptops
09:35
iivanov has quit [Remote host closed the connection]
09:36
iivanov has joined #aarch64-laptops
12:00
<
agl >
Which kernel parameter are neccessary to switch on IOxx_DMA_LAZY ?
12:00
<
agl >
for the USB ports
12:01
<
agl >
s/parameter/parameters/
12:04
<
jhovold >
agl: you don't need to do that anymore
12:05
<
jhovold >
but if you still want to do it, it's "iommu.passthrough=0 iommu.strict=0"
12:05
<
agl >
I need it for my ACASIS-BOX. I have it to do in the .config of linux-x13s of x13s-alarm, and then it works.
12:06
<
agl >
jhovold: Thanks :)
12:07
<
agl >
THE ACASIS-Box with a SSD and some ports seems a little bit difficult.
13:00
alpernebbi has joined #aarch64-laptops
13:11
<
agl >
jhovold: I see it works WITHOUT ..._DMA_LAZY or without the iommu.... parameters! I have tried this!
13:11
alpernebbi has quit []
13:20
alpernebbi has joined #aarch64-laptops
13:24
alpernebbi has quit []
13:25
alpernebbi has joined #aarch64-laptops
14:30
<
jhovold >
agl: as I said, you don't need it anymore since the underlying issue was fixed
14:38
<
bamse >
jhovold: i was about to resubmit the touchscreen patches...but realized that i was on the wrong path...
14:40
<
bamse >
jhovold: as i was extending the binding and the driver, i stumbled upon i2c-hid-of-elan.c
14:40
<
bamse >
jhovold: so we apparently have the generic driver that doesn't allow us to set that one timeout, and then we have a elan-specific driver...
14:41
<
bamse >
jhovold: so, if we could just figure out what elan-chip we actually have...
14:44
<
jhovold >
bamse: heh, nice find, looks just like what we need :)
14:45
<
bamse >
no idea why there are two drivers doing essentially the same thing...
14:47
<
bamse >
jhovold: didn't you or someone over there have schematics for the "display" as well? or could you ping someone who has that information?
14:47
<
jhovold >
bamse: i don't have it but I think I know someone who does, i'll check
14:48
f_ is now known as funderscore
14:50
funderscore is now known as f_
14:56
<
jhovold >
bamse: there was no product string tobe found in windows?
14:56
<
jhovold >
oh, and did you notice that pmic_glink device links errors are gone in rc5?
14:56
<
bamse >
jhovold: i have not rebooted yet
14:57
<
jhovold >
saravanna apparently finally got around to fixing that
14:57
<
bamse >
nice, i didn't notice
14:57
baspar[m] has quit [Ping timeout: 480 seconds]
14:57
Nao[m] has quit [Ping timeout: 480 seconds]
14:57
<
bamse >
sounds like a -rc1 change
14:57
<
jhovold >
yeah, what could go wrong, right?
14:58
<
jhovold >
still, i'm down to essentially a single error in the log after boot now (sound driver)
14:58
baspar[m] has joined #aarch64-laptops
14:58
Nao[m] has joined #aarch64-laptops
15:00
<
jhovold >
and the bluetooth frame reassembly error every other boot
15:01
<
bamse >
the timeout from the sound driver?
15:01
<
jhovold >
a reminder that that needs to fixed at some point
15:04
<
bamse >
yeah...and i need to figure out how to reproduce that other issue, with pmic_glink not coming up as well
15:45
todi has joined #aarch64-laptops
16:08
<
jhovold >
bamse: nothing in the schematics, but I'll see what I can find out from Lenovo
16:09
<
jenneron[m] >
bamse: which timeout? just curious
16:09
<
jhovold >
and lumag looked for a product name in Windows, without any luck there either
16:09
<
jenneron[m] >
i2c-hid-of has got some new bindings recently which allowed me to make it working on flex 5g
16:09
<
jhovold >
jenneron[m]: we need a delay after deasserting the touchscreen reset at boot
16:10
<
jhovold >
it's not actually in the bindings yet, but yeah, the driver know how to handle it now
16:10
<
jenneron[m] >
i see
16:11
<
jhovold >
the thing is, such details should not be in the devicetree
16:11
<
jhovold >
but rather in the driver, based on the compatible string
16:11
<
jenneron[m] >
that's if you know the IC..
16:11
<
jenneron[m] >
unlike my case with flex 5g
16:12
<
jhovold >
so know we need to figure out a name for the Elan device with product id 0x901c
16:13
<
jhovold >
can't you find a pid in the dsdt there too?
16:13
<
jenneron[m] >
evtest reports bus 0x18 vendor 0x4f3 product 0x2a7d version 0x100
16:14
<
jhovold >
so that's Elan too IIUC
16:15
<
jenneron[m] >
yeah it is elan
16:15
<
jenneron[m] >
DSDT: Name (_HID, "ELAN901C")
16:16
<
jhovold >
or maybe I'm reading this wrong, and 901c is the product name?
16:16
<
bamse >
jenneron[m]: i noticed that as i reviewed your(?) patches, but wanted to figure out the path forward...
16:16
<
jhovold >
the X13s dsdt have the same string for the touchscreen, not sure about the pid anymore
16:17
<
jhovold >
bamse: can you check dmesg?
16:17
<
bamse >
it wouldn't be totally crazy if it's the same touchscreen on both
16:17
<
bamse >
jhovold: "msdu_done bit in attention is not set" :)
16:18
<
bamse >
jhovold: what do you want me to check? if there's anything useful in the logs identifying the touchscreen?
16:19
<
jhovold >
there should be a pid in there somewhere
16:19
<
jhovold >
dmesg | grep HID should tell
16:20
<
bamse >
i'm back on my clean upstream kernel....let's see if i can do the sysfs dance
16:21
<
jenneron[m] >
touchscreen is Device (TSC1)
16:21
<
bamse >
jhovold: [342566.707605] hid-multitouch 0018:04F3:2FE6.0003: input: I2C HID v1.00 Device [hid-over-i2c 04F3:2FE6] on 4-0010
16:22
<
jenneron[m] >
nah it's not the same touchscreen at least
16:22
<
jhovold >
so different PID than jenneron[m]: 0x2FE6 vs 0x2a7d
16:22
<
jhovold >
guess that string in the dsdt doesn't mean much
16:26
<
jhovold >
bamse: but judging from that bugzilla entry, that ath11k spam message depends on which network the reporter is connected too
16:26
<
jhovold >
and I've never seen it here (or elsewhere)
16:28
<
bamse >
jhovold: i'm not surprised, i have it on all my ath11k-devices
16:29
<
_[m]123 >
sending my x13s with fedex to poland (for free) to replace my touchpad đ¤
16:29
<
_[m]123 >
they said, the ssd is a user replacable item and doens't void the warranty đ
16:33
<
_[m]123 >
I'll cheer when they actually replace it
16:53
<
bamse >
jhovold: fun stuff, speedtest.net over wifi gives me 3mbps down and 293mbps up today again...
16:58
<
bamse >
jhovold: numbers consistent with iperf3 towards my local machine...not sure what's up
17:29
<
jhovold >
bamse: I have 513 down 523 up Mbit/s just now with my 6.8-rc5 wip branch
17:29
<
jhovold >
but I did notice that I only got 50 Mbit/s in one direction sometimes when doing the PCIe work this last few weeks
17:30
<
jhovold >
a reboot helped so possibly another firmware regression in the January 15 release (i.e. .36)
17:31
<
bamse >
how do i check which version i'm on?
17:31
<
jhovold >
dmesg | grep LITE-3
17:32
<
jhovold >
as you run arch, I assume we both run .36
17:32
<
jhovold >
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36
17:35
<
jhovold >
heh, forgot to disconnect the USB-C ethernet, the wifi numbers are 473/523 Mbits/s (down/up)
17:52
<
bamse >
jhovold: yeah, got .36 here as well
17:53
<
Dylanger >
jenneron: I successfully expanded Kernel Partition 1 via deleting the 2nd Kernel partition, now I have a 64MB kernel partition and I got to leave my user LUKs partition alone đ
17:53
<
Dylanger >
Gonna look into grabbing Fedora's Kernel and packaging it into a depthcharge compatible kernel image, then SELinux should work
17:56
<
bamse >
jhovold: perhaps we could just propose elan,<pid> as compatibles for those touchscreens?
18:10
hightower4 has joined #aarch64-laptops
18:16
hightower3 has quit [Ping timeout: 480 seconds]
18:40
matthias_bgg has quit [Quit: Leaving]
18:43
jglathe_ has quit [Remote host closed the connection]
18:46
jglathe_x13s has joined #aarch64-laptops
18:52
<
jglathe_x13s >
on 6.8-rc5 now, yay the pmic_glink errors are gone
19:00
Mary has joined #aarch64-laptops
19:04
Mary has joined #aarch64-laptops
19:56
hightower3 has joined #aarch64-laptops
20:02
hightower4 has quit [Ping timeout: 480 seconds]
22:42
hightower4 has joined #aarch64-laptops
22:43
cyrinux3 has joined #aarch64-laptops
22:46
cyrinux has quit [Ping timeout: 480 seconds]
22:48
hightower3 has quit [Ping timeout: 480 seconds]
23:01
cyrinux3 has quit []
23:01
cyrinux3 has joined #aarch64-laptops
23:34
hightower3 has joined #aarch64-laptops
23:37
hightower4 has quit [Read error: Connection reset by peer]