LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices


Reply
  Search this Thread
Old 05-30-2014, 04:58 AM   #1
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Rep: Reputation: 4
Debian 7.5 "wheezy" does not recognise Intel AC7260 (dual wifi and bluetooth)


The problem is confirmed when I run lspic:

Code:
achim@ascomtux:~$ lspci
00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09)
00:03.0 Audio device: Intel Corporation Device 0a0c (rev 09)
00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 (rev e4)
00:1c.2 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 3 (rev e4)
00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 (rev e4)
00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation Lynx Point-LP SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
02:00.0 Network controller: Intel Corporation Device 08b1 (rev 73)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5287 (rev 01)
03:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 12)
I also checked dmesg and found the following:
Code:
[45344.905881] Bluetooth: hci0: read Intel version: 370710018002030d00
[45344.905897] bluetooth hci0: firmware: failed to load intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq (-2)
[45344.905900] bluetooth hci0: Direct firmware load failed with error -2
[45344.905902] bluetooth hci0: Falling back to user helper
[45344.907748] Bluetooth: hci0 failed to open Intel firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq(-2)
[45344.907761] bluetooth hci0: firmware: failed to load intel/ibt-hw-37.7.bseq (-2)
[45344.907763] bluetooth hci0: Direct firmware load failed with error -2
[45344.907765] bluetooth hci0: Falling back to user helper
[45344.908106] Bluetooth: hci0 failed to open default Intel fw file: intel/ibt-hw-37.7.bseq
Since the AC7260 is a dual wifi and bluetooth device, this suggests that the device is being found but the firmware module isn't present. If anybody sees it differently, please let me know. I'm no expert and might just be missing the point of something.

I'm checking through the information on wifi in the Debian Wiki but haven't found any reference to the AC7260 (yet).

I'm certain that it should work, because I had it working under ubuntu 12.04 running a 3.14 kernel. I am now running debian 7.5 also with a 3.14 kernel. So what am I missing?

Do I need to access another repository? I've already added one for the MATE desktop and another for Shrew Soft VPN client software. Adding a third to the list is unlikely to cause problems if the site is reliable.

All hints, tips, and such like are appreciated.
 
Old 05-30-2014, 05:25 AM   #2
Dutch Master
Senior Member
 
Registered: Dec 2005
Posts: 1,686

Rep: Reputation: 124Reputation: 124
What you (probably) need is the Intel firmware package. It *should* be an apt-get away If not, try adding the Debian-multimedia resource and/or the backports:

http://www.deb-multimedia.org/
http://backports.debian.org/

HTH!
 
Old 05-30-2014, 10:30 AM   #3
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
The firmware packge for intel wireless goes by the name of "firmware-iwlwifi". I installed this package and checked lspci but noted no change to what I've shown above.

Acording to this Linux Wireless page my dual wifi chipset (AC7260) has been supported since kernel 3.10 and, as noted, I'm running 3.14. So I'm fine from that point of view.

I thought I might just be getting an older version of the firmware, so I added the two repositories mentioned by Dutch Master and reinstalled the package. This also has had no effect. I used synaptic (because I'm basically lazy) so I didn't get a lot of diagnotic info back. I guess there's a log somewhere, and I'll look for it eventually to find out just where I'm getting that package from. but not just at this moment.

Since network restart is deprecated and I can't think of anything else I'm going to restart the machine. I know that sounds like a very "windows" thing to do, but it can't hurt.

So where was the firmware coming from when I used ubuntu??
 
Old 05-30-2014, 11:00 AM   #4
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
Problem isolated

After restarting, I tried lspci again but tthere was no change as far as I could tell:
Code:
achim@ascomtux:~$ lspci
00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09)
00:03.0 Audio device: Intel Corporation Device 0a0c (rev 09)
00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 (rev e4)
00:1c.2 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 3 (rev e4)
00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 (rev e4)
00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation Lynx Point-LP SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
02:00.0 Network controller: Intel Corporation Device 08b1 (rev 73)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5287 (rev 01)
03:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 12)
Checking the output from dmesg more closely this time revealed the following:
Code:
[    1.480246] iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-7260-7.ucode (-2)
[    1.480316] iwlwifi 0000:02:00.0: Direct firmware load failed with error -2
[    1.480318] iwlwifi 0000:02:00.0: Falling back to user helper
[    1.482849] iwlwifi 0000:02:00.0: no suitable firmware found!
The same bluetooth messages as above are also present. Given the information on the site I mentioned in my previous post and the fact that The chipset I've got is not listed when I check the package details in synaptic, leads me to believe that I am indeed getting a somewhat older version of iwlwifi.

