Bug 12417 - Driver works using Mageia 4 RC LiveCD KDE4 en 32bit CD but not, when using Mageia 4 RC 32bit DVD
Summary: Driver works using Mageia 4 RC LiveCD KDE4 en 32bit CD but not, when using M...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL: https://forums.mageia.org/de/viewtopi...
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2014-01-24 15:20 CET by Jürgen Kowalzik
Modified: 2016-04-29 16:04 CEST (History)
2 users (show)

See Also:
Source RPM: Driver: rt2800pci
CVE:
Status comment:


Attachments

Description Jürgen Kowalzik 2014-01-24 15:20:23 CET
Description of problem:


Version-Release number of selected component (if applicable):
Device Names
Device: RT2860
Driver: rt2800pci

How reproducible:
I use the netbook MEDION AKOYA E1210
The last time this WLAN worked was Mandriva 2010.2
Yesterday I tryed  Mageia 4 RC LiveCD KDE4 en 32bit CD and what happens....
Heureka
WLAN is working :) :) :)
come on.. upgrading with  Mageia 4 RC 32bit DVD
2 hours later.............
"Verbindungsfehler"
The same thing like https://forums.mageia.org/de/viewtopic.php?f=5&t=1624
I tried a lot of Linux-Distri's
MAGEIA 1,2,3 and 4 are the only distributions which dos'nt work.

Steps to Reproduce:
1. see above
2.
3.


Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2014-01-29 18:42:24 CET

CC: (none) => ennael1, thierry.vignaud
Assignee: bugsquad => tmb

Comment 1 Marja Van Waes 2016-04-26 12:02:00 CEST
This bug report hasn't seen any action since before Mga4 release. Is it still valid in current cauldron (or, for traditional installer: with the 6dev1 snapshot, or for live isos with Mga5)?

Keywords: (none) => NEEDINFO

Comment 2 Jürgen Kowalzik 2016-04-29 14:50:24 CEST
since MGA5 it works well.
Comment 3 Thierry Vignaud 2016-04-29 16:04:34 CEST
Closing then

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.