I have 2 DLINK DWL-2100AP , setting a higher power trasmission with a panel of 15db attached, make the router continuely reboot. So i substitute with 2 linksys WRT54GL some months ago.
if you want, and someone need/give help, i can use this 2 units as guinea-pig :)
i have also some conexant AccessRunner ADSL router to burn, if needed.
I have a DWL-2100AP with openwrt kamikaze.
I have replace the bootloader with redboot
I have compiled a pachted version of kamikaze and loaded on it.
It work very good.
I think dd-wrt can work with no problem on the 2100AP.
I have tried the Buffalo WHR-HP-AG108, the fonera and the meraki version on it but i receive kernel panic.
I think it is needed to recompile ad-hoc, but i think it is possible
the following text is copied from the email sent to BS:
"Hi,
Some time ago I read in the forum about the 2100 dd-wrt porting, the only problem you have is that you don't have a device to port, am I right?
So I was thinking about sending you one 2100 so that you could port dd-wrt... Would it be ok for you?
Best Regards"
the following text is copied from the email sent to BS:
"Hi,
Some time ago I read in the forum about the 2100 dd-wrt porting, the only problem you have is that you don't have a device to port, am I right?
So I was thinking about sending you one 2100 so that you could port dd-wrt... Would it be ok for you?
Best Regards"
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Tue Sep 04, 2007 13:02 Post subject:
if you flash the WHR HP AG108 firmware in the right way it should work. if not, some adjustment for the flash memory support are maybe needed. hard to tell without having this device on my table _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Posted: Sat Sep 08, 2007 16:26 Post subject: DWL-5000AP
I have a couple of this AP, is this AP support by DDWRT...?
Its and old one but the can get a 50 Mbit/s transfer wireless an also have turbo mode at 72 Mbit.
I have tried the 24 RC3 for fonera, meraki and buffalo AG108 on my 2100AP
When redboot load the firmware and try to start, this is the result:
Code:
lzma_init: initialize the decoder
decompression error: insufficient memory
RedBoot> exec
Now booting linux kernel:
Base address 0x80080000 Entry 0x80041000
Cmdline :
$T04thread:00000001;25:80041000;1d:80702170;#32+
I have replace the original kernel with the openwrt kamikaze 7.07 kernel.
So, i tried openwrt kernel + dd-wrt fs
This is the result:
Code:
lzma_init: initialize the decoder
lzma_inflate: decompress stream
lzma_inflate; copy decodification code to RAM
Image loaded from 0x80041000-0x80289086
RedBoot> exec
Now booting linux kernel:
Base address 0x80080000 Entry 0x80041000
Cmdline :
Linux version 2.6.19.2 (ramponis@ramponis-desktop) (gcc version 4.1.2) #11 Tue J
ul 10 13:51:29 CEST 2007
CPU revision is: 0001800a
Determined physical RAM map:
memory: 01000000 @ 00000000 (usable)
Initrd not found or empty - disabling initrd
Built 1 zonelists. Total pages: 4064
Kernel command line: console=ttyS0,9600 rootfstype=squashfs,jffs2 init=/etc/prei
nit
Primary instruction cache 16kB, physically tagged, 4-way, linesize 16 bytes.
Primary data cache 16kB, 4-way, linesize 16 bytes.
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
PID hash table entries: 64 (order: 6, 256 bytes)
Using 90.000 MHz high precision timer.
Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Memory: 13536k/16384k available (1942k kernel code, 2848k reserved, 282k data, 1
12k init, 0k highmem)
Mount-cache hash table entries: 512
Checking for 'wait' instruction... available.
NET: Registered protocol family 16
Radio config found at offset 0x10000(0x100)
NET: Registered protocol family 2
IP route cache hash table entries: 128 (order: -3, 512 bytes)
TCP established hash table entries: 512 (order: -1, 2048 bytes)
TCP bind hash table entries: 256 (order: -2, 1024 bytes)
TCP: Hash tables configured (established 512 bind 256)
TCP reno registered
squashfs: version 3.0 (2006/03/15) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 1 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0xbc000003 (irq = 37) is a 16550A
eth0: Dropping NETIF_F_SG since no checksum feature.
eth0: Atheros AR231x: 00:13:46:60:cb:7c, irq 4
physmap platform flash device: 00400000 at 1e000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
Amd/Fujitsu Extended Query Table at 0x0041
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
cmdlinepart partition parsing not available
Searching for RedBoot partition table in physmap-flash.0 at offset 0x3d0000
5 RedBoot partitions found on MTD device physmap-flash.0
Creating 5 MTD partitions on "physmap-flash.0":
0x00000000-0x00030000 : "RedBoot"
0x00030000-0x000f0000 : "vmlinux.bin.l7"
0x000f0000-0x003c0000 : "rootfs"
0x003c0000-0x003c1000 : "RedBoot config"
0x003d0000-0x003e0000 : "FIS directory"
nf_conntrack version 0.5.0 (128 buckets, 1024 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
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>
alfter that i receive a long list of this error...
Code:
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000: 0x7471 in
stead
And then...
Code:
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x002a0024: 0x5349 in
stead
Further such events for this erase block will not be printed
Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
empty_blocks 2, bad_blocks 0, c->nr_blocks 45
VFS: Cannot open root device "<NULL>" or unknown-block(31,2)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)