Bug 1260414 - bay trail wifi flackiness
Summary: bay trail wifi flackiness
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-06 15:20 UTC by Nicolas Mailhot
Modified: 2017-05-02 06:48 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Nicolas Mailhot 2015-09-06 15:20:27 UTC
Description of problem:


Version-Release number of selected component (if applicable):
anaconda 24.1-1 (as used in the rawhide boot image published 2015-09-02)

Comment 1 Nicolas Mailhot 2015-09-06 15:24:20 UTC
Installing Fedora on a Toshiba Chromebook 2 (CB30 104) requires entering the same wifi key multiple times as wifi setup will fail/timeout and there is no obvious way to kick it other than selecting the same ssid again and re-entering the wifi key (cut and paste from another anaconda field helps, as the key field itself is cloaked and useless)

Comment 2 David Shea 2015-09-08 13:49:32 UTC
Please attach the log files from /tmp to this bug as individual, text/plain attachments.

Comment 3 Nicolas Mailhot 2015-09-08 16:31:26 UTC
There is already one copy in attachment 1071411 [details] 

https://bugzilla.redhat.com/attachment.cgi?id=1071411

Comment 4 Dan Williams 2015-09-22 14:51:41 UTC
14:41:15,578 WARNING NetworkManager: <warn>  (wlp1s0): Activation: (wifi) association took too long, failing activation
14:41:15,578 INFO NetworkManager: <info>  (wlp1s0): device state change: config -> failed (reason 'ssid-not-found') [50 120 53]
14:41:15,580 INFO NetworkManager: <info>  NetworkManager state is now DISCONNECTED
14:41:15,582 WARNING NetworkManager: <warn>  (wlp1s0): Activation: failed for connection 'okg'

The wifi driver did not find the AP in a scan.  That's a kernel problem, or an AP problem...


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