Wireless network not working after upgrade too 10.10

[Snowhog]

Re: Wireless network not working after upgrade too 10.10

It's a log file, not an application to be installed.

sudo cat /var/log/jockey.log

[snowflake_nz]

Re: Wireless network not working after upgrade too 10.10

oh dear, thanks for the correction Snowhog.
Seems the sunny New Zealand weather has taken over my brain LOL

Here's the correct output
ndetermined, adding to pool
2010-10-30 11:17:37,898 DEBUG: loading custom handler /usr/share/jockey/handlers
/dvb_usb_firmware.py
2010-10-30 11:17:37,955 DEBUG: Instantiated Handler subclass __builtin__.DvbUsbFirmwareHandler
from name DvbUsbFirmwareHandler
2010-10-30 11:17:37,956 DEBUG: Firmware for DVB cards not available
2010-10-30 11:17:37,956 DEBUG: loading custom handler /usr/share/jockey/handlers/sl_modem.py
2010-10-30 11:17:37,986 DEBUG: Instantiated Handler subclass __builtin__.SlModem from name
SlModem
2010-10-30 11:17:38,034 DEBUG: Software modem is available
2010-10-30 11:17:38,034 DEBUG: loading custom handler /usr/share/jockey/handlers/broadcom_wl.py
2010-10-30 11:17:38,048 WARNING: modinfo for module wl failed: ERROR: modinfo: could not find
module wl
2010-10-30 11:17:38,079 DEBUG: Instantiated Handler subclass __builtin__.BroadcomWLHandler from
name BroadcomWLHandler
2010-10-30 11:17:38,079 DEBUG: Broadcom STA wireless driver availability undetermined, adding to
pool
2010-10-30 11:17:38,079 DEBUG: loading custom handler /usr/share/jockey/handlers/fglrx.py
2010-10-30 11:17:38,142 WARNING: modinfo for module fglrx failed: ERROR: modinfo: could not find
module fglrx
2010-10-30 11:17:38,143 DEBUG: Instantiated Handler subclass __builtin__.FglrxDriver from name
FglrxDriver
2010-10-30 11:17:38,167 DEBUG: ATI/AMD proprietary FGLRX graphics driver availability undetermined,
adding to pool
2010-10-30 11:17:38,168 DEBUG: loading custom handler /usr/share/jockey/handlers/nvidia.py
2010-10-30 11:17:38,186 DEBUG: Could not instantiate Handler subclass __builtin__.NvidiaDriver96
from name NvidiaDriver96
Traceback (most recent call last):
File "/usr/lib/python2.6/dist-packages/jockey/detection.py", line 914, in get_handlers
inst = obj(backend)
File "/usr/share/jockey/handlers/nvidia.py", line 184, in __init__
raise SystemError, 'does not currently work with xserver 1.9'
SystemError: does not currently work with xserver 1.9
2010-10-30 11:17:38,214 WARNING: modinfo for module nvidia_current failed: ERROR: modinfo: could
not find module nvidia_current
2010-10-30 11:17:38,215 DEBUG: Instantiated Handler subclass __builtin__.NvidiaDriverCurrent from
name NvidiaDriverCurrent
2010-10-30 11:17:38,244 DEBUG: NVIDIA accelerated graphics driver availability undetermined, adding
to pool
2010-10-30 11:17:38,244 DEBUG: Could not instantiate Handler subclass __builtin__.NvidiaDriverBase
from name NvidiaDriverBase
Traceback (most recent call last):
File "/usr/lib/python2.6/dist-packages/jockey/detection.py", line 914, in get_handlers
inst = obj(backend)
TypeError: __init__() takes exactly 3 arguments (2 given)
2010-10-30 11:17:38,253 WARNING: modinfo for module nvidia_173 failed: ERROR: modinfo: could not
find module nvidia_173

2010-10-30 11:17:38,254 DEBUG: Instantiated Handler subclass __builtin__.NvidiaDriver173 from
name NvidiaDriver173
2010-10-30 11:17:38,266 DEBUG: NVIDIA accelerated graphics driver availability undetermined, adding
to pool
2010-10-30 11:17:38,266 DEBUG: all custom handlers loaded
2010-10-30 11:17:38,267 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance
at 0x91194ac> about HardwareID('modalias', 'pci:v00008086d000027A6sv00001025sd00000110bc03sc8 0i00')
2010-10-30 11:17:38,840 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'input:b0003v1241p1177e0110-
e0,1,2,4,k110,111,112,r0,1,8,am4,lsfw')
2010-10-30 11:17:39,283 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,284 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'pci:v0000104Cd00008039sv00001025sd00000110bc06sc0 7i00')
2010-10-30 11:17:39,313 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'yenta_socket', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,313 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'yenta_socket', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,313 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'pci:v000014E4d00004318sv00001468sd00000312bc02sc8 0i00')
2010-10-30 11:17:39,389 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'ssb', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,389 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'acpi:PNP0200:')
2010-10-30 11:17:39,389 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'acpi:LNXSYSTM:')
2010-10-30 11:17:39,390 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias',
'pci:v00008086d000027D8sv00001025sd00000110bc04sc0 3i00')
2010-10-30 11:17:39,395 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'snd_hda_intel', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,395 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'platform:eisa')
2010-10-30 11:17:39,396 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00')
2010-10-30 11:17:39,429 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance
at 0x91194ac> about HardwareID('modalias', 'pci:v0000104Cd0000803Bsv00001025sd00000110bc01sc8 0i00')
2010-10-30 11:17:39,430 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'tifm_7xx1', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,430 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'input:b0011v0001p0001eAB41-
e0,1,4,11,14,k71,72,73,74,75,77,79,7A,7B,7C,7D,7E, 7F,80,8A,8C,8D,8E,8F,94,95,9B,9C,9D,9E,9F,A3,
A4,A5,A6,AC,AD,B7,B8,B9,C0,C1,D9,E0,E1,E2,E3,EC,ED ,EE,1A9,1B2,1B3,1D0,ram4,l0,1,2,sfw')
2010-10-30 11:17:39,431 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,431 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'acpi:LNXSYBUS:')
2010-10-30 11:17:39,431 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias',
'pci:v00008086d000027B9sv00001025sd00000110bc06sc0 1i00')
2010-10-30 11:17:39,436 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'intel_rng', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,436 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'iTCO_wdt', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,436 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'leds_ss4200', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,436 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'platformcspkr')
2010-10-30 11:17:39,437 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'pcspkr', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,437 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'snd_pcsp', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,437 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias',
'pci:v00008086d000027C9sv00001025sd00000110bc0Csc0 3i00')
2010-10-30 11:17:39,442 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'platform:regulatory')
2010-10-30 11:17:39,443 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'wmi:CFF94C79-6C77-4AF7-
AC56-7DD0CE01C997')
2010-10-30 11:17:39,443 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias',
'pci:v00008086d000027A0sv00001025sd00000110bc06sc0 0i00')
2010-10-30 11:17:39,448 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'intel_agp', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,448 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'wmiB85B1A7-069A-4ABB-A2B5-
D186A21B80F1')
2010-10-30 11:17:39,448 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'acpi:PNP0303:')
2010-10-30 11:17:39,449 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'acpi:PNP0C02:')
2010-10-30 11:17:39,449 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias',
'pci:v00008086d000027A2sv00001025sd00000110bc03sc0 0i00')
2010-10-30 11:17:39,454 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'i915', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,454 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'acpi:device:')
2010-10-30 11:17:39,454 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'acpi:SYN1003:SYN1000:SYN0002:PNP0F13:')
2010-10-30 11:17:39,454 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'acpi:PNP0103:PNP0C01:')
2010-10-30 11:17:39,454 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'acpi:PNP0B00:')
2010-10-30 11:17:39,455 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias',
'usb:v1241p1177d0270dc00dsc00dp00ic03isc01ip02')
2010-10-30 11:17:39,455 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'usbhid', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,455 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias',
'pci:v000011ABd00004352sv00001025sd00000110bc02sc0 0i00')
2010-10-30 11:17:39,512 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'sky2', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,515 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias',
'pci:v00008086d00002448sv00001025sd00000110bc06sc0 4i01')
2010-10-30 11:17:39,519 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'input:b0019v0000p0001e0000-
e0,1,k74,ramlsfw')
2010-10-30 11:17:39,520 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,522 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'input:b0019v0000p0005e0000-e0,5,kramlsfw0,')
2010-10-30 11:17:39,523 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,523 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'wmi:E78C4453-0227-4861-9EDE-F5600B4A3D39')
2010-10-30 11:17:39,523 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'acpi:LNXTHERM:')
2010-10-30 11:17:39,524 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'dmi:bvnAcer:bvrv1.3221:bd12/15
/06:svnAcer,inc.nAspire3680vrNotApplicable:rvnAcer,Inc.:rnPrespa1:rvrNotAppli cable:cvnAcer,
Inc.:ct1:cvrN/A:')
2010-10-30 11:17:39,559 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'wmi:79772EC5-04B1-4BFD-843C-61E7F77B6CC9')
2010-10-30 11:17:39,559 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'acpi:PNP0000:')
2010-10-30 11:17:39,559 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'wmi:95764E09-FB56-4E83-B31A-37761F60994A')
2010-10-30 11:17:39,559 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'input:b0019v0000p0003e0000-
e0,1,k8E,ramlsfw')
2010-10-30 11:17:39,560 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,560 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias',
'usb:v1D6Bp0002d0206dc09dsc00dp00ic09isc00ip00')
2010-10-30 11:17:39,564 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'option', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,564 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias',
'usb:v1058p1010d0105dc00dsc00dp00ic08isc06ip50')
2010-10-30 11:17:39,565 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'usb_storage', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,566 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'acpi:PNP0100:')
2010-10-30 11:17:39,566 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'acpi:PNP0C04:')
2010-10-30 11:17:39,566 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'pci:v00008086d000027CCsv00001025sd00000110
bc0Csc03i20')
2010-10-30 11:17:39,573 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias',
'usb:v0402p5602d0100dc00dsc00dp00icFFiscFFipFF')
2010-10-30 11:17:39,576 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'gspca_m5602', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,578 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'wmi:A7C9A0B7-4C9D-4C72-83BB-
53A3459171DF')
2010-10-30 11:17:39,579 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'wmi:CC1A61AC-4256-41A3-
B9E0-05A445ADE2F5')
2010-10-30 11:17:39,579 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias',
'pci:v00008086d000027CBsv00001025sd00000110bc0Csc0 3i00')
2010-10-30 11:17:39,584 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias',
'pci:v00008086d000027C8sv00001025sd00000110bc0Csc0 3i00')
2010-10-30 11:17:39,588 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'platform:dock')
2010-10-30 11:17:39,589 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'input:b0011v0002p0007e12B1-
e0,1,3,k100,101,102,103,110,111,145,14A,14D,14E,ra 0,1,18,1C,mlsfw')
2010-10-30 11:17:39,590 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,590 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'joydev', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,590 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'joydev', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,590 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'wmi:AAE04F7B-B3C5-4865-95D6-9FAC7FF3E92B')
2010-10-30 11:17:39,590 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias',
'usb:v05E3p0608d0901dc09dsc00dp01ic09isc00ip00')
2010-10-30 11:17:39,599 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'wmi:653A064F-A23A-485F-B3D9-13F6532A0182')
2010-10-30 11:17:39,600 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'platform:Fixed MDIO bus')
2010-10-30 11:17:39,603 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias',
'pci:v00008086d000027DAsv00001025sd00000110bc0Csc0 5i00')
2010-10-30 11:17:39,607 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'i2c_i801', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,608 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'serio:ty01pr00id00ex00')
2010-10-30 11:17:39,622 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'serio_raw', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,622 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'psmouse', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,622 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'ssb:v4243id0812rev09')
2010-10-30 11:17:39,627 DEBUG: got handler firmware:b43([B43Handler, free, enabled] Broadcom B43
wireless driver)
2010-10-30 11:17:39,862 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'wmi:6AF4F258-B401-42FD-
BE91-3D4AC2D7C0D3')
2010-10-30 11:17:39,862 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias',
'pci:v00008086d000027CAsv00001025sd00000110bc0Csc0 3i00')
2010-10-30 11:17:39,871 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'input:b0019v0000p0006e0000-
e0,1,kE0,E1,E3,F1,F2,F3,F4,F5,ramlsfw')
2010-10-30 11:17:39,871 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'evbug', 'jockey_handler': 'KernelModuleHandler'}
2010-10-30 11:17:39,871 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias', 'wmi:36916B91-1A64-4583-84D0-53830FB9108D')
2010-10-30 11:17:39,871 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias',
'pci:v00008086d000027A6sv00001025sd00000110bc03sc8 0i00')
2010-10-30 11:17:39,872 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'input:b0003v1241p1177e0110-
e0,1,2,4,k110,111,112,r0,1,8,am4,lsfw')
2010-10-30 11:17:39,872 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'pci:v0000104Cd00008039sv00001025sd00000110bc06sc0 7i00')
2010-10-30 11:17:39,874 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias',
'pci:v000014E4d00004318sv00001468sd00000312bc02sc8 0i00')
2010-10-30 11:17:39,874 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'acpi:PNP0200:')
2010-10-30 11:17:39,875 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'acpi:LNXSYSTM:')
2010-10-30 11:17:39,875 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias',
'pci:v00008086d000027D8sv00001025sd00000110bc04sc0 3i00')
2010-10-30 11:17:39,875 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'platform:eisa')
2010-10-30 11:17:39,875 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00')
2010-10-30 11:17:39,875 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias',
'pci:v0000104Cd0000803Bsv00001025sd00000110bc01sc8 0i00')
2010-10-30 11:17:39,875 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'input:b0011v0001p0001eAB41-
e0,1,4,11,14,k71,72,73,74,75,77,79,7A,7B,7C,7D,7E, 7F,80,8A,8C,8D,8E,8F,94,95,9B,9C,9D,9E,9F,A3,A4,
A5,A6,AC,AD,B7,B8,B9,C0,C1,D9,E0,E1,E2,E3,EC,ED,EE ,1A9,1B2,1B3,1D0,ram4,l0,1,2,sfw')
2010-10-30 11:17:39,876 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'acpi:LNXSYBUS:')
2010-10-30 11:17:39,876 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias',
'pci:v00008086d000027B9sv00001025sd00000110bc06sc0 1i00')
2010-10-30 11:17:39,876 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'platformcspkr')
2010-10-30 11:17:39,876 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias',
'pci:v00008086d000027C9sv00001025sd00000110bc0Csc0 3i00')
2010-10-30 11:17:39,876 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'platform:regulatory')
2010-10-30 11:17:39,876 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'wmi:CFF94C79-6C77-4AF7-AC56-7DD0CE01C997')
2010-10-30 11:17:39,876 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias',
'pci:v00008086d000027A0sv00001025sd00000110bc06sc0 0i00')
2010-10-30 11:17:39,877 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'wmiB85B1A7-069A-4ABB-A2B5-D186A21B80F1')
2010-10-30 11:17:39,877 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'acpi:PNP0303:')
2010-10-30 11:17:39,877 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'acpi:PNP0C02:')
2010-10-30 11:17:39,877 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias',
'pci:v00008086d000027A2sv00001025sd00000110bc03sc0 0i00')
2010-10-30 11:17:39,877 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'acpi:device:')
2010-10-30 11:17:39,877 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'acpi:SYN1003:SYN1000:SYN0002:PNP0F13:')
2010-10-30 11:17:39,877 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'acpi:PNP0103:PNP0C01:')
2010-10-30 11:17:39,878 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'acpi:PNP0B00:')
2010-10-30 11:17:39,878 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'usb:v1241p1177d0270dc00dsc00dp00ic03isc01ip02')
2010-10-30 11:17:39,878 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias',
'pci:v000011ABd00004352sv00001025sd00000110bc02sc0 0i00')
2010-10-30 11:17:39,878 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias',
'pci:v00008086d00002448sv00001025sd00000110bc06sc0 4i01')
2010-10-30 11:17:39,878 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'input:b0019v0000p0001e0000-e0,1,k74,ramlsfw')
2010-10-30 11:17:39,878 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'input:b0019v0000p0005e0000-e0,5,kramlsfw0,')
2010-10-30 11:17:39,879 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'wmi:E78C4453-0227-4861-9EDE-F5600B4A3D39')
2010-10-30 11:17:39,879 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'acpi:LNXTHERM:')
2010-10-30 11:17:39,879 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'dmi:bvnAcer:bvrv1.3221:bd12/15
/06:svnAcer,inc.nAspire3680vrNotApplicable:rvnAcer,Inc.:rnPrespa1:rvrNotAppli cable:cvnAcer,Inc.
:ct1:cvrN/A:')
2010-10-30 11:17:39,879 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'wmi:79772EC5-04B1-4BFD-843C-61E7F77B6CC9')
2010-10-30 11:17:39,880 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'acpi:PNP0000:')
2010-10-30 11:17:39,880 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'wmi:95764E09-FB56-4E83-B31A-37761F60994A')
2010-10-30 11:17:39,882 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'input:b0019v0000p0003e0000-e0,1,k8E,ramlsfw')
2010-10-30 11:17:39,882 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'usb:v1D6Bp0002d0206dc09dsc00dp00ic09isc00ip00')
2010-10-30 11:17:39,883 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'usb:v1058p1010d0105dc00dsc00dp00ic08isc06ip50')
2010-10-30 11:17:39,883 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'acpi:PNP0100:')
2010-10-30 11:17:39,883 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'acpi:PNP0C04:')
2010-10-30 11:17:39,883 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias',
'pci:v00008086d000027CCsv00001025sd00000110bc0Csc0 3i20')
2010-10-30 11:17:39,883 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'usb:v0402p5602d0100dc00dsc00dp00icFFiscFFipFF')
2010-10-30 11:17:39,883 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'wmi:A7C9A0B7-4C9D-4C72-83BB-53A3459171DF')
2010-10-30 11:17:39,884 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'wmi:CC1A61AC-4256-41A3-B9E0-05A445ADE2F5')
2010-10-30 11:17:39,884 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias',
'pci:v00008086d000027CBsv00001025sd00000110bc0Csc0 3i00')
2010-10-30 11:17:39,884 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'pci:v00008086d000027C8sv00001025sd00000110bc0Csc0 3i00')
2010-10-30 11:17:39,884 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'platform:dock')
2010-10-30 11:17:39,884 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'input:b0011v0002p0007e12B1-
e0,1,3,k100,101,102,103,110,111,145,14A,14D,14E,ra 0,1,18,1C,mlsfw')
2010-10-30 11:17:39,884 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'wmi:AAE04F7B-B3C5-4865-95D6-9FAC7FF3E92B')
2010-10-30 11:17:39,884 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'usb:v05E3p0608d0901dc09dsc00dp01ic09isc00ip00')
2010-10-30 11:17:39,885 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'wmi:653A064F-A23A-485F-B3D9-13F6532A0182')
2010-10-30 11:17:39,885 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'platform:Fixed MDIO bus')
2010-10-30 11:17:39,885 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias',
'pci:v00008086d000027DAsv00001025sd00000110bc0Csc0 5i00')
2010-10-30 11:17:39,885 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'serio:ty01pr00id00ex00')
2010-10-30 11:17:39,885 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'ssb:v4243id0812rev09')
2010-10-30 11:17:39,885 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'wmi:6AF4F258-B401-42FD-BE91-3D4AC2D7C0D3')
2010-10-30 11:17:39,885 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias',
'pci:v00008086d000027CAsv00001025sd00000110bc0Csc0 3i00')
2010-10-30 11:17:39,886 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'input:b0019v0000p0006e0000-
e0,1,kE0,E1,E3,F1,F2,F3,F4,F5,ramlsfw')
2010-10-30 11:17:39,886 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance
at 0x93bf4cc> about HardwareID('modalias', 'wmi:36916B91-1A64-4583-84D0-53830FB9108D')
2010-10-30 11:18:28,888 DEBUG: Shutting down
tanya@acer-aspire-3680:~$

