I've tried regular-wmaker-20141217-x86_64.iso on a Dell Latitude. Thw wifi driver wasn't loaded and no wifi network adapters were available. altlinux-7.0.4-simply-x86_64-live-dvd5.iso doesn't have this problem. The computer: [root@localhost ~]# lspci 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1c.5 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 6 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation QM77 Express Chipset LPC Controller (rev 04) 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04) 02:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01) 03:00.0 SD Host controller: O2 Micro, Inc. Device 8221 (rev 05) [root@localhost ~]# Simply Linux Live system has loaded the following modules and has a working WiFi: [root@localhost ~]# lsmod Module Size Used by ipv6 347743 16 af_packet 35632 6 rfcomm 42737 8 bnep 18177 2 snd_seq_midi 13324 0 snd_seq_midi_event 14899 1 snd_seq_midi snd_seq 57544 2 snd_seq_midi_event,snd_seq_midi snd_rawmidi 30266 1 snd_seq_midi snd_seq_device 14497 3 snd_seq,snd_rawmidi,snd_seq_midi zram 18532 1 joydev 17456 0 dm_snapshot 39168 15 coretemp 13355 0 hwmon 12967 1 coretemp acpi_cpufreq 14151 0 mperf 12745 1 acpi_cpufreq intel_powerclamp 18762 0 kvm_intel 134821 0 kvm 425076 1 kvm_intel crc32_pclmul 13113 0 crc32c_intel 22079 0 ghash_clmulni_intel 13259 0 aesni_intel 55624 0 aes_x86_64 17131 1 aesni_intel lrw 13286 1 aesni_intel gf128mul 14951 1 lrw glue_helper 13985 1 aesni_intel ablk_helper 13597 1 aesni_intel cryptd 16307 3 ghash_clmulni_intel,aesni_intel,ablk_helper ppdev 12934 0 dell_wmi 12681 0 sparse_keymap 13890 1 dell_wmi iTCO_wdt 13509 0 iTCO_vendor_support 13718 1 iTCO_wdt dell_laptop 17369 0 arc4 12615 2 brcmsmac 514049 0 cordic 12574 1 brcmsmac brcmutil 15618 1 brcmsmac mac80211 502610 1 brcmsmac microcode 19005 0 psmouse 78093 0 pcspkr 12718 0 cfg80211 485118 2 brcmsmac,mac80211 sdhci_pci 18839 0 sdhci 33159 1 sdhci_pci mmc_core 111158 2 sdhci,sdhci_pci btusb 22596 0 uinput 17693 0 bluetooth 226492 22 bnep,btusb,rfcomm uvcvideo 80965 0 videobuf2_vmalloc 13056 1 uvcvideo videobuf2_memops 13202 1 videobuf2_vmalloc videobuf2_core 40543 1 uvcvideo videodev 127140 2 uvcvideo,videobuf2_core snd_hda_codec_hdmi 36967 1 rfkill 22455 5 cfg80211,bluetooth media 21468 2 uvcvideo,videodev snd_hda_codec_idt 50425 1 snd_hda_intel 43707 4 snd_hda_codec 179512 3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel snd_hwdep 13602 1 snd_hda_codec snd_pcm 97684 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel battery 18773 0 thermal 18435 0 parport_pc 41391 0 snd_page_alloc 18739 2 snd_pcm,snd_hda_intel snd_timer 29450 2 snd_pcm,snd_seq snd 68888 18 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_idt,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_seq_device parport 42322 2 ppdev,parport_pc soundcore 12680 1 snd i2c_i801 21760 0 ac 13227 0 lpc_ich 21073 0 processor 36160 1 acpi_cpufreq efivars 18094 0 dm_mod 84619 48 dm_snapshot autofs4 36620 2 squashfs 36551 1 loop 28009 2 nls_utf8 12557 1 nls_cp866 16929 1 vfat 17490 1 fat 66098 1 vfat ext4 511873 0 jbd2 98640 1 ext4 crc16 12675 2 ext4,bluetooth ext3 208874 0 jbd 79047 1 ext3 ext2 73085 0 mbcache 14939 3 ext2,ext3,ext4 sd_mod 45218 3 crc_t10dif 12563 1 sd_mod usb_storage 57338 2 dcdbas 14426 1 dell_laptop ahci 25819 0 libahci 32026 1 ahci evdev 17836 15 libata 212051 2 ahci,libahci serio_raw 13282 0 scsi_mod 213182 3 usb_storage,libata,sd_mod bcma 41843 2 brcmsmac i915 616463 2 intel_agp 14337 1 i915 ehci_pci 12705 0 intel_gtt 19531 2 i915,intel_agp ehci_hcd 49787 1 ehci_pci xhci_hcd 99665 0 drm_kms_helper 48813 1 i915 drm 286315 3 i915,drm_kms_helper e1000e 204234 0 usbcore 191277 6 btusb,uvcvideo,usb_storage,ehci_hcd,ehci_pci,xhci_hcd i2c_algo_bit 13413 1 i915 ptp 18580 1 e1000e pps_core 14139 1 ptp usb_common 13057 1 usbcore i2c_core 31051 6 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,videodev wmi 19070 1 dell_wmi button 13871 1 i915 video 19261 1 i915 [root@localhost ~]# Do NOT screenscrape this tool, we don't consider its output stable. [root@localhost ~]# iw list Wiphy phy0 Band 1: Capabilities: 0x70 HT20 Static SM Power Save RX Greenfield RX HT20 SGI RX HT40 SGI No RX STBC Max AMSDU length: 3839 bytes No DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 8 usec (0x06) HT TX/RX MCS rate indexes supported: 0-7 Frequencies: * 2412 MHz [1] (19.0 dBm) * 2417 MHz [2] (19.0 dBm) * 2422 MHz [3] (19.0 dBm) * 2427 MHz [4] (19.0 dBm) * 2432 MHz [5] (19.0 dBm) * 2437 MHz [6] (19.0 dBm) * 2442 MHz [7] (19.0 dBm) * 2447 MHz [8] (19.0 dBm) * 2452 MHz [9] (19.0 dBm) * 2457 MHz [10] (19.0 dBm) * 2462 MHz [11] (19.0 dBm) * 2467 MHz [12] (19.0 dBm) * 2472 MHz [13] (19.0 dBm) (passive scanning, no IBSS) * 2484 MHz [14] (disabled) Bitrates (non-HT): * 1.0 Mbps * 2.0 Mbps (short preamble supported) * 5.5 Mbps (short preamble supported) * 11.0 Mbps (short preamble supported) * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps max # scan SSIDs: 4 max scan IEs length: 2257 bytes Coverage class: 0 (up to 0m) Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP (00-0f-ac:4) Available Antennas: TX 0 RX 0 Supported interface modes: * IBSS * managed * AP * AP/VLAN * monitor software interface modes (can always be added): * AP/VLAN * monitor interface combinations are not supported Supported commands: * new_interface * set_interface * new_key * start_ap * new_station * new_mpath * set_mesh_config * set_bss * authenticate * associate * deauthenticate * disassociate * join_ibss * join_mesh * set_tx_bitrate_mask * frame * frame_wait_cancel * set_wiphy_netns * set_channel * set_wds_peer * probe_client * set_noack_map * register_beacons * start_p2p_device * Unknown command (92) * testmode * connect * disconnect Supported TX frame types: * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 Supported RX frame types: * IBSS: 0x40 0xb0 0xc0 0xd0 * managed: 0x40 0xd0 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * mesh point: 0xb0 0xc0 0xd0 * P2P-client: 0x40 0xd0 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * P2P-device: 0x40 0xd0 Device supports RSN-IBSS. HT Capability overrides: * MCS: ff ff ff ff ff ff ff ff ff ff * maximum A-MSDU length * supported channel width * short GI for 40 MHz * max A-MPDU length exponent * min MPDU start spacing Device supports TX status socket option. Device supports HT-IBSS. Device supports low priority scan. Device supports scan flush. Device supports AP scan. [root@localhost ~]#
Please specify kernel-modules-* and firmware-* packages included in environment that works for you; TIA.
Ok, I'll take a look right now. Another thought: perhaps, in regular-wmaker some service should be started manually to initialize the network drivers? Perhaps: service network start I haven't tried that.
In the working system (Simply Linux 7.0.4 Live): [altlinux@localhost ~]$ rpm -qa kernel-modules-* kernel-modules-drm-std-def-3.10.32-alt1 kernel-modules-v4l-std-def-3.10.32-alt1 kernel-modules-kvm-std-def-3.10.32-alt1 kernel-modules-staging-std-def-3.10.32-alt1 kernel-modules-drm-nouveau-std-def-3.10.32-alt1 kernel-modules-virtualbox-addition-std-def-4.3.6-alt1.199200.1 kernel-modules-drm-radeon-std-def-3.10.32-alt1 kernel-modules-bcmwl-std-def-6.30.223.141-alt2.199200.1 [altlinux@localhost ~]$ rpm -qa firmware-* firmware-zd1211-1.4-alt1 firmware-ipw2200-3.1-alt1 firmware-ipw2100-1.3-alt2 firmware-rt61pci-1.2-alt1 firmware-crystalhd-3.10.0-alt1_4.qa1 firmware-prism54-2.7.0.0-alt2 firmware-linux-20140123-alt1 firmware-acx100-1.2.1.34-alt1 firmware-ipw3945-1.14.2-alt2 firmware-rt73usb-1.8-alt2 [altlinux@localhost ~]$
I suspect (not sure) that kernel-modules-bcmwl-std-def-6.30.223.141-alt2.199200.1 is the thing that make WiFi work.
Weird: firmware packages are basically the same (the only broadcom-related one present in Simply and missing in regular-wmaker is firmware-crystalhd which is related to video decoding I believe); k-m-bcmwl and -staging are also present but it doesn't even matter as brcmsmac.ko is sitting in kernel-image-std-def. This is definitely not about services per se. Try getting to the point when "modprobe brcmsmac" on regular-wmaker with any differing packages installed gets you wlan0 interface (putting success/fail dmesgs aside might be useful either).
Thanks for the comment! "This is definitely not about services per se." Ok... I even used to think that in SimplyLinux NetworkManager might care about loading the network drivers, and since NM is missing in regular-wmaker I had no WiFi... So, that's not the right way to explore. Will try to look at dmesg side by side next.
It's rather udev's responsibility but it's the same in both cases.
Created attachment 6209 [details] dmesg-simply7.0.4.txt
Created attachment 6210 [details] journalctl-simply7.0.4.txt
Created attachment 6211 [details] dmesg-regular-wmaker-20141217.txt
Created attachment 6212 [details] messages-regular-wmaker-20141217.txt
Created attachment 6213 [details] lsmod-regular-wmaker-20141217.txt
Created attachment 6214 [details] diff -du <( sed 's|^\[[^]]*\] ||' < dmesg-simply7.0.4.txt) <( sed 's|^\[[^]]*\] ||' < dmesg-regular-wmaker-20141217.txt ) > dmesg.diff There are only 4 differing lines where brcmsmac is mentioned: $ diff -du <( sed 's|^\[[^]]*\] ||' < dmesg-simply7.0.4.txt) <( sed 's|^\[[^]]*\] ||' < dmesg-regular-wmaker-20141217.txt ) | fgrep -4 brcm -USB Video Class driver (1.1.1) -microcode: CPU0 sig=0x306a9, pf=0x10, revision=0x15 -cfg80211: Calling CRDA to update world regulatory domain -ACPI: AC Adapter [AC] (off-line) -brcmsmac bcma0:0: mfg 4bf core 812 rev 24 class 0 irq 17 -bcma: bus0: Switched to core: 0x812 -ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' -ieee80211 phy0: registered radio enabled led device: brcmsmac-phy0:radio gpio: 243 -parport_pc 00:0b: activated -parport_pc 00:0b: reported by Plug and Play ACPI -thermal LNXTHERM:00: registered as thermal_zone0 -ACPI: Thermal Zone [THM] (33 C) -- -Bluetooth: RFCOMM ver 1.11 +dell_wmi: Received unknown WMI event (0x0) e1000e 0000:00:19.0: irq 42 for MSI/MSI-X e1000e 0000:00:19.0: irq 42 for MSI/MSI-X -brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: false (implement) -brcmsmac bcma0:0: brcms_ops_config: change power-save mode: false (implement) +e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx +e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO NET: Registered protocol family 17 -aufs may_rename_srcdir:488:mv[2914]: renaming dir who has child(ren) on multiple branches, is not supported $ modprobe brcmsmac works without errors: # dmesg | tail [ 427.293514] e1000e 0000:00:19.0: irq 42 for MSI/MSI-X [ 427.393971] e1000e 0000:00:19.0: irq 42 for MSI/MSI-X [ 428.901328] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [ 428.901342] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO [ 428.995341] NET: Registered protocol family 17 [ 430.237250] NET: Registered protocol family 10 [ 3269.762807] brcmsmac bcma0:0: mfg 4bf core 812 rev 24 class 0 irq 17 [ 3269.762852] bcma: bus0: Switched to core: 0x812 [ 3269.773069] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 3269.773313] ieee80211 phy0: registered radio enabled led device: brcmsmac-phy0:radio gpio: 243 # After that the interface is listed by "ip addr" (but not by "ifconfig"). Probably, if I configure it correctly (in etcnet or after installing NM), it will work. The confusing part is that the driver is not loaded automatically and not shown in the list of interfaces.
[root@localhost ~]# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether b8:ca:3a:c6:a4:c1 brd ff:ff:ff:ff:ff:ff inet 10.0.0.75/24 brd 10.0.0.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::baca:3aff:fec6:a4c1/64 scope link valid_lft forever preferred_lft forever 3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether b8:76:3f:3f:9c:45 brd ff:ff:ff:ff:ff:ff [root@localhost ~]# ifconfig eth0 Link encap:Ethernet HWaddr B8:CA:3A:C6:A4:C1 inet addr:10.0.0.75 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::baca:3aff:fec6:a4c1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:18244 errors:0 dropped:4 overruns:0 frame:0 TX packets:8787 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:23434372 (22.3 MiB) TX bytes:778788 (760.5 KiB) Interrupt:20 Memory:f7e00000-f7e20000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) [root@localhost ~]#
iwlist scan gives results. So wifi works. It's not quite clear how to configure it easily. (Probably, manually editing etcnet is the way.) alterator has a broken WiFi configuration (at least, in this setup, without dbus): it can't correctly copy the name of the network and has other problems. NetworkManager is not installed. So, it seems that it is possible to configure WiFi in this distro after installation (without network access, but knowing the correct module name). A problem was to learn the correct driver name in this situation, because it wasn't loaded automatically.
(В ответ на комментарий №13) > sed 's|^\[[^]]*\] ||' < dmesg-simply7.0.4.txt dmesg -t :) > +dell_wmi: Received unknown WMI event (0x0) This *might* be related (via rfkill)... > modprobe brcmsmac works without errors [...] > Probably, if I configure it correctly (in etcnet or after installing NM), > it will work. Indeed; NM (or rather polkit) won't work without systemd-logind operable though, see also http://altlinux.org/sysvinit; but etcnet-based setup should work just fine (manual or via alterator-net-wifi), or say connman-based one. (В ответ на комментарий №15) > A problem was to learn the correct driver name in this situation > because it wasn't loaded automatically. Now *that* is strange and worth investigating IMO. dell-wmi.ko is included into kernel-image-std-def either, no idea on what could be the culprit so far.
Just for info: The behavior in altlinux-p7-wmaker-20141212-x86_64.iso is the same: module not loaded, wlan0 not present after booting the Live system.
Perhaps, /lib/systemd/system/systemd-udev-trigger.service does this in Simply Linux, and there is no analogue in regular-wmaker... # cat /lib/systemd/system/systemd-udev-trigger.service # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. [Unit] Description=udev Coldplug all Devices Documentation=man:udev(7) man:systemd-udevd.service(8) DefaultDependencies=no Wants=systemd-udevd.service After=systemd-udevd-kernel.socket systemd-udevd-control.socket Before=sysinit.target ConditionCapability=CAP_MKNOD [Service] Type=oneshot RemainAfterExit=yes ExecStart=/sbin/udevadm trigger --type=subsystems --action=add ; /sbin/udevadm trigger --type=devices --action=add #
/sbin/udevadm trigger --type=devices --action=add seems to make the interface appear in regular-wmaker. (Under a different name though: eth1)
(В ответ на комментарий №19) > /sbin/udevadm trigger --type=devices --action=add > > seems to make the interface appear in regular-wmaker. (Under a different name > though: eth1) Correction: in starterkit-wmaker. Another driver is used: wl . brcmsmac was not loaded.
No, everything I wrote above about udevadm is not correct because that was not a clean experiment: I did it after modprobe -r brcmsmac. After a clean boot, this doesn't make the wireless appear.
In the wmaker system (tested in starterkit), after the boot: udevadm trigger makes no difference: no wlan0 interface. But if I do: modprobe -r bcma udevadm trigger then the wifi interface appears (under the name eth1). "wl" driver is used, "brcmsmac" is not used and not loaded. So, proably "bcma" somehow gets into the way for correct initialization of the wifi drivers...
But "bcma" is not a problem in Simply Linux 7.0.4 (it is listed above among the moules loaded).
Ugh.
Here they also observe similar two variants of modules for a WiFi card: wl vs bcma -- https://bugzilla.altlinux.org/show_bug.cgi?id=29270#c0 . Here they had problems with bcma, which were gone after blacklisting it -- https://bugzilla.altlinux.org/show_bug.cgi?id=30229 . The only strange thing is that SimplyLinux 7.0.4 seems to use bcma and brcmsmac successfully, but starterkit-wmaker and regular-wmaker can't do this anymore.
https://bugzilla.altlinux.org/show_bug.cgi?id=26854#c1 : То же самое на текущем Сизифе. Предлагаю перевесить на Сизиф и, наконец, разобраться, какой драйвер использовать и какой блек
Давай.
(В ответ на комментарий №26) > https://bugzilla.altlinux.org/show_bug.cgi?id=26854#c1 : > > То же самое на текущем Сизифе. > Предлагаю перевесить на Сизиф и, наконец, разобраться, какой драйвер > использовать и какой блек Это цитата из https://bugzilla.altlinux.org/show_bug.cgi?id=26854#c1 . Это несколько ссылок на возникавшие проблемы такого рода в этой области. Какой драйвер из двух работающих лучше, я не смогу судить (пока). И как так получилось, что грузится bcma и мешает дальше грузиться и тому (brcmsmac), и другому (wl), я не понимаю. Менялся состав модулей и списки в blacklists (в результате они плохо друг другу соответствуют)?
Кстати, а как сейчас в http://nightly.altlinux.org/p7/beta/ выходит? (ничего особо не трогал, но вдруг алиасы в ядре поправили)
Looks like a bug #30229 dup. *** This bug has been marked as a duplicate of bug 30229 ***
If this machine is interesting for some experiments with these drivers, it is with me. But I don't remember well all the details. (Well, I see: it was fine with a p7 distro, which I'm using now, but was broken with some newer regular-* distros.)