DIR-615 D3 - info from dmesg:

Chipset:

CPU revision is: 0001964c (MIPS 24Kc)
Ralink RT3052   id:1 rev:3 running at 384.00 MHz

WiFi chipset:

phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 2872, rf: 0000, rev: 0200.

rf: 0000 means unknown RF chip (it should be 0008 - RF3022 - I set it manually).

(Last edited by omgwtfbbq on 8 Jan 2011, 21:53)

Hi, all. Could you make some d1-d4 photos for wiki page ? Please remove cpu shield before (No need to solder - it just opens with knife or something sharp).

Hello. I am trying to build r25238 for my DIR-615 D4. I have tried RF3022 IDs 0x0000, 0x0008, and 0x000c, all to no avail. With all of them, in dmesg, is

phy0 -> rt2800_init_eeprom: Error - Invalid RF chipset detected.
phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.

Where do I proceed from here?

Sorry for the late reply, I've been a bit distracted.

I built rev 24915 (well, svn co said it was 24920) with no modifications to the driver files, completely clean and untouched, only selected target platform as per your instructions. Did not change the chip IDs or drivers in any way.

The wireless works in N mode with encryption and no modifications on a D2 revision,

CPU revision is: 0001964c (MIPS 24Kc)
Ralink RT3052   id:1 rev:2 running at 384.00 MHz

Output of my D4 differs only slightly:

CPU revision is: 0001964c (MIPS 24Kc)
Ralink RT3052   id:1 rev:3 running at 384.00 MHz

I don't have any output from dmesg like the second line you quoted (phy0 -> etc.). The wireless driver seems to be:

Compat-wireless backport release: compat-wireless-2010-12-10-3-g880bb0b
Backport based on wireless-testing.git master-2010-12-16
cfg80211: Calling CRDA to update world regulatory domain
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Registered led device: rt2800pci-phy0::radio
Registered led device: rt2800pci-phy0::assoc
Registered led device: rt2800pci-phy0::quality

lsmod shows the following drivers loaded:

rt2800pci               6064  0
rt2800lib              32048  1 rt2800pci
rt2x00soc               1152  1 rt2800pci
rt2x00pci               1744  1 rt2800pci
rt2x00lib              24688  4 rt2800pci,rt2800lib,rt2x00soc,rt2x00pci
mac80211              194592  3 rt2800lib,rt2x00soc,rt2x00lib
eeprom_93cx6            1136  0
crc_itu_t               1008  0
crc_ccitt                992  2 ppp_async,rt2800lib
cfg80211              117728  2 rt2x00lib,mac80211
compat                  3216  3 rt2x00lib,mac80211,cfg80211

Dunno if this is relevant or helps. Not a linux expert I'm afraid. Don't see anywhere that lists the chip revision. But either way this build works, with wireless N (144/300mbps) and WPA2 security. The same binary works on both my D2 and D4 revisions. Not sure what I'm doing differently from you to be honest :-/

I've uploaded my built binary here if you want to try it, the wireless is fully working on my D2 and D4. I don't have D1 or D3's to test. Vanilla build, straight from trunk with standard driver, just seems to work somehow.
WARNING: This build caused severe problems with the ethernet switch on my D2 hardware. The ethernet ports would only work either a) with a cat 6 cable or b) when the other device is forcefully set to 10mbps mode. Could have just been a faulty unit, I've only tried it on one out of my 4 D2's. It doesn't seem to have this effect on my D4 but YMMV. Be careful.

http://www.megaupload.com/?d=V5DMZA5H

(Last edited by qasdfdsaq on 30 Jan 2011, 02:38)

Poke me next week and I'll post pics of D2 and D4.

Nope, no difference with your build.
I'm still getting extremely unstable connection (only several packets per minute are lucky enough to pass through).

You have to enable rt2x00 debug output in order to get this line:
Kernel modules -> Wireless Drivers -> kmod-rt2x00-lib -> Configuration -> enable both options.

The recent builds I tried (with changes to mac80211, but not the latest one) are reporting known chip again but still not the one they should have.
I'm sure RT3052 is 2T2R chipset and thus it has RF3022, yet driver reports RF3021 which is 1T2R.
Getting the feeling that D3 === D4 except for crappy wireless chip (Ralink/Dlink screwed something up).

@fahadsadah
First step is to obtain your router's RF chip ID.
Build firmware with rt2x00 debug output, flash it to your router and run dmesg.
Now open rt2800.h in a text editor and change ID of RF chip you want to try to the ID your device reports.
If there is already RF chip with that ID, change its ID to any value that is not listed.

