linux-armv7-xe303c12-only
linux-armv7-xe303c12-only copied to clipboard
Touchpad not working
Hi, I am testing the arch Linux xfce image and my touchpad does not work at all.
Any help would be nice.
Hi.
Not working at all.. may be you have different touchpad h/w.
I have try it and in my case only tapping/clicking doesn't work, but there is a simple solution for it.
I have the same issue. I dont even have anything showing up in the device box.
What did say cat /proc/bus/input/devices
and xinput list
?
In my case there are
cat /proc/bus/input/devices
I: Bus=0018 Vendor=0000 Product=0000 Version=0001
N: Name="Cypress APA Trackpad (cyapa)"
P: Phys=i2c-1-0067/input0
S: Sysfs=/devices/platform/soc/12c70000.i2c/i2c-1/1-0067/input/input0
U: Uniq=
H: Handlers=mouse0 event0
B: PROP=5
B: EV=b
B: KEY=e520 0 10000 0 0 0 0 0 0 0 0
B: ABS=6608000 1000003
I: Bus=0006 Vendor=0000 Product=0000 Version=0001
N: Name="cros_ec"
P: Phys=i2c-4-mux (chan_id 0)/input0
S: Sysfs=/devices/platform/soc/12ca0000.i2c/i2c-4/i2c-104/104-001e/i2c-arbitrator:i2c@0:embedded-controller@1e:keyboard-controller/input/input1
U: Uniq=
H: Handlers=sysrq kbd event1
B: PROP=0
B: EV=100013
B: KEY=4000 30001692 5240001f fb7fffff fffffffe
B: MSC=10
I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="gpio-keys"
P: Phys=gpio-keys/input0
S: Sysfs=/devices/platform/gpio-keys/input/input3
U: Uniq=
H: Handlers=kbd event3
B: PROP=0
B: EV=23
B: KEY=100000 0 0 0
B: SW=1
xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Cypress APA Trackpad (cyapa) id=7 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ gpio-keys id=6 [slave keyboard (3)]
↳ cros_ec
I booted into the really old Kali linux build they made and the track pad reports as "atmel maXTouch touchpad"
I: Bus=0006 Vendor=0000 Product=0000 Version=0001
N: Name="cros_ec"
P: Phys=i2c-4-mux (chan_id 0)/input0
S: Sysfs=/devices/platform/soc/12ca0000.i2c/i2c-4/i2c-104/104-001e/i2c-arbitrator:i2c@0:embedded-controller@1e:keyboard-controller/input/input0
U: Uniq=
H: Handlers=sysrq kbd event0
B: PROP=0
B: EV=100013
B: KEY=4000 30001692 5240001f fb7fffff fffffffe
B: MSC=10
I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="gpio-keys"
P: Phys=gpio-keys/input0
S: Sysfs=/devices/platform/gpio-keys/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=23
B: KEY=100000 0 0 0
B: SW=1
[user@void-glibc ~]$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ gpio-keys id=6 [slave keyboard (3)]
↳ cros_ec id=7 [slave keyboard (3)]
Actually Atmel maXTouch (atmel_mxt_ts) should be compiled as kernel module and available to modprobe like sudo modprobe atmel_mxt_ts
.
https://ww1.microchip.com/downloads/en/Appnotes/AN3084_Using_the_maXTouch_Linux_Driver_00003084A.pdf page 5 but I am not sure about dtsi files, exynos5 dtsi do not contain any Atmel maXTouch lines. And according to page 10 some firmware could be required.
Well heck, this seems a little out of my wheel house on linux knowledge. The old kali linux image I used by the way is kali-linux-2019.3-exynos.img.xz from http://old.kali.org/arm-images/kali-2019.3/ for future people if I cant figure this out.
So that mean modprobe didnt work.
probably i missed exynos5250-spring.dts
, looks like it contain some maxtouch line. Probably original Kali scripts adds it to kernel during build system. And ChromeOs uses some maxtouch firmware.
For mount chromeos disk image i was use something like:
sudo mount -o,loop,offset=$((512*319488)),ro ./chromeos_recovery.bin mountfolder
and firmware symlinks lead to opt/google/firmware
Looks like you run void-linux. Solution may be in re-signing kernel with spring dtb file. Copy exynos5250-spring.dtb
to /boot/dtb
and run modded 10-flashkernel
with sudo privileges; agree to re-sign and flash kernel. Be careful where to flash it in case you steel have chromeos. Re-signing kernel will require vboot-utils, uboot-tools, cgpt etc. I did not remember exact packages names and it installation status, so check it before re-signing
Actually dts provided with kernel source and may not work with different ver, but it is not like file itself changes from ver to ver so it may work with that dtb.
maxhouch fw and cfg may be copied to firmware dir in case dmesg gives maxtouch firmware load errors
everything runs fine up to dd: failed to open '/boot/kernel_image' no such file of directory. I went there and confirmed it is indeed not there. I was only trying void because I was going through your prebuilt images seeing if it worked on any of them. I had not actually ever heard of it before. I've only ever messed around with debian and arch distros before.
There are was changes in kernel package. That script taken from new ver, probably some incompatibilities. Ok, i will try to recompile kernel with extra dtb files.
Recompiled kernel void-glibc.zip void-musl.zip deb-arch.zip
deb package works as previous in my devuan system, for void should too. Arch-arm package could be repacked from deb.
FIT description: Chrome OS kernel image with one or more FDT blobs
Created: Sun May 14 11:22:46 2023
Image 0 (kernel@1)
Description: kernel
Created: Sun May 14 11:22:46 2023
Type: Kernel Image (no loading done)
Compression: uncompressed
Data Size: 6797256 Bytes = 6637.95 KiB = 6.48 MiB
Image 1 (fdt@1)
Description: exynos5250-snow.dtb
Created: Sun May 14 11:22:46 2023
Type: Flat Device Tree
Compression: uncompressed
Data Size: 47585 Bytes = 46.47 KiB = 0.05 MiB
Architecture: ARM
Hash algo: sha1
Hash value: e182f465919f87834e39b6b0f9079a44de6d1a0d
Image 2 (fdt@2)
Description: exynos5250-snow-rev5.dtb
Created: Sun May 14 11:22:46 2023
Type: Flat Device Tree
Compression: uncompressed
Data Size: 47621 Bytes = 46.50 KiB = 0.05 MiB
Architecture: ARM
Hash algo: sha1
Hash value: 303341884bd97928ae19c3636a03121dfccc6cb5
Image 3 (fdt@3)
Description: exynos5250-spring.dtb
Created: Sun May 14 11:22:46 2023
Type: Flat Device Tree
Compression: uncompressed
Data Size: 44447 Bytes = 43.41 KiB = 0.04 MiB
Architecture: ARM
Hash algo: sha1
Hash value: e6a496f5242b6817676140047bd42200b7dd45b7
Default Configuration: 'conf@1'
Configuration 0 (conf@1)
Description: unavailable
Kernel: kernel@1
FDT: fdt@1
Configuration 1 (conf@2)
Description: unavailable
Kernel: kernel@1
FDT: fdt@2
Configuration 2 (conf@3)
Description: unavailable
Kernel: kernel@1
FDT: fdt@3
spring dtb is included now, i hope that help
Trying the devuan image and after installing vboot-kernel-utils to resign the kernel after running the deb. It seems like even after it seems to have completed fine, it still does not work.
edit: Forgot to include after doing all of this cat /proc/bus/input/devices and xinput list still return nothing.
Does dmesg says somthing about maxtouch fw?
I did inspect old kali disk image that successfully detected your touchpad and find out it use old Chrome Os 3.8 kernel with blobs:
- exynos5250-skate.dtb
- exynos5250-smdk5250.dtb
- exynos5250-snow-rev4.dtb
- exynos5250-snow-rev5.dtb
- exynos5250-spring.dtb and other blobs for other CPUs.
skate and snow-rev4 are not available at newer kernel source.
I added smdk blob and recompiled it but not sure this will solve the problem. deb.zip
I grabbed kernel from that old kali, like:
dd if=kali-linux-2019.3-exynos.img of=kernel_image bs=512 skip=8192 count=32768
and dd kernel_image to kernel partition of devuan; copy /lib/modules/3.18* and firmwares. Then try to boot. It boots but stuck because btrfs unsupported. So i did backup all files from root partition, reformat it to ext2, restore files and mod /etc/fstab to correspond rootfs. It boots succesfully, but slover. I guess same true for archlinuxarm or any other armv7 (glibc) distro.
Old kernel config contain same maxtouch driver but it was specified as a part of kernel and not module.
Not that I could see from dmesg. I'll try your recompile later when I get a chance. This is the most stubborn hardware.
root@devuan:~# dmesg
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 5.15.111 (root@flcl) (arm-linux-gnueabihf-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP Sun May 14 09:16:42 EDT 2023
[ 0.000000] CPU: ARMv7 Processor [410fc0f4] revision 4 (ARMv7), cr=10c5387d
[ 0.000000] CPU: div instructions available: patching division code
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000] OF: fdt: Machine model: Google Snow Rev 5+
[ 0.000000] Malformed early option 'console'
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] cma: Reserved 8 MiB at 0xbf800000
[ 0.000000] Samsung CPU ID: 0x43520010
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x0000000040000000-0x000000006fffffff]
[ 0.000000] HighMem [mem 0x0000000070000000-0x00000000bfffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000040000000-0x00000000bfffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x00000000bfffffff]
[ 0.000000] percpu: Embedded 12 pages/cpu s20108 r8192 d20852 u49152
[ 0.000000] pcpu-alloc: s20108 r8192 d20852 u49152 alloc=12*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 522560
[ 0.000000] Kernel command line: cros_secure console= console=tty0 root=PARTUUID=182ab7df-2882-4045-8ae8-5af8e4b7979b/PARTNROFF=1 rootwait rw noinitrd zswap.compressor=zstd zswap.max_pool_percent=40 audit=0
[ 0.000000] Unknown kernel command line parameters "cros_secure audit=0", will be passed to user space.
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 2046236K/2097152K available (15360K kernel code, 1164K rwdata, 3928K rodata, 1024K init, 420K bss, 42724K reserved, 8192K cma-reserved, 1302528K highmem)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] Tracing variant of Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] Exynos5250: clock setup completed, armclk=1700000000
[ 0.000000] Switching to timer-based delay loop, resolution 41ns
[ 0.000000] clocksource: mct-frc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[ 0.000001] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[ 0.000015] genirq: irq_chip COMBINER did not update eff. affinity mask of irq 57
[ 0.000325] arch_timer: cp15 timer(s) running at 24.00MHz (virt).
[ 0.000337] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[ 0.000348] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[ 0.000357] Ignoring duplicate/late registration of read_current_timer delay
[ 0.000485] Console: colour dummy device 80x30
[ 0.000666] printk: console [tty0] enabled
[ 0.000697] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=240000)
[ 0.000713] pid_max: default: 32768 minimum: 301
[ 0.001099] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.001116] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.001847] CPU: Testing write buffer coherency: ok
[ 0.001884] CPU0: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[ 0.001896] CPU0: Spectre BHB: enabling loop workaround for all CPUs
[ 0.002064] /cpus/cpu@0 missing clock-frequency property
[ 0.002091] /cpus/cpu@1 missing clock-frequency property
[ 0.002105] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.002641] Setting up static identity map for 0x40100000 - 0x40100060
[ 0.002711] rcu: Hierarchical SRCU implementation.
[ 0.003321] smp: Bringing up secondary CPUs ...
[ 0.010037] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.010044] CPU1: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[ 0.010138] smp: Brought up 1 node, 2 CPUs
[ 0.010150] SMP: Total of 2 processors activated (96.00 BogoMIPS).
[ 0.010159] CPU: All CPU(s) started in SVC mode.
[ 0.010513] devtmpfs: initialized
[ 0.017685] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[ 0.017856] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.017876] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[ 0.018123] pinctrl core: initialized pinctrl subsystem
[ 0.019133] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.020303] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.021226] thermal_sys: Registered thermal governor 'fair_share'
[ 0.021232] thermal_sys: Registered thermal governor 'bang_bang'
[ 0.021243] thermal_sys: Registered thermal governor 'step_wise'
[ 0.021251] thermal_sys: Registered thermal governor 'user_space'
[ 0.021508] cpuidle: using governor ladder
[ 0.021536] cpuidle: using governor menu
[ 0.021666] No ATAGs?
[ 0.021710] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.021723] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.021878] Serial: AMBA PL011 UART driver
[ 0.076636] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible.
[ 0.078469] cryptd: max_cpu_qlen set to 1000
[ 0.249986] raid6: neonx8 gen() 3072 MB/s
[ 0.419986] raid6: neonx8 xor() 2315 MB/s
[ 0.589992] raid6: neonx4 gen() 4393 MB/s
[ 0.759993] raid6: neonx4 xor() 3007 MB/s
[ 0.929992] raid6: neonx2 gen() 3840 MB/s
[ 1.099990] raid6: neonx2 xor() 2902 MB/s
[ 1.269996] raid6: neonx1 gen() 3295 MB/s
[ 1.439994] raid6: neonx1 xor() 2607 MB/s
[ 1.610000] raid6: int32x8 gen() 957 MB/s
[ 1.780000] raid6: int32x8 xor() 564 MB/s
[ 1.950014] raid6: int32x4 gen() 1092 MB/s
[ 2.120000] raid6: int32x4 xor() 619 MB/s
[ 2.290008] raid6: int32x2 gen() 1025 MB/s
[ 2.460004] raid6: int32x2 xor() 517 MB/s
[ 2.630008] raid6: int32x1 gen() 826 MB/s
[ 2.800026] raid6: int32x1 xor() 417 MB/s
[ 2.800036] raid6: using algorithm neonx4 gen() 4393 MB/s
[ 2.800044] raid6: .... xor() 3007 MB/s, rmw enabled
[ 2.800051] raid6: using neon recovery algorithm
[ 2.801206] iommu: Default domain type: Translated
[ 2.801219] iommu: DMA domain TLB invalidation policy: strict mode
[ 2.801328] vgaarb: loaded
[ 2.801633] SCSI subsystem initialized
[ 2.801770] libata version 3.00 loaded.
[ 2.801878] usbcore: registered new interface driver usbfs
[ 2.801907] usbcore: registered new interface driver hub
[ 2.801944] usbcore: registered new device driver usb
[ 2.802471] s3c-i2c 12c60000.i2c: slave address 0x00
[ 2.802486] s3c-i2c 12c60000.i2c: bus frequency set to 378 KHz
[ 2.803022] s3c-i2c 12c60000.i2c: i2c-0: S3C I2C adapter
[ 2.803135] s3c-i2c 12c70000.i2c: slave address 0x00
[ 2.803148] s3c-i2c 12c70000.i2c: bus frequency set to 378 KHz
[ 2.803436] s3c-i2c 12c70000.i2c: i2c-1: S3C I2C adapter
[ 2.803528] s3c-i2c 12c80000.i2c: slave address 0x00
[ 2.803540] s3c-i2c 12c80000.i2c: bus frequency set to 65 KHz
[ 2.803645] s3c-i2c 12c80000.i2c: i2c-2: S3C I2C adapter
[ 2.803748] s3c-i2c 12c90000.i2c: slave address 0x00
[ 2.803760] s3c-i2c 12c90000.i2c: bus frequency set to 65 KHz
[ 2.803873] s3c-i2c 12c90000.i2c: i2c-3: S3C I2C adapter
[ 2.804003] s3c-i2c 12ca0000.i2c: slave address 0x00
[ 2.804015] s3c-i2c 12ca0000.i2c: bus frequency set to 65 KHz
[ 2.804107] s3c-i2c 12ca0000.i2c: i2c-4: S3C I2C adapter
[ 2.804189] s3c-i2c 12cb0000.i2c: slave address 0x00
[ 2.804200] s3c-i2c 12cb0000.i2c: bus frequency set to 65 KHz
[ 2.804303] s3c-i2c 12cb0000.i2c: i2c-5: S3C I2C adapter
[ 2.804406] s3c-i2c 12cd0000.i2c: slave address 0x00
[ 2.804418] s3c-i2c 12cd0000.i2c: bus frequency set to 65 KHz
[ 2.804635] i2c 7-0020: Fixing up cyclic dependency with 145b0000.dp-controller
[ 2.804675] i2c 7-0020: Fixing up cyclic dependency with panel
[ 2.805067] s3c-i2c 12cd0000.i2c: i2c-7: S3C I2C adapter
[ 2.805228] s3c-i2c 12ce0000.i2c: slave address 0x00
[ 2.805241] s3c-i2c 12ce0000.i2c: bus frequency set to 378 KHz
[ 2.805400] s3c-i2c 12ce0000.i2c: i2c-8: S3C I2C adapter
[ 2.805524] mc: Linux media interface: v0.10
[ 2.805547] videodev: Linux video capture interface: v2.00
[ 2.805600] pps_core: LinuxPPS API ver. 1 registered
[ 2.805609] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
[ 2.805625] PTP clock support registered
[ 2.805656] EDAC MC: Ver: 3.0.0
[ 2.805993] Advanced Linux Sound Architecture Driver Initialized.
[ 2.806669] clocksource: Switched to clocksource mct-frc
[ 2.806850] VFS: Disk quotas dquot_6.6.0
[ 2.806909] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 2.811059] NET: Registered PF_INET protocol family
[ 2.811180] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
[ 2.811769] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
[ 2.811794] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 2.811808] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
[ 2.811851] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 2.811930] TCP: Hash tables configured (established 8192 bind 8192)
[ 2.812049] MPTCP token hash table entries: 1024 (order: 2, 16384 bytes, linear)
[ 2.812100] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 2.812127] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 2.812271] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 2.812297] NET: Registered PF_XDP protocol family
[ 2.812309] PCI: CLS 0 bytes, default 64
[ 2.812717] armv7-pmu pmu: hw perfevents: no interrupt-affinity property, guessing.
[ 2.812931] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counters available
[ 2.815494] Initialise system trusted keyrings
[ 2.815591] workingset: timestamp_bits=14 max_order=19 bucket_order=5
[ 2.817849] zbud: loaded
[ 2.819870] Key type cifs.spnego registered
[ 2.819920] Key type cifs.idmap registered
[ 2.820152] fuse: init (API version 7.34)
[ 2.860981] NET: Registered PF_ALG protocol family
[ 2.861005] xor: measuring software checksum speed
[ 2.863844] arm4regs : 3478 MB/sec
[ 2.867630] 8regs : 2621 MB/sec
[ 2.871485] 32regs : 2558 MB/sec
[ 2.872901] neon : 6993 MB/sec
[ 2.872911] xor: using function: neon (6993 MB/sec)
[ 2.872921] Key type asymmetric registered
[ 2.872929] Asymmetric key parser 'x509' registered
[ 2.872979] bounce: pool size: 64 pages
[ 2.873020] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[ 2.873032] io scheduler mq-deadline registered
[ 2.873041] io scheduler kyber registered
[ 2.873113] io scheduler bfq registered
[ 2.874494] samsung-usb2-phy 12130000.phy: supply vbus not found, using dummy regulator
[ 2.874925] exynos5_usb3drd_phy 12100000.phy: supply vbus-boost not found, using dummy regulator
[ 2.878691] dma-pl330 121a0000.pdma: Loaded driver for PL330 DMAC-241330
[ 2.878709] dma-pl330 121a0000.pdma: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[ 2.879788] dma-pl330 121b0000.pdma: Loaded driver for PL330 DMAC-241330
[ 2.879801] dma-pl330 121b0000.pdma: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[ 2.880162] dma-pl330 10800000.mdma: Loaded driver for PL330 DMAC-241330
[ 2.880174] dma-pl330 10800000.mdma: DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[ 2.880544] dma-pl330 11c10000.mdma: Loaded driver for PL330 DMAC-241330
[ 2.880555] dma-pl330 11c10000.mdma: DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[ 2.880705] soc soc0: Exynos: CPU[EXYNOS5250] PRO_ID[0x43520010] REV[0x10] Detected
[ 2.881522] Serial: 8250/16550 driver, 6 ports, IRQ sharing enabled
[ 2.882877] Serial: AMBA driver
[ 2.883015] 12c00000.serial: ttySAC0 at MMIO 0x12c00000 (irq = 64, base_baud = 0) is a S3C6400/10
[ 2.883294] 12c10000.serial: ttySAC1 at MMIO 0x12c10000 (irq = 65, base_baud = 0) is a S3C6400/10
[ 2.883530] 12c20000.serial: ttySAC2 at MMIO 0x12c20000 (irq = 66, base_baud = 0) is a S3C6400/10
[ 2.883750] 12c30000.serial: ttySAC3 at MMIO 0x12c30000 (irq = 67, base_baud = 0) is a S3C6400/10
[ 2.884894] exynos-trng 10830600.rng: Exynos True Random Number Generator.
[ 2.885214] sdhci: Secure Digital Host Controller Interface driver
[ 2.885224] sdhci: Copyright(c) Pierre Ossman
[ 2.885339] Synopsys Designware Multimedia Card Interface Driver
[ 2.885672] VUB300 Driver rom wait states = 1C irqpoll timeout = 0400
[ 2.885845] dwmmc_exynos 12200000.mmc: IDMAC supports 32-bit address mode.
[ 2.885968] dwmmc_exynos 12200000.mmc: Using internal DMA controller.
[ 2.885985] dwmmc_exynos 12200000.mmc: Version ID is 241a
[ 2.886035] dwmmc_exynos 12200000.mmc: DW MMC controller at irq 121,32 bit host data width,128 deep fifo
[ 2.886161] mmc_host mmc0: card is non-removable.
[ 2.886168] dwmmc_exynos 12220000.mmc: IDMAC supports 32-bit address mode.
[ 2.886246] dwmmc_exynos 12220000.mmc: Using internal DMA controller.
[ 2.886262] dwmmc_exynos 12220000.mmc: Version ID is 241a
[ 2.886295] dwmmc_exynos 12220000.mmc: DW MMC controller at irq 122,32 bit host data width,128 deep fifo
[ 2.886401] dwmmc_exynos 12220000.mmc: Got WP GPIO
[ 2.886717] dwmmc_exynos 12230000.mmc: IDMAC supports 32-bit address mode.
[ 2.886790] dwmmc_exynos 12230000.mmc: Using internal DMA controller.
[ 2.886805] dwmmc_exynos 12230000.mmc: Version ID is 241a
[ 2.886835] dwmmc_exynos 12230000.mmc: DW MMC controller at irq 123,32 bit host data width,128 deep fifo
[ 2.887047] usbcore: registered new interface driver vub300
[ 2.887082] usbcore: registered new interface driver ushc
[ 2.887092] sdhci-pltfm: SDHCI platform and OF driver helper
[ 2.887406] [drm] Initialized vgem 1.0.0 20120112 for vgem on minor 0
[ 2.887640] exynos4-fb 14400000.fimd: Adding to iommu group 0
[ 2.888199] OF: graph: no port node found in /soc/fimd@14400000
[ 2.888655] exynos-mixer 14450000.mixer: Adding to iommu group 1
[ 2.889600] exynos-rotator 11c00000.rotator: Adding to iommu group 2
[ 2.895591] loop: module loaded
[ 2.896724] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[ 2.896803] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[ 2.897744] P1.8V_LDO_OUT2: Bringing 1500000uV into 1800000-1800000uV
[ 2.914276] Loading iSCSI transport class v2.0-870.
[ 2.916573] exynos-dwc3 soc:usb_dwc3: supply vdd33 not found, using dummy regulator
[ 2.916695] exynos-dwc3 soc:usb_dwc3: supply vdd10 not found, using dummy regulator
[ 2.917902] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 2.917920] ehci-pci: EHCI PCI platform driver
[ 2.917960] ehci-platform: EHCI generic platform driver
[ 2.918111] ehci-exynos: EHCI Exynos driver
[ 2.918424] exynos-ehci 12110000.usb: EHCI Host Controller
[ 2.918544] exynos-ehci 12110000.usb: new USB bus registered, assigned bus number 1
[ 2.918726] exynos-ehci 12110000.usb: irq 124, io mem 0x12110000
[ 2.946692] exynos-ehci 12110000.usb: USB 2.0 started, EHCI 1.00
[ 2.946872] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[ 2.946888] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.946900] usb usb1: Product: EHCI Host Controller
[ 2.946908] usb usb1: Manufacturer: Linux 5.15.111 ehci_hcd
[ 2.946916] usb usb1: SerialNumber: 12110000.usb
[ 2.947218] hub 1-0:1.0: USB hub found
[ 2.947252] hub 1-0:1.0: 3 ports detected
[ 2.947629] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 2.947642] ohci-platform: OHCI generic platform driver
[ 2.947783] ohci-exynos: OHCI Exynos driver
[ 2.947957] exynos-ohci 12120000.usb: USB Host Controller
[ 2.948041] exynos-ohci 12120000.usb: new USB bus registered, assigned bus number 2
[ 2.948108] exynos-ohci 12120000.usb: irq 124, io mem 0x12120000
[ 2.980764] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 52000000Hz, actual 50000000HZ div = 0)
[ 2.983181] mmc0: new DDR MMC card at address 0001
[ 2.983656] mmcblk0: mmc0:0001 SEM16G 14.7 GiB
[ 2.987816] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12
[ 2.988936] mmcblk0boot0: mmc0:0001 SEM16G 2.00 MiB
[ 2.989847] mmcblk0boot1: mmc0:0001 SEM16G 2.00 MiB
[ 2.990530] mmcblk0rpmb: mmc0:0001 SEM16G 128 KiB, chardev (243:0)
[ 3.020911] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.15
[ 3.020929] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.020941] usb usb2: Product: USB Host Controller
[ 3.020950] usb usb2: Manufacturer: Linux 5.15.111 ohci_hcd
[ 3.020958] usb usb2: SerialNumber: 12120000.usb
[ 3.021241] hub 2-0:1.0: USB hub found
[ 3.021286] hub 2-0:1.0: 3 ports detected
[ 3.022100] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[ 3.022195] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 3
[ 3.022510] xhci-hcd xhci-hcd.1.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x0000000002010010
[ 3.022583] xhci-hcd xhci-hcd.1.auto: irq 162, io mem 0x12000000
[ 3.022598] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[ 3.022679] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 4
[ 3.022696] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0 SuperSpeed
[ 3.022832] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[ 3.022848] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.022859] usb usb3: Product: xHCI Host Controller
[ 3.022868] usb usb3: Manufacturer: Linux 5.15.111 xhci-hcd
[ 3.022876] usb usb3: SerialNumber: xhci-hcd.1.auto
[ 3.023131] hub 3-0:1.0: USB hub found
[ 3.023162] hub 3-0:1.0: 1 port detected
[ 3.023415] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[ 3.023526] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.15
[ 3.023540] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.023551] usb usb4: Product: xHCI Host Controller
[ 3.023559] usb usb4: Manufacturer: Linux 5.15.111 xhci-hcd
[ 3.023567] usb usb4: SerialNumber: xhci-hcd.1.auto
[ 3.023836] hub 4-0:1.0: USB hub found
[ 3.023866] hub 4-0:1.0: 1 port detected
[ 3.024126] usbcore: registered new interface driver cdc_acm
[ 3.024137] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 3.024170] usbcore: registered new interface driver usblp
[ 3.024196] usbcore: registered new interface driver cdc_wdm
[ 3.024319] usbcore: registered new interface driver uas
[ 3.024369] usbcore: registered new interface driver usb-storage
[ 3.024394] usbcore: registered new interface driver ums-cypress
[ 3.024417] usbcore: registered new interface driver ums_eneub6250
[ 3.024440] usbcore: registered new interface driver ums-freecom
[ 3.024463] usbcore: registered new interface driver ums-isd200
[ 3.024609] mousedev: PS/2 mouse device common for all mice
[ 3.155062] max77686-rtc max77686-rtc: registered as rtc0
[ 3.187714] max77686-rtc max77686-rtc: setting system clock to 2023-05-15T15:54:31 UTC (1684166071)
[ 3.188328] s3c-rtc 101e0000.rtc: rtc disabled, re-enabling
[ 3.188498] s3c-rtc 101e0000.rtc: registered as rtc1
[ 3.188721] i2c_dev: i2c /dev entries driver
[ 3.190498] tps65090 104-0048: No cache defaults, reading back from HW
[ 3.194839] tps65090-pmic tps65090-pmic: could not find DCDC external control GPIO
[ 3.194860] tps65090-pmic tps65090-pmic: could not find DCDC external control GPIO
[ 3.194878] tps65090-pmic tps65090-pmic: could not find DCDC external control GPIO
[ 3.194933] TPS65090_RAILSDCDC1: supplied by vbat-supply
[ 3.195706] TPS65090_RAILSDCDC2: supplied by vbat-supply
[ 3.196462] TPS65090_RAILSDCDC3: supplied by vbat-supply
[ 3.197272] vcd_led: supplied by vbat-supply
[ 3.197977] video_mid: supplied by vbat-supply
[ 3.201015] wwan_r: supplied by vbat-supply
[ 3.204102] sdcard: supplied by vbat-supply
[ 3.205271] camout: supplied by vbat-supply
[ 3.208362] lcd_vdd: supplied by vbat-supply
[ 3.209045] video_mid_1a: supplied by vbat-supply
[ 3.212072] TPS65090_RAILSLDO1: supplied by vbat-supply
[ 3.212162] TPS65090_RAILSLDO2: supplied by vbat-supply
[ 3.212501] i2c i2c-4: Added multiplexed i2c bus 104
[ 3.214552] exynos-tmu 10060000.tmu: Regulator node (vtmu) not found
[ 3.215283] hid: raw HID events driver (C) Jiri Kosina
[ 3.215452] usbcore: registered new interface driver usbhid
[ 3.215464] usbhid: USB HID core driver
[ 3.239897] cros-ec-dev cros-ec-dev.3.auto: cannot get EC features: -95/1
[ 3.246683] usb 1-1: new high-speed USB device number 2 using exynos-ehci
[ 3.250842] input: cros_ec as /devices/platform/soc/12ca0000.i2c/i2c-4/i2c-104/104-001e/i2c-arbitrator:i2c@0:embedded-controller@1e:keyboard-controller/input/input0
[ 3.259181] cros-ec-i2c 104-001e: Chrome EC device registered
[ 3.261772] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s
[ 3.262373] snow-audio sound: Failed parsing codec node
[ 3.262850] NET: Registered PF_INET6 protocol family
[ 3.264678] Segment Routing with IPv6
[ 3.264695] RPL Segment Routing with IPv6
[ 3.264732] In-situ OAM (IOAM) with IPv6
[ 3.264788] NET: Registered PF_PACKET protocol family
[ 3.265014] Key type dns_resolver registered
[ 3.265420] ThumbEE CPU extension supported.
[ 3.265436] Registering SWP/SWPB emulation handler
[ 3.266576] registered taskstats version 1
[ 3.266597] Loading compiled-in X.509 certificates
[ 3.267975] zswap: loaded using pool zstd/z3fold
[ 3.268300] Key type .fscrypt registered
[ 3.268312] Key type fscrypt-provisioning registered
[ 3.268995] Btrfs loaded, crc32c=crc32c-generic, zoned=no, fsverity=yes
[ 3.270846] dwmmc_exynos 12230000.mmc: IDMAC supports 32-bit address mode.
[ 3.270982] dwmmc_exynos 12230000.mmc: Using internal DMA controller.
[ 3.270997] dwmmc_exynos 12230000.mmc: Version ID is 241a
[ 3.271019] dwmmc_exynos 12230000.mmc: DW MMC controller at irq 123,32 bit host data width,128 deep fifo
[ 3.271212] dwmmc_exynos 12230000.mmc: allocated mmc-pwrseq
[ 3.271227] mmc_host mmc2: card is non-removable.
[ 3.272873] OF: graph: no port node found in /soc/hdmi@14530000
[ 3.274120] panfrost 11800000.gpu: clock rate = 533000000
[ 3.275494] panfrost 11800000.gpu: mali-t600 id 0x600 major 0x0 minor 0x0 status 0x1
[ 3.275511] panfrost 11800000.gpu: features: 00000000,10206000, issues: 00000000,31b4dfff
[ 3.275525] panfrost 11800000.gpu: Features: L2:0x07110206 Shader:0x00000000 Tiler:0x00000809 Mem:0x1 MMU:0x00002830 AS:0xf JS:0x7
[ 3.275540] panfrost 11800000.gpu: shader_present=0xf l2_present=0x1
[ 3.276477] [drm] Initialized panfrost 1.2.0 20180908 for 11800000.gpu on minor 1
[ 3.276869] snow-audio sound: ASoC: failed to instantiate card -517
[ 3.277808] [drm] Exynos DRM: using 14400000.fimd device for DMA mapping operations
[ 3.277850] exynos-drm exynos-drm: bound 14400000.fimd (ops fimd_component_ops)
[ 3.277944] exynos-drm exynos-drm: bound 14450000.mixer (ops mixer_component_ops)
[ 3.278194] exynos-drm exynos-drm: bound 145b0000.dp-controller (ops exynos_dp_ops)
[ 3.278221] exynos-drm exynos-drm: bound 14530000.hdmi (ops hdmi_component_ops)
[ 3.278241] exynos-rotator 11c00000.rotator: The exynos rotator has been probed successfully
[ 3.278252] exynos-drm exynos-drm: bound 11c00000.rotator (ops rotator_component_ops)
[ 3.284083] mmc_host mmc2: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[ 3.347324] mmc_host mmc2: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[ 3.351191] mmc2: new high speed SDIO card at address 0001
[ 3.452011] usb 1-1: New USB device found, idVendor=090c, idProduct=1000, bcdDevice=11.00
[ 3.452020] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.452025] usb 1-1: Product: Flash Drive DUO
[ 3.452029] usb 1-1: Manufacturer: Samsung
[ 3.452032] usb 1-1: SerialNumber: 0332115080010283
[ 3.453103] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 3.453468] scsi host0: usb-storage 1-1:1.0
[ 4.237235] Console: switching to colour frame buffer device 170x48
[ 4.255579] exynos-drm exynos-drm: [drm] fb0: exynosdrmfb frame buffer device
[ 4.255900] [drm] Initialized exynos 1.1.0 20180330 for exynos-drm on minor 2
[ 4.256342] snow-audio sound: ASoC: failed to instantiate card -517
[ 4.256805] snow-audio sound: ASoC: failed to instantiate card -517
[ 4.257520] input: gpio-keys as /devices/platform/gpio-keys/input/input1
[ 4.259010] ALSA device list:
[ 4.259052] No soundcards found.
[ 4.259089] snow-audio sound: ASoC: failed to instantiate card -517
[ 4.259245] Waiting for root device PARTUUID=182ab7df-2882-4045-8ae8-5af8e4b7979b/PARTNROFF=1...
[ 4.807946] scsi 0:0:0:0: Direct-Access Samsung Flash Drive DUO 1100 PQ: 0 ANSI: 6
[ 4.809409] sd 0:0:0:0: [sda] 125304832 512-byte logical blocks: (64.2 GB/59.8 GiB)
[ 4.812028] sd 0:0:0:0: [sda] Write Protect is off
[ 4.813659] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 4.814661] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 4.831194] sda: sda1 sda2
[ 4.836154] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 4.838172] snow-audio sound: ASoC: failed to instantiate card -517
[ 4.866271] F2FS-fs (sda2): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[ 4.867924] F2FS-fs (sda2): Can't find valid F2FS filesystem in 1th superblock
[ 4.870021] F2FS-fs (sda2): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[ 4.871626] F2FS-fs (sda2): Can't find valid F2FS filesystem in 2th superblock
[ 4.874781] BTRFS: device label rootfs devid 1 transid 96 /dev/root scanned by swapper/0 (1)
[ 4.878781] BTRFS info (device sda2): using crc32c (crc32c-generic) checksum algorithm
[ 4.880399] BTRFS info (device sda2): using free space tree
[ 4.881966] BTRFS info (device sda2): has skinny extents
[ 4.917528] VFS: Mounted root (btrfs filesystem) on device 0:16.
[ 4.920395] devtmpfs: mounted
[ 4.922260] Freeing unused kernel image (initmem) memory: 1024K
[ 4.936818] Run /sbin/init as init process
[ 4.938314] with arguments:
[ 4.938317] /sbin/init
[ 4.938320] cros_secure
[ 4.938323] with environment:
[ 4.938326] HOME=/
[ 4.938328] TERM=linux
[ 4.938331] audit=0
[ 6.106769] udevd[348]: starting version 3.2.9
[ 6.156777] random: udevd: uninitialized urandom read (16 bytes read)
[ 6.162008] random: udevd: uninitialized urandom read (16 bytes read)
[ 6.163522] random: udevd: uninitialized urandom read (16 bytes read)
[ 6.222064] udevd[350]: starting eudev-3.2.9
[ 6.531233] snow-audio sound: ASoC: failed to instantiate card -517
[ 6.616507] s5p-secss 10830000.sss: s5p-sss driver registered
[ 6.620654] s3c2410-wdt 101d0000.watchdog: watchdog inactive, reset disabled, irq disabled
[ 6.627378] max98090 7-0010: MAX98090 REVID=0x43
[ 6.631439] max98090 7-0010: use default 2.8v micbias
[ 6.651923] s5p-mfc 11000000.codec: Adding to iommu group 3
[ 6.657606] s5p-mfc 11000000.codec: preallocated 8 MiB buffer for the firmware and context buffers
[ 6.673308] s5p-mfc 11000000.codec: decoder registered as /dev/video0
[ 6.675018] s5p-mfc 11000000.codec: encoder registered as /dev/video1
[ 6.859703] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 6.866227] Bluetooth: Core ver 2.22
[ 6.867906] NET: Registered PF_BLUETOOTH protocol family
[ 6.869399] Bluetooth: HCI device and connection manager initialized
[ 6.870971] Bluetooth: HCI socket layer initialized
[ 6.872490] Bluetooth: L2CAP socket layer initialized
[ 6.873935] Bluetooth: SCO socket layer initialized
[ 6.893919] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 6.910451] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
[ 6.932679] Bluetooth: vendor=0x2df, device=0x912a, class=255, fn=2
[ 6.971987] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 7.027580] sbs-battery 104-000b: sbs-battery: battery gas gauge device registered
[ 7.046609] tps65090-charger tps65090-charger: DMA mask not set
[ 7.048474] tps65090-charger tps65090-charger: IRQ index 0 not found
[ 7.051764] cros-ec-pchg cros-ec-pchg.7.auto: Unable to get number or ports (err:-95)
[ 7.053254] cros-ec-pchg cros-ec-pchg.7.auto: No peripheral charge ports (err:-95)
[ 7.094369] power_supply sbs-104-000b: driver failed to report `technology' property: -74
[ 7.106384] power_supply sbs-104-000b: driver failed to report `technology' property: -74
[ 7.128084] BTRFS info: devid 1 device path /dev/root changed to /dev/sda2 scanned by udevd (365)
[ 7.196739] exynos-gsc 13e00000.gsc: Adding to iommu group 4
[ 7.199237] exynos-gsc 13e10000.gsc: Adding to iommu group 5
[ 7.201282] exynos-gsc 13e20000.gsc: Adding to iommu group 6
[ 7.203249] exynos-gsc 13e30000.gsc: Adding to iommu group 7
[ 7.266699] random: crng init done
[ 7.268112] random: 8 urandom warning(s) missed due to ratelimiting
[ 7.527568] power_supply sbs-104-000b: driver failed to report `technology' property: -74
[ 7.533193] power_supply sbs-104-000b: driver failed to report `technology' property: -74
[ 7.665699] mwifiex_sdio mmc2:0001:1: info: FW download over, size 533976 bytes
[ 7.796731] mwifiex_sdio mmc2:0001:1: WLAN FW is active
[ 8.276810] btmrvl_sdio mmc2:0001:2: sdio device tree data not available
[ 8.325417] mwifiex_sdio mmc2:0001:1: CMD_RESP: cmd 0x242 error, result=0x2
[ 8.326900] mwifiex_sdio mmc2:0001:1: mwifiex_process_cmdresp: cmd 0x242 failed during initialization
[ 8.348391] mwifiex_sdio mmc2:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (14.68.29.p59)
[ 8.349989] mwifiex_sdio mmc2:0001:1: driver_version = mwifiex 1.0 (14.68.29.p59)
[ 8.815793] BTRFS info (device sda2): use zstd compression, level 5
[ 8.817236] BTRFS info (device sda2): enabling ssd optimizations
[ 9.145182] device-mapper: ioctl: 4.45.0-ioctl (2021-03-22) initialised: [email protected]
[ 10.322154] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 10.323474] Bluetooth: BNEP filters: protocol multicast
[ 10.324787] Bluetooth: BNEP socket layer initialized
[ 17.325374] power_supply sbs-104-000b: driver failed to report `technology' property: -74
[ 17.327528] power_supply sbs-104-000b: driver failed to report `manufacturer' property: -74
[ 17.329558] power_supply sbs-104-000b: driver failed to report `model_name' property: -74
[ 19.881510] mwifiex_sdio mmc2:0001:1: info: trying to associate to bssid a0:63:91:d5:bd:4f
[ 19.907926] mwifiex_sdio mmc2:0001:1: info: associated to bssid a0:63:91:d5:bd:4f successfully
[ 19.932509] IPv6: ADDRCONF(NETDEV_CHANGE): mlan0: link becomes ready
[ 19.933911] mwifiex_sdio mmc2:0001:1: CMD_RESP: cmd 0x23f error, result=0x2
root@devuan:~#
Log has link to wifi firmware only.
So now we know wich blob is used [ 0.000000] OF: fdt: Machine model: Google Snow Rev 5+
I guess touchpad config may be integrated to it.
In my case its [ 0.000000] OF: fdt: Machine model: Google Snow
I did make some changes in blobs source and recompile it again. Now dmesg shows something that was absent before:
lsmod | grep atmel
atmel_mxt_ts 40960 0
dmesg | grep atmel
[ 6.226910] atmel_mxt_ts 1-004b: supply vdda not found, using dummy regulator
[ 6.227047] atmel_mxt_ts 1-004b: supply vdd not found, using dummy regulator
[ 6.230993] genirq: Flags mismatch irq 163. 00082002 (atmel_mxt_tp) vs. 00002002 (cyapa)
[ 6.231630] atmel_mxt_ts 1-004b: Failed to register interrupt
[ 6.232342] atmel_mxt_ts: probe of 1-004b failed with error -16
[ 6.232553] atmel_mxt_ts 1-0025: supply vdda not found, using dummy regulator
[ 6.232644] atmel_mxt_ts 1-0025: supply vdd not found, using dummy regulator
[ 6.234570] genirq: Flags mismatch irq 163. 00082002 (atmel_mxt_tp) vs. 00002002 (cyapa)
[ 6.234628] atmel_mxt_ts 1-0025: Failed to register interrupt
[ 6.234832] atmel_mxt_ts: probe of 1-0025 failed with error -16
wow that did something. It is showing up as the maXTouch Touchscreen. It works but it is acting as if it is a touch screen. So where you touch it the mouse goes there. Was there a flag for touchscreen vs touchpad? I'm amazed its even working. Very close
Edit: Have you seen these? https://github.com/atmel-maxtouch/maXTouch_linux https://www.kernel.org/doc/Documentation/devicetree/bindings/input/atmel%2Cmaxtouch.txt
I dont know if anything is of use here. I'm not super familiar with Kernel stuff.
Kernel driver itself is for touchscreens. Maybe chrome os firmware config reassigns it as a trackpad. Do you copied maxtouch.fw and maxtouch.cfg to /lib/firmware ?
I am not a C developer, i just writed by analogy to chromeos kernel 3.18. Patch:
diff -Naur a/arch/arm/boot/dts/exynos5250-snow-common.dtsi b/arch/arm/boot/dts/exynos5250-snow-common.dtsi
--- a/arch/arm/boot/dts/exynos5250-snow-common.dtsi 2023-05-11 14:00:40.000000000 +0000
+++ b/arch/arm/boot/dts/exynos5250-snow-common.dtsi 2023-05-16 23:30:03.286646457 +0000
@@ -446,6 +446,22 @@
interrupt-parent = <&gpx1>;
wakeup-source;
};
+
+ trackpad@4b {
+ reg = <0x4b>;
+ compatible = "atmel,atmel_mxt_tp";
+ interrupts = <2 IRQ_TYPE_NONE>;
+ interrupt-parent = <&gpx1>;
+ wakeup-source;
+ };
+
+ trackpad@25 {
+ reg = <0x25>;
+ compatible = "atmel,atmel_mxt_tp";
+ interrupts = <2 IRQ_TYPE_NONE>;
+ interrupt-parent = <&gpx1>;
+ wakeup-source;
+ };
};
/*
I was not seen that. Thanks. I did change atmel_mxt_tp to maxtouch and recompile it. To try it you need to overwrite files at /boot/dtbs , re-sign kernel, re-flash kernel and reboot. exynos5250.zip
I started with a fresh image and reflashed and resigned with the new dtb files. I also placed the firmware files in /lib/firmware. However it still acts like the touchscreen and reports in dmesg as atmel_mxt_ts.
edit: console output
root@devuan:~# lsmod | grep atmel
atmel_mxt_ts 40960 0
root@devuan:~# dmesg | grep atmel
[ 6.796998] atmel_mxt_ts 1-004b: supply vdda not found, using dummy regulator
[ 6.798671] atmel_mxt_ts 1-004b: supply vdd not found, using dummy regulator
[ 6.875503] atmel_mxt_ts 1-004b: Family: 130 Variant: 35 Firmware V2.0.AA Objects: 23
[ 6.878470] atmel_mxt_ts 1-0025: supply vdda not found, using dummy regulator
[ 6.880571] atmel_mxt_ts 1-0025: supply vdd not found, using dummy regulator
[ 6.884359] atmel_mxt_ts 1-004b: Resetting device
[ 6.887776] atmel_mxt_ts 1-0025: Failed to register interrupt
[ 6.889668] atmel_mxt_ts: probe of 1-0025 failed with error -16
[ 7.038353] atmel_mxt_ts 1-004b: Touchscreen size X2039Y1359
root@devuan:~#
Making that driver detect device as a trackpad may require more diging in subject or maybe conculting with developers.
I find some example how to assign touchpad as touchscreen or something like that, guess it could be done in reverse. https://askubuntu.com/questions/822272/monitor-is-detecting-as-touchpad-instead-of-touchscreen https://unix.stackexchange.com/questions/129339/touchscreen-and-mouse-as-separate-inputs
edit: I changed dts in similar way to spring.dts but not sure about pinctrl-names and pinctrl-0 so it was commented. Added gpio-keymap and interrupt type changed to edge_falling. Patch is
diff -Naur a/arch/arm/boot/dts/exynos5250-snow-common.dtsi b/arch/arm/boot/dts/exynos5250-snow-common.dtsi
--- a/arch/arm/boot/dts/exynos5250-snow-common.dtsi 2023-05-11 14:00:40.000000000 +0000
+++ b/arch/arm/boot/dts/exynos5250-snow-common.dtsi 2023-05-16 23:30:03.286646457 +0000
@@ -446,6 +446,40 @@
interrupt-parent = <&gpx1>;
wakeup-source;
};
+
+ trackpad@4b {
+ reg = <0x4b>;
+ compatible = "atmel,atmel,maxtouch";
+ //interrupts = <2 IRQ_TYPE_NONE>;
+ interrupts = <2 IRQ_TYPE_EDGE_FALLING>;
+ interrupt-parent = <&gpx1>;
+ //pinctrl-names = "default";
+ //pinctrl-0 = <&trackpad_irq>;
+ linux,gpio-keymap = <KEY_RESERVED
+ KEY_RESERVED
+ KEY_RESERVED
+ KEY_RESERVED
+ KEY_RESERVED
+ BTN_LEFT>;
+ wakeup-source;
+ };
+
+ trackpad@25 {
+ reg = <0x25>;
+ compatible = "atmel,maxtouch";
+ //interrupts = <2 IRQ_TYPE_NONE>;
+ interrupts = <2 IRQ_TYPE_EDGE_FALLING>;
+ interrupt-parent = <&gpx1>;
+ //pinctrl-names = "default";
+ //pinctrl-0 = <&trackpad_irq>;
+ linux,gpio-keymap = <KEY_RESERVED
+ KEY_RESERVED
+ KEY_RESERVED
+ KEY_RESERVED
+ KEY_RESERVED
+ BTN_LEFT>;
+ wakeup-source;
+ };
};
/*
I never got notified about the edit and decided to comeback and see if I missed a notification. Your changed dtb files did the trick. Tapping and clicking works. Even 2 finger scrolling. I also shows up as a touchpad in the system. Amazing work, thank you for taking the time to figure out the issue with this very old and outdated Chromebook. Now I just need to look into getting it to run on the internal emmc. Any leads where I could start looking for that. I've seen a couple sketchy guides but don't want to nuke this laptop. I don't know how tied in the CTRL+U boot loader is tied into the partitions of the EMMC.
Edit: ok starting from a fresh image here is what I did to getting it working. First I install vboot-kernel-utils. I then run the file .deb file located in deb_pkg.zip. I tried doing it without this deb file but I suspect it contains the spring.dts file and it is needed. Then I copy over the config and firmware files from the maxtouch.zip to lib/firmware. Then from the latest dtb.zip i copy those to boot/dtbs and then run the reflash in boot/reflash and say yes to both prompts. Then I restart and have a working touchpad.
I am glad it helped.
With my model it is possible to brick it in case of removing chrome os, exiting from dev mode and rebooting in same time. So my suggestion is do not exit from dev mode until you may succesfully boot from emmc. Disconnecting battery or complete discharge leads to exiting from dev mode too.
Guide actually same for emmc as for usb or sd-card (micro-sd-card + sd adapter), diffs only on specified device. Usually /dev/sda is a usb, /dev/mmcblk1 - sd-card and /dev/mmcblk0 - emmc (partitions like /dev/mmcblk0p1 and so on). You may manually repart it like described on archlinuxarm guide. Be aware, on step 7 of that guide should be used apostrophes and not quotes. It has different meaning for shell. At first time i was stuck there. Or you may use edim script to create disk image with same size as emmc, write there rootfs and kernel than dd disk image to emmc. Demonstartion of using edim script on main page of this project. In my case emmc size is 15028M. edim script creates only kernel and rootfs partitions. With manual method you may add swap partition or use another sheme (i suggest to try it on usb or sdcard firstly). Partitioning with anything other than cgpt with hight chance will lead to unbootable system.
To boot from emmc at dev mode you need to press Ctrl+D
As I know there is another method with flashing unverified uboot, in that case it does not matter wich util you use for patitioning disk.. but i never tryed it.
edit: Actually in the last kernel deb i returned to previous scheme without spring.dtb because of trying to integrate atmel trackpad support to snow and snow-rev5 dtbs
Awesome thank you for all the help. I went ahead and compiled everything together and edited the deb and wrapped it up in a little script. Figured I'd drop it here for anyone in the future.
FixTrackpadSamsungXE303C12.zip Just follow the readme and should be pretty dummy proof. Worked for me on a fresh image.
Now I just gotta look into putting it over chromium or somehow making the normal usb port look to the usb3 port to boot from a usb harddrive.