There are some instructions on the site I mentioned previously that explain how to install the firmware manually. I guess that will be the next step. But before then I'll need to take a break and get on with some work that puts bread on the table. ;-)

Helpful hints that might save me some time are, as always, most welcome.
 
Old 05-31-2014, 06:56 PM   #5
Tadaen
Member
 
Registered: Sep 2005
Distribution: Arch
Posts: 210

Rep: Reputation: 39
The iwlwifi package for wheezy only goes up to the 6200 series of intel wifi cards. firmware-iwlwifi can do the 7200 from backports. It is in the non-free section.
 
Old 05-31-2014, 07:02 PM   #6
k3lt01
Senior Member
 
Registered: Feb 2011
Location: Australia
Distribution: Debian Wheezy, Jessie, Sid/Experimental, playing with LFS.
Posts: 2,900

Rep: Reputation: 637Reputation: 637Reputation: 637Reputation: 637Reputation: 637Reputation: 637
As pointed out a few times you need to upgrade to the latest iwlwifi package from backports. Just because you are running kernel 3.14 doesn't mean you are running the appropriate firmware when that firmware is non-free.
 
Old 06-01-2014, 07:36 AM   #7
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
Quote:
Originally Posted by k3lt01 View Post
As pointed out a few times you need to upgrade to the latest iwlwifi package from backports. Just because you are running kernel 3.14 doesn't mean you are running the appropriate firmware when that firmware is non-free.
I do believe I was the first to have pointed to that as being the likely problem. I later confirmed it. In my posts, I also mentioned, that I have added the resource and the backport repos mentioned by Dutch Master to my sources.list and that it didn't fix the problem. This is, incidentally, why I wanted to know where ubuntu was getting the firmware from.

As for running kernel 3.14, I pointed that out because (with the correct firmware) the AC7260 has been supported since kernel 3.10. However, standard wheezy installations run a 3.2.something-or-other kernel. With or without the correct firmware, you are unlikely to get this device functioning correctly using that kernel.

The latest attempt to get the firmware I need involved following the basic instructions for backport repositories in the debian wiki. This also does not provide an iwlwifi package with AC7260 support. However, there are other repositories to be checked. Since the URL in the instructions doesn't match that in this announcement, I'll have to try that one instead. If anybody out there knows which repository I should use, please let me know.

If no such repository exists, I'll have to try the hands on approach described in the Linux Wireless page and apply a patch which it describes. This means compiling the firmware from source and installing it myself... well it's not the most difficult thing to do, just time consuming and error prone.

I'll post again when I have something positive to report.

P.S. I correct my earlier assertion... Dutch Master was the first to mention using a different repository, though I mentioned in my first post that it was most likely a firmware problem. Tadaen also mentioned that the firmware is available (only just noticed that piece of information) but unfortunately didn't mention the backport URL, just that it's non-free, which I already know. As mentioned above, there seems to be more than one backport URL I could use.

Last edited by achim_59; 06-01-2014 at 07:48 AM. Reason: Factual correction & spelling
 
Old 06-02-2014, 02:30 AM   #8
k3lt01
Senior Member
 
Registered: Feb 2011
Location: Australia
Distribution: Debian Wheezy, Jessie, Sid/Experimental, playing with LFS.
Posts: 2,900

Rep: Reputation: 637Reputation: 637Reputation: 637Reputation: 637Reputation: 637Reputation: 637
I don't quite get what the point of your last post is if you know all this. From reading your posts, this last one included, it appears you have a few misconceptions. Myself and others are just trying to help you.

Debian removes all non-free blobs (firmware is a blob) from the kernel. Just because you have the latest kernel installed doesn't men you have the latest blob for your hardware installed. Thinking that because Ubuntu has it means Debian must also have it ignores the fact Ubuntu and Debian don't have the same ideals. Ubuntu uses Jockey, which it adds to the kernel, to check the users hardware to see if they require non-free firmware and it will install it for you. Debian does not do this nor does it provide that firmware in its official iso images.

There is only 1 official Debian backport repository. The information on how to add it and use it is here.

If you need to find things in Debian packages the best place to look is here.Checked for 7260 in iwlwifi and it is present in the backports repository non-free firmware-iwlwifi package.

