HOWTO: Broadcom Wireless cards With Native Drivers

Issues Related to Networking (Wired and Wireless)

Moderator: Moderators

Re: HOWTO: Broadcom Wireless cards With Native Drivers

Postby IceDragon » Thu May 08, 2008 18:20

I've followed the howto, everything went fine, but it doesn't find any wlans. Running 3.5 loop2 with 2.6.24 kernel.

Here's iwconfig
Code: Select all
ID sabayonuser # iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wmaster0  no wireless extensions.

wlan0     IEEE 802.11g  ESSID:""
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated
          Tx-Power=27 dBm
          Retry min limit:7   RTS thr:off   Fragment thr=2346 B
          Encryption key:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

here's lsmod
Code: Select all
ID sabayonuser # lsmod
Module                  Size  Used by
rfkill_input            6400  0
snd_seq_dummy           5380  0
snd_seq_oss            33600  0
snd_seq_midi_event      9344  1 snd_seq_oss
snd_seq                55664  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device          9876  3 snd_seq_dummy,snd_seq_oss,snd_seq
ipv6                  293576  14
mmc_block              15616  0
tifm_sd                12936  0
mmc_core               55176  2 mmc_block,tifm_sd
b43                   148912  0
rfkill                  9620  3 rfkill_input,b43
mac80211              129292  1 b43
led_class               7048  1 b43
input_polldev           6800  1 b43
ohci_hcd               27908  0
nvidia               7007396  26
serio_raw               8836  0
pcspkr                  4608  0
snd_hda_intel         350116  0
snd_hwdep              11656  1 snd_hda_intel
tifm_7xx1               9600  0
yenta_socket           28556  1
rsrc_nonstatic         12928  1 yenta_socket
k8temp                  7424  0
tifm_core              12936  2 tifm_sd,tifm_7xx1
ssb                    39300  2 b43,ohci_hcd
forcedeth              50956  0
i2c_nforce2             8064  0
pcmcia                 42776  2 b43,ssb
i2c_core               26752  2 nvidia,i2c_nforce2
video                  22676  8
output                  5632  1 video
joydev                 14592  0
tg3                   112388  0
e1000                 122176  0
scsi_wait_scan          2816  0
sl811_hcd              14592  0
uhci_hcd               27040  0
ehci_hcd               36364  0

and lspci
Code: Select all
ID sabayonuser # lspci
00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:05.0 VGA compatible controller: nVidia Corporation MCP51 PCI-X GeForce Go 6100 (rev a2)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
00:0a.3 Co-processor: nVidia Corporation MCP51 PMU (rev a3)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev f1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev f1)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01)
04:06.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller
04:06.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD)


I think maybe the problem is that it's a rev 1 94311? But I wouldn't know.

Thanks for any help given
IceDragon
Baby Hen
 
Posts: 14
Joined: Wed Feb 20, 2008 23:35

Re: HOWTO: Broadcom Wireless cards With Native Drivers

Postby chickpea » Thu May 08, 2008 19:01

wmaster0 no wireless extensions.


Something you did was wrong.
OOPS, actually iwconfig always has wlanmaster0 as no wireless extensions my bad, ifconfig gives more information on the wireless device post that output please.


Code: Select all
login as: bichinh0
Using keyboard-interactive authentication.
Password:
Last login: Thu May  8 10:24:11 2008 from 70.21.123.161
[email protected] ~ $ sudo ifconfig
Password:
eth0      Link encap:Ethernet  HWaddr 00:1b:24:54:04:da
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:777 errors:0 dropped:0 overruns:0 frame:0
          TX packets:847 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:862993 (842.7 KiB)  TX bytes:167214 (163.2 KiB)
          Interrupt:20 Base address:0xa000

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:16436  Metric:1
          RX packets:167 errors:0 dropped:0 overruns:0 frame:0
          TX packets:167 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:49431 (48.2 KiB)  TX bytes:49431 (48.2 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:1a:73:6b:51:09
          inet addr:192.168.1.6  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::21a:73ff:fe6b:5109/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2200606 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1918468 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2150238738 (2.0 GiB)  TX bytes:417821106 (398.4 MiB)

wmaster0  Link encap:UNSPEC  HWaddr 00-1A-73-6B-51-09-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST  MTU:1500  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:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

[email protected] ~ $


that is the appropriate ifconfig output. Try ifconfig and see what it says.

Do you have the appropriate b43-fwcutter and firmware tarball installed?

Try posting the output of this after you try to associate with a WAP

Code: Select all
sudo dmesg | grep "b43"


and
Code: Select all
 sudo cat /var/log/messages | tail -150
chickpea
Sagely Hen
 
Posts: 1084
Joined: Fri Jan 05, 2007 15:08
Location: Washington, DC

Re: HOWTO: Broadcom Wireless cards With Native Drivers

Postby IceDragon » Thu May 08, 2008 19:11

I played around a bit with the drivers. Now it says:

iwconfig:

Code: Select all
ID sabayonuser # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:D3:5B:26:F1
          inet addr:192.168.254.35  Bcast:192.168.254.255  Mask:255.255.255.0
          inet6 addr: fe80::216:d3ff:fe5b:26f1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8801 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4987 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:9322732 (8.8 Mb)  TX bytes:586205 (572.4 Kb)
          Interrupt:20 Base address:0x8000

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:16436  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)

