Debian on iomega storcenter ix4-200d: succes!

Hi bodhi,

How can I do this when I have a wholeflash backup file. I suppose I would have to boot the board with kwboot and this wholeflash image, and then flash it into nand flash. Is this correct?

Gastal

Gastal,

> How can I do this when I have a wholeflash backup
> file. I suppose I would have to boot the board wit
> h kwboot and this wholeflash image, and then flash
> it into nand flash. Is this correct?

Yes.

- Format a USB flash drive as ext2 or ext3. Put the mtd NAND dump files on the root folder.
- Boot with kwboot using the stock mtd0.
- Load mtd0 file to memory.
- And do nand flash erase and nand write.

After this you can boot normally with u-boot. And the next step depending on whether you want to boot Debian first or restore stock first.

1 .To boot Debian first,
- create Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 rootfs on USB: http://forum.doozan.com/read.php?2,12096.
- follow damacc posts to adjust u-boot envs in serial console to boot into Debian.
- and then flash the rest of the stock mtds in Debian.

2. To boot stock first,
- Do flash erase and nand write for each mtds in serial console.

I would recommend doing number 1 (booting Debian first).

And see here for flashing instruction for Pogo V4 mtd0 (section B):
http://forum.doozan.com/read.php?3,16789,16789#msg-16789

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 05/11/2017 12:39AM by bodhi.

Hi, I have a ix4-200d here collecting dust, I want to give a new chance... currently it has 4 hd 500gb each with stock firmware.

I want to throw away those disk and install and boot debian on a usb-stick, probably put other disk and maybe a zfs or ntfs there...

I have successfully written kernel, initramfs, and rootf on some HD for some Iomega Ez Media & Backup Center that I have around using some help from here too, my instructions are here: https://gist.github.com/braian87b/b5a4c5f20d1112473c470b096df766a3 those Iomega Ez have NTFS and ext4 and works extremely well so far.

Now I want to play with the ix4-200d, since I have very basic understanding, can someone point me to some url's with info and needed files on how to do it and explain briefly the steps to be able to do it?

I have some computers and vm's with debian and usb's sticks and usb-ttl also to start with this.

Thanks.

Hi, Bodhi provides instructions and a root filesystem to boot from usb here;
Kernel and rootfs

Scroll down to the rootfs instructions at: Updated 24 Jul 2017:

Basic Debian stretch Kirkwood rootfs for most Kirwood plugs

You will need to follow the 'append dtb to uImage' instructions, then change the u-boot parameters via a serial console to boot from usb.

First of all, thanks for all of the research done for giving new life to the ix4 box. I've one of these laying around myself and knowing it's possible to run debian on it would be a nice opportunity to set it up as a backup server with better disk management. But now having read all of the related posts here and tried out many described ways, I still couldn't manage to boot into debian.

I might have not understood everything what's going on and how it works, but here's what I've done so far:

- Setting up an USB stick with Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 rootfs (as described in https://forum.doozan.com/read.php?2,12096)
-> Plugged into ix4 and turned on, but boots into normal firmware
- Tried aswell Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 with same result (but shouldn't work anyways with stock uboot iirc)
- Attached serial interface, interrupted boot and set some env variables (as in https://forum.doozan.com/read.php?3,25120,25675#msg-25675) and tried "boot", but seems like it can't correctly init the usb stick and reboots:

Marvell>> boot
Unknown command 'usb' - try 'help'

** Block device usb 0 not supported

** Block device usb 0 not supported
## Booting image at 00800000 ...
Bad Magic Number

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|  ** uboot_ver:v1.0.0 **

 ** MARVELL BOARD: IX4-110 LE

U-Boot 1.1.4 (Jul 23 2009 - 14:25:44) Marvell version: 3.4.4

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006904EC

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

- I've set the vars again and performed saveenv (probably not the smartest thing to do; now it tries to boot from usb by default, and fails)
- Tried to do a kwboot with different images such as uboot.2015.10-tld-1.sheevaplug.bodhi.tar, ix4-200d-mtd0.kwb and a mtd0 that was attached to some forum posts. Tried with command

kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2015.10-tld-1.sheevaplug.mtd0.kwb -p

but it stucks at

Sending boot message. Please reboot the target...\

no matter how often I reboot or interrupt with ctrl-c and re-do kwboot as described in an other topic
(https://forum.doozan.com/read.php?3,7852,7852)

I've often just seen the reference to the rootfs-post, but never actually an explaination on what to do after having the usb stick ready. Booting with serial and interrupt? The only thing I've found from that point were some posts where a custom uboot seemed already to be applied - which I couldn't load with kwboot.

I might also be totally wrong and doing pointless stuff, since I don't understand everything. But even after reading all of the posts multiple times, I couldn't figure out the clear steps to be able to boot into debian. Am I doing something wrong? Any help would be appreciated; I can also provide outputs or any other info if needed.

Radm,

Quote

I've often just seen the reference to the rootfs-post, but never actually an explaination on what to do after having the usb stick ready. Booting with serial and interrupt? The only thing I've found from that point were some posts where a custom uboot seemed already to be applied - which I couldn't load with kwboot.

- Plug in the USB rootfs with Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 on it.
- Power up, interrupt serial console and

setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'
setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd'
setenv usb_boot 'mw 0x800000 0 1; run load_uimage; if run load_uinitrd; then bootm 0x800000 0x2100000; else bootm 0x800000; fi'
setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
setenv bootcmd 'usb start; run usb_bootcmd; usb stop; reset'

And then,

printenv
boot

==========

The above instruction is in the Wiki thread:

Quote

Boot Kirkwood rootfs with stock u-boot:
https://forum.doozan.com/read.php?2,102054,105374#msg-105374

You've raised a good point, I need to update the rootfs instruction to point to that post to recommend a basic approach when users are booting from stock Kirkwood u-boot.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks for the fast response! Only thing not working so far is when setting the usb_boot env; it's not possible to save it:

Marvell>> setenv usb_boot 'mw 0x800000 0 1; run load_uimage; if run load_uinitrd; then bootm 0x800000 0x2100000; else bootm 0x800000; fi'
** Too many args (max. 16) **

Any workaround?

Edit: Oh nvm I should have rtfm. Will try again as described in the linked post :)



Edited 3 time(s). Last edit at 01/29/2021 06:16AM by Radm.

So setenv worked now, but I'm still experiencing the "Unknown command 'usb' - try 'help'" message after trying to boot. Might there be missing something, could it be usb not being created correctly or do you by occasion see anything wrong in the log? Does the partition table type matter on the usb stick (msdos for me)?

Here's the serial output from the beginning of startup to when it bootloops (when it's not being interrupted):

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__|  ** uboot_ver:v1.0.0 **

 ** MARVELL BOARD: IX4-110 LE 

U-Boot 1.1.4 (Jul 23 2009 - 14:25:44) Marvell version: 3.4.4

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006904EC

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB 
DRAM CS[1] base 0x10000000   size 256MB 
DRAM Total size 512MB  16bit width
Found 0x20 i2c device
Set Power State as Always On
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:32 MB
Found ADT7473, program LED ...(led_volt=90)  OK
Found ADT7473, program thermal/Fan ...(pwm_min=0) (pwm_max=130) (therm=67) (temp_min=60)  OK

Marvell Serial ATA Adapter
Integrated Sata device found


CPU : Marvell Feroceon (Rev 1)
Found initrd at 0x2d4000

Streaming disabled 
Write allocate disabled

Module 0 is RGMII
Module 1 is RGMII

USB 0: host mode
PCI 0: PCI Express Root Complex Interface
PEX interface detected Link X1
SCSI:  AHCI 0001.0000 32 slots 3 ports 3 Gbps 0x7 impl IDE mode
flags: 64bit ncq stag led pmp slum part 
scanning bus for devices...
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  1  0

Marvell>> setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'
Marvell>> setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
Marvell>> setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd'
Marvell>> setenv usb_boot 'mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x2100000'
Marvell>> setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
Marvell>> setenv bootcmd 'usb start; run usb_bootcmd; usb stop; reset'
Marvell>> printenv


bootdelay=1
baudrate=115200
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
console=console=ttyS0,115200 mtdparts=nand_mtd:0xa0000@0x0(uboot),0x00010000@0x000a0000(param),32m@0x0(flash) 
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end); bootm 0x2000000;
mvNetConfig=mv_net_config=(00:11:88:01:32:97,0:1:2:3),mtu=1500
usb0Mode=host
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
uboot_ver=v1.0.0
ethact=egiga0
uboot_start=0x0
uboot_size=0xa0000
env_start=0xa0000
env_size=0x10000
kernel_start=0xb0000
kernel_size=0x224000
initrd_size=0x224000
flash_load=run make_boot_args;nand read.e 0x2000000 $(kernel_start) $(kernel_size);nand read.e 0x12000000 $(initrd_start) $(initrd_size);bootm 0x2000000 0x12000000
make_boot_args=setenv bootargs console=ttyS0,115200 mtdparts=nand_mtd:;setenv bootargs $(bootargs)$(uboot_size)@$(uboot_start)(uboot),;setenv bootargs $(bootargs)$(env_size)@$(env_start)(env),;setenv bootargs $(bootargs)$(kernel_size)@$(kernel_start)(zImage),;setenv bootargs $(bootargs)$(initrd_size)@$(initrd_start)(initrd),;setenv bootargs $(bootargs)32m@0x0(flash);
mfgmodel=ix4
fw_ver=v1_0_3_46472
preroot_ver=0.1.5
serial_number=556_______________
ethaddr=00:26:__:__:__:__
serialno=EUK_______
modelname=318522
runintime=10800
ftpserver=192.168.43.4
testfile=100M
mfgtest_state=system_tested_ok
usb_make_boot_args=setenv bootargs console=ttyS0,115200 mtdparts=orion_nand:$(uboot_size)@$(uboot_start)(uboot),$(env_size)@$(env_start)(env),$(kernel_size)@$(kernel_start)(zImage),$(initrd_size)@$(initrd_start)(initrd),32m@0x0(flash) root=LABEL=rootfs rootdelay=10
load_initrd=ext2load usb 0:1 0x1100000 /boot/uInitrd
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
initrd_start=0x2d4000
disaMvPnp=no
eth1addr=00:__:__:__:__:__
enaAutoRecovery=yes
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial
load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
load_uinitrd=ext2load usb 0:1 0x2100000 /boot/uInitrd
usb_boot=mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x2100000
usb_bootcmd=run usb_set_bootargs; run usb_boot
bootcmd=usb start; run usb_bootcmd; usb stop; reset

Environment size: 2615/16380 bytes
Marvell>> boot


Unknown command 'usb' - try 'help'

** Block device usb 0 not supported

** Block device usb 0 not supported
## Booting image at 00800000 ...
Bad Magic Number
Unknown command 'usb' - try 'help'

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__|  ** uboot_ver:v1.0.0 **

 ** MARVELL BOARD: IX4-110 LE 

U-Boot 1.1.4 (Jul 23 2009 - 14:25:44) Marvell version: 3.4.4

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006904EC

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB 
DRAM CS[1] base 0x10000000   size 256MB 
DRAM Total size 512MB  16bit width
Found 0x20 i2c device
Set Power State as Always On
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:32 MB
Found ADT7473, program LED ...(led_volt=90)  OK
Found ADT7473, program thermal/Fan ...(pwm_min=0) (pwm_max=130) (therm=67) (temp_min=60)  OK

Marvell Serial ATA Adapter
Integrated Sata device found


CPU : Marvell Feroceon (Rev 1)
Found initrd at 0x2d4000

Streaming disabled 
Write allocate disabled

Module 0 is RGMII
Module 1 is RGMII

USB 0: host mode
PCI 0: PCI Express Root Complex Interface
PEX interface detected Link X1
SCSI:  AHCI 0001.0000 32 slots 3 ports 3 Gbps 0x7 impl IDE mode
flags: 64bit ncq stag led pmp slum part 
scanning bus for devices...
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  1  0 
Unknown command 'usb' - try 'help'

** Block device usb 0 not supported

** Block device usb 0 not supported
## Booting image at 00800000 ...
Bad Magic Number
Unknown command 'usb' - try 'help'

Edited 1 time(s). Last edit at 01/29/2021 07:06AM by Radm.

Radm,

I forgot that this box stock u-boot might not have usb command support.

Read this thread from the 1st post down, see if you can confirm that you have to boot from this ix4-200d box using the HDD "raw sectors".

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

After playing a bit around and reading even more posts, some good news: I've managed to flash stock uboot 1.1.4 which supports the usb command and to boot into debian. In case anyone needs the steps, this is how I've done it:

This implies you have some drives in the nas and a working installation of the default linux "distro" from iomega (the default one with the web-interface).

1. Startup the nas normally
2. Download the uboot-1.1.4-Mar-10-2011.mtd0 attachment from https://forum.doozan.com/read.php?2,22623,29586#msg-29586
3. Copy the image to the NAS and ssh into it
4. Write image to nand:

flash_eraseall /dev/mtd0
nandwrite -p /dev/mtd0 uboot-1.1.4-Mar-10-2011.mtd0

5. Reboot (or shutdown)

6. Prepare rootfs usb stick with Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (see https://forum.doozan.com/read.php?2,12096)
7. Attach serial, start the nas and interrupt at boot
8. Set env vars:

	setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'
	setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
	setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd'
	setenv usb_boot 'mw 0x800000 0 1; run load_uimage; if run load_uinitrd; then bootm 0x800000 0x2100000; else bootm 0x800000; fi'
	setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd'
	setenv usb_boot 'mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x2100000'
	setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
	setenv bootcmd 'usb start; run usb_bootcmd; usb stop; reset'
	setenv rootfstype ext3

9. And then boot

boot

And there we go, booting into debian

Marvell>> boot

(Re)start USB...
USB:   scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
....
.
......
............
.........................
...................................................
......................................................................................................
............................................................................................................................................................................................................
....
.......................................................................

4972946 bytes read
....
.
......
............
.........................
...................................................
......................................................................................................
.................................................................................................................................................................................................................
.........................................................................................................................................................................................................................................................................................................................................................................................................................
............................................................................................................................

9713936 bytes read
## Booting image at 00800000 ...
   Image Name:   Linux-5.2.9-kirkwood-tld-1
   Created:      2021-02-05  18:10:18 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4972882 Bytes =  4.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 02100000 ...
   Image Name:   initramfs-5.2.9-kirkwood-tld-1
   Created:      2019-08-25   2:22:50 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9713872 Bytes =  9.3 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000][    T0] Booting Linux on physical CPU 0x0
[    0.000000][    T0] Linux version 5.2.9-kirkwood-tld-1 (root@tldDebian) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 PREEMPT Sat Aug 17 15:00:56 PDT 2019
[    0.000000][    T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f

Hope this can resolve someone elses struggle
Thanks bodhi for helping out :)



Ps. Is there meanwhile support for the small front display, or for controlling the fan? And is there a newer uboot I can flash on it, so I don't have to regenerate the uInitrd everytime an update-initramfs happens?



Edited 2 time(s). Last edit at 02/05/2021 04:16PM by Radm.

Radm,

Well done!

> Ps. Is there meanwhile support for the small front
> display, or for controlling the fan?

Let me take a look in the DTS. LCD support should have been in the kernel config. But the LCD must be also in the DTS to make it work.

> And is there
> a newer uboot I can flash on it, so I don't have
> to regenerate the uInitrd everytime an
> update-initramfs happens?

You don't need new u-boot to do this. Debian flash-kernel will do this. But I've recommended removing it in the kernel upgrade instruction, since it is not a sure thing flash-kernel wil handle the customed kernel like ours correctly (there is a way to ensure flash-kernel will behave the way we want, but needs more set up).

Besides, each time you upgrade the kernel, or upgrade Debian, you should manually examine the result anyway. So regenerating uImage and/or uInitrd manually is not much more works.

With that said, if you want to set up some automatic Debian upgrade (or some trigger) it is possible to make sure the uInitrd will be recreated.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I don't think there is a driver/binding for this type of display (please correct me if I'm wrong about that).

