OpenWrt Forum Archive

Topic: Success with Belkin F5D9230-4!

The content of this topic has been archived on 26 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

In case anyone is interested, I just got OpenWrt fully working on my F5D9230-4 (v3000) with the Airlink AR525W firmware image.

Nobody else on the forum seems to have had any luck, so here are the instructions:

1) Go to the router config page (ex. https://192.168.2.1/), log in, and then go to ver.htm (ex. https://192.168.2.1/ver.htm).
2) Set firmware header checking to 0, apply, and wait for it to reboot.
3) Use the firmware upgrade page to upload the OpenWrt firmware intended for the Airlink AR525W (ex. openwrt-rdc-squashfs-ar525w.img). Do not use the -web.img version.
4) OpenWrt should be working after it reboots.

PS: In theory this should also work on other Gemtek WRTR-159G-based routers. They all use modified versions of the web interface and they should all have ver.htm.

I too have flashed this router successfully except that it locks up on me after a couple of hours and i have to power cycle to regain access was wondering if you had had this problem and if so how did you fix it?

Nevermind, I had the TX power up too high i dropped it down to 50 and all problems fixed smile

(Last edited by douggle on 11 Mar 2009, 22:57)

Any ideas how to get this to remember settings? Would appreciate a howto :> thanks

his didn't work for me, but then again I have the v3100.  Apparently even after setting the firmware header check to 0, the firmware still checks the firmware being uploaded and stops it from being uploaded all the way.  I tried using the -web version as well (as it should work but just has the interface with some incorrect outputs as it would think the device is an Airlink AR525W) but that doesn't upload either.   Would REALLY like to see some more support for this chipset or just ralink in general.

Hi! sorry for the bump, but great job on getting this working!!

A few questions though:

1) Does the Wireless work correctly?
2) Can it go into bridged mode?
3) Did you have to change the header on your firmware to use it?

The reason I ask #3 is because i tried this on my device, except it was a v5000, and it bricked it. Unfortunatly there is basically no documentation on this device, so i had quite a time figuring out how to un brick it...

Once i got it unbricked, i found out that the Boot loader (U-boot) checks the header of the firmware for Belkin's
"Magic Number" So far, i have seen no way to successfully trick the bootloader into thinking that the openwrt firmware is legit. All i can do is edit the header of a legit belkin firmware to reflash the router to its standard settings. Is there anything i can do to get OpenWRT on here?

If anyone can help that would be great. I'll post the things i learned to get it unbricked just in case someone else had the same problems i did.

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

I read, on the few sites that had specs for this router, that the F5D9230-4 had no serial port available for launching the console. Lucky for me, there is infact a serial port on this router. Luckier still, it has the same pinout as the AR-525W, which is well documented. I also had the benefit of unbricking the AR525 at the same time big_smile

Some things you need to know:

The Belkin F5D9230-4 (v5000) uses U-Boot bootloader instead of Redboot. I found U-boot far more confusing.

The correct settings for accessing the U-Boot through Putty are 57600, 8, N, 1, No Flow

When accessing U-boot, there is no break key (ctrl-c) like Redboot, but rather you must enter a menu choice within ~1 second of plugging in the router. You have to be very quick...

I think you can use pretty much any usb to serial adapter to hook this up to your computer, BUT you MUST have a Level Shifter. It wont work very well otherwise. you can do it without one, but when i did this, it ended up burning out my usb-serial adapter. Get a Level Shifter.