wlan0     Link encap:Ethernet  HWaddr 00:19:7E:9D:2C:3D
          UP BROADCAST MULTICAST  MTU:1500  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:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wmaster0  Link encap:UNSPEC  HWaddr 00-19-7E-9D-2C-3D-2B-90-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST  MTU:1500  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:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


and here are the two latter thing you asked
Code: Select all
ID sabayonuser # sudo dmesg | grep "b43"
[   42.979138] b43-phy0: Broadcom 4311 WLAN found
[   42.993919] b43-phy0 debug: Found PHY: Analog 4, Type 2, Revision 8
[   42.993946] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
[   82.926591] input: b43-phy0 as /class/input/input11
[   83.301229] b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
[   84.925947] b43-phy0 debug: Chip initialized
[   84.926279] b43-phy0 debug: 32-bit DMA initialized
[   84.935856] Registered led device: b43-phy0:tx
[   84.936022] Registered led device: b43-phy0:rx
[   84.936109] Registered led device: b43-phy0:radio
[   84.936148] b43-phy0 debug: Wireless interface started
[   84.958679] b43-phy0 debug: Adding Interface type 2
[  199.532388] b43-phy0: Radio hardware status changed to DISABLED
[  203.530098] b43-phy0: Radio hardware status changed to ENABLED
ID sabayonuser #  sudo cat /var/log/messages | tail -150
May  8 18:44:43 ID [   84.936022] Registered led device: b43-phy0:rx
May  8 18:44:43 ID [   84.936109] Registered led device: b43-phy0:radio
May  8 18:44:43 ID [   84.936148] b43-phy0 debug: Wireless interface started
May  8 18:44:43 ID [   84.958679] b43-phy0 debug: Adding Interface type 2
May  8 18:44:43 ID [   84.960670] ADDRCONF(NETDEV_UP): wlan0: link is not ready
May  8 18:44:43 ID NetworkManager: <debug> [1210265083.877554] GentooReadConfig(): Enabling DHCP for device wlan0.
May  8 18:44:43 ID NetworkManager: <debug> [1210265083.877631] GentooReadConfig(): Found DNS nameservers in config.
May  8 18:44:43 ID NetworkManager: <debug> [1210265083.877672] GentooReadConfig(): Found hostname.
May  8 18:44:43 ID NetworkManager: nm_ip4_config_set_hostname: assertion `config != NULL' failed
May  8 18:44:43 ID NetworkManager: <info>  wlan0: Device is fully-supported using driver 'b43-pci-bridge'.
May  8 18:44:43 ID NetworkManager: <info>  wlan0: driver does not support SSID scans (scan_capa 0x00).
May  8 18:44:43 ID NetworkManager: <info>  nm_device_init(): waiting for device's worker thread to start
May  8 18:44:43 ID NetworkManager: <info>  nm_device_init(): device's worker thread started, continuing.
May  8 18:44:43 ID NetworkManager: <info>  Now managing wireless (802.11) device 'wlan0'.
May  8 18:44:43 ID NetworkManager: <info>  Deactivating device wlan0.
May  8 18:44:43 ID NetworkManager: <debug> [1210265083.893365] GentooReadConfig(): Enabling DHCP for device eth0.
May  8 18:44:43 ID NetworkManager: <debug> [1210265083.893597] GentooReadConfig(): Found DNS nameservers in config.
May  8 18:44:43 ID NetworkManager: <debug> [1210265083.893732] GentooReadConfig(): Found hostname.
May  8 18:44:43 ID NetworkManager: nm_ip4_config_set_hostname: assertion `config != NULL' failed
May  8 18:44:43 ID NetworkManager: <info>  eth0: Device is fully-supported using driver 'forcedeth'.
May  8 18:44:43 ID NetworkManager: <info>  nm_device_init(): waiting for device's worker thread to start
May  8 18:44:43 ID NetworkManager: <info>  nm_device_init(): device's worker thread started, continuing.
May  8 18:44:43 ID NetworkManager: <info>  Now managing wired Ethernet (802.3) device 'eth0'.
May  8 18:44:43 ID NetworkManager: <info>  Deactivating device eth0.
May  8 18:44:43 ID NetworkManager: <info>  Will activate wired connection 'eth0' because it now has a link.
May  8 18:44:44 ID rc-scripts: WARNING:  net.lo has already been started.
May  8 18:44:44 ID NetworkManager: <debug> [1210265084.070524] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/computer_logicaldev_input_6').
May  8 18:44:44 ID NetworkManager: <info>  Will activate wired connection 'eth0' because it now has a link.
May  8 18:44:44 ID dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
May  8 18:44:44 ID NetworkManager: <info>  SWITCH: no current connection, found better connection 'eth0'.
May  8 18:44:44 ID NetworkManager: <info>  Will activate connection 'eth0'.
May  8 18:44:44 ID NetworkManager: <info>  Device eth0 activation scheduled...
May  8 18:44:44 ID NetworkManager: <info>  Activation (eth0) started...
May  8 18:44:44 ID NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
May  8 18:44:44 ID NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) started...
May  8 18:44:44 ID NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
May  8 18:44:44 ID NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
May  8 18:44:44 ID NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) starting...
May  8 18:44:44 ID NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) successful.
May  8 18:44:44 ID NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
May  8 18:44:44 ID NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete.
May  8 18:44:44 ID NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
May  8 18:44:45 ID NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction.
May  8 18:44:45 ID NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
May  8 18:44:45 ID NetworkManager: <info>  DHCP daemon state is now 12 (successfully started) for interface eth0
May  8 18:44:45 ID dhclient: wmaster0: unknown hardware address type 801
May  8 18:44:46 ID sshd[9221]: Server listening on :: port 22.
May  8 18:44:46 ID sshd[9221]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
May  8 18:44:47 ID NetworkManager: <info>  DHCP daemon state is now 1 (starting) for interface eth0
May  8 18:44:47 ID dhclient: wmaster0: unknown hardware address type 801
May  8 18:44:47 ID cron[9378]: (CRON) STARTUP (V5.0)
May  8 18:44:48 ID dhclient: option_space_encapsulate: option space agent does not exist, but is configured.
May  8 18:44:48 ID dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
May  8 18:44:48 ID [   89.695807] atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly.
May  8 18:44:49 ID [   90.695261] atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly.
May  8 18:44:50 ID dhclient: DHCPOFFER from 192.168.254.1
May  8 18:44:50 ID dhclient: option_space_encapsulate: option space agent does not exist, but is configured.
May  8 18:44:50 ID dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
May  8 18:44:50 ID dhclient: DHCPACK from 192.168.254.1
May  8 16:44:50 ID avahi-daemon[8377]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.254.35.
May  8 16:44:50 ID avahi-daemon[8377]: New relevant interface eth0.IPv4 for mDNS.
May  8 16:44:50 ID avahi-daemon[8377]: Registering new address record for 192.168.254.35 on eth0.IPv4.
May  8 18:44:50 ID NetworkManager: <info>  DHCP daemon state is now 2 (bound) for interface eth0
May  8 18:44:50 ID NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
May  8 18:44:50 ID NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
May  8 18:44:50 ID dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
May  8 18:44:50 ID dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
May  8 18:44:50 ID NetworkManager: <info>  Retrieved the following IP4 configuration from the DHCP daemon:
May  8 18:44:50 ID NetworkManager: <info>    address 192.168.254.35
May  8 18:44:50 ID NetworkManager: <info>    netmask 255.255.255.0
May  8 18:44:50 ID NetworkManager: <info>    broadcast 192.168.254.255
May  8 18:44:50 ID NetworkManager: <info>    gateway 192.168.254.1
May  8 18:44:50 ID NetworkManager: <info>    nameserver 195.238.2.21
May  8 18:44:50 ID NetworkManager: <info>    nameserver 195.238.2.22
May  8 18:44:50 ID NetworkManager: <info>    hostname 'ID'
May  8 18:44:50 ID NetworkManager: <info>    domain name 'lan'
May  8 18:44:50 ID dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.interface_mtu
May  8 18:44:50 ID NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
May  8 18:44:50 ID NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
May  8 18:44:50 ID NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
May  8 18:44:50 ID dhclient: bound to 192.168.254.35 -- renewal in 3286 seconds.
May  8 16:44:50 ID avahi-daemon[8377]: Withdrawing address record for 192.168.254.35 on eth0.
May  8 16:44:50 ID avahi-daemon[8377]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.254.35.
May  8 16:44:50 ID avahi-daemon[8377]: Interface eth0.IPv4 no longer relevant for mDNS.
May  8 16:44:50 ID avahi-daemon[8377]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.254.35.
May  8 16:44:50 ID avahi-daemon[8377]: New relevant interface eth0.IPv4 for mDNS.
May  8 16:44:50 ID avahi-daemon[8377]: Registering new address record for 192.168.254.35 on eth0.IPv4.
May  8 18:44:51 ID NetworkManager: <info>  Setting hostname to 'ID'
May  8 18:44:51 ID NetworkManager: <info>  Activation (eth0) successful, device activated.
May  8 18:44:51 ID NetworkManager: <info>  Activation (eth0) Finish handler scheduled.
May  8 18:44:51 ID NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
May  8 16:44:52 ID avahi-daemon[8377]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::216:d3ff:fe5b:26f1.
May  8 16:44:52 ID avahi-daemon[8377]: New relevant interface eth0.IPv6 for mDNS.
May  8 16:44:52 ID avahi-daemon[8377]: Registering new address record for fe80::216:d3ff:fe5b:26f1 on eth0.*.
May  8 18:45:00 ID kdm: :0[8629]: pam_unix(kde:session): session opened for user sabayonuser by (uid=0)
May  8 18:45:01 ID [  103.043282] eth0: no IPv6 routers present
May  8 18:45:27 ID [  127.956458] Clocksource tsc unstable (delta = -110981666 ns)
May  8 18:45:31 ID NetworkManager: <info>  Updating allowed wireless network lists.
May  8 18:45:31 ID NetworkManager: <WARN>  nm_dbus_get_networks_cb(): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - org.freedesktop.NetworkManagerInfo.NoNetworks.
May  8 18:45:36 ID (sabayonuser-9738): starting (version 2.20.1), pid 9738 user 'sabayonuser'
May  8 18:45:36 ID (sabayonuser-9738): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
May  8 18:45:36 ID (sabayonuser-9738): Resolved address "xml:readwrite:/home/sabayonuser/.gconf" to a writable configuration source at position 1
May  8 18:45:36 ID (sabayonuser-9738): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
May  8 18:47:30 ID su[9889]: Successful su for root by sabayonuser
May  8 18:47:30 ID su[9889]: + pts/1 sabayonuser:root
May  8 18:47:30 ID su[9889]: pam_unix(su:session): session opened for user root by (uid=1000)
May  8 18:47:46 ID [  198.975558] atkbd.c: Unknown key pressed (translated set 2, code 0xd6 on isa0060/serio0).
May  8 18:47:46 ID [  198.975564] atkbd.c: Use 'setkeycodes e056 <keycode>' to make it known.
May  8 18:47:46 ID [  199.131684] atkbd.c: Unknown key released (translated set 2, code 0xd6 on isa0060/serio0).
May  8 18:47:46 ID [  199.131690] atkbd.c: Use 'setkeycodes e056 <keycode>' to make it known.
May  8 18:47:46 ID [  199.532388] b43-phy0: Radio hardware status changed to DISABLED
May  8 18:47:50 ID [  202.954858] atkbd.c: Unknown key pressed (translated set 2, code 0xd5 on isa0060/serio0).
May  8 18:47:50 ID [  202.954864] atkbd.c: Use 'setkeycodes e055 <keycode>' to make it known.
May  8 18:47:50 ID [  203.150007] atkbd.c: Unknown key released (translated set 2, code 0xd5 on isa0060/serio0).
May  8 18:47:50 ID [  203.150013] atkbd.c: Use 'setkeycodes e055 <keycode>' to make it known.
May  8 18:47:50 ID [  203.530098] b43-phy0: Radio hardware status changed to ENABLED
May  8 18:50:01 ID cron[9910]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
May  8 18:50:38 ID su[9889]: pam_unix(su:session): session closed for user root
May  8 19:00:01 ID cron[10137]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
May  8 19:00:01 ID cron[10141]: (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
May  8 19:04:24 ID [  694.874235] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:24 ID [  694.938183] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:39 ID [  700.383131] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:39 ID [  700.429633] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:39 ID [  700.511041] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:40 ID [  700.554635] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:40 ID [  700.606974] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:40 ID [  700.650569] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:41 ID [  701.008143] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:41 ID [  701.054655] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:46 ID [  702.749478] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:46 ID [  702.790186] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:46 ID [  702.822157] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:46 ID [  702.862847] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:46 ID [  702.912274] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:46 ID [  702.947148] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:49 ID [  703.862886] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:49 ID [  703.906482] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:49 ID [  703.947188] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:04:49 ID [  703.987893] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:05:03 ID [  709.865242] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:05:03 ID [  709.905929] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:05:03 ID [  709.943730] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:05:03 ID [  709.990243] drivers/hid/usbhid/hid-core.c: event field not found
May  8 19:07:02 ID su[10185]: Successful su for root by sabayonuser
May  8 19:07:02 ID su[10185]: + pts/1 sabayonuser:root
May  8 19:07:02 ID su[10185]: pam_unix(su:session): session opened for user root by (uid=1000)
May  8 19:09:35 ID sudo:     root : TTY=pts/1 ; PWD=/home/sabayonuser ; USER=root ; COMMAND=/bin/dmesg
May  8 19:10:01 ID cron[10198]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
May  8 19:10:09 ID sudo:     root : TTY=pts/1 ; PWD=/home/sabayonuser ; USER=root ; COMMAND=/bin/cat /var/log/messages


:) You're my hero Chickpea
IceDragon
Baby Hen
 
