You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The post-install service to fix usb-c does not enable on my KANO chromebook.
What I did - created the file in /etc/systemd/system as instructed.
[Unit]
Description=Enable USB-C on chromebook
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStartPre=/sbin/modprobe -r -a cros-ec-typec intel-pmc-mux
ExecStart=/sbin/modprobe -a intel-pmc-mux cros-ec-typec
[Install]
WantedBy=multi-user.target
I tried to enable it: sudo systemctl enable --now chromebook-usbc.service
It should have enabled without error, instead it failed to enable:
xyz@deb714:/etc/systemd/system$ sudo systemctl enable --now chromebook-usbc.service
Job for chromebook-usbc.service failed because the control process exited with error code.
See "systemctl status chromebook-usbc.service" and "journalctl -xeu chromebook-usbc.service" for details.
The recommended debugging steps yielded the following:
xyz@deb714:~$ systemctl status chromebook-usbc.service
× chromebook-usbc.service - Enable USB-C on chromebook
Loaded: loaded (/etc/systemd/system/chromebook-usbc.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Fri 2024-04-05 15:24:31 CDT; 2min 23s ago
Process: 1942 ExecStartPre=/sbin/modprobe -r -a cros-ec-typec intel-pmc-mux (code=exited, status=1/FAILURE)
CPU: 7ms
sudo journalctl -xeu chromebook-usbc.service
Apr 05 15:24:31 deb714 systemd[1]: Starting chromebook-usbc.service - Enable USB-C on chromebook...
░░ Subject: A start job for unit chromebook-usbc.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit chromebook-usbc.service has begun execution.
░░
░░ The job identifier is 1981.
Apr 05 15:24:31 deb714 modprobe[1942]: modprobe: WARNING: Module intel_pmc_mux is in use.
Apr 05 15:24:31 deb714 systemd[1]: chromebook-usbc.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStartPre= process belonging to unit chromebook-usbc.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 05 15:24:31 deb714 systemd[1]: chromebook-usbc.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit chromebook-usbc.service has entered the 'failed' state with result 'exit-code'.
Apr 05 15:24:31 deb714 systemd[1]: Failed to start chromebook-usbc.service - Enable USB-C on chromebook.
░░ Subject: A start job for unit chromebook-usbc.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit chromebook-usbc.service has finished with a failure.
░░
░░ The job identifier is 1981 and the job result is failed.
OS Linux deb714 6.6.10-chrultrabook #1 SMP PREEMPT_DYNAMIC Tue Jan 9 04:03:43 UTC 2024 x86_64 GNU/Linux Coreboot Firmware version: and Device:
Acer Chromebook Spin 714 [CP714-1WN] (Kano)
FW: MrChromebox-4.22.2-5-g822782a1001
13th Gen Intel (R) Core (TM) i5-1335U
(as reported during boot, although it's actually CP714-2W-56B2)
Don't know if you solved the problem, but I want to share my solution.
First add cros-ec-typc in the blacklist with:
/etc/modprob.d/chromebook-usbc.conf
"blacklist cros-ec-typc"
Second modify the chromebook-usbc.service(which on the chrultrabook guide)
Remove the line of "ExecStartPre" and edit the "ExecStart" with "/sbin/modprobe -a cros-ec-typc"
The post-install service to fix usb-c does not enable on my KANO chromebook.
What I did - created the file in /etc/systemd/system as instructed.
I tried to enable it:
sudo systemctl enable --now chromebook-usbc.service
It should have enabled without error, instead it failed to enable:
The recommended debugging steps yielded the following:
OS
Linux deb714 6.6.10-chrultrabook #1 SMP PREEMPT_DYNAMIC Tue Jan 9 04:03:43 UTC 2024 x86_64 GNU/Linux
Coreboot Firmware version: and Device:
Additional context
The text was updated successfully, but these errors were encountered: