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.

#1 2010-02-28 01:23:18

f4exb
Member
Registered: 2010-02-14
Posts: 18

A few good reasons not to buy a new DNS-323 (H/W rev. C1)

Hello,

I am with hardware revision C1 and this poor thing seems really crippled.

Preliminary: what is at the origin of my quest for a decent firmware... original firmware support for NFS and SMBFS is minimal to say the least.

1. You can't use Fonz custom kernel (see my previous post)
2. You can't install Debian following Martin Michlmayr's method (does not support C1)
3. D-Link does not release the source (at least on their website)
4. Last but not least: its uBoot cannot load kernel nor initrd. When trying a loadb k or loadb r with kermit transfer I get the following...
For kernel area:

Code:

Un-Protect Flash Bank # 1
Erase Kernel from 0xff820000 to 0xff99ffff Can't erase unknown flash type - aborted

Same thing with initrd area:

Code:

Un-Protect Flash Bank # 1
Erase Ramdisk from 0xff9a0000 to 0xfff7ffff Can't erase unknown flash type - aborted

Now you've been warned...

Best regards.

Last edited by f4exb (2010-02-28 01:24:54)

Offline

 

#2 2010-03-08 21:59:33

bernd123
Member
Registered: 2010-03-07
Posts: 12

Re: A few good reasons not to buy a new DNS-323 (H/W rev. C1)

Hi,

U-Boot can load a kernel and an initrd, however it seems to refuse flashing them. But you can flash from within linux.

Code:

loadb

Now send a kernel with kermit. It will be at 100000

Copy kernel to another location in memory:

Code:

cp 0100000 02000000 <sizeofkernel>

Load an initrd:

Code:

loadb

Send an initrd with kermit.

Copy initrd to another location in memory:

Code:

cp 0100000 03000000 <sizeofinitrd>

Load and boot kernel and initrd:

Code:

bootm 02000000 03000000

Notice: loading the kernel from 0100000 does work while loading the initrd from 0100000 doesn't work, keep that in mind.

For custom kernel, the GPIO/LED-stuff seems to be broken, compile without CONFIG_LEDS_GPIO.

Offline

 

#3 2010-03-29 19:17:47

jcard
Member
From: Portugal
Registered: 2008-09-21
Posts: 289

Re: A few good reasons not to buy a new DNS-323 (H/W rev. C1)

f4exb:

Have you tried Alt-F, recently announced in this forum? Its 2.6.33.1 based.

I have a report that the network does not work with it on a rev-C1 board, but the user does not have a serial link to debug it.
On the other side, the user report that buttons and leds work fine.


Please consider discussing Alt-F at http://groups.google.com/group/alt-f/topics
Please consider filling Alt-F bugs at http://code.google.com/p/alt-f/issues/list

Offline

 

#4 2010-11-16 07:35:38

f4exb
Member
Registered: 2010-02-14
Posts: 18

Re: A few good reasons not to buy a new DNS-323 (H/W rev. C1)

Yes Alt-F does work with revision C1 and has kernel NFS support.
Thanks for all the good work!
Now I have to find a replacement for the door stop :-)

Best regards.

Offline

 

#5 2010-11-17 10:54:29

haim
Member
Registered: 2010-01-13
Posts: 83

Re: A few good reasons not to buy a new DNS-323 (H/W rev. C1)

It might be worth posting this on the main forum.  I could imagine there might be a few C board owners who wanted to install debian for a newer kernel.

Offline

 

#6 2014-10-01 20:07:58

l0rd_hex
New member
From: Edmonton, Alberta, Canada
Registered: 2012-04-28
Posts: 4

Re: A few good reasons not to buy a new DNS-323 (H/W rev. C1)

4 years later... but thank you bernd123 I used your method to unbrick my B1!

Offline

 

#7 2014-11-24 17:44:28

abingarten
New member
Registered: 2014-11-24
Posts: 1

Re: A few good reasons not to buy a new DNS-323 (H/W rev. C1)

Hi Guys,