@regressor
Sorry, my device is still under warranty (2 years).

(Last edited by omgwtfbbq on 30 Jan 2011, 03:23)

Actually it might be a bad build. I did a bit of further testing and as it seems, r24920 is actually very unstable on my D4 -  the wireless interface will regularly freeze up for a 30 seconds or a minute and may require manual resetting. The freezing seems to be a regression as it's a lot worse than with r23074. With r23074 it still happens but at least it recovered itself in ~3 seconds most times. Seems to be caused by a rapid change in signal levels (bad rate control?). Not had time to change the rate control algorithms, but setting the transmit power higher (i.e. to max) reduced the problem for me. Running the command "wifi" restores things when the wireless freezes up, without needing a reboot. Anyhow the driver seems a little unstable, but seems to at least work (for me) without modification.

On D4 both r23074 and r24920 are slow and CPU utilization is high (~65mbps actual throughput, load average >3.0) but at least 23074 seems more stable. I've uploaded my old build here - give it a try, as it works slightly better for me:

http://www.megaupload.com/?d=VV46TS28

Same warning as before (for everyone else) - D2 units may have problems with the ethernet interface.

Well anyway, it's far from perfect and the wireless driver is still unstable but when it's working it'll connect at 'N' speeds and transmit data at 'N' speeds for me, though nowhere near as fast as it should. I've not tried recently the D2 as I can't even get it to connect to an ethernet switch properly so can't configure it or transmit data through it once flashed with openwrt >_<

What client device are you using by the way? Mine seems slightly more stable with a Ralink client than an Intel one, but that might just be my imagination.

Ah that'd be it. Done. Outputs below:

Seems to be detecting the right card for me automatically.

Definitely 2T2R's, don't know why mine seems to detect it as RF3022 correctly.

Interestingly two of my D2's (a D2G and a D2E) have ethernet switch problems with newer builds but older ones (i.e. a year old) are OK, and D4 is completely unaffected.

Doesn't flashing with un-approved firmware technically void the warranty too? Anyways, opening the device is non-destructive, there's no seals to break and you can do it without leaving any evidence.

(Last edited by qasdfdsaq on 30 Jan 2011, 05:20)

Thanks for that. For the record, the chip ID of my DIR-615 D4 is 0x000d

phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 2872, rf: 000d, rev: 0200.

That's very odd. 0x000d is supposedly the RF3853, a 2.4/5Ghz 3T3R wireless chip! Anyhow it's clearly identifying itself or being detected incorrectly, but if you modify your driver rt2800.h file with that it should work.

Let us know how you get on.

On second thoughts, perhaps not. I think it's more of a driver/firmware issue. I noticed on one of my DIR-615 D's the stock firmware would allow 300mbps speeds (2T2R) but *both* dd-wrt and openwrt would only do 150mbps (1T2R) on the same device. Maybe the chip has a bad EEPROM value somewhere that made it identify as RF3021 so that openwrt thought it was a 1T2R?

(Last edited by qasdfdsaq on 30 Jan 2011, 19:10)

The interface identifies as 802.11bgn. I'll test throughput now.

EDIT: I can't see the SSID from any client I try =/

(Last edited by fahadsadah on 30 Jan 2011, 19:50)

r24805 is slightly better, I can even ping my laptop several times, also the reported speed doesn't change that much but stays at around 104-144mbps.

Intel WiFi Link 5300 AGN.

Previous builds of DDWRT (14xxx) work at 300mbps (40MHz) without problem*.
Only 15xxx contains a new driver from Ralink that reverts back to 144 whenever it detects channel colisions (or even more often).
I once managed to run 15xxx at 300 but only for short time then it fell back to 144.

*- Not really without a problem, the connection was unstable after several minutes, loading websites took unusualy long time, sometimes just timed out - whole 14xxx was unstable even on wired connection.
I have a similiar problem with original firmware on 40MHz (20MHz works fine), it may be a client-ap related problem (Ralink vs Intel).

I can always flash back to original firmware without leaving any trace.
Considering my previous experience, opening a router is always destructive...

I can confirm that r25238 (and possibly later) do not have any support for wireless networking whatsoever.

If wifi is set to 802.11g-only on a r24xxx build, does it work acceptably?

802.11g works fine for some time already.

----------------------

I've been exerimenting with Ralink SDK (several router manufacturers published it) and here's the result:

http://www.mediafire.com/?q75p02kdxycjogy
Do NOT, I repeat, do NOT flash this firmware if you don't know how to access Dlink Emergency room and if you haven't read the rest of this post yet.

+ WiFi @ 300mbps
+ IPv6, radvd, IPv6 over IPv4
+ more options to set directly in web GUI
+ telnet
- ugly terminal
- switch not working out of the box

!!! Only the 1st LAN port (WAN port actually) works out of the box - I don't know how to enable the rest.
!!! If someone manages to get it working, please let me know.
!!! There are only 2 ways to get to administration: WiFi (open, SSID wireless) and the 1st wired port.

IP: 192.168.0.1
User: admin
Password: admin

You might have to restart your router manually (unplug & plug the power) after flashing (after +- 90 seconds of uploading the image) to actually boot this firmware for the first time.

(Last edited by omgwtfbbq on 4 Feb 2011, 03:25)

Some status how it works for me at the moment:
1) Router revision: D1
2) Wireless mode: g+n
3) HT mode: 40Mhz
4) Security mode: WPA2-PSK
5) Client device: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) [168c:002a] (rev 01)
6) Security *and* encryption mode on client: WPA2-PSK, Encryption: CCMP
7) Highest reported rate on client: tx bitrate: 65.0 MBit/s MCS 7

OpenWrt is r25423 except the files in target/linux/ramips/files/drivers/net. I reverted them to r24328 to get the LAN ports working.
Without this it was not even possible to get a link with the onboard NIC on my Desktop PC (link up/link down every second).

(Last edited by catdog2 on 10 Feb 2011, 15:31)

Yeah, I've got the same problem with the LAN ports on a D2, looks like D1 and D2 are both affected but D4 isn't. Only able to get a link to stay up if manually set to 10mbps on the other device.

Out of interest how did you revert the NIC drivers only? I can't figure out how to get the old revisions out of svn, but then I've never used svn before now.

Assuming you are in the root of the source tree:

cd target/linux/ramips/files/drivers/net
svn -r 24328 update

Remember: if you run svn update in the root of your tree the files in target/linux/ramips/files/drivers/net will be updated to the latest revision, too.

PCB photos (for wiki) are still needed...

right, no soldering necessary

got some PCB pics; DIR-615 REV D3

transferred to the wiki:
http://wiki.openwrt.org/toh/d-link/dir- … otos/start

(Last edited by Tf2k on 24 Apr 2011, 19:51)

Added to wiki. Could you make pcb bottom side photo ?

As you wish

http://www.flickr.com/photos/51271814@N06/5461498597/

OK, internal pictures of D2 and D4 PCB are now up. Sorry it took me so long. Just so busy and forgetful these days

D2 Front
D2 Back
D4 Front
D4 Back

The D4 seems to be an overall cheaper unit - no removeable antennas, no LED shields, plastic instead of metal frame on ethernet ports, etc - but the newer CPU revision seems to work better with the latest openwrt trunk builds (at least as far as the network driver is concerned). D3 and D4 look pretty similar, I'd hazard a guess that D1 and D2 are pretty much the same too.

(Last edited by qasdfdsaq on 21 Feb 2011, 02:16)

d1 pictures

http://rapidshare.com/files/449325137/201102A0.rar

if there is someone with skills interested in making shdc mod for dir-615 D1 i can send one of mine routers
no return of that unit necessary

(Last edited by m4rkiz on 26 Feb 2011, 15:08)

There is a firmware for RT350x based devices based on Ralink SDK over at www.sadnet.ru, Wive NG-RTNL. Might be worth checking out, since it contains a newer kernel + fixes.
Tried flashing it to my D1 without succes (2T2R version). Since it should be a generic image (according to sfstudio (author) on DD-WRT forums), it should work. My guess is that it isn't properly signed but I don't have enough knowledge about the whole process to know for sure.

After digging around on the internet some more I found this site: https://sites.google.com/site/wivertnl/. There is a link to firmware for for the Dir 615 D1.
Going to upload it to my D1 and see how it goes.

Edit: My D1 won't accept the image, in the webinterface and the emergency room =/

(Last edited by iddqd on 11 Apr 2011, 17:23)

Can you please post non-thumbnail links to these photographs?  Thank you

http://img593.imageshack.us/img593/1904/img2357.jpg http://img185.imageshack.us/img185/1456/img2358o.jpg http://img684.imageshack.us/img684/8435/img2355a.jpg

xD

(Last edited by dk_giuse89 on 14 Apr 2011, 16:14)