13.04 - marvell driver bugs- surface pro w/ avastar 350N

Bug #1173673 reported by Steve Novakov
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I would like to comment that I did not spend a lot of time debugging this due to time constraints. Then again, something like this should probably work out of the box.

Upon installing the 13.04 beta2 (about 1-2 weeks ago, whatever release that was), I attempted to use the wifi on my MS surface pro. This was a fresh install, I re-formatted the partition of the hard drive that ubuntu sits on. I downloaded updates, etc, via a usb-ethernet interface.

The wifi widget in the top right hand corner shows 3 active instances of the wireless network interface for the marvell chip.

http://i.imgur.com/Y2vTdFd.png

 When switching the wireless functionality to ON, they seem to be competing with each other. All 3 of them show that they see the surrounding wifi networks but I can never actually get a connection. I get a prompt for the network password, I enter it, and then 1-2 seconds later I get another prompt, ad nauseum. I am not simply mis-typing the password. I remember seeing this behaviour before when I was trying to kluge together a working wifi driver with a 12.04 installation on my surface pro by grabbing the marvell driver packages from the 13.04 beta and manually implementing them. This suggests to me that there is something wrong with the driver for that particular chipset, rather than an installation error on my end. Though, I could be wrong.

Thanks

affects: ubuntu → network-manager (Ubuntu)
Revision history for this message
Elliot Saba (staticfloat) wrote :

I am also seeing this issue on 13.04 final. I can't connect to open networks either. Any solutions?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Steve Novakov, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1173673
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: network-manager (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Tony S. Hariman (thariman) wrote :

I open a Bug #1212720 so far the patch work on the latest saucy daily.

Revision history for this message
Steve Novakov (stevenovakov) wrote :

Hi Tony. I read through But #1212720, thanks. Just to confirm, I should grab saucy daily, and jsalisbury's test kernel and all my problems will disappear, correct?

Revision history for this message
Tony S. Hariman (thariman) wrote :

Hi Steve,

Yes the wifi work fine directly from the network-manager. I tried it on open network and WPA2 network.
I tested using http://cdimage.ubuntu.com/daily-live/current/saucy-desktop-amd64.iso dated 20130822

Tony

Revision history for this message
Steve Novakov (stevenovakov) wrote :

Sorry, just to be explicit: you did use jsalisbury's test kernel build or no?

Revision history for this message
Tony S. Hariman (thariman) wrote :

Yes installed saucy desktop. Reboot. Download via usb ethernet or copy from usb thumb drive. Install the kernel using sudo dpkg -i *.deb and reboot.

Revision history for this message
Tony S. Hariman (thariman) wrote :
Revision history for this message
Steve Novakov (stevenovakov) wrote :

Thank you for the confirmation. Cheers.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.