This router is reversed from most that ive seen in terms of tftp. once you log into u-boot, you have access to a tftp client, but you need to have a tftp server on your computer and the firmware file you wish to flash. you then can set the ip settings of the router in the tftp client (one of the menu choices- #2 i think) and access your computer.

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

if anyone needs help unbricking their router, i will try to help you, but this was my first real venture into the unbricking world.

(Last edited by darthcircuit on 23 Mar 2010, 20:39)

sorry for the bump, but i found out that the reason the v5000 f5d9230 doesnt like the ar525w firmware is because it is in fact a RALink chipset, not RDC.

unfortunately, my board suffered a horrible accident (something about voltages too high for the system) and i no longer have it.

just thought id post so that others with this router can check to see if your board is rdc before you try and flash.

Thanks jamend, flashed my F5D9230-4 successfully. The only thing I had to do was "mtd unlock rootfs_data" so it could remember the settings, other then that everything went smooth.

(Last edited by slackerus on 24 Dec 2009, 12:07)

I have a F5D9230-4 ver 3000fr ,CPU is 'RDC R3211-G',wifi chipset is 'RAlink RT2661t'.

I flashed it follow this thread. When it finished flashing ,I wait about 10 min, then unplug/plug the router. But it become a brick.

How can I recover it. Is there anything that I can refer to ?

(Last edited by cliusn on 23 Jan 2010, 09:52)

OK, I have recovered my F5D9230-4 ver 3000fr .
I do it following here http://forum.x-wrt.org/index.php/topic,641.0.html ,and I flash this firmware 'openwrt-rdc-jffs2-64k-ar525w.img' .
But its wifi don't work .I have set 'option disabled 0' in the /etc/config/wireless .

root@OpenWrt:~# lsmod |grep rt
xt_multiport            1456  5
x_tables                4884  37 ipt_TOS,ipt_tos,ipt_TTL,xt_MARK,ipt_ECN,xt_CLASSIFY,ipt_ttl,xt_time,xt_tcpmss,xt_statistic,xt_mark,xt_length,ipt_ecn,xt_DSCP,xt_dscp,ipt_IMQ,xt_string,xt_layer7,ipt_ipp2p,ipt_MASQUERADE,iptable_nat,xt_NOTRACK,xt_CONNMARK,ipt_recent,xt_helper,xt_conntrack,xt_connmark,xt_connbytes,xt_state,ipt_REJECT,xt_TCPMSS,ipt_LOG,xt_multiport,xt_mac,xt_limit,ip_tables,xt_tcpudp
rt61pci                11408  0
rt2x00pci               2448  1 rt61pci
rt2x00lib              11920  2 rt61pci,rt2x00pci
mac80211              106988  2 rt2x00pci,rt2x00lib
cfg80211               17216  2 rt2x00lib,mac80211
eeprom_93cx6             784  1 rt61pci
crc_itu_t                944  1 rt61pci

(Last edited by cliusn on 25 Jan 2010, 05:09)

I successfully got Open-wrt installed on my Belkin F5D9230-4 ver 3000uk. However, jamend's method would not work for me. Instead, I had to solder a serial connection onto the board according to this pinout: 
[   ] [RX   ] [       ] [       ] [TX   ]
       [GND1] [GND2] [Vcc1] [Vcc2]

settings are 38400, 8, N, 1, no flow (http://nuwiki.openwrt.org/oldwiki/OpenW … 101/AR525W)

Using the serial console, i got a prompt at redboot y pressing ctrl + c (there is only like a 1second window so you have to be fast.). in the serial console i typed:
tftpd
Then on the laptop i flashed it using the using the openwrt-rdc-squashfs-ar525w.img tftp method outlined here:
http://wiki.openwrt.org/doc/howto/tftp?s[]=tftp

I can now get the openwrt webpage on 192.168.1.1, and scan for wireless networks (which finds actual wireless networks), but cannot create a wireless network. When i click "enable" and save, it just lights the wireless LED but i cannot find any wireless network with my laptop.

Does anybody know of a solution to this?

Ok, i got a bit more progress made. I had tried to edit /etc/configuration/wireless to enable wireless by commenting out the line:
#       option disabled 1

However, I noticed that the F5D9230-4 wasnt saving the wireless configuration after a reboot. So i typed

dmesg; logread

and noticed a load of jffs related errors. I then entered

mtd erase rootfs_data
mtd unlock rootfs_data

and it now seems to remember its settings, and i was successfully able to comment out the line in the wireless configuration file. However, wireless *still* doesnt seem to work. Anybody have any other ideas i could try?

Thanks!

Is wpad-mini installed? Whats in logread and dmesg after you enabled the wireless?

Hey, Thanks for the reply, the command
dmesg; logread 

shows the following:

_______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 KAMIKAZE (8.09.2, r18961) -------------------------
  * 10 oz Vodka       Shake well with ice and strain
  * 10 oz Triple sec  mixture into 10 shot glasses.
  * 10 oz lime juice  Salute!
 ---------------------------------------------------
root@OpenWrt:/# dmesg; logread
Linux version 2.6.24.7 (agb@arrakis) (gcc version 4.1.2) #4 Tue Dec 29 17:24:44 UTC 2009
BIOS-provided physical RAM map:
 BIOS-e801: 0000000000000000 - 000000000009f000 (usable)
 BIOS-e801: 0000000000100000 - 0000000001000000 (usable)
16MB LOWMEM available.
Entering add_active_range(0, 0, 4096) 0 entries of 256 used
Zone PFN ranges:
  DMA             0 ->     4096
  Normal       4096 ->     4096
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0:        0 ->     4096
On node 0 totalpages: 4096
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 4064 pages, LIFO batch:0
  Normal zone: 0 pages used for memmap
  Movable zone: 0 pages used for memmap
DMI not present or invalid.
Allocating PCI resources starting at 10000000 (gap: 01000000:ff000000)
Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 4064
Kernel command line: console=ttyS0,38400 root=/dev/mtdblock1 noinitrd init=/etc/preinit
Initializing CPU#0
PID hash table entries: 64 (order: 6, 256 bytes)
console [ttyS0] enabled
Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Memory: 13940k/16384k available (1279k kernel code, 2056k reserved, 341k data, 132k init, 0k highmem)
virtual kernel memory layout:
    fixmap  : 0xffffa000 - 0xfffff000   (  20 kB)
    vmalloc : 0xc1800000 - 0xffff8000   ( 999 MB)
    lowmem  : 0xc0000000 - 0xc1000000   (  16 MB)
      .init : 0xc0298000 - 0xc02b9000   ( 132 kB)
      .data : 0xc023ffdd - 0xc029549c   ( 341 kB)
      .text : 0xc0100000 - 0xc023ffdd   (1279 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 49.53 BogoMIPS (lpj=99072)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
CPU: After all inits, caps: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Compat vDSO mapped to ffffe000.
CPU: 486
Checking 'hlt' instruction... OK.
Freeing SMP alternatives: 0k freed
net_namespace: 64 bytes
NET: Registered protocol family 16
PCI: Using configuration type 1
Setting up standard PCI resources
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
Time: pit clocksource has been installed.
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 512 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 512 bind 512)
TCP reno registered
rdc321x: init success
Total HugeTLB memory allocated, 0
squashfs: version 3.0 (2006/03/15) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler cfq registered (default)
Non-volatile memory driver v1.2
Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
flash device: 400000 at ffc00000
RDC3210 Flash: Found 1 x16 devices at 0x0 in 16-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040
RDC3210 Flash: Swapping erase regions for broken CFI table.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Creating 4 MTD partitions on "RDC3210 Flash":
0x00000000-0x003e0000 : "linux"
0x000ba240-0x00210000 : "romfs"
mtd: partition "romfs" doesn't start on an erase block boundary -- force read-only
0x00210000-0x003e0000 : "rootfs_data"
0x003e0000-0x00400000 : "bootldr"
Registered led device: rdc321x:dmz
nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
TCP vegas registered
NET: Registered protocol family 1
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
Using IPI Shortcut mode
VFS: Mounted root (squashfs filesystem) readonly.
Freeing unused kernel memory: 132k freed
Please be patient, while OpenWrt loads ...
mini_fo: using base directory: /
mini_fo: using storage directory: /jffs
PCI: Setting latency timer of device 0000:00:01.0 to 64
phy0: Selected rate control algorithm 'pid'
PPP generic driver version 2.4.2
ip_tables: (C) 2000-2006 Netfilter Core Team
r6040: RDC R6040 NAPI net driver,version 0.22 (25Mar2009)
PCI: Setting latency timer of device 0000:00:08.0 to 64
r6040: MAC address not initialized, generating random
r6040: RDC R6040 NAPI net driver,version 0.22 (25Mar2009)
PCI: Setting latency timer of device 0000:00:09.0 to 64
r6040: MAC address not initialized, generating random
br-lan: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
device eth1 entered promiscuous mode
br-lan: port 1(eth1) entering learning state
br-lan: topology change detected, propagating
br-lan: port 1(eth1) entering forwarding state
device wlan0 entered promiscuous mode
Aug  7 04:02:11 OpenWrt user.notice kernel: 0x000ba240-0x00210000 : "romfs"
Aug  7 04:02:11 OpenWrt user.warn kernel: mtd: partition "romfs" doesn't start on an erase block boundary -- force read-only
Aug  7 04:02:11 OpenWrt user.notice kernel: 0x00210000-0x003e0000 : "rootfs_data"
Aug  7 04:02:11 OpenWrt user.notice kernel: 0x003e0000-0x00400000 : "bootldr"
Aug  7 04:02:11 OpenWrt user.info kernel: Registered led device: rdc321x:dmz
Aug  7 04:02:11 OpenWrt user.warn kernel: nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
Aug  7 04:02:11 OpenWrt user.info kernel: TCP vegas registered
Aug  7 04:02:11 OpenWrt user.info kernel: NET: Registered protocol family 1
Aug  7 04:02:11 OpenWrt user.info kernel: NET: Registered protocol 
Aug  7 04:02:11 OpenWrt user.info kernel: family 17
Aug  7 04:02:11 OpenWrt user.info kernel: 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
Aug  7 04:02:11 OpenWrt user.info kernel: All bugs added by David S. Miller <davem@redhat.com>
Aug  7 04:02:11 OpenWrt user.warn kernel: Using IPI Shortcut mode
Aug  7 04:02:11 OpenWrt user.warn kernel: VFS: Mounted root (squashfs filesystem) readonly.
Aug  7 04:02:11 OpenWrt user.info kernel: Freeing unused kernel memory: 132k freed
Aug  7 04:02:11 OpenWrt user.warn kernel: Please be patient, while OpenWrt loads ...
Aug  7 04:02:11 OpenWrt user.info kernel: mini_fo: using base directory: /
Aug  7 04:02:11 OpenWrt user.info kernel: mini_fo: using storage directory: /jffs
Aug  7 04:02:11 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 304) exited. Scheduling for restart.
Aug  7 04:02:11 OpenWrt daemon.info init: init: starting pid 330, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:12 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 330) exited. Scheduling for restart.
Aug  7 04:02:12 OpenWrt daemon.info init: init: starting pid 368, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:14 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 368) exited. Scheduling for restart.
Aug  7 04:02:14 OpenWrt daemon.info init: init: starting pid 385, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:15 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 385) exited. Scheduling for restart.
Aug  7 04:02:15 OpenWrt daemon.info init: init: starting pid 417, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:16 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 417) exited. Scheduling for restart.
Aug  7 04:02:16 OpenWrt daemon.info init: init: starting pid 430, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:16 OpenWrt user.debug kernel: PCI: Setting latency timer of device 0000:00:01.0 to 64
Aug  7 04:02:16 OpenWrt user.debug kernel: phy0: Selected rate control algorithm 'pid'
Aug  7 04:02:17 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 430) exited. Scheduling for restart.
Aug  7 04:02:17 OpenWrt daemon.info init: init: starting pid 457, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:17 OpenWrt user.info kernel: PPP generic driver version 2.4.2
Aug  7 04:02:18 OpenWrt user.info kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Aug  7 04:02:18 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 457) exited. Scheduling for restart.
Aug  7 04:02:18 OpenWrt daemon.info init: init: starting pid 490, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:19 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 490) exited. Scheduling for restart.
Aug  7 04:02:19 OpenWrt daemon.info init: init: starting pid 529, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:19 OpenWrt user.info kernel: <6>r6040: RDC R6040 NAPI net driver,version 0.22 (25Mar2009)
Aug  7 04:02:19 OpenWrt user.debug kernel: PCI: Setting latency timer of device 0000:00:08.0 to 64
Aug  7 04:02:20 OpenWrt user.warn kernel: r6040: MAC address not initialized, generating random
Aug  7 04:02:20 OpenWrt user.info kernel: <6>r6040: RDC R6040 NAPI net driver,version 0.22 (25Mar2009)
Aug  7 04:02:20 OpenWrt user.debug kernel: PCI: Setting latency timer of device 0000:00:09.0 to 64
Aug  7 04:02:20 OpenWrt user.warn kernel: r6040: MAC address not initialized, generating random
Aug  7 04:02:20 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 529) exited. Scheduling for restart.
Aug  7 04:02:20 OpenWrt daemon.info init: init: starting pid 553, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:21 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 553) exited. Scheduling for restart.
Aug  7 04:02:21 OpenWrt daemon.info init: init: starting pid 584, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:22 OpenWrt user.err kernel: br-lan: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
Aug  7 04:02:22 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 584) exited. Scheduling for restart.
Aug  7 04:02:22 OpenWrt daemon.info init: init: starting pid 618, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:22 OpenWrt user.info kernel: device eth1 entered promiscuous mode
Aug  7 04:02:22 OpenWrt user.info kernel: br-lan: port 1(eth1) entering learning state
Aug  7 04:02:22 OpenWrt user.info kernel: br-lan: topology change detected, propagating
Aug  7 04:02:22 OpenWrt user.info kernel: br-lan: port 1(eth1) entering forwarding state
Aug  7 04:02:23 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 618) exited. Scheduling for restart.
Aug  7 04:02:23 OpenWrt daemon.info init: init: starting pid 657, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:24 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 657) exited. Scheduling for restart.
Aug  7 04:02:24 OpenWrt daemon.info init: init: starting pid 681, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:25 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 681) exited. Scheduling for restart.
Aug  7 04:02:25 OpenWrt daemon.info init: init: starting pid 710, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:26 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 710) exited. Scheduling for restart.
Aug  7 04:02:26 OpenWrt daemon.info init: init: starting pid 751, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:27 OpenWrt user.info kernel: device wlan0 entered promiscuous mode
Aug  7 04:02:27 OpenWrt user.info sysinit: Loading defaults
Aug  7 04:02:27 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 751) exited. Scheduling for restart.
Aug  7 04:02:27 OpenWrt daemon.info init: init: starting pid 780, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:28 OpenWrt user.info sysinit: Loading synflood protection
Aug  7 04:02:29 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 780) exited. Scheduling for restart.
Aug  7 04:02:29 OpenWrt daemon.info init: init: starting pid 804, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:29 OpenWrt user.info sysinit: Adding custom chains
Aug  7 04:02:29 OpenWrt user.info sysinit: Loading zones
Aug  7 04:02:30 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 804) exited. Scheduling for restart.
Aug  7 04:02:30 OpenWrt daemon.info init: init: starting pid 855, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:30 OpenWrt user.info sysinit: Loading forwarding
Aug  7 04:02:30 OpenWrt user.info sysinit: Loading redirects
Aug  7 04:02:30 OpenWrt user.info sysinit: Loading rules
Aug  7 04:02:30 OpenWrt user.info sysinit: Loading includes
Aug  7 04:02:31 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 855) exited. Scheduling for restart.
Aug  7 04:02:31 OpenWrt daemon.info init: init: starting pid 888, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:32 OpenWrt user.notice root: adding lan (br-lan) to firewall zone lan
Aug  7 04:02:32 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 888) exited. Scheduling for restart.
Aug  7 04:02:32 OpenWrt daemon.info init: init: starting pid 918, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:33 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 918) exited. Scheduling for restart.
Aug  7 04:02:33 OpenWrt daemon.info init: init: starting pid 937, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:33 OpenWrt authpriv.info dropbear[943]: Running in background
Aug  7 04:02:34 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 937) exited. Scheduling for restart.
Aug  7 04:02:34 OpenWrt daemon.info init: init: starting pid 964, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:35 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 964) exited. Scheduling for restart.
Aug  7 04:02:35 OpenWrt daemon.info init: init: starting pid 974, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:36 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 974) exited. Scheduling for restart.
Aug  7 04:02:36 OpenWrt daemon.info init: init: starting pid 979, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:37 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 979) exited. Scheduling for restart.
Aug  7 04:02:37 OpenWrt daemon.info init: init: starting pid 984, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:38 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 984) exited. Scheduling for restart.
Aug  7 04:02:38 OpenWrt daemon.info init: init: starting pid 995, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:38 OpenWrt daemon.info dnsmasq[1001]: started, version 2.47 cachesize 150
Aug  7 04:02:38 OpenWrt daemon.info dnsmasq[1001]: compile time options: IPv6 GNU-getopt no-DBus no-I18N TFTP
Aug  7 04:02:38 OpenWrt daemon.info dnsmasq[1001]: DHCP, IP range 192.168.1.100 -- 192.168.1.251, lease time 12h
Aug  7 04:02:38 OpenWrt daemon.info dnsmasq[1001]: using local addresses only for domain lan
Aug  7 04:02:38 OpenWrt daemon.warn dnsmasq[1001]: no servers found in /tmp/resolv.conf.auto, will retry
Aug  7 04:02:38 OpenWrt daemon.info dnsmasq[1001]: read /etc/hosts - 1 addresses
Aug  7 04:02:38 OpenWrt daemon.info dnsmasq[1001]: read /etc/ethers - 0 addresses
Aug  7 04:02:39 OpenWrt daemon.info dnsmasq[1001]: DHCPREQUEST(br-lan) 192.168.1.174 00:19:e3:35:c5:74 
Aug  7 04:02:39 OpenWrt daemon.info dnsmasq[1001]: DHCPACK(br-lan) 192.168.1.174 00:19:e3:35:c5:74 MacBook
Aug  7 04:02:39 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 995) exited. Scheduling for restart.
Aug  7 04:02:39 OpenWrt daemon.info init: init: starting pid 1012, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:40 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1012) exited. Scheduling for restart.
Aug  7 04:02:40 OpenWrt daemon.info init: init: starting pid 1017, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:41 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1017) exited. Scheduling for restart.
Aug  7 04:02:41 OpenWrt daemon.info init: init: starting pid 1022, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:42 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1022) exited. Scheduling for restart.
Aug  7 04:02:42 OpenWrt daemon.info init: init: starting pid 1027, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:43 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1027) exited. Scheduling for restart.
Aug  7 04:02:43 OpenWrt daemon.info init: init: starting pid 1040, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:44 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1040) exited. Scheduling for restart.
Aug  7 04:02:44 OpenWrt daemon.info init: init: starting pid 1045, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:45 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1045) exited. Scheduling for restart.
Aug  7 04:02:45 OpenWrt daemon.info init: init: starting pid 1050, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:46 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1050) exited. Scheduling for restart.
Aug  7 04:02:46 OpenWrt daemon.info init: init: starting pid 1055, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:47 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1055) exited. Scheduling for restart.
Aug  7 04:02:47 OpenWrt daemon.info init: init: starting pid 1060, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:48 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1060) exited. Scheduling for restart.
Aug  7 04:02:48 OpenWrt daemon.info init: init: starting pid 1065, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:49 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1065) exited. Scheduling for restart.
Aug  7 04:02:49 OpenWrt daemon.info init: init: starting pid 1070, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:50 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1070) exited. Scheduling for restart.
Aug  7 04:02:50 OpenWrt daemon.info init: init: starting pid 1075, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:51 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1075) exited. Scheduling for restart.
Aug  7 04:02:51 OpenWrt daemon.info init: init: starting pid 1080, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:52 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1080) exited. Scheduling for restart.
Aug  7 04:02:52 OpenWrt daemon.info init: init: starting pid 1085, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:53 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1085) exited. Scheduling for restart.
Aug  7 04:02:53 OpenWrt daemon.info init: init: starting pid 1090, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:54 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1090) exited. Scheduling for restart.
Aug  7 04:02:54 OpenWrt daemon.info init: init: starting pid 1095, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:56 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1095) exited. Scheduling for restart.
Aug  7 04:02:56 OpenWrt daemon.info init: init: starting pid 1100, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:57 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1100) exited. Scheduling for restart.
Aug  7 04:02:57 OpenWrt daemon.info init: init: starting pid 1105, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:58 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1105) exited. Scheduling for restart.
Aug  7 04:02:58 OpenWrt daemon.info init: init: starting pid 1110, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:02:59 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1110) exited. Scheduling for restart.
Aug  7 04:02:59 OpenWrt daemon.info init: init: starting pid 1115, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:03:00 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1115) exited. Scheduling for restart.
Aug  7 04:03:00 OpenWrt daemon.info init: init: starting pid 1120, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:03:01 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1120) exited. Scheduling for restart.
Aug  7 04:03:01 OpenWrt daemon.info init: init: starting pid 1125, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:03:02 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1125) exited. Scheduling for restart.
Aug  7 04:03:02 OpenWrt daemon.info init: init: starting pid 1130, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:03:03 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1130) exited. Scheduling for restart.
Aug  7 04:03:03 OpenWrt daemon.info init: init: starting pid 1135, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:03:04 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1135) exited. Scheduling for restart.
Aug  7 04:03:04 OpenWrt daemon.info init: init: starting pid 1140, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:03:05 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1140) exited. Scheduling for restart.
Aug  7 04:03:05 OpenWrt daemon.info init: init: starting pid 1145, tty '/dev/ttyS1': '/bin/ash --login'
Aug  7 04:03:06 OpenWrt daemon.info init: init: process '/bin/ash --login' (pid 1145) exited. Scheduling for restart.
Aug  7 04:03:06 OpenWrt daemon.info init: init: starting pid 1151, tty '/dev/ttyS1': '/bin/ash --login'
root@OpenWrt:/#

My Wireless config file is as follows:
config 'wifi-device' 'wlan0'
        option 'type' 'mac80211'
        option 'disabled' '0'
        option 'channel' '2'

config 'wifi-iface'
        option 'device' 'wlan0'
        option 'network' 'lan'
        option 'mode' 'ap'
        option 'encryption' 'none'
        option 'ssid' 'OpenWr'


How do I check if wpad-mini is installed?

(Last edited by SchrodingersCat on 26 Apr 2010, 01:42)

Oh, I see you use 8.09.2 - that has very limited support for mac80211 drivers and wpad didn't exist back then, hostapd was used instead.
You can check the installed packages with opkg list_installed

Thanks for the reply, ive tried to install wpad-mini, but with no luck (i got a weird error), so i tried installing hostapd instead:

root@OpenWrt:/# opkg update           
Downloading http://downloads.openwrt.org/kamikaze/8.09.2/rdc/packages/Packages.gz
Connecting to downloads.openwrt.org (78.24.191.177:80)
Packages.gz          100% |*******************************|   143k 00:00:00 ETA
Inflating http://downloads.openwrt.org/kamikaze/8.09.2/rdc/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/snapshots
root@OpenWrt:/#opkg upgrade
root@OpenWrt:/# opkg install wpad-mini
An error ocurred, return value: -1209119224.
root@OpenWrt:/# opkg install hostapd
....
root@OpenWrt:/# wifi up
Configuration file: /var/run/hostapd-wlan0.conf
Line 2: invalid/unknown driver 'nl80211'
1 errors found in configuration file '/var/run/hostapd-wlan0.conf'
enable_mac80211(wlan0): Failed to set up wpa for interface wlan0

I tried some of the latest builds located here here: http://downloads.openwrt.org/snapshots/trunk/rdc/ and here http://downloads.x-wrt.org/xwrt/kamikaz … c/default/
I tried openwrt-rdc-squashfs-ar525w.img, openwrt-rdc-jffs2-64k-ar525w.img , and openwrt-rdc-jffs2-128k-ar525w.img.
But they all just froze after the redboot stage:

RedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version v2_0 - built 18:31:11, Aug  4 2005

Platform: PC (I386)
Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

RAM: 0x00000000-0x000f0000, 0x00072ed0-0x000a0000 available
ver 00:0003  05-24-05

<press Ctrl+C to enter prompt mode>

# Activate RDC-Keilven's RS232 Patch V2
RedBoot>
# Kernel size = 17568 bytes
# FW size = 1703940 bytes

# fwcheck: base = 0x00400000, size = 0x00000400
# Firmware Checksum O.K
# Kernel copying......BEGIN
# Kernel copying......FINISH

mem_size: 1000000

The only build that didnt freeze at this stage was the 8.09.2. Is there any way to get the wifi working on this build, or to stop the newer builds from hanging?

(Some other information: The Belkin F5D9230-4 ver 3000 is based on a RDC R3211-G processor, Ralink RT2661T wireless chipset and a IC IP175C ethernet controller.)

