Installing firmware for intel 7260

[Geoffrey Leach]

I'm setting up a laptop with Fedora 19 up-to-date. The wireless chip is an Intel 7260.HMW, and I've confirmed that it works (under windows). The chip was not recognized by the install, so I did a yum install of iwl7260.firmware.noarch. That did not install the module, and insmod refuses to install either of the two ucode files. So, presumably they're not modules ("firmware" might be a clue?) So, how should I proceed at this point?

Thanks.

[Kevin Cummings]

On 08/20/2014 03:47 PM, Geoffrey Leach wrote:
> I'm setting up a laptop with Fedora 19 up-to-date. The wireless chip is an Intel 7260.HMW, and I've confirmed that it works (under windows). The chip was not recognized by the install, so I did a yum install of iwl7260.firmware.noarch. That did not install the module, and insmod refuses to install either of the two ucode files. So, presumably they're not modules ("firmware" might be a clue?) So, how should I proceed at this point?

Have you looked here?

http://wireless.kernel.org/en/users/Drivers/iwlwifi

What happens when you "modprobe iwlwifi" with the firmware installed?
> Thanks.

[Joe Zeff]

On 08/20/2014 12:47 PM, Geoffrey Leach wrote:
> I'm setting up a laptop with Fedora 19 up-to-date. The wireless chip is an Intel 7260.HMW, and I've confirmed that it works (under windows). The chip was not recognized by the install, so I did a yum install of iwl7260.firmware.noarch. That did not install the module, and insmod refuses to install either of the two ucode files. So, presumably they're not modules ("firmware" might be a clue?) So, how should I proceed at this point?

I tried to check this with yum info but it told me that there were no 
matching packages.  However, yum list iwl7260* gave me 
iwl7260-firmware.noarch.  (A simple typo; tish happens.)  This time, yum 
info reports that it's the firmware needed by the iwlagn driver.  Do you 
have that installed?

[Geoffrey Leach]

The kernel info at the link is helpful in that it confirms that the 7260 is supported. Your modprobe command is the key. With all of the permutations I tried, that particular one never occurred :-) Of course, modprobe installed the firmware with nary a complaint. With this, NetworkManager permitted me to create an entry for wifi, although this did not allow me to connect, even after a reboot (modprobe config file in place)

The only thing that I can think of is that I mis-copied the MAC address at install time. Any idea how to find it?

On 08/20/2014 01:07:22 PM, Kevin J. Cummings wrote:
> On 08/20/2014 03:47 PM, Geoffrey Leach wrote:
> > I'm setting up a laptop with Fedora 19 up-to-date. The wireless chip
>
> is an Intel 7260.HMW, and I've confirmed that it works (under
> windows). The chip was not recognized by the install, so I did a yum
> install of iwl7260.firmware.noarch. That did not install the module,
> and insmod refuses to install either of the two ucode files. So,
> presumably they're not modules ("firmware" might be a clue?) So, how
> should I proceed at this point?
>
> Have you looked here?
>
> http://wireless.kernel.org/en/users/Drivers/iwlwifi
>
> What happens when you "modprobe iwlwifi" with the firmware installed?
> > Thanks.
>
> -- 
> Kevin J. Cummings
> [e-mail]
> [e-mail]
> [e-mail]
> Registered Linux User #1232 (http://www.linuxcounter.net/)
> -- 
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org

[Geoffrey Leach]

Hmmm ... memo to self: always google first.

So, two things. The MAC address that I used was for the ethernet interface. ip does not show wifi, nor does lspci. The module is loaded.

