[Kernel-packages] [Bug 1173673] Re: 13.04 - marvell driver bugs- surface pro w/ avastar 350N
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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: Expired 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
[Kernel-packages] [Bug 1173673] Re: 13.04 - marvell driver bugs- surface pro w/ avastar 350N
Thank you for the confirmation. Cheers. -- 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
[Kernel-packages] [Bug 1173673] Re: 13.04 - marvell driver bugs- surface pro w/ avastar 350N
download kernel http://kernel.ubuntu.com/~jsalisbury/lp1212720/ -- 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
[Kernel-packages] [Bug 1173673] Re: 13.04 - marvell driver bugs- surface pro w/ avastar 350N
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. -- 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
[Kernel-packages] [Bug 1173673] Re: 13.04 - marvell driver bugs- surface pro w/ avastar 350N
Sorry, just to be explicit: you did use jsalisbury's test kernel build or no? -- 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
[Kernel-packages] [Bug 1173673] Re: 13.04 - marvell driver bugs- surface pro w/ avastar 350N
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 -- 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
[Kernel-packages] [Bug 1173673] Re: 13.04 - marvell driver bugs- surface pro w/ avastar 350N
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? -- 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
[Kernel-packages] [Bug 1173673] Re: 13.04 - marvell driver bugs- surface pro w/ avastar 350N
I open a Bug #1212720 so far the patch work on the latest saucy daily. -- 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
[Kernel-packages] [Bug 1173673] Re: 13.04 - marvell driver bugs- surface pro w/ avastar 350N
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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
[Kernel-packages] [Bug 1173673] Re: 13.04 - marvell driver bugs- surface pro w/ avastar 350N
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