Skip to content

Instantly share code, notes, and snippets.

@braian87b
Last active April 27, 2023 11:46
  • Star 11 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
Star You must be signed in to star a gist
Save braian87b/b5a4c5f20d1112473c470b096df766a3 to your computer and use it in GitHub Desktop.
How to Install pure Debian on Iomega EZ Media and Backup Center
# Relevant info about this:
https://forum.lede-project.org/t/lenovo-iomega-ez-media-backup-center/5031/ # "Lenovo Iomega EZ Media & Backup Center"
https://forum.doozan.com/read.php?2,35331,35434#msg-35434 # "Lenovo iomega EZ support" but read entire thread if it is possible
https://forum.doozan.com/read.php?2,15887 # "Debian on Iomega EZ Media & Backup Center" this is another thread about
https://forum.doozan.com/read.php?2,12096 # "Linux Kernel 4.14.1 Kirkwood package and Debian rootfs" Kernel and rootfs, thanks to this it is possible to run Debian
# Newer kernel guide:
https://gist.github.com/koczaj/a20ed52c969a8d0612986ca576067876
# Using a Debian box (it could be a VM) with the harddrive connected (it could be a minimal net-install Debian)
See ip with:
ip addr show
# connect remotely using:
user@outside:~/# ssh user@10.211.55.6
# We elevate permissions or even better install and config sudo
user@debian8vm:~/# su
root@debian8vm:~/# apt-get install sudo -y
root@debian8vm:~/# sudo adduser user sudo
user@debian8vm:~/# exit
root@debian8vm:~/# exit
user@outside:~/# ssh user@10.211.55.6
user@debian8vm:~/# sudo su
# install miscelaneous
root@debian8vm:~/# apt-get install u-boot-tools parted gdisk -y
# Should be already installed
root@debian8vm:~/# apt-get install wget tar -y
# if we want to read the hardware description table file
root@debian8vm:~/# apt-get install device-tree-compiler-y
# we create a directory to work whithin
root@debian8vm:~/# mkdir iomegaez
root@debian8vm:~/# cd iomegaez
# download needed files
# we could use kernel 4.12 or newer one 4.14
root@debian8vm:~/iomegaez/# wget https://www.dropbox.com/s/orud4fq131gtut9/linux-4.12.1-kirkwood-tld-1-bodhi.tar.bz2
root@debian8vm:~/iomegaez/# wget https://www.dropbox.com/s/2gmcik1hu95i316/linux-4.14.1-kirkwood-tld-1-bodhi.tar.bz2
# we download Debian rootfs
root@debian8vm:~/iomegaez/# wget https://www.dropbox.com/s/wsyuzr69se20um2/Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2
# we download the hardware description tables for the Iomega EZ
root@debian8vm:~/iomegaez/# wget https://forum.doozan.com/file.php?2,file=1456,filename=kirkwood-lenovo-iomega-ez.dtb,download=1 -O kirkwood-lenovo-iomega-ez.dtb
# if we want to check it out:
root@debian8vm:~/iomegaez/# fdtdump kirkwood-lenovo-iomega-ez.dtb
# make directories for Kernel and Debian rootfs and uncompress them:
root@debian8vm:~/iomegaez/# mkdir linux-4.14.1-kirkwood-tld-1-bodhi Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi
root@debian8vm:~/iomegaez/# tar -jxvf linux-4.14.1-kirkwood-tld-1-bodhi.tar.bz2 -C linux-4.14.1-kirkwood-tld-1-bodhi
root@debian8vm:~/iomegaez/# tar -jxvf Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 -C Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi
# These are the files:
root@debian8vm:~/iomegaez/# ls -lht ./linux-4.14.1-kirkwood-tld-1-bodhi/
# # total 32M
# # -rw-r--r-- 1 root root 141K Nov 25 19:59 linux-4.14.1-kirkwood-tld-1.patch
# # -rw-r--r-- 1 root root 1.3M Nov 24 02:48 linux-dtb-4.14.1-kirkwood-tld-1.tar
# # -rw-r--r-- 1 root root 8.4M Nov 23 20:56 linux-headers-4.14.1-kirkwood-tld-1_1.0_armel.deb
# # -rw-r--r-- 1 root root 18M Nov 23 20:38 linux-image-4.14.1-kirkwood-tld-1_1.0_armel.deb
# # -rw-r--r-- 1 root root 152K Nov 23 19:41 config-4.14.1-kirkwood-tld-1
# # -rwxr-xr-x 1 root root 3.7M Nov 23 04:40 zImage-4.14.1-kirkwood-tld-1
root@debian8vm:~/iomegaez/# ls -lht ./Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi/boot/
# # total 36M
# # -rw-r--r-- 1 root root 39K Nov 30 03:02 uImage
# # -rw-r--r-- 1 root root 7.0M Nov 30 03:02 uInitrd
# # -rw-r--r-- 1 root root 39K Nov 30 02:58 zImage.fdt
# # -rw-r--r-- 1 root root 64 Nov 30 02:55 uInitrd.bak
# # -rw-r--r-- 1 root root 7.0M Jul 23 21:15 initrd.img-4.12.1-kirkwood-tld-1
# # -rw-r--r-- 1 root root 3.7M Jul 20 05:11 uImage.bak
# # -rw-r--r-- 1 root root 8.1M Jul 16 05:06 linux-headers-4.12.1-kirkwood-tld-1_1.0_armel.deb
# # -rw------- 1 root root 2.4M Jul 16 04:43 System.map-4.12.1-kirkwood-tld-1
# # -rw------- 1 root root 3.7M Jul 16 04:43 vmlinuz-4.12.1-kirkwood-tld-1
# # -rwxr-xr-x 1 root root 3.7M Jul 16 01:42 zImage-4.12.1-kirkwood-tld-1
# # -rw-r--r-- 1 root root 150K Jul 16 00:21 config-4.12.1-kirkwood-tld-1
# # drwxr-xr-x 2 root root 4.0K Jul 15 19:14 dts
# Here there is a hardware descriptor table, but it has some problems, do not use.
root@debian8vm:~/iomegaez/# ls -lht ./Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi/boot/dts/ | grep 'iomega-ez'
# # -rw-r--r-- 1 root root 13K Jul 16 05:08 kirkwood-lenovo-iomega-ez.dtb
# Creating uImage & uInitrd and putting it to the disk
# We will work on boot directory from the rootfs dirtree
root@debian8vm:~/iomegaez/# cd ./Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi/boot/
# we copy the zImage file to a zImage.fdt
root@debian8vm:~/(...)/boot# cp -a zImage-4.12.1-kirkwood-tld-1 zImage.fdt
# if we want to check it out (see the fdt data on the dtb file):
# root@debian8vm:~/iomegaez/# # fdtdump dts/kirkwood-lenovo-ix2-ng.dtb
# Do not use this file, use below instead:
# root@debian8vm:~/(...)/boot# # cat dts/kirkwood-lenovo-ix2-ng.dtb >> zImage.fdt
# Important: We must put dtb data AT THE END of the zImage.fdt file.
root@debian8vm:~/(...)/boot# cat ../../kirkwood-lenovo-iomega-ez.dtb >> zImage.fdt
root@debian8vm:~/(...)/boot# #cp -a uImage uImage.bak
root@debian8vm:~/(...)/boot# #cp -a uInitrd uInitrd.bak
# This are the name of the images, initrd image is the same name as the file we use as source
root@debian8vm:~/(...)/boot# INITRD_IMAGE="initrd.img-4.12.1-kirkwood-tld-1"
root@debian8vm:~/(...)/boot# LINUX_TLD="Linux-4.12.1-kirkwood-tld-1"
# Create initramfs image:
root@debian8vm:~/(...)/boot# mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n $INITRD_IMAGE -d $INITRD_IMAGE uInitrd
# # Image Name: initrd.img-4.12.1-kirkwood-tld-1
# # Created: Thu Nov 30 03:02:50 2017
# # Image Type: ARM Linux RAMDisk Image (gzip compressed)
# # Data Size: 7245632 Bytes = 7075.81 kB = 6.91 MB
# # Load Address: 00000000
# # Entry Point: 00000000
# Create kernel image
root@debian8vm:~/(...)/boot# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n $LINUX_TLD -d zImage.fdt uImage
## Image Name: Linux-4.12.1-kirkwood-tld-1
## Created: Thu Nov 30 03:02:58 2017
## Image Type: ARM Linux Kernel Image (uncompressed)
## Data Size: 39273 Bytes = 38.35 kB = 0.04 MB
## Load Address: 00008000
## Entry Point: 00008000
# write the images to disk
root@debian8vm:~/iomegaez/# dd if=uImage of=/dev/sdb bs=1MiB seek=10
root@debian8vm:~/iomegaez/# dd if=uInitrd of=/dev/sdb bs=1MiB seek=20
# create partitions on the disk, using GPT since the disk is probably bigger than 2Tb
root@debian8vm:~/iomegaez/# parted -s /dev/sdb mklabel gpt \
mkpart swap linux-swap 100MiB 8.1GiB \
mkpart rootfs ext3 8.1GiB 24.1GiB \
mkpart Data ext3 24.1GiB 100%
# this creates 100Mb unused space, 8gb for swap, 16gb for rootfs and rest of the disk for Data
# Chek out the partitions (we check using gdisk if it is correct swap should be code 82 and other two are 83)
root@debian8vm:~/iomegaez/# parted /dev/sdb print
root@debian8vm:~/iomegaez/# gdisk /dev/sdb -l
# IMPORTANT: don't bother if the virtual machine fails to recognize more than 1.6 or 1.8Tb, we can fix this later.
# we format and set label to 2nd partition
root@debian8vm:~/iomegaez/# mkfs.ext3 /dev/sdb2 -L rootfs
# Create mountpoint and mount partition
root@debian8vm:~/iomegaez/# mkdir /mnt/sdb2 && mount /dev/sdb2 /mnt/sdb2
# Copy the rootfs dirtree to mountpoint
root@debian8vm:~/iomegaez/# tar -C ./Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi/ -cvf - . | tar -C /mnt/sdb2 -xf -
root@debian8vm:~/iomegaez/# sync; sync; sync
# unmount and remove mountpoint
root@debian8vm:~/iomegaez/# umount /mnt/sdb2 && rmdir /mnt/sdb2
# IMPORTANT, if we Forget to set proper label as 'rootfs' the label is has to be on the filesystem
# it is not enough that if it was set as label on the GPT table
root@debian8vm:~/iomegaez/# e2label /dev/sdb2
root@debian8vm:~/iomegaez/# e2label /dev/sdb2 rootfs
root@debian8vm:~/iomegaez/# e2label /dev/sdb2
# Now we can disconnect the harddrive and put in the Iomega EZ box
# We must connect a Serial TTL Cable as described here: https://forum.lede-project.org/t/lenovo-iomega-ez-media-backup-center/5031/13?u=braian87b
# Original bootargs and bootcmd (I copy mine here since we are gonna modify it) :
Marvell>> printenv
# # bootargs=console=ttyS0,115200 root=/dev/ram0 mtdparts=spi_flash:0x7e000@0(u-boot),0x1000@0x7f000(env),0x1000@0x7e000(env2) :::DB88FXX81:eth0:none
# # bootcmd=ide reset; ide read 0x40000 0x800 0x1800; ide read 0x900000 0x2000 0x2000; setenv bootargs $(console) $(bootargs_root) $(bootargs_mtd) $(bootargs_end); bootm 0x40000 0x900000;run bootcmd2
# # bootcmd2=ide dev 1;ide read 0x40000 0x800 0x1800; ide read 0x900000 0x2000 0x2000; bootm 0x40000 0x900000;
# Commands to boot, must be used with a USB-Serial-TTL cable
Marvell>> setenv bootargs 'root=/dev/sda2 init=/bin/systemd fsck.mode=force fsck.repair=yes console=ttyS0,115200 mtdparts=spi_flash:0x7e000@0(u-boot),0x1000@0x7f000(env),0x1000@0x7e000(env2)'
Marvell>> setenv bootcmd 'ide read 0x40000 0x5000 0x2000; ide read 0x2100000 0xA000 0x4000; bootm 0x40000 0x2100000'
# To persist chages to flash chip on the PCB (you could try to boot first to see if everything is working
Marvell>> saveenv
# try to boot (to see if it works)
Marvell>> boot
# Now it must boot properly, check the IP of the box and connect using SSH or continue using serial
# username: root
# password: root
# If the vm didn't recognize all the capacity of the harddrive, now we could fix that easily
# If we run:
root@debian:~# parted /dev/sda print
# Wil say:
# # Warning: Not all of the space available to /dev/sda appears to be used, you can
# # fix the GPT to use all of the space (an extra 8589934592 blocks) or continue
# # with the current setting?
# We put:
Fix
# This will align a little the end of the last partition, now we must resize completely the last partition
root@debian:~# parted -s /dev/sda resizepart 3 100%
# Another way it could be to remove the 3rd partition and create it again, but I do not recommend it, I didn't try it by myself
root@debian:~# parted -s /dev/sda rm 3 mkpart Data ext3 24.1GiB 100%
# now data partition it should fill the rest of the disk
root@debian:~# parted /dev/sda print
# Enable Swap partition
root@debian:~# mkswap /dev/sda1
# # Setting up swapspace version 1, size = 8 GiB (8592445440 bytes)
# # no label, UUID=c37d2e4c-dd32-40e5-9d4a-cea151d02389
root@debian:~# free -h
# # total used free shared buff/cache available
# # Swap: 0B 0B 0B
root@debian:~# swapon /dev/sda1
root@debian:~# free -h
# # total used free shared buff/cache available
# # Swap: 8.0G 0B 8.0G
cat<<'EOF' >> /etc/fstab
/dev/sda1 none swap sw 0 0
EOF
# TODO: try LEDE, try USB boot, apt-get upgrade, LEDS and buttons, auto spindown disk, etc, etc
# ------------------------------------------------------------------------------------------
Special thanks and acknowledgmentto: Ein (thanks for your dedication on this!),
bobafetthotmail for be the first to push me to try, Bodhi, armik, Mijzelf and all the help on the Doozan and Lede-Project Forums
@koczaj
Copy link