Posts: 14
Joined: Wed Feb 20, 2008 23:35

Re: HOWTO: Broadcom Wireless cards With Native Drivers

Postby chickpea » Thu May 08, 2008 19:19

Well from the logs I can tell that your wireless card is not associating, although it is at least being brought up by the kernel. Did you patch the kernel at all? If you are running that kernel, it would have needed to be patched with that patch I mentioned in the howto. Reading over my howto it might not be very clear that you need to patch <=2.6.24 kernels. If you didn't patch the kernel, then redo the howto, but this time do all the patching and rebuild the kernel. See if that helps. If you just can't get it to work, then upgrade to linux-sabayon-2.6.25, which is MUCH easier to deal with (no patching required).
chickpea
Sagely Hen
 
Posts: 1084
Joined: Fri Jan 05, 2007 15:08
Location: Washington, DC

Re: HOWTO: Broadcom Wireless cards With Native Drivers

Postby chickpea » Thu May 08, 2008 19:32

Well you are running the correct firmware from what I see (351.126), but it appears that it is not functioning properly. That leads me to believe that you didn't patch the kernel. If I am wrong, and you did properly patch the kernel, then I am really all out of answers, sorry. :oops: :cry:

Like I said, you may just want to upgrade to 2.6.25 and see if you have any better luck with that. (Remember with 2.6.25 you will need the newer firmware and the fwcutter-011)