On 08/20/2014 02:02:48 PM, Geoffrey Leach wrote:
> The kernel info at the link is helpful in that it confirms that the
> 7260 is supported. Your modprobe command is the key. With all of the
> permutations I tried, that particular one never occurred :-) Of
> course, modprobe installed the firmware with nary a complaint. With
> this, NetworkManager permitted me to create an entry for wifi,
> although this did not allow me to connect, even after a reboot
> (modprobe config file in place)
>
> The only thing that I can think of is that I mis-copied the MAC
> address at install time. Any idea how to find it?
>
> On 08/20/2014 01:07:22 PM, Kevin J. Cummings wrote:
> > On 08/20/2014 03:47 PM, Geoffrey Leach wrote:
> > > I'm setting up a laptop with Fedora 19 up-to-date. The wireless
>
> chip
> > is an Intel 7260.HMW, and I've confirmed that it works (under
> > windows). The chip was not recognized by the install, so I did a yum
> > install of iwl7260.firmware.noarch. That did not install the module,
> > and insmod refuses to install either of the two ucode files. So,
> > presumably they're not modules ("firmware" might be a clue?) So, how
> > should I proceed at this point?
> >
> > Have you looked here?
> >
> > http://wireless.kernel.org/en/users/Drivers/iwlwifi
> >
> > What happens when you "modprobe iwlwifi" with the firmware
>
> installed?
> > > Thanks.
> >
> > -- 
> > Kevin J. Cummings
> > [e-mail]
> > [e-mail]
> > [e-mail]
> > Registered Linux User #1232 (http://www.linuxcounter.net/)
> > -- 
> > users mailing list
> > [e-mail]
> > To unsubscribe or change subscription options:
> > https://admin.fedoraproject.org/mailman/listinfo/users
> > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> > Have a question? Ask away: http://ask.fedoraproject.org
>
> -- 
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org

[Geoffrey Leach]

Here's how to get a MAC address. Assuming (as I do) you have Windows on the same box, go there and start Windows. Then start wireless. Now go to the router admin page on Fedora, asn look to see what's attached. Voila!

The bad news: upgraded the definition for the connection. Still no luck.

How can I tell if the kernel sees the driver?

On 08/20/2014 02:11:13 PM, Geoffrey Leach wrote:
> Hmmm ... memo to self: always google first.
>
> So, two things. The MAC address that I used was for the ethernet
> interface. ip does not show wifi, nor does lspci. The module is
> loaded.
>
> On 08/20/2014 02:02:48 PM, Geoffrey Leach wrote:
> > The kernel info at the link is helpful in that it confirms that the
> > 7260 is supported. Your modprobe command is the key. With all of the
> > permutations I tried, that particular one never occurred :-) Of
> > course, modprobe installed the firmware with nary a complaint. With
> > this, NetworkManager permitted me to create an entry for wifi,
> > although this did not allow me to connect, even after a reboot
> > (modprobe config file in place)
> >
> > The only thing that I can think of is that I mis-copied the MAC
> > address at install time. Any idea how to find it?
> >
> > On 08/20/2014 01:07:22 PM, Kevin J. Cummings wrote:
> > > On 08/20/2014 03:47 PM, Geoffrey Leach wrote:
> > > > I'm setting up a laptop with Fedora 19 up-to-date. The wireless
> >
> > chip
> > > is an Intel 7260.HMW, and I've confirmed that it works (under
> > > windows). The chip was not recognized by the install, so I did a
>
> yum
> > > install of iwl7260.firmware.noarch. That did not install the
>
> module,
> > > and insmod refuses to install either of the two ucode files. So,
> > > presumably they're not modules ("firmware" might be a clue?) So,
>
> how
> > > should I proceed at this point?
> > >
> > > Have you looked here?
> > >
> > > http://wireless.kernel.org/en/users/Drivers/iwlwifi
> > >
> > > What happens when you "modprobe iwlwifi" with the firmware
> >
> > installed?
> > > > Thanks.
> > >
> > > -- 
> > > Kevin J. Cummings
> > > [e-mail]
> > > [e-mail]
> > > [e-mail]
> > > Registered Linux User #1232 (http://www.linuxcounter.net/)
> > > -- 
> > > users mailing list
> > > [e-mail]
> > > To unsubscribe or change subscription options:
> > > https://admin.fedoraproject.org/mailman/listinfo/users
> > > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> > > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> > > Have a question? Ask away: http://ask.fedoraproject.org
> >
> > -- 
> > users mailing list
> > [e-mail]
> > To unsubscribe or change subscription options:
> > https://admin.fedoraproject.org/mailman/listinfo/users
> > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> > Have a question? Ask away: http://ask.fedoraproject.org
>
> -- 
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org

