Dear,
I had Netgear DM200 and firmware 19.07.8 works fine, now I have upgrade to firmware 21.02 I used
"openwrt-21.02.0-lantiq-xrx200-netgear_dm200-squashfs-sysupgrade"
, but now my router has stopped work and I can't connect my router, I try use reset button but no solution and try use
failsafe mode but again I can't never connet my router ip 192.168.1.1, my router is died.
Any idea how solve this problems?
Giovanni
Had exactly the same problem myself. It appears as if 21.02 is broken for the DM200. I've already raised a ticket on the bugtracker for it.
To recover, please use the following netgear instructions
https://kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP
I successfully followed them and recovered back to 19.07.8
You can recover with the TFTP method @madhatter , or the nmrpflash method
Stick to 19.07.8
Your device is old, and barely fits the need for 21.02. Even if the image firmware is provided by openwrt, there is no certainty that it can be flashed and ran successfully on such limited device. Even if it runs, performance will be sluggish.
I had exactly the same case a couple of years ago with an old device. It was able to run lede 17, but I have never succeeded to install 18.06 nor 19.07 which had bigger images firmwares.
That advice is plain wrong, with 21.02.0 released, the time for 19.07.x is up (there might be one final wrap-up release, but that's it) - and new security issues are found and fixed (in master and the maintained release branches) regularly.
Yes, there are lantiq devices with better specifications, but the dm200 should still be supported just fine (which doesn't preclude bugs) - it's a freaking VDSL modem after all, so you can't expect too much from it to begin with.
Dear madhatter,
thank you for help, your solution is very nice and I add other solution with "nmrpflash"
here easy video for netgear users https://youtu.be/DUZouixjko0
Now my DM 200 run 19.07.8 and run fine.
Giovanni
Dear badulesia,
thk for help I used nmrpflash and recovered my DM200.
Yes, it's old modem/router, but for me it perfect because I need only modem fuctions, my config
Giovanni
I agreed to the security point of view.
My idea is that the image provide by openwrt maybe to large. 4.8 MB for 19.07.8 and 5.8 MB for 21.02.0, for a device with 8 MB.
If you remember a couple of years ago, devices with 4/32 memory begin to be deprecated. Openwrt still provided 19.07 images for such devices, but they were too large, and flashing mandatory leads to bricking.
For example, I had this issue with the netgear 3500v2. 19.08.7 file is 4.1 MB large, but you can't flash more than 3.4 MB. No way, even with a custom build. So I had to stick to LEDE 17 ... despite no security update.
Image files are generated with scripts. It is obvious that the Openwrt dev team can't physically test on each device. So on limited device, users may encounter file size issues.
In the thread case, my advice is to stick to 19.07 until it is confirmed that 21.02 images can be flashed successfully. Apparently it can't.
such a great tool.
Well as long as your device fits your need, enjoy.
As I answered to @slh, you may encounter a problem with the image file size. 21.02 image is 1MB larger than 19.07. Try to build a lighter image (no luci .. read doc) and see if it runs. I agree on the will to update to 21.02 for security (@slh answer), but you may not be able to do so.
delfo2000 - glad you're back up and and running.
I also find the DM200 perfect for my needs and do not think of the device as old (opinions will always vary on age matters ).
Using 19.07, performance is excellent on an 80/20 FTTC connection. Also the dimensions and form factor of the device are ideal for where I have to locate it.
I raised a bugtracker item hoping that the problem will be fixed but I appreciate it's a device that is unlikely to have been tested during development of 21.02. Unfortunately, trying to diagnose what is wrong is above my level of expertise.
Whatever happens, OpenWRT is far better than the stock Netgear firmware.
I recall some time ago discussion about there being a bootloader limitation on the kernel size for the DM200 which was probably going to require a modified kernel configuration. Whether that happened and recent updates to compiler/kernel versions have resulted in the kernel size limit now being exceeded I don't know - the only way to find out is to attach a serial connection and get the full boot log.
Dear,
I'm waiting (next week) other DM200 when it will arrive I try serial connections and check boot logs
Now I can't because my DM200 working hard my line.
Giovanni
I only have an Ethernet cable, so not much help there I'm afraid.
I did find an earlier problem with the DM200 (link below) but unfortunately I do not understand enough to know if it's relevant to the current error, sorry.
https://lists.openwrt.org/pipermail/openwrt-devel/2019-January/021207.html
I also noticed that some devices have had problems with the size of the mtd partitions, so I've shown the DM200 details below in case that is useful. Apologies once again. sadly out of my depth here.
root@OpenWrt:/# cat /proc/mtd
dev: size erasesize name
mtd0: 00020000 00010000 "uboot"
mtd1: 00010000 00010000 "gphyfirmware"
mtd2: 007b0000 00010000 "firmware"
mtd3: 00200000 00010000 "kernel"
mtd4: 005b0000 00010000 "rootfs"
mtd5: 00320000 00010000 "rootfs_data"
mtd6: 00010000 00010000 "sysconfig"
mtd7: 00002000 00010000 "ubootconfig"
mtd8: 00001000 00010000 "ART"
mtd9: 00001000 00010000 "pot"
mtd10: 0000c000 00010000 "ret"
Hi,
today my friends give me new DM200, same problems no way use 21.02.
Now I have other problem, I try use serial understand boot problems, but now no way comunicate with serial, I'm using this:
https://www.amazon.com/DSD-TECH-Adapter-FT232RL-Compatible/dp/B07BBPX8B8/ref=sr_1_1?dchild=1&keywords=sh-u09c&qid=1631280412&sr=8-1
Is it wrong serial? I'm using for tasmota device and works fine.
Hi,
there was my error with serial cable I inverted RX and TX. Now I have the serial log this log when I try upgrade from 19.07.3 to 21.02
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2021.09.10 19:11:43 =~=~=~=~=~=~=~=~=~=~=~=
Watchdog handover: fd=3
- watchdog -
killall: telnetd: no process killed
killall: ash: no process killed
Sending TERM to remaining processes ... uhttpd ntpd dnsmasq luci sh ubus ubusd askfirst urngd logd rpcd netifd odhcpd
Sending KILL to remaining processes ... ntpd
Switching to ramdisk...
Performing system upgrade...
Unlocking firmware ...
Writing from <stdin> to firmware ... [ ][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w][e][w]
Appending jffs2 data from /tmp/sysupgrade.tgz to firmware..
.
Writing from <stdin> to firmware ... [ ][e][w][e][w]
Upgrade completed
Rebooting system...
umount: can't unmount /dev: Resource busy
umount: can't unmount /tmp: Resource busy
[ 414.221684] reboot: Resü
ROM VER: 1.1.4
CFG 05
DDR autotuning Rev 1.0
DDR size from 0xa0000000 - 0xa3ffffff
DDR check ok... start booting...
U-Boot 2010.06-12284-ga4702df (Mar 03 2016 - 13:07:38)
DM200 (hw29765233p8p0p64p0p0) UBoot-v2010.06 dni1 V0.9
CLOCK CPU 500M RAM 250M
DRAM: 64 MiB
In: serial
Out: serial
Err: serial
8192 KiB W25Q64 at 0:3 is now current device
Net: Internal phy(FE) firmware version: 0xc434
vr9 Switch
Type "run flash_nfs" to mount root filesystem over NFS
Hit any key to stop autoboot: 2 1 0
Unknown command 'sleep' - try 'help'
Client starts...[Listening] for ADVERTISE...TTT
Retry count exceeded; boot the image as usual
nmrp server is stopped or failed !
8192 KiB W25Q64 at 0:3 is now current device
## Booting kernel from Legacy Image at 80800000 ...
Image Name: MIPS OpenWrt Linux-5.4.143
Created: 2021-08-31 22:20:08 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 2475578 Bytes = 2.4 MiB
Load Address: 80002000
Entry Point: 80002000
Verifying Checksum ... Bad Data CRC
The Router is in TFTP Server Firmware Recovery mode NOW!
Listening on Port : 69, IP Address: 192.168.0.1 ...
Upgrade Mode Upgrade Mode Upgrade Mode Upgrade Mode Upgrade Mode
Abort
Firmware recovering from TFTP server failed! :(
ERROR: can't get kernel image!
VR9 #
Hi,
This looks like the issue that madhatter posted:
https://lists.openwrt.org/pipermail/openwrt-devel/2019-January/021207.html
To see if this is the problem, get a bootloader console (press a key when it says Hit any key to stop autoboot), then run:
printenv bootcmd
If it shows this:
bootcmd="sleep 1;nmrp;sf probe 0:3;sf read $loadaddr 0x30000 0x200000;bootm $loadaddr"
then that's the problem (specifically the 0x200000).
To make it work with bigger kernels you could try running this before rebooting:
setenv bootcmd "sleep 1;nmrp;sf probe 0:3;sf read $loadaddr 0x30000 0x400000;bootm $loadaddr"
saveenv
I don't have a device immediately at hand to test so i might have got the printenv command wrong. It should be possible to up the read size to 0x7b0000, but that shouldn't be required.
Dear @tomn ,
yes, I can run firmware 21.02 (no very nice need console) my DM200, your solution is perfect and @madhatter discover very fast solution.
Here my serial log:
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2021.09.11 00:06:20 =~=~=~=~=~=~=~=~=~=~=~=
BusyBox v1.33.1 (2021-08-31 22:20:08 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 21.02.0, r16279-5cc0535800
-----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@OpenWrt:/# [ 155.867150] br-lan: port 1(eth0) entered disabled state
[ 155.877281] device eth0 left promiscuous mode
[ 155.880520] br-lan: port 1(eth0) entered disabled state
[ 155.897929] lantiq,xrx200-net 1e108000.eth eth0: port 4 lost link
ROM VER: 1.1.4
CFG 05
DDR autotuning Rev 1.0
DDR size from 0xa0000000 - 0xa3ffffff
DDR check ok... start booting...
U-Boot 2010.06-12284-ga4702df (Mar 03 2016 - 13:07:38)
DM200 (hw29765233p8p0p64p0p0) UBoot-v2010.06 dni1 V0.9
CLOCK CPU 500M RAM 250M
DRAM: 64 MiB
In: serial
Out: serial
Err: serial
8192 KiB W25Q64 at 0:3 is now current device
Net: Internal phy(FE) firmware version: 0xc434
vr9 Switch
Type "run flash_nfs" to mount root filesystem over NFS
Hit any key to stop autoboot: 2 1 0
Unknown command 'sleep' - try 'help'
Client starts...[Listening] for ADVERTISE...TTT
Retry count exceeded; boot the image as usual
nmrp server is stopped or failed !
8192 KiB W25Q64 at 0:3 is now current device
## Booting kernel from Legacy Image at 80800000 ...
Image Name: MIPS OpenWrt Linux-5.4.143
Created: 2021-08-31 22:20:08 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 2475578 Bytes = 2.4 MiB
Load Address: 80002000
Entry Point: 80002000
Verifying Checksum ... Bad Data CRC
The Router is in TFTP Server Firmware Recovery mode NOW!
Listening on Port : 69, IP Address: 192.168.0.1 ...
Upgrade Mode Upgrade Mode Upgrade Mode
Abort
Firmware recovering from TFTP server failed! :(
ERROR: can't get kernel image!
VR9 # nmrp;sf probe 0:3;sf read $loadaddr 0x30000 0x400000;bootm $loadaddr
VR9 # nmrp;sf probe 0:3;sf read $loadaddr 0x30000 0x400000;bootm $loadaddr
Unknown command 'nmrp' - try 'help'
8192 KiB W25Q64 at 0:3 is now current device
## Booting kernel from Legacy Image at 80800000 ...
Image Name: MIPS OpenWrt Linux-5.4.143
Created: 2021-08-31 22:20:08 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 2475578 Bytes = 2.4 MiB
Load Address: 80002000
Entry Point: 80002000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting kernel ...
[ 0.000000] Linux version 5.4.143 (builder@buildhost) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r16279-5cc0535800)) #0 SMP Tue Aug 31 22:20:08 2021
[ 0.000000] SoC: xRX200 rev 1.2
[ 0.000000] printk: bootconsole [early0] enabled
[ 0.000000] CPU0 revision is: 00019556 (MIPS 34Kc)
[ 0.000000] MIPS: machine is Netgear DM200
[ 0.000000] Initrd not found or empty - disabling initrd
[ 0.000000] Detected 1 available secondary CPU(s)
[ 0.000000] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x0000000000000000-0x0000000003ffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x0000000003ffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000003ffffff]
[ 0.000000] percpu: Embedded 14 pages/cpu s26256 r8192 d22896 u57344
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 16240
[ 0.000000] Kernel command line: console=ttyLTQ0,115200
[ 0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes, linear)
[ 0.000000] Writing ErrCtl register=00000400
[ 0.000000] Readback ErrCtl register=00000400
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 55744K/65536K available (6249K kernel code, 220K rwdata, 1040K rodata, 1240K init, 223K bss, 9792K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[ 0.000000] NR_IRQS: 256
[ 0.000000] random: get_random_bytes called from 0x8075aa38 with crng_init=0
[ 0.000000] CPU Clock: 500MHz
[ 0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041786 ns
[ 0.000011] sched_clock: 32 bits at 250MHz, resolution 4ns, wraps every 8589934590ns
[ 0.007906] Calibrating delay loop... 332.54 BogoMIPS (lpj=665088)
[ 0.045951] pid_max: default: 32768 minimum: 301
[ 0.050876] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.058070] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.069553] rcu: Hierarchical SRCU implementation.
[ 0.075159] smp: Bringing up secondary CPUs ...
[ 0.080885] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[ 0.080902] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[ 0.081046] CPU1 revision is: 00019556 (MIPS 34Kc)
[ 0.111803] Synchronize counters for CPU 1: done.
[ 0.136152] smp: Brought up 1 node, 2 CPUs
[ 0.145657] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.155314] futex hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.162354] pinctrl core: initialized pinctrl subsystem
[ 0.169712] NET: Registered protocol family 16
[ 0.181700] dcdc-xrx200 1f106a00.dcdc: Core Voltage : 1016 mV
[ 0.194532] pinctrl-xway 1e100b10.pinmux: Init done
[ 0.201073] dma-xway 1e104100.dma: Init done - hw rev: 7, ports: 7, channels: 28
[ 0.253678] usbcore: registered new interface driver usbfs
[ 0.259257] usbcore: registered new interface driver hub
[ 0.264628] usbcore: registered new device driver usb
[ 0.270372] workqueue: max_active 576 requested for napi_workq is out of range, clamping between 1 and 512
[ 0.282896] clocksource: Switched to clocksource MIPS
[ 0.290216] thermal_sys: Registered thermal governor 'step_wise'
[ 0.291056] NET: Registered protocol family 2
[ 0.301611] IP idents hash table entries: 2048 (order: 2, 16384 bytes, linear)
[ 0.309945] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
[ 0.318300] TCP established hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.325959] TCP bind hash table entries: 1024 (order: 1, 8192 bytes, linear)
[ 0.333057] TCP: Hash tables configured (established 1024 bind 1024)
[ 0.339668] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 0.346154] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 0.353521] NET: Registered protocol family 1
[ 0.357840] PCI: CLS 0 bytes, default 32
[ 0.362191] gptu: totally 6 16-bit timers/counters
[ 0.367025] gptu: misc_register on minor 63
[ 0.371231] gptu: succeeded to request irq 126
[ 0.375696] gptu: succeeded to request irq 127
[ 0.380237] gptu: succeeded to request irq 128
[ 0.384742] gptu: succeeded to request irq 129
[ 0.389256] gptu: succeeded to request irq 130
[ 0.393752] gptu: succeeded to request irq 131
[ 0.398468] No VPEs reserved for AP/SP, not initialize VPE loader
[ 0.398468] Pass maxvpes=<n> argument as kernel argument
[ 0.409858] No TCs reserved for AP/SP, not initializing RTLX.
[ 0.409858] Pass maxtcs=<n> argument as kernel argument
[ 0.423425] workingset: timestamp_bits=14 max_order=14 bucket_order=0
[ 0.449198] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.454959] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.469645] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.476928] random: fast init done
[ 0.485580] gpio-export gpio_export: 2 gpio(s) exported
[ 0.494551] 1e100c00.serial: ttyLTQ0 at MMIO 0x1e100c00 (irq = 112, base_baud = 0) is a lantiq,asc
[ 0.503458] printk: console [ttyLTQ0] enabled
[ 0.503458] printk: console [ttyLTQ0] enabled
[ 0.512190] printk: bootconsole [early0] disabled
[ 0.512190] printk: bootconsole [early0] disabled
[ 0.527282] spi-lantiq-ssc 1e100800.spi: Lantiq SSC SPI controller (Rev 8, TXFS 8, RXFS 8, DMA 1)
[ 0.549438] spi-nor spi0.4: s25fl064k (8192 Kbytes)
[ 0.553034] 8 fixed-partitions partitions found on MTD device spi0.4
[ 0.559247] Creating 8 MTD partitions on "spi0.4":
[ 0.564058] 0x000000000000-0x000000020000 : "uboot"
[ 0.570364] 0x000000020000-0x000000030000 : "gphyfirmware"
[ 0.576769] 0x000000030000-0x0000007e0000 : "firmware"
[ 0.584176] 2 uimage-fw partitions found on MTD device firmware
[ 0.588737] 0x000000030000-0x0000002a0000 : "kernel"
[ 0.595879] 0x0000002a0000-0x0000007e0000 : "rootfs"
[ 0.601683] mtd: device 4 (rootfs) set to be root filesystem
[ 0.606248] 1 squashfs-split partitions found on MTD device rootfs
[ 0.612181] 0x0000005c0000-0x0000007e0000 : "rootfs_data"
[ 0.619736] 0x0000007e0000-0x0000007f0000 : "sysconfig"
[ 0.625802] 0x0000007f0000-0x0000007f2000 : "u-boot-env"
[ 0.632056] 0x0000007f2000-0x0000007f3000 : "ART"
[ 0.637561] 0x0000007f3000-0x0000007f4000 : "pot"
[ 0.643285] 0x0000007f4000-0x000000800000 : "ret"
[ 0.650607] libphy: Fixed MDIO Bus: probed
[ 0.664775] NET: Registered protocol family 10
[ 0.672307] Segment Routing with IPv6
[ 0.674642] NET: Registered protocol family 17
[ 0.679217] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 0.691980] 8021q: 802.1Q VLAN Support v1.8
[ 0.809936] libphy: lantiq,xrx200-mdio: probed
[ 0.814357] net-xrx200: invalid MAC, using random
[ 0.818346] Intel XWAY PHY22F (xRX v1.2 integrated) 0:13: attached PHY driver [Intel XWAY PHY22F (xRX v1.2 integrated)] (mii_bus:phy_addr=0:13, irq=POLL)
[ 0.847464] VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
[ 0.857437] Freeing unused kernel memory: 1240K
[ 0.860584] This architecture does not have kernel memory protection.
[ 0.866997] Run /sbin/init as init process
[ 1.491556] random: crng init done
[ 2.121450] init: Console is alive
[ 2.123887] init: - watchdog -
[ 2.931893] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[ 3.155663] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[ 3.163957] init: - preinit -
[ 4.991189] lantiq,xrx200-net 1e108000.eth eth0: port 4 got link
[ 4.995870] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[ 9.362401] jffs2: notice: (544) jffs2_build_xattr_subsystem: complete building xattr subsystem, 11 of xdatum (0 unchecked, 3 orphan) and 13 of xref (3 dead, 0 orphan) found.
[ 9.385524] mount_root: switching to jffs2 overlay
[ 9.417496] overlayfs: upper fs does not support tmpfile.
[ 9.470439] urandom-seed: Seeding with /etc/urandom.seed
[ 9.743731] lantiq,xrx200-net 1e108000.eth eth0: port 4 lost link
[ 9.766364] procd: - early -
[ 9.768150] procd: - watchdog -
[ 10.447084] procd: - watchdog -
[ 10.459347] procd: - ubus -
[ 10.565463] procd: - init -
Please press Enter to activate this console.
[ 11.924098] kmodloader: loading kernel modules from /etc/modules.d/*
[ 11.932333] IFXOS, Version 1.5.19 (c) Copyright 2009, Lantiq Deutschland GmbH
[ 11.943029] NET: Registered protocol family 8
[ 11.945954] NET: Registered protocol family 20
[ 11.959510] PPP generic driver version 2.4.2
[ 11.998011] Lantiq (VRX) DSL CPE MEI driver, version 1.5.17.6, (c) 2007-2015 Lantiq Beteiligungs-GmbH & Co. KG
[ 12.010469]
[ 12.010469]
[ 12.010469] Lantiq CPE API Driver version: DSL CPE API V4.17.18.6
[ 12.028181]
[ 12.028181] Predefined debug level: 3
[ 12.060265] NET: Registered protocol family 24
[ 12.078791] xt_time: kernel timezone is -0000
[ 12.128600] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 12.282054] urngd: v1.0.2 started.
[ 22.801102] br-lan: port 1(eth0) entered blocking state
[ 22.805055] br-lan: port 1(eth0) entered disabled state
[ 22.810992] device eth0 entered promiscuous mode
[ 25.856517] lantiq,xrx200-net 1e108000.eth eth0: port 4 got link
[ 25.861287] br-lan: port 1(eth0) entered blocking state
[ 25.866410] br-lan: port 1(eth0) entered forwarding state
[ 25.891015] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Great!
I've added these instructions to the wiki. There were already some there, but they were not quite correct.
Hi.
That confirms the image file size limitation issue possibility I have raised.
Hi,
yes all my step:
setenv bootcmd "sleep 1;nmrp;sf probe 0:3;sf read $loadaddr 0x30000 0x400000;bootm $loadaddr"Giovanni
I don't have a DM200. The thread case reminded me a similar issue I had with another device.
Your solving is kinda tricky and requires a lot of steps.