broadcom triggering udev event error
Posted: 5. Jun 2013, 03:34
The install of 64-bit Salix 14 on my HP Pavillion 6450b went normally, but when booting it waits for around 30 seconds at the 'triggering udev events' step and then throws up this message:
udev [1557] worker [1570] timeout, kill it
udev [1557] seq 1933 'devices/pci0000:00/0000:1c.3/0000:44.0' killed
udev [1557] worker [1570] terminated by signal 9 (Killed)
Following advice on the internet to find out what it taking too long i did:
root[andy]# lspci -s 0000:44:00.0
44:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
And more details:
root[andy]# lspci -vnn -s 0000:44:00.0
44:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:145c]
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at d0500000 (64-bit, non-prefetchable)
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 00-00-82-ff-ff-d4-00-26
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: brcmsmac
But when it finishes booting and I check with lsmod I see that brcmsmac is loaded.
use 66626 3
brcmsmac 534140 0
cordic 1065 1 brcmsmac
crc8 1104 1 brcmsmac
brcmutil 3531 1 brcmsmac
mac80211 227731 1 brcmsmac
hp_wmi 7802 0
The link I was following suggested pre-loading the module so I tried putting the line /sbin/modprobe brcmsmac in /etc/rc.d/rc.local but it made no difference - presumably because the module is actually loading anyway.
Another problem which may be connected is that the wireless isn't working consistently. On one occasion I was able to activate and use wireless by touching the wifi LED on the keyboard but presently I can't - wireless is not active at all.
I have checked the forum and read many of the posts on Broadcom problems but I didn't see anything similar to mine. Thanks in advance for any pointers.
Andy
udev [1557] worker [1570] timeout, kill it
udev [1557] seq 1933 'devices/pci0000:00/0000:1c.3/0000:44.0' killed
udev [1557] worker [1570] terminated by signal 9 (Killed)
Following advice on the internet to find out what it taking too long i did:
root[andy]# lspci -s 0000:44:00.0
44:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
And more details:
root[andy]# lspci -vnn -s 0000:44:00.0
44:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:145c]
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at d0500000 (64-bit, non-prefetchable)
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 00-00-82-ff-ff-d4-00-26
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: brcmsmac
But when it finishes booting and I check with lsmod I see that brcmsmac is loaded.
use 66626 3
brcmsmac 534140 0
cordic 1065 1 brcmsmac
crc8 1104 1 brcmsmac
brcmutil 3531 1 brcmsmac
mac80211 227731 1 brcmsmac
hp_wmi 7802 0
The link I was following suggested pre-loading the module so I tried putting the line /sbin/modprobe brcmsmac in /etc/rc.d/rc.local but it made no difference - presumably because the module is actually loading anyway.
Another problem which may be connected is that the wireless isn't working consistently. On one occasion I was able to activate and use wireless by touching the wifi LED on the keyboard but presently I can't - wireless is not active at all.
I have checked the forum and read many of the posts on Broadcom problems but I didn't see anything similar to mine. Thanks in advance for any pointers.
Andy