[Rick Stevens]

On 08/20/2014 04:04 PM, Geoffrey Leach issued this missive:
> Here's how to get a MAC address. Assuming (as I do) you have Windows on the same box, go there and start Windows. Then start wireless. Now go to the router admin page on Fedora, asn look to see what's attached. Voila!
>
> The bad news: upgraded the definition for the connection. Still no luck.
>
> How can I tell if the kernel sees the driver?

To get the MAC address, as root, "ifconfig -a", look for the wifi device
and look for the "ether" bit...just like any NIC:

[root@golem4 local]# ifconfig wlan0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         inet 192.168.2.157  netmask 255.255.255.0  broadcast 192.168.2.255
         inet6 fe80::be77:37ff:fe51:115c  prefixlen 64  scopeid 0x20<link>
  --->>> ether bc:77:37:51:11:5c  txqueuelen 1000  (Ethernet) <<<----
         RX packets 165126  bytes 31581078 (30.1 MiB)
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 17241  bytes 1449351 (1.3 MiB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Alternately, use "lspci -v" and look for its entry. The MAC will be
listed as "Device Serial Number":

01:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030 
[Rainbow Peak] (rev 34)
    Subsystem: Intel Corporation Centrino Wireless-N 1030 BGN
    Flags: bus master, fast devsel, latency 0, IRQ 49
    Memory at d1600000 (64-bit, non-prefetchable) [size=8K]
    Capabilities: [c8] Power Management version 3
    Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
    Capabilities: [e0] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
  ---->>	Capabilities: [140] Device Serial Number bc-77-37-ff-ff-51-11-5c
    Kernel driver in use: iwlwifi
    Kernel modules: iwlwifi

At least it does for me. Your mileage may differ.
> On 08/20/2014 02:11:13 PM, Geoffrey Leach wrote:
> > Hmmm ... memo to self: always google first.
> >
> > So, two things. The MAC address that I used was for the ethernet
> > interface. ip does not show wifi, nor does lspci. The module is
> > loaded.
> >
> > On 08/20/2014 02:02:48 PM, Geoffrey Leach wrote:
> > > The kernel info at the link is helpful in that it confirms that the
> > > 7260 is supported. Your modprobe command is the key. With all of the
> > > permutations I tried, that particular one never occurred :-) Of
> > > course, modprobe installed the firmware with nary a complaint. With
> > > this, NetworkManager permitted me to create an entry for wifi,
> > > although this did not allow me to connect, even after a reboot
> > > (modprobe config file in place)
> > >
> > > The only thing that I can think of is that I mis-copied the MAC
> > > address at install time. Any idea how to find it?
> > >
> > > On 08/20/2014 01:07:22 PM, Kevin J. Cummings wrote:
> > > > On 08/20/2014 03:47 PM, Geoffrey Leach wrote:
> > > > > I'm setting up a laptop with Fedora 19 up-to-date. The wireless
> > >
> > > chip
> > > > is an Intel 7260.HMW, and I've confirmed that it works (under
> > > > windows). The chip was not recognized by the install, so I did a
> >
> > yum
> > > > install of iwl7260.firmware.noarch. That did not install the
> >
> > module,
> > > > and insmod refuses to install either of the two ucode files. So,
> > > > presumably they're not modules ("firmware" might be a clue?) So,
> >
> > how
> > > > should I proceed at this point?
> > > >
> > > > Have you looked here?
> > > >
> > > > http://wireless.kernel.org/en/users/Drivers/iwlwifi
> > > >
> > > > What happens when you "modprobe iwlwifi" with the firmware
> > >
> > > installed?
> > > > > Thanks.

----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    [e-mail] -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-           Lottery: A tax on people who are bad at math.            -
----------------------------------------------------------------------

[Geoffrey Leach]

Does not work for an unrecognized piece of hardware. Alas.

The good news is that although I thought I'd installed all updates, that apparently was not the case. Hopefully that will resolve the version conflict that I've discovered from the dmesg output.

