DSM-G600, DNS-3xx and NSA-220 Hack Forum

Unfortunately no one can be told what fun_plug is - you have to see it for yourself.

You are not logged in.

Announcement

#1 2008-06-07 23:55:26

aread22
Member
Registered: 2008-04-29
Posts: 9

Help diagnosing DNS323

Hello everyone,

A month back my dns323 went on the fritz when I uploaded a config file that had been edited on windows causing it to have the CR\LF error. Now everytime I boot up the dns323, the web interface never comes up and the power light keeps blinking on and off. After about a month of getting all the parts, I have finally been able to put together a serial cable and get into the dns323. Upon booting up the dns323 the following output occurs from the serial console in putty for windows (sorry about the length):

Code:

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2008.06.07 16:51:16 =~=~=~=~=~=~=~=~=~=~=~=
 ** LOADER **
 ** MARVELL BOARD: RD-88F5181-POS-NAS LE 

U-Boot 1.1.1 (Nov 13 2006 - 14:01:34) Marvell version: 1.4.2

DRAM CS[0] base 0x00000000   size  64MB 
DRAM Total size  64MB 
[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


Soc: MV88F5181 Rev 3
CPU: ARM926 (Rev 0) running @ 500Mhz 
SysClock = 166Mhz , TClock = 166Mhz 


 Init usb device.
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Hit any key to stop autoboot:  3  0 
## Booting image at ff820000 ...
   Image Name:   Linux-2.6.12.6-arm1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1426600 Bytes =  1.4 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at ff9a0000 ...
   Image Name:   Ramdisk
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6210253 Bytes =  5.9 MB
   Load Address: 00800000
   Entry Point:  00800000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux............................................................................................... done, booting the kernel.

Linux version 2.6.12.6-arm1 (jack@SWTEST2) (gcc version 3.3.3) #29 Thu Dec 27 09:59:48 CST 2007

CPU: ARM926EJ-Sid(wb) [41069260] revision 0 (ARMv5TEJ)

CPU0: D VIVT write-back cache

CPU0: I cache: 32768 bytes, associativity 1, 32 byte lines, 1024 sets

CPU0: D cache: 32768 bytes, associativity 1, 32 byte lines, 1024 sets

Machine: MV-88fxx81

Using UBoot passing parameters structure

Sys Clk = 166000000, Tclk = 166000000



- Warning - This LSP release was tested only with U-Boot release 1.7.3 


Memory policy: ECC disabled, Data cache writeback

Built 1 zonelists

Kernel command line: root=/dev/ram console=ttyS0,115200 :::DB88FXX81:egiga0:none

PID hash table entries: 512 (order: 9, 8192 bytes)

Console: colour dummy device 80x30

Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)

Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)

Memory: 64MB 0MB 0MB 0MB = 64MB total

Memory: 55680KB available (2466K code, 454K data, 112K init)

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

checking if image is initramfs...it isn't (no cpio magic); looks like an initrd

Freeing initrd memory: 6064K

NET: Registered protocol family 16


  Marvell Development Board (LSP Version 1.7.6_NAS)-- RD-88F5181-88SX7042-2xSATA 


 Detected Tclk 166000000 and SysClk 166000000 

Marvell USB EHCI Host controller #0: c03a7bc0

pexBarOverlapDetect: winNum 2 overlap current 0

mvPexInit:Warning :Bar 2 size is illigal

it will be disabled

please check Pex and CPU windows configuration

PCI: bus0: Fast back to back transfers disabled

PCI: bus1: Fast back to back transfers enabled

SCSI subsystem initialized

usbcore: registered new driver usbfs

usbcore: registered new driver hub

cesadev_init(c0012498)

Fast Floating Point Emulator V0.9 (c) Peter Teichmann.

VFS: Disk quotas dquot_6.5.1

Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

Initializing Cryptographic API

Serial: 8250/16550 driver $Revision: 1.1.1.1 $ 4 ports, IRQ sharing disabled

ttyS0 at MMIO 0x0 (irq = 3) is a 16550A

io scheduler noop registered

io scheduler deadline registered

RAMDISK driver initialized: 16 RAM disks of 10240K size 1024 blocksize

loop: loaded (max 8 devices)

Marvell Gigabit Ethernet Driver 'egiga':

  o Ethernet descriptors in DRAM

  o DRAM SW cache-coherency

  o Checksum offload enabled

  o Loading network interface 'egiga0' 

