Forum français des utilisateurs MX
larry11
Posts: 15 Joined: Mon Dec 30, 2024 12:03 pm
#1
Post
by larry11 » Mon Jun 09, 2025 4:07 am
Bonjour,
j'ai installé la dernière version de MX sur un notebook asus UX331F. Un écran noir s'affiche lors du redémarrage de la machine, après l'écran d'accueil de MX. Je pense qu'il y a dans le bios un blocage M Windows ( voir image jointe). Comment faire sauter ce blocage?
merci.
Cdt.
Eadwine Rose
Administrator
Posts: 14805 Joined: Wed Jul 12, 2006 2:10 am
#2
Post
by Eadwine Rose » Mon Jun 09, 2025 4:20 am
Déplacé dans le sous-forum des langues.
La langue du forum est l'anglais, merci de faire attention et de poster en anglais sur le forum, ou de poster dans votre langue dans ce sous-forum. Nous vous remercions.
MX-23.6_x64 July 31 2023 * 6.1.0-37amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
j2mcgreg
Global Moderator
Posts: 6919 Joined: Tue Oct 23, 2007 12:04 pm
#4
Post
by j2mcgreg » Mon Jun 09, 2025 7:09 am
Nous avons besoin du profil complet de votre ordinateur avant de pouvoir continuer. Vous devez donc publier le résultat de l'utilitaire QSI. L'utilitaire Quick System Info (QSI) se trouve dans MX Tools et son résultat est automatiquement formaté pour être utilisé sur le forum. Exécutez l'utilitaire QSI, cliquez sur « Copier pour le forum » en bas, puis collez-le simplement dans votre discussion.
Règles du forum
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;
In Linux, newer isn't always better. The best solution is the one that works.
larry11
Posts: 15 Joined: Mon Dec 30, 2024 12:03 pm
#5
Post
by larry11 » Mon Jun 09, 2025 10:08 am
voici l'information sur la machine.
Au démarrage, la mire MX Linux s'affiche puis lors du lancement l'écran devient noir. MX Linux s'est installé sans probléme avec un affichage correct.
Merci.
Code: Select all
System:
Kernel: 6.1.0-33-amd64 [6.1.133-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash lang=fr_FR kbd=fr tz=Europe/Paris
Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
dm: LightDM v: 1.32.0 Distro: MX-23.6_x64 Libretto April 13 2025 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: ASUSTeK product: ZenBook UX331FA_UX331FA v: 1.0 serial: <superuser required>
Mobo: ASUSTeK model: UX331FA v: 1.0 serial: <superuser required> UEFI: American Megatrends
v: UX331FA.203 date: 02/20/2019
Battery:
ID-1: BAT0 charge: 29.8 Wh (99.0%) condition: 30.1/50.1 Wh (60.1%) volts: 15.9 min: 15.9
model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: charging
CPU
Info: model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Whiskey Lake gen: core 8 level: v3
note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x8E (142) stepping: 0xB (11)
microcode: 0x98
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 400 min/max: 400/3900 scaling: driver: intel_pstate governor: powersave
cores: 1: 400 2: 400 3: 400 4: 400 5: 400 6: 400 7: 400 8: 400 bogomips: 28800
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities:
Type: gather_data_sampling status: Vulnerable: No microcode
Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf status: Not affected
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Type: meltdown status: Not affected
Type: mmio_stale_data status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT
vulnerable
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional; RSB filling;
PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Vulnerable: No microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: ASUSTeK driver: i915 v: kernel
arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1 empty: HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:3ea0 class-ID: 0300
Device-2: IMC Networks USB2.0 VGA UVC WebCam type: USB driver: uvcvideo bus-ID: 1-5:3
chip-ID: 13d3:5a09 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 509x286mm (20.04x11.26") s-diag: 584mm (22.99")
Monitor-1: eDP-1 model: AU Optronics 0x492d built: 2017 res: 1920x1080 hz: 60 dpi: 166
gamma: 1.2 size: 293x165mm (11.54x6.5") diag: 336mm (13.2") ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics 620 (WHL GT2)
direct-render: Yes
Audio:
Device-1: Intel Cannon Point-LP High Definition Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:9dc8
class-ID: 0403
API: ALSA v: k6.1.0-33-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel modules: wl pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 8086:24fd class-ID: 0280
IF: wlan0 state: up mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-10:4
chip-ID: 8087:0a2b class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
sub-v: 100 hci-v: 4.2 rev: 100
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch hold sniff
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
Drives:
Local Storage: total: 245.95 GiB used: 2.16 GiB (0.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: PC SN520 SDAPNUW-256G-1002
size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 15.8 Gb/s lanes: 2 type: SSD
serial: <filter> rev: 20110000 temp: 22.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 type: USB model: General USB Flash Disk size: 7.47 GiB block-size:
physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 1100 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 36.0 C pch: 34.0 C mobo: N/A
Fan Speeds (RPM): cpu: 0
Repos:
Packages: pm: dpkg pkgs: 2127 libs: 1058 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/mx/repo/ bookworm main non-free
Info:
Processes: 252 Uptime: 1m wakeups: 30 Memory: 7.6 GiB used: 1.12 GiB (14.8%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
larry11
Posts: 15 Joined: Mon Dec 30, 2024 12:03 pm
#6
Post
by larry11 » Wed Jun 11, 2025 1:33 pm
bonsoir,
le problème persiste. Y-a-t-il une solution en modifiant un fichier de config?
Merci.
Cdt
larry11
Posts: 15 Joined: Mon Dec 30, 2024 12:03 pm
#7
Post
by larry11 » Thu Jun 12, 2025 10:23 am
bonjour,
après mise à jour du bios version 305, tout fonctionne.
Merci.
Cdt