Last edited by k3lt01; 06-02-2014 at 06:54 AM. Reason: Rechecked after noticing typographical error.
 
Old 06-02-2014, 05:40 AM   #9
EDDY1
LQ Addict
 
Registered: Mar 2010
Location: Oakland,Ca
Distribution: wins7, Debian wheezy
Posts: 6,841

Rep: Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649
This thread says that it's fixed in 3.10 kernel
http://forums.debian.net/viewtopic.php?f=7&t=106537
You may want to try backports kernel
https://packages.debian.org/wheezy-backports/kernel/
 
Old 06-03-2014, 03:56 PM   #10
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
Ahem... I didn't mean to offend. Honestly.

Quote:
I don't quite get what the point of your last post is if you know all this. From reading your posts, this last one included, it appears you have a few misconceptions. Myself and others are just trying to help you.
I know diddly-squat. What I have posted to date is my surmise and interpretation of the information I have. To say I have some misconceptions presumes I have some conception of what's going on. That is certainly not the case. I'm on a steep learning curve here. Until recently my experiences were one step removed from the O/S (applications, databases... that sort of thing). In the last few months I've been learning C (on the fly) and been confronted with various systems programming issues. Now I'm confronted with (shudder) kernel stuff and I'm feeling a bit lost.

Thanks for the tip about kernel "blobs". I'll add that to my mental repository. As far as I'm aware, firmware is usually in the form of a shared object library. For blobs it might be a statically linked archive. Whatever. I'll check out the links you've given and report back. Work is taking a front seat in the priorities at the moment, so it might take a while.

For my VPN I added the following:
Code:
deb http://ftp.de.debian.org/debian wheezy-backports main
However, that hasn't helped with the issue at hand. I'll read the full backports info first, then I'll try adding that iwlwifi package.

'Bye for now,
Achim
 
Old 06-03-2014, 05:19 PM   #11
k3lt01
Senior Member
 
Registered: Feb 2011
Location: Australia
Distribution: Debian Wheezy, Jessie, Sid/Experimental, playing with LFS.
Posts: 2,900

Rep: Reputation: 637Reputation: 637Reputation: 637Reputation: 637Reputation: 637Reputation: 637
Quote:
Originally Posted by achim_59 View Post
Ahem... I didn't mean to offend. Honestly.
Don't worry no offense taken. It seems you have taken on alot of learning, I couldn't do it.
Just so you know backports are not automatic upgrades from normal to backport, you have to force the first upgrade after that they are automatic.
 
Old 06-11-2014, 02:57 PM   #12
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
OK, this has taken a while, but I haven't been idle. When I had some moments to spare I checked out the debian administrator's handbook entries on repositories and apt tools. Armed with that and the URLs in the last few posts, after fiddling a bit with the syntax I added the following entries to my sources.list (first one, then the other)...
Code:
deb https://packages.debian.org/ wheezy-backports/kernel non-free
deb https://packages.debian.org/ wheezy-backports/kernel/firmware non-free
After each addition I tried running apt-get upgrade with the following results.
After the first addition:
Code:
root@ascomtux:/etc/apt# apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be upgraded:
  libavcodec53 libavformat53 libavutil51 libgnutls26 libpostproc52 libssl1.0.0 libswscale2 libusb-1.0-0 linux-image-3.14-0.bpo.1-amd64
  linux-image-3.2.0-4-amd64 openssl