[GreyGeek]

Re: Wireless network not working after upgrade too 10.10

2010-10-30 11:17:37,956 DEBUG: loading custom handler /usr/share/jockey/handlers/sl_modem.py
2010-10-30 11:17:37,986 DEBUG: Instantiated Handler subclass __builtin__.SlModem from name SlModem
2010-10-30 11:17:38,034 DEBUG: Software modem is available
2010-10-30 11:17:38,034 DEBUG: loading custom handler /usr/share/jockey/handlers/broadcom_wl.py
2010-10-30 11:17:38,048 WARNING: modinfo for module wl failed: ERROR: modinfo: could not find module wl
2010-10-30 11:17:38,079 DEBUG: Instantiated Handler subclass __builtin__.BroadcomWLHandler from name BroadcomWLHandler
2010-10-30 11:17:38,079 DEBUG: Broadcom STA wireless driver availability undetermined, adding to pool
..
2010-10-30 11:17:39,576 DEBUG: no corresponding handler available for {'driver_type': 'kernel_module', 'kernel_module': 'gspca_m5602', 'jockey_handler': 'KernelModuleHandler'}
...
2010-10-30 11:17:39,622 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB instance at 0x91194ac> about HardwareID('modalias', 'ssb:v4243id0812rev09')
2010-10-30 11:17:39,627 DEBUG: got handler firmware:b43([B43Handler, free, enabled] Broadcom B43 wireless driver)
...
2010-10-30 11:17:39,885 DEBUG: querying driver db <jockey.detection.OpenPrintingDriverDB instance at 0x93bf4cc> about HardwareID('modalias', 'ssb:v4243id0812rev09')
...