(Last edited by SchrodingersCat on 26 Apr 2010, 16:47)

Just to update, im still having no luck getting the kernel to boot on the router. I have tried the latest builds from http://downloads.openwrt.org/snapshots/trunk/rdc/ with no luck. Could it be a memory issue?

here is the full terminal output from turning on the router, to flashing it, to resetting it, to where it finally freezes at "mem_size: 1000000"

+Ethernet eth0: MAC address 00:00:01:02:03:04
IP: 192.168.1.1/255.255.255.0, Gateway: 192.168.1.254
Default server: 0.0.0.0

RedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version v2_0 - built 18:31:11, Aug  4 2005

Platform: PC (I386)
Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

RAM: 0x00000000-0x000f0000, 0x00072ed0-0x000a0000 available
ver 00:0003  05-24-05

<press Ctrl+C to enter prompt mode>

# Activate RDC-Keilven's RS232 Patch V2
RedBoot> ^C
RedBoot> ^C
RedBoot> ^C
RedBoot> ^C
RedBoot> tftpd
# Dante's tiny tftpd is ready......
WRequest from 192.168.1.100: [openwrt-rdc-jffs2-64k-ar525w.img, octet]

# Firmware Checksum O.K
# DFLASH: SRC=0x00400000, DST=0xFFC00000, LEN=0x00290004
# Decide to use AMD/Fujitsu Standard command set.
# MFG ID = 0x007F, DEV ID = 0x22F6
Flash size = 4 MB
# Erasing..........................................
# Writing..........................................
# Finishing successfully...
# Firmware Upgrade Finished, and shotdown the TFTPD......
RedBoot> reset
... Resetting.+Ethernet eth0: MAC address 00:00:01:02:03:04
IP: 192.168.1.1/255.255.255.0, Gateway: 192.168.1.254
Default server: 0.0.0.0

RedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version v2_0 - built 18:31:11, Aug  4 2005

Platform: PC (I386)
Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

RAM: 0x00000000-0x000f0000, 0x00072ed0-0x000a0000 available
ver 00:0003  05-24-05

<press Ctrl+C to enter prompt mode>

# Activate RDC-Keilven's RS232 Patch V2
RedBoot>
# Kernel size = 851936 bytes
# FW size = 2686980 bytes

# fwcheck: base = 0x00400000, size = 0x00000400
# Firmware Checksum O.K
# Kernel copying......BEGIN
# Kernel copying......FINISH

mem_size: 1000000
jamend wrote:

In case anyone is interested, I just got OpenWrt fully working on my F5D9230-4 (v3000) with the Airlink AR525W firmware image.

Nobody else on the forum seems to have had any luck, so here are the instructions:

1) Go to the router config page (ex. https://192.168.2.1/), log in, and then go to ver.htm (ex. https://192.168.2.1/ver.htm).
2) Set firmware header checking to 0, apply, and wait for it to reboot.
3) Use the firmware upgrade page to upload the OpenWrt firmware intended for the Airlink AR525W (ex. openwrt-rdc-squashfs-ar525w.img). Do not use the -web.img version.
4) OpenWrt should be working after it reboots.

PS: In theory this should also work on other Gemtek WRTR-159G-based routers. They all use modified versions of the web interface and they should all have ver.htm.

