[How-To] Alternatives of Samsung WiFi Link Stick

This forum is for information related with B series hardware instead of firmware/software.
Locked

arris69
Official SamyGO Developer
Posts: 1700
Joined: Fri Oct 02, 2009 8:52 am
Location: Austria/Vienna (no Kangaroos here)
Contact:

Re: [How-To] Alternatives of Samsung WiFi Link Stick

Post by arris69 »

moominek wrote:Hello, I've read all thread and still have problem with WiFi dongle. My it is TP-Link TL-WN321G V4 with Ralink chip using probably rt2870sta drivers. In Ubuntu Linux the used driver is rt2800usb. The ID's of dongle are 148f:2070.
I change the driver rt2870sta in TV from SamyGO and when I try to up or down wireless interface (ra0 or ra11n0) the following info is shown: SIOCGIFFLAGS: No such device.
The ifconfig show that there are only two interfaces: lo and eth, no one wireless. What kind of problem there is? Is the problem of rt2870sta drivers and the ID's (148f:2070) ? What should I do? Compile the rt2870 drivers with my ID's, but how can I do it (i'm familiar with linux OS's but not an expert ;) ) ? Any sugestions will be helpfull for me.
check that you have rt3070sta.ko in the extensions pack for your device, if not then wait for next release.

hth
arris
arris69
Official SamyGO Developer
Posts: 1700
Joined: Fri Oct 02, 2009 8:52 am
Location: Austria/Vienna (no Kangaroos here)
Contact:

Re: [How-To] Alternatives of Samsung WiFi Link Stick

Post by arris69 »

moominek wrote:Thanks Arris for answer. Unfortunelly I don't find the rt3070sta.ko in the last extensions pack.
Arris could you give me some basic instructions or directions to cross-compile the driver, maybe I try to prepare driver for this dongle? My TV set is LE40B651.
I find some usefull wep pages for this driver:
http://embedded.abstract-blue.net/?p=14
http://www.friendlyarm.net/forum/topic/2461?lang=de

It seems not complicated, I hope. :)
Regards,
M
it isn't complicated. just get a cross-toolchain witch correct version of gcc and glibc (glibc not required if you just like to build modules) and the kernel sources and compile the modules you need

for your wlan device rt3070sta-2.1.1.0 is too old, you can patch the driver for the device id may it will work
rt3070usb-2.3.0.4 supports the device but you need to patch it for kernel 2.6.18 (if you will use it on b-series tv)

btw: try this http://linux.zsolttech.com/Samsung/rt3070sta.ko

Code: Select all

version:        2.3.0.4
license:        GPL
description:    RT2870 Wireless Lan Linux Driver
author:         Paul Lin <paul_lin@ralinktech.com>
srcversion:     6CCBA4C2A164B3ABB67BF3F
alias:          usb:v148Fp2070d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0789p0166d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v07FAp7712d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v13D3p3321d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v13D3p3307d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v083ApA703d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v5A57p0282d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0p821Ad*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0p3821d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0p822Ad*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0p871Ad*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0p3871d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0p3822d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0p6899d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0p870Ad*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0p3870d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0p899Ad*dc*dsc*dp*ic*isc*ip*
alias:          usb:v203Dp14A9d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0B05p1784d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v20B8p8888d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v203Dp1480d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v04BBp0948d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v04BBp0947d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v04BBp0945d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v5A57p0283d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v5A57p5257d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1D4Dp000Ed*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1D4Dp000Cd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v07D1p3C17d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v07D1p3C16d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v07D1p3C0Fd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v07D1p3C0Ed*dc*dsc*dp*ic*isc*ip*
alias:          usb:v07D1p3C0Dd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v07D1p3C0Ad*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1EDAp2310d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1A32p0304d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v7392p7711d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v07B8p3072d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v07B8p3071d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v07B8p3070d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v2019pAB25d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1044p800Dd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v13D3p3305d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v13D3p3273d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1740p9709d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1740p9708d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1740p9707d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1740p9706d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1740p9705d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1740p9703d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v083ApA702d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v083ApA701d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v083Ap7511d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v18C5p0012d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v14B2p3C12d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DF6p0047d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DF6p0048d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DF6p0042d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DF6p003Ed*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0p822Bd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0p871Bd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0p822Cd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0p871Cd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0p3820d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v148Fp3072d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v148Fp3071d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v148Fp3070d*dc*dsc*dp*ic*isc*ip*
depends:        usbcore
vermagic:       2.6.18_SELP-ARM preempt mod_unload ARMv6 gcc-4.2
parm:           mac:rt28xx: wireless mac addr (charp)
hth
arris
arris69
Official SamyGO Developer
Posts: 1700
Joined: Fri Oct 02, 2009 8:52 am
Location: Austria/Vienna (no Kangaroos here)
Contact:

