* Re: A problem loading ssb module [not found] ` <4ABBAB47.8040300@canonical.com> @ 2009-09-24 18:33 ` Hauke Mehrtens 2009-09-24 18:37 ` Luis R. Rodriguez 0 siblings, 1 reply; 16+ messages in thread From: Hauke Mehrtens @ 2009-09-24 18:33 UTC (permalink / raw) To: Bryan Wu Cc: Mauro Di Domenico, bcm43xx-dev, Luis R. Rodriguez, linux-wireless [-- Attachment #1: Type: text/plain, Size: 1742 bytes --] 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) [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 898 bytes --] ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: A problem loading ssb module 2009-09-24 18:33 ` A problem loading ssb module Hauke Mehrtens @ 2009-09-24 18:37 ` Luis R. Rodriguez 2009-09-25 0:04 ` Tim Gardner 2009-09-27 15:15 ` Clyde McPherson 0 siblings, 2 replies; 16+ messages in thread From: Luis R. Rodriguez @ 2009-09-24 18:37 UTC (permalink / raw) To: Hauke Mehrtens, Tim Gardner Cc: Bryan Wu, Mauro Di Domenico, bcm43xx-dev, linux-wireless On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens <hauke@hauke-m.de> 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 ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: A problem loading ssb module 2009-09-24 18:37 ` Luis R. Rodriguez @ 2009-09-25 0:04 ` Tim Gardner 2009-09-25 0:08 ` Luis R. Rodriguez 2009-09-27 15:15 ` Clyde McPherson 1 sibling, 1 reply; 16+ messages in thread From: Tim Gardner @ 2009-09-25 0:04 UTC (permalink / raw) To: Luis R. Rodriguez Cc: Hauke Mehrtens, Bryan Wu, Mauro Di Domenico, bcm43xx-dev, linux-wireless Luis R. Rodriguez wrote: > On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens <hauke@hauke-m.de> 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 No, initramfs is not updated when LBM is installed. I think maybe its a bug that ssb is in the initramfs modules list since AFAIK its not a boot essential device. Even in the netboot case, ssb/b44 should be in a udeb. rtg -- Tim Gardner tim.gardner@canonical.com ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: A problem loading ssb module 2009-09-25 0:04 ` Tim Gardner @ 2009-09-25 0:08 ` Luis R. Rodriguez 2009-09-25 0:14 ` Tim Gardner 0 siblings, 1 reply; 16+ messages in thread From: Luis R. Rodriguez @ 2009-09-25 0:08 UTC (permalink / raw) To: tim.gardner Cc: Hauke Mehrtens, Bryan Wu, Mauro Di Domenico, bcm43xx-dev, linux-wireless On Thu, Sep 24, 2009 at 5:04 PM, Tim Gardner <tim.gardner@canonical.com> wrote: > Luis R. Rodriguez wrote: >> >> On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens <hauke@hauke-m.de> 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 > > No, initramfs is not updated when LBM is installed. I think maybe its a bug > that ssb is in the initramfs modules list since AFAIK its not a boot > essential device. Even in the netboot case, ssb/b44 should be in a udeb. That would make life much easier. Luis ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: A problem loading ssb module 2009-09-25 0:08 ` Luis R. Rodriguez @ 2009-09-25 0:14 ` Tim Gardner 2009-09-25 0:53 ` Luis R. Rodriguez 2009-09-26 15:15 ` Hauke Mehrtens 0 siblings, 2 replies; 16+ messages in thread From: Tim Gardner @ 2009-09-25 0:14 UTC (permalink / raw) To: Luis R. Rodriguez Cc: Hauke Mehrtens, Bryan Wu, Mauro Di Domenico, bcm43xx-dev, linux-wireless Luis R. Rodriguez wrote: > On Thu, Sep 24, 2009 at 5:04 PM, Tim Gardner <tim.gardner@canonical.com> wrote: >> Luis R. Rodriguez wrote: >>> On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens <hauke@hauke-m.de> 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 >> No, initramfs is not updated when LBM is installed. I think maybe its a bug >> that ssb is in the initramfs modules list since AFAIK its not a boot >> essential device. Even in the netboot case, ssb/b44 should be in a udeb. > > That would make life much easier. > > Luis > I'm looking at the Karmic initramfs-tools package and am not seeing _any_ reference to ssb or b44. -- Tim Gardner tim.gardner@canonical.com ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: A problem loading ssb module 2009-09-25 0:14 ` Tim Gardner @ 2009-09-25 0:53 ` Luis R. Rodriguez 2009-09-26 15:15 ` Hauke Mehrtens 1 sibling, 0 replies; 16+ messages in thread From: Luis R. Rodriguez @ 2009-09-25 0:53 UTC (permalink / raw) To: tim.gardner Cc: Hauke Mehrtens, Bryan Wu, Mauro Di Domenico, bcm43xx-dev, linux-wireless On Thu, Sep 24, 2009 at 5:14 PM, Tim Gardner <tim.gardner@canonical.com> wrote: > Luis R. Rodriguez wrote: >> >> On Thu, Sep 24, 2009 at 5:04 PM, Tim Gardner <tim.gardner@canonical.com> >> wrote: >>> >>> Luis R. Rodriguez wrote: >>>> >>>> On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens <hauke@hauke-m.de> >>>> 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 >>> >>> No, initramfs is not updated when LBM is installed. I think maybe its a >>> bug >>> that ssb is in the initramfs modules list since AFAIK its not a boot >>> essential device. Even in the netboot case, ssb/b44 should be in a udeb. >> >> That would make life much easier. >> >> Luis >> > > I'm looking at the Karmic initramfs-tools package and am not seeing _any_ > reference to ssb or b44. Seems like a Debian 2.6.30-6 bug then. Luis ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: A problem loading ssb module 2009-09-25 0:14 ` Tim Gardner 2009-09-25 0:53 ` Luis R. Rodriguez @ 2009-09-26 15:15 ` Hauke Mehrtens 1 sibling, 0 replies; 16+ messages in thread From: Hauke Mehrtens @ 2009-09-26 15:15 UTC (permalink / raw) To: tim.gardner Cc: Luis R. Rodriguez, Bryan Wu, Mauro Di Domenico, bcm43xx-dev, linux-wireless [-- Attachment #1: Type: text/plain, Size: 3080 bytes --] Tim Gardner wrote: > Luis R. Rodriguez wrote: >> On Thu, Sep 24, 2009 at 5:04 PM, Tim Gardner >> <tim.gardner@canonical.com> wrote: >>> Luis R. Rodriguez wrote: >>>> On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens <hauke@hauke-m.de> >>>> 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 >>> No, initramfs is not updated when LBM is installed. I think maybe its >>> a bug >>> that ssb is in the initramfs modules list since AFAIK its not a boot >>> essential device. Even in the netboot case, ssb/b44 should be in a udeb. >> >> That would make life much easier. >> >> Luis >> > > I'm looking at the Karmic initramfs-tools package and am not seeing > _any_ reference to ssb or b44. > Hi Tim, I have decompressed initrd.img-2.6.31-11-generic from karmic and initrd.img-2.6.28-15-generic form jaunty. In both packages I found the ssb.ko and b44.ko module. Hauke [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 898 bytes --] ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: A problem loading ssb module 2009-09-24 18:37 ` Luis R. Rodriguez 2009-09-25 0:04 ` Tim Gardner @ 2009-09-27 15:15 ` Clyde McPherson 2009-09-27 19:50 ` Luis R. Rodriguez 1 sibling, 1 reply; 16+ messages in thread From: Clyde McPherson @ 2009-09-27 15:15 UTC (permalink / raw) To: Luis R. Rodriguez Cc: Hauke Mehrtens, Tim Gardner, linux-wireless, bcm43xx-dev > On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens <hauke@hauke-m.de> 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 > _______________________________________________ > Bcm43xx-dev mailing list > Bcm43xx-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > All: I have a large group that uses the ssb module along with the Broadcom 4318, in a CF form factor. If the CF card is inserted before boot, and the ssb module is not in the initrd process, the laptops lock up and do not become operational. The solution to this problem is/was adding the ssb.ko to the initrd process. So I agree with Luis on this, the ssb module will have to be added/updated to the initrd process. As for PCI operations, I don't know, but for PCMCIA operations ssb.ko has to be added and/or updated. Anytime I am testing new releases of b43, I run "update-initramfs -u" to update the ssb module. (Sometimes you can do a rmmod ssb and rmmod b43, and then modprobe them back in. - This saves a reboot) Thanks -Tex ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: A problem loading ssb module 2009-09-27 15:15 ` Clyde McPherson @ 2009-09-27 19:50 ` Luis R. Rodriguez 2009-09-27 21:02 ` Luis R. Rodriguez 0 siblings, 1 reply; 16+ messages in thread From: Luis R. Rodriguez @ 2009-09-27 19:50 UTC (permalink / raw) To: Clyde McPherson; +Cc: Hauke Mehrtens, Tim Gardner, linux-wireless, bcm43xx-dev On Sun, Sep 27, 2009 at 8:15 AM, Clyde McPherson <ccmcphe@verizon.net> wrote: > > >> On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens <hauke@hauke-m.de> 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 >> _______________________________________________ >> Bcm43xx-dev mailing list >> Bcm43xx-dev@lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/bcm43xx-dev >> > > All: > I have a large group that uses the ssb module along with the Broadcom 4318, > in a CF form factor. If the CF card is inserted before boot, and the ssb > module is not in the initrd process, the laptops lock up and do not become > operational. The solution to this problem is/was adding the ssb.ko to the > initrd process. So I agree with Luis on this, the ssb module will have to be > added/updated to the initrd process. As for PCI operations, I don't know, > but for PCMCIA operations ssb.ko has to be added and/or updated. Anytime I > am testing new releases of b43, I run "update-initramfs -u" to update the > ssb module. (Sometimes you can do a rmmod ssb and rmmod b43, and then > modprobe them back in. - This saves a reboot) But why is ssb, b43, b44 needed upon early boot? Luis ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: A problem loading ssb module 2009-09-27 19:50 ` Luis R. Rodriguez @ 2009-09-27 21:02 ` Luis R. Rodriguez 2009-09-28 19:55 ` Luis R. Rodriguez 2009-09-28 20:00 ` Tim Gardner 0 siblings, 2 replies; 16+ messages in thread From: Luis R. Rodriguez @ 2009-09-27 21:02 UTC (permalink / raw) To: Luis R. Rodriguez Cc: Clyde McPherson, Hauke Mehrtens, Tim Gardner, linux-wireless, bcm43xx-dev [-- Attachment #1: Type: text/plain, Size: 6239 bytes --] On Sun, Sep 27, 2009 at 12:50:19PM -0700, Luis R. Rodriguez wrote: > On Sun, Sep 27, 2009 at 8:15 AM, Clyde McPherson <ccmcphe@verizon.net> wrote: > > > > > >> On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens <hauke@hauke-m.de> 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 > >> _______________________________________________ > >> Bcm43xx-dev mailing list > >> Bcm43xx-dev@lists.berlios.de > >> https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > >> > > > > All: > > I have a large group that uses the ssb module along with the Broadcom 4318, > > in a CF form factor. If the CF card is inserted before boot, and the ssb > > module is not in the initrd process, the laptops lock up and do not become > > operational. The solution to this problem is/was adding the ssb.ko to the > > initrd process. So I agree with Luis on this, the ssb module will have to be > > added/updated to the initrd process. As for PCI operations, I don't know, > > but for PCMCIA operations ssb.ko has to be added and/or updated. Anytime I > > am testing new releases of b43, I run "update-initramfs -u" to update the > > ssb module. (Sometimes you can do a rmmod ssb and rmmod b43, and then > > modprobe them back in. - This saves a reboot) > > But why is ssb, b43, b44 needed upon early boot? OK the reason seems to be netboot. Yeah the only fix for distros who want this on the initramfs is to update it after a compat-wireless package is installed. I suppose we can add a hook to compat-wireless for each distro. I'm only familiar with Ubuntu way of doing this so if people are interested in other distros you'll need to point/test how to do this on there. Please try this patch against compat-wireless: (also attached) >From 99af88246c2de71aa799de2b63f9d9ccac41634f Mon Sep 17 00:00:00 2001 From: Luis R. Rodriguez <lrodriguez@atheros.com> Date: Sun, 27 Sep 2009 13:58:22 -0700 Subject: [PATCH] Add scripts/update-initramfs and use it Some distributions may ship b44 and ssb on the initramfs for netboot. To help with this we need to update the initrafms for those distributions. Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com> --- Makefile | 1 + scripts/update-initramfs | 33 +++++++++++++++++++++++++++++++++ 2 files changed, 34 insertions(+), 0 deletions(-) create mode 100755 scripts/update-initramfs diff --git a/Makefile b/Makefile index ab97de0..c7333a2 100644 --- a/Makefile +++ b/Makefile @@ -65,6 +65,7 @@ install: uninstall install-modules install-scripts install-modules: modules $(MAKE) -C $(KLIB_BUILD) M=$(PWD) $(KMODDIR_ARG) $(KMODPATH_ARG) \ modules_install + @./scripts/update-initramfs install-scripts: @# All the scripts we can use diff --git a/scripts/update-initramfs b/scripts/update-initramfs new file mode 100755 index 0000000..412d885 --- /dev/null +++ b/scripts/update-initramfs @@ -0,0 +1,33 @@ +#!/bin/bash +# Copyright 2009 Luis R. Rodriguez <mcgrof@gmail.com> +# +# Since we provide ssb, the Ethernet module b44 some people may +# rely on it to netboot, so update the initrafms for each +# distribution. +# +# Note that in the future people may want to wireless-boot +# so this will help with that as well. + +LSB_RED_ID=$(/usr/bin/lsb_release -i -s) + +KLIB=/lib/modules/2.6.31-wl/build +ver=$(echo $KLIB | awk -F "/lib/modules/" '{print $2}' | awk -F"/" '{print $1}') +dir=/boot/ + +case $LSB_RED_ID in +"Ubuntu") + echo "Updating Ubuntu's initramfs for $ver under $dir ..." + mkinitramfs -o $dir/initrd.img-$ver $ver + echo "Will now run update-grub to ensure grub will find the new initramfs ..." + update-grub + ;; +*) + echo "Warning:" + echo "You may or may not need to update your initframfs, you should if" + echo "any of the modules installed are part of your initramfs. To add" + echo "support for your distribution to do this automatically send a" + echo "patch against $0. If your distribution does not require this" + echo "send a patch against the '/usr/bin/lsb_release -i -s': $LSB_RED_ID" + echo "tag for your distribution to avoid this warning." + ;; +esac -- 1.6.3.3 [-- Attachment #2: add-update-initrafms.patch --] [-- Type: text/plain, Size: 2363 bytes --] >From 99af88246c2de71aa799de2b63f9d9ccac41634f Mon Sep 17 00:00:00 2001 From: Luis R. Rodriguez <lrodriguez@atheros.com> Date: Sun, 27 Sep 2009 13:58:22 -0700 Subject: [PATCH] Add scripts/update-initramfs and use it Some distributions may ship b44 and ssb on the initramfs for netboot. To help with this we need to update the initrafms for those distributions. Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com> --- Makefile | 1 + scripts/update-initramfs | 33 +++++++++++++++++++++++++++++++++ 2 files changed, 34 insertions(+), 0 deletions(-) create mode 100755 scripts/update-initramfs diff --git a/Makefile b/Makefile index ab97de0..c7333a2 100644 --- a/Makefile +++ b/Makefile @@ -65,6 +65,7 @@ install: uninstall install-modules install-scripts install-modules: modules $(MAKE) -C $(KLIB_BUILD) M=$(PWD) $(KMODDIR_ARG) $(KMODPATH_ARG) \ modules_install + @./scripts/update-initramfs install-scripts: @# All the scripts we can use diff --git a/scripts/update-initramfs b/scripts/update-initramfs new file mode 100755 index 0000000..412d885 --- /dev/null +++ b/scripts/update-initramfs @@ -0,0 +1,33 @@ +#!/bin/bash +# Copyright 2009 Luis R. Rodriguez <mcgrof@gmail.com> +# +# Since we provide ssb, the Ethernet module b44 some people may +# rely on it to netboot, so update the initrafms for each +# distribution. +# +# Note that in the future people may want to wireless-boot +# so this will help with that as well. + +LSB_RED_ID=$(/usr/bin/lsb_release -i -s) + +KLIB=/lib/modules/2.6.31-wl/build +ver=$(echo $KLIB | awk -F "/lib/modules/" '{print $2}' | awk -F"/" '{print $1}') +dir=/boot/ + +case $LSB_RED_ID in +"Ubuntu") + echo "Updating Ubuntu's initramfs for $ver under $dir ..." + mkinitramfs -o $dir/initrd.img-$ver $ver + echo "Will now run update-grub to ensure grub will find the new initramfs ..." + update-grub + ;; +*) + echo "Warning:" + echo "You may or may not need to update your initframfs, you should if" + echo "any of the modules installed are part of your initramfs. To add" + echo "support for your distribution to do this automatically send a" + echo "patch against $0. If your distribution does not require this" + echo "send a patch against the '/usr/bin/lsb_release -i -s': $LSB_RED_ID" + echo "tag for your distribution to avoid this warning." + ;; +esac -- 1.6.3.3 ^ permalink raw reply related [flat|nested] 16+ messages in thread
* Re: A problem loading ssb module 2009-09-27 21:02 ` Luis R. Rodriguez @ 2009-09-28 19:55 ` Luis R. Rodriguez 2009-09-28 20:00 ` Tim Gardner 1 sibling, 0 replies; 16+ messages in thread From: Luis R. Rodriguez @ 2009-09-28 19:55 UTC (permalink / raw) To: Luis R. Rodriguez Cc: Clyde McPherson, Hauke Mehrtens, Tim Gardner, linux-wireless, bcm43xx-dev On Sun, Sep 27, 2009 at 2:02 PM, Luis R. Rodriguez <mcgrof@bombadil.infradead.org> wrote: > On Sun, Sep 27, 2009 at 12:50:19PM -0700, Luis R. Rodriguez wrote: >> On Sun, Sep 27, 2009 at 8:15 AM, Clyde McPherson <ccmcphe@verizon.net> wrote: >> > >> > >> >> On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens <hauke@hauke-m.de> 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 >> >> _______________________________________________ >> >> Bcm43xx-dev mailing list >> >> Bcm43xx-dev@lists.berlios.de >> >> https://lists.berlios.de/mailman/listinfo/bcm43xx-dev >> >> >> > >> > All: >> > I have a large group that uses the ssb module along with the Broadcom 4318, >> > in a CF form factor. If the CF card is inserted before boot, and the ssb >> > module is not in the initrd process, the laptops lock up and do not become >> > operational. The solution to this problem is/was adding the ssb.ko to the >> > initrd process. So I agree with Luis on this, the ssb module will have to be >> > added/updated to the initrd process. As for PCI operations, I don't know, >> > but for PCMCIA operations ssb.ko has to be added and/or updated. Anytime I >> > am testing new releases of b43, I run "update-initramfs -u" to update the >> > ssb module. (Sometimes you can do a rmmod ssb and rmmod b43, and then >> > modprobe them back in. - This saves a reboot) >> >> But why is ssb, b43, b44 needed upon early boot? > > OK the reason seems to be netboot. Yeah the only fix for distros who want > this on the initramfs is to update it after a compat-wireless package is > installed. I suppose we can add a hook to compat-wireless for each distro. > I'm only familiar with Ubuntu way of doing this so if people are interested > in other distros you'll need to point/test how to do this on there. > > Please try this patch against compat-wireless: (also attached) > > From 99af88246c2de71aa799de2b63f9d9ccac41634f Mon Sep 17 00:00:00 2001 > From: Luis R. Rodriguez <lrodriguez@atheros.com> > Date: Sun, 27 Sep 2009 13:58:22 -0700 > Subject: [PATCH] Add scripts/update-initramfs and use it > > Some distributions may ship b44 and ssb on the initramfs for > netboot. To help with this we need to update the initrafms > for those distributions. > > Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com> I didn't see much feedback but I'm going to merge this in so that it gets out with the 2.6.32-rc1 stable compat-wireless release. Luis ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: A problem loading ssb module 2009-09-27 21:02 ` Luis R. Rodriguez 2009-09-28 19:55 ` Luis R. Rodriguez @ 2009-09-28 20:00 ` Tim Gardner 2009-09-28 20:07 ` Luis R. Rodriguez 1 sibling, 1 reply; 16+ messages in thread From: Tim Gardner @ 2009-09-28 20:00 UTC (permalink / raw) To: Luis R. Rodriguez Cc: Luis R. Rodriguez, Clyde McPherson, Hauke Mehrtens, linux-wireless, bcm43xx-dev Luis R. Rodriguez wrote: > On Sun, Sep 27, 2009 at 12:50:19PM -0700, Luis R. Rodriguez wrote: >> On Sun, Sep 27, 2009 at 8:15 AM, Clyde McPherson <ccmcphe@verizon.net> wrote: >>> >>>> On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens <hauke@hauke-m.de> 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 >>>> _______________________________________________ >>>> Bcm43xx-dev mailing list >>>> Bcm43xx-dev@lists.berlios.de >>>> https://lists.berlios.de/mailman/listinfo/bcm43xx-dev >>>> >>> All: >>> I have a large group that uses the ssb module along with the Broadcom 4318, >>> in a CF form factor. If the CF card is inserted before boot, and the ssb >>> module is not in the initrd process, the laptops lock up and do not become >>> operational. The solution to this problem is/was adding the ssb.ko to the >>> initrd process. So I agree with Luis on this, the ssb module will have to be >>> added/updated to the initrd process. As for PCI operations, I don't know, >>> but for PCMCIA operations ssb.ko has to be added and/or updated. Anytime I >>> am testing new releases of b43, I run "update-initramfs -u" to update the >>> ssb module. (Sometimes you can do a rmmod ssb and rmmod b43, and then >>> modprobe them back in. - This saves a reboot) >> But why is ssb, b43, b44 needed upon early boot? > > OK the reason seems to be netboot. Yeah the only fix for distros who want > this on the initramfs is to update it after a compat-wireless package is > installed. I suppose we can add a hook to compat-wireless for each distro. > I'm only familiar with Ubuntu way of doing this so if people are interested > in other distros you'll need to point/test how to do this on there. > > Please try this patch against compat-wireless: (also attached) > > From 99af88246c2de71aa799de2b63f9d9ccac41634f Mon Sep 17 00:00:00 2001 > From: Luis R. Rodriguez <lrodriguez@atheros.com> > Date: Sun, 27 Sep 2009 13:58:22 -0700 > Subject: [PATCH] Add scripts/update-initramfs and use it > > Some distributions may ship b44 and ssb on the initramfs for > netboot. To help with this we need to update the initrafms > for those distributions. > > Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com> > --- > Makefile | 1 + > scripts/update-initramfs | 33 +++++++++++++++++++++++++++++++++ > 2 files changed, 34 insertions(+), 0 deletions(-) > create mode 100755 scripts/update-initramfs > > diff --git a/Makefile b/Makefile > index ab97de0..c7333a2 100644 > --- a/Makefile > +++ b/Makefile > @@ -65,6 +65,7 @@ install: uninstall install-modules install-scripts > install-modules: modules > $(MAKE) -C $(KLIB_BUILD) M=$(PWD) $(KMODDIR_ARG) $(KMODPATH_ARG) \ > modules_install > + @./scripts/update-initramfs > > install-scripts: > @# All the scripts we can use > diff --git a/scripts/update-initramfs b/scripts/update-initramfs > new file mode 100755 > index 0000000..412d885 > --- /dev/null > +++ b/scripts/update-initramfs > @@ -0,0 +1,33 @@ > +#!/bin/bash > +# Copyright 2009 Luis R. Rodriguez <mcgrof@gmail.com> > +# > +# Since we provide ssb, the Ethernet module b44 some people may > +# rely on it to netboot, so update the initrafms for each > +# distribution. > +# > +# Note that in the future people may want to wireless-boot > +# so this will help with that as well. > + > +LSB_RED_ID=$(/usr/bin/lsb_release -i -s) > + > +KLIB=/lib/modules/2.6.31-wl/build > +ver=$(echo $KLIB | awk -F "/lib/modules/" '{print $2}' | awk -F"/" '{print $1}') > +dir=/boot/ > + > +case $LSB_RED_ID in > +"Ubuntu") > + echo "Updating Ubuntu's initramfs for $ver under $dir ..." > + mkinitramfs -o $dir/initrd.img-$ver $ver > + echo "Will now run update-grub to ensure grub will find the new initramfs ..." > + update-grub > + ;; > +*) > + echo "Warning:" > + echo "You may or may not need to update your initframfs, you should if" > + echo "any of the modules installed are part of your initramfs. To add" > + echo "support for your distribution to do this automatically send a" > + echo "patch against $0. If your distribution does not require this" > + echo "send a patch against the '/usr/bin/lsb_release -i -s': $LSB_RED_ID" > + echo "tag for your distribution to avoid this warning." > + ;; > +esac > Luis - I'll do something similar in a post install script for Karmic LBM since the install-modules target in your makefile isn't used for a debian install. rtg -- Tim Gardner tim.gardner@canonical.com ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: A problem loading ssb module 2009-09-28 20:00 ` Tim Gardner @ 2009-09-28 20:07 ` Luis R. Rodriguez 2009-09-28 20:38 ` Tim Gardner 0 siblings, 1 reply; 16+ messages in thread From: Luis R. Rodriguez @ 2009-09-28 20:07 UTC (permalink / raw) To: Tim Gardner Cc: Luis R. Rodriguez, Luis Rodriguez, Clyde McPherson, Hauke Mehrtens, linux-wireless, bcm43xx-dev@lists.berlios.de On Mon, Sep 28, 2009 at 01:00:55PM -0700, Tim Gardner wrote: > Luis R. Rodriguez wrote: > > On Sun, Sep 27, 2009 at 12:50:19PM -0700, Luis R. Rodriguez wrote: > >> On Sun, Sep 27, 2009 at 8:15 AM, Clyde McPherson <ccmcphe@verizon.net> wrote: > >>> > >>>> On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens <hauke@hauke-m.de> 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 > >>>> _______________________________________________ > >>>> Bcm43xx-dev mailing list > >>>> Bcm43xx-dev@lists.berlios.de > >>>> https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > >>>> > >>> All: > >>> I have a large group that uses the ssb module along with the Broadcom 4318, > >>> in a CF form factor. If the CF card is inserted before boot, and the ssb > >>> module is not in the initrd process, the laptops lock up and do not become > >>> operational. The solution to this problem is/was adding the ssb.ko to the > >>> initrd process. So I agree with Luis on this, the ssb module will have to be > >>> added/updated to the initrd process. As for PCI operations, I don't know, > >>> but for PCMCIA operations ssb.ko has to be added and/or updated. Anytime I > >>> am testing new releases of b43, I run "update-initramfs -u" to update the > >>> ssb module. (Sometimes you can do a rmmod ssb and rmmod b43, and then > >>> modprobe them back in. - This saves a reboot) > >> But why is ssb, b43, b44 needed upon early boot? > > > > OK the reason seems to be netboot. Yeah the only fix for distros who want > > this on the initramfs is to update it after a compat-wireless package is > > installed. I suppose we can add a hook to compat-wireless for each distro. > > I'm only familiar with Ubuntu way of doing this so if people are interested > > in other distros you'll need to point/test how to do this on there. > > > > Please try this patch against compat-wireless: (also attached) > > > > From 99af88246c2de71aa799de2b63f9d9ccac41634f Mon Sep 17 00:00:00 2001 > > From: Luis R. Rodriguez <lrodriguez@atheros.com> > > Date: Sun, 27 Sep 2009 13:58:22 -0700 > > Subject: [PATCH] Add scripts/update-initramfs and use it > > > > Some distributions may ship b44 and ssb on the initramfs for > > netboot. To help with this we need to update the initrafms > > for those distributions. > > > > Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com> > > --- > > Makefile | 1 + > > scripts/update-initramfs | 33 +++++++++++++++++++++++++++++++++ > > 2 files changed, 34 insertions(+), 0 deletions(-) > > create mode 100755 scripts/update-initramfs > > > > diff --git a/Makefile b/Makefile > > index ab97de0..c7333a2 100644 > > --- a/Makefile > > +++ b/Makefile > > @@ -65,6 +65,7 @@ install: uninstall install-modules install-scripts > > install-modules: modules > > $(MAKE) -C $(KLIB_BUILD) M=$(PWD) $(KMODDIR_ARG) $(KMODPATH_ARG) \ > > modules_install > > + @./scripts/update-initramfs > > > > install-scripts: > > @# All the scripts we can use > > diff --git a/scripts/update-initramfs b/scripts/update-initramfs > > new file mode 100755 > > index 0000000..412d885 > > --- /dev/null > > +++ b/scripts/update-initramfs > > @@ -0,0 +1,33 @@ > > +#!/bin/bash > > +# Copyright 2009 Luis R. Rodriguez <mcgrof@gmail.com> > > +# > > +# Since we provide ssb, the Ethernet module b44 some people may > > +# rely on it to netboot, so update the initrafms for each > > +# distribution. > > +# > > +# Note that in the future people may want to wireless-boot > > +# so this will help with that as well. > > + > > +LSB_RED_ID=$(/usr/bin/lsb_release -i -s) > > + > > +KLIB=/lib/modules/2.6.31-wl/build > > +ver=$(echo $KLIB | awk -F "/lib/modules/" '{print $2}' | awk -F"/" '{print $1}') > > +dir=/boot/ > > + > > +case $LSB_RED_ID in > > +"Ubuntu") > > + echo "Updating Ubuntu's initramfs for $ver under $dir ..." > > + mkinitramfs -o $dir/initrd.img-$ver $ver > > + echo "Will now run update-grub to ensure grub will find the new initramfs ..." > > + update-grub > > + ;; > > +*) > > + echo "Warning:" > > + echo "You may or may not need to update your initframfs, you should if" > > + echo "any of the modules installed are part of your initramfs. To add" > > + echo "support for your distribution to do this automatically send a" > > + echo "patch against $0. If your distribution does not require this" > > + echo "send a patch against the '/usr/bin/lsb_release -i -s': $LSB_RED_ID" > > + echo "tag for your distribution to avoid this warning." > > + ;; > > +esac > > > > Luis - I'll do something similar in a post install script for Karmic LBM Great, thanks for the heads up. > since the install-modules target in your makefile isn't used for a > debian install. Not sure I followed this part, what do you mean? Luis ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: A problem loading ssb module 2009-09-28 20:07 ` Luis R. Rodriguez @ 2009-09-28 20:38 ` Tim Gardner 2009-09-28 21:00 ` Luis R. Rodriguez 0 siblings, 1 reply; 16+ messages in thread From: Tim Gardner @ 2009-09-28 20:38 UTC (permalink / raw) To: Luis R. Rodriguez Cc: Luis R. Rodriguez, Luis Rodriguez, Clyde McPherson, Hauke Mehrtens, linux-wireless, bcm43xx-dev@lists.berlios.de Luis R. Rodriguez wrote: > On Mon, Sep 28, 2009 at 01:00:55PM -0700, Tim Gardner wrote: >> Luis R. Rodriguez wrote: >>> On Sun, Sep 27, 2009 at 12:50:19PM -0700, Luis R. Rodriguez wrote: >>>> On Sun, Sep 27, 2009 at 8:15 AM, Clyde McPherson <ccmcphe@verizon.net> wrote: >>>>>> On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens <hauke@hauke-m.de> 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 >>>>>> _______________________________________________ >>>>>> Bcm43xx-dev mailing list >>>>>> Bcm43xx-dev@lists.berlios.de >>>>>> https://lists.berlios.de/mailman/listinfo/bcm43xx-dev >>>>>> >>>>> All: >>>>> I have a large group that uses the ssb module along with the Broadcom 4318, >>>>> in a CF form factor. If the CF card is inserted before boot, and the ssb >>>>> module is not in the initrd process, the laptops lock up and do not become >>>>> operational. The solution to this problem is/was adding the ssb.ko to the >>>>> initrd process. So I agree with Luis on this, the ssb module will have to be >>>>> added/updated to the initrd process. As for PCI operations, I don't know, >>>>> but for PCMCIA operations ssb.ko has to be added and/or updated. Anytime I >>>>> am testing new releases of b43, I run "update-initramfs -u" to update the >>>>> ssb module. (Sometimes you can do a rmmod ssb and rmmod b43, and then >>>>> modprobe them back in. - This saves a reboot) >>>> But why is ssb, b43, b44 needed upon early boot? >>> OK the reason seems to be netboot. Yeah the only fix for distros who want >>> this on the initramfs is to update it after a compat-wireless package is >>> installed. I suppose we can add a hook to compat-wireless for each distro. >>> I'm only familiar with Ubuntu way of doing this so if people are interested >>> in other distros you'll need to point/test how to do this on there. >>> >>> Please try this patch against compat-wireless: (also attached) >>> >>> From 99af88246c2de71aa799de2b63f9d9ccac41634f Mon Sep 17 00:00:00 2001 >>> From: Luis R. Rodriguez <lrodriguez@atheros.com> >>> Date: Sun, 27 Sep 2009 13:58:22 -0700 >>> Subject: [PATCH] Add scripts/update-initramfs and use it >>> >>> Some distributions may ship b44 and ssb on the initramfs for >>> netboot. To help with this we need to update the initrafms >>> for those distributions. >>> >>> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com> >>> --- >>> Makefile | 1 + >>> scripts/update-initramfs | 33 +++++++++++++++++++++++++++++++++ >>> 2 files changed, 34 insertions(+), 0 deletions(-) >>> create mode 100755 scripts/update-initramfs >>> >>> diff --git a/Makefile b/Makefile >>> index ab97de0..c7333a2 100644 >>> --- a/Makefile >>> +++ b/Makefile >>> @@ -65,6 +65,7 @@ install: uninstall install-modules install-scripts >>> install-modules: modules >>> $(MAKE) -C $(KLIB_BUILD) M=$(PWD) $(KMODDIR_ARG) $(KMODPATH_ARG) \ >>> modules_install >>> + @./scripts/update-initramfs >>> >>> install-scripts: >>> @# All the scripts we can use >>> diff --git a/scripts/update-initramfs b/scripts/update-initramfs >>> new file mode 100755 >>> index 0000000..412d885 >>> --- /dev/null >>> +++ b/scripts/update-initramfs >>> @@ -0,0 +1,33 @@ >>> +#!/bin/bash >>> +# Copyright 2009 Luis R. Rodriguez <mcgrof@gmail.com> >>> +# >>> +# Since we provide ssb, the Ethernet module b44 some people may >>> +# rely on it to netboot, so update the initrafms for each >>> +# distribution. >>> +# >>> +# Note that in the future people may want to wireless-boot >>> +# so this will help with that as well. >>> + >>> +LSB_RED_ID=$(/usr/bin/lsb_release -i -s) >>> + >>> +KLIB=/lib/modules/2.6.31-wl/build >>> +ver=$(echo $KLIB | awk -F "/lib/modules/" '{print $2}' | awk -F"/" '{print $1}') >>> +dir=/boot/ >>> + >>> +case $LSB_RED_ID in >>> +"Ubuntu") >>> + echo "Updating Ubuntu's initramfs for $ver under $dir ..." >>> + mkinitramfs -o $dir/initrd.img-$ver $ver >>> + echo "Will now run update-grub to ensure grub will find the new initramfs ..." >>> + update-grub >>> + ;; >>> +*) >>> + echo "Warning:" >>> + echo "You may or may not need to update your initframfs, you should if" >>> + echo "any of the modules installed are part of your initramfs. To add" >>> + echo "support for your distribution to do this automatically send a" >>> + echo "patch against $0. If your distribution does not require this" >>> + echo "send a patch against the '/usr/bin/lsb_release -i -s': $LSB_RED_ID" >>> + echo "tag for your distribution to avoid this warning." >>> + ;; >>> +esac >>> >> Luis - I'll do something similar in a post install script for Karmic LBM > > Great, thanks for the heads up. > >> since the install-modules target in your makefile isn't used for a >> debian install. > > Not sure I followed this part, what do you mean? > It has to do with the way debian packages are installed. In the case of LBM, the .ko files from the binary package are simply copied to their target locations during 'apt-get install'. Therefore, a post installation script needs to be run that updates the initramfs. rtg -- Tim Gardner tim.gardner@canonical.com ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: A problem loading ssb module 2009-09-28 20:38 ` Tim Gardner @ 2009-09-28 21:00 ` Luis R. Rodriguez 2009-09-30 16:59 ` Tim Gardner 0 siblings, 1 reply; 16+ messages in thread From: Luis R. Rodriguez @ 2009-09-28 21:00 UTC (permalink / raw) To: Tim Gardner Cc: Luis Rodriguez, Luis R. Rodriguez, Clyde McPherson, Hauke Mehrtens, linux-wireless, bcm43xx-dev@lists.berlios.de On Mon, Sep 28, 2009 at 01:38:46PM -0700, Tim Gardner wrote: > Luis R. Rodriguez wrote: > > On Mon, Sep 28, 2009 at 01:00:55PM -0700, Tim Gardner wrote: > >> Luis R. Rodriguez wrote: > >>> On Sun, Sep 27, 2009 at 12:50:19PM -0700, Luis R. Rodriguez wrote: > >>>> On Sun, Sep 27, 2009 at 8:15 AM, Clyde McPherson <ccmcphe@verizon.net> wrote: > >>>>>> On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens <hauke@hauke-m.de> 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 > >>>>>> _______________________________________________ > >>>>>> Bcm43xx-dev mailing list > >>>>>> Bcm43xx-dev@lists.berlios.de > >>>>>> https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > >>>>>> > >>>>> All: > >>>>> I have a large group that uses the ssb module along with the Broadcom 4318, > >>>>> in a CF form factor. If the CF card is inserted before boot, and the ssb > >>>>> module is not in the initrd process, the laptops lock up and do not become > >>>>> operational. The solution to this problem is/was adding the ssb.ko to the > >>>>> initrd process. So I agree with Luis on this, the ssb module will have to be > >>>>> added/updated to the initrd process. As for PCI operations, I don't know, > >>>>> but for PCMCIA operations ssb.ko has to be added and/or updated. Anytime I > >>>>> am testing new releases of b43, I run "update-initramfs -u" to update the > >>>>> ssb module. (Sometimes you can do a rmmod ssb and rmmod b43, and then > >>>>> modprobe them back in. - This saves a reboot) > >>>> But why is ssb, b43, b44 needed upon early boot? > >>> OK the reason seems to be netboot. Yeah the only fix for distros who want > >>> this on the initramfs is to update it after a compat-wireless package is > >>> installed. I suppose we can add a hook to compat-wireless for each distro. > >>> I'm only familiar with Ubuntu way of doing this so if people are interested > >>> in other distros you'll need to point/test how to do this on there. > >>> > >>> Please try this patch against compat-wireless: (also attached) > >>> > >>> From 99af88246c2de71aa799de2b63f9d9ccac41634f Mon Sep 17 00:00:00 2001 > >>> From: Luis R. Rodriguez <lrodriguez@atheros.com> > >>> Date: Sun, 27 Sep 2009 13:58:22 -0700 > >>> Subject: [PATCH] Add scripts/update-initramfs and use it > >>> > >>> Some distributions may ship b44 and ssb on the initramfs for > >>> netboot. To help with this we need to update the initrafms > >>> for those distributions. > >>> > >>> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com> > >>> --- > >>> Makefile | 1 + > >>> scripts/update-initramfs | 33 +++++++++++++++++++++++++++++++++ > >>> 2 files changed, 34 insertions(+), 0 deletions(-) > >>> create mode 100755 scripts/update-initramfs > >>> > >>> diff --git a/Makefile b/Makefile > >>> index ab97de0..c7333a2 100644 > >>> --- a/Makefile > >>> +++ b/Makefile > >>> @@ -65,6 +65,7 @@ install: uninstall install-modules install-scripts > >>> install-modules: modules > >>> $(MAKE) -C $(KLIB_BUILD) M=$(PWD) $(KMODDIR_ARG) $(KMODPATH_ARG) \ > >>> modules_install > >>> + @./scripts/update-initramfs > >>> > >>> install-scripts: > >>> @# All the scripts we can use > >>> diff --git a/scripts/update-initramfs b/scripts/update-initramfs > >>> new file mode 100755 > >>> index 0000000..412d885 > >>> --- /dev/null > >>> +++ b/scripts/update-initramfs > >>> @@ -0,0 +1,33 @@ > >>> +#!/bin/bash > >>> +# Copyright 2009 Luis R. Rodriguez <mcgrof@gmail.com> > >>> +# > >>> +# Since we provide ssb, the Ethernet module b44 some people may > >>> +# rely on it to netboot, so update the initrafms for each > >>> +# distribution. > >>> +# > >>> +# Note that in the future people may want to wireless-boot > >>> +# so this will help with that as well. > >>> + > >>> +LSB_RED_ID=$(/usr/bin/lsb_release -i -s) > >>> + > >>> +KLIB=/lib/modules/2.6.31-wl/build > >>> +ver=$(echo $KLIB | awk -F "/lib/modules/" '{print $2}' | awk -F"/" '{print $1}') > >>> +dir=/boot/ > >>> + > >>> +case $LSB_RED_ID in > >>> +"Ubuntu") > >>> + echo "Updating Ubuntu's initramfs for $ver under $dir ..." > >>> + mkinitramfs -o $dir/initrd.img-$ver $ver > >>> + echo "Will now run update-grub to ensure grub will find the new initramfs ..." > >>> + update-grub > >>> + ;; > >>> +*) > >>> + echo "Warning:" > >>> + echo "You may or may not need to update your initframfs, you should if" > >>> + echo "any of the modules installed are part of your initramfs. To add" > >>> + echo "support for your distribution to do this automatically send a" > >>> + echo "patch against $0. If your distribution does not require this" > >>> + echo "send a patch against the '/usr/bin/lsb_release -i -s': $LSB_RED_ID" > >>> + echo "tag for your distribution to avoid this warning." > >>> + ;; > >>> +esac > >>> > >> Luis - I'll do something similar in a post install script for Karmic LBM > > > > Great, thanks for the heads up. > > > >> since the install-modules target in your makefile isn't used for a > >> debian install. > > > > Not sure I followed this part, what do you mean? > > > > It has to do with the way debian packages are installed. In the case of > LBM, the .ko files from the binary package are simply copied to their > target locations during 'apt-get install'. Therefore, a post > installation script needs to be run that updates the initramfs. Oh I see, the debian/rules file entry for install, got it. Luis ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: A problem loading ssb module 2009-09-28 21:00 ` Luis R. Rodriguez @ 2009-09-30 16:59 ` Tim Gardner 0 siblings, 0 replies; 16+ messages in thread From: Tim Gardner @ 2009-09-30 16:59 UTC (permalink / raw) To: Luis R. Rodriguez Cc: Luis Rodriguez, Luis R. Rodriguez, Clyde McPherson, Hauke Mehrtens, linux-wireless, bcm43xx-dev@lists.berlios.de Luis R. Rodriguez wrote: > On Mon, Sep 28, 2009 at 01:38:46PM -0700, Tim Gardner wrote: >> Luis R. Rodriguez wrote: >>> On Mon, Sep 28, 2009 at 01:00:55PM -0700, Tim Gardner wrote: >>>> Luis R. Rodriguez wrote: >>>>> On Sun, Sep 27, 2009 at 12:50:19PM -0700, Luis R. Rodriguez wrote: >>>>>> On Sun, Sep 27, 2009 at 8:15 AM, Clyde McPherson <ccmcphe@verizon.net> wrote: >>>>>>>> On Thu, Sep 24, 2009 at 11:33 AM, Hauke Mehrtens <hauke@hauke-m.de> 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 >>>>>>>> _______________________________________________ >>>>>>>> Bcm43xx-dev mailing list >>>>>>>> Bcm43xx-dev@lists.berlios.de >>>>>>>> https://lists.berlios.de/mailman/listinfo/bcm43xx-dev >>>>>>>> >>>>>>> All: >>>>>>> I have a large group that uses the ssb module along with the Broadcom 4318, >>>>>>> in a CF form factor. If the CF card is inserted before boot, and the ssb >>>>>>> module is not in the initrd process, the laptops lock up and do not become >>>>>>> operational. The solution to this problem is/was adding the ssb.ko to the >>>>>>> initrd process. So I agree with Luis on this, the ssb module will have to be >>>>>>> added/updated to the initrd process. As for PCI operations, I don't know, >>>>>>> but for PCMCIA operations ssb.ko has to be added and/or updated. Anytime I >>>>>>> am testing new releases of b43, I run "update-initramfs -u" to update the >>>>>>> ssb module. (Sometimes you can do a rmmod ssb and rmmod b43, and then >>>>>>> modprobe them back in. - This saves a reboot) >>>>>> But why is ssb, b43, b44 needed upon early boot? >>>>> OK the reason seems to be netboot. Yeah the only fix for distros who want >>>>> this on the initramfs is to update it after a compat-wireless package is >>>>> installed. I suppose we can add a hook to compat-wireless for each distro. >>>>> I'm only familiar with Ubuntu way of doing this so if people are interested >>>>> in other distros you'll need to point/test how to do this on there. >>>>> >>>>> Please try this patch against compat-wireless: (also attached) >>>>> >>>>> From 99af88246c2de71aa799de2b63f9d9ccac41634f Mon Sep 17 00:00:00 2001 >>>>> From: Luis R. Rodriguez <lrodriguez@atheros.com> >>>>> Date: Sun, 27 Sep 2009 13:58:22 -0700 >>>>> Subject: [PATCH] Add scripts/update-initramfs and use it >>>>> >>>>> Some distributions may ship b44 and ssb on the initramfs for >>>>> netboot. To help with this we need to update the initrafms >>>>> for those distributions. >>>>> >>>>> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com> >>>>> --- >>>>> Makefile | 1 + >>>>> scripts/update-initramfs | 33 +++++++++++++++++++++++++++++++++ >>>>> 2 files changed, 34 insertions(+), 0 deletions(-) >>>>> create mode 100755 scripts/update-initramfs >>>>> >>>>> diff --git a/Makefile b/Makefile >>>>> index ab97de0..c7333a2 100644 >>>>> --- a/Makefile >>>>> +++ b/Makefile >>>>> @@ -65,6 +65,7 @@ install: uninstall install-modules install-scripts >>>>> install-modules: modules >>>>> $(MAKE) -C $(KLIB_BUILD) M=$(PWD) $(KMODDIR_ARG) $(KMODPATH_ARG) \ >>>>> modules_install >>>>> + @./scripts/update-initramfs >>>>> >>>>> install-scripts: >>>>> @# All the scripts we can use >>>>> diff --git a/scripts/update-initramfs b/scripts/update-initramfs >>>>> new file mode 100755 >>>>> index 0000000..412d885 >>>>> --- /dev/null >>>>> +++ b/scripts/update-initramfs >>>>> @@ -0,0 +1,33 @@ >>>>> +#!/bin/bash >>>>> +# Copyright 2009 Luis R. Rodriguez <mcgrof@gmail.com> >>>>> +# >>>>> +# Since we provide ssb, the Ethernet module b44 some people may >>>>> +# rely on it to netboot, so update the initrafms for each >>>>> +# distribution. >>>>> +# >>>>> +# Note that in the future people may want to wireless-boot >>>>> +# so this will help with that as well. >>>>> + >>>>> +LSB_RED_ID=$(/usr/bin/lsb_release -i -s) >>>>> + >>>>> +KLIB=/lib/modules/2.6.31-wl/build >>>>> +ver=$(echo $KLIB | awk -F "/lib/modules/" '{print $2}' | awk -F"/" '{print $1}') >>>>> +dir=/boot/ >>>>> + >>>>> +case $LSB_RED_ID in >>>>> +"Ubuntu") >>>>> + echo "Updating Ubuntu's initramfs for $ver under $dir ..." >>>>> + mkinitramfs -o $dir/initrd.img-$ver $ver >>>>> + echo "Will now run update-grub to ensure grub will find the new initramfs ..." >>>>> + update-grub >>>>> + ;; >>>>> +*) >>>>> + echo "Warning:" >>>>> + echo "You may or may not need to update your initframfs, you should if" >>>>> + echo "any of the modules installed are part of your initramfs. To add" >>>>> + echo "support for your distribution to do this automatically send a" >>>>> + echo "patch against $0. If your distribution does not require this" >>>>> + echo "send a patch against the '/usr/bin/lsb_release -i -s': $LSB_RED_ID" >>>>> + echo "tag for your distribution to avoid this warning." >>>>> + ;; >>>>> +esac >>>>> >>>> Luis - I'll do something similar in a post install script for Karmic LBM >>> Great, thanks for the heads up. >>> >>>> since the install-modules target in your makefile isn't used for a >>>> debian install. >>> Not sure I followed this part, what do you mean? >>> >> It has to do with the way debian packages are installed. In the case of >> LBM, the .ko files from the binary package are simply copied to their >> target locations during 'apt-get install'. Therefore, a post >> installation script needs to be run that updates the initramfs. > > Oh I see, the debian/rules file entry for install, got it. > > Luis > Ok, this turned out to not be a debian package problem. Rather its a build issue for compat-wireless. Patch to follow. rtg -- Tim Gardner tim.gardner@canonical.com ^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2009-09-30 17:00 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1253811559.4579.44.camel@pc3.dido>
[not found] ` <4ABBAB47.8040300@canonical.com>
2009-09-24 18:33 ` A problem loading ssb module Hauke Mehrtens
2009-09-24 18:37 ` Luis R. Rodriguez
2009-09-25 0:04 ` Tim Gardner
2009-09-25 0:08 ` Luis R. Rodriguez
2009-09-25 0:14 ` Tim Gardner
2009-09-25 0:53 ` Luis R. Rodriguez
2009-09-26 15:15 ` Hauke Mehrtens
2009-09-27 15:15 ` Clyde McPherson
2009-09-27 19:50 ` Luis R. Rodriguez
2009-09-27 21:02 ` Luis R. Rodriguez
2009-09-28 19:55 ` Luis R. Rodriguez
2009-09-28 20:00 ` Tim Gardner
2009-09-28 20:07 ` Luis R. Rodriguez
2009-09-28 20:38 ` Tim Gardner
2009-09-28 21:00 ` Luis R. Rodriguez
2009-09-30 16:59 ` Tim Gardner
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).