ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion
Rathann|Mobile has quit [Quit: Leaving]
lurchi_ is now known as lurchi__
lurchi__ is now known as lurchi_
lurchi_ is now known as lurchi__
lurchi__ is now known as lurchi_
stikonas has quit [Ping timeout: 252 seconds]
warpme__ has quit [Quit: Connection closed for inactivity]
kevery has quit [Quit: kevery]
vagrantc has quit [Quit: leaving]
chewitt has joined #linux-rockchip
lurchi_ is now known as lurchi__
lurchi_ has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 268 seconds]
camus1 has joined #linux-rockchip
camus has quit [Ping timeout: 252 seconds]
camus1 is now known as camus
wwilly has joined #linux-rockchip
shailangsa has quit [Ping timeout: 265 seconds]
wwilly has quit [Remote host closed the connection]
wwilly has joined #linux-rockchip
shailangsa has joined #linux-rockchip
wwilly has quit [Ping timeout: 256 seconds]
wwilly has joined #linux-rockchip
chewitt has quit [Ping timeout: 256 seconds]
wwilly has quit [Ping timeout: 252 seconds]
wwilly has joined #linux-rockchip
archetyp has joined #linux-rockchip
stikonas has joined #linux-rockchip
kevery has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
robmur01 has quit [Read error: Connection reset by peer]
robmur01 has joined #linux-rockchip
alyssa has joined #linux-rockchip
<alyssa> Anyone seen touchpads randomly fail?
<alyssa> Samsung Chromebook Plus (RK3399) mainline, Atmel maXTouch Touchpad
<alyssa> dmesg shows it failing to probe
<alyssa> atmel_mxt_ts 5-004a: __mxt_read_reg: i2c transfer failed (-6), mxt_bootloader_read: i2c recv failed (-6)
<alyssa> Used to work fine (as of last night), works fine on my other identical machine.
<alyssa> Guessing this is hardware failure but what?
<alyssa> Interesting the touchscreen works fine, that is also using the atmel_mxt_ts driver.
<alyssa> come to think of it, the touchpad on my c201 also failed back in the day
warpme__ has joined #linux-rockchip
<mps> alyssa: which kernel version
<CounterPillow> Weren't there some i2c changes recently? Would be unfortunate if that was a regression
<mps> works with kernel 5.15.4
<CounterPillow> https://patchwork.kernel.org/project/linux-rockchip/patch/20210924111528.2924251-1-megous@megous.com/ if your kernel has this, try reverting it, but I somehow doubt it's this
<alyssa> I haven't updated the kernel on either machine recently, though. Just randomly stop working..?
<mps> hmm, in last 5-8 major kernels didn't had this problem anytime
<mps> I think I started to use mainline kernels on it with version 5.2
<alyssa> *nod*
<alyssa> hence why I'm kinda suspecting hw failure
<amstan> alyssa: that's weird, idk what could possibly fail on that
<amstan> did you open the case frequently? maybe the flex is not connected all the way?
<amstan> "mxt_bootloader_read", hopefully it's not some failed tp firmware upgrade that bricked it
<alyssa> Haven't opened the case, no
<alyssa> (Technically got the machine used so don't know about its early days, but..)
<amstan> i guess an easy test is to do an i2cdetect on that bus
camus has quit [Quit: camus]
lurchi_ is now known as lurchi__
CounterPillow has quit [Quit: Bye.]
CounterPillow has joined #linux-rockchip
lurchi__ is now known as lurchi_
wwilly_ has joined #linux-rockchip
robmur01_ has joined #linux-rockchip
robmur01 has quit [Ping timeout: 256 seconds]
wwilly has quit [Ping timeout: 256 seconds]
CounterPillow has quit [Quit: Bye.]
CounterPillow has joined #linux-rockchip
lurchi_ is now known as lurchi__
<alyssa> so uh... after another reboot it's working again...
<alyssa> so not hardware failure, but evidently a heisenbug
<urja> I2C has a habit of being a heisenbus :P
<alyssa> urja: :(
warpme__ has quit [Quit: Connection closed for inactivity]
archetyp has quit [Quit: Leaving]