|
Re: LG N1T1 NAS October 13, 2020 03:22AM |
Registered: 4 years ago Posts: 13 |
Hi bodhi.
Would the latest u-boot allow booting from a pure gpt system ? I would actually feel better without the hybrid mbr/gpt. Could it allow booting from 2 different gpt partitions whether a usb stick is connected or not (might even be empty, just present) ?
If it is the case, I do have jtag + serial adapter and could do the testing being one month retired with time to spare.
Regards.
Edited 2 time(s). Last edit at 10/13/2020 03:29AM by Jmax.
Would the latest u-boot allow booting from a pure gpt system ? I would actually feel better without the hybrid mbr/gpt. Could it allow booting from 2 different gpt partitions whether a usb stick is connected or not (might even be empty, just present) ?
If it is the case, I do have jtag + serial adapter and could do the testing being one month retired with time to spare.
Regards.
Edited 2 time(s). Last edit at 10/13/2020 03:29AM by Jmax.
|
Re: LG N1T1 NAS October 13, 2020 06:33PM |
Admin Registered: 13 years ago Posts: 19,114 |
Jmax,
> Would the latest u-boot allow booting from a pure
> gpt system ?
> Could it allow booting from 2
> different gpt partitions whether a usb stick is
> connected or not (might even be empty, just
> present) ?
Yes, my released Kirkwood u-boots have all those capabilities.
> If it is the case, I do have jtag + serial adapter
> and could do the testing being one month retired
> with time to spare.
>
I can't promise that I will build new u-boot for this box. At the moment I'm too busy and don't know when I will have a few-days block of free time.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Would the latest u-boot allow booting from a pure
> gpt system ?
> Could it allow booting from 2
> different gpt partitions whether a usb stick is
> connected or not (might even be empty, just
> present) ?
Yes, my released Kirkwood u-boots have all those capabilities.
> If it is the case, I do have jtag + serial adapter
> and could do the testing being one month retired
> with time to spare.
>
I can't promise that I will build new u-boot for this box. At the moment I'm too busy and don't know when I will have a few-days block of free time.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: LG N1T1 NAS October 15, 2020 02:15AM |
Registered: 4 years ago Posts: 13 |
bodhi Wrote:
-------------------------------------------------------
> Yes,
> my
> released Kirkwood u-boots have all those
> capabilities.
>
> > If it is the case, I do have jtag + serial
> adapter
> > and could do the testing being one month
> retired
> > with time to spare.
> >
>
> I can't promise that I will build new u-boot for
> this box. At the moment I'm too busy and don't
> know when I will have a few-days block of free
> time.
Please do not worry about that.
I just mentioned being free to build and test it myself if possible, it is more an academic question than anything else.
Do not take the trouble.
-------------------------------------------------------
> Yes,
> my
> released Kirkwood u-boots have all those
> capabilities.
>
> > If it is the case, I do have jtag + serial
> adapter
> > and could do the testing being one month
> retired
> > with time to spare.
> >
>
> I can't promise that I will build new u-boot for
> this box. At the moment I'm too busy and don't
> know when I will have a few-days block of free
> time.
Please do not worry about that.
I just mentioned being free to build and test it myself if possible, it is more an academic question than anything else.
Do not take the trouble.
|
Re: LG N1T1 NAS October 15, 2020 04:11PM |
Admin Registered: 13 years ago Posts: 19,114 |
|
Re: LG N1T1 NAS October 16, 2020 01:50AM |
Registered: 4 years ago Posts: 13 |
Hi bodhi.
I did some more testing after determining that bootrom was version 1.21. kwboot works fine with the first image uboot.2017.07-tld-1.goflexhome.bodhi.tar that mentioned using the same processor, booting proceeds and give me a totally functional debian system.
I am not even sure I need to go any further, the stock N1T1 uboot supports hybrid mbr/gpt, it could as well support plain gpt. I have a spare disk that I shall format gpt, and un'tar the debian, then the stock system. I will update in case somebody comes around.
If I go farther, what should I look for beyond proper disk/net/serial already working ?
I suppose it is a good idea to get the stock uboot backed up and test it with kwboot ?
Regards.
EDIT: I backed up the mtd0 with "nanddump -l 0x80000 -f mtd0 /dev/mtd0" the -n option gives an error. From main PC, I used scp to get the image and tested it with kwboot, works perfectly.
Edited 2 time(s). Last edit at 10/16/2020 02:23AM by Jmax.
I did some more testing after determining that bootrom was version 1.21. kwboot works fine with the first image uboot.2017.07-tld-1.goflexhome.bodhi.tar that mentioned using the same processor, booting proceeds and give me a totally functional debian system.
I am not even sure I need to go any further, the stock N1T1 uboot supports hybrid mbr/gpt, it could as well support plain gpt. I have a spare disk that I shall format gpt, and un'tar the debian, then the stock system. I will update in case somebody comes around.
If I go farther, what should I look for beyond proper disk/net/serial already working ?
I suppose it is a good idea to get the stock uboot backed up and test it with kwboot ?
Regards.
EDIT: I backed up the mtd0 with "nanddump -l 0x80000 -f mtd0 /dev/mtd0" the -n option gives an error. From main PC, I used scp to get the image and tested it with kwboot, works perfectly.
Edited 2 time(s). Last edit at 10/16/2020 02:23AM by Jmax.
|
Re: LG N1T1 NAS October 16, 2020 04:06PM |
Admin Registered: 13 years ago Posts: 19,114 |
Jmax,
> I did some more testing after determining that
> bootrom was version 1.21. kwboot works fine with
> the first image
> uboot.2017.07-tld-1.goflexhome.bodhi.tar that
> mentioned using the same processor, booting
> proceeds and give me a totally functional debian
> system.
Well done!
>
> I am not even sure I need to go any further,
No need to if you found that stock u-boot works booting the Debian rootfs.
>
> If I go farther, what should I look for beyond
> proper disk/net/serial already working ?
The GoFlex Home and this N1T1 have the same SoC and memory. But different in other aspect such as flash type, LED GPIOs. Might be the same network chip (I have not looked to confirm but it should be).
So while it is OK to kwboot as a rescue tool, it should not be used as is.
> EDIT: I backed up the mtd0 with "nanddump
> -l 0x80000 -f mtd0 /dev/mtd0" the -n option gives
> an error. From main PC, I used scp to get the
> image and tested it with kwboot, works perfectly.
Now you know there is a rescue mechanism working with stock mtd0.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I did some more testing after determining that
> bootrom was version 1.21. kwboot works fine with
> the first image
> uboot.2017.07-tld-1.goflexhome.bodhi.tar that
> mentioned using the same processor, booting
> proceeds and give me a totally functional debian
> system.
Well done!
>
> I am not even sure I need to go any further,
No need to if you found that stock u-boot works booting the Debian rootfs.
>
> If I go farther, what should I look for beyond
> proper disk/net/serial already working ?
The GoFlex Home and this N1T1 have the same SoC and memory. But different in other aspect such as flash type, LED GPIOs. Might be the same network chip (I have not looked to confirm but it should be).
So while it is OK to kwboot as a rescue tool, it should not be used as is.
> EDIT: I backed up the mtd0 with "nanddump
> -l 0x80000 -f mtd0 /dev/mtd0" the -n option gives
> an error. From main PC, I used scp to get the
> image and tested it with kwboot, works perfectly.
Now you know there is a rescue mechanism working with stock mtd0.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: LG N1T1 NAS October 21, 2020 12:47AM |
Registered: 4 years ago Posts: 13 |
Well, I shouted "victory" too soon.
While installing Linux, I did not understand why the partitions were shown as "linux-raid" and lost any possibility of reverting to the original software. The updated u-boot, which support pure gpt prevents from reinstalling the base software. It is fine with Debian though.
I do not know if anybody still has the original 1Tb box and would be capable of extracting the information I missed at the beginning, some much for my eagerness to get the disk upgraded and not keeping the old one as it was :/
If anybody has the original non-upgraded firmware, I would like to get in touch.
Edited 2 time(s). Last edit at 10/24/2020 12:05PM by Jmax.
While installing Linux, I did not understand why the partitions were shown as "linux-raid" and lost any possibility of reverting to the original software. The updated u-boot, which support pure gpt prevents from reinstalling the base software. It is fine with Debian though.
I do not know if anybody still has the original 1Tb box and would be capable of extracting the information I missed at the beginning, some much for my eagerness to get the disk upgraded and not keeping the old one as it was :/
If anybody has the original non-upgraded firmware, I would like to get in touch.
Edited 2 time(s). Last edit at 10/24/2020 12:05PM by Jmax.
|
S
Re: LG N1T1 NAS October 28, 2020 01:21PM |
|
Re: LG N1T1 NAS October 29, 2020 07:24AM |
Registered: 4 years ago Posts: 13 |
S Wrote:
-------------------------------------------------------
> The original firmware can be downloaded from LG's
> website. As long, the updated u-boot contains LG's
> rescue mode, it shouldn't be any problem to use it
> to restore the raid configuration.
Hi S.
I did that already, but it fails. Unfortunately, once updated for the new new U-boot, there is no way back, the original software can no longer be installed, I suppose it relies on the old U-boot. The only solution seems to be reverting to the original U-boot.
-------------------------------------------------------
> The original firmware can be downloaded from LG's
> website. As long, the updated u-boot contains LG's
> rescue mode, it shouldn't be any problem to use it
> to restore the raid configuration.
Hi S.
I did that already, but it fails. Unfortunately, once updated for the new new U-boot, there is no way back, the original software can no longer be installed, I suppose it relies on the old U-boot. The only solution seems to be reverting to the original U-boot.
|
S
Re: LG N1T1 NAS November 01, 2020 01:23PM |
Jmax Wrote:
-------------------------------------------------------
> S Wrote:
> -------------------------------------------------------
> > The original firmware can be downloaded from
> LG's
> > website. As long, the updated u-boot contains
> LG's
> > rescue mode, it shouldn't be any problem to use
> it
> > to restore the raid configuration.
>
> Hi S.
>
> I did that already, but it fails. Unfortunately,
> once updated for the new new U-boot, there is no
> way back, the original software can no longer be
> installed, I suppose it relies on the old U-boot.
> The only solution seems to be reverting to the
> original U-boot.
The rescue mode will create a raid partition which will require the u-boot to boot the /dev/md0 partition (and not /dev/sda1). So, it might just be wrong configuration. Post your envs and I can compare it with my envs. Otherwise, there exist a uboot file in LG site which can be used to get the old uboot.
-------------------------------------------------------
> S Wrote:
> -------------------------------------------------------
> > The original firmware can be downloaded from
> LG's
> > website. As long, the updated u-boot contains
> LG's
> > rescue mode, it shouldn't be any problem to use
> it
> > to restore the raid configuration.
>
> Hi S.
>
> I did that already, but it fails. Unfortunately,
> once updated for the new new U-boot, there is no
> way back, the original software can no longer be
> installed, I suppose it relies on the old U-boot.
> The only solution seems to be reverting to the
> original U-boot.
The rescue mode will create a raid partition which will require the u-boot to boot the /dev/md0 partition (and not /dev/sda1). So, it might just be wrong configuration. Post your envs and I can compare it with my envs. Otherwise, there exist a uboot file in LG site which can be used to get the old uboot.
|
Re: LG N1T1 NAS November 02, 2020 01:24AM |
Registered: 4 years ago Posts: 13 |
S Wrote:
> The rescue mode will create a raid partition which
> will require the u-boot to boot the /dev/md0
> partition (and not /dev/sda1). So, it might just
> be wrong configuration. Post your envs and I can
> compare it with my envs. Otherwise, there exist a
> uboot file in LG site which can be used to get the
> old uboot.
Yes, the env variable specify /dev/md0 as the root as root_path.
My environment, as it is now after the changes made to boot linux
from hard disk is :
Some changes were made for Debian, which I tried to revert as
well as possible but, I guess, screwed up something in the process.
I should mention that I tried the rescue process for the new U-boot
system (new UI) but this fails as well. Probably environment being
wrong as you indicate.
In the meantime, I shall search again the LG site to find the u-boot
mentioned.
Regards.
EDIT :
You were right. One single option I overlooked was a "gateway" which
prevented the system from booting. It was straightforward after that, I
was able to restore a full standard system. I just have to figure out how
to fit it with a usb boot for Debian and I will be very happy. Many thanks.
Edited 1 time(s). Last edit at 11/02/2020 04:14AM by Jmax.
> The rescue mode will create a raid partition which
> will require the u-boot to boot the /dev/md0
> partition (and not /dev/sda1). So, it might just
> be wrong configuration. Post your envs and I can
> compare it with my envs. Otherwise, there exist a
> uboot file in LG site which can be used to get the
> old uboot.
Yes, the env variable specify /dev/md0 as the root as root_path.
My environment, as it is now after the changes made to boot linux
from hard disk is :
baudrate=115200 loads_echo=0 rootpath=/opt/Orion-SDK/armel-2.0/rootfs run_diag=yes console=console=ttyS0,115200 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env) CASset=min MALLOC_len=1 ethprime=egiga0 bootargs_nfs=root=/dev/nfs rw image_name=uImage boot_name=u-boot.bin up-boot=tftp 2000000 nt/$(boot_name); sflash protect off; sflash erase all; sflash write 2000000 0 $(filesize) root_path=root=/dev/md0 rw read-kern=ide reset; ext2load ide 0 2000000 /boot/$(image_name); mem-clear=mw.l 1000000 0x00000000 1000000 bootcmd_nfs=tftpboot 0x2000000 $(image_name); setenv bootargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvNetConfig) $(mvPhoneConfig); bootm 0x2000000; bootargs_usb=root=/dev/sdc2 rw rootdelay=10 bootcmd_enc=run mem-clear; set bootargs $(console) $(bootargs_ram) enclosure; ide res; ide load; bootm 1000000 2000000 bootargs_ram=root=/dev/ram0 rw tftp-ram=tftp 1000000 nt/$(uImage-ram); tftp 2000000 nt/ramdisk_image; set bootargs $(console) $(bootargs_ram); bootm 1000000 2000000 uImage-ram=uImage-2.6.30-nt1_11_ramdisk bootcmd=run bootcmd_hdd bootcmd_tftp=tftp 0x2000000 $(image_name); setenv bootargs $(console) $(root_path) lpj=4964352; bootm 0x2000000; ethmtu=1500 mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs 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 ethact=egiga0 ethaddr=00:E0:91:81:15:DC nas_type=0x00000110 firmware=firmware.tar.gz bootcmd_netenc=set bootargs $(console) $(bootargs_ram) netenc nas_type=$(nas_type) IP=$(ipaddr) SIP=$(serverip) FW=$(firmware); bootm 1000000 2000000 bootcmd_usbenc=set bootargs $(console) $(bootargs_ram) usbenc nas_type=$(nas_type) IP=$(ipaddr) SIP=$(serverip) FW=$(firmware); bootm 1000000 2000000 hdd_off_delay=4000000 arcNumber=1681 bootcmd_hdd=run read-kern; setenv bootargs $(console) $(root_path) lpj=4964352; bootm 0x2000000; bootargs_deb=console=ttyS0,115200 root=LABEL=debfs rootdelay=10 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env) earlyprintk=serial autoload=no ipaddr=10.177.190.59 netmask=netmask=255.255.254.0 bootargs_end=:::DB88FXX81:eth0:none 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=1 disaMvPnp=no hddPowerCtrl=no enaAutoRecovery=no pcieTune=no serverip=10.177.191.39
Some changes were made for Debian, which I tried to revert as
well as possible but, I guess, screwed up something in the process.
I should mention that I tried the rescue process for the new U-boot
system (new UI) but this fails as well. Probably environment being
wrong as you indicate.
In the meantime, I shall search again the LG site to find the u-boot
mentioned.
Regards.
EDIT :
You were right. One single option I overlooked was a "gateway" which
prevented the system from booting. It was straightforward after that, I
was able to restore a full standard system. I just have to figure out how
to fit it with a usb boot for Debian and I will be very happy. Many thanks.
Edited 1 time(s). Last edit at 11/02/2020 04:14AM by Jmax.
|
S
Re: LG N1T1 NAS November 08, 2020 03:47PM |
Jmax Wrote:
-------------------------------------------------------
> Some changes were made for Debian, which I tried
> to revert as
> well as possible but, I guess, screwed up
> something in the process.
> I should mention that I tried the rescue process
> for the new U-boot
> system (new UI) but this fails as well. Probably
> environment being
> wrong as you indicate.
> In the meantime, I shall search again the LG site
> to find the u-boot
> mentioned.
>
> Regards.
>
> EDIT :
> You were right. One single option I overlooked was
> a "gateway" which
> prevented the system from booting. It was
> straightforward after that, I
> was able to restore a full standard system. I just
> have to figure out how
> to fit it with a usb boot for Debian and I will be
> very happy. Many thanks.
I'm glad it worked out. I have been busy with other things and have almost forgot about the post.
Usb boot should probably be similar steps as described in other posts, haven't tested but it should likely work. Hopefully you will find a solution for it.
-------------------------------------------------------
> Some changes were made for Debian, which I tried
> to revert as
> well as possible but, I guess, screwed up
> something in the process.
> I should mention that I tried the rescue process
> for the new U-boot
> system (new UI) but this fails as well. Probably
> environment being
> wrong as you indicate.
> In the meantime, I shall search again the LG site
> to find the u-boot
> mentioned.
>
> Regards.
>
> EDIT :
> You were right. One single option I overlooked was
> a "gateway" which
> prevented the system from booting. It was
> straightforward after that, I
> was able to restore a full standard system. I just
> have to figure out how
> to fit it with a usb boot for Debian and I will be
> very happy. Many thanks.
I'm glad it worked out. I have been busy with other things and have almost forgot about the post.
Usb boot should probably be similar steps as described in other posts, haven't tested but it should likely work. Hopefully you will find a solution for it.
|
Re: LG N1T1 NAS January 11, 2021 03:04PM |
Registered: 3 years ago Posts: 5 |
Hello N1T1 owners,
I now run my device with Bodhi's Kernel 5.9.12. Finally an open system, thanks for that.
I need help putting this device on standby.
My first attempt with hdparm spoke to the HDD successfully. Unfortunately, it is reactivated after 3 minutes of running processes.
Is it possible to put the device into energy saving mode with this kernel?
Thanks in advance.
I now run my device with Bodhi's Kernel 5.9.12. Finally an open system, thanks for that.
I need help putting this device on standby.
My first attempt with hdparm spoke to the HDD successfully. Unfortunately, it is reactivated after 3 minutes of running processes.
Is it possible to put the device into energy saving mode with this kernel?
Thanks in advance.
|
Re: LG N1T1 NAS January 11, 2021 04:57PM |
Admin Registered: 13 years ago Posts: 19,114 |
gf ,
> I need help putting this device on standby.
> My first attempt with hdparm spoke to the HDD
> successfully. Unfortunately, it is reactivated
> after 3 minutes of running processes.
If the rootfs is on the HDD, then don't try to put it to sleep. It is not feasible. Only way to ensure the HDD is sleeping all the time is to have the rootfs on USB.
> Is it possible to put the device into energy
> saving mode with this kernel?
The energy saving mode is possible with this kernel CPU Frequency governor. Install cpufrequtils, and use the cpufreq-set to set the governor to what you like to. There are many modes: userspace, conservative, ondemand, powersave, and performance.
For example, my NSA325 box is set to ondemand. THe CUP is 1.6Ghz, but most of the time it is running at 533 MHz.
uname -a
cpufreq-info
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I need help putting this device on standby.
> My first attempt with hdparm spoke to the HDD
> successfully. Unfortunately, it is reactivated
> after 3 minutes of running processes.
If the rootfs is on the HDD, then don't try to put it to sleep. It is not feasible. Only way to ensure the HDD is sleeping all the time is to have the rootfs on USB.
> Is it possible to put the device into energy
> saving mode with this kernel?
The energy saving mode is possible with this kernel CPU Frequency governor. Install cpufrequtils, and use the cpufreq-set to set the governor to what you like to. There are many modes: userspace, conservative, ondemand, powersave, and performance.
For example, my NSA325 box is set to ondemand. THe CUP is 1.6Ghz, but most of the time it is running at 533 MHz.
uname -a
Linux HomeBackup 5.9.12-kirkwood-tld-1 #1.0 PREEMPT Sat Dec 5 14:05:39 PST 2020 armv5tel GNU/Linux
cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: kirkwood-cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 5.0 us.
hardware limits: 533 MHz - 1.60 GHz
available frequency steps: 1.60 GHz, 533 MHz
available cpufreq governors: ondemand, conservative, userspace, powersave, performance
current policy: frequency should be within 533 MHz and 1.60 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 533 MHz (asserted by call to hardware).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: LG N1T1 NAS January 16, 2021 08:11AM |
Registered: 3 years ago Posts: 5 |
Hello Bodhi,
#1
I wanted to undo my last change. Unfortunately I can no longer save "setenv".
See below:
# 2
In comparison with raffe's settings from 11/22/2017 05:37, it is noticeable that the following values are missing:
# 3
Can the u-boot be saved on a hard drive or USB?
The u-boot settings are based on the latest version from LG. I did not make a backup out of ignorance, so I cannot say whether the settings were missing or whether I accidentally removed them.
# 4
The status today:
~USB only: runs
~HDD only: runs
~USB / HDD both with debian and labeled "rootfs": Boot from USB, then the system is seen on the HDD and continues to load from the HDD. Since I can drive with only HDD.
~USB / empty HDD: Boot from USB, then error due to empty HDD.
Lots of construction sites. Maybe there is a solution for # 1 first.
Thanks in advance.
#1
I wanted to undo my last change. Unfortunately I can no longer save "setenv".
See below:
�Normal mode boot start! _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| ** LOADER ** ** LGE-NAS BOARD: NT1 LE U-Boot 1.1.4 (May 21 2011 - 03:56:55)NT1 U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CDEE0 Soc: 88F6281 A1 (DDR2) CPU running @ 1000Mhz L2 running @ 333Mhz SysClock = 333Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 15 tRCD=5 DRAM CS[0] base 0x00000000 size 128MB DRAM Total size 128MB 16bit width [512kB@f8000000] Flash: 512 kB Addresses 8M - 0M are saved for the U-Boot usage. Mem malloc Initialization (8M - 7M): Done 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>> printenv baudrate=115200 loads_echo=0 ipaddr=10.177.190.59 serverip=10.177.191.39 rootpath=/opt/Orion-SDK/armel-2.0/rootfs netmask=255.255.254.0 run_diag=yes console=console=ttyS0,115200 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env) CASset=min MALLOC_len=1 ethprime=egiga0 bootargs_nfs=root=/dev/nfs rw bootargs_end=:::DB88FXX81:eth0:none image_name=uImage boot_name=u-boot.bin up-boot=tftp 2000000 nt/$(boot_name); sflash protect off; sflash erase all; sflash write 2000000 0 $(filesize) root_path=root=/dev/md0 rw read-kern=ide reset; ext2load ide 0 2000000 /boot/$(image_name); mem-clear=mw.l 1000000 0x00000000 1000000 bootcmd_nfs=tftpboot 0x2000000 $(image_name); setenv bootargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvNetConfig) $(mvPhoneConfig); bootm 0x2000000; bootcmd_hdd=run read-kern; setenv bootargs $(console) $(root_path) lpj=4964352; bootm 0x2000000; bootcmd_enc=run mem-clear; set bootargs $(console) $(bootargs_ram) enclosure; ide res; ide load; bootm 1000000 2000000 bootargs_ram=root=/dev/ram0 rw tftp-ram=tftp 1000000 nt/$(uImage-ram); tftp 2000000 nt/ramdisk_image; set bootargs $(console) $(bootargs_ram); bootm 1000000 2000000 uImage-ram=uImage-2.6.30-nt1_11_ramdisk bootcmd_tftp=tftp 0x2000000 $(image_name); setenv bootargs $(console) $(root_path) lpj=4964352; bootm 0x2000000; ethmtu=1500 mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs 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 ethact=egiga0 ethaddr=00:E0:91:80:FF:E6 nas_type=0x00000110 firmware=firmware.tar.gz bootcmd_netenc=set bootargs $(console) $(bootargs_ram) netenc nas_type=$(nas_type) IP=$(ipaddr) SIP=$(serverip) FW=$(firmware); bootm 1000000 2000000 bootcmd_usbenc=set bootargs $(console) $(bootargs_ram) usbenc nas_type=$(nas_type) IP=$(ipaddr) SIP=$(serverip) FW=$(firmware); bootm 1000000 2000000 arcNumber=1681 set_mw=mw 0x800000 0 1 load_bootm=bootm 0x800000 0x2100000 load_usbuimage=ext2load usb 0:1 0x800000 /boot/uImage load_usbuinitrd=ext2load usb 0:1 0x2100000 /boot/uInitrd bootargs_usb=console=ttyS0,115200 root=LABEL=rootfs_usb rootdelay=10 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env) earlyprintk=serial bootcmd_usb=run bootargs_usb; usb start; run set_mw; run load_usbuimage; run load_usbuinitrd; run load_bootm load_myhdduimage=ext2load ide 0:1 0x800000 /boot/uImage load_myhdduinitrd=ext2load ide 0:1 0x2100000 /boot/uInitrd bootcmd_myhdd=ide reset; run set_mw; run load_myhdduimage; run load_myhdduinitrd; run load_bootm bootcmd=run bootcmd_usb; run bootcmd_myhdd; reset stdin=serial stdout=serial stderr=serial mainlineLinux=yes 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=1 disaMvPnp=no hddPowerCtrl=no enaAutoRecovery=no pcieTune=no Environment size: 2999/4092 bytes LGE-NAS>> setenv bootargs_usb 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env) earlyprintk=serial' LGE-NAS>> saveenv Saving Environment to Flash... Error: start and/or end address not on sector boundary LGE-NAS>>
# 2
In comparison with raffe's settings from 11/22/2017 05:37, it is noticeable that the following values are missing:
setenv bootargs 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env) earlyprintk=serial' setenv run_mw 'mw 0x800000 0 1' setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage' setenv load_initrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd' setenv bootargs_usb 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env) earlyprintk=serial'
# 3
Can the u-boot be saved on a hard drive or USB?
The u-boot settings are based on the latest version from LG. I did not make a backup out of ignorance, so I cannot say whether the settings were missing or whether I accidentally removed them.
# 4
The status today:
~USB only: runs
~HDD only: runs
~USB / HDD both with debian and labeled "rootfs": Boot from USB, then the system is seen on the HDD and continues to load from the HDD. Since I can drive with only HDD.
~USB / empty HDD: Boot from USB, then error due to empty HDD.
Lots of construction sites. Maybe there is a solution for # 1 first.
Thanks in advance.
|
Re: LG N1T1 NAS January 16, 2021 03:57PM |
Admin Registered: 13 years ago Posts: 19,114 |
gf ,
> I wanted to undo my last change. Unfortunately I
> can no longer save "setenv".
> LGE-NAS>> saveenv
> Saving Environment to Flash...
> Error: start and/or end address not on sector
> boundary
This error was due to a bug in this stock u-boot. So try to set the envs inside Debian after you have booted, and at Linux shell. I recall somewhere in this thread I showed how to do that. Look for the /etc/fw_env.config setup info.
> # 2
> In comparison with raffe's settings from
> 11/22/2017 05:37, it is noticeable that the
> following values are missing
You do have them set for USB booting as shown in your post above
> # 3
> Can the u-boot be saved on a hard drive or USB?
> The u-boot settings are based on the latest
> version from LG. I did not make a backup out of
> ignorance, so I cannot say whether the settings
> were missing or whether I accidentally removed
> them.
Not sure exactly what you are asking. But the envs listing can be copy/pasted to a notepad. u-boot image on flash can be dump to a file while you are inside Debian.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I wanted to undo my last change. Unfortunately I
> can no longer save "setenv".
> LGE-NAS>> saveenv
> Saving Environment to Flash...
> Error: start and/or end address not on sector
> boundary
This error was due to a bug in this stock u-boot. So try to set the envs inside Debian after you have booted, and at Linux shell. I recall somewhere in this thread I showed how to do that. Look for the /etc/fw_env.config setup info.
> # 2
> In comparison with raffe's settings from
> 11/22/2017 05:37, it is noticeable that the
> following values are missing
You do have them set for USB booting as shown in your post above
load_bootm=bootm 0x800000 0x2100000 load_usbuimage=ext2load usb 0:1 0x800000 /boot/uImage load_usbuinitrd=ext2load usb 0:1 0x2100000 /boot/uInitrd bootargs_usb=console=ttyS0,115200 root=LABEL=rootfs_usb rootdelay=10 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env) earlyprintk=serial bootcmd_usb=run bootargs_usb; usb start; run set_mw; run load_usbuimage; run load_usbuinitrd; run load_bootm load_myhdduimage=ext2load ide 0:1 0x800000 /boot/uImage load_myhdduinitrd=ext2load ide 0:1 0x2100000 /boot/uInitrd bootcmd_myhdd=ide reset; run set_mw; run load_myhdduimage; run load_myhdduinitrd; run load_bootm bootcmd=run bootcmd_usb; run bootcmd_myhdd; reset
> # 3
> Can the u-boot be saved on a hard drive or USB?
> The u-boot settings are based on the latest
> version from LG. I did not make a backup out of
> ignorance, so I cannot say whether the settings
> were missing or whether I accidentally removed
> them.
Not sure exactly what you are asking. But the envs listing can be copy/pasted to a notepad. u-boot image on flash can be dump to a file while you are inside Debian.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: LG N1T1 NAS January 17, 2021 11:51PM |
Registered: 3 years ago Posts: 5 |
Thank you Bodhi!
I found this post on Sep 27, 2016 04:24 AM.
> In the uboot installation thread: http://forum.doozan.com/read.php?3,12381
And here are my settings. I hope this helps.
My idea for the setup:
Start and operation from USB, the HDD (with rootfs for operation without USB) then as personal data storage. Then "hdparm" should also work for the HDD.
The device starts well with two options:
1. Boot from HDD (without connected USB stick)
2. Boot from USB stick (without connected HDD)
If I operate the device with a USB stick and HDD at the same time, "Linux-5.2.9-kirkwood-tld-1" and "initramfs-5.2.9-kirkwood-tld-1" are loaded from the USB.
The operating system is then reloaded from the HDD and Debian works from the HDD. But I want to stay on the USB to put the HDD to sleep.
Can you help?
Thanks in advance.
Edited 2 time(s). Last edit at 01/18/2021 01:41PM by gf.
I found this post on Sep 27, 2016 04:24 AM.
> In the uboot installation thread: http://forum.doozan.com/read.php?3,12381
And here are my settings. I hope this helps.
root@debian:~# fw_printenv
Warning: Bad CRC, using default environment
bootcmd=run distro_bootcmd
bootdelay=2
baudrate=115200
stdin=serial,cros-ec-keyb,usbkbd
stdout=serial,vidconsole
stderr=serial,vidconsole
ethaddr=00:00:11:22:33:44
eth1addr=00:00:11:22:33:45
eth3addr=00:00:11:22:33:46
eth5addr=00:00:11:22:33:47
ipaddr=1.2.3.4
host_boot=if host dev ${devnum}; then setenv devtype host; run scan_dev_for_boot_part; fi
sata_boot=if sata dev ${devnum}; then setenv devtype sata; run scan_dev_for_boot_part; fi
scsi_init=if ${scsi_need_init}; then setenv scsi_need_init false; scsi scan; fi
scsi_boot=run scsi_init; if scsi dev ${devnum}; then setenv devtype scsi; run scan_dev_for_boot_part; fi
virtio_boot=if virtio dev ${devnum}; then setenv devtype virtio; run scan_dev_for_boot_part; fi
boot_prefixes=/ /boot/
boot_scripts=boot.scr.uimg boot.scr
boot_script_dhcp=boot.scr.uimg
boot_targets=host1 host0
boot_syslinux_conf=extlinux/extlinux.conf
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}${boot_syslinux_conf}
scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${boot_syslinux_conf}; then echo Found ${prefix}${boot_syslinux_conf}; run boot_extlinux; echo SCRIPT FAILED: continuing...; fi
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}
scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done
scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done;
scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then run scan_dev_for_boot; fi; done
bootcmd_host1=setenv devnum 1; run host_boot
bootcmd_host0=setenv devnum 0; run host_boot
distro_bootcmd=setenv scsi_need_init; for target in ${boot_targets}; do run bootcmd_${target}; done
bootm_size=0x10000000
kernel_addr_r=0x1000000
fdt_addr_r=0xc00000
ramdisk_addr_r=0x2000000
scriptaddr=0x1000
pxefile_addr_r=0x2000
root@debian:~#
GNU nano 3.2 /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size $ /dev/mtd0 0xc0000 0x20000 0x20000
root@debian:~# cat /proc/mtd dev: size erasesize name mtd0: 00080000 00001000 "u-boot" root@debian:~#
My idea for the setup:
Start and operation from USB, the HDD (with rootfs for operation without USB) then as personal data storage. Then "hdparm" should also work for the HDD.
The device starts well with two options:
1. Boot from HDD (without connected USB stick)
2. Boot from USB stick (without connected HDD)
If I operate the device with a USB stick and HDD at the same time, "Linux-5.2.9-kirkwood-tld-1" and "initramfs-5.2.9-kirkwood-tld-1" are loaded from the USB.
The operating system is then reloaded from the HDD and Debian works from the HDD. But I want to stay on the USB to put the HDD to sleep.
Can you help?
Thanks in advance.
Edited 2 time(s). Last edit at 01/18/2021 01:41PM by gf.
|
Re: LG N1T1 NAS January 18, 2021 05:27PM |
Admin Registered: 13 years ago Posts: 19,114 |
gf,
This is why I have the bootargs with root device identifed by label rootfs
To make sure the HDD is not scanned by Debian when it tries to find the rootfs, check the HDD partitions label. If any of the partitions is labeled rootfs then change the partition label to something else such as Data, Music, Pictures... whatever is appropriate.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Quote
If I operate the device with a USB stick and HDD at the same time, "Linux-5.2.9-kirkwood-tld-1" and "initramfs-5.2.9-kirkwood-tld-1" are loaded from the USB.
The operating system is then reloaded from the HDD and Debian works from the HDD. But I want to stay on the USB to put the HDD to sleep.
This is why I have the bootargs with root device identifed by label rootfs
bootargs_usb=console=ttyS0,115200 root=LABEL=rootfs_usb rootdelay=10 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env) earlyprintk=serial
To make sure the HDD is not scanned by Debian when it tries to find the rootfs, check the HDD partitions label. If any of the partitions is labeled rootfs then change the partition label to something else such as Data, Music, Pictures... whatever is appropriate.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: LG N1T1 NAS January 19, 2021 12:14PM |
Registered: 3 years ago Posts: 5 |
Hello Bodhi!
For this reason, I have already changed the entry "root =" to "rootfs_usb" in the past. The HDD has the label "data"
1st part
Here a start with USB "rootfs" and an empty HDD "data". It is always started and loaded from USB, but /root is then expected on the HDD.
Can this be the reason?
2nd part
Unfortunately, my empty HDD is no longer ready. I take my HDD with Debian from here.
But it makes no difference in the result, it is satisfactory.
If you enter it manually, sdb = USB and sda = HDD
/root is on sdb
This result when entered manually is good!
But what can you do for "1st part" so that /root is not searched for on sda?
Thanks in advance.
Edited 2 time(s). Last edit at 01/19/2021 03:30PM by gf.
For this reason, I have already changed the entry "root =" to "rootfs_usb" in the past. The HDD has the label "data"
root=LABEL=rootfs_usb
My USB now has the label "rootfs" again, and it starts anyway!
1st part
Here a start with USB "rootfs" and an empty HDD "data". It is always started and loaded from USB, but /root is then expected on the HDD.
Can this be the reason?
Kernel command line: console=ttyS0,115200n8 earlyprintk root=/dev/sda1 rootdelay=10
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__| ** LOADER **
** LGE-NAS BOARD: NT1 LE
U-Boot 1.1.4 (May 21 2011 - 03:56:55)NT1
U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CDEE0
Soc: 88F6281 A1 (DDR2)
CPU running @ 1000Mhz L2 running @ 333Mhz
SysClock = 333Mhz , TClock = 200Mhz
DRAM CAS Latency = 5 tRP = 5 tRAS = 15 tRCD=5
DRAM CS[0] base 0x00000000 size 128MB
DRAM Total size 128MB 16bit width
[512kB@f8000000] Flash: 512 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
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
Unknown command 'console=ttyS0,115200' - try 'help'
(Re)start USB...
USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
....
.
......
............
4975560 bytes read
....
.
......
............
9788570 bytes read
## Booting image at 00800000 ..., header_size = 00000040, header_addr = 0068dcdc
image_header_t hdr contents
hdr->ih_magic = 56190527, hdr->ih_hcrc = 2a469a26
hdr->ih_time = 2d9a0460, hdr->ih_size = 004beb88
hdr->ih_load = 00800000, hdr->ih_ep = 00800000
hdr->ih_dcrc = 7d8590d3
hdr->ih_os = 05, hdr->ih_arch = 02
hdr->ih_type = 02, hdr->ih_comp = 00
hdr->ih_name = Linux-5.2.9-kirkwood-tld-1
Image Name: Linux-5.2.9-kirkwood-tld-1
Created: 2021-01-17 20:12:29 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4975496 Bytes = 4.7 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 02100000, header_addr = 0068dcdc, header_size = 00000040 ...
RAMdisk image_header_t hdr contents
hdr->ih_magic = 56190527, hdr->ih_hcrc = cad6b62c
hdr->ih_time = bdab0460, hdr->ih_size = 00955c5a
hdr->ih_load = 00000000, hdr->ih_ep = 00000000
hdr->ih_dcrc = cbb7b960
hdr->ih_os = 05, hdr->ih_arch = 02
hdr->ih_type = 03, hdr->ih_comp = 01
hdr->ih_name = initramfs-5.2.9-kirkwood-tld-1
Image Name: initramfs-5.2.9-kirkwood-tld-1
Created: 2021-01-17 21:27:25 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 9788506 Bytes = 9.3 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000][ T0] Booting Linux on physical CPU 0x0
[ 0.000000][ T0] Linux version 5.2.9-kirkwood-tld-1 (root@tldDebian) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 PREEMPT Sat Aug 17 15:00:56 PDT 2019
[ 0.000000][ T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000][ T0] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000][ T0] OF: fdt: Machine model: LG N1T1
[ 0.000000][ T0] printk: bootconsole [earlycon0] enabled
[ 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,115200n8 earlyprintk root=/dev/sda1 rootdelay=10
[ 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: 104756K/131072K available (9216K kernel code, 868K rwdata, 3400K rodata, 1024K init, 301K bss, 26316K 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.000010][ T0] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[ 0.008524][ T0] Switching to timer-based delay loop, resolution 5ns
[ 0.015971][ T0] Console: colour dummy device 80x30
[ 0.021176][ T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[ 0.032401][ T0] pid_max: default: 32768 minimum: 301
[ 0.038102][ T0] LSM: Security Framework initializing
[ 0.043641][ T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.050990][ T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.059699][ T0] *** VALIDATE proc ***
[ 0.063977][ T0] *** VALIDATE cgroup1 ***
[ 0.068249][ T0] *** VALIDATE cgroup2 ***
[ 0.072644][ T0] CPU: Testing write buffer coherency: ok
[ 0.080092][ T1] Setting up static identity map for 0x100000 - 0x100058
[ 0.087251][ T1] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.093430][ T1] rcu: Hierarchical SRCU implementation.
[ 0.102615][ T1] devtmpfs: initialized
[ 0.113174][ T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.123759][ T1] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.130873][ T1] xor: measuring software checksum speed
[ 0.228550][ T1] arm4regs : 907.200 MB/sec
[ 0.328552][ T1] 8regs : 544.800 MB/sec
[ 0.428551][ T1] 32regs : 792.000 MB/sec
[ 0.433416][ T1] xor: using function: arm4regs (907.200 MB/sec)
[ 0.439618][ T1] prandom: seed boundary self test passed
[ 0.450203][ T1] prandom: 100 self tests passed
[ 0.454979][ T1] pinctrl core: initialized pinctrl subsystem
[ 0.462456][ T1] NET: Registered protocol family 16
[ 0.468213][ T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.476744][ T1] audit: initializing netlink subsys (disabled)
[ 0.484244][ T14] audit: type=2000 audit(0.470:1): state=initialized audit_enabled=0 res=1
[ 0.492800][ T1] cpuidle: using governor ladder
[ 0.497656][ T1] cpuidle: using governor menu
[ 0.502902][ T1] Feroceon L2: Enabling L2
[ 0.507196][ T1] Feroceon L2: Cache support initialised.
[ 0.520111][ T1] No ATAGs?
[ 2.568533][ C0] random: fast init done
.
.
.
.
.
13.030187][ T114] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl F300)
[ 13.050911][ T1] Key type encrypted registered
[ 13.055814][ T114] ata2.00: ATAPI: HL-DT-STDVDRAM GA31N, T106, max UDMA/100
[ 13.092476][ T114] ata2.00: configured for UDMA/100
[ 13.130107][ T15] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 13.240217][ T23] scsi 1:0:0:0: CD-ROM HL-DT-ST DVDRAM GA31N T106 PQ: 0 ANSI: 5
[ 13.337375][ T15] usb 1-1: New USB device found, idVendor=058f, idProduct=6387, bcdDevice= 1.12
[ 13.346342][ T15] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 13.354257][ T15] usb 1-1: SerialNumber: 12D48FF4
[ 13.359957][ T15] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 13.371319][ T1] Freeing unused kernel memory: 1024K
[ 13.377182][ T1] Checked W+X mappings: passed, no W+X pages found
[ 13.384005][ T15] scsi host2: usb-storage 1-1:1.0
[ 13.389614][ T1] Run /init as init process
Loading, please wait...
Starting version 241
[ 14.217031][ T170] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 14.402142][ T175] usbcore: registered new interface driver uas
[ 14.412374][ T23] scsi 2:0:0:0: Direct-Access 8.07 PQ: 0 ANSI: 4
[ 14.432690][ T116] sd 2:0:0:0: [sdb] 7831552 512-byte logical blocks: (4.01 GB/3.73 GiB)
[ 14.449315][ T116] sd 2:0:0:0: [sdb] Write Protect is off
[ 14.460129][ T116] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 14.487480][ T116] sdb: sdb1
[ 14.496311][ T116] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[ 14.624951][ T170] sr 1:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[ 14.655916][ T170] cdrom: Uniform CD-ROM driver Revision: 3.20
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.
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/sda1 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) [ 167.130139][ C0] random: crng init done
2nd part
Unfortunately, my empty HDD is no longer ready. I take my HDD with Debian from here.
But it makes no difference in the result, it is satisfactory.
If you enter it manually, sdb = USB and sda = HDD
/root is on sdb
usb start ext2load usb 0:1 0x800000 /boot/uImage ext2load usb 0:1 0x2100000 /boot/uInitrd setenv console console=ttyS0,115200 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env) setenv bootargs_usb root=LABEL=rootfs rw rootdelay=10 rootfstype=ext3 setenv bootargs $(console) $(bootargs_usb) bootm 0x800000 0x2100000
## Booting image at 00800000 ..., header_size = 00000040, header_addr = 0068dcdc image_header_t hdr contents hdr->ih_magic = 56190527, hdr->ih_hcrc = 2a469a26 hdr->ih_time = 2d9a0460, hdr->ih_size = 004beb88 hdr->ih_load = 00800000, hdr->ih_ep = 00800000 hdr->ih_dcrc = 7d8590d3 hdr->ih_os = 05, hdr->ih_arch = 02 hdr->ih_type = 02, hdr->ih_comp = 00 hdr->ih_name = Linux-5.2.9-kirkwood-tld-1 Image Name: Linux-5.2.9-kirkwood-tld-1 Created: 2021-01-17 20:12:29 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4975496 Bytes = 4.7 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK ## Loading Ramdisk Image at 02100000, header_addr = 0068dcdc, header_size = 00000040 ... RAMdisk image_header_t hdr contents hdr->ih_magic = 56190527, hdr->ih_hcrc = cad6b62c hdr->ih_time = bdab0460, hdr->ih_size = 00955c5a hdr->ih_load = 00000000, hdr->ih_ep = 00000000 hdr->ih_dcrc = cbb7b960 hdr->ih_os = 05, hdr->ih_arch = 02 hdr->ih_type = 03, hdr->ih_comp = 01 hdr->ih_name = initramfs-5.2.9-kirkwood-tld-1 Image Name: initramfs-5.2.9-kirkwood-tld-1 Created: 2021-01-17 21:27:25 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 9788506 Bytes = 9.3 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.000000][ T0] Booting Linux on physical CPU 0x0 [ 0.000000][ T0] Linux version 5.2.9-kirkwood-tld-1 (root@tldDebian) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 PREEMPT Sat Aug 17 15:00:56 PDT 2019 [ 0.000000][ T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000][ T0] CPU: VIVT data cache, VIVT instruction cache [ 0.000000][ T0] OF: fdt: Machine model: LG N1T1 [ 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 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env) root=LABEL=rootfs rw rootdelay=10 rootfstype=ext3 [ 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: 104756K/131072K available (9216K kernel code, 868K rwdata, 3400K rodata, 1024K init, 301K bss, 26316K 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.000010][ T0] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns [ 0.000052][ T0] Switching to timer-based delay loop, resolution 5ns [ 0.000927][ T0] Console: colour dummy device 80x30 [ 0.000981][ T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000) [ 0.001011][ T0] pid_max: default: 32768 minimum: 301 [ 0.001432][ T0] LSM: Security Framework initializing [ 0.001639][ T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.001669][ T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.002635][ T0] *** VALIDATE proc *** [ 0.002921][ T0] *** VALIDATE cgroup1 *** [ 0.002950][ T0] *** VALIDATE cgroup2 *** [ 0.003058][ T0] CPU: Testing write buffer coherency: ok [ 0.004899][ T1] Setting up static identity map for 0x100000 - 0x100058 [ 0.005223][ T1] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3 , , , Debian GNU/Linux 10 debian ttyS0 debian login: root Password: Last login: Tue Jan 19 12:16:30 PST 2021 on ttyS0 Linux debian 5.2.9-kirkwood-tld-1 #1 PREEMPT Sat Aug 17 15:00:56 PDT 2019 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:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 3.7T 0 disk |-sda1 8:1 0 10G 0 part `-sda2 8:2 0 3.6T 0 part sdb 8:16 1 3.8G 0 disk `-sdb1 8:17 1 3.8G 0 part / sr0 11:0 1 1024M 0 rom mtdblock0 31:0 0 512K 0 disk root@debian:~# mount /dev/sda2 /mnt/ [ 793.066493][ T1628] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) root@debian:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 3.7T 0 disk |-sda1 8:1 0 10G 0 part `-sda2 8:2 0 3.6T 0 part /mnt sdb 8:16 1 3.8G 0 disk `-sdb1 8:17 1 3.8G 0 part / sr0 11:0 1 1024M 0 rom mtdblock0 31:0 0 512K 0 disk root@debian:~#
This result when entered manually is good!
But what can you do for "1st part" so that /root is not searched for on sda?
Thanks in advance.
Edited 2 time(s). Last edit at 01/19/2021 03:30PM by gf.
|
Re: LG N1T1 NAS January 19, 2021 03:44PM |
Admin Registered: 13 years ago Posts: 19,114 |
gf,
It should be always:
So in serial console, set it
The HDD is always initialized first in the kernel so it will take /dev/sda1. With the root label, you don't care how the kernel initialize the drives, it always look for a partition with label rootfs to mount as root.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
It should be always:
root=LABEL=rootfs
So in serial console, set it
setenv bootargs_usb 'console=ttyS0,115200 root=LABEL=rootfs_usb rootdelay=10 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env) earlyprintk=serial'
The HDD is always initialized first in the kernel so it will take /dev/sda1. With the root label, you don't care how the kernel initialize the drives, it always look for a partition with label rootfs to mount as root.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: LG N1T1 NAS January 20, 2021 02:19PM |
Registered: 3 years ago Posts: 5 |
Hello Bodhi!
Thank you for your help!
"saveenv" always worked. The change to "rootfs_usb" was my last entry.
Unfortunately "saveenv" can no longer be executed since then.
I am not sure what to do. Can you show me the place where you showed it?
Thanks in advance!
Thank you for your help!
"saveenv" always worked. The change to "rootfs_usb" was my last entry.
Unfortunately "saveenv" can no longer be executed since then.
LGE-NAS>> setenv bootargs_usb 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env) earlyprintk=serial'
LGE-NAS>> saveenv
Saving Environment to Flash...
Error: start and/or end address not on sector boundary
LGE-NAS>>
You gave me the hint for this:
Quote
This error was due to a bug in this stock u-boot. So try to set the envs inside Debian after you have booted, and at Linux shell. I recall somewhere in this thread I showed how to do that. Look for the /etc/fw_env.config setup info.
I am not sure what to do. Can you show me the place where you showed it?
Thanks in advance!
|
Re: LG N1T1 NAS January 20, 2021 03:50PM |
Admin Registered: 13 years ago Posts: 19,114 |
gf,
> Unfortunately "saveenv" can no longer be executed
> since then.
For now, use the new envs settings with the label, and make sure you can boot flawlessly.
> I am not sure what to do. Can you show me the
> place where you showed it?
Probably in this thread somewhere. Look for
/etc/fw_env.config
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Unfortunately "saveenv" can no longer be executed
> since then.
For now, use the new envs settings with the label, and make sure you can boot flawlessly.
> I am not sure what to do. Can you show me the
> place where you showed it?
Probably in this thread somewhere. Look for
/etc/fw_env.config
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
anestef
Re: LG N1T1 NAS September 05, 2022 10:27AM |
|
Re: LG N1T1 NAS October 14, 2024 02:04PM |
Registered: 8 weeks ago Posts: 2 |
Hello All,
I know this is a really old thread, but I just pulled my old LG NAS N1T1DD1 out of storage and just wanted to play around with it. What I am finding is that SMB is v1.5 and won't work on certain devices and NFS won't work on other devices like the FireStick via Kodi because of permissions that I apparently need to be able to SSH into the NAS to get functional.
So, I have a few questions on how to proceed:
1. Will simply flashing the Tantalus firmware suffice in accomplishing the above goals? If so, does anyone have access to this firmware? I followed the link in this thread and the site was down. Wayback machine shows it not being archived at all.
2. If that won't do it or I can't locate the firmware, will the method listed here allow me accomplish this? If so, is there a way to accomplish this without soldering? I haven't soldered in about 25 years or so and don't even know if I still have an iron and such lying around to do so.
Anyway, thanks in advance for any help provided and great job to those that put this build together!
I know this is a really old thread, but I just pulled my old LG NAS N1T1DD1 out of storage and just wanted to play around with it. What I am finding is that SMB is v1.5 and won't work on certain devices and NFS won't work on other devices like the FireStick via Kodi because of permissions that I apparently need to be able to SSH into the NAS to get functional.
So, I have a few questions on how to proceed:
1. Will simply flashing the Tantalus firmware suffice in accomplishing the above goals? If so, does anyone have access to this firmware? I followed the link in this thread and the site was down. Wayback machine shows it not being archived at all.
2. If that won't do it or I can't locate the firmware, will the method listed here allow me accomplish this? If so, is there a way to accomplish this without soldering? I haven't soldered in about 25 years or so and don't even know if I still have an iron and such lying around to do so.
Anyway, thanks in advance for any help provided and great job to those that put this build together!
|
Re: LG N1T1 NAS October 14, 2024 02:54PM |
Admin Registered: 13 years ago Posts: 19,114 |
Paseo92,
> 2. If that won't do it or I can't locate the
> firmware, will the method listed here allow me
> accomplish this?
This working thread resulted in the LG N1T1 DTS which is included in the Debian rootfs (the latest is Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2).
See the basic steps to install Debian with stock u-boot in the Wiki thread.
Since this box does not have new u-boot, it does require serial console to install.
> If so, is there a way to
> accomplish this without soldering? I haven't
> soldered in about 25 years or so and don't even
> know if I still have an iron and such lying around
> to do so.
>
Have you opened the box? if you are lucky, the serial header is already populated by the manufacturer.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> 2. If that won't do it or I can't locate the
> firmware, will the method listed here allow me
> accomplish this?
This working thread resulted in the LG N1T1 DTS which is included in the Debian rootfs (the latest is Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2).
See the basic steps to install Debian with stock u-boot in the Wiki thread.
Quote
Kirkwood plugs
Boot Kirkwood rootfs with stock u-boot
Since this box does not have new u-boot, it does require serial console to install.
> If so, is there a way to
> accomplish this without soldering? I haven't
> soldered in about 25 years or so and don't even
> know if I still have an iron and such lying around
> to do so.
>
Have you opened the box? if you are lucky, the serial header is already populated by the manufacturer.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: LG N1T1 NAS October 15, 2024 04:19PM |
Registered: 8 weeks ago Posts: 2 |
Hi Bodhi,
Thank you for your reply.
What exactly do you mean by new u-boot? I updated the u-boot to the latest version LG had which was 111223. This is considered the new u-boot via LG, but I think you are referring to another u-boot, right?
I also upated the firmware to 10124. I'm sure this doesn't matter, just putting it out there.
I actually did open it to upgrade the HDD to a 2TB SSD, but I wasn't paying attention at that time. I will pull it apart when the kids aren't using it (got a sick one at home streaming Usavich).
Thanks again,
Jeremy
Thank you for your reply.
What exactly do you mean by new u-boot? I updated the u-boot to the latest version LG had which was 111223. This is considered the new u-boot via LG, but I think you are referring to another u-boot, right?
I also upated the firmware to 10124. I'm sure this doesn't matter, just putting it out there.
I actually did open it to upgrade the HDD to a 2TB SSD, but I wasn't paying attention at that time. I will pull it apart when the kids aren't using it (got a sick one at home streaming Usavich).
Thanks again,
Jeremy
|
Re: LG N1T1 NAS October 15, 2024 06:24PM |
Admin Registered: 13 years ago Posts: 19,114 |
Hi Jeremy,
> What exactly do you mean by new u-boot? I updated
> the u-boot to the latest version LG had which was
> 111223. This is considered the new u-boot via LG,
That is still stock u-boot, which is quite limited.
> but I think you are referring to another u-boot,
> right?
Right. The other Kirkwood boxes have new u-boot, see here. But this LN N1T1 does not (I would have developed one for this box if there were interest back then).
> I also upated the firmware to 10124. I'm sure this
> doesn't matter, just putting it out there.
It does not matter much, if at all. When you install Debian rootfs and boot with stock u-boot, just follow the instruction I posted using serial console.
> I actually did open it to upgrade the HDD to a 2TB
> SSD, but I wasn't paying attention at that time. I
> will pull it apart when the kids aren't using it
> (got a sick one at home streaming Usavich).
Then it's in important operation. When you get to install the Debian rootfs on USB/HDD, remember to not saving u-boot envs. Avoid doing saveenv until you are satisifed that you want to use Debian .
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> What exactly do you mean by new u-boot? I updated
> the u-boot to the latest version LG had which was
> 111223. This is considered the new u-boot via LG,
That is still stock u-boot, which is quite limited.
> but I think you are referring to another u-boot,
> right?
Right. The other Kirkwood boxes have new u-boot, see here. But this LN N1T1 does not (I would have developed one for this box if there were interest back then).
> I also upated the firmware to 10124. I'm sure this
> doesn't matter, just putting it out there.
It does not matter much, if at all. When you install Debian rootfs and boot with stock u-boot, just follow the instruction I posted using serial console.
> I actually did open it to upgrade the HDD to a 2TB
> SSD, but I wasn't paying attention at that time. I
> will pull it apart when the kids aren't using it
> (got a sick one at home streaming Usavich).
Then it's in important operation. When you get to install the Debian rootfs on USB/HDD, remember to not saving u-boot envs. Avoid doing saveenv until you are satisifed that you want to use Debian .
Quote
https://forum.doozan.com/read.php?2,102054,105374#msg-105374
Since setenvs are transient, after test boot a few times with the above setenvs, you can proceed to make the envs permanent before boot.
saveenv
boot
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