I'm new to this topic but have some experience with embedded linux systems. I also managed to install debian on my DNS 323 but got a weird issue now: ETH0 is gone and isn't detected by UDEV anymore.
I've no idea what is/was going on.

Here is a snipped from the log:
It seems like some directories are missing?!

Many thanks for your help!


udevd[174]: device 0x1ca93c0 has devpath '/devices/platform/leds-gpio'

udevd[174]: no db file to read /run/udev/data/+platform:leds-gpio: No such file or directory

udevd[174]: passed -1 bytes to netlink monitor 0x1ca9a98

udevd[174]: seq 423 processed with 0

udevd[171]: seq 427 running

udevd[171]: device 0x1c98320 has devpath '/devices/platform/mv643xx_eth.0'

udevd[171]: no db file to read /run/udev/data/+platform:mv643xx_eth.0: No such file or directory

udevd[171]: RUN '/sbin/modprobe -b $env{MODALIAS}' /lib/udev/rules.d/80-drivers.rules:7

udevd[182]: starting '/sbin/modprobe -b platform:dns323c-fan'

udevd[141]: passed 187 bytes to netlink monitor 0x1c98320

udevd[141]: seq 423 done with 0

udevd[141]: seq 428 queued, 'add' 'platform'

udevd[174]: seq 424 running

udevd[174]: device 0x1c984b0 has devpath '/devices/platform/leds-gpio/leds/left:amber'

udevd[174]: no db file to read /run/udev/data/+leds:left:amber: No such file or directory

udevd[174]: passed -1 bytes to netlink monitor 0x1ca9a98

udevd[174]: seq 424 processed with 0

udevd[185]: starting '/sbin/modprobe -b platform:gpio-keys'

udevd[184]: starting '/sbin/modprobe -b platform:mv643xx_eth'
udevd[141]: passed 165 bytes to netlink monitor 0x1c98320

udevd[141]: seq 425 forked new worker [187]


udevd[187]: seq 425 running

udevd[187]: device 0x1c98648 has devpath '/devices/platform/leds-gpio/leds/power:blue'

udevd[187]: no db file to read /run/udev/data/+leds:power:blue: No such file or directory

udevd[187]: passed -1 bytes to netlink monitor 0x1caadb0

udevd[187]: seq 425 processed with 0

udevd[141]: seq 426 forked new worker [188]

udevd[141]: seq 428 forked new worker [189]

udevd[141]: seq 424 done with 0

udevd[141]: seq 425 done with 0

udevd[141]: seq 429 queued, 'add' 'platform'

udevd[174]: seq 429 running

udevd[174]: device 0x1c98448 has devpath '/devices/platform/mv64xxx_i2c.0'

udevd[174]: no db file to read /run/udev/data/+platform:mv64xxx_i2c.0: No such file or directory

udevd[174]: passed -1 bytes to netlink monitor 0x1ca9a98

udevd[174]: seq 429 processed with 0

udevd[188]: seq 426 running

udevd[188]: device 0x1c98320 has devpath '/devices/platform/leds-gpio/leds/right:amber'

udevd[188]: no db file to read /run/udev/data/+leds:right:amber: No such file or directory

udevd[188]: passed -1 bytes to netlink monitor 0x1caaec0

udevd[188]: seq 426 processed with 0

udevd[189]: seq 428 running

udevd[189]: device 0x1ca93c0 has devpath '/devices/platform/mv643xx_eth_port.0'

udevd[189]: no db file to read /run/udev/data/+platform:mv643xx_eth_port.0: No such file or directory

udevd[189]: RUN '/sbin/modprobe -b $env{MODALIAS}' /lib/udev/rules.d/80-drivers.rules:7

udevd[173]: '/sbin/modprobe -b platform:gpio-keys'(err) 'FATAL: Module platform:gpio-keys not found.'

udevd[172]: '/sbin/modprobe -b platform:dns323c-fan'(err) 'FATAL: Module platform:dns323c-fan not found.'

udevd[171]: '/sbin/modprobe -b platform:mv643xx_eth'(err) 'FATAL: Module platform:mv643xx_eth not found.'

