I've been fiddling around with Crunchbang for a bit, and it seems pretty good. I'd love to be able to use it, but I can't get my Intel N 1030 wireless card to work.
I downloaded iwlwifi-6000g2b-6.ucode off intellinuxwireless.org, because that's the driver that's supposed to make my wireless card work. But I have no idea how to install it. Can anyone help me? I copied it into /lib/firmware, and tried modprobe -r iwlagn and then modprobe iwlagn, rebooted but it didn't seem to do anything. I then changed the permissions of the iwlwifi file I copied in to read only like all of the other iwlwifi files. I copied it in, modprobe –r and modprobe again, rebooted, but it didn't do anything again. I've got a wired connection at the moment, but I need a wireless connection. There's a readme that came with the file that’s supposed to tell me how to install it, but I think I’ve done everything it tells me.
I then tried running waldorf off a live usb, and it wouldn’t boot, because of bad LUN numbers or something. I then installed the linux 2.6.36 64-bit image and headers because, according to intellinuxwireless, that version should work with my wireless card. When it booted, it said iwlwifi-6000g2b-4.ucode can’t be found, even though that’s not the driver for my card, and once again my wireless card didn’t work. I then installed linux image 2.6.37 and headers, and that wouldn’t even boot. I don’t know what else I can do to get my wireless card to work. Am I overlooking something?
Thanks in advance!
00:00.0 Host bridge : Intel Corporation Sandy Bridge DRAM Controller [8086:0104] (rev 09) 00:01.0 PCI bridge : Intel Corporation Sandy Bridge PCI Express Root Port [8086:0101] (rev 09) 00:02.0 VGA compatible controller : Intel Corporation Sandy Bridge Integrated Graphics Controller [8086:0116] (rev 09) 00:16.0 Communication controller : Intel Corporation Cougar Point HECI Controller #1 [8086:1c3a] (rev 04) 00:1a.0 USB Controller [0c03]: Intel Corporation Cougar Point USB Enhanced Host Controller #2 [8086:1c2d] (rev 05) 00:1b.0 Audio device : Intel Corporation Cougar Point High Definition Audio Controller [8086:1c20] (rev 05) 00:1c.0 PCI bridge : Intel Corporation Cougar Point PCI Express Root Port 1 [8086:1c10] (rev b5) 00:1c.1 PCI bridge : Intel Corporation Cougar Point PCI Express Root Port 2 [8086:1c12] (rev b5) 00:1c.2 PCI bridge : Intel Corporation Cougar Point PCI Express Root Port 3 [8086:1c14] (rev b5) 00:1c.3 PCI bridge : Intel Corporation Cougar Point PCI Express Root Port 4 [8086:1c16] (rev b5) 00:1d.0 USB Controller [0c03]: Intel Corporation Cougar Point USB Enhanced Host Controller #1 [8086:1c26] (rev 05) 00:1f.0 ISA bridge : Intel Corporation Cougar Point LPC Controller [8086:1c49] (rev 05) 00:1f.2 SATA controller : Intel Corporation Cougar Point 6 port SATA AHCI Controller [8086:1c03] (rev 05) 00:1f.3 SMBus [0c05]: Intel Corporation Cougar Point SMBus Controller [8086:1c22] (rev 05) 01:00.0 VGA compatible controller : ATI Technologies Inc Device [1002:6740] 07:00.0 Ethernet controller : Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06) 0d:00.0 Network controller : Intel Corporation Device [8086:008b] (rev 34) 13:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device [10ec:5209] (rev 01) 19:00.0 USB Controller [0c03]: NEC Corporation uPD720200 USB 3.0 Host Controller [1033:0194] (rev 04)
Firstly, it's always advisable to check distro-specific documentation (in Crunchbang's case, it would be Debian) first. Turning to tarballs from vendors should only be done as a last resort or for some specific functionality the distro packages don't provide.
According to your PCI alias field, your device (8086:008b) seems to only be supported with the firmware-iwlwifi & wireless-tools packages (and possibly a 3.2.0 kernel or later) from Testing/Wheezy. I'm assuming the versions you grabbed directly from Intel are equal to or more recent.
Not sure what course of action I can recommend aside from changing your sources to point to Wheezy, which you might or might not want to do. I suppose you could remove the drivers you installed manually, then revert configs, and then manually download and install (either with "dpkg -i" or gdebi) the firmware-iwlwifi and wireless-tools deb's from Testing (check the dependencies as well), and then follow steps 3, 4 and 5 from here.
Might be best to wait for xaos52 to comment first, as his ways are usually safer than my own (I run Sid), plus he's just generally better at explaining stuff.
Last edited by gutterslob (2012-06-06 10:00:36)
Point & Squirt
Thanks for the info gutterslob, I'm new to all of this so its much appreciated.
I reinstalled crunchbang, added wheezy to my sources.list, and installed the newest firmware-iwlwifi and wireless-tools. I installed the newest gcc and libc6 as well as they were dependencies. I then tried modprobe -r iwlwifi, and terminal gave me 'FATAL: Module iwlwifi not found.'. Not sure what I'm supposed to do from here
No i didn't, I'm using the statler default kernel.
uname -r gives:
Do I need to update to kernel 3.2.0 for it to work? Thanks for the quick reply!
I installed the 3.2.0-2 headers and image. It hangs for about a minute after telling me
udevd-work: '/sbin/modprobe -bv pci:<followed by some numbers>' unexpected exit with status 0x0009
from recovery mode. But it eventually skips that and keeps going.
What I'm really concerned about is after GDM starts, I get a blank screen. I've looked around and I think its to do with X. When I go into recovery mode and startx, the screen goes blank on me again. So do I need to install some ati drivers or something?
Sounds like video driver issue.
I have nil experience with ATI.
el_koraco is the specialist here.
It is highly probable that you have to re-install the prop video driver after a kernel change.
Use 'USER LIST' to search for el_koraco. He has links to ATI threads in his signature.
Using smxi/sgfxi might be an option too. Search the forum for references.
Sorry about the delay between replies, I had exams.
So i went into recovery mode of linux 3.2.0-2 to try and run smxi, and while trying to apt-get install it, it told me that it was unable to fetch from ftp.debian.org. So then I tried apt-get updating, but that didn't work either. I then removed and added the r8169 module, tried using dhclient eth0, but the wired connection still isn't working. So I'm not sure how to run smxi
Networking is not up in recovery mode.
To enable wired network in recovery mode, run this command as root
echo -e "\nauto eth0\niface eth0 inet dhcp" >>/etc/network/interfaces
Reboot into recover mode and you should have wired eth working...
It still won't be working. When you're in recovery mode after you've added what dr xaos said, run
invoke-rc.d networking start ifup eth0
But first, go into your BIOS settings and see if there is an option to run only on integrated graphics. If so, select it and try to boot normally. If not, proceed as planned. I'm afraid the hybrid graphics situation is a little trickier than using straight up AMD graphics.
Thanks for the info. I got the internet working in recovery mode, and ran smxi according to your guide el_koraco. It eventually asked me if I want to quit or create an xorg.conf file since I don't have one, so I hit create xorg.conf, and it then gave me the blank screen that it gives me when I boot into 3.2.0-2 normally.
My BIOS has a fixed or dynamic switchable graphics mode so I don' think I can only use the integrated card, but I'm dual booting with Windows 7 so using only integrated graphics wouldn't be desirable.
Thanks for your help, it seems to be one problem after the other.