Re: [How-To] Alternatives of Samsung WiFi Link Stick

Post by arris69 »

moominek wrote:It seems not complicated but not easy ;)
I have kernel sources from Samsung Opensources (linux-r011 from LE32B650 pack), have rt3070sta-2.5.0.2 sources. But which cross compiler should I use? I tried friendly arm gcc-4.4.3 but it doesnt work - too many errors :/
Regards
you'll need gcc-4.2.<something> (think it's in 32B650.zip) from samsung if you like to rebuild it.

arris

ps: i don't preach again/more that we have a svn....
mafgr
Posts: 10
Joined: Wed Aug 10, 2011 10:13 am

Re: [How-To] Alternatives of Samsung WiFi Link Stick

Post by mafgr »

Guys Please help me a bit

Spare a few minutes from your time i think it can help others as well.

I want to change VID/PID to a Dlink DWA-140 to match Samsung WIS09ABGN.I know it is compatible
I have found some Russian guides but i can not translate them correctly.(Google Translate,Babylon,Systran).
Can you assist??Do i need Ubuntu on a live CD??can i make the permanent PID/VID change to my wifi stick in eeprom on WINDOWS 7,XP
I have installed and download Ubuntu 11.04 but the commands are not compatible??

http://forum.ixbt.com/topic.cgi?id=62:18540:3746#3746
http://forum.ixbt.com/topic.cgi?id=62:18540:1618#1618

Please help me a bit

I have also posted in this site for help but no one replies to me

http://forum.wdlxtv.com/viewtopic.php?f=31&t=4713
User avatar
erdem_ua
SamyGO Admin
Posts: 3125
Joined: Thu Oct 01, 2009 6:02 am
Location: Istanbul, Turkey
Contact:

Re: [How-To] Alternatives of Samsung WiFi Link Stick

Post by erdem_ua »

Firstly you cannot change PID/VID of your device via EEPROM flashing.
Just use SamyGO Expansion Pack and read our Wiki pages. Thats all.
User avatar
juusso
SamyGO Moderator
Posts: 10129
Joined: Sun Mar 07, 2010 6:20 pm

Re: [How-To] Alternatives of Samsung WiFi Link Stick

Post by juusso »

Erdem, you are mistaken.
I successfully changed VID and PID of my dwa-125 on ubuntu virtual machine many time ago. And i don`t need to use patched wifi drivers for my TV. the dwa-125 is recognized as WIS09ABGN.
But i had no succes by changing the same for my Edimax-uN7711, i got it broken - unknown VID and PID were rewritten and i couldn`t write original meanings back.
mafgr wrote:Do i need Ubuntu on a live CD??
it is better to use virtual mashine. Because you need to compile driver for changing VID&PID
can i make the permanent PID/VID change to my wifi stick in eeprom on WINDOWS 7,XP
You can change it permanent (not for all wifi sticks, some of them are protected), but only in Linux.
I have installed and download Ubuntu 11.04 but the commands are not compatible??
What exact errors do you get?
LE40B653T5W,UE40D6750,UE65Q8C
Have questions? Read SamyGO Wiki, Search on forum first!
FFB (v0.8), FFB for CI+ . Get root on: C series, D series, E series, F series, H series. rooting K series, exeDSP/exeTV patches[C/D/E/F/H]