udevd[141]: passed 206 bytes to netlink monitor 0x1c98320

udevd[141]: seq 429 done with 0

udevd[141]: seq 426 done with 0

udevd[141]: seq 430 queued, 'add' 'i2c'

udevd[172]: '/sbin/modprobe -b platform:dns323c-fan' [182] exit with return code 1

udevd[172]: passed -1 bytes to netlink monitor 0x1c9a070

udevd[172]: seq 421 processed with 0

udevd[190]: starting '/sbin/modprobe -b platform:mv643xx_eth_port'

[ ok udevd[173]: '/sbin/modprobe -b platform:gpio-keys' [185] exit with return code 1

udevd[173]: passed -1 bytes to netlink monitor 0x1ca9480

udevd[173]: seq 422 processed with 0

udevd[174]: seq 430 running

udevd[174]: device 0x1c98320 has devpath '/devices/platform/mv64xxx_i2c.0/i2c-0'

udevd[174]: no db file to read /run/udev/data/+i2c:i2c-0: No such file or directory

udevd[174]: passed -1 bytes to netlink monitor 0x1ca9a98

udevd[174]: seq 430 processed with 0

udevd[141]: passed 158 bytes to netlink monitor 0x1c98320

udevd[141]: seq 421 done with 0

udevd[141]: seq 422 done with 0

udevd[141]: seq 430 done with 0

udevd[141]: seq 431 queued, 'add' 'i2c'

udevd[172]: seq 431 running

udevd[172]: device 0x1c99b20 has devpath '/devices/platform/mv64xxx_i2c.0/i2c-0/0-0048'

udevd[172]: no db file to read /run/udev/data/+i2c:0-0048: No such file or directory

udevd[172]: RUN '/sbin/modprobe -b $env{MODALIAS}' /lib/udev/rules.d/80-drivers.rules:7

udevd[171]: '/sbin/modprobe -b platform:mv643xx_eth' [184] exit with return code 1

udevd[171]: passed -1 bytes to netlink monitor 0x1c99a90

udevd[171]: seq 427 processed with 0

udevd[193]: starting '/sbin/modprobe -b i2c:lm75'

udevd[141]: passed 183 bytes to netlink monitor 0x1c98320

udevd[141]: seq 427 done with 0

udevd[141]: seq 432 queued, 'add' 'i2c'

udevd[171]: seq 432 running

udevd[171]: device 0x1c98320 has devpath '/devices/platform/mv64xxx_i2c.0/i2c-0/0-0068'

udevd[171]: no db file to read /run/udev/data/+i2c:0-0068: No such file or directory

udevd[171]: passed -1 bytes to netlink monitor 0x1c99a90

udevd[171]: seq 432 processed with 0

udevd[141]: passed 203 bytes to netlink monitor 0x1c98320

udevd[141]: seq 432 done with 0

udevd[141]: seq 433 queued, 'add' 'rtc'

udevd[171]: seq 433 running

udevd[171]: device 0x1c98320 has devpath '/devices/platform/mv64xxx_i2c.0/i2c-0/0-0068/rtc/rtc0'

udevd[171]: no db file to read /run/udev/data/c254:0: No such file or directory

udevd[171]: device 0x1c99f88 has devpath '/devices/platform/mv64xxx_i2c.0/i2c-0/0-0068'

udevd[171]: device 0x1c9a238 has devpath '/devices/platform/mv64xxx_i2c.0/i2c-0'

udevd[141]: passed 205 bytes to netlink monitor 0x1c98320

udevd[141]: seq 434 queued, 'add' 'i2c-dev'

udevd[173]: seq 434 running

Offline

 

#8 2015-05-02 22:01:29

sargem
New member
Registered: 2015-05-02
Posts: 1

Re: A few good reasons not to buy a new DNS-323 (H/W rev. C1)

use cp.b instead of cp
write<sizeofkernel> in bytes

Offline

 

Board footer

Powered by PunBB
© Copyright 2002–2010 PunBB