# Impossible d'activer ma connexion WIFI via le contrôleur MEDIATEK Corp. Device 7902

**URL:** <https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528>\
**Category:** Support Debian\
**Tags:** firmware-mediatek, kde, trixie, wifi\
**Created:** [Septembre 10, 2025, 5:27 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528 "2025-09-10T17:27:13Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![martialus7](https://www.debian-fr.org/user_avatar/www.debian-fr.org/martialus7/32/14863_2.png) [@martialus7](https://www.debian-fr.org/u/martialus7)\
**Post date:** [Septembre 10, 2025, 5:27 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/1 "2025-09-10T17:27:13Z")

</div>

Bonjour à tous,

Passionné de Linux, j’ai installé la version KDE 13 sur mon nouveau poste mais je ne parviens pas à activer le WIFI

**Voici les caractéristiques du poste**  
Système d’exploitation : Debian GNU/Linux 13  
Version de KDE Plasma : 6.3.6  
Version des frameworks KDE : 6.13.0  
Version de Qt : 6.8.2  
Version du noyau : 6.12.43+deb13-amd64 (64 bits)  
Plate-forme graphique : Wayland  
Processeurs : 2 × Intel® Celeron® N4500 à 1,10 GHz  
Mémoire : 4 Gio de RAM (3,7 Gio utilisables)  
Processeur graphique : Mesa Intel® UHD Graphics  
Fabricant : Packard Bell  
Nom du produit : B114-33  
Version du système : V1.53

**En lançant lspci -vv -s 02:00.0, voici le résultat :**

```auto
02:00.0 Contrôleur réseau : MEDIATEK Corp. Device 7902
        Sous-système : AzureWave Device 5524
        Contrôle : E/S- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Statut : Cap+ 66 MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Interruption : broche A routeée vers l'IRQ 255
        Groupe IOMMU : 12
        Région 0 : Mémoire à 6001 000 000 (64 bits, pré-récupérable) [désactivé] [taille = 1 M]
        Région 2 : Mémoire à 7f800000 (64 bits, non pré-récupérable) [désactivé] [taille = 32 Ko]
        Capacités : <accès refusé>

```

Pourriez-vous m’aider ?

Merci d’avance pour votre compréhension

---

<div class="post-metadata">

**Author:** ![anon95513332](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/aeb1de/32.png) [@anon95513332](https://www.debian-fr.org/u/anon95513332)\
**Post date:** [Septembre 10, 2025, 5:58 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/2 "2025-09-10T17:58:57Z")

</div>

Salut,

Comment as-tu installé Debian 13 & KDE ?

---

<div class="post-metadata">

**Author:** ![martialus7](https://www.debian-fr.org/user_avatar/www.debian-fr.org/martialus7/32/14863_2.png) [@martialus7](https://www.debian-fr.org/u/martialus7)\
**Post date:** [Septembre 10, 2025, 7:05 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/3 "2025-09-10T19:05:52Z")

</div>

Via une Netinstall

---

<div class="post-metadata">

**Author:** ![anon95513332](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/aeb1de/32.png) [@anon95513332](https://www.debian-fr.org/u/anon95513332)\
**Post date:** [Septembre 10, 2025, 7:08 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/4 "2025-09-10T19:08:59Z")

</div>

Apparemment, tu n’es pas le premier à avoir des soucis avec la MT 7902:

[Y’a des drivers pour le Mediatek Corp. Device 7902 ?](https://www.reddit.com/r/debian/comments/1lp4vou/any_drivers_for_the_mediatek_corp_device_7902/?tl=fr)

---

<div class="post-metadata">

**Author:** ![martialus7](https://www.debian-fr.org/user_avatar/www.debian-fr.org/martialus7/32/14863_2.png) [@martialus7](https://www.debian-fr.org/u/martialus7)\
**Post date:** [Septembre 10, 2025, 7:17 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/5 "2025-09-10T19:17:06Z")

</div>

C’est à mes risque et péril.  
J’ai déjà fais plin de test de compilation avec l’aide de l’IA ChatGpt mais sas résultat positif et sur le site ACER ils n’ont que les firmware pour windobe.

---

<div class="post-metadata">

**Author:** ![anon95513332](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/aeb1de/32.png) [@anon95513332](https://www.debian-fr.org/u/anon95513332)\
**Post date:** [Septembre 10, 2025, 8:06 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/6 "2025-09-10T20:06:10Z")

</div>

Tiens nous au courant.

---

<div class="post-metadata">

**Author:** ![Zargos](https://www.debian-fr.org/user_avatar/www.debian-fr.org/zargos/32/10889_2.png) [@Zargos](https://www.debian-fr.org/u/Zargos)\
**Post date:** [Septembre 10, 2025, 9:14 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/7 "2025-09-10T21:14:49Z")

</div>

tu as bien installé firmware-mediatek? car le 7902 existe depuis 1 an tout de même.

> **[GitHub - TMTCo/mt7902driver: A newbie-friendly, temporary solution that...](https://github.com/TMTCo/mt7902driver)**
>
> A newbie-friendly, temporary solution that encourages all contributions for long-term and stable use for MT7902 driver on Linux - TMTCo/mt7902driver

---

<div class="post-metadata">

**Author:** ![martialus7](https://www.debian-fr.org/user_avatar/www.debian-fr.org/martialus7/32/14863_2.png) [@martialus7](https://www.debian-fr.org/u/martialus7)\
**Post date:** [Septembre 11, 2025, 9:43 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/8 "2025-09-11T09:43:02Z")

</div>

je viens de l’installer à partir du site [Debian -- Package Download Selection -- firmware-mediatek\_20250410-2\_all.deb](https://packages.debian.org/trixie/all/firmware-mediatek/download)  
Package : firmware-mediatek\_20250410-2\_all.deb  
mais le résultat est identique

---

<div class="post-metadata">

**Author:** ![Zargos](https://www.debian-fr.org/user_avatar/www.debian-fr.org/zargos/32/10889_2.png) [@Zargos](https://www.debian-fr.org/u/Zargos)\
**Post date:** [Septembre 11, 2025, 10:15 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/9 "2025-09-11T10:15:48Z")

</div>

rssaye avec la version backport?

---

<div class="post-metadata">

**Author:** ![martialus7](https://www.debian-fr.org/user_avatar/www.debian-fr.org/martialus7/32/14863_2.png) [@martialus7](https://www.debian-fr.org/u/martialus7)\
**Post date:** [Septembre 11, 2025, 10:39 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/10 "2025-09-11T10:39:27Z")

</div>

J’ai téléchargé puis installé le package firmware-mediatek\_20250808-1~bpo13+1\_all.deb  
redémarré le poste mais c’est idem

---

<div class="post-metadata">

**Author:** ![martialus7](https://www.debian-fr.org/user_avatar/www.debian-fr.org/martialus7/32/14863_2.png) [@martialus7](https://www.debian-fr.org/u/martialus7)\
**Post date:** [Septembre 11, 2025, 10:42 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/11 "2025-09-11T10:42:15Z")

</div>

Peut-être qu’il n’est pas adapté pour la version KDE Plasma ?

---

<div class="post-metadata">

**Author:** ![Zargos](https://www.debian-fr.org/user_avatar/www.debian-fr.org/zargos/32/10889_2.png) [@Zargos](https://www.debian-fr.org/u/Zargos)\
**Post date:** [Septembre 11, 2025, 12:48 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/12 "2025-09-11T12:48:03Z")

</div>

JE ne suis pas certain que ce soit lié à l’environnement graphique. Mais teste eventuellement avec XFCE, il n’est pas wayland et plus léger.  
Si c’est pareil, c’est que c’est le firmware qui n’est pas suffisant.

---

<div class="post-metadata">

**Author:** ![martialus7](https://www.debian-fr.org/user_avatar/www.debian-fr.org/martialus7/32/14863_2.png) [@martialus7](https://www.debian-fr.org/u/martialus7)\
**Post date:** [Septembre 11, 2025, 2:05 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/13 "2025-09-11T14:05:14Z")

</div>

Oui, je vient de faire l’installation de la version XFCE, le résultat n’est pas mieux.

lspci

```auto
00:00.0 Host bridge: Intel Corporation Processor Transaction Router SKU 2 Core
00:02.0 VGA compatible controller: Intel Corporation JasperLake [UHD Graphics] (rev 01)
00:04.0 Signal processing controller: Intel Corporation Dynamic Tuning service
00:14.0 USB controller: Intel Corporation Jasper Lake USB 3.1 xHCI Host Controller (rev 01)
00:14.2 RAM memory: Intel Corporation Jasper Lake Shared SRAM (rev 01)
00:15.0 Serial bus controller: Intel Corporation Jasper Lake Serial IO I2C Host Controller #0 (rev 01)
00:15.2 Serial bus controller: Intel Corporation Jasper Lake Serial IO I2C Host Controller #2 (rev 01)
00:16.0 Communication controller: Intel Corporation Management Engine Interface (rev 01)
00:17.0 SATA controller: Intel Corporation Jasper Lake SATA AHCI Controller (rev 01)
00:1a.0 SD Host controller: Intel Corporation Jasper Lake eMMC Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation Jasper Lake PCIe Root Port #1 (rev 01)
00:1c.1 PCI bridge: Intel Corporation Jasper Lake PCIe Root Port #2 (rev 01)
00:1f.0 ISA bridge: Intel Corporation Jasper Lake eSPI Controller (rev 01)
00:1f.3 Audio device: Intel Corporation Jasper Lake HD Audio (rev 01)
00:1f.4 SMBus: Intel Corporation Jasper Lake SMBus (rev 01)
00:1f.5 Serial bus controller: Intel Corporation Jasper Lake SPI Controller (rev 01)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)
02:00.0 Network controller: MEDIATEK Corp. Device 7902

```

et lspci -vv -s 02:00.

```auto
02:00.0 Network controller: MEDIATEK Corp. Device 7902
	Subsystem: AzureWave Device 5524
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 255
	IOMMU group: 12
	Region 0: Memory at 6001000000 (64-bit, prefetchable) [disabled] [size=1M]
	Region 2: Memory at 7f800000 (64-bit, non-prefetchable) [disabled] [size=32K]
	Capabilities: [80] Express (v2) Endpoint, IntMsgNum 0
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 10W TEE-IO-
		DevCtl:	CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+
			RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ FLReset-
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
		LnkCap:	Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <2us, L1 <8us
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, LnkDisable- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt+ EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- TPHComp- ExtTPHComp-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
			 AtomicOpsCtl: ReqEn-
			 IDOReq- IDOCompl- LTR+ EmergencyPowerReductionReq-
			 10BitTagReq- OBFF Disabled, EETLPPrefixBlk-
		LnkCap2: Supported Link Speeds: 2.5GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1-
			 EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+
		Address: 0000000000000000 Data: 0000
		Masking: 00000000 Pending: 00000000
	Capabilities: [f8] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v1] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
	Capabilities: [108 v1] Latency Tolerance Reporting
		Max snoop latency: 3145728ns
		Max no snoop latency: 3145728ns
	Capabilities: [110 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=3us PortTPowerOnTime=52us
		L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-
			   T_CommonMode=0us LTR1.2_Threshold=81920ns
		L1SubCtl2: T_PwrOn=52us
	Capabilities: [200 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP-
			ECRC- UnsupReq- ACSViol- UncorrIntErr- BlockedTLP- AtomicOpBlocked- TLPBlockedErr-
			PoisonTLPBlocked- DMWrReqBlocked- IDECheck- MisIDETLP- PCRC_CHECK- TLPXlatBlocked-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP-
			ECRC- UnsupReq- ACSViol- UncorrIntErr+ BlockedTLP- AtomicOpBlocked- TLPBlockedErr-
			PoisonTLPBlocked- DMWrReqBlocked- IDECheck- MisIDETLP- PCRC_CHECK- TLPXlatBlocked-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+
			ECRC- UnsupReq- ACSViol- UncorrIntErr+ BlockedTLP- AtomicOpBlocked- TLPBlockedErr-
			PoisonTLPBlocked- DMWrReqBlocked- IDECheck- MisIDETLP- PCRC_CHECK- TLPXlatBlocked-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr- CorrIntErr- HeaderOF-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+ CorrIntErr+ HeaderOF-
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000

```

et

```auto
dmesg | grep -i firmware
[0.145165] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[0.750642] ACPI: thermal: [Firmware Bug]: No valid trip points!
[1.164922] wmi_bus wmi_bus-PNP0C14:00: [Firmware Bug]: WMBF method block execution control method not found
[2.434149] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/icl_dmc_ver1_09.bin (v1.9)
[3.838465] systemd[1]: systemd-hibernate-clear.service - Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).

```

et

```auto
nmcli device status
DEVICE TYPE STATE CONNECTION         
enp1s0 ethernet connecté Wired connection 1 
lo loopback connecté (en externe) lo                 

```

je ne comprend pas !

---

<div class="post-metadata">

**Author:** ![Zargos](https://www.debian-fr.org/user_avatar/www.debian-fr.org/zargos/32/10889_2.png) [@Zargos](https://www.debian-fr.org/u/Zargos)\
**Post date:** [Septembre 11, 2025, 2:20 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/14 "2025-09-11T14:20:22Z")

</div>

A priori le pilote n’a pas laire de fonctionner.  
Juste assez pour identifier l’interface et ses capacités.

As-tu essayé le lien github que j’ai mis dans mon post 7/13?

---

<div class="post-metadata">

**Author:** ![martialus7](https://www.debian-fr.org/user_avatar/www.debian-fr.org/martialus7/32/14863_2.png) [@martialus7](https://www.debian-fr.org/u/martialus7)\
**Post date:** [Septembre 11, 2025, 2:55 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/15 "2025-09-11T14:55:50Z")

</div>

J’ai récupéré le script et lancé la procédure

## Prérequis

- Un système Linux avec des privilèges sudo.
- Connexion Internet pour télécharger les packages et les fichiers de pilotes nécessaires.

## Installation

1. **Cloner le dépôt :**

```auto
git clone https://github.com/Nevergiveup11837/mt7902driverforlinux.git cd mt7902driverforlinux

```

REMARQUES : Utilisez chmod +x install\_wifi\_driver.sh et sudo ./install\_wifi\_driver.sh pour exécuter correctement le fichier sh. Après l’installation, redémarrez votre système pour appliquer les modifications. Encouragez les contributions pour créer un pilote fonctionnant directement et de manière stable sous Linux.

Ou vous pouvez mettre à jour le noyau

```auto
wget https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15-rc6/amd64/linux-headers-5.15.0-051500rc6-generic_5.15.0-051500rc6.202110180730_amd64.deb wget https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15-rc6/amd64/linux-headers-5.15.0-051500rc6_5.15.0-051500rc6.202110180730_all.deb wget https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15-rc6/amd64/linux-image-unsigned-5.15.0-051500rc6-generic_5.15.0-051500rc6.202110180730_amd64.deb wget https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15-rc6/amd64/linux-modules-5.15.0-051500rc6-generic_5.15.0-051500rc6.202110180730_amd64.deb sudo dpkg -i *.deb sudo reboot now

```

mais lorsque j’ai lancé l’installation : sudo ./install\_wifi\_driver.sh

Il me répond :

```auto
E: Impossible de trouver le paquet ndiswrapper-utils-1.9
E: Impossible de trouver de paquet correspondant à l'expression rationnelle « ndiswrapper-utils-1.9 »
E: Impossible de trouver de paquet correspondant à l'expression rationnelle « ndiswrapper-utils-1.9 »
Updating and installing necessary packages... Done.
Checking for driver files in /home/jean-luc...
  ✓ mtkihvx.dll found locally.
Downloading mtkwl1.dat...
Failed to download mtkwl1.dat. Exiting.

```

Le paquet ndiswrapper-utils-1.9 n’existe plus sur la version 13 !

---

<div class="post-metadata">

**Author:** ![Zargos](https://www.debian-fr.org/user_avatar/www.debian-fr.org/zargos/32/10889_2.png) [@Zargos](https://www.debian-fr.org/u/Zargos)\
**Post date:** [Septembre 11, 2025, 3:00 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/16 "2025-09-11T15:00:56Z")

</div>

> [@martialus7](#):
>
> ndiswrapper-utils-1.9 n’existe plus sur la version 13

il n’existait déjà plus sur Bookworm 🙂

ndiswrapper c’était pour utiliser des pilotes windows .

---

<div class="post-metadata">

**Author:** ![martialus7](https://www.debian-fr.org/user_avatar/www.debian-fr.org/martialus7/32/14863_2.png) [@martialus7](https://www.debian-fr.org/u/martialus7)\
**Post date:** [Septembre 11, 2025, 4:01 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/17 "2025-09-11T16:01:59Z")

</div>

y-a-t’il une solution ?

---

<div class="post-metadata">

**Author:** ![Zargos](https://www.debian-fr.org/user_avatar/www.debian-fr.org/zargos/32/10889_2.png) [@Zargos](https://www.debian-fr.org/u/Zargos)\
**Post date:** [Septembre 11, 2025, 4:16 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/18 "2025-09-11T16:16:53Z")

</div>

analyser le script d’installation pour voir pourquoi il utilise ndiswrapper. Car c’est une anomalie, ou alors c’est que c’est bancal comme solution.

---

<div class="post-metadata">

**Author:** ![martialus7](https://www.debian-fr.org/user_avatar/www.debian-fr.org/martialus7/32/14863_2.png) [@martialus7](https://www.debian-fr.org/u/martialus7)\
**Post date:** [Septembre 11, 2025, 4:30 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/19 "2025-09-11T16:30:07Z")

</div>

# Install driver using NDISWrapper

display\_progress «&nbsp;Installing driver with NDISWrapper&nbsp;»  
ndiswrapper -i «&nbsp;$SCRIPT\_DIR/mtkwl6ex.inf&nbsp;» \>/dev/null 2\>&1  
if [$? -ne 0]; then  
echo -e «&nbsp;\nFailed to install driver with NDISWrapper. Exiting.&nbsp;»  
exit 1  
fi  
echo «&nbsp;Installing driver with NDISWrapper… Done.&nbsp;»

---

<div class="post-metadata">

**Author:** ![Zargos](https://www.debian-fr.org/user_avatar/www.debian-fr.org/zargos/32/10889_2.png) [@Zargos](https://www.debian-fr.org/u/Zargos)\
**Post date:** [Septembre 11, 2025, 5:19 UTC](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528/20 "2025-09-11T17:19:03Z")

</div>

bon, pas une bonne solution au final. 😕

MediaTek c’est vraiment un problème pour leurs pilotes

[Page suivante](https://www.debian-fr.org/t/impossible-dactiver-ma-connexion-wifi-via-le-controleur-mediatek-corp-device-7902/91528.md?page=2)