3.1-rc9 wifi problem

3.1-rc9 wifi problem

[werner]

[-- Attachment #1: Type: text/plain, Size: 546 bytes --]

A laptop of a friend, which worked always with wifi until 
3.0.4 , stopped to work when installing 3.1-rc9 , after 
re-installing 3.0.4 wifi returned to work.  I think it was 
a packard-bell laptop.   I can't test this better because 
he gone with his laptop; perhaps next week he'll visit me 
again. Since 2.6.38 his laptop worked with my wifi.

This can be a regression in the wifi drivers, or because 
of a slightly changed config. Anyway the diff of config is 
enclosed.

w.landgraf
---
Professional hosting for everyone - http://www.host.ru

[-- Attachment #2: config.diff.txt --]
[-- Type: text/plain, Size: 10410 bytes --]

2,3c2,3
< # Automatically generated make config: don't edit
< # Linux/i386 3.0.0 Kernel Configuration
---
> # Automatically generated file; DO NOT EDIT.
> # Linux/i386 3.1.0-rc8 Kernel Configuration
85c85,87
< # CONFIG_TASKSTATS is not set
---
> CONFIG_TASKSTATS=y
> CONFIG_TASK_DELAY_ACCT=y
> # CONFIG_TASK_XACCT is not set
150a153
> # CONFIG_KALLSYMS_ALL is not set
155a159
> CONFIG_HAVE_PCSPKR_PLATFORM=y
171a176
> # CONFIG_DEBUG_PERF_USE_VMALLOC is not set
201a207
> CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y
220a227
> # CONFIG_BLK_DEV_BSGLIB is not set
277c284
< CONFIG_X86_MRST=y
---
> # CONFIG_X86_INTEL_MID is not set
283a291
> # CONFIG_PARAVIRT_TIME_ACCOUNTING is not set
290a299
> # CONFIG_PARAVIRT_DEBUG is not set
321a331
> CONFIG_CMPXCHG_DOUBLE=y
343d352
< CONFIG_APB_TIMER=y
346d354
< CONFIG_IOMMU_API=y
408a417
> # CONFIG_HWPOISON_INJECT is not set
483,484c492,494
< CONFIG_ACPI_APEI_GHES=m
< # CONFIG_ACPI_APEI_PCIEAER is not set
---
> CONFIG_ACPI_APEI_GHES=y
> CONFIG_ACPI_APEI_PCIEAER=y
> CONFIG_ACPI_APEI_MEMORY_FAILURE=y
558,560d567
< CONFIG_DMAR=y
< CONFIG_DMAR_DEFAULT_ON=y
< CONFIG_DMAR_FLOPPY_WA=y
570a578
> # CONFIG_PCI_DEBUG is not set
589c597,598
< CONFIG_OLPC_XO1=m
---
> # CONFIG_OLPC_XO1_PM is not set
> # CONFIG_OLPC_XO15_SCI is not set
851a861
> CONFIG_IP_SET_HASH_NETIFACE=m
989a1000,1004
> 
> #
> # DCCP Kernel Hacking
> #
> # CONFIG_IP_DCCP_DEBUG is not set
1318a1334,1340
> CONFIG_NFC=m
> 
> #
> # Near Field Communication (NFC) devices
> #
> CONFIG_PN544_NFC=m
> CONFIG_NFC_PN533=m
1334a1357,1358
> # CONFIG_DEBUG_DRIVER is not set
> # CONFIG_DEBUG_DEVRES is not set
1335a1360,1361
> CONFIG_REGMAP=y
> CONFIG_REGMAP_I2C=m
1512a1539
> CONFIG_OF_PCI_IRQ=y
1572a1600
> CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
1620a1649
> CONFIG_USB_SWITCH_FSA9480=m
1631a1661
> # CONFIG_EEPROM_93XX46 is not set
1805a1836
> # CONFIG_SCSI_MVSAS_TASKLET is not set
2035d2065
< # CONFIG_LOOPBACK_TARGET_CDB_DEBUG is not set
2036a2067
> CONFIG_ISCSI_TARGET=m
2236a2268
> # CONFIG_SKGE_GENESIS is not set
2334a2367,2368
> CONFIG_B43_BCMA=y
> CONFIG_B43_SSB=y
2338a2373
> CONFIG_B43_BCMA_PIO=y
2441a2477
> CONFIG_RTL8192DE=m
2585a2622
> CONFIG_CAIF_HSI=m
2900d2936
< CONFIG_TOUCHSCREEN_INTEL_MID=y
2944a2981,2982
> CONFIG_INPUT_MMA8450=y
> CONFIG_INPUT_MPU3050=y
2950a2989,2990
> CONFIG_INPUT_KXTJ9=y
> CONFIG_INPUT_KXTJ9_POLLED_MODE=y
2955a2996
> CONFIG_INPUT_TWL6040_VIBRA=y
3045d3085
< CONFIG_SERIAL_MAX3107_AAVA=m
3190a3231
> # CONFIG_SPI_DEBUG is not set
3243a3285
> # CONFIG_DEBUG_GPIO is not set
3244a3287
> CONFIG_GPIO_GENERIC=m
3250,3251c3293
< CONFIG_GPIO_BASIC_MMIO_CORE=m
< CONFIG_GPIO_BASIC_MMIO=m
---
> CONFIG_GPIO_GENERIC_PLATFORM=m
3265a3308
> CONFIG_GPIO_TPS65912=m
3346d3388
< CONFIG_BATTERY_INTEL_MID=m
3350a3393,3394
> CONFIG_CHARGER_MAX8997=m
> CONFIG_CHARGER_MAX8998=m
3413a3458
> CONFIG_SENSORS_LM95245=m
3416a3462
> CONFIG_SENSORS_MAX1668=m
3419a3466
> CONFIG_SENSORS_NTC_THERMISTOR=m
3425a3473
> # CONFIG_SENSORS_LM25066 is not set
3441a3490
> CONFIG_SENSORS_SCH56XX_COMMON=m
3442a3492
> CONFIG_SENSORS_SCH5636=m
3478a3529
> # CONFIG_WATCHDOG_CORE is not set
3502d3552
< CONFIG_INTEL_SCU_WATCHDOG=y
3569a3620
> CONFIG_BCMA_BLOCKIO=y
3584a3636,3639
> CONFIG_MFD_TPS65910=y
> CONFIG_MFD_TPS65912=y
> CONFIG_MFD_TPS65912_I2C=y
> CONFIG_MFD_TPS65912_SPI=y
3587c3642
< CONFIG_TWL4030_CODEC=y
---
> CONFIG_MFD_TWL4030_AUDIO=y
3588a3644
> CONFIG_TWL6040_CORE=y
3624c3680
< CONFIG_MFD_TPS65910=y
---
> CONFIG_MFD_AAT2870_CORE=y
3655a3712
> CONFIG_REGULATOR_TPS65912=m
3662a3720
> CONFIG_REGULATOR_AAT2870=m
3672a3731
> CONFIG_DVB_NET=y
3688a3748
> CONFIG_IR_MCE_KBD_DECODER=y
3720a3781
> CONFIG_MEDIA_TUNER_XC4000=m
3737a3799
> CONFIG_VIDEOBUF2_DMA_CONTIG=m
3803a3866,3869
> # Flash devices
> #
> 
> #
3867a3934
> CONFIG_SOC_CAMERA_OV5642=m
3895a3963
> CONFIG_USB_GSPCA_SE401=m
3926a3995
> CONFIG_VIDEO_EM28XX_RC=y
4082a4152,4156
> # Supported ddbridge ('Octopus') Adapters
> #
> CONFIG_DVB_DDBRIDGE=m
> 
> #
4099a4174,4179
> # Multistandard (cable + terrestrial) frontends
> #
> CONFIG_DVB_DRXK=m
> CONFIG_DVB_TDA18271C2DD=m
> 
> #
4362a4443
> CONFIG_LCD_AMS369FG06=m
4376a4458
> CONFIG_BACKLIGHT_AAT2870=m
4496a4579
> CONFIG_SND_TEA575X=m
4546d4628
< CONFIG_SND_TEA575X=m
4547a4630
> CONFIG_SND_HDA_PREALLOC_SIZE=64
4554a4638
> CONFIG_SND_HDA_ENABLE_REALTEK_QUIRKS=y
4561a4646
> CONFIG_SND_HDA_CODEC_CA0132=y
4610,4611d4694
< CONFIG_SND_MFLD_MACHINE=m
< CONFIG_SND_SST_PLATFORM=m
4618a4702
> CONFIG_SND_SOC_ADAV80X=m
4638d4721
< CONFIG_SND_SOC_SN95031=m
4640a4724
> CONFIG_SND_SOC_STA32X=m
4666a4751
> CONFIG_SND_SOC_WM8782=m
4671d4755
< CONFIG_SND_SOC_WM8915=m
4679a4764
> CONFIG_SND_SOC_WM8983=m
4686a4772
> CONFIG_SND_SOC_WM8996=m
4743a4830,4831
> CONFIG_HID_HOLTEK=m
> CONFIG_HOLTEK_FF=y
4779a4868
> CONFIG_HID_SPEEDLINK=m
4789a4879
> CONFIG_HID_WIIMOTE=m
4969a5060
> # CONFIG_USB_GADGET_DEBUG is not set
4973,4979c5064,5067
< CONFIG_USB_GADGET_SELECTED=y
< # CONFIG_USB_GADGET_FUSB300 is not set
< # CONFIG_USB_GADGET_R8A66597 is not set
< # CONFIG_USB_GADGET_PXA_U2O is not set
< # CONFIG_USB_GADGET_M66592 is not set
< # CONFIG_USB_GADGET_AMD5536UDC is not set
< CONFIG_USB_GADGET_CI13XXX_PCI=y
---
> CONFIG_USB_FUSB300=m
> CONFIG_USB_R8A66597=m
> CONFIG_USB_M66592=m
> CONFIG_USB_AMD5536UDC=m
4981,4985c5069,5075
< # CONFIG_USB_GADGET_NET2280 is not set
< # CONFIG_USB_GADGET_GOKU is not set
< # CONFIG_USB_GADGET_LANGWELL is not set
< # CONFIG_USB_GADGET_EG20T is not set
< # CONFIG_USB_GADGET_DUMMY_HCD is not set
---
> CONFIG_USB_NET2272=m
> CONFIG_USB_NET2272_DMA=y
> CONFIG_USB_NET2280=m
> CONFIG_USB_GOKU=m
> CONFIG_USB_LANGWELL=m
> CONFIG_USB_EG20T=m
> CONFIG_USB_DUMMY_HCD=m
4986a5077
> CONFIG_USB_GADGET_SUPERSPEED=y
5024d5114
< CONFIG_USB_LANGWELL_OTG=m
5050d5139
< CONFIG_MMC_SDHCI_OF=y
5089,5090d5177
< CONFIG_LEDS_GPIO_PLATFORM=y
< CONFIG_LEDS_GPIO_OF=y
5122,5123d5208
< CONFIG_NFC_DEVICES=y
< CONFIG_PN544_NFC=m
5231d5315
< CONFIG_RTC_DRV_VRTC=m
5287a5372,5379
> CONFIG_VIRTIO=y
> CONFIG_VIRTIO_RING=y
> 
> #
> # Virtio drivers
> #
> CONFIG_VIRTIO_PCI=m
> CONFIG_VIRTIO_BALLOON=m
5289,5294d5380
< CONFIG_STALLION=m
< CONFIG_ISTALLION=m
< CONFIG_DIGIEPCA=m
< CONFIG_RISCOM8=m
< CONFIG_SPECIALIX=m
< CONFIG_COMPUTONE=m
5406a5493
> CONFIG_COMEDI_DYNA_PCI10XX=m
5490,5493d5576
< CONFIG_SPECTRA=m
< # CONFIG_SPECTRA_MRST_HW is not set
< CONFIG_SPECTRA_MTD=y
< # CONFIG_SPECTRA_EMU is not set
5553a5637
> CONFIG_AD7793=m
5575a5660
> CONFIG_AD5686=m
5633,5635d5717
< # CONFIG_AD2S1210_GPIO_INPUT is not set
< # CONFIG_AD2S1210_GPIO_OUTPUT is not set
< CONFIG_AD2S1210_GPIO_NONE=y
5643d5724
< CONFIG_CS5535_GPIO=m
5651a5733
> CONFIG_DT3155_STREAMING=y
5668,5669d5749
< CONFIG_EASYCAP_SND=y
< # CONFIG_EASYCAP_OSS is not set
5673d5752
< CONFIG_MACH_NO_WESTBRIDGE=y
5698,5699d5776
< CONFIG_SND_INTEL_SST=m
< CONFIG_SND_INTELMID=m
5723,5726c5800,5802
< 
< #
< # Altera FPGA firmware download module
< #
---
> CONFIG_DRM_PSB_MRST=y
> CONFIG_DRM_PSB_MFLD=y
> CONFIG_DRM_PSB_CDV=y
5765,5770d5840
< CONFIG_INTEL_SCU_IPC=y
< CONFIG_INTEL_SCU_IPC_UTIL=y
< CONFIG_GPIO_INTEL_PMIC=y
< CONFIG_INTEL_MID_POWER_BUTTON=m
< CONFIG_INTEL_MFLD_THERMAL=m
< CONFIG_RAR_REGISTER=y
5777a5848
> CONFIG_SAMSUNG_Q10=m
5778a5850,5858
> CONFIG_CLKEVT_I8253=y
> CONFIG_I8253_LOCK=y
> CONFIG_CLKBLD_I8253=y
> CONFIG_IOMMU_API=y
> CONFIG_IOMMU_SUPPORT=y
> CONFIG_DMAR=y
> CONFIG_DMAR_DEFAULT_ON=y
> CONFIG_DMAR_FLOPPY_WA=y
> CONFIG_VIRT_DRIVERS=y
5952a6033
> CONFIG_SQUASHFS_ZLIB=y
5972a6054
> CONFIG_ORE=y
5982c6064,6065
< CONFIG_PNFS_OBJLAYOUT=y
---
> CONFIG_PNFS_BLOCK=m
> CONFIG_PNFS_OBJLAYOUT=m
5988d6070
< CONFIG_NFSD_DEPRECATED=y
5998a6081
> CONFIG_SUNRPC_BACKCHANNEL=y
6116,6117c6199,6214
< # CONFIG_DEBUG_KERNEL is not set
< # CONFIG_HARDLOCKUP_DETECTOR is not set
---
> CONFIG_DEBUG_KERNEL=y
> # CONFIG_DEBUG_SHIRQ is not set
> CONFIG_LOCKUP_DETECTOR=y
> CONFIG_HARDLOCKUP_DETECTOR=y
> # CONFIG_BOOTPARAM_HARDLOCKUP_PANIC is not set
> CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE=0
> # CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
> CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
> CONFIG_DETECT_HUNG_TASK=y
> CONFIG_DEFAULT_HUNG_TASK_TIMEOUT=120
> # CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
> CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
> # CONFIG_SCHED_DEBUG is not set
> # CONFIG_SCHEDSTATS is not set
> # CONFIG_TIMER_STATS is not set
> # CONFIG_DEBUG_OBJECTS is not set
6119a6217,6226
> CONFIG_DEBUG_KMEMLEAK=y
> CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE=400
> # CONFIG_DEBUG_KMEMLEAK_TEST is not set
> # CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF is not set
> # CONFIG_DEBUG_RT_MUTEXES is not set
> # CONFIG_RT_MUTEX_TESTER is not set
> # CONFIG_DEBUG_SPINLOCK is not set
> # CONFIG_DEBUG_MUTEXES is not set
> # CONFIG_DEBUG_LOCK_ALLOC is not set
> # CONFIG_PROVE_LOCKING is not set
6120a6228,6230
> # CONFIG_LOCK_STAT is not set
> # CONFIG_DEBUG_ATOMIC_SLEEP is not set
> # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
6121a6232,6234
> # CONFIG_DEBUG_STACK_USAGE is not set
> # CONFIG_DEBUG_KOBJECT is not set
> # CONFIG_DEBUG_HIGHMEM is not set
6122a6236,6239
> # CONFIG_DEBUG_INFO is not set
> # CONFIG_DEBUG_VM is not set
> # CONFIG_DEBUG_VIRTUAL is not set
> # CONFIG_DEBUG_WRITECOUNT is not set
6123a6241,6245
> # CONFIG_DEBUG_LIST is not set
> # CONFIG_TEST_LIST_SORT is not set
> # CONFIG_DEBUG_SG is not set
> # CONFIG_DEBUG_NOTIFIERS is not set
> # CONFIG_DEBUG_CREDENTIALS is not set
6125a6248,6249
> # CONFIG_BOOT_PRINTK_DELAY is not set
> # CONFIG_RCU_TORTURE_TEST is not set
6126a6251,6254
> # CONFIG_BACKTRACE_SELF_TEST is not set
> # CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
> # CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
> # CONFIG_DEBUG_PER_CPU_MAPS is not set
6127a6256,6258
> # CONFIG_CPU_NOTIFIER_ERROR_INJECT is not set
> # CONFIG_FAULT_INJECTION is not set
> # CONFIG_LATENCYTOP is not set
6128a6260
> # CONFIG_DEBUG_PAGEALLOC is not set
6171a6304
> # CONFIG_KGDB is not set
6177d6309
< CONFIG_EARLY_PRINTK_MRST=y
6178a6311,6314
> CONFIG_DEBUG_STACKOVERFLOW=y
> # CONFIG_X86_PTDUMP is not set
> CONFIG_DEBUG_RODATA=y
> CONFIG_DEBUG_RODATA_TEST=y
6179a6316
> # CONFIG_DEBUG_NX_TEST is not set
6191a6329,6330
> # CONFIG_DEBUG_BOOT_PARAMS is not set
> # CONFIG_CPA_DEBUG is not set
6192a6332
> # CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set
6349c6489
< # CONFIG_KVM_MMU_AUDIT is not set
---
> CONFIG_KVM_MMU_AUDIT=y
6352,6355d6491
< CONFIG_VIRTIO=y
< CONFIG_VIRTIO_RING=y
< CONFIG_VIRTIO_PCI=m
< CONFIG_VIRTIO_BALLOON=m
6370a6507
> CONFIG_CRC8=y
6406a6544,6545
> CONFIG_CORDIC=y
> CONFIG_LLIST=y

Re: 3.1-rc9 wifi problem

[Arend van Spriel]

On 10/15/2011 08:07 PM, werner wrote:
> A laptop of a friend, which worked always with wifi until 
> 3.0.4 , stopped to work when installing 3.1-rc9 , after 
> re-installing 3.0.4 wifi returned to work.  I think it was 
> a packard-bell laptop.   I can't test this better because 
> he gone with his laptop; perhaps next week he'll visit me 
> again. Since 2.6.38 his laptop worked with my wifi.
> 
> This can be a regression in the wifi drivers, or because 
> of a slightly changed config. Anyway the diff of config is 
> enclosed.
> 
> w.landgraf
> ---
> Professional hosting for everyone - http://www.host.ru

Hi Werner,

"wifi" is a bit too generic and "think it was a packard-bell" is vague
so not helping either. At least provide some basic info 1) uname -a, and
2) lspci -v. Or is the "wifi" a usb device? Also the 3.1.0-rc9 config
and not just the diff can help (which says 3.1.0-rc8?).

Gr. AvS

3.1-rc9 wifi problem

[werner]

I'm very sorry that I cannot give more informations, my 
own computer is connected with the modem via ethernet 
cable, a friend used in the past often wifi here at me, 
and since 2.6.38 never with problems, also with 3.0-rcX no 
problems, nor with 3.0.X until 3.0.4 .  There were 
 general problems with 3.1-rcX until 5 , which had nothing 
to do with wifi but what was the reason that I only late 
got working 3.1-rcX , so the first 3.1-rc the friend 
tested on his laptop was 3.1-rc9, and with this his wifi 
didn't work, but I don't know if it would have worked with 
-rc5. When he come back, perhaps next week , then I'll ask 
him to try 3.1-rc5 or 6 .   This is a kernel+modules 
problem, because with re-installing 3.0.4 it returned to 
work as before.  Anyway, I wanted to report this, so that 
before the release of 3.1 the wifi drivers could be 
checked better.

wl
---
Professional hosting for everyone - http://www.host.ru

Re: 3.1-rc9 wifi problem

[Larry Finger]

On 10/15/2011 04:43 PM, werner wrote:
> I'm very sorry that I cannot give more informations, my own computer is
> connected with the modem via ethernet cable, a friend used in the past often
> wifi here at me, and since 2.6.38 never with problems, also with 3.0-rcX no
> problems, nor with 3.0.X until 3.0.4 . There were general problems with 3.1-rcX
> until 5 , which had nothing to do with wifi but what was the reason that I only
> late got working 3.1-rcX , so the first 3.1-rc the friend tested on his laptop
> was 3.1-rc9, and with this his wifi didn't work, but I don't know if it would
> have worked with -rc5. When he come back, perhaps next week , then I'll ask him
> to try 3.1-rc5 or 6 . This is a kernel+modules problem, because with
> re-installing 3.0.4 it returned to work as before. Anyway, I wanted to report
> this, so that before the release of 3.1 the wifi drivers could be checked better.

