LG N1T1 NAS

Good news everyone! :)

 96 % [......................................................................]
 99 % [..............................]
[Type Ctrl-\ + c to quit]


U-Boot 2015.10-g3ea3d35-dirty (Mar 22 2016 - 20:36:35 +0100)
LG NT1

SoC:   Kirkwood 88F6281_A1
SPI:   ready
DRAM:  128 MiB (ECC not enabled)
WARNING: Caches not enabled
SF: Detected MX25L4005 with page size 256 Bytes, erase size 64 KiB, total 512 KiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Error: egiga0 address not set.

Hit any key to stop autoboot:  0

This is a U-Boot that was adapted to run on the N1T1 back in March. Unfortunately at that time there was a problem with my serial cable. But today I got a different cable and managed to run it using kwboot. It also boots Linux.

Now the next step is to transfer the modifications into the latest U-Boot version from git and run it again. Also I need to flash it to the SPI Flash and make it run from there (shouldn't be a problem but it is a little risky). If all goes well, by next week there will be a pull request for the N1T1 U-Boot.



Edited 1 time(s). Last edit at 10/01/2016 03:01PM by ron.

Thank you, Ron and Bodhi, for having made possible to run a current Linux version on the N1T1. This is a significant enhancement for the use which I can make of the device.

I followed Ron's mini Howto and want to describe how it worked for me and the experiences I made - could be helpful for others.

I have a N1T1TD1 which is the branded version of the N1T1 sold by Deutsche Telekom some years ago. The mainboard looks identical to Ron's pictures in http://forum.doozan.com/read.php?2,26671,30316#msg-30316.

The following steps refer to the steps of the mini Howto.

Step 1:
According to the blinking of the LEDs of my USB-TTL-Adapter, the solder eyelets at the N1T1 are probably - from Power connector side to DVD side - 3V3, input of N1T1, output of N1T1, GND. The output of the N1T1 has to be connected to the input of the adapter and conversely.
The labels RX, TX may be sometimes confusing - at least at my USB-TTL-Adapter they are the other way around for people who want to connect RX with RX and TX with TX.

Step 5 and 6:
The original uboot (U-Boot 1.1.4 (Oct 28 2010 - 11:33:14) LGE version: NT1 Series) doesn't find files on an ext4 partition. At least uImage and uInitrd should be on an ext3 partition.

The uImage given by Ron for the very first boot didn't work for me. I got the message

   Image Name:   Linux-4.4.0-kirkwood-tld-1
   Created:      2016-03-19  22:59:01 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3326534 Bytes =  3.2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 00000000, header_addr = 0068dcdc, header_size = 00000040 ...
Bad Magic Number

I circumvented this problem by performing steps 7 to 9 in a chroot environment on a Raspberry Pi 2.
Additionally, I have used this to add a new sudo user to the N1T1 environment.
If /media/pi/rootext3/ is the mount point of my new N1T1 root partition on the Raspbery Pi, the commands to get to the chroot environment are:

sudo mount --bind /dev  /media/pi/rootext3/dev
sudo mount -t devpts devpts  /media/pi/rootext3/dev/pts
sudo mount -t proc proc  /media/pi/rootext3/proc
sudo mount -t sysfs sysfs  /media/pi/rootext3/sys
sudo chroot /media/pi/rootext3

After having finished Steps 6-9, the commands to get out from chroot are:

exit
sudo umount  /media/pi/rootext3/dev/pts  /media/pi/rootext3/dev /media/pi/rootext3/proc  /media/pi/rootext3/sys

I used Bodhi's
kernel linux-4.8.0-kirkwood-tld-1-bodhi.tar.bz2 (10 Oct 2016)
and rootfs Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (20 Feb 2016)

Step 10:
To get the number of the Partition where uImage and uInitrd reside in your configuration, the uboot commands

usb storage
usb part
ext2ls usb  0:1  /boot

may be useful, where 0:1 are to be replaced by the numbers (drive:partition) you have found out by "usb storage" and "usb part".

For the parameter "root=/dev/sda1" in the "setenv bootargs_usb" command (from step 6, needed here as well), a SATA disk if you have one connected to the N1T1 has to be taken into account. So for me, as my root is on the second partition of the USB stick or disk, it is "/root=/dev/sdb2"

Remark:
uImage and uInitrd may be on the same partition as the root filesystem or on a separate boot partition.



Edited 1 time(s). Last edit at 10/19/2016 03:51AM by bernd.

Thanks bernd for the additional comments! I guess I am seeing enough indication that this is working to try this on myself.

I have a couple questions to ron:

Any news regarding the u-boot?
Also, In #5 or #6 of your instructions, you give a link to download a uImage. Would you mind also giving instructions to create it myself?

Thanks in advance!

Hi shwouchk!

To create your own uImage, download the 4.4 kernel sources from bodhi and apply the patch from the first post in this thread. Then build it and create an uImage from the zImage. I also enabled USB support, USB mass storage support and IDE/SATA support in the kernel menuconfig so the needed drivers are part of the kernel. That was needed because there was no initrd (or uInitrd) for my kernel and it could only boot from NFS.
Unfortunately I can't remember the exact steps but there should be a guide either on this forum on the Internet how to compile a kernel for the DockStar, you can use that.

Regarding the u-boot, I didn't had time to work on it in the last 2 weeks. So far there is a version that can be uploaded to the N1T1 by UART and it starts the kernel (including separate DTS/DTB loading). There is still work to be done, such as: figure out how the power button and power LED is connected, if the Ethernet PHY needs resetting at startup and of course to flash it to the SPI flash and boot from there.
As soon as I have a free weekend, it will be finished! :)