Last year I wrote a python script which displays a bitmap on the screen (it can also be used to read the screen). Checkout lcd_test.py here:
https://github.com/1000001101000/ix4-200d-research

I was originally planning to do a bunch of other things for this device but ran into some roadblocks getting sata working on mine for some reason.

....I also took on too many projects shortly before my free time started getting shorter which led to a bit of a burnout, I don't know how bodhi does it!

1000001101000,

> I don't think there is a driver/binding for this
> type of display (please correct me if I'm wrong
> about that).
>
> Last year I wrote a python script which displays a
> bitmap on the screen (it can also be used to read
> the screen). Checkout lcd_test.py here:
> https://github.com/1000001101000/ix4-200d-research

Thanks, I defer to your experience about this :) I recall some binding for LCD in some Armada boxes. But I don't really know if this LCD needs some driver that is not in mainline yet.

>
> I was originally planning to do a bunch of other
> things for this device but ran into some
> roadblocks getting sata working on mine for some
> reason.
>
> ....I also took on too many projects shortly
> before my free time started getting shorter which
> led to a bit of a burnout, I don't know how bodhi
> does it!

I do get burnt out from time to time. Been on this forum for 10 years already :) But my cure of burn out is that I hope people get curious about my blog (in my signature) and visit it. And I just stop doing any more new hacking for a while, just helping out with problems here, and go read some books.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Quote