If all else fails, go to http://linuxwireless.org/ and post in their development listserv, cause that's where I get all my juju anyways...
chickpea
Sagely Hen
 
Posts: 1084
Joined: Fri Jan 05, 2007 15:08
Location: Washington, DC

Re: HOWTO: Broadcom Wireless cards With Native Drivers

Postby IceDragon » Thu May 08, 2008 19:43

repatching and following steps from start.

I hope it will work.
IceDragon
Baby Hen
 
Posts: 14
Joined: Wed Feb 20, 2008 23:35

Re: HOWTO: Broadcom Wireless cards With Native Drivers

Postby IceDragon » Sun May 11, 2008 12:57

aaah module rebuild for nvidia-drivers-100.14.19 fails. I hate this.
Ofc new kernel doesn't boot properly now. :x

Maybe I should just wait for the alpha release of 3.5?
IceDragon
Baby Hen
 
Posts: 14
Joined: Wed Feb 20, 2008 23:35

Re: HOWTO: Broadcom Wireless cards With Native Drivers

Postby chickpea » Mon May 12, 2008 15:10

1. 3.5 is already in beta loop 2, way past alpha stage.

2. the kernel doesn't boot at all, or doesn't give you a gui?

3. what are the errors that boot throws off when you boot?

4. Module rebuild WILL fail for 100.14.19, because it is not correctly patched for 2.6.25 kernel. You will need to upgrade to the new beta nvidia driver. If you have a mobile GeForce Go card, this WILL cause some problems with black screens etc, which are mildly annoying but not fatal. Just emerge nvidia-drivers and this will automagically update your moduledb. Then you can resume a module-rebuild rebuild

Look you need to read a little on the wiki from the upgrading kernel section of the wiki, these are all steps that are explained there.

http://wiki.sabayonlinux.org/index.php? ... _genkernel
chickpea
Sagely Hen
 
Posts: 1084
Joined: Fri Jan 05, 2007 15:08
Location: Washington, DC

Previous

Return to Networking and Wireless

Who is online

Users browsing this forum: No registered users and 1 guest

cron