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.
** This bug is no longer a duplicate of bug 1165938
1286:2044 [Microsoft Surface Pro] Marvell 88W8797 wifi does not work
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1173673
Title:
13.04 - marvell driver bugs- surface pro w/ avastar 350N
Status in “linux” package in Ubuntu:
Incomplete
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173673/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