Thanks!

hello everybody!

I saw your work and I'd like to know one thing
following your thread is possible to install an updated version of debian, to manage with webmin or stuff like this?
the best would be to install a distro Like OpenMediaVault
have you got any suggestion to leave the definitely the LG UI?

I'm asking this because I broke the stock UI making upgrades to the packages; otherwise, is possible to launch the official firmware upgrade process trough SSH without losing my DATA?
I'm still keeping the hacked firmware package I used to install the New UI, gaining the root access. (as expained here http://dandylife.net/blog/archives/63 )

varma Wrote:
-------------------------------------------------------
> hello everybody!
>
> I saw your work and I'd like to know one thing
> following your thread is possible to install an
> updated version of debian, to manage with webmin
> or stuff like this?
> the best would be to install a distro Like
> OpenMediaVault
> have you got any suggestion to leave the
> definitely the LG UI?
>
> I'm asking this because I broke the stock UI
> making upgrades to the packages; otherwise, is
> possible to launch the official firmware upgrade
> process trough SSH without losing my DATA?
> I'm still keeping the hacked firmware package I
> used to install the New UI, gaining the root
> access. (as expained here
> http://dandylife.net/blog/archives/63 )


You can get the Debian rootfs here:

http://forum.doozan.com/read.php?2,12096

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

Hi varma!

Once you have Debian running (according to my guide for this particular device or another generic guide from the forum) it's up to you to install any web management interface for the NAS. I think OpenMediaVault can be installed on Debian by adding the repos to the apt configuration and installing the omv package. See http://wiki.openmediavault.org/index.php?title=Download_OpenMediaVault for more info.

Your data is stored on a different partition than the OS so as long as that partition (and the partition table) remains intact, you should be able to overwrite the stock OS without any data loss.

Thank you for the super fast replies
I'll try to apply when I'll find enough time!
Maybe I could consider to replace the ODD with a notebook disk, within a caddy, to make an experimental configuration and avoid to destroy all my data, gaining even more disk space (or a chinese SSD to speed up the OS)

Guys, total noob question here, can I swap the hdd (everything is still stock), for a 2tb hdd, just by cloning the original hdd onto the new one? Will that work without any other modifications?

I know this is totally off topic, apologies for that, but your thread was the only live one I could find on this device... TIA!

It will probably work, no modifications should be needed (except for resizing the cloned partition).

ron & Den,

When cloning the rootfs, you should look at the udev files to make sure ethernet will work. Otherwise udev rules will prevent eth0 to be active.

See here:
http://forum.doozan.com/read.php?2,18007,18008#msg-18008

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



Edited 1 time(s). Last edit at 02/01/2017 05:36AM by bodhi.

Thanks Ron, Bodhi

@Bodhi, can I look in the rootfs and change files while the hdd is attached to my laptop?

Also, @ Ron,
How did you open the darn casing?

I managed to get the black front of (1 screw and pull)
And one white side (the right side when gabbing the dvd slot) with a spudger.
The other side has a different licking system by the looks of it, as does the rest of the black casing...

Any help appreciated, thanks guys

Den,

you should be able to pull it towards yourself (when facing the DVD slot). There are some tabs locking the panel at the bottom and the back (near the fan outlet), so be careful.

@Den,

Yes, you can change it offline on your Linux laptop. But make sure that you are the root user while doing that (sudo won't work). After changing them, list the files and double check the permission. For example:

ls -l /etc/udev/rules.d/70-persistent-net.rules
-rw-r--r-- 1 root root 822 Jun  4  2016 /etc/udev/rules.d/70-persistent-net.rules

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

@Den,

here is a Howto for opening the case: nasausbau.pdf.

(I don't find any more the webpage where I originally found this link.)

Bernd

@all thanks for all the willingness to help and quick replies!

@Bodhi In my simple thinking mind, I should be able to get away with cloning and putting the new bigger hdd back in the old enclosure. If I were to clone a hdd and then put the clone from one enclosure to another I would have to check the settings. Am I correct in this assumption?

Thanks all!

@Den,

The enclosure will not matter. Only if the HDD rootfs was used in booting one box, and then you clone it, then it should be doublecheck.

But if everything is done for this specific N1T1 NAS, and you have no intention of using the backup rootfs for any other N1T1 box or other Kirkwood boxes then there is no need to worry.

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

That's what I thought, thanks Bodhi, I'll let you guys know one I'm finished.

Allright, some good, some bad..

1.) Enclosure opened without damage, easy to swap HDD's. Great, Thanks Bernd for the pdf!

2.) HDD cloned, looks exactly the same in Partition manager as the other one (4 partitions, two small ones, one 100GB, one almost 800GB. So far so good, but windows doesn't recognize the form of the partitions, so how can i resize the 800GB to 1800GB? Ron?

3.) I have put the new HDD in the enclosure, and it boots up fine, also in the LG NAS detector, the NAS shows up with an ip.
I can look up two of the partitions in windows file explorer.
However, if i try to connect to the webportal, i get the following error in my webbrowser:
Forbidden

You don't have permission to access / on this server.
Apache/2.2.14 (Unix) mod_ssl/2.2.14 OpenSSL/0.9.8g DAV/2 PHP/5.2.11 with Suhosin-Patch Server at 192.168.1.12 Port 80

Maybe this has to do with the rootfs afterall Bodhi?
(i do not have a linux laptop, all i have is some minor experience with SSH through Putty)

Also even though i can see the drive partitions as network folders, i cannot see anything in them.

When i swap back to the original HDD, everything functions properly, and even, if i leave the webportal open, after swapping back to the clone, i can acces the NAS with cloned HDD through webportal (still no files visible in the main folders though)..

(I could reformat or scan HDD though the web portal after doing this, but the scan claims to take 6-8hrs, so i will only do this if you guys advise to)

Any more suggestions?
Thanks a bunch!!

Addition:

If i enter the ip in my webbrowser, i get the error msg above.

If i go to my webbrowser history, i can acces the nas with clone HDD (with the above restrictions).

Den,

Check your rootfs cloning process. Were you root user? how did you clone it?

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

Hi Bodhi,

Still not quite sure how to check my rootfs, right now putty wont let me connect with the new hdd in..

Cloning was done with a cloning dock (standalone, without use of computer)

can i get into rootfs if i put the hdd in a dock? Or do i have to do it inside the nas, (assuming NAS), then i have to figure out how i can get into it through ethernet, have to work around the error..

Den,

> Cloning was done with a cloning dock (standalone,
> without use of computer)

This could be problematic. But I don't know how your dock work so can't say for sure. Usually, if you clone a HDD --> a HDD, then the sectors would be replicated. But from a USB to HDD, I am not sure if this dock does that.

You can do the cloning in Linux, if you clone your USB rootfs to another USB drive first using the cloning dock. And then use the new USB drive to boot the NAS. After you logged in, you would plug in the HDD and the old USB rootfs. And follow the procedure here:

http://forum.doozan.com/read.php?2,12096,24034#msg-24034

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

hi everybody!

I solved the broken official UI problem.
following and old guide I decrypted the firmware archive and decompressed it.
I uninstalled all the new packages that broke the system
then, looking at the timestamp of the files I replaced all the files modified the day of the disaster with the original ones.
also I renamed with a "_" all the orphan files to "neutralize" them.
after a reboot I regained the access to the GUI, to Transmissions and all the other web based softwares.

I guess I won't try Debian for a while...it's quite a shame, but it's a lot easier!!

thank you very much

Hi, I have LG NAS N2B1

in my case, success on step 6 but step 10 fail to booting.
I think n2b1's dtb is not same with n1t1's.
( cat /root/dts/kirkwood-n1t1.dtb >> zImage.fdt)

how can I get n2b1's dtb.
would you please help me?

yongki,

> Hi, I have LG NAS N2B1
>
> in my case, success on step 6 but step 10 fail to
> booting.

Which procedure are you using (step 6 and step 10 from where)? Can you post the log of your attempt?

> I think n2b1's dtb is not same with n1t1's.
> ( cat /root/dts/kirkwood-n1t1.dtb >> zImage.fdt)

Do you have a list of the N2B1 specifications? how does that compare to the N1T1? i.e. what are the differences or the same?

It might be possible if they simliar and there is only some minor differences.

You do need to post a lot more information so we can see if it possible to create a different DTS/DTB for this N2B1 box.

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

Normal mode boot start!

_   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__| 
 ** LGE-NAS BOARD: NC1 LE 

U-Boot 1.1.4 (Feb 24 2012 - 15:06:45)NC1

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006D0700

Soc: 88F6192 A1 CPU running @ 1000Mhz L2 running @ 500Mhz
SysClock = 250Mhz , TClock = 166Mhz 

DRAM (DDR2) CAS Latency = 3 tRP = 3 tRAS = 8 tRCD=3
DRAM CS[0] base 0x00000000   size 128MB 
DRAM Total size 128MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:nand_bbm_init: Init nand bad block information...
nand_bbm_find_pos: nand_bbm_check = 0, erasesize = 20000
nand_bbm_find_pos: nand_bbm_find_pos: bbm pos = 7800000, pos = 7800000
Loading nand bad block info(07800000+00020000)...
nand_bbm_info_load: bbm->magic        = 8192a5a7
nand_bbm_info_load: bbm->bb_count     = 1
nand_bbm_info_load: bbm->assign_index = 3fe
nand_bbm_info_load: [0 (0:0)] maps(2c6->3ff) pos(58c0000->7fe0000)
Assign index = 3fe
nand_bbm_info_load: Loading nand bad block info...ok
128 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled 
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
 Normal mode : lg_bootmode = 0 
Hit any key to stop autoboot:  0 
LGE-NAS>>   usb start
(Re)start USB...
USB:   scanning bus for devices... 3 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
       scanning bus for storage devices... 1 Storage Device(s) found
LGE-NAS>>   ext2load usb 0:1 0x800000 /boot/uImage
....
................................................................................................................................................................................................................................................................................................................................

3326598 bytes read
LGE-NAS>>   setenv console console=ttyS0,115200 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env)
LGE-NAS>>   setenv bootargs_usb root=/dev/sda1 rw rootdelay=10 rootfstype=ext3
LGE-NAS>>   setenv bootargs $(console) $(bootargs_usb)
LGE-NAS>>
LGE-NAS>> bootm 0x800000

....

Debian GNU/Linux 8 debian ttyS0

debian login: root
Password:
Last login: Sat Mar 25 21:12:03 PDT 2017 on ttyS0
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.
root@debian:~#

root@debian:~#tar jxvf linux-4.6.0-kirkwood-tld-1-bodhi.tar.bz2
...
root@debian:~#tar xvf linux-dtb-4.6.0-kirkwood-tld-1.tar
...
root@debian:~# dpkg -i linux-image-4.6.0-kirkwood-tld-1_1.0_armel.deb
Selecting previously unselected package linux-image-4.6.0-kirkwood-tld-1.
(Reading database ... 12657 files and directories currently installed.)
Preparing to unpack linux-image-4.6.0-kirkwood-tld-1_1.0_armel.deb ...
Examining /etc/kernel/preinst.d/
Done.
Unpacking linux-image-4.6.0-kirkwood-tld-1 (1.0) ...
Setting up linux-image-4.6.0-kirkwood-tld-1 (1.0) ...

Hmm. There is a symbolic link /lib/modules/4.6.0-kirkwood-tld-1/build
However, I can not read it: No such file or directory
Therefore, I am deleting /lib/modules/4.6.0-kirkwood-tld-1/build


Hmm. The package shipped with a symbolic link /lib/modules/4.6.0-kirkwood-tld-1/source
However, I can not read the target: No such file or directory
Therefore, I am deleting /lib/modules/4.6.0-kirkwood-tld-1/source

Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.6.0-kirkwood-tld-1 /boot/vmlinuz-4.6.0-kirkwood-tld-1
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.6.0-kirkwood-tld-1 /boot/vmlinuz-4.6.0-kirkwood-tld-1
update-initramfs: Generating /boot/initrd.img-4.6.0-kirkwood-tld-1
run-parts: executing /etc/kernel/postinst.d/zz-flash-kernel 4.6.0-kirkwood-tld-1 /boot/vmlinuz-4.6.0-kirkwood-tld-1


root@debian:/boot# cp -a /root/zImage-4.6.0-kirkwood-tld-1 zImage.fdt
root@debian:/boot# cat /root/dts/kirkwood-n1t1.dtb >> zImage.fdt
Linux-4.6.0-kirkwood-tld-1 -d zImage.fdt uImage kernel -C none -a 0x00008000 -n
Image Name: Linux-4.6.0-kirkwood-tld-1
Created: Sun Mar 26 04:38:57 2017
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3269366 Bytes = 3192.74 kB = 3.12 MB
Load Address: 00008000
Entry Point: 00008000
uInitrd000 -n initramfs-4.6.0-kirkwood-tld-1 -d initrd.img-4.6.0-kirkwood-tld-1
Image Name: initramfs-4.6.0-kirkwood-tld-1
Created: Sun Mar 26 04:39:03 2017
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7251403 Bytes = 7081.45 kB = 6.92 MB
Load Address: 00000000
Entry Point: 00000000

root@debian:/boot# sync
root@debian:/boot# reboot

....

CPU : Marvell Feroceon (Rev 1)

Streaming disabled 
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
 Normal mode : lg_bootmode = 0 
Hit any key to stop autoboot:  0 
LGE-NAS>>   usb start
(Re)start USB...
USB:   scanning bus for devices... 3 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
       scanning bus for storage devices... 1 Storage Device(s) found
LGE-NAS>>   ext2load usb 0:1 0x800000 /boot/uImage
....
.
......
............
.........................
...................................................
......................................................................................................
..................................................................................................................

3269430 bytes read
LGE-NAS>>   ext2load usb 0:1 0x1100000 /boot/uInitrd
....
.
......
............
.........................
...................................................
......................................................................................................
............................................................................................................................................................................................................
....
.....................................................................................................................................................................................................................................................................................................

7251467 bytes read
LGE-NAS>>   setenv bootargs $(console) $(bootargs_usb)
LGE-NAS>> bootm 0x800000 0x1100000

7251467 bytes read
LGE-NAS>>   setenv bootargs $(console) $(bootargs_usb)
LGE-NAS>> bootm 0x800000 0x1100000
## Booting image at 00800000 ..., header_size = 00000040, header_addr = 0069024c
image_header_t hdr contents
hdr->ih_magic = 56190527, hdr->ih_hcrc = a064e8d6
hdr->ih_time = 51a8d758, hdr->ih_size = 0031e2f6
hdr->ih_load = 00800000, hdr->ih_ep = 00800000
hdr->ih_dcrc = e6257564
hdr->ih_os = 05, hdr->ih_arch = 02
hdr->ih_type = 02, hdr->ih_comp = 00
hdr->ih_name = Linux-4.6.0-kirkwood-tld-1

   Image Name:   Linux-4.6.0-kirkwood-tld-1
   Created:      2017-03-26  11:38:57 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3269366 Bytes =  3.1 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000, header_addr = 0069024c, header_size = 00000040 ...
RAMdisk image_header_t hdr contents
hdr->ih_magic = 56190527, hdr->ih_hcrc = ba9adaf7
hdr->ih_time = 57a8d758, hdr->ih_size = 006ea5cb
hdr->ih_load = 00000000, hdr->ih_ep = 00000000
hdr->ih_dcrc = 0e1244dc
hdr->ih_os = 05, hdr->ih_arch = 02
hdr->ih_type = 03, hdr->ih_comp = 01
hdr->ih_name = initramfs-4.6.0-kirkwood-tld-1

   Image Name:   initramfs-4.6.0-kirkwood-tld-1
   Created:      2017-03-26  11:39:03 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7251403 Bytes =  6.9 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

...

[    4.749649] i2c /dev entries driver
[    4.754918] hidraw: raw HID events driver (C) Jiri Kosina
[    4.760877] drop_monitor: Initializing network drop monitor service
[    4.767455] NET: Registered protocol family 17
[    4.772169] Key type dns_resolver registered
[    4.777453] registered taskstats version 1
[    4.781579] Loading compiled-in X.509 certificates
[    4.786456] zswap: loaded using pool lzo/zbud
[    4.801304] Key type encrypted registered
[    4.805982] hctosys: unable to open rtc device (rtc0)
[    4.813768] Freeing unused kernel memory: 304K (c0824000 - c0870000)
[    4.820210] This architecture does not have kernel memory protection.
Loading, please wait...
[    4.908684] systemd-udevd[83]: starting version 215
[    4.926198] random: systemd-udevd urandom read with 8 bits of entropy available
[    5.119631] SCSI subsystem initialized
�

========================================

specifications : https://www.cnet.com/products/lg-n2b1-nas-server-2-tb/specs/

thanks in advance!!!



Edited 2 time(s). Last edit at 03/26/2017 04:28PM by bodhi.

yongki,

First, please use code tags when posting log.

1. How did you create this rootf? was it based on my Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 rootfs ? And if true, did you compile the 4.4.0-n1t1-tld-1 kernel?

Debian GNU/Linux 8 debian ttyS0 

debian login: root 
Password: 
Last login: Sat Mar 25 21:12:03 PDT 2017 on ttyS0 
Linux debian 4.4.0-n1t1-tld-1 #1 PREEMPT Tue Mar 15 14:10:10 CET 2016 armv5tel

2. At this point, is the box running OK? any thing different from the N1T1?

3. Your box is not the same as the N1T1. The N1T1 use the 6281 SoC

Your box

Soc: 88F6192 A1 CPU running @ 1000Mhz L2 running @ 500Mhz
SysClock = 250Mhz , TClock = 166Mhz

N1T1

Soc: 88F6281 A1 (DDR2)
CPU running @ 1000Mhz L2 running @ 333Mhz
SysClock = 333Mhz , TClock = 200Mhz

4. Your box is not the N2B1 either! It's the same SoC, but running at a different clock

** LGE-NAS BOARD: NC1 LE
...
Soc: 88F6192 A1 CPU running @ 1000Mhz L2 running @ 500Mhz
SysClock = 250Mhz , TClock = 166Mhz

In the link you posted, the N2B1 SoC is the same as yours, but running at a slower clock speed, exactly like the Pogo V4.

Processors Installed Marvell 88F6192 800 MHz
RAM Installed DRAM 128 MB

-------

So not sure what your intention is. If you can run the "Linux debian 4.4.0-n1t1-tld-1" kernel without propblem, then you shoudl use the DTB from that box, which is Ron's version that I incorporated into the kernel since 4.4+.

But when you install the kernel 4.6, it does not work any more? is that the question?

Note: at each section of log that you posted, please write a short sentence of what you want to say about that snippet of log. Does not have to be long (lot of us here are not native English speakers), just enough to say what you want to convey.

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