scsi0 : Marvell SCSI to SATA adapter

scsi1 : Marvell SCSI to SATA adapter

scsi2 : Marvell SCSI to SATA adapter

scsi3 : Marvell SCSI to SATA adapter

  Vendor: WDC       Model: WD800JD-00LSA0    Rev: 06.0

  Type:   Direct-Access                      ANSI SCSI revision: 03

Attached scsi generic sg0 at scsi1, channel 0, id 0, lun 0,  type 0

physmap flash device: 800000 at ff800000

phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank

 Amd/Fujitsu Extended Query Table at 0x0040

number of CFI chips: 1

cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.

cmdlinepart partition parsing not available

RedBoot partition parsing not available

Using physmap partition definition

Creating 5 MTD partitions on "phys_mapped_flash":

0x00000000-0x00010000 : "MTD1"

0x00010000-0x00020000 : "MTD2"

0x00020000-0x001a0000 : "Linux Kernel"

0x001a0000-0x007d0000 : "File System"

0x007d0000-0x00800000 : "u-boot"

ehci_platform ehci_platform.20865: EHCI Host Controller

ehci_platform ehci_platform.20865: new USB bus registered, assigned bus number 1

ehci_platform ehci_platform.20865: irq 17, io mem 0x00000000

ehci_platform ehci_platform.20865: park 0

ehci_platform ehci_platform.20865: USB 0.0 initialized, EHCI 1.00, driver 10 Dec 2004

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

usbcore: registered new driver usblp

drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver

mice: PS/2 mouse device common for all mice

md: linear personality registered as nr 1

md: raid0 personality registered as nr 2

md: raid1 personality registered as nr 3

md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27

device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com

NET: Registered protocol family 2

IP: routing cache hash table of 512 buckets, 4Kbytes

TCP established hash table entries: 4096 (order: 3, 32768 bytes)

TCP bind hash table entries: 4096 (order: 2, 16384 bytes)

TCP: Hash tables configured (established 4096 bind 4096)

NET: Registered protocol family 1

NET: Registered protocol family 17

md: Autodetecting RAID arrays.

md: autorun ...

md: ... autorun DONE.

RAMDISK: Compressed image found at block 0

EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended

VFS: Mounted root (ext2 filesystem).

Freeing init memory: 112K


init started:  BusyBox v1.00-pre1 (2007.12.10-08:03+0000) multi-call binary

init started:  BusyBox v1.00-pre1 (2007.12.10-08:03+0000) multi-call binary

Starting pid 221, console /dev/ttyS0: '/etc/rc.sh'

init started:  BusyBox v1.00-pre1 (2007.12.10-08:03+0000) multi-call binary


init started:  BusyBox v1.00-pre1 (2007.12.10-08:03+0000) multi-call binary


Starting pid 221, console /dev/ttyS0: '/etc/rc.sh'


init started:  BusyBox v1.00-pre1 (2007.12.10-08:03+0000) multi-call binary

ini** Mounting /etc/fstab
t started:  BusyBox v1.00-pre1 (2007.12.10-08:03+0000) multi-call binary


Starting pid 221, console /dev/ttyS0: '/etc/rc.sh'


init started:  BusyBox v1.00-pre1 (2007.12.10-08:03+0000) multi-call binary


ini** Mouumount: proc: not mounted
umount: proc: not mounted
nting /etc/fstab

t started:  BusyBox v1.00-pre1 (2007.12.10-08:03+0000) multi-call binary

Starting pumount: /image.cfs: not mounted
umount: /image.cfs: not mounted
id 221, console /dev/ttyS0: '/etc/rc.sh'


init started:  BusyBox v1.00-pre1 (2007.12.10-08:03+0000) multi-call binary


ini** Mouumount: proc: not mounted

umount: proc: not mounted

nting /etc/fstab

t started:  BusyBox v1.00-pre1 (2007.12.10-08:03+0000) multi-call binary

Starting pumount: /image.cfs: not mounted

umount: /image.cfs: not mounted

id 221, console /dev/ttyS0: '/etc/rc.sh'

init started:  BusyBox v1.00-pre1 (2007.12.10-08:03+0000) multi-call binary

ini** Mouumount: proc: not mounted

umount: proc: not mounted


nting /etc/fstab

t started:  BusyBox v1.00-pre1 (2007.12.10-08:03+0000) multi-call binary

Starting pumount: /image.cfs: not mounted

