Installation problem of Linux Kernerl 4.6 on ix4-200d

Hi all,

i'm following the procedure found in this forum "Linux Kernel 4.6 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs" but when execute this step:

"3. And install it with dpkg. Remove flash-kernel first to avoid potential problem (It is much better to generate uImage and uInitrd manually anyway):"

receive follow error:

root@storage:/boot# dpkg --instdir=/opt/ --admindir=/opt/dpkg/ -i linux-image-4.6.0-kirkwood-tld-1_1.0_armel.deb
dpkg: regarding linux-image-4.6.0-kirkwood-tld-1_1.0_armel.deb containing linux-image-4.6.0-kirkwood-tld-1, pre-dependency problem:
linux-image-4.6.0-kirkwood-tld-1 pre-depends on debconf (>= 0.2.17) | debconf-2.0
debconf-2.0 is not installed.
dpkg: error processing linux-image-4.6.0-kirkwood-tld-1_1.0_armel.deb (--install):
pre-dependency problem - not installing linux-image-4.6.0-kirkwood-tld-1
Errors were encountered while processing:
linux-image-4.6.0-kirkwood-tld-1_1.0_armel.deb

My question is, how should I install the package debconf-2.0 ?

Please help me for resolve that issue.

Regards
Francesco

Francesco,

You can not install the new kernel on top of stock OS. You will need to create a whole rootfs using

Quote

Updated 20 Feb 2016:

This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1.

Create this on a USB drive, and remember to append the DTB (4. Create uImage with embedded DTB for booting with older u-boots (2012 or earlier)) since you are booting with stock u-boot.

And then adjust your u-boot env to boot with it. If not sure how to adjust u-boot envs then at the Linux shell, get the listing of:

fw_printenv

NOTE: I've modified my previous post in the kernel thread and this post to clarify the part about embedded DTB.

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



Edited 2 time(s). Last edit at 06/12/2016 06:30PM by bodhi.

Hi bodhi,

thank a lot for your support, how can I set my u-boot env? The command fw_setenv is not present on my box.
Follow the output of fw_printenv.

root@storage:/var/cache# fw_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
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
CASset=min
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
MALLOC_len=1
ethprime=egiga0
netbsd_en=no
vxworks_en=no
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;
disaMvPnp=no
eth1addr=00:50:43:3c:3b:5e
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
enaAutoRecovery=yes
uboot_ver=v1.0.0
ethact=egiga0
bootcmd=run flash_load
uboot_start=0x0
uboot_size=0xa0000
env_start=0xa0000
env_size=0x10000
kernel_start=0xb0000
kernel_size=0x224000
initrd_start=0x2d4000
initrd_size=0x224000
flash_load=run make_boot_args;nand read 0x2000000 $(kernel_start) $(kernel_size);nand read 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
preroot_ver=0.1.5
serial_number=5560Y01001G93100021J0A1
fw_ver=46472
ethaddr=00:26:2D:06:03:2E
serialno=0KAK33000U
modelname=34550
runintime=10800
ftpserver=192.168.43.4
testfile=100M
mfgtest_state=runin_tested_ok

Thanks a lot

It is always best to connect serial console before changing u-boot envs. Or at least if you are willing to connect a serial console. There is chance of bricking the box: typos, power outage,....

If that sounds reasonable, then I will post the envs. If not then don't change u-boot envs.

In the mean time, see other who have sucessfully install new Debian rootfs:

