Biff, thanks.
I had already tried this but forgot to say in the first post. As I have reinstalled WattOS since then, I tried again with the same result. What it actually does is install a 3.2.0-4 kernel and this then appears in the grub menu. I don't really understand the line that starts "apt-get install...". So, I'm not sure what was going on but it is repeatable.
What happened as I followed the instructions was that, when I got to the "modprobe wl" bit, I got the same error as mentioned in my first post. As the process had loaded a new kernel, I tried rebooting into it. It didn't load any wireless drivers and when I typed "modprobe wl" I got the same error yet again. By the way, just to be clear, I did use sudo each time to get modprobe to do anything, although it doesn't appear in the instructions.
Going back to Debian as the basis for WattOS may have its merits but it seems that you may have thrown the baby out with the bath water. At least Lubuntu gets wireless drivers to work. I had high hopes for WattOS but, if you don't actually know how to get the Broadcom wireless drivers to work and no one else on this forum does, I know from experience I could spend many hours on this and still get nowhere. I know from the lspci command that my hardware is found and correctly identified but I don't know what happens next and how to troubleshoot it. The system just seems to ignore it and doesn't give any hints. I don't know what libkmod is and why it throws up the error it does. I don't know why the Debian Wheezy instructions install a different kernel and still don't seem to make any difference to the wireless drivers. If no one out there can help me, I'm probably better giving up now rather than wasting a lot of time...