Ill give this a go on the F5D7230-4 1000W based on:

Broadcom 4710
RAM 16 MB
FLASH 4 MB
DD-WRT: ftp://dd-wrt.com/others/eko/V24_TNG/svn … _micro.bin
OpenWRT: http://downloads.openwrt.org/backfire/10.03/brcm47xx/

Firmware must be less then 3.5 MB
http://www.dd-wrt.com/phpBB2/viewtopic. … 180#239052

Watch this space big_smile

(Last edited by francisuk on 10 Aug 2010, 19:40)

Hi folks,

I am also playing around whit a "Belkin F5D9230-4 ver.3000de" Router for about four month now
and got it at least partially working.

What I did:
 
  checked out backfire from svn (revision 23698)
  changed platform to RDC321x
  disabled "CONFIG_MAGIC_SYSRQ" in backfire/target/linux/generic-2.6/config-2.6.30
  build the image

Could anybody confirm that this works for their routers too?

Unfortunately, after enabling "kmod_ipv6"  the kernel also doesn't boot anymore.

matti

having an issue with the 3100 also,

http://members.cox.net/jdsanchez473/fw-error.jpg

Not sure what to think about that... Uploads the belkin firmware fine, but openwrt-rdc-squashfs-ar525w.img give a write fail.

(Last edited by WoR473 on 10 Aug 2011, 19:35)

The discussion might have continued from here.