Off hand, there are too many wireless modules being loaded, and the right one is out of order... can't elaborate right now -- time to go to the Halloween party.

The broadcom-wl driver (installed via Broadcom STA from the System --> Hardware Drivers) looks for these signatures, from /usr/share/jockey/modaliases/bcmwl:

# Listing generated by bcmwl_supported. Do not edit manually.
alias pci:v000014E4d00004311sv*sd*bc*sc*i* wl bcmwl-kernel-source
alias pci:v000014E4d00004312sv*sd*bc*sc*i* wl bcmwl-kernel-source
alias pci:v000014E4d00004313sv*sd*bc*sc*i* wl bcmwl-kernel-source
alias pci:v000014E4d00004315sv*sd*bc*sc*i* wl bcmwl-kernel-source
alias pci:v000014E4d00004328sv*sd*bc*sc*i* wl bcmwl-kernel-source
alias pci:v000014E4d00004329sv*sd*bc*sc*i* wl bcmwl-kernel-source
alias pci:v000014E4d0000432Asv*sd*bc*sc*i* wl bcmwl-kernel-source
alias pci:v000014E4d0000432Bsv*sd*bc*sc*i* wl bcmwl-kernel-source
alias pci:v000014E4d0000432Csv*sd*bc*sc*i* wl bcmwl-kernel-source
alias pci:v000014E4d0000432Dsv*sd*bc*sc*i* wl bcmwl-kernel-source
alias pci:v000014E4d00004353sv*sd*bc*sc*i* wl bcmwl-kernel-source
alias pci:v000014E4d00004357sv*sd*bc*sc*i* wl bcmwl-kernel-source
alias pci:v000014E4d00004727sv*sd*bc*sc*i* wl bcmwl-kernel-source