> I was originally planning to do a bunch of other
> things for this device but ran into some
> roadblocks getting sata working on mine for some
> reason.

May be I can help looking at the log?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Quote
bodhi
Thanks, I defer to your experience about this :) I recall some binding for LCD in some Armada boxes. But I don't really know if this LCD needs some driver that is not in mainline yet.

I believe the binding is for the shift-register that is used to multiplex the LEDs (I had fun writing a script to find those pins). As far as I could tell when I was looking into it there was no mainline driver for that kind of LCD though the person I originally forked that repo wrote one for the armada device which appeared to be based on the GPL code for that device. I wrote something vaguely equivalent in python which has the added bonus of using soem python libraries to handle converting the input image into something usable for the display code.

re-writing stuff that NAS vendors put in their custom kernel code as user space bash/python utilities is turning into a specialty of mine.

I know this is old, but I want to upgrade the OEM firmware to support SMB v2 or higher. is there a step by step idiots guide how to do all the above?

reformedfan,

> I know this is old, but I want to upgrade the OEM
> firmware to support SMB v2 or higher. is there a
> step by step idiots guide how to do all the above?

You will need serial console connected. And create the Debian rootfs on USB using Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2

See the rootfs release thread:
https://forum.doozan.com/read.php?2,12096

Scroll down to section:

