fis create linux
... Erase from 0xa8030000-0xa868ae2a: ......................................................................................................
... Program from 0x80041000-0x8069be2a at 0xa8030000: .....................................................................................................V
Can't program region at 0xa8680000: Unknown error
Code:
43424
Fonera 2100/2200
Firmware Version
DD-WRT v3.0-r43424 (06/16/20)
Kernel Version
Linux 3.2.102 #127919 Tue Jun 16 07:21:02 +04 2020 mips
MAC Address
00:18:84:A2:D5:95
Over "regular beta builds" it reports fonera 2201, this one show up Fonera 2100/2200.
wifi connection is up and running, can navigate over menus. But applying network changes ( lan, wan, vlan, got very strange logs:
Code:
bridge : interface ath0 successfully deleted from bridge br0
[ 664.850000] device ath0 left promiscuous mode
[ 664.850000] br0: port 1(ath0) entering forwarding state
bridge : bridge br0 successfully deleted
bridge br0 is still up; can't delete it
ttraff : traffic counter daemon successfully stopped
eth0: No such device
eth0: No such device
ntpclient : Network Time Protocol client successfully stopped
bridge : interface ath0 successfully deleted from bridge br0
device ath0 is not a slave of br0
bridge : bridge br0 successfully added
device br0 already exists; can't create bridge with the same name
[ 667.280000] device br0 entered promiscuous mode
[ 667.450000] device br0 left promiscuous mode
[ 667.480000] device br0 entered promiscuous mode
[ 667.520000] device br0 left promiscuous mode
cannot open /proc/sys/dev/wifi0/pollingmode
cannot open /proc/sys/dev/wifi0/maxvaps
ath0
iw: No such file or directory
cannot open /proc/sys/dev/wifi0/csma
bridge : interface ath0 successfully added to bridge br0
[ 669.320000] device ath0 entered promiscuous mode
[ 669.320000] br0: port 1(ath0) entering forwarding state
[ 669.330000] br0: port 1(ath0) entering forwarding state
sh: can't create /sys/class/net/ath0/brport/multicast_to_unicast: nonexistent directory
lo: File exists
cannot open /proc/net/arp_spoofing_enable
cannot open /proc/sys/net/netfilter/nf_conntrack_helper
cannot open /proc/sys/net/ipv4/conf/br0/loop
vpn modules : vpn modules successfully unloaded
vpn modules : nf_conntrack_proto_gre successfully loaded
vpn modules : nf_nat_proto_gre successfully loaded
vpn modules : nf_conntrack_pptp successfully loaded
vpn modules : nf_nat_pptp successfully loaded
eth0: No such device
eth0: No such device
dnsmasq : daemon successfully stopped
dnsmasq : daemon successfully started
wland : daemon successfully stopped
wland : daemon successfully started
wan : WAN is up. IP: 192.168.4.200
cannot open /proc/net/arp_spoofing_enable
cannot open /proc/sys/net/netfilter/nf_conntrack_helper
cannot open /proc/sys/net/ipv4/conf/br0/loop
Over setup ---> networking,
Current Bridging Table, is empty, and couldn't modify or add any entry at Assign to Bridge tab.
And couldn't get vlan0 vlan0 eth0 up, even with startup script as previously:
Joined: 08 May 2018 Posts: 14208 Location: Texas, USA
Posted: Wed Jun 17, 2020 17:45 Post subject:
Thanks for the report. I sent an email already asking for progress updates from the developer to see if he ran into the same issues flashing, no reply yet. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Thu Jun 18, 2020 2:29 Post subject:
root@DD-WRT:~# softwarerevision
43432
root@DD-WRT:~# nvram get DD_BOARD
Fonera 2201
root@DD-WRT:~#
works. the 2201 has 2 ethernet ports. the older 2200 has just a single ethernet port and was never a problem. only the dual ethernet problem had a issue with the switch. the single port variant always worked. and yes your eth0 might not be bridged. thats always the case if wan is enabled. this turns eth0 to a wan port if wireless is in ap mode. it all depends how you configured it. _________________ "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
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Thu Jun 18, 2020 2:45 Post subject:
maybe also take a look on my microredboot for the fonera. it has full tftp recovery support with just pushin the reset button and it boots in just 5 seconds
but dont do it if you are not sure. 2009 was the last time i touched this test fonera 2200 on my table.
ah and btw. i will work on this fonera the next days to switch the driver to ath5k which will allow us to support wpa3 and other things we really should not do on such a small device _________________ "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
maybe also take a look on my microredboot for the fonera. it has full tftp recovery support with just pushin the reset button and it boots in just 5 seconds
but dont do it if you are not sure. 2009 was the last time i touched this test fonera 2200 on my table.
ah and btw. i will work on this fonera the next days to switch the driver to ath5k which will allow us to support wpa3 and other things we really should not do on such a small device
Thanx, both of you, BS and kernel-panic69.
I will try a shoot with this microredboot. I can easy recover them with a external flash programmer.
Where I can get build 43432 ?, only see:
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Thu Jun 18, 2020 10:50 Post subject:
just use the latest. the version i mentioned was internal but the newer one works too of course
i also have now a wpa3 and mesh capable version available. its experimental and uses mac80211 based drivers. its working on my local device but not widelly tested. if you want to try it by yourself. i attached you this version here. since it uses a newer driver. some gui things are changed. it maybe that you need to reconfigure your security settings
for the microredboot you will also find a documentation in our wiki which shows you how to install it.
by default it will boot straight the firmware. to enter the redboot console you need to push the reset button. if you push it 5 seconds the nvram will be reset. if you push it 11 seconds a tftp server will start for recovery.
if you do nvram set resetbutton_enable=0 / nvram commit, the redboot will always start and the fast boot process is disabled. this is a trick if you have problems with your reset button
ah one thing. unlike the original bootloader the baudrate setting is 115200 for serial access and the default ip for tftp is 192.168.1.1 (i changed this on my device)
boot process with recovery
Quote:
MicroRedBoot v1.3, (c) 2009 DD-WRT.COM (Jul 6 2009)
CPU Clock: 184Mhz
Found Flash device SIZE=0x00800000 SECTORSIZE=0x00010000 FLASHBASE=0xA8000000
DD-WRT NVRAM with size = 25916 found on [0xA87D0000]
Board: Fonera 2201
reset button manual override detected! (nvram var resetbutton_enable=0)
Reset Button triggered
Booting Recovery RedBoot
loading.....
�+Ethernet eth0: MAC address 00:18:84:a0:c1:20
IP: 10.88.193.85, Default server: 10.88.193.134
RedBoot(tm) bootstrap and debug environment [RAM]
Non-certified release, version UNKNOWN - built 12:18:03, Jul 6 2009
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
Copyright (C) 2009 NewMedia-NET GmbH
Board: ap51
RAM: 0x80000000-0x81000000, [0x80031490-0x80fed000] available
FLASH: 0xa8000000 - 0xa87f0000, 128 blocks of 0x00010000 bytes each.
== Executing boot script in 2.000 seconds - enter ^C to abort
^C
RedBoot> ^C
RedBoot> ^C
RedBoot> tftpd
Warning: memory buffer for uploaded file may be on reserved RAM area.
TFTPD is running (using memory ranges: 0x80031800 - 0x80831800, 0x80831800 - 0x81011800).
TFTPD: Connect from 10.88.193.134 port 55114
TFTPD: Upload completed (got 5955612 bytes).
Checking uploaded file...
DD-WRT_FW: DD-WRT FW CRC Okay
DD-WRT: firmware format detected
*** Initialize FLASH Image System
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
DD-WRT_FW: flash base is 0xA8010000
... Erase from 0xa8010000-0xa85be000: ...........................................................................................
... Program from 0x8083181c-0x80ddf81c at 0xa8010000: ...........................................................................................
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
DD-WRT_FW: flashing done
Flash update complete.
boot process with fastboot and no recovery
Quote:
MicroRedBoot v1.3, (c) 2009 DD-WRT.COM (Jul 6 2009)
CPU Clock: 184Mhz
Found Flash device SIZE=0x00800000 SECTORSIZE=0x00010000 FLASHBASE=0xA8000000
DD-WRT NVRAM with size = 25892 found on [0xA87D0000]
Board: Fonera 2201
found bootable image: [linux] at [0xA8010000] EP [0x80041000]
Booting Linux
loading..................................................................................[ 0.000000] Linux version 3.2.102 (root@linux) (gcc version 9.2.0 (OpenWrt GCC 9.2.0 r10890-7d542dc804) ) #127994 Thu Jun 18 13:49:35 +04 2020
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU revision is: 00019064 (MIPS 4KEc)
[ 0.000000] Determined physical RAM map:
[ 0.000000] memory: 01000000 @ 00000000 (usable)
[ 0.000000] Zone PFN ranges:
[ 0.000000] Normal 0x00000000 -> 0x00001000
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[1] active PFN ranges
[ 0.000000] 0: 0x00000000 -> 0x00001000
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping off. Total pages: 4064
[ 0.000000] Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd init=/sbin/init
DD-WRT
Router Model
Fonera 2201
Firmware Version
DD-WRT v3.0-r43432 std (06/16/20)
Kernel Version
Linux 3.2.102 #127950 Tue Jun 16 12:04:08 +04 2020 mips
MAC Address
00:18:84:A2:D5:95
As I said previously, I was unsuccessful to update via redboot, CLI serial. I tried GarGoyle fonFlash for the 1st time, and voila ... I's alive...
At 1st boot, vlan's, routing tables, bridge, and ip configurations were messy. Made some corrections via CLI, and it's running flawlessly. Will keep this unit running for a while to see its performances.
Later, will try last version, and look at the microredboot.
Can't express my gratitude for you and Kernel-panic69.
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Thu Jun 18, 2020 13:30 Post subject:
but this is still the older version. my attachment in my post contains wpa3 and mesh support and has a totally different driver _________________ "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
but this is still the older version. my attachment in my post contains wpa3 and mesh support and has a totally different driver
Just saw your attached file now... upss.
Dumb question, shouldn't be linux.bin. I never could update via Firmware update Tab, always returned update fail, even working builds.
[ 0.420000] found 1
[ 0.430000] Found board config at 0xa87f0000
[ 0.430000] Radio config found at offset 0xf8(0x1f8) (a87f00f8)
[ 0.450000] gpio_proc: module loaded and /proc/gpio/ created
[ 0.460000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.470000] msgmni has been set to 25
[ 0.480000] io scheduler noop registered
[ 0.490000] io scheduler deadline registered (default)
[ 0.490000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[ 0.520000] serial8250: ttyS0 at MMIO 0xb1100003 (irq = 37) is a 16550A
[ 0.530000] serial8250 serial8250.0: unable to register port at index 0 (IO3f8 MEM0 IRQ4): -28
[ 0.540000] serial8250 serial8250.0: unable to register port at index 1 (IO2f8 MEM0 IRQ3): -28
[ 0.550000] serial8250 serial8250.0: unable to register port at index 2 (IO3e8 MEM0 IRQ4): -28
[ 0.560000] serial8250 serial8250.0: unable to register port at index 3 (IO2e8 MEM0 IRQ3): -28
[ 0.570000] gpiodev: gpio device registered with major 254
[ 0.590000] scanning for root partition
[ 0.590000]
[ 0.590000] found squashfs at 100000
[ 0.600000] found RedBoot partition at [0xA8000000]
[ 0.610000] found linux partition at [0xA8030000]
[ 0.610000] Creating 8 MTD partitions on "spiflash":
[ 0.620000] 0x000000000000-0x000000030000 : "RedBoot"
[ 0.630000] 0x000000030000-0x0000007d0000 : "linux"
[ 0.640000] 0x000000100000-0x0000005e0000 : "rootfs"
[ 0.660000] 0x0000005e0000-0x0000007d0000 : "ddwrt"
[ 0.670000] 0x0000007d0000-0x0000007e0000 : "nvram"
[ 0.690000] 0x0000007e0000-0x0000007f0000 : "FIS directory"
[ 0.700000] 0x0000007f0000-0x000000800000 : "board_config"
[ 0.720000] 0x000000000000-0x000000800000 : "fullflash"
[ 0.740000] PPP generic driver version 2.4.2
[ 0.740000] PPP BSD Compression module registered
[ 0.750000] PPP Deflate Compression module registered
[ 0.760000] PPP MPPE Compression module registered
[ 0.770000] NET: Registered protocol family 24
[ 0.770000] watchdog hb: 60 ISR: 0x20 IMR: 0xc8 WD : 0xa5e772fd WDC: 0x0
[ 0.780000] ar2315_wdt_probe using heartbeat 60 s cycles 2400000000
[ 0.780000] watchdog hb: 60 ISR: 0x20 IMR: 0xc8 WD : 0x8f065420 WDC: 0x0
[ 0.800000] u32 classifier
[ 0.800000] Performance counters on
[ 0.800000] input device check on
[ 0.810000] Actions configured
[ 0.810000] Netfilter messages via NETLINK v0.30.
[ 0.810000] nf_conntrack version 0.5.0 (207 buckets, 828 max)
[ 0.820000] nf_conntrack_rtsp v0.6.21 loading
[ 0.830000] nf_nat_rtsp v0.6.21 loading
[ 0.830000] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 0.840000] IPP2P v0.8.2 loading
[ 0.840000] TCP westwood registered
[ 0.850000] TCP hybla registered
[ 0.850000] TCP vegas registered
[ 0.850000] NET: Registered protocol family 17
[ 0.860000] Bridge firewalling registered
[ 0.860000] 8021q: 802.1Q VLAN Support v1.8
[ 0.870000] searching for nvram
[ 0.870000] nvram size = 0
[ 0.940000] SQUASHFS error: unable to read id index table
[ 0.940000] List of all partitions:
[ 0.950000] 1f00 192 mtdblock0 (driver?)
[ 0.950000] 1f01 7808 mtdblock1 (driver?)
[ 0.960000] 1f02 4992 mtdblock2 (driver?)
[ 0.960000] 1f03 1984 mtdblock3 (driver?)
[ 0.970000] 1f04 64 mtdblock4 (driver?)
[ 0.970000] 1f05 64 mtdblock5 (driver?)
[ 0.980000] 1f06 64 mtdblock6 (driver?)
[ 0.990000] 1f07 8192 mtdblock7 (driver?)
[ 0.990000] No filesystem could mount root, tried: squashfs
[ 1.000000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
[ 1.000000] Rebooting in 1 seconds..
Via gargoyle utility uploading linux.bin, I had success with:
Code:
DD-WRT
Router Model
Fonera 2201
Firmware Version
DD-WRT v3.0-r43443 std (06/17/20)
Kernel Version
Linux 3.2.102 #127954 Wed Jun 17 15:58:21 +04 2020 mips
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Thu Jun 18, 2020 18:21 Post subject:
flash it correct. the first log shows that your upload broke. since update takes 20 minutes and longer its dangerous if your connection breaks. _________________ "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
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Thu Jun 18, 2020 19:37 Post subject:
and consider i flashed alot just with web upgrade the last days. but never wireless. just wired _________________ "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
Got it.
The trick was to ignore upgrade fail, and let the action proceed to the end.
Code:
System
Router Name
DD-WRT
Router Model
Fonera 2201
Firmware Version
DD-WRT v3.0-r43443 std (06/18/20)
Kernel Version
Linux 3.2.102 #127994 Thu Jun 18 13:49:35 +04 2020 mips
MAC Address
00:18:84:A2:D5:95
Only "bug" I found so far, wifi led not show up, but wifi is up and connecting.
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Fri Jun 19, 2020 1:48 Post subject:
yes. the wifi led is not yet implemented. need to write some more code to archive this. i dont think this issue is critical now. and yes the upgrade fail message on some browsers are bogus. just wait until its finished. its all a problem of the poor flash chip on this device which is outstanding slow _________________ "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