Your jockey messages supplied this:

2010-10-30 11:17:39,313 DEBUG: querying driver db <jockey.detection.LocalKernelModulesDriverDB
instance at 0x91194ac> about HardwareID('modalias',
pci:v000014E4d00004318sv00001468sd00000312bc02sc80i00')
2010-10-30 11:17:39,389 DEBUG: no corresponding handler available for {'driver_type':
'kernel_module', 'kernel_module': 'ssb', 'jockey_handler': 'KernelModuleHandler'}

which caused the kernel to load the wrong ssb module. The error msgs also said that the Broadcom STA driver wasn't being recognized. That's because it was NOT looking for your 4318, but for chips listed in the modalias/bcmwl file.


Take notice of this:
http://wireless.kernel.org/en/users/Drivers/b43

b43 and b43legacy

The b43 drivers (bcm43xx in mainline kernels, b43 and b43legacy in wireless-2.6 and 2.6.24 and later) are drivers for the 802.11 B/G family of wireless chips Broadcom produces. The choice of which driver your card uses depends on the revision level of the 802.11 core. This number is read by driver ssb, and the correct choice for your device is made at that point. Note: If your card is a BCM4306 Rev 2, or only has 802.11b capability, it uses b43legacy. All other models use b43.
...
The difference with broadcom-wl driver compared to b43/b43legacy is that broadcom-wl can only offer connection to AP or Ad-Hoc network, it does not offer AP modes and Monitor modes. Furthermore the driver does not corporate well with iw tools because it has its own ieee80211 stack that is both outdated and does not work with mac80211 stack which b43/b43legacy is based on.
...
Users/Owners of unsupported Broadcom device wanting more functionality/support out of wl driver will have no choice but to continue emailing Broadcom. There will be no support offered on either the mailing list or the IRC channel due to the fact that the driver is mainly a proprietary binary blob. This is not due to b43 developers' fault but Broadcom's own internal conflicts with the linux community.

So, the Broadcom STA wl driver is out. Then, there is this paragraph:

b43legacy should be used on all 4301 and 4303 cards. 4306 and 4309 cards with a MAC core revision of 4 or less should also use b43legacy. b43 should be used on all other cards. You can safely have both versions built on the same system. The full MAC core version is printed in the kernel logs when "SSB debugging" is enabled in KConfig and the driver finds a board. Type "dmesg" to see it. If you are unsure and don't know what we are talking about here, always build both b43 and b43legacy (and get firmware for both too). The kernel autoloader will automatically do the right thing and load the correct driver for your device.

Your wireless is a BCM4318 and will use the b43.ko module. The kernel loader apparently did NOT do the right thing with your setup, probably because the Broadcom STA drivers and wl, so we'll have to do it manually and then make it permanent.

You'll need the ethernet cable plugged into the back of your wireless and your laptop.

Use Synaptic to uninstall anything with "Broadcom 802.11 Linux STA wireless driver" in the description. Search for "broadcom" to find them. Make sure the b43-fwcutter was installed by using Synaptic to re-install it. It supplies b43. It should put a bunch of bcm* files and/or directory in /lib/firmware

Make sure the following are in /etc/modprobe.d/blacklist.conf
blacklist bcm43xx
blacklist b43
blacklist b43legacy
blacklist ssb
blacklist wl
blacklist gspca_m5602
blacklist gspca_main

so that they will NOT automatically get loaded by Upstart/HAL during boot up. These just prevent modules from automatically loading at boot but don't stop manual or subsequent scripts activity from loading and running them.

Then, clean up your system by doing

sudo rmmod b43
sudo rmmod b43legacy
sudo rmmod ssb
sudo rmmod lib20811_crypt_tkip
sudo rmmod lib20811
sudo rmmod wl

Now, at this point, if you do an "lsmod" in the console and inspect the output closely you should not see any of the wireless drivers mentioned above. If you do, use "sudo rmmod xxxxx", replacing xxxxx with the exact name of the driver, to remove it.

In a Konsole issue
sudo modprobe b43

That should turn on your wifi lamp, if your laptop has one.
iwlist scanning
should show wlan0
If it is disabled issue
sudo ifup wlan0
then repeat the iwlist scannning to see if you see any wifi access points listed under wlan0.
IF you see wlan0 listing access points then issue
sudo depmod -a
to make the list of loaded modules after boot up to include b43. Modprobe b43 should automatically load the ssb and 802* modules.
Now, us wicd to configure your wireless.

If this method does not work then we will use the ndiswrapper on the Windows drivers for this chip.

[snowflake_nz]

Re: Wireless network not working after upgrade too 10.10

Hi GreyGeek
I'll wait for your answer. Am going treak or treating with the toddler anyway too.
Enjoy the party - Halloween parties are always such fun.

Cheers

[snowflake_nz]

Re: Wireless network not working after upgrade too 10.10

Hi there GreyGeek

okay, back to work we go.
I followed the steps in your post, but nothing.
I'm eagerly awaiting the next steps with ndiswrapper.

I can confirm that there are no such problems with 10.04 (Kubuntu or Ubuntu). Wireless is stable after installing Broadcom b43 via Additional hardware. I've even shut down my laptop and connected it to the usb modem that I have in another room and wireless was stable. But with 10.10 it dies after the first reboot.

[GreyGeek]

Re: Wireless network not working after upgrade too 10.10

I'm not ready to give up yet.

In a Konsole issue:
kdesudo kate /var/lib/NetworkManager/NetworkManager.state

and put everything true

[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true

then restart the network:
sudo service networking stop
sudo service networking start

or
sudo ifconfig wlan0 down & sudo ifconfig wlan0 up

You can see all of your services with: service --status-all.
I installed sysv-rc-conf and start it in a Konsole as root. It gives me a service menu that lets me start of stop any service, or set any service to run at any run level.

[snowflake_nz]

Re: Wireless network not working after upgrade too 10.10

Hey there
thanks for sticking by me & trying to get this sorted. I've been so looking forward to working with Meerkat Maverick, but if I can't get wireless stable (because I don't always have the option of using my ethernet cable) I'll just have to fresh install Lynx again.

Anyhow, here's the output of what I get on all the above
tanya@acer-aspire-3680:~$ kdesudo kate /var/lib/NetworkManager/NetworkManager.state
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/tanya/.config/ibus/bus
Bus:pen: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
kate(3800)/kdecore (services) KMimeTypeFactory:arseMagic: Now parsing "/usr/share/mime/magic"
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.config/ibus/bus
Bus:pen: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
tanya@acer-aspire-3680:~$ sudo service networking stop
stop: Unknown instance:
tanya@acer-aspire-3680:~$ sudo service networking start
networking stop/waiting
tanya@acer-aspire-3680:~$ sudo ifconfig wlan0 down
tanya@acer-aspire-3680:~$
tanya@acer-aspire-3680:~$ sudo ifconfig wlan0 up
SIOCSIFFLAGS: Operation not possible due to RF-kill
tanya@acer-aspire-3680:~$ service --status-all
[ ? ] acpi-support
[ ? ] acpid
[ ? ] alsa-mixer-save
[ ? ] anacron
[ - ] apparmor
[ ? ] apport
[ ? ] atd
[ ? ] avahi-daemon
[ - ] bluetooth
[ - ] bootlogd
[ - ] brltty
[ ? ] console-setup
[ ? ] cron
[ ? ] cups
[ ? ] dbus
[ ? ] dmesg
[ ? ] dns-clean
[ ? ] failsafe-x
[ - ] fancontrol
[ - ] grub-common
[ ? ] hostname
[ ? ] hwclock
[ ? ] hwclock-save
[ ? ] irqbalance
[ ? ] kdm
[ - ] kerneloops
[ ? ] killprocs
[ - ] lm-sensors
[ ? ] module-init-tools
[ ? ] network-interface
[ ? ] network-interface-security
[ ? ] network-manager
[ ? ] networking
[ ? ] ondemand
[ ? ] pcmciautils
[ ? ] plymouth
[ ? ] plymouth-log
[ ? ] plymouth-splash
[ ? ] plymouth-stop
[ ? ] pppd-dns
[ ? ] procps
[ + ] pulseaudio
[ ? ] rc.local
[ - ] rsync
[ ? ] rsyslog
[ + ] saned
[ ? ] screen-cleanup
[ ? ] sendsigs
[ - ] sl-modem-daemon
[ ? ] stop-bootlogd
[ ? ] stop-bootlogd-single
[ ? ] sudo
[ ? ] udev
[ ? ] udev-finish
[ ? ] udevmonitor
[ ? ] udevtrigger
[ ? ] ufw
[ ? ] umountfs
[ ? ] umountnfs.sh
[ ? ] umountroot
[ ? ] unattended-upgrades
[ - ] urandom
[ - ] x11-common
tanya@acer-aspire-3680:~$ sudo apt-get install sysv-rc-conf
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libindicator0 libappindicator0 liboil0.3 libgupnp-igd-1.0-2
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
libcurses-perl libcurses-ui-perl
The following NEW packages will be installed:
libcurses-perl libcurses-ui-perl sysv-rc-conf
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 399kB of archives.
After this operation, 1,446kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://nz.archive.ubuntu.com/ubuntu/ maverick/universe libcurses-perl i386 1.28-1 [132kB]
Get:2 http://nz.archive.ubuntu.com/ubuntu/ maverick/universe libcurses-ui-perl all 0.9607-1 [243kB]
Get:3 http://nz.archive.ubuntu.com/ubuntu/ maverick/universe sysv-rc-conf all 0.99-6 [24.2kB]
Fetched 399kB in 2s (180kB/s)
Selecting previously deselected package libcurses-perl.
(Reading database ... 142765 files and directories currently installed.)
Unpacking libcurses-perl (from .../libcurses-perl_1.28-1_i386.deb) ...
Selecting previously deselected package libcurses-ui-perl.
Unpacking libcurses-ui-perl (from .../libcurses-ui-perl_0.9607-1_all.deb) ...
Selecting previously deselected package sysv-rc-conf.
Unpacking sysv-rc-conf (from .../sysv-rc-conf_0.99-6_all.deb) ...
Processing triggers for man-db ...
Setting up libcurses-perl (1.28-1) ...
Setting up libcurses-ui-perl (0.9607-1) ...
Setting up sysv-rc-conf (0.99-6) ...
tanya@acer-aspire-3680:~$ sysv-rc-conf
Can't create /var/lib/sysv-rc-conf : Permission denied at /usr/sbin/sysv-rc-conf line 454.
tanya@acer-aspire-3680:~$

[GreyGeek]

Re: Wireless network not working after upgrade too 10.10

....

Anyhow, here's the output of what I get on all the above
tanya@acer-aspire-3680:~$ kdesudo kate /var/lib/NetworkManager/NetworkManager.state
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/tanya/.config/ibus/bus
Bus:pen: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
kate(3800)/kdecore (services) KMimeTypeFactory:arseMagic: Now parsing "/usr/share/mime/magic"
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.config/ibus/bus
Bus:pen: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon

You can take a look at the attached photo to see what I get when use the command: "kdesudo kate /var/lib/NetworkManager/NetworkManager.state"

I take it that you couldn't open NetworkManager.state, even though it is there. Just do
sudo kate
and then use Kate's open file dialog to go to /var/lib/NetworkManager/NetworkManager.state
and open it. Then make sure all the equals are set to true and NOT false. Then save it.

tanya@acer-aspire-3680:~$ sudo service networking stop
stop: Unknown instance:
tanya@acer-aspire-3680:~$ sudo service networking start
networking stop/waiting
tanya@acer-aspire-3680:~$ sudo ifconfig wlan0 down
tanya@acer-aspire-3680:~$
tanya@acer-aspire-3680:~$ sudo ifconfig wlan0 up
SIOCSIFFLAGS: Operation not possible due to RF-kill

I.E. your network was not enabled. See NetworkManager.state above.

tanya@acer-aspire-3680:~$ service --status-all
......
[ ? ] module-init-tools
[ ? ] network-interface
[ ? ] network-interface-security
[ ? ] network-manager
[ ? ] networking

Here is what mine shows

[ ? ] network-interface
[ ? ] network-interface-security
[ ? ] networking

This tells me that you are using KNetworkManager. IMO, wicd is better, but lets get the NetworkManager.state settings right, then restart the network first.

.....
tanya@acer-aspire-3680:~$ sudo apt-get install sysv-rc-conf
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libindicator0 libappindicator0 liboil0.3 libgupnp-igd-1.0-2
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
libcurses-perl libcurses-ui-perl
The following NEW packages will be installed:
libcurses-perl libcurses-ui-perl sysv-rc-conf
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 399kB of archives.
After this operation, 1,446kB of additional disk space will be used.
....

sudo apt-get autoremove

will clear up that stuff.

Can't create /var/lib/sysv-rc-conf : Permission denied at /usr/sbin/sysv-rc-conf line 454.
tanya@acer-aspire-3680:~$

The correct command is
sudo sysv-rc-conf
but, lets hold off using that until the state problem is cleared. And, before we use ndiswrapper, IF we can't get KNetworkManager to work for you, we should try wicd.

[snowflake_nz]

Re: Wireless network not working after upgrade too 10.10

Hi GreyGeek
apologies. I thought I had removed Network manager and installed wicd (my preference too).
Anyhow, back to business
sudo kate has now been sorted and I've changes all to true and saved.

Here's the output of sudo kate /var/lib/NetworkManager/NetworkManager.state (I had to change all to true again after rebooting - so this is a vicious cycle)

tanya@acer-aspire-3680:~$ sudo kate /var/lib/NetworkManager/NetworkManager.state[sudo] password for tanya:
Sorry, try again.
[sudo] password for tanya:
Error: "/var/tmp/kdecache-tanya" is owned by uid 1000 instead of uid 0.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QStr ing,QString,QString)
Error: "/var/tmp/kdecache-tanya" is owned by uid 1000 instead of uid 0.
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewIn stance()
kbuildsycoca4 running...
Error: "/var/tmp/kdecache-tanya" is owned by uid 1000 instead of uid 0.
kbuildsycoca4(2988) KConfigGroup::readXdgListEntry: List entry text/html in "/home/tanya/.local/share/applications/mimeapps.list" is not compliant with XDG standard (missing trailing semicolon).
Error: "/var/tmp/kdecache-tanya" is owned by uid 1000 instead of uid 0.
kate(2894)/kdecore (services) KMimeTypeFactory:arseMagic: Now parsing "/usr/share/mime/magic"
kate(2894)/kdecore (services) KMimeTypeFactory:arseMagic: Now parsing "/home/tanya/.local/share/mime/magic"
Bus:pen: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
kate(2894)/kdecore (services) KMimeTypeFactory:arseMagic: Now parsing "/usr/share/mime/magic"
kate(2894)/kdecore (services) KMimeTypeFactory:arseMagic: Now parsing "/home/tanya/.local/share/mime/magic"
klauncher(2980)/kio (KLauncher): SlavePool: No communication with slave.

klauncher(2980)/kio (KLauncher): SlavePool: No communication with slave.

tanya@acer-aspire-3680:~$

I don't really want to give up on this, but it's doing my head in. I'm really thinking of going back to 10.04, luckily it's LTS until 2013!!

[dibl]

Re: Wireless network not working after upgrade too 10.10

tanya@acer-aspire-3680:~$ sudo kate /var/lib/NetworkManager/NetworkManager.state[sudo]

[BUTTING IN]

Oh geez you guys, pleeeeeeeeeze don't use "sudo" with a KDE (or Gnome) package -- you will bork your user's ability to log in to X.

Do Alt-F2 "kdesudo kate" and then browse to whichever file you need to edit with root privileges.

[/BUTTING IN]

[snowflake_nz]

Re: Wireless network not working after upgrade too 10.10

Hi Dibl

thanks for 'butting in' (as you put it). I just use sudo because that's what I used with Ubuntu (since 2008), seems that some habits are real hard to break.
Have now made a not of ALT-F2 'kdesudo kate' and put it on a post-it note by my laptop ;-)

[GreyGeek]

Re: Wireless network not working after upgrade too 10.10

tanya@acer-aspire-3680:~$ sudo kate /var/lib/NetworkManager/NetworkManager.state[sudo]

[BUTTING IN]

Oh geez you guys, pleeeeeeeeeze don't use "sudo" with a KDE (or Gnome) package -- you will bork your user's ability to log in to X.

Do Alt-F2 "kdesudo kate" and then browse to whichever file you need to edit with root privileges.

[/BUTTING IN]

THANKS FOR THE CATCH, Dibl.... I knew to use kdesudo with KDE apps, but I use a konsole more now than I ever used to use in the past and most uses don't involve using Kapps, so I thoughtlessly told her to use "sudo".

Naughty fingers! Naughty, Naughty!! Slap, slap, slap...
(Too bad they can't read what I'm thinking...)

[snowflake_nz]

Re: Wireless network not working after upgrade too 10.10

And that is why I just love spending some free time on these forums . . . you guys know how to make me laugh out loud LOL.
Perhaps my many grey hair could be blocking my thinking side of the brain

[GreyGeek]

Re: Wireless network not working after upgrade too 10.10

.....
Perhaps my many grey hair could be blocking my thinking side of the brain

I could use that as my excuse but at the rate they are falling out it won't be long before I won't be able to use it, so I'll just continue to blame the real cause, NutraSweet, which is no joke.

So, as I read your last msg, you changed the states of the three lines to "true" but on rebooting they were changed back. That is probably because Upstart (HAL's replacement) didn't make a match between your broadcom 4318 and the b43 driver, which it should have. You should have put all of the suspect wireless drivers in the blacklist.conf file so that Upstart will ignore them. Perchance, on your next reboot, do a
lsmod | grep cfg80211
and see what wireless driver it is using. Mine shows this:

...:~$ lsmod | grep cfg80211
cfg80211 148725 3 iwlagn,iwlcore,mac80211
...:~$

but yours will show something else. ("modinfo iwlagn" shows that iwlagn depends on the three listed above being loaded first, and "modprobe iwlagn" automatically loads the dependencies before it installs iwlagn.)

You will be able to tell if another wireless driver is being loaded because it will most likely require cfg80211 OR mac80211 (so "lsmod | grep mac80211" will also reveal the wireless driver being used).

If you find a wireless driver then add it to the list of driver in /etc/modprobe.d/blacklist.conf:
blacklist bcm43xx
blacklist b43
blacklist b43legacy
blacklist ssb
blacklist wl
blacklist gspca_m5602
blacklist gspca_main

If you don't see either the mac80211 or the cfg80211 drivers present in the lsmod listing then a wireless driver isn't being loaded. In that case making sure that
/var/lib/NetworkManager/NetworkManager.state
holds only

[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true

and doing

sudo modprobe b43

followed by

sudo service networking stop
sudo service networking start

should cause your wireless light to come on, if you PC has a wireless light indicating activity. KNetworkManager should be able to manage your connection and allow you to connect using your ESSID and password.

If it works and you can make a connection then open a konsole and issue
sudo depmod -a
which will make the current mod list permanent.

IF KNetworkManager fails then it is time to switch to wicd. Here's how:

Use apt-get or Synaptic to install
python-urwid
python-wicd
wicd
wicd-cli
wicd-curses
wicd-daemon
wicd-gtk

The last four will give you the ability to make network connections from a console, even without KDE running.

Now, completely removed the following packages:
network-manager
knm-runtime
plasma-widget-networkmanagement

Then, reboot and run
sudo apt-get autoremove
to remove all other apps dependent on network-manager.

Run wicd and see if it can show access points to log into. If it can, choose yours, add the necessary type and password info and connect.

If you can't see any access points being listed, then run
sudo lsmod | grep mac80211
to see if b43 is in the resulting list. If it is we'll have to go to the ndiswrapper. If it is not, then something is amiss with depmod or your blacklist.conf file.
If b43 is not in the lsmod listing then run
sudo modprobe b43
and then run wicd again to see if it gives a list of access points. If it does then connect to yours and we'll figure out later how to make it permanent. If it doesn't then it is time for the ndiswrapper. (IF your Maverick CD has checked out OK).

[snowflake_nz]

Re: Wireless network not working after upgrade too 10.10

I laughed so loudly about the hair falling out, I think my family thought I was truly insane LOL.

Output for lsmod | grep cfg80211:
tanya@acer-aspire-3680:~$ lsmod | grep cfg80211
cfg80211 144470 2 b43,mac80211

I've installed the wicd and un-installed network manager.
Just rebooted and . . . nothing.

As for the Maverick CD, I didn't use the cd. I updated from 10.04

Hope this helps somehow