Witam.
Posiadam router Netgear WNR854T.
Na podstawie poradnika http://wiki.openwrt.org/toh/netgear/w...ar/wnr854t Wgrywałem do niego alternatywne oprogramowanie. Wszystko było OK po wgraniu OpenWrt, aż do momentu kiedy chciałem zrobić upgrade, też według tego poradnika. Po upgrade router włącza się, na chwile zapala sie pomarańczowa dioda POWER i po chwili mruga cały czas na zielono. Po podpięciu kabla LAN zapala się kontrolka z numerem LAN w który włożony jest kabel, ale router nie nadaje adresu IP.
Wlutowałem też piny w płytę na port SERIAL i podłączyłem żeńskie gniazdo COM, przez które podłączyłem router do starego laptopa z windowsem XP, ale program putty po włączeniu routera pokazuje jedynie jakieś krzaki. To samo pokazuje kiedy podłącze router do nowszego laptopa przez przejściówkę USB-COM w Windows 7 64Bit.
Może ktoś mi poradzić coś na ten problem.
Dodam, że USB-COM mam na układzie Profilic, a na stronie OpenWRT dedykowany jest CP2102 USB-to-UART, a więc jak narazie zamówiłem coś takiego:http://allegro.pl/usb-uart-ttl-rs232-...?source=ooEdytowany przez areckifx dnia 27-11-2012 02:05
DRAM CS[0] base 0x00000000 size 32MB
DRAM Total size 32MB
[8192kB@ff800000] Flash: 8 MB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done
*** Warning - bad CRC, using default environment
USB 0: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Net: egiga0 [PRIME]
Hit any key to stop autoboot: 0
Marvell>> tftpboot 0x400000 openwrt-wnr854t-uImage
Using egiga0 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.1
Filename 'openwrt-wnr854t-uImage'.
Load address: 0x400000
Loading: #################################################################
#################################################################
############################################
done
Bytes transferred = 889320 (d91e8 hex)
Marvell>> bootm 0x400000
## Booting image at 00400000 ...
Image Name: Linux-2.6.32.10
Created: 2010-04-06 14:58:29 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 889256 Bytes = 868.4 kB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.32.10 (openwrt@wrt1.marcant.net) (gcc version 4.3.3 (GCC) ) #16 Tue Apr 6 16:58:21 CEST 2010
CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Netgear WNR854T
Clearing invalid memory bank 0KB@0xffffffff
Clearing invalid memory bank 0KB@0xffffffff
Clearing invalid memory bank 0KB@0xffffffff
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
Kernel command line: root=/dev/mtdblock1 rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200
PID hash table entries: 128 (order: -3, 512 bytes)
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 32MB = 32MB total
Memory: 29984KB available (2232K code, 137K data, 96K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:64
Calibrating delay loop... 332.59 BogoMIPS (lpj=1662976)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Orion ID: MV88F5181-Rev-B1. TCLK=166666667.
Applying Orion-1/Orion-NAS PCIe config read transaction workaround
PCI: bus0: Fast back to back transfers disabled
pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot
pci 0000:01:00.0: PME# disabled
PCI: bus1: Fast back to back transfers enabled
bio: create slab at 0
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
NET: Registered protocol family 1
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2. (NAND) (SUMMARY) Š 2001-2006 Red Hat, Inc.
msgmni has been set to 58
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A
console [ttyS0] enabled
physmap platform flash device: 00800000 at f4000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
Intel/Sharp Extended Query Table at 0x0031
Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
cmdlinepart partition parsing not available
RedBoot partition parsing not available
Using physmap partition information
Creating 4 MTD partitions on "physmap-flash.0":
0x000000000000-0x000000100000 : "kernel"
0x000000100000-0x000000760000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
mtd: partition "rootfs_data" created automatically, ofs=2A0000, len=4C0000
0x0000002a0000-0x000000760000 : "rootfs_data"
0x000000760000-0x0000007a0000 : "uboot"
0x000000000000-0x000000760000 : "image"
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:00:00:00:51:81
i2c /dev entries driver
TCP westwood registered
NET: Registered protocol family 17
Distributed Switch Architecture driver version 0.1
eth0[0]: detected a Marvell 88E6131 switch
dsa slave smi: probed
802.1Q VLAN Support v1.8 Ben Greear
All bugs added by David S. Miller
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
SQUASHFS error: squashfs_read_data failed to read block 0x18bace
SQUASHFS error: Unable to read metadata cache entry [18bace]
SQUASHFS error: Unable to read inode 0x15f20a3f
------------[ cut here ]------------
WARNING: at fs/inode.c:712 0xc009b524()
Modules linked in:
Backtrace:
Function entered at [] from []
r7:00000000 r6:c009b524 r5:c0223ce0 r4:000002c8
Function entered at [] from []
Function entered at [] from []
r7:c1d08e00 r6:c1d55dc0 r5:c180ae48 r4:c180ae48
Function entered at [] from []
Function entered at [] from []
r5:c180ae48 r4:c180ae48
Function entered at [] from []
r5:c180ae48 r4:fffffffb
Function entered at [] from []
Function entered at [] from []
Function entered at [] from []
r4:c1c0a320
Function entered at [] from []
r8:c025892c r7:c1d56880 r6:00000000 r5:c1d56840 r4:00008000
Function entered at [] from []
r9:c001e808 r8:00000020 r7:c1d56880 r6:c1d56840 r5:00000000
r4:00008000
Function entered at [] from []
Function entered at [] from []
r7:00008000 r6:c1c4a000 r5:c02b609f r4:c1c4a000
Function entered at [] from []
Function entered at [] from []
r5:c001e808 r4:c0260ee4
Function entered at [] from []
r6:00000000 r5:c001d46c r4:c001d46c
Function entered at [] from []
r5:00000000 r4:00000000
---[ end trace 4decd757382df4e0 ]---
VFS: Cannot open root device "mtdblock1" or unknown-block(31,1)
Please append a correct "root=" boot option; here are the available partitions:
1f00 1024 mtdblock0 (driver?)
1f01 6528 mtdblock1 (driver?)
1f02 4864 mtdblock2 (driver?)
1f03 256 mtdblock3 (driver?)
1f04 7552 mtdblock4 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,1)
DRAM CS[0] base 0x00000000 size 32MB
DRAM Total size 32MB
[8192kB@ff800000] Flash: 8 MB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done
*** Warning - bad CRC, using default environment
DRAM CS[0] base 0x00000000 size 32MB
DRAM Total size 32MB
[8192kB@ff800000] Flash: 8 MB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done
*** Warning - bad CRC, using default environment
USB 0: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Net: egiga0 [PRIME]
Hit any key to stop autoboot: 0
### JFFS2 loading 'uImage' to 0x400000
Scanning JFFS2 FS: done.
find_inode failed for name=uImage
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for uImage!
## Booting image at 00400000 ...
Image Name: Linux-2.6.32.10
Created: 2010-04-06 14:58:29 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 889256 Bytes = 868.4 kB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.32.10 (openwrt@wrt1.marcant.net) (gcc version 4.3.3 (GCC) ) #16 Tue Apr 6 16:58:21 CEST 2010
CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Netgear WNR854T
Clearing invalid memory bank 0KB@0xffffffff
Clearing invalid memory bank 0KB@0xffffffff
Clearing invalid memory bank 0KB@0xffffffff
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
Kernel command line: root=/dev/mtdblock1 rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200
PID hash table entries: 128 (order: -3, 512 bytes)
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 32MB = 32MB total
Memory: 29984KB available (2232K code, 137K data, 96K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:64
Calibrating delay loop... 332.59 BogoMIPS (lpj=1662976)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Orion ID: MV88F5181-Rev-B1. TCLK=166666667.
Applying Orion-1/Orion-NAS PCIe config read transaction workaround
PCI: bus0: Fast back to back transfers disabled
pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot
pci 0000:01:00.0: PME# disabled
PCI: bus1: Fast back to back transfers enabled
bio: create slab at 0
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
NET: Registered protocol family 1
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2. (NAND) (SUMMARY) Š 2001-2006 Red Hat, Inc.
msgmni has been set to 58
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A
console [ttyS0] enabled
physmap platform flash device: 00800000 at f4000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
Intel/Sharp Extended Query Table at 0x0031
Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
cmdlinepart partition parsing not available
RedBoot partition parsing not available
Using physmap partition information
Creating 4 MTD partitions on "physmap-flash.0":
0x000000000000-0x000000100000 : "kernel"
0x000000100000-0x000000760000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
mtd: partition "rootfs_data" created automatically, ofs=2A0000, len=4C0000
0x0000002a0000-0x000000760000 : "rootfs_data"
0x000000760000-0x0000007a0000 : "uboot"
0x000000000000-0x000000760000 : "image"
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:00:00:00:51:81
i2c /dev entries driver
TCP westwood registered
NET: Registered protocol family 17
Distributed Switch Architecture driver version 0.1
eth0[0]: detected a Marvell 88E6131 switch
dsa slave smi: probed
802.1Q VLAN Support v1.8 Ben Greear
All bugs added by David S. Miller
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
SQUASHFS error: squashfs_read_data failed to read block 0x18bace
SQUASHFS error: Unable to read metadata cache entry [18bace]
SQUASHFS error: Unable to read inode 0x15f20a3f
------------[ cut here ]------------
WARNING: at fs/inode.c:712 0xc009b524()
Modules linked in:
Backtrace:
Function entered at [] from []
r7:00000000 r6:c009b524 r5:c0223ce0 r4:000002c8
Function entered at [] from []
Function entered at [] from []
r7:c1d08e00 r6:c1d55dc0 r5:c180ae48 r4:c180ae48
Function entered at [] from []
Function entered at [] from []
r5:c180ae48 r4:c180ae48
Function entered at [] from []
r5:c180ae48 r4:fffffffb
Function entered at [] from []
Function entered at [] from []
Function entered at [] from []
r4:c1c0a320
Function entered at [] from []
r8:c025892c r7:c1d56880 r6:00000000 r5:c1d56840 r4:00008000
Function entered at [] from []
r9:c001e808 r8:00000020 r7:c1d56880 r6:c1d56840 r5:00000000
r4:00008000
Function entered at [] from []
Function entered at [] from []
r7:00008000 r6:c1c4a000 r5:c02b609f r4:c1c4a000
Function entered at [] from []
Function entered at [] from []
r5:c001e808 r4:c0260ee4
Function entered at [] from []
r6:00000000 r5:c001d46c r4:c001d46c
Function entered at [] from []
r5:00000000 r4:00000000
---[ end trace 4decd757382df4e0 ]---
VFS: Cannot open root device "mtdblock1" or unknown-block(31,1)
Please append a correct "root=" boot option; here are the available partitions:
1f00 1024 mtdblock0 (driver?)
1f01 6528 mtdblock1 (driver?)
1f02 4864 mtdblock2 (driver?)
1f03 256 mtdblock3 (driver?)
1f04 7552 mtdblock4 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,1)
· Łącznie użytkowników: 24,115 · Najnowszy użytkownik: Ja
Czat
Musisz się zalogować, aby opublikować wiadomość.
Maniek91PL
06-11-2024 22:37
dzięki !
maxikaaz
29-10-2024 14:27
@Maniek91PL - Administration=> Admin Access, i tam masz "Allow Wireless Access" do zaznaczenia
Maniek91PL
26-10-2024 22:07
siemka! ktoś przypomni co się ustawiało jeśli nie mogę wejść od strony wifi do tomato? od lan działa
overflow2
04-10-2024 17:34
Kupowałem Asusy n10u albo n12d1 ale nie widzę ich, chyba już nie produkują, Chodzi o coś nowego i taniego. Transfery niewielkie.
maxikaaz
04-10-2024 09:38
@overflow2 patrząc po dostępności funkcji w nowych kompilacjach, to chyba nawet WRT54G/GL jeszcze ma OpenVPN, albo jakiś odpowiednik... zależy, na jakie transfery liczysz.
overflow2
30-09-2024 20:53
Jaki aktualnie najtańszy router do tomato do openvpn?
maxikaaz
27-07-2024 15:07
@servee - na początek router do rozebrania i obejrzenia, ciężko wróżyć tak tylko po objawach
maxikaaz
27-07-2024 14:55
@servee - cały kontroler nie pada tak sobie z powodu "zbiegu okoliczności", więc prawdopodobnie gdzieś przepięcie.
servee
25-07-2024 13:33
@maxikaaz: działało, aż pewnego pięknego dnia przestało działać. W tym dniu była też burza, ale to raczej zbieg okoliczności.
maxikaaz
25-07-2024 11:38
@servee - o ile problem jest w obrębie samych wyjść (dławiki, warystory), to naprawialne, ale jeśli w samym SoC - to nienaprawialne ze względu na koszta. A co było przyczyną?
' target='_blank'>Link
