Got it ty!! :)
On Mon, May 12, 2014 at 6:07 AM, Jiri B <ji...@devio.us> wrote: > On Mon, May 12, 2014 at 06:03:28AM -0600, Wylie Bayes wrote: > > Figured i'd piggy back on this thread since it's related.... > > > > Any plans to fix the iwn(4) firmware for: > > > > # dmesg |grep iwn > > iwn0 at pci1 dev 0 function 0 "Intel WiFi Link 1030" rev 0x34: msi, MIMO > > 1T2R, BGN, address bc:77:37:6e:d8:90 > > iwn0: error, 2, could not read firmware iwn-6030 > > iwn0: could not read firmware > > iwn0: error, 2, could not read firmware iwn-6030 > > iwn0: could not read firmware > > iwn0: error, 2, could not read firmware iwn-6030 > > iwn0: could not read firmware > > iwn0: error, 2, could not read firmware iwn-6030 > > iwn0: could not read firmware > > iwn0: error, 2, could not read firmware iwn-6030 > > iwn0: could not read firmware > > iwn0: error, 2, could not read firmware iwn-6030 > > iwn0: could not read firmware > > iwn0 at pci1 dev 0 function 0 "Intel WiFi Link 1030" rev 0x34: msi, MIMO > > 1T2R, BGN, address bc:77:37:6e:d8:90 > > iwn0 at pci1 dev 0 function 0 "Intel WiFi Link 1030" rev 0x34: msi, MIMO > > 1T2R, BGN, address bc:77:37:6e:d8:90 > > man iwn > > iwn0: error N, could not read firmware ... For some reason, the > driver > was unable to read the firmware image from the filesystem. The file > might be missing or corrupted. > > j. > -- ___________________________ Respectfully, Wylie S. Bayes