Quote

Updated 25 Aug 2019:

Basic Debian buster Kirkwood rootfs for most Kirwood plugs:

After you have the USB rootfs. Attach it to the box. Power up, and use serial console to enter envs to boot:

https://forum.doozan.com/read.php?2,102054,105374#msg-105374

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Great thanks, that will get me started. As always more questions on the way, but first.

1) Once complete, can you monitor for RAID5/disk failure? How would I get alerted?
2) Not so importation, as I have backed up the data, but can you protect the existing RAID group and thus the data (4 x 3TB = 5.26 TB)?



Edited 2 time(s). Last edit at 05/17/2021 07:41AM by reformedfan.

reformedfan,

> 1) Once complete, can you monitor for RAID5/disk
> failure? How would I get alerted?
> 2) Not so importation, as I have backed up the
> data, but can you protect the existing RAID group
> and thus the data (4 x 3TB = 5.26 TB)?


This is the basic Debian rootfs, so only neccessary packages were installed. For advance users, this avoids bloat, and for beginner users it is a learning vehicle.

For advance suff, you would need to add to it. Things like alert, you would need a cron job to monitor the RAID status.

For bring up existing RAID array that was built with much older Linux, see here:

https://forum.doozan.com/read.php?3,106724,120859#msg-120859

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi, where is the serial pin out on the Mobi. I see no jumpers and guess it is in the attached, the 2 x 5 pins (top RHS). if so can anyone help for which pins to use for tx, rx, 3.3 and gnd?

reformedfan,

Not sure if you can see it clearly, the picture attached in the first post:

https://forum.doozan.com/read.php?2,22623,22623#msg-22623

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi Bodhi,

