in contrast to my hardware:
lspci -k|grep -i --after-context=3 network
03:00.0 Network controller: RaLink RT2860
Subsystem: Foxconn International, Inc. Device e002
Kernel driver in use: rt2860
Kernel modules: rt2860sta, rt2800pci
Which means the rt2860sta does not offer itself for your RaLink Device 3060. Which means the standard workaround (switching to the rt2860sta module) most people here are using will not work for you.
>Error - MCU request failed, no response from hardware
Afair I have seen that one in my syslog when rt2800pci worked, so I think that error is no show stopper.
Also I do not see:
"Error - PBF system register not ready."
which seems to be the core of this bug here.
I think it would be best if you made a new bug report (with "ubuntu-bug linux") after a fresh cold start and connection attempt. Maybe someone can then see from your logs where this fails for you.
Simão, your problem looks quite a bit different:
>04:06.0 Network controller: RaLink Device 3060
...
>Kernel modules: rt2800pci
in contrast to my hardware:
lspci -k|grep -i --after-context=3 network
03:00.0 Network controller: RaLink RT2860
Subsystem: Foxconn International, Inc. Device e002
Kernel driver in use: rt2860
Kernel modules: rt2860sta, rt2800pci
Which means the rt2860sta does not offer itself for your RaLink Device 3060. Which means the standard workaround (switching to the rt2860sta module) most people here are using will not work for you.
>Error - MCU request failed, no response from hardware
Afair I have seen that one in my syslog when rt2800pci worked, so I think that error is no show stopper.
Also I do not see:
"Error - PBF system register not ready."
which seems to be the core of this bug here.
I think it would be best if you made a new bug report (with "ubuntu-bug linux") after a fresh cold start and connection attempt. Maybe someone can then see from your logs where this fails for you.