lenovo_legion_5_15arh05
Différences
Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentesRévision précédenteProchaine révision | Révision précédente | ||
| lenovo_legion_5_15arh05 [2024/10/29 18:57] – [5 Easy Ways to Block Page Redirects in a Web Browser] Benjamin Labomedia | lenovo_legion_5_15arh05 [2026/09/18 20:46] (Version actuelle) – [Convertir un fichier pdf en images et reconstituer un fichier pdf à partir de ces images] Benjamin Labomedia | ||
|---|---|---|---|
| Ligne 1: | Ligne 1: | ||
| ====== Ordinateur Lenovo Legion 5 15ARH05 sous Linux ====== | ====== Ordinateur Lenovo Legion 5 15ARH05 sous Linux ====== | ||
| * Modèle Lenovo Legion 5 15ARH05 (82B500F1FR) fiche tech from LDLC{{ :: | * Modèle Lenovo Legion 5 15ARH05 (82B500F1FR) fiche tech from LDLC{{ :: | ||
| - | * F2 pour accéder au bios | + | |
| + | | ||
| ====== Installation Debian 12 bookworm ====== | ====== Installation Debian 12 bookworm ====== | ||
| Ligne 51: | Ligne 52: | ||
| Voir https:// | Voir https:// | ||
| accessibility.blockautorefresh true | accessibility.blockautorefresh true | ||
| + | | ||
| + | Pour régler le problème de taille de police / icone avec Mate sous le driver NVIDIA [[https:// | ||
| + | gsettings set org.mate.interface window-scaling-factor 0 | ||
| + | |||
| + | 0 is for auto-detect | ||
| + | 1 is for Regular | ||
| + | 2 is for HiDP | ||
| + | | ||
| + | ==== Faire en sorte que Fireefox utilise l' | ||
| + | When using Nvidia proprietary drivers, package nvidia-vaapi-driver must be additionally installed | ||
| + | * https:// | ||
| + | * https:// | ||
| + | * Voir 05 2025 https:// | ||
| ===== Troubleshooting ===== | ===== Troubleshooting ===== | ||
| * Régler le problème du touchpad avec noyau 5.10 https:// | * Régler le problème du touchpad avec noyau 5.10 https:// | ||
| Ligne 124: | Ligne 138: | ||
| systemctl reload NetworkManager | systemctl reload NetworkManager | ||
| | | ||
| - | | + | What is the list of the systemd' |
| + | su -l -c " | ||
| + | |||
| + | ==== Pour réactiver ==== | ||
| + | Vérifier que le serveur DHCP donne bien des DNS | ||
| + | |||
| + | Voir modifs de | ||
| + | sudo nano / | ||
| + | [main] | ||
| + | dns=default | ||
| + | plugins=ifupdown, | ||
| + | |||
| + | [ifupdown] | ||
| + | managed=false | ||
| + | |||
| + | |||
| + | https:// | ||
| + | |||
| + | Pour régler le nameserver ::1 | ||
| + | sudo nmcli con down pvpn-ipv6leak-protection | ||
| + | Tu peux trouver que ça démarre automatiquement au démarrage, ça devrait l' | ||
| + | nmcli c m pvpn-ipv6leak-protection connection.autoconnect no | ||
| + | |||
| + | |||
| + | * https:// | ||
| + | * https:// | ||
| ===== Virer les snap inutiles ===== | ===== Virer les snap inutiles ===== | ||
| https:// | https:// | ||
| Ligne 219: | Ligne 258: | ||
| Aller dans paramètre > Editeur de configuration tout en bas de la page et passer le paramètre : | Aller dans paramètre > Editeur de configuration tout en bas de la page et passer le paramètre : | ||
| pdfjs.disabled true | pdfjs.disabled true | ||
| + | | ||
| + | ==== Voir ou convertir des images au format .heic ==== | ||
| + | Pour voir dans le visualiseur d' | ||
| + | |||
| + | sudo apt install heif-gdk-pixbuf | ||
| + | |||
| + | Convertir .heic en .jpg | ||
| + | sudo apt install libheif-examples | ||
| + | |||
| + | As test files, we have IMG_8123.HEIC, | ||
| + | |||
| + | for i in *.HEIC; do heif-convert " | ||
| + | | ||
| + | ==== Nettoyer sa debian ==== | ||
| + | * https:// | ||
| + | Virer les vieux paquets dans archive | ||
| + | apt-get autoclean | ||
| + | apt-get clean | ||
| + | apt-get autoremove | ||
| + | | ||
| + | ==== Convertir un fichier pdf en images et reconstituer un fichier pdf à partir de ces images ==== | ||
| + | pdftoppm -r 96 -png monficher.pdf page | ||
| + | sudo apt install img2pdf | ||
| + | img2pdf page-*.png -o resultat.pdf | ||
| + | | ||
| + | |||
| + | ==== Firefox freeze sur la lecture de vidéos en plein écran ==== | ||
| + | |||
| + | |||
| + | Try this sequence; NVIDIA + Firefox freezes are often caused by the video-decoding or compositor path rather than the website itself. | ||
| + | |||
| + | 1. **Confirm whether hardware acceleration is the cause** | ||
| + | |||
| + | Open Firefox → `about: | ||
| + | |||
| + | - Uncheck **Use recommended performance settings** | ||
| + | - Uncheck **Use hardware acceleration when available** | ||
| + | - Restart Firefox | ||
| + | |||
| + | Test the same video. Mozilla recommends this as a diagnostic step for graphics-driver-related playback problems. < | ||
| + | |||
| + | If playback is stable afterward, leave acceleration disabled temporarily and continue with the driver/ | ||
| + | |||
| + | 2. **Check Firefox’s graphics and media status** | ||
| + | |||
| + | Open: | ||
| + | |||
| + | ```text | ||
| + | about: | ||
| + | ``` | ||
| + | |||
| + | Check these sections: | ||
| + | |||
| + | - **Window Protocol** — whether you are using `wayland` or `x11` | ||
| + | - **Compositing** | ||
| + | - **Hardware Video Decoding** | ||
| + | - **Video Acceleration Information** | ||
| + | - **Decision Log** | ||
| + | |||
| + | Also test Firefox without extensions: | ||
| + | |||
| + | ```bash | ||
| + | firefox --safe-mode | ||
| + | ``` | ||
| + | |||
| + | If the freeze disappears, disable extensions—especially video downloaders, | ||
| + | |||
| + | 3. **Update the NVIDIA stack** | ||
| + | |||
| + | On Debian, make sure the kernel module, user-space libraries, and firmware are from compatible packages: | ||
| + | |||
| + | ```bash | ||
| + | sudo apt update | ||
| + | sudo apt full-upgrade | ||
| + | sudo reboot | ||
| + | ``` | ||
| + | |||
| + | Then check: | ||
| + | |||
| + | ```bash | ||
| + | nvidia-smi | ||
| + | firefox --version | ||
| + | uname -r | ||
| + | ``` | ||
| + | |||
| + | If `nvidia-smi` fails, fix the NVIDIA driver installation before troubleshooting Firefox. Avoid mixing NVIDIA packages from different Debian releases or random `.run` installers. | ||
| + | |||
| + | 4. **Test the display protocol** | ||
| + | |||
| + | If you are currently using Wayland, test an X11 session from the login screen. If you are using X11, test Wayland. | ||
| + | |||
| + | You can also test Firefox explicitly: | ||
| + | |||
| + | ```bash | ||
| + | MOZ_ENABLE_WAYLAND=1 firefox | ||
| + | ``` | ||
| + | |||
| + | or, for X11: | ||
| + | |||
| + | ```bash | ||
| + | MOZ_X11_EGL=1 firefox | ||
| + | ``` | ||
| + | |||
| + | If the freeze occurs only under Wayland, it is likely in the NVIDIA GBM/ | ||
| + | |||
| + | 5. **Check NVIDIA VA-API support** | ||
| + | |||
| + | Firefox uses VA-API for browser video acceleration. Debian notes that proprietary NVIDIA drivers need the third-party `nvidia-vaapi-driver`; | ||
| + | |||
| + | Install the available package: | ||
| + | |||
| + | ```bash | ||
| + | sudo apt install nvidia-vaapi-driver vainfo | ||
| + | ``` | ||
| + | |||
| + | Then test: | ||
| + | |||
| + | ```bash | ||
| + | vainfo | ||
| + | ``` | ||
| + | |||
| + | If `vainfo` cannot initialize or shows no decode profiles, hardware video decoding is not correctly configured. The package may be unavailable on older Debian releases; in that case, use the corresponding package from your Debian release/ | ||
| + | |||
| + | 6. **Try Firefox’s VA-API setting** | ||
| + | |||
| + | In `about: | ||
| + | |||
| + | ```text | ||
| + | media.ffmpeg.vaapi.enabled = true | ||
| + | ``` | ||
| + | |||
| + | Restart Firefox and check `about: | ||
| + | |||
| + | Do not force every codec to hardware-decode initially. In particular, setting `media.ffvpx.enabled=false` can make playback worse if your GPU does not support the selected VP8/VP9 codec. | ||
| + | |||
| + | 7. **Test AV1** | ||
| + | |||
| + | Some NVIDIA GPUs or driver combinations have problems with AV1 playback. Temporarily set: | ||
| + | |||
| + | ```text | ||
| + | media.av1.enabled = false | ||
| + | ``` | ||
| + | |||
| + | Restart Firefox and test YouTube again. Debian specifically recommends disabling AV1 when the GPU cannot decode it reliably, allowing sites to fall back to H.264 or VP9. < | ||
| + | |||
| + | 8. **Collect useful logs if it still freezes** | ||
| + | |||
| + | Run Firefox from a terminal: | ||
| + | |||
| + | ```bash | ||
| + | LIBVA_DRIVER_NAME=nvidia LIBVA_MESSAGING_LEVEL=1 firefox | ||
| + | ``` | ||
| + | |||
| + | For NVIDIA GPU activity, in another terminal run: | ||
| + | |||
| + | ```bash | ||
| + | watch -n 1 nvidia-smi | ||
| + | ``` | ||
| + | |||
| + | If the entire desktop locks up rather than only the video frame, after reboot check: | ||
| + | |||
| + | ```bash | ||
| + | journalctl -b -1 -k | grep -Ei ' | ||
| + | ``` | ||
| + | |||
| + | An `NVRM: Xid` error points to an NVIDIA driver/GPU reset, not a normal Firefox media setting. | ||
| + | |||
| + | The quickest practical workaround is usually: **disable Firefox hardware acceleration, | ||
lenovo_legion_5_15arh05.1730228249.txt.gz · Dernière modification : de Benjamin Labomedia