DO NOT EVER INSTALL FIRMWARE UPGRADE
mafgr
Posts: 10
Joined: Wed Aug 10, 2011 10:13 am

Re: [How-To] Alternatives of Samsung WiFi Link Stick

Post by mafgr »

Hello juuso.
Thanks you for your prompt answer.
This is what i understand from translating the russian pages

------------------------------------------------------------------
So, the promised account for Linux beginners on how to change VID and PID Wi-Fi adapters.
is strongly recommended before you buy an adapter to check whether the VID and PID to the list of devices drivers for rt2870 from Ralinka (located in the file common \ rtusb_dev_id.c). If it is not your device from its purchase should be avoided, but if you believe ... then about this later.
In fact, all described below is not nothing but a detailed steps for installing and compiling the Linux drivers for use of the method BigHercules.
let's go.
1. Download and install a virtual machine - VMware-workstation-6.5.4 Windows.
2. Download the Linux distribution (I do it under Ubuntu 10.4 on it further and will be discussed.)
3. Configure the VMware (there is no big deal), create a new partition (8 GB is enough), connect the image of Linux as a virtual drive.
4. Install Linux. It's easy: select the language, theme, login and password (I used a login - q1, and password - 1). We look forward to when it is established.
5. Requires internet, because after installing Ubuntu wants to upgrade - do not prevent this, otherwise the success of the operation, I can not comment.
The whole process took me about an hour with the unit. Upon completion of the upgrade reboot Ubuntu.
Here we come to activation of the interface ra0, for this you need unzipped driver from Ralink placed into usb stick's directory 2870 (link to the driver is above).
Then run the terminal and execute the following sequence of commands (you need internet access):

Code: Select all

sudo aptitude update 
sudo aptitude install build-essential
Copy the folder 2870 from the stick to home directory (as in Windows, open the folder, right click on the flash drive and select copy in your home directory).
Further, if the VID and PID of your device are missing from the file ..common\rtusb_dev_id.c, and you are certainly sure that the device is in based on rt2870, put the number (code?) of the device into the file and save it. Go to the terminal and execute the following commands:

Code: Select all

cd 2870
sudo make
sudo make install



When done, your compiled driver rt2870sta.ko will be in the directory / 2870/os/linux , which we install with command:

Code: Select all

sudo insmod / home/q1/2870/os/linux/rt2870sta.ko
I draw your attention that all paths will be as if you created a user is q1, and dad is the driver with the codes 2870 and also placed in the home directory.
Next, if the error was not properly proceed to action. Sticks adapter and check to see whether its Ubuntu team:

Code: Select all

lsusb

On the screen the list of connected USB-devices should be displayed, where you should see you wifi-stick also. If it's not in the list, look at the icon of USB device in the right bottom coner of virtual machine. It should have a green dot. If there is no green dot, it means that WINDOWS took over the control of your device. If that's the case, cick on the icon an select first menu item, the device should become active. Other option is to connect the adaptor to a different USB port. In any case there no point to go on with the procedure until you see your device with the command lsusb.
If everything ok, check if ra0 is up with the command:

Code: Select all

ifconfig ra0
as the result of the command execution it will be clear if interface become active or not. If it's on, move to replacement of VID and PID as described by BigHercules, sudo command shall be executed prior to the configuration of interface

Code: Select all

sudo ifconfig ra0 19 ...
Additional checks can be done by removing the device and stuck it on again. Then execute:

Code: Select all

lsusb
---------------------------------------------------

I can not install the 10.4.4 LTS ubuntu in my system i tried both a laptop and a desktop that i have i am getting a strange message like

"Can not mount /dev/loop0(/cdrom/casper/filesystem/squashfs) om //filesystem squashfs"

I tried to install the 11.4 which was sucesfull but the commands with the 11.4 are not compatible such as aptitute is in 11.4 apt-get
I am total noob in linux but i am trying.......
When i proceed to sudo make then after a while i am getting a error 2 and i can not procced to sudo install

Pleaseee can you help me???

Locked

Return to “[B] Hardware”