SamyGO

don`t know for sure I used a 32 bit ubuntu system (see you have a 64 bit) and struggled a while to compile driver.
I have a sitecom stick wich clearly doesn`t work same results as you, plugged in a dwa-140 and it worked.
however dwa-140 I have is rev B and this is unsupported

Daniel

I encountered no problems with driver compiling. But it's strange that it doesn't work with 2 different dongles/hardware.
Can you tell me, please, which driver version did you use and where you download it from?

Thanks.

PS: Do you know about a dongle that works for sure? A dongle without different hardware revisions etc. - just to plug it, chage its VID&PID and after that plug it into my TV (UE37D5500)...

I will look up my sources later.
Only one I can confirm is original samsung, probbably not what you wanted to hear.
Also tried 2 sticks without success
Daniel

ok here it goes:
the rar contains a compiled version and source
the bz2 is original from ralink

as usual downloads will be removed after 1 week.

if not in line with ralink license please notify me and I will remove downloads immidiatly

Daniel

Hi i do not see a ra0 device, did you rmmod the old rt2800usb ?
Please run And post outcome here.
Also please type the steps you have taken and what driver version you compiled
Daniel

nspierbundel wrote:ok here it goes:

the rar contains a compiled version and source
the bz2 is original from ralink
Daniel

Thank you for the link. Of course I wasn't able to use you compiled driver but I recompiled the source for my system. Still no results. It seems that DWA-125 rev.A3 and EW-7711UAn do not permit access (read or/an write) to their EEPROMs. Both dongles were functional under Debian and connect to my wireless router with no problems.

I noticed that when I run an e2p command, no matter the parameters, a file is created in current directory - "EEPROMdump.....txt". It only contains 00-fe addresses but no data corresponds to device VID & PID. When I run a mac command ("iwpriv ra0 mac ....") a file named "MACdump....txt", also containing 00-ff addresses with no useful data.

I come to think that a reasonable thing to do is to buy the original Samsung dongle

In my case dwa-125 a3 after e2p returned nothing. I had to ctrl+break after few minutes of waiting. Then pid and vid didn't change but dongle was bricked and went to trash.

If a dongle is bricked how can you read pid/vid?
Are u sure it is bricked?
Not a bad connection?
Daniel

VID and PID are visble but dongle is not recognized by its drivers under linux or windows. Windows starts to install driver and finish with communicate that it is not compatible. Already checked .inf and this vid and pid are correct.

I have second one and i hestiate to try whole procedure again