koczaj commented May 27, 2020

Marvell>>` printenv
baudrate=115200
loads_echo=0
rootpath=/srv/ubuntu
run_diag=yes
MALLOC_len=1
ethprime=egiga0
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
lcd0_enable=0
lcd0_params=640x480-16@60
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev[0]:fxs,dev[1]:fxo
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
image_multi=yes
ethact=egiga0
console=console=ttyS0,115200
bootargs_root=root=/dev/ram0
bootargs_mtd=mtdparts=spi_flash:0x7e000@0(u-boot),0x1000@0x7f000(env),0x1000@0x7e000(env2)
kernelimage=zImage
initrdimage=mfginitrd
mfgmodel=ix1
preroot_ver=0.0.2
uboot_ver=0.0.8
serial_number=5563Z01001G3180036FJ0C1
ethaddr=00:D0:B8:14:41:12
serialNo=EUAD19009R
modelname=32041100
serialno=0,01IwLhPM5+5+jdZI07rVgbhfeCiqQrioX6Glf/Nudm0r9qIKdB9hjMm1dcDPhK05GM,EUAD19009R,
fw_ver=4.0.2.9497
runintime=10800
ftpserver=192.168.43.4
testfile=100M
mfgtest_state=system_tested_ok
pre_path=IX1/1.0.5/download_runin.sh
pre_path_conf=IX1/1.0.5/download_runin.conf
pre_serverip=192.168.32.4
pre_user=ixxrunin
pre_passwd=123
pre_dirzi=IX1/1.0.5
bootcmd2=ide dev 1;ide read 0x40000 0x800 0x1800; ide read 0x900000 0x2000 0x2000; bootm 0x40000 0x900000;
filesize=9438d0
fileaddr=900000
gatewayip=192.168.0.1
netmask=255.255.255.0
hostname=kieszen
ipaddr=192.168.0.90
serverip=192.168.0.1
bootargs=root=/dev/sda2 init=/bin/systemd fsck.mode=force fsck.repair=yes console=ttyS0,115200 mtdparts=spi_flash:0x7e000@0(u-boot),0x1000@0x7f000(env),0x1000@0x7e000(env2)
bootcmd=ide read 0x40000 0x5000 0x2A00; ide read 0x2100000 0xA000 0x4000; bootm 0x40000 0x2100000
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
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
pcieTune=no
pcieTune1=no

Environment size: 2128/4091 bytes

@koczaj
Copy link

koczaj commented May 27, 2020

One more comment: I little bit changed bootenv settings to below:
s

etenv bootcmd 'ide read 0x40000 0x5000 0x2A00; ide read 0x2100000 0xA000 **0x5000**; bootm 0x40000 0x2100000'

Now I don't see CRC issue but there is other problem:

> 
>  ** MARVELL BOARD: DB-88F6282A-BP LE
> 
> U-Boot 1.1.4 (Oct 28 2011 - 15:17:21) Marvell version: 3.6.1 - EMC
> 
> U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CD5A0
> 
> Soc: 88F6282 A1 CPU running @ 1200Mhz L2 running @ 400Mhz
> SysClock = 400Mhz , TClock = 200Mhz
> 
> DRAM (DDR3) CAS Latency = 6 tRP = 6 tRAS = 15 tRCD=6
> DRAM CS[0] base 0x00000000   size 128MB
> DRAM Total size 128MB  16bit width
> Addresses 8M - 0M are saved for the U-Boot usage.
> Mem malloc Initialization (8M - 7M): Done
> [1024kB@f8000000] Flash:  1 MB
> 
> Marvell Serial ATA Adapter
> Integrated Sata device found
> [0 0 0]: Enable DMA mode (6)
>   Device 0 @ 0 0:
> Model: WDC WD3200BPVT-80ZEST0                   Firm: 01.01A01 Ser#:      WD-WX51AC084375
>             Type: Hard Disk
>             Supports 48-bit addressing
>             Capacity: 305245.3 MB = 298.0 GB (625142448 x 512)
> 
> 
> CPU : Marvell Feroceon (Rev 1)
> 
> Streaming disabled
> Write allocate disabled
> 
> 
> USB 0: host mode
> PEX 0: interface detected no Link.
> PEX 1: interface detected no Link.
> Net:   egiga0 [PRIME]
> Hit any key to stop autoboot:  0
> 
> IDE read: device 0 block # 20480, count 10752 ... 10752 blocks read: OK
> 
> IDE read: device 0 block # 40960, count 20480 ... 20480 blocks read: OK
> ## Booting image at 00040000 ...
>    Image Name:   linux-headers-5.2.9-kirkwood-tld
>    Created:      2020-05-27  14:28:50 UTC
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    4976261 Bytes =  4.7 MB
>    Load Address: 00008000
>    Entry Point:  00008000
>    Verifying Checksum ... OK
> OK
> ## Loading Ramdisk Image at 02100000 ...
>    Image Name:   initrd.img-5.2.9-kirkwood-tld-1
>    Created:      2020-05-27  14:29:12 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 ...
> 
> [    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
> [    0.000000][    T0] CPU: VIVT data cache, VIVT instruction cache
> [    0.000000][    T0] OF: fdt: Machine model: Lenovo IX2-ng
> [    0.000000][    T0] Memory policy: Data cache writeback
> [    0.000000][    T0] Built 1 zonelists, mobility grouping on.  Total pages: 32512
> [    0.000000][    T0] Kernel command line: console=ttyS0,115200 root=/dev/mtdblock0 rw ip=192.168.0.90:192.168.0.1:::DB88FXX81:eth0:none mv_phone_config=dev[0]:fxs,dev[1]:fxo
> [    0.000000][    T0] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
> [    0.000000][    T0] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
> [    0.000000][    T0] Memory: 104828K/131072K available (9216K kernel code, 868K rwdata, 3400K rodata, 1024K init, 301K bss, 26244K reserved, 0K cma-reserved)
> [    0.000000][    T0] random: get_random_u32 called from cache_alloc_refill+0x38c/0x928 with crng_init=0
> [    0.000000][    T0] rcu: Preemptible hierarchical RCU implementation.
> [    0.000000][    T0]  Tasks RCU enabled.
> [    0.000000][    T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
> [    0.000000][    T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
> [    0.000000][    T0] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
> [    0.000008][    T0] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
> [    0.000046][    T0] Switching to timer-based delay loop, resolution 5ns
> [    0.000799][    T0] Console: colour dummy device 80x30
> [    0.000849][    T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
> [    0.000876][    T0] pid_max: default: 32768 minimum: 301
> [    0.001244][    T0] LSM: Security Framework initializing
> [    0.001423][    T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
> [    0.001450][    T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
> [    0.002304][    T0] *** VALIDATE proc ***
> [    0.002563][    T0] *** VALIDATE cgroup1 ***
> [    0.002589][    T0] *** VALIDATE cgroup2 ***
> [    0.002685][    T0] CPU: Testing write buffer coherency: ok
> [    0.004341][    T1] Setting up static identity map for 0x100000 - 0x100058
> [    0.004628][    T1] mvebu-soc-id: MVEBU SoC ID=0x6282, Rev=0x1
> [    0.004907][    T1] rcu: Hierarchical SRCU implementation.
> [    0.008065][    T1] devtmpfs: initialized
> [    0.014065][    T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
> [    0.014095][    T1] futex hash table entries: 256 (order: -1, 3072 bytes)
> [    0.014335][    T1] xor: measuring software checksum speed
> [    0.110112][    T1]    arm4regs  :  1084.000 MB/sec
> [    0.210076][    T1]    8regs     :   650.800 MB/sec
> [    0.310070][    T1]    32regs    :   946.000 MB/sec
> [    0.310088][    T1] xor: using function: arm4regs (1084.000 MB/sec)
> [    0.310108][    T1] prandom: seed boundary self test passed
> [    0.314304][    T1] prandom: 100 self tests passed
> [    0.314315][    T1] pinctrl core: initialized pinctrl subsystem
> [    0.315717][    T1] NET: Registered protocol family 16
> [    0.316273][    T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
> [    0.317079][    T1] audit: initializing netlink subsys (disabled)
> [    0.318306][   T14] audit: type=2000 audit(0.310:1): state=initialized audit_enabled=0 res=1
> [    0.318422][    T1] cpuidle: using governor ladder
> [    0.318496][    T1] cpuidle: using governor menu
> [    0.319053][    T1] Feroceon L2: Enabling L2
> [    0.319102][    T1] Feroceon L2: Cache support initialised.
> [    0.325494][    T1] No ATAGs?
> [    2.560053][    C0] random: fast init done
> [    6.253117][   T71] alg: No test for lzo-rle (lzo-rle-generic)
> [    6.253476][   T73] alg: No test for lzo-rle (lzo-rle-scomp)
> [    6.430695][    T1] raid6: int32x8  gen()   127 MB/s
> [    6.600440][    T1] raid6: int32x8  xor()    86 MB/s
> [    6.770360][    T1] raid6: int32x4  gen()   129 MB/s
> [    6.940332][    T1] raid6: int32x4  xor()    83 MB/s
> [    7.110096][    T1] raid6: int32x2  gen()   132 MB/s
> [    7.280361][    T1] raid6: int32x2  xor()    94 MB/s
> [    7.450610][    T1] raid6: int32x1  gen()   100 MB/s
> [    7.620329][    T1] raid6: int32x1  xor()    68 MB/s
> [    7.620340][    T1] raid6: using algorithm int32x2 gen() 132 MB/s
> [    7.620348][    T1] raid6: .... xor() 94 MB/s, rmw enabled
> [    7.620357][    T1] raid6: using intx1 recovery algorithm
> [    7.620620][    T1] vgaarb: loaded
> [    7.621140][    T1] SCSI subsystem initialized
> [    7.621647][    T1] usbcore: registered new interface driver usbfs
> [    7.621719][    T1] usbcore: registered new interface driver hub
> [    7.621804][    T1] usbcore: registered new device driver usb
> [    7.621982][    T1] pps_core: LinuxPPS API ver. 1 registered
> [    7.621994][    T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
> [    7.622021][    T1] PTP clock support registered
> [    7.623363][    T1] clocksource: Switched to clocksource orion_clocksource
> [    8.658625][    T1] VFS: Disk quotas dquot_6.6.0
> [    8.658722][    T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> [    8.668590][    T1] NET: Registered protocol family 2
> [    8.669435][    T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes)
> [    8.669472][    T1] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
> [    8.669498][    T1] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
> [    8.669521][    T1] TCP: Hash tables configured (established 1024 bind 1024)
> [    8.669614][    T1] UDP hash table entries: 256 (order: 0, 4096 bytes)
> [    8.669643][    T1] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
> [    8.669882][    T1] NET: Registered protocol family 1
> [    8.670550][    T1] RPC: Registered named UNIX socket transport module.
> [    8.670564][    T1] RPC: Registered udp transport module.
> [    8.670573][    T1] RPC: Registered tcp transport module.
> [    8.670581][    T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
> [    8.670596][    T1] PCI: CLS 0 bytes, default 32
> [    8.670841][    T1] Trying to unpack rootfs image as initramfs...
> [    9.509391][    T1] Freeing initrd memory: 9488K
> [    9.509603][    T1] NetWinder Floating Point Emulator V0.97 (double precision)
> [    9.510887][    T1] Initialise system trusted keyrings
> [    9.510938][    T1] Key type blacklist registered
> [    9.511176][    T1] workingset: timestamp_bits=30 max_order=15 bucket_order=0
> [    9.511285][    T1] zbud: loaded
> [    9.512429][    T1] NFS: Registering the id_resolver key type
> [    9.512465][    T1] Key type id_resolver registered
> [    9.512475][    T1] Key type id_legacy registered
> [    9.512495][    T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
> [    9.512512][    T1] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> [    9.512808][    T1] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
> [    9.513047][    T1] fuse: init (API version 7.31)
> [    9.513531][    T1] orangefs_debugfs_init: called with debug mask: :none: :0:
> [    9.513733][    T1] orangefs_init: module version upstream loaded
> [    9.513746][    T1] SGI XFS with ACLs, security attributes, realtime, scrub, no debug enabled
> [    9.530970][    T1] async_tx: api initialized (async)
> [    9.530995][    T1] Key type asymmetric registered
> [    9.531005][    T1] Asymmetric key parser 'x509' registered
> [    9.531077][    T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
> [    9.532538][    T1] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
> [    9.534760][    T1] mv_xor f1060800.xor: Marvell shared XOR driver
> [    9.594195][    T1] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
> [    9.596232][    T1] mv_xor f1060900.xor: Marvell shared XOR driver
> [    9.654199][    T1] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
> [    9.656528][    T1] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
> [    9.657812][    T1] printk: console [ttyS0] disabled
> [    9.657889][    T1] f1012100.serial: ttyS0 at MMIO 0xf1012100 (irq = 27, base_baud = 12500000) is a 16550A
> [   10.413561][    T1] printk: console [ttyS0] enabled
> [   10.426212][    T1] loop: module loaded
> [   10.430644][    T1] sata_mv f1080000.sata: slots 32 ports 2
> [   10.439066][    T1] scsi host0: sata_mv
> [   10.443563][    T1] scsi host1: sata_mv
> [   10.447716][    T1] ata1: SATA max UDMA/133 irq 34
> [   10.452531][    T1] ata2: SATA max UDMA/133 irq 34
> [   10.459191][    T1] m25p80 spi0.0: mx25l8005 (1024 Kbytes)
> [   10.464802][    T1] 3 fixed-partitions partitions found on MTD device spi0.0
> [   10.471887][    T1] Creating 3 MTD partitions on "spi0.0":
> [   10.477428][    T1] 0x000000000000-0x00000007e000 : "u-boot"
> [   10.483111][    T1] mtd: partition "u-boot" doesn't end on an erase/write block -- force read-only
> [   10.493529][    T1] 0x00000007e000-0x00000007f000 : "u-boot env2"
> [   10.499653][    T1] mtd: partition "u-boot env2" doesn't start on an erase/write block boundary -- force read-only
> [   10.511342][    T1] 0x00000007f000-0x000000080000 : "u-boot env"
> [   10.517416][    T1] mtd: partition "u-boot env" doesn't start on an erase/write block boundary -- force read-only
> [   10.530174][    T1] libphy: Fixed MDIO Bus: probed
> [   10.535839][    T1] libphy: orion_mdio_bus: probed
> [   10.554953][    T1] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
> [   10.562981][    T1] mv643xx_eth_port mv643xx_eth_port.0: DMA mask not set
> [   10.571160][    T1] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:d0:b8:14:41:12
> [   10.580861][    T1] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> [   10.588196][    T1] ehci-pci: EHCI PCI platform driver
> [   10.593463][    T1] ehci-orion: EHCI orion driver
> [   10.598374][    T1] orion-ehci f1050000.ehci: EHCI Host Controller
> [   10.604645][    T1] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
> [   10.613206][    T1] orion-ehci f1050000.ehci: irq 31, io mem 0xf1050000
> [   10.643400][    T1] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
> [   10.650393][    T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.02
> [   10.659426][    T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> [   10.667404][    T1] usb usb1: Product: EHCI Host Controller
> [   10.673008][    T1] usb usb1: Manufacturer: Linux 5.2.9-kirkwood-tld-1 ehci_hcd
> [   10.680396][    T1] usb usb1: SerialNumber: f1050000.ehci
> [   10.686483][    T1] hub 1-0:1.0: USB hub found
> [   10.691026][    T1] hub 1-0:1.0: 1 port detected
> [   10.696460][    T1] usbcore: registered new interface driver usb-storage
> [   10.703653][    T1] mousedev: PS/2 mouse device common for all mice
> [   10.710559][    T1] rtc-mv f1010300.rtc: registered as rtc0
> [   10.716416][    T1] i2c /dev entries driver
> [   10.722172][    T1] device-mapper: uevent: version 1.0.3
> [   10.727887][    T1] device-mapper: ioctl: 4.40.0-ioctl (2019-01-18) initialised: dm-devel@redhat.com
> [   10.737535][    T1] device-mapper: multipath round-robin: version 1.2.0 loaded
> [   10.744887][    T1] device-mapper: multipath queue-length: version 0.2.0 loaded
> [   10.752264][    T1] device-mapper: multipath service-time: version 0.3.0 loaded
> [   10.759740][    T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
> [   10.766618][    T1] device-mapper: raid: Loading target version 1.14.0
> [   10.774686][    T1] hidraw: raw HID events driver (C) Jiri Kosina
> [   10.781171][    T1] drop_monitor: Initializing network drop monitor service
> [   10.788589][    T1] NET: Registered protocol family 17
> [   10.794028][    T1] Key type dns_resolver registered
> [   10.799877][    T1] registered taskstats version 1
> [   10.805096][    T1] Loading compiled-in X.509 certificates
> [   10.810692][    T1] zswap: loaded using pool lzo/zbud
> [   10.907562][    T1] Key type big_key registered
> [   10.953490][  T112] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
> [   10.961104][    T1] Key type encrypted registered
> [   10.968486][    T1] rtc-mv f1010300.rtc: setting system clock to 2020-05-27T16:06:03 UTC (1590595563)
> [   11.023454][  T112] ata1.00: ATA-8: WDC WD3200BPVT-80ZEST0, 01.01A01, max UDMA/133
> [   11.031070][  T112] ata1.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32)
> [   11.045312][  T112] ata1.00: configured for UDMA/133
> [   11.060807][    T7] scsi 0:0:0:0: Direct-Access     ATA      WDC WD3200BPVT-8 1A01 PQ: 0 ANSI: 5
> [   11.070681][  T116] sd 0:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
> [   11.079419][  T116] sd 0:0:0:0: [sda] 4096-byte physical blocks
> [   11.085531][  T116] sd 0:0:0:0: [sda] Write Protect is off
> [   11.091172][  T116] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [   11.153157][  T116]  sda: sda1 sda2 sda3
> [   11.159092][  T116] sd 0:0:0:0: [sda] Attached SCSI disk
> [   11.414861][  T114] ata2: SATA link down (SStatus 0 SControl F300)
> [   14.042809][    C0] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
> [   14.093389][    T1] IP-Config: Guessing netmask 255.255.255.0
> [   14.099162][    T1] IP-Config: Complete:
> [   14.103109][    T1]      device=eth0, hwaddr=00:d0:b8:14:41:12, ipaddr=192.168.0.90, mask=255.255.255.0, gw=255.255.255.255
> [   14.114307][    T1]      host=DB88FXX81, domain=, nis-domain=(none)
> [   14.120607][    T1]      bootserver=192.168.0.1, rootserver=192.168.0.1, rootpath=
> [   14.132209][    T1] Freeing unused kernel memory: 1024K
> [   14.153917][    T1] Checked W+X mappings: passed, no W+X pages found
> [   14.160308][    T1] Run /init as init process
> Loading, please wait...
> Starting version 241
> Begin: Loading essential drivers ... done.
> Begin: Running /scripts/init-premount ... done.
> Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
> Begin: Running /scripts/local-premount ... done.
> Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> done.
> Gave up waiting for root file system device.  Common problems:
>  - Boot args (cat /proc/cmdline)
>    - Check rootdelay= (did the system wait long enough?)
>  - Missing modules (cat /proc/modules; ls /dev)
> ALERT!  /dev/mtdblock0 does not exist.  Dropping to a shell!
> 
> 
> BusyBox v1.30.1 (Debian 1:1.30.1-4) built-in shell (ash)
> Enter 'help' for a list of built-in commands.
> 
> (initramfs)

I will be very happy if someone can help me with this case. I can organize quick sharing session on skype, can even give the control to get this hardware working with the new kernel.

dferrg , Any ideas ? clues ?

@dferrg
Copy link

dferrg commented May 27, 2020

Looks like your kernel couldn't find a valid rootfs. Is your rootfs in /dev/sda2? if it is, please try mounting it and chrooting.

#check your partition table 
lsblk

#mount root fs
mkdir /mnt
mount -t ext4 -o remount,rw /dev/sda2 /mnt

#chroot
chroot /mnt

if it works, check your fstab

#inside chroot
cat /etc/fstab

@koczaj
Copy link

koczaj commented May 27, 2020

Bingo !!
I entered again:

setenv bootargs 'root=/dev/sda2 init=/bin/systemd fsck.mode=force fsck.repair=yes console=ttyS0,115200

and it started!


> root@debian:~# uname -a
> Linux debian 5.2.9-kirkwood-tld-1 #1 PREEMPT Sat Aug 17 15:00:56 PDT 2019 armv5tel GNU/Linux

@dferrg
Copy link

dferrg commented May 27, 2020

nice :)
when you have time, please update your guide on https://gist.github.com/koczaj/a20ed52c969a8d0612986ca576067876

@koczaj
Copy link

koczaj commented May 27, 2020

definitely!

@yulonglong
Copy link

yulonglong commented Jul 19, 2020

@braian87b, a very big thank you! your instructions work perfectly (for 4.12) and my device is up and running now! I almost threw it into the garbage bin because i was very frustrated with the original firmware and interface.

super minor suggestions (for a noob like me, first time using USB to Serial TTL):

  1. Mention how to find the device path. e.g., dmesg | grep tty and then I found out it's /dev/ttyUSB0
  2. Mention how to actually run commands or "ssh" via the serial cable, e.g., screen /dev/ttyUSB0 115200

Other than that, it's perfect...

Thank you once again,
a stranger

@xickwy
Copy link

xickwy commented Nov 7, 2020

To avoid the boot-fault of missing drive, replace /dev/sda2 to root=LABEL=rootfs

I'm booting it with a usb and works well. But changing the boot orders.

bootargs=root=LABEL=rootfs init=/bin/systemd fsck.mode=force fsck.repair=yes console=ttyS0,115200 mtdparts=spi_flash:0x7e000@0(u-boot),0x1000@0x7f000(env),0x1000@0x7e000(env2)
bootcmd=usb start; usb read 0x40000 0x5000 0x2b00; usb read 0x2100000 0xA000 0x4000; bootm 0x40000 0x2100000

@haastecnologia
Copy link

Good afternoon.

My Iomega HM EZ worked correctly after following the instructions presented here.
Now that I have Debian installed on the NAS and getting started I would like to know how do I manage the sharing of the Storage Unit. Is there a web application or some easy way to access it? Wait.

@koczaj
Copy link

koczaj commented Feb 2, 2021

For me samba is enough. Additionally vsftp as FTP serwer.

@dferrg
Copy link

dferrg commented Feb 2, 2021

Take a look at openmediavault also, if you need more than just samba. It's not straightforward to install on the Iomega, but it can be done with some effort.

@braian87b
Copy link
Author

happy that some of you were able to give a new life to your boxes... Please if you have additional steps to install useful features post the links to gists or github to be able to give a try... will be very grateful. Thanks!

@xickwy
Copy link

xickwy commented Feb 4, 2021

Take a look at openmediavault also, if you need more than just samba. It's not straightforward to install on the Iomega, but it can be done with some effort.

A lot of resources for a 128mb arm device. Its bestest a smb/NFS share configured by SSH. If you want a lowest use of resources, use Arch Linux. Debían 10 use 70-80mb of RAM, with systemd.. and a lot of things. With Arch only use 30-40mb. Rest are for mdadm and smb/nfs

@haastecnologia
Copy link

Muitos recursos para um dispositivo de braço de 128 MB. Seu melhor é um compartilhamento smb / NFS configurado por SSH. Se você deseja um uso mínimo de recursos, use o Arch Linux. Debían 10 usa 70-80mb de RAM, com systemd .. e um monte de coisas. Com o Arch, use apenas 30-40 MB. O resto é para mdadm e smb / nfs

Como faço para instalar o Arch Linux no IOMEGA EZ?

@xickwy
Copy link

xickwy commented Feb 4, 2021

Muitos recursos para um dispositivo de braço de 128 MB. Seu melhor é um compartilhamento smb / NFS configurado por SSH. Se você deseja um uso mínimo de recursos, use o Arch Linux. Debían 10 usa 70-80mb de RAM, com systemd .. e um monte de coisas. Com o Arch, use apenas 30-40 MB. O resto é para mdadm e smb / nfs

Como faço para instalar o Arch Linux no IOMEGA EZ?
In english, please. ;)

Use this procedure.
https://archlinuxarm.org/platforms/armv5/seagate-goflex-net

Ignore the uboot update. Only need the 11 and 12 step. Do It with a debían/Arch environment

Only need to build the kernel and initramfs and does the steps by braian. Flash into a USB Drive and use the hard disk for the rest. One step that i've practiced are create four partitions. One initramfs 10M, two kernel 32M, three systemdata 2GiB, and four userdata. When you update the kernel, create a hook with apt or Pacman and dd in the hard Drive partitions

Pd. I'm spanish, but the most helpful that i've learned are from english community

@ricoberlim
Copy link

happy that some of you were able to give a new life to your boxes... Please if you have additional steps to install useful features post the links to gists or github to be able to give a try... will be very grateful. Thanks!

Hey, thanks very much for what you have done. I just got one of these for free, but unfortunately it doesn't get an IP or anything. I'm trying to connect thru serial, but I don't know the parameters (speed, etc) to connect it.

@braian87b
Copy link
Author

@ricoberlim
the board on the box has an uBoot configuration (like the bios on a PC) and that has a string with the configuration of where to find in the disk the boot program, so probably that is the reason because is not working, you may have a corrupted boot on the drive or a drive without the boot program.
I recommend you to try with a USB-TTL cable to see if you can see there the boot process and if you can interrupt it and enter commands there. you can either use a raspberry pi to do that or a usb-ttl cable like those with chip FT232, cp2102, ch340, pl2303.
if you buy a cheap or conterfeit cable you may have to use alternative (not original) driver on windows in order to make it work or use it on linux.

@toddmax
Copy link

toddmax commented Sep 28, 2022

The links for kernels in Dropbox arent working for me. Alternate?

@koczaj
Copy link

koczaj commented Sep 28, 2022

The links for kernels in Dropbox arent working for me. Alternate?
rootfs link is working but kirkwood-tld-1-bodhi is here:
https://www.dropbox.com/s/y2rd35yqeo5o381/linux-4.12.1-kirkwood-tld-1-bodhi.tar.bz2?dl=0

@ziprasidone146939277
Copy link

I was able to follow the guide. Unfortunately I don't have a serial cable to track the boot process. The Iomega-EZ got an IP address from the network, but SSH returns refused. (BTW; what is the root default password?)

Starting Nmap 7.80 ( https://nmap.org ) at 2023-04-22 18:43 -03
Initiating ARP Ping Scan at 18:43
Scanning 192.168.1.22 [1 port]
Completed ARP Ping Scan at 18:43, 0.08s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 18:43
Completed Parallel DNS resolution of 1 host. at 18:43, 0.04s elapsed
Initiating Connect Scan at 18:43
Scanning 192.168.1.22 [1000 ports]
Completed Connect Scan at 18:43, 1.21s elapsed (1000 total ports)
Nmap scan report for 192.168.1.22
Host is up (0.21s latency).
All 1000 scanned ports on 192.168.1.22 are closed
MAC Address: 00:D0:B8:1D:1B:90 (Iomega)

Read data files from: /usr/bin/../share/nmap
Nmap done: 1 IP address (1 host up) scanned in 1.39 seconds
           Raw packets sent: 1 (28B) | Rcvd: 1 (28B)

What can I do to access the device via SSH o similar; without a USB-Serial cable? Is this possible?

Than You for this.

@ziprasidone146939277
Copy link

ziprasidone146939277 commented Apr 23, 2023

I am new and a noob on this.
After some research, is it possible to track the boot process using netcat? I tried some things like uEnv.txt and /etc/fw_env.config without success.

Thank you in advance

EDIT: I am going, meanwhile, to try to get a USB-Serial cable.

@braian87b
Copy link
Author

braian87b commented Apr 24, 2023

@ziprasidone146939277

try password root
is recommended to use the usb-ttl cable, much easier.

@koczaj
Copy link

koczaj commented Apr 24, 2023

the password was toor or root. One of them :)

@ziprasidone146939277
Copy link

Thank You, @braian87b @koczaj .
I got a USB-TTL cable. Based on what i've read on the web, this have to be connected to the NAS board at 3.3v right? But by "default" the cable delivers 5v. (is this a risk?) I have to open it (the USB-Serial adapter) and switch it to 3.3 if what I am saying is correct.

@ziprasidone146939277
Copy link

This is the adapter:

[Mon Apr 24 19:02:20 2023] usb 2-2: new full-speed USB device number 6 using xhci_hcd
[Mon Apr 24 19:02:20 2023] usb 2-2: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 4.00
[Mon Apr 24 19:02:20 2023] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[Mon Apr 24 19:02:20 2023] usb 2-2: Product: USB-Serial Controller D
[Mon Apr 24 19:02:20 2023] usb 2-2: Manufacturer: Prolific Technology Inc. 
[Mon Apr 24 19:02:20 2023] usbcore: registered new interface driver usbserial_generic
[Mon Apr 24 19:02:20 2023] usbserial: USB Serial support registered for generic
[Mon Apr 24 19:02:20 2023] usbcore: registered new interface driver pl2303
[Mon Apr 24 19:02:20 2023] usbserial: USB Serial support registered for pl2303
[Mon Apr 24 19:02:20 2023] pl2303 2-2:1.0: pl2303 converter detected
[Mon Apr 24 19:02:20 2023] usb 2-2: pl2303 converter now attached to ttyUSB0

@ziprasidone146939277
Copy link

I connected the adapter to NAS (without any VCC pin to the PCB), i saw a strange behavior; it seems that the NAS it not booting the correct image.

Here is a gist with the boot process: iomega_ez.out

I guess that I done something wrong, but I can realize what.

@ziprasidone146939277
Copy link

Done!

boot.out

The USB-TTL cable came failed; the pins were incorrect inside. (no TX). Once i've got TX (to interrupt boot proccess) i done:

Marvell>> setenv bootcmd 'ide read 0x40000 0x5000 0x2A00; ide read 0x2100000 0xA000 0x5000; bootm 0x40000 0x2100000'
Marvell>> saveenv 
Marvell>> setenv bootargs 'root=/dev/sda2 init=/bin/systemd fsck.mode=force fsck.repair=yes console=ttyS0,115200 
Marvell>> saveenv
Marvell>>boot

The root password is "root".

I attach a picture showing how I connected de PL2303 to NAS board.

IMG_20230424_234411464

@braian87b
Copy link
Author

@ziprasidone146939277

Correct, for TTL you should only connect TX, RX and GND, never connect VCC.

did you wrote the kernel and initramfs images to this two locations on the HD ?

root@debian8vm:~/iomegaez/# dd if=uImage of=/dev/sdb bs=1MiB seek=10
root@debian8vm:~/iomegaez/# dd if=uInitrd of=/dev/sdb bs=1MiB seek=20

or you are trying to boot using USB? for USB you need also to change the boot args. default ones won't work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment