On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens <hauke@xxxxxxxxxx> wrote: > Bryan Wu wrote: >> Mauro Di Domenico wrote: >>> Hi, >>> I'm testing new b43 modules for my 14e4:4315 broadcom card. >>> I've compiled and installed compat-wireless-2009-09-16 in a debian >>> machine with kernel version 2.6.30-6. >>> >>> During the boot I experience this problem: >>> >>> $ dmesg|egrep "b43|ssb" >>> >>> [ 2.384463] b43-pci-bridge 0000:06:00.0: PCI INT A -> GSI 17 (level, >>> low) -> IRQ 17 >>> [ 2.384477] b43-pci-bridge 0000:06:00.0: setting latency timer to 64 >>> [ 2.544344] ssb: Sonics Silicon Backplane found on PCI device >>> 0000:06:00.0 >>> [ 6.968981] b43: disagrees about version of symbol >>> ssb_device_is_enabled >>> [ 6.968986] b43: Unknown symbol ssb_device_is_enabled >>> [ 6.969280] b43: Unknown symbol ssb_pmu_set_ldo_paref >>> [ 6.969407] b43: disagrees about version of symbol >>> ssb_pcicore_dev_irqvecs_enable >>> [ 6.969410] b43: Unknown symbol ssb_pcicore_dev_irqvecs_enable >>> ..... >>> .... >>> ... >>> >> >> I faced the exactly same issue as Mauro did. +1 from me, but currently have >> no time to take a deeper look. >> >> Thanks > Hi, > > I had the same problem with the ssb module and compat-wireless in ubuntu > 9.04. The problem is that the ssb module is integrated into the > initramfs image. The version out of the initramfs image is loaded on > startup and not the version of compat-wireless. Running "sudo > update-initramfs -u" after installing compat-wireless and restaing the > system fixes the problem for me. Either Debian/Ubuntu should remove ssb > form default initramfs image or compat-wireless should update the image > with the install command. At least the compat-wireless documentation > needs an update. > > Hauke > > (adding Luis and linux-wireless list) Tim, do you guys update the initramfs upon installation of lbm? If a user does not use lbm and uses compat-wireless I suppose we need to do something similar. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
