2022년 11월 16일 오늘 업데이트됨 - 1520GTM
내 Pinebook Pro에서 pip를 통해 Python 설치를 망친 후에는 더 이상 시스템을 업데이트하고 업그레이드할 수 없습니다. 제안된 해결 방법은 다음과 같습니다.
pip를 통해 설치된 Python 항목을 제거하고,
그리고 다음을 실행하세요:
sudo pacman -S manjaro-system
sudo pacman -Syu --overwrite "*"
일이 잘 안 됐어요. 질문:
:: Replace breath2-icon-themes with community/plasma5-themes-breath? [Y/n] y
...
:: Replace plasma5-themes-breath2 with community/plasma5-themes-breath? [Y/n] y
:: Replace sddm-breath2-theme with community/sddm-breath-theme? [Y/n] y
그런 다음 다음을 시도합니다.
...
:: Replace breath2-icon-themes with community/plasma5-themes-breath? [Y/n] n
...
:: Replace plasma5-themes-breath2 with community/plasma5-themes-breath? [Y/n] n
:: Replace sddm-breath2-theme with community/sddm-breath-theme? [Y/n] n
완벽한! 그러나 실패한 시스템 장치가 나타났습니다.
journalctl -p 3 -b
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
Oct 25 13:44:17 lxm kernel: OF: graph: no port node found in /i2c@ff3d0000/fusb30x@22
Oct 25 13:44:17 lxm kernel: rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
Oct 25 13:44:17 lxm kernel: mmc0: error -110 whilst initialising SDIO card
Nov 16 10:09:39 lxm kernel: rockchip-dp ff970000.edp: no DP phy configured
Nov 16 10:09:39 lxm systemd-udevd[303]: event6: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[303]: event6: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[303]: event6: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[308]: event4: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[308]: event4: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[308]: event4: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[301]: event7: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[301]: event7: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[301]: event7: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[319]: event8: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[319]: event8: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[319]: event8: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[306]: event5: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[306]: event5: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Nov 16 10:09:39 lxm systemd-udevd[306]: event5: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Nov 16 10:09:41 lxm bluetoothd[412]: Failed to set mode: Failed (0x03)
Nov 16 10:09:41 lxm systemd[1]: Failed to start PostgreSQL database server.
Nov 16 10:13:16 lxm pulseaudio[853]: module-rescue-stream is obsolete and should no longer be loaded. Please remove it from your configuration.
Nov 16 11:14:33 lxm kernel: .ready
Nov 16 15:10:39 lxm kernel: clk_spi1 already disabled
Nov 16 15:10:39 lxm kernel: Modules linked in: rfcomm bnep zram r8153_ecm cdc_ether usbnet uvcvideo r8152 mii snd_soc_simple_amplifier joydev videobuf2_vmalloc hci_uart panfrost>
Nov 16 15:10:39 lxm kernel: CPU: 0 PID: 5853 Comm: systemd-sleep Tainted: G C 6.0.7-2-MANJARO-ARM #1
위의 문제를 제거하고 시스템을 원활하게 실행하려면 어떻게 해야 합니까?
Manjaro를 처음부터 다시 설치해야 합니까?
또는:
Debian ARM 또는 Ubuntu ARM을 설치해야 합니까?