My first goal is to gather info about the wireless device on the Surface Pro 2. The wireless card, chipset, drivers needed. This in itself has been a mission…
Second goal is to install whatever is needed to be able to use wifi after identifying what is missing in openSUSE (or what is not recognized??)
When I entered /sbin/lspci the results did not show a network controller. The first entry was:
00:00.0 Host bridge: Intel Corporation Device 0a0c (rev 0b)
Followed by the USB controller, communication controller, audio device, etc…
I have also tried to find anything regarding a wireless device through Yast. Yast -> Hardware ->Hardware Information…
So following deltaflyer44’s list in http://forums.opensuse.org/showthread.php/309432-Welcome I cannot provide info on 1-5. For 6) I am using openSUSE 13.1. Like before, 7) did not turn up anything about a network controller. And for 8) it is not a USB device.
On 04/06/2014 03:46 PM, User1020 wrote:
>
> As of yesterday I had success installing openSUSE 13.1 onto a Surface
> Pro 2. (http://tinyurl.com/ln35drx!) I knew before even installing the
> OS that there would be issues with using wifi. I will try to include as
> much info as I can but bare with me, considering my knowledge of Linux
> is extremely limited.My first goal is to gather info about the wireless
> device on the Surface Pro 2. The wireless card, chipset, drivers needed.
> This in itself has been a mission… Second goal is to install whatever
> is needed to be able to use wifi after identifying what is missing in
> openSUSE (or what is not recognized??)
> http://forums.opensuse.org/showthread.php/309432-Welcome
> http://tinyurl.com/kevyojf I am trying to follow the guidelines of the
> above threads to provide useful information so that someone can help me.
> Unfortunately I am having trouble locating a lot of the info. In the
> second thread lwfinger says:When I entered /sbin/lspci the results did
> not show a network controller. The first entry was:00:00.0 Host bridge:
> Intel Corporation Device 0a0c (rev 0b)Followed by the USB controller,
> communication controller, audio device, etc… I have also tried to
> find anything regarding a wireless device through Yast. Yast → Hardware
> ->Hardware Information… So following deltaflyer44’s list in
> http://forums.opensuse.org/showthread.php/309432-Welcome I cannot
> provide info on 1-5. For 6) I am using openSUSE 13.1. Like before, 7)
> did not turn up anything about a network controller. And for 8) it is
> not a USB device.As far as I can tell, both the Surface Pro 1 and the
> Surface Pro 2 use the Marvell AVASTAR 350N wireless chipset.
> http://tinyurl.com/k9c4mk5http://tinyurl.com/ks7k3ugI guess the only
> useful information I have is: Surface Pro 2 openSUSE 13.1 Marvell 350N
> chipset Which isn’t very helpful =/(I apologize for the jumbled post,
> for some reason the formatting did not work…)
This sort of rambling post is exactly the reason that we prefer direct cut and
paste of computer output over a “story”. The links to previous forum info are
not very helpful. In addition, you managed to run two TinyURL links together
here so as to prevent clicking on them. It took a while to sort that out - I
just thought you has messed up the URL.
The second one of those had some useful info. The device is connected by USB,
which explains why it did not show up in the lspci listing. Although it is
internal, it is not PCI.
Microsoft’s putting a Marvell chip in that Surface is what I would expect for a
company that is doing everything they can to prevent people from running Linux.
Marvell has no presence in the Linux driver business, and getting a native Linux
driver for that chip is unlikely. You might be able to use ndiswrapper with the
Windows driver, but as many of the Windows users are having problems with that
driver, I am not certain that you will get anywhere. The specs say that the SP2
has a USB 3.0 port. I would recommend that you buy an external USB wifi device
that is supported by Linux.
Please use CODE tags around copied/pasted computer text. It is the # button in the tool bar of the post editor. And whenever applicable copy/paste the prompt, the command, the output and the next prompt between the tags. This will show others who you was (root/user), were you were (working directory), what you typed and what you got without much further explanation.
Thanks for the replies. I will keep things brief here on out.
I went ahead and got a usb wireless adapter. Trendnet N300 TEW-664UB. Everywhere I read said it was Linux compatible. I’ll have to figure out the driver installation still.
I still want to give ndiswrapper a try. I am having trouble identifying the wireless device. If its usb then which of the following is the marvell chipset?
The output for lsusb:
/usr/bin/lsusb
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 019: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09
Bus 002 Device 004: ID 045e:0799 Microsoft Corp.
Bus 002 Device 005: ID 03eb:8209 Atmel Corp.
Bus 002 Device 006: ID 045e:0794 Microsoft Corp.
Bus 002 Device 007: ID 045e:0795 Microsoft Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Scratch what I posted before. For some reason lsusb showed the marvell device and the trendnet adapter this time.
lsusb
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 023: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 002 Device 026: ID 1286:2044 Marvell Semiconductor, Inc.
Bus 002 Device 004: ID 045e:0799 Microsoft Corp.
Bus 002 Device 005: ID 03eb:8209 Atmel Corp.
Bus 002 Device 006: ID 045e:0794 Microsoft Corp.
Bus 002 Device 007: ID 045e:0795 Microsoft Corp.
Bus 003 Device 004: ID 05e3:0612 Genesys Logic, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 027: ID 20f4:664b TRENDnet
Bus 002 Device 025: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09
On 04/17/2014 12:46 PM, User1020 wrote:
>
> lwfinger;2635477 Wrote:
>> On 04/06/2014 03:46 PM, User1020 wrote:
>> The second one of those had some useful info. The device is connected by
>> USB,
>> which explains why it did not show up in the lspci listing. Although it
>> is
>> internal, it is not PCI.
>>
>
> Thanks for the replies. I will keep things brief here on out.
> I went ahead and got a usb wireless adapter. Trendnet N300 TEW-664UB.
> Everywhere I read said it was Linux compatible. I’ll have to figure out
> the driver installation still.
> I still want to give ndiswrapper a try. I am having trouble identifying
> the wireless device. If its usb then which of the following is the
> marvell chipset?
>
> The output for lsusb:
>
> /usr/bin/lsusb
> Bus 001 Device 002: ID 8087:8000 Intel Corp.
> Bus 002 Device 019: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09
> Bus 002 Device 004: ID 045e:0799 Microsoft Corp.
> Bus 002 Device 005: ID 03eb:8209 Atmel Corp.
> Bus 002 Device 006: ID 045e:0794 Microsoft Corp.
> Bus 002 Device 007: ID 045e:0795 Microsoft Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
None of those USB ID’s match any TEW-664UB that I know about. Version one has an
ID of 148f:2870 and uses driver rt2800usb. V2.0r has ID 20f4:664b and has a
Realtek RTL8192DU chip. That driver is not yet in the kernel, but there is a git
repo at GitHub that has the code that is being prepared. Are you sure the device
was plugged in when you ran lsusb?
On 04/17/2014 01:56 PM, User1020 wrote:
>
> Scratch what I posted before. For some reason lsusb showed the marvell
> device and the trendnet adapter this time.
>
> lsusb
> Bus 001 Device 002: ID 8087:8000 Intel Corp.
> Bus 002 Device 023: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
> Bus 002 Device 026: ID 1286:2044 Marvell Semiconductor, Inc.
> Bus 002 Device 004: ID 045e:0799 Microsoft Corp.
> Bus 002 Device 005: ID 03eb:8209 Atmel Corp.
> Bus 002 Device 006: ID 045e:0794 Microsoft Corp.
> Bus 002 Device 007: ID 045e:0795 Microsoft Corp.
> Bus 003 Device 004: ID 05e3:0612 Genesys Logic, Inc.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 002 Device 027: ID 20f4:664b TRENDnet
> Bus 002 Device 025: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09
You definitely have a V2 of the device, and you have lousy luck in selecting
devices with built-in drivers in Linux. You need to follow the stuff on how to
obtain and build the driver using the instructions at http://www.linux-hardware-guide.com/2013-11-16-trendnet-tew-664ub-300-mbps-usb-wifi-adapter-802-11n.
Of course, the “apt-get” part of the command will not work with openSUSE. You
need to replace that with
sudo zypper install make gcc kernel-devel
As I never need to set up a kernel development environment without the full
kernel sources, I probably missed something. One of the experts on that topic
will help.
Lousy luck indeed. Well, I have no idea how to build drivers but I’ll attempt to understand it. It may just be all around easier to get a different wireless adapter. I didn’t realize openSUSE would have preinstalled drivers for certain wireless devices.
On Thu 17 Apr 2014 07:31:14 PM CDT, Larry Finger wrote:
As I never need to set up a kernel development environment without the
full kernel sources, I probably missed something. One of the experts on
that topic will help.
Hi Larry
Is it worthwhile creating an OBS project (I can do it in my home repo
for the moment) to build kmp’s pulled from your git repo, or are there
potential license issues?
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-7-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
> On Thu 17 Apr 2014 07:31:14 PM CDT, Larry Finger wrote:
>
> As I never need to set up a kernel development environment without the
> full kernel sources, I probably missed something. One of the experts on
> that topic will help.
>
> Hi Larry
> Is it worthwhile creating an OBS project (I can do it in my home repo
> for the moment) to build kmp’s pulled from your git repo, or are there
> potential license issues?
The only problem is that the driver sources have never been merged into the
kernel. It is not difficult to do, but I don’t have the time at the moment. In
addition, it needs considerable work to be in kernel “style” and I do not want
any half-prepared kernel version floating on the net.
I could boot the standard kernel and build with it; however, the driver would
break as soon as there is an update, and I certainly would not want to do that
on a regular basis.
On 04/17/2014 02:56 PM, User1020 wrote:
>
> Lousy luck indeed. Well, I have no idea how to build drivers but I’ll
> attempt to understand it. It may just be all around easier to get a
> different wireless adapter. I didn’t realize openSUSE would have
> preinstalled drivers for certain wireless devices.
There are preinstalled drivers in openSUSE for everything that is in the kernel
that is chosen for that release. Of course, that is a moving target. For
example, I have personally submitted drivers for 3 new devices since kernel
3.10, and there are 3 more that I am currently getting ready for submission.
It is your bad luck to have selected a rare device that no one has cared enough
to write a Linux driver, and another one that is so new that the driver is not
yet in the kernel.
Of course, you may select another wireless device; however, I think you will be
happy with the RTL8192DU once you get the driver built. Most of my testing has
been with the 5G radio, but I have had a 48-hour period without a single
connection drop.
From what I understand, the trendnet adapter works very well with only the drawback of range, which isn’t a problem. Originally, I was going to go with the edimax EW-7718Un but it is out of stock everywhere. Apparently it would have run out of the box with linux. Anyhow, let’s put trendnet on the back burner for now because I’m lacking the patience to learn how to build a driver at the moment. Do you know of any tutorials for installing ndiswrapper on openSUSE 13.1? Preferably one that caters towards Linux newbies. I figure trying to get the marvell chipset working is worth a shot. I looked for the guide here: ndiswrapper download | SourceForge.net but the link does not work…
On 04/17/2014 04:26 PM, User1020 wrote:
>
> lwfinger;2637586 Wrote:
>> On 04/17/2014 02:56 PM, User1020 wrote:
>>
>> There are preinstalled drivers in openSUSE for everything that is in the
>> kernel
>> that is chosen for that release. Of course, that is a moving target. For
>> example, I have personally submitted drivers for 3 new devices since
>> kernel
>> 3.10, and there are 3 more that I am currently getting ready for
>> submission.
>>
>> It is your bad luck to have selected a rare device that no one has cared
>> enough
>> to write a Linux driver, and another one that is so new that the driver
>> is not
>> yet in the kernel.
>>
>> Of course, you may select another wireless device; however, I think you
>> will be
>> happy with the RTL8192DU once you get the driver built. Most of my
>> testing has
>> been with the 5G radio, but I have had a 48-hour period without a single
>> connection drop.
>
> From what I understand, the trendnet adapter works very well with only
> the drawback of range, which isn’t a problem. Originally, I was going to
> go with the edimax EW-7718Un but it is out of stock
> everywhere. Apparently it would have run out of the box with linux.
> Anyhow, let’s put trendnet on the back burner for now because I’m
> lacking the patience to learn how to build a driver at the moment. Do
> you know of any tutorials for installing ndiswrapper on openSUSE 13.1?
> Preferably one that caters towards Linux newbies. I figure trying to get
> the marvell chipset working is worth a shot. I looked for the guide
> here: http://tinyurl.com/yknx27n but the link does not work…
Sorry, I do not do ndiswrapper. In any case, it will be harder than implementing
the other driver, and it may not work.