On 08/20/2014 05:58:25 PM, Rick Stevens wrote:
> On 08/20/2014 04:04 PM, Geoffrey Leach issued this missive:
> > Here's how to get a MAC address. Assuming (as I do) you have Windows
>
> on the same box, go there and start Windows. Then start wireless. Now
> go to the router admin page on Fedora, asn look to see what's
> attached. Voila!
> > The bad news: upgraded the definition for the connection. Still no
>
> luck.
> > How can I tell if the kernel sees the driver?
>
> To get the MAC address, as root, "ifconfig -a", look for the wifi
> device
> and look for the "ether" bit...just like any NIC:
>
> [root@golem4 local]# ifconfig wlan0
> wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>          inet 192.168.2.157  netmask 255.255.255.0  broadcast
> 192.168.2.255
>          inet6 fe80::be77:37ff:fe51:115c  prefixlen 64  scopeid
> 0x20<link>
>   --->>> ether bc:77:37:51:11:5c  txqueuelen 1000  (Ethernet) <<<----
>          RX packets 165126  bytes 31581078 (30.1 MiB)
>          RX errors 0  dropped 0  overruns 0  frame 0
>          TX packets 17241  bytes 1449351 (1.3 MiB)
>          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> Alternately, use "lspci -v" and look for its entry. The MAC will be
> listed as "Device Serial Number":
>
> 01:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030
>
> [Rainbow Peak] (rev 34)
>    Subsystem: Intel Corporation Centrino Wireless-N 1030 BGN
>    Flags: bus master, fast devsel, latency 0, IRQ 49
>    Memory at d1600000 (64-bit, non-prefetchable) [size=8K]
>    Capabilities: [c8] Power Management version 3
>    Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
>    Capabilities: [e0] Express Endpoint, MSI 00
>    Capabilities: [100] Advanced Error Reporting
>   ---->>	Capabilities: [140] Device Serial Number
> bc-77-37-ff-ff-51-11-5c
>    Kernel driver in use: iwlwifi
>    Kernel modules: iwlwifi
>
> At least it does for me. Your mileage may differ.
> > On 08/20/2014 02:11:13 PM, Geoffrey Leach wrote:
> > > Hmmm ... memo to self: always google first.
> > >
> > > So, two things. The MAC address that I used was for the ethernet
> > > interface. ip does not show wifi, nor does lspci. The module is
> > > loaded.
> > >
> > > On 08/20/2014 02:02:48 PM, Geoffrey Leach wrote:
> > > > The kernel info at the link is helpful in that it confirms that
>
> the
> > > > 7260 is supported. Your modprobe command is the key. With all of
>
> the
> > > > permutations I tried, that particular one never occurred :-) Of
> > > > course, modprobe installed the firmware with nary a complaint.
>
> With
> > > > this, NetworkManager permitted me to create an entry for wifi,
> > > > although this did not allow me to connect, even after a reboot
> > > > (modprobe config file in place)
> > > >
> > > > The only thing that I can think of is that I mis-copied the MAC
> > > > address at install time. Any idea how to find it?
> > > >
> > > > On 08/20/2014 01:07:22 PM, Kevin J. Cummings wrote:
> > > > > On 08/20/2014 03:47 PM, Geoffrey Leach wrote:
> > > > > > I'm setting up a laptop with Fedora 19 up-to-date. The wireless
> > > >
> > > > chip
> > > > > is an Intel 7260.HMW, and I've confirmed that it works (under
> > > > > windows). The chip was not recognized by the install, so I did a
> > >
> > > yum
> > > > > install of iwl7260.firmware.noarch. That did not install the
> > >
> > > module,
> > > > > and insmod refuses to install either of the two ucode files. So,
> > > > > presumably they're not modules ("firmware" might be a clue?) So,
> > >
> > > how
> > > > > should I proceed at this point?
> > > > >
> > > > > Have you looked here?
> > > > >
> > > > > http://wireless.kernel.org/en/users/Drivers/iwlwifi
> > > > >
> > > > > What happens when you "modprobe iwlwifi" with the firmware
> > > >
> > > > installed?
> > > > > > Thanks.
> Rick Stevens, Systems Engineer, AllDigital    [e-mail] -
> AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
>                                                                -
>       Lottery: A tax on people who are bad at math.            -
>
> -- 
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org