Bug 1099401 - Unable to enable ACPI - causes usb bluetooth keyboard/mouse to fail and wireless doesn't work
Summary: Unable to enable ACPI - causes usb bluetooth keyboard/mouse to fail and wirel...
Keywords:
Status: CLOSED DUPLICATE of bug 1099406
Alias: None
Product: Fedora
Classification: Fedora
Component: acpi
Version: 20
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Steven M. Parrish
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-20 08:41 UTC by David Eccleston
Modified: 2014-05-20 13:26 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-05-20 13:26:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg of failing boot (65.30 KB, text/x-log)
2014-05-20 08:41 UTC, David Eccleston
no flags Details

Description David Eccleston 2014-05-20 08:41:34 UTC
Created attachment 897505 [details]
dmesg of failing boot

Description of problem: Getting message Unable to enable ACPI
this causes
Microsoft Bluetooth USB Mouse/KB not to work
Wireless doesn't work - not detecting wireless signale
Very long time to bring up Plasma Desktop
When I try to lsusb - terminal hangs


Version-Release number of selected component (if applicable):
13.14.4
13.14.3-200
13.14.2-200

3.13.10-200 This works but I noticed I get ACPI warnings
ACPI Warning: 0x0000000000000b00-0x0000000000000b07 SystemIO conflicts with Region \_SB_.PCI0.SMB_.SMB0 1 (20131115/utaddress-251)
[   21.033108] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver


How reproducible:
Very reproducible

Steps to Reproduce:
1. Boot into the non-working kernels above
2.
3.

Actual results:
Wireless not working
Mouse/Keyboard not working
Long to time to bring up Plasma Desktop

Expected results:
All should work

Additional info:
Machine Acer Aspire 5560

Comment 1 David Eccleston 2014-05-20 13:26:50 UTC

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


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