11 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 60.2 MB of archives.
After this operation, 2,670 kB disk space will be freed.
Do you want to continue [Y/n]? y
Get:1 http://ftp.debian.org/debian/ wheezy-backports/main libusb-1.0-0 amd64 2:1.0.18-2~bpo70+1 [53.5 kB]
Get:2 http://security.debian.org/ wheezy/updates/main libgnutls26 amd64 2.12.20-8+deb7u2 [618 kB]
Get:3 http://ftp.debian.org/debian/ wheezy-backports/main linux-image-3.14-0.bpo.1-amd64 amd64 3.14.5-1~bpo70+1 [30.8 MB]
Get:4 http://security.debian.org/ wheezy/updates/main libssl1.0.0 amd64 1.0.1e-2+deb7u10 [1,258 kB]
Get:5 http://security.debian.org/ wheezy/updates/main libavutil51 amd64 6:0.8.12-1 [102 kB]                                                
Get:6 http://security.debian.org/ wheezy/updates/main libavcodec53 amd64 6:0.8.12-1 [2,516 kB]                                             
Get:7 http://security.debian.org/ wheezy/updates/main libavformat53 amd64 6:0.8.12-1 [475 kB]                                              
Get:8 http://security.debian.org/ wheezy/updates/main libpostproc52 amd64 6:0.8.12-1 [97.7 kB]                                             
Get:9 http://security.debian.org/ wheezy/updates/main libswscale2 amd64 6:0.8.12-1 [130 kB]                                                
Get:10 http://security.debian.org/ wheezy/updates/main linux-image-3.2.0-4-amd64 amd64 3.2.57-3+deb7u2 [23.4 MB]                           
Get:11 http://security.debian.org/ wheezy/updates/main openssl amd64 1.0.1e-2+deb7u10 [700 kB]                                             
Fetched 60.2 MB in 1min 41s (595 kB/s)                                                                                                     
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 148151 files and directories currently installed.)
Preparing to replace libgnutls26:amd64 2.12.20-8+deb7u1 (using .../libgnutls26_2.12.20-8+deb7u2_amd64.deb) ...
Unpacking replacement libgnutls26:amd64 ...
Preparing to replace libssl1.0.0:amd64 1.0.1e-2+deb7u9 (using .../libssl1.0.0_1.0.1e-2+deb7u10_amd64.deb) ...
Unpacking replacement libssl1.0.0:amd64 ...
Preparing to replace libavutil51:amd64 6:0.8.10-1 (using .../libavutil51_6%3a0.8.12-1_amd64.deb) ...
Unpacking replacement libavutil51:amd64 ...
Preparing to replace libavcodec53:amd64 6:0.8.10-1 (using .../libavcodec53_6%3a0.8.12-1_amd64.deb) ...
Unpacking replacement libavcodec53:amd64 ...
Preparing to replace libavformat53:amd64 6:0.8.10-1 (using .../libavformat53_6%3a0.8.12-1_amd64.deb) ...
Unpacking replacement libavformat53:amd64 ...
Preparing to replace libpostproc52:amd64 6:0.8.10-1 (using .../libpostproc52_6%3a0.8.12-1_amd64.deb) ...
Unpacking replacement libpostproc52:amd64 ...
Preparing to replace libswscale2:amd64 6:0.8.10-1 (using .../libswscale2_6%3a0.8.12-1_amd64.deb) ...
Unpacking replacement libswscale2:amd64 ...
Preparing to replace libusb-1.0-0:amd64 2:1.0.17-1~bpo70+1 (using .../libusb-1.0-0_2%3a1.0.18-2~bpo70+1_amd64.deb) ...
Unpacking replacement libusb-1.0-0:amd64 ...
Preparing to replace linux-image-3.14-0.bpo.1-amd64 3.14.4-1~bpo70+1 (using .../linux-image-3.14-0.bpo.1-amd64_3.14.5-1~bpo70+1_amd64.deb) ...
Unpacking replacement linux-image-3.14-0.bpo.1-amd64 ...
Preparing to replace linux-image-3.2.0-4-amd64 3.2.57-3+deb7u1 (using .../linux-image-3.2.0-4-amd64_3.2.57-3+deb7u2_amd64.deb) ...
Unpacking replacement linux-image-3.2.0-4-amd64 ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
Preparing to replace openssl 1.0.1e-2+deb7u9 (using .../openssl_1.0.1e-2+deb7u10_amd64.deb) ...
Unpacking replacement openssl ...
Processing triggers for man-db ...
Setting up libgnutls26:amd64 (2.12.20-8+deb7u2) ...
Setting up libssl1.0.0:amd64 (1.0.1e-2+deb7u10) ...
Setting up libavutil51:amd64 (6:0.8.12-1) ...
Setting up libavcodec53:amd64 (6:0.8.12-1) ...
Setting up libavformat53:amd64 (6:0.8.12-1) ...
Setting up libpostproc52:amd64 (6:0.8.12-1) ...
Setting up libswscale2:amd64 (6:0.8.12-1) ...
Setting up libusb-1.0-0:amd64 (2:1.0.18-2~bpo70+1) ...
Setting up linux-image-3.14-0.bpo.1-amd64 (3.14.5-1~bpo70+1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-3.14-0.bpo.1-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169
/etc/kernel/postinst.d/zz-update-grub:
Generating grub.cfg ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-3.14-0.bpo.1-amd64
Found initrd image: /boot/initrd.img-3.14-0.bpo.1-amd64
Found linux image: /boot/vmlinuz-3.12-0.bpo.1-amd64
Found initrd image: /boot/initrd.img-3.12-0.bpo.1-amd64
Found linux image: /boot/vmlinuz-3.2.0-4-amd64
Found initrd image: /boot/initrd.img-3.2.0-4-amd64
done
Setting up linux-image-3.2.0-4-amd64 (3.2.57-3+deb7u2) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
Generating grub.cfg ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-3.14-0.bpo.1-amd64
Found initrd image: /boot/initrd.img-3.14-0.bpo.1-amd64
Found linux image: /boot/vmlinuz-3.12-0.bpo.1-amd64
Found initrd image: /boot/initrd.img-3.12-0.bpo.1-amd64
Found linux image: /boot/vmlinuz-3.2.0-4-amd64
Found initrd image: /boot/initrd.img-3.2.0-4-amd64
done
That's probably more output than you want to read, so I'll point out the salient fact: firmware-iwlwifi was not included in the list of packages upgraded. That's why I tried adding the second line shown above. Again I ran apt-get upgrade and got rather less output:
Code:
root@ascomtux:/etc/apt# apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@ascomtux:/etc/apt# less sources.list
Obviously I haven't fully understood what the administrator's handbook says. I admit I haven't read all of it and probably didn't pay as much attention to the details as I should have. Sadly, I really don't have much time for this stuff and the administrator's handbook is not really an ideal learning source, but it's the best I've found to date.

So what exactly is the point that I'm missing? I checked in Synaptic and the installed version is 0.36, whereas the package listed on the backport URL has 0.41. Furthermore, Synaptic does not offer the option to upgrade the package.

So I guess the question should be: What did I do wrong?

Any suggestions, people?
 
Old 06-11-2014, 04:29 PM   #13
EDDY1
LQ Addict
 
Registered: Mar 2010
Location: Oakland,Ca
Distribution: wins7, Debian wheezy
Posts: 6,841

Rep: Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649
You need to install firmware-realtek
 
Old 06-12-2014, 02:47 AM   #14
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
Quote:
Originally Posted by EDDY1 View Post
You need to install firmware-realtek
Why would I need that firmware? The device (AC 7260) is from Intel and it is not listed in Synaptic as part of the firmware-realtek package. It is listed for the firmware-iwlwifi package for version 0.41 as seen here

So OK, firmware you don't need doesn't hurt, so I installed it anyway. Hasn't helped, though. Neither wicd nor Kismet detect any wireles networks. Since I'm in the middle of Düsseldorf, I'd expect there to be a dozen or so WLANs within spitting distance.

There would seem to be no reason to retain that firmware, so I guess I'll remove it.

BTW the list generated by lspci is unchanged to that shown previously.

So any other ideas out there?
 
Old 06-12-2014, 03:54 AM   #15
EDDY1
LQ Addict
 
Registered: Mar 2010
Location: Oakland,Ca
Distribution: wins7, Debian wheezy
Posts: 6,841

Rep: Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649
Well that is my bad although your system is requesting the firmware package for your ethernet card.
also the package that you're wanting to install is 1 that has to be manually installed.
You can either install thru synapic which is easier, by searching from origin selecting backports & selecting desired package or with apt-get.
Quote:
apt-get -t wheezy-backports install "package"
changing "package" to your kernel version or iwlwifi or both. Actually your kernel was upgraded, so install iwlwifi
Quote:
apt-get -t wheezy-backports install firmware-iwlwifi

Last edited by EDDY1; 06-12-2014 at 04:00 AM.
 
  


Reply

Tags
bluetooth, wheezy, wifi



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
where is "Users and Groups" in Debian "Wheezy" ? StefanP Linux - Newbie 10 04-28-2014 03:37 PM
Debian "squeeze" install - Intel Centrino 6230 wifi problems blooz4u Linux - Wireless Networking 4 03-13-2013 05:10 AM
LXer: Deploy your own "cloud" with Debian "Wheezy" LXer Syndicated Linux News 0 04-25-2012 06:50 PM
LXer: "military grade" Linux PDA gains WiFi, Bluetooth LXer Syndicated Linux News 0 07-08-2006 07:54 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian

All times are GMT -5. The time now is 03:24 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration