Quantcast
Channel: Linux Device Hacking - Debian
Viewing all 26659 articles
Browse latest View live

Re: ZyXEL nas326 installation problem

$
0
0
rkachowski & kekeke,

pastebin is quite hard to read. Next time please post here in code tags. Except for the boot log, everything else is easier to troubleshoot if in code tags.

Here is rkachowski's output of fw_printenv

CASset=max
CONTRY_TYPE=FF
FEATURE_BIT=00
MALLOC_len=5
MODEL_ID=B303
MPmode=SMP
PRODUCT_NAME=STG-328
VENDOR_NAME=MitraStar Technology Corp.
autoload=no
baudrate=115200
boot_order=hd_scr usb_scr mmc_scr hd_img usb_img mmc_img pxe net_img net_scr
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=armada-nand:2m(u-boot),2m(env),2m(config),15m(kernel1),110m(rootfs1),15m(kernel2),-(rootfs2) earlyprintk=serial
bootargs_dflt=$console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel
bootargs_end=:10.4.50.254:255.255.255.0:Armada38x:eth0:none
bootargs_root=root=/dev/nfs rw
bootcmd=nand read 0x2000000 0x08700000 0xF00000 && bootz 0x2000000
bootcmd_auto=stage_boot $boot_order
bootcmd_custom=if run usb_bootcmd; then; else if run bootcmd_stock_1; then; else run bootcmd_stock_2; reset; fi; fi
bootcmd_fdt=tftpboot 0x2000000 $image_name;tftpboot $fdtaddr $fdtfile;setenv bootargs $console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x2000000 - $fdtaddr;
bootcmd_fdt_boot=tftpboot 0x2000000 $image_name; setenv bootargs $console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x2000000 - $fdtaddr;
bootcmd_fdt_edit=tftpboot $fdtaddr $fdtfile; fdt addr $fdtaddr; setenv bootcmd $bootcmd_fdt_boot
bootcmd_lgcy=tftpboot 0x2000000 $image_name; setenv bootargs $bootargs_dflt; bootm 0x2000000;
bootcmd_stock_1=run set_bootargs_stock; echo Booting from NAND kernel 1 ...; nand read 0x2000000 0x00E00000 0xF00000 && bootz 0x2000000
bootcmd_stock_2=run set_bootargs_stock; echo Booting from NAND kernel 2 ...; nand read 0x2000000 0x08700000 0xF00000 && bootz 0x2000000
bootdelay=3
cacheShare=no
console=console=ttyS0,115200
core_checksum_1=868590f39fdf3fe14e07e5824a550dd7
core_checksum_2=868590f39fdf3fe14e07e5824a550dd7
device_partition=0:1
disaMvPnp=no
eeeEnable=no
enaClockGating=no
enaCpuStream=no
enaFPU=yes
enaMonExt=no
enaWrAllo=no
eth1addr=xxxxxxx
eth1mtu=1500
eth2addr=xxxxxxx
eth2mtu=1500
eth3addr=xxxxxxx
eth3mtu=1500
ethact=egiga0
ethaddr=xxxxxxxx
ethmtu=1500
ethprime=egiga0
fdt_addr=2040000
fdt_skip_update=yes
fdtaddr=0x1000000
fdtfile=armada-38x-modular.dtb
fwversion_1=V5.20(AAZF.1)
fwversion_2=V5.20(AAZF.1)
ide_path=/
image_name=uImage
img_checksum_1=596153a55a196698e2f816f42d2dae47
img_checksum_2=596153a55a196698e2f816f42d2dae47
initrd_name=uInitrd
ipaddr=10.4.50.170
kernel_addr=${kernel_addr_1}
kernel_addr_1=0x00000000; run bootcmd_custom;
kernel_addr_2=0x08700000
kernel_addr_r=2080000
kernel_mtd_1=3
kernel_mtd_2=5
lcd0_enable=0
lcd0_params=640x480-16@60
lcd_panel=0
load_dtb_addr=0x1000000
load_image_addr=0x02000000
load_initrd_addr=0x2900000
loadaddr=0x02000000
loads_echo=0
modelid_1=B303
modelid_2=B303
mtdids=nand0=armada-nand
mtdparts=mtdparts=armada-nand:2m(u-boot),2m(env),2m(config),15m(kernel1),110m(rootfs1),15m(kernel2),-(rootfs2)
mvNetConfig=mv_net_config=4,(00:50:43:11:11:11,0:1:2:3),mtu=1500
mv_pon_addr=00:50:43:25:a6:38
nandEcc=nfcConfig=4bitecc
netbsd_en=no
netmask=255.255.255.0
netretry=no
pcieTune=no
pexMode=RC
pxe_files_load=:default.arm-armadaxp-db:default.arm-armadaxp:default.arm
pxefile_addr_r=3100000
ramdisk_addr_r=2880000
revision_1=50729
revision_2=50729
romfile_checksum_1=9D0A
romfile_checksum_2=9D0A
rootpath=/srv/nfs/
sata_delay_reset=0
sata_dma_mode=yes
script_addr_r=3000000
script_name=boot.scr
serial_number=xxxxxxxxxxxx
serverip=10.4.50.38
set_bootargs_stock=setenv bootargs "console=ttyS0,115200 ubi.mtd=4,2048 rootfstype=ubifs root=ubi0:rootfs1 rw rootdelay=2"
standalone=fsload 0x2000000 $image_name;setenv bootargs $console $nandEcc $mtdparts root=/dev/mtdblock0 rw ip=$ipaddr:$serverip$bootargs_end; bootm 0x2000000;
stderr=serial
stdin=serial
stdout=serial
sysimg_mtd_1=4
sysimg_mtd_2=6
usb0Mode=host
usbActive=0
usbType=2
usb_bootcmd=echo Booting from USB ...; setenv fdt_skip_update yes; run usb_init; ext2load usb 0:1 $load_image_addr /boot/zImage; ext2load usb 0:1 $load_dtb_addr /boot/dts/armada-380-zyxel-nas326.dtb; ext2load usb 0:1 $load_initrd_addr /boot/uInitrd; run usb_set_bootargs; bootz $load_image_addr $load_initrd_addr $load_dtb_addr
usb_init=mw.l f1018100 20420000; mw.l f1018140 003E8800; sleep 3; usb start
usb_set_bootargs=setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial"
vxworks_en=no
yuk_ethaddr=xxxxxxxxxxxxx
zld_checksum_1=845ace22f5de7ac51fbd2ed1338bd28d
zld_checksum_2=845ace22f5de7ac51fbd2ed1338bd28d
curr_bootfrom=1
next_bootfrom=1
change_boot_part=0

Re: ZyXEL nas326 installation problem

$
0
0
rkachowski,

Try one more time.

After logging int the stock OS

fw_setenv change_boot_part 1

Sync, and reboot.

-----

Note:

Your envs look fine. Nothing wrong with them. change_boot_part is reset to 0 each time the stock OS booted successfully, so it is no surprise that it is 0.

It could be that this problem has something to do with the USB rootfs itself. But we cannot see that problem without serial console to watch the kernel mounting process.

Re: ZyXEL nas326 installation problem

$
0
0
@kekeke,

> I tried to debug using netconsole
> (https://forum.doozan.com/read.php?3,14), but no
> luck either. Just empty output on nc.

Stock u-boot does not have netconsole.

@all,

Serial console is absolutely necessary when you start hacking these embedded Linux boxes. Serial console is not just for trouble shooting purpose, it's also a tool for learning Linux, because you can see how Linux boots, info that you cannot see without it.

If you plan to change your configuration often (or later adding RAID ...), I'd suggest getting a serial convert. It's the best tool for under 5 USD. This NAS326 serial header is already installed by the manufacturer, you will only need to plug in the correct pins.

See the Wiki thread:
https://forum.doozan.com/read.php?2,23630

Quote

Serial Console & JTAG console

Repair Pogo E02 with Raspberry PI (JTAG) and OpenOCD
Serial Port connector - what are people using to make it work
Serial Console hookup - GoFlex Net (external link)
Serial Console hookup - Pogoplug E02 and Pogoplug Pro V3 (external link)
OSX Serial/Net Console
Use Phone Jack - Phone Jack Serial Console Pics
Adding serial connector to Pogoplug Mobile (external link)
WD Mycloud EX2100/4100 Serial Console pic1, also pic2, pic3
Dreamplug Serial Console

Re: ZyXEL nas326 installation problem

$
0
0
sorry about the paste bin, I was just concerned about noise in the thread. I've retried the commands as above with no success. I'll also find a new usb drive to see if that works, but the next step will be a serial console setup.

(it turns out I have an ftdi TTL 232r v5 cable lying around, is this suitable? I considered it before but I'm not sure about the voltages / which pins to connect.)

Re: ZyXEL nas326 installation problem

$
0
0
NAS326 serial console

Connect only GND, RX, TX (dont connect 3.3V power).


          +----+----+
          |    |    |
+----+----+----+----+----+
|3.3V| TX | RX |    | GND|
+----+----+----+    +----+

Re: ZyXEL nas326 installation problem

Re: ZyXEL nas326 installation problem

$
0
0
I've got usb-to-ttl (https://ru.aliexpress.com/store/product/CP2102-USB-2-0-to-UART-TTL-5PIN-Connector-Module-Serial-Converter-New/343255_32695520129.html), attached it like GND-GND, RX-TX, TX-RX and didn't see any output. I tried to change to rx-rx, tx-tx and got same results. I tried on mac,win,linux (using kwboot, putty, picocom, screen), tried different laptop, but everything is useless.

P.S. When I'm removing jumper that stated as tx on your schema systems continues to boot normally.

I have no ideas what else should I try...

P.P.S Thank you for your help!

Re: ZyXEL nas326 installation problem

$
0
0
kekeke.

Quote

> see any output. I tried to change to rx-rx, tx-tx
> and got same results. I tried on mac,win,linux
> (using kwboot, putty, picocom, screen), tried
> different laptop, but everything is useless.
>
> P.S. When I'm removing jumper that stated as tx on
> your schema systems continues to boot normally.
>

It is expected. NAS326 box behaves this way. This quirk about serial console is not typical for all boxes, just this one.


Look back to the installation instruction:


Quote

Zyxel NAS326 Installation

Updated 25 Mar 2017 (added Section C - Installation for SATA rootfs, no serial console)
Updated 18 Feb 2017 (added Section B - Installation for USB rootfs, no serial console)
Updated 05 Feb 2017 (Section A - Installation for USB rootfs, with serial console)


Installation for NAS326 box can be done with serial console connected (section A), or inside stock OS and without serial console (section B for USB rootfs, section C for SATA rootfs). Note: for section A and B, the USB rootfs must be inserted to the front USB port (USB 2.0).

.....
.....


A3. Normal Operation

The USB rootfs should be plugged in permanently, and the serial console module should be removed.

1. Whenever the NAS326 is rebooted or cold started, to boot without manual intervention, the serial console module must be unplugged from the NAS326. If the serial console module is plugged in, then step 1 in the installation instruction A2 must be executed (so that the NAS326 will continue booting when it detected the serial console present).


Quote

A2. Installation

Warning: Step 4 in the instruction in this section uses a "env/code injection" to replace the Zyxel NAS326 stock u-boot bootcmd with a different command during boot. It's a simple trick that change u-boot env bootcmd (it does not touch u-boot binary in NAND). However, this hack should not be used on a different MVEBU box (any box other than the NAS326). Doing this without examining your box's stock u-boot source code could likely messing up your u-boot envs and prevent booting, or in the worse case bricking it. Please post questions regarding installation for other MVEBU boxes, it might be possible to do this.

1. Start kwboot on the serial console host

For ARM32 kwboot:
./kwboot -t -B 115200 /dev/ttyUSB0 -d

For x86-64 kwboot:
./kwboot -t -B 115200 /dev/ttyUSB0


So the short explanation: NAS326 senses the presence of a serial console being attached, and will not boot wihout proper trigger. The kwboot command above sends a debug message to "trigger" that (a long technical explanation obmitted here).

Re: ZyXEL nas326 installation problem

$
0
0
Finally, I got it to work. I read it (instructions), but it was unclear without context (especially in part about the platform. I thought that it's about the host, not the target).

This comment helped me a lot (https://forum.doozan.com/read.php?2,27108,31735#msg-31735).

Maybe it worth to mention this issue in instructions? Just everyone could be prepared that this is a typical situation (if I'm not alone who stuck with this).

So what I studied during my experiments:
1. It's better to reboot and not a cold start. (End even when rebooting I often needed to replug Tx on a board).
2. I have cp2102, but Rx should be connected to Tx (I saw posts on here that for this chip it should be connected Tx-Tx, Rx-Rx).
3. It's necessary to use kwboot with '-d' key (I thought that this is one of the options).

Anyway, huge thanks @bodhi

Re: ZyXEL nas326 installation problem

$
0
0
Returning to the initial issue with booting from HDD. Now I have a boot log:

�}�M���KKKK�--OKKK�����DDR3 Training Sequence - Switching XBAR Window to FastPath Window
DDR3 Training Sequence - Ended Successfully
Not detected suspend to RAM indication
 0

NAND read: device 0 whole chip
Attempt to read outside the flash area
 0 bytes read: ERROR
Booting from SATA ...
AHCI init for unit0
Target spinup took 0 ms.
SATA link 1 timeout.

Error: SCSI Controller(s) 1B4B:9215 1B4B:9235 not found
scanning bus for devices...

And printenv:

CASset=max
CONTRY_TYPE=FF
FEATURE_BIT=00
MALLOC_len=5
MODEL_ID=B303
MPmode=SMP
PRODUCT_NAME=STG-328
VENDOR_NAME=MitraStar Technology Corp.
autoload=no
baudrate=115200
boot_order=hd_scr usb_scr mmc_scr hd_img usb_img mmc_img pxe net_img net_scr
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=armada-nand:2m(u-boot),2m(env),2m(config),15m(kernel1),110m(rootfs1),15m(kernel2),-(rootfs2) earlyprintk=serial
bootargs_dflt=$console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel
bootargs_end=:10.4.50.254:255.255.255.0:Armada38x:eth0:none
bootargs_root=root=/dev/nfs rw
bootcmd=nand read 0x2000000 0x00000000; run bootcmd_custom;  0xF00000 && bootz 0x2000000
bootcmd_auto=stage_boot $boot_order
bootcmd_custom=run bootcmd_custom_sata
bootcmd_custom_sata=if run sata_bootcmd; then; else if run bootcmd_stock_1; then; else run bootcmd_stock_2; reset; fi; fi
bootcmd_fdt=tftpboot 0x2000000 $image_name;tftpboot $fdtaddr $fdtfile;setenv bootargs $console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x2000000 - $fdtaddr;
bootcmd_fdt_boot=tftpboot 0x2000000 $image_name; setenv bootargs $console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x2000000 - $fdtaddr;
bootcmd_fdt_edit=tftpboot $fdtaddr $fdtfile; fdt addr $fdtaddr; setenv bootcmd $bootcmd_fdt_boot
bootcmd_lgcy=tftpboot 0x2000000 $image_name; setenv bootargs $bootargs_dflt; bootm 0x2000000;
bootcmd_stock_1=run set_bootargs_stock; echo Booting from NAND kernel 1 ...; nand read 0x2000000 0x00E00000 0xF00000 && bootz 0x2000000
bootcmd_stock_2=run set_bootargs_stock; echo Booting from NAND kernel 2 ...; nand read 0x2000000 0x08700000 0xF00000 && bootz 0x2000000
bootdelay=20
cacheShare=no
change_boot_part=1
console=console=ttyS0,115200
core_checksum_1=868590f39fdf3fe14e07e5824a550dd7
core_checksum_2=2773b03df8b32c243f8b84dcefa79efb
curr_bootfrom=1
device_partition=0:1
disaMvPnp=no
eeeEnable=no
enaClockGating=no
enaCpuStream=no
enaFPU=yes
enaMonExt=no
enaWrAllo=no
eth1addr=00:50:43:38:32:25
eth1mtu=1500
eth2addr=00:50:43:38:a6:25
eth2mtu=1500
eth3addr=00:50:43:32:a6:38
eth3mtu=1500
ethact=egiga0
ethaddr=B8:EC:A3:7F:D9:46
ethmtu=1500
ethprime=egiga0
fdt_addr=2040000
fdt_skip_update=yes
fdtaddr=0x1000000
fdtfile=armada-38x-modular.dtb
fwversion_1=V5.20(AAZF.1)
fwversion_2=V5.21(AAZF.1)
ide_path=/
image_name=uImage
img_checksum_1=596153a55a196698e2f816f42d2dae47
img_checksum_2=5356a1c083dfd6bc8c74bfd231aa15a6
initrd_name=uInitrd
ipaddr=10.4.50.170
kernel_addr=${kernel_addr_1}
kernel_addr_1=0x00000000; run bootcmd_custom;
kernel_addr_2=0x08700000
kernel_addr_r=2080000
kernel_mtd_1=3
kernel_mtd_2=5
lcd0_enable=0
lcd0_params=640x480-16@60
lcd_panel=0
load_dtb_addr=0x1000000
load_image_addr=0x02000000
load_initrd_addr=0x2900000
loadaddr=0x02000000
loads_echo=0
modelid_1=B303
modelid_2=B303
mtdids=nand0=armada-nand
mtdparts=mtdparts=armada-nand:2m(u-boot),2m(env),2m(config),15m(kernel1),110m(rootfs1),15m(kernel2),-(rootfs2)
mvNetConfig=mv_net_config=4,(00:50:43:11:11:11,0:1:2:3),mtu=1500
mv_pon_addr=00:50:43:25:a6:38
nandEcc=nfcConfig=4bitecc
netbsd_en=no
netmask=255.255.255.0
netretry=no
next_bootfrom=1
pcieTune=no
pexMode=RC
pxe_files_load=:default.arm-armadaxp-db:default.arm-armadaxp:default.arm
pxefile_addr_r=3100000
ramdisk_addr_r=2880000
revision_1=50729
revision_2=50984
romfile_checksum_1=9D0A
romfile_checksum_2=A762
rootpath=/srv/nfs/
sata_bootcmd=echo Booting from SATA ...; setenv fdt_skip_update yes; run sata_init; ext2load scsi 0:1 $load_image_addr /boot/zImage; ext2load scsi 0:1 $load_dtb_addr /boot/dts/armada-380-zyxel-nas326.dtb; ext2load scsi 0:1 $load_initrd_addr /boot/uInitrd; run sata_set_bootargs; bootz $load_image_addr $load_initrd_addr $load_dtb_addr
sata_delay_reset=0
sata_dma_mode=yes
sata_init=mw.l f1018100 20420000; mw.l f1018140 003ca800; sleep 3; scsi init
sata_set_bootargs=setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial"
script_addr_r=3000000
script_name=boot.scr
serial_number=
serverip=10.4.50.38
set_bootargs_stock=setenv bootargs "console=ttyS0,115200 ubi.mtd=4,2048 rootfstype=ubifs root=ubi0:rootfs1 rw rootdelay=2"
standalone=fsload 0x2000000 $image_name;setenv bootargs $console $nandEcc $mtdparts root=/dev/mtdblock0 rw ip=$ipaddr:$serverip$bootargs_end; bootm 0x2000000;
stderr=serial
stdin=serial
stdout=serial
sysimg_mtd_1=4
sysimg_mtd_2=6
usb0Mode=host
usbActive=0
usbType=2
usb_bootcmd=echo Booting from USB ...; setenv fdt_skip_update yes; run usb_init; ext2load usb 0:1 $load_image_addr /boot/zImage; ext2load usb 0:1 $load_dtb_addr /boot/dts/armada-380-zyxel-nas326.dtb; ext2load usb 0:1 $load_initrd_addr /boot/uInitrd; run usb_set_bootargs; bootz $load_image_addr $load_initrd_addr $load_dtb_addr
usb_init=mw.l f1018100 20420000; mw.l f1018140 003E8800; sleep 3; usb start
usb_set_bootargs=setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial"
vxworks_en=no
yuk_ethaddr=00:00:00:EE:51:81
zld_checksum_1=845ace22f5de7ac51fbd2ed1338bd28d
zld_checksum_2=102d2dc16f397df0dddc4f1ad6380e52

Environment size: 5763/524284 bytes

Re: LG N1T1 NAS

$
0
0
I have a LG N1D1DD1 and have tried this. I did come quite far, but I am stuck at a read only problem and I don't know how to proceed. I tried some chown and chmod on the USB flash disk like in https://ubuntuforums.org/showthread.php?t=1448092 but it don't help.

What I have done so far is this.

I read
Ron's mini howto: http://forum.doozan.com/read.php?2,26671,30371#msg-30371
bernd's additions: http://forum.doozan.com/read.php?2,26671,30643#msg-30643

I should use Bodhi's latest kernel from: http://forum.doozan.com/read.php?2,12096,12096#msg-12096

So I did this:
1. I format a 8GB USB drive as ext3. I use Ubuntu and I opened Disks as normal user (gnome-disk-utility 3.18.3.1, UDisks 2.1.7 (built against 2.1.6)).
Plugged in the USB drive
Unmounted the USB drive in Disks.
Selected Format Partition...
Selected
> Erase: Don't overwrite existing data (Quick)
> Type: Custom (Enter filesystems type)
> Name:
> Filesystem: ext3
Clicked Format...
And then as last step in Disks, I mounted the USB drive

2. I make a directory where I can work
cd ~
mkdir stuff

3. I download linux-4.13.5-kirkwood-tld-1-bodhi.tar.bz2 to ~/stuff from https://forum.doozan.com/read.php?2,12096,12096#msg-12096
cd ~/stuff
wget https://bitly.com/2yTkIaH
mv 2yTkIaH linux-4.13.5-kirkwood-tld-1-bodhi.tar.bz2

4. I download Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 ~/stuff from https://forum.doozan.com/read.php?2,12096,12096#msg-12096
cd ~/stuff
wget https://bitly.com/2gW5oGg
mv 2gW5oGg Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2

5. On a Linux PC I go to the USB drive and extract the rootfs into it
cd /media/superuser/87dbfdc8-b51a-4ff2-9e04-000edc8e08f3
tar -xf ~/stuff/Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2

It extract a lot of files, but ends with
tar: ./dev/mem: Cannot mknod: Operation not permitted
tar: ./dev/loop4: Cannot mknod: Operation not permitted
tar: ./dev/port: Cannot mknod: Operation not permitted
tar: ./dev/loop1: Cannot mknod: Operation not permitted
tar: ./dev/ram8: Cannot mknod: Operation not permitted
tar: ./dev/ram11: Cannot mknod: Operation not permitted
tar: ./dev/ram16: Cannot mknod: Operation not permitted
tar: ./dev/ram1: Cannot mknod: Operation not permitted
tar: ./dev/ram14: Cannot mknod: Operation not permitted
tar: ./dev/tty: Cannot mknod: Operation not permitted
tar: ./dev/kmem: Cannot mknod: Operation not permitted
tar: ./dev/ram0: Cannot mknod: Operation not permitted
tar: ./dev/ram2: Cannot mknod: Operation not permitted
tar: ./dev/loop6: Cannot mknod: Operation not permitted
tar: ./dev/ram13: Cannot mknod: Operation not permitted
tar: ./dev/zero: Cannot mknod: Operation not permitted
tar: ./dev/ram6: Cannot mknod: Operation not permitted
tar: ./dev/ram15: Cannot mknod: Operation not permitted
tar: ./dev/loop7: Cannot mknod: Operation not permitted
tar: ./dev/tty0: Cannot mknod: Operation not permitted
tar: ./dev/loop5: Cannot mknod: Operation not permitted
tar: ./dev/loop3: Cannot mknod: Operation not permitted
tar: ./dev/urandom: Cannot mknod: Operation not permitted
tar: ./dev/ram10: Cannot mknod: Operation not permitted
tar: ./dev/console: Cannot mknod: Operation not permitted
tar: ./dev/ram12: Cannot mknod: Operation not permitted
tar: ./dev/random: Cannot mknod: Operation not permitted
tar: ./dev/loop2: Cannot mknod: Operation not permitted
tar: ./dev/full: Cannot mknod: Operation not permitted
tar: ./dev/ptmx: Cannot mknod: Operation not permitted
tar: ./dev/ram7: Cannot mknod: Operation not permitted
tar: ./dev/null: Cannot mknod: Operation not permitted
tar: ./dev/ram5: Cannot mknod: Operation not permitted
tar: ./dev/ram9: Cannot mknod: Operation not permitted
tar: ./dev/ram3: Cannot mknod: Operation not permitted
tar: ./dev/loop0: Cannot mknod: Operation not permitted
tar: ./dev/ram4: Cannot mknod: Operation not permitted
tar: Exiting with failure status due to previous errors

I wait until it has finished writing data to USB flash disk before unplugging it. It take some time...

6. The mini howto say I should now replace uImage, So I download https://drive.google.com/file/d/0B-uU4xdcKTB6dUFEeXFwdFVYWU0/view?usp=sharing with Firefox and then
cd ~/stuff
mv ../Downloads/uImage .

7. Copy uImage to USB
cd ~/stuff
mv /media/interndata/87dbfdc8-b51a-4ff2-9e04-000edc8e08f3/boot/uImage uImageOLD
cp uImage /media/interndata/87dbfdc8-b51a-4ff2-9e04-000edc8e08f3/boot/

8. I unmount the USB drive in Ubuntu

9. I plug in the USB drive in the LG N1D1DD1

10. On LG. With my gtkterm I try USB start
LGE-NAS>> usb start
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found

11. On LG. Then I try ext2load usb 0:1 0x800000 /boot/uImage
LGE-NAS>> ext2load usb 0:1 0x800000 /boot/uImage
....
..............
3326598 bytes read

12. On LG. I set variables
setenv console console=ttyS0,115200 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env)
setenv bootargs_usb root=/dev/sda1 rw rootdelay=10 rootfstype=ext3
setenv bootargs $(console) $(bootargs_usb)

13. On LG. I try to boot the kernel
bootm 0x800000

14. After som stuff it says
[....] File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file [FAILm manually. ... failed!
[....] A maintenance shell will now be started. CONTROL-D will ter[warne this shell and resume system boot. ... (warning).
Give root password for maintenance
(or press Control-D to continue):

I try Ctrl-D

15. On LG. I got some kind of DHCP loop with write error, I stopped it with plugging out network cable and then replugging it. It then looks something like this
...
...
DHCPDECLINE on eth0 to 255.255.255.255 port 67
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPREQUEST of 192.168.0.68 on eth0 to 255.255.255.255 port 67
DHCPOFFER of 192.168.0.68 from 192.168.0.1
DHCPACK of 192.168.0.68 from 192.168.0.1
RTNETLINK answers: File exists
DHCPDECLINE on eth0 to 255.255.255.255 port 67
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPREQUEST of 192.168.0.69 on eth0 to 255.255.255.255 port 67
DHCPOFFER of 192.168.0.69 from 192.168.0.1
DHCPACK of 192.168.0.69 from 192.168.0.1
RTNETLINK answers: File exists
DHCPDECLINE on eth0 to 255.255.255.255 port 67
I disconnect cable, wait a little and then connect again
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.
[ ok ] Starting RPC port mapper daemon: rpcbind.
[ ok ] Starting NFS common utilities: statd idmapd.
[ ok ] Cleaning up temporary files....
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
/etc/init.d/bootlogs: 23: /etc/init.d/bootlogs: cannot create /var/log/dmesg: Read-only file system
chgrp: cannot access '/var/log/dmesg': No such file or directory
[....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd...
4812 (syslogd)
. ok
[ ok ] Starting NFS common utilities: statd idmapd.
[ ok ] Starting system message bus: dbus.
[ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
[warn] Not starting NFS kernel daemon: no exports. ... (warning).
[ ok ] Starting NTP server: ntpd.
[....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd...
4810 (klogd)
. ok
[ ok ] Starting OpenBSD Secure Shell server: sshd.
[ ok ] Running local boot scripts (/etc/rc.local).

Debian GNU/Linux 9 debian ttyS0

debian login:

So, I finally get
debian login:

16. On LG. I try to login with root/root and I get
debian login: root
Password:
Linux debian 4.4.0-n1t1-tld-1 #1 PREEMPT Tue Mar 15 14:10:10 CET 2016 armv5tel

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.

17. On LG. I start with checking my IP number with ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet 192.168.0.77  netmask 255.255.255.0  broadcast 192.168.0.255

18. Now I should upgrade the kernel to latest and ditch the custom uImage... Copy the kernel archive to the NAS. Ron used SCP to put it in /root, so I check https://kb.iu.edu/d/agye. One example is
scp ~/rebels.txt dvader@deathstar.com:~/revenge
Maybe I will try
scp ~/stuff/linux-4.13.5-kirkwood-tld-1-bodhi.tar.bz2 root@192.168.0.77:/root

19. On Ubuntu. I download the kernel again
wget https://bitly.com/2yTkIaH
mv 2yTkIaH linux-4.13.5-kirkwood-tld-1-bodhi.tar.bz2

20. On Ubuntu I try to copy the kernel to LG
scp ~/stuff/linux-4.13.5-kirkwood-tld-1-bodhi.tar.bz2 root@192.168.0.77:/root

But I get
cp: /root/linux-4.13.5-kirkwood-tld-1-bodhi.tar.bz2: Read-only file system

On LG. I check with ls
root@debian:~# ls / -la
total 64
drwxr-xr-x 21 1000 1000 4096 Feb 16  2015 .
drwxr-xr-x 21 1000 1000 4096 Feb 16  2015 ..
drwxr-xr-x  2 1000 1000 4096 Jul 23 17:12 bin
drwxr-xr-x  3 1000 1000 4096 Dec 31  1969 boot
drwxr-xr-x  9 root root 2260 Dec 31  1999 dev
drwxr-xr-x 57 1000 1000 4096 Dec 31  1969 etc
drwxr-xr-x  2 1000 1000 4096 Jan 22  2012 home
drwxr-xr-x 14 1000 1000 4096 Jul 20 01:55 lib
drwx------  2 1000 1000 4096 Feb 24  2012 lost+found
drwxr-xr-x  2 1000 1000 4096 Feb 24  2012 media
drwxr-xr-x  2 1000 1000 4096 Feb 10  2015 mnt
drwxr-xr-x  2 1000 1000 4096 Feb 24  2012 opt
dr-xr-xr-x 65 root root    0 Dec 31  1969 proc
drwx------  5 1000 1000 4096 Jul 23 18:49 root
drwxr-xr-x 14 root root  560 Nov 15 10:54 run
drwxr-xr-x  2 1000 1000 4096 Jul 23 17:12 sbin
drwxr-xr-x  2 1000 1000 4096 Feb 24  2012 srv
dr-xr-xr-x 12 root root    0 Dec 31  1999 sys
drwxrwxrwt  2 root root   40 Dec 31  1999 tmp
drwxr-xr-x 10 1000 1000 4096 Feb 24  2012 usr
drwxr-xr-x 11 1000 1000 4096 Dec 31  1969 var
root@debian:~# ls /root/ -la
total 32
drwx------  5 1000 1000 4096 Jul 23 18:49 .
drwxr-xr-x 21 1000 1000 4096 Feb 16  2015 ..
-rw-------  1 1000 1000   49 Jul 23 18:51 .bash_history
-rw-r--r--  1 1000 1000  570 Jan 31  2010 .bashrc
drwx------  3 1000 1000 4096 Jun 14  2013 .config
drwxr-xr-x  2 1000 1000 4096 Jul 23 17:53 .nano
-rw-r--r--  1 1000 1000  481 Jul 20 02:15 .profile
drwx------  2 1000 1000 4096 Jul 23 18:30 .ssh
root@debian:~#
Maybe I am just tired, but I feel I am out of ideas. Where should I start to continue?

EDIT
Now I read in https://forum.doozan.com/read.php?2,12096 that "Note: all steps below must be done while logging in as root user (not sudo). If you are not the root user then don't continue, because the rootfs will not work.". This I have not done when I worked on Ubuntu. Could that be the problem?

Re: LG N1T1 NAS

$
0
0
raffe,

> Now I read in
> https://forum.doozan.com/read.php?2,12096 that
> "Note: all steps below must be done while logging
> in as root user (not sudo). If you are not the
> root user then don't continue, because the rootfs
> will not work.". This I have not done when I
> worked on Ubuntu. Could that be the problem?

Yes, there will be quite many problems with permission if you are not root when tarring the rootfs.

Re: Possible to get Debian on a Medion NAS P89654 2x4 TB?

$
0
0
use a different type of usb stick. some work some dont.
good luck!

Re: ZyXEL nas326 installation problem

$
0
0
kekeke,

> Booting from SATA ...
> AHCI init for unit0
> Target spinup took 0 ms.
> SATA link 1 timeout.
>
> Error: SCSI Controller(s) 1B4B:9215 1B4B:9235 not
> found
> scanning bus for devices...
> [/code]
>

Did it hang here?

Re: ZyXEL nas326 installation problem

$
0
0
Yes, I waited for around 2 minutes.

Re: ZyXEL nas326 installation problem

$
0
0
kekeke,

Please post the entire bootlog, from u-boot banner until it stopped (a snippet of log is never helpful!).

Re: LG N1T1 NAS

$
0
0
OK, almost there, but near the goal... nothing. What I have done this time

I have a LG N1D1DD1

I read
Ron's mini howto: http://forum.doozan.com/read.php?2,26671,30371#msg-30371
bernd's additions: http://forum.doozan.com/read.php?2,26671,30643#msg-30643

I should use Bodhi's latest kernel from: http://forum.doozan.com/read.php?2,12096,12096#msg-12096

So I did this:
I soldered cables as in the picture in this post: https://forum.doozan.com/read.php?2,26671,30316#msg-30316

I could use a CP2102 or a PL-2303 or a FT232 USB to serial adapter, but in the end I bought the little more expensive FT232I (~$10) as I could get it directly (this one https://www.kjell.com/no/produkter/elektro-og-verktoy/arduino/moduler/luxorparts-usb-til-seriell-adapter-for-arduino-p90738 ).

========================
=== PART 1 on Ubuntu ===
========================

0. I format a 8 GB USB drive as ext3. I use Ubuntu and I opened Disks as normal user (gnome-disk-utility 3.18.3.1, UDisks 2.1.7 (built against 2.1.6)).
Plugged in the USB drive
Unmounted the USB drive in Disks.
Selected Format Partition...
Selected
> Erase: Don't overwrite existing data (Quick)
> Type: Custom (Enter filesystems type)
> Name: rootfs
> Filesystem: ext3
Clicked Format...
And then as last step in Disks, I mounted the USB drive

1. I read in https://forum.doozan.com/read.php?2,12096 that say
"Note: all steps below must be done while logging in as root user (not sudo). If you are not the root user then don't continue, because the rootfs will not work."

I read https://askubuntu.com/questions/44418/how-to-enable-root-login and on my Ubuntu I do this
sudo passwd root
sudo passwd -u root

(I am not doing pkexec users-admin yet, I will first try if sudo -i works)...

Then I start a terminal as root, this is the terminal I use below, e.g. I start a terminal and write
sudo -i


2. I make a directory where I can work
cd ~
mkdir stuff


3. I download linux-4.13.5-kirkwood-tld-1-bodhi.tar.bz2 to ~/stuff from https://forum.doozan.com/read.php?2,12096,12096#msg-12096
cd ~/stuff
wget https://bitly.com/2yTkIaH
mv 2yTkIaH linux-4.13.5-kirkwood-tld-1-bodhi.tar.bz2


4. I download Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 from https://forum.doozan.com/read.php?2,12096,12096#msg-12096
cd ~/stuff
wget https://bitly.com/2gW5oGg
mv 2gW5oGg Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2


5. On a Linux PC I go to the USB drive and extract the rootfs into it
cd /media/superuser/rootfs
tar -xjf ~/stuff/Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2


It extract a lot of files, and it takes some time...

6. The mini howto say I should now replace uImage, So I download https://drive.google.com/file/d/0B-uU4xdcKTB6dUFEeXFwdFVYWU0/view?usp=sharing with Firefox and then
cd ~/stuff
mv ../Downloads/uImage .


7. Copy uImage to USB
cd ~/stuff
mv /media/superuser/rootfs/boot/uImage uImageOLD
cp uImage /media/superuser/rootfs/boot/


8. I unmount the USB drive in Ubuntu and remove it.

====================
=== PART 2 on LG ===
====================

9. I plug in the rootfs USB drive in the LG N1D1DD1.
I also connect the FT232 USB/serial adapter between the Ubuntu computer and the LG NAS.

10. I start GtkTerm as root, e.g. start a terminal and in it write
sudo -i
gtkterm


11. I set up my GtkTerm. I click the menu items Configuration - Port and there I choose
> Port: /dev/ttyUSB0
> Baud Rate: 115200
And click OK

12. I do as Ron writes
"Apply power to the NAS and press the red power button on the back of the device. Meanwhile repeatedly hit a button on your keyboard, so the u-boot autostarting can be disabled. If you see the kernel boot messages, the stock OS has started booting, so you need to unplug the power (or shut down via the web UI) and repeat this step until you can access the u-boot command line."

I get access to the u-boot command line.

13. On LG. With my gtkterm I try USB start
LGE-NAS>> usb start
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found


14. On LG. Then I try ext2load usb 0:1 0x800000 /boot/uImage
LGE-NAS>> ext2load usb 0:1 0x800000 /boot/uImage
....
..............
3326598 bytes read


15. On LG. I set variables
setenv console console=ttyS0,115200 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env)
setenv bootargs_usb root=/dev/sda1 rw rootdelay=10 rootfstype=ext3
setenv bootargs $(console) $(bootargs_usb)


16. On LG. I try to boot the kernel
bootm 0x800000


17. After some stuff it says
...
...
[ ok ] Cleaning up temporary files....
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd...
1199 (syslogd)
. ok
[ ok ] Starting NFS common utilities: statd idmapd.
[ ok ] Starting system message bus: dbus.
[ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
[warn] Not starting NFS kernel daemon: no exports. ... (warning).
[ ok ] Starting NTP server: ntpd.
[ ok ] Starting OpenBSD Secure Shell server: sshd.
[....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd...
1198 (klogd)
. ok
[ ok ] Running local boot scripts (/etc/rc.local).

Debian GNU/Linux 9 debian ttyS0

debian login:


18. On LG. I try to login with root/root and I get
debian login: root
Password:
Linux debian 4.4.0-n1t1-tld-1 #1 PREEMPT Tue Mar 15 14:10:10 CET 2016 armv5tel

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.

19. On LG. I start with checking my IP number with ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet 192.168.0.77  netmask 255.255.255.0  broadcast 192.168.222.255


20. Now I should upgrade the kernel to latest and ditch the custom uImage... Copy the kernel archive to the NAS. Ron used SCP to put it in /root, so I check https://kb.iu.edu/d/agye. One example is
scp ~/rebels.txt dvader@deathstar.com:~/revenge
Maybe I will try
scp ~/stuff/linux-4.13.5-kirkwood-tld-1-bodhi.tar.bz2 root@192.168.0.77:/root

21. On Ubuntu. I download the kernel again (did'nt find it, maybe I deleted it by mistake)
wget https://bitly.com/2yTkIaH
mv 2yTkIaH linux-4.13.5-kirkwood-tld-1-bodhi.tar.bz2


22. On Ubuntu I try to copy the kernel to LG
scp ~/stuff/linux-4.13.5-kirkwood-tld-1-bodhi.tar.bz2 root@192.168.0.77:/root

It seem to work well (after I answer 'yes'), it says
The authenticity of host '192.168.0.77 (192.168.0.77)' can't be established.
ECDSA key fingerprint is SHA256:X3OIRMgyzDLUVNcgHsfQK4eE+kAVMZ8JVkVPp2RLSH4.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.0.77' (ECDSA) to the list of known hosts.
root@192.168.0.77's password:
linux-4.13.5-kirkwood-tld-1-bodhi.tar.bz2     100%   30MB   1.5MB/s   00:20


23. On LG. Extract the files
cd /root
tar jxvf linux-4.13.5-kirkwood-tld-1-bodhi.tar.bz2
tar xvf linux-dtb-4.13.5-kirkwood-tld-1.tar


24. On LG. Install the kernel (this will take some time)
dpkg -i linux-image-4.13.5-kirkwood-tld-1_1.0_armel.deb


25. On LG. Ron say: "Now that the kernel and the modules are installed, we need to create uImage and uInitrd for the bootloader"
cd /boot/
cp -a /root/zImage-4.13.5-kirkwood-tld-1 zImage.fdt
cat /root/dts/kirkwood-n1t1.dtb >> zImage.fdt
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -n Linux-4.13.5-kirkwood-tld-1 -d zImage.fdt uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-4.13.5-kirkwood-tld-1 -d initrd.img-4.13.5-kirkwood-tld-1 uInitrd


26. On LG. Ron say: "Now there should be two u-boot images in the /boot directory. Sync and reboot. Remember to start pressing a key when the u-boot starts to avoid autoboot. (You can also set bootdelay to a nonzero value in u-boot.)"
sync
reboot


27, On LG. As Ron say Meanwhile: "repeatedly hit a button on your keyboard, so the u-boot autostarting can be disabled. If you see the kernel boot messages, the stock OS has started booting, so you need to unplug the power (or shut down via the web UI) and repeat this step until you can access the u-boot command line."

I get access to the u-boot command line.

28. On LG. Ron say "we need to repeat the previous procedure in u-boot, but this time uInitrd has to be loaded too. Also you can save these commands for later use (saveenv).". So I run
usb start
ext2load usb 0:1 0x800000 /boot/uImage

It says
LGE-NAS>> ext2load usb 0:1 0x800000 /boot/uImage
....
.

3860410 bytes read


29. On LG. Ron say "Load uInitrd too:"
ext2load usb 0:1 0x1100000 /boot/uInitrd

It says
...
.
7732059 bytes read


30. On LG. Ron say "These are the previously set arguments, set console and bootargs_usb if you didn't save them, e.g setenv bootargs $(console) $(bootargs_usb)". I do it old style
setenv console console=ttyS0,115200 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env)
setenv bootargs_usb root=/dev/sda1 rw rootdelay=10 rootfstype=ext3
setenv bootargs $(console) $(bootargs_usb)


31. On LG. Ron say "Cross fingers, boot (notice the uInitrd RAM address at the end): bootm 0x800000 0x1100000". I run this (and wait, and wait...)
bootm 0x800000 0x1100000


It says
LGE-NAS>> bootm 0x800000 0x1100000
## Booting image at 00800000 ..., header_size = 00000040, header_addr = 0068dcdc
image_header_t hdr contents
hdr->ih_magic = 56190527, hdr->ih_hcrc = f66af729
hdr->ih_time = 88ca0d5a, hdr->ih_size = 003ae77a
hdr->ih_load = 00800000, hdr->ih_ep = 00800000
hdr->ih_dcrc = e23a0718
hdr->ih_os = 05, hdr->ih_arch = 02
hdr->ih_type = 02, hdr->ih_comp = 00
hdr->ih_name = Linux-4.13.5-kirkwood-tld-1

   Image Name:   Linux-4.13.5-kirkwood-tld-1
   Created:      2017-11-16  17:27:36 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3860346 Bytes =  3.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000, header_addr = 0068dcdc, header_size = 00000040 ...
RAMdisk image_header_t hdr contents
hdr->ih_magic = 56190527, hdr->ih_hcrc = e747bdca
hdr->ih_time = 23cb0d5a, hdr->ih_size = 0075fb1b
hdr->ih_load = 00000000, hdr->ih_ep = 00000000
hdr->ih_dcrc = 1403cfb0
hdr->ih_os = 05, hdr->ih_arch = 02
hdr->ih_type = 03, hdr->ih_comp = 01
hdr->ih_name = initramfs-4.13.5-kirkwood-tld-1

   Image Name:   initramfs-4.13.5-kirkwood-tld-1
   Created:      2017-11-16  17:30:11 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7731995 Bytes =  7.4 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

And nothing more, it stops there for ever.

Any ideas?

It could be something about this
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -n Linux-4.13.5-kirkwood-tld-1 -d zImage.fdt uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-4.13.5-kirkwood-tld-1 -d initrd.img-4.13.5-kirkwood-tld-1 uInitrd

Are Linux-4.13.5-kirkwood-tld-1 and initramfs-4.13.5-kirkwood-tld-1 real files that I can confirm? I don't think I have seen them...

Re: ZyXEL nas326 installation problem

$
0
0
so amazon came through and provided a uart - usb connection, and eventually I managed to get the serial console working. what i've found is that when all the leds turn on dim and wait there, the TX connector needs to be removed and immediately reattached to continue the boot process. from there i can interrupt the autoboot and get into the console.

*** Booting kernel from kernel 1 @0x00000000; run bootcmd_custom;  ***
USB2.0 0: Host Mode
USB3.0 0: Host Mode
USB3.0 1: Host Mode
Board configuration detected:
Net:
|  port  | Interface | PHY address  |
|--------|-----------|--------------|
| egiga0 |   RGMII   |     0x01     |
egiga0 [PRIME]
Hit any key to stop autoboot:  0

NAND read: device 0 whole chip
Attempt to read outside the flash area
 0 bytes read: ERROR
Booting from USB ...
(Re)start USB...
USB0:   Port (usbActive) : 0	Interface (usbType = 2) : USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
       scanning usb for ethernet devices... 0 Ethernet Device(s) found
** No partition table - usb 0 **
** No partition table - usb 0 **
** No partition table - usb 0 **
*  kernel: cmdline image address = 0x02000000
Bad Linux ARM zImage magic!
Booting from NAND kernel 1 ...

NAND read: device 0 offset 0xe00000, size 0xf00000
 15728640 bytes read: OK
*  kernel: cmdline image address = 0x02000000

Starting kernel ...

Power on HDD1 ...
Power on HDD2 ...
Power on USB ...

Uncompressing Linux... done, booting the kernel.

from what i understand this implies the contents of the usb aren't setup correctly - Bad Linux ARM zImage magic. I'm not sure how to address this though.

Re: LG N1T1 NAS

$
0
0
raffe Wrote:
-------------------------------------------------------
> Are Linux-4.13.5-kirkwood-tld-1 and initramfs-4.13.5-kirkwood-tld-1 real files that I
> can confirm? I don't think I have seen them...

Those aren't files; they're names given to the created images. Check out mkimage usage info.

Re: ZyXEL nas326 installation problem

$
0
0
rkachowski,

1. Regarding serial console

> what i've found is that
> when all the leds turn on dim and wait there, the
> TX connector needs to be removed and immediately
> reattached to continue the boot process. from
> there i can interrupt the autoboot and get into
> the console.

Or run kwboot as instructed in the installation post:

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

Running kwboot at any time before or after power up, i.e. you don't have to time the action.

2. Most of the time, that bad image magic error is not what it seems to be.

Interrupt serial console at countdown, and

printenv

Please post the entire serial console log until this point here.
Viewing all 26659 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>