umount: /image.cfs: not mounted


id 221, console /dev/ttyS0: '/etc/rc.sh'

init started:  BusyBox v1.00-pre1 (2007.12.10-08:03+0000) multi-call binary

ini** Mouumount: proc: not mounted

umount: proc: not mounted

nting /etc/fstab

t started:  BusyBox v1.00-pre1 (2007.12.10-08:03+0000) multi-call binary

Starting pumount: /image.cfs: not mounted

umount: /image.cfs: not mounted

id 221, console /dev/ttyS0: '/etc/rc.sh'

init started:  BusyBox v1.00-pre1 (2007.12.10-08:03+0000) multi-call binary

ini** Mouumount: proc: not mounted

umount: proc: not mounted

nting /etc/fstab

t started:  BusyBox v1.00-pre1 (2007.12SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)

SCSI device sda: drive cache: write back

SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)

SCSI device sda: drive cache: write back

 sda: sda1

Attached scsi disk sda at scsi1, channel 0, id 0, lun 0

** Activate Gigabit Interface
** execute rc.init.sh
/etc/rc.sh: /etc/rc.d/rc.init.sh: No such file or directory
mbr: No such file or directory
DEVICE_A = HD_a2
DEVICE_B = HD_b2
old_channel = 1
disk = 0
Serial Number =
Serial Number =
RAID0 mode
lost hd
Set Timezone=-5
1.Set Date & time ...(command: sntp -r ntp1.dlink.com &)
get IP = [NONE SET]
sntp: unable to locate IP address/number
sntp: Network is unreachable
<rtc>: getRTC time= 5/1/7 22:38:42
check button V2.26.12272007
Jan  7 22:38:42 crond[543]: crond 2.3.2 dillon, started, log level 8

1.04(1.36.0110.2008)
01/10/2008
SIOCADDRT: No such device
mfg_search
create /tmp/fatmount script file
mount FAT storage devices
Starting pid 554, console /dev/ttyS0: '/bin/sh'


BusyBox v1.00-pre1 (2007.12.10-08:03+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

Now when I try to break into shell using 5784468 and pressing "enter" nothing happens. I am on firmware 1.04 by the way. Anybody know what I can do to try and fix my dns323?


For further information about what I did to screw up the dns32 you can see these 2 post (http://dns323.kood.org/forum/t2121-Blin … ns%3F.html) and (http://dns323.kood.org/forum/t2124-anyb … le%3F.html)

Thank You

Last edited by aread22 (2008-06-08 01:00:13)

Offline

 

#2 2008-06-08 01:24:23

jdoering
Member
Registered: 2008-04-10
Posts: 95

Re: Help diagnosing DNS323

Can you break into the U-Boot loader during the initial 3 second window (see the U-Boot wiki entry for details)?

I ask because the first question is whether your serial setup is writing successfully to the DNS-323 at all... if you can't break into U-Boot or the shell; I'd double check the serial write wire, etc.

If you can break into U-Boot; then I don't know as the breaking into the shell has always "just worked" for me.

BTW your U-Boot Marvell version looks old for 1.04; I thought it should be 1.7.3?

-Jeff

Offline

 

#3 2008-06-08 02:14:50

aread22
Member
Registered: 2008-04-29
Posts: 9

Re: Help diagnosing DNS323

Thanks for responding jdoering,

Well I can't see any input when I type anything so I am not sure how to see if I can break into u-boot, I tried hitting space and 1 but nothing happens

Is not seeing anything when you type in the console normal?

Also here is my wiring:

I am using the cable that you recommend from Dionysus Design (http://www.dionysusdesign.com/product_i … ucts_id/72)

DNS323        DD CABLE
3.3V       -     Nothing (I don't have this connected to the 5v line of the cable)
TX          -     TX
RX          -     RX
Ground   -     Ground

Last edited by aread22 (2008-06-08 02:24:29)

Offline

 

#4 2008-06-08 04:44:11

aread22
Member
Registered: 2008-04-29
Posts: 9

Re: Help diagnosing DNS323

I fixed it, it was my wiring. FINALLY MY DNS323 works again!!!!

Thanks for all your help jdoering and everyone else.

Offline

 

#5 2009-08-16 22:32:17

bjby
Member
Registered: 2009-02-22
Posts: 265

Re: Help diagnosing DNS323

Wow

Offline

 

Board footer

Powered by PunBB
© Copyright 2002–2010 PunBB