Unless you say which driver is involved, we will n ot be able to help.

Larry

Re: 3.1-rc9 wifi problem

[werner]

I have to wait until the friend with the laptop comes 
back, perhaps this week. Then I can look what wireless 
card is in it.

However, now I remember me:  that laptop worked only good 
since 2.6.39 with the new kernel-embedded modules. 
  Before, it didn't work normally, i.e. on booting the 
wireless almost never didn't switch on; only ocasionally .


And, beside of kernel 2.6.39, and the normal wifi 
software, I still had him to install a file 
iwlwifi-1000-3.ucode or .5 ucode (i'm not sure, the number 
can also be 5000), and I had the problem to search long 
time for that file because one find only .2 or .4 in 
internet but what don't work at that wifi card.   You 
could improve the kernel-module so that everything is 
included so that one don't need to search such files.

Then, with this kernel and that file however, it worked 
without any problem.

I hope from these informations you can find out what wifi 
card or what driver is in the laptop.

W.Landgraf
---
Professional hosting for everyone - http://www.host.ru

Re: 3.1-rc9 wifi problem

[Larry Finger]

On 10/16/2011 08:33 PM, werner wrote:
> I have to wait until the friend with the laptop comes back, perhaps this week.
> Then I can look what wireless card is in it.
>
> However, now I remember me: that laptop worked only good since 2.6.39 with the
> new kernel-embedded modules. Before, it didn't work normally, i.e. on booting
> the wireless almost never didn't switch on; only ocasionally .
>
>
> And, beside of kernel 2.6.39, and the normal wifi software, I still had him to
> install a file iwlwifi-1000-3.ucode or .5 ucode (i'm not sure, the number can
> also be 5000), and I had the problem to search long time for that file because
> one find only .2 or .4 in internet but what don't work at that wifi card. You
> could improve the kernel-module so that everything is included so that one don't
> need to search such files.

