Hi Ralph,
On 26 February 2011 01:21, Ralph Corderoy <ra...@inputplus.co.uk> wrote:
>
>> $ lspci -vmmnn | awk 'BEGIN {RS = ""}
>> /Vendor:[^[]+*\[14e4\]/ {print $0, "\n"}'
>> Slot: 00:0a.0
>> Class: Network controller [0280]
>> Vendor: Broadcom Corporation [14e4]
>> Device: BCM4306 802.11b/g Wireless LAN Controller [4320]
>> SVendor: Wistron NeWeb Corp. [185f]
>> SDevice: Device [1220]
>> Rev: 03
>
> Discussion on #dorset, particularly thanks to John Carlyle-Clarke,
> suggested that this is supported by the b43 driver. This was based on
> http://wireless.kernel.org/en/users/Devices/PCI, select PCI vendor of
> 0x14e4 and PCI product 0x4320 to filter. Then looking for a PCI
> Subvendor of 0x185f (based on your output above) gives just one match,
>
> Form PCI PCI PCI PCI
> Driver Vendor Product factor vendor product subvendor subsystem
> b43 Linksys WMP54G PCI 0x14e4 0x4320 0x185f 0x1220
OK.
> and that matches on the PCI Subsystem too.
That sounds hopeful then.
> Then http://wireless.kernel.org/en/users/Drivers/b43#Known_PCI_devices
> has three entries for 14e4:4320. One's USB and can be ignored. The
> other two vary depending on the chip you have; BCM4306/2 or BCM4306/3.
> We guess that the `Rev: 03' you machine gives above means you've the
> latter. The Modes and PHY version being `?' is somewhat disconcerting
> but documentation is so often out of date. :-)
Yes, that's slightly irritating, but everyone hates doing documentation :-(
>> there's a lovely little switch on the laptop that turns the Wi-Fi on
>> and off...
>> ...
>> So I suppose that I've actually asked the wrong question, what I
>> should have asked is "How do I find out what input / signal the
>> processor sees when I press the shiny button
>
> Consensus was that this bit will "just work". These buttons tend to be
> part of ACPI. Pressing them will cause an interrupt that filters up
> through the kernel and pops out into userspace, probably through
> /proc/acpi/event where it will cause something appropriate to happen.
> As a start to checking this you could do
>
> cat /proc/interrupts
>
> then press and release the button and then repeat that command. Has the
> count of the number of interrupts increased by one for any likely
> looking interrupt source?
Here is the complete printout of the second call to /proc/interrupts,
followed by some lines from a spreadsheet I copied the data into that
show different counts. (Yes I know I could have piped the commands
into sed or awk, or some other CLI, but I'm damned if I know how to
extract the data I want, so I did it my way !!).
peter@peter-laptop:~$ cat /proc/interrupts
CPU0
0: 29 IO-APIC-edge timer
1: 5851 IO-APIC-edge i8042
6: 5 IO-APIC-edge floppy
7: 1 IO-APIC-edge parport0
8: 0 IO-APIC-edge rtc0
9: 26187 IO-APIC-fasteoi acpi
10: 0 IO-APIC-edge wbsd
12: 1123 IO-APIC-edge i8042
14: 45555 IO-APIC-edge pata_via
15: 183312 IO-APIC-edge pata_via
16: 21993 IO-APIC-fasteoi radeon
17: 0 IO-APIC-fasteoi yenta
18: 0 IO-APIC-fasteoi yenta
19: 2 IO-APIC-fasteoi ohci1394
20: 192706 IO-APIC-fasteoi eth0
21: 146458 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2,
uhci_hcd:usb3, uhci_hcd:usb4
22: 143 IO-APIC-fasteoi VIA82XX-MODEM, VIA8233
NMI: 0 Non-maskable interrupts
LOC: 3497801 Local timer interrupts
SPU: 0 Spurious interrupts
PMI: 0 Performance monitoring interrupts
PND: 0 Performance pending work
RES: 0 Rescheduling interrupts
CAL: 0 Function call interrupts
TLB: 0 TLB shootdowns
TRM: 0 Thermal event interrupts
THR: 0 Threshold APIC interrupts
MCE: 0 Machine check exceptions
MCP: 42 Machine check polls
ERR: 1
MIS: 0
1 5842 IO-APIC-edge i8042 1 5851
IO-APIC-edge i8042 9
9 26123 IO-APIC-fasteoi acpi 9 26187
IO-APIC-fasteoi acpi 64
14 45465 IO-APIC-edge pata_via 14 45555
IO-APIC-edge pata_via 90
15 182754 IO-APIC-edge pata_via 15 183312
IO-APIC-edge pata_via 558
16 21719 IO-APIC-fasteoi radeon 16 21993
IO-APIC-fasteoi radeon 274
20 192336 IO-APIC-fasteoi eth0 20 192706
IO-APIC-fasteoi eth0 370
21 144650 IO-APIC-fasteoi ehci_hcd = Usb1 – uhci_hcd = usb2 – uhci_hcd
= usb3 – uhci_hcd = usb4 21 146458 IO-APIC-fasteoi
ehci_hcd = Usb1 –
uhci_hcd = usb2 – uhci_hcd = usb3 – uhci_hcd = usb4 1808
It strikes me that the obvious line of interest is second one since
that mentions "acpi", I'm just not sure why that line has seen 64
changes, although I did finish reading Ralph's comments between first
and second runs of the command.
If anyone wants me send them the whole spreadsheet, then I can do so.
I'm attaching a PDF of part of the spreadsheet since the formatting is
totally messed up on my screen, lack of mono-spaced font in gmail non
RTF format.
--
Cheers Peter
--
Next meeting: Blandford Forum, Wednesday 2011-03-02 20:00
Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/
How to Report Bugs Effectively: http://goo.gl/4Xue
