Description of problem: Don't know if problem is driver or firmware. I have: 02:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61) When first loaded Oct 24 19:45:24 nbecker1 kernel: iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.1.17kds Oct 24 19:45:24 nbecker1 kernel: iwl4965: Copyright(c) 2003-2007 Intel Corporation sudo /sbin/iwlist wlan0 scan wlan0 Interface doesn't support scanning. ls /sys/class/net eth0 lo But after rmmod/modprobe, it works. There is also 1 kernel message that wasn't there the first time, it's the 3rd one below: Oct 24 19:45:24 nbecker1 kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Oct 24 19:45:24 nbecker1 kernel: iwl4965: Detected Intel Wireless WiFi Link 4965AGN Oct 24 19:45:24 nbecker1 kernel: iwl4965: Tunable channels: 11 802.11bg, 13 802.11a channels Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
How did you installed iwl4965-firmware ? Was it installed at boot time ? Anyway that's not a firmware package problem... Reassigned to someone who may know better... (maybe kernel or NetworkManager or else )
I installed the iwl4965-firmware rpm. As for loading the firmware into the chip, I don't know how that is supposed to happen, or how to tell if it did happen. Any hints?
If you have installed manually the iwl4965-firmware rpm, then that's normal to reload the module... If you have installed the firmware, then rebooted, then you need to reload iwl4965 again, that's meant there is a problem...
(In reply to comment #3) > If you have installed manually the iwl4965-firmware rpm, then that's normal to > reload the module... If you have installed the firmware, then rebooted, then you > need to reload iwl4965 again, that's meant there is a problem... What does "installed the firmware" mean? I installed the rpm.
where does this rpm come from ?
(In reply to comment #5) > where does this rpm come from ? rpm -q iwl4965-firmware iwl4965-firmware-4.44.1.18-2.noarch
well ? why did you installed it ? Wasn't the iwl4965-firmware installed already ? (Have you run Fedora from a livecd or installed on hard disk ?)
(In reply to comment #7) > well ? why did you installed it ? > Wasn't the iwl4965-firmware installed already ? > (Have you run Fedora from a livecd or installed on hard disk ?) I installed F8T3 from disk. Anaconda installed iwl4965-firmware. I have since applied all updates from devel.
Ok, so you have it installed to your drive, but does the problem still appear if you have rebooted ? (and the same tweaks have to be done each time you reboot ?) Does it affect the chip detection if you have your "radio kill switch" on/off before reboot ? your message on the fedora-devel ml say also: > Oct 24 09:44:06 nbecker1 NetworkManager: <WARN> > killswitch_getpower_reply(): Error getting killswitch power: > hal-ipw-killswitch-linux returned 255. Why don't you have mentionned this on this bug ??? Which is your laptol model ? Please be accurate in your answears !
Neal. The problem might be related with "radio kill switch" which vary between many kind of implementation... AFAIK i don't knwo how to determine which is your. So a good information to start would be to tell which is you laptop model ?...
(In reply to comment #10) > Neal. The problem might be related with "radio kill switch" which vary between > many kind of implementation... AFAIK i don't knwo how to determine which is > your. So a good information to start would be to tell which is you laptop model ?... > > Sure. HP dv9000t (brand new)
from your ml list message: I suppose the bug can be closed. Can you confirm this ?
(In reply to comment #12) > from your ml list message: > I suppose the bug can be closed. > Can you confirm this ? Seems OK, thanks for your help.