That will not happen. In fact, the trend is from having firmware be a part of 
the driver to having it be external.

I don't know what distro you use, but mine (openSUSE) maintains a package called 
kernel-firmware that contains all the redistributable firmware that is available 
from tne linux-firmware git tree. If that package is installed, then you do not 
have to search for firmware in most cases. If your distro does not have such a 
package, then complain or find another distro.

> Then, with this kernel and that file however, it worked without any problem.
>
> I hope from these informations you can find out what wifi card or what driver is
> in the laptop.

We can tell that you have an Intel card, but not much more.

Larry

Re: 3.1-rc9 wifi problem

[Guy, Wey-Yi]

On Sun, 2011-10-16 at 19:16 -0700, Larry Finger wrote:
> On 10/16/2011 08:33 PM, werner wrote:
> > I have to wait until the friend with the laptop comes back, perhaps this week.
> > Then I can look what wireless card is in it.
> >
> > However, now I remember me: that laptop worked only good since 2.6.39 with the
> > new kernel-embedded modules. Before, it didn't work normally, i.e. on booting
> > the wireless almost never didn't switch on; only ocasionally .
> >
> >
> > And, beside of kernel 2.6.39, and the normal wifi software, I still had him to
> > install a file iwlwifi-1000-3.ucode or .5 ucode (i'm not sure, the number can
> > also be 5000), and I had the problem to search long time for that file because
> > one find only .2 or .4 in internet but what don't work at that wifi card. You
> > could improve the kernel-module so that everything is included so that one don't
> > need to search such files.
> 
> That will not happen. In fact, the trend is from having firmware be a part of 
> the driver to having it be external.
> 
> I don't know what distro you use, but mine (openSUSE) maintains a package called 
> kernel-firmware that contains all the redistributable firmware that is available 
> from tne linux-firmware git tree. If that package is installed, then you do not 
> have to search for firmware in most cases. If your distro does not have such a 
> package, then complain or find another distro.
> 
> > Then, with this kernel and that file however, it worked without any problem.
> >
> > I hope from these informations you can find out what wifi card or what driver is
> > in the laptop.
> 
> We can tell that you have an Intel card, but not much more.
> 
> Larry
> 

Not knowing much about what problem you  encounter, but you can find all
the latest intel WiFi firmware at
http://www.intellinuxwireless.org/?n=Downloads

Thanks
Wey