Bug 785386

Summary: kernel-3.2.2-1 broke Asus EEE-PC 1000H wi-fi
Product: [Fedora] Fedora Reporter: Rui Mota <rmomota>
Component: kernelAssignee: John W. Linville <linville>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 16CC: antonbaklanov, dboshell, g0tt, gansalmon, gisburne, itamar, jonathan, kernel-maint, madhu.chinakonda, sgruszka
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-30 15:03:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Rui Mota 2012-01-28 15:17:55 UTC 
Description of problem:
In kernel-3.2.2-1 there's no more wi-fi on Asus EEE-PC 1000H.
Only cable conection is allowed, wifi driver no longer works.

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

How reproducible:
Everytime it boots.

Steps to Reproduce:
1. Just boot
2. Then login
  
Actual results:
No wi-fi card detected

Expected results:
There must be a wi-fi card.

Additional info:
By reverting to previous kernel version it works.
Comment 1 Anton Baklanov 2012-01-28 17:25:17 UTC 
have no wifi on my eeepc 901 with kernel-3.2.2-1.fc16.i686

with kernel-3.1.9-1.fc16.i686 it works fine.
Comment 2 Kirill Sychev 2012-01-28 18:15:17 UTC 
have no wifi on my Asus EEE-PC 1000H with kernel-3.2.2-1.fc16.i686
Comment 3 dave 2012-01-28 22:30:59 UTC 
Kernel 3.2.2-1.fc16.x86_64 also broke my wifi (hardware: rt2860). 

From memory the boot messages say there is an eeprom error.

Reverting to 3.1.9-1.fc16.x86_64 fixes it.
Comment 4 Josh Boyer 2012-01-30 14:09:55 UTC 
*** Bug 785510 has been marked as a duplicate of this bug. ***
Comment 5 John W. Linville 2012-01-30 15:03:35 UTC 

*** This bug has been marked as a duplicate of bug 785393 ***