Thank you for your help, it's been so useful. I did see the image and have attached my board in the previous post. It is really hard to work out which pins are for what. If we look at the board, with the pin are at the top right with the I/O on the right (NICs). which it which?

Simplified

x x x x -> Rear (NICs)
x x x x
<- front of unit

1 2 3 4 5
6 7 8 9 10


As there are no pins on the board I shall solder some on.
Many thanks

reformedfan,

I'm not sure either (I don't have this box). Hopefully damacc will come by and answer the question.

Anybody who has this box, please help!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

This should be the pinout, I also marked it on the picture of the board :)

CN4 
--------------
|  9 8 6 4 2 |
| 10 7 5 3 1 |
-------------- PIN 1 Mark (fat line)


 1 = RXD
 4 = TXD
 6 = GND
10 = 3.3v

Awesome! thanks damacc.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks to you both, i'll crack on! serial now connected



Edited 1 time(s). Last edit at 05/22/2021 05:35AM by reformedfan.

All, good, now can ssh.
1) how do you install samba - see error below - ignore - apt-get update !!!!! all fixed
2) how do you commit the env, so when you reboot it uses rootfs?
3) to create the raid do you use fdisk?
4)how do you stop nfs as I dont need it

Apt install samba...
Do you want to continue? [Y/n] Y
Err:1 http://ftp.us.debian.org/debian buster/main armel libpython2.7-minimal armel 2.7.16-2
404 Not Found [IP: 64.50.236.52 80]
Err:2 http://ftp.us.debian.org/debian buster/main armel python2.7-minimal armel 2.7.16-2


Cheers
Matthew



Edited 3 time(s). Last edit at 05/22/2021 11:34AM by reformedfan.

Matthew,

Quote

2) how do you commit the env, so when you reboot it uses rootfs?

First, make sure that serial log to console does not show any error during boot. Interrupt serial console, and

Repeat the setenvs like you did:

setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'
setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd'
setenv usb_boot 'mw 0x800000 0 1; run load_uimage; if run load_uinitrd; then bootm 0x800000 0x2100000; else bootm 0x800000; fi'
setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
setenv bootcmd 'usb start; run usb_bootcmd; usb stop; reset'

And then, save it before booting,

saveenv

Print out the envs for keepsake,

printenv
boot

Quote

3) to create the raid do you use fdisk?

Use mdadm to create the array.

Quote

4)how do you stop nfs as I dont need it

It does not hurt to run it always and without export any shared folder (its memory footprint is very small during idle).

However, to disable it so it will not run during boot, install and run rcconf in Debian:

apt-get install rcconf
rcconf

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Cheers again, all going well.

Would like get your views

1) RAID - Guess there is no H/W raid. I did get it all working and I mounted the old RAID volumes, installed LVM and made it active https://www.cyberciti.biz/faq/linux-mount-an-lvm-volume-partition-command. I didnt use MDADM as it didnt like the LVM2 volume

2) rootfs is running off the USB,. I guess this has to as the OEM boot is inside the RAID LVM.

3) swap - had to set up SWAP, pointed to a file on the RAID volume using https://linuxize.com/post/how-to-add-swap-space-on-debian-10/

4) How would I monitor for RAID/disk failuire? e.g when disk dies or SMART sends a warning.


Thanks again, progress and I look forward to hearing from you and if you are in the UK i'll buy you a beer.
Matthew



Edited 7 time(s). Last edit at 05/23/2021 03:35PM by reformedfan.

reformedfan,

> 2) rootfs is running off the USB,. I guess this
> has to as the OEM boot is inside the RAID LVM.

Make sure to take precaution. Back up regularly

https://forum.doozan.com/read.php?2,111249,111249#msg-111249

and do some set up to prolong the life of your USB rootfs:

https://forum.doozan.com/read.php?2,13702,13704#msg-13704

> 4) How would I monitor for RAID/disk failuire?
> e.g when disk dies or SMART sends a warning.

IMO, for home usage, RAID is not needed. Just have a daily backup job that back up your rootfs and files to another box in the network, or to an attached USB HDD.

I don't have a setup to notify disk failure. But it should be simple. smartcl daemon can be set up in /etc/smartd.conf to send mail.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)