damacc thread (thumb up to damacc's great contribution):
http://forum.doozan.com/read.php?2,22623,28113#msg-28113

Reto:
http://forum.doozan.com/read.php?3,25120,25675#msg-25675

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



Edited 1 time(s). Last edit at 06/12/2016 07:23PM by bodhi.

Hi bodhi,

ok, no problem for brick, I accept the possibility.
How can I to connect in serial console? I've JTAG but i don't found the scheme for attach JTAG.

Thanks and regards
Francesco

PS: i've posted my env

Francesco,

> How can I to connect in serial console?

See this thread about which serial module converter to get:
http://forum.doozan.com/read.php?8,13263


Let's set up USB booting with stock u-boot in 2 steps.

1. Verify that the fw_setenv works (fw_printenv and fw_setenv are actually the same binary). So do this:

a. Boot into stock, and at the stock OS $ prompt:

cd /tmp
ln -s `which fw_printenv` fw_setenv
./fw_setenv test_fw_setenv 1

b. Reboot, and when back to the stock OS $ prompt

fw_printenv test_fw_setenv

expect output

test_fw_setenv=1

2. If the test in step 1 is successful then go ahead and set up booting with USB rootfs.

cd /tmp
ln -s `which fw_printenv` fw_setenv
./fw_setenv 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'
./fw_setenv load_initrd 'ext2load usb 0:1 0x1100000 /boot/uInitrd'
./fw_setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
./fw_setenv usb_boot 'usb start; run load_uimage; run load_initrd; bootm 0x800000 0x1100000'
./fw_setenv bootcmd 'run usb_make_boot_args ; run usb_boot; run flash_load; reset'

3. You can verify the envs with

fw_printenv

At the end of the output, these new envs will be listed.

4. If all looks good, reboot

sync
shutdown -r now

or

sync
/sbin/reboot

5. Find the dynamic IP address of the box (the new Debian rootfs will get dhcp), and log in with credential root/root. And follow the rest of the instruction in the rootfs thread to generate your own ssh key, ...

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

Hi bodhi,

thanks a lot!!!

Regards
Francesco

Hi Bodhi,

during the procedure execution i get following error:

root@storage:/# cd /tmp
root@storage:/tmp# ln -s `which fw_printenv` fw_setenv
root@storage:/tmp# ./fw_setenv test_fw_setenv 1
Unlocking flash...
Done
Erasing old environment...
Done
Writing environment to /dev/mtd1...
CRC write error on /dev/mtd1: Invalid argument
Error: can't write fw_env to flash

Please help me.

Thanks and regards
Francesco

root@storage:/tmp# cat /proc/mtd
dev: size erasesize name
mtd0: 000a0000 00004000 "uboot"
mtd1: 00010000 00004000 "env"
mtd2: 00224000 00004000 "zImage"
mtd3: 00224000 00004000 "initrd"
mtd4: 02000000 00004000 "flash"

Hi Bodhi,

in serial console, after set env with the follow configuration

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
load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
usb_boot=usb start; run load_uimage; run load_initrd; bootm 0x800000 0x1100000
bootcmd=run usb_make_boot_args ; run usb_boot; reset

Environment size: 2055/16380 bytes

When execute boot, i receive following error:
Marvell>> boot
Unknown command 'usb' - try 'help'

** Block device usb 0 not supported

** Block device usb 0 not supported

finished the problem, storage bricked :(

I've execute this command :

./kwboot -t -B 115200 /dev/pts/0 -b mtd0.bin -p

and now the storage does not start and remains with led blue and the fan at max speed.

Is there any action for resolve?

Regards
Francesco

Francesco Wrote:
-------------------------------------------------------
> finished the problem, storage bricked :(
>
> I've execute this command :
>
>

> ./kwboot -t -B 115200 /dev/pts/0 -b mtd0.bin -p
>

>
> and now the storage does not start and remains
> with led blue and the fan at max speed.
>
> Is there any action for resolve?
>
> Regards
> Francesco

kwboot does not do anything to the box. Just power off and turn it back on :)

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

Keep the serial console connect, and interrupt it at the count down,

help
usb start

And post the serial console log here.

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

Hi Bodhi,

now the storage does not start and remains with display blue and the fan at max speed.
The serial console does not work.

Thanks
Francesco

Francesco Wrote:
-------------------------------------------------------
> Hi Bodhi,
>
> now the storage does not start and remains with
> display blue and the fan at max speed.
> The serial console does not work.
>
> Thanks
> Francesco

Unplug power. Wait a few minutes and plug it back in.

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

last night I'm waiting, considering that it was all night without power

Francesco,

I said above

2. If the test in step 1 is successful then go ahead and set up booting with USB rootfs.

Your step 1 was not successful. Step 2 should not have been executed.

The only advice I have now is to unplug the power, and wait a few minutes

- power up
- immediately pounding on the keyboard to interrupt serial console.
- If you see the u-boot prompt then you are OK.

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

Hi Bodhi,

you're right, i'm very stupid.

Now, i don't found any procedure for reset bios.

Please help me.

Regards
Francesco

Francesco,

No, you are just too careless :) be a very careful when messing with u-boot envs or u-boot.

To recover, starting form this post:
http://forum.doozan.com/read.php?3,25120,25668#msg-25668

Download that mtd0.bin file and run kwboot as I described in next post after that:

./kwboot -t -B 115200 /dev/ttyUSB0 -b mtd0.bin -p

If it load and runs, when you see the countdown, type any key to interrupt serial console, and printenv

printenv

You won't be able to boot right away, but you should be be able to change envs back to the original condition.

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

Hi Bodhi,

thanks a lot for your support but i think that my situation is different because when my nas start not execute any boot and the display remain blue without that appears the Iomega screen but remain blue only.
It seems as if the PC does not exceed all of the hardware test.

Today, i've deassembled this for search any jumper for CMOS reset but I found nothing.

In other words my NAS not boot, it is as if he stopped before.

Please, see the photo so that you can understand what I mean.
Bricked Iomega NAS ix4-200d

Thanks and regards
Francesco



Edited 1 time(s). Last edit at 06/14/2016 04:58PM by maframan.

Francesco Wrote:
-------------------------------------------------------
> Hi Bodhi,
>
> in serial console, after set env with the follow
> configuration
>
> usb_make_boot_args=setenv bootargs
> console=ttyS0,115200
> mtdparts=orion_nand:$(uboot_size)@$(uboot_start)(u
> boot),$(env_size)@$(env_start)(env),$(kernel_size)
> @$(kernel_start)(zImage),$(initrd_size)@$(initrd_s
> tart)(initrd),32m@0x0(flash) root=LABEL=rootfs
> rootdelay=10
> load_initrd=ext2load usb 0:1 0x1100000
> /boot/uInitrd
> load_uimage=ext2load usb 0:1 0x800000
> /boot/uImage
> usb_boot=usb start; run load_uimage; run
> load_initrd; bootm 0x800000 0x1100000
> bootcmd=run usb_make_boot_args ; run usb_boot;
> reset
>
> Environment size: 2055/16380 bytes
>
> When execute boot, i receive following error:
> Marvell>> boot
> Unknown command 'usb' - try 'help'
>
> ** Block device usb 0 not supported
>
> ** Block device usb 0 not supported


Was the above the only thing you did, and then try

> ./kwboot -t -B 115200 /dev/pts/0 -b mtd0.bin -p

before you cannot boot and see the blue screen?

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



Edited 2 time(s). Last edit at 06/14/2016 08:01PM by bodhi.

Hi Bodhi,

how long should the command?

I've launched the command 1 hour ago and is it in execution in this mode:

root@ubuntu:/mnt/hgfs/SecureCRT# kwboot -t -B 115200 /dev/ttyUSB0 -b mtd0.bin -p

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

Thanks and regards
Francesco

Add other information found on /var/log/syslog on my ubuntu:

Jun 16 00:22:21 ubuntu kernel: [ 1481.008195] pl2303 2-2.2:1.0: pl2303_vendor_write - failed to write [0008]: -110
Jun 16 00:22:21 ubuntu kernel: [ 1481.276319] pl2303 2-2.2:1.0: pl2303_vendor_write - failed to write [0009]: -110
Jun 16 00:22:22 ubuntu kernel: [ 1482.006906] pl2303 ttyUSB0: pl2303_get_line_request - failed: -110
Jun 16 00:22:22 ubuntu kernel: [ 1482.275247] pl2303 ttyUSB0: pl2303_set_line_request - failed: -110
Jun 16 00:22:23 ubuntu kernel: [ 1483.005554] pl2303 2-2.2:1.0: pl2303_vendor_write - failed to write [0000]: -110
Jun 16 00:22:23 ubuntu kernel: [ 1483.274153] pl2303 ttyUSB0: pl2303_set_control_lines - failed: -110

Add process kwboot strace, (continuously the same info):

select(4, [3], NULL, NULL, {0, 50000})  = 0 (Timeout)
ioctl(3, TCFLSH, TCIOFLUSH)             = 0
write(3, "\273\21\"3DUfw", 8)           = 8
ioctl(3, TCSBRK, 1)                     = 0
select(4, [3], NULL, NULL, {0, 50000})  = 0 (Timeout)
ioctl(3, TCFLSH, TCIOFLUSH)             = 0
write(3, "\273\21\"3DUfw", 8)           = 8
ioctl(3, TCSBRK, 1)                     = 0
select(4, [3], NULL, NULL, {0, 50000})  = 0 (Timeout)
write(1, "\10\\", 2)                    = 2
ioctl(3, TCFLSH, TCIOFLUSH)             = 0
write(3, "\273\21\"3DUfw", 8)           = 8
ioctl(3, TCSBRK, 1)                     = 0
select(4, [3], NULL, NULL, {0, 50000})  = 0 (Timeout)
ioctl(3, TCFLSH, TCIOFLUSH)             = 0
write(3, "\273\21\"3DUfw", 8)           = 8
ioctl(3, TCSBRK, 1)                     = 0
select(4, [3], NULL, NULL, {0, 50000})  = 0 (Timeout)
ioctl(3, TCFLSH, TCIOFLUSH)             = 0
write(3, "\273\21\"3DUfw", 8)           = 8
ioctl(3, TCSBRK, 1)                     = 0
select(4, [3], NULL, NULL, {0, 50000})  = 0 (Timeout)
ioctl(3, TCFLSH, TCIOFLUSH)             = 0
write(3, "\273\21\"3DUfw", 8)           = 8
ioctl(3, TCSBRK, 1)                     = 0

maframan Wrote:
-------------------------------------------------------
> Add other information found on /var/log/syslog on
> my ubuntu:
>
>

> Jun 16 00:22:21 ubuntu kernel: [ 1481.008195]
> pl2303 2-2.2:1.0: pl2303_vendor_write - failed to
> write [0008]: -110
> Jun 16 00:22:21 ubuntu kernel: [ 1481.276319]
> pl2303 2-2.2:1.0: pl2303_vendor_write - failed to
> write [0009]: -110
> Jun 16 00:22:22 ubuntu kernel: [ 1482.006906]
> pl2303 ttyUSB0: pl2303_get_line_request - failed:
> -110
> Jun 16 00:22:22 ubuntu kernel: [ 1482.275247]
> pl2303 ttyUSB0: pl2303_set_line_request - failed:
> -110
> Jun 16 00:22:23 ubuntu kernel: [ 1483.005554]
> pl2303 2-2.2:1.0: pl2303_vendor_write - failed to
> write [0000]: -110
> Jun 16 00:22:23 ubuntu kernel: [ 1483.274153]
> pl2303 ttyUSB0: pl2303_set_control_lines - failed:
> -110
> 
>

Francesco,


Very good troubleshooting, it means your serial console has problem. Try reinstall it on your Ubuntu box, or update the driver. And try kwboot again:

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

Hi Bodhi,

is possible that my serial have problem because I run my ubuntu on VMWare?
Maybe you should try without vmware, you say?

Thanks and regards
Francesco

maframan Wrote:
-------------------------------------------------------
> Hi Bodhi,
>
> is possible that my serial have problem because I
> run my ubuntu on VMWare?
> Maybe you should try without vmware, you say?
>
> Thanks and regards
> Francesco

Yes, it's possible a VM problem. If you have a Mac then see here:
http://forum.doozan.com/read.php?3,26098,26098#msg-26098

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

Hi Bodhi,

i've received from my friend another iomega ix4-200d. In this storage is present usb command into u-boot environment.
After i've configured the parameter in this mode:

setenv 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'
setenv load_initrd 'ext2load usb 0:1 0x1100000 /boot/uInitrd'
setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
setenv usb_boot 'usb start; run load_uimage; run load_initrd; bootm 0x800000 0x1100000'
setenv bootcmd 'run usb_make_boot_args ; run usb_boot; reset'
printenv
boot

USB start correctly but the boot process stops in this mode:

Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/disk/by-label/rootfs does not exist.  Dropping to a shell!
modprobe: module i8042 not found in modules.dep
[   46.306101] uhci_hcd: USB Universal Host Controller Interface driver
[   46.322343] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[   46.339280] usbcore: registered new interface driver usbhid
[   46.345057] usbhid: USB HID core driver


BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off

This time before you do anything, I await your help :)

Thanks and regards
Francesco

PS: for repair the first box, i'm downloading an ubuntu iso for install OS in other notebook without VMWare.

Francesco,

Look at 2 possible reasons. Mount the rootfs on Ubuntu and examine it.

1. Our bootargs expects the rootfs to be labeled rootfs (lowercase).

Quote

setenv 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'

So the USB Ext3 rootfs partition must be labeled rootfs.

2. The fstab file in the rootfs has been changed to use the label. And that sometimes caused the problem with mounting

cat /etc/fstab

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/root      /               ext3    noatime,errors=remount-ro 0 1

If you see the root device was specified as LABEL=rootfs somewhere in fstab, then change it to use /dev/root like above (/dev/root is obsolete, so it is only a place holder here). fstab is really does not matter, since we use bootargs to specify the root device. But a change in initramfs introduced in Debian jessie seem to have caused some problem when fstab contains rootfs label.

If after verifiyng the 2 items above and it still not mounting rootfs, then boot up with serial console, interrupt it and
1. set the envs like you did above, and then
2. start booting

printenv
boot

Post the entire serial console log here.

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

Hi Bodhi,

i've applied first option and work fine. Now for save the boot parameter in eeprom, what should I do?

While for first box (bricked) also with the linux OS doesn't execute the u-boot installation via kwboot, the command remains in trying.

root@ubuntu:/mnt/hgfs/SecureCRT# kwboot -t -B 115200 /dev/ttyUSB0 -b mtd0.bin -p

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

The ubuntu linux syslog messages is empty and i have not found any error.

Regards
Francesco