On Tue, Aug 18, 2015 at 10:13 PM, Robert Moskowitz <rgm@xxxxxxxxxxxxxxx> wrote: > I have not done any Fedora-arm testing for many weeks and am behind on > developments. Correct me if I missed something in past threads. > > I am trying to make sense of this thread, though. > > I am running the lastest F23 build (Fedora-Xfce-armhfp-23-20150818-sda) and > no Wifi (or Bluetooth) flashing LEDs. On the serial console on firstboot I > do see: > > [ 28.134790] cfg80211: World regulatory domain updated: > [ 28.134804] cfg80211: DFS Master region: unset > [ 28.134805] cfg80211: (start_freq - end_freq @ bandwidth), > (max_antenna_gain, max_eirp), (dfs_cac_time) > [ 28.134818] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, > 2000 mBm), (N/A) > [ 28.134824] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, > 2000 mBm), (N/A) > [ 28.134829] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, > 2000 mBm), (N/A) > [ 28.134837] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 > KHz AUTO), (N/A, 2000 mBm), (N/A) > [ 28.134954] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 > KHz AUTO), (N/A, 2000 mBm), (0 s) > [ 28.134961] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, > 2000 mBm), (0 s) > [ 28.134967] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, > 2000 mBm), (N/A) > [ 28.134973] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), > (N/A, 0 mBm), (N/A) > > So one might THINK that the WiFi was seen. > > But nothing shows for WiFi in NetworkManager. Did you add a firmware? At the moment you need to get the firmware from elsewhere as we don't have the ability to legally redistribute it directly. You might also want to check the output of lsmod, "ip link" and "iw list" > The thought of pacthing nvram leaves me a little worried. I would like to > get WiFi working on the F23 build. > > > On 08/10/2015 02:55 PM, Clive Messer wrote: >> >> On Fri, 2015-08-07 at 17:15 +0200, Hans de Goede wrote: >>> >>> Hi, >>> >>> On 07-08-15 12:19, Clive Messer wrote: >>>> >>>> On Fri, 2015-08-07 at 10:46 +0200, Hans de Goede wrote: >>>> >>>>> I've been running with that fix for a while now and I'm seeing no >>>>> such issues. >>>> >>>> Patch was applied to F22 4.1.3-201. Didn't managed to boot that >>>> successfully due to problems reading/writing sdcard and timeouts. >>>> No >>>> such issues booting with a "stock" 4.1.3-201. That was on >>>> BananaPro. >>>> I'll try again with Cubietruck today. (And apart from the fsck >>>> required, no problems immediately booting the stock kernel after >>>> the >>>> boot failures due to mmc timeouts with the patched kernel.) >>> >>> Weird. I'll keep this in mind when there is more clarity about a >>> "proper" fix for this upstream. >> >> Hans, >> >> I've also booted the kernel with your sunxi-mmc patch on CubieTruck and >> BananaPi, since my initial testing with BananaPro. Even if it doesn't >> hang on boot, while accessing SDCARD, sooner or later.... >> >> ** 61 printk messages dropped ** [ 105.010500] mmcblk0: error -5 >> sending status command, retrying >> ** 36 printk messages dropped ** [ 105.020100] mmcblk0: error -5 >> sending status command, aborting >> ** 31 printk messages dropped ** [ 105.028429] mmcblk0: error -5 >> sending status command, retrying >> ** 43 printk messages dropped ** [ 105.037543] mmcblk0: error -5 >> sending status command, retrying >> ** 38 printk messages dropped ** [ 105.046260] mmcblk0: error -5 >> sending status command, retrying >> ** 38 printk messages dropped ** [ 105.055028] mmcblk0: error -5 >> sending status command, retrying >> ** 33 printk messages dropped ** [ 105.063290] mmcblk0: error -5 >> sending status command, retrying >> >> I rebuilt with original sigint patch ( >> https://groups.google.com/forum/#!topic/linux-sunxi/v6Ktt8lAnw0) where >> the check is only being performed for sdio access from wifi driver >> rather than everything that goes through sunxi mmc driver.... No >> issues. Have put many Gigs of data through the wifi connection on the >> BananaPro. >> >> Sorry, don't have any more time to look into this and as you say, >> probably a non-issue, if neither is the actual "fix" that will make it >> upstream anyway. >> >> Clive > > > _______________________________________________ > arm mailing list > arm@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/arm _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
