I have not taken a look at the code for Hardware Drivers (jockey I think) in a while, but it sounds like the activation might have just unloaded and reloaded the module. I could be wrong though.
Ubuntu addict and loving it
I have not taken a look at the code for Hardware Drivers (jockey I think) in a while, but it sounds like the activation might have just unloaded and reloaded the module. I could be wrong though.
Spilled the Beans
I wouldn't be surprised. I had previously gotten fwcutter on my machine, but without being able to get wl_apsta-3.130.20.0.o, it couldn't work fully. Once I had all the files, it worked like a charm.Originally Posted by Ayuthia
John
Frothy Coffee!
Hi, I seem to be having a similar problem. Activating it with the restricted driver manager did not work so I built fw cutter as per the instructions and copied the firmware to /lib/firmware/ yet it still won't find my network. iwlist eth1 scan says nothing found. Any idea what else I can do?
Ubuntu addict and loving it
Can you post the results of:
It will help us identify which chipset you are using along with giving us some information about what you wireless card is trying to use.Code:lspci -nn lshw -C network
Adv Reply
Bookmarks