Bug 14082 - 5a2: Unable to connect with my RT3090 Wireless 802.11n 1T/1R PCIe
Summary: 5a2: Unable to connect with my RT3090 Wireless 802.11n 1T/1R PCIe
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-10 03:45 CEST by Bit Twister
Modified: 2014-09-12 02:49 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Bit Twister 2014-09-10 03:45:04 CEST
Description of problem:
 Unable to connect with my Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe. 
It is working on Mageia 4.

My install scripts pulled the same rpms and created the ifcfg-wlp2s0 and wireless.d files. x_urpmi is a function to strip the comment and call urpmi.


x_urpmi kernel-firmware-nonfree ! Video card Wireless firmware
x_urpmi wireless-tools  ! Wireless ethernet configuration toolsâ
x_urpmi rfkill ! Simple /dev/rfkill userspace toolâ needed to dis/enable wireless and bluetooth 
x_urpmi ralink-firmware ! for my RT3090 Wireless 802.11n 1T/1R PCIe
x_urpmi rtlwifi-firmware ! Nonfree rtlwifi wireless firmware files for the Linux kernelâ
x_urpmi iwlwifi-agn-ucode ! Nonfree iwlwifi wireless firmware files for the Linux kernelâ
x_urpmi wpa_supplicant-gui ! Graphical tool for wpa_supplicantâ wireless


Problem seems to be no link beat detected.

Info from Hardware screen:

Identification
Vendor: âRalink corp.
Description: âRT3090 Wireless 802.11n 1T/1R PCIe
Media class: âNetwork controller
Connection
Bus: âPCI Express
PCI domain: â0
Bus PCI #: â2
PCI device #: â0
PCI function #: â0
Vendor ID: â0x1814
Device ID: â0x3090
Sub vendor ID: â0x11ad
Sub device ID: â0x6632
Misc
Module: ârt2800pci


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Bit Twister 2014-09-12 02:49:26 CEST
new fglrx rpms solved the problem.

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


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