D-Link Forums
D-Link Wireless Routers for Home and Small Business => Information => Archive => Topic started by: Heffer on December 27, 2009, 02:52:35 AM
-
Hi there. Here's a little howto I wrote.
Check this: http://fetzig.org/2009/12/24/openwrt-on-the-d-link-dir-825/
Maybe you have more luck with this than with D-Links Firmware. For me it solved all my IPv6 issues I reported to D-Link Germany, as they decided not to respond to my E-Mails.
Greetings,
Felix
-
Are there some instructions or Screenshots available where you can take a look at before you are flashing the router with this firmware?
Looks like you need telnet to configure the router from then on. Is it not possible via webbrowser anymore?
-
Hi there. Here's a little howto I wrote.
Check this: http://fetzig.org/2009/12/24/openwrt-on-the-d-link-dir-825/
Maybe you have more luck with this than with D-Links Firmware. For me it solved all my IPv6 issues I reported to D-Link Germany, as they decided not to respond to my E-Mails.
Greetings,
Felix
Yes, thank you, Felix. I came across your blog post a few days ago and flashed my router. It's been working well ever since. I now have a reliable IPv6 router. It self-updates my tunnel if my IPv4 address changes without needing to reboot. I can now access my modem from behind my router and also all my computers on my LAN are correctly registered in the router's DNS. So many headaches are now a thing of the past.
-
Are there some instructions or Screenshots available where you can take a look at before you are flashing the router with this firmware?
Looks like you need telnet to configure the router from then on. Is it not possible via webbrowser anymore?
OpenWrt is mainly command-line driven. There is a web interface, though it's not installed by default so at a bare minimum, you would need to telnet/ssh and install that (opkg update; opkg install install luci-admin-full) before you could use it. The web interface covers much of the standard router features, but certainly does not cover the full range of what OpenWrt is capable of. For example, configuring your PPPoE information or NTP is fine, but I didn't see anything in there for my IPv6 configuration and I doubt it would have stuff for Asterisk. I found myself using a shell for installing new components (opkg), setting my wireless mode (enabling 'n' mode, but not setting the encryption, band, etc), and setting my IPv6 info. PPPoE, static DHCP, NTPD, and WiFi settings (all but setting the mode) I did from the web interface. One other thing of note, is the LEDs are not configured correctly (at least not with the firmware from a couple days ago). They can be configured from the web interface, but since my router's in a whole other room I haven't bothered.
In short, if you're not comfortable with a CLI, then I wouldn't recommend going the OpenWrt route (at least not yet). The good news is that the hard work is done, so hopefully it won't be long for more consumer oriented firmwares to add support as well (such as Tomato and DD-Wrt). On the other hand, if you're comfortable with a CLI and have a bit of time, then it's a good choice.
Although not a step-by-step picture instructions you asked about, some screenshots can be found here: http://wiki.openwrt.org/doc/configuring to give an indication of what the web UI looks like.
HTH.
-
Thanks. I will wait and see what's happening in the future. :-)
For now on I have no problems with my DIR-825. So an firmware upgrade is not necessary for me.
-
How did you guys got the wireless working?
I managed to flash my 825 with openWrt with Felix's instructions and I have it routing properly the wired connections. However, I cannot configure the Wifi, if I go via luci I have no devices to choose and configure; in the command line, if i do 'wifi detect' I get no output at all and if I try to configure '/etc/config/wireless' by hand I always get "Interface type not supported error" (I tried all 3 of them).
Do you guys get any output on 'wifi detect'? Am I missing some other configuration?
-
This really is great news! I can't wait for a full DD-WRT release. I understand CLI but really don't have the patience to risk my network being in-operable right now.
I figure now with OpenWRT working DD-WRT won't be far off. Infact according to this post on DD-WRT the porting is already underway:
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=57708&postdays=0&postorder=asc&start=15
-
DD WRT shows atheros chipset cannot work with WRT. What am I missing here. How did you get this to work
?
-
Supposedly DDWRT is working now
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=57708&postdays=0&postorder=asc&start=15
http://svn.dd-wrt.com:8000/dd-wrt/changeset/13516
-
Anyone want to try it out? If DD-WRT works i'll scrap D-Link's firmware in a second.
-
How did you guys got the wireless working?
I managed to flash my 825 with openWrt with Felix's instructions and I have it routing properly the wired connections. However, I cannot configure the Wifi, if I go via luci I have no devices to choose and configure; in the command line, if i do 'wifi detect' I get no output at all and if I try to configure '/etc/config/wireless' by hand I always get "Interface type not supported error" (I tried all 3 of them).
Do you guys get any output on 'wifi detect'? Am I missing some other configuration?
For WiFi, make sure the drivers and hostapd are installed:
opkg update
opkg install kmod-ath9k
opkg install hostapd
Here's my /etc/config/wireless:
config 'wifi-device' 'radio0'
option 'type' 'mac80211'
option 'macaddr' 'MAC-addr-goes-here'
option 'hwmode' '11g'
option 'disabled' '0'
option 'channel' '9'
config 'wifi-iface'
option 'device' 'radio0'
option 'network' 'lan'
option 'mode' 'ap'
option 'encryption' 'psk2'
option 'key' 'WPA-key-goes-here'
option 'ssid' 'SSID-goes-here'
config 'wifi-device' 'radio1'
option 'type' 'mac80211'
option 'channel' '36'
option 'macaddr' 'MAC-addr-goes-here'
option 'hwmode' '11a'
option 'hwmode_11n' 'a'
list 'ht_capab' 'HT40+'
list 'ht_capab' 'SHORT-GI-40'
list 'ht_capab' 'DSSS_CCK-40'
option 'disabled' '0'
config 'wifi-iface'
option 'device' 'radio1'
option 'network' 'lan'
option 'mode' 'ap'
option 'ssid' 'SSID-goes-here'
option 'encryption' 'psk2'
option 'key' 'WPA-key-goes-here'
If that doesn't work, let me know. I don't recall tweaking anything else, but it's possible.
-
Many thaks for your help mactalla, Felix (on your blog) but I still have no wifi.
I cannot properly install the drivers as when I try to install the 'kmod-ath9k' package I get an error that it cannot resolve the dependencies 'kmod-crypto-arc4' and ''kmod-crypto-aes'; even though these packages are in the repository I'm using (http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages) I cannot see them in opkg list.
I did force the package installation and tried 'wifi detect' and got nothing in the output.
Just for the sake of it, I used your '/etc/config/wireless' and gave it a go but all I got was
PHY for wifi device radio0 not found
PHY for wifi device radio1 not found
But then, I did comment out the mac address option as I don't know where to find them for the radios...
By the way, these are all the devices I have:
br-lan
eth0
eth1
lo
so, no wireless devices, which makes sense, seen as my drivers are not properly installed.
Problem is I'm clueless on what to do next (damn noob :-[ )...
-
I cannot properly install the drivers as when I try to install the 'kmod-ath9k' package I get an error that it cannot resolve the dependencies 'kmod-crypto-arc4' and ''kmod-crypto-aes'; even though these packages are in the repository I'm using (http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages) I cannot see them in opkg list.
[...]
Problem is I'm clueless on what to do next (damn noob :-[ )...
I know the feeling :)
One thing that I noticed (and failed to mention here) is that when fetching the list of available packages (opkg update) it stores it in RAM. I guess this is a feature since the flash is a precious commodity and the list does change over time. So what that means is you must run opkg update again if you're rebooted since the last time or it won't know about most packages.
Secondly, to get the drivers you must not only install them (download) but also load them. This should be done automatically when you (re)boot, but can also do it manually by running "insmod ath9k" This will also let you see any trouble it has loading the module without having to look at the logs ("logread" and "dmesg").
When the driver is loaded (it shows up in "lsmod"), then you should start seeing the radios and calling "wifi up" should attempt to bring them up. Again, this is automatic on boot, but you can move it along manually without needing to constantly reboot.
So hopefully it was just a missing opkg update. Let me know how you fare.
-
Ok, I had to install the 'crypto' packages by hand as they were not declared in the 'Packages' file.
Now I get WiFi, woohooo!
Many thanks for your help guys!
-
Did you need a cable to load OpenWrt to the 825?
-
Did you need a cable to load OpenWrt to the 825?
Just a standard network cable between your PC & laptop (do not try to flash over WiFi!)
Rember, your warranty is VOID after you try this!
(Neither I, nor D-Link, nor Felix, nor DD-WRT can be hold responsible if you 'brick' your router!)
To get DD-WRT working simply download the file 'factory-to-ddwrt_WW.bin' to your computer from the DD-WRT site here (http://www.dd-wrt.com/site/support/other-downloads?path=others%2Feko%2FBrainSlayer-V24-preSP2%2F12-28-09-r13525%2Fdlink-dir825-revb%2F).
Then use the 'Felix Kaechele method' at his blog (http://fetzig.org/2009/12/24/openwrt-on-the-d-link-dir-825/) and use the factory-to-ddwrt_WW.bin file to flash the firmware instead of the openwrt-ar71xx-dir-825-b1-squashfs-backup-loader.bin
After the successful flash remember to do a 30-30-30 Hard reset (http://www.dd-wrt.com/wiki/index.php/Hard_reset_or_30/30/30) (if you do not, CPU load in the router is verry high and your WiFi might not be working)
I'm now running DD-WRT on my D-Link DIR-825 and its running great!
See my screen shot:
(http://tweakers.net/ext/f/ZncXzTbqAHeevdr9vBhHh7tg/full.jpg)
-
Will it be possible to go back to the D-Link original firmware if I don't like the DD-WRT firmware version?
Basically the orignal firmware works fine for me. A feature I like is the Guest-WLAN. Where I can give friends access to my wifi without to give them access to my attached network devices.
-
I successfully installed the dlink firmware 2.02NA after having both openwrt and dd-wrt installed and working.
I decided to try going back because despite having dd-wrt all configured and working, even the config backed up, when I unplugged the device to move it to the area I keep all my IT equipment in, something went wrong. Once I plugged it back in, I could no longer connect to it (wired or wireless - telnet/ssh/http and not getting DHCP.)
I tried everything I could think of. I was able to get openwrt up and working again, but could not get the wireless radios to show up this time. Installed dd-wrt again only took me to the same place, no access. So I remembered seeing on fetzig.org that you use the same procedure to install the dlink firmware again.
That works, but I cannot get the wireless radios to turn on. There must be something stuck in its craw.
I'm still working on it.
So you can install the firmware again, but I can't guarantee everything will work again.
-
Try a 30-30-30 reset (http://www.dd-wrt.com/wiki/index.php/Hard_reset_or_30/30/30 (http://www.dd-wrt.com/wiki/index.php/Hard_reset_or_30/30/30))
That worked for me getting the WiFi back again.
And creating a 'Guest network' is possible in DD-WRT by creating an unbridged network under 'Virtual Interfaces'.
-
Try a 30-30-30 reset (http://www.dd-wrt.com/wiki/index.php/Hard_reset_or_30/30/30 (http://www.dd-wrt.com/wiki/index.php/Hard_reset_or_30/30/30))
That worked for me getting the WiFi back again.
And creating a 'Guest network' is possible in DD-WRT by creating an unbridged network under 'Virtual Interfaces'.
I've done the 30-30-30, including the 10-10 added at: http://www.dd-wrt.com/wiki/index.php/Recover_from_a_Bad_Flash, but no luck.
Something is stuck in nvram (I think) and I can't even telnet/ssh to the unit to erase the nvram. I'm actually finding myself wanting a Cisco style console connection right now... Oh well. I'll keep trying different things. Any other suggestions, please let me know. I'm open to anything, except that old 'it's small enough to throw out the window' idea.. (already thought about it:))
-
Tried it now this DD-WRT firmware. Looks good but it's for me like a function-overload.
Wanted to go back to the original firmware. But when I'm loading this firmware, I'm getting the message "Upload failed". :-(
-
I've done the 30-30-30, including the 10-10 added at: http://www.dd-wrt.com/wiki/index.php/Recover_from_a_Bad_Flash, but no luck.
Something is stuck in nvram (I think) and I can't even telnet/ssh to the unit to erase the nvram. I'm actually finding myself wanting a Cisco style console connection right now... Oh well. I'll keep trying different things. Any other suggestions, please let me know. I'm open to anything, except that old 'it's small enough to throw out the window' idea.. (already thought about it:))
You said OpenWrt is working for you, right? (at least SSH access). Have you tried erasing the NVRAM from OpenWrt (which does not use NVRAM for its config) then flashing whatever other firmware you like (DD-Wrt or stock) and have it create their default values?
Big disclaimer: I have not tried this myself, etc, etc.
To be on the safe side, I would read up on boot_wait and tftp before attempting it.
-
Tried to reload once again the same firmware which I already have installed. And even here I get the message "Upload failed".
WLAN does only work with one laptop for a couple of minutes. The other one can't get an ip-address at all.
-
You said OpenWrt is working for you, right? (at least SSH access). Have you tried erasing the NVRAM from OpenWrt (which does not use NVRAM for its config) then flashing whatever other firmware you like (DD-Wrt or stock) and have it create their default values?
Big disclaimer: I have not tried this myself, etc, etc.
To be on the safe side, I would read up on boot_wait and tftp before attempting it.
Thanks for the reply. That's actually along the same lines that I've been thinking, but I can't figure out how to erase nvram. ('erase nvram' does not work)
the 30-30-30 doesn't seem to work properly on the dir-825. At the end of the 90 seconds, the power light is flashing orange and it's in the firmware upload mode (192.168.0.1)...
I'm starting to think maybe quick shock with a defib may be the only way to clear the memory ;)
Thanks,
Marc
-
Thanks for the reply. That's actually along the same lines that I've been thinking, but I can't figure out how to erase nvram. ('erase nvram' does not work)
According to this: https://forum.openwrt.org/viewtopic.php?pid=52389#p52389 (https://forum.openwrt.org/viewtopic.php?pid=52389#p52389) the command is mtd -r erase nvram (again, not tested myself).
the 30-30-30 doesn't seem to work properly on the dir-825. At the end of the 90 seconds, the power light is flashing orange and it's in the firmware upload mode (192.168.0.1)...
What does the dir825 manual say about resetting to factory defaults? Is it somehow different than the 30-30-30? Because that should be doing the exact same thing (resetting the NVRAM).
...
Just looked it up. It says to hold the reset for 10secs and the router should reboot itself. Then wait a while before logging on. Perhaps by holding the full 30s it jumps to the firmware upload mode without resetting the NVRAM?
-
According to this: https://forum.openwrt.org/viewtopic.php?pid=52389#p52389 (https://forum.openwrt.org/viewtopic.php?pid=52389#p52389) the command is mtd -r erase nvram (again, not tested myself).
What does the dir825 manual say about resetting to factory defaults? Is it somehow different than the 30-30-30? Because that should be doing the exact same thing (resetting the NVRAM).
...
Just looked it up. It says to hold the reset for 10secs and the router should reboot itself. Then wait a while before logging on. Perhaps by holding the full 30s it jumps to the firmware upload mode without resetting the NVRAM?
Thanks for looking up all of that info:) I've tried the mtd command a bunch of times and in different formats, but I get the same message:
Could not open mtd device: nvram
I also tried the 10 second reset and while it doesn't go into firmware upload mode, it doesn't seem to clear what ever is stuck in its craw.
I did a fresh install of the openwrt firmware, installed luci, hostapd & kmod-ath9k. I then opened luci (http://192.168.1.1) and found the following in the system log (I'm guessing these are indications of what is actually wrong, but I'm not sure how to interpret it. Anyway have any idea?
Jan 1 00:04:37 OpenWrt user.warn kernel: ath9k_hw: Unknown symbol ath_hw_setbssidmask
Jan 1 00:04:37 OpenWrt user.warn kernel: ath9k_hw: Unknown symbol ath_regd_get_band_ctl
Jan 1 00:04:37 OpenWrt user.warn kernel: ath9k_common: Unknown symbol ieee80211_get_hdrlen_from_skb
Jan 1 00:04:37 OpenWrt user.warn kernel: ath9k_common: Unknown symbol ieee80211_find_sta_by_hw
Jan 1 00:04:37 OpenWrt user.warn kernel: ath9k_common: Unknown symbol ath9k_hw_extend_tsf
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_set_txpowerlimit
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_set11n_aggr_last
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_start_tx_ba_cb_irqsafe
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_getdefantenna
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_reset_calvalid
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_set11n_burstduration
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_intrpend
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_set11n_ratescenario
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_setcapability
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_btcoex_init_3wire
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath_gen_timer_alloc
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_free_hw
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_reset
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_setuptxqueue
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_setuprxdesc
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_startpcureceive
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath_rxbuf_alloc
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_cmn_rx_skb_preprocess
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_putrxbuf
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_keyreset
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_alloc_hw
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_start_tx_ba_session
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_setmcastfilter
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol regulatory_hint
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_btcoex_set_weight
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_register_hw
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_setpower
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_rate_control_unregister
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_get_hdrlen_from_skb
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol __ieee80211_get_radio_led_name
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_phy_disable
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_cmn_padpos
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_cmn_rx_skb_postprocess
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_wake_queue
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath_hw_setbssidmask
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_setrxabort
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_txstart
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol __ieee80211_get_tx_led_name
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_get_buffered_bc
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_gettxintrtxqs
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_updatetxtriglevel
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_beaconinit
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_calibrate
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol wiphy_rfkill_set_hw_state
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_set11n_aggr_middle
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_settsf64
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol __ieee80211_get_rx_led_name
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_name
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_beaconq_setup
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_stop_tx_ba_cb_irqsafe
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_init_btcoex_hw
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol wiphy_to_ieee80211_hw
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_puttxbuf
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath_reg_notifier_apply
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_queue_delayed_work
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_write_associd
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_cleartxdesc
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol wiphy_rfkill_stop_polling
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_set11n_txdesc
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath_is_world_regd
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_gen_timer_stop
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_ani_monitor
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_getrxfilter
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_btcoex_disable
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_wake_queues
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_set_tsfadjust
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_clr11n_aggr
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_rate_control_register
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_set_sta_beacon_timers
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_configpcipowersave
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_btcoex_init_2wire
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_gettsf64
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_rxprocdesc
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath_gen_timer_isr
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_resettxqueue
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_rxena
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_disable
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_setopmode
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_tx_status
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_stop_queue
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_stop_queues
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_gettsf32
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_filltxdesc
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_cfg_gpio_input
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_set11n_aggr_first
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol __ieee80211_get_assoc_led_name
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol wiphy_rfkill_start_polling
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_reset_tsf
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_get_txq_props
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_releasetxqueue
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_setrxfilter
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath_gen_timer_free
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_set_keycache_entry
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_stoppcurecv
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_iterate_active_interfaces_atomic
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_setmac
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol rate_control_send_low
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_unregister_hw
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_gettxbuf
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath_regd_init
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_gpio_get
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_beacon_get_tim
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_getisr
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_computetxtime
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_stoptxdma
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_getchan_noise
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_getcapability
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_stopdmarecv
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_set_interrupts
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_wait
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_btcoex_enable
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_find_sta_by_hw
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_numtxpending
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ieee80211_queue_work
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_set_gpio
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_gen_timer_start
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_setantenna
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_setslottime
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_cfg_output
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_txprocdesc
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_procmibevent
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_detach
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_init
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol ath9k_hw_set_txq_props
Jan 1 00:04:38 OpenWrt user.warn kernel: ath9k: Unknown symbol mac80211_ieee80211_rx
Jan 1 00:04:38 OpenWrt user.info kernel: cfg80211: Using static regulatory domain info
Jan 1 00:04:38 OpenWrt user.info kernel: cfg80211: Regulatory domain: US
Jan 1 00:04:38 OpenWrt user.info kernel: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan 1 00:04:38 OpenWrt user.info kernel: (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
Jan 1 00:04:38 OpenWrt user.info kernel: (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
Jan 1 00:04:38 OpenWrt user.info kernel: (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
Jan 1 00:04:38 OpenWrt user.info kernel: (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
Jan 1 00:04:38 OpenWrt user.info kernel: (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
Jan 1 00:04:38 OpenWrt user.info kernel: (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
Jan 1 00:04:38 OpenWrt user.info kernel: cfg80211: Calling CRDA for country: US
-
Sounds like something's not being loaded correctly.
PM me the output of:
uname -a
opkg list_installed
lsmod
And I'll see how it compares with mine.
-
I can install this into a A2 model? if not, why not?
-
I can install this into a A2 model? if not, why not?
No. D-Link built the rev A using a Ubicom chipset which does not support Linux. They have fixed this by using Atheros chipset in the rev B hardware. Atheros does support Linux, permitting 3rd party firmware.
-
Smart in my opinion as it allows us to run DD-WRT and stop harassing D-Link for updates because once you go DD-WRT you won't go back trust me.
-
Thanks for the reply. That's actually along the same lines that I've been thinking, but I can't figure out how to erase nvram. ('erase nvram' does not work)
the 30-30-30 doesn't seem to work properly on the dir-825. At the end of the 90 seconds, the power light is flashing orange and it's in the firmware upload mode (192.168.0.1)...
Same problem for me. Running erase nvram via telnet seems to work. But I still have Wifi problems after it. So actually I agree that this is not working as a reset on the DIR-825.
Also for me after 30-30-30 rest the powerlight is flashing orange.
Impossible to upload another firmware. Get always "Upload failed".
-
Sounds like something's not being loaded correctly.
PM me the output of:
uname -a
opkg list_installed
lsmod
And I'll see how it compares with mine.
I find myself in the same situation as waffull. I installed dd-wrt but it wasn't working for me so decided to go back to openwrt. However, this time around, even though I upgraded the firmware and installed the packages without errors, I also get the 'unknow symbol' error and some modules don't get loaded. I tried loading them by hand with insmod, but still no success.
Futhermore, if I do 'wifi detect' I get an error:
root@OpenWrt:/sys# wifi detect
ls: /sys/class/ieee80211: No such file or directory
Have you guys figured out how to fix it?
-
Errr just looked at my dir-825 and its a rev A1 :( that just ruined my night I was so excited when I saw this post, but thats just how my luck always goes >:(
-
I find myself in the same situation as waffull.
...
Have you guys figured out how to fix it?
Not yet, but could you PM me the output from
opkg update;
opkg install pciutils
lspci -vv
We've begun narrowing down what his problem is, it'll be interesting to see if you're having the same issue.
-
Got the wifi working again with openwrt!
Here's what I did:
1. Flashed router with the latest 'openwrt-ar71xx-dir-825-b1-squashfs.bin' build
2. Did the 30/30/30 hard reset
3. Connected and installed the hostapd and kmod-ath9k
and voila... it's working again (go figure).
I did have it unpowered for the night, don't if it has anything to do with that as well.
-
perhaps you may be able to install those two packages in ddwrt if you prefer it to openwrt.
-
I have a DIR-825 and I tried dd-wrt with terrible results.
I started with a DIR-825 rev B1 with the stock 2.02NA firmware.
I installed dd-wrt following the directions, and it seemed to work and I could configure it with the dd-wrt web setup, but I had no wireless.
So, I flashed back the stock 2.02NA firmware, and reset it to factory defaults. Now I could get into the web interface of the stock Dlink firmware... but still NO wireless! The wireless LED's would not even turn on.
Next I tried putting back dd-wrt, but now, if I flash dd-wrt onto the router, I have NO network at all. I can't connect to dd-wrt at all, via LAN or WAN ports, and there is no wireless. I can see that dd-wrt is booting, because the little world icon LED lights up that sickly purple color that only dd-wrt does when it boots.
I can still flash back the stock firmware, or I can flash on dd-wrt, or even OpenWRT, but I have NO wireless in any of these firmware. It's like the wireless is broken now.
When I tried OpenWRT I followed ALL of the suggestions from this thread. I thought I had the same problem that LuisGC described in this thread, except he was able to sold it, and I couldn't.
LuisGC says he got wireless fixed on OpenWRT like this:
1. Flashed router with the latest 'openwrt-ar71xx-dir-825-b1-squashfs.bin' build
2. Did the 30/30/30 hard reset
3. Connected and installed the hostapd and kmod-ath9k
I tried to follow those steps, but I could not use the file "openwrt-ar71xx-dir-825-b1-squashfs.bin". The emergency flash page (accessed by holding down reset for 45 seconds) always says it has the wrong hardware ID. I could only use the backup loader version, which i got from here:
http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-dir-825-b1-squashfs-backup-loader.bin
So I used that version of OpenWRT, did a 30/30/30 hard reset (which in my experience doesn't seem to work right on this router), and I installed the packages hostapd and kmod-ath9k.
Still no wireless! I could see that the ath9k module was loaded but no wireless.
I couldn't add the radios with Luci because Luci is broken on the OpenWRT image I used. It just returns at error "Not Found" when I browse to it. Sigh. I found a thread that says this is a problem in the sources of this build or something. So I manually edited the wireless configuration file, using the settings I found in this thread. Still no wireless. The wifi detect command reports it can't find the radios.
I wanted to check my system logs for the error other people saw about symbols, but didn't know how, because I don't have Luci working and I don't know where that log resides on the system.
Also, someone said they used the command "erase nvram". I was never able to try this on my router. Why? Because that command doesn't work for me when I'm logged into openwrt, it says there's no such command or something.
-
I wish I had some news (preferably good) for everyone, but I don't.
I'm guessing one of two things is going on:
1) dd-wrt loads a wireless driver that is getting stuck in an area of memory (some sort of eprom or something) that isn't getting cleared by re-flashing the unit, performing a 30-30-30 +10-10 (I don't think this works on the 825 at all,) or a 10-10-10, that also does not seem to do anything but at least conforms to the reset instructions from DLink.
2) dd-wrt loads a driver that somehow fries the wireless radios. Thinking back, I did notice the unit was quite hot when dd-wrt was installed and running properly. But I never made note of how hot it was running before, so that comparison may not be meaningful.
I have setup a DIR-655 so I have wireless again. I'm going to continue to work with Mactalla (who has been a tremendous help, THANK YOU!) and hopefully we can come up with a solution and/or answer.
-
I wish I had some news (preferably good) for everyone, but I don't...
Thank you for your efforts, Waffull.
Unfortunately I already exchanged my dir-825, and I'm too scared to put dd-wrt or openwrt on it again. I don't have another router to use so I can't afford to break it again.
I kind of wish I had a spare or still had the first (messed up) one so I could be part of figuring this out!
Anyway Waffull it sounds like you are having exactly the same problem I was having.
Can I ask you one thing though, exactly which openwrt firmware file did you use, and where did you get it? Can you link to it? I ask, because the only one I ever used or could get to work, didn't have a working web interface (luci). I see posts talking about putting openwrt on this router and having the web interface work, but I never was able to get the web interface to work. If you did, please show me which file you used (link preferably). I may give this another shot in the future if I see any promising news here.
-
Can I ask you one thing though, exactly which openwrt firmware file did you use, and where did you get it? Can you link to it? I ask, because the only one I ever used or could get to work, didn't have a working web interface (luci). I see posts talking about putting openwrt on this router and having the web interface work, but I never was able to get the web interface to work. If you did, please show me which file you used (link preferably).
At least you were able to get it exchanged:)
I got the file at: http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-dir-825-b1-squashfs-backup-loader.bin
(as of today, the latest release is Kamikaze (r19060), dated 1-5-2010)
It comes with parts of luci (webgui) built in, but you need to install the actual interface part:
opkg update
opkg install luci-admin-full
reboot; exit
Then you can access the web interface (default: http://192.168.1.1)
Hopefully we'll figure something out and if we do, we'll post it..
Take care...
-
That's odd, I tried the command
"opkg install luci-admin-full"
and it reported that this package was already up to date...
However when I opened up the webpage it would just say "Not Found".
-
That's odd, I tried the command
"opkg install luci-admin-full"
and it reported that this package was already up to date...
However when I opened up the webpage it would just say "Not Found".
I found the only way to get it to show up was to reboot the unit after installing it.
You could try:
opkg remove luci-admin-full
reboot;exit
opkg update
opkg install luci-admin-full
reboot;exit
Goodnight.
-
I tried to follow those steps, but I could not use the file "openwrt-ar71xx-dir-825-b1-squashfs.bin". The emergency flash page (accessed by holding down reset for 45 seconds) always says it has the wrong hardware ID.
You can install that one directly from LuCI, without the need to go to the emergency flash page.
If LuCI is not working for you, you can use the webif from x-wrt (http://wiki.x-wrt.org/index.php/Kamikaze_Installation#Updating_OpenWrt_Kamikaze_8.09).
-
What ever I try to upload, it always failes with the firmware update.
Always geht the message "Upload failed".
Any other way to flash the firmware? Via Telnet somehow?
Tried the opkg commands but I only get as answer "-sh: opkg: not found".
Impossible to flash the router to any other firmware.
Any suggestions?
-
I managed to flash the firmware with the mtd command.
Downloaded first the OpenWRT firmware to the router.
Will try more later. :-)
-
Just common question. Have you guys checked that the md5sum of the image you are trying to upload matches with the one that is reported ::)
-
Installed the Web-Admin for the OpenWRT firmware.
Then I uploaded the orignal D-Link firmware again. Finally the router is working perfectly again after one week troubles with the open-source firmwares.
In the meantime I have bought a Netgear WNDR3700 and I'm very happy with this product.
I think I will sell my DIR-825 and stick with Netgear instead since the Wifi signal both in the 2,4 and 5 GHz band is stronger than the signal on the DIR-825.
-
Just want to update you all.
Went back to the shop with the Netgear router. Keeping my D-Link DIR-825 and running it with firmware 2.01WWB02Build02 från Lizzi55's FTP server (http://ftp://lizzi555.dyndns.org/Download/WLAN/DLINK/DIR/DIR-825/Firmware/201wwb03/).
Stable firmware. Everything is working as it should.
Don't need to mess with any other firmware version so far.
-
Hey guys,
did anybody get the 5GHz working? I always get
wlan1: IEEE 802.11 Configured channel (36) not found from the channel list of current mode (2) IEEE 802.11a
wlan1: IEEE 802.11 Hardware does not support configured channel
Could not select hw_mode and channel. (-1)
by wifi and by hostapd itself. But:
root@OpenWrt:~# iwlist wlan1 chan
wlan1 9 channels in total; available frequencies :
Channel 36 : 5.18 GHz
Channel 40 : 5.2 GHz
Channel 44 : 5.22 GHz
Channel 48 : 5.24 GHz
Channel 149 : 5.745 GHz
Channel 153 : 5.765 GHz
Channel 157 : 5.785 GHz
Channel 161 : 5.805 GHz
Channel 165 : 5.825 GHz
and
root@OpenWrt:~# iw phy1 info
Wiphy phy1
Band 1:
Capabilities: 0x104e
HT20/HT40
SM Power Save disabled
RX HT40 SGI
No RX STBC
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
Frequencies:
* 5180 MHz [36] (20.0 dBm) (passive scanning, no IBSS)
* 5200 MHz [40] (20.0 dBm) (passive scanning, no IBSS)
* 5220 MHz [44] (20.0 dBm) (passive scanning, no IBSS)
* 5240 MHz [48] (20.0 dBm) (passive scanning, no IBSS)
* 5260 MHz [52] (disabled)
* 5280 MHz [56] (disabled)
* 5300 MHz [60] (disabled)
* 5320 MHz [64] (disabled)
* 5500 MHz [100] (disabled)
* 5520 MHz [104] (disabled)
* 5540 MHz [108] (disabled)
* 5560 MHz [112] (disabled)
* 5580 MHz [116] (disabled)
* 5600 MHz [120] (disabled)
* 5620 MHz [124] (disabled)
* 5640 MHz [128] (disabled)
* 5660 MHz [132] (disabled)
* 5680 MHz [136] (disabled)
* 5700 MHz [140] (disabled)
* 5745 MHz [149] (20.0 dBm) (passive scanning, no IBSS)
* 5765 MHz [153] (20.0 dBm) (passive scanning, no IBSS)
* 5785 MHz [157] (20.0 dBm) (passive scanning, no IBSS)
* 5805 MHz [161] (20.0 dBm) (passive scanning, no IBSS)
* 5825 MHz [165] (20.0 dBm) (passive scanning, no IBSS)
...
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
...
Does anybody know how to get this working?
Btw: iw reg set DE did not work for me, does anybody know why?
Using Kamikaze r19497 from 3rd feb, but it was the same on the releases before. dir-825 b1.
-
Hey guys,
did anybody get the 5GHz working?
Do these ( https://forum.openwrt.org/viewtopic.php?pid=101782#p101782 ) instructions help you?
-
Do these ( https://forum.openwrt.org/viewtopic.php?pid=101782#p101782 ) instructions help you?
Thanks for that, now I got some changes in the available channels. But the main problem remains, there is still this "Hardware does not support configured channel" although it apears in iwlist chan and iw list.
-
I got it all working now with mactallas great help, thank you very much!
Here is what I did:
- installed crda
- added "export COUNTRY=US" to /etc/profile
- added "option 'country' 'US'" to the 'wifi-device' section in /etc/config/wireless
- chose a channel which is allowed in US and DE, see here (http://de.wikipedia.org/wiki/802.11a#Frequenzen.2FKan.C3.A4le)
- removed "option 'hwmode_11n' 'a'" and changed "option 'hwmode' '11a'" to "option 'hwmode' '11na'" in /etc/config/wireless
-
another question - does anybody of the OpenWRT-users use timebased activation/deactivation of wireless or know if OpenWRT can handle this. I find this a quite useful feature (both for security reasons and for powersaving) and would wan't to miss it in case I switch to OpenWRT.
-
There is a beta of the next OpenWrt release out now. I read that some packages for getting the wireless and usb to work are not included in the default image, but just download the imagebuilder and build an image yourself for this router and it will work from start. If you need more space for own packages see this guide, http://wiki.openwrt.org/doc/howto/rootfsonexternalstorage and include the packages needed using the imagebuilder. I am running this version now with a 2GB usbdrive connected for rootfs and it works as expected, the firmwares i tried from D-Link was never close to as stable as the current setup.
-
So what's the current status on how OpenWRT is performing on the DIR-825 Rev B? I have tried DD-WRT but honestly the wireless power leaves a lot to be desired. The stock firmware is much better in that respect.
-
So what's the current status on how OpenWRT is performing on the DIR-825 Rev B? I have tried DD-WRT but honestly the wireless power leaves a lot to be desired. The stock firmware is much better in that respect.
OpenWrt works pretty nicely with this router, far better actually than the extremely buggy DD-WRT. Thanks to the Ath9k driver (much better than the cr*ppy madwifi used by DD-WRT) I'm getting the best signal strength than any other firmware, including stock v2.02. I did however experience many bugs such as the non-working wlan leds (https://dev.openwrt.org/ticket/7090) (minor), and the infamous "Deauthenticated due to local deauth request" issue (https://dev.openwrt.org/ticket/7413).
The problem with OpenWrt and DIR-825 is that very few people are actively working fixing bugs for this specific combination and AR71xx in general. Same as any opensource project, code maintainers are merging untested patches that fix a specific router but break others. That's why I always revert to stock firmware after a while.
-
Yea, I really like DD-WRT on my WRT54G routers. It works great, but then again that was a main target of DD-WRT. I haven't tried OpenWRT on my DIR-825 but maybe in a few months after seeing a few more software releases pop out. I'm looking to replace one of my WRT54G routers with this D-Link router so I can experiment on the 5GHz band.
-
Hi
I have dd-wrt fm on my dir-825
I cannot get rid of the dd-wrt fm. after 30-30-30 and flashing original fm (DIR825B1_FW202EUB04.bin)
I always get error ""Upgrade failed"
any help please
-
Hi
I have dd-wrt fm on my dir-825
I cannot get rid of the dd-wrt fm. after 30-30-30 and flashing original fm (DIR825B1_FW202EUB04.bin)
I always get error ""Upgrade failed"
any help please
Hey, how's it going? I hope the instructions on the DD-WRT are helping.
Cheers
-
Hi JoeSchmuck
thx for your help :)
now back on earth
cheers
stone99
-
Anything else out there worth grabbing for 3rd party for the Rev B.
-
I flashed my dir825 with OpenWRT (openwrt-ar71xx-generic-dir-825-b1-squashfs-backup-loader.bin), but it won't boot. The power led stays orange, no network access (I tried 192.168.1.1).
My board reads DIR-825B1 REV:A2. could this be a hardware issue?
I can successfully reinstall the 2.03NA firmware back.
-
Anything else out there worth grabbing for 3rd party for the Rev B.
*bump*
What's the latest on 3rd party f/w